Forum Discussion
NimbostratusAdding a new VLAN to LTM traffic
Hi all,
I have LTM with VLAN 2, self IP 10.2.2.1 and Floating IP 10.2.2.2 using the virtual server 4.4.4.4 working fine,
Servers are using the floating IP as gateway instead of the VLAN IP on sw2 (downstream switch).
Now I want to add another network, VLAN 3 on sw2. The difference is that servers on this new VLAN are using VLAN IP on the switch as gateway rather than floating IP and I can ping all self IPs fine because I added self IP.
Can I use virtual server 4.4.4.5 for traffic distined to VLAN 3?
Do I need to create floating for this new network specifically for the new VLAN 3 traffic even though servers are not using the floating IP address as gateway?
|||| fw
|
|||| sw1
| Virtual Server 4.4.4.4.
---|||---- LTM
| float IP 10.2.2.2, self ip 10.2.2.1
|
|||| sw2
VLAN 2, 10.2.2.6
VLAN 3, 10.3.3.6
Regards
Elias
3 Replies
Andrew_HuskingCirrus
If i'm understanding your config correctly, i believe so.
As long as your F5 can talk to VLAN 3 that will work fine.
The only thing to be aware of is that the F5 won't pass the client IP to the servers (unless you use x forwarded for).
Cheers
Elias_O_16228No success with forwarding. I must be doing somethong incorrect. I think I need another floating IP for the new VLAN to look as follows:
|||| fw
|
|||| sw1
| Virtual Server 4.4.4.4.
---|||---- LTM
| float IP 10.2.2.2, self ip 10.2.2.1 Vlan 2
float IP 10.3.3.3 self ip 10.3.3.1 Vlan 3
|
|||| sw2
VLAN 2, 10.2.2.6
VLAN 3, 10.3.3.6
What_Lies_Bene1Cirrostratus
Yes you do need relevant Self IPs for VLAN3 on the BIG-IP. You should also create VLAN3 on the BIG-IP first (if you haven't) and trunk it to SW2 accordingly. Note that you might have issues if SW2 routes to the source/client IPs through another VLAN on the BIG-IP.
