Vendor560 problems· 4 reviewed

Cisco

560 incident problems in Cisco environments.

All problems (560)

NETWORK-1473A port-channel stays up and still drops multicastMulticast loss appears on a subset of receivers after a supervisor switchover while the port-channel never drops.NetworkAdvanced12 minProNETWORK-1527An Anycast DNS node advertises and one POP misses probesAnycast DNS health checks fail only from one POP after cleanup.NetworkAdvanced12 minProNETWORK-1497An Anycast DNS node advertises normally and health checks still miss one POPAnycast DNS health checks fail only from one POP after a route-reflector maintenance VRF cleanup.NetworkAdvanced12 minProNETWORK-1517An Anycast DNS node advertises normally and one POP misses probesAnycast DNS health checks fail only from one POP after route-reflector cleanup.NetworkAdvanced12 minProNETWORK-1507An Anycast DNS node advertises normally and one POP still misses health checksAnycast DNS health checks fail only from one POP after a route-reflector cleanup.NetworkAdvanced12 minProNETWORK-1463An LACP bundle stays up and still blackholes one VLANOnly one VLAN experiences packet loss after a peer maintenance event while the bundle stays up.NetworkAdvanced12 minProNETWORK-1451An OSPF adjacency reaches two-way and still never advancesAn adjacency appears half-alive and never reaches full after a link refresh changed one side's interface defaults.NetworkAdvanced13 minProNETWORK-1442A BGP failback never happensPrimary links recover and traffic stays on the backup path until manual intervention.NetworkAdvanced14 minProNETWORK-1355A Cisco OSPF adjacency stays two-wayA routing policy cleanup introduces passive-interface default and later one neighbor remains stuck in two-way despite matching hello parameters.NetworkAdvanced14 minProNETWORK-1319A BFD-assisted failover never triggers the backup routeA network adds ACL hardening and later one redundant path stops failing over quickly despite healthy-looking interface counters.NetworkAdvanced15 minProNETWORK-1432A BGP failback never restores the preferred ISPA BGP failback never restores the preferred ISP focuses on bgp and asks the reader to isolate the key signal in Cisco. BGP failback bugs often come from attribute handling on reflected paths rather than from neighbor health.NetworkAdvanced15 minProNETWORK-1422A BGP failback never restores the primary ISPA BGP failback never restores the primary ISP focuses on bgp and asks the reader to isolate the key signal in Cisco. BGP preference bugs often come from attribute handling on reflection rather than from neighbor health.NetworkAdvanced15 minProNETWORK-1412A BGP failover never restores the preferred ISPA BGP failover never restores the preferred ISP focuses on bgp and asks the reader to isolate the key signal in Cisco. BGP recovery bugs often come from attribute loss during reflection rather than from neighbor reachability itself.NetworkAdvanced15 minProNETWORK-1323A BGP session stays up and reachability still diesA provider handoff is redesigned and only then one BGP neighbor starts flapping or refusing traffic despite correct passwords and addresses.NetworkAdvanced15 minProNETWORK-1345A Cisco DHCP relay looks healthy and the server still logs the wrong sourceA Cisco DHCP relay looks healthy and the server still logs the wrong source focuses on firewall-policy-basics and asks the reader to isolate the key signal in Cisco. DHCP relay failures after VRF moves often come from source context drift, not...NetworkAdvanced15 minProNETWORK-1290A load balancer can reach the service IP but health checks still failA service behind a load balancer never becomes healthy even though the backend responds from the same subnet during manual testing.NetworkIntermediate15 minProNETWORK-1273A port-channel comes up partially but traffic still hashes badlyAn EtherChannel looks mostly healthy after a maintenance change and later only certain flows or VLANs misbehave.NetworkIntermediate15 minProNETWORK-1296A port-channel reports up but multicast behaves strangelyA port-channel looks healthy in summaries and only multicast-dependent services begin failing after a template rollout.NetworkIntermediate15 minProNETWORK-1402A route reflector cluster keeps preferring the wrong exitA route reflector cluster keeps preferring the wrong exit focuses on bgp and asks the reader to isolate the key signal in Cisco. BGP policy bugs often come from the order in which attributes are mutated, not from the absence of the inte...NetworkAdvanced15 minProNETWORK-1308Large DNS lookups fail only on TCP fallbackOnly large DNS responses or DNSSEC-heavy queries fail through a path that otherwise seems to resolve names correctly.NetworkAdvanced15 minPro