Forum Discussion
NimbostratusNot able to ping from vlan 300 to 400 on F5
Hello we have two cluster node server (on VLAN 400) and quorum server(VLAN 300) We have migrated all vlan 400 subnet all to (F5 v800 ),After the migration we have changed the gateway of F5 in the two cluster node hosts,now problem is not able to ping the quorum server (VLAN300) as the gateway is changed now.so we have to communiate the quorum server to availability of cluster node,,
Do we need to change anything on F5 to ping the quorum server..?
So, just to add to Pete's reply, here is an official F5 SOL article explaining how to achieve your goal (as I understand it). http://support.f5.com/kb/en-us/solutions/public/7000/300/sol7366.html?sr=34764674
Be sure to select "All protocols" when you create your virtual server, otherwise the system will select the default option (which is TCP).
5 Replies
PeteWhiteEmployee
The f5 device is not a router - it is default deny. For it to forward packets you need to add a virtual server with a pool of devices. If you want packets to go from vlan 300 to vlan 400 then you need to create a virtual server specific to the traffic (eg http, https, subnets, wildcard, etc).
So, just to add to Pete's reply, here is an official F5 SOL article explaining how to achieve your goal (as I understand it). http://support.f5.com/kb/en-us/solutions/public/7000/300/sol7366.html?sr=34764674
Be sure to select "All protocols" when you create your virtual server, otherwise the system will select the default option (which is TCP).
Vitaliy_SavransNacreous
Just to add to previius replies by my mind it's bad idea use f5 for routing between vlans. Maybe it's better to make changes in routing scheme in your network.
- boneyard
MVP
why would it be bad to route with the big-ip? it totally depends on your network setup, might be a perfectly good option.
billa_142214Thanks All, we have enable the automap SNAT to forward the virtual server between two internal VLANs,now we can able to ping the server.
