Forum Discussion
Does Tagged interface acts like trunk?
For example there is my internal vlan is 169 and only one interface is connected to one switch with internal vlan. Now Question is that I have 2.5 interface tagged to vlan 169 but have not configured any trunk on the side of F5. But I configured the switch interface as trunk and allowed vlan 169. If I configure switch interface as access then traffic stops.
Does tagging interface on F5 makes it kind of trunk?
5 Replies
- nathe
Cirrocumulus
Hi,
Always confusing talking about trunking on the f5s with cisco guys as they use the same terms for different things.
Now I'm now expert on the switching side but here's what i know. A trunk in cisco is a port carrying multiple VLANs. So Yes, tagging interfaces on the BIG-IP is, in effect, a cisco trunk as multiple VLANs will traverse this link.
An f5 trunk is actually an etherchannel or aggregated links.
Hope this makes sense.
N
- kunjan_118660
Cumulonimbus
Are you using cisco management vlan default 1 as the source IP to ping? Is the management vlan tagged in F5?
- No not management vlan that is totally separate. Production vlan. I can ping F5 self ips and VS with max 1454 MTU not more than that....
- kunjan
Nimbostratus
Are you using cisco management vlan default 1 as the source IP to ping? Is the management vlan tagged in F5?
- No not management vlan that is totally separate. Production vlan. I can ping F5 self ips and VS with max 1454 MTU not more than that....
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