Feature Requirements |
Series |
Models |
|---|---|---|
ESQM does not support flow identification based on VPN and inbound/outbound interface information. A device regards the flows with the same quintuple information (source and destination IP addresses, source and destination port numbers, and protocol number) and monitoring direction (inbound or outbound) as one flow for statistics collection, even if the inbound/outbound interfaces and VPNs of the flows are different. Please prevent this scenario during service planning. Otherwise, the statistics about the flows in this scenario are combined. As a result, the monitoring results are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F1A |
ESQM flow entries share resources with MAC address entries. If the number of MAC address entries created reaches the upper limit of the resources, ESQM flow entries cannot be created. If the number of ESQM flow entries created reaches the upper limit of the resources, the maximum number of MAC address entries cannot be created. Please prevent this scenario during service planning. Otherwise, if both ESQM and MAC address services are deployed, the maximum numbers of ESQM flow entries and MAC address entries cannot be reached at the same time. If the MAC table usage exceeds the configured alarm threshold, an alarm is generated. The default alarm threshold is 90%. |
NetEngine 8000 F |
NetEngine 8000 F1A |
ESQM is mutually exclusive with the NetStream, sFlow, flow recognition or ACL log function and cannot be configured at the same time. |
NetEngine 8000 F |
NetEngine 8000 F1A |
ESQM collects statistics about the traffic forwarded by a device instead of the traffic discarded by the device or the local traffic. |
NetEngine 8000 F |
NetEngine 8000 F1A |
ESQM uses a hash algorithm to create a flow table. However, the hash results are uneven. As a result, the maximum number of ESQM flow entries cannot be created. In certain scenarios, if the hash results for the quintuple information of packets are severely uneven, the maximum number of ESQM flow entries may not be created. |
NetEngine 8000 F |
NetEngine 8000 F1A |
ESQM can monitor packets on Ethernet interfaces and sub-interfaces, Eth-Trunk interfaces and sub-interfaces, L3VE sub-interfaces, QinQ and dot1q VLAN tag termination sub-interfaces. ESQM is not supported in heterogeneous media scenarios. |
NetEngine 8000 F |
NetEngine 8000 F1A |
ESQM is not supported in a NAT scenario. Please prevent this scenario during service planning. Otherwise, the collected information is inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F1A |
ESQM is not supported in a P2MP TE, or NG MVPN scenario. Please prevent this scenario during service planning. Otherwise, the collected information is inaccurate in this scenario. |
NetEngine 8000 F |
NetEngine 8000 F1A |
The transit node does not support ESQM. The collected information is inaccurate in this scenario. |
NetEngine 8000 F |
NetEngine 8000 F1A |
ESQM cannot monitor fragmented packets. Please prevent this scenario during service planning. Otherwise, statistics about fragmented packets are not collected. As a result, the collected traffic is different from the actual one. |
NetEngine 8000 F |
NetEngine 8000 F1A |
ESQM can monitor only native IPv4 and IPv4 in MPLS packets. The traffic restoration information is inaccurate for the other packets and you should prevent this scenario during service planning.. |
NetEngine 8000 F |
NetEngine 8000 F1A |
When a path switchover occurs, the reported TTL value may be different from the actual TTL value. The TTL value of a TCP/SCTP packet is obtained when the first packet is used to create a flow. The TTL value is related to the number of nodes on the path. After the path is switched, the new TTL value of the node may be different from the TTL value obtained when the first packet is used to create a flow. Before the flow table ages out, only subsequent packets (not containing TTL information) are sent to the controller, and the TTL value cannot be updated. Therefore, only the TTL value during flow table creation can be sent to the controller when the flow table ages out. |
NetEngine 8000 F |
NetEngine 8000 F1A |
ESQM is not supported in a multi-VS scenario. Prevent this scenario during service planning. |
NetEngine 8000 F |
NetEngine 8000 F1A |
When ESQM is configured on a sub-interface, main interface information, not sub-interface can be restored in flow restoration in the same direction as the ESQM direction. Both routed main interface sub-interface information, however, can be restored in flow restoration in the opposite direction of the ESQM direction. When NCE displays path information, sub-interface information on paths cannot be displayed. |
NetEngine 8000 F |
NetEngine 8000 F1A |
When traffic of the same flow is sent and received by different interfaces on the same node, ESQM traffic statistics are doubled. You can onfigure the ESQM function on the source and destination nodes to avoid this scenario. |
NetEngine 8000 F |
NetEngine 8000 F1A |