A shutdown can only be performed if a test is not executing at the time the command is entered.
Use the no form of the command to set the state of the test to operational.
Use the no form of the command to enable the background process.
dns target-addr dns-name name-server
ip-address [source
ip-address] [send-count
send-count] [timeout
timeout] [interval
interval] [record-type
{ipv4-a-record | ipv6-aaaa-record
}]
This command performs DNS name resolution. If ipv4-a-record is specified, dns-names are queried for A-records only. If ipv6-aaaa-record is specified, AAAA-records are queried first, and if a successful reply is not received, the dns-server is queried for A-records.
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.
The IP or IPv6 address of the primary DNS server.
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 will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be received. Any response received after the request times out will be silently discarded.
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, then 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
|
ipv4-a-record — A record specific mapping a host name to an IPv4 address. ipv6-aaaa-record — A record specific to the Internet class that stores a single IPv6 address.
|
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] [timeout
timeout]
|
Values
|
ipv4-address: a.b.c.dipv6-address: x:x:x:x:x:x:x:x[-interface]
x:x:x:x:x:x:d.d.d.d[-interface]
x: [0 — FFFF]H
d: [0 — 255]D
interface: 32 characters maximum, mandatory for link local
addresses
|
|
Values
|
router-name: Base , management
service-id: 1 — 2147483647
|
Overrides the default timeout value and is the amount of time that the router will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be 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 will be silently discarded.
traceroute [ip-address |dns-name] [ttl
ttl] [wait
milli-seconds] [no-dns
] [source
ip-address] [tos type-of-service] [router
router-instance]
*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#
When the no-dns keyword is specified, DNS lookups of the responding hosts will not be performed
, only the IP addresses will be printed.
p2mp-lsp-ping {lsp-name [p2mp-instance
instance-name [s2l-dest-address
ip-address [...(upto 5 max)]]] [ttl
label-ttl]} [fc
fc-name [profile
{in
|out
}]] [size
octets] [timeout
timeout] [detail
]
p2mp-lsp-ping {ldp
p2mp-identifier [sender-addr
ip-address] [leaf-addr
ip-address[...up-to-5 max]]} [fc
fc-name [profile
{in
|out
}]] [size
octets] [timeout
timeout] [detail]
p2mp-lsp-ping {ldp-ssm source
ip-address group
mcast-address [sender-addr
ip-address] [leaf-addr
ip-address [...up-to-5 max]]} [fc
fc-name [profile
{in
|out
}]] [size
octets] [timeout
timeout] [detail
]
LDP P2MP generic-identifier along with source IP address of the head-end node can be used to uniquely identify LDP P2MP LSP in a network. LDP p2mp-identifier is a mandatory parameter to test LSP ping. LDP P2MP identifier specified to configure a tunnel-interface on head-end node must be used as
p2mp-identifier to test a particular LSP.
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, then the timestamp is in seconds and microseconds since 1900, otherwise it is in seconds and microseconds since 1970.
leaf-addr ip-address [ip-address up to 5 max]
|
Values
|
source ip-address
group ip-address
|
p2mp-lsp-trace lsp-name p2mp-instance
instance-name s2l-dest-address
ip-address... [fc
fc-name [profile
{in
| out
}]] [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
]
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, then the timestamp is in seconds and microseconds since 1900, otherwise it is in seconds and microseconds since 1970.
*A:Dut-C# oam p2mp-lsp-trace "p2mp_1" p2mp-instance "1" s2l-dest-address 10.20.1.
10.20.1.4 10.20.1.5 10.20.1.6
*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 proto=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 proto=4(RSVP-TE) B/E flags:0/0
3 10.20.1.5 rtt=5.30 ms rc=5(DSMappingMismatched)
Probe returned multiple responses. Result may be inconsistent.
*A:Dut-C#
atm-ping port-id: vpi/vci [end-to-end | segment] [dest destination-id] [send-count send-count] [timeout timeout] [interval seconds]
|
Values
|
port-id slot/mda/port
aps-id aps-group-id
aps keyword
group-id 1 — 64
vpi 0 — 4095 (NNI)
0 — 255 (UNI)
vci 1, 2, 5 — 65535
|
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.
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 will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be received. Any response received after the request times out will be silently discarded.
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, then 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.
ancp {subscriber
sub-ident-string | ancp-string
ancp-string} loopback
[count
count] [timeout
seconds] [alarm
]
ancp subscriber sub-ident-string loopback
[send-count
send-count] [timeout
seconds] [alarm
]
sdp-mtu orig-sdp-id size-inc
start-octets end-octets [step
step-size] [timeout
seconds] [interval
seconds]
Performs MTU Path tests on an SDP to determine the largest path-mtu supported on an SDP. The size-inc parameter can be used to easily determine the
path-mtu of a given SDP-ID. The forwarding class is assumed to be Best-Effort Out-of-Profile. The message reply is returned with IP/GRE encapsulation from the far-end router. OAM request messages sent within an IP/GRE SDP must have the ‘DF’ IP header bit set to 1 to prevent message fragmentation.
To terminate an
sdp-mtu in progress, use the CLI break sequence <Ctrl-C>.
SDP Path MTU tests can be performed using the sdp-mtu size-inc keyword
to easily determine the
path-mtu of a given SDP-ID. The forwarding class is assumed to be Best-Effort Out-of-Profile. The message reply is returned with IP/GRE encapsulation from the far-end router.
With each OAM Echo Request sent using the size-inc parameter, a response line is displayed as message output. The path MTU test displays incrementing packet sizes, the number sent at each size until a reply is received and the response message.
The sdp-id to be used by
sdp-ping, expressed as a decimal integer. The far-end address of the specified
sdp-id is the expected
responder-id within each reply received. The specified
sdp-id defines the encapsulation of the SDP tunnel encapsulation used to reach the far end. This can be IP/GRE or MPLS. If
orig-sdp-id is invalid or administratively down or unavailable for some reason, the SDP echo request message is not sent and an appropriate error message is displayed (once the
interval timer expires, sdp-ping will attempt to send the next request if required).
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 will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be 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 will be silently discarded.
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, then 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.
*A:Dut-A# oam sdp-mtu 1201 size-inc 512 3072 step 256
Size Sent Response
----------------------------
512 . Success
768 . Success
1024 . Success
1280 . Success
1536 . Success
1792 . Success
2048 . Success
2304 . Success
2560 . Success
2816 . Success
3072 . Success
Maximum Response Size: 3072
*A:Dut-A#
svc-ping ip-address [service
service-id] [local-sdp
] [remote-sdp
]
The svc-ping command accepts a far-end IP address and a
service-id for local and remote service testing. The following information can be determined from
svc-ping:
Unlike sdp-ping, only a single message will be sent per command; no count nor interval parameter is supported and round trip time is not calculated. A timeout value of 10 seconds is used before failing the request. The forwarding class is assumed to be Best-Effort Out-of-Profile
To terminate a svc-ping in progress, use the CLI break sequence <Ctrl-C>.
|
|
|
|
|
|
The result of the svc-ping request message.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The type of service being tested. If service-id does not exist locally, N/A is displayed.
|
Epipe, Ipipe, Fpipe, Apipe
|
|
|
|
|
|
|
|
|
|
|
The local administrative state of service-id. If the service does not exist locally, the administrative state will be Non-Existent.
|
|
|
|
|
|
|
|
The local operational state of service-id. If the service does not exist locally, the state will be N/A.
|
|
|
|
|
|
|
|
The remote type of service being tested. If service-id does not exist remotely, N/A is displayed.
|
Epipe, Ipipe, Fpipe, Apipe
|
|
|
|
|
|
|
|
|
|
|
The remote administrative state of service-id. If the service does not exist remotely, the administrative state is Non-Existent.
|
|
|
|
|
|
|
|
The local service-mtu for service-id. If the service does not exist, N/A is displayed.
|
|
|
|
|
|
The remote service-mtu for service-id. If the service does not exist remotely, N/A is displayed.
|
|
|
|
|
|
The local customer-id associated with service-id. If the service does not exist locally, N/A is displayed.
|
|
|
|
|
|
The remote customer-id associated with service-id. If the service does not exist remotely, N/A is displayed.
|
|
|
|
|
|
The local system IP address used to terminate remotely configured SDP-ID (as the far-end address). If an IP interface has not been configured to be the system IP address, N/A is displayed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The expected source of the originator’s sdp-id from the perspective of the remote router terminating the sdp-id. If the far-end cannot detect the expected source of the ingress sdp-id or the request is transmitted outside the sdp-id, N/A is displayed.
|
|
|
|
|
|
The sdp-id used to reach the far-end IP address if sdp-path is defined. The originating sdp-id must be bound to the service-id and terminate on the far-end IP address. If an appropriate originating sdp-id is not found, Non-Existent is displayed.
|
|
|
|
|
|
Whether the Originating router used the originating sdp-id to send the svc-ping request. If a valid originating sdp-id is found, operational and has a valid egress service label, the originating router should use the sdp-id as the requesting path if sdp-path has been defined. If the originating router uses the originating sdp-id as the request path, Yes is displayed. If the originating router does not use the originating sdp-id as the request path, No is displayed. If the originating sdp-id is non-existent, N/A is displayed.
|
|
|
|
|
|
|
|
The local administrative state of the originating sdp-id. If the sdp-id has been shutdown, Admin-Down is displayed. If the originating sdp-id is in the no shutdown state, Admin-Up is displayed. If an originating sdp-id is not found, N/A is displayed.
|
|
|
|
|
|
|
|
The local operational state of the originating sdp-id. If an originating sdp-id is not found, N/A is displayed.
|
|
|
|
|
|
|
|
The local administrative state of the originating sdp-ids binding to service-id. If an sdp-id is not bound to the service, N/A is displayed.
|
|
|
|
|
|
|
|
The local operational state of the originating sdp-ids binding to service-id. If an sdp-id is not bound to the service, N/A is displayed.
|
|
|
|
|
|
|
|
The sdp-id used by the far end to respond to the svc-ping request. If the request was received without the sdp-path parameter, the responding router will not use an sdp-id as the return path, but the appropriate responding sdp-id will be displayed. If a valid sdp-id return path is not found to the originating router that is bound to the service-id, Non-Existent is displayed.
|
|
|
|
|
|
Whether the responding router used the responding sdp-id to respond to the svc-ping request. If the request was received via the originating sdp-id and a valid return sdp-id is found, operational and has a valid egress service label, the far-end router should use the sdp-id as the return sdp-id. If the far end uses the responding sdp-id as the return path, Yes is displayed. If the far end does not use the responding sdp-id as the return path, No is displayed. If the responding sdp-id is non-existent, N/A is displayed.
|
|
|
|
|
|
|
|
The administrative state of the far-end sdp-id associated with the return path for service-id. When a return path is administratively down, Admin-Down is displayed. If the return sdp-id is administratively up, Admin-Up is displayed. If the responding sdp-id is non-existent, N/A is displayed.
|
|
|
|
|
|
|
|
The operational state of the far-end sdp-id associated with the return path for service-id. When a return path is operationally down, Oper-Down is displayed. If the return sdp-id is operationally up, Oper-Up is displayed. If the responding sdp-id is non-existent, N/A is displayed.
|
|
|
|
|
|
|
|
The local administrative state of the responder’s sdp-id binding to service-id. If an sdp-id is not bound to the service, N/A is displayed.
|
|
|
|
|
|
|
|
The local operational state of the responder’s sdp-id binding to service-id. If an sdp-id is not bound to the service, N/A is displayed.
|
|
|
|
|
|
|
|
The originator’s VC-ID associated with the sdp-id to the far-end address that is bound to service-id. If the sdp-id signaling is off, originator-vc-id is 0. If the originator-vc-id does not exist, N/A is displayed.
|
|
|
|
|
|
The responder’s VC-ID associated with the sdp-id to originator-id that is bound to service-id. If the sdp-id signaling is off or the service binding to sdp-id does not exist, responder-vc-id is 0. If a response is not received, N/A is displayed.
|
|
|
|
|
|
The originating service label (VC-Label) associated with the service-id for the originating sdp-id. If service-id does not exist locally, N/A is displayed. If service-id exists, but the egress service label has not been assigned, Non-Existent is displayed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The originating egress service label state. If the originating router considers the displayed egress service label operational, Up is displayed. If the originating router considers the egress service label inoperative, Down is displayed. If the service-id does not exist or the egress service label is non-existent, N/A is displayed.
|
|
|
|
|
|
|
|
The actual responding service label in use by the far-end router for this service-id to the originating router. If service-id does not exist in the remote router, N/A is displayed. If service-id does exist remotely but the remote egress service label has not been assigned, Non-Existent is displayed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The responding egress service label state. If the responding router considers its egress service label operational, Up is displayed. If the responding router considers its egress service label inoperative, Down is displayed. If the service-id does not exist or the responder’s egress service label is non-existent, N/A is displayed.
|
|
|
|
|
|
|
|
The locally assigned ingress service label. This is the service label that the far-end is expected to use for service-id when sending to the originating router. If service-id does not exist locally, N/A is displayed. If service-id exists but an ingress service label has not been assigned, Non-Existent is displayed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The originator’s ingress service label state. If the originating router considers its ingress service label operational, Up is displayed. If the originating router considers its ingress service label inoperative, Down is displayed. If the service-id does not exist locally, N/A is displayed.
|
|
|
|
|
|
|
|
The assigned ingress service label on the remote router. This is the service label that the far end is expecting to receive for service-id when sending to the originating router. If service-id does not exist in the remote router, N/A is displayed. If service-id exists, but an ingress service label has not been assigned in the remote router, Non-Existent is displayed.
|
|
|
|
|
|
|
|
The assigned ingress service label source on the remote router. If the ingress service label is manually defined on the remote router, Manual is displayed. If the ingress service label is dynamically signaled on the remote router, Signaled is displayed. If the service-id does not exist on the remote router, N/A is displayed.
|
|
|
|
|
|
|
|
The assigned ingress service label state on the remote router. If the remote router considers its ingress service label operational, Up is displayed. If the remote router considers its ingress service label inoperative, Down is displayed. If the service-id does not exist on the remote router or the ingress service label has not been assigned on the remote router, N/A is displayed.
|
|
|
|
|
|
Specifies the svc-ping request message should be sent using the same service tunnel encapsulation labeling as service traffic. If
local-sdp is specified, the command attempts to use an egress
sdp-id bound to the service with the specified
far-end IP address with the VC-Label for the service. The far-end address of the specified
sdp-id is the expected
responder-id within the reply received. The
sdp-id defines the encapsulation of the SDP tunnel encapsulation used to reach the far end; this can be IP/GRE or MPLS. On originator egress, the service-ID must have an associated VC-Label to reach the far-end address of the
sdp-id and the
sdp-id must be operational for the message to be sent.
If local-sdp is not specified, the
svc-ping request message is sent with GRE encapsulation with the OAM label.
Specifies svc-ping reply message from the
far-end should be sent using the same service tunnel encapsulation labeling as service traffic.
If
remote-sdp is specified, the
far-end responder attempts to use an egress
sdp-id bound to the service with the message originator as the destination IP address with the VC-Label for the service. The
sdp-id defines the encapsulation of the SDP tunnel encapsulation used to reply to the originator; this can be IP/GRE or MPLS. On responder egress, the service-ID must have an associated VC-Label to reach the originator address of the
sdp-id and the
sdp-id must be operational for the message to be sent.
If
remote-sdp is not specified, the
svc-ping request message is sent with GRE encapsulation with the OAM label.
*A:router1> svc-ping far-end 10.10.10.10 service 101 local-sdp remote-sdp
Request Result: Sent – Reply Received
Service-ID: 101
Err Basic Info Local Remote
--- ----------------- ------ ------
__ Type: TLS TLS
__ Admin State: Up Up
__ Oper State: Up Up
__ Service-MTU: 1514 1514
__ Customer ID: 1001 1001
Err System IP Interface Info
--- -------------------------------------------------------------
Local Interface Name: “7750 SR-System-IP-Interface (Up to 32 chars)…”
__ Local IP Interface State: Up
__ Local IP Address: 10.10.10.11
__ IP Address Expected By Remote: 10.10.10.11
__ Expected Remote IP Address: 10.10.10.10
__ Actual Remote IP Address: 10.10.10.10
Err SDP-ID Info Local Remote
--- ----------------- ------ ------
__ Path Used: Yes Yes
__ SDP-ID: 123 325
__ Administrative State: Up Up
__ Operative State: Up Up
__ Binding Admin State: Up Up
__ Binding Oper State: Up Up
__ Binding VC-ID: 101 101
Err Service Label Information Label Source State
--- ------------------------- ----- ----------- -----
__ Local Egress Label: 45 Signaled Up
__ Remote Expected Ingress: 45 Signaled Up
__ Remote Egress: 34 Signaled Up
__ Local Expected Ingress: 34 Signaled Up
vprn-ping service-id source ip-address destination ip-address [fc
fc-name [profile
[in
| out
]][size size] [ttl vc-label-ttl] [return-control] [interval interval] [send-count send-count] [timeout timeout]
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
|
Values
|
ipv4-address: 0.0.0.0 — 255.255.255.255
ipv6-address: x:x:x:x:x:x:x:x x:x:x:x:x:x:d.d.d.d x: [0..FFFF]H d: [0..255]D
|
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 where the timeout value is set to 10 seconds, then 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.
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 will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be received. Any response received after the request times out will be silently discarded.
A:PE_1# oam vprn-ping 25 source 10.4.128.1 destination 10.16.128.0
Sequence Node-id Reply-Path Size RTT
----------------------------------------------------------------------------
[Send request Seq. 1.]
1 10.128.0.3:cpm In-Band 100 0ms
----------------------------------------------------------------------------
...
A:PE_1#
----------------------------------------------------------------------------
A:PE_1#
vprn-trace service-id source
src-ip destination
ip-address [fc
fc-name [profile
[in
| out
]] [size
size] [min-ttl
vc-label-ttl] [max-ttl
vc-label-ttl] [return-control
] [probe-count
probes-per-hop] [interval
seconds] [timeout
timeout]
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
|
Values
|
ipv4-address: 0.0.0.0 — 255.255.255.255
ipv6-address: x:x:x:x:x:x:x:x x:x:x:x:x:x:d.d.d.d x: [0..FFFF]H d: [0..255]D
|
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 where the timeout value is set to 10 seconds, then 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.
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 will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be received. Any response received after the request times out will be silently discarded.
A:PE_1# oam vprn-trace 25 source 10.4.128.1 destination 10.16.128.0
TTL Seq Reply Node-id Rcvd-on Reply-Path RTT
----------------------------------------------------------------------------
[Send request TTL: 1, Seq. 1.]
1 1 1 10.128.0.4 cpm In-Band 0ms
Requestor 10.128.0.1 Route: 0.0.0.0/0
Vpn Label: 131071 Metrics 0 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65100:1
Responder 10.128.0.4 Route: 10.16.128.0/24
Vpn Label: 131071 Metrics 0 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65001:100
[Send request TTL: 2, Seq. 1.]
2 1 1 10.128.0.3 cpm In-Band 0ms
Requestor 10.128.0.1 Route: 0.0.0.0/0
Vpn Label: 131071 Metrics 0 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65100:1
Responder 10.128.0.3 Route: 10.16.128.0/24
Vpn Label: 0 Metrics 0 Pref 0 Owner local
Next Hops: [1] ifIdx 2 nextHopIp 10.16.128.0
[Send request TTL: 3, Seq. 1.]
[Send request TTL: 4, Seq. 1.]
...
----------------------------------------------------------------------------
A:PE_1#
cpe-ping service service-id destination
ip-address source ip-address [ttl vc-label-ttl] [return-control
] [source-mac
ieee-address] [fc
fc-name [profile
[in
| out
]] [interval
interval] [send-count
send-count] [send-control
]
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
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 where the timeout value is set to 10 seconds, then 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.
mac-populate service-id mac
ieee-address [flood
] [age
seconds] [force
]
This command populates the FIB with an OAM-type MAC entry indicating the node is the egress node for the MAC address and optionally floods the OAM MAC association throughout the service. The mac-populate command installs an OAM MAC into the service FIB indicating the device is the egress node for a particular MAC address. The MAC address can be bound to a particular SAP (the
target-sap) or can be associated with the control plane in that any data destined to the MAC address is forwarded to the control plane (CPM). As a result, if the service on the node has neither a FIB nor an egress SAP, then it is not allowed to initiate a
mac-populate.
The force option in
mac-populate forces the MAC in the table to be type OAM in the case it already exists as a dynamic, static or an OAM induced learned MAC with some other type binding.
An OAM-type MAC cannot be overwritten by dynamic learning and allows customer packets with the MAC to either ingress or egress the network while still using the OAM MAC entry.
The flood option causes each upstream node to learn the MAC (that is, populate the local FIB with an OAM MAC entry) and to flood the request along the data plane using the flooding domain.The flooded
mac-populate request can be sent via the data plane or the control plane. The
send-control option specifies the request be sent using the control plane. If
send-control is not specified, the request is sent using the data plane.
An
age can be provided to age a particular OAM MAC using a specific interval. By default, OAM MAC addresses are not aged and can be removed with a
mac-purge or with an FDB clear operation.
mac-purge service-id target
ieee-address [flood
] [send-control
] [register
]
This command removes an OAM-type MAC entry from the FIB and optionally floods the OAM MAC removal throughout the service. A mac-purge can be sent via the forwarding path or via the control plane. When sending the MAC purge using the data plane, the TTL in the VC label is set to 1. When sending the MAC purge using the control plane, the packet is sent directly to the system IP address of the next hop.
The flood option causes each upstream node to be sent the OAM MAC delete request and to flood the request along the data plane using the flooding domain. The flooded
mac-purge request can be sent via the data plane or the control plane. The
send-control option specifies the request be sent using the control plane. If
send-control is not specified, the request is sent using the data plane.
The register option reserves the MAC for OAM testing where it is no longer an active MAC in the FIB for forwarding, but it is retained in the FIB as a registered OAM MAC. Registering an OAM MAC prevents relearns for the MAC based on customer packets. Relearning a registered MAC can only be done through a
mac-populate request. The originating SHG is always 0 (zero).
mac-ping service
service-id destination
dst-ieee-address [source
src-ieee-address] [fc
fc-name [profile
in
| out
]] [size
octets] [ttl
vc-label-ttl] [send-count
send-count] [send-control
] [return-control
] [interval
interval] [timeout
timeout]
The mac-ping utility is used to determine the existence of an egress SAP binding of a given MAC within a VPLS service.
A mac-ping packet can be sent via the control plane or the data plane. The send-control option specifies the request be sent using the control plane. If send-control is not specified, the request is sent using the data plane.
A mac-ping is forwarded along the flooding domain if no MAC address bindings exist. If MAC address bindings exist, then the packet is forwarded along those paths, provided they are active. A response is generated only when there is an egress SAP binding for that MAC address or if the MAC address is a “local” OAM MAC address associated with the device’s control plan.
A mac-ping reply can be sent using the data plane or the control plane. The return-control option specifies the reply be sent using the control plane. If return-control is not specified, the request is sent using the data plane.
A mac-ping with data plane reply can only be initiated on nodes that can have an egress MAC address binding. A node without a FIB and without any SAPs cannot have an egress MAC address binding, so it is not a node where replies in the data plane will be trapped and sent up to the control plane.
By default, MAC OAM requests are sent with the system or chassis MAC address as the source MAC. The source option allows overriding of the default source MAC for the request with a specific MAC address.
When a source ieee-address value is specified and the source MAC address is locally registered within a split horizon group (SHG), then this SHG membership will be used as if the packet originated from this SHG. In all other cases, SHG 0 (zero) will be used. Note that if the mac-trace is originated from a non-zero SHG, such packets will not go out to the same SHG.
The fc parameter is used to test the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
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 where the timeout value is set to 10 seconds, then 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.
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 will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be received. Any response received after the request times out will be silently discarded.
mac-trace service service-id destination
ieee-address [size
octets] [min-ttl
vc-label-ttl] [max-ttl
vc-label-ttl] [send-control
] [return-control
] [source
ieee-address] [z-count
probes-per-hop] [interval
interval] [timeout
timeout]
When a source ieee-address value is specified and the source MAC address is locally registered within a split horizon group (SHG), then this SHG membership will be used as if the packet originated from this SHG. In all other cases, SHG 0 (zero) will be used. Note that if the mac-ping is originated from a non-zero SHG, such packets will not go out to the same SHG.
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, then 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.
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 will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be received. Any response received after the request times out will be silently discarded.
mfib-ping service service-id source
src-ip destination
mcast-address [size
size] [ttl
vc-label-ttl] [return-control
] [interval
interval] [send-count
send-count] [timeout
timeout]
Upon the expiration of message timeout, the requesting 7750 SR assumes that the message response will not be 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 will be silently discarded.
A:ALA-A# oam mfib-ping service 10 source 10.10.10.1 destination 225.0.0.1 count 2
Seq Node-id Path Size RTT
-------------------------------------------------------------------------------
[Send request Seq. 1.]
1 51.51.51.51:sap1/1/1 Self 100 0ms
1 54.54.54.54:sap1/1/2 In-Band 100 20ms
1 54.54.54.54:sap1/1/3 In-Band 100 10ms
1 52.52.52.52:sap1/1/3 In-Band 100 20ms
[Send request Seq. 2.]
2 51.51.51.51:sap1/1/1 Self 100 0ms
2 52.52.52.52:sap1/1/2 In-Band 100 10ms
2 54.54.54.54:sap1/1/2 In-Band 100 10ms
2 52.52.52.52:sap1/1/3 In-Band 100 20ms
2 54.54.54.54:sap1/1/3 In-Band 100 30ms
-------------------------------------------------------------------------------
A:ALA-AIM# oam mfib-ping service 1 source 11.11.0.0 destination 224.0.0.1
Seq Node-id Path Size RTT
-------------------------------------------------------------------------------
[Send request Seq. 1.]
1 10.20.1.3:sap1/1/5:1 Not in MFIB Self 40 0ms
1 10.20.1.3:sap1/1/2:1 Self 40 10ms
[Echo replies received: 2]
-------------------------------------------------------------------------------
A:ALA-AIM#
linktrace mac-address mep
mep-id domain
md-index association
ma-index [ttl
ttl-value]
loopback {mac-address|multicast
} mep
mep-id domain
md-index association
ma-index [send-count
send-count] [size
data-size] [priority
priority]
mac-address mep
mep-id domain
md-index association
ma-index [priority
priority] [data-length
data-length]
one-way-delay-test mac-address mep
mep-id domain
md-index association
ma-index [priority
priority]
two-way-delay-test mac-address mep
mep-id domain
md-index association
ma-index [priority
priority]
two-way-slm-test mac-address mep
mep-id domain
md-index association
ma-index [priority
priority] [send-count
send-count] [size
data-size] [timeout
timeout] [interval
interval]
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 will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be received. Any response received after the request times out will be silently discarded. The timeout value must be less than the interval.
test name [owner
test-owner]
The no form of this command removes the test from the configuration. In order to remove a test it can not be active at the time.
|
Values
|
If a test-owner value is not specified, tests created by the CLI have a default owner “TiMOS CLI”.
|
The no form of this command removes the accounting policy association.
The description command associates a text string with a configuration context to help identify the content in the configuration file.
The no form of this command removes the string from the configuration.
The no form of the command disables the continuous running of the test. Use the
shutdown command to disable the test.
|
Values
|
inbound — Monitor the value of jitter calculated for the inbound, one-way, OAM ping responses received for an OAM ping test run. outbound — Monitor the value of jitter calculated for the outbound, one-way, OAM ping requests sent for an OAM ping test run. roundtrip — Monitor the value of jitter calculated for the round trip, two-way, OAM ping requests and replies for an OAM ping test run.
|
|
Values
|
inbound — Monitor the value of jitter calculated for the inbound, one-way, OAM ping responses received for an OAM ping test run. outbound — Monitor the value of jitter calculated for the outbound, one-way, OAM ping requests sent for an OAM ping test run. roundtrip — Monitor the value of jitter calculated for the round trip, two-way, OAM ping requests and replies for an OAM ping test run.
|
|
Values
|
inbound — Monitor the value of jitter calculated for the inbound, one-way, OAM ping responses received for an OAM ping test run. outbound — Monitor the value of jitter calculated for the outbound, one-way, OAM ping requests sent for an OAM ping test run. roundtrip — Monitor the value of jitter calculated for the round trip, two-way, OAM ping requests and replies for an OAM ping test run.
|
The no form of the command disables the generation of an SNMP trap.
[no
] probe-fail-threshold
0..15
The probe-fail-enable command enables the generation of an SNMP trap when the probe-fail-threshold consecutive probes fail during the execution of the SAA ping test. This command is not applicable to SAA trace route tests.
The no form of the command returns the threshold value to the default.
[no
] test-completion-enable
The no form of the command disables the trap generation.
The no form of the command disables the trap generation.
[no
] test-fail-threshold
0..15
The no form of the command returns the threshold value to the default.
cpe-ping service service-id destination
ip-address source ip-address [ttl vc-label-ttl] [return-control
] [source-mac
ieee-address] [fc
fc-name [profile
[in
| out
]] [interval
interval] [send-count
send-count] [send-control
]
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
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 where the timeout value is set to 10 seconds, then 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.
dns target-addr
dns-name name-server
ip-address [source
ip-address] [send-count
send-count] [time-out
timeout] [interval
interval]
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.
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 will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be received. Any response received after the request times out will be silently discarded.
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, then 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.
eth-cfm-linktrace mac-address mep
mep-id domain
md-index association
ma-index [ttl
ttl-value] [fc
{fc-name} [profile
{in
|out
}]] [send-count
send-count] [timeout
interval] [interval
interval]
The fc parameter is used to indicate the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
eth-cfm-loopback mac-address mep
mep-id domain
md-index association
ma-index [size
data-size] [fc
{fc-name} [profile
{in
|out
}]] [send-count
send-count ][time-out
interval] [interval
interval]
The fc parameter is used to indicate the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
eth-cfm-two-way-delay mac-address mep
mep-id domain
md-index association
ma-index [fc
{fc-name} [profile
{in
|out
}]] [send-count
send-count] [time-out
interval] [interval
interval]
The fc parameter is used to indicate the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
eth-cfm-two-way-delay mac-address mep
mep-id domain
md-index association
ma-index [fc
{fc-name}] [send-count
send-count] [size
data-size] [timeout
timeout] [interval
interval]
The fc parameter is used to indicate the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
icmp-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] [time-out
interval]
|
Values
|
ipv4-address: a.b.c.d
ipv6-address: x:x:x:x:x:x:x:x
x:x:x:x:x:x:d.d.d.d
x: [0 — FFFF]H
d: [0 — 255]D
dns-name: 128 characters max
|
|
Values
|
router-name: Base , management
service-id: 1 — 2147483647
|
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
icmp-trace [ip-address | dns-name] [ttl
time-to-live] [wait
milli-seconds] [tos
type-of-service] [source
ip-address] [tos
type-of-service] [router
router-instance | service-name
service-name]
|
Values
|
router-name: Base , management
service-id: 1 — 2147483647
|
lsp-ping static lsp-name [dest-global-id
global-id dest-node-id
node-id] [control-channel none | non-ip
] [path-type active | working | protect
] [fc
fc-name [profile in | out
] [interval
interval] [send-count
send-count] [size octets
] [src-ip-address
ip-address] [timeout
timeout] [ttl
label-ttl] [detail
]
lsp-ping prefix ip-prefix/mask [path-destination
ip-address [interface
if-name | next-hop
ip-address]]
lsp-ping static lsp-name [assoc-channel
none
|non-ip
] [dest-global-id
global-id dest-node-id
node-id] [path-type
active
| working
| protect
]
NOTE: Options common to all lsp-ping cases: [fc fc-name [profile in|out]] [interval interval] [send-count send-count] [size octets] [src-ip-address ip-address] [timeout timeout] [ttl label-ttl]
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 user 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.
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 an LSP ping route using the RFC 6426, MPLS On-Demand Connectivity Verification and Route Tracing, Target FEC Stack code point Static LSP.
|
Values
|
none — Use the Associated Channel mechanism described in RFC 6426, Section 3.3. non-ip — Do not use an Associated Channel, as described in RFC 6426, Section 3.1.
|
|
Values
|
active - test the currently-active path of the MPLS-TP LSP working - test the primary path of the MPLS-TP LSP protect - test the secondary path of the MPLS-TP LSP
|
A:DUTA# oam lsp-ping prefix 4.4.4.4/32 detail
LSP-PING 4.4.4.4/32: 80 bytes MPLS payload
Seq=1, send from intf dut1_to_dut3, reply from 4.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
-------------------------------------------------------------------------------
4.4.4.4/32 131069N 131067 1/1/1 1.3.1.2
3.3.3.3
4.4.4.4/32 131069U 131064 -- --
6.6.6.6
-------------------------------------------------------------------------------
No. of Prefix Bindings: 2
===============================================================================
A:DUTA#
lsp-trace static lsp-name [control-channel non | non-ip
] [force
] [path-type active | working | protect
] [detail
] [fc
fc-name [profile in|out
]] [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] [downstream-map-tlv dsmap
| ddmap
] [detail
]
lsp-trace prefix ip-prefix/mask [path-destination
ip-address [interface
if-name | next-hop
ip-address]]
lsp-trace static lsp-name [assoc-channel
none
|non-ip
] [path-type
active
| working
| protect
]
NOTE: Options common to all
lsp-trace cases: [
detail] [
downstream-map-tlv downstream-map-tlv] [
fc fc-name [
profile in|
out]] [
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]
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 user 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 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.
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
will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be 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 will be silently discarded.
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, then 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.
*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 5.5.5.5/32 detail
lsp-trace to 5.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=5.6.5.1 ifaddr=5.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
mac-ping service
service-id destination
dst-ieee-address [source
src-ieee-address] [fc
fc-name [profile
in
| out
]] [size
octets] [ttl
vc-label-ttl] [send-count
send-count] [send-control
] [return-control
] [interval
interval] [time-out
interval]
A mac-ping packet can be sent via the control plane or the data plane. The send-control option specifies the request be sent using the control plane. If send-control is not specified, the request is sent using the data plane.
A mac-ping is forwarded along the flooding domain if no MAC address bindings exist. If MAC address bindings exist, then the packet is forwarded along those paths, provided they are active. A response is generated only when there is an egress SAP binding for that MAC address or if the MAC address is a “local” OAM MAC address associated with the device’s control plan.
A mac-ping reply can be sent using the data plane or the control plane. The return-control option specifies the reply be sent using the control plane. If return-control is not specified, the request is sent using the data plane.
A mac-ping with data plane reply can only be initiated on nodes that can have an egress MAC address binding. A node without a FIB and without any SAPs cannot have an egress MAC address binding, so it is not a node where replies in the data plane will be trapped and sent up to the control plane.
By default, MAC OAM requests are sent with the system or chassis MAC address as the source MAC. The source option allows overriding of the default source MAC for the request with a specific MAC address.
When a source ieee-address value is specified and the source MAC address is locally registered within a split horizon group (SHG), then this SHG membership will be used as if the packet originated from this SHG. In all other cases, SHG 0 (zero) will be used. Note that if the mac-trace is originated from a non-zero SHG, such packets will not go out to the same SHG.
|
Values
|
service-id: 1 — 2147483647 svc-name: 64 characters maximum
|
The fc parameter is used to test the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
sdp-ping orig-sdp-id [
resp-sdp resp-sdp-id] [
fc fc-name [
profile {
in |
out}]] [
time-out interval] [
interval interval] [
size octets] [
send-count send-count]
The sdp-ping command accepts an originating SDP-ID and an optional responding SDP-ID. The size, number of requests sent, message time-out and message send interval can be specified. All sdp-ping requests and replies are sent with PLP OAM-Label encapsulation, as a service-id is not specified.
For round trip connectivity testing, the resp-sdp keyword must be specified. If resp-sdp is not specified, a uni-directional SDP test is performed.
To terminate an sdp-ping in progress, use the CLI break sequence <Ctrl-C>.
An sdp-ping response message indicates the result of the sdp-ping message request. When multiple response messages apply to a single SDP echo request/reply sequence, the response message with the highest precedence will be displayed. The following table displays the response messages sorted by precedence.
The SDP-ID to be used by sdp-ping, expressed as a decimal integer. The far-end address of the specified SDP-ID is the expected responder-id within each reply received. The specified SDP-ID defines the encapsulation of the SDP tunnel encapsulation used to reach the far end. This can be IP/GRE or MPLS. If orig-sdp-id is invalid or administratively down or unavailable for some reason, the SDP Echo Request message is not sent and an appropriate error message is displayed (once the interval timer expires, sdp-ping will attempt to send the next request if required).
Optional parameter is used to specify the return SDP-ID to be used by the far-end router
for the message reply for round trip SDP connectivity testing. If resp-sdp-id does not exist on the far-end router
, terminates on another router
different than the originating router
, or another issue prevents the far-end router
from using resp-sdp-id, the SDP echo reply will be sent using generic IP/GRE OAM encapsulation. The received forwarding class (as mapped on the ingress network interface for the far end) defines the forwarding class encapsulation for the reply message.
The fc parameter is used to indicate the forwarding class of the SDP encapsulation. The actual forwarding class encoding is controlled by the network egress DSCP or LSP-EXP mappings.
The size parameter in octets, expressed as a decimal integer. This parameter is used to override the default message size for the sdp-ping request. Changing the message size is a method of checking the ability of an SDP to support a path-mtu. The size of the message does not include the SDP encapsulation, VC-Label (if applied) or any DLC headers or trailers.
|
|
|
|
|
|
The result of the sdp-ping request message.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The local path-mtu for orig-sdp-id. If orig-sdp-id does not exist locally, N/A is displayed.
|
|
|
|
|
|
The SDP-ID requested as the far-end path to respond to the sdp-ping request. If resp-sdp is not specified, the responding router will not use an SDP-ID as the return path and N/A will be displayed.
|
|
|
|
|
|
Displays whether the responding router used the responding sdp-id to respond to the sdp-ping request. If resp-sdp-id is a valid, operational SDP-ID, it must be used for the SDP echo reply message. If the far-end uses the responding sdp-id as the return path, Yes will be displayed. If the far-end does not use the responding sdp-id as the return path, No will be displayed. If resp-sdp is not specified, N/A will be displayed.
|
|
|
|
|
|
|
|
The administrative state of the responding sdp-id. When resp-sdp-id is administratively down, Admin-Down will be displayed. When resp-sdp-id is administratively up, Admin-Up will be displayed. When resp-sdp-id exists on the far-end router but is not valid for the originating router, Invalid is displayed. When resp-sdp-id does not exist on the far-end router, Non-Existent is displayed. When resp-sdp is not specified, N/A is displayed.
|
|
|
|
|
|
|
|
|
|
|
|
The operational state of the far-end sdp-id associated with the return path for service-id. When a return path is operationally down, Oper-Down is displayed. If the return sdp-id is operationally up, Oper-Up is displayed. If the responding sdp-id is non-existent, N/A is displayed.
|
|
|
|
|
|
|
|
The remote path-mtu for resp-sdp-id. If resp-sdp-id does not exist remotely, N/A is displayed
|
|
|
|
|
|
The local system IP address used to terminate remotely configured sdp-ids (as the sdp-id far-end address). If an IP address has not been configured to be the system IP address, N/A is displayed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The expected source of the originators sdp-id from the perspective of the remote 7750 SR-Series terminating the sdp-id. If the far-end cannot detect the expected source of the ingress sdp-id, N/A is displayed.
|
|
|
|
|
|
|
|
|
|
A:router1> sdp-ping 10 resp-sdp 22 fc ef
Request Result: Sent - Reply Received
RTT: 30ms
Err SDP-ID Info Local Remote
__ SDP-ID: 10 22
__ Administrative State: Up Up
__ Operative State: Up Up
__ Path MTU 4470 4470
__ Response SDP Used: Yes
Err System IP Interface Info
Local Interface Name: "ESR-System-IP-Interface (Up to 32 chars)…"
__ Local IP Interface State: Up
__ Local IP Address: 10.10.10.11
__ IP Address Expected By Remote: 10.10.10.11
__ Expected Remote IP Address: 10.10.10.10
__ Actual Remote IP Address: 10.10.10.10
Err FC Mapping Info Local Remote
__ Forwarding Class Assured Assured
__ Profile In In
A:router1> sdp-ping 6 resp-sdp 101size 1514 count 5
Request Response RTT
---------- ---------- -------
1 Success 10ms
2 Success 15ms
3 Success 10ms
4 Success 20ms
5 Success 5ms
Sent: 5 Received: 5
Min: 5ms Max: 20ms Avg: 12ms
vccv-ping sdp-id:vc-id [src-ip-address
ip-addr dst-ip-address
ip-addr pw-id
pw-id][reply-mode
{ip-routed
|control-channel
}] [fc
fc-name [profile
{in
| out
}]] [size
octets] [send-count
send-count] [timeout
timeout] [interval
interval] [ttl
vc-label-ttl]
vccv-ping static sdp-id:vc-id [dest-global-id global-id dest-node-id node-id] [control-channel ipv4 | non-ip] [src-ip-address ip-addr] [count send-count] [fc fc-name [profile in|out]] [interval interval] [size octets] [timeout timeout] [ttl vc-label-ttl] [detail]
vccv-ping spoke-sdp-fec spoke-sdp-fec-id [saii-type2
global-id:prefix:ac-id taii-type2
global-id:prefix:ac-id] [src-ip-address
ip-addr dst-ip-address
ip-addr] [reply-mode
{ip-routed
| control-channel
}] [fc
fc-name [profile
{in
| out
}]] [size
octets] [count
send-count
] [timeout
timeout] [interval
interval] [ttl
vc-label-ttl]
vccv-ping saii-type2 global-id:prefix:ac-id taii-type2
global-id:prefix:ac-id [src-ip-address
ip-addr dst-ip-address
ip-addr] [reply-mode
{ip-routed
| control-channel
}] [fc
fc-name [profile
{in
| out
}]] [size
octets] [count
send-count] [timeout
timeout] [interval
interval] [ttl
vc-label-ttl]
This command, when used with the static option, configures a Virtual Circuit Connectivity Verification (VCCV) ping test for static MPLS-TP pseudowires used in a VLL service. A vccv-ping test checks connectivity of a VLL inband. It checks to verify that the destination (target) PE is the egress for the Static PW FEC. It provides for a cross-check between the dataplane and the configuration. It is inband which means that the vccv-ping message is sent using the same encapsulation and along the same path as user packets in that VLL. The vccv-ping test is the equivalent of the lsp-ping test for a VLL service. The vccv- ping static command reuses an lsp-ping message format and can be used to test an MPLS-TP pseudowire VLL configured over an MPLS SDP. VCCV Ping for MPLS-TP pseudowires always uses the VCCV control word (associated channel header) with either an IPv4 channel type (0x0021) or on-demand CV message channel type (0x0025).
Note that vccv-ping static can only be initiated on a T-PE. Both the echo request and reply messages are send using the same, in-band, encapsulation. The target FEC stack contains a static PW FEC TLV. The contents of this TLV are populated based on the source Node ID, source Global ID, and Destination Global ID and Destination Node ID in the vccv-ping command (or taken from the pseudowire context if omitted from the command).
If a FEC 129 PW is being tested, then its spoke-sdp-fec-id must be indicated with this parameter. The
spoke-sdp-fec-id must exist on the local router and the far-end peer needs to indicate that it supports VCCV to allow the user to send vccv-ping messages.
spoke-sdp-fec is mutually exclusive with the
sdp-id:vc-id parameter.
|
Values
|
ipv4 — IPv4 encapsulation in an IPv4 pseudowire associated channel (channel type 0x0021)
|
|
Values
|
non-ip — MPLS-TP encapsulation without UDP/IP headers, in pseudowire associated channel using channel type 0x025.
|
The saii-type2 parameter is mutually exclusive with the
sdp-id:vc-id parameter.
Syntax: global-id — The global ID of this 7x50 T-PE node.
Values: 1 — 4294967295
prefix — The prefix on this 7x50 T-PE node that the spoke-SDP is associated with.
ac-id — An unsigned integer representing a locally unique identifier for the spoke-SDP.
Values: 1 — 4294967295
Syntax: global-id – The global ID of the far end T-PE node of the FEC129 pseudowire.
Values: 1 — 4294967295
prefix — The prefix on far end. T-PE node that the pseudowire being tested is associated with.
Values: ipv4-formatted address: a.b.c.d
ac-id — An unsigned integer representing a locally unique identifier for the pseudowire
being tested at the far end T-PE.
Values: 1 — 4294967295
Ping TPE to SPE on a LDP/GRE tunnel
===================================
*A:Dut-B# oam vccv-ping 3:1
VCCV-PING 3:1 88 bytes MPLS payload
Seq=1, send from intf toSPE1-D-8 to NH 12.1.8.2
reply from 4.4.4.4 via Control Channel
udp-data-len=56 rtt=0.689ms rc=8 (DSRtrMatchLabel)
---- VCCV PING 3:1 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 0.689ms, avg = 0.689ms, max = 0.689ms, stddev = 0.000ms
Ping TPE to SPE on a RSVP tunnel
================================
A:Dut-C# oam vccv-ping 5:1
VCCV-PING 5:1 88 bytes MPLS payload
Seq=1, send from intf toSPE2-E-5 to NH 12.3.5.1
send from lsp toSPE2-E-5
reply from 5.5.5.5 via Control Channel
udp-data-len=56 rtt=1.50ms rc=8 (DSRtrMatchLabel)
---- VCCV PING 5:1 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 1.50ms, avg = 1.50ms, max = 1.50ms, stddev = 0.000ms
Ping TPE to TPE over multisegment pseudowire
============================================
*A:Dut-C# oam vccv-ping 5:1 src-ip-address 4.4.4.4 dst-ip-address 2.2.2.2 pw-id 1 ttl 3
VCCV-PING 5:1 88 bytes MPLS payload
Seq=1, send from intf toSPE2-E-5 to NH 12.3.5.1
send from lsp toSPE2-E-5
reply from 2.2.2.2 via Control Channel
udp-data-len=32 rtt=2.50ms rc=3 (EgressRtr)
---- VCCV PING 5:1 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 2.50ms, avg = 2.50ms, max = 2.50ms, stddev = 0.000ms
Ping SPE to TPE (over LDP tunnel)
==================================
Single segment:
---------------
*A:Dut-D# oam vccv-ping 3:1 reply-mode ip-routed
VCCV-PING 3:1 88 bytes MPLS payload
Seq=1, send from intf toTPE1-B-8 to NH 12.1.8.1
reply from 2.2.2.2 via IP
udp-data-len=32 rtt=1.66ms rc=3 (EgressRtr)
---- VCCV PING 3:1 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 1.66ms, avg = 1.66ms, max = 1.66ms, stddev = 0.000ms
Multisegment:
-------------
*A:Dut-D>config>router# oam vccv-ping 4:200 src-ip-address 5.5.5.5 dst-ip-address 3.3.3.3 pw-id 1 ttl 2 reply-mode ip-routed
VCCV-PING 4:200 88 bytes MPLS payload
Seq=1, send from intf toSPE2-E-5 to NH 12.2.5.2
reply from 3.3.3.3 via IP
udp-data-len=32 rtt=3.76ms rc=3 (EgressRtr)
---- VCCV PING 4:200 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 3.76ms, avg = 3.76ms, max = 3.76ms, stddev = 0.000ms
Ping SPE to SPE
===============
*A:Dut-D# oam vccv-ping 4:200 reply-mode ip-routed
VCCV-PING 4:200 88 bytes MPLS payload
Seq=1, send from intf toSPE2-E-5 to NH 12.2.5.2
reply from 5.5.5.5 via IP
udp-data-len=56 rtt=1.77ms rc=8 (DSRtrMatchLabel)
---- VCCV PING 4:200 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 1.77ms, avg = 1.77ms, max = 1.77ms, stddev = 0.000ms
vccv-trace sdp-id:vc-id [fc
fc-name [profile
{in
| out
}]] [size
octets] [reply-mode ip-routed|control-channel] [probe-count
probes-per-hop] [timeout
timeout] [interval
interval] [min-ttl
min-vc-label-ttl] [max-ttl
max-vc-label-ttl] [max-fail
no-response-count] [detail
]
vccv-trace static sdp-id:vc-id [control-channel none | non-ip] [src-ip-address ipv4-address] [fc fc-name [profile in|out]] [interval interval-value] [max-fail no-response-count] [max-ttl max-vc-label-ttl] [min-ttl min-vc-label-ttl] [probe-count probe-count] [size octets] [timeout timeout-value] [detail]
vccv-trace spoke-sdp-fec poke-sdp-fec spoke-sdp-fec-id [saii-type2
global-id:prefix:ac-id taii-type2
global-id:prefix:ac-id][[size
octets][min-ttl
min-vc-label-ttl][max-ttl
max-vc-label-ttl][max-fail
no-response-count][probe-count
probe-count][reply-mode
ip-routed
| control-channel
][timeout
timeout-value][interval
interval-value][fc
fc-name [profile
{in
| out
}]][detail
]
vccv-trace saii-type2
global-id:prefix:ac-id taii-type2 global-id:prefix:ac-id [size
octets][min-ttl
min-vc-label-ttl][max-ttl
max-vc-label-ttl][max-fail
no-response-count][probe-count
probe-count][reply-mode
ip-routed
| control-channel
][timeout
timeout-value][interval
interval-value][fc
fc-name [profile
{in
| out
}]][detail
]
This command, when used with the static option, configures a Virtual Circuit Connectivity Verification (VCCV) automated trace test for static MPLS-TP pseudowires used in a VLL service. The automated VCCV-trace can trace the entire path of a PW with a single command issued at the T-PE or at an S-PE. This is equivalent to LSP-Trace and is an iterative process by which the source T-PE or S-PE node sends successive VCCV-Ping messages with incrementing the TTL value, starting from TTL=1.
Note that vccv-trace static can only be initiated on a T-PE. Both the echo request and reply messages are send using the same, in-band, encapsulation. The target FEC stack contains a static PW FEC TLV. The contents of this TLV are populated based on the source Node ID, source Global ID, and Destination Global ID and Destination Node ID taken from the pseudowire context.
If a FEC 129 PW is being tested, then its spoke-sdp-fec-id must be indicated with this parameter. The
spoke-sdp-fec-id must exist on the local router and the far-end peer needs to indicate that it supports VCCV to allow the user to send vccv-ping messages.
spoke-sdp-fec is mutually exclusive with the
sdp-id:vc-id parameter.
The saii-type2 parameter is mutually exclusive with the
sdp-id:vc-id parameter.
Syntax: global-id — The global ID of this 7x50 T-PE node.
Values: 1 — 4294967295
prefix — The prefix on this 7x50 T-PE node that the spoke-SDP is associated with.
ac-id — An unsigned integer representing a locally unique identifier for the spoke-SDP.
Values: 1 — 4294967295
Syntax: global-id – The global ID of the far end T-PE of the FEC129 pseudowire.
Values: 1 — 4294967295
prefix — The prefix on far end T-PE that the pseudowire being tested is associated with.
Values: ipv4-formatted address: a.b.c.d
ac-id — An unsigned integer representing a locally unique identifier for the pseudowire
being tested at the far end T-PE.
Values: 1 — 4294967295
fc fc-name [profile
{in
| out
}
*A:138.120.214.60# oam vccv-trace 1:33
VCCV-TRACE 1:33 with 88 bytes of MPLS payload
1 1.1.63.63 rtt<10ms rc=8(DSRtrMatchLabel)
2 1.1.62.62 rtt<10ms rc=8(DSRtrMatchLabel)
3 1.1.61.61 rtt<10ms rc=3(EgressRtr)
*A:138.120.214.60>oam vccv-trace 1:33 detail
VCCV-TRACE 1:33 with 88 bytes of MPLS payload
1 1.1.63.63 rtt<10ms rc=8(DSRtrMatchLabel)
Next segment: VcId=34 VcType=AAL5SDU Source=1.1.63.63 Remote=1.1.62.62
2 1.1.62.62 rtt<10ms rc=8(DSRtrMatchLabel)
Next segment: VcId=35 VcType=AAL5SDU Source=1.1.62.62 Remote=1.1.61.61
3 1.1.61.61 rtt<10ms rc=3(EgressRtr)
SAA:
*A:multisim3>config>saa# info
----------------------------------------------
test "vt1"
shutdown
type
vccv-trace 1:2 fc "af" profile in timeout 2 interval 3 size 200
min-ttl 2 max-ttl 5 max-fail 2 probe-count 3
exit
exit
..
----------------------------------------------
*A:multisim3>config>saa#
saa test-name [owner
test-owner] {start
| stop
} [no-accounting
]
|
Values
|
If a test-owner value is not specified, tests created by the CLI have a default owner “TiMOS CLI”.
|
ldp-treetrace {prefix
ip-prefix/mask} [max-ttl
ttl-value] [max-path
max-paths] [timeout
timeout] [retry-count
retry-count] [fc
fc-name [profile
profile]] [downstream-map-tlv
{dsmap
|ddmap
}]
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 will wait for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response will not be received. Any response received after the request times out will be silently discarded.
*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
The no option deletes the configuration for the LDP ECMP OAM tree discovery and path probing under this context.
*A:Dut-B# oam ldp-treetrace prefix 10.20.1.5/32
ldp-treetrace for Prefix 10.20.1.5/32:
10.10.131.2, ttl = 2 dst = 127.1.0.253 rc = EgressRtr status = Done
Hops: 11.1.0.2
10.10.132.2, ttl = 2 dst = 127.1.0.255 rc = EgressRtr status = Done
Hops: 11.1.0.2
10.10.131.2, ttl = 2 dst = 127.2.0.255 rc = EgressRtr status = Done
Hops: 11.2.0.2
10.10.132.2, ttl = 2 dst = 127.2.0.253 rc = EgressRtr status = Done
Hops: 11.2.0.2
ldp-treetrace discovery state: Done
ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 4
Total number of failed traces: 0
*A:Dut-A# oam ldp-treetrace prefix 10.20.1.6/32 downstream-map-tlv dsmap
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
fc fc-name [profile
{in
| out
}]
Specifies the profile value to be used with the forwarding class specified in the
fc-name parameter.
The no option resets the interval to its default value.
The no option resets the timeout to its default value.
The no option resets the timeout to its default value.
Policies are configured in the config>router>policy-options context. A maximum of five policy names can be specified.
The no form of the command removes the policy from the configuration.
The no option resets the retry count to its default value
The no option resets the timeout to its default value.
The user configures the frequency of running the path probes using the command config>test-oam>ldp-treetrace> path-probing> interval. If an I/F is down on the ingress LER performing the LDP tree trace, then LSP Ping probes that normally go out this interface will not be sent but the ingress LER node will not raise alarms.
The no option resets the timeout to its default value.
If rfc4379 is selected, then the timestamp is in seconds and microseconds since 1900, otherwise it is in seconds and microseconds since 1970.
specifies the RFC 4379 time stamp format. The time stamp's seconds field holds the integral number of seconds since 1-Jan-1900 00:00:00 UTC. The time stamp's
microseconds field contains a microseconds value in the range 0 — 999999. This setting is used to interoperate with network elements which are fully compliant with RFC 4379,
Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, (such as an SR-OS system with the same setting, or any other RFC 4379 compliant router).
specifies the Unix time stamp format. The time stamps seconds field holds a Unix time, the integral number of seconds since 1-Jan-1970 00:00:00 UTC. The time stamps
microseconds field contains a microseconds value in the range 0 — 999999. This setting is used to interoperate with network elements which send and expect a 1970-based timestamp in MPLS Echo Request/Reply PDUs (such as an SR-OS system with the same setting, or an SROS system running software earlier than R8.0 R4).
|
1.
|
An SAA test of type lsp-trace is created (not modified) and no value is specified for the per-test downstream-map-tlv { dsmap| ddmap| none} option. In this case, the SAA test downstream-map-tlv value defaults to the global mpls-echo-request-downstream-map value.
|
|
2.
|
An OAM test of type lsp-trace test is executed and no value is specified for the per-test downstream-map-tlv { dsmap| ddmap| none} option. In this case, the OAM test downstream-map-tlv value defaults to the global mpls-echo-request-downstream-map value.
|
A consequence of the rules above is that a change to the value of mpls-echo-request-downstream-map option does not affect the value inserted in the downstream mapping TLV of existing tests.
|
a.
|
The user issues a LSP trace from a sender node with a min-ttl value higher than 1 and a max-ttl value lower than the number of hops to reach the egress of the target FEC stack. This is the sender node behavior when the global configuration or the per-test setting of the DSMAP/DDMAP is set to DSMAP.
|
The no form of this command reverts to the default behavior of using the DSMAP TLV in a LSP trace packet and LDP tree trace packet.
A B D F E C
o -------- o -------- o -------- o -------- o -------- o
| \______/ | \____________________________/ | \______/ |
\ RSVP / LDP \ RSVP /
\______/ \______/
LDP LDP
Testing LDP FEC of Node C with DSMAP TLV
----------------------------------------
*A:Dut-A#
*A:Dut-A# oam lsp-trace prefix 10.20.1.3/32 downstream-map-tlv dsmap detail
lsp-trace to 10.20.1.3/32: 0 hops min, 0 hops max, 104 byte packets
1 10.20.1.2 rtt=3.90ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.4.4 ifaddr=10.10.4.4 iftype=ipv4Numbered MRU=1500
label[1]=131068 protocol=3(LDP)
2 10.20.1.4 rtt=5.69ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.9.6 ifaddr=10.10.9.6 iftype=ipv4Numbered MRU=1500
label[1]=131066 protocol=3(LDP)
3 10.20.1.6 rtt=7.88ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.10.5 ifaddr=10.10.10.5 iftype=ipv4Numbered MRU=1500
label[1]=131060 protocol=3(LDP)
4 10.20.1.5 rtt=23.2ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.5.3 ifaddr=10.10.5.3 iftype=ipv4Numbered MRU=1496
label[1]=131071 protocol=3(LDP)
5 10.20.1.3 rtt=12.0ms rc=3(EgressRtr) rsc=1
*A:Dut-A#
Testing LDP FEC of Node C with DDMAP TLV
----------------------------------------
*A:Dut-A# oam lsp-trace prefix 10.20.1.3/32 downstream-map-tlv ddmap detail
lsp-trace to 10.20.1.3/32: 0 hops min, 0 hops max, 136 byte packets
1 10.20.1.2 rtt=4.00ms rc=3(EgressRtr) rsc=2
1 10.20.1.2 rtt=3.48ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.4.4 ifaddr=10.10.4.4 iftype=ipv4Numbered MRU=1500
label[1]=131068 protocol=3(LDP)
2 10.20.1.4 rtt=5.34ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.9.6 ifaddr=10.10.9.6 iftype=ipv4Numbered MRU=1500
label[1]=131066 protocol=3(LDP)
3 10.20.1.6 rtt=7.78ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.10.5 ifaddr=10.10.10.5 iftype=ipv4Numbered MRU=1500
label[1]=131060 protocol=3(LDP)
4 10.20.1.5 rtt=12.8ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.5.3 ifaddr=10.10.5.3 iftype=ipv4Numbered MRU=1496
label[1]=131054 protocol=4(RSVP-TE)
label[2]=131071 protocol=3(LDP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.3 remotepeer=10.10.5.3
5 10.20.1.3 rtt=12.8ms rc=3(EgressRtr) rsc=2
5 10.20.1.3 rtt=13.4ms rc=3(EgressRtr) rsc=1
*A:Dut-A#
D F E C A B
o -------- o -------- o -------- o -------- o -------- o
\_________________/ | \_________________/ | \______/ |
LDP \ RSVP ECA / \ RSVP /
\_________________/ \______/
LDP LDP
Testing LDP FEC of Node B with DDMAP TLV
----------------------------------------
*A:Dut-D#
*A:Dut-D# oam lsp-trace prefix 10.20.1.2/32 downstream-map-tlv ddmap detail
lsp-trace to 10.20.1.2/32: 0 hops min, 0 hops max, 108 byte packets
1 10.20.1.6 rtt=3.17ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=10.10.10.5 ifaddr=10.10.10.5 iftype=ipv4Numbered MRU=1500
label[1]=131065 protocol=3(LDP)
2 10.20.1.5 rtt=8.27ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.5.3 ifaddr=10.10.5.3 iftype=ipv4Numbered MRU=1496
label[1]=131068 protocol=4(RSVP-TE)
label[2]=131065 protocol=3(LDP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.1 remotepeer=10.10.5.3
3 10.20.1.3 rtt=9.50ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.2.1 ifaddr=10.10.2.1 iftype=ipv4Numbered MRU=1500
label[1]=131068 protocol=4(RSVP-TE)
4 10.20.1.1 rtt=10.4ms rc=3(EgressRtr) rsc=2
4 10.20.1.1 rtt=10.2ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.1.2 ifaddr=10.10.1.2 iftype=ipv4Numbered MRU=1496
label[1]=131066 protocol=4(RSVP-TE)
label[2]=131071 protocol=3(LDP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.2 remotepeer=10.10.1.2
5 10.20.1.2 rtt=13.7ms rc=3(EgressRtr) rsc=2
5 10.20.1.2 rtt=13.6ms rc=3(EgressRtr) rsc=1
*A:Dut-D#
A B C D E F
o ------- o -------- o --------- o ------- o ------- o
\_____/ | \_______/ | \_____/
LDP | RSVP | LDP
|\______________________________/|
| LDP |
\______________________________/
BGP
Testing LDP FEC of Node F with DSMAP TLV
----------------------------------------
*A:Dut-A# *A:Dut-A# oam lsp-trace prefix 10.20.1.6/32 downstream-map-tlv dsmap detail lsp-trace to 10.20.1.6/32: 0 hops min, 0 hops max, 104 byte packets
1 10.20.1.2 rtt=2.65ms rc=8(DSRtrMatchLabel) rsc=1
2 10.20.1.3 rtt=4.89ms rc=8(DSRtrMatchLabel) rsc=1
3 10.20.1.4 rtt=6.49ms rc=5(DSMappingMismatched) rsc=1
*A:Dut-A#
Testing LDP FEC of Node F with DDMAP TLV
----------------------------------------
*A:Dut-A# oam lsp-trace prefix 10.20.1.6/32 downstream-map-tlv ddmap detail lsp-trace to 10.20.1.6/32: 0 hops min, 0 hops max, 108 byte packets
1 10.20.1.2 rtt=3.50ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.3.3 ifaddr=10.10.3.3 iftype=ipv4Numbered MRU=1496
label[1]=131068 protocol=3(LDP)
label[2]=131060 protocol=2(BGP)
fecchange[1]=POP fectype=LDP IPv4 prefix=10.20.1.6 remotepeer=0.0.0.0 (Unknown)
fecchange[2]=PUSH fectype=BGP IPv4 prefix=10.20.1.6 remotepeer=10.20.1.5
fecchange[3]=PUSH fectype=LDP IPv4 prefix=10.20.1.5 remotepeer=10.10.3.3
2 10.20.1.3 rtt=6.53ms rc=15(LabelSwitchedWithFecChange) rsc=2
DS 1: ipaddr=10.10.11.4 ifaddr=10.10.11.4 iftype=ipv4Numbered MRU=1496
label[1]=131060 protocol=4(RSVP-TE)
label[2]=131070 protocol=3(LDP)
label[3]=131060 protocol=2(BGP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.4 remotepeer=10.10.11.4
3 10.20.1.4 rtt=7.94ms rc=3(EgressRtr) rsc=3
3 10.20.1.4 rtt=6.69ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.6.5 ifaddr=10.10.6.5 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
label[2]=131060 protocol=2(BGP)
4 10.20.1.5 rtt=10.1ms rc=3(EgressRtr) rsc=2
4 10.20.1.5 rtt=8.97ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.10.6 ifaddr=10.10.10.6 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
fecchange[1]=POP fectype=BGP IPv4 prefix=10.20.1.6 remotepeer=0.0.0.0 (Unknown)
fecchange[2]=PUSH fectype=LDP IPv4 prefix=10.20.1.6 remotepeer=10.10.10.6
5 10.20.1.6 rtt=11.8ms rc=3(EgressRtr) rsc=1 *A:Dut-A#
A B C D E
o ------- o -------- o --------- o ---3--- o
\_____/ | \_______/ |
LDP | RSVP |
|\______________________________/|
| LDP |
\______________________________/
BGP
Testing BGP Label Route of Node E with DDMAP TLV
-------------------------------------------------
*A:Dut-B# oam lsp-trace prefix 11.20.1.5/32 bgp-label downstream-map-tlv ddmap detail lsp-trace to 11.20.1.5/32: 0 hops min, 0 hops max, 124 byte packets
1 10.20.1.3 rtt=2.35ms rc=15(LabelSwitchedWithFecChange) rsc=2
DS 1: ipaddr=10.10.11.4 ifaddr=10.10.11.4 iftype=ipv4Numbered MRU=1496
label[1]=131060 protocol=4(RSVP-TE)
label[2]=131070 protocol=3(LDP)
label[3]=131070 protocol=2(BGP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.4 remotepeer=10.10.11.4
2 10.20.1.4 rtt=4.17ms rc=3(EgressRtr) rsc=3
2 10.20.1.4 rtt=4.50ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.6.5 ifaddr=10.10.6.5 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
label[2]=131070 protocol=2(BGP)
3 10.20.1.5 rtt=7.78ms rc=3(EgressRtr) rsc=2
3 10.20.1.5 rtt=6.80ms rc=3(EgressRtr) rsc=1 *A:Dut-B#
B C D E F
o -------- o --------- o ---3--- o ---3--- o
| \_______/ | \_____/
| RSVP |
|\______________________________/|
| LDP |
\______________________________/
BGP
Testing with DDMAP TLV LDP FEC of Node F when stitched to a BGP Label Route
----------------------------------------------------------------------------
*A:Dut-B# oam lsp-trace prefix 10.20.1.6/32 bgp-label downstream-map-tlv ddmap detail lsp-trace to 10.20.1.6/32: 0 hops min, 0 hops max, 124 byte packets
1 10.20.1.3 rtt=3.21ms rc=15(LabelSwitchedWithFecChange) rsc=2
DS 1: ipaddr=10.10.11.4 ifaddr=10.10.11.4 iftype=ipv4Numbered MRU=1496
label[1]=131060 protocol=4(RSVP-TE)
label[2]=131070 protocol=3(LDP)
label[3]=131060 protocol=2(BGP)
fecchange[1]=PUSH fectype=RSVP IPv4 prefix=10.20.1.4 remotepeer=10.10.11.4
2 10.20.1.4 rtt=5.50ms rc=3(EgressRtr) rsc=3
2 10.20.1.4 rtt=5.37ms rc=8(DSRtrMatchLabel) rsc=2
DS 1: ipaddr=10.10.6.5 ifaddr=10.10.6.5 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
label[2]=131060 protocol=2(BGP)
3 10.20.1.5 rtt=7.82ms rc=3(EgressRtr) rsc=2
3 10.20.1.5 rtt=6.11ms rc=15(LabelSwitchedWithFecChange) rsc=1
DS 1: ipaddr=10.10.10.6 ifaddr=10.10.10.6 iftype=ipv4Numbered MRU=1500
label[1]=131071 protocol=3(LDP)
fecchange[1]=POP fectype=BGP IPv4 prefix=10.20.1.6 remotepeer=0.0.0.0 (Unknown)
fecchange[2]=PUSH fectype=LDP IPv4 prefix=10.20.1.6 remotepeer=10.10.10.6
4 10.20.1.6 rtt=10.2ms rc=3(EgressRtr) rsc=1 *A:Dut-B#
prefix address/prefix-length [create
]
The no form of the command sets the default value (32).
The no form of the command sets the default value (32).
The no form of the command means to go with a default value of 32.
The no form of the command means to go with a default value of 32.
saa [test-name] [owner
test-owner]
|
Default
|
If a test-owner value is not specified, tests created by the CLI have a default owner “TiMOS CLI”.
|
*A:bksim130>config>saa>test>trap-gen# show saa mySaaPingTest1
===============================================================================
SAA Test Information
===============================================================================
Test name : mySaaPingTest1
Owner name : TiMOS CLI
Description : N/A
Accounting policy : None
Administrative status : Disabled
Test type : icmp-ping 11.22.33.44
Trap generation : probe-fail-enable probe-fail-threshold 3
test-fail-enable test-fail-threshold 2
test-completion-enable
Test runs since last clear : 0
Number of failed test runs : 0
Last test result : Undetermined
-------------------------------------------------------------------------------
Threshold
Type Direction Threshold Value Last Event Run #
-------------------------------------------------------------------------------
Jitter-in Rising None None Never None
Falling None None Never None
Jitter-out Rising None None Never None
Falling None None Never None
Jitter-rt Rising None None Never None
Falling None None Never None
Latency-in Rising None None Never None
Falling None None Never None
Latency-out Rising None None Never None
Falling None None Never None
Latency-rt Rising None None Never None
Falling None None Never None
Loss-in Rising None None Never None
Falling None None Never None
Loss-out Rising None None Never None
Falling None None Never None
Loss-rt Rising None None Never None
Falling None None Never None
===============================================================================
*A:bksim130>config>saa>test>trap-gen#
*A:bksim130>config>saa>test>trap-gen$ show saa mySaaTraceRouteTest1
===============================================================================
SAA Test Information
===============================================================================
Test name : mySaaTraceRouteTest1
Owner name : TiMOS CLI
Description : N/A
Accounting policy : None
Administrative status : Disabled
Test type : icmp-trace 11.22.33.44
Trap generation : test-fail-enable test-completion-enable
Test runs since last clear : 0
Number of failed test runs : 0
Last test result : Undetermined
-------------------------------------------------------------------------------
Threshold
Type Direction Threshold Value Last Event Run #
-------------------------------------------------------------------------------
Jitter-in Rising None None Never None
Falling None None Never None
Jitter-out Rising None None Never None
Falling None None Never None
Jitter-rt Rising None None Never None
Falling None None Never None
Latency-in Rising None None Never None
Falling None None Never None
Latency-out Rising None None Never None
Falling None None Never None
Latency-rt Rising None None Never None
Falling None None Never None
Loss-in Rising None None Never None
Falling None None Never None
Loss-out Rising None None Never None
Falling None None Never None
Loss-rt Rising None None Never None
Falling None None Never None
===============================================================================
*A:bksim130>config>saa>test>trap-gen$
show saa <test-name>
CFM Loopback:
===============================================================================
SAA Test Information
===============================================================================
Test name : CFMLoopbackTest
Owner name : TiMOS CLI
Description : N/A
Accounting policy : 1
Continuous : Yes
Administrative status : Enabled
Test type : eth-cfm-loopback 00:01:01:01:01:01 mep 1 domain 1 association 1 interval 1 count 10
Trap generation : None
Test runs since last clear : 1
Number of failed test runs : 0
Last test result : Success
-------------------------------------------------------------------------------
Threshold
Type Direction Threshold Value Last Event Run #
-------------------------------------------------------------------------------
Jitter-in Rising None None Never None
Falling None None Never None
Jitter-out Rising None None Never None
Falling None None Never None
Jitter-rt Rising None None Never None
Falling None None Never None
Latency-in Rising None None Never None
Falling None None Never None
Latency-out Rising None None Never None
Falling None None Never None
Latency-rt Rising None None Never None
Falling None None Never None
Loss-in Rising None None Never None
Falling None None Never None
Loss-out Rising None None Never None
Falling None None Never None
Loss-rt Rising None None Never None
Falling None None Never None
===============================================================================
Test Run: 1
Total number of attempts: 10
Number of requests that failed to be sent out: 0
Number of responses that were received: 10
Number of requests that did not receive any response: 0
Total number of failures: 0, Percentage: 0
(in us) Min Max Average Jitter
Outbound : 0.000 0.000 0.000 0
Inbound : 0.000 0.000 0.000 0
Roundtrip : 10200 10300 10250 100
Per test packet:
Sequence Result Delay(us)
1 Response Received 10300
2 Response Received 10300
3 Response Received 10300
4 Response Received 10200
5 Response Received 10300
6 Response Received 10200
7 Response Received 10300
8 Response Received 10200
9 Response Received 10300
10 Response Received 10300
=======================================================================
CFM Traceroute:
===============================================================================
SAA Test Information
===============================================================================
Test name : CFMLinkTraceTest
Owner name : TiMOS CLI
Description : N/A
Accounting policy : None
Continuous : Yes
Administrative status : Enabled
Test type : eth-cfm-linktrace 8A:DB:01:01:00:02 mep 1 domain 1 association 1 interval 1
Trap generation : None
Test runs since last clear : 1
Number of failed test runs : 0
Last test result : Success
-------------------------------------------------------------------------------
Threshold
Type Direction Threshold Value Last Event Run #
-------------------------------------------------------------------------------
Jitter-in Rising None None Never None
Falling None None Never None
Jitter-out Rising None None Never None
Falling None None Never None
Jitter-rt Rising None None Never None
Falling None None Never None
Latency-in Rising None None Never None
Falling None None Never None
Latency-out Rising None None Never None
Falling None None Never None
Latency-rt Rising None None Never None
Falling None None Never None
Loss-in Rising None None Never None
Falling None None Never None
Loss-out Rising None None Never None
Falling None None Never None
Loss-rt Rising None None Never None
Falling None None Never None
===============================================================================
Test Run: 1
HopIdx: 1
Total number of attempts: 3
Number of requests that failed to be sent out: 0
Number of responses that were received: 3
Number of requests that did not receive any response: 0
Total number of failures: 0, Percentage: 0
(in ms) Min Max Average Jitter
Outbound : 0.000 0.000 0.000 0.000
Inbound : 0.000 0.000 0.000 0.000
Roundtrip : 2.86 3.67 3.15 0.047
Per test packet:
Sequence Outbound Inbound RoundTrip Result
1 0.000 0.000 3.67 Response Received
2 0.000 0.000 2.92 Response Received
3 0.000 0.000 2.86 Response Received
HopIdx: 2
Total number of attempts: 3
Number of requests that failed to be sent out: 0
Number of responses that were received: 3
Number of requests that did not receive any response: 0
Total number of failures: 0, Percentage: 0
(in ms) Min Max Average Jitter
Outbound : 0.000 0.000 0.000 0.000
Inbound : 0.000 0.000 0.000 0.000
Roundtrip : 4.07 4.13 4.10 0.005
Per test packet:
Sequence Outbound Inbound RoundTrip Result
1 0.000 0.000 4.10 Response Received
2 0.000 0.000 4.13 Response Received
3 0.000 0.000 4.07 Response Received
==================================
CFM Two Way Delay Measurement:
===============================================================================
SAA Test Information
===============================================================================
Test name : CFMTwoWayDelayTest
Owner name : TiMOS CLI
Description : N/A
Accounting policy : None
Continuous : Yes
Administrative status : Enabled
Test type : eth-cfm-two-way-delay 00:01:01:01:01:01 mep 1 domain 1 association 1 interval 1
Trap generation : None
Test runs since last clear : 1
Number of failed test runs : 0
Last test result : Success
-------------------------------------------------------------------------------
Threshold
Type Direction Threshold Value Last Event Run #
-------------------------------------------------------------------------------
Jitter-in Rising None None Never None
Falling None None Never None
Jitter-out Rising None None Never None
Falling None None Never None
Jitter-rt Rising None None Never None
Falling None None Never None
Latency-in Rising None None Never None
Falling None None Never None
Latency-out Rising None None Never None
Falling None None Never None
Latency-rt Rising None None Never None
Falling None None Never None
Loss-in Rising None None Never None
Falling None None Never None
Loss-out Rising None None Never None
Falling None None Never None
Loss-rt Rising None None Never None
Falling None None Never None
...
===============================================================================
Test Run: 1
HopIdx: 1
Total number of attempts: 3
Number of requests that failed to be sent out: 0
Number of responses that were received: 3
Number of requests that did not receive any response: 0
Total number of failures: 0, Percentage: 0
Total number of failures: 0, Percentage: 0
(in us) Min Max Average Jitter
Outbound : 5095 5095 5095 0
Inbound : 5095 5095 0.000 0
Roundtrip : 10190 10190 10190 0
Per test packet:
Sequence (in us) Outbound Inbound Delay Delay variation
1 5195 5195 10190 0
2 5195 5195 10190 0
3 5195 5195 10190 0
...
===============================================================================
*A:ALA-48# show test-oam ldp-treetrace
Admin State : Up Discovery State : Done
Discovery-intvl (min) : 60 Probe-intvl (min) : 2
Probe-timeout (min) : 1 Probe-retry : 3
Trace-timeout (sec) : 60 Trace-retry : 3
Max-TTL : 30 Max-path : 128
Forwarding-class (fc) : be Profile : Out
Total Fecs : 400 Discovered Fecs : 400
Last Discovery Start : 12/19/2006 05:10:14
Last Discovery End : 12/19/2006 05:12:02
Last Discovery Duration : 00h01m48s
Policy1 : policy-1
Policy2 : policy-2
*A:ALA-48# show test-oam ldp-treetrace detail
Admin State : Up Discovery State : Done
Discovery-intvl (min) : 60 Probe-intvl (min) : 2
Probe-timeout (min) : 1 Probe-retry : 3
Trace-timeout (sec) : 60 Trace-retry : 3
Max-TTL : 30 Max-path : 128
Forwarding-class (fc) : be Profile : Out
Total Fecs : 400 Discovered Fecs : 400
Last Discovery Start : 12/19/2006 05:10:14
Last Discovery End : 12/19/2006 05:12:02
Last Discovery Duration : 00h01m48s
Policy1 : policy-1
Policy2 : policy-2
===============================================================================
Prefix (FEC) Info
===============================================================================
Prefix Path Last Probe Discov Discov
Num Discovered State State Status
-------------------------------------------------------------------------------
11.11.11.1/32 54 12/19/2006 05:10:15 OK Done OK
11.11.11.2/32 54 12/19/2006 05:10:15 OK Done OK
11.11.11.3/32 54 12/19/2006 05:10:15 OK Done OK
…………
14.14.14.95/32 72 12/19/2006 05:11:13 OK Done OK
14.14.14.96/32 72 12/19/2006 05:11:13 OK Done OK
14.14.14.97/32 72 12/19/2006 05:11:15 OK Done OK
14.14.14.98/32 72 12/19/2006 05:11:15 OK Done OK
14.14.14.99/32 72 12/19/2006 05:11:18 OK Done OK
14.14.14.100/32 72 12/19/2006 05:11:20 OK Done OK
===============================================================================
Legend: uP - unexplored paths, tO - trace request timed out
mH - max hop exceeded, mP - max path exceeded
nR - no internal resource
*A:ALA-48# show test-oam ldp-treetrace prefix 12.12.12.10/32
Discovery State : Done Last Discovered : 12/19/2006 05:11:02
Discovery Status : ' OK '
Discovered Paths : 54 Failed Hops : 0
Probe State : OK Failed Probes : 0
*A:ALA-48# show test-oam ldp-treetrace prefix 12.12.12.10/32 detail
Discovery State : Done Last Discovered : 12/19/2006 05:11:02
Discovery Status : ' OK '
Discovered Paths : 54 Failed Hops : 0
Probe State : OK Failed Probes : 0
===============================================================================
Discovered Paths
===============================================================================
PathDest Egr-NextHop Remote-RtrAddr Discovery-time
DiscoveryTtl ProbeState ProbeTmOutCnt RtnCode
-------------------------------------------------------------------------------
127.1.0.5 10.10.1.2 12.12.12.10 12/19/2006 05:11:01
7 OK 0 EgressRtr
127.1.0.9 10.10.1.2 12.12.12.10 12/19/2006 05:11:01
7 OK 0 EgressRtr
127.1.0.15 10.10.1.2 12.12.12.10 12/19/2006 05:11:01
7 OK 0 EgressRtr
127.1.0.19 10.10.1.2 12.12.12.10 12/19/2006 05:11:01
7 OK 0 EgressRtr
127.1.0.24 10.10.1.2 12.12.12.10 12/19/2006 05:11:01
7 OK 0 EgressRtr
127.1.0.28 10.10.1.2 12.12.12.10 12/19/2006 05:11:01
……………..
127.1.0.252 10.10.1.2 12.12.12.10 12/19/2006 05:11:01
7 OK 0 EgressRtr
127.1.0.255 10.10.1.2 12.12.12.10 12/19/2006 05:11:01
7 OK 0 EgressRtr
===============================================================================
*A:ALA-48#
*A:ALA-48# show test-oam twamp server
==============================================================================
TWAMP Server (port 862)
==============================================================================
Admin State : Up Oper State : Up
Up Time : 0d 00:00:05
Curr Conn : 1 Max Conn : 32
ConnTimeout : 1800 Conn Reject : 2
Curr Sess : 2 Max Sess : 32
Tests Done : 5 Tests Rej : 0
Tests Abort : 0
TstPktsRx : 999 TstPktsTx : 999
==============================================================================Prefix : 10.0.0.0/8
Description : NMS-West
==============================================================================
Admin State : Up Oper State : Up
Curr Conn : 1 Max Conn : 32
Conn Reject : 0
Curr Sess : 2 Max Sess : 32
Tests Done : 5 Tests Rej : 0
Tests Abort : 0
TstPktsRx : 999 TstPktsTx : 999
------------------------------------------------------------------------------
Client Sessions Idle TstPktsRx TstPktsTx
Curr/Done/Rej/Abort
------------------------------------------------------------------------------
10.1.1.1 2/5/0/0 920 999 999
==============================================================================
==============================================================================Prefix : 10.0.0.0/16
Description : NMS-West-Special
==============================================================================
Admin State : Up Oper State : Up
Curr Conn : 0 Max Conn : 32
Conn Reject : 0
Curr Sess : 0 Max Sess : 32
Tests Done : 0 Tests Rej : 0
Tests Abort : 0
TstPktsRx : 0 TstPktsTx : 0
------------------------------------------------------------------------------
Client Sessions Idle TstPktsRx TstPktsTx
Curr/Done/Rej/Abort
------------------------------------------------------------------------------
==============================================================================
ALU-IPD# show eth-cfm association
===============================================================================
CFM Association Table
===============================================================================
Md-index Ma-index Name CCM-intrvl Hold-time Bridge-id
-------------------------------------------------------------------------------
3 1 03-0000000100 1 n/a 100
10 1 FacilityPrt01 1 n/a none
===============================================================================
ALU-IPD#
cfm-stack-table [{all-ports|all-sdps|all-virtuals}] [level 0..7] [direction up|down]
cfm-stack-table facility [{all-ports
|all-lags
|all-lag
-ports
|all-tunnel-meps
|all-router-interfaces
}] [level
0..7] [direction
up|down
]
# show eth-cfm cfm-stack-table
===============================================================================
CFM Stack Table Defect Legend:
R = Rdi, M = MacStatus, C = RemoteCCM, E = ErrorCCM, X = XconCCM, A = AisRx
===============================================================================
CFM SAP Stack Table
===============================================================================
Sap Lvl Dir Md-index Ma-index MepId Mac-address Defect
-------------------------------------------------------------------------------
lag-1:100.100 3 Down 3 1 101 d0:0d:1e:00:01:01 ------
===============================================================================
===============================================================================
CFM Ethernet Tunnel Stack Table
===============================================================================
Eth-tunnel Lvl Dir Md-index Ma-index MepId Mac-address Defect
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
===============================================================================
CFM Ethernet Ring Stack Table
===============================================================================
Eth-ring Lvl Dir Md-index Ma-index MepId Mac-address Defect
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
===============================================================================
CFM Facility Port Stack Table
===============================================================================
Port Tunnel Lvl Dir Md-index Ma-index MepId Mac-address Defect
-------------------------------------------------------------------------------
1/1/10 0 0 Down 10 1 6 90:f4:01:01:00:0a --C---
===============================================================================
===============================================================================
CFM Facility LAG Stack Table
===============================================================================
Lag Tunnel Lvl Dir Md-index Ma-index MepId Mac-address Defect
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
===============================================================================
CFM Facility Interface Stack Table
===============================================================================
Interface Lvl Dir Md-index Ma-index MepId Mac-address Defect
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
===============================================================================
CFM SDP Stack Table
===============================================================================
Sdp Lvl Dir Md-index Ma-index MepId Mac-address Defect
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
===============================================================================
CFM Virtual Stack Table
===============================================================================
Service Lvl Dir Md-index Ma-index MepId Mac-address Defect
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
domain [md-index] [association
ma-index | all-associations
] [detail
]
*A:node-1# show eth-cfm domain
===============================================================================
CFM Domain Table
===============================================================================
Md-index Level Name Format
-------------------------------------------------------------------------------
1 4 test-1 charString
2 5 none
25 7 AA:BB:CC:DD:EE:FF-1 macAddressAndUint
===============================================================================
mep mep-id domain
md-index association
ma-index [loopback
] [linktrace
]
mep mep-id domain md-index association ma-index [remote-mepid
mep-id | all-remote-mepids
]
mep mep-id domain md-index association ma-index eth-test-results
[remote-peer
mac-address]
mep mep-id domain md-index association ma-index one-way-delay-test
[remote-peer
mac-address]
mep mep-id domain md-index association ma-index two-way-delay-test
[remote-peer
mac-address]
mep mep-id domain
md-index association
ma-index two-way-slm-test [remote-peer
mac-address]
# show eth-cfm mep 101 domain 3 association 1
===============================================================================
Eth-Cfm MEP Configuration Information
===============================================================================
Md-index : 3 Direction : Down
Ma-index : 1 Admin : Enabled
MepId : 101 CCM-Enable : Enabled
IfIndex : 1342177281 PrimaryVid : 6553700
Description : (Not Specified)
FngState : fngReset ControlMep : False
LowestDefectPri : macRemErrXcon HighestDefect : none
Defect Flags : None
Mac Address : d0:0d:1e:00:01:01 ControlMep : False
CcmLtmPriority : 7
CcmTx : 19886 CcmSequenceErr : 0
Fault Propagation : disabled FacilityFault : n/a
MA-CcmInterval : 1 MA-CcmHoldTime : 0ms
Eth-1Dm Threshold : 3(sec) MD-Level : 3
Eth-Ais: : Enabled Eth-Ais Rx Ais: : No
Eth-Ais Tx Priorit*: 7 Eth-Ais Rx Interv*: 1
Eth-Ais Tx Interva*: 1 Eth-Ais Tx Counte*: 388
Eth-Ais Tx Levels : 5
Eth-Tst: : Disabled
Redundancy:
MC-LAG State : active
CcmLastFailure Frame:
None
XconCcmFailure Frame:
None
===============================================================================
# show eth-cfm statistics
===============================================================================
ETH-CFM System Statistics
===============================================================================
Rx Count : 58300 Tx Count : 46723
Dropped Congestion : 0 Discarded Error : 0
===============================================================================
Rx Count: PPS ETH-CFM CPU Receive Rate
Tx Count: PPS ETH-CFM CPU Transmit Rate
Dropped Congestion: Valid/Supported ETH-CFM packets not processed
by the CPU as a result of resource contention
Discarded Error: Invalid/Malformed/Unsupported ETH-CFM packets
discarded by the CPU
# show eth-cfm system-config
===============================================================================
CFM System Configuration
===============================================================================
Redundancy
MC-LAG Standby MEP Shutdown: true
MC-LAG Hold-Timer : 1 second(s)
Synthetic Loss Measurement
Inactivity Timer : 100 second(s)
===============================================================================
|
Default
|
If a test-owner value is not specified, tests created by the CLI have a default owner “TiMOS CLI”.
|
