Forum Discussion
DuBang_322065
Nimbostratus
Sep 22, 2017Cannot ping floating IP and active side self IP from client
I've deployed 2 BIGIP VE(12.1.2.1.65.271 Engineering Hotfix HF1) without HA configuration with following IP address
floating IP: 172.21.61.254/24
active side self IP: 172.21.61.253/24
standby side self IP: 172.21.61.252/24
Here's the problem,
- All loadbalancing are functional, all 3 configured nodes(172.21.61.[11,12,13]) can ping all these self & floating IPs on BIGIP and client, which is not in this 172.21.61.0/24 range
- Client can ping VIP and these nodes, but ping to floating IP(172.21.61.254) and active side(172.21.61.253) self IP timeout, only standby side self IP(172.21.61.252) is pingable.
- I tried failover but still, only current standby self IP(this time 172.21.61.253) is pingable, other 2 IPs result in timeout.
Is it an expected behavior or am I missing some configurations?
1 Reply
- Vijay_E
Cirrus
Could be something to do with the way you have your network set up. I am not sure why the client needs to access the self and floating IP facing the servers though.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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
