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

Using Ping/Tracert on a P2MP Network

This section describes how to use ping and tracert operations to check the P2MP network connectivity.

Using Ping to Check Link Connectivity on a P2MP Network

Run the ping commands to check the connectivity between nodes on a Point-to-Multipoint (P2MP) network.

Usage Scenario

On a VPLS over P2MP network, ping can be used to check the following tunnels:

  • P2MP label distribution protocol (LDP) label switched paths (LSPs)
  • P2MP TE tunnels that are automatically generated

Pre-configuration Tasks

Before using ping to check the P2MP network connectivity, ensure that P2MP is correctly configured.

Procedure

  1. Run the ping multicast-lsp command to check the connectivity of the following tunnels on a P2MP network:

    • P2MP LDP LSPs

      ping multicast-lsp [ -a source-ip | -c count | -exp exp-value | -j jitter-value | -m interval | -r reply-mode | -s packet-size | -t time-out | -v ] * mldp p2mp root-ip root-ip-address { lsp lsp-id | opaque-value opaque-value } [ leaf-destination leaf-destination ]

    • P2MP TE tunnels that are automatically generated

      ping multicast-lsp [ -a source-ip | -c count | -exp exp-value | -j jitter-value | -m interval | -r reply-mode | -s packet-size | -t time-out | -v ] * te-auto-tunnel auto-tunnel-name [ leaf-destination leaf-destination ]

    # Use ping to check the P2MP LDP LSP connectivity.

    <HUAWEI> ping multicast-lsp mldp p2mp root-ip 1.1.1.1 lsp-id 1
      LSP PING FEC: root-ip 1.1.1.1 : 100  data bytes, press CTRL_C to break
        Reply from 10.10.10.10: bytes=100 Sequence=1 time=60 ms
        Reply from 10.10.10.10: bytes=100 Sequence=2 time=50 ms
        Reply from 10.10.10.10: bytes=100 Sequence=3 time=30 ms
        Reply from 10.10.10.10: bytes=100 Sequence=4 time=100 ms
        Reply from 10.10.10.10: bytes=100 Sequence=5 time=80 ms
    
        round-trip min/avg/max = 30/64/100 ms

    # Use ping to check the P2MP TE tunnel connectivity.

    <HUAWEI> ping multicast-lsp te-auto-tunnel P2MPoh5121 
      LSP PING FEC: RSVP P2MP IPv4 P2MP-Auto-tunnel : 100  data bytes, press CTRL_C to break                                            
        Reply from 2.2.2.2: bytes=100 Sequence=1 time=10 ms                                                                                
        Reply from 3.3.3.3: bytes=100 Sequence=1 time=60 ms                                                                                 
        Reply from 5.5.5.5: bytes=100 Sequence=1 time=60 ms                                                                             
        Reply from 6.6.6.6: bytes=100 Sequence=1 time=80 ms                                                                             
        Reply from 2.2.2.2: bytes=100 Sequence=2 time=20 ms                                                                             
        Reply from 5.5.5.5: bytes=100 Sequence=2 time=50 ms                                                                             
        Reply from 6.6.6.6: bytes=100 Sequence=2 time=70 ms                                                                             
        Reply from 3.3.3.3: bytes=100 Sequence=2 time=70 ms                                                                             
        Reply from 2.2.2.2: bytes=100 Sequence=3 time=50 ms                                                                             
        Reply from 6.6.6.6: bytes=100 Sequence=3 time=100 ms                                                                            
        Reply from 3.3.3.3: bytes=100 Sequence=3 time=110 ms                                                                            
        Reply from 5.5.5.5: bytes=100 Sequence=3 time=110 ms                                                                            
        Reply from 2.2.2.2: bytes=100 Sequence=4 time=30 ms                                                                             
        Reply from 6.6.6.6: bytes=100 Sequence=4 time=50 ms                                                                             
        Reply from 5.5.5.5: bytes=100 Sequence=4 time=60 ms                                                                             
        Reply from 3.3.3.3: bytes=100 Sequence=4 time=60 ms                                                                             
        Reply from 2.2.2.2: bytes=100 Sequence=5 time=30 ms                                                                             
        Reply from 6.6.6.6: bytes=100 Sequence=5 time=40 ms                                                                             
        Reply from 5.5.5.5: bytes=100 Sequence=5 time=80 ms                                                                             
        Reply from 3.3.3.3: bytes=100 Sequence=5 time=80 ms                                                                             
                                                                                                                                        
      --- Destination: 2.2.2.2  ping statistics ---                                                                                     
        5 packet(s) transmitted                                                                                                         
        5 packet(s) received                                                                                                            
        0.00% packet loss                                                                                                               
        round-trip min/avg/max = 10/28/50 ms                                                                                            
                                                                                                                                        
      --- Destination: 3.3.3.3  ping statistics ---                                                                                     
        5 packet(s) transmitted                                                                                                         
        5 packet(s) received                                                                                                            
        0.00% packet loss                                                                                                               
        round-trip min/avg/max = 60/76/110 ms                                                                                           
                                                                                                                                        
      --- Destination: 5.5.5.5  ping statistics ---                                                                                     
        5 packet(s) transmitted                                                                                                         
        5 packet(s) received                                                                                                            
        0.00% packet loss                                                                                                               
        round-trip min/avg/max = 50/72/110 ms                                                                                           
                                                                                                                                        
      --- Destination: 6.6.6.6  ping statistics ---                                                                                     
        5 packet(s) transmitted                                                                                                         
        5 packet(s) received                                                                                                            
        0.00% packet loss                                                                                                               
        round-trip min/avg/max = 40/68/100 ms                                
    

Using Tracert to Check the Forwarding Path on a P2MP Network

Run the tracert commands to check path information on a Point-to-Multipoint (P2MP) network so that faults can be located.

Usage Scenario

On a VPLS over P2MP network, tracert can be used to check the following tunnels:

  • P2MP label distribution protocol (LDP) label switched paths (LSPs)
  • P2MP TE tunnels that are automatically generated

Pre-configuration Tasks

Before using tracert to check the P2MP network connectivity, ensure that P2MP is correctly configured.

Procedure

  1. Run the tracert multicast-lsp command to check path information about the following tunnels on a VPLS over P2MP network:

    • VPLS over P2MP LDP LSPs

      tracert multicast-lsp [ -a source-ip | -exp exp-value | -h ttl-value | -j jitter-value | -r reply-mode | -t time-out | t-flag ] * mldp p2mp root-ip root-ip-address { lsp lsp-id | opaque-value opaque-value } [ detail ]

    • VPLS over P2MP TE tunnels that are automatically generated

      tracert multicast-lsp [ -a source-ip | -exp exp-value | -h ttl-value | -j jitter-value | -r reply-mode | -t time-out | t-flag ] * te-auto-tunnel auto-tunnel-name [ leaf-destination leaf-destination ] [ detail ]

    # Use tracert to check path information about a P2MP LDP LSP.

    <HUAWEI> tracert multicast-lsp -h 10 mldp p2mp root-ip 8.8.8.8 lsp-id 1
      LSP Trace Route FEC: Multicast P2MP LDP , press CTRL_C to break.
      TTL   Replier            Time    Type      Downstream
      1     192.168.1.9        40 ms   Transit   192.168.2.12/[1024 ]
      2     10.10.10.10        110 ms  Egress
      3     10.10.10.10        140 ms  Egress
      4     10.10.10.10        50 ms   Egress
      5     10.10.10.10        70 ms   Egress
      6     10.10.10.10        80 ms   Egress
      7     10.10.10.10        70 ms   Egress
      8     10.10.10.10        30 ms   Egress
      9     10.10.10.10        60 ms   Egress
      10    10.10.10.10        110 ms  Egress

    # Use tracert to check path information about a P2MP TE tunnel.

    <HUAWEI> tracert multicast-lsp -h 2 te-auto-tunnel P2MPoh5121
      LSP Trace Route FEC: RSVP P2MP IPv4 , press CTRL_C to break.
      TTL   Replier            Time    Type      Downstream
      1     2.2.2.2            30 ms   Bud       172.16.3.2/[1048575 ]
      1     4.1.1.2            40 ms   Transit   5.1.1.2/[900001 ]
      2     2.2.2.2            30 ms   Bud       172.16.3.2/[1048575 ]
      2     6.6.6.6            60 ms   Egress
      2     3.3.3.3            80 ms   Egress
      2     5.5.5.5            80 ms   Egress 
    

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058924

Views: 7805

Downloads: 24

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