What does the vendor reference establish?
Cisco's IOS XE VLAN trunking guide describes a trunk receiving tagged and untagged traffic and forwarding untagged traffic in the configured native VLAN by default. It also describes untagged transmission when the VLAN matches the outgoing port's native VLAN.
That documented behavior is a vendor and configuration example, not a universal instruction for every industrial switch. Substation Drafting is independent and is not affiliated with Cisco. The approved network design and actual device configuration control the project.
Sources: Cisco: Cisco: official reference checked 22 October 2026
Which fields make the link schedule reviewable?
Document both endpoints. Matching VLAN numerals do not establish matching port treatment or prove that a particular application message is passing correctly.
| Field | End A and end B evidence | Question |
|---|---|---|
| Interface | Device and physical port | Same actual link? |
| Port mode | Approved access or trunk basis | Compatible roles? |
| Membership | Approved VLAN scope | Which traffic is allowed? |
| Tag treatment | Tagged or untagged basis | What is on the link? |
| Native treatment | Applicable configured value | How is untagged traffic handled? |
| Verification | Approved as-built evidence | Matches the drawing? |
How can an apparently complete schedule be ambiguous?
Illustrative example. A fictional switch-to-device row contains VLAN 20 at both endpoints but says nothing about tagging. One reviewer assumes every frame carries that tag; another assumes the connected device sends untagged frames and the switch assigns them to its native VLAN.
The drawing cannot resolve the conflict from the number 20. Obtain the approved interface behavior and actual configuration references, then document the resolved arrangement. The example does not recommend VLAN 20, expose a real network or authorize a port change.
What should the drafter avoid concluding?
A completed VLAN row does not prove protection communications, multicast filtering, timing or failover behavior. Keep those acceptance records with the responsible communications and protection engineers.
Do not copy configuration commands from a generic reference into a live substation. Engineering sign-off is performed only by the registered engineer on the job.
Common questions
What else should the bid team know?
Does VLAN membership prove a frame has a tag?
No. Port and native-VLAN behavior also matter.
Can one endpoint establish the complete link arrangement?
No. Retain the approved behavior at both ends.
Does this guide authorize configuration changes?
No. It is a drafting evidence checklist.