Licensing Requirements and Limitations for IP FPM
Restrictions and Guidelines
Restrictions |
Guidelines |
Impact |
---|---|---|
IP FPM one-way delay measurement requires the deployment of 1588v2 clock synchronization. IP FPM two-way delay measurement and packet loss measurement require the deployment of NTP or 1588v2 clock synchronization. |
To measure one-way delay, deploy 1588v2 clock synchronization. To measure two-way delay and packet loss, deploy NTP or 1588v2 clock synchronization. |
IP FPM measurement results are not available. |
For the same VPN or in a native IP scenario, the flow characteristics (including the source IP address, destination IP address, source port, destination port, protocol number, and DSCP) of different measurement instances under the same DCP cannot conflict. For example, the characteristics of one measurement instance cannot include or overlap the characteristics of another. If the characteristics conflict, the measurement result is inaccurate. |
Plan the flow granularity for measurement instances, and ensure that the characteristics of one measurement instance do not include or overlap the characteristics of another. |
Packet loss statistics are inaccurate, and no delay measurement result is available. |
In the case of 1588v2 clock synchronization, the 1588v2 clock source cannot obtain the locking status of the 1588v2 clock. Therefore, the 1588v2 clock source cannot function as a DCP. If the 1588v2 clock source functions as a DCP in this situation, a statistics collection abnormality occurs. |
Do not use the 1588v2 clock source as a DCP. |
IP FPM measurement results are not available. |
In an L2VPN scenario, private packets whose Layer 2 headers are not Ethernet headers are not supported. |
None |
In an L2VPN scenario, statistics about private packets whose Layer 2 headers are not Ethernet headers cannot be collected. |
IP FPM does not support GRE tunnels. |
None |
IP FPM measurement results are inaccurate when GRE tunnels are deployed. |
IP FPM multi-path detection: In load balancing mode, the hwIpfpmDcpInstTlpIndexTable and hwIpfpmDcpInstTlpNHIndexTable MIB tables are used to deliver configurations. In non-load balancing mode, the hwIpfpmDcpInstTlpTable and hwIpfpmDcpInstTlpNHTable MIB tables are used to deliver configurations. |
Use the corresponding MIB tables properly. |
Configuration delivery may fail. |
IP FPM requires a license. Some configurations cannot be deleted when the device does not have a license or the license trial use is not enabled. The configurations can be deleted after a license file is loaded. |
IP FPM requires a license. Some configurations cannot be deleted when the device does not have a license or the license trial use is not enabled. The configurations can be deleted after a license file is loaded. |
None |