[no] shutdown
config>saa>test
Supported on all 7210 SAS platforms as described in this document.
This command shuts down a test. To modify an existing test it must first be shut down. When a test is created it is in shutdown mode until a no shutdown command is executed.
A shutdown can only be performed if a test is not executing at the time the command is entered.
The no form of this command sets the state of the test to operational.
[no] shutdown
config>test-oam>ldp-treetrace
config>test-oam>twamp>server
config>test-oam>twamp>server>prefix
Supported on all 7210 SAS platforms as described in this document
This command suspends the background process running the LDP ECMP OAM tree discovery and path probing features. The configuration is not deleted.
The no form of this command enables the background process.
[no] shutdown
config>oam-pm>bin-group
config>oam-pm>session>ethernet>dmm
config>oam-pm>session>ethernet>slm
config>oam-pm>session>ip>twamp-light
config>oam-pm>session>measurement-interval>event-mon
config>saa>test
config>test-oam>ldp-treetrace
config>test-oam>mpls-dm
config>test-oam>twamp>server
config>test-oam>twamp>server>prefix
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.
The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
Entities are created in the administratively down (shutdown) state. When a no shutdown command is entered, the entity becomes administratively up and then tries to enter the operationally up state.
The no form of this command administratively enables the entity.
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}]
oam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command performs DNS name resolution. If ipv4-a-record is specified, DNS names are queried for A-records only.
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.
Specifies the IP or IPv6 address of the primary DNS server.
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 has not been received. Any response received after the request times out is silently discarded.
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.
Specifies a record type.
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]
<GLOBAL>
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command verifies the reachability of a remote host.
Specifies the far-end IP address to which to send the sve-ping request message in dotted-decimal notation.
IPv6 is supported only for the "Management" instance of the router.
Specifies the DNS name of the far-end device to which to send the sve-ping request message, expressed as a character string.
Packets are generated as fast as possible instead of the default 1 per second.
Specifies detailed information.
Specifies the TTL value for the MPLS label, expressed as a decimal integer.
Specifies the service type.
Specifies the request packet size in bytes, expressed as a decimal integer.
Specifies that the date portion in a ping packet is filled with the pattern value specified. If not specified, position info is filled instead.
Specifies the IP address to be used.
IPv6 is supported only for the "Management" instance of the router.
Specifies the router name or service ID.
Specifies the service name as an integer or string.
Specifies whether to send the ping request to a host on a directly attached network bypassing the routing table.
Specifies the name of an IP interface. The name must already exist in the config>router>interface context.
Only displays static routes with the specified next hop IP address.
IPv6 is supported only for the "Management" instance of the router.
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.
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.
Sets the DF (Do Not Fragment) bit in the ICMP ping packet.
Specifies the forwarding class of the MPLS echo request encapsulation.
Overrides 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 has not been 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.
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]
<GLOBAL>
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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#
Specifies the far-end IP address to which to send the traceroute request message in dotted decimal notation.
IPv6 is supported only for the "Management" instance of the router.
Specifies the DNS name of the far-end device to which to send the traceroute request message, expressed as a character string.
Specifies the maximum Time-To-Live (TTL) value to include in the traceroute request, expressed as a decimal integer.
Specifies the time in milliseconds to wait for a response to a probe, expressed as a decimal integer.
When the no-dns keyword is specified, DNS lookups of the responding hosts are not performed. Only the IP addresses is printed.
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 device’s interfaces, an error is returned.
Specifies the type-of-service (TOS) bits in the IP header of the probe packets, expressed as a decimal integer.
Specifies the alphanumeric character string up to 32 characters.
Specifies the service name as an integer or string.
lsp-ping lsp-name [path path-name]
lsp-ping bgp-label prefix ip-prefix/mask [path-destination ip-address [interface if-name | next-hop ip-address]]
lsp-ping prefix ip-prefix/mask [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/mask}} [src-ip-address ip-address] [size octets] [ttl label-ttl] [timeout timeout] [interval interval] [fc fc-name] [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]
lsp-ping static lsp-name [assoc-channel ipv4|none|non-ip] [force] [dest-global-id global-id dest-node-id node-id] [path-type active | working | protect]
Options common to all lsp-ping cases: [detail] [fc fc-name] [interval interval] [send-count send-count] [size octets] [src-ip-address ip-address] [timeout timeout] [ttl label-ttl]
oam
config>saa>test>type
Supported on all 7210 SAS platforms as described in this document
This command performs in-band LSP connectivity tests.
The lsp-ping command performs an LSP ping using the protocol and data structures defined in the 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.
This command, when used with the static option, performs in-band on-demand LSP connectivity verification tests for static MPLS-TP LSPs. For other LSP types, the static option should be excluded and these are described elsewhere in this guide.
The lsp-ping static command performs an LSP ping using the protocol and data structures defined in the RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, as extended by RFC 6426, MPLS On-Demand Connectivity Verification and Route Tracing.
In MPLS-TP, the echo request and echo reply messages are always sent in-band over the LSP, either in a G-ACh channel or encapsulated as an IP packet below the LSP label.
The timestamp format to be sent, and to be expected when received in a PDU, is as 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.
Specifies the name that identifies an LSP to ping. The LSP name can be up to 32 characters.
Specifies the MPLS-TP global ID for the far end node of the LSP under test. If this is not entered, the dest-global-id is taken from the LSP context.
Specifies the MPLS-TP global ID for the far end node of the LSP under test. If this is not entered, the dest-global-id is taken from the LSP context.
Specifies the encapsulation format to use for the LSP Ping echo request and echo reply packet.
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.
The LSP path to test.
Specifies the LSP path name along which to send the LSP ping request.
Specifies the address prefix and subnet mask of the target BGP IPv4 label route.
Specifies the source IP address. This option is used when an OAM packet must be generated from a different address than the node’s 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.
Specifies the fc parameter is used to indicate the forwarding class 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 parameter value. 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 parameter value is 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 parameter value 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. The following table summarizes this behavior:
| Node | Packet and description of behavior |
|---|---|
cpm (sender node) |
echo request packet:
|
outgoing interface (sender node) |
echo request packet:
|
Incoming interface (responder node) |
echo request packet:
|
cpm (responder node) |
echo reply packet:
|
outgoing interface (responder node) |
echo reply packet:
|
Incoming interface (sender node) |
echo reply packet:
|
The LSP-EXP mappings on the receive network interface controls the mapping of the message reply back at the originating router.be
Specifies the source IP address. This parameter is used when an OAM packet must be generated from a different address than the node's system interface address. For example, 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.
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.
Specifies the TTL value for the MPLS label, expressed as a decimal integer.
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.
Specifies the time-out 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 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.
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.
Specifies the IP address of the path destination from the range 127/8.
Specifies the name of an IP interface. The name must already exist in the config>router>interface context.
Only displays static routes with the specified next hop IP address.
Specifies the address prefix and subnet mask of the target BGP IPv4 label route.
Specifies an LSP ping route using the RFC 6426, MPLS On-Demand Connectivity Verification and Route Tracing, Target FEC Stack code point Static LSP.
Specifies the launched echo request’s usage of the Associated Channel (ACH) mechanism, when testing an MPLS-TP LSP.
Specifies the source MPLS-TP global identifier of the replying node. The value is copied from the reply’s RFC 6426 Source Identifier TLV.
Specifies the target MPLS-TP Node Identifier.
Specifies the type of an MPLS TP path.
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 4.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 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]]
lsp-trace static lsp-name [assoc-channel ipv4|none|non-ip] [path-type active | working | protect]
Options 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]
oam
config>saa>test>type
Supported on all 7210 SAS platforms as described in this document
This command, when used with the static option, performs in-band on-demand LSP traceroute tests for static MPLS-TP LSPs. For other LSP types, the static option should be excluded and these are described elsewhere in this guide.
The lsp-trace static command performs an LSP trace using the protocol and data structures defined in the RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, as 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.
Two 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. More details are provided in the following DDMAP TLV sub-section.
In addition, 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.
In MPLS-TP, the echo request and echo reply messages are always sent in-band over the LSP, either in a G-ACh channel or encapsulated as an IP packet below the LSP label.
Some restrictions apply when using this feature on 7210 nodes. LSP diagnostics: LSP ping and trace
Specifies the name that identifies an LSP to ping. The LSP name can be up to 32 characters.
Specifies the LSP path name along which to send the LSP trace request.
Specifies the encapsulation format to use for the MPLS echo request and echo reply packet.
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. Note that 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.
Specifies the source IP address. This option is used when an OAM packet must be generated from a different address than the node’s 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.
Specifies the minimum TTL value in the MPLS label for the LSP trace test, expressed as a decimal integer.
Specifies the maximum TTL value in the MPLS label for the LDP treetrace test, expressed as a decimal integer.
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 specific TTL.
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.
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 has not been 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.
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.
Specifies the fc parameter used to indicate the forwarding class 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 parameter value. 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 parameter value is 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 parameter value 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. The following table summarizes this behavior:
| Node | Packet and description |
|---|---|
cpm (sender node) |
echo request packet:
|
outgoing interface (sender node) |
echo request packet:
|
Incoming interface (responder node) |
echo request packet:
|
cpm (responder node) |
echo reply packet:
|
outgoing interface (responder node) |
echo reply packet:
|
Incoming interface (sender node) |
echo reply packet:
|
Specifies the IP address of the path destination from the range 127/8.
Specifies the name of an IP interface. The name must already exist in the config>router>interface context.
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. When lsp-trace is used on a MPLS-TP LSP (static option), it can only be executed if the control-channel is set to 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. The TLV is not included if the egress interface is of type unnumbered-mpls-tp.
*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 proto=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 proto=4(RSVP-TE)
3 10.20.1.6 rtt=5.68ms rc=3(EgressRtr)
*A:Dut-C#
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 proto=3(LDP)
2 5.5.5.5 rtt=4.77ms rc=3(EgressRtr)
A:DUTA#
*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-A# oam ldp-treetrace prefix 10.20.1.6/32
ldp-treetrace for Prefix 10.20.1.6/32:
127.0.0.1, ttl = 3 dst = 127.1.0.255 rc = EgressRtr status = Done
Hops: 127.0.0.1 127.0.0.1
127.0.0.1, ttl = 3 dst = 127.2.0.255 rc = EgressRtr status = Done
Hops: 127.0.0.1 127.0.0.1
ldp-treetrace discovery state: Done
ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 2
Total number of failed traces: 0
p2mp-lsp-ping {{lsp-name p2mp-instance instance-name s2l-dest-addr ip-address…[ip-address...up to 5] [ttl label-ttl]} | {ldp p2mp-id [sender-addr ip-address] [leaf-addr ip-address…[ip-address…up to 5 ]}} [fc fc-name] [size octets] [timeout timeout] [interval interval] [detail]
oam
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-T
This command performs an in-band connectivity test for an RSVP P2MP LSP.
The echo request message is sent on the active P2MP instance and is replicated in the datapath over all branches of the P2MP LSP instance. By default, all egress LER nodes that are leaves of the P2MP LSP instance reply to the echo request message.
The user can reduce the scope of the echo reply messages by explicitly entering a list of addresses for the egress LER nodes that are required to reply. A maximum of 5 addresses can be specified in a single run of the p2mp-lsp-ping command. An LER node parses the list of egress LER addresses, and if its address is included, it replies with an echo reply message.
The display is delayed until all responses are received or the timer configured in the timeout parameter expires. Entering other CLI commands while waiting for the display is not allowed. Use control-C (^C) to stop the ping operation.
Specifies the forwarding class of the MPLS echo request packet.
When an MPLS echo request packet is generated in CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc parameter value. The LSP-EXP mappings on the outgoing interface dictate the marking of the packet EXP bits.
When the MPLS echo request packet is received on the responding node, the LSP-EXP mappings of the incoming interface determine the fc parameter value.
When an MPLS echo reply packet is generated in CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the fc parameter value determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The LSP-EXP mappings on the outgoing interface dictate the marking of the packet EXP bits.
Configures the name of the P2MP LSP instance to send the echo request, up to 32 characters.
Specifies the name for the P2MP LSP, up to 32 characters, to ping.
Specifies the egress LER system address of the S2L sub-LSP path that is being traced.
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. The OAM command does not fail if the size entered is lower than the minimum number of octets required to build the packet for the echo request message. The payload is automatically padded to meet the minimum size.
Specifies the TTL value for the MPLS label, expressed as a decimal integer.
Specifies the identifier of the LDP P2MP LSP to ping, expressed as a 32-bit integer.
Optional parameter to specify root-node address. If omitted, the system IP address is used.
Specifies the list of egress LER system addresses that are required to reply to an LSP ping echo request message.
Specifies the timeout parameter, in seconds, expressed as a decimal integer. This value is used to override the default timeout value and is the length of time that the router waits for an echo reply message from all leaves of the P2MP LSP after sending the message request message. When message timeout expires, the requesting router assumes that the missing replies are not received. Any echo reply message received after the request times out is silently discarded.
If the detail parameter is omitted, the command output provides a high-level summary of error and success codes received. If the detail parameter is specified, the command output displays a line for each replying node, similar to the output of the LSP ping for a P2P LSP.
The following sample output is an example of P2MP LSP ping information.
Sample output*A:Dut-C# oam lsp-ping A2F_3
LSP-PING A2F_3: 92 bytes MPLS payload
Total S2L configured/up/responded = 400/390/388, round-trip min/avg/max = <10/10/
11 ms
Responses based on return code:
EgressRtr(3) = 387
NoFecMapping(4) = 1
Note: Missing responses on UP S2Ls implies "request timeout"
*A:Dut-A#
*A:Dut-C# oam lsp-ping A2F_3 detail
LSP-PING A2F_3: 92 bytes MPLS payload
=============================================
S2L Info
=============================================
From Rtt ReturnCode
---------------------------------------------
10.20.1.2 <10ms EgressRtr
10.20.1.3 10ms EgressRtr
10.20.1.5 11ms EgressRtr
10.20.1.6 <10ms EgressRtr
10.20.1.7 10ms NoFecMapping
:
:
==========================================
Total S2L configured/up/responded = 400/390/388, round-trip min/avg/max
= <10/10/11 ms
Responses based on return code:
EgressRtr(3) = 387
NoFecMapping(4) = 1
*A:Dut-A#
*A:Dut-C# oam lsp-ping A2F_3 > p2mp-instance "1" s2l-dest-
address 10.20.1.5 10.20.2.6 10.20.3.7
LSP-PING A2F_3: 132 bytes MPLS payload
P2MP Instance 1, S2L Egress 10.20.1.5 S2L Egress 10.20.2.6 S2L Egress 10.20.3.7
Total S2L configured/up/responded = 400/390/4, round-trip min/avg/max = <10/10/11 ms
Responses based on return code:
EgressRtr(3) = 3
NoFecMapping(4) = 1
Note: Missing responses on UP S2Ls implies "request timeout"
*A:Dut-A#
*A:Dut-C# oam lsp-ping A2F_3 > p2mp-instance "1" s2l-dest-
address 10.20.1.5 10.20.2.6 10.20.3.7 detail
LSP-PING A2F_3: 132 bytes MPLS payload
P2MP Instance 1, S2L Egress 10.20.1.5 S2L Egress 10.20.2.6 S2L Egress 10.20.3.7
=============================================
S2L Info
=============================================
From Rtt ReturnCode
---------------------------------------------
10.20.1.2 <10ms EgressRtr
10.20.1.3 10ms EgressRtr
10.20.1.4 Timeout N/A
10.20.1.5 11ms NoFecMapping
10.20.1.6 <10ms EgressRtr
==========================================
Total S2L configured/up/responded = 400/390/4, round-trip min/avg/max
= <10/10/11 ms
Responses based on return code:
EgressRtr(3) = 3
NoFecMapping (4) = 1
*A:Dut-A#
p2mp-lsp-trace {lsp-name [p2mp-instance instance-name] [s2l-dest-address ip-address…[ip-address…up-to-5]]} | {ldp p2mp-id}} [fc fc-name] [size octets] [max-fail no-response-count] [probe-count probes-per-hop] [min-ttl min-label-ttl] [max-ttl max-label-ttl] [timeout timeout] [interval interval] [detail]
oam
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-T
This command discovers and displays the hop-by-hop path for a source-to-leaf (S2L) sub-LSP of an RSVP P2MP LSP.
The LSP trace capability allows the user to trace the path of a single S2L path of a P2MP LSP. Its operation is similar to that of the p2mp-lsp-ping, but the sender of the echo reply request message includes the downstream mapping TLV to request the downstream branch information from a branch LSR or bud LSR. The branch LSR or bud LSR also includes the downstream mapping TLV to report the information about the downstream branches of the P2MP LSP. An egress LER must not include this TLV in the echo response message.
The probe-count parameter operates in the same way as in LSP Trace on a P2P LSP. It represents the maximum number of probes sent per TTL value before giving up on receiving the echo reply message. If a response is received from the traced node before reaching maximum number of probes, no more probes are sent for the same TTL. The sender of the echo request increments the TTL and uses the information it received in the downstream mapping TLV to start sending probes to the node downstream of the last node which replied. This continues until the egress LER for the traced S2L path replied.
Similar to the p2mp-lsp-ping command, an LSP trace probe results in all egress LER nodes eventually receiving the echo request message, but only the traced egress LER node replies to the last probe.
Any branch LSR node or bud LSR node in the P2MP LSP tree may receive a copy of the echo request message with the TTL in the outer label expiring at this node. However, only a branch LSR or bud LSR that has a downstream branch over which the traced egress LER is reachable responds.
When a branch LSR or bud LSR responds, it sets the global return code in the echo response message to RC=14, ‟See DDMAP TLV for Return Code and Return Sub-Code” and the return code in the DDMAP TLV corresponding to the outgoing interface of the branch used by the traced S2L path to RC=8, ‟Label switched at stack-depth <RSC>”.
Specifies the forwarding class of the MPLS echo request packet.
When an MPLS echo request packet is generated in CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc parameter value. The LSP-EXP mappings on the outgoing interface dictate the marking of the packet EXP bits.
When the MPLS echo request packet is received on the responding node, the LSP-EXP mappings of the incoming interface dictate the marking of the packet EXP bits.
When an MPLS echo reply packet is generated in CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the fc parameter value determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The LSP-EXP mappings on the outgoing interface dictate the marking of the packet EXP bits.
Specifies the minimum amount of time, in seconds, that must expire before the next echo request message is sent. The parameter overrides the default echo request message send interval.
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 an echo reply message corresponding to the outstanding message request.
Specifies the identifier for a LDP P2MP LSP to ping, expressed as a 32-bit integer.
Specifies the name of an P2MP LSP to ping, up to 32 characters.
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 specific TTL.
Specifies the maximum TTL value in the MPLS label for the LSP trace test, expressed as a decimal integer.
Specifies the minimum TTL value in the MPLS label for the LSP trace test, expressed as a decimal integer.
Specifies the name, up to 32 characters, of the specific instance of the P2MP LSP to send the echo request.
Specifies the number of LSP trace echo request messages to send per TTL value.
Specifies the egress LER system address of the S2L sub-LSP path that is being traced.
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. The OAM command is not failed if the user enters 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.
Specifies the length of time, in seconds, expressed as a decimal integer, that the router waits for an echo reply message from all leaves of the P2MP LSP after sending the message request message. This value overrides the default timeout value. When the message timer expires, the requesting router assumes that the missing replies are not received. Any echo reply message received after the request times out is silently discarded.
If the detail parameter is omitted, the command output provides a high-level summary of error and success codes received. If the detail parameter is specified, the command output displays a line for each replying node, similar to the output of the LSP ping for a P2P LSP.
The following sample output is an example of P2MP LSP trace information.
Sample output*A:Dut-C# oam p2mp-lsp-trace "p2mp_1" p2mp-instance "1" s2l-dest-
address 10.20.1.5 detail
P2MP LSP p2mp_1: 132 bytes MPLS payload
P2MP Instance 1, S2L Egress 10.20.1.5
1 10.20.1.1 rtt=3.78 ms rc=8(DSRtrMatchLabel)
DS 1: ipaddr 10.20.1.2 iftype 'ipv4Unnumbered' ifaddr 2 MRU=1500 label=131060 p
roto=4(RSVP-TE) B/E flags:0/0
2 10.20.1.2 rtt=3.54 ms rc=8(DSRtrMatchLabel)
DS 1: ipaddr 10.20.1.4 iftype 'ipv4Unnumbered' ifaddr 3 MRU=1500 label=131061 p
roto=4(RSVP-TE) B/E flags:0/0
3 10.20.1.5 rtt=5.30 ms rc=5(DSMappingMismatched)
*A:Dut-A#