Feature Requirements |
Series |
Models |
|---|---|---|
MVPN over BIER supports only physical main interfaces and sub-interfaces, Eth-Trunk main interfaces and sub-interfaces, dot1q VLAN tag termination sub-interfaces, and QinQ VLAN tag termination sub-interfaces. If the BIER selects an unsupported interface as the next-hop outbound interface, forwarding fails. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
MVPN over BIER does not support MTU-based packet fragmentation. If the size of a packet exceeds the MTU configured on an interface, the interface forwards the packet without fragmenting it. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The tunnel types configured for the root nodes in an MVPN over BIER dual-root protection scenario cannot be different. Otherwise, fast switching of dual-root protection does not take effect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In BIER multi-level load balancing scenarios, traffic may not be evenly load balanced at each level. For example, when the number of load balancing paths configured for two adjacent hops is a multiple relationship, the second hop may fail to perform load balancing (which is not limited to this case). You can adjust the number of load balancing paths at each level to optimize the load balancing effect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
MVPN over BIER supports dual-root 1+1 protection in traffic monitoring mode. MVPN over BIER does not support dual-root 1+1 protection in BFD mode. In the case of a fault, the convergence is slow. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
(1) A maximum of eight sub-domains can be configured on a device. (2) A maximum of four sub-domains can be configured for the same BFR prefix, the same topology, and the same underlay protocol. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In the MVPN over BIER scenario, tunnels of only the BIER type can be deployed for I-PMSIs and S-PMSIs, and the I-PMSIs and S-PMSIs must use the same sub-domain and BSL. Otherwise, the configuration fails. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In MVPN over BIER scenarios, all devices in IS-IS areas must support BIER forwarding. Properly plan the network and ensure that the BIER function is enabled on all devices. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Multiple devices in the same sub-domain can forward data only among devices with the same BSL. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
BIER does not support LFA routes. In the case of microloops, the larger the ring, the slower the convergence. Properly plan the network to prevent microloops. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Different BFR prefix addresses and BFR-IDs need to be configured for different devices. BFR prefixes can be advertised only as host routes, not as network segment routes. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |