Feature Requirements |
Series |
Models |
|---|---|---|
If the loop breaking function is enabled, the reserved Z field in packets needs to be changed. In case of interconnection with other vendors, check whether the vendors are using or have modified the reserved Z field. When the loop breaking function is enabled, the involved device may fail to be interconnected with devices from vendors. In case of interconnection with devices from other vendors, use commands to prevent loop breaking. Command: test-session <session-id> local-ip <local-ip-address> remote-ip <remote-ip-address> local-port <port> remote-port <port> [ vpn-instance <vpn-name> ] [ anti-loop-on ] |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
During DSCP configuration, priority mapping can be performed based only on the default traffic classification policy template. Otherwise, TWAMP does not support traffic entering queues based on the traffic policy configured on the interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When TWAMP Light is performed in an E2E L2+L3 scenario, the TWAMP Light sender is configured on the L3 side and the DIP is specified as the user-side IP address to implement a TWAMP Light test. If the L2 responder is not configured at this time or the configuration is delivered to the responder after the sender initiates the test, TWAMP Light packets cannot be terminated on the L2 side and are transparently transmitted to the terminal or device connected to the L2 AC side. Please configure the L2 responder first. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Trunk member interface-based TWAMP measurement applies only to directly connected interfaces between two directly connected devices and does not apply to multi-device (multi-hop) or point-to-multipoint scenarios. Please plan configurations properly. Otherwise, the trunk member interface-based TWAMP Light function does not take effect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |