Vendor560 problems· 4 reviewed

Cisco

560 incident problems in Cisco environments.

All problems (560)

NETWORK-324An EVPN tenant imports the right route-target while one border leaf maps it to the wrong L3VNI after a template clone during a failover rehearsalControl-plane membership is right and forwarding domain identity is not. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced19 minPro NETWORK-099BFD over an encrypted WAN path stays up but the data plane breaksThe fast detection channel looks healthy, yet application traffic fails because larger encrypted packets are dropped midpath.NetworkAdvanced19 minPro NETWORK-071BFD timers are too aggressive for WAN jitter and routing oscillates under light lossLinks are mostly usable, but routing keeps flapping because failure detection is tuned for a clean LAN rather than a noisy WAN path.NetworkAdvanced19 minPro NETWORK-081BGP max-prefix protection drops the session during a route leak but only in one directionBoth peers are configured, yet only one side resets because the received leak exceeds the local protection threshold while the reverse direction stays below it.NetworkAdvanced19 minPro NETWORK-102EVPN MAC mobility on the returning leaf uses a lower sequence and remote sites keep the stale locationThe server is back online, but east-west traffic still follows the old path because mobility ordering never tells peers to trust the new home.NetworkAdvanced19 minPro NETWORK-1221VLAN trunks look healthy but one segment goes root-inconsistentA campus segment works for most VLANs but one path blocks after a trunk template change.NetworkAdvanced19 minPro NETWORK-175A mitigation community is set at the source and stripped before it reaches the edge that should act on it after an environment identity renameThe intent exists in one domain and disappears in the middle of the network. The functional path still exists, but one identity, namespace, or naming assumption still points at the previous environment contract.NetworkAdvanced20 minPro NETWORK-178A mitigation community is set at the source and stripped before it reaches the edge that should act on it during a rollback rehearsalThe intent exists in one domain and disappears in the middle of the network. The steady path hides the problem until the system is asked to move backward through the dependency chain.NetworkAdvanced20 minPro NETWORK-631A 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/방화벽, 목적지 응답을 계층별로 잘라서 확인하면 장애 구간을 훨씬 빠르게 좁힐 수 있습니다.NetworkIntermediate20 minPro NETWORK-088GRE keepalives pass but PMTUD blackholes the applicationTunnel control looks healthy, yet large application payloads fail because path MTU discovery signals never make it back through an intermediate filter.NetworkAdvanced20 minPro NETWORK-077GRE tunnel MTU is too high and BGP over the tunnel flaps only during large updatesSmall keepalives succeed, but route churn triggers session instability because the encapsulated path cannot carry larger update packets cleanly.NetworkAdvanced20 minPro NETWORK-095Route leaking between VRFs works in one direction but the return path missesForward reachability is proven, yet replies fail because the destination VRF only imports part of the leaked prefix set.NetworkAdvanced20 minPro NETWORK-1230STP root placement looks intentional but one access stack goes root-inconsistentA backup uplink that is rarely used becomes active during maintenance and one stack immediately enters a root-inconsistent or blocked state.NetworkAdvanced20 minPro NETWORK-1188Interface flap alarms hide that one side still negotiates the wrong speed and duplex profilePacket loss and churn appear during intermittent link events because one interface reverted to a different negotiation profile after maintenance.NetworkAdvanced21 minPro NETWORK-073QinQ outer VLAN mismatch isolates one tenant even though the provider handoff is upThe carrier circuit is healthy, but one tenant stays dark because the outer service tag expected by the handoff does not match on both edges.NetworkAdvanced21 minPro NETWORK-1191Trunk link stays up but one VLAN is black-holedA trunk link is rebuilt after maintenance. Community threads suggest checking tagging expectations, and it turns out one side still treats a management VLAN as native.NetworkIntermediate21 minPro NETWORK-067VRRP advertisements hit control-plane policing and the backup never sees master lossBoth routers are online, but failover stalls because the protection policy drops the very control traffic that should signal the state change.NetworkAdvanced21 minPro NETWORK-690A 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/방화벽, 목적지 응답을 계층별로 잘라서 확인하면 장애 구간을 훨씬 빠르게 좁힐 수 있습니다.NetworkIntermediate22 minPro NETWORK-066ECMP asymmetric return traffic breaks the stateful firewall even though both routers look healthyEvery routing table looks correct, yet sessions reset because the forward and return directions traverse different firewall state holders.NetworkAdvanced22 minPro NETWORK-083MPLS L3VPN route is present in the core but import RT mismatch keeps the customer VRF emptyThe transport side looks correct, but the service remains dark because the destination VRF never imports the route target the provider is exporting.NetworkAdvanced22 minPro