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

NE40E V800R010C00 Configuration Guide - System Monitor 01

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).
Using Ping/Tracert on an MPLS Network

Using Ping/Tracert on an MPLS Network

The ping and tracert operations can be used to monitor MPLS networks.

Using Ping to Monitor Link Connectivity on an MPLS Network

Ping operations can be used to check the connectivity of label distribution protocol (LDP) label switched path (LSPs) that carry IPv4 or IPv6 packets and TE tunnels that carry IPv4 packets.

Prerequisites

Before you start a test, run the lspv mpls-lsp-ping echo enable command to enable the device to respond to MPLS echo request packets.

As NQA is deployed on the main control board of a device, both the initiator and responder of an LSP ping test need to send LSP ping test packets to the main control board for processing. If a large number of packets are sent to the main control board, the CPU usage of the main control board increases, which adversely affects device operation. To prevent this problem, run the lspv mpls-lsp-ping cpu-defend cpu-defend command to set an upper limit for the rate of sending MPLS Echo Request packets to the main control board.

If the MPLS packet length of an NQA test instance is greater than the MTU of a specified MPLS tunnel, MPLS packets fail to pass through the tunnel. To allow the packets to pass through the tunnel, run the fragment enable command to enable MPLS packet fragmentation.

Context

Perform the following steps in any view on the NQA client:

Procedure

  • To test the connectivity of an LDP LSP that carries IPv4 packets, run:

    ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -r reply-mode | -s packet-size | -t time-out | -v | -g ] * ip destination-iphost mask-length [ ip-address ] [ nexthop nexthop-address ] [ remote remote-address ]

    For example:

    <HUAWEI> ping lsp -v ip 3.3.3.3 32 
      LSP PING FEC: IPV4 PREFIX 3.3.3.3/32/ : 100  data bytes, press CTRL_C to break
        Reply from 3.3.3.3: bytes=100 Sequence=1 time = 4 ms Return Code 3, Subcode 1
        Reply from 3.3.3.3: bytes=100 Sequence=2 time = 4 ms Return Code 3, Subcode 1
        Reply from 3.3.3.3: bytes=100 Sequence=3 time = 4 ms Return Code 3, Subcode 1
        Reply from 3.3.3.3: bytes=100 Sequence=4 time = 4 ms Return Code 3, Subcode 1
        Reply from 3.3.3.3: bytes=100 Sequence=5 time = 5 ms Return Code 3, Subcode 1
      --- FEC: IPV4 PREFIX 3.3.3.3/32/ ping statistics ---
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 4/4/5 ms   

  • To test the connectivity of a TE tunnel (RSVP-TE tunnel, static TE tunnel, or dynamic TE tunnel) that carries IPv4 packets, run:

    ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -r reply-mode | -s packet-size | -t time-out | -v | -g ] * te { Tunnel interface-number [ hot-standby ] [ compatible-mode ] | auto-tunnel auto-tunnelname }

    For example:

    <HUAWEI> ping lsp te Tunnel 1
      LSP PING FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1 : 100  data bytes, press CTRL_C to break
        Reply from 1.1.1.1: bytes=100 Sequence=1 time = 4 ms
        Reply from 1.1.1.1: bytes=100 Sequence=2 time = 2 ms
        Reply from 1.1.1.1: bytes=100 Sequence=3 time = 2 ms
        Reply from 1.1.1.1: bytes=100 Sequence=4 time = 2 ms
        Reply from 1.1.1.1: bytes=100 Sequence=5 time = 2 ms
    
      --- FEC: RSVP IPV4 SESSION QUERY Tunnel1 ping statistics ---
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 2/2/4 ms                     

  • Test SR-TE IPv4 tunnel connectivity.

    • To test the connectivity of an SR-TE tunnel dynamically created, run the ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -s packet-size | -t time-out | -v | -g ] * segment-routing auto-tunnel auto-tunnelname version { draft2 | draft4 } [ remote remote-address ] [ hot-standby ] command and specify auto-tunnelname on the ingress to initiate a ping test to the egress.

      <HUAWEI> ping lsp segment-routing auto-tunnel Tunnel10 version draft4 
        LSP PING FEC: AUTO TE TUNNEL IPV4 SESSION QUERY Tunnel10 : 100 data bytes, press CTRL_C to break
          Reply from 10.1.1.2: bytes=100 Sequence=1 time=11 ms
          Reply from 10.1.1.2: bytes=100 Sequence=2 time=9 ms
          Reply from 10.1.1.2: bytes=100 Sequence=3 time=6 ms
      
        --- FEC: AUTO TE TUNNEL IPV4 SESSION QUERY Tunnel10 ping statistics ---
          3 packet(s) transmitted
          3 packet(s) received
          0.00% packet loss
          round-trip min/avg/max = 6/8/11 ms
    • To test the connectivity of an SR-TE IPv4 tunnel manually configured, run the ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -s packet-size | -t time-out | -v | -g ] * segment-routing te Tunnel interface-number [ draft2 ] [ remote remote-address ] [ hot-standby ] command to initiate a ping test to the egress.

      <HUAWEI> ping lsp segment-routing te Tunnel10
        LSP PING FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel10 : 100 data bytes, press CTRL_C to break
          Reply from 10.1.1.2: bytes=100 Sequence=1 time=11 ms
          Reply from 10.1.1.2: bytes=100 Sequence=2 time=9 ms
          Reply from 10.1.1.2: bytes=100 Sequence=3 time=6 ms
      
        --- FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel10 ping statistics ---
          3 packet(s) transmitted
          3 packet(s) received
          0.00% packet loss
          round-trip min/avg/max = 6/8/11 ms

  • Test SR-TE IPv6 tunnel connectivity.

    To test the connectivity of an SR-TE IPv6 tunnel, run the ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -s packet-size | -t time-out | -v | -g ] * segment-routing te ipv6 Tunnel interface-number nil-fec [ hot-standby ] command on the ingress to initiate a ping test to the egress.

  • Test SR-BE IPv4 tunnel connectivity.

    To test the connectivity of an SR-BE IPv4 tunnel, run the ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -s packet-size | -t time-out | -v | -g ] * segment-routing ip destination-address mask-length version draft2 [ remote remote-ip ] command.

    <HUAWEI> ping lsp segment-routing ip 3.3.3.9 32 version draft2
    LSP PING FEC: SEGMENT ROUTING IPV4 PREFIX 3.3.3.9/32 : 100  data bytes, press CTRL_C to break
      Reply from 3.3.3.9: bytes=100 Sequence=1 time=13 ms
      Reply from 3.3.3.9: bytes=100 Sequence=2 time=9 ms
      Reply from 3.3.3.9: bytes=100 Sequence=3 time=2 ms
      Reply from 3.3.3.9: bytes=100 Sequence=4 time=3 ms
      Reply from 3.3.3.9: bytes=100 Sequence=5 time=6 ms
    --- FEC: SEGMENT ROUTING IPV4 PREFIX 3.3.3.9/32 ping statistics ---
      5 packet(s) transmitted
      5 packet(s) received
      0.00% packet loss
      round-trip min/avg/max = 2/6/13 ms
    

  • Test the connectivity of the BGP LSP carrying IPv4 packets.

    Run the ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -r reply-mode | -s packet-size | -t time-out | -v | -g ] * bgp destination-iphost mask-length [ ip-address ] [ nexthop nexthop-address ] command to test the connectivity.

    <HUAWEI> ping lsp -c 2 bgp 4.4.4.4 32
    LSP PING FEC: BGP LABELED IPV4 PREFIX 4.4.4.4/32/ : 100 data bytes, press CTRL_C to break
    Reply from 4.4.4.4: bytes=100 Sequence=1 time=46 ms
    Reply from 4.4.4.4: bytes=100 Sequence=2 time=2 ms
    
    --- FEC: BGP LABELED IPV4 PREFIX 4.4.4.4/32 ping statistics ---
    2 packet(s) transmitted
    2 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 2/24/46 ms
    

  • Test the connectivity of the LSP between a master and an AP in a virtual access scenario.

    Run the ping lsp [ -c count | -exp exp-value | -m interval | -t time-out | -g ] * ap { ap-id | ap-address } [ primary | hot-standby ] command to test the connectivity.

    <HUAWEI> ping lsp ap 1024
      LSP PING FEC: AP 1.1.1.2 , press CTRL_C to break
        Reply from 1.1.1.2: bytes=60 Sequence=1 time=10 ms
        Reply from 1.1.1.2: bytes=60 Sequence=2 time=2 ms
        Reply from 1.1.1.2: bytes=60 Sequence=3 time=4 ms
        Reply from 1.1.1.2: bytes=60 Sequence=4 time=2 ms
        Reply from 1.1.1.2: bytes=60 Sequence=5 time=3 ms
    
      --- FEC: AP 1.1.1.2 statistics ---
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 2/4/10 ms
    

  • Test the connectivity of an LSP of a tunnel from a master to an AP in a virtual access scenario.

    Run the ping lsp [ -c count | -exp exp-value | -m interval | -t time-out | -g ] * ap { ap-id | ap-address } [ primary | hot-standby ] va-tunnel-name command to test the connectivity of an LSP of a tunnel from the master to AP.

    <HUAWEI> ping lsp ap 1024 tunnel1 
      LSP PING FEC: AP 2.2.2.9 , press CTRL_C to break
        Reply from 2.2.2.9: bytes=60 Sequence=1 time=34 ms
        Reply from 2.2.2.9: bytes=60 Sequence=2 time=6 ms
        Reply from 2.2.2.9: bytes=60 Sequence=3 time=7 ms
        Reply from 2.2.2.9: bytes=60 Sequence=4 time=9 ms
        Reply from 2.2.2.9: bytes=60 Sequence=5 time=8 ms
    
    --- FEC: AP 2.2.2.9 statistics ---
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet losss
        round-trip min/avg/max = 6/12/34 ms

  • Test the connectivity of an LDP LSP connected with an SR-BE tunnel.

    To test the connectivity of an LDP LSP connected with an SR-BE tunnel, run the ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -r reply-mode | -s packet-size | -t time-out | -v | -g ] * ip destination-iphost mask-length [ ip-address ] [ nexthop nexthop-address ] [ remote remote-address ] command on the ingress to initiate a ping test to the egress of the SR-BE tunnel.

    <HUAWEI> ping lsp -c 3 ip 5.5.5.9 32 remote 5.5.5.9
      LSP PING FEC: IPV4 PREFIX 5.5.5.9/32/ : 100  data bytes, press CTRL_C to break
        Reply from 5.5.5.9: bytes=100 Sequence=1 time=3 ms
        Reply from 5.5.5.9: bytes=100 Sequence=2 time=3 ms
        Reply from 5.5.5.9: bytes=100 Sequence=3 time=3 ms
    
      --- FEC: IPV4 PREFIX 5.5.5.9/32 ping statistics ---
        3 packet(s) transmitted
        3 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 3/3/3 ms
    

  • Test the connectivity of an SR-BE tunnel connected with an LDP LSP.

    To test the connectivity of an SR-BE tunnel connected with an LDP LSP, run the ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -s packet-size | -t time-out | -v | -g ] * segment-routing ip destination-address mask-length version draft2 remote remote-ip command on the ingress to initiate a ping test to the egress with destination address being the LDP LSP.
    NOTE:
    When testing the connectivity of an SR-BE tunnel connected with an LDP LSP, specify a remote IP address using the remote remote-ip parameter.
    <HUAWEI> ping lsp -c 3 segment-routing ip 5.5.5.9 32 version draft2 remote 5.5.5.9
      LSP PING FEC: IPV4 PREFIX 5.5.5.9/32 : 100  data bytes, press CTRL_C to break
        Reply from 5.5.5.9: bytes=100 Sequence=1 time=9 ms
        Reply from 5.5.5.9: bytes=100 Sequence=2 time=2 ms
        Reply from 5.5.5.9: bytes=100 Sequence=3 time=3 ms
    
      --- FEC: IPV4 PREFIX 5.5.5.9/32 ping statistics ---
        3 packet(s) transmitted
        3 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 2/4/9 ms
    
    

Follow-up Procedure

After the test is completed, you are advised to run the undo lspv mpls-lsp-ping echo enable command to disable the device from responding to MPLS Echo Request packets to prevent system resource occupation.

Using Tracert to Test the Forwarding Path on an MPLS Network

A tracert operation tests the path over which an label distribution protocol (LDP) label switched path (LSP) or a TE tunnel that carries IPv4 packets is established or locate the fault point on the path.

Prerequisites

Before you start a test, run the lspv mpls-lsp-ping echo enable command to enable the device to respond to MPLS echo request packets.
NOTE:

If the device interworks with a non-Huawei device, run the lspv echo-reply compitable fec enable command to enable the device to respond to MPLS Echo Request packets with MPLS Echo Reply packets that do not carry FEC information.

As NQA is deployed on the main control board of a device, both the initiator and responder of an LSP ping test need to send LSP ping test packets to the main control board for processing. If a large number of packets are sent to the main control board, the CPU usage of the main control board increases, which adversely affects device operation. To prevent this problem, run the lspv mpls-lsp-ping cpu-defend cpu-defend command to set an upper limit for the rate of sending MPLS Echo Request packets to the main control board.

Context

Perform the following steps in any view on the NQA client:

Procedure

  • To test the path over which an LDP LSP that carries IPv4 packets is established or locate the fault point on the path, run:

    tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -t time-out | -s size  | -g ] * ip destination-iphost mask-length [ ip-address ] [ nexthop nexthop-address ] [ detail ]

    For example:

    <HUAWEI> tracert lsp ip 1.1.1.1 32
      LSP Trace Route FEC: IPV4 PREFIX 1.1.1.1/32 , press CTRL_C to break.
      TTL    Replier            Time    Type      Downstream
      0                                 Ingress   10.1.1.1/[3 ]
      1      1.1.1.1            5       Egress           

  • To test the path over which a TE tunnel (RSVP-TE tunnel, static TE tunnel, or dynamic TE tunnel) that carries IPv4 packets is established or locate the fault point on the path, run:

    tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -t time-out | -s size  | -g ] * { te Tunnel interface-number [ hot-standby ] [ compatible-mode ] | auto-tunnel auto-tunnelname [ detail ]

    For example:

    <HUAWEI> tracert lsp te Tunnel 1
      LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1 , press CTRL_C to break.
      TTL    Replier            Time    Type      Downstream
      0                                 Ingress   10.1.1.1/[3 ]
      1      1.1.1.1            4       Egress                             

  • Test the path over which an SR-TE IPv4 tunnel is established or locate the fault point on the path.

    • To test an SR-TE tunnel dynamically created, run the tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -t time-out | -s size | -g ] * segment-routing auto-tunnel auto-tunnelname version { draft2 | draft4 } [ hot-standby ] [ detail ] command and specify auto-tunnelname on the ingress to initiate a tracert test to the egress.

      <HUAWEI> tracert lsp segment-routing auto-tunnel Tunnel10 version draft4
        LSP  Trace  Route  FEC: AUTO TE TUNNEL IPV4 SESSION QUERY Tunnel10 , press CTRL_C to break.
        TTL     Replier                   Time    Type      Downstream
        0                                         Ingress   10.1.1.2/[284688 ]
        1       10.1.1.2                  7 ms    Egress 
    • To test an SR-TE IPv4 tunnel manually configured, run the tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -t time-out | -s size | -g ] * segment-routing te Tunnel tunnel-number [ draft2 ] [ hot-standby ] [ detail ] command and specify Tunnel interface-number on the ingress to initiate a tracert test to the egress.

      <HUAWEI> tracert lsp segment-routing te Tunnel10 
        LSP  Trace  Route  FEC: AUTO TE TUNNEL IPV4 SESSION QUERY Tunnel10 , press CTRL_C to break.
        TTL     Replier              Time    Type      Downstream
        0                                    Ingress   10.1.1.2/[284688 ]
        1       10.1.1.2             7 ms    Egress

  • Test the path over which an SR-BE IPv4 tunnel is established or the fault point on the path.

    To test the fault point on an SR-BE IPv4 tunnel, run the tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -s size | -g ] * segment-routing ip ip-address mask-length version draft2 [ remote remote-ip ] command.

    <HUAWEI> tracert lsp segment-routing ip 2.2.2.2 32 version draft2
      LSP Trace Route FEC: SEGMENT ROUTING IPV4 PREFIX 2.2.2.2/32 , press CTRL_C to break.
      TTL    Replier            Time    Type      Downstream
      0                                 Ingress   192.1.1.2/[1001 ]
      1      192.1.1.2          6 ms    Transit    192.1.2.2/[3 ]
      2      192.1.2.2          6 ms    Egress

  • Test the BGP LSP carrying IPv4 packets or locate the fault point on the path.

    Run the tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -t time-out | -s size | -g ] * bgp destination-iphost mask-length [ ip-address ] [ detail ] [ nexthop nexthop-address ] command to test the BGP LSP carrying IPv4 packets or locate the fault point on the path.

    <HUAWEI> tracert lsp -h 5 bgp 4.4.4.4 32
      LSP Trace Route FEC: IPV4 PREFIX 4.4.4.4/32 , press CTRL_C to break.
      TTL    Replier            Time    Type      Downstream
      0                                 Ingress   20.1.1.2/[32967 3 ]
      1      20.1.1.2           5 ms    Transit   20.2.1.2/[32938 3 ]
      2      20.2.1.2           6 ms    Transit   20.3.1.2/[32989 3 ]
      3      4.4.4.4            1 ms    Egress 
    

  • In a virtual access scenario, test the path from the Master to the AP or locate the fault point on the path.

    Run the tracert lsp [ -exp exp-value | -t timeout-value | -g ] * ap { ap-address | ap-id } [ primary | hot-standby ] [ downstream-interface ] [ detail ] command to test the path from the Master to the AP or locate the fault point on the path.

    <HUAWEI> tracert lsp ap 1024 downstream-interface
      LSP Trace Route FEC: AP 1.1.1.2/0/, press CTRL_C to break.
      TTL    Replier            Time    Type      Downstream
      0                                 Ingress   Ethernet1/0/1/0[17 ]
      1      1.1.1.2            5 ms    Egress 

  • Test the connectivity of an LSP of a tunnel from the Master to an AP in a virtual access scenario.

    Run the tracert lsp [ -exp exp-value | -t timeout-value | -g ] * ap { ap-address | ap-id } [ primary | hot-standby ] [ downstream-interface ] [ detail ] va-tunnel-name command to test the connectivity of an LSP of a tunnel from the Master to an AP.

    <HUAWEI> tracert lsp ap 1024 tunnel1 
      LSP Trace Route FEC: AP 2.2.2.9 , press CTRL_C to break.
      TTL   Replier    Time      Type       Downstream
      0                          Ingress    4.4.4.9/[43 ]
      1     4.4.4.9    33 ms     Transit    3.3.3.9/[40 ]
      2     3.3.3.9    28 ms     Transit    2.2.2.9/[32 ]
      3     2.2.2.9    8 ms      Egress 

  • Locate a fault point on an LDP LSP connected with an SR-BE tunnel.

    To locate a fault point on an LDP LSP connected with an SR-BE tunnel, run the tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -t time-out | -s size | -g ] * ip destination-iphost mask-length [ ip-address ] [ nexthop nexthop-address ] [ detail ] [ ddmap ] command on the ingress to initiate a tracert test to the egress of the SR-BE tunnel.

    <HUAWEI> tracert -h 10 ip 1.1.1.1 32 ddmap
      LSP Trace Route FEC: IPV4 PREFIX 5.5.5.9/32 , press CTRL_C to break.
      TTL    Replier            Time    Type      Downstream
      0                                 Ingress   12.1.1.2/[66010 ]
      1      12.1.1.2           9 ms    Transit   21.1.1.2/[33182 ]
      2      21.1.1.2           7 ms    Transit   100.1.1.2/[319836 ]
      3      1.1.1.2            9 ms    Transit   2.1.1.2/[3 ]
      4      5.5.5.9            3 ms    Egress 
    

  • Locate a fault point on an SR-BE tunnel connected with an LDP LSP.

    To locate a fault point on an SR-BE tunnel connected with an LDP LSP, run the tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -s size | -g ] * segment-routing ip ip-address mask-length version draft2 [ remote remote-ip ] command on the ingress to initiate a tracert test to the egress with destination address being the LDP LSP.

    <HUAWEI> tracert lsp -h 10 segment-routing ip 5.5.5.9 32 version draft2 remote 5.5.5.9
      LSP Trace Route FEC: SEGMENT ROUTING IPV4 PREFIX 5.5.5.9/32 , press CTRL_C to break.
      TTL    Replier            Time    Type      Downstream
      0                                 Ingress   12.1.1.2/[319546 ]
      1      12.1.1.2           7 ms    Transit   21.1.1.2/[319546 ]
      2      21.1.1.2           7 ms    Transit   100.1.1.2/[33517 3 ]
      3      100.1.1.2          11 ms   Transit   200.1.1.2/[3 ]
      4      5.5.5.9            2 ms    Egress    
    
    

Follow-up Procedure

After the test is completed, you are advised to run the undo lspv mpls-lsp-ping echo enable command to disable the device from responding to MPLS Echo Request packets to prevent system resource occupation.

Download
Updated: 2018-07-12

Document ID: EDOC1100028538

Views: 29310

Downloads: 220

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