What state does the vendor describe?
Cisco's IOS XE 17 spanning-tree guide describes a blocking interface as not participating in frame forwarding. It distinguishes that state from forwarding and disabled states within the protocol's operation.
Substation Drafting is independent and is not affiliated with Cisco. That is a vendor and protocol-state reference, not a universal description of every industrial switch, RSTP implementation or protection network. Use the actual approved device and protocol documentation.
Sources: Cisco: Cisco IOS XE 17: Spanning Tree Protocol configuration guide, checked 22 October 2026
Which records should the drawing keep separate?
A physical link can belong on the as-built topology even when its observed protocol state does not forward data for the applicable instance. Record the actual scope of the observation.
| Layer | Evidence | Question |
|---|---|---|
| Physical | Cable and endpoint references | What is installed? |
| Interface | Actual port identity and link indication | What is observed? |
| Administration | Approved enabled or disabled record | What is configured? |
| Protocol | State, instance and observation time | What forwards in this context? |
| Design | Approved topology and intended behavior | Does the record match? |
| Acceptance | Qualified test and review reference | What was verified? |
How can a topology drawing lose an important link?
Illustrative example. A fictional switch report shows one link in a blocking state. A drafter removes its cable from the as-built diagram because the row says not forwarding. The resulting drawing no longer represents the installed cable and endpoints.
The reviewer restores the physical link and records the observed protocol state separately, with its time and applicable context. The communications engineer checks the intended behavior. This does not prove a fault or authorize changing a path cost, port mode or switch priority.
What remains outside a documentation check?
A topology label does not establish protection-message delivery, timing, recovery performance or successful failover. Retain the approved acceptance evidence for those functions instead of treating a complete diagram as a test result.
Do not copy generic configuration commands 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 blocking prove a broken or unplugged cable?
No. Physical and protocol state need separate evidence.
Should the observation include its protocol context and time?
Yes. Do not treat one state report as a timeless property of every path.
Does this authorize network changes?
No. It is a drafting and evidence checklist.