Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) - Manual (Page 337)

Brocade Virtual ADX Server Load Balancing Guide 321
53-1003247-01
Hot-standby HA with routing protocols
6
Tie state of virtual link and HA physical link using health checks
The Brocade Virtual ADX virtual interface is unaware of the state of the physical interface and this
result is an inconsistent port state. In HA scenarios, failover cannot be triggered even if the
associated physical interface is down. Hence, the virtual interface state is tied with that of the
physical interface. The existing ICMP Boolean health checks are deployed in these scenarios as
follows:
Virtual ADX(config)#healthck c1 icmp
Virtual ADX(config-hc-c1)#dest-ip 3.3.3.1
Virtual ADX(config)#healthck c2 icmp
Virtual ADX(config-hc-c2)#dest-ip 3.3.3.2
Virtual ADX(config)#healthck c3 boolean
Virtual ADX(config-hc-c3)#or c1 c2
The healthck command is introduced in server router-port command to tie the health checks as
follows:
Virtual ADX(config)#server router-port e 1 healthck c3
NOTE
In a Hot-Standby HA configuration, the server port interface is connected to the external device using
the virtual switch. If the port on the external device is down, the Brocade Virtual ADX does not detect
it because of the presence of the virtual switch in between. The result is that the status of the
server-port is not be marked as down. To overcome this drawback, you can configure the server
backup-vip-cnt or server backup-vport-cnt command while running Hot-Standby HA to perform
failover based on a real-server health check failure.
For more information on configuring OSPF, refer to the Brocade Virtual ADX Switch and Route
Guide.