Tagged VLAN / Interface

1) VTP is a Cisco proprietary thing. The F5 LTM can peak VLAN tags, but not VTP as far as I know. So, configured your environment accordingly (either no tags or use tags, but don't depend on the LTM participating in a Cisco Catalyst VTP session)

 

 

2) Here's a quick command line recipe - where I've assumed that the LTM will be 10.1.1.5 on the internal VLAN and a single node, 10.1.1.100, exists, serving up HTTP on TCP port 9000 with the virtual 10.2.2.200, which will serve up HTTP on TCP port 80.

 

 

(but, really, configuring the BIG-IP without a Self-IP on the external network is a bit limiting, so you probably don't want to do that for a production network):

 

 

b vlan external interfaces 1.1

 

b vlan internal interfaces 1.2

 

b self 10.1.1.5 vlan internal netmask 255.255.255.0

 

b node 10.1.1.100 monitor icmp screen Node1

 

b pool WebServer9000 { members 10.1.1.100:9000 { monitor tcp } }

 

b virtual Web80 { destination 10.2.2.200:http mask 255.255.255.0 pool WebServer9000 }

 

 

 

(the key to the above trick is that I'm specifying a mask on the virtual server. If I didn't, the unit would use the mask from the self-ip, or basically, not really use a netmask. It doesn't really help much, as default routes and other things need to be set to get the traffic moving in the right directions... but it does let one configure a virtual without self-ip's...)

 

 

 

What really needs to happen is a set of Self-IP's configured on the LTM for each network, so that a route statement can be put in place:

 

b self 10.2.2.21 netmask 255.255.255.0 vlan external

 

b route default inet { gateway 10.2.2.2 }

 

 

and then traffic will start flowing.

 

 

 

This is covered in the LTM manuals in extensive detail. Good Luck!