I'm getting some mixed signals when configuring a trunk on a Cisco switch and I'd like to know which VLANs are actually being allowed on it. The way I want it to be is that only VLANs 1,10,20,30,99 should be allowed. Have a look at the output:

S1(config-if)#do show int tru
Port        Mode         Encapsulation  Status        Native vlan
Gig1/1      on           802.1q         trunking      99
Gig1/2      on           802.1q         trunking      99

Port        Vlans allowed on trunk //What is this?
Gig1/1      1-1005
Gig1/2      1-1005

Port        Vlans allowed and active in management domain //What is this?
Gig1/1      1,10,20,30,99
Gig1/2      1,10,20,30,99

Port        Vlans in spanning tree forwarding state and not pruned //What is this?
Gig1/1      none
Gig1/2      1,10,20,30,99

What confuses me is that first it states that all VLANs in range 1-1005 are allowed and then it says 1,10,20,30,99 are "allowed and active in management domain" - what is that supposed to mean? What do the different headings mean?

2 Answers 2


When you configure a trunk link with the command:

(config-if)#switchport mode trunk

all the vlans will be allowed in the trunk link.

If you want to control which VLANs are allowed in a trunk link use the following commands:

(config-if)#switchport trunk allowed vlan
  WORD    VLAN IDs of the allowed VLANs when this port is in trunking mode
  add     add VLANs to the current list
  all     all VLANs
  except  all VLANs except the following
  none    no VLANs
  remove  remove VLANs from the current list

For example if you want to allow VLANs 1,10,20,30,99 in a trunk link you have to type:

(config-if)#switchport trunk allowed vlan 1,10,20,30,99

Pay attention that if you want to add a vlan on a trunk link (for example VLAN 100) you have to use the add statement (this is really a commond mistake), for example:

(config-if)#switchport trunk allowed vlan add 100

When you read "Vlans allowed and active" it simply means that just the active VLANs (the ones you have defined) are allowed in that trunk link.

Reference here: How to define the VLANs allowed on a trunk link

EDIT: Analyzing the output of the show interface trunk command it's easy to see that it is organized in 4 sections;

  • The first one is a list of all the trunk interfaces togheter with the encapsulation and the native VLAN.

  • For what concern the second and the third lines the important point to clarify is the difference between allowed and active. Allowed simply stays for "It is allowed to pass" meanwhile active means "this VLAN is up and running in the swtich". Note that active does not simply mean "it is present in the database" since you can shutdown a vlan with (config-vlan)#shutdown.

  • The last one deserves a little note; when dealing with PVST (Per-VLAN Spanning Tree) the switch creates a loop-free topology for each L2 broadcast domain (VLAN). Since it is not said that each VLAN share the same phisical topology there could be the case in which, even if a vlan is active and allowed, that vlan will not be forwarded across the trunk interface. This is because that interface it is not in the Forwarding state for that particular PVST process. Is it also possible that a VLAN is not forwarded across a trunk if it has been pruned by the VTP pruning process.

  • To add to this, if you had two switches on either side that were trunking VLAN 40 towards this switch, this switch would NOT pass VLAN 40 data from one side to the other because it is not active (not in the VLAN database) as is evident in the third and fourth section. You cannot trunk a VLAN through a switch that isn't aware of that VLAN. Apr 17, 2014 at 1:32
  • Thank you for an excellent answer! I think I'll just nevermind the last one (about Spanning Tree) since I'm in CCNA2 now and we haven't studied it. Probably good stuff though! Apr 17, 2014 at 16:19

The "active management VLans are the ones currently being utilized....you can open the pipe full blast and allow all vlans across a trunk...I wouldnt recommend it, however this is what that configuration says. Also it looks like 99 is your native vlan, which essentially means it sends the frames in an almost untagged fashion but not quite....gi1/1 seems to not be participating in STP for some reason, without seeing the show Spanning-tree command your guess is as good as mine. just make sure when you use trunked links...you specify, encapsulation native vlan, and allowed vlans on the trunk along with the fact that it is a trunk.....

Good luck!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.