Feature Requirements |
Series |
Models |
|---|---|---|
MVPNv4 over BIERv6 applies only to physical interfaces and their sub-interfaces (including breakout interfaces), Eth-Trunk interfaces and their sub-interfaces, dot1q/QinQ VLAN tag termination sub-interfaces. If BIERv6 selects an unsupported interface as the outbound interface to a next hop, traffic cannot be forwarded. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a scenario where multicast packets are transmitted through a BIERv6 tunnel, if the total length of a multicast VPN IPv4 packet and BIERv6 header is greater than the MTU of the outbound interface, the packet fails to be forwarded. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Multicast services depend on unicast routes. When VPN unicast routes recurse to IPv6 public network routes for forwarding through SRv6, MVPN supports only BIERv6 tunnels. Supported unicast routes are preferred. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The SRv6 locator used by BIERv6 cannot be associated with Flex-Algo. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The SRv6 locator used by BIERv6 cannot be associated with Flex-Algo. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Only the simple automatic traversal solution is supported. That is, if the next hop does not support BIER in the automatic traversal scenario, a BFER is used as an indirect BFR neighbor, the next hop of the IS-IS route to the BFER is used as the next hop of the indirect BFR neighbor, and routes of other routing protocols cannot be used for recursion. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an NG MVPN over BEIRv6 dual-root 1+1 service scenario, unicast VPNv4 dual-stack is configured. When the primary root AC interface is shut down to trigger a dual-root switchover, second-level packet loss occurs. Configure an export policy on the primary root in the VPNv4 address family for a neighbor and apply the cost to the matched routes so that the cost of the routes sent by the IPv6 neighbor of the secondary root is less than the cost of the routes sent by the IPv4 neighbor of the primary root. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1, The manually configured BFR-neighbor address must be a routable End.BIER address. 2, The BFR-neighbor SD, BSL, and SI that are manually configured must be the same as localy configured BFR-neighbor SD, BSL, and SI. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the BIERv6 root and leaf nodes are of different levels, the root and leaf nodes must be able to learn routes from each other. Currently, only 128-bit host route leaking is supported. If a device learns a large number of routes, a large number of resources are consumed. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Multicast services depend on unicast routes. When VPN unicast routes recurse to IPv6 public network routes for forwarding through SRv6, MVPN supports only BIERv6 tunnels. Supported unicast routes are preferred. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The SRv6 locator used by BIERv6 cannot be associated with Flex-Algo. When the SRv6 locator used by BIERv6 is associated with Flex-Algo, BIERv6 cannot generate a forwarding table. As a result, forwarding fails. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |