Feature Requirements |
Series |
Models |
|---|---|---|
BGP can establish VPNv4 peer relationships with peers using IPv4 and IPv6 addresses. In this manner, BGP may receive the same BGP VPNv4 route prefix from peers in two forms, but the next hops are IPv4 and IPv6 addresses. In this case, one route recurses to an MPLS (including SR-MPLS) tunnel and the other route recurses to an SRv6 tunnel. Currently, load balancing or FRR cannot be implemented among such BGP VPNv4 routes with the same prefix. BGP selects only one type of route for data forwarding based on route selection rules. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
BGP ingress LSP load balancing and ingress LSP FRR are mutually exclusive. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The POPGO mode does not support load balancing and selects a route to forward packets based on the incoming label. The one-label-per-next-hop POPGO mode and VPN route load balancing are mutually exclusive. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In the unicast address family view, configuration of the peer label capability and configuration of the labeled address family are mutually exclusive. The ipv4-family labeled-unicast and peer label-route-capability (BGP) commands are mutually exclusive. The peer label capability and labeled address family capability cannot be both enabled in the unicast address family view. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |