Internal end points load balancing

I have a cloud service with a web role of 4 instances, having 2 internal end points. I found that for internal end points azure load balancing is not supported. My question here is how to configure my own load balancer for my web role instances and
if scale up happens based on CPU utilization can those scales instances included in my own load balancer. is auto scaling can be detected by my own load balancer.

What do you mean by 'your own load balancer' ? are you pointing to the Azure traffic manager?
If you have configured the auto scaling on your cloud service and if it is kicked in, azure load balancer will consider newly added / deleted role instances automatically.
Bhushan | http://www.passionatetechie.blogspot.com | http://twitter.com/BhushanGawale

Similar Messages

BPEL End Point URL using External Load Balancer URL

Hi All,
We have Oracle SOA Suite installed in a clustered environment as per the Enterprise Deployment Guide 10g Release 310.1.3.3.0 E10294-02.
I have deployed a BPEL process to the clustered environment and the end point refers to the internal url of the load balancer e.g. http://internallink:8001/orabpel/default/testService/1.0
When we just paste this end point in a browser, enter the parameters and click on invoke, the BPEL Process gets invoked.
However, if we try to use the external url(which is on https) of the load balancer as the enpoint url eg https://externallink/orabpel/default/testService/1.0 to invoke the same BPEL process, the page which is used to accept the parameters and the used to invoke the BPEL process is successfully displayed. However, when we try to invoke the service, the connection times out.
Please note that internallink and externallink are the internal and external VIPs, respectively.
Does someone have an idea of what may be wrong or what needs to be corrected to be able to invoke the BPEL process using the external VIP, please?
Thanks in advance.

Check if the port of ESB in your server is open.
I think that the port is: 7777
try from ESB server:
wget WSDLURI
if you got the file then the port is closed.

Load balancing SMA web service and SMA end point URL

Hi,
We have set up the recommended 3 servers with Azure Pack, SMA Web Service and Runbook Worker. We are now wanting to configure the Azure pack portal to setup the SMA endpoint url for the web service. Before we do that, we are assuming we should
load balance the web services to answer on 1 url (ie, smaws.domainname.com).
1. Is there any guidance or things to consider when load balancing the 3 web services to answer to 1 url. We will probably use f5 since that is what we use.
2. The end point url that we configure for Azure Pack automation should be this load balanced URL correct?
3. Should we have the Azure pack installed on just one of the servers or all 3. We did all 3 but it seems like server2 and 3 just redirect to 1 anyway so I am assuming the URL for Azure pack is stored in a db somewhere.
4. Are there any other components of SMA/Azure Pack that should also be load balanced?
Thanks
Thanks Lance

So in this case you need to register the SMA Runbook Workers (do this on machine 1):
$webService
= "https://localhost"
$workers
= (Get-SmaRunbookWorkerDeployment
-WebServiceEndpoint
$webService).ComputerName
if($workers
-isnot [system.array]) {$workers
= @($workers)}
$workers
+= "MachineName2"
$workers += "MachineName3"
New-SmaRunbookWorkerDeployment
-WebServiceEndpoint
$webService -ComputerName
$workers

Site not accessible from the Load balanced web front end server - sharepoint 2010

I have a production environment with 2 WFE's(sp-wfe1 & sp-wfe2), 2 APP's and 2 SQL clustered VM's.
2 WFE's are load balanced using hardware load balancer.
An A-Record(PORTAL) is created in DNS for the virtual IP of the load balancer which points to the 2 WFE's.
A web application is created on the WFE's on port 80.
alternative access mapping is configured and the load balanced record "http://PORTAL" is used under the default zone.
Under IIS I have edited the bindings for the sharepoint site at port 80 and added the HOSTNAME as PORTAL.
Result: The site is accessible from outside the server and works fine.
ISSUE: The site is not accessible within the WFE's(sp-wfe1 & sp-wfe2).
When I browse the site from the WFE's server it ask for the credentials and when I enter the credentials and click OK it ask the credentials again and again and in the end displays a blank page.
Kindly help me in this issue because I am clueless and couldn't find anything helpful on the internet.
Regards,
Mudassar
MADDY-DEV Forum answers from Microsoft Forum

Loop back check.
http://www.harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx

Lync Server Front End 2 Hardware Load Balancer IP

I currently have the following Setup.
I only have 1 Hardware Load Balanced IP for my Front End Pool.
After running the Lync Planning Tool it actually states that i need 2 Hardware Load Balanced IP, 1 for internal and 1 for external.
My question would be would i be able to configure for mobility and external access with just using 1 Hardware Load Balanced IP?
Because i seem to have problem with connecting to the front end server based on the following scenario.
Without Reverse Proxy Mapping (port 80/443 internet to port 80/443 reverse proxy to port 80/443 lyncpool frontend)
Internal Access (No Issue)
Lync Mobile 2013 App (Can Connect and chat but intermittent connection) *gets disconnected if i access video/audio
Lync Client 2013 Externally (Cannot Connect to Server)
https://meet.domain.com (working)
With Reverse Proxy Mapping (Port 80/443 internet to port 8080/4443 reverse proxy to port 8080/4443 lyncpool frontend)
Internal Access (No Issue)
Lync Mobile 2013 App (Cannot connect)
Lync Client 2013 Externally (Cannot connect)
https://meet.domain.com (Not working)
Would i actually need to have a additional front end pool IP for external access? or can i maintain it as it is?
I do not understand why without the mapping it can work whereas if i do the mapping according to technet article it won't work.
Everything is running windows server 2012 R2 and Lync 2013, Loadbalancer / Reverse Proxy is the same F5 Appliance
Any assistance on this is greatly appreciated.

Hi Greg,
I have been making use of it (https://testconnectivity.microsoft.com/) to test my autodiscover and remote
access.
Like i mentioned it is weird that without doing port mapping from 80/443 to 8080/4443 i was able to pass
the autodiscovery and all but once i changed to the proper steps to do port mapping it stopped working.
and im not using TMG but using a F5 Hardware Reverse Proxy which also happen to be my Load Balancing Appliance.
Is there anyone who can help give me more details if i need 2 VIP for the front end ?

Lync 2013 Enterprise load balancing on the front end and edge pool

Hi,
I am setting up a Lync 2013 Enterprise deployment consisting of a Front End pool (x2 FE servers) and an Edge pool (x2 Edge servers). I'm seeing some conflicting advice regarding load balancing using hardware or DNS for the front end and the edge.
On the front end I have 2 internal DNS records 'lyncfepool1.contoso.local' each of which map to one of the IPs of the FE servers. I've used my details to populate the Detailed Design Planner excel spreadsheet and am told that I require a HLB to load
balance my front end pool. I'm aware of the need to load balance HTTPS traffic internally (which will be done by TMG) however other traffic to the front end (SIP, etc) can be balanced by DNS only, and not require a HLB?
Can someone clarify the front end requirement?
Also - looking now at the edge pool - this site again have two edge servers in a pool. We are using a total of six private IP addresses, two per edge service (2 x av.contoso.com, 2 x sip.contoso.com and 2 x webcon.contoso.com). These will be
NAT'ed by the external firewall and directed to the respective external (DMZ) IP addresses on the Edge servers on port 443. I know this isn't true roundrobin due to the intelligence of the Lync client when connecting (in that the Lync client will connect
to one of the public IPs and if it can't connect, it will know to connect to the other service IP), however I want to clarify this set up, particularly the need to direct the external public IP traffic at the DMZ Edge IP specified in the topology builder.
I've attached a basic diagram of the external/DMZ/Edge side which hopefully helps with this question
Persevere, Persevere, Per..

That is because you will always need HLB for a front-end server since it hosts the Lync webservices which use HTTP/HTTPS traffic.
The description on the calculation tool also describes this correctly:
Supports Standard and Enterprise pools (up to 12 nodes), with pure device-based load balancing or a combination of DNS load balancing and device-based load balancing (for
Lync web services)
You can use either Hardware or DNS loadbalancing for SIP traffic only, but you will always need a HLB for the webservices. Both are applicable for the Front-End so you have either
full HLB for both SIP and HTTP(S) traffic
DNS LB for SIP traffic and HLB for HTTP(S) traffic
Hope this is more clear :-)
Lync Server MVP | MCITP Lync Server 2010 | If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.

Site not found using Sharepoint Designer 2013, Load balance URL and the Front end servers.

Dears,
My SharePoint farm is with the below configuration in our office :
Batch processing server the with Central Administration
Web Front End Sever 1 (http://wfe01)
Web Front End Sever 2 (http://wfe02)
I do have the load balance URL as http://finance.mycompany.com and as per the system administrator it seems configured properly.
In AAM i have mapped the URLs as below for the web application in Central Administration portal:
http://finance.mycompany.com - Default Zone
http://wfe01 - Intranet Zone
http://wfe02 - Internet Zone
I was able to browse the site via the load balance URL : http://finance.mycompany.com, but couldn't open the site using the Share Point Designer 2013. It always says the site not found.
please advise,
thanks,
Ammar

What do the wfe01 and wfe02 aams do?
Are you browsing to the SharePoint site and using SPD on the same computer, is it part of the farm or a seperate client computer?
thanks Alex a lot for your response and appreciate the same.
WFE01, WFE01 is connected to the one central admin on Batch Processing Server (central admin URL is http://SharepointCA:5555 and the SharePoint Web Application is hosted under port 80 on the same server). So the AAM configured on the batch processing server
central admin.
I can connect to the site using the SPD inside the Batch Processing server if i mention the site urs as http://localhost. But not from other client computers by putting the load balance URL - http://finance.mycompany.com.
I can browse the sites directly putting http://wfe01, http://wfe02 and as well as the load balance URL (http://finance.mycompany.com). The custom webparts are getting crashed when i put the web application URL as http://finance.mycompany.com.
thanks,
Ammar

Lync Discover Internal Load Balance

I have tried using DNS and hardware load balancing for the lyncdiscoverinternal A record,
If I disable the NIC on one of my 2 front end servers in my pool that the client is connected to it gets signed out,
the client does not then sign back in for about 2 minutes.
Can someone explain why the client takes so long to try another server in the pool and re-try the signing to a different FE server as 2 minutes is too long...
I have 2 servers in a pool called pool.domain.com and the srv record points to pool.domain.com
I have 2 A records for pool.domain.com pointing to each FE server
I also have a director pool, will pointing the pool.domain.com srv record for _sip to this pool improve failover speed?
***Don't forget to mark helpful or answer***

i tried doing the full HLB method (using f5) and during testing it seems lync itself doesnt want to support that (which is why microsoft recommends DNS AND HLB i am betting). What i saw in my testing was after the node you were on was "failed" the
lync client went to its secondary via the list of servers it gets when it first connects, so instead of connecting to the VIP of the HLB, it connected directly to a front-end server that was listed as secondary for that user at that point.
Doing the combination of HLB and DNS LB, the time it takes for the client to connect seemed to be much less (under 10 seconds in my tests). I hate that i have to use both technologies, if they are going to force you to use HLB (for web servcies), they
should let everything work via that method...

Why do I have to overide internal Lyncpool FQDN when using hardware load balancing

Hi!
As the title says, why do I need to override the FQDN when using HLB? Why can't I just change the DNS entry of lyncpool01.domain.com to point to the HLB?
Thanks!

You'd want to override it because there are non-HTTP/HTTPS ports involved that are better load balanced using DNS.
http://social.technet.microsoft.com/wiki/contents/articles/22988.demystify-hlb-and-dns-load-balancing-lync-2013-topology-with-high-availability-pools-dns-lb-vs-hlb.aspx
http://technet.microsoft.com/en-us/library/gg615011.aspx
If you want to use HLB for all internal ports, then you wouldn't necessarily need to override this.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Geting IP address for Internal Load Balancer

I've recently been experimenting with internal load balancing for VMs. I'm able to create and delete an internal load balancer (ILB) using the .NET wrapper for the API (https://github.com/Azure/azure-sdk-for-net). What I cannot do though is actually
get the internal address for it. Nor does it seem you can get it from the REST API (which, as far as I know, is what .NET wrapper wraps). The only method I can see that claims to get the address is Powershell.
Can anyone confirm if there is any way using the REST API or its .NET wrapper to obtain the internal address for the ILB?

I have not looked into the .NET wrapper that you mentioned here, but according to this powershell script:
http://msdn.microsoft.com/en-us/library/azure/dn690125.aspx
$svc="<Cloud Service Name>"
$ilb="<Name of your ILB instance>"
$subnet="<Name of the subnet within your virtual network-optional>"
$IP="<The IPv4 address to use on the subnet-optional>"
Add-AzureInternalLoadBalancer -ServiceName $svc -InternalLoadBalancerName $ilb –SubnetName $subnet –StaticVNetIPAddress $IP
IP address is optional, so maybe the wrapper hasn't implemented this, which is kind of undesirable. But maybe it allows you to specify the IP?
Frank

Internal load balance ilb on ServiceConfiguration LoadBalancers

Hi everybody, I try to setup an internal load balancer using this configuration:
from cscfg:
<NetworkConfiguration>
<VirtualNetworkSite name="WE" />
<AddressAssignments>
  <InstanceAddress roleName="Role1">
   <Subnets>
    <Subnet name="WE_WWW" />
   </Subnets>
  </InstanceAddress>
  <InstanceAddress roleName="Role">
   <Subnets>
    <Subnet name="WE_SERVICE" />
   </Subnets>
  </InstanceAddress>
</AddressAssignments>
<LoadBalancers>
  <LoadBalancer name="WEB_ILB">
   <FrontendIPConfiguration type="private" subnet="WE_WWW" staticVirtualNetworkIPAddress="192.168.1.5" />
  </LoadBalancer>
  <LoadBalancer name="API_ILB">
   <FrontendIPConfiguration type="private" subnet="WE_SERVICE" staticVirtualNetworkIPAddress="192.168.2.5" />
  </LoadBalancer>
</LoadBalancers>
</NetworkConfiguration>
from csdef:
<WebRole name="Role1" vmsize="Small">
<Sites>
  <Site name="Web">
   <Bindings>
    <Binding name="httpIn" endpointName="httpIn" />
    <Binding name="httpsIn" endpointName="httpsIn" />
   </Bindings>
  </Site>
</Sites>
<Endpoints>
  <InputEndpoint name="httpIn" protocol="http" port="80" loadBalancer="WEBILB" />
  <InputEndpoint name="httpsIn" protocol="https" port="443" certificate="Valuta" />
</Endpoints>
<Imports>
  <Import moduleName="Diagnostics" />
  <Import moduleName="RemoteAccess" />
  <Import moduleName="RemoteForwarder" />
</Imports>
<Certificates>
  <Certificate name="Valuta" storeLocation="LocalMachine" storeName="CA" />
</Certificates>
</WebRole>
<WebRole name="Role2" vmsize="Small">
<Sites>
  <Site name="Web">
   <Bindings>
    <Binding name="httpIn" endpointName="httpIn" />
   </Bindings>
  </Site>
</Sites>
<Endpoints>
  <InputEndpoint name="httpIn" protocol="http" port="8080" loadBalancer="APIILB" />
</Endpoints>
<Imports>
  <Import moduleName="Diagnostics" />
  <Import moduleName="RemoteAccess" />
</Imports>
</WebRole>
as you can see I have two webroles linked to a vnet:
Role1 has two input endpoint: https and http (the one I want to "internal" load balance)
Role2 has only an http input endpoint (again the one I want to "internal" load balance)
and I try to configure an internal loadbalancer (see here:
vs2013-update3)
When I try to deploy the package I receive this error:
Error: The specified configuration settings for Settings are invalid. Verify that the service configuration file is a valid XML file, and that role instance counts are specified as positive integers. Http Status Code: BadRequest OperationId:
874024071e88327f8cb73c16f15f3ac2
I'm sure it depends on the ilb configuration because when I remove it the deploy succeed...
Does anybody try something like this?
Thanks,
Simone

I've found a solution by myself with the help of a friend (Sandro Vecchiarelli): the "problem" is that I try to setup two load balancers in one cloud service. Trying with only one work correctly; the error probably is a schema validation and I
really don't know if the error is on "client" schema that allow me to configure more than one ILB (note the node name
LoadBalancers... its plural...) or online (the one on Azure).
By the way...at the moment use just one ILB per cloud service.
Hope this help.

Internal load balancer for ADFS, Web Application Proxy join problem

Hello,
we deployed 2 x ADFS (2012 R2) behind a internal Azure load balancer.
In front are two WAP servers, which should be joined to the ADFS farm based on the internal load balancer IP.
Unfortunately the WAPs fail to join and sometimes after 5 tries it works. The problem is (based on the event logs) that the ADFS Servers dont trust the WAP certificate.
It seems, that during the join process the ADFS internal load balancer does not stick to one ADFS server. If we join the WAP directly (without the ILB) to one of the ADFS servers, everything works fine.
As soon as we try to join via the ADFS internal load balancer IP, the abover occurs.
Did anyone experience the same problems? How does the internal load balancer distribute the requests? Seems to be not sticky at all.
Thanks for any Feedback,
Thomas

Thomas -
This article talks (in detail) about a recently updated distribution mode - Source IP affinity.
http://azure.microsoft.com/blog/2014/10/30/azure-load-balancer-new-distribution-mode/
Hope this helps!
/Arvind

How can I design Load Balancing for distant Datacenters? without single point of failure

Dear Experts,
We are using the following very old and passive method of redundancy for our cload SaaS but it's time to make it approperiate. Can youplease advise:
Current issues:
1. No load balancing. IP selection is based on primary and secondary IP configurations. If Primary fails to respond, IP record for DNS changes to secondary IP with TTL=1min
2. When primary server fails, it takes around 15 min for clients to access the servers. Way too long!
The target:
A. Activate a load balancing mechanism to utilized the stand-by server.
B. How can the solution be designed to avoid single point of failure? In the previous example, UltraDNS is a single point of failure.
C. If using GSS is the solution, how can it be designed in both server locations (for active redundancy) using ordinary DNS server?
D. How can HSRP, GSS, GSLB, and/or VIP be used? What would be the best solution?
Servers are running ORACLE DB, MS SQL, and tomcat with 2x SAN of 64TB each.

Hi Codlick,
the answer is, you cannot (switch to two web dispatchers).
If you want to use two web dispatchers, they need something in front, like a hardware load balancer. This would actually work, as WD know their sessions and sticky servers for those. But remember you always need a single point for the incoming address (ip).
Your problem really is about switchover groups. Both WD need to run in different switchover groups and need to switch to the same third software. I'm not sure if your switchover software can handle this (I'm not even sure if anyone can do this...), as this means the third WD needs to be in two switchover groups at the same time.
Hope this helps,
Regards,
Benny

Internal Load Balancer status - how to get it?

Hello,
is there any possibility to get the info, whats the status of the internal load balancer?
We would need to know, if e.g. one endpoint for forwarding is recognized as down.
Thanks,
Thomas

Hi Thomas,
Based on my exprience, you can use
Get-AzureInternalLoadBalancer cmdlet to get the internal load balancer configuration of a deployment. However, there is no other way to obatin the information of internal load balancer.
I recommend you to submit your request in Azure feedback below:
http://feedback.azure.com/forums/34192--general-feedback
Best regards,
Susie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Internal Load Balancing

I'm after a definitive answer as to whether you can do internal load balancing with Roles as its a highly desirable feature but also i've seen conflicting information on it. For instance the following Azure blog article suggests you can but I can't find
any sign as to how you do it (assuming the assertion that you can is accurate).
http://azure.microsoft.com/blog/2014/05/20/internal-load-balancing/
So can it be done? If so how? If not then is it a forthcoming feature?

Hi,
As far as I know, we can use powershell to configure Internal Load Balancing at currently, please have a look at this article:
http://msdn.microsoft.com/en-us/library/dn690125.aspx, if I misunderstand, please feel free to let me know.
Regards

Internal end points load balancing

Similar Messages

Maybe you are looking for