Trunking, 802.1Q, and Native VLAN
An access port can carry one VLAN, but a VLAN must be able to span many switches. The link that does this is a trunk, and the language it speaks is 802.1Q: a four-byte tag slipped into every frame that tells each switch which VLAN the frame belongs to. This lesson is where “tagged”, “native”, and “allowed VLAN” stop being buzzwords and become the commands you can type.
- Describe the 4-byte 802.1Q tag and its fields: TPID, PCP, DEI, and 12-bit VLAN ID.
- Explain why the maximum frame grows from 1518 bytes to 1522 bytes when tagged.
- Understand why trunks carry many VLANs and access ports carry one.
- Configure a trunk with switchport mode trunk and manage the native VLAN and allowed VLAN lists.
- Explain the danger of a native VLAN mismatch and why the native VLAN is left untagged.
- Position ISL as the legacy Cisco-proprietary trunking protocol that 802.1Q replaced.
- Verify trunks with show interfaces trunk.
The problem a trunk solves
VLAN 10 exists on switch S1 and on switch S2. To carry VLAN 10 traffic between them, the two switches need a link — but a single copper cable is one physical path. If both VLANs 10 and 20 must cross the same cable, how can a frame for VLAN 10 be told apart from a frame for VLAN 20 at the far end?
The answer is tagging. The sending switch inserts a small identifier into each frame saying which VLAN it belongs to; the receiving switch reads it, strips it (on access ports) or keeps it (on trunks), and switches the frame into the right VLAN. A trunk is the port that performs this: one physical link, many logical VLANs, each frame labelled. This is the whole job of IEEE 802.1Q, the industry-standard trunking protocol.
The 802.1Q tag, byte by byte
802.1Q inserts a 4-byte tag between the source MAC address and the EtherType/Length field (sometimes called the (type/length) field) of the ordinary Ethernet frame. The tag has two halves:
- Tag Protocol Identifier (TPID) — 2 bytes, fixed at the EtherType value
0x8100. The receiving switch sees0x8100exactly where it expected the EtherType and knows: “a VLAN tag is coming next.” - Tag Control Information (TCI) — 2 bytes, split into three sub-fields:
- Priority Code Point (PCP) — 3 bits, a Class-of-Service priority from 0–7 (802.1p). Voice is commonly marked 5.
- Drop Eligible Indicator (DEI) — 1 bit, marks frames that may be dropped first under congestion (formerly CFI).
- VLAN ID (VID) — 12 bits, the VLAN number, 0–4095 (usable 1–4094).
So the four bytes unpack as: 2 bytes 0x8100 + 3 bits priority + 1 bit DEI + 12 bits
VLAN ID. The 12-bit VID is the same field that limits VLANs to 4094 usable numbers from Lesson 12.
Frame sizes: 1518 and 1522
A standard Ethernet frame is at most 1518 bytes (add the 8-byte preamble and SFD and you get 1526 on the wire). Tagging adds 4 bytes, so the maximum becomes 1522 bytes for a tagged frame. This number has to be exact for the exam:
Every receiving interface on the path must be able to accept a 1522-byte frame if trunks are in use. This is why a frame that is jumbo-sized on one link can be silently dropped at the next switch: maximum transmission unit (MTU) settings and interface buffers must accommodate the tag.
The native VLAN
The native VLAN is the one VLAN you do not tag on a trunk. It defaults to VLAN 1. Frames belonging to the native VLAN travel across the trunk as ordinary, untagged Ethernet frames — which keeps them readable by devices that do not understand tagging and gives you a management path even if trunking fails.
Because both ends of a trunk must agree on which VLAN is native, a mismatch is a classic failure
mode. Two switches that disagree on the native VLAN may accidentally bridge VLANs:
untagged native frames from S1 (VLAN 10) arrive on S2, which interprets them as its own native VLAN
(VLAN 20), and the two VLANs leak into each other at Layer 2. The leak may not show up in DHCP or ARP
right away, but broadcast traffic and unexpected reachability are the symptoms, and
show interfaces trunk highlights the mismatch.
Configuring a trunk
The minimal trunk is two commands on each switch, plus a native-VLAN tweak if you want to move away from VLAN 1:
S1(config)# interface gigabitethernet 0/24 S1(config-if)# switchport mode trunk S1(config-if)# switchport trunk native vlan 99 ! optional, but good practice S1(config-if)# end S2(config)# interface gigabitethernet 0/24 S2(config-if)# switchport mode trunk S2(config-if)# switchport trunk native vlan 99 S2(config-if)# end
switchport mode trunk forces the port to trunk unconditionally. There are softer
options (dynamic desirable, dynamic auto) that use DTP
(Dynamic Trunking Protocol) to negotiate trunking, and an exam answer may ask which one forms a trunk:
desirable forms a trunk with desirable or auto, while auto-only-to-auto stays an access link.
The safest, most exam-safe configuration is the static switchport mode trunk, which
leaves nothing to negotiation.
Filtering VLANs with allowed lists
By default a trunk carries all VLANs. Restricting it is a security measure: a trunk that carries only the VLANs you actually need cannot be used to smuggle traffic from unexpected VLANs across the switch fabric. The command is:
S1(config-if)# switchport trunk allowed vlan 10,20,99
Now VLAN 30’s frames will not cross this trunk even if VLAN 30 exists on S1. Two exam details:
the list is a comma-separated set of IDs (ranges allowed, e.g. 10-20), and resetting to
the default uses no switchport trunk allowed vlan or the explicit
switchport trunk allowed vlan all. Also note the allowed list and the native VLAN are
separate concepts — the native VLAN should usually be in the allowed list too, or untagged
traffic may be dropped.
Verification and the mismatch trap
S1# show interfaces trunk Port Mode Encapsulation Status Native vlan Gi0/24 on 802.1q trunking 99 Port Vlans allowed on trunk Gi0/24 10,20,99 Port Vlans allowed and active in management domain Gi0/24 10,20
Read the output top to bottom: the port is in trunk mode with 802.1Q encapsulation, the native VLAN is 99, and only VLANs 10, 20 and 99 may cross it (VLAN 99 appears in the allowed list even though it is native). The third block lists only VLANs that exist on the switch, which is why 99 drops out — remember that VLAN 99 must be created for the native choice to be active.
The native VLAN mismatch shows up here too: if S1 says native 99 and S2 says native VLAN 1, the trunk sometimes still comes up (because DTP/management traffic rides native VLAN 1) while the two switches silently disagree about every untagged frame. The symptoms are bizarre connectivity where management pings work but data VLANs cross-pollinate — a real troubleshooting scenario on the exam.
ISL: the legacy alternative
Before 802.1Q became the standard, Cisco offered ISL (Inter-Switch Link), an Ethernet-proprietary trunking method. ISL fully encapsulated the frame with a 26-byte header and a 4-byte trailer (30 extra bytes), tagged every VLAN including the native one, and worked only on Cisco equipment. It survives on the syllabus as a historical contrast: 802.1Q is the open IEEE standard, ISL is the legacy Cisco-proprietary protocol. Modern Cisco switches negotiate 802.1Q only, so if a question asks for the industry-standard trunking protocol, the answer is 802.1Q.
| Characteristic | 802.1Q | ISL (legacy) |
|---|---|---|
| Standard | IEEE open standard | Cisco proprietary |
| Overhead | 4-byte tag inside the frame | 30 bytes (26 header + 4 trailer) surrounding the frame |
| Native VLAN | Timeless: left untagged | None — all VLANs tagged |
| Used today | Yes — the industry standard | No — obsolete on modern platforms |
The vocabulary you need
Every term below appears in the lesson text above. Select one to read its definition, then use the quiz at the end to check what stuck.
Review
Check what you have learned with these review questions.
Sources & references
- Cisco. CCNA (200-301) Exam Topics. cisco.com.
- IETF. Request for Comments (RFCs). rfc-editor.org.
- IANA. Internet Assigned Numbers Authority registries. iana.org.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.