Home > Switches > Port and VLAN Configuration > Standard Trunk Port Configuration Not Working with Cisco Switch

Standard Trunk Port Configuration Not Working with Cisco Switch

Table of contents
No headers
In the scenario where the following standard trunk-port configuration is not working on a Cisco switch:

switchport mode trunk
switchport trunk encapsulation dot1q

Check to make sure the global command "dot1q tag native" is not invoked.  Here is Cisco's description for the command:

When enabled, native VLAN packets going out all IEEE 802.1Q trunk ports are tagged.
When disabled, native VLAN packets going out all IEEE 802.1Q trunk ports are not tagged.
You can use this command with the IEEE 802.1Q tunneling feature. This feature operates on an edge
switch of a service-provider network and expands VLAN space by using a VLAN-in-VLAN hierarchy
and tagging the tagged packets. You must use IEEE 802.1Q trunk ports for sending packets to the
service-provider network. However, packets going through the core of the service-provider network
might also be carried on IEEE 802.1Q trunks. If the native VLANs of an IEEE 802.1Q trunks match the
native VLAN of a tunneling port on the same switch, traffic on the native VLAN is not tagged on the
sending trunk port. This command ensures that native VLAN packets on all IEEE 802.1Q trunk ports are
tagged.

Any traffic passed over the native VLAN should be untagged to ensure proper communication.
You must to post a comment.
Last modified
21:21, 2 Feb 2015

Tags

This page has no custom tags.

Classifications

This page has no classifications.

Article ID

ID: 1178

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community