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

Moncef_Azure — Fri, 07 May 2021 12:01:50 GMT

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

topic AZURE ILB healthcheck Fails because of MS Public IP (168.63.129.16) in VM-Series in the Public Cloud

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