ping multicast-lsp

Function

The ping multicast-lsp command checks path information between nodes on a point to point dynamic P2MP.

The ping multicast-lsp command checks path information between nodes on a point to point VPLS over P2MP, NGMVPN, static P2MPTE, static MLDP network.

Format

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

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

Parameters

Parameter	Description	Value
-a source-ip	Source IP address of MPLS echo request messages to be sent. If no source IP address is specified, the outbound interface's IP address is used as the source IP address of MPLS echo request messages to be sent.	The value is in dotted decimal notation.
-c count	Specifies the number of MPLS echo request messages to be sent.	The value is an integer ranging from 1 to 4294967295. The default value is 5.
-exp exp-value	Specifies the EXP value of MPLS echo request messages to be sent. The EXP value indicates the packet priority.	The value is an integer ranging from 0 to 7. The default value is 0.
-m interval	Specifies an interval at which MPLS echo request messages are sent.	The value is an integer ranging from 2000 to 10000, in milliseconds.
-r reply-mode	Specifies the mode in which the peer responds with MPLS echo reply messages.	The value is an integer ranging from 1 to 4. The default value is 2. 1: no reply This mode is used in unidirectional tests. The test is successful if the source node displays a timeout message. The test fails if the system displays a message showing that the LSP does not exist. 2: reply with an IPv4 or IPv6 UDP packet 3: reply with an IPv4 or IPv6 UDP packet that carries the Router Alert option 4: reply through the control channel of the application plane
-s packet-size	Specifies a packet payload length, excluding the IP header and UDP header.	The value is an integer ranging from 65 to 9600, in bytes. The default value is 100.
-t time-out	Specifies the timeout period for waiting for MPLS echo reply messages.	The value is an integer ranging from 2000 to 65535, in milliseconds. The default value is 2000. time-out must be less than -m interval.
-j jitter-value	Specifies a delay after which the destination node responds with an MPLS echo reply message.	The value is an integer ranging from 0 to 1000.
-v	Displays non-ICMP Echo Response packets.	-
te tunnel-name	Specifies the interface name of the TE tunnel.	-
tunnel-type	Specifies the interface type of the TE tunnel.	-
tunnel-number	Specifies the interface number of the TE tunnel.	-
leaf-destination leaf-destination	Specifies the destination node on a sub-LSP of a P2MP TE tunnel.	The value is in dotted decimal notation.
te-auto-tunnel auto-tunnel-name	Specifies the interface type of the auto TE tunnel.	-
mldp	Specifies multipoint extensions for LDP.	-
p2mp	Specifies the point to multi-point.	-
root-ip root-ip-address	Specifies the IP address of the root node on a P2MP label distribution protocol (LDP) label switched path (LSP).	The value is in dotted decimal notation.
lsp-id lsp-id	Specifies the ID on a P2MP label distribution protocol (LDP) label switched path (LSP).	The value is an integer ranging from 0 to 4294967295.
opaque-value opaque-value	Specifies information used to uniquely identify a P2MP LDP LSP.	The value is an integer ranging from 1 to 254.

Views

All views

Default Level

0: Visit level

Task Name and Operations

Task Name	Operations
sla	execute

Usage Guidelines

Usage Scenario

To check path information between nodes on a point to point VPLS over P2MP, NGMVPN, static P2MPTE, static MLDP network, run the ping multicast-lsp command.

To check the P2MP LDP LSP connectivity, run the ping multicast-lsp mldp p2mp root-ip command.
To check the connectivity of a P2MP TE tunnel that is automatically generated, run the ping multicast-lsp te-auto-tunnel command.
To check the connectivity of a P2MP TE tunnel, run the ping multicast-lsp te command.

Example

# 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 P2MPoh5121 : 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

# 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: Multicast P2MP LDP root-ip 1.1.1.1 opaque-value 01000400014497 : 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

**Table 1** Description of the **ping multicast-lsp** command output
Item	Description
LSP PING FEC: RSVP P2MP IPv4 P2MP-Auto-tunnel : 100 data bytes, press CTRL_C to break	The RSVP P2MP IPv4 P2MP-Auto-tunnel is being pinged, with the packet length of 100 bytes. You can press CTRL+C to stop the ongoing ping test.
Reply from x.x.x.x	Response from the destination node to each MPLS echo request message. bytes: length of an MPLS echo reply message. sequence: sequence number of an MPLS echo reply message. time: delay after which the destination node responds with an MPLS echo reply message. If no MPLS echo reply message is received after the timeout period expires, "Request time out" is displayed.
--- Destination: 2.2.2.2 ping statistics ---	Ping statistics. packet(s) transmitted: number of MPLS echo request messages sent. packet(s) received: number of MPLS echo reply messages received. % packet loss: percentage of the number of MPLS echo request messages with no responses to the total number of MPLS echo request messages sent. round-trip min/avg/max: minimum, average, or maximum response time.