Operational commands

dns

Syntax

dns target-addr dns-name name-server ip-address [source ip-address] [count send-count] [timeout timeout] [interval interval] [record-type {ipv4-a-record | ipv6-aaaa-record}]

Context

oam

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command performs DNS name resolution. If ipv4-a-record is specified, DNS names are queried for A-records only.

Parameters

ip-address

Specifies the IP address of the primary DNS server. IPv6 address is only supported on 7210 SAS-D and 7210 SAS-Dxp.

Values

ipv4-address:	a.b.c.d
ipv6-address:	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x:	[0 .. FFFF]H
	d:	[0 .. 255]D

timeout timeout

Specifies the timeout parameter in seconds, expressed as a decimal integer. This value is used to override the default timeout value and is the amount of time that the router waits for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes the message response is not received. Any response received after the request times out is silently discarded.

Default: 5

Values: 1 to 120

interval interval

Specifies the interval parameter in seconds, expressed as a decimal integer. This parameter is used to override the default request message send interval and defines the minimum amount of time that must expire before the next message request is sent.

If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds, and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.

Default: 1

Values: 1 to 10

record-type

Specifies a record type. The IPv6 address is only supported on 7210 SAS-D and 7210 SAS-Dxp.

Values

ipv4-a-record — Keyword for a record specific mapping a host name to an IPv4 address.

ipv6-aaaa-record— Keyword for a record specific to the Internet class that stores a single IPv6 address.

ping

Syntax

ping [ip-address | dns-name] [rapid | detail] [ttl time-to-live] [tos type-of-service] [size bytes] [pattern pattern] [source ip-address | dns-name] [interval seconds] [{next-hop ip-address} | {interface interface-name} | bypass-routing] [count requests] [do-not-fragment] [router router-instance | service-name service-name] [timeout timeout]

Context

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command verifies the reachability of a remote host.

Parameters

ip-address

Specifies the far-end IP address to which to send the icmp-ping request message in dotted-decimal notation. The IPv6 address is only supported on the 7210 SAS-D and 7210 SAS-Dxp.

Values

ipv4-address:	a.b.c.d
ipv6-address:	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x:	[0 to FFFF]H
	d:	[0 to 255]D

dns-name: Specifies the DNS name of the far-end device to which to send the icmp-ping request message, expressed as a character string.

rapid: Specifies that packets be generated as fast as possible, instead of the default 1 per second.

detail: Displays detailed information.

ttl time-to-live

Specifies the TTL value for the IP TTL, expressed as a decimal integer

Values: 1 to 128

tos type-of-service

Specifies the service type.

Values: 0 to 255

size bytes

Specifies the request packet size in bytes, expressed as a decimal integer.

Values: 0 to 16384

pattern pattern

Specifies that the date portion in a ping packet is filled with the pattern value specified. If not specified, position information is filled instead.

Values: 0 to 65535

source ip-address

Specifies the IP address to be used. IPv6 address is only supported on 7210 SAS-D and 7210 SAS-Dxp.

Values

ipv4-address:	a.b.c.d
ipv6-address:	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x:	[0 to FFFF]H
	d:	[0 to 255]D

router router-instance

Specifies the router name or service ID.

Values: router-name: Base

Default: Base

service-name service-name: Specifies the service name as an integer or string.

bypass-routing: Specifies whether to send the ping request to a host on a directly attached network bypassing the routing table.

interface interface-name: Specifies the name of an IP interface. The name must already exist in the config>router>interface context.

next-hop ip-address

Specifies to only display static routes with the specified next-hop IP address. The IPv6 address is only supported on 7210 SAS-D and 7210 SAS-Dxp.

Values

ipv4-address:	a.b.c.d (host bits must be 0)
ipv6-address:	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x:	[0 to FFFF]H
	d:	[0 to 255]

interval seconds

If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.

Values: 1 to 10000

count requests

Specifies the number of times to perform an OAM ping probe operation. Each OAM echo message request must either timeout or receive a reply before the next message request is sent.

Values: 1 to 100000

Default: 5

do-not-fragment: Sets the DF (Do Not Fragment) bit in the ICMP ping packet.

fc-name

Specifies the forwarding class of the MPLS echo request encapsulation.

Values: be, l2, af, l1, h2, ef, h1, nc

Default: nc

timeout seconds

Specifies to override the default timeout value and is the amount of time that the router waits for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response is not received. A ‟request timeout” message is displayed for each message request sent that expires. Any response received after the request times out is silently discarded.

Default: 5

Values: 1 to 10

traceroute

Syntax

traceroute [ip-address |dns-name] [ttl ttl] [wait milli-seconds] [no-dns] [source ip-address] [tos type-of-service] [router router-instance | service-name service-name]

Context

Global

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command determines the route to a destination address. DNS lookups of the responding hosts is enabled by default.

*A:ALA-1# traceroute 192.168.xx.xx4
traceroute to 192.168.xx.xx4, 30 hops max, 40 byte packets
 1  192.168.xx.xx4 0.000 ms  0.000 ms  0.000 ms
*A:ALA-1#

Parameters

ip-address

Specifies the far-end IP address to which to send the traceroute request message, in dotted-decimal notation. The IPv6 address is only supported on 7210 SAS-D and 7210 SAS-Dxp.

Values

ipv4-address:	a.b.c.d
ipv6-address:	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x:	[0 .. FFFF]H
	d:	[0 .. 255]D

dns-name: Specifies the DNS name of the far-end device to which to send the traceroute request message, expressed as a character string.

ttl ttl

Specifies the maximum Time-To-Live (TTL) value to include in the traceroute request, expressed as a decimal integer.

Values: 1 to 255

wait milliseconds

Specifies the time in milliseconds to wait for a response to a probe, expressed as a decimal integer.

Default: 5000

Values: 10 to 60000

no-dns

Specifies that DNS lookups of the responding hosts are not performed, only the IP addresses is printed.

Default: DNS lookups are performed

source ip-address: Specifies the source IP address to use as the source of the probe packets in dotted-decimal notation. If the IP address is not one of the interfaces on the device, an error is returned. The IPv6 address is only supported on 7210 SAS-D and 7210 SAS-Dxp.

tos type-of-service

Specifies the type-of-service (TOS) bits in the IP header of the probe packets, expressed as a decimal integer.

Values: 0 to 255

router router-name

Specifies an alphanumeric character string, up to 32 characters.

Values: Base, Management

service-name service-name: Specifies the service name as an integer or string.

lsp-ping

Syntax

lsp-ping lsp-name [path path-name]

lsp-ping bgp-label prefix ip-prefix/prefix-length [path-destination ip-address [interface if-name | next-hop ip-address]]

lsp-ping prefix ip-prefix/prefix-length [path-destination ip-address [interface if-name | next-hop ip-address]] [src-ip-address ip-address]

lsp-ping {{lsp-name [path path-name]}|{prefix ip-prefix/prefix-length}} [src-ip-address ip-address] [size octets] [ttl label-ttl] [timeout timeout] [interval interval] [fc fc-name [profile {in | out}]] [send-count send-count] {lsp-name [path path-name]} [fc fc-name] [size octets][ttl label-ttl] [send-count send-count] [timeout timeout] [interval interval]

The following options are common to all lsp-ping cases: [detail] [fc fc-name [profile in | out]] [interval interval] [send-count send-count] [size octets] [src-ip-address ip-address] [timeout timeout] [ttl label-ttl]

Context

oam

config>saa>test>type

Platforms

7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C

Description

This command performs in-band LSP connectivity tests.

The lsp-ping command performs an LSP ping using the protocol and data structures defined in RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures.

The LSP ping operation is modeled after the IP ping utility, which uses ICMP echo request and reply packets to determine IP connectivity.

In an LSP ping, the originating device creates an MPLS echo request packet for the LSP and path to be tested. The MPLS echo request packet is sent through the data plane and awaits an MPLS echo reply packet from the device terminating the LSP. The status of the LSP is displayed when the MPLS echo reply packet is received.

The lsp-ping static command performs an LSP ping using the protocol and data structures defined in RFC 4379, as extended by RFC 6426, MPLS On-Demand Connectivity Verification and Route Tracing.

The timestamp format to be sent, and to be expected when received in a PDU, is configured by the config test-oam mpls-time-stamp-format command. If RFC 4379 is selected, the timestamp is in seconds and microseconds since 1900, otherwise it is in seconds and microseconds since 1970.

Parameters

lsp-name: Specifies a name that identifies an LSP to ping. The LSP name can be up to 32 characters long.

force: Allows LSP Ping to test a path that is operationally down, including cases where MPLS-TP BFD CC/V is enabled and has taken a path down. This parameter is only allowed in the OAM context; it is not allowed for a test configured as a part of an SAA.

path path-name

Specifies the LSP path name along which to send the LSP ping request.

Values: Any path name associated with the LSP.

Default: The active LSP path.

bgp-label-prefix ip-prefix/mask: Specifies the address prefix and subnet mask of the target BGP IPv4 label route.

src-ip-address ip-addr

Specifies the source IP address. This option is used when an OAM packet must be generated from a different address than the node system interface address. An example is when the OAM packet is sent over an LDP LSP and the LDP LSR-ID of the corresponding LDP session to the next hop is set to an address other than the system interface address.

Values: ipv4-address: a.b.c.d

fc fc-name

Specifies the FC name. The FC and profile parameters are used to indicate the forwarding class and profile of the MPLS echo request packet.

When an MPLS echo request packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified FC and profile parameter values. The marking of the packet EXP is dictated by the LSP-EXP mappings on the outgoing interface.

When the MPLS echo request packet is received on the responding node, the FC and profile parameter values are dictated by the LSP-EXP mappings of the incoming interface.

When an MPLS echo reply packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the FC and profile parameter values determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The marking of the packet EXP is dictated by the LSP-EXP mappings on the outgoing interface. The TOS byte is not modified. The following table describes this behavior.

Table: Request packet and behavior
Node	Packet and description
cpm (sender node)	echo request packet: packet{tos=1, fc1, profile1} fc1 and profile1 are as entered by user in OAM command or default values tos1 as per mapping of {fc1, profile1} to IP precedence in network egress QoS policy of outgoing interface
Outgoing interface (sender node)	echo request packet: pkt queued as {fc1, profile1} ToS field=tos1 not remarked EXP=exp1, as per mapping of {fc1, profile1} to EXP in network egress QoS policy of outgoing interface
Incoming interface (responder node)	echo request packet: packet{tos1, exp1} exp1 mapped to {fc2, profile2} as per classification in network QoS policy of incoming interface
cpm (responder node)	echo reply packet: packet{tos=1, fc2, profile2}
Outgoing interface (responder node)	echo reply packet: pkt queued as {fc2, profile2} ToS filed= tos1 not remarked (reply inband or out-of-band) EXP=exp2, if reply is inband, remarked as per mapping of {fc2, profile2} to EXP in network egress QoS policy of outgoing interface
Incoming interface (sender node)	echo reply packet: packet{tos1, exp2} exp2 mapped to {fc1, profile1} as per classification in network QoS policy of incoming interface

The LSP-EXP mappings on the receive network interface control the mapping of the message reply back to the originating router.

Values: be, l2, af, l1, h2, ef, h1, nc

Default: be

profile {in | out}

Specifies the profile state of the MPLS echo request packet.

Default: out

size octets

Specifies the MPLS echo request packet size in octets, expressed as a decimal integer. The request payload is padded with zeros to the specified size.

Values: 1 to 9198

Default: 1

ttl label-ttl

Specifies the TTL value for the MPLS label, expressed as a decimal integer.

Values: 1 to 255

Default: 255

send-count send-count

Specifies the number of messages to send, expressed as a decimal integer. This parameter overrides the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.

Values: 1 to 100

Default: 1

time-out interval

Specifies the time-out parameter in seconds, expressed as a decimal integer. This value overrides the default timeout value and is the amount of time that the router waits for a message reply after sending the last probe for a particular test. Upon the expiration of timeout, the test is marked complete and no more packets are processed for any of those request probes.

Values: 1 to 10

Default: 5

interval interval: Specifies the interval parameter in seconds, expressed as a decimal integer. This parameter overrides the default request message send interval and defines the minimum amount of time that must expire before the next message request is sent.

path-destination ip-address: Specifies the IP address of the path destination from the range 127/8.

interface interface-name: Specifies the name of an IP interface. The name must already exist in the config>router>interface context.

next-hop ip-address

Specifies to only display static routes with the specified next-hop IP address.

Values: ipv4-address: a.b.c.d (host bits must be 0)

prefix ip-prefix/mask: Specifies the address prefix and subnet mask of the target BGP IPv4 label route.

static lsp-name: Specifies an LSP ping route using RFC 6426, MPLS On-Demand Connectivity Verification and Route Tracing.

Output

Sample output

A:DUTA# oam lsp-ping prefix 10.4.4.4/32 detail
LSP-PING 10.4.4.4/32: 80 bytes MPLS payload
Seq=1, send from intf dut1_to_dut3, reply from 10.4.4.4
       udp-data-len=32 ttl=255 rtt=5.23ms rc=3 (EgressRtr)

---- LSP 10.4.4.4/32 PING Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 5.23ms, avg = 5.23ms, max = 5.23ms, stddev = 0.000ms

===============================================================================
LDP LSR ID: 1.1.1.1
===============================================================================
Legend: U - Label In Use,  N - Label Not In Use, W - Label Withdrawn
        WP - Label Withdraw Pending, BU - Alternate For Fast Re-Route
===============================================================================
LDP Prefix Bindings
===============================================================================
Prefix              IngLbl       EgrLbl     EgrIntf/         EgrNextHop
   Peer                                     LspId
-------------------------------------------------------------------------------
10.4.4.4/32          131069N      131067     1/1/1            1.3.1.2
   3.3.3.3
10.4.4.4/32          131069U      131064       --               --
   6.6.6.6
-------------------------------------------------------------------------------
No. of Prefix Bindings: 2
===============================================================================
A:DUTA#

lsp-trace

Syntax

lsp-trace lsp-name [path path-name]

lsp-trace bgp-label prefix ip-prefix/mask [path-destination ip-address [interface if-name | next-hop ip-address]]

lsp-trace prefix ip-prefix/mask [path-destination ip-address [interface if-name | next-hop ip-address]]

The following options are common to all lsp-trace cases: [detail] [downstream-map-tlv {dsmap | ddmap | none}] [fc fc-name] [interval interval] [max-fail no-response-count] [max-ttl max-label-ttl] [min-ttl min-label-ttl] [probe-count probes-per-hop] [size octets] [src-ip-address ip-address] [timeout timeout]

Context

oam

config>saa>test>type

Platforms

7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C

Description

This command performs an LSP trace using the protocol and data structures defined in RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, and extended by RFC 6426, MPLS On-Demand Connectivity Verification and Route Tracing.

The LSP trace operation is modeled after the IP traceroute utility, which uses ICMP echo request and reply packets with increasing TTL values to determine the hop-by-hop route to a destination IP.

In an LSP trace, the originating device creates an MPLS echo request packet for the LSP to be tested with increasing values of the TTL in the outermost label. The MPLS echo request packet is sent through the data plane and awaits a TTL exceeded response or the MPLS echo reply packet from the device terminating the LSP. The devices that reply to the MPLS echo request packets with the TTL exceeded and the MPLS echo reply are displayed.

The downstream mapping TLV is used in lsp-trace to provide a mechanism for the sender and responder nodes to exchange and validate interface and label stack information for each downstream hop in the path of the LDP FEC or an RSVP LSP, or a BGP IPv4 label route.

The following downstream mapping TLVs are supported: the original Downstream Mapping (DSMAP) TLV, defined in RFC 4379; and the new Downstream Detailed Mapping (DDMAP) TLV, defined in RFC 6424.

When the responder node has multiple equal cost next hops for an LDP FEC or a BGP label IPv4 prefix, it replies in the Downstream Mapping TLV with the downstream information for each outgoing interface which is part of the ECMP next-hop set for the prefix. The downstream mapping TLV can further be used to exercise a specific path of the ECMP set using the path-destination option.

Some restrictions apply when using this feature on 7210 SAS nodes, see LSP diagnostics: LSP ping and trace.

Parameters

lsp-name: Specifies a name, up to 32 characters, that identifies an LSP to ping.

path path-name

Specifies the LSP path name along which to send the LSP trace request.

Default: the active LSP path

size octets

Specifies the size in octets, expressed as a decimal integer, of the MPLS echo request packet, including the IP header but not the label stack. The request payload is padded with zeros to the specified size. An OAM command is not failed if the user entered a size lower than the minimum required to build the packet for the echo request message. The payload is automatically padded to meet the minimum size.

Values: 104 to 9198

Default: 1

src-ip-address ip-addr

Specifies the source IP address. This option is used when an OAM packet must be generated from a different address than the node system interface address. An example is when the OAM packet is sent over an LDP LSP and the LDP LSR-ID of the corresponding LDP session to the next-hop is set to an address other than the system interface address.

Values: ipv4-address: a.b.c.d

min-ttl min-label-ttl

Specifies the minimum TTL value in the MPLS label for the LSP trace test, expressed as a decimal integer.

Values: 1 to 255

Default: 1

max-ttl max-label-ttl

Specifies the maximum TTL value in the MPLS label for the LDP treetrace test, expressed as a decimal integer.

Values: 1 to 255

Default: 30

max-fail no-response-count

Specifies the maximum number of consecutive MPLS echo requests, expressed as a decimal integer that do not receive a reply before the trace operation fails for a given TTL.

Values: 1 to 255

Default: 5

probes-per-hop

Specifies the number of messages to send, expressed as a decimal integer. The send-count parameter is used to override the default number of message requests sent. Each message request must either timeout or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.

Values: 1 to 10

Default: 1

timeout timeout

Specifies the timeout parameter in seconds, expressed as a decimal integer. This value is used to override the default timeout value and is the amount of time that the router waits for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response is not received. A ‟request timeout” message is displayed by the CLI for each message request sent that expires. Any response received after the request times out is silently discarded.

Values: 1 to 60

Default: 3

interval interval

Values: 1 to 10

Default: 1

fc fc-name

Specifies the fc and profile parameters used to indicate the forwarding class and profile of the MPLS echo request packet.

When an MPLS echo request packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc and profile parameter values. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface.

When the MPLS echo request packet is received on the responding node, The fc and profile parameter values are dictated by the LSP-EXP mappings of the incoming interface.

When an MPLS echo reply packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the fc and profile parameter values determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface. The TOS byte is not modified. Table: Request packet and behavior summarizes this behavior:

Values: be, l2, af, l1, h2, ef, h1, nc

Default: be

profile {in | out}

Specifies the profile state of the MPLS echo request packet.

Default: out

path-destination ip-address: Specifies the IP address of the path destination from the range 127/8.

interface interface-name: Specifies the name of an IP interface. The name must already exist in the config>router>interface context.

downstream-map-tlv {dsmap | ddmap | none}

Specifies which format of the downstream mapping TLV to use in the LSP trace packet. The DSMAP TLV is the original format in RFC 4379. The DDMAP is the new enhanced format specified in RFC 6424. The user can also choose not to include the downstream mapping TLV by entering the value none. In addition, the DSMAP/DDMAP TLV is only included in the echo request message if the egress interface is either a numbered IP interface, or an unnumbered IP interface.

Default: Inherited from global configuration of downstream mapping TLV in option mpls-echo-request-downstream-map {dsmap | ddmap}.

Output

The following output is an example of LSP trace information.

Sample output

*A:Dut-A# oam lsp-trace prefix 10.20.1.6/32 downstream-map-tlv ddmap path-
destination 127.0.0.1 detail lsp-trace to 10.20.1.6/
32: 0 hops min, 0 hops max, 152 byte packets
1  10.20.1.2  rtt=3.44ms rc=8(DSRtrMatchLabel) rsc=1 
     DS 1: ipaddr=127.0.0.1 ifaddr=0 iftype=ipv4Unnumbered MRU=1500 
           label[1]=131070 protocol=3(LDP)
2  10.20.1.4  rtt=4.65ms rc=8(DSRtrMatchLabel) rsc=1 
     DS 1: ipaddr=127.0.0.1 ifaddr=0 iftype=ipv4Unnumbered MRU=1500 
           label[1]=131071 protocol=3(LDP)
3  10.20.1.6  rtt=7.63ms rc=3(EgressRtr) rsc=1 *A:Dut-A# 

*A:Dut-C# oam lsp-trace "p_1" detail
lsp-trace to p_1: 0 hops min, 0 hops max, 116 byte packets
1  10.20.1.2  rtt=3.46ms rc=8(DSRtrMatchLabel)
     DS 1: ipaddr 10.20.1.4 ifaddr 3 iftype 'ipv4Unnumbered' MRU=1500 label=131071 p
roto=4(RSVP-TE)
2  10.20.1.4  rtt=3.76ms rc=8(DSRtrMatchLabel)
     DS 1: ipaddr 10.20.1.6 ifaddr 3 iftype 'ipv4Unnumbered' MRU=1500 label=131071 p
roto=4(RSVP-TE)
3  10.20.1.6  rtt=5.68ms rc=3(EgressRtr)
*A:Dut-C#

lsp-trace over a numbered IP interface

A:DUTA#
A:DUTA# oam lsp-trace prefix 10.5.5.5/32 detail
lsp-trace to 10.5.5.5/32: 0 hops min, 0 hops max, 104 byte packets
1  6.6.6.6  rtt=2.45ms rc=8(DSRtrMatchLabel)
     DS 1: ipaddr=10.6.5.1 ifaddr=10.6.5.1 iftype=ipv4Numbered MRU=1564 label=131071
 p
roto=3(LDP)
2  5.5.5.5  rtt=4.77ms rc=3(EgressRtr)
A:DUTA#

lsp-trace over an unnumbered IP interface

*A:Dut-A# oam lsp-trace prefix 10.20.1.6/32 downstream-map-tlv ddmap path-
destination 127.0.0.1 detail lsp-trace to 10.20.1.6/
32: 0 hops min, 0 hops max, 152 byte packets
1  10.20.1.2  rtt=3.44ms rc=8(DSRtrMatchLabel) rsc=1 
     DS 1: ipaddr=127.0.0.1 ifaddr=0 iftype=ipv4Unnumbered MRU=1500 
           label[1]=131070 protocol=3(LDP)
2  10.20.1.4  rtt=4.65ms rc=8(DSRtrMatchLabel) rsc=1 
     DS 1: ipaddr=127.0.0.1 ifaddr=0 iftype=ipv4Unnumbered MRU=1500 
           label[1]=131071 protocol=3(LDP)
3  10.20.1.6  rtt=7.63ms rc=3(EgressRtr) rsc=1 *A:Dut-A#

Operational commands

shutdown

Syntax

Context

Platforms

Description

shutdown

Syntax

Context

Platforms

Description

shutdown

Syntax

Context

Platforms

Description

dns

Syntax

Context

Platforms

Description

Parameters

ping

Syntax

Context

Platforms

Description

Parameters

traceroute

Syntax

Context

Platforms

Description

Parameters

lsp-ping

Syntax

Context

Platforms

Description

Parameters

Output

lsp-trace

Syntax

Context

Platforms

Description

Parameters

Output