For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

yogesh_gaikwad_'s avatar
yogesh_gaikwad_
Icon for Nimbostratus rankNimbostratus
Oct 09, 2015

Need help on some issues in route domains

Hi,   Below is the detailed description of the issue.   We are creating multiple partitions on the F5, and each partition is going to have its separate default route. For achieving this I am us...
application delivery
LTM
tatmotiv's avatar
tatmotiv
Icon for Cirrostratus rankCirrostratus
Oct 12, 2015

The routes of the big IP itself are only feasible for "from the big IP" traffic (health checks, reaching, non-directly connected pool members, etc), not for "through the big IP" traffic. That's probably the reason why ping from the big IP is working, but SSH from outside the big IP is not.

 

In order to have your big IP forward traffic between VLANs, you need to add some forwarding virtuals. E.g. when you want to forward traffic to subnet 10.129.50.32/27, you'll need to deploy a network forwarding virtual destined for 10.129.50.32/27 and enable that one on your "external" VLAN (make sure it is bound to the right route domain).

 

See https://support.f5.com/kb/en-us/solutions/public/7000/500/sol7595.html for hints on how to configure forwarding virtuals.