Forum Discussion
Tim_Patrick
Altostratus
Altostratusunable to ping VIP from server with the F5 as the DGW
In our current setup, we have a cluster of servers that utilize the F5 load balancer as their default gateway. This load balancer operates as a high availability (HA) pair, with the default gateway s...
so if it was suggested and I didnt see it I apoligize. The fix for me was to go to the virtual server that I was trying to access from the host nework (10.1.228.x) which used the F5 as its gateway and add the VLAN to the VLAN and tunnels section. it only had the ext vlan present and when I created the new network and new vlan (int_vlan) I needed to add it to that in order for it to connect to the VIPS
wtwiggs
Altocumulus
Altocumulussorry I just reread your issue and my first response may not be on point... if I understand (more) correctly... it is just the VIPs and self IPs that you cannot ping?
is it just from the 10.1.228.x network that you cannot ping those 10.1.216.x VIP/selfIP? can you ping them from the 10.1.216.x network?
have you checked "Port Lockdown" on the self IP address properties (possibly set to default of "Allow None" and if so does "Allow All" work)?
and have you checked the VLAN(s) the VIPs are listening on?
here is a related possibility:
https://my.f5.com/manage/s/article/K3475
and a "forwarding (layer 3)" virtual server may still be needed, if not in place, so that the ping packets will "forward" thru from the interface acting as the gateway to the other interface(s) where the far end self IP or VIP is listening...
hopefully some of this helps... please provide some additional configuration details, as we do have similar in place and working so I think we can get it working.
Tim_PatrickAltostratus
AltostratusWtwiggs, thanks for the response, I have included a file with a summary and screenshots of what I am experiencing. I did double check the port lockdown and it is set to allow all