Forum Discussion
F5 LTM tagged interface doesn't encapsulate using 802.1q
Hi all. I've a problem. I want to use a single LTM interface for more that one VLAN so I configured it as a tagged interface and I configured a tag on each and every VLAN. The fact is that apparently the LTM correctly understands the 802.1q frames sent to it thru a (Cisco) trunk interface but it returns the traffic without the 16 bits 802.1q encapsulation so the Cisco switch doesn't accept them. Could you please help me understand what I'm missing ? Thanks
2 Replies
- mimlo_61970
Cumulonimbus
Never seen this before. Did you also add the vlan to the proper interface as Tagged?
- rrr2015
Nimbostratus
Hi mimlo, thanks for the reply. I had a talk with a tech guy far before me in his knowledge of F5 LTM and he suggested that being my setup based on the trial 11.3 LTM the problem could be related to route domains missing in the partition I used. I told me that the right configuration procedure in 11.3 is not that in the config. guide but it's the same as before (10.x) but unfortunately I didn't find it. Does it ring a bell in 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