im guessing really really simple problem

Hi -

 

 

I'm guessing your question should go to websupport.f5.com instead of devCentral. ;-) All kidding aside, I just happened to jump on and see your question and thought I'd give you some "free support" and suggest you forward your case to F5 tech support.

 

 

As for the pinging of a NAT, don't expect a standard response from the node. NATs will not forward ICMP requests to the node. At most, the BIG-IP's external interface will respond, not the node. That could be why the HTTP VIP still works but NAT doesn't respond to pings.

 

 

Also, if you had a power outage, the active BIG-IP could have changed on bootup (the other box came up first and became active), so the MAC address has changed, and the upstream device (usually a FW with a long ARP cache) has an other MAC address still in it's cache.

 

 

Finally, a myriad of other factors could be involved on a power outage / reboot of both BIG-IP controllers. Do a trace route to from the outside in and find the last device that responds. The most likely cause if it ends with the device before BIG-IP is that the NAT is missing, incorrectly configured, or different on the currently active device (devices were not synced prior to the outage), or the ARP cache issue I mentioned above.

 

 

/mh