Learning paths › Scenarios › BGP policy, tunnels and first-hop services
BGP policy, tunnels and first-hop services
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.
Lessons
- Fix a mistyped neighbour, then an inbound route-map
- Hold the topology still and vary the policy
- Tell a wrong remote-AS from an AS_PATH rejection
- Separate peer eligibility from IP reachability
- Choose multihop over disabling the connected check
- Treat the tunnel and its underlay as two problems
- Carry OSPFv3 across an IPv4-only hop
- Name the exact source and destination to test
- Advertise the tunnel destination, not just the neighbour
- Hold the address plan still across both cases
- Match GRE protocol 47 against IPv6-in-IPv4 protocol 41
- See NAT, DHCP and HSRP share one topology
- Do not assume a reused diagram keeps its config
- Stop two HSRP routers both going active
- Trace an NTP failure back to a missing address
- Put the NAT inside and outside roles back
- Add a relay when the DHCP server moves off-segment
- Follow a DHCP request through the relay and back
- Put both HSRP routers in the same group
- Fix the helper address, then route to the server
- Point the NAT ACL at the real inside subnet