Forum Discussion
VLAN Routing
Having an issue passing traffic from F5 BigIP to internal/external network. Both network's are using tagged VLAN's. I have configured BigIP to use the same VLAN number and assigned a Self IP to the same VLAN subnet. The ICMP monitors show all objects as down. From BigIP command line I am able to ping all self IP's and Virtual Servers, but nothing outside of BigIP. TCPDump shows arp request, but no response. Configuration is as follows;
96.193.25.1 Default Gateway
-
-
VLAN 900
-
-
96.193.25.21 Virtual Server
-
-
96.193.25.17 Self IP
-
-
-
F5 LTM/LC
-
-
172.18.7.10 Self IP
-
-
VLAN 17
-
-
172.18.7.63 Server
Any help would be greatly appreciated. I am sure I am missing something simple.
Thanks
19 Replies
- Chris_Miller
Altostratus
Posted By Drodneys on 08/11/2010 07:10 AM
Chris that is correct.
Can you run this command from console/ssh and grab the output? bigpipe interface 1.1 - Drodneys_24642
Nimbostratus
Chris found cable issue for interface 1.1. Looks like it is up now;
INTERFACE 1.1
| Speed Pkts Pkts Drop Coll Bits Bits Errs Trunk
| Mbps in out in out
| UP 1000 FD 1.072M 8912 1.056M 0 1.505G 5.035M 0 - Chris_Miller
Altostratus
Posted By Drodneys on 08/11/2010 08:54 AM
Chris found cable issue for interface 1.1. Looks like it is up now;
INTERFACE 1.1
| Speed Pkts Pkts Drop Coll Bits Bits Errs Trunk
| Mbps in out in out
| UP 1000 FD 1.072M 8912 1.056M 0 1.505G 5.035M 0
When you say "up", I'm crossing my fingers that this means you're able to ping the server in the same subnet now? Are you still having other issues? - Drodneys_24642
Nimbostratus
On vlan 7 I am able to ping the server in the same subnet. On vlan 998 I am not able to ping. - Chris_Miller
Altostratus
So on vlan 998:
96.193.25.17/255.255.255.0 is your Self-IP and set to vlan 998. You're unable to ping 96.193.25.1 from the BIG-IP? - Drodneys_24642
Nimbostratus
that is correct - Chris_Miller
Altostratus
Can you do a "bigpipe interface 1.3" and show the output? - Drodneys_24642
Nimbostratus
Chris I found the issue(I think you mentioned it earlier but I didnt catch it). VLAN 998 is a tagged interface, but it is not a trunk on the switch side like 1.1. When changed VLAN 998 to untagged all the health monitors went to green. I am able to ping on VLAN 998. Thanks for all your help! - Chris_Miller
Altostratus
Posted By Drodneys on 08/12/2010 09:48 AM
Chris I found the issue(I think you mentioned it earlier but I didnt catch it). VLAN 998 is a tagged interface, but it is not a trunk on the switch side like 1.1. When changed VLAN 998 to untagged all the health monitors went to green. I am able to ping on VLAN 998. Thanks for all your help!
Gotcha...so from the F5, you were sending a vlan tag but the switch wouldn't get that...makes sense. Glad to hear it's working for you.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com