Forum Discussion
Daniel_55334
Altostratus
Aug 28, 2008active/active configuration behavior
Customer is running active/active configurations and they found the following behavior. Are they normal?
1. for each VLAN on BIG-IP, unit 1 is not able to ping the floating ip of unit 2, and vice versa. unit 1 is able to ping its own floating ip and physical ip of both units.
2. vs1 is active on unit 1 and vs2 active on unit 2. both vs on vlan-a. A client, which is on vlan-b, has default gateway pointing to unit 1. It is not able to access vs2. vlan-a and vlan-b are both on BIG-IP.
- dennypayne
Employee
Yes, this happens with active/standby pairs as well if the packet is forwarded through the system. It's similar to firewall anti-spoofing measures, where "in and out" on the same interface is blocked. - Daniel_55334
Altostratus
Thanks for your reply. I assume what you say is that pinging from unit 1 to floating ip of unit 2 causes "in and out" on the same interface. But why pinging its own floating ip is ok? What's the difference?
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects