Vendor106 problems

Juniper

106 incident problems in Juniper environments.

All problems (106)

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 NETWORK-062MLAG peer link is healthy but the orphan VLAN is not allowed and ARP blackholes one rackThe chassis pair stays up, yet half the rack cannot resolve the gateway because the affected VLAN was never permitted across the peer path.NetworkAdvanced23 minPro NETWORK-085VXLAN VTEP peers are reachable but the overlay MAC table never learns one tenant segmentThe underlay looks healthy, yet one tenant still cannot communicate because the overlay learning path or segment mapping is broken for that VNI only.NetworkAdvanced23 minPro NETWORK-063Route reflector strips a BGP community and upstream traffic engineering stops workingSessions remain established and routes are present, but the intended upstream policy no longer triggers because a critical community vanished in the reflection path.NetworkAdvanced24 minPro NETWORK-035BGP session is established but the expected prefix never reaches the RIBThe neighbor shows Established, yet the target route is absent because a prefix list, route map, or best-path rule discards it before installation.NetworkAdvanced26 minPro NETWORK-039VRF leak design misses the import policy for a shared services subnetThe route exists in the source VRF, but shared services remain unreachable because the target VRF never imports the right route target or policy match.NetworkAdvanced27 minPro