Feature Requirements |
Series |
Models |
|---|---|---|
IFIT does not support shortcut-or-EPE-based access to an SRv6 public network tunnel encapsulated in USD mode. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the function to collect statistics about out-of-order packets is disabled for an iFIT instance, some packets are out of order. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an HVPN E2E measurement scenario, when the UPE functions as the ingress and the encapsulation nexthop ip-address command is configured, you must specify the next hop IP address as the IP address of the SPE. When the encapsulation nexthop ip-address command is configured on the SPE, you must specify the next hop IP address as the IP address of the NPE. If the configuration is improper, iFIT measurement results are not available. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If a packet needs to be fragmented, iFIT measures only the first fragment, which may cause the number of bytes to be inaccurate. If packet loss occurs on the transit or egress slice, fault demarcation cannot be performed based on iFIT statistics. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT does not support multi-VS, and can be configured only in Admin-VS. The VSn does not support iFIT detection. Please properly plan services. Otherwise, iFIT measurement results are not available. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT does not support broadcast or multicast flow measurement. In multicast scenarios, multiple copies of traffic statistics are collected. As a result, statistics about extra packets are collected and are inaccurate. There are restrictions on the multicast and broadcast IP addresses, and the traffic detected by iFIT cannot be broadcast or replicated (for example, the traffic is carried over a P2MP tunnel). Please properly plan services. Otherwise, iFIT measurement results are not available. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT measurement cannot be used together with the flow label function. If both functions are configured, the flow label overwrites the iFIT label. As a result, the iFIT function fails on the entire detection link, and the ASG or egress node fails to remove the iFIT header, causing service interruption. Please prevent this scenario during service planning. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the configuration in an iFIT instance changes or the ingress node restarts, the ingress node reallocates flow IDs. As a result, the data in several periods may be inaccurate or no measurement data is obtained. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The iFIT measurement results are inaccurate during a master/slave interface board switchover. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If traffic is light or a large number of packets are lost, there may be no delay data in some iFIT periods. If congestion occurs for a long time, the iFIT measurement results are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Flow characteristics in different measurement instances cannot conflict. If flow characteristics conflict (for example, the characteristics of one measurement instance include or overlap those of another measurement instance), the iFIT measurement results may be inaccurate. Please prevent this scenario during service planning. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
During the iFIT measurement, if the forwarding path changes due to FRR or hard convergence, the measurement data in one or two periods after the switchover is inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT supports MPLS, SR-MPLS and SRv6 tunnel, does not support GRE or VXLAN tunnels. Please properly plan services. Otherwise, iFIT measurement results are not available. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT requires 1588v2, G.8275.1, or NTP for time synchronization, but does not support latency measurement when NTP is deployed. Please properly plan services. Otherwise, iFIT measurement results are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Assume that PE1 and ASBR1 belong to AS 100 and that PE2 and ASBR2 belong to AS 200. Inter-AS VPN iFIT is required between AS 100 and AS 200. The static next hop IP addresses are configured as follows: 1. In an inter-AS VPN Option A scenario, E2E measurement cannot be performed between PEs on different VPNs. 2. In an inter-AS VPN Option B scenario, when PE1 functions as the ingress and the encapsulation nexthop ip-address command is configured, you must specify the next hop IP address as the IP address of ASBR1. When the encapsulation nexthop ip-address command is configured on ASBR1, you must specify the next hop IP address as the IP address of ASBR2. When the encapsulation nexthop ip-address command is configured on ASBR2, you must specify the next hop IP address as the IP address of PE2. 3. In an inter-AS VPN Option C scenario, when PE1 functions as the ingress and the encapsulation nexthop ip-address command is configured, you must specify the next hop IP address as the IP address of PE2. If the configuration is improper, iFIT measurement results are not available. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Before configuring static capability negotiation, ensure that the egress PE can remove the iFIT extension header. Otherwise, traffic forwarding is affected. Please properly plan services. Otherwise, the egress node does not identify packets, which causes traffic interruption. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
On a board equipped with an eTM subcard, HQoS is implemented on the eTM subcard, and iFIT statistics are collected by the NP. If packet loss occurs on the eTM subcard, for example, in traffic congestion scenarios, iFIT statistics shown on NCE may indicate that packet loss occurs on links. iFIT statistics displayed on NCE may vary in scenarios where a TM or eTM subcard is installed. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When an SPE or ASBR is used as an ingress, VPNs cannot be distinguished. If there are duplicate flow characteristics in different VPNs, the measurement results are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
VPN+peer IP-based iFIT measurement is supported. In segmented VPN (HoVPN, H-VPN, and Option B) scenarios, you can specify the IP address of only the SPE or ASBR, not the IP address of the CE or PE, as the peer IP address. If multiple NPEs exist, you can specify the IP address of the SPE or ASBR as the peer IP address. In this case, the overall performance of all flows from the ingress to the NPEs is measured, but the flows are not differentiated. Please properly plan the service. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
VPN+peer locator-based iFIT measurement is supported. In segmented VPN (HoVPN and H-VPN) scenarios, you can specify only the SPE or ASBR, not the CE or PE, as the locator. If multiple NPEs exist, you can specify the SPE or ASBR as the locator. In this case, the overall performance of all flows from the ingress to the NPEs is measured, but the flows are not differentiated. Please properly plan the service. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
VPN+peer locator-based iFIT measurement is supported. In segmented VPN (HoVPN and H-VPN) scenarios, SPEs or ASBRs cannot function as the ingress for iFIT measurement. Please properly plan the service. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT configurations on devices running different versions is not compatible with each other. If iFIT is required on devices running a later version, you are advised to disable iFIT, upgrade all devices that require iFIT, and then enable iFIT on these devices again. Please properly plan the service, iFIT on a device running a later version is not compatible with iFIT on a device running an earlier version, causing packets not to be correctly parsed. As a result, iFIT statistics are inaccurate and traffic is interrupted. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
VPN+peer IP-based iFIT measurement is supported. In segmented VPN (HoVPN, H-VPN, and Option B) scenarios, SPEs or ASBRs cannot function as the ingress for iFIT measurement. Please properly plan the service. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In MPLS TE Group scenarios, iFIT supports only 5-tuple-based statistics collection or 5-tuple+DSCP-based statistics collection rather than VPN+peer-based statistics collection. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a device enabled with iFIT globally receives a large number of invalid iFIT packets, the generation of dynamic iFIT instances may be affected, but the iFIT instances that have been dynamically created are not affected. Please properly plan the service. Otherwise, dynamic iFIT instances are generated slowly or fail to be generated. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When portshaping process is on eTM or card and portshaping is enabled , iFIT will report the loss count before portshaping. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If Configure iFIT on SRv6 BE tunnel, flow load balance ways will change. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The sum of the forwarding delay and processing delay of iFIT packets varies on each node, causing the start time of iFIT statistics on the ingress to be different from that on subsequent devices. As a result, the first period of iFIT statistics on the egress may be the second period of iFIT statistics on the ingress, causing the third period of E2E iFIT statistics to be inaccurate. In the first two periods of each instance, ErrorInfo is reported to iMaster NCE for data filtering. The third period of the ingress, however, corresponds to the second period of the egress. Therefore, data collected during the third period is filtered out by iMaster NCE due to ErrorInfo reported by the egress. Please properly plan the service. Otherwise, data collected during the third period of E2E iFIT statistics collection is inaccurate and is filtered out by iMaster NCE. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When PSP is enabled in SRv6, if the device before PE is't HUAWEI device or HUAWEI device with no iFIT function or HUAWEI device with disabled iFIT function, PE node will not have iFIT statistics. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an HoVPN scenario, segment-by-segment iFIT is deployed from the UPE to the SPE and from the NPE to the SPE. A backward iFIT instance cannot be dynamically generated using an SPE node as the reflector. Please use a manually configured backward iFIT instance, or use an end-to-end iFIT instance between the UPE and NPE. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a PE and a CE are connected through physical interfaces, if the upstream and downstream AC interfaces of the traffic to be measured are inconsistent on the AC side, the backward iFIT instance generated cannot collect statistics on the backward traffic. If the PE and CE are connected through trunk interfaces and the upstream and downstream traffic is transmitted through different member interfaces, the same problem occurs. Please properly plan configurations. Otherwise, the iFIT instance statistics are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If a static iFIT instance on the reflector conflicts with a dynamic iFIT instance, the static iFIT instance takes precedence over the dynamic iFIT instance. A static iFIT instance takes precedence over a dynamic iFIT instance. After the static iFIT instance is deleted, the dynamic iFIT instance is restored. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the L2VPN network uses public MPLS tunnels in Option B or HVPN scenarios, iFIT does not support end-to-end measurement. iFIT is supported only from the PE to the ASBR or from the PE to the SPE. Please properly plan configurations. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an L2VPN accessing L3VPN scenario, iFIT does not support end-to-end measurement, and only supports L2VPN and L3VPN segment-by-segment measurement. Please properly plan configurations. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an L2VPN tunnel scenario, if an AC interface fails and the bypass tunnel takes effect, traffic is re-entered into the public network and forwarded to the backup PE. In this case, the iFIT egress is not configured on the AC interface, but is configured on the inbound interface of the bypass tunnel. Please properly plan configurations. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If service traffic is discarded or reported in the upstream direction, iFIT statistics may fail to be collected for L2VPN traffic. Please properly plan configurations. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When iFIT is overlaid with the entropy label, the hash key of the entropy label supports only the Layer 2 header. Please properly plan configurations. Otherwise, if traffic is load-balanced based on the entropy label, the load balancing capability is degraded. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT path restoration is supported only on VLAN-type dot1q sub-interfaces (packets can carry only one VLAN tag). Properly plan the configuration. Otherwise, iFIT path restoration for non-VLAN-type dot1q sub-interfaces is affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT sub-interface path restoration disallows the same iFIT measurement flow to enter different network slices. That is, only one sub-interface can be restored, and information about other sub-interfaces cannot be restored. Properly plan the configuration. Otherwise, iFIT sub-interface path restoration is affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT sub-interface path restoration supports only transit nodes (including the downstream node of the ingress and the upstream node of the egress), but not the upstream node of the ingress or the downstream node of the egress. Properly plan the configuration. Otherwise, iFIT sub-interface path restoration is affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT does not support RSVP-TE over GRE scenarios but can encapsulate iFIT headers. However, GRE tunnel segments do not support iFIT measurement and do not have hop-by-hop measurement data. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The maximum delay, minimum delay, and total delay reported by iFIT to NCE are the delay between the current measurement point and the ingress. The hop-by-hop maximum delay and minimum delay cannot be calculated. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an inter-AS iFIT Option A scenario where cloud and network PEs are co-deployed, if the Option A interface is a QinQ interface and the cloud PE functions as the iFIT ingress, the iFIT header cannot be encapsulated for detection. Therefore, properly plan the configuration. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
iFIT does not support SRv6 over GRE scenarios but can encapsulate iFIT headers. However, GRE tunnel segments do not support iFIT measurement and do not have hop-by-hop measurement data. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When iFIT automatic learning of bidirectional flows is enabled, if the IP address of the interface corresponding to the learned VPN that has traffic passing through is changed or a new IP address is added, the dumb element is generated. As a result, the instance corresponding to the traffic cannot be generated immediately. After the dumb element ages 10 minutes later, the instance is restored. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When deep load balancing is not enabled on the P, packets with iFIT headers cannot be properly balanced on the P. Properly plan configurations. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When deploying iFIT for a Layer 2 private line, ensure that the peer device specified by iFIT supports iFIT for the Layer 2 private line. Otherwise, the egress cannot remove the iFIT header, causing a service interruption. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The IFIT function is based on EVPL instances and peer IP addresses. Ensure that the device to which the peer IP address belongs has the IFIT header removal capability in Layer 2 scenarios. Otherwise, the egress cannot remove the IFIT header, causing service interruptions. After this instance is configured, the device considers that the device to which the peer IP address belongs has the iFIT capability. Therefore, you do not need to run the encapsulation nexthop command for all IFIT instances based on the peer IP address. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When IFIT supports global VE interfaces, delay measurement is not supported. As a result, the delay function and TTL message sending are affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
IFIT does not collect statistics about EOAM, Y.1731, or LPT packets. The packets are not encapsulated with the IFIT header, and therefore IFIT measurement is not performed. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When IFIT detects RFC 2544/Y.1564 return packets on the egress, that is, when the RFC 2544/Y.1564 transmit end receives packets, the IFIT egress instance cannot be generated. Statistics about RFC 2544/Y.1564 return packets collected by IFIT on the egress are affected, and no IFIT egress instance is generated. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
For the packets (including TWAMP, BFD, NQA, and other packets sent to the CPU) that are added with an IFIT header on the ingress but terminated on the egress, IFIT cannot collect statistics about the packets on the egress outbound interface. As a result, IFIT incorrectly considers that packet loss occurs. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When IFIT detects ping packets, ping packets are fast replied on the egress PE. The ping packets are not sent to the AC interface, but reflected back from the public network interface. Therefore, the IFIT-generated egress instance interface is a public network interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |