Vendor560 problems· 4 reviewed

Cisco

560 incident problems in Cisco environments.

All problems (560)

NETWORK-158A multicast RP failover is configured, but MSDP source-active filtering drops one application's group range and recovery never completesCore redundancy exists, yet the failover control-plane view excludes the affected stream set.NetworkAdvanced18 minPro NETWORK-306A QoS trust boundary changed on one edge while policy-map assumptions on the WAN handoff still reflect the old marking point during a failover rehearsalMarking is correct in one segment and wrong by the time traffic reaches the WAN policy decision. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minPro NETWORK-1293A route leaking design works until a maintenance reloadInter-VRF reachability is stable for months and fails only after a planned reload or software update.NetworkAdvanced18 minPro NETWORK-1289A route reflects correctly inside the core but one edge never installs itA route is visible at the route-reflector and on several peers, but one edge still never installs it after a prior prefix surge incident.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-105A VXLAN VTEP loopback is reachable in the default table but not in the transport VRF and overlays stay downPing tests look fine from one context, yet the actual encapsulation source resides in a different VRF that lacks the same reachability.NetworkAdvanced18 minPro NETWORK-192An engineered path exists while forwarding never actually prefers it during a failover rehearsalThe control-plane setup is visible and the data-plane choice remains unchanged. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minPro NETWORK-149An EVPN anycast gateway MAC is correct on both leaves, but one site keeps an older virtual router MAC and hosts split traffic unpredictably after maintenanceGateway abstraction exists, yet endpoint behavior diverges because one site's virtual identity is stale.NetworkAdvanced18 minPro NETWORK-156An EVPN border leaf imports the route target correctly, but export policy blocks the MAC-IP advertisement toward the legacy MPLS edge and hybrid reachability failsThe new fabric side looks fine, yet the interdomain bridge is missing one critical advertisement direction.NetworkAdvanced18 minPro NETWORK-387An EVPN fabric imports the tenant route-targetAn EVPN fabric imports the tenant route-target focuses on wan-and-overlay-connectivity and asks the reader to isolate Rollout Stuck in Cisco. 실무에서는 rollout-stuck 이슈를 볼 때 DNS, 라우팅, ACL/방화벽, 목적지 응답을 계층별로 잘라서 확인하면 장애 구간을 훨씬 빠르게 좁힐 수 있습니다.NetworkAdvanced18 minPro NETWORK-124An EVPN fabric imports type-5 routes but misses the companion type-2 host signals, so specific reachability breaks while summaries look fineOverlay routing seems healthy at a prefix level, yet endpoint-level forwarding fails because one route family is absent.NetworkAdvanced18 minPro NETWORK-1251An HSRP failover looks clean on the routers but clients still blackholeA maintenance failover succeeds on the routers, but a portion of users remain offline until cache state ages out or is forced to refresh.NetworkAdvanced18 minPro NETWORK-1281An OSPF adjacency remains stuck in ExStartAn OSPF adjacency remains stuck in ExStart focuses on ospf-operations and asks the reader to isolate the key signal in Cisco. Protocol failures sometimes follow the effective data-plane MTU, not the configured value visible in the template.NetworkAdvanced18 minPro NETWORK-180An overlay fabric can flood traffic broadly while one endpoint optimization still trusts stale host identity during a failover rehearsalGeneral connectivity looks healthy and one endpoint remains blackholed due to stale local knowledge. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minPro