We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 651 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

469 Sign Ups in the last 30 days

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: ,

Forum Replies

  1. Ahmad,
    A Native VLAN is the vlan that is used should a trunk port receive an frame with no explicit VLAN tag. I will give you an example of how I used Native VLANs in the real world:

    For many of my locations, users have a single network connection to their desk. They use both a VOIP phone (not Cisco :frowning: ), and a PC. Both of these devices use the single network connection. The connection goes to the VOIP phone, and the computer plugs into another port on the phone. The VOIP traffic is on a separate VLAN than the PC data traffic.

    To get this to work, we have to

    ... Continue reading in our forum

  2. Hi Hussien,

    The vlan dot1q tag native is a global command so it applies to all interfaces. If you want to exclude certain interfaces, you can use the no switchport trunk native vlan tag command on the interface level.

  3. Hi Andrew,
    I was just browsing through the native vlan topics and i saw your reply to Ahmad. I dont understand your replay starting “To get this to work, we have to configure each port as a Trunk and allow both the VOIP VLAN and the PC Data vlan on the switch port” Which port are you configuring as a trunk?
    I have configured VOIP vlan and pc data vlan on a switch port and it is not configured as a trunk port for both devices to work with the cat5 from the wall going into the phone first and then the pc connected to the phone.
    The port on the switch is configu

    ... Continue reading in our forum

  4. Hello Aniket

    There are two ways to implement the following scenario:


    One is to configure the Gi0/1 interface as a trunk. Let’s say the voice VLAN on our network is 137 and the data VLAN is 135. We would configure the Gi0/1 interface as a trunk, with a native VLAN of 135 and an allowed VLAN of 137. This means that frames on VLAN 135 destined for H1 would exit the Gi0/1 interface untagged. Any such frames reaching the IP phone would continue on to H1. A

    ... Continue reading in our forum

82 more replies! Ask a question or join the discussion by visiting our Community Forum