No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Configuration Guide - Network Management and Monitoring

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, NETCONF, OpenFlow, LLDP, NQA, Mirroring, Packet Capture, Packet Trace, Path and Connectivity Detection Configuration, NetStream, sFlow, and iPCA.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring the MCP

Configuring the MCP


The MCP is the controller in the IP FPM system. It collects, summarizes, and calculates statistics data, and sends measurement results to user terminals or NMS. Generally, the MCP is a dedicated device in the network management center or a high-performance switch.


The MCP parameters configured in this task, for example, UDP port number, authentication mode, and authentication password, must be the same as the parameters set on the DCPs involved in measurement instances on MCP. Otherwise, the statistics cannot be reported to the MCP.


  1. Run system-view

    The system view is displayed.

  2. Run nqa ipfpm mcp

    The MCP function is enabled globally and the IPFPM-MCP view is displayed.

  3. Run mcp id mcp-id

    The MCP ID is set.

    By default, an MCP has no ID. It is recommended that you configure the router ID of the device as the MCP ID.

    The MCP ID must be an IP address that DCPs can reach. If you have changed the MCP ID, you must change the MCP IDs specified in the measurement instances associated with the DCPs; otherwise, the DCPs cannot report the statistics data received from TLPs to the MCP.

  4. (Optional) Run protocol udp port port-number

    The UDP port number is configured on the MCP. The MCP and DCPs communicate with each other using this UDP port.

    By default, the UDP port used between DCPs and MCP is port 65030. The default port is recommended.

  5. (Optional) Run authentication-mode hmac-sha256 key-id key-id [ cipher ] password

    The authentication mode and password are configured on the MCP.

    By default, no authentication mode or password is configured on the MCP.

    The authentication modes and passwords on the MCP and DCPs must be the same so that the MCP receives the packets only from authenticated DCPs. This improves statistics data security and reliability.

  6. Configure measurement instances on the MCP.

    The MCP reports measurement results based on measurement instances. The MCP summarizes and analyzes statistics data of the same measurement instance on all DCPs, and reports measurement results of target flows. After the configuration is complete, you can view performance measurement results on the MCP based on measurement instances.

    1. Run instance instance-id

      A measurement instance is created and the IPFPM-MCP instance view is displayed.

      By default, no measurement instance exists on an MCP.

      In the IP FPM system, a measurement instance must have a unique ID in the management region of the MCP. A measurement instance must be configured on the MCP and all of its associated DCPs. Otherwise, performance measurement does not take effect.

    2. (Optional) Run description text

      The description is configured for the measurement instance.

      By default, a measurement instance does not have a description, and the instance is identified by an ID in integer format. The description helps you understand the service monitored by the measurement instance and avoids misuse on the measurement instance. For example, if a measurement instance is configured to measure network performance in the traffic from headquarters to branch 1, the description of the instance can be set to HeaderToBranch1.

    3. Run dcp dcp-id

      The DCP ID included in the measurement instance is set.

      By default, a measurement instance on MCP does not contain DCP.

    4. Configure the Atomic Closed Hop (ACH).

      1. Run the ach ach-id command to create an ACH and enter the ACH view.
      2. Run the flow { forward | backward | bidirectional } command to configure the direction of the target flow on which the hop-by-hop measurement is deployed.
      3. Run the in-group dcp dcp-id tlp tlp-id command to configure the ingress measurement point group for the target flow.
      4. Run the out-group dcp dcp-id tlp tlp-id command to configure the egress measurement point group for the target flow.

  7. Run commit

    The configuration is committed.

Follow-up Procedure

If the IP FPM settings on a DCP are modified, the MCP will receive incorrect data during setting modification. To address this problem, you can run the measure disable command to disable the performance measurement function in a measurement instance temporarily. When the setting modification on the DCP is complete, run the undo measure disable or measure enable command to enable the performance measurement function for the measurement instance again. This makes the statistics accurate.

Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 33680

Downloads: 121

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next