AZURE ILB healthcheck Fails because of MS Public IP (168.63.129.16)
cancel
Showing results for 
Search instead for 
Did you mean: 

AZURE ILB healthcheck Fails because of MS Public IP (168.63.129.16)

L0 Member

Hello,

 

I'm setting an Active/Active PA design with Azure ILB for traffic balancing, my backends are PA firewalls on each of their interfaces (I'm using 6 interfaces)

Azure ILB uses the same Public IP to monitor health status of all the backends https://docs.microsoft.com/fr-fr/azure/virtual-network/what-is-ip-address-168-63-129-16

 

The probing fails on all interfaces except one (the one facing internet access) because of asymmetric routing.

 

One solution is to use ECMP and force symmetric return which works for me but it's only limited to 4 paths & i need to use 6 interfaces on this cluster, so 6 different paths for the same IP (168.63.129.16)

 

The other one is to create separate VRs for this.

 

Is there any other solution or workaround for this ecmp limitation ? 

 

Thank you 

 

0 REPLIES 0
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!