Vendor106 problems

Juniper

106 incident problems in Juniper environments.

All problems (106)

NETWORK-078Anycast service becomes unstable after an IGP cost change moves stateful clients across sitesThe anycast design still advertises correctly, but a cost change shifts clients to another site that does not hold the expected state continuity.NetworkAdvanced21 minPro NETWORK-1220Intermittent packet loss follows only one ECMP pathA service sees sporadic failures only on some flows and packet captures show the issue correlates with one hashed path and larger payloads.NetworkAdvanced21 minPro NETWORK-1225Packet loss follows only jumbo frames on one uplinkLarge transfers fail unpredictably while ordinary traffic continues to work, and the failure follows only some hashed paths.NetworkAdvanced21 minPro NETWORK-090EVPN MAC mobility is detected but the dampening timer keeps traffic pinned to the old leafThe control plane sees the move, yet data still breaks because mobility dampening delays acceptance of the new location longer than the workload can tolerate.NetworkAdvanced22 minPro NETWORK-1198BFD flap symptoms make BGP look unstable when the real issue is an aggressive keepalive path on one sideThe control plane appears unstable, but the real trigger is an overly aggressive liveness path that flaps faster than the underlying network can reliably support.NetworkAdvanced24 minPro NETWORK-1182OSPF adjacency never reaches FullA link migration leaves OSPF Hellos healthy, yet LSDB exchange never completes. Community threads point back to hidden interface MTU mismatch.NetworkAdvanced24 minPro NETWORK-052BFD flaps continuouslyThe routing session looks unstable for no obvious reason, but the real break is that BFD control traffic is handled differently from the data path and gets dropped or delayed.NetworkAdvanced26 minPro NETWORK-1183BGP session comes up but no routes installA peer migration completes and BGP shows Established, but reachability never changes because the import policy still reflects the old prefix scope.NetworkAdvanced26 minPro NETWORK-059Cross-vendor redistribution loop appearsRedistribution seemed correct in each direction separately, but the combined policy creates a feedback loop because the tags used to stop reimport are not interpreted the same way everywhere.NetworkAdvanced28 minPro NETWORK-138A local preference change is present in policy, but without soft reconfiguration the edge never reevaluates existing paths until a clearThe route-map is correct, yet the live table still reflects yesterday's decision because policy reevaluation never happened.NetworkAdvanced16 minPro NETWORK-155A routing summary is correct in normal conditions, but when the only specific route fails the summary still attracts traffic into a black holeAggregation reduced table size, yet it also masked the absence of any viable child route.NetworkIntermediate16 minPro NETWORK-393A static summary route is valid while the tracking object for the real downstream next hop was repointed to an interface that stays up during failure during a staged decommissionThe summary remains installed long after the useful path is gone. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.NetworkIntermediate16 minPro NETWORK-1256Two OSPF neighbors stay in ExStart or ExchangeA routing change enables OSPF between devices that can ping each other but never complete adjacency formation.NetworkIntermediate16 minPro NETWORK-345A BGP edge prefers the right path (Rollout Stuck)A BGP edge prefers the right path (Rollout Stuck) focuses on Routing And Failover Paths and asks the reader to isolate Rollout Stuck in Cisco. 실무에서는 rollout-stuck 이슈를 볼 때 DNS, 라우팅, ACL/방화벽, 목적지 응답을 계층별로 잘라서 확인하면 장애 구간을 훨씬 빠르게 좁힐 수 있습니다.NetworkAdvanced17 minPro NETWORK-153A GRE over IPsec tunnel survives WAN failover, but MSS adjustment stays on the old physical interface and large HTTP transfers start hangingOverlay continuity exists, yet payload sizing logic remained attached to the wrong underlay object.NetworkAdvanced17 minPro NETWORK-330A route summary survives while every specific path behind it is now gone and traffic keeps choosing the black hole during a failover rehearsalAggregation stays healthy after the real forwarding options disappeared. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkIntermediate17 minPro NETWORK-221A route-map matches the right prefix set while one additive community action is replaced instead of appended after a maintenance template changeThe route is still policy-matched, yet a downstream signal disappears because one action semantics was misunderstood. The path looked healthy before the template changed, but one inherited assumption no longer matches the live environment.NetworkAdvanced17 minPro NETWORK-225A route-map matches the right prefix set while one additive community action is replaced instead of appended after a retention policy refreshThe route is still policy-matched, yet a downstream signal disappears because one action semantics was misunderstood. The operational object still exists somewhere in the system, but the lifecycle policy around its supporting state no longer matches reality.NetworkAdvanced17 minPro NETWORK-223A route-map matches the right prefix set while one additive community action is replaced instead of appended after an environment identity renameThe route is still policy-matched, yet a downstream signal disappears because one action semantics was misunderstood. The functional path still exists, but one identity, namespace, or naming assumption still points at the previous environment contract.NetworkAdvanced17 minPro NETWORK-141A route-policy preserves MED during normal operation, but a maintenance template strips it on the backup edge and inbound traffic never returns after failoverPaths exist both ways, yet partner preference signals vanish only on the standby path.NetworkAdvanced17 minPro