close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

ping mpls segment routing spring-te

date_range 19-Nov-23

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
ping mpls segment-routing spring-te
<egress-ip (active | color |  count | detail | exp | instance | logical-system | secondary | segment-list | size | skip-fec-validation  | source | sweep | tunnel-source) >
<label-stack ( detail | egress | labels | logical-system | nexthop-address | nexthop-interface ) >
<source-routing-path ( active | color | count | detail | egress-ip | exp | instance | logical-system | secondary | segment-list | size | skip-fec-validation | source | sweep | tunnel-source>

Description

Check the operability of MPLS segment routing label-switched path (LSP) connections added by segment routing traffic-engineered (SPRING-TE) protocol. Type Ctrl+c to interrupt a ping mpls segment routing spring-te command.

Options

egress-ip

Specify to ping to or install IP address to use when sending probes.

active	Specify to use the forwarding path or nexthops from the RIB table.
color	Specify the color identifier for the tunnel end-point. Range: 1 through 4294967295
count `count`	(Optional) Number of ping requests to send. If `count` is not specified, five ping requests are sent. Range: 1 through 1000000 Default: 5
detail	(Optional) Display detailed output.
exp `exp`	(Optional) Specify the class of service to use when sending probes. Range: 0 through 7
instance `routing-instance-name`	(Optional) Allows you to ping a combination of the routing instance and forwarding equivalence class (FEC) associated with an LSP.
`logical-system logical-system-name`	(Optional) Specify the name of the logical system.
`secondary`	Specify to use configured secondary segment list for the given segment routing path.
`segment-list`	Specify the segment list to use when sending probes.
size `bytes`	(Optional) Size of the LSP ping request packet (`88` through `65468` bytes). Packets are 4-byte aligned. For example, If you enter a size of 89, 90, 91, or 92, the router or switch uses a size value of 92 bytes. If you enter a packet size that is smaller than the minimum size, an error message is displayed reminding you of the 88-byte minimum.
`skip-fec-validation`	Specify to skip forwarding equivalence class (FEC) validation or use NIL FEC.
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 (`lo.0`).
sweep	(Optional) Automatically determine the size of the maximum transmission unit (MTU).
tunnel-source	Specify the source protocol used to create tunnel.

label-stack

Specify label stack for ping packets. This option works only if you do a minimum configuration of source-packet-routing at the [edit protocols] hierarchy level.

detail	(Optional) Display detailed output.
egress	Specify the egress IP address.
labels	Specify the labels in label stack. Range: 16 through 1048575
logical-system `logical-system-name`	(Optional) Specify the name of the logical system.
nexthop-address `address`	Specify the nexthop IP address for the ping packet.
nexthop-interface `interface`	Specify the outgoing interface for the ping packet.

source-routing-path

Specify ping source path routing to use when sending probes.

active	Specify to use the forwarding path or nexthops from the RIB table.
color	Specify the color identifier for the tunnel end-point. Range: 1 through 4294967295
count `count`	(Optional) Number of ping requests to send. If `count` is not specified, five ping requests are sent. Range: 1 through 1000000 Default: 5
detail	(Optional) Display detailed output.
egress-ip
exp `exp`	(Optional) Specify the class of service to use when sending probes. Range: 0 through 7
instance `routing-instance-name`	(Optional) Allows you to ping a combination of the routing instance and forwarding equivalence class (FEC) associated with an LSP.
`logical-system logical-system-name`	(Optional) Specify the name of the logical system.
`secondary`	Specify to use configured secondary segment list for the given segment routing path.
`segment-list`	Specify the segment list to use when sending probes.
size `bytes`	(Optional) Size of the LSP ping request packet (`88` through `65468` bytes). Packets are 4-byte aligned. For example, If you enter a size of 89, 90, 91, or 92, the router or switch uses a size value of 92 bytes. If you enter a packet size that is smaller than the minimum size, an error message is displayed reminding you of the 88-byte minimum.
`skip-fec-validation`	Specify to skip forwarding equivalence class (FEC) validation or use NIL FEC.
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 (`lo.0`).
sweep	(Optional) Automatically determine the size of the maximum transmission unit (MTU).
tunnel-source	Specify the source protocol used to create tunnel.

Additional Information

Note:

With segment-list option, valid tunnel-source (source protocol used to create tunnel) is only static.

Note:

segment-list option is not present when tunnel-source is BGP SR-TE since BGP SR-TE does not have named segment list.

Note:

With source-routing-path name, valid tunnel-source are PCEP and static.

Note:

With tunnel-source as PCEP, secondary option is not valid as PCEP always sends one primary LSP.

Note:

FEC validation is performed for ping mpls segment-routing spring-te by default.

Note:

FEC validation is supported when segment-routing traffic-engineering (SR-TE) tunnel has IGP labels (OSPF and IS-IS) only. For all the other labels (for example, static, LDP, RSVP, etc.), you can use skip-fec-validation option.

Note:

For a combination of egress-ip and color options, valid tunnel-source are static and BGP SR-TE.

Note:

ping mpls segment-routing spring-te command with label-stack option is supported in operational mode only. It is not supported in configuration mode.

Note:

Parallel SID, binding SID, LDP over SR-TE is not supported.

Note:

ping mpls segment-routing spring-te command with label-stack option adds explicit null label at the bottom of the label stack for interoperability. You can include NIL FEC for label “0” or “router alert label” per OAM standard.

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 error codes are not counted in the received packets count. They are accounted for separately.

Sample Output

ping mpls segment-routing spring-te
ping mpls segment-routing spring-te (label-stack)
ping mpls segment-routing spring-te (source-routing-path) (No FEC validation)
ping mpls segment-routing spring-te (source-routing-path) (FEC validation)
ping mpls segment-routing spring-te (egress-ip) (No FEC validation)
ping mpls segment-routing spring-te (egress-ip) (FEC validation)