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

Hummingbird_143's avatar
Hummingbird_143
Icon for Nimbostratus rankNimbostratus
Jul 11, 2014

virtual server snatpool, only automap works for different vlan connection

There are several vlans hosted on our F5, for example vlan 1, vlan 2, and vlan 3, and the default router is on the same network as vlan 1, each vlan has self ip created, route domain is default inclu...
application delivery
availability
design
LTM
management
performance
Hummingbird_143's avatar
Hummingbird_143
Icon for Nimbostratus rankNimbostratus
Jul 11, 2014

Thanks for your response!

 

The backend server is on vlan4 which is at a different datacenter, I can't trunk vlan4 to F5, instead I want to use IP from vlan2 in virtual server's snappool to backend servers on vlan4, which doesn't work, as you can see from the tcpdumps in my first post, 2.2.2.2 send Reset to 4.4.4.4.

 

Also I have added a virtual server using same snat address 2.2.2.2, and 4.4.4.4 has no problem to access that virtual server, so seems to me packet originated from F5 has problem to reach servers on vlan that not on F5?

 

Thanks again Lily

 

  • Hummingbird_143's avatar
    Hummingbird_143
    Icon for Nimbostratus rankNimbostratus
    Jul 11, 2014
    Also, if I try to ping outside host from interface on F5 except vlan1 which has default router configured, ping fails, only ping from vlan1 interface works, the default route is upgrade router IP, listed on "Partition Default Route Domain" on F5, which includes vlan2, wonder why vlan2 traffic won't be able to use this default router to get out ? Any help or suggestions will be greatly appreciated!! Lily