Feature Requirements |
Series |
Models |
|---|---|---|
In control word scenarios, the control word value of 0X10007FFA in TP OAM packets and he control word value of 0X10000021 in BFD packets can be identified. Other control words are forwarded as data packets. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Restrictions for a dot1q VLAN tag termination sub-interface to support the qualify mode are as follows: 1, After the qualify mode is configured for a dot1q VLAN tag termination sub-interface, CE ping is not supported. The CE ping fails. 2, After the qualify mode is configured for a PW in dot1q VLAN tag termination or VLAN mode, the outer VLAN tag is learned, which does not meet the VPLS RFC specifications. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The LDP FRR, LDP RLFA, TE FRR, TE best-effort path, TE protection group, BGP FRR, and backup path of the tunnel do not support VPLS QoS. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If a VLANIF interface is bound to a VSI, VLAN member interfaces must not be a VLAN stacking interfaces. Otherwise, traffic is interrupted. The configuration is not limited. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a VPLS switches from the decoupling mode to the non-decoupling mode, a short-time traffic interruption occurs, and unicast transmission changes to broadcast transmission. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After a VPLS switches to the decoupling mode, ACL cannot be enabled to control or match the inner IP header. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the VPLS public-network-and-private-network decoupling function is disabled using the undo mpls vpls convergence separate enable command, the VPLS does not support ECMP or TI-LFA for SR-MPLS TE tunnels, the protection does not take effect, and the switching performance is poor. Run the mpls vpls convergence separate enable command to enable the VPLS public-network-and-private-network decoupling function. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If multiple network-side outbound interfaces exist, bandwidth restriction and bandwidth guarantee are implemented based on the interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Note the following points: 1, If no spoke PW configuration exists, suppression does not take effect on unknown unicast, multicast, or broadcast traffic. In P2P mode, when packets are sent by a PE, it searches the decapsulation table for an entry for upstream packets. The upstream packets that match the table are unicast. The upstream packets that do not match the table are discarded. 2, If a spoke PW configuration exists and the spoke PW is Up, the packets to be forwarded to the spoke PW that fail to match the decapsulation table are suppressed based on the B-DMAC. Because the B-DMAC is not a multicast or broadcast MAC address, suppression takes effect on unknown unicast packets, not on multicast or broadcast packets. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
For public network tunnels: In VPLS over GRE scenarios, you can enable the flow label function. Flow labels can be encapsulated, but flow label-based load balancing is not supported on the P. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Loopback cannot be set on user-side interfaces of the VLL\VPLS\EVPN\L2TPV3\PORTSWTICH\MODE L2 network. Loopback can be set only on Ethernet interfaces, Ethernet sub-interfaces, Eth-Trunk interfaces, and Eth-Trunk sub-interfaces. If loopback is set on other types of interfaces, a broadcast storm is caused on the Layer 2 network. Do not set loopback for non-supported services. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Multicast supports outbound interface-based VPLS QoS rather than VSI-based VPLS QoS. Traffic rate is limited based on the interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In the layer 2 loop detection scenario, when the time when a blocked interface will be unblocked is configured using the loop-detect block command before the block/unblock function, if a loop exists, the interface is blocked. As a result, the block/unblock function is not implemented due to time sequence. Configure the block/unblock function before setting the time when a blocked interface will be unblocked. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Restrictions for a Layer 2 interface to support Layer 3 ping are as follows: AC interfaces support access through a VLANIF interface or sub-interface rather than through a VE, QinQ, or main interface. PW-side interfaces support Ethernet interfaces, sub-interfaces, and TE or Eth-Trunk interfaces and sub-interfaces. If the preceding constraints are not met, the ping fails. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the P2P VSI function is configured, broadcast or multicast features, such as Layer 2 suppression, MAC address limitation, and IGMP snooping are not supported. Do not configure the multicast or broadcast functions after configuring the P2P VSI function. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When loop detection is enabled on a PE, the number of looped PE interfaces in the same loop cannot be greater than 2, Otherwise, the loop detection function becomes invalid. The loop detection function cannot be configured on over two interfaces in the same loop. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
VPLS non-decoupling scenarios do not support the following: 1, TE over GRE 2, LDP over TE over GRE 3, BGP over TE over GRE 4, BGP over LDP over TE over GRE If any of these features is used, a traffic forwarding failure will occur. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If VLL VPN QoS is used in the following scenarios: 1. TE over GRE 2. LDP over TE over GRE 3. BGP over TE over GRE 4. BGP over LDP over TE over GRE Traffic fails to be forwarded in the VPN QoS scenario. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Currently, only LDP VLL/VSI detection is supported. BGP VSI and VLL detection and PW switching are not supported. The configuration of an unsupported function does not take effect. Deploy it properly. |
NetEngine 8000 F |
NetEngine 8000 F1A |
On a Layer 2 network, if a tag is removed or encapsulated or the VLAN ID or VLAN priority is modified in packets, a false alarm for the loop detection function may be reported or loop detection does not take effect. Deploy it properly. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a physical main interface is blocked, its physical sub-interfaces are not blocked. When a trunk interface is blocked, its member interfaces are also blocked, but the trunk sub-interfaces are not blocked. Deploy it properly. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Loop detection can be performed on an interface only when the following conditions are met: 1. Entire-port transparent transmission is configured on the main interface. 2. Loop detection is enabled on the main interface. 3. The detection VLAN on the local main interface is the same as the detection VLAN (if the detection VLAN is not configured, the service VLAN is used) on the peer sub-interface. If the VLAN configuration on the local main interface is different from that on the peer sub-interface, a false blocking may occur. Deploy it properly. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the device is restarted, as long as the BFD session status is not Up, the primary and secondary PWs are associated for service switching. The PW whose BFD detection status is Up is preferentially served. However, if the primary and secondary PWs are not Up, PW switching is not affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A VE ID is used as an identifier for a site to access a BGP VPWS or BGP VPLS. 1. If a CE is dual-homed to PEs, the same VE ID can be assigned to different PEs. 2. In a non-dual-homing scenario, different PEs cannot be assigned the same VE ID. If BGP VPWS or BGP VPLS assigns the same VE ID to sites on different PEs, the same VE ID affects each other. As a result, services cannot be established. VE IDs (site IDs for BGP VPLS and CE IDs for BGP VPWS) must be properly planned to ensure that different sites accessing BGP VPLS or BGP VPWS services use different VE IDs. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an active-active scenario where primary and secondary PWs of a VPLS interwork with a VXLAN, the VXLAN cannot interwork with an EVPN. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a scenario where primary and secondary PWs of a VPLS interwork with a VXLAN, the ignore-standby-state parameter cannot be configured for the PW on a DC GW. The BUM traffic from the TOR switch to the PE-AGG may be duplicated. The PE-AGG -> TOR switch traffic may flow back to the PE-AGG. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |