Vendor560 problems· 4 reviewed

Cisco

560 incident problems in Cisco environments.

All problems (560)

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 NETWORK-091BGP community is set on ingress but removed by a route-map sequence later in the same policy chainThe intended tag exists briefly, yet traffic engineering never works because a later policy step strips it before export.NetworkAdvanced18 minPro NETWORK-135EVPN ARP suppression keeps the old IP-to-MAC entry after a DHCP reassignment, and east-west peers blackhole the hostAddress reuse looks safe on the DHCP server, yet the overlay still trusts an earlier endpoint identity.NetworkAdvanced18 minPro NETWORK-132GRE keepalives remain up, but an underlay ACL blocks the recursive route to the tunnel destination during WAN failoverTunnel health appears good until the underlay path changes, exposing a missing control route allowance.NetworkAdvanced18 minPro NETWORK-1216HSRP failover happens but some clients still reach the old MACAn HSRP pair switches roles during maintenance and some users remain blackholed even though the new active gateway is up.NetworkAdvanced18 minPro NETWORK-1257ip ospf mtu-ignore brings the adjacency up, but later large LSUs still failOperators apply mtu-ignore to stop an adjacency flap and later discover certain routes still never arrive correctly.NetworkAdvanced18 minPro NETWORK-108LDP sessions form, but labels stay withheldMPLS control adjacencies look normal, yet forwarding never starts because the platform still considers the underlay unstable.NetworkAdvanced18 minPro NETWORK-1226OSPF neighbors remain in ExStartTwo routers see each other and even exchange hellos, but the adjacency sticks in ExStart over a tunnel interface.NetworkAdvanced18 minPro NETWORK-1206OSPF neighbors remain stuck in ExStartTwo routers can see each other but never reach Full adjacency after an interface template change.NetworkAdvanced18 minPro NETWORK-076Policy-based routing sends health-check probes into a blackhole next hopNormal application flows look fine, but the service stays unhealthy because policy routing treats the health-check source differently and steers it to a dead path.NetworkAdvanced18 minPro NETWORK-097Route reflector client to client reflection is disabled and one site never learns the backup exit pathThe RR is reachable, yet backup routes are missing because the reflection policy does not actually propagate client routes to the other client set.NetworkAdvanced18 minPro NETWORK-110The ACL is accepted in the config, but TCAM is full and the new deny rule is never programmed into hardwareOperators trust the running configuration, yet packets keep flowing because the forwarding ASIC could not install the rule set.NetworkAdvanced18 minPro NETWORK-126The MLAG peer link looks healthy, but orphan port behavior prevents storage VLAN failover the way the team expectedRedundant links exist, yet one edge case in dual-chassis behavior leaves a subset of single-homed devices isolated.NetworkAdvanced18 minPro NETWORK-117Tunnel MTU is adjusted on GRE over IPsec, but the underlay policer still drops fragments above the old profileThe logical tunnel is tuned correctly, yet the carrier-facing policy continues to enforce a smaller assumption and silently drops larger traffic.NetworkAdvanced18 minPro NETWORK-113A campus overlay fabric duplicates the anycast gateway across sites with overlapping VNIs and east-west traffic misroutes intermittentlyLocal routing works most of the time, but some flows take the wrong site path because fabric identifiers are no longer unique per domain.NetworkAdvanced19 minPro NETWORK-177A mitigation community is set at the source and stripped before it reaches the edge that should act on it after a retention policy refreshThe intent exists in one domain and disappears in the middle of the network. The operational object still exists somewhere in the system, but the lifecycle policy around its supporting state no longer matches reality.NetworkAdvanced19 minPro NETWORK-174A mitigation community is set at the source and stripped before it reaches the edge that should act on it during a failover rehearsalThe intent exists in one domain and disappears in the middle of the network. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced19 minPro NETWORK-210A shared gateway keeps the same IP while one site drifts to a different virtual identity during a failover rehearsalDependent controls stay anchored on an identity the network no longer presents consistently. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced19 minPro NETWORK-571A 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/방화벽, 목적지 응답을 계층별로 잘라서 확인하면 장애 구간을 훨씬 빠르게 좁힐 수 있습니다.NetworkIntermediate19 minPro NETWORK-246An EVPN route target import is correct while one border leaf maps the tenant to the wrong VNI during a failover rehearsalThe control-plane membership is healthy and the forwarding domain identity is not. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced19 minPro