Feature Requirements |
Series |
Models |
|---|---|---|
If a static route is associated with NQA and the path tested by NQA also depends on the static route, only direct connection is supported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The server and client of an ICMP jitter, UDP jitter, or TCP test instance must be VRP-based devices. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If a destination IP address is configured for the client end, the outbound interface of a route cannot be any management interface. Do not deploy any test instance for which the outbound interface of a route is a management interface. Otherwise, hardware-based packet sending measurement results obtained during a jitter test are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the client end supports hardware-based packet sending, the board that sends packets must support 1588v2 clock synchronization. Please select a board that supports 1588v2 clock synchronization for packet sending. Otherwise, hardware-based packet sending measurement results obtained during a jitter test are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
NQA ICMP jitter supports hardware-based packet sending and reflector interconnection. The reflector must support standard ICMP timestamp packets. If the reflector does not support ICMP timestamp packets, the reflector cannot be interconnected. Additionally, when replying with an ICMP timestamp response packet, the reflector must include the request packet's private extended load information in the response packet. If the reflector allows load information to be carried, the hardware-based packet sending process is used and the delay is more accurate. If the reflector does not allow load information to be carried, the software-based packet sending process is used. If the reflector does not meet the requirements, the measurement related to NQA ICMP jitter's hardware-based packet sending fails. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The MTU of the tested link cannot be less than 64. Configure the MTU of the tested link properly. Otherwise, Jitter measurement results are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The RFC 2544 initiator's inward measurement supports flexible access sub-interfaces. If different sub-interfaces of an interface are configured with the same VLAN, only one sub-interface can be measured. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the RFC 2544 initiator is bound to a flexible access sub-interface to initiate a measurement, configuring static ARP entry learning for the source and destination IP addresses causes the RFC 2544 measurement path to fail to be learned. Configure dynamic ARP entry learning for the source and destination IP addresses when the RFC 2544 initiator is bound to a flexible access sub-interface to initiate a measurement. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the server end supports hardware-based packet reply, the board that replies packets must support 1588v2 clock synchronization. Otherwise, hardware-based packet sending measurement results obtained during a jitter test are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
One-way delay measurement requires the deployment of 1588v2 clock synchronization. Otherwise, hardware-based packet sending measurement results obtained during a jitter test are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a cross-domain or private L3VPN detection scenario where a P node does not have any return route but supports MPLS forwarding, when the tracert ipv4 command is run to test an MPLS tunnel, the display of cross-domain P node information depends on whether the associated board supports tracert fast reply. Information about cross-domain P nodes fails to be displayed if the associated board does not support tracert fast reply. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The server and client of an ICMP jitter, UDP jitter, or TCP test instance must be VRP-based devices. The test result depends on the board hardware capability. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Ping function for BASE user access in CU separation scenarios: 1. If the NE functions as the initiator, a ping operation can be initiated on the CP only. An error is reported if the UP initiates a ping test. 2. If the NE functions as the response end, only fast reply scenarios are supported. In this case, you must enable the fast reply function on the VNE by running the icmp-reply fast command. If the response end does not support fast reply, request packets will be discarded. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When testing VPLS or VLL PWs with tunnel overlapping, L2VPN PW ping/tracert can test only the outer backup plane. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
L2VPN PW ping/tracert can test a PW with only one segment, not a PW with multiple segments. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the tracert lsp command is run to test an LSP , cross-domain P nodes are not supported. After the tracert lsp command is run, "timeout" is displayed for cross-domain P nodes. The tracert test skips cross-domain P nodes. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1. Y.1564 supports only unicast detection and does not support broadcast detection. 2. Y.1564 does not support flexible access of EVC sub-interfaces. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In EVPN/L3VPN over SRv6 TE Policy scenarios, when the uniform mode is configured for L3VPNs, the PE tracert PE operation is performed, and information about transit nodes is not displayed. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
For the ping/tracert ipv6-sid function, if the End.OP SID outbound interface does not have a global IPv6 address, the source IP address contained in the detection packets sent by the local device may be an unreachable IPv6 address. This causes a detection failure, but traffic forwarding is not affected. Initiate detection with the -a parameter specified. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In the ping and trace functions, IPv6 SIDs support only unicast addresses. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1. A third-party responder does not send response packets carrying the payload that contains Huawei proprietary extended information. In this scenario, the ICMP jitter single-ended detection function is used. The delay and jitter, however, are large in inter-board scenarios. 2. A third-party responder does not support ICMP timestamp packets (standard non-private packets). ICMP timestamp packets are parsed as ICMP echo packets. In this scenario, ICMP jitter single-ended detection supports only two-way frame delay measurement but does not support one-way frame delay measurement. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an EVPNv4/v6+SRv6 BE/SR TE Policy scenario, when the uniform mode is specified for E2E tracert, the IP address of the P node on the public network can be displayed, but the following rule is followed: When the TTL in the SRv6 header on the P device expires, an IPv4 address is selected as the source IP address of the ICMP error packet. The P device must have an IPv4 address. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In ingress-specific partial protection scenarios, the ping/trace operation cannot be performed for an SRv6 TE Policy during an FRR switchover. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
For the ping/tracert segment-routing function delivered by the network management MIB, the source IP address contained in the detection packets sent by the local device may be an unreachable IPv4 address. This causes a detection failure, but traffic forwarding is not affected. Initiate detection by specifying the source address, such as the lsr-id address. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In EVPN VPLS MAC ping and EVPN VPWS ping/tracert inter-AS active-active scenarios, only interconnection between Huawei devices is supported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1. IPv6 addresses can only be set to global addresses but not link-local addresses. 2. The ICMP jitter IPv6 instance supports echo packets and does not support timestamp packets. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1, BIERv6 tracert allows return traffic to be transmitted through routes only, not through tunnels. 2, In load balancing scenarios, only one path can be detected. 3, A correct BSL must be specified. Otherwise, the tracert operation may fail. 4, BIERv6 tracert does not support packet fragmentation. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1, BIERv6 ping supports only return routes, but does not support return tunnels. 2, In load balancing scenarios, only one of the routes can be overwritten. 3, The specified target BFR IDs must be in the same set. 4, Specify a correct BSL. Otherwise, the ping operation may fail. 5, BIERv6 ping does not support fragments. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |