ping mpls rsvp
Syntax
ping mpls rsvp <lsp-name> <count count> <destination address> <detail> <dynamic-bypass> <egress egress-address> <exp forwarding-class> <interface interface-name> <logical-system (all | logical-system-name)> <manual-bypass> <multipoint> <size bytes> <source source-address> <standby standby-path-name> <sweep>
Description
Check the operability of MPLS RSVP-signaled
label-switched path (LSP) connections. Type Ctrl+c to interrupt a ping mpls command.
Options
| count count | (Optional) Number of ping requests to send. If |
| destination address | (Optional) Specify an address other than the default
( |
| detail | (Optional) Display detailed information about the echo requests sent and received. Note:
When using the In practice, it is difficult to synchronize the system times
of independent Juniper Networks routers with sufficient accuracy to
provide a meaningful time value for the |
| dynamic-bypass | (Optional) Ping dynamically generated bypass LSPs, used for protecting other LSPs. |
| egress egress-address | (Optional) Only the specified egress router or switch responds to the ping request. |
| exp forwarding-class | (Optional) Value of the forwarding class for the MPLS ping packets. |
| interface | (Optional)
Specify the name of the interface protected by the manual bypass LSP.
This option is only available when you have also used the |
| logical-system (all | logical-system-name) | (Optional) Perform this operation on all logical systems or on the specified logical system. |
| lsp-name | Ping an RSVP-signaled LSP using an LSP name. |
| manual-bypass | (Optional)
Ping manually configured bypass LSPs, used for protecting other LSPs.
For this option, you must also specify the interface protected by
the manual bypass LSP using the |
| multipoint | (Optional)
Send ping requests to each of the egress routers or switches participating
in a point-to-multipoint LSP. You can also include the |
| size bytes | (Optional) Size of the LSP ping request packet ( |
| source source-address | (Optional) IP address of the outgoing interface. This address is sent in the IP source address field of the ping request. If this option is not specified, the default address is usually the loopback interface. |
| standby standby-path-name | (Optional) Name of the standby path. |
| sweep | (Optional) Automatically determine the size of the maximum transmission unit (MTU). |
Additional Information
If the LSP changes, the label and interface
information displayed when you issued the ping command
continues to be used. You must configure MPLS at the [edit protocols
mpls] hierarchy level on the remote router or switch to ping
an LSP terminating there. You must configure MPLS even if you intend
to ping only LDP forwarding equivalence classes (FECs).
In asymmetric MTU scenarios, the echo response might be dropped. For example, if the MTU from System A to System B is 1000 bytes, the MTU from System B to System A is 500 bytes, and the ping request packet size is 1000 bytes, the echo response is dropped because the PAD TLV is included in the echo response, making it too large.
In a Juniper-Cisco interoperation network scenario, a point-to-multipoint LSP ping echo reply message from a Cisco device in a different IGP area is dropped on the Juniper device when the source address of the reply message is an interface address other than the loopback address or router ID. Starting in Junos OS Release 13.3X8, 14.2R6, 15.1R4, 15.1F6, 15.1F5-S8, 16.1R1, and later releases, such point-to-multipoint LSP ping echo reply messages are accepted by the Juniper device and the messages get logged as uncorrelated responses.
Required Privilege Level
network
Output Fields
When you enter this command, you are provided
feedback on the status of your request. An exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply was not received within the
timeout period. An x indicates that an echo reply was received
with an error code. Packets with an error code are not counted in
the received packets count. They are accounted for separately.
Sample Output
- ping mpls rsvp (Echo Reply Received)
- ping mpls rsvp (Echo Reply with Error Code)
- ping mpls rsvp detail
- ping mpls rsvp multipoint egress detail count
- ping mpls rsvp multipoint detail count
- ping mpls rsvp destination detail count size
- ping mpls rsvp destination detail sweep size
ping mpls rsvp (Echo Reply Received)
user@host> ping mpls rsvp test1 !!!!!--- lsping statistics ---5 packets transmitted, 5 packets received, 0% packet loss
ping mpls rsvp (Echo Reply with Error Code)
user@host> ping mpls rsvp test2 !!xxx--- lsping statistics ---5 packets transmitted, 2 packets received, 60% packet loss3 packets received with error status, not counted as received.
ping mpls rsvp detail
user@host> ping mpls rsvp to-green detail Request for seq 1, to interface 67, labels <100095, 0, 0> Reply for seq 1, return code: Egress-ok Request for seq 2, to interface 67, labels <100095, 0, 0> Reply for seq 2, return code: Egress-ok
ping mpls rsvp multipoint egress detail count
user@host>ping mpls rsvp sample-lsp multipoint egress 192.168.1.3 detail count 1 Request for seq 1, to interface 70, label 299952 Request for seq 1, to interface 70, no label stack. Request for seq 1, to interface 67, no label stack. Reply for seq 1, egress 192.168.1.3, return code: Egress-ok, time: 0.242 ms Local transmit time: 1205310695s 215737us Remote receive time: 1205310695s 215979us --- lsping, egress 192.168.1.3 statistics --- 1 packets transmitted, 1 packets received, 0% packet loss
ping mpls rsvp multipoint detail count
user@host>ping mpls rsvp sample-lsp multipoint detail count 1 Request for seq 1, to interface 70, label 299952 Request for seq 1, to interface 70, no label stack. Request for seq 1, to interface 67, no label stack. Reply for seq 1, return code: Unknown TLV, time: 9.877 m Local transmit time: 1205310615s 347317us Remote receive time: 1205310615s 357194us Reply for seq 1, egress 192.168.1.3, return code: Egress-ok, time: 0.351 ms Local transmit time: 1205310615s 347262us Remote receive time: 1205310615s 347613us Reply for seq 1, egress 192.168.1.13, return code: Egress-ok, time: 0.301 ms Local transmit time: 1205310615s 347167us Remote receive time: 1205310615s 347468us Timeout for seq 1, egress 192.168.1.1 Timeout for seq 1, egress 192.168.1.4 Timeout for seq 1, egress 192.168.1.14 --- lsping, egress 192.168.1.1 statistics --- 1 packets transmitted, 0 packets received, 100% packet loss --- lsping, egress 192.168.1.3 statistics --- 1 packets transmitted, 1 packets received, 0% packet loss --- lsping, egress 192.168.1.4 statistics --- 1 packets transmitted, 0 packets received, 100% packet loss --- lsping, egress 192.168.1.13 statistics --- 1 packets transmitted, 1 packets received, 0% packet loss --- lsping, egress 192.168.1.14 statistics --- 1 packets transmitted, 0 packets received, 100% packet loss
ping mpls rsvp destination detail count size
user@host>ping mpls rsvp chaser-access destination 192.168.0.1 detail count 1 size 4468
Request for seq 1, to interface 88, label 299984, packet size 4468
Reply for seq 1, return code: Egress-ok, time: 44.804 ms
Local transmit time: 2009-03-30 22:05:02 CEST 408.629 ms
Remote receive time: 2009-03-30 22:05:02 CEST 453.433 ms
--- lsping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
ping mpls rsvp destination detail sweep size
user@router> ping mpls rsvp chaser-access destination 192.168.0.1 detail sweep size 4500
Request for seq 1, to interface 86, no label stack., packet size 100
Reply for seq 1, return code: Egress-ok, time: -39.264 ms
Local transmit time: 2009-04-24 14:05:40 CEST 541.423 ms
Remote receive time: 2009-04-24 14:05:40 CEST 502.159 ms
Request for seq 2, to interface 86, no label stack., packet size 2300
Reply for seq 2, return code: Egress-ok, time: -38.179 ms
Local transmit time: 2009-04-24 14:05:41 CEST 544.240 ms
Remote receive time: 2009-04-24 14:05:41 CEST 506.061 ms
Request for seq 3, to interface 86, no label stack., packet size 4500
Timeout for seq 3
Request for seq 4, to interface 86, no label stack., packet size 3400
Reply for seq 4, return code: Egress-ok, time: -37.545 ms
Local transmit time: 2009-04-24 14:05:45 CEST 549.953 ms
Remote receive time: 2009-04-24 14:05:45 CEST 512.408 ms
Request for seq 5, to interface 86, no label stack., packet size 3952
Reply for seq 5, return code: Egress-ok, time: -37.176 ms
Local transmit time: 2009-04-24 14:05:46 CEST 555.881 ms
Remote receive time: 2009-04-24 14:05:46 CEST 518.705 ms
Request for seq 6, to interface 86, no label stack., packet size 4228
Reply for seq 6, return code: Egress-ok, time: -36.962 ms
Local transmit time: 2009-04-24 14:05:47 CEST 561.809 ms
Remote receive time: 2009-04-24 14:05:47 CEST 524.847 ms
Request for seq 7, to interface 86, no label stack., packet size 4368
Reply for seq 7, return code: Egress-ok, time: -36.922 ms
Local transmit time: 2009-04-24 14:05:48 CEST 568.738 ms
Remote receive time: 2009-04-24 14:05:48 CEST 531.816 ms
Request for seq 8, to interface 86, no label stack., packet size 4440
Reply for seq 8, return code: Egress-ok, time: -36.855 ms
Local transmit time: 2009-04-24 14:05:49 CEST 575.669 ms
Remote receive time: 2009-04-24 14:05:49 CEST 538.814 ms
Request for seq 9, to interface 86, no label stack., packet size 4476
Timeout for seq 9
Request for seq 10, to interface 86, no label stack., packet size 4460
Reply for seq 10, return code: Egress-ok, time: -36.906 ms
Local transmit time: 2009-04-24 14:05:53 CEST 584.382 ms
Remote receive time: 2009-04-24 14:05:53 CEST 547.476 ms
Request for seq 11, to interface 86, no label stack., packet size 4480
Timeout for seq 11
Request for seq 12, to interface 86, no label stack., packet size 4472
Timeout for seq 12
Request for seq 13, to interface 86, no label stack., packet size 4468
Reply for seq 13, return code: Egress-ok, time: -36.943 ms
Local transmit time: 2009-04-24 14:06:00 CEST 594.884 ms
Remote receive time: 2009-04-24 14:06:00 CEST 557.941 ms
Request for seq 14, to interface 86, no label stack., packet size 4476
Timeout for seq 14
Request for seq 15, to interface 86, no label stack., packet size 4472
Timeout for seq 15
--- lsp ping sweep result---
Maximum Transmission Unit (MTU) is 4468 bytes
Release Information
Command introduced before Junos OS Release 7.4.
The egress and multipoint options were
introduced in Junos OS Release 9.2.
The size and sweep options were introduced
in Junos OS Release 9.6.
The dynamic-bypass and manual-bypass options
were introduced in Junos OS Release 10.2.