You built 802.1Q trunks back in your CCNA.
Let's rebuild one from scratch.Why We Need a Trunk
Look at the topology below: VLAN 10 and VLAN 20 exist on both switches, but no link connects SW1 to SW2.

Figure 1 – VLAN 10 is stranded on each switch
So you run a cable between SW1 and SW2.
But that one cable has to carry VLAN 10 and VLAN 20 at the same time.
That is the job of a trunk: one link that carries every VLAN at once.
Figure 2 – A single trunk carries VLAN 10 and VLAN 20
In our example, let's say PC1 wants to communicate with PC3. They are in the same VLAN.
They will use the trunk link.Let's review how 802.1Q tagging works so you understand the process.
Answer the question below
How many links does a trunk need to carry every VLAN?
How the 802.1Q Tag Works
PC1 wants to send traffic to PC3.
When the frame lands on SW2, how does the switch know whether it belongs to VLAN 10 or VLAN 20?The answer is the 802.1Q tag.
A 4-byte tag is inserted right after the source MAC address when the frame enters the trunk.
Figure 3 – The 802.1Q tag lives inside the Ethernet frame
Inside that tag sits a 12-bit VLAN ID, enough to label VLANs 1 through 4094.
Answer the question below
How many bits in the 802.1Q tag carry the VLAN ID?
Follow the Frame
The trunk between SW1 and SW2 is up.
Follow one frame from PC1 to PC3.
Figure 4 – The frame crosses the trunk tagged with VLAN 10
Ping PC3 (192.168.10.3) from PC1:
PC1> ping 192.168.10.3 Pinging 192.168.10.3 with 32 bytes of data: Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.10.3: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0msSW1 pushes the frame onto the trunk and marks it with VLAN ID 10.
SW2 reads the 10, strips the tag, and delivers a plain frame to PC3.
See the 10 marked on the frame as it crosses the link.
The tag lives only on the trunk: PC1 and PC3 never see it.Answer the question below
Which VLAN ID does SW1 stamp on the frame?
Time to build that trunk on our topology.
Both switches already hold VLAN 10 and VLAN 20, and every PC sits on its access port.
Figure 5 – The trunk to build on G0/1
Turn G0/1 into a Trunk
Start on SW1:
SW1# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW1(config)# interface g0/1 SW1(config-if)# switchport trunk encapsulation dot1q SW1(config-if)# switchport mode trunk SW1(config-if)# endThe encapsulation line pins the tagging standard to 802.1Q.
The command switchport mode trunk forces the port to trunk.
It is the mode you want on inter-switch links.
Answer the question below
Which switchport mode hardcodes the port as a trunk?
Now mirror the configuration on SW2:
SW2# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW2(config)# interface g0/1 SW2(config-if)# switchport trunk encapsulation dot1q SW2(config-if)# switchport mode trunk SW2(config-if)# endAnswer the question below
Which command pins the tagging standard before mode trunk?
Verify the Trunk
Run
show interfaces trunkon SW1:SW1# show interfaces trunk Port Mode Encapsulation Status Native vlan Gi0/1 on 802.1q trunking 1 Port Vlans allowed on trunk Gi0/1 1-4094 Port Vlans allowed and active in management domain Gi0/1 1,10,20 Port Vlans in spanning tree forwarding state and not pruned Gi0/1 1,10,20Two things to read in this output:
Status reads trunking: the trunk is up
Vlans allowed shows 1-4094: every VLAN can cross
Answer the question below
What does the Status column read on a working trunk?
The Allowed VLAN List
By default a trunk allows every VLAN, all 4094 of them.
The allowed VLAN list defines which VLANs can actually cross the link.On this link, only two VLANs will carry traffic.
Therefore, we will allow only VLANs 10 and 20 on the link:SW1# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW1(config)# interface g0/1 SW1(config-if)# switchport trunk allowed vlan 10,20 SW1(config-if)# endMirror the list on SW2:
SW2# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW2(config)# interface g0/1 SW2(config-if)# switchport trunk allowed vlan 10,20 SW2(config-if)# endNow imagine that months later, VLAN 30 joins the network and must cross this trunk.
We can add this VLAN to the list without having to retype it.
SW1# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW1(config)# interface g0/1 SW1(config-if)# switchport trunk allowed vlan add 30 SW1(config-if)# endSame command on SW2.
Read the list back:SW1# show interfaces trunk Port Mode Encapsulation Status Native vlan Gi0/1 on 802.1q trunking 1 Port Vlans allowed on trunk Gi0/1 10,20,30 Port Vlans allowed and active in management domain Gi0/1 10,20 Port Vlans in spanning tree forwarding state and not pruned Gi0/1 10,20VLAN 30 sits on the list, and 10 and 20 survived.
It is allowed but not created yet, so the active line still shows 10,20.
The plain allowed command replaces the entire list, while the add keyword extends it without touching what is already there.
Answer the question below
By default, how many VLANs does a trunk allow?
Answer the question below
If the admin typed switchport trunk allowed vlan 30 without add, which VLANs would be allowed?
There is a second way to configure trunking: DTP (Dynamic Trunking Protocol) negotiates it for you.
DTP is Cisco proprietary: it only works between Cisco switches.DTP: Desirable and Auto
Out of the box, every switchport runs dynamic auto: it listens for DTP frames but never sends them.
If you connect two switches, the trunk does not form:
Figure 6 – Two dynamic-auto ports never start a trunk
Both sides wait, nobody asks: no trunk forms.
Every DTP pairing comes down to one thing: at least one side has to initiate.Answer the question below
Which dynamic mode never starts the negotiation?
Now flip SW1 to dynamic desirable and it starts asking:
SW1# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW1(config)# interface g0/1 SW1(config-if)# switchport mode dynamic desirable SW1(config-if)# endHere is the negotiation that just happened:

Figure 7 – One side asks, the trunk forms
SW1# show interfaces g0/1 switchport Name: Gi0/1 Switchport: Enabled Administrative Mode: dynamic desirable Operational Mode: trunk // Details omitted for clarityDTP Mode Combinations
When a trunk refuses to come up, check the two modes against this table first:
Local mode
Neighbor mode
Result
dynamic auto
dynamic auto
No trunk
dynamic auto
dynamic desirable
Trunk
dynamic desirable
dynamic desirable
Trunk
trunk (on)
dynamic auto or desirable
Trunk
trunk (on)
access
Mismatch
Table 1 – DTP mode outcomes
Answer the question below
Do two dynamic-auto ports form a trunk?
Answer the question below
A hardcoded trunk facing an access port gives which result?
Each trunk keeps a single VLAN whose frames cross untagged: the native VLAN.

Figure 8 – Untagged frames land in the native VLAN
The default Native VLAN is VLAN 1 on every Cisco switch.
Answer the question below
What is the default native VLAN on Cisco switches?
It is not recommended to leave VLAN 1 as the native VLAN, as VLAN hopping attacks exploit this.
The best approach is to move it to an unused VLAN.
Set VLAN 99 as the Native VLAN on SW1:SW1# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW1(config)# interface g0/1 SW1(config-if)# switchport trunk native vlan 99 SW1(config-if)# endMirror 99 on SW2:
SW2# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW2(config)# interface g0/1 SW2(config-if)# switchport trunk native vlan 99 SW2(config-if)# endBoth ends now agree that VLAN 99 is the native VLAN.
Native VLAN and the allowed list are set per trunk interface, never globally.Answer the question below
Is the native VLAN set globally or per interface?
The Final Check
Read the trunk one last time and compare it with your first look:
SW1# show interfaces trunk Port Mode Encapsulation Status Native vlan Gi0/1 desirable 802.1q trunking 99 Port Vlans allowed on trunk Gi0/1 10,20,30 Port Vlans allowed and active in management domain Gi0/1 10,20 Port Vlans in spanning tree forwarding state and not pruned Gi0/1 10,20Three things to check, in order:
Status reads trunking, so the port is a trunk, not an access port
Native vlan reads 99, matching the other end
Vlans allowed shows 10,20,30, the list you trimmed then extended
Now that you have reviewed the basics, move on to the next lesson: a hands-on Troubleshoot 802.1Q Trunking lab.
Answer the question below
Complete the verification command: show interfaces ____