In this user interface, you can query information about IP flow performance management (IP FPM) instances. Based on the Data Collecting Point (DCP) instance ID in alarm details, you can analyze the faulty IP flow in the IP FPM Instance window.
In the NE Explorer, choose from the navigation tree.
Parameter |
Value |
Description |
|---|---|---|
DCP Instance ID |
Example: 1 |
Indicates the DCP instance ID. DCPs are responsible for collecting the measurement data generated by Target Logical Ports (TLPs) and sending the data to Measurement Control Points (MCPs) DCP instance IDs must be unique on NEs. |
DCP Instance Description |
Character string |
Indicates the description of the DCP instance. The description helps users distinguish DCP instances. |
MCP ID |
Example: 0.0.0.0 |
Indicates the MCP ID. MCPs are responsible for analyzing the data sent from DCPs and reporting the analysis results. Each IP FPM instance uses only one MCP, but each MCP may serve multiple IP FPM instances. IP routes must exist between the MCP and all DCPs. |
UDP Port |
Example: 65030 |
Indicates the UDP port ID. |
VRF Name |
Character string |
Indicates the VRP routing table entry. Each service has its own VRP routing table entry. |
TLP ID |
Example: 1 |
Indicates the TLP port. TLPs are observation points distributed at the network edge. They work with logical interfaces (Layer 2 or Layer 3 interfaces) of network devices to collect statistics and produce measurement data. Each IP FPM instance may use multiple TLPs, and each TLP may serve multiple IP FPM instances. |
Detection Point Type |
in-point, out-point |
Indicates the type of the detection point. |
Flow Type |
forward, backward |
Indicates the flow type. |
TLP Direction |
egress, ingress |
Indicates the direction of IP service flows. For incoming service flows, the value is ingress; for outgoing service flows, the value is egress. |
TLP Status |
Example: valid |
Specifies whether the TLP ID is valid. |