Forum Discussion
Unable ping to active and floating selfip
Hi Masters,
I have two BIGIP i5600 in an active/standby configuration. TMOS version = 13.1.1.4
There are 2 VLANs. Internal, External, HA configuration. My problem is on the internal vlan.
Let's say on the internal-vlan:
F5-1-selfip (Active) : .52
F5-2-selfip (Standby) : .53
Floating-ip = .51
From the upstream L3 switches, I can ping .53 but can't ping .52 and .51
When I force F5-1 to standby, the problem reverses. Now I can ping .52 but not for .53 or .51
Port-lockdown is set to allow-default.
It appears I can only ping the standby unit's self ip. The other two do not respond.
Anybody have any experiences on what may be occuring here?
I was see the seem issue on this https://devcentral.f5.com/questions/cant-ping-active-ltms-self-ip-or-floating-ip but there is no solution.
If it this a behavior design from bigip does anyone know the way how we can do ping to selfip both active and standby?
I will be grateful for any help you can provide!
- youssef1
Cumulonimbus
Hi,
I see that you check this post:
https://devcentral.f5.com/questions/cant-ping-active-ltms-self-ip-or-floating-ip
Thanks for your prompt reply. Would you know how I can get ping to work on the Active node? and not just on the Standby node?
This behavior is by design. When you try to ping a SelfIP on an interface that is not the interface you are originating from, it won't work on the Active device. You can ping the standby because, once you get back there, the Active device knows where to find that IP.
it is your case? if not can you confirm that you don't activate "packet filter", you don't use ASM or you don't setup mac masquerading on the BIG-IP HA pair...
Regards
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