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

S1720, S2700, S5700, and S6720 V200R011C10

This document provides the configurations of network management and monitoring features supported by the product, including SNMP, RMON and RMON2, LLDP, Performance Management, iPCA, NQA, Service Diagnosis, Mirroring, Packet Capture, NetStream, sFlow, TWAMP Light, and NETCONF.

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 network-level packet loss measurement. 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. Perform the following operations on the MCP:

The MCP parameters configured in this task must be the same as the parameters set on the DCPs involved in measurement instances on MCP.


  1. Run the system-view command to enter the system view.
  2. Run the nqa ipfpm mcp command to enable the global MCP function and enter the IPFPM-MCP view.
  3. Run the mcp id mcp-id command to set the MCP ID.

    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 the protocol udp port port-number command to configure the UDP port number on the MCP. The MCP and DCPs communicate with each other through this port.

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

  5. (Optional) Run the authentication-mode hmac-sha256 key-id key-id [ cipher ] password command to configure the authentication mode and password on the MCP.

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

    After the authentication mode and password are configured, 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 packet loss measurement results on the MCP based on measurement instances.

    1. Run the instance instance-id command to create a measurement instance and enter the IPFPM-MCP instance view.

      By default, no measurement instance exists on an MCP.

    2. Run the dcp dcp-id command to specify the DCP ID in the measurement instance.

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

    3. Run the following commands to configure Atomic Closed Hops (ACHs).

      An ACH identifies a range between two neighboring measurement points. The network shown in Figure 6-17 is classified into two ACHs: ACH1 {TLP100, TLP200}, and ACH2 {TLP200, TLP310}. In ACH1, TLP100 is the in-point, and TLP200 is the out-point. In ACH2, TLP200 is the in-point, and TLP310 is the out-point.

      1. Run the ach ach-id command to create an ACH and enter the ACH view.
      2. Run the flow { forward | backward } command to specify the direction in which hop-by-hop delay measurement is implemented for the target flow.
      3. Run the in-group dcp dcp-id tlp tlp-id command to configure the TLP in-group.

      4. Run the out-group dcp dcp-id tlp tlp-id command to configure the TLP out-group.

      5. Run the quit command to return to the IPFPM-MCP instance view.

    4. Run the loss-measure ratio-threshold upper-limit upper-limit lower-limit lower-limit command to configure the alarm and clear alarm thresholds of packet loss ratio.

      By default, the alarm and clear alarm thresholds of packet loss ratio are not configured. That is, no alarm is generated for packet loss.

      If the network administrator is unaware of packet loss on the network and does not adjust services on the network in a timely manner, the number of lost packets will continuously increase, causing user experience to degrade. To facilitate network operation and maintenance, configure the alarm thresholds on the MCP. When the packet loss ratio reaches the upper threshold, an alarm is generated; when the packet loss ratio falls below the lower threshold, a clear alarm is generated.

    5. (Optional) Run the description text command to configure the description of 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 packet loss in the traffic from headquarters to branch 1, the description of the instance can be set to HeaderToBranch1.

    6. (Optional) Run the measure disable command to disable the measurement function of an instance.

      By default, the measurement function of an instance is enabled.

      If the MCP receives error data during the DCP configuration update, you can run the measure disable command to disable the measurement function of an instance on the MCP. When the DCP configuration update is complete, run the undo measure disable or measure enable command to enable the measurement function of the instance again.

Updated: 2020-02-06

Document ID: EDOC1000178174

Views: 208972

Downloads: 827

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next