Learning paths › CCNP Enterprise › Maintenance, switching and spanning tree
Maintenance, switching and spanning tree
Keeping a campus diagnosable and then switching it: log timestamps made comparable, the documentation diagnosis depends on, reachability, jitter and loss measured from the device, and a choice between polling, events, flows and capture — then VLANs and trunks, SVIs and a trunked subinterface gateway, three tiers against a collapsed core, link bundling and why one flow stays on one member, the risk a distributed VLAN database carries, and spanning tree from root election through RSTP to MST.
Lessons
- See how one move change ripples through the network
- Make log timestamps comparable across devices
- Keep the documentation that diagnosis depends on
- Read device, client and service evidence in one place
- Measure reachability, jitter and loss from the device
- Filter show output without losing the context
- Choose between polling, events, flows and capture
- Give access, distribution and core distinct jobs
- Collapse the core without losing redundancy
- Choose a switch from required function and capacity
- Judge switch hardware by how it forwards
- Weigh local VLANs against end-to-end VLANs
- Distribute a VLAN database and carry its risk
- Converge faster with proposal and agreement
- Recognise UplinkFast and BackboneFast in old designs
- Map VLAN groups onto a few instances
More in CCNP Enterprise
- Enterprise design and switching
- Topology protection and routing
- Routing policy and isolation
- Services, assurance and automation
- ENARSI — Advanced Routing and Services
- Catalyst SD-WAN — Overlay and Controller Operations
- Routing: EIGRP, OSPF and redistribution
- Internet edge, BGP and overlay transport
- First-hop redundancy, access control and switch services
- Wireless, multicast, automation and SD-Access
- Quality of service and what an outage costs