Network operational with different native vlans on each side of the trunk
OfWolfAndMan
Member Posts: 923 ■■■■□□□□□□
in CCNP
I work with a network that recently underwent some changes, one being a native vlan change, and this is what I observed. Yes, I am aware that you are supposed to have your command #switchport trunk native vlan [vlan #] identical on each side of the trunk, but is it possible for the access layer to be completely operational if the native vlan is different? I know it's possible, but why is it working?
:study:Reading: Lab Books, Ansible Documentation, Python Cookbook 2018 Goals: More Ansible/Python work for Automation, IPSpace Automation Course [X], Build Jenkins Framework for Network Automation []
Comments
-
networker050184
Mod Posts: 11,962 Mod
Having a mismatch isn't necessarily going to break anything and it will not prevent the trunk from operating. If a trunk receives untagged frames it is going to assume they belong to the VLAN assigned as native.An expert is a man who has made all the mistakes which can be made. -
OfWolfAndMan
Member Posts: 923 ■■■■□□□□□□
Should've done my homework on this one. Essentially I assume if different native vlan numbers are present, its possible to trunk, but just a greater security vulnerability having two native vlans rather than one. Thanks for the info!:study:Reading: Lab Books, Ansible Documentation, Python Cookbook 2018 Goals: More Ansible/Python work for Automation, IPSpace Automation Course [X], Build Jenkins Framework for Network Automation []