saa
config
This command enables the context to configure the SAA tests.
[no] test test-name [owner test-owner]
config>saa
This command identifies a test and creates or modifies the context to provide the test parameters for the named test. Subsequent to the creation of the test instance, the test can be started in the OAM context.
A test must be shut down before it can be modified or removed from the configuration.
The no form of this command removes the test from the configuration.
identifies the SAA test name to be created or edited
specifies the owner of an SAA operation, up to 32 characters in length
accounting-policy acct-policy-id]
no accounting-policy
config>saa>test
This command associates an accounting policy to the SAA test. The accounting policy must already be defined before it can be associated or else an error message is generated.
A notification (trap) is issued when a test is completed.
The no form of this command removes the accounting policy association.
specifies the accounting acct-policy-id as configured in the config>log>accounting-policy context
description description-string
no description
config>saa>test
This command creates a text description stored in the configuration file for a configuration context.
The no form of this command removes the string from the configuration.
no description
the description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, or spaces), the entire string must be enclosed within double quotes.
[no] continuous
config>saa>test
This command specifies whether the SAA test is continuous. Once you have configured a test as continuous, you cannot start or stop it by using the oam saa test-name {start | stop} command. This option is not applicable to all SAA test types.
The no form of the command disables the continuous execution of the test.
jitter-event rising-threshold threshold[falling-threshold threshold][direction]
no jitter-event
config>saa>test
This command specifies that at the termination of an SAA test probe, the calculated jitter value is evaluated against the configured rising and falling jitter thresholds. SAA threshold events are generated as required.
After the threshold (rising/falling) is crossed, it is disabled from generating additional events until the opposite threshold is crossed. If a falling threshold is not supplied, the rising threshold will be re-enabled when it falls below the threshold after the initial crossing that generated the event.
The configuration of jitter event thresholds is optional.
specifies a rising threshold jitter value. When the test run is completed, the calculated jitter value is compared to the configured jitter rising threshold. If the test run jitter value is greater than the configured rising threshold value, then an SAA threshold event is generated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
specifies a falling threshold jitter value. When the test run is completed, the calculated jitter value is compared to the configured jitter falling threshold. If the test run jitter value is greater than the configured falling threshold value, then an SAA threshold event is generated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
specifies the direction for OAM ping responses received for an OAM ping test run
latency-event rising-threshold threshold [falling-threshold threshold] [direction]
no latency-event
config>saa>test
This command specifies that at the termination of an SAA test probe, the calculated latency event value is evaluated against the configured rising and falling latency event thresholds. SAA threshold events are generated as required.
The configuration of latency event thresholds is optional.
specifies a rising threshold latency value. When the test run is completed, the calculated latency value is compared to the configured latency rising threshold. If the test run latency value is greater than the configured rising threshold value, then an SAA threshold event is generated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
specifies a falling threshold latency value. When the test run is completed, the calculated latency value is compared to the configured latency falling threshold. If the test run latency value is greater than the configured falling threshold value, then an SAA threshold event is generated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
specifies the direction for OAM ping responses received for an OAM ping test run
loss-event rising-threshold threshold [falling-threshold threshold] [direction]
no loss-event
config>saa>test
This command specifies that at the termination of an SAA test run, the calculated loss event value is evaluated against the configured rising and falling loss event thresholds. SAA threshold events are generated as required.
The configuration of loss event thresholds is optional.
specifies a rising threshold loss event value. When the test run is completed, the calculated loss event value is compared to the configured loss event rising threshold. If the test run loss event value is greater than the configured rising threshold value, then an SAA threshold event is generated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
specifies a falling threshold loss event value. When the test run is completed, the calculated loss event value is compared to the configured loss event falling threshold. If the test run loss event value is greater than the configured falling threshold value, then an SAA threshold event is generated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
specifies the direction for OAM ping responses received for an OAM ping test run
trap-gen
config>saa>test
This command enables the context to configure SNMP trap generation for the SAA test.
[no] probe-fail-enable
config>saa>test>trap-gen
This command works in conjunction with the probe-fail-threshold command. The command enables the generation of an SNMP trap after threshold consecutive probe failures during the execution of the SAA ping test. This command is not applicable to SAA trace route tests.
The no form of the command disables the generation of an SNMP trap.
probe-fail-threshold threshold
no probe-fail-threshold
config>saa>test>trap-gen
This command works in conjunction with the probe-fail-enable command. When the probe-fail-enable command is enabled, the generation of an SNMP trap occurs after threshold consecutive probe failures during the execution of the SAA ping test. This command is not applicable to SAA trace route tests.
This command has no effect when the probe-fail-enable command is disabled.
The no form of the command returns the threshold value to the default.
1
specifies the number of consecutive SAA ping probe failures before an SNMP trap is generated
[no] test-completion-enable
config>saa>test>trap-gen
This command enables the generation of an SNMP trap when an SAA test completes.
The no form of the command disables the trap generation.
[no] test-fail-enable
config>saa>test>trap-gen
This command enables the generation of an SNMP trap when a test fails. In the case of a ping test, the test is considered failed—for the purpose of trap generation—if the number of failed probes is at least the value of the test-fail-threshold threshold parameter.
The no form of the command disables the trap generation.
test-fail-threshold threshold
no test-fail-threshold
config>saa>test>trap-gen
This command configures the threshold for SNMP trap generation on test failure. This command is not applicable to SAA trace route tests.
This command has no effect when the test-fail-enable command is disabled.
The no form of the command returns the threshold value to the default.
1
specifies the number of consecutive test failures before an SNMP trap is generated
[no] type
config>saa>test
This command enables the context to provide the test type for the named test. Only a single test type can be configured.
A test can only be modified while the test is in shutdown mode.
When a test type has been configured, the command can be modified by re-entering the command. The test type must be the same as the previously entered test type.
To change the test type, the old command must be removed using the config>saa>test>no type command.
cpe-ping service service-id destination ip-address source ip-address[source-mac ieee-address][fc fc-name[profile {in | out}]][ttl vc-label-ttl][count send-count][send-control][return-control][timeout timeout][interval interval]
oam
config>saa>test>type
This ping utility determines the IP connectivity to a CPE within a specified VPLS service.
specifies the service ID or name of the service to diagnose or manage
specifies the IP address to be used as the destination for performing an OAM ping operation
specifies an unused IP address in the same network that is associated with the VPLS
specifies the profile state of the MPLS echo request encapsulation
specifies the source MAC address that will be sent to the CPE. If not specified or set to 0, the MAC address configured for the CSM is used.
specifies the forwarding class of the MPLS echo request encapsulation
specifies the TTL value in the VC label for the OAM MAC request, expressed as a decimal integer
specifies the number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
specifies the MAC OAM request be sent using the control plane instead of the data plane
specifies that the MAC OAM reply to a data plane MAC OAM request is sent using the control plane instead of the data plane
specifies the maximum amount of time, in seconds, that the router will wait for a message reply after sending the message request. The timeout parameter overrides the default timeout value. If the timeout expires, 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 value.
specifies the interval parameter in seconds, expressed as a decimal integer. This parameter is used to override the default request message send interval and defines the minimum amount of time that must expire before the next message request is sent.
If the interval is set to 1 s and the timeout value is set to 10 s, then the maximum time between message requests is 10 s and the minimum is 1 s. 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}]][count send-count][timeout timeout][interval interval]
config>saa>test>type
This command configures an Ethernet CFM linktrace test in SAA.
specifies a unicast destination MAC address
specifies the target MEP ID
specifies the MD index
specifies the MA index
specifies the number of hops to use in a linktrace test
specifies the forwarding class for CFM test traffic. The fc-name is mapped to the dot1p priority that is set in the CFM frame forwarding class. See Table: Priority Mapping Based on Message Type and MEP Direction for the Dot1p Priority-to-FC mapping.
specifies the profile state for CFM test traffic; this parameter is not used
specifies the number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
specifies the maximum amount of time, in seconds, that the router will wait for a message reply after sending the message request. The timeout parameter overrides the default timeout value. If the timeout expires, 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 value.
specifies the minimum amount of time, in seconds, that must expire before the next message request is sent. The interval parameter is used to override the default request message send interval. If the interval is set to 1 s, and the timeout value is set to 10 s, then the maximum time between message requests is 10 s and the minimum is 1 s. The timeout value must be less than the interval value.
eth-cfm-loopback mac-address mep mep-id domain md-index association ma-index[size data-size][fc fc-name [profile {in | out}]][count send-count][timeout timeout][interval interval]
config>saa>test>type
This command configures an Ethernet CFM loopback test in SAA.
specifies a unicast destination MAC address
specifies the target MEP ID
specifies the MD index
specifies the MA index
specifies the packet size in bytes, expressed as a decimal integer
specifies the forwarding class for CFM test traffic. The fc-name is mapped to the dot1p priority that is set in the CFM frame forwarding class. See Table: Priority Mapping Based on Message Type and MEP Direction for the Dot1p Priority-to-FC mapping.
specifies the profile state for CFM test traffic; this parameter is not used
specifies the number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
specifies the maximum amount of time, in seconds, that the router will wait for a message reply after sending the message request. The timeout parameter overrides the default timeout value. If the timeout expires, 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 value.
specifies the minimum amount of time, in seconds, that must expire before the next message request is sent. The interval parameter is used to override the default request message send interval. If the interval is set to 1 s, and the timeout value is set to 10 s, then the maximum time between message requests is 10 s and the minimum is 1 s. The timeout value must be less than the interval value.
eth-cfm-two-way-delay mac-address mep mep-id domain md-index association ma-index [fc {fc-name}[profile {in | out}]][count send-count][size data-size][timeout timeout][interval interval]
config>saa>test>type
This command configures an Ethernet CFM two-way delay test in SAA.
specifies a unicast MAC address
specifies the target MEP ID
specifies the MD index
specifies the MA index
specifies the forwarding class for CFM test traffic. The fc-name is mapped to the dot1p priority that is set in the CFM frame forwarding class. See Table: Priority Mapping Based on Message Type and MEP Direction for the Dot1p Priority-to-FC mapping.
specifies the profile state for CFM test traffic; this parameter is not used
specifies the number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
specifies the maximum amount of time, in seconds, that the router will wait for a message reply after sending the message request. The timeout parameter overrides the default timeout value. If the timeout expires, 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 value.
specifies the minimum amount of time, in seconds, that must expire before the next message request is sent. The interval parameter is used to override the default request message send interval. If the interval is set to 1 s, and the timeout value is set to 10 s, then the maximum time between message requests is 10 s and the minimum is 1 s. The timeout value must be less than the interval value.
eth-two-way-slm mac-address mep mep-id domain md-index association ma-index[fc fc-name[profile {in |out}]] [count send-count] [size data-size] [timeout timeout] [interval interval]
config>saa>test>type
This command specifies an Ethernet CFM two-way SLM test in SAA.
specifies a unicast MAC address
specifies the target MEP ID
specifies the MD index
specifies the MA index
specifies the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
specifies the profile state of the MPLS echo request encapsulation
the number of messages to send, expressed as a decimal integer. The message interval value must be expired before the next message request is sent.
the size of the data portion of the data TLV. If 0 is specified, no data TLV is added to the packet.
the timeout parameter in seconds. This value is the length of time that the router will wait for a message reply after sending the message request. If the timeout expires, 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 or equal to the interval.
the time, in seconds between probes within a test run
icmp-ping ip-address | dns-name [rapid] [ttl time-to-live] [tos type-of-service] [size bytes] [pattern pattern] [source ip-address] [interval seconds] [{next-hop ip-address}| {interface interface-name} | bypass-routing] [count requests] [do-not-fragment] [router router-instance | service-name service-name] [timeout timeout] [fc fc-name [profile {in | out}]]
config>saa>test>type
This command configures an ICMP ping test.
identifies the far-end IP address to which to send the icmp-ping request message in dotted-decimal notation
identifies the DNS name of the far-end device to which to send the icmp-ping request message, expressed as a character string up to 63 characters
changes the units for the interval from seconds to hundredths of seconds
specifies the TTL value for the MPLS label, expressed as a decimal integer
specifies the service type
specifies the request packet size in bytes, expressed as a decimal integer
specifies the pattern that will be used to fill the date portion in a ping packet. If no pattern is specified, position information will be filled instead.
specifies the IP address to be used
defines the minimum amount of time, expressed as a decimal integer, that must expire before the next message request is sent
This parameter is used to override the default request message send interval. If the interval is set to 1 s, and the timeout value is set to 10 s, then the maximum time between message requests is 10 s and the minimum is 1 s. This depends upon the receipt of a message reply corresponding to the outstanding message request.
displays only the static routes with the specified next-hop IP address
specifies the name of an IP interface. The name must already exist in the config>router>interface context.
specifies whether to send the ping request to a host on a directly attached network bypassing the routing table
specifies the number of times to perform an OAM ping probe operation. Each OAM echo message request must either time out or receive a reply before the next message request is sent.
sets the DF (Do not fragment) bit in the ICMP ping packet
specifies the router name or service ID
the service name, up to 64 characters
specifies the amount of time that the router will wait for a message reply after sending the message request. If the timeout expires, 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.
This value is used to override the default timeout value.
specifies the forwarding class for ICMP echo-request packets, which controls the marking of packets based on the configured SAP egress or network QoS policy. The packets use the egress data queue for the specified forwarding class. If the fc option is not specified, the ICMP echo-request packets use the nc forwarding class by default.
specifies the profile state of packets assigned to the specified forwarding class
icmp-trace [ip-address|dns-name] [ttl time-to-live] [wait milli-seconds] [source ip-address] [tos type-of-service] [router router-instance | service-name service-name]
config>saa>test>type
This command configures an ICMP traceroute test.
the far-end IP address to which to send the icmp-trace request message in dotted-decimal notation
the DNS name of the far-end device to which to send the icmp-trace request message, expressed as a character string
the TTL value for the MPLS label, expressed as a decimal integer
the time, in milliseconds, to wait for a response to a probe, expressed as a decimal integer
specifies the IP address to be used
specifies the service type
specifies the router name or service ID
the service name, up to 64 characters
lsp-ping lsp-name [path path-name]
lsp-ping bgp-label prefix ip-prefix/prefix-length [path-destination ip-address [interface if-name | next-hop ip-address]]
lsp-ping prefix ip-prefix/prefix-length [path-destination ip-address [interface if-name | next-hop ip-address]]
lsp-ping sr-isis prefix ip-prefix/prefix-length [igp-instance igp-instance] [path-destination ip-address [interface if-name | next-hop ip-address]]
lsp-ping sr-ospf prefix ip-prefix/prefix-length [igp-instance igp-instance] [path-destination ip-address [interface if-name | next-hop ip-address]]
lsp-ping sr-te lsp-name[path path-name] [path-destination ip-address [interface if-name| next-hop ip-address]]
- 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]
oam
config>saa>test>type
This command performs in-band LSP connectivity tests using the protocol and data structures defined in RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures.
The LSP ping operation is modeled after the IP ping utility, which uses ICMP echo request and reply packets to determine IP connectivity.
In an LSP ping, the originating device creates an MPLS echo request packet for the LSP and path to be tested. The MPLS echo request packet is sent through the data plane and waits for an MPLS echo reply packet from the device terminating the LSP. The status of the LSP is displayed when the MPLS echo reply packet is received.
The detail parameter is available only from the oam context.
specifies a unique LSP name, up to 64 characters
specifies the name for the LSP path, up to 32 characters
specifies the address prefix and prefix length of the target BGP IPv4 label route
specifies the IP address of the path destination from the range 127/8. When the LDP FEC prefix is IPv6, the user must enter a 127/8 IPv4 mapped IPv6 address, that is, in the range ::ffff:127/104.
specifies the name of an IP interface. The name must already exist in the config>router>interface context.
specifies the next-hop IP address to send the MPLS echo request message to
specifies the address prefix and prefix length of the destination node
specifies the address prefix and prefix length of the target node SID of the SR-ISIS tunnel
specifies the IGP instance
specifies the address prefix and prefix length of the target node SID of the SR-OSPF tunnel
indicates the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
The LSP-EXP mappings on the receive network interface control the mapping back to the internal forwarding class used by the far-end 7705 SAR that receives the message request. The egress mappings of the egress network interface on the far-end 7705 SAR control the forwarding class markings on the return reply message.
The LSP-EXP mappings on the receive network interface control the mapping of the message reply back at the originating 7705 SAR.
specifies the profile state of the MPLS echo request encapsulation
specifies the minimum amount of time that must expire before the next message request is sent
If the interval is set to 1 s, and the timeout value is set to 10 s, the maximum time between message requests is 10 s and the minimum is 1 s. This depends upon the receipt of a message reply corresponding to the outstanding message request.
This parameter is used to override the default request message send 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 time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
specifies the MPLS echo request packet size in octets, expressed as a decimal integer. The request payload is padded with zeros to the specified size.
specifies the IP address to be used when an OAM packet must be generated from an address other than the node system interface address
specifies the amount of time that the router will wait for a message reply after sending the message request. If the timeout expires, 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.
This value is used to override the default timeout value.
specifies the TTL value for the MPLS label, expressed as a decimal integer
displays detailed information
lsp-trace lsp-name[path path-name]
lsp-trace bgp-label prefix ip-prefix/prefix-length[path-destination ip-address[interface if-name| next-hop ip-address]]
lsp-trace prefix ip-prefix/prefix-length[path-destination ip-address[interface if-name| next-hop ip-address]]
lsp-trace sr-isis prefix ip-prefix/prefix-length[igp-instance igp-instance] [path-destination ip-address[{interface if-name| next-hop ip-address}]]
lsp-trace sr-ospf prefix ip-prefix/prefix-length[igp-instance igp-instance] [path-destination ip-address[{interface if-name| next-hop ip-address}]]
lsp-trace sr-te lsp-name [path path-name] [path-destination ip-address[{interface if-name | next-hop ip-address}]]
- 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]
oam
config>saa>test>type
This command displays the hop-by-hop path for an LSP traceroute using the protocol and data structures defined in RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures.
The LSP traceroute operation is modeled after the IP traceroute utility, which uses ICMP echo request and reply packets with increasing TTL values to determine the hop-by-hop route to a destination IP.
In an LSP traceroute, the originating device creates an MPLS echo request packet for the LSP to be tested with increasing values of the TTL in the outermost label. The MPLS echo request packet is sent through the data plane and waits for a TTL exceeded response or the MPLS echo reply packet from the device terminating the LSP. The devices that reply to the MPLS echo request packets with the TTL exceeded and the MPLS echo reply are displayed.
The downstream mapping TLV allows the sender and responder nodes to exchange and validate interface and label stack information for each downstream hop in an LDP FEC path, an RSVP LSP, a BGP-labeled IPv4 route, an SR-ISIS node SID, or an SR-OSPF node SID. If the responder node has multiple equal-cost next hops for the LDP FEC, BGP-labeled IPv4 prefix, SR-ISIS node SID, or SR-OSPF node SID, it replies in the downstream mapping TLV with the downstream information of each outgoing interface that is part of the ECMP next hop set for the prefix. The downstream mapping TLV can be further used to exercise a specific path of the ECMP set using the path-destination option.
The detail parameter is available only from the oam context.
specifies a unique LSP name, up to 64 characters
specifies the name for the LSP path, up to 32 characters
specifies the address prefix and prefix length of the target BGP IPv4 label route
specifies the IP address of the path destination from the range 127/8. When the LDP FEC prefix is IPv6, the user must enter a 127/8 IPv4 mapped IPv6 address, that is, in the range ::ffff:127/104.
specifies the name of an IP interface. The name must already exist in the config>router>interface context.
specifies the next-hop IP address to send the MPLS echo request message to
specifies the address prefix and prefix length of the destination node
specifies the address prefix and prefix length of the target node SID of the SR-ISIS tunnel
specifies the address prefix and prefix length of the target node SID of the SR-OSPF tunnel
specifies the IGP instance, 0 to 31
specifies which format of the downstream mapping TLV to use in the LSP trace packet
indicates the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
The LSP-EXP mappings on the receive network interface control the mapping back to the internal forwarding class used by the far-end 7705 SAR that receives the message request. The egress mappings of the egress network interface on the far-end 7705 SAR control the forwarding class markings on the return reply message.
The LSP-EXP mappings on the receive network interface control the mapping of the message reply back at the originating 7705 SAR.
specifies the profile state of the MPLS echo request encapsulation
specifies the minimum amount of time that must expire before the next message request is sent
If the interval is set to 1 s, and the timeout value is set to 10 s, the maximum time between message requests is 10 s and the minimum is 1 s. This depends upon the receipt of a message reply corresponding to the outstanding message request.
This parameter is used to override the default request message send interval.
specifies the maximum TTL value in the MPLS label for the LSP trace test, expressed as a decimal integer
specifies the minimum TTL value in the MPLS label for the LSP trace test, expressed as a decimal integer
specifies the maximum number of consecutive MPLS echo requests, expressed as a decimal integer, that do not receive a reply before the trace operation fails for a particular TTL
specifies the number of OAM requests sent for a particular TTL value, expressed as a decimal integer
specifies the MPLS echo request packet size in octets, expressed as a decimal integer. The request payload is padded with zeros to the specified size.
specifies the IP address to be used when an OAM packet must be generated from an address other than the node system interface address
specifies the amount of time that the router will wait for a message reply after sending the message request. If the timeout expires, 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.
This value is used to override the default timeout value.
displays detailed information
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] [count send-count] [send-control] [return-control] [interval interval] [timeout timeout]
oam
config>saa>test>type
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 plane.
A MAC ping reply can be sent using the control plane or the data 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 an FDB 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.
A control plane request is responded to via a control plane reply only.
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. If the MAC trace originated from a non-zero SHG, the packets will not go out to the same SHG.
the service ID or name of the service to diagnose or manage
the destination MAC address for the OAM MAC request
the source MAC address from which the OAM MAC request originates. By default, the system MAC address for the chassis is used.
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 MAC OAM request packet size in octets, expressed as a decimal integer. The request payload is padded to the specified size with a 6-byte PAD header and a byte payload of 0xAA as necessary. If the octet size specified is less than the minimum packet, the minimum size packet necessary to send the request is used.
the TTL value in the VC label for the OAM MAC request, expressed as a decimal integer
the number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
specifies the MAC OAM request be sent using the control plane instead of the data plane
specifies the MAC OAM reply to a data plane MAC OAM request be sent using the control plane instead of the data plane
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 s and the timeout value is set to 10 s, then the maximum time between message requests is 10 s and the minimum is 1 s. 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. If the timeout expires, 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-populate service-id mac ieee-address [flood] [age seconds] [force] [target-sap sap-id] [send-control]
oam
This command populates the FDB with an OAM-type MAC entry indicating the node is the egress node for the MAC address, and it optionally floods the OAM MAC association throughout the service. 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 for the MAC address is forwarded to the control plane (CSM). As a result, if the service on the node has neither an FDB nor an egress SAP, then it is not allowed to initiate a mac-populate command.
The MAC address that is populated in the FDB in the provider network is given a type OAM, so that it can be treated distinctly from regular dynamically learned or statically configured MACs. OAM MAC addresses are operational MAC addresses and are not saved in the device configuration. An exec file can be used to define OAM MACs after system initialization.
The force option in the mac-populate command forces the MAC in the table to be type OAM in case it already exists as a dynamic, static, or an OAM-induced learned MAC with some other type of 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 FDB 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 command or with an FDB clear operation.
When a split horizon group (SHG) is configured, the flooding domain depends on which SHG the packet originates from. The target-sap sap-id value dictates the originating SHG information.
the service ID or name of the service to diagnose or manage
the MAC address to be populated
sends the OAM MAC populate to all upstream nodes
the age for the OAM MAC, expressed as a decimal integer
converts the MAC to an OAM MAC even if it currently is another type of MAC
the local target SAP bound to a service on which to associate the OAM MAC. By default, the OAM MAC is associated with the control plane; that is, it is associated with the CPU on the router.
When the target-sap sap-id value is not specified, the MAC is bound to the CSM. The originating SHG is 0 (zero). When the target-sap sap-id value is specified, the originating SHG is the SHG of the target-sap.
specifies the MAC OAM request be sent using the control plane instead of the data plane
mac-purge service-id target ieee-address [flood ][send-control] [register] [force]
oam
This command removes an OAM-type MAC entry from the FDB and optionally floods the OAM MAC removal throughout the service. A mac-purge command 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.
A MAC address is purged only if it is marked as OAM. A mac-purge request is a packet with the following fields: the Reply Flags is set to 0 (since no reply is expected), and the Reply Mode and Reserved fields are set to 0. The Ethernet header has the source set to the (system) MAC address and the destination set to the broadcast MAC address. There is a VPN TLV in the FEC Stack TLV to identify the service domain.
If the register option is provided, the R bit in the Address Delete flags is turned on.
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 that 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 FDB for forwarding, but it is retained in the FDB 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).
The force option causes the specified OAM-type MAC entry to be purged from the FDB even if the entry was created by another node.
the service ID or name of the service to diagnose or manage
the MAC address to be purged (all zeros and multicast not allowed)
sends the OAM MAC purge to all upstream nodes
send the mac-purge request using the control plane
reserve the MAC for OAM testing
force the specified MAC entry to be purged, regardless of where the entry originated
mac-trace service service-id destination ieee-address [source ieee-address][fc fc-name [profile {in | out}]] [size octets] [min-ttl vc-label-ttl] [max-ttl vc-label-ttl] [probe-count send-count] [send-control] [return-control] [interval interval][timeout timeout]
oam
config>saa>test>type
This command displays the hop-by-hop path for a destination MAC address within a VPLS. The MAC trace operation is modeled after the IP traceroute utility, which uses ICMP echo request and reply packets with increasing TTL values to determine the hop-by-hop route to a destination IP address. The MAC trace command uses Nokia OAM packets with increasing TTL values to determine the hop-by-hop route to a destination MAC.
In a MAC trace, the originating device creates a MAC ping echo request packet for the MAC to be tested with increasing values of the TTL. The echo request packet is sent through the control plane or data plane and waits for a TTL exceeded response or the echo reply packet from the device with the destination MAC. The devices that reply to the echo request packets with the TTL exceeded and the echo reply are displayed.
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. If the MAC ping originated from a non-zero SHG, the packets will not go out to the same SHG.
the service ID or name of the service to diagnose or manage
the destination MAC address to be traced (all zeros not allowed)
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 MAC OAM request packet size in octets, expressed as a decimal integer. The request payload is padded to the specified size with a 6-byte PAD header and a byte payload of 0xAA as necessary. If the octet size specified is less than the minimum packet, the minimum size packet necessary to send the request is used.
the minimum TTL value in the VC label for the MAC trace test, expressed as a decimal integer
the maximum TTL value in the VC label for the MAC trace test, expressed as a decimal integer
specifies the MAC OAM request be sent using the control plane instead of the data plane
specifies the MAC OAM reply to a data plane MAC OAM request be sent using the control plane instead of the data plane
the number of MAC OAM requests sent for a particular TTL value, expressed as a decimal integer
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 s, and the timeout value is set to 10 s, then the maximum time between message requests is 10 s and the minimum is 1 s. 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. If the timeout expires, the requesting router assumes that the message response will not be received. Any response received after the request times out will be silently discarded.
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]
oam
This command performs an in-band connectivity test for an LDP point-to-multipoint LSP. An echo request message is sent on the active point-to-multipoint instance and is replicated in the data path over all branches of the point-to-multipoint LSP instance. By default, all egress LER nodes that are leaves of the point-to-multipoint LSP instance will reply to the echo request message.
An LDP point-to-multipoint generic identifier that includes the source IP address of the root node can be used to uniquely identify an LDP point-to-multipoint LSP in a network. The LDP p2mp-identifier is a mandatory parameter needed for the LSP ping test. The LDP P2MP ID specified when configuring a tunnel interface on the root node must be used as the p2mp-identifier to test a particular LSP.
The user can reduce the scope of the echo reply messages by explicitly entering a list of addresses for the egress LER nodes that are required to reply. A maximum of five addresses can be specified in a single run of the p2mp-lsp-ping command. An LER node parses the list of egress LER addresses, and if its address is included in the list, it will send back an echo reply message.
Without the detail option, the output of the command provides a high-level summary of error codes and success codes received. With the detail option, the output of the command shows a line for each replying node (similar to the output of the LSP ping for a point-to-point LSP).
The output display is delayed until all responses are received or the timer configured for the timeout parameter has expired. No other CLI commands can be entered while waiting for the display. The CLI break sequence <Ctrl-C> aborts the ping operation.
the fc and profile parameters are used to indicate the forwarding class and profile of the MPLS echo request packet.
When an MPLS echo request packet is generated in the CSM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc and profile parameter values. The marking of the packet EXP bits is dictated by the LSP-to-EXP mappings on the outgoing interface.
When the MPLS echo request packet is received on the responding node, the fc and profile parameter values are dictated by the LSP-to-EXP mappings of the incoming interface.
When an MPLS echo reply packet is generated in the CSM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the fc and profile parameter values determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The marking of the packet EXP bits is dictated by the LSP-to-EXP mappings on the outgoing interface. The ToS byte is not modified. The following table summarizes this behavior.
|
CSM (sender node) |
Echo request packet:
|
|
Outgoing interface (sender node) |
Echo request packet:
|
|
Incoming interface (responder node) |
Echo request packet:
|
|
CSM (responder node) |
Echo reply packet:
|
|
Outgoing interface (responder node) |
Echo reply packet:
|
|
Incoming interface (sender node) |
Echo reply packet:
|
identifier of an LDP point-to-multipoint LSP to ping
specifies the list of egress LER system addresses that are required to reply to an LSP ping echo request message
the profile of the LSP ping echo request message
specifies any local IP sender address for the mLDP
the size in octets, expressed as a decimal integer, of the MPLS echo request packet, including the IP header but not the label stack. An oam command does not fail if the size entered is lower than the minimum number of octets required to build the packet for the echo request message. The payload is automatically padded with zeros to meet the minimum size.
the timeout parameter, in seconds. This value is used to override the default timeout value and is the length of time that the router will wait for an echo reply message from all leaves of the point-to-multipoint LSP after sending the echo request message. When the timeout expires, the requesting router assumes that the missing replies will not be received. Any echo reply message received after the request times out will be silently discarded.
displays detailed information the connectivity test for an LDP point-to-multipoint LS P
sdp-ping orig-sdp-id [resp-sdp resp-sdp-id] [fc fc-name [profile {in | out}]] [size octets] [count send-count] [timeout timeout] [interval interval]
oam
config>saa>test>type
This command tests SDPs for unidirectional or round-trip connectivity and performs SDP MTU path tests.
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 unidirectional 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. Table: SDP Ping Response Messages displays the response messages sorted by precedence.
Result of Request |
Displayed Response Message |
Precedence |
|---|---|---|
Request timeout without reply |
Request Timeout |
1 |
Request not sent due to non-existent orig-sdp-id |
Orig-SDP Non-Existent |
2 |
Request not sent due to administratively down orig-sdp-id |
Orig-SDP Admin-Down |
3 |
Request not sent due to operationally down orig-sdp-id |
Orig-SDP Oper-Down |
4 |
Request terminated by user before reply or timeout |
Request Terminated |
5 |
Reply received, invalid origination-id |
Far End: Originator-ID Invalid |
6 |
Reply received, invalid responder-id |
Far End: Responder-ID Error |
7 |
Reply received, non-existent resp-sdp-id |
Far End: Resp-SDP Non-Existent |
8 |
Reply received, invalid resp-sdp-id |
Far End: Resp-SDP Invalid |
9 |
Reply received, resp-sdp-id down (admin or oper) |
Far-end: Resp-SDP Down |
10 |
Reply received, No Error |
Success |
11 |
a single response sdp-ping test provides detailed test results. Upon request timeout, message response, request termination, or request error, the local and remote information described in Table: Single Response Connectivity will be displayed. Local and remote information is dependent upon SDP-ID existence and reception of reply.
Field |
Description |
Values |
|---|---|---|
Request Result |
The result of the sdp-ping request message |
Sent - Request Timeout |
Sent - Request Terminated |
||
Sent - Reply Received |
||
Not Sent - Non-Existent Local SDP-ID |
||
Not Sent - Local SDP-ID Down |
||
Originating SDP-ID |
The originating SDP-ID specified by orig-sdp |
orig-sdp-id |
Originating SDP-ID Administrative State |
The local administrative state of the originating SDP-ID. If the SDP-ID has been shut down, Admin-Down is displayed. If the originating SDP-ID is in the no shutdown state, Admin-Up is displayed. If the orig-sdp-id does not exist, Non-Existent is displayed. |
Admin-Up |
Admin-Down |
||
Non-Existent |
||
Originating SDP-ID Operating State |
The local operational state of the originating SDP-ID. If orig-sdp-id does not exist, N/A will be displayed. |
Oper-Up |
Oper-Down |
||
N/A |
||
Originating SDP-ID Path MTU |
The local path-mtu for orig-sdp-id. If orig-sdp-id does not exist locally, N/A is displayed. |
orig-path-mtu |
N/A |
||
Responding SDP-ID |
The SDP-ID requested as the far-end path to respond to the sdp-ping request. If resp-sdp is not specified, the responding 7705 SAR will not use an SDP-ID as the return path and N/A will be displayed. |
resp-sdp-id |
N/A |
||
Responding SDP-ID Path Used |
Displays whether the responding 7705 SAR 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. |
Yes |
No |
||
N/A |
||
Responding SDP-ID Administrative State |
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-idexists on the far-end 7705 SAR but is not valid for the originating 7705 SAR, Invalid is displayed. When resp-sdp-iddoes not exist on the far-end 7705 SAR, Non-Existent is displayed. When resp-sdp is not specified, N/A is displayed. |
Admin-Down |
Admin-Up |
||
Invalid |
||
Non-Existent |
||
N/A |
||
Responding SDP-ID Operational State |
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. |
Oper-Up |
Oper-Down |
||
N/A |
||
Responding SDP-ID Path MTU |
The remote path-mtu for resp-sdp-id. If resp-sdp-id does not exist remotely, N/A is displayed. |
resp-path-mtu |
N/A |
||
Local Service IP Address |
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. |
system-ip-addr |
N/A |
||
Local Service IP Interface Name |
The name of the local system IP interface. If the local system IP interface has not been created, N/A is displayed. |
system-interface-name |
N/A |
||
Local Service IP Interface State |
The state of the local system IP interface. If the local system IP interface has not been created, Non-Existent is displayed. |
Up |
Down |
||
Non-Existent |
||
Expected Far End Address |
The expected IP address for the remote system IP interface. This must be the far-end address configured for the orig-sdp-id. |
orig-sdp-far-end-addr |
dest-ip-addr |
||
N/A |
||
Actual Far End Address |
The returned remote IP address. If a response is not received, the displayed value is N/A. If the far-end service IP interface is down or non-existent, a message reply is not expected. |
resp-ip-addr |
N/A |
||
Responders Expected Far End Address |
The expected source of the originator's SDP-ID from the perspective of the remote 7705 SAR terminating the SDP-ID. If the far end cannot detect the expected source of the ingress SDP-ID, N/A is displayed. |
resp-rec-tunnel-far-end-addr |
N/A |
||
Round Trip Time |
The round-trip time between SDP Echo Request and the SDP Echo Reply. If the request is not sent, times out or is terminated, N/A is displayed. |
delta-request-reply |
N/A |
When the connectivity test count is greater than one (1), a single line is displayed per SDP echo request send attempt.
The request number is a sequential number starting with 1 and ending with the last request sent, incrementing by 1 for each request. This should not be confused with the message-id contained in each request and reply message.
A response message indicates the result of the message request. Following the response message is the round-trip time value. If any reply is received, the round-trip time is displayed.
After the last reply has been received or response timed out, a total is displayed for all messages sent and all replies received. A maximum, minimum and average round-trip time is also displayed. Error response and timed-out requests do not apply toward the average round-trip time.
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 SDP tunnel encapsulation used to reach the far end — GRE, IP, 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).
specifies the return SDP-ID to be used by the far-end 7705 SAR for the message reply for round-trip SDP connectivity testing. If resp-sdp-id does not exist on the far-end 7705 SAR, terminates on another 7705 SAR different from the originating 7705 SAR, or another issue prevents the far-end 7705 SAR from using resp-sdp-id, the SDP echo reply will be sent using generic 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.
This is an optional parameter.
indicates the forwarding class of the SDP encapsulation. The actual forwarding class encoding is controlled by the network egress DSCP or LSP-EXP mappings.
The DSCP or LSP-EXP mappings on the receive network interface control the mapping back to the internal forwarding class used by the far-end 7705 SAR that receives the message request. The egress mappings of the egress network interface on the far-end 7705 SAR control the forwarding class markings on the return reply message.
The DSCP or LSP-EXP mappings on the receive network interface control the mapping of the message reply back at the originating 7705 SAR. This is displayed in the response message output upon receipt of the message reply.
specifies the profile state of the SDP encapsulation
the size of the packet 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.
When the OAM message request is encapsulated in an SDP, the IP DF (Do not fragment) bit is set. If any segment of the path between the sender and receiver cannot handle the message size, the message is discarded. MPLS LSPs are not expected to fragment the message either, as the message contained in the LSP is not an IP packet.
the number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
specifies the amount of time that the router will wait for a message reply after sending the message request. If the timeout expires, 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.
This value is used to override the default timeout value.
specifies 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.
This parameter is used to override the default request message send interval.
The following outputs are examples of SDP ping information.
Single Response Round-trip Connectivity Test Output ExampleA:router1> oam sdp-ping 10 resp-sdp 22 fc ef
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
==> IP Interface State: Up
Actual IP Address: 10.10.10.11 10.10.10.10
Expected Peer IP: 10.10.10.10 10.10.10.11
Forwarding Class ef ef
Profile Out Out
Request Result: Sent - Reply Received
RTT: 30ms
A:router1> oam sdp-ping 6 resp-sdp 101 size 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] [count send-count] [timeout timeout] [interval interval] [ttl vc-label-ttl]
oam
config>saa>test>type
This command configures a virtual circuit connectivity verification (VCCV) ping test. A VCCV ping test checks connectivity of a VLL in-band. It checks to verify that the destination (target) PE is the egress for the Layer 2 FEC. It provides for a cross-check between the data plane and the control plane. The test is in-band, 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. VCCV ping reuses an LSP ping message format and can be used to test a VLL configured over an MPLS, GRE, or IP SDP.
VCCV ping can be initiated on the terminating provider edge (T-PE) router or the switching provider edge (S-PE) router. The 7705 SAR can function as an S-PE or T-PE. If initiated on the S-PE, the reply-mode parameter must be used with the ip-routed value. The ping from the T-PE can have values or the values can be omitted.
VCCV ping can be initiated on a node with MC-LAG or MC-APS configured on it. If the node is in standby mode, and ICB is configured on the service, the reply-mode parameter must be used with the ip-routed value.
If a VCCV ping is initiated from a T-PE to a neighboring S-PE (one segment only), only the sdp-id:vc-id parameter must be used. However, if the ping is across two or more segments, the sdp-id:vc-id, src-ip-address ip-addr, dst-ip-address ip-addr, ttl vc-label-ttl and pw-id pw-id parameters must be used, where:
the src-ip-address is the system IP address of the router preceding the destination router
the pw-id is the VC ID of the last pseudowire segment
the vc-label-ttl must have a value equal to or greater than the number of pseudowire segments
VCCV ping on multi-segment pseudowires require that the control word be enabled in all segments of the VLL. If the control word is not enabled on spoke SDP it will not be signaled peer VCCV CC bits to the far end, consequently VCCV ping cannot be successfully initiated on that specific spoke SDP.
identifies the virtual circuit of the pseudowire being tested. The VC ID must exist on the local router and the far-end peer must indicate that it supports VCCV to allow the user to send a vccv-ping message.
This is a mandatory parameter.
specifies the source IP address
specifies the destination IP address
specifies the pseudowire ID to be used for performing a vccv-ping operation. The pseudowire ID is a non-zero, 32-bit connection ID required by the FEC 128, as defined in RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures.
specifies the method for sending the reply message to the far-end 7705 SAR
This is a mandatory parameter.
indicates the forwarding class of the MPLS echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
The LSP-EXP mappings on the receive network interface control the mapping back to the internal forwarding class used by the far-end 7705 SAR that receives the message request. The egress mappings of the egress network interface on the far-end router control the forwarding class markings on the return reply message.
The LSP-EXP mappings on the receive network interface control the mapping of the message reply back at the originating SAR.
specifies the profile state of the MPLS echo request encapsulation
specifies the VCCV ping echo request packet size in octets, expressed as a decimal integer. The request payload is padded with zeros to the specified size.
the number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
specifies the amount of time that the router will wait for a message reply after sending the message request. If the timeout expires, 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.
This value is used to override the default timeout value.
specifies 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.
This parameter is used to override the default request message send interval.
specifies the time-to-live value for the vc-label of the echo request message. The outer label TTL is still set to the default of 255 regardless of this value.
The following outputs are examples of VCCV ping information.
Output ExamplePing from T-PE to T-PE:
*A:ALU-dutb_a# oam vccv-ping 1:1 src-ip-address 192.0.2.0 dst-ip-address 192.0.2.1
pw-id 1
ttl 3
VCCV-PING 1:1 88 bytes MPLS payload
Seq=1, reply from 192.0.2.3 via Control Channel
udp-data-len=32 rtt=10ms rc=3 (EgressRtr)
---- VCCV PING 1:1 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 10.0ms, avg = 10.0ms, max = 10.0ms, stddev < 10ms
Ping from T-PE to S-PE:
*A:ALU-dut-b_a# oam vccv-ping 1:1
VCCV-PING 1:1 88 bytes MPLS payload
Seq=1, reply from 192.0.2.4 via Control Channel
udp-data-len=32 rtt<10ms rc=8 (DSRtrMatchLabel)
---- VCCV PING 1:1 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min < 10ms, avg < 10ms, max < 10ms, stddev < 10ms
*A:ALU-dut-b_a#
oam vccv ping 1:1 src-ip-address 192.0.2.5 dst-ip-address 192.0.2.6 ttl 2 pw-
id 200
VCCV-PING 1:1 88 bytes MPLS payload
Seq=1, reply from 192.0.2.7 via Control Channel
udp-data-len=32 rtt<10ms rc=8 (DSRtrMatchLabel)
---- VCCV PING 1:1 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min < 10ms, avg < 10ms, max < 10ms, stddev < 10ms
Ping from S-PE (on single or multi-segment):
*A:ALU-dut-b_a# oam vccv-ping 4:200 reply-mode ip-routed
VCCV-PING 4:200 88 bytes MPLS payload
Seq=1, reply from 192.0.2.7 via IP
udp-data-len=32 rtt<10ms rc=8 (DSRtrMatchLabel)
---- VCCV PING 4:200 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min < 10ms, avg < 10ms, max < 10ms, stddev < 10ms
*A:ALU-dut-b_a# oam vccv-ping 4:200 reply-mode ip-routed src-
ip address 192.0.2.8 dst ip-address 192.0.2.9 ttl 2 pw-id 1
VCCV-PING 4:200 88 bytes MPLS payload
Seq=1, reply from 192.0.2.10 via IP
udp-data-len=32 rtt<10ms rc=3 (EgressRtr)
---- VCCV PING 4:200 Statistics ----
1 packets sent, 1 packets received, 0.00% packet loss
round-trip min < 10ms, avg < 10ms, max < 10ms, stddev < 10ms
vccv-trace sdp-id:vc-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]
oam
config>saa>test>type
This command configures a Virtual Circuit Connectivity Verification (VCCV) automated trace test. The automated VCCV trace can trace the entire path of a PW with a single command issued at the terminating PE (T-PE) or at a switching PE (S-PE). VCCV trace 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 TTL values, starting from TTL=1.
In each iteration, the T-PE builds the MPLS echo request message in a way similar to VCCV ping. The first message (with TTL=1) includes the next-hop S-PE targeted LDP session source address in the Remote PE Address field of the PW FEC TLV. Each S-PE that terminates and processes the message will include the FEC 128 TLV corresponding to the PW segment to its downstream node in the MPLS echo reply message. The source T-PE or S-PE node can then build the next echo reply message with TTL=2 to test the next-next hop for the MS-PW. It will copy the FEC TLV it received in the echo reply message into the new echo request message. The process is terminated when the reply is from the egress T-PE or when a timeout occurs.
VCCV trace can be initiated on a node with MC-LAG or MC-APS configured on it. If the node is in standby mode, and ICB is configured on the service, the reply-mode parameter must be used with the ip-routed value.
The user can specify to display the result of the VCCV trace for a fewer number of PW segments of the end-to-end MS-PW path. In this case, the min-ttl and max-ttl parameters should be configured accordingly. However, the T-PE or S-PE node will still probe all hops up to min-ttl in order to correctly build the FEC of the desired subset of segments.
specifies the VC ID of the pseudowire being tested. The VC ID must exist on the local 7705 SAR and the far-end peer must indicate that it supports VCCV to allow the user to send a VCCV ping message.
specifies the VCCV ping echo request packet size, in octets, expressed as a decimal integer. The request payload is padded with zeros to the specified size.
specifies the TTL value for the VC label of the echo request message for the first hop of the MS-PW for which the results are to be displayed. This is expressed as a decimal integer. The outer label TTL is still set to the default of 255 regardless of the value of the VC label.
specifies the TTL value for the VC label of the echo request message for the last hop of the MS-PW for which the results are to be displayed. This is expressed as a decimal integer. The outer label TTL is still set to the default of 255 regardless of the value of the VC label.
specifies the maximum number of consecutive VCCV trace echo requests, expressed as a decimal integer, that do not receive a reply before the trace operation fails for a given TTL value.
specifies the number of VCCV trace echo request messages to send per TTL value
specifies the method for sending the reply message to the far-end 7705 SAR. This is a mandatory parameter.
specifies the timeout parameter, in seconds, expressed as a decimal integer. This value is used to override the default timeout value and is the amount of time that the 7705 SAR will wait for a message reply after sending the message request. If the timeout expires, the requesting 7705 SAR 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.
specifies the interval parameter, in seconds, expressed as a decimal integer. This parameter is used to override the default request message send interval and defines the minimum amount of time that must expire before the next message request is sent.
If the interval is set to 1 s and the timeout value is set to 10 s, then the maximum time between message requests is 10 s and the minimum is 1 s. This depends upon the receipt of a message reply corresponding to the outstanding message request.
specifies the forwarding class of the VCCV trace echo request encapsulation. The fc and profile parameters are used to indicate the forwarding class of the VCCV trace echo request packets. The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
The LSP-EXP mappings on the receive network interface control the mapping back to the internal forwarding class used by the far-end router that receives the message request. The egress mappings of the egress network interface on the far-end router control the forwarding class markings on the return reply message. The LSP-EXP mappings on the receive network interface control the mapping of the message reply back at the originating router.
specifies the profile state of the VCCV trace echo request encapsulation
displays detailed information
The following outputs are examples of VCCV trace information.
Output Example*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)
Trace with detail:
*A:ALU2>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)
----------------------------------------------
*A:ALU2>oam vccv-trace#
vprn-ping [service-id| service service-name] source ip-address destination ip-address [fc fc-name [profile [in | out]] [size size] [ttl vc-label-ttl ][count send-count] [return-control][ timeout timeout ][interval seconds]
oam
config>saa>test>type
This command performs a VPRN ping.
the VPRN service ID to diagnose or manage
the service name, up to 64 characters
the IP prefix for the source IP address
the IP prefix for the destination IP address
the OAM request packet size in octets, expressed as a decimal integer
the TTL value in the VC label for the OAM request, expressed as a decimal integer
specifies the response to come on the control plane.
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 number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. Each message request must either time out or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
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. If the timeout expires, 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 forwarding class of the MPLS echo request encapsulation
the profile state of the MPLS echo request encapsulation
The following output is an example of VPRN ping information.
Output ExampleA: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#
vprn-trace [service-id| service service-name] source ip-address destination ip-address[fc fc-name [profile [in | out]][size size][min-ttl vc-label-ttl][max-ttl vc-label-ttl][probe-count send-count][return-control][timeout timeout][interval seconds]
oam
config>saa>test>type
This command performs a VPRN trace.
the VPRN service ID to diagnose or manage
the service name, up to 64 characters
the IP prefix for the source IP address
the IP prefix for the destination IP address
the OAM request packet size in octets, expressed as a decimal integer
the minimum TTL value in the VC label for the trace test, expressed as a decimal integer
the maximum TTL value in the VC label for the trace test, expressed as a decimal integer
specifies the OAM reply to a data plane OAM request be sent using the control plane instead of the data plane
the number of OAM requests sent for a particular TTL value, expressed as a decimal integer
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. If the timeout expires, 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 forwarding class of the MPLS echo request encapsulation
the profile state of the MPLS echo request encapsulation
The following output is an example of VPRN trace information.
Output ExampleA: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 O wner 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.]
...
[no] enable-icmp-vse
config>system
This command is a global command that enables and disables one-way timestamping of outbound SAA ICMP ping packets. Enabling one-way timestamping on a 7705 SAR node requires enable-icmp-vse to be set on both the near-end and far-end nodes. The current status can be seen on the show>system>information CLI display.
The -vse part of the command means vendor-specific extension.
The no form of this command disables one-way timestamping.
no enable-icmp-vse