Forum Discussion
About ping from BIG-IP
Are you pinging from the Management interface or TMM/data interface? If from the Management interface, it's unlikely to be a BigIP problem. Nevertheless, as a first step, try to set a MAC masquerade address for your BigIP traffic-group. This is normally only needed for Active-Active BigIP clusters but it doesn't hurt with Active-Standby. A problem with
Gratuitous ARP updates and old ARP caches is a possibility. You may need to perform a similar procedure with your L3 switches to make the failover event more reliable.
Is it okay for the Standby L3 switch to have floating IP addresses so that you know the way to the Firewall and ping is returned?
Please let me organize it again.
① Delete VLAN of old L3SW (Clear with Standby machine → Clear with Active machine)
② Clear MAC address table with FW
③ Put VLAN in new L3SW (Add to Active machine → Add to Standby machine)
※ L3 switch uses vPC function on Nexus (maybe I forgot to say something quite important)
Describing in detail the ping of this situation.
① When VLAN is deleted on Standby machine → ping stop (Time out)
② After that, "From [Firewall] Destination Host Unreachable" is repeated several times from the firewall, then "[BIG-IP _ external_SelfIP] destination host unreachable" continues. (In some cases, after returning from BIG-IP, several pings are returned from the firewall.)
③ After that, the ping returns normally from the Firewall.
I am concerned about the behavior of ping after ②.
I am sorry for lack of information. Does the first explanation and situation change?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com