Learning paths › Scenarios
Enterprise Scenarios: Isolate The Fault, Then Defend The Call
Most of this path is Cisco IOS fault isolation with one right answer — 69 lessons of it, through Layer 2 and EIGRP, then OSPF and BGP adjacencies, then BGP policy, tunnels and first-hop services. Above that sit fourteen lessons that have no single right answer: the same intent written four ways, and design calls where the constraints genuinely conflict. Twelve break-fix tickets come with them — eight mixed-vendor, four open-ended.
Level: Advanced · Provider: Multi-vendor
What you will be able to do
Isolate a fault to one device and one cause, then justify a change where the evidence is incomplete and the constraints conflict.
- Separate Layer 2 from routing, adjacency from route installation, and policy from reachability, across 69 Cisco IOS fault-isolation lessons.
- Translate the same intent across Cisco IOS, Junos, Arista EOS and AOS-CX, and read the operational evidence each platform gives you.
- Close an open-ended scenario — a multi-building outage, a merger with overlapping addressing, segmentation that must not break shared services — with positive tests, negative controls and a stated rollback condition.
Skills
- Cisco IOS
- Fault isolation
- Multi-vendor operations
- Junos
- Arista EOS
- AOS-CX
- Design trade-offs
Courses
- Multi-vendor operations (8 lessons) — Translate intent across platforms, compare operational evidence, and coordinate changes across a mixed-vendor network.
- Open-ended scenarios (6 lessons) — Investigate incidents with incomplete evidence, justify design trade-offs, and define verification and rollback before acting.
- Layer 2 and EIGRP fault isolation (24 lessons) — Worked break-fix tickets that start at Layer 2: forwarding behaviour read from the configuration and from the device rather than the diagram's labels, a missing or wrong VLAN, a trunk encapsulation mismatch, an admin shutdown told from a down line protocol, a trunk err-disabled by BPDU Guard, and one switch you are not allowed to touch — then EIGRP faults split into interface, neighbour and route, with K-value mismatches, a static neighbour paired with multicast discovery, mismatched timers and a network statement selecting the wrong interface.
- OSPF, EIGRP and BGP adjacency faults (24 lessons) — Adjacency faults across three protocols, one cause at a time: an interface addressed in the wrong subnet, an ACL dropping IP protocol 88, an OSPF area or network-type mismatch, a letter O typed as a zero in an authentication key, a key chain pointing at nothing, a passive interface left on a transit link, authentication applied to the wrong area, and an MTU mismatch that stalls database exchange — closing on BGP sessions that need TCP 179 up and a route to the peer's loopback before any prefix appears.
- BGP policy, tunnels and first-hop services (21 lessons) — Twenty-one tickets that hold the topology still and vary only the policy: a mistyped neighbour and then an inbound route-map, a wrong remote-AS told from an AS_PATH rejection, peer eligibility separated from plain IP reachability, and multihop weighed against disabling the connected check — then a tunnel and its underlay treated as two problems, with GRE's protocol 47 kept apart from IPv4-in-IPv4's 41, and a last set where address translation roles, a DHCP helper address and two HSRP routers both going active share one topology.
Other learning paths
- Cisco CCNA: Wire It, Route It, Secure It
- Visual Modules: The CCNA, Drawn And Narrated
- Juniper JNCIA-Junos: One Candidate Config At A Time
- Arista EOS: Build The Switched Campus, Port By Port
- HPE Aruba AOS-CX: Campus Switching, Routed Both Ways
- Palo Alto PAN-OS: Everything Before You Touch Prod
- Fortinet FortiSwitch: Switching Under The Firewall's Thumb
- Linux For Network Engineers: The Shell Is The Interface
- Network Automation: Never Type The Same Change Twice
- Cloud Networking: Where The Packet Actually Goes
- Juniper Professional: Past The Associate, Into The Weeds
- Cisco CCNP Enterprise: Where The WAN Actually Lives
- Cisco CCNP Security: Lock Down What’s Already Live
- Cisco CCNP Data Center: Keep The Fabric Breathing
- BGP In Practice: The Protocol The Internet Runs On
- Network Security Engineer: Detect, Triage, Contain