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

Reminder

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

upgrade

Configuration Guide - Network Management and Monitoring

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, LLDP, NQA, Service Diagnosis, Mirroring, Packet Capture, sFlow, 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 DCP

Configuring the DCP

Context

DCP is the executor in the IP FPM system. The DCP manages and controls TLPs, aggregates performance statistics, and sends statistics to the MCP.

NOTE:

The measurement instance parameters of a DCP configured in this task, for example, UDP port number, authentication mode, and authentication password, must be the same as the parameters of the same measurement instance on the MCP; otherwise, the DCPs cannot send statistics data to the MCP.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run nqa ipfpm dcp

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

  3. Run dcp id dcp-id

    The DCP ID is set.

    By default, a DCP does not have an ID. A DCP has a unique ID on the network. It is recommended that you configure the router ID of the device as the DCP ID.

    The DCP ID set in this step must be the same as the DCP ID specified in the measurement instance on the MCP. Otherwise, the MCP cannot receive statistics from DCPs.

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

    The authentication mode and password are configured on the DCP.

    By default, no authentication mode or password is configured on a DCP.

    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.

  5. (Optional) Run color-flag loss-measure { tos-bit tos-bit | flags-bit0 } delay-measure { tos-bit tos-bit | flags-bit0 | none }

    The color bit for IP FPM performance measurement is set.

    By default, the 6th and 7th color bits in the ToS field of an IP packet are used for packet loss measurement and delay measurement respectively. The default configuration is recommended.

    NOTE:

    All devices on a network must use the same color bit setting.

    Packet loss measurement and delay measurement cannot use the same color bit. Before you specify a color bit, ensure that this bit is not occupied by other services.

    RFC2474 defines the ToS field in the IPv4 packet header as the Differentiated Service (DS) field. In the DS field, the leftmost 6 bits (bits 0-5) are the DS Code Point (DSCP). When the DS field is used to provide differentiated service, it is not recommended that you configure bits 3-5 as color bits because the measurement result may be inaccurate.

  6. Run mcp mcp-id [ port port-number ] [ vpn-instance vpn-instance-name | net-manager-vpn ]

    The MCP ID is set for all measurement instances on the specified DCP, and the UDP port number used for communication between the DCP and MCP is configured.

    By default, no MCP ID is associated with the measurement instances on the DCP, and the DCP and MCP communicate with each other through UDP port 65030.

    If you want the DCP to send statistics to the MCP through the specified or management VPN, ensure that the VPN instance has been created on the DCP before specifying the vpn-instance vpn-instance-name or net-manager-vpn in the command.

  7. (Optional) Run period source ntp

    The DCP is configured to select NTP as the clock source when calculating an IP FPM statistical period ID.

    By default, a DCP selects the clock source with higher precision than NTP as the clock source when calculating an IP FPM statistical period ID.

    If the ingress of a service flow uses NTP as the clock source, but the egress uses a different clock source, for example, 1588v2, you must configure the egress to select NTP as the clock source when calculating an IP FPM statistical period ID to ensure consistent clock sources on the ingress and egress.

  8. Configure measurement instances on the DCP.

    The DCP collects statistics based on measurement instances. Each measurement instance consists of the target flow, TLP, and measurement interval. To measure packet loss for a specified service flow, create a measurement instance.

    1. Run instance instance-id

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

      By default, no measurement instance exists on a DCP.

      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 DCP and the MCP that it belongs to. 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.

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

      The authentication mode and password are configured on the DCP.

      By default, no authentication mode or password is configured for a measurement instance.

      If no authentication mode or password is configured for a measurement instance, the authentication mode and password configured in the IPFPM-DCP view are used for this instance. If the authentication mode and password are configured for a measurement instance, the configuration in this step is used.

    4. (Optional) Run interval interval

      The measurement interval is set for the measurement instance.

      By default, the measurement interval is 10 seconds.

      NOTE:

      After packet loss measurement takes effect, to change the measurement interval, disable packet loss measurement in the instance view.

      Do not change the measurement interval when the measurement instance is running. Otherwise, the statistics on MCP may be inaccurate. Before changing the measurement interval, run the measure disable command in the IPFPM-MCP instance view to disable the measurement function. After the interval is changed, run the undo measure disable or measure enable command to enable the measurement function again.

    5. Define a target flow in the measurement instance.

      A target flow is the objective in IP FPM measurement, and can be defined by any combinations of source IP address, destination IP address, protocol type, DSCP value, source port number, and destination port number. Specifying more attributes can make the target flow accurate. Therefore, it is recommended that you specify more attributes to improve precision of measurement results.

      A target flow has the direction feature. If the target flow in an instance is unidirectional, either forward or backward can be specified. If a service flow is bidirectional (the source and destination addresses of forward and backward flows mirror to each other), only a bidirectional symmetrical flow needs to be configured. The system then automatically generates two unidirectional flows. If the source and destination addresses are not mirrored, two unidirectional flows need to be configured.

      A measurement instance can contain only one unidirectional flow or bidirectional flow (two unidirectional flows logically). One target flow can only be defined for one measurement instance. The forward and backward flows in one measurement instance cannot be identical.

      • Run the flow { forward | backward } { dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] | protocol { { tcp | udp } { source-port src-port-number1 [ to src-port-number2 ] | destination-port dest-port-number1 [ to dest-port-number2 ] } * | { protocol-number } } | vxlan [ vni vni-id ] } *command to define a unidirectional flow.

      • Run the flow bidirectional { dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] | protocol { { tcp | udp } { source-port src-port-number1 [ to src-port-number2 ] | destination-port dest-port-number1 [ to dest-port-number2 ] } * | { protocol-number } } | vxlan [ vni vni-id ] } * command to define a bidirectional symmetrical flow.

      NOTE:
      • To measure performance of the VXLAN, specify the vni vni-id parameter.
      • The protocol and vxlan parameters cannot both be configured.
      • If the target flow entering a DCP has been fragmented, the device counts only the first fragment. Therefore, if a transit device on the network has fragmented the target flow, the measurement result may be inaccurate.

      • To define a bidirectional symmetrical flow, specify both source address (src-ip-address) and destination address (dest-ip-address).

    6. Configure TLPs and roles.

      • Run the tlp tlp-id { in-point | out-point } { ingress | egress } command to configure the ingress and egress TLPs of the measurement instance and their roles.

      • Run the tlp tlp-id mid-point flow { forward | backward | bidirectional } { ingress | egress } command to configure the middle point in the measurement instance and its role.

        NOTE:

        The direction of TLP must be the same as the direction of the target flow; otherwise, the function does not take effect.

      TLPs are the measurement points in the measurement instance. They collect data and generate statistics. By default, no TLP is configured.

  9. Run commit

    The configuration is committed.

  10. Run quit

    Return to the IPFPM-DCP view.

  11. Run quit

    Return to the system view.

  12. Bind interfaces to TLPs.

    1. Run interface interface-type interface-number

      The view of the interface to be bound to a TLP is displayed.

      On a switch, the GE/10GE/40GE/100GE interfaces and Eth-Trunk can be bound to TLPs.

    2. Run ipfpm tlp tlp-id

      The interface is bound to a TLP.

      By default, an interface is not bound to a TLP.

      NOTE:

      In the management region of an MCP, a TLP can only be bound to one interface.

  13. Run quit

    Return to the system view.

  14. Enable IP FPM hop-by-hop performance measurement:
    1. Run nqa ipfpm dcp

      The IPFPM-DCP view is displayed.

    2. Run instance instance-id

      The IPFPM-DCP instance view is displayed.

    3. Run loss-measure enable mid-point [ time-range time-range | continual ]

      Hop-by-hop packet loss measurement is enabled.

      By default, packet loss measurement is disabled on the middle point of a measurement instance.

    4. Enable delay measurement.

      If the target flow is a unidirectional flow:
      • Run the delay-measure enable one-way tlp mid-point [ time-range time-range | continual ] command to enable hop-by-hop delay measurement.

        By default, delay measurement is disabled on the middle point of a measurement instance.

        To enable continual hop-by-hop delay measurement, specify the continual parameter.

      If the target flow is a bidirectional flow, select one of the following methods:
      • Run the delay-measure enable two-way tlp mid-point [ time-range time-range ] command to enable on-demand directional delay measurement.

        By default, on-demand bidirectional delay measurement is disabled for a measurement instance.

      • Run the delay-measure enable two-way tlp mid-point continual command to enable continual bidirectional delay measurement.

        By default, continual bidirectional delay measurement is disabled for a measurement instance.

  15. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075344

Views: 28422

Downloads: 29

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