Learning paths › Scenarios › Layer 2 and EIGRP fault isolation
Layer 2 and EIGRP fault isolation
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.
Lessons
- Explain forwarding behaviour from the configuration
- Check Layer 2 before you blame routing
- Tell a VLAN problem from a routing problem
- Map the VLAN and subnet plan before testing
- Trust the device, not the diagram's labels
- Spot a missing VLAN and a trunk encapsulation mismatch
- Tell an admin shutdown from a down line protocol
- Find a trunk err-disabled by BPDU Guard
- Note the gateway addresses before chasing the fault
- Fix a switch you are not allowed to touch
- Tell a missing VLAN from a wrong VLAN
- Create a VLAN through VTP and fix the SVI
- Walk access, trunk, allowed VLAN and forwarding in order
- Split EIGRP faults into interface, neighbour and route
- Know when 2-Way is normal and not a fault
- Read the loopback and link addressing convention
- Check the links under a routing protocol first
- Catch an EIGRP K-value mismatch
- Catch a static neighbour paired with multicast discovery
- Catch mismatched OSPF hello and dead intervals
- Fix a network statement that selects the wrong interface
- Catch a stub flag that one spoke does not share
- Solve it without static neighbour statements
- Tell discovery problems from reachability problems