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

CLI-based Configuration Guide - Network Management and Monitoring

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R009

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

DCPs are the executors in the IP FPM system. They control and manage TLPs, collect performance statistics, and report the statistics to the MCP.

Context

Figure 4-10 shows a typical networking for IP FPM end-to-end performance measurement. The target flow enters the transit network through RouterA, travels through RouterB, and leaves the transit network through RouterC. To monitor the transit network performance in real time or check whether a fault occurs on the transit network, configure IP FPM end-to-end performance measurement on RouterA and RouterC.
Figure 4-10  Networking diagram for IP FPM end-to-end performance measurement

In Figure 4-10, RouterA and RouterC are configured as DCPs to control and manage TLP100 and TLP310 respectively, collect performance statistics, and report the statistics to the MCP.

Perform the following operations on RouterA and RouterC to configure them as DCPs.

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

    A DCP ID is configured.

    By default, a DCP has no ID. It is recommended that you use the Router ID of the device as the DCP ID.

    The DCP ID must be the same as that specified in the IP FPM instance of the MCP using the dcp dcp-id command. Otherwise, the MCP cannot receive statistics reported by the DCP.

  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 mode and password configured on a DCP must be the same as those configured on the MCP to which the DCP belongs using the authentication-mode hmac-sha256 key-id key-id [ cipher ] password command. Otherwise, the MCP cannot receive statistics reported by the DCP.

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

    The IP FPM color bit is configured.

    By default, the color bit for IP FPM packet loss measurement is bit 6 in the type of service (ToS) field of the IP packet header, the color bit for IP FPM delay measurement is bit 7 in the ToS field of the IP packet header, The default settings are recommended.

    When deploying IP FPM, ensure that packet loss and delay measurement use different color bits, and the color bits for packet loss and delay measurement have not been used in other measurement tasks.

    In MPLS scenario, the ToS field of the IP packet header cannot be used as the IP FPM color bit. You can use bit 0 in the Flags field of the IP packet header as the IP FPM color bit.

    NOTE:

    Currently, IP FPM can detect traffic on both the LAN side and WAN side. However, IP FPM color bit is a global configuration in the IPFPM-DCP view and detection of the traffic on both sides cannot be configured manually.

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

    The MCP ID for all IP FPM instances on the DCP is specified.

    The UDP port number specified on the DCP must be the same as that specified on the MCP using the protocol udp port port-number command. Otherwise, the DCP cannot report statistics collected from TLPs to the MCP.

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

  7. Run instance instance-id

    An IP FPM instance is created, and the instance view is displayed.

    In the IP FPM system, the IP FPM instance ID specified by the instance-id parameter must be unique in the management domain of the MCP to which the instance belongs. You must configure the same IP FPM instance on DCPs and the MCP to which the DCPs belong. Otherwise, IP FPM end-to-end performance measurement does not take effect.

  8. (Optional) Run mcp mcp-id [ port port-number ] [ vpn-instance vpn-instance-name | net-manager-vpn ]

    The MCP ID for all IP FPM instances on the DCP is specified.

    The UDP port number specified on the DCP must be the same as that specified on the MCP using the protocol udp port port-number command. Otherwise, the DCP cannot report statistics collected from TLPs to the MCP.

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

  9. (Optional) Run description text

    A description is configured for the IP FPM instance.

    By default, no description is configured for an IP FPM instance, and an IP FPM instance can be identified only by an ID in integer format.

    The description of an IP FPM instance helps you understand services and functions monitored by the instance and avoid misuses of the instance.

  10. (Optional) Run interval { 10 | 60 | 600 }

    The measurement interval of the IP FPM instance is configured.

    By default, the measurement interval of an IP FPM instance is 10s.

    NOTE:

    To ensure statistics accuracy, it is recommended that you disable packet loss or delay measurement in the IP FPM instance view before modifying the measurement interval of the instance, and enable the measurement function after the modification.

  11. Configure the target flow features in the IP FPM instance. Choose either of the following methods based on the target flow type.

    Configure forward or backward target flow features.
    • When protocol is specified as TCP or UDP, the command for configuring the forward target flow features is as follows:

      flow forward { protocol { tcp | udp } { source-port src-port-number1 [ to src-port-number2 ] | destination-port dest-port-number1 [ to dest-port-number2 ] } * | dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] } *

    • When protocol is specified as TCP or UDP, the command for configuring the backward target flow features is as follows:

      flow backward { protocol { tcp | udp } { source-port src-port-number1 [ to src-port-number2 ] | destination-port dest-port-number1 [ to dest-port-number2 ] } * | dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] } *

    • When protocol is specified as any protocol other than TCP or UDP, the command for configuring the forward target flow features is as follows:

      flow forward { protocol protocol-number | dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] } *

    • When protocol is specified as any protocol other than TCP or UDP, the command for configuring the backward target flow features is as follows:

      flow backward { protocol protocol-number | dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] } *

    Configure the symmetrical bidirectional target flow features.
    • When protocol is specified as TCP or UDP, the command for configuring the target flow features is as follows:

      flow bidirectional { protocol { tcp | udp } { source-port src-port-number1 [ to src-port-number2 ] | destination-port dest-port-number1 [ to dest-port-number2 ] } * | dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] } *

      NOTE:

      Currently, the IP FPM system supports port range matching. If you do not specify the IP address for a packet, ensure that the source port number and destination port number of the packet do not match the port range simultaneously. Otherwise, the port range is incorrectly matched and the statistics fail to be collected.

    • When protocol is specified as any protocol other than TCP or UDP, the command for configuring the target flow features is as follows:

      flow bidirectional { protocol protocol-number | dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] } *

    To configure the application matching information of the target flow, use the following command:

    flow application application-name

    NOTE:
    • When configuring the bidirectional target flow in the IP FPM instance, pay attention to the following points:
      • If the bidirectional target flow is asymmetrical, you need to specify the forward and backward parameters to configure forward and backward target flow features.
      • If the bidirectional target flow is symmetrical, you only need to specify the bidirectional parameter to configure one bidirectional flow. By default, the forward flow features are used as features of this bidirectional flow, and the backward flow features mirror to the forward flow features. Note that if the specified target flow is a symmetrical bidirectional flow, you must configure both the src-ip-address and dest-ip-address parameters to specify the source and destination IP addresses of the target flow.
    • To make the application protocol of the target flow configured for a specified application in an IP FPM instance take effect, you need to specify bidirectional, forward, or backward to configure any flow characteristic of bidirectional target flow, forward target flow, and backward target flow. In addition, you need to run the sa application-statistic enable command on the interface to enable SAC before using the IP FPM function.

  12. Run tlp tlp-id { in-point ingress | out-point egress }

    TLPs of the IP FPM instance and their roles are configured.

    TLPs are the measurement points along the target flow in the IP FPM instance. They compile and generate statistics. TLPs in the IP FPM instances are classified into In-Point-TLPs (in-point indicates an In-Point-TLP on which the system adds the color bit to a target flow) and Out-Point-TLPs (out-point indicates an Out-Point-TLP on which the system removes the color bit from a target flow.) In Figure 4-10, TLP100 and TLP310 on the network are the In-Point-TLP and Out-Point-TLP, respectively.

    NOTE:
    If you want to exclude RouterA and RouterC when measuring the transit network performance, configure the downlink port on RouterA as an In-Point-TLP on which the system adds the color bit to a target flow, and configure the uplink port on RouterC as an Out-Point-TLP on which the system removes the color bit from a target flow.

  13. Run quit

    Return to the IPFPM-DCP view.

  14. Run quit

    Return to the system view.

  15. Bind an interface to a TLP.

    1. Run interface interface-type interface-name

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

    2. Run ipfpm tlp tlp-id

      A Layer 3 interface on the device is bound to a TLP.

  16. Enable IP FPM end-to-end performance measurement.

    1. Run system-view

      The system view is displayed.

    2. Run nqa ipfpm dcp

      The IPFPM-DCP view is displayed.

    3. Run instance instance-id

      The IP FPM instance view is displayed.

    4. Enable packet loss measurement. Choose either of the following commands based on actual requirements:
      • Run loss-measure enable time-range { 5 | 10 | 15 | 30 }

        On-demand packet loss measurement is enabled.

        By default, the interval for on-demand packet loss measurement is 10 minutes.

      • Run loss-measure enable continual

        Continuous packet loss measurement is enabled.

    5. Enable delay measurement.

      If the target flow is bidirectional, choose either of the following commands based on actual requirements:
      • Run delay-measure enable two-way tlp tlp-id1 [ tlp-id2 ] [ time-range { 5 | 10 | 15 | 30 } ]

        On-demand two-way delay measurement is enabled.

        By default, the interval for on-demand packet loss measurement is 10 minutes.

      • Run delay-measure enable two-way tlp tlp-id1 [ tlp-id2 ] continual

        Continuous two-way delay measurement is enabled.

      NOTE:

      After the DCP configuration changes, you need to run the undo loss-measure enable command to disable packet loss measurement for an IP FPM instance, and then run the loss-measure enable command to enable packet loss measurement for an IP FPM instance on the DCP. Otherwise, the statistics may fail to be collected.

      By default, packet loss measurement is disabled for an IP FPM instance.

      You are advised to enable packet loss measurement on the DCP and then enable measurement on the MCP.

      Note that data may be inaccurate in the first two periods after measurement is enabled. As a result, the statistical result is unreliable.

Translation
Download
Updated: 2019-05-17

Document ID: EDOC1000174072

Views: 100658

Downloads: 332

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