Feature Requirements |
Series |
Models |
|---|---|---|
The eMDI detection does not support P node detection in Layer 3 multicast Rosen-MVPN scenarios and L2VPN multicast scenarios. The configurations for detection on P nodes fails. |
NetEngine 8000 F |
NetEngine 8000 F1A |
In NG-MVPN scenarios, VPN cannot be identified on P nodes. If the SG is the same among multiple VPNs, multiple pieces of traffic are detected simultaneously. As a result, an eMDI detection error occurs. Please prevent this scenario during networking deployment. |
NetEngine 8000 F |
NetEngine 8000 F1A |
In NG-MVPN dual-node protection scenarios, if the transit node and bud node overlap, two pieces of traffic are detected on the same node. As a result, an eMDI detection error occurs. Please prevent this scenario during networking deployment. If the transit node overlaps with the bud node, run the emdi monitor-rate-only command to perform only rate detection. |
NetEngine 8000 F |
NetEngine 8000 F1A |
Downstream eMDI detection does not support the following scenarios: 1, PIM FRR 2, Multicast source cloning-based PIM FRR 3, ABR nodes in segmented NG MVPN scenarios 4, Public-network-side forwarding on root and bud nodes in NG MVPN scenarios 5, Layer 2 multicast eMDI detection does not take effect in unsupported scenarios. |
NetEngine 8000 F |
NetEngine 8000 F1A |
After the eMDI detection period is changed, an eMDI detection error occurs within the first period after such change. If the period is changed to be larger, the eMDI detection data within the first period after such change is small. If the period is changed to be smaller, the eMDI detection data within the first period after such change is large. |
NetEngine 8000 F |
NetEngine 8000 F1A |
The result of eMDI detection within a specified period may be incorrect in the following switching scenarios: 1, Interface switching over inter-board trunk 2, Switching between NGMVPN S tunnels and I tunnels 3, Dual-device hot backup switchback |
NetEngine 8000 F |
NetEngine 8000 F1A |
To prevent the device from incorrectly reporting the number of out-of-order packets and alarms after traffic is interrupted and then restored, the number of out-of-order packets is reported as 0 when there is no packet loss count. When there is no packet loss count, EMDI cannot report the out-of-order packet count alone. |
NetEngine 8000 F |
NetEngine 8000 F1A |
Detection jitter is not supported in BIER scenarios. The channel configuration does not carry the <clock-rate> parameter. Transit nodes and subsequent nodes fail to get aware of the <clock-rate> parameter of channels and therefore jitter cannot be calculated. |
NetEngine 8000 F |
NetEngine 8000 F1A |
The inbound PE in the upstream direction and the outbound PE in the downstream direction do not support BIER EMDI detection. Allow the inbound PE in the upstream direction and the outbound PE in the downstream direction to implement common EMDI detection. |
NetEngine 8000 F |
NetEngine 8000 F1A |