Topic183 problems· 2 reviewed

Routing And Failover Paths

183 incident problems about Routing And Failover Paths. Start with the reviewed ones.

All problems (183)

NETWORK-121A transit interface was left out of passive-interface default exceptions, and a rogue OSPF adjacency forms during an access switch replacementThe underlay works until maintenance introduces a neighbor on a segment that should never have participated in routing.NetworkAdvanced17 minPro NETWORK-270A VRRP pair shares the gateway IP while one downstream ACL still permits only the previous virtual MAC during a failover rehearsalRedundancy is healthy and the dependent security policy remains bound to yesterday's identity. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced17 minPro NETWORK-129BFD minimum receive timers do not align between vendors, and only one side believes the session is stableBoth devices show partial liveliness, but the negotiated timing reality differs enough to keep the path flapping.NetworkAdvanced17 minPro NETWORK-115BGP confederation sub-AS policy strips the community needed to choose the correct exit pathThe routes arrive everywhere, but exit selection is wrong because a transit policy removed the signal the edge uses for preference.NetworkAdvanced17 minPro NETWORK-111Consistent hashing is disabled during a line-card replacement and long-lived sessions reset across ECMP membersRedundancy remains, but user sessions drop because path stickiness disappeared during the hardware swap window.NetworkAdvanced17 minPro NETWORK-122eBGP TTL security is configured on one side only after the provider path gains an extra hop, and the session drops permanentlyBoth peers still have the right neighbors configured, yet the control-plane hardening assumption no longer matches reality.NetworkAdvanced17 minPro NETWORK-137VRRP advertisements pass, but the mixed-vendor pair uses different packet version expectations and both routers think they are masterLayer-3 reachability exists, yet first-hop symmetry collapses because redundancy control messages are interpreted differently.NetworkAdvanced17 minPro NETWORK-143A BGP blackhole community is set correctly, but the route reflector policy strips it before it reaches the transit edge and mitigation never activatesMitigation signaling exists at the source, yet it vanishes in the core policy path.NetworkAdvanced18 minPro NETWORK-234A BGP session remains established while graceful restart keeps stale forwarding alive longer than the outage can tolerate during a failover rehearsalControl-plane continuity looks stable while data-plane truth is already different. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minPro NETWORK-204A failover signal tracks device liveness while the service behind it is already gone during a failover rehearsalThe route follows a reachable box instead of the actual service dependency. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minPro NETWORK-176A mitigation community is set at the source and stripped before it reaches the edge that should act on it after a control-plane upgradeThe intent exists in one domain and disappears in the middle of the network. The workload or policy had been stable, but the upgraded control layer now interprets one dependency differently.NetworkAdvanced18 minPro NETWORK-173A mitigation community is set at the source and stripped before it reaches the edge that should act on it after a maintenance template changeThe intent exists in one domain and disappears in the middle of the network. The path looked stable before the template changed, but one inherited assumption no longer matches the live environment.NetworkAdvanced18 minPro NETWORK-224A route-map matches the right prefix set while one additive community action is replaced instead of appended after a control-plane upgradeThe route is still policy-matched, yet a downstream signal disappears because one action semantics was misunderstood. The workload or policy had been stable, but the upgraded control layer now interprets one dependency differently.NetworkAdvanced18 minPro NETWORK-222A route-map matches the right prefix set while one additive community action is replaced instead of appended during a failover rehearsalThe route is still policy-matched, yet a downstream signal disappears because one action semantics was misunderstood. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minPro NETWORK-226A route-map matches the right prefix set while one additive community action is replaced instead of appended during a rollback rehearsalThe route is still policy-matched, yet a downstream signal disappears because one action semantics was misunderstood. The steady path hides the problem until the system is asked to move backward through the dependency chain.NetworkAdvanced18 minPro NETWORK-151A route-reflector cluster reflects the primary path, but the add-path policy excludes backup labels and remote PIC never builds the alternate forwarding stateCore routing is healthy, yet fast failover never materializes because backup state was never distributed.NetworkAdvanced18 minPro NETWORK-282A route-reflector keeps the primary path while the backup path attributes are never re-advertised after policy cleanup during a failover rehearsalReachability remains while fast failover assumptions quietly disappear. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minPro NETWORK-162A standby edge keeps routes while losing the preference signal that made inbound traffic behave correctly during a failover rehearsalFailover succeeds functionally and inbound policy intent disappears on the alternate path. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minPro NETWORK-511A static summary route is valid (Rollout Stuck)A static summary route is valid (Rollout Stuck) focuses on Routing And Failover Paths and asks the reader to isolate Rollout Stuck in Cisco. 실무에서는 rollout-stuck 이슈를 볼 때 DNS, 라우팅, ACL/방화벽, 목적지 응답을 계층별로 잘라서 확인하면 장애 구간을 훨씬 빠르게 좁힐 수 있습니다.NetworkIntermediate18 minPro NETWORK-104BGP add-path is enabled on the route reflector, but the edge still rejects the extra routes due to a capability mismatchThe core advertises multiple paths, yet the edge keeps only one because one side never negotiated the additional-path capability correctly.NetworkAdvanced18 minPro