I refer to the new feature of sticky session on <a href="http://azure.microsoft.com/blog/2014/10/30/azure-load-balancer-new-distribution-mode/">this article here</a> where you are able to set 2-tuple or 3-tuple affinity in addition
to the previous version of endpoint load balancer on azure.
After following the Azure cmdlet on the above blogpost, I've stumbled upon the error in the image/title whenever I try to add in new endpoints on the manage.windowsazure.com or portal.azure.com portal.
<a href="http://www.tanchunsiong.com/wp-content/uploads/2014/11/error-crop.jpg"><img class="alignnone size-full wp-image-385" alt="error-crop" src="http://www.tanchunsiong.com/wp-content/uploads/2014/11/error-crop.jpg"
width="800" height="119" /></a>
The error can be reproduced with either of the below scenarios
<ol>
<li>VM1 and VM2 are in the same Availability Set and Cloud Service. Using the command<em>Get-AzureVM -ServiceName $csname -Name $vm1name | Add-AzureEndpoint -Name $nameofEndpoint -Protocol "tcp" -PublicPort
$publicport -LocalPort $localport -DefaultProbe -LBSetname $nameofLBEndpoint –LoadBalancerDistribution "sourceIPProtocol" | Update-AzureVM</em><em>Get-AzureVM -ServiceName $csname -Name $vm2name | Add-AzureEndpoint -Name $nameofEndpoint
-Protocol "tcp" -PublicPort $publicport -LocalPort $localport -DefaultProbe -LBSetname $nameofLBEndpoint –LoadBalancerDistribution "sourceIPProtocol" | Update-AzureVM</em></li>
<li>Using the command<em>Set-AzureLoadBalancedEndpoint -ServiceName $csname -LBSetName $portname -Protocol tcp -LocalPort $portnumber -ProbeProtocolTCP -ProbePort $probeport –LoadBalancerDistribution "sourceIPProtocol"</em></li>
</ol>
What's the fix for now?
