Cisco Support Community
Community Member

Configuring Trunk Ports

Can Trunk Ports be configured without the USE of NATIVE VLAN. ? Please HELP!


Configuring Trunk Ports

Hi Muhammad,

Not too sure whether I have understood your question correctly.

Yes, If you keep encapsulation as ISL, there won't be any Native VLAN concept.

Native VLAN concept only applies to dot1q.

Also, while configuring dot1q, it is not mandatory to define native vlan, as by default native vlan is VLAN 1.



Configuring Trunk Ports

Hi Muhammad,

With 802.1Q, a trunk link frames can tag between devices that understand the protocol. This allows for multiple VLANs to exist on a single topology. Because 802.1Q is defined as a type of Ethernet frame, it does not require that every device on a link speaks the 802.1Q protocol. Because Ethernet is a shared media and more than two device could be connected on this media, all devices on the link must still be capable of communicating even if they do not speak the 802.1Q protocol. For this reason, 802.1Q also defines a Native VLAN. A trunk port on a switch is defined to be in a Native VLAN, and the 802.1Q trunk will not tag frames that are going out the port that came in on any port that belongs to the same VLAN that is the Native VLAN on the switch. Any Ethernet device would be capable of reading frames for the Native VLANs. The Native VLAN is important on an 802.1Q trunk link. If both sides of the link do not agree on the Native VLAN, the trunk will not operate properly

A Native VLAN is nothing else than a default VLAN given that any port in a (CISCO)switch has to assigned to one VLAN. And by default all ports (access links) belong to VLAN 1 or native VLAN.

Please rate the helpfull posts.


Configuring Trunk Ports


on some platforms you can tag all frames with the global command: vlan dot1q tag native



Don't forget to rate helpful posts.
CreatePlease to create content