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 - System Monitor 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - System Monitor
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 NQA to Monitor an MPLS Network

Configuring NQA to Monitor an MPLS Network

NQA can be configured to monitor an MPLS network. Before configuring NQA to monitor an MPLS network, familiarize yourself with the usage scenario of each test instance and complete the pre-configuration tasks.

Usage Scenario

Table 4-2 NQA test instances used to monitor an MPLS network
Test Type Usage Scenario
LSP ping test A Label Switched Path (LSP) ping test monitors the end-to-end connectivity, packet loss ratio, and delay time on an MPLS network.
LSP trace test A Label Switched Path (LSP) trace test monitors the connectivity, packet loss ratio, and delay time hop by hop on an MPLS network and the forwarding path for MPLS packets.
LSP jitter test A Label Switched Path (LSP) jitter test monitors the end-to-end jitter time on an MPLS network.

Pre-configuration Tasks

Before configuring NQA to monitor an MPLS network, configuring basic MPLS functions.

Configuration Procedures

Perform one or more of the following configurations as required.

Configuring an LSP Ping Test

A Label Switched Path (LSP) ping test monitors the end-to-end connectivity, packet loss ratio, and delay time on an MPLS network.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to LSP ping.
    1. Run nqa test-instance admin-name test-name

      An NQA test instance is created, and the view of the test instance is displayed.

    2. Run test-type lspping

      The test instance type is set to LSP ping.

    3. (Optional) Run description description

      A description is configured for the NQA test instance.

  3. (Optional) Run fragment enable

    MPLS packet fragmentation is enabled for the NQA test instance.

  4. (Optional) Run lsp-type { ipv4 | te | bgp | srte }

    The LSP type is specified for the NQA test instance.

  5. Configure the destination address or tunnel interface based on the type of the checked LSP.

    • To configure the destination address for a checked LDP LSP, run the destination-address ipv4 ip-address lsp-masklen masklen [ lsp-loopback loopback-address ] command.

    • To configure the tunnel interface for a checked TE tunnel, run the lsp-tetunnel tunnel interface-number command.

    • To configure the destination address for a BGP tunnel, run the destination-address ipv4 ip-address lsp-masklen masklen [ lsp-loopback loopback-address ] command.

    • To configure the tunnel interface for an SR-TE tunnel, run the lsp-tetunnel tunnel interface-number command.

    • To configure the destination address for an SR-BE tunnel, run the destination-address ipv4 ip-address lsp-masklen masklen command.

  6. (Optional) Run lsp-nexthop

    An IP address is configured for the next hop when load balancing is enabled.

    When load balancing is enabled on an ingress node, run the lsp-nexthop command to configure an IP address for the next hop.

  7. Set parameters for the test instance to simulate packets.
    1. Run lsp-exp exp

      The LSP EXP value is set for the NQA test instance.

      The default LSP EXP value is 0.

    2. Run lsp-replymode { level-control-channel | no-reply | udp }

      The reply mode in the NQA LSP test instance is configured.

    3. Run datafill fillstring

      Padding characters in NQA test packets are configured.

    4. Run datasize size

      The size of the data field in an NQA test packet.

    5. Run probe-count number

      The number of probes in a test is set for the NQA test instance.

      By default, the number of probes is 3.

    6. Run interval seconds interval

      The interval at which NQA test packets are sent is set for the NQA test instance.

    7. Run source-address ipv4 ip-address

      The source IP address of NQA test packets is set.

    8. Run ttl number

      The TTL value in NQA test packets is set.

      By default, the TTL value is 30.

  8. (Optional) Configure test failure conditions.
    1. Run timeout time

      The response timeout period is set.

      If no response packets are received before the set period expires, the probe is regarded as a failure.

      By default, the timeout period is 3s.

    2. Run fail-percent percent

      The failure percentage is set for the NQA test instance.

      If the percentage of failed probes is equal to or greater than the failure percentage, the test is regarded as a failure.

      By default, the failure percent threshold is 100. A test is considered failed only after all probes fail.

  9. (Optional) Configure the NQA statistics function.

    Run records { history number | result number }

    The maximum number of history records and the maximum number of result records that can be saved for the NQA test instance are set.

  10. Schedule the test instance.
    1. (Optional) Run frequency interval

      The test period is set for the NQA test instance.

      By default, no interval is set. An NQA test instance is performed once.

    2. Run start

      An NQA test is started.

      The start command has multiple formats. Choose one of the following as needed.

      • To start an NQA test instance immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time, run the start at [ yyyy/mm/dd ] hh:mm:ss [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance after a specified delay, run the start delay { seconds second | hh:mm:ss } [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  11. Run commit

    The configuration is committed.

Configuring an LSP Trace Test

A Label Switched Path (LSP) trace test monitors the connectivity, packet loss ratio, and delay time hop by hop on an MPLS network and the forwarding path for MPLS packets.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to LSP trace.
    1. Run nqa test-instance admin-name test-name

      An NQA test instance is created, and the view of the test instance is displayed.

    2. Run test-type lsptrace

      The test instance type is set to LSP trace.

    3. (Optional) Run description description

      A description is configured for the NQA test instance.

  3. (Optional) Run fragment enable

    MPLS packet fragmentation is enabled for the NQA test instance.

  4. (Optional) Run lsp-type { ipv4 | te | bgp | srte }

    The LSP type is specified for the NQA test instance.

  5. Configure the destination address or tunnel interface based on the type of the checked LSP.

    • To configure the destination address for a checked LDP LSP, run the destination-address ipv4 ip-address lsp-masklen masklen [ lsp-loopback loopback-address ] command.

    • To configure the tunnel interface for a checked TE tunnel, run the lsp-tetunnel tunnel interface-number command.

    • To configure the destination address for a BGP tunnel, run the destination-address ipv4 ip-address lsp-masklen masklen [ lsp-loopback loopback-address ] command.

    • To configure the tunnel interface for an SR-TE tunnel, run the lsp-tetunnel tunnel interface-number command.

    • To configure the destination address for an SR-BE tunnel, run the destination-address ipv4 ip-address lsp-masklen masklen command.

  6. (Optional) Set parameters for the test instance to simulate packets.
    1. Run lsp-exp exp

      The LSP EXP value is set for the NQA test instance.

      The default LSP EXP value is 0.

    2. Run lsp-replymode { level-control-channel | no-reply | udp }

      The reply mode in the NQA LSP test instance is configured.

    3. Run probe-count number

      The number of probes in a test is set for the NQA test instance.

      By default, the number of probes is 3.

    4. Run source-address ipv4 ip-address

      The source IP address of NQA test packets is set.

    5. Run tracert-livetime first-ttl first-ttl max-ttl max-ttl

      The TTL of test packets is set.

      By default, the initial TTL of packets is 1, and the maximum TTL of packets is 30.

  7. (Optional) Configure test failure conditions.
    1. Run timeout time

      The response timeout period is set.

      If no response packets are received before the set period expires, the probe is regarded as a failure.

      By default, the timeout period is 3s.

    2. Run tracert-hopfailtimes times

      The maximum number of hop failures in a probe is set.

      By default, a probe is considered failed when there are five hop failures in the probe.

  8. (Optional) Configure the NQA statistics function.

    Run records { history number | result number }

    The maximum number of history records and the maximum number of result records that can be saved for the NQA test instance are set.

  9. Schedule the test instance.
    1. (Optional) Run frequency interval

      The test period is set for the NQA test instance.

      By default, no interval is set. An NQA test instance is performed once.

    2. Run start

      An NQA test is started.

      The start command has multiple formats. Choose one of the following as needed.

      • To start an NQA test instance immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time, run the start at [ yyyy/mm/dd ] hh:mm:ss [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance after a specified delay, run the start delay { seconds second | hh:mm:ss } [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  10. Run commit

    The configuration is committed.

Configuring an LSP Jitter Test

A Label Switched Path (LSP) jitter test monitors the end-to-end jitter time on an MPLS network.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Create an NQA test instance and set the test instance type to LSP jitter.
    1. Run nqa test-instance admin-name test-name

      An NQA test instance is created, and the view of the test instance is displayed.

    2. Run test-type lspjitter

      The test instance type is set to LSP jitter.

    3. (Optional) Run description description

      A description is configured for the NQA test instance.

  3. (Optional) Run fragment enable

    MPLS packet fragmentation is enabled for the NQA test instance.

  4. Run lsp-type{ ipv4 | te | bgp| srte }

    The LSP type is specified for the NQA test instance.

  5. Configure the destination address or tunnel interface based on the type of the checked LSP.

    • To configure the destination address for a checked LDP LSP, run the destination-address ipv4 ip-address lsp-masklen masklen [ lsp-loopback loopback-address ] command.

    • To configure the tunnel interface for a checked TE tunnel, run the lsp-tetunnel tunnel interface-number command.

    • To configure the destination address for a BGP tunnel, run the destination-address ipv4 ip-address lsp-masklen masklen [ lsp-loopback loopback-address ] command.

    • To configure the tunnel interface for an SR-TE tunnel, run the lsp-tetunnel tunnel interface-number command.

    • To configure the destination address for an SR-BE tunnel, run the destination-address ipv4 ip-address lsp-masklen masklen command.

  6. (Optional) Set parameters for the test instance to simulate packets.
    1. Run lsp-exp exp

      The LSP EXP value is set for the NQA test instance.

      The default LSP EXP value is 0.

    2. Run lsp-replymode { level-control-channel | no-reply | udp }

      The reply mode in the NQA LSP test instance is configured.

    3. Run datafill fillstring

      Padding characters in NQA test packets are configured.

    4. Run datasize size

      The size of the data field in an NQA test packet.

    5. Run jitter-packetnum number

      The number of packets sent each time in a probe is set.

      By default, 20 packets are sent each time in a probe.

    6. Run probe-count number

      The number of probes in a test is set for the NQA test instance.

      By default, the number of probes is 3.

    7. Run interval seconds interval

      The interval at which NQA test packets are sent is set for the NQA test instance.

    8. Run source-address ipv4 ip-address

      The source IP address of NQA test packets is set.

    9. Run ttl number

      The TTL value in NQA test packets is set.

      By default, the TTL value is 30.

  7. (Optional) Configure test failure conditions.
    1. Run timeout time

      The response timeout period is set.

      If no response packets are received before the set period expires, the probe is regarded as a failure.

      By default, the timeout period is 3s.

    2. Run fail-percent percent

      The failure percentage is set for the NQA test instance.

      If the percentage of failed probes is equal to or greater than the failure percentage, the test is regarded as a failure.

      By default, the failure percent threshold is 100. A test is considered failed only after all probes fail.

  8. (Optional) Configure the NQA statistics function.

    Run records { history number | result number }

    The maximum number of history records and the maximum number of result records that can be saved for the NQA test instance are set.

  9. Schedule the test instance.
    1. (Optional) Run frequency interval

      The test period is set for the NQA test instance.

      By default, no interval is set. An NQA test instance is performed once.

    2. Run start

      An NQA test is started.

      The start command has multiple formats. Choose one of the following as needed.

      • To start an NQA test instance immediately, run the start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time, run the start at [ yyyy/mm/dd ] hh:mm:ss [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance after a specified delay, run the start delay { seconds second | hh:mm:ss } [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ] command.

      • To start an NQA test instance at a specified time every day, run the start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ] command.

  10. Run commit

    The configuration is committed.

Verifying the NQA Configuration

After the test is complete, use the following commands to verify test results.

Prerequisites

NOTE:
NQA test results are not displayed automatically on the terminal. To view test results, run the display nqa results command.

Procedure

  • Run the display nqa results [ collection ] [ test-instance admin-name test-name ] command to check NQA test results.
  • Run the display nqa results [collection] this command to check NQA test results in a specified NQA test instance view.
  • Run the display nqa history [ test-instance admin-name test-name ] command to check historical NQA test records.
  • Run the display nqa history [ this ] command to check historical statistics on NQA tests in a specified NQA test instance view.
  • Run the display lspv statistics command to check LSPV statistics.

Example

Run the display nqa results command to view NQA test results.

<HUAWEI> display nqa results test-instance admin lspping
NQA entry(admin, lspping) :testflag is active ,testtype is lspping
  1 . Test 1 result   The test is finished
   Send operation times: 3                Receive response times: 3
   Completion:success                     RTD OverThresholds number:0
   Attempts number:1                      Drop operation number:0
   Disconnect operation number:0          Operation timeout number:0
   System busy operation number:0         Connection fail number:0
   Operation sequence errors number:0     RTT Stats errors number:0
   Destination ip address:2.2.2.2
   Min/Max/Average Completion Time: 2/4/2
   Sum/Square-Sum  Completion Time: 8/24
   Last Good Probe Time: 2015-03-12 09:34:37.4
   Lost packet ratio: 0 %                                

Run the display nqa results [collection] this command to view NQA test results in a specified NQA test instance view.

<HUAWEI> system-view 
[~HUAWEI] nqa test-instance admin lspping
[~HUAWEI-nqa-admin-lspping] test-type lspping
[~HUAWEI-nqa-admin-lspping] display nqa results this
NQA entry(admin, lspping) :testflag is active ,testtype is lspping
  1 . Test 1 result   The test is finished
   Send operation times: 1                Receive response times: 0             
   Completion:failed                      RTD OverThresholds number:0           
   Attempts number:1                      Drop operation number:0               
   Disconnect operation number:0          Operation timeout number:0            
   System busy operation number:1         Connection fail number:0              
   Operation sequence errors number:0     RTT Stats errors number:0             
   Destination ip address:10.1.1.1
   Min/Max/Average Completion Time: 0/0/0
   Sum/Square-Sum  Completion Time: 0/0
   Last Good Probe Time: 0000-00-00 00:00:00.0 
   Lost packet ratio: 100 %

Run the display nqa history command to view historical NQA test records.

<HUAWEI> display nqa history test-instance admin lspping
NQA entry(admin,lspping) history:
--------------------------------------------------------------------------------
Index   T/H/P     Response Status       Address         Time
--------------------------------------------------------------------------------
 1      1/1/1        4ms   success      2.2.2.2         2015-03-12 09:34:29.414
 2      1/1/2        2ms   success      2.2.2.2         2015-03-12 09:34:33.419
 3      1/1/3        2ms   success      2.2.2.2         2015-03-12 09:34:37.415
--------------------------------------------------------------------------------

Run the display nqa history this command to view historical statistics on NQA tests in a specified NQA test instance view.

<HUAWEI> system-view 
[~HUAWEI] nqa test-instance admin lspping
[~HUAWEI-nqa-admin-lspping] test-type lspping
[~HUAWEI-nqa-admin-lspping] display nqa history this
NQA entry(admin,icmp) history:
--------------------------------------------------------------------------------
Index  T/H/P     Response Status       Address         Time
--------------------------------------------------------------------------------
 1     1/1/1         32ms success      1.1.1.1         2012-11-27 10:12:38.511
 2     1/1/2         47ms success      1.1.1.1         2012-11-27 10:12:42.520
 3     1/1/3         46ms success      1.1.1.1         2012-11-27 10:12:46.531
--------------------------------------------------------------------------------

Run the display lspv statistics command to view LSPV statistics.

<HUAWEI> display lspv statistics
Total sent: 1329 packet(s)
Total received: 1329 packet(s)
MPLS echo request sent: 2 packet(s), received: 1327 packet(s)
MPLS echo reply sent: 1327 packet(s), received: 2 packet(s)
Dropped beacause MPLS and virtual cluster access disabled: 0 packet(s)
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058924

Views: 7833

Downloads: 24

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