3.11. Diagnostics Command Reference
3.11.1. Command Hierarchies
3.11.1.1. OAM Commands
3.11.1.1.1. Base Operational Commands
3.11.1.1.1.1. LSP Diagnostics
3.11.1.1.1.2. LDP Diagnostics
3.11.1.1.1.4. TWAMP Light
3.11.1.1.1.5. SDP Diagnostics
3.11.1.1.1.6. Common Service Diagnostics
3.11.1.1.1.7. VLL Diagnostics
3.11.1.1.1.8. VPLS MAC Diagnostics
3.11.1.1.1.9. Ethernet in the First Mile (EFM) Commands
3.11.1.1.1.10. ETH-CFM OAM Commands
3.11.1.1.1.11. ETH CFM Configuration Commands
3.11.1.1.1.12. Y.1564 Testhead OAM commands
3.11.1.1.1.13. Y.1564 Testhead OAM Commands
3.11.1.1.2. Show commands
3.11.1.2. OAM Performance Monitoring, Bin Group, and Session Commands
3.11.1.2.1. OAM-PM Session IP Commands
3.11.1.2.2. Clear Commands
3.11.1.3. SAA Commands
 | Note: The following commands are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode:
|
3.11.1.3.1. Show Commands
3.11.1.3.2. Monitor Commands
3.11.2. Command Descriptions
3.11.2.1. OAM and SAA Command Hierarchies
3.11.2.1.1. Operational Commands
shutdown
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document.
Description
This command shuts down a test. To modify an existing test it must first be shut down. When a test is created it is in shutdown mode until a no shutdown command is executed.
A shutdown can only be performed if a test is not executing at the time the command is entered.
The no form of this command sets the state of the test to operational.
shutdown
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command suspends the background process running the LDP ECMP OAM tree discovery and path probing features. The configuration is not deleted.
The no form of this command enables the background process.
shutdown
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.
The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
Entities are created in the administratively down (shutdown) state. When a no shutdown command is entered, the entity becomes administratively up and then tries to enter the operationally up state.
The no form of this command administratively enables the entity.
dns
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command performs DNS name resolution. If ipv4-a-record is specified, DNS names are queried for A-records only.
Parameters
ipv4-address - a.b.c.d | |
ipv6-address - x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | |
x - [0..FFFF]H | |
d - [0..255]D | |
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
ping
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command verifies the reachability of a remote host.
Parameters
Note: IPv6 is supported only for "Management" instance of the router.
ipv4-address: | a.b.c.d | |
ipv6-address: | x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x: | [0 .. FFFF]H | |
d: | [0 .. 255]D | |
Note: IPv6 is supported only for "Management" instance of the router.
ipv4-address: | a.b.c.d | |
ipv6-address: | x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x: | [0 .. FFFF]H | |
d: | [0 .. 255]D | |
Note: IPv6 is supported only for "Management" instance of the router.
ipv4-address: | a.b.c.d (host bits must be 0) | |
ipv6-address: | x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x: | [0 to FFFF]H | |
d: | [0 to 255] | |
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
traceroute
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command determines the route to a destination address. DNS lookups of the responding hosts is enabled by default.
Parameters
Note: IPv6 is supported only for "Management" instance of the router.
ipv4-address: | a.b.c.d | |
ipv6-address: | x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x: | [0 .. FFFF]H | |
d: | [0 .. 255]D | |
lsp-ping
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command performs in-band LSP connectivity tests.
The lsp-ping command performs an LSP ping using the protocol and data structures defined in the RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures.
The LSP ping operation is modeled after the IP ping utility which uses ICMP echo request and reply packets to determine IP connectivity.
In an LSP ping, the originating device creates an MPLS echo request packet for the LSP and path to be tested. The MPLS echo request packet is sent through the data plane and awaits an MPLS echo reply packet from the device terminating the LSP. The status of the LSP is displayed when the MPLS echo reply packet is received.
This command, when used with the static option, performs in-band on-demand LSP connectivity verification tests for static MPLS-TP LSPs. For other LSP types, the static option should be excluded and these are described elsewhere in this guide.
The lsp-ping static command performs an LSP ping using the protocol and data structures defined in the RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, as extended by RFC 6426, MPLS On-Demand Connectivity Verification and Route Tracing.
In MPLS-TP, the echo request and echo reply messages are always sent in-band over the LSP, either in a G-ACh channel or encapsulated as an IP packet below the LSP label.
The timestamp format to be sent, and to be expected when received in a PDU, is as configured by the config>test-oam>mpls-time-stamp-format command. If RFC 4379 is selected, the timestamp is in seconds and microseconds since 1900, otherwise it is in seconds and microseconds since 1970.
Parameters
When an MPLS echo request packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc parameter value. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface.
When the MPLS echo request packet is received on the responding node, The fc parameter value is dictated by the LSP-EXP mappings of the incoming interface.
When an MPLS echo reply packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the fc parameter value determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface. The TOS byte is not modified. The following table summarizes this behavior:
Table 24: Request Packet and Behavior
Node | Packet and Description of Behavior |
cpm (sender node) | echo request packet:
|
outgoing interface (sender node) | echo request packet:
|
Incoming interface (responder node) | echo request packet:
|
cpm (responder node) | echo reply packet:
|
outgoing interface (responder node) | echo reply packet:
|
Incoming interface (sender node) | echo reply packet:
|
The LSP-EXP mappings on the receive network interface controls the mapping of the message reply back at the originating router.be
Output
lsp-trace
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document
Description
NOTE: Options common to all lsp-trace cases: [detail] [downstream-map-tlv {dsmap | ddmap | none}] [fc fc-name] [interval interval] [max-fail no-response-count] [max-ttl max-label-ttl] [min-ttl min-label-ttl] [probe-count probes-per-hop] [size octets] [src-ip-address ip-address] [timeout timeout]
This command, when used with the static option, performs in-band on-demand LSP traceroute tests for static MPLS-TP LSPs. For other LSP types, the static option should be excluded and these are described elsewhere in this guide.
The lsp-trace static command performs an LSP trace using the protocol and data structures defined in the RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, as extended by RFC 6426, MPLS On-Demand Connectivity Verification and Route Tracing.
The LSP trace operation is modeled after the IP traceroute utility which uses ICMP echo request and reply packets with increasing TTL values to determine the hop-by-hop route to a destination IP.
In an LSP trace, the originating device creates an MPLS echo request packet for the LSP to be tested with increasing values of the TTL in the outermost label. The MPLS echo request packet is sent through the data plane and awaits a TTL exceeded response or the MPLS echo reply packet from the device terminating the LSP. The devices that reply to the MPLS echo request packets with the TTL exceeded and the MPLS echo reply are displayed.
The downstream mapping TLV is used in lsp-trace to provide a mechanism for the sender and responder nodes to exchange and validate interface and label stack information for each downstream hop in the path of the LDP FEC or an RSVP LSP, or a BGP IPv4 label route.
Two downstream mapping TLVs are supported. The original Downstream Mapping (DSMAP) TLV defined in RFC 4379 and the new Downstream Detailed Mapping (DDMAP) TLV defined in RFC 6424. More details are provided in the following DDMAP TLV sub-section.
In addition, when the responder node has multiple equal cost next-hops for an LDP FEC or a BGP label IPv4 prefix, it replies in the Downstream Mapping TLV with the downstream information for each outgoing interface which is part of the ECMP next-hop set for the prefix. The downstream mapping TLV can further be used to exercise a specific path of the ECMP set using the path-destination option.
In MPLS-TP, the echo request and echo reply messages are always sent in-band over the LSP, either in a G-ACh channel or encapsulated as an IP packet below the LSP label.
Some caveats apply when using this feature on 7210 nodes. LSP Diagnostics: LSP Ping and Trace
Parameters
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
When an MPLS echo request packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc parameter value. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface.
When the MPLS echo request packet is received on the responding node, The fc parameter value is dictated by the LSP-EXP mappings of the incoming interface.
When an MPLS echo reply packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the fc parameter value determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface. The TOS byte is not modified. The following table summarizes this behavior:
Table 25: Request Packet and Behavior
Node | Packet and Description |
cpm (sender node) | echo request packet:
|
outgoing interface (sender node) | echo request packet:
|
Incoming interface (responder node) | echo request packet:
|
cpm (responder node) | echo reply packet:
|
outgoing interface (responder node) | echo reply packet:
|
Incoming interface (sender node) | echo reply packet:
|
Output
p2mp-lsp-ping
Syntax
Context
Supported Platforms
7210 SAS Mxp, 7210 SAS- R6, 7210 SAS-R12, 7210 SAS-T, and 7210 SAS-Sx/S 1/10GE (standalone mode)
Description
This command performs an in-band connectivity test for an RSVP P2MP LSP.
The echo request message is sent on the active P2MP instance and is replicated in the data path over all branches of the P2MP LSP instance. By default, all egress LER nodes that are leaves of the P2MP LSP instance reply to the echo request message.
The user can reduce the scope of the echo reply messages by explicitly entering a list of addresses for the egress LER nodes that are required to reply. A maximum of 5 addresses can be specified in a single run of the p2mp-lsp-ping command. An LER node parses the list of egress LER addresses, and if its address is included, it replies with an echo reply message.
The display is delayed until all responses are received or the timer configured in the timeout parameter expires. Entering other CLI commands while waiting for the display is not allowed. Use control-C (^C) to stop the ping operation.
Parameters
When an MPLS echo request packet is generated in CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc parameter value. The LSP-EXP mappings on the outgoing interface dictate the marking of the packet EXP bits.
When the MPLS echo request packet is received on the responding node, the LSP-EXP mappings of the incoming interface determine the fc parameter value.
When an MPLS echo reply packet is generated in CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the fc parameter value determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The LSP-EXP mappings on the outgoing interface dictate the marking of the packet EXP bits.
Output
The following sample output is an example of P2MP LSP ping information.
p2mp-lsp-trace
Syntax
Context
Supported Platforms
7210 SAS Mxp, 7210 SAS- R6, 7210 SAS-R12, 7210 SAS-T, and 7210 SAS-Sx/S 1/10GE (standalone mode)
Description
This command discovers and displays the hop-by-hop path for a source-to-leaf (S2L) sub-LSP of an RSVP P2MP LSP.
The LSP trace capability allows the user to trace the path of a single S2L path of a P2MP LSP. Its operation is similar to that of the p2mp-lsp-ping, but the sender of the echo reply request message includes the downstream mapping TLV to request the downstream branch information from a branch LSR or bud LSR. The branch LSR or bud LSR also includes the downstream mapping TLV to report the information about the downstream branches of the P2MP LSP. An egress LER must not include this TLV in the echo response message.
The probe-count parameter operates in the same way as in LSP Trace on a P2P LSP. It represents the maximum number of probes sent per TTL value before giving up on receiving the echo reply message. If a response is received from the traced node before reaching maximum number of probes, no more probes are sent for the same TTL. The sender of the echo request increments the TTL and uses the information it received in the downstream mapping TLV to start sending probes to the node downstream of the last node which replied. This continues until the egress LER for the traced S2L path replied.
Similar to the p2mp-lsp-ping command, an LSP trace probe results in all egress LER nodes eventually receiving the echo request message, but only the traced egress LER node replies to the last probe.
Any branch LSR node or bud LSR node in the P2MP LSP tree may receive a copy of the echo request message with the TTL in the outer label expiring at this node. However, only a branch LSR or bud LSR that has a downstream branch over which the traced egress LER is reachable responds.
When a branch LSR or bud LSR responds, it sets the global return code in the echo response message to RC=14, “See DDMAP TLV for Return Code and Return Sub-Code” and the return code in the DDMAP TLV corresponding to the outgoing interface of the branch used by the traced S2L path to RC=8, “Label switched at stack-depth <RSC>”.
Parameters
When an MPLS echo request packet is generated in CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc parameter value. The LSP-EXP mappings on the outgoing interface dictate the marking of the packet EXP bits.
When the MPLS echo request packet is received on the responding node, the LSP-EXP mappings of the incoming interface dictate the marking of the packet EXP bits.
When an MPLS echo reply packet is generated in CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the fc parameter value determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The LSP-EXP mappings on the outgoing interface dictate the marking of the packet EXP bits.
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of an echo reply message corresponding to the outstanding message request.
Output
The following sample output is an example of P2MP LSP trace information.
3.11.2.1.2. Service Diagnostics
sdp-mtu
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command 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 specific SDP-ID. The forwarding class is assumed to be Best-Effort Out-of-Profile. The message reply is returned with IP encapsulation from the far-end 7210 SAS M. OAM request messages sent within an IP SDP must have the ‘DF’ IP header bit set to 1 to prevent message fragmentation. This command is not supported on the 7210 SAS-M and 7210 SAS-T in the access-uplink mode of operation.
To terminate an sdp-mtu in progress, use the CLI break sequence <Ctrl-C>.
Special Cases
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.
As the request message is sent, its size value is displayed followed by a period for each request sent of that size. Up to three requests are sent unless a valid response is received for one of the requests at that size. When a response is received, the next size message is sent. The response message indicates the result of the message request.
After the last reply has been received or response timeout, the maximum size message replied to indicates the largest size OAM Request message that received a valid reply.
Parameters
If the incremented size exceeds the end-octets value, no more messages are sent.
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
Output
svc-ping
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command tests a service ID for correct and consistent provisioning between two service end points. This command is not supported on the 7210 SAS-M and 7210 SAS-T in the access-uplink mode of operation.
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:
- Local and remote service existence
- Local and remote service state
- Local and remote service type correlation
- Local and remote customer association
- Local and remote service-to-SDP bindings and state
- Local and remote ingress and egress service label association
Unlike sdp-ping, only a single message is 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
If no request is sent or a reply is not received, all remote information is shown as N/A.
To terminate a svc-ping in progress, use the CLI break sequence <Ctrl-C>.
Upon request timeout, message response, request termination, or request error the following local and remote information is displayed. Local and remote information is dependent upon service existence and reception of reply.
Field | Description | Values |
Request Result | The result of the svc-ping request message. | Sent - Request Timeout |
Sent - Request Terminated | ||
Sent - Reply Received | ||
Not Sent - Non-Existent Service-ID | ||
Not Sent - Non-Existent SDP for Service | ||
Not Sent - SDP For Service Down | ||
Not Sent - Non-existent Service Egress Label | ||
Service-ID | The ID of the service being tested. | service-id |
Local Service Type | The type of service being tested. If service-id does not exist locally, N/A is displayed. | Epipe |
TLS | ||
IES | ||
Mirror-Dest | ||
N/A | ||
Local Service Admin State | The local administrative state of service-id. If the service does not exist locally, the administrative state is Non-Existent. | Admin-Up |
Admin-Down | ||
Non-Existent | ||
Local Service Oper State | The local operational state of service-id. If the service does not exist locally, the state is N/A. | Oper-Up |
Oper-Down | ||
N/A | ||
Remote Service Type | The remote type of service being tested. If service-id does not exist remotely, N/A is displayed. | Epipe, Ipipe |
TLS | ||
IES | ||
Mirror-Dest | ||
N/A | ||
Remote Service Admin State | The remote administrative state of service-id. If the service does not exist remotely, the administrative state is Non-Existent. | Up |
Down | ||
Non-Existent | ||
Local Service MTU | The local service-mtu for service-id. If the service does not exist, N/A is displayed. | service-mtu |
N/A | ||
Remote Service MTU | The remote service-mtu for service-id. If the service does not exist remotely, N/A is displayed. | remote-service-mtu |
N/A | ||
Local Customer ID | The local customer-id associated with service-id. If the service does not exist locally, N/A is displayed. | customer-id |
N/A | ||
Remote Customer ID | The remote customer-id associated with service-id. If the service does not exist remotely, N/A is displayed. | customer-id |
N/A | ||
Local Service IP Address | 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. | system-ip-address |
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 entered for the svc-ping command. | 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. sdp-ping should also fail. | 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 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. | resp-rec-tunnel-far-end-address |
N/A | ||
Originating SDP-ID | 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. | orig-sdp-id |
Non-Existent | ||
Originating SDP-ID Path Used | 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. | Yes |
No | ||
N/A | ||
Originating SDP-ID Administrative State | 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. | Admin-Up |
Admin-Up | ||
N/A | ||
Originating SDP-ID Operating State | The local operational state of the originating sdp-id. If an originating sdp-id is not found, N/A is displayed. | Oper-Up |
Oper-Down | ||
N/A | ||
Originating SDP-ID Binding Admin State | 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. | Admin-Up |
Admin-Up | ||
N/A | ||
Originating SDP-ID Binding Oper State | 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. | Oper-Up |
Oper-Down | ||
N/A | ||
Responding SDP-ID | 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 does not use an sdp-id as the return path, but the appropriate responding sdp-id is 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. | resp-sdp-id |
Non-Existent | ||
Responding SDP-ID Path Used | 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. | Yes |
No | ||
N/A | ||
Responding SDP-ID Administrative State | 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. | Admin-Up |
Admin-Up | ||
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 Binding Admin State | 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. | Admin-Up |
Admin-Down | ||
N/A | ||
Responding SDP-ID Binding Oper State | 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. | Oper-Up |
Oper-Down | ||
N/A | ||
Originating VC-ID | 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. | originator-vc-id |
N/A | ||
Responding VC-ID | 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. | responder-vc-id |
N/A | ||
Originating Egress Service Label | 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. | egress-vc-label |
N/A | ||
Non-Existent | ||
Originating Egress Service Label Source | The originating egress service label source. If the displayed egress service label is manually defined, Manual is displayed. If the egress service label is dynamically signaled, Signaled is displayed. If the service-id does not exist or the egress service label is non-existent, N/A is displayed. | Manual |
Signaled | ||
N/A | ||
Originating Egress Service Label State | 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. | Up |
Down | ||
N/A | ||
Responding Service Label | 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. | rec-vc-label |
N/A | ||
Non-Existent | ||
Responding Egress Service Label Source | The responder’s egress service label source. If the responder’s egress service label is manually defined, Manual is displayed. If the responder’s egress service label is dynamically signaled, Signaled is displayed. If the service-id does not exist on the responder or the responder’s egress service label is non-existent, N/A is displayed. | Manual |
Signaled | ||
N/A | ||
Responding Service Label State | The responding egress service label state. If the responding router considers it is an egress service label operational, Up is displayed. If the responding router considers it is an 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. | Up |
Down | ||
N/A | ||
Expected Ingress Service Label | 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. | ingress-vc-label |
N/A | ||
Non-Existent | ||
Expected Ingress Label Source | The originator’s ingress service label source. If the originator’s ingress service label is manually defined, Manual is displayed. If the originator’s ingress service label is dynamically signaled, Signaled is displayed. If the service-id does not exist on the originator or the originators ingress service label has not been assigned, N/A is displayed. | Manual |
Signaled | ||
N/A | ||
Expected Ingress Service Label State | The originator’s ingress service label state. If the originating router considers it as an ingress service label operational, Up is displayed. If the originating router considers it as an ingress service label inoperative, Down is displayed. If the service-id does not exist locally, N/A is displayed. | Up |
Down | ||
N/A | ||
Responders Ingress Service Label | 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. | resp-ingress-vc-label |
N/A | ||
Non-Existent | ||
Responders Ingress Label Source | 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. | Manual |
Signaled | ||
N/A | ||
Responders Ingress Service Label State | The assigned ingress service label state on the remote router. If the remote router considers it as an ingress service label operational, Up is displayed. If the remote router considers it as an 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. | Up |
Down | ||
N/A |
Parameters
If local-sdp is not specified, the svc-ping request message is sent with encapsulation with the OAM label.
The following table indicates whether a message is sent and how the message is encapsulated based on the state of the service ID.
Local Service State | local-sdp Not Specified | local-sdp Specified | ||
Message Sent | Message Encapsulation | Message Sent | Message Encapsulation | |
Invalid Local Service | Yes | Generic IP OAM (PLP) | No | None |
No Valid SDP-ID Bound | Yes | Generic IP OAM (PLP) | No | None |
SDP-ID Valid But Down | Yes | Generic IP OAM (PLP) | No | None |
SDP-ID Valid and Up, But No Service Label | Yes | Generic IP OAM (PLP) | No | None |
SDP-ID Valid, Up and Egress Service Label | Yes | Generic IP OAM (PLP) | Yes | SDP Encapsulation with Egress Service Label (SLP) |
The following table indicates how the message response is encapsulated based on the state of the remote service ID.
Remote Service State | Message Encapsulation | |
remote-sdp Not Specified | remote-sdp Specified | |
Invalid Ingress Service Label | Generic IP OAM (PLP) | Generic IP OAM (PLP) |
Invalid Service-ID | Generic IP OAM (PLP) | Generic IP OAM (PLP) |
No Valid SDP-ID Bound on Service-ID | Generic IP OAM (PLP) | Generic IP OAM (PLP) |
SDP-ID Valid But Down | Generic IP OAM (PLP) | Generic IP OAM (PLP) |
SDP-ID Valid and Up, but No Service Label | Generic IP OAM (PLP) | Generic IP OAM (PLP) |
SDP-ID Valid and Up, Egress Service Label, but VC-ID Mismatch | Generic IP OAM (PLP) | Generic IP OAM (PLP) |
SDP-ID Valid and Up, Egress Service Label, but VC-ID Match | Generic IP OAM (PLP) | SDP Encapsulation with Egress Service Label (SLP) |
Output
vprn-ping
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command performs a VPRN ping.
Parameters
ipv4-address | a.b.c.d |
ipv6-address | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x - [0 to FFFF]H | |
d - [0 to 255]D |
ipv4-address | a.b.c.d |
ipv6-address | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x - [0 to FFFF]H | |
d - [0 to 255]D |
If the interval is set to 1 second where the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
Output
vprn-trace
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document
Description
Performs VPRN trace.
Parameters
ipv4-address | a.b.c.d |
ipv6-address | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x - [0 to FFFF]H | |
d - [0 to 255]D |
ipv4-address | a.b.c.d |
ipv6-address | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x - [0 to FFFF]H | |
d - [0 to 255]D |
If the interval is set to 1 second where the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
Output
3.11.2.1.3. VPLS MAC Diagnostics
| Note: VPLS MAC diagnostics commands are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode. |
cpe-ping
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command determines the IP connectivity to a CPE within a specified VPLS service.
Parameters
If the interval is set to 1 second where the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
mac-populate
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document
Description
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, it is not allowed to initiate a mac-populate.
The MAC address that is populated in the FIBs in the provider network is specific a type OAM, so that it can be treated distinctly from regular dynamically learned or statically configured MACs. Note that 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 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.
When 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.
Parameters
When the target-sap sap-id value is not specified the MAC is bound to the CPM. 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.
mac-purge
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document.
Description
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.
A MAC address is purged only if it is marked as OAM. A mac-purge request is an HVPLS OAM packet, with the following fields. The Reply Flags is set to 0 (since no reply is expected), the Reply Mode and Reserved fields are set to 0. The Ethernet header has source set to the (system) MAC address, 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 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).
Parameters
mac-ping
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document.
Description
This command tests for the existence of an egress SAP binding of a specific MAC within a VPLS service.
A mac-ping packet can be sent through 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, 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 are trapped and sent up to the control plane.
A control plane request is responded to through 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), this SHG membership is used as if the packet originated from this SHG. In all other cases, SHG 0 (zero) is used. Note that if the mac-trace is originated from a non-zero SHG, such packets do not go out to the same SHG.
If EMG is enabled, mac-ping returns only the first SAP in each chain.
Parameters
If the interval is set to 1 second where the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
mac-trace
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays the hop-by-hop path for a destination MAC address within a VPLS.
The MAC 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. The MAC traceroute command uses Nokia OAM packets with increasing TTL values to determine the hop-by-hop route to a destination MAC.
In a MAC traceroute, 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 awaits 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), this SHG membership is used as if the packet originated from this SHG. In all other cases, SHG 0 (zero) is used. Note that if the mac-ping is originated from a non-zero SHG, such packets do not go out to the same SHG.
If EMG is enabled, mac-trace returns only the first SAP in each chain.
Parameters
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
3.11.2.1.4. EFM Commands
efm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables Ethernet in the First Mile (EFM) OAM loopback tests on the specified port.
Parameters
3.11.2.1.5. ETH-CFM OAM Commands
eth-test
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command issues an ETH-CFM test.
Parameters
linktrace
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
The command specifies to initiate a linktrace test.
Parameters
loopback
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
The command specifies to initiate a loopback test.
Parameters
one-way-delay-test
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command issues an ETH-CFM one-way delay test.
Parameters
two-way-delay-test
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command issues an ETH-CFM two-way delay test.
Parameters
two-way-slm-test
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures an Ethernet CFM two-way SLM test in SAA.
Parameters
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
3.11.2.1.6. ETH CFM Configuration Commands
eth-cfm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure 802.1ag CFM parameters.
domain
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures Connectivity Fault Management domain parameters.
The no form of this command removes the Maintenance Domain (MD) index parameters from the configuration.
Parameters
dns: | Specifies the DNS name format. | |
mac: | x:x:x:x:x:x-u | |
x: [0..ff]h | ||
u: | [0..65535]d | |
none: | Specifies a Y.1731 domain format and the only format allowed to execute Y.1731 specific functions. | |
string | Specifies an ASCII string. | |
association
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the Maintenance Association (MA) for the domain.
Parameters
icc-based: | Only applicable to a Y.1731 context where the domain format is configured as none, allows for exactly a 13 character name in raw ascii. |
integer | 0 to 65535 (integer value 0 means the MA is not attached to a VID.) |
string: | raw ascii |
vid: | 0 to 4094 |
vpn-id: | RFC-2685, Virtual Private Networks Identifier xxx:xxxx, where x is a value between 00 and ff. |
bridge-identifier
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the service ID for the domain association. The value must be configured to match the service ID of the service where MEPs for this association is created.
Note: The system does not verify whether a service has been created with a matching service ID.
Parameters
id-permission
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the inclusion of the Sender ID TLV information specified with the config>eth-cfm>system>sender-id command for installed MEPs and MIPs. When this option is present under the maintenance association, the specific MIPs in the association includes the Sender ID TLV information in ETH-CFM PDUs. MEPs include the Sender ID TLV for CCM (subsecond CCM-enabled MEPs do not support the Sender ID TLV) in LBM/LBR and LTM/LTR PDUs. MIPs include this value in the LBR and LTR PDUs.
NOTE: LBR functions reflect back all TLVs received in the LBM unchanged, including the Sender ID TLV. Transmission of the Management Domain and Management Address fields are not supported in this TLV.
The no form of this command disables the inclusion of the Sender ID TLV.
Default
no id-permission
Parameters
mhf-creation
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command determines whether to allow MIP creation for the MA. Use of the none, default and explicit parameters are only allowed for MHFs (MIPs) that are not associated with a configured primary VLAN.
The static parameter is only applicable to MHFs (MIPs) that are associated with a Primary VLAN.
| Note: Ingress MIPs and egress MIPs are supported on 7210 SAS platforms. Ingress MIPs respond to OAM messages received from the wire. Egress MIPs respond to OAM messages that are being sent out to the wire. |
See Table 12, Table 13, Table 14, Table 15, Table 16, Table 17, Table 18, and Table 19 for MEP and MIP support available for different services on different platforms.
Parameters
| Note: On 7210 SAS-R6 and 7210 SAS-R12, the default parameter is supported for Ingress MIPs only in a VPLS service and it is supported for MIP creation in an Epipe service. |
mip-ltr-priority
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to set the priority of the Linktrace Response Message (ETH-LTR) from a MIP for this association. If this command is not specified, an LTR priority of 7 is used.
Default
no mip-ltr-priority
Parameters
vlan
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the bridge identifier primary VLAN ID. Note that this configuration is optional as no verification is done to ensure that MEPs on this association are on the configured VLAN. When the primary VLAN feature is enabled for the MEP or a MIP, this is used to match with the VLAN in the packet to identify the packets to process in the context of the primary VLAN MIP/MEP.
Note: Also see the description for the config>eth-cfm>domain>association>bridge-identifier command.
Parameters
ccm-interval
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the CCM transmission interval for all MEPs in the association. See Table 26 to Table 28 for the CCM transmission interval values for each 7210 SAS platform.
Table 26: CCM Transmission Interval for 7210 SAS-M (Network Mode), 7210 SAS-T (Network Mode), 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10 GE (Standalone and Standalone-VC), and 7210 SAS-Sx 10/100GE
MEP Timer Support | 7210 SAS-M Network mode | 7210 SAS-T Network mode | 7210 SAS-Mxp | 7210 SAS-Sx /S 1/10GE | 7210 SAS-Sx 10/100 GE |
Service Down MEP | 100ms | 1 | 10 | 60 | 600 | 1 | 10 | 60 | 600 | 1 | 10 | 60 | 600 | 1 | 10 | 60 | 600 | 1 | 10 | 60 | 600 |
G8032 Down MEP | 100ms | 1 | 10 | 60 | 600 | 100ms | 1 | 10 | 60 | 600 | 10ms | 100ms | 1 | 10 | 60 | 600 | 10ms |100ms | 1 | 10 | 60 | 600 | 100ms | 1 | 10 | 60 | 600 |
Service UP MEP | 1 | 10 | 60 | 600 | 1 | 10 | 60 | 600 | 1 | 10 | 60 | 600 | 1 | 10 | 60 | 600 | 1 | 10 | 60 | 600 |
Table 27: CCM transmission interval for 7210 SAS-M and 7210 SAS-T (Access-Uplink Mode)
MEP Timer Support | 7210 SAS-M Access-Uplink mode | 7210 SAS-T Access-Uplink mode |
Service Down MEP | 100ms | 1 | 10 | 60 | 600 | 100ms | 1 | 10 | 60 | 600 |
G8032 Down MEP | 100ms | 1 | 10 | 60 | 600 | 100ms | 1 | 10 | 60 | 600 |
Service UP MEP | 1 | 10 | 60 | 600 | 1 | 10 | 60 | 600 |
Table 28: CCM transmission interval for 7210 SAS-R6 and 7210 SAS-R12
MEP Timer Support | 7210 SAS-R6 and 7210 SAS-R12 |
Service Down MEP | 1s |
G8032 Down MEP | 10ms |
Service UP MEP | 1s |
The no form of this command resets the value to the default.
Default
10 s
Parameters
remote-mepid
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the remote MEP identifier.
Parameters
slm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command specifies the container that provides the global configuration parameters for ITU-T Synthetic Loss Measurement (ETH-SL).
inactivity-timer
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the length of time that the responder keeps a test active. If the time between packets exceeds this values within a test, the responder marks the previous test as complete. It treats any new packets from a peer with the same test ID, source MAC address, and MEP ID as a new test responding with the sequence number 1.
The no form of this command resets the timeout to the default value.
Default
100
Parameters
system
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure connectivity fault management general system parameters.
The no form of this command resets the timeout to the default value.
Values - 10 to 100
sender-id
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the ETH-CFM Sender ID used in CFM PDUs.
This command enables the context to include the configured system name or a locally configured name as the Chassis ID in Sender ID TLVs for ETH-CFM PDUs sent from MEPs and MIPs. MEPs include the Sender ID TLV for the CCM (subsecond CCM-enabled MEPs do not support the Sender ID TLV) in LBM/LBR and LTM/LTR PDUs. MIPs include this value in the LBR and LTR PDUs.
| Note: LBR functions reflect back all TLVs received in the LBM unchanged, including the Sender ID TLVs. |
The no form of this command reverts to the default.
Default
no sender-id
Parameters
3.11.2.1.7. Testhead Commands
test-oam
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure Operations, Administration, and Maintenance test parameters.
testhead-profile
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to create service testhead profiles which are used by the Y.1564/RFC 2544 testhead (also known as, traffic generator) OAM tool. A service testhead profile configures the parameters, such as contents of the frame payload that is generated by traffic generator, the size of the frame, test duration, test acceptance criteria, and other criteria to be used by the testhead tool.
The profile is used by the testhead OAM tool to generate the appropriate frame at the configured rate and measure the performance parameters (FD, FDV, and loss). At the end of the test run, the tool compares the measured values against the test acceptance criteria that is configured in the profile to determine whether the service is within bounds of the acceptance criteria or not.
The no form of this command removes user created profile from the system.
Parameters
acceptance-criteria
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the test acceptance criteria to be used by the testhead OAM tool to declare the PASS/FAIL result at the completion of the test.
Users can create up to 4 different acceptance criteria per profile to measure different SLA needs. User has an option to specify only one of the acceptance criteria to be specified with the testhead OAM tool during the invocation of the test.
The no form of this command removes the test acceptance criteria.
Default
no defaults
Parameters
cir-threshold
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the CIR rate with the measured CIR rate at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘PASS’, else it is considered to be ‘FAIL’.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. The threshold value is ignored and not considered for declaring the test result.
Default
no cir-threshold
Parameters
jitter-rising-threshold
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the jitter with the measured jitter at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. The threshold value is ignored and not considered for declaring the test result.
Default
no jitter-rising-threshold
Parameters
jitter-rising-threshold-in
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the jitter with the measured jitter for green/in-profile packets at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. The threshold value is ignored and not considered for declaring the test result.
Default
no jitter-rising-threshold-in
Parameters
jitter-rising-threshold-out
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the jitter with the measured jitter for yellow/out-of-profile packets at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. The threshold value is ignored and not considered for declaring the test result.
Default
no jitter-rising-threshold-out
Parameters
latency-rising-threshold
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the latency with the measured latency at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. The threshold value is ignored and not considered for declaring the test result.
Default
no latency-rising-threshold
Parameters
latency-rising-threshold-in
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the latency with the measured latency for green/in-profile packets at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. The threshold value is ignored and not considered for declaring the test result.
Default
no latency-rising-threshold-in
Parameters
latency-rising-threshold-out
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the latency with the measured latency of yellow or out-of-profile packets at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. The threshold value is ignored and not considered for declaring the test result.
Default
no latency-rising-threshold-out
Parameters
loss-rising-threshold
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the Frame Loss Ratio (FLR) with the measured FLR at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
Frame Loss Ratio is computed as a ratio of the difference of number of received frames, to number of injected or sent frames, divided by the number of sent frames.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. The threshold value is ignored and not considered for declaring the test result.
Default
no loss-rising-threshold
Parameters
loss-rising-threshold-in
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the frame loss ratio (FLR) with the measured FLR for green or in-profile packets at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
Frame Loss Ratio for green/in-profile packets is computed as a ratio of the difference of number of received green or in-profile frames to number of injected/sent green/in-profile frames divided by the number of sent green frames.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. The threshold value is ignored and not considered for declaring the test result.
Default
no loss-rising-threshold-in
Parameters
loss-rising-threshold-out
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the frame loss ratio (FLR) with the measured FLR for yellow/out-of-profile packets at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
Frame Loss ratio for yellow/out-of-profile packets is computed as a ratio of the difference of number of received yellow frames to number of injected/sent yellow frames divided by the number of sent yellow frames.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. The threshold value is ignored and not considered for declaring the test result.
Default
no loss-rising-threshold
Parameters
pir-threshold
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command compares the specified value for the PIR rate with the measured PIR rate at the end of the test to declare the test result. If the measured value is greater than the specified value, the test is declared as ‘PASS’, else it is considered to be ‘FAIL’.
The no form of this command disables the comparison of the parameter with the measured value at the end of the test. Basically, the threshold value is ignored and not considered for declaring the test result.
Default
no pir-threshold
Parameters
description
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command associates a description with the profile.
The no form the command removes description.
Parameters
dot1p
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure the Dot1p values to identify the in-profile or green packets and out-of-profile or yellow packets. The values configured using this command are used by the testhead tool on the local end (that is, the node on which the testhead tool is executed) to match the dot1p values received in the packet header and identify green and yellow packets and appropriately account the packets. These values are used only when the testhead tool is invoked with the parameter color-aware is set to ‘enable’.
The dot1p in-profile value (that is, packets with dot1p values in the L2 header equal to the dot1p-in-profile value configured is considered to be in-profile or green packet) is used to count the number of in-profile packets and measure the latency, jitter, and FLR for in-profile packets. Similarly, the dot1p out-profile is used to count the total out-of-profile or yellow packets and measure latency, jitter, and FLR for out-of-profile or yellow packets.
While the testhead tool is initiated, if color-aware is set to enable and no values are specified (that is, the no form of this command is used in the profile), the CLI gives an error. If values are specified, the configured values are used to match and identify in-profile and out-of-profile packets.
The no form of this command disables the use of dot1p to identify a green or yellow packet.
Note: Testhead OAM tool does not mark the packets below CIR as in-profile packets and packets above CIR and below PIR as out-of-profile packets using the Dot1p or DSCP or other packet header bits to indicate the color of the packet (for example: DEI bit), as the 7210 SAS access SAP ingress does not support color-aware metering. It is used to only identify green and yellow packets and maintain a count of received green and yellow packets when the tests are run in color-aware mode.
Default
The no form of this command is the default. There are no defaults for the dot1p values.
Parameters
frame-payload
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the packet header values to be used in frames generated by the testhead tool.
User can create up to 4 different types of frame payload representing different kinds of traffic, within a profile. User chooses one among these when starting the throughput test.
The parameter payload-type determines the packet header fields that are used to populate the frame generated by the testhead OAM tool. The packet header fields use the value from the parameters configured under the frame-payload. For example, when the payload-type is configured as “l2”, software uses the parameters src-mac, dst-mac, vlan-tag-1 (if configured), vlan-tag-2 (if configured), ethertype, and data-pattern. See the following for parameters used when other values are specified with payload-type.
The no form of this command removes the frame payload context.
Parameters
data-pattern
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the data pattern to populate the payload portion of the frame generated by the testhead tool.
This value can be specified if the payload-type is configured as l2 or ipv4 or tcp-ipv4 or udp-ipv4. For all these payload types, the frame with the appropriate headers is created and the payload portion of the frame, is filled up with the data-pattern-value specified with this command, repeating it as many times as required to fill up the remaining length of the payload.
The no form of this command uses the default data-pattern value of 0xa1b2c3d4e5f6.
Default
no data-pattern
Parameters
description
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to add some description to the frame type created to describe the purpose or identify the usage or any other such purpose.
The no form of this command removes the description.
Default
no description
Parameters
dscp
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the IP DSCP value to use in the IP header for the frame generated by the testhead tool.
This value can be specified if the payload-type is configured as ipv4 or tcp-ipv4 or udp-ipv4 and if configured is used by the testhead tool to populate the IP DSCP field of the IP header. If it is not specified it defaults to 0 when the payload type is ipv4, tcp-ipv4, and udp-ipv4. The testhead tool does not use the value specified with this command if the payload-type is “l2”.
NOTES:
- If both IP DSCP and IP ToS is configured, IP DSCP take precedence.
- If IP DSCP is not configured, but IP ToS is configured, the IP ToS value is used.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no dscp
Parameters
dst-ip
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the destination IPv4 address to use in the IP header for the frame generated by the testhead tool.
This value must be specified if the payload-type is configured as ipv4 or tcp-ipv4 or udp-ipv4. The testhead tool does not use the value specified with this command if the payload-type is “l2”.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no dst-ip, if the payload-type is set to ipv4, tcp-ipv4, udp-ipv4.
Parameters
dst-mac
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
Specifies the value of source MAC address to use in the frame generated by the testhead OAM tool. Only unicast MAC address must be specified.
This value must be specified for all possible values of payload-type.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no dst-mac
Parameters
dst-port
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the destination port to use in the TCP header for the frame generated by the testhead tool.
This value must be specified if the payload-type is configured as tcp-ipv4 or udp-ipv4. The testhead tool does not use the value specified with this command if the payload-type is l2 or ipv4.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no dst-port, if the payload-type is set to tcp-ipv4 or udp-ipv4
Parameters
ethertype
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the ethertype of the frame generated by the testhead tool.
This value must be specified if the payload-type is “l2”. The testhead tool uses the value specified with this command only if the payload-type is “l2”. For all other values of payload-type, the ethertype value used in the frame generated by the testhead tool uses specific value based on the payload-type. See the frame-payload CLI description for more information.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no ethertype, if the payload-type is set to l2, else the values used depends on the payload-type specified.
Parameters
ip-proto
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the IP protocol value to use in the IP header for the frame payload generated by the testhead tool.
This value must be specified if the payload-type is configured as ipv4. If the payload-type is specified as tcp-ipv4 or udp-ipv4, the appropriate standard defined values are used. The testhead tool does not use the value specified with this command if the payload-type is “l2”.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no ip-proto
Parameters
ip-tos
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the IP TOS (Type of Service) value to use in the IP header for the frame generated by the testhead tool.
This value can be specified if the payload-type is configured as ipv4 or tcp-ipv4 or udp-ipv4 and if configured is used by the testhead tool to populate the IP TOS field of the IP header. If it is not specified it defaults to 0 when the payload type is ipv4, tcp-ipv4, and udp-ipv4. The testhead tool does not use the value specified with this command if the payload-type is “l2”.
NOTES:
- If both IP DSCP and IP ToS is configured, IP DSCP take precedence.
- If IP DSCP is not configured, but IP ToS is configured, the IP ToS value is used.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no ip-tos
Parameters
ip-ttl
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the IP TTL (Time-to-Live) value to use in the IP header for the frame generated by the testhead tool.
This value can be specified if the payload-type is configured as ipv4 or tcp-ipv4 or udp-ipv4 and if configured is used by the testhead tool to populate the IP TTL field of the IP header. If it is not specified it defaults to 1 when the payload type is ipv4, tcp-ipv4, and udp-ipv4. The testhead tool does not use the value specified with this command if the payload-type is “l2”.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no ip-ttl
Parameters
src-ip
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the source IPv4 address to use in the IP header for the frame generated by the testhead tool.
This value must be specified if the payload-type is configured as ipv4 or tcp-ipv4 or udp-ipv4. The testhead tool does not use the value specified with this command if the payload-type is “l2”.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no src-ip, if the payload-type is set to ipv4, tcp-ipv4, udp-ipv4.
Parameters
src-mac
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command specifies the unicast source MAC address to use in the frame generated by the testhead OAM tool.
This value must be specified for all possible values of payload-type.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no src-mac
Parameters
src-port
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the source port to use in the TCP header for the frame generated by the testhead tool.
This value must be specified if the payload-type is configured as tcp-ipv4 or udp-ipv4. The testhead tool does not use the value specified with this command if the payload-type is l2 or ipv4.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
Default
no src-port, if the payload-type is set to tcp-ipv4 or udp-ipv4
Parameters
vlan-tag-1
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the values to be used for the outermost vlan-tag (often called the outer vlan) in the frame generated by the testhead OAM tool. The tool uses the values specified for VLAN ID, dot1p bits and TPID in populating the outermost VLAN tag in the frame generated.
Configuration of this parameter is optional and it is used for all possible values of payload-type, if configured.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
NOTES:
- The user must ensure that TPID/ethertype configured with this command matches the QinQ ethertype value in use on the port on which the test SAP is configured or must match 0x8100 if the test SAP is configured on a Dot1q encapsulation port, for the frame generated by the tool to be processed successfully on SAP ingress. If this value does not match the one configured under the port, frames generated by the testhead are dropped by the node on SAP ingress due to ethertype mismatch.
- The user must ensure that VLAN ID configured with this command matches the outermost VLAN tag of the QinQ SAP or the Dot1q SAP used for the test SAP for the frame generated by the tool to be processed successfully on SAP ingress. If this value does not match the one configured for the SAP, frames generated by the testhead are dropped by the node on SAP ingress due to VLAN ID mismatch.
- The Dot1p bits specified for the outermost tag can be used for SAP ingress QoS classification.
Default
no vlan-tag-1
Parameters
vlan-tag-2
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the values to be used for the second vlan-tag (often called the inner vlan or the C-vlan) in the frame generated by the testhead OAM tool. The tool uses the values specified for VLAN ID, dot1p bits and TPID in populating the second VLAN tag in the frame generated.
Configuration of this parameter is optional and it is used for all possible values of payload-type, if configured.
The no form of this command indicates that the field is not to be used in the frame generated by the tool.
NOTES:
- The user must ensure that TPID/ethertype configured with this command is 0x8100 for the frame generated by the tool to be processed successfully on SAP ingress. If this value does not match 0x8100, frames generated by the testhead are dropped by the node on SAP ingress due to ethertype mismatch (7210 supports only 0x8100 as the ethertype value for the inner vlan tag).
- The user must ensure that VLAN ID configured with this command matches the outermost VLAN tag of the QinQ SAP or the Dot1q SAP used for the test SAP for the frame generated by the tool to be processed successfully on SAP ingress. If this value does not match the one configured for the SAP, frames generated by the testhead are dropped by the node on SAP ingress due to VLAN ID mismatch.
- The Dot1p bits specified for the outermost tag can be used for SAP ingress QoS classification.
Default
no vlan-tag-2
Parameters
frame-size
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the frame size of the packets generated by the test head tool. Any frame size in the specific range can be specified.
The no form of this command reverts to the default value.
Default
1514
Parameters
rate
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command specifies the committed information rate (CIR) and peak information rate (PIR) for a test head profile.
If the optional PIR rate is not specified, the test head tool generates traffic up to the configured CIR rate. The CIR rate specifies the bandwidth or throughput that the user needs to validate. If specified, the PIR value must be greater than or equal to the CIR value. The test head tool then generates traffic up to the configured PIR value.
Specify the adaptation-rule parameter to instruct the system to derive the operational hardware rate for both the CIR and PIR. The software finds the best operational rate based on the user-specified constraint and the hardware-based rate supported on the platform. Refer to the 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide for more information about the hardware rate steps supported for test head traffic generator meters on different platforms.
The no form of this command sets the CIR value to the default; the PIR value is not set. Consequently, if the test head tool is run after the no rate command is run, the test generates traffic up to the configured CIR rate.
Default
rate cir 1000 kbps adaptation-rule closest
Parameters
test-completion-trap-enable
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command specifies that the test completion trap needs to be generated after the completion of the test or if the test is stopped. The trap contains the details of test configuration, the measured values, test completion status and PASS or FAIL result.
The no form of this command disables the generation of the event/log/trap after test completion.
Default
no test-completion-trap-enable
test-duration
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to specify the total test duration to be used for throughput measurement. The hours, minutes, and seconds specify the total duration of the throughput measurement. If all the parameters are specified together, the total test duration is set to the sum of the values specified for hours, minutes and seconds.
The no form of this command sets the value to the default value
Default
3 minutes
Parameters
3.11.2.1.7.1. OAM testhead commands
testhead
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command executes the throughput test by generating traffic up to the configured rate and measuring the delay, delay-variation, and frame-loss ratio. At the end of the test run, the testhead command compares the measured values against the test acceptance criteria that is specified to determine whether the service is within bounds of the acceptance criteria. It reports a pass if the configured rate thresholds are achieved and the measured performance parameter (that is, latency, jitter, and FLR) values are less than the thresholds configured in the acceptance criteria. It reports a failure if the configured rate thresholds are not achieved or if any of the measured values for the performance parameters exceeds the thresholds configured in the acceptance criteria.
The user must specify the testhead-profile parameter, which determines traffic generation rate and the content of the frames used for traffic generation. If both the CIR and PIR is specified, or if only the PIR is specified (by setting CIR to zero), the tool generates traffic up to the configured PIR. If only the CIR is specified, the tool generates traffic up to the configured CIR.
If the acceptance-criteria parameter is not specified and color-aware is set to disable by default, the software displays the test result as “PASS” if the frame loss is zero and desired rate is achieved. For comparison with the measured rate, the test uses the configured CIR, if only the CIR is configured, or it uses the PIR, if either only the PIR is specified or both the CIR and PIR are set to non-zero values. Measured values of latency, jitter, and delay variation are not compared.
If the acceptance-criteria parameter is not specified and color-aware is set to enable, the software displays the test result as “PASS” if the measured CIR and PIR match the configured CIR and PIR values and frame loss is zero, or if one of the following is true:
- the measured throughput rate (CIR + PIR) is equal to the configured CIR rate and if no PIR rate is configured
- the measured throughput rate (CIR + PIR) is equal to the configured PIR rate and if either no CIR rate is configured or if the CIR rate is configured
Otherwise, the test is declared failed. Measured values of latency, jitter, and delay variation are not compared.
If acceptance-criteria is specified and color-aware is set to enable, the test uses the configured packet header marking values (dot1p) to identify the color of the packet and classify it as green (in-profile) or yellow (out-of-profile). It measures the green packet (CIR) and the green/in-profile packet performance parameter values and the yellow packet rate (PIR) and the yellow/out-of-profile packet performance parameter values individually based on the packet markings. In addition to comparing the measured performance parameter values against the normal performance parameter threshold values (if enabled), if the user has enabled in/out thresholds for performance parameters in the acceptance criteria, the tool uses these values to compare against the measured values and declare a pass or fail result. The tool uses the cir-threshold and pir-threshold to compare against the measured CIR and PIR throughput rates and declare pass or fail if the thresholds specified by the cir-threshold and pir-threshold are achieved.
| Note: When color-aware mode is set to enable, the marking values used to identify both in-profile/green packet and out-of-profile/yellow packet must be configured. If either of the packet header marking values (for example, dot1p) is not configured by the user, the CLI displays an error. |
If acceptance-criteria is specified and color-aware is set to disable, the tests are color blind (not color-aware). The tool does not use the configured packet header marking values to identify the color of the packet and treats all packets the same. The tool uses the normal thresholds configured in the acceptance-criteria (that is, the threshold values other than the in/out profile thresholds) to compare the measured values and declare a pass or fail result. The tool does not attempt to compare the in/out thresholds against measured values. The tool uses the cir-threshold and pir-threshold as follows.
- If no PIR is configured and if the measured throughput rate is equal to the configured cir-threshold rate, the desired rate is said to have been achieved and the tests continue to compare the measured performance parameter thresholds with the configured performance parameter thresholds (if any).
- If PIR rate is configured and no CIR is configured and if the measured throughput rate is equal to the configured pir-threshold rate, the desired rate is said to have been achieved and the tests continue to compare the measured performance parameter thresholds with the configured performance parameter thresholds (if any).
- If PIR is configured and CIR is configured, and if the measured throughput rate is equal to the configured pir-threshold rate, the desired rate is said to have been achieved and the tests continue to compare the measured performance parameter thresholds with the configured performance parameter thresholds (if any).
The test-name and owner-name together uniquely identify a particular testhead invocation or session. The results of the testhead session are associated with the test-name and owner-name. Use these parameters to display the results of the testhead tool and to clear the results of a completed run. Multiple invocations of the testhead tool with the same test-name and owner-name is not allowed if the results of the old run using the same pair of test-name and owner-name are present. That is, the results are not overwritten when the testhead is invoked again with the same values for test-name and owner-name. The results must be cleared explicitly using the clear command before invoking the testhead tool with the same test-name and owner-name. Results for up to 100 unique sessions, each using a different test-name and owner-name, are saved in memory (that is, the results are not available for use after a reboot).
| Note: The testhead command is not saved in the configuration file after a reboot. |
See Prerequisites for Using the Testhead Tool for more information.
Parameters
See Configuration Guidelines for more information.
3.11.2.1.8. OAM Performance Monitoring, Bin Group, and Session Commands
oam-pm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command allows the operator to start and stop on-demand OAM-PM sessions.
Parameters
oam-pm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure storage parameters (including binning structures), availability/resiliency, and the individual proactive and on-demand tests used to gather performance and statistical data.
bin-group
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the parameters for a specific bin group. Bin-group 1 is a default bin group and cannot be modified. If no bin group is assigned to an OAM-PM session, bin-group 1 is assigned by default. The default values for bin-group 1 are fd-bin-count 3 bin 1 lower-bound 5000 bin 2 lower-bound 10000, fdr-bin-count 2 bin 1 lower-bound 5000, and ifdv-bin-count 2 bin 1 lower-bound 5000.
The no form of this command removes the specified bin group.
Parameters
bin-type
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the specified delay metric configuration context.
The no form of this command restores the default value.
Default
bin-type fd
Parameters
bin
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure the floor threshold for an individual bin.
Parameters
lower-bound
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the lower threshold for an individual bin. The operator does not have to specific a lower threshold for every bin that was previously defined by the bin-count for the specific type. By default, the lower threshold for each bin is the bin-number * 5000 microseconds. Lower thresholds in the previous adjacent bin must be lower than the threshold of the next higher bin threshold; otherwise, an error prevents the bin from entering the active state when the no shutdown command is issued for the bin group. Bin 0 is the result of the difference between 0 and the configured lower-bound of bin 1. The highest bin in the bin-count captures every result above the threshold. Any negative delay metric result is treated as zero and placed in bin 0.
The no form of this command restores the default threshold for the bin.
Parameters
delay-event
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the bin number, threshold, and direction that are monitored to determine if a delay metric threshold crossing event has occurred or has cleared. It requires a bin number, a rising threshold value and a direction. If the [clear threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. When a raise threshold is reached, the log event is generated. Each unique threshold can only be raised once for the threshold within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised another is not raised until a measurement interval completes, and the clear threshold has not been exceeded. A clear event is raised under that condition. In general, alarms are generated when there is a state change. The thresholds configured are applied to the count in specified bin and all higher number bins.
The no version of this command removes thresholding for this delay metric. The complete command must be configured in order to remove the specific threshold.
Default
[no] delay-events
Parameters
description
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command creates a text description stored in the configuration file for a configuration context. 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.
Parameters
shutdown
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command activates and deactivates the bin group or test.
When a bin group is active, only the description of the bin group can be modified. The bin group can only be shut down and modified when all references in the various PM sessions or individual tests have been shut down. If an active PM session is referencing the bin group, it generates an error indicating there are a number of active tests referencing the bin group, and it cannot be shut down.
When a test is shut down, no active measurements are made and any outstanding requests are ignored. If the test is started or stopped during a measurement interval, the suspect flag is set to “yes” to indicate that the data for the specific data set is in questionable.
The no form of this command activates the bin group or test.
session
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the individual session containers that house the test-specific configuration parameters. Since this session context provides only a container abstract to house the individual test functions, it cannot be shut down. Only individual tests sessions within the container may be shut down. No values, parameters, or configuration within this context may be changed if any individual test is active. Changes may only be made when all tests within the context are shut down, with the exception of the description.
The no form of this command removes the session.
Parameters
bin-group
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command links the individual test to the group of bins that map the probe responses.
The no form of this command installs the default bin-group 1 as the bin group for the session.
Default
bin-group 1
Parameters
ethernet
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure Ethernet-specific source and destination information, priority, and Ethernet test tools on the launch point.
dest-mac
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command defines the destination MAC address of the peer MEP and sets the destination MAC address in the Layer 2 header to match. This must be a unicast address.
The no form of this command removes the session parameter.
Parameters
dmm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the test ID to be assigned to the delay test, and creates the container to allow the individual test parameters to be configured.
The no form of this command removes the DMM test function from the PM session.
Parameters
data-tlv-size
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command is used to add an optional Data TLV to the PDU and increase the frame on the wire by the specified amount. This value is not the total size of the frame on the wire, but rather the size of the additional padding added to the PDU.
The no form of this command removes the optional TLV.
Default
data-tlv-size 0
Parameters
interval
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the message period, or probe spacing, for the transmission of DMM frames.
The no form of this command restores the default value.
Default
interval 1000
Parameters
test-duration
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command defines the length of time the test runs before stopping automatically. This command is only a valid option when a session has been configured with a session-type of on-demand. This is not an option when the session-type is configured as proactive. All tests start immediately following the execution of a no shutdown command.
The test duration value, remaining time, or completed state, is not synchronized with the backup CPM. This means that a failover re-launches any active test without regard to the test-duration timer on the previously active CPM. When the test starts on the newly active CPM, the test-duration is reset to the beginning.
The no form of this command removes a previously configured test-duration and allows the test to execute until manually stopped.
Parameters
priority
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the CoS priority across all tests configured under this session. This CoS value is exposed to the various QoS policies the frame passes through and does not necessarily map directly to the CoS value on the wire.
The no form of this command restores the default value.
Default
0
Parameters
slm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the test ID to be assigned to the synthetic loss test, and creates the container to allow the individual test parameters to be configured.
The no form of this command removes the SLM test function from the PM session.
Parameters
flr-threshold
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the frame loss threshold that is used to determine whether the delta-t is available or unavailable. An individual delta-t with a frame loss threshold equal to or higher than the configured threshold is marked unavailable. An individual delta-t with a frame loss threshold lower than the configured threshold is marked as available.
The no form of this command reverts to the default value.
Default
flr-threshold 50
Parameters
loss-events
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This context enables the context to define the loss events and thresholds that are to be tracked.
avg-flr-event
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command sets the frame loss ratio threshold configuration that is applied and checked at the end of the measurement interval for the specified direction. This is a percentage based on average frame loss ratio over the entire measurement interval. If [clear clear-threshold-percent] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
Default
no avg-flr-event forward
no avg-flr-event backward
Parameters
chli-event
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command sets the consecutive high loss interval (CHLI) threshold to be monitored and the associated thresholds using the counter of the specified direction. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If [clear clear-threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
Default
no chli-event forward
no chli-event backward
no chli-event aggregate
Parameters
hli-event
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command sets the high loss interval (HLI) threshold to be monitored and the associated thresholds using the counter of the specified direction. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If the [clear clear-threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
Default
no hli-event backward
no hli-event aggregate
Parameters
unavailability-event
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command sets the threshold to be applied to the overall count of the unavailability indicators, not transitions, per configured direction. This value is compared to the 32 bit unavailability counter specific to the direction which tracks the number of individual delta-ts that have been recorded as unavailable. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If the [clear clear-threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
Default
no unavailable-event forward
no unavailable-event backward
no unavailable-event aggregate
Parameters
undet-availability-event
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command sets the threshold to be applied to the overall count of the undetermined availability indicators, not transitions, per configured direction. This value is compared to the 32 bit unavailability counter specific to the direction which tracks the number of individual delta-ts that have been recorded as undetermined available. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If the [clear clear-threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
Default
no undetermined-available-event forward
no undetermined-available-event backward
no undetermined-available-event aggregate
Parameters
undet-unavailability-event
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command sets the threshold to be applied to the overall count of the undetermined unavailability indicators, not transitions, per configured direction. This value is compared to the 32 bit unavailability counter specific to the direction which tracks the number of individual delta-ts that have been recorded as undetermined unavailable. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If the [clear clear-threshold] is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and without regard to any previous window. Each unique event can only be raised once within measurement interval. If the optional clear threshold is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised, another is not raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.
The no version of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.
Default
no undet-unavailable-event forward
no undet-unavailable-event backward
no undet-unavailable-event aggregate
Parameters
timing
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures various availability parameters and the probe spacing (interval) for the SLM frames. The maximum size of the availability window cannot exceed 10 s (10000 ms).
The no form of this command installs the default values for all timing parameters and use those values to compute availability and set the SLM frequency. If an SLM test is active, it always has timing parameters, whether default or operator-configured.
Default
timing frames-per-delta-t 10 consec-delta-t 10 interval 100 chli-threshold 5
Parameters
source
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the source launch point for Y.1731 parameters that are used by the individual tests within the session. If an MEP matching the configuration does not exist, the session is allowed to become active; however, the frames sent and received as seen under the show>oam-pm>statistics>session session-name command are zero.
The no form of this command removes this session parameter.
Parameters
meas-interval
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command establishes the parameters of the individual measurement intervals utilized by the session. A maximum of three different measurement intervals may be configured under each session.
The no form of this command deletes the specified measurement interval.
Parameters
accounting-policy
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command assigns a record-type of complete-pm to the specified accounting policy (configured using the config>log>accounting-policy command). This runs the data collection process for completed measurement intervals in memory, file storage, and maintenance functions, moving data from memory to flash. A single accounting policy can be applied to a measurement interval.
The no form of this command removes the accounting policy.
Parameters
boundary-type
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command establishes the alignment of the start of the measurement interval with either the time of day clock or the start of the test.
Test-relative start times launch the measurement interval when the individual test enters the active no shutdown state.
Alignment with the time of day clock always defaults to the representative top of the hour. Clocks aligned at 15-minute measurement intervals divide the hour into four equal sections at 00, 15, 30, and 45. Clocks aligned at 1-hour measurement intervals start at 00. Clocks aligned at 1-day measurement intervals start at midnight. It is typical for the first measurement interval of a clock-aligned test to have the suspect flag set to yes because it is unlikely that the no shutdown command exactly corresponds to the clock-based measurement interval start time. Clock-aligned measurement intervals can include an additional offset. See the clock-offset command option under this context.
The no form of this command restores the default value.
Default
boundary-type clock-aligned
Parameters
clock-offset
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures an offset between measurement intervals with a boundary-type of clock-aligned and the default time of day clock. The configured offset must be smaller than the size of the measurement interval. As an example, an offset of 300 seconds shifts the start times of the measurement intervals by 5 minutes from their default alignments with respect to the time of day clock.
The no form of this command restores the default value.
Default
clock-offset 0
Parameters
event-mon
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables different threshold events on a specific measurement interval. Only one measurement interval with a configured OAM PM session can have events enabled using the no shutdown command.
delay-events
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This enables the monitoring of all configured delay events.
Configuring this command starts the monitoring of the configured delay events at the start of the next measurement interval. If the command is disabled using the no command, all monitoring of configured delay events, logging, and recording of new events for that session are suspended. Any existing events at the time of the shut down are maintained until the active measurement window in which the removal was performed has completed. The state of this monitoring function can be changed without needing to shut down all the tests in the session.
The no form of this command disables the monitoring of all configured delay events.
loss-events
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This enables the monitoring of all configured loss events.
Configuring this command starts the monitoring of the configured loss events at the start of the next measurement interval. If the command is disabled using the no command, all monitoring of configured loss events, logging, and recording of new events for that session are suspended. Any existing events at the time of the shut down are maintained until the active measurement window in which the removal was performed has completed. The state of this monitoring function can be changed without needing to shut down all the tests in the session.
The no form of this command disables the monitoring of all configured loss events.
intervals-stored
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the number of completed measurement intervals per session to be stored in volatile system memory. The entire block of memory is allocated for the measurement interval when the test is active (no shutdown) to ensure that memory is available. The numbers increase from 1 to the configured value + 1. The active PM data is stored in interval number 1, and older runs are stored, in order, to the upper most number, with the oldest run being deleted when the number of completed measurement intervals exceeds the configured value + 1. As new test measurement intervals complete for the session, the stored intervals are renumbered to maintain the described order. Care must be taken when setting this value. There must be a balance between completed runs stored in volatile memory and the use of the write-to-flash function of the accounting policy.
The 5-mins and 15-mins measurement intervals share the same (1 to 96) retention pool. In the unlikely event that both intervals are required, the total of both cannot exceed 96. The 1-hour and 1-day measurement intervals utilize their own ranges. If this command is omitted when configuring the measurement interval, the default values are used.
Parameters
3.11.2.1.9. Service Assurance Agent (SAA) Commands
saa
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document.
Description
This command enables the context to configure the Service Assurance Agent (SAA) tests.
test
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables 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 can only be modified while it is shut down.
The no form of this command removes the test from the configuration. To remove a test it can not be active at the time.
Parameters
accounting-policy
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command associates an accounting policy to the SAA test. The accounting policy must already be defined before it can be associated else an error message is generated.
When a test terminates, a notification trap is issued.
The no form of this command removes the accounting policy association.
Parameters
continuous
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command specifies whether the SAA test is continuous. When the test is configured as continuous, it cannot be started or stopped by using the saa command.
The no form of this command disables the continuous running of the test. Use the shutdown command to disable the test.
description
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command creates a text description stored in the configuration file for a configuration context.
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.
Parameters
jitter-event
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
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.
When 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 is re-enabled when it falls below the threshold after the initial crossing that generate the event.
The configuration of jitter event thresholds is optional.
Parameters
latency-event
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
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.
When 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 is re-enabled when it falls below the threshold after the initial crossing that generate the event.
The configuration of latency event thresholds is optional.
Parameters
loss-event
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command specifies that at the termination of an SAA testrun, 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.
Parameters
probe-history
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command defines history probe behavior. Defaults are associated with various configured parameters within the SAA test. Auto (keep) is used for test with probe counts of 100 or less, and intervals of 1 second and above. Auto (drop) only maintains summary information for tests marked as continuous with file functions, probe counts in excess of 100 and intervals of less than 1 second. SAA tests that are not continuous with a write to file defaults to Auto (keep). The operator is free to change the default behaviors for each type. Each test that maintains per probe history consumes more system memory. When per probe entries are required, the probe history is available at the completion of the test.
Default
auto
Parameters
trap-gen
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure trap generation for the SAA test.
probe-fail-enable
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the generation of an SNMP trap when 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 this command disables the generation of an SNMP trap.
probe-fail-threshold
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This 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. This command has no effect when probe-fail-enable is disabled.
The no form of this command returns the threshold value to the default.
Default
1
test-completion-enable
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the generation of a trap when an SAA test completes.
The no form of this command disables the trap generation.
test-fail-enable
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the generation of a 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 parameter.
The no form of this command disables the trap generation.
test-fail-threshold
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the threshold for trap generation on test failure.
This command has no effect when test-fail-enable is disabled. This command is not applicable to SAA trace route tests.
The no form of this command returns the threshold value to the default.
Default
1
type
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
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, and 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
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command determines the IP connectivity to a CPE within a specified VPLS service.
Parameters
If the interval is set to 1 second where the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
dns
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures a DNS name resolution test.
Parameters
ipv4-address - a.b.c.d | |
ipv6-address - x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | |
x - [0..FFFF]H | |
d - [0..255]D | |
ipv4-address - a.b.c.d | |
ipv6-address - x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | |
x - [0..FFFF]H | |
d - [0..255]D | |
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
eth-cfm-linktrace
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures a CFM linktrace test in SAA.
Parameters
The actual forwarding class encoding is controlled by the network egress mappings.
If the interval is set to “1” second, and the timeout value is set to “10” seconds, the maximum time between message requests is “10” seconds and the minimum is “1” second. This depends upon the receipt of a message reply corresponding to the outstanding message request. The timeout value must be less than the interval.
eth-cfm-loopback
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures an Ethernet CFM loopback test in SAA.
Parameters
The actual forwarding class encoding is controlled by the network egress mappings.
If the interval is set to “1” second, and the timeout value is set to “10” seconds, the maximum time between message requests is “10” seconds and the minimum is “1” second. This depends upon the receipt of a message reply corresponding to the outstanding message request. The timeout value must be less than the interval.
eth-cfm-two-way-delay
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures an Ethernet CFM two-way delay test in SAA.
Parameters
The actual forwarding class encoding is controlled by the network egress mappings.
If the interval is set to “1” second, and the timeout value is set to “10” seconds, the maximum time between message requests is “10” seconds and the minimum is “1” second. This depends upon the receipt of a message reply corresponding to the outstanding message request. The timeout value must be less than
the interval.
eth-cfm-two-way-slm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures an Ethernet CFM two-way SLM test in SAA.
Parameters
icmp-ping
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures an ICMP ping test.
Parameters
ipv4-address: | a.b.c.d | |
ipv6-address: | x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x: | [0 .. FFFF]H | |
d: | [0 .. 255]D | |
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
icmp-trace
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures an ICMP traceroute test.
Parameters
ipv4-address: | a.b.c.d | |
ipv6-address: | x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x: | [0 .. FFFF]H | |
d: | [0 .. 255]D | |
ipv4-address: | a.b.c.d | |
ipv6-address: | x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x: | [0 .. FFFF]H | |
d: | [0 .. 255]D | |
mac-ping
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command determines the existence of an egress SAP binding of a specific 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, 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 are 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), this SHG membership is used as if the packet originated from this SHG. In all other cases, SHG 0 (zero) is used. Note that if the mac-trace is originated from a non-zero SHG, such packets do not go out to the same SHG.
If EMG is enabled, mac-ping returns only the first SAP in each chain.
Parameters
If the interval is set to 1 second where the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
Output
sdp-ping
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command tests SDPs for uni-directional 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 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 is displayed. The following table 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 |
Special Cases
Upon request timeout, message response, request termination, or request error the following local and remote information is 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 shutdown, 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 is 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 router does not use an SDP-ID as the return path and N/A is displayed. | resp-sdp-id |
N/A | ||
Responding SDP-ID Path Used | Displays whether the responding 7210 SAS M 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 is displayed. If the far-end does not use the responding sdp-id as the return path, No is displayed. If resp-sdp is not specified, N/A is 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 is displayed. When resp-sdp-id is administratively up, Admin-Up is displayed. When resp-sdp-id exists on the far-end 7210 SAS M 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. | 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 originators sdp-id from the perspective of the remote 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 |
The request number is a sequential number starting with 1 and ending with the last request sent, incrementing by one (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.
Parameters
The DSCP or LSP-EXP mappings on the receive network interface controls the mapping back to the internal forwarding class used by the far-end 7210 SAS M that receives the message request. The egress mappings of the egress network interface on the far-end 7210 SAS M controls the forwarding class markings on the return reply message.
The DSCP or LSP-EXP mappings on the receive network interface controls the mapping of the message reply back at the originating 7210 SAS M. This is displayed in the response message output upon receipt of the message reply.
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
When the OAM message request is encapsulated in an IP/ 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.
Output
vccv-ping
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command configures a Virtual Circuit Connectivity Verification (VCCV) ping test. A vccv-ping test checks connectivity of a VLL inband. 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. 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 reuses an lsp-ping message format and can be used to test a VLL configured over an MPLS.
Note that VCCV ping can be initiated on TPE or SPE. If initiated on the SPE, the reply-mode parameter must be used with the ip-routed value The ping from the TPE can have either values or can be omitted, in which case the default value is used.
If a VCCV ping is initiated from TPE to neighboring a SPE (one segment only) it is sufficient to only use the sdpid:vcid parameter. However, if the ping is across two or more segments, at least the sdpId:vcId, src-ip-address ip-addr, dst-ip-address ip-addr, ttl vc-label-ttland pw-id pw-id parameters are used where:
- The src-ip-address is system IP address of the router preceding the destination router.
- The pwid is actually the VC ID of the last pseudowire segment.
- The vc-label-ttl must have a value equal or higher than the number of pseudowire segments.
Note that VCCV ping is a multi-segment pseudowire. For a single-hop pseudowire, only the peer VCCV CC bit of the control word is advertised when the control word is enabled on the pseudowire. 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 does not signal peer VCCV CC bits to the far end, consequently VCCV ping cannot be successfully initiated on that specific spoke SDP.
Parameters
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 T-PE node. | |
Values: | 1 to 4294967295 | |
prefix — The prefix on this 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 to 4294967295 | |
Syntax: | global-id – The global ID of the far end T-PE node of the FEC129 pseudowire. | |
Values: | 1 to 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 to 4294967295 | |
The LSP-EXP mappings on the receive network interface controls the mapping back to the internal forwarding class used by the far-end 7210 SAS M that receives the message request. The egress mappings of the egress network interface on the far-end router controls the forwarding class markings on the return reply message. The LSP-EXP mappings on the receive network interface controls the mapping of the message reply back at the originating SR.
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
vccv-trace
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document.
Description
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 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.
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 has the next-hop S-PE T-LDP session source address in the Remote PE Addressí field in the PW FEC TLV. Each S-PE which terminates and processes the message includes in the MPLS echo reply message the FEC 128 TLV corresponding the PW segment to its downstream node. The source T-PE or S-PE node can build the next echo reply message with TTL=2 to test the next-next hop for the MS-PW. It copies 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.
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 are configured accordingly. However, the T-PE/S-PE node still probes all hops up to min-ttl to correctly build the FEC of the desired subset of segments.
Parameters
Note that when a VCCV trace message is originated from an S-PE node, the user should used the IPv4 reply mode as the replying node does not know how to set the TTL to reach the sending S-PE node. If the user attempts this, a warning is issued to use the ipv4 reply mode
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 7210 T-PE node. | |
Values: | 1 to 4294967295 | |
prefix — The prefix on this 7210 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 to 4294967295 | |
Syntax: | global-id – The global ID of the far end T-PE of the FEC129 pseudowire. | |
Values: | 1 to 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 to 4294967295 | |
The LSP-EXP mappings on the receive network interface controls 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 controls the forwarding class markings on the return reply message. The LSP-EXP mappings on the receive network interface controls the mapping of the message reply back at the originating router.
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
3.11.2.1.10. OAM SAA Commands
saa
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command starts or stops an SAA test.
Parameters
A test cannot be started if it is in a shut-down state. An error message and log event are generated to indicate a failed attempt to start an SAA test run. A test cannot be started if it is in a continuous state.
3.11.2.1.11. LDP Treetrace Commands
ldp-treetrace
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command configures LDP treetrace to perform a single run of the LDP ECMP OAM tree trace. LDP treetrace tests are run to discover all ECMP paths of an LDP FEC
Parameters
When an MPLS echo request packet is generated in the CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc and profile parameter values. The LSP-EXP mappings on the outgoing interface control the marking of the packet EXP.
When the MPLS echo request packet is received on the responding node, the LSP-EXP mappings of the incoming interface determine the fc parameter values.
When an MPLS echo reply packet is generated in the CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the fc parameter. The parameter values is determined by the classification of the echo request packet being replied to at the incoming interface control the marking of the packet. The LSP-EXP mappings on the outgoing interface. The TOS byte is not modified. Table 29 summarizes the MPLS echo request packet behavior.
Table 29: Request Packet and Behavior for Sender and Responder Nodes
Node | Packet and Description of Behavior |
CPM (sender node) | echo request packet:
|
Outgoing interface (sender node) | echo request packet:
|
Incoming interface (responder node) | echo request packet:
|
CPM (responder node) | echo reply packet:
|
Outgoing interface (responder node) | echo reply packet:
|
Incoming interface (sender node) | echo reply packet:
|
Output
The following output is an example of LDP treetrace information.
test-oam
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command enables the context to configure Operations, Administration, and Maintenance test parameters.
ldp-treetrace
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command enables the context to configure the LDP ECMP OAM tree trace which consists of an LDP ECMP path discovery and an LDP ECMP path probing features.
The no option deletes the configuration for the LDP ECMP OAM tree discovery and path probing under this context.
Output
The following outputs are examples of LDP treetrace information over a numbered IP interface.
fc
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command configures the forwarding class of the MPLS echo request packet.
When an MPLS echo request packet is generated in the CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified fc parameter values. The LSP-EXP mappings on the outgoing interface control the marking of the packet EXP.
When the MPLS echo request packet is received on the responding node, the LSP-EXP mappings of the incoming interface determine the fc parameter values.
When an MPLS echo reply packet is generated in the CPM and forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the fc parameter. The classification of the echo request packet being replied to at the incoming interface determines the value of the fc parameter. The LSP-EXP mappings on the outgoing interface control the marking of the packet EXP. The TOS byte is not modified. Table 29 summarizes this behavior.
The no form of this command reverts the FC type to the default value.
Default
be
Parameters
path-discovery
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command enables the context to configure LDP ECMP OAM path discovery.
The ingress LER sends LSP Trace messages, including the LDP IPv4 Prefix FEC TLV and DSMAP TLV to the downstream LSR to build the ECMP tree for a specific FEC (egress FEC). It also inserts an IP address range drawn from the 127/8 space. The downstream LSR uses the address range to determine the ECMP path exercised by an IP address or a subrange of addresses within the specified range based on its internal hash routine. When the ingress LER receives the MPLS echo reply, it records this information and proceeds with the next echo request message targeted for a node downstream of the first LSR node along one of the ECMP paths. The subrange of IP addresses indicated in the initial reply allows the LSR downstream of the ingress LER to pass this message to its downstream node along the first ECMP path.
Use the interval command to configure the frequency of running tree discovery.
The ingress LER gets the list of FECs from the LDP FEC database. New FECs are added to the discovery list at the next tree discovery, and not when they are learned and added into the FEC database. Use the policy-statement command to configure FECs to include or exclude the use of a policy profile.
interval
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command configures the frequency of the LDP ECMP OAM path-discovery process. At every interval, the node sends LSP trace messages to discover the entire ECMP path tree for a specific destination FEC.
The no form of this command reverts the interval to its default value.
Default
60
Parameters
max-path
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12.
Description
This command configures the maximum number of ECMP paths the path discovery attempts to discover for each run every interval minutes.
The no form of this command reverts to the default value.
Default
16
Parameters
max-ttl
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command configures the maximum number of hops that are traced in the path of each FEC to be discovered.
The no form of this command reverts to the maximum time-to-live (TTL) default value.
Default
255
Parameters
policy-statement
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command configures FEC policy to determine which routes are imported from the LDP FEC database for the purpose of discovering its paths and probing them.
If no policy is specified, the ingress LER imports the full list of FECs from the LDP FEC database. New FECs are added to the discovery list at the next path discovery, and not when they are learned and added into the FEC database. A maximum of 500 FECs can be discovered using path discovery.
The user can configure the FECs to include or exclude.
Policies are configured in the config>router>policy-options context. A maximum of five policy names can be specified.
The no form of this command removes the policy from the configuration.
Default
no policy-statement
Parameters
retry-count
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
In the config>oam-test>ldp-treetrace>path-discovery context, this command configures the number of retransmissions of an LSP trace message to discover the path of an LDP FEC when no response is received within the timeout period.
In the config>oam-test>ldp-treetrace>path-probing context, this command configures the number of retransmissions of an LSP ping message to probe the path of an LDP FEC when no response is received within the timeout period.
The no form of this command reverts to the default value.
Default
3
Parameters
timeout
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command configures the maximum amount of time, in seconds, that the node will wait for a response after sending an LSP Trace message sent to discover the path of an LDP FEC before it declares failure. After consecutive failures equal to the value configured for the retry-count command, the node gives up.
The no form of this command reverts the timeout period to the default value.
Default
30
Parameters
path-probing
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command enables the context to configure LDP tree trace path probing.
The periodic path exercising runs in the background to test the LDP ECMP paths discovered by the path discovery capability. The probe used is an LSP Ping message with an IP address drawn from the subrange of 127/8 addresses indicated by the output of the tree discovery for this FEC.
Use the interval command to configure the frequency of running path probes. If an interface is down on the ingress LER that is performing the LDP tree trace, LSP ping probes tfrom the interface are not sent, but the ingress LER node does not raise alarms.
The LSP ping routine updates the content of the MPLS echo request message, specifically the IP address, as soon as the LDP ECMP path discovery phase has output the results of a new computation for the path in question.
interval
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command configures the frequency of the LSP Ping messages used to probe the paths of all LDP FECs discovered by the LDP tree trace path discovery.
The no option resets the interval to its default value.
Default
1
Parameters
timeout
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command configures the maximum amount of time, in minutes, that the node waits for a response after sending an LSP Ping message to probe the path of an LDP FEC before declaring failure. After consecutive failures equal to the value configured for the retry-count command, the node gives up.
The no form of this command resets the timeout period to its default value.
Default
1
Parameters
mpls-echo-request-downstream-map
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command specifies which format of the DSMAP TLV to use in all LSP trace packets and LDP tree trace packets originated on this node. The DSMAP TLV is the original format defined in RFC 4379 and is the default value. The Downstream Detailed Mapping (DDMAP) TLV is the enhanced format, as defined in RFC 6424.
This command applies to the LSP trace of an RSVP P2P LSP, MPLS-TP LSP, or LDP unicast FEC, and to LDP tree trace of a unicast LDP FEC. It does not apply to LSP trace of an RSVP P2MP LSP, which always uses the DDMAP TLV.
The global DSMAP and DDMAP setting impacts the behavior of both OAM LSP trace packets and SAA test packets of type lsp-trace and is used by the sender node when one of the following events occurs.
- 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.
- 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 preceding rules is that a change to the value of mpls-echo-request-downstream-map does not affect the value inserted in the DSMAP TLV of existing tests.
The following are the details of the processing of the new DDMAP TLV.
- When either the DSMAP TLV or the DDMAP TLV is received in an echo request message, the responder node includes the same type of TLV in the echo reply message with the correct downstream interface and label stack information.
- If an echo request message without a DSMAP or DDMAP TLV expires at a node that is not the egress for the target FEC stack, the responder node always includes the DSMAP TLV in the echo reply message. This can occur in the following cases.
- The user issues an 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 or DDMAP is set to DSMAP.
- The user issues an LSP ping from a sender node with a 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 of the DSMAP or DDMAP is set to DSMAP.
- The behavior in (a) is changed when the global configuration or the per-test setting of the DSMAP TLV is set to DDMAP. In this case, the sender node includes the DDMAP TLV with the Downstream IP address field set to the all-routers multicast address, as defined in Section 3.3 of RFC 4379. The responder node bypasses the interface and label stack validation and replies with a DDMAP TLV with the correct downstream information for the target FEC stack.
- A sender node never includes the DSMAP or DDMAP TLV in an LSP Ping message.
In addition to performing the same features as the DSMAP TLV, the new DDMAP TLV addresses the following scenarios:
- full validation of an LDP FEC stitched to a BGP IPv4 label route; in this case, the LSP trace message is inserted from the LDP LSP segment or from the stitching point
- full validation of a BGP IPv4 label route stitched to an LDP FEC
- full validation of an LDP FEC that is stitched to a BGP LSP and stitched back into an LDP FEC; in this case, the LSP trace message is inserted from the LDP segments or the or from the stitching points
- full validation of an LDP FEC tunneled over an RSVP LSP using LSP trace
To correctly check a target FEC that is stitched to another FEC (stitching FEC) of the same or a different type, or that is tunneled over another FEC (tunneling FEC), the responding nodes must provide details about the FEC manipulation back to the sender node. This is achieved using the FEC stack change sub-TLV in the DDMAP TLV, as defined in RFC 6424.
When the user configures the use of the DDMAP TLV on a trace for an LSP that does not undergo stitching or tunneling in the network, the procedures at the sender and responder nodes are the same as for the DSMAP TLV.
This feature introduces changes to the target FEC stack validation procedures at the sender and responder nodes in the case of LSP stitching and LSP hierarchy. These changes pertain to the processing of the new FEC stack change sub-TLV in the new DDMAP TLV and the new return code of value 15 Label switched with FEC change.
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.
Default
dsmap
Output
The following output is an example of DSMAP TLV information.
3.11.2.1.12. TWAMP commands
twamp
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure TWAMP functionality.
Default
no twamp
server
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure the node for TWAMP server functionality.
prefix
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures an IP address prefix containing one or more TWAMP clients. In order for a TWAMP client to connect to the TWAMP server (and subsequently conduct tests) it must establish the control connection using an IP address that is part of a configured prefix
Default
no prefix
Parameters
description
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command creates a text description for the current configuration context that is stored in the configuration file. 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 description.
Parameters
max-conn-prefix
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the maximum number of TWAMP control connections by clients with an IP address in a specific prefix. A new control connection is rejected if accepting it would cause either the prefix limit defined by this command or the server limit (max-conn-server) to be exceeded.
The no form of this command sets the default value.
Default
no max-conn-prefix
Parameters
max-sess-prefix
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the maximum number of concurrent TWAMP-Test sessions by clients with an IP address in a specific prefix. A new test session (described by a Request-TW-Session message) is rejected if accepting it would cause either the limit defined by this command or the server limit (max-sess-server) to be exceeded.
The no form of this command instructs the system to go with the default value.
Default
no max-sess-prefix
Parameters
inactivity-timeout
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the inactivity timeout for all TWAMP-control connections. If no TWAMP control message is exchanged over the TCP connection for this duration of time the connection is closed and all tests in progress are terminated.
The no form of this command instructs the system to go with the default value.
Default
no inactivity-timeout
Parameters
max-conn-server
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the maximum number of TWAMP control connections from all TWAMP clients.
A new control connection is rejected if accepting it would cause either this limit or a prefix limit (max-conn-prefix) to be exceeded.
The no form of this command sets the default value.
Default
no max-conn-server
Parameters
max-sess-server
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the maximum number of concurrent TWAMP-Test sessions across all allowed clients.
A new test session (described by a Request-TW-Session message) is rejected if accepting it would cause either the limit defined by this command or a prefix limit (max-sess-prefix) to be exceeded.
The no form of this command instructs the system to go with the default value.
Default
no max-sessions
Parameters
shutdown
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command administratively disables the TWAMP server.
The no form of this command administratively enables the TWAMP server.
Default
shutdown
3.11.2.1.13. TWAMP Light Commands
twamp-light
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure TWAMP Light functionality.
| Note: The config>service>vprn context is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode. |
reflector
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures TWAMP Light session reflector-specific parameters. When creating a reflector, the udp-port-number value must be configured and the create keyword must be included.
The no form of this command removes the reflector.
| Note: The config>service>vprn>twamp-light context is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode. |
Parameters
description
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
| Note: The config>service>vprn>twamp-light>reflector and config>service>vprn>twamp-light>reflector>prefix contexts are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode. |
This command creates a text description for the current configuration context that is stored in the configuration file. 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 description.
Parameters
prefix
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the IP prefixes that the reflector accepts TWAMP Light packets from and respond to. Each prefix requires its own configuration entry.
The no form of this command removes the specifies prefix.
| Note: The config>service>vprn>twamp-light>reflector context is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode. |
Parameters
shutdown
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command disables the TWAMP Light reflector functionality within the current context.
The no form of this command enables the TWAMP Light reflector functionality within the current context.
| Note: The config>service>vprn>twamp-light>reflector context is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode. |
Default
shutdown
inactivity-timeout
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the length of time to maintain stale states on the session reflector. A stale state occurs when test data information has not been refreshed or updated by newly arriving probes for that specific test in a predetermined amount of time. Any single reflector can maintain an up state for a maximum of 12000 tests. If the maximum value is exceeded, the session reflector does not have memory to allocate to new tests.
The no form of this command disables the inactivity timer.
Default
inactivity-timer 100
Parameters
session
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the individual session containers that house the test-specific configuration parameters. Since this session context provides only a container abstract to house the individual test functions, it cannot be shut down. Only individual tests sessions within the container may be shut down. No values, parameters, or configuration within this context may be changed if any individual test is active. Changes may only be made when all tests within the context are shut down, with the exception of the description.
The no form of this command removes the session.
Parameters
ip
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to configure the IP-specific source and destination information, the priority, and the IP test tools on the launch point.
destination
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the destination IP address to which the TWAMP Light packets are addressed. The destination address must be included in the prefix list on the session reflector within the context to allow the reflector to process the inbound TWAMP Light packets.
The no form of this command removes the destination parameters.
Default
no destination
Parameters
dest-udp-port
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the destination UDP port to which the TWAMP Light packets are sent from the session controller. This value must match the udp-port udp-port number configured on the TWAMP Light reflector that responds to this specific TWAMP Light test.
The no form of this command removes the destination UDP port configuration.
Parameters
fc
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the forwarding class designation for TWAMP Light packets that are sent through the node and exposed to the various QoS functions on the network element.
The no form of this command restores the default value.
Default
fc be
Parameters
forwarding
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures influence for the forwarding decision of the TWAMP Light packet. When this command is used, only one of the forwarding options can be enabled at any time.
The no form of this command removes the configured influence and enables the default forwarding logic.
Default
no forwarding
Parameters
profile
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures whether TWAMP Light PDUs are treated as in-profile or out-of-profile.
The no form of this command restores the default value. The default has been selected because the forwarding class defaults to best effort.
Default
profile out
Parameters
router
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the source context from which TWAMP Light packets are launched. The routing instance and service name must be a VPRN instance.
NOTE: VPRN instances may only be specified on 7210 SAS platforms that support VPRN services. Refer to the platform-specific 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide for information about platform support for VPRN services.
The no form of this command restores the default value.
Default
router base
Parameters
source
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the source IP address that the session controller (launch point) uses for the test. The source address must be a local resident IP address in the context; otherwise, the response packets are not processed by the TWAMP Light application. Only source addresses configured as part of TWAMP tests are able to process the reflected TWAMP packets from the session reflector.
The no form of this command removes the source address parameters.
Parameters
source-udp-port
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command restricts the source UDP range. When this command is omitted, the source UDP port is dynamically allocated by the system. This command should only be used if a TWAMP Client is used to establish a TCP connection and communicate the test parameters to a TWAMP Server over TWAMP TCP Control, and the test is launched from OAM-PM (Session-Sender). This command should not be used when the reflection point is a TWAMP Light reflector that does not require TCP TWAMP Control.
The no form of this command removes the source UDP port configuration and enables default allocation.
Default
no source-udp-port
Parameters
ttl
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the value of the TTL (time to live) field in the IP header.
The no form of this command restores the default value.
Default
ttl 255
Parameters
twamp-light
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command assigns an identifier to the TWAMP Light test and creates the individual test.
The no form of this command removes the TWAMP Light test function from the OAM-PM session.
Default
no twamp-light
Parameters
interval
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the message period, or probe spacing, for the transmission of TWAMP Light frames.
The no form of this command restores the default value.
Parameters
loss
Syntax
Context
Description
This command enables the context to configure loss parameters for the TWAMP-Light test.
pad-size
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the amount by which the TWAMP Light packets are padded. TWAMP session-controller packets are 27 bytes smaller than TWAMP session-reflector packets. If symmetrical packet sizes in the forward and backward direction are required, a minimum padding of 27 bytes must be configured.
The no form of this command removes all padding.
Default
pad-size 0
Parameters
record-stats
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command configures the statistics that are recorded and reported for the TWAMP-Light PDU.
The TWAMP-Light PDU can report on both delay and loss using a single packet. The user can choose which statistics to report. Only delay recording is enabled by default. All other metrics are ignored.
To change the record statistics configuration, the user must shut down the TWAMP-Light session. This is required because base statistics are shared among various datasets as a result of the single packet approach of the TWAMP-Light PDU. Issuing a no shutdown command clears all previous non-volatile memory for the session and allocates new memory blocks.
All command parameters are mutually exclusive.
The no form of this command reverts to the default value.
Default
record-stats delay
Parameters
shutdown
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command starts or stops the test.
Default
shutdown
test-duration
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This optional command configures the length of time that the test runs before stopping automatically. This command is only a valid option when a session-type is configured as on-demand. This command is not an option when the session-type is configured as proactive.
The no form of this command removes a previously configured test-duration value and allows the TWAMP Light test to execute until it is stopped manually.
Default
test-duration 0
Parameters
3.11.2.1.14. Show Commands
twamp-light
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays TWAMP Light information.
Output
The following output is an example of TWAMP light information, and Table 30 describes the output fields.
Table 30: Output Fields: TWAMP Light
Label | Description |
TWAMP Light Reflector | |
Admin State | Up—Specifies that the server or prefix is administratively enabled (no shutdown) in configuration. Down—Specifies that the server or prefix is administratively disabled (shutdown) in configuration. |
Decription | Text string to describe the context of the protocol. |
Up Time | The time since the server process was started, measured in days (d), hours, minutes, and seconds |
UDP Port | The UDP port number used |
Test Frames Received | The total number of frames received from session senders |
Test Frames Sent | The total number of frames sent to session senders |
Prefixes | The time since the server process was started, measured in days (d), hours, minutes, and seconds |
saa
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays information about the SAA test.
If no specific test is specified, a summary of all configured tests is displayed.
If a specific test is specified, detailed test results for that test are displayed for the last three occurrences that this test has been executed, or since the last time the counters have been reset via a system reboot or clear command.
Parameters
Output
The following output is an example of SAA information, and Table 31 describes the output fields.
Table 31: Ouput Fields: SAA
Label | Description |
Test Name | Specifies the name of the test. |
Owner Name | Specifies the owner of the test. |
Description | Specifies the description for the test type. |
Accounting policy | Specifies the associated accounting policy ID. |
Administrative status | Specifies whether the administrative status is enabled or disabled. |
Test type | Specifies the type of test configured. |
Trap generation | Specifies the trap generation for the SAA test. |
Test runs since last clear | Specifies the total number of tests performed since the last time the tests were cleared. |
Number of failed tests run | Specifies the total number of tests that failed. |
Last test run | Specifies the last time a test was run. |
Threshold type | Indicates the type of threshold event being tested, jitter-event, latency-event, or loss-event, and the direction of the test responses received for a test run: in — inbound out — outbound rt — roundtrip |
Direction | Indicates the direction of the event threshold, rising or falling. |
Threshold | Displays the configured threshold value. |
Value | Displays the measured crossing value that triggered the threshold crossing event. |
Last event | Indicates the time that the threshold crossing event occurred. |
Run # | Indicates what test run produced the specified values. |
test-oam
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to display Operations, Administration, and Maintenance test parameters
Output
The following output is an example of OAM test parameters information.
eth-cfm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to display CFM information.
association
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays eth-cfm association information.
Parameters
Output
The following output is an example of ETH-CFM information, and Table 32 describes the output fields.
Table 32: Output Fields: ETH-CFM Association
Label | Description |
Md-index | Displays the MD index |
Ma-index | Displays the MA index |
Name | Displays the name of the MA |
CCM-interval | Displays the CCM interval (in seconds) |
Bridge-id | Displays the bridge ID for the MA. The bridge ID is the same value as the service ID of the service to which the MEP belongs. |
cfm-stack-table
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays stack-table information. This stack-table is used to display the various management points MEPs and MIPs that are configured on the system. These can be Service based or facility based. If no parameters are included, the entire stack-table is displayed.
Parameters
Output
The following output is an example of CFM stack-table information, and Table 33 describes the output fields.
Table 33: Output Fields: CFM stack Table
Label | Description |
Sap | Displays the SAP identifier |
Level | Displays the MD level of the domain |
Dir (direction) | Displays the direction of OAMPDU transmission |
Md-index | Displays the MD index of the domain |
Ma-index | Displays the MA index of the domain |
Mep-id | Displays the MEP identifier |
Mac-address | Displays the MAC address of the MEP |
domain
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays domain information.
Parameters
Output
The following output is an example of ETH-CFM domain information, and Table 34 describes the output fields.
Table 34: Output Fields: ETH-CFM Domain
Label | Description |
Domain | |
Md-index | Displays the MD index of the domain |
Level | Displays the MD level of the domain |
Name | Displays the name of the MD |
Name Format | Displays the format for the MD name |
mep
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays information for a specified Maintenance Endpoint (MEP).
Parameters
Output
The following outputs are examples of MEP information, and the associated tables describe the output fields:
Table 35: Output fields: MEP
Label | Description |
Mep Information | |
Md-index | Displays the MD index of the domain |
Direction | Displays the direction of OAMPDU transmission |
Ma-index | Displays the MA index of the association |
Admin | Displays the administrative status of the MEP |
MepId | Displays the MEP identifier |
CCM-Enable | Displays the status of the CCM (enabled or disabled) |
IfIndex | Displays the index of the interface |
PrimaryVid | Displays the identifier of the primary VLAN |
FngState | Indicates the different states of the Fault Notification Generator |
LowestDefectPri | Displays the lowest priority defect (a configured value) that is allowed to generate a fault alarm |
HighestDefect | Identifies the highest defect that is present (for example, if defRDICCM and defXconCCM are present, the highest defect is defXconCCM) |
Defect Flags | Displays the number of defect flags |
Mac Address | Displays the MAC address of the MEP |
CcmLtmPriority | Displays the priority value transmitted in the linktrace messages (LTM)s and CCMs for this MEP. The MEP must be configured on a VLAN. |
CcmTx | Displays the number of Continuity Check Messages (CCM) sent. The count is taken from the last polling interval (every 10 s). |
CcmSequenceErr | Displays the number of CCM errors |
Eth-1DM Threshold | Displays the one-way-delay threshold value |
Eth-Ais | Displays the state of the ETH-AIS test (enabled or disabled) |
Eth-Test | Displays the state of the ETH-Test (enabled or disabled) |
CcmLastFailure Frame | Displays the frame that caused the last CCM failure |
XconCcmFailure Frame | Displays the frame that caused the XconCCMFailure |
Mep Loopback Information | |
LbRxReply | Displays the number of received loopback (LB) replies |
LbRxBadOrder | Displays the number of received loopback messages that are in a bad order |
LbRxBadMsdu | Displays the number of loopback replies that have been received with the wrong destination MAC address (MSDU = MAC Service Data Unit) |
LbTxReply | Displays the number of loopback replies transmitted out this MEP |
LbTxReply (Total) | Displays the total number of LBRs (loopback replies) transmitted from this MEP |
LbTxReplyNoTLV | Displays the number of LBRs (loopback replies) transmitted from this MEP with no TLV. Because only LBMs with no TLVs are used for throughput testing, the LbTxReply (Total), LbTxReplyNoTLV, and LbTxReplyWithTLV counters can help debug problems if throughput testing is not working |
LbTxReplyWithTLV | Displays the number of LBRs (loopback replies) transmitted from this MEP with TLV |
LbSequence | Displays the sequence number in the loopback message |
LbNextSequence | Displays the next loopback sequence |
LbStatus | Displays the loopback status as True or False: True — loopback is in progress False — no loopback is in progress |
LbResultOk | Displays the result of the loopback test |
DestIsMepId | Identifies whether the destination interface has a MEP-ID (true or false) |
DestMepId | Displays the MEP-ID of the destination interface |
DestMac | Displays the MAC address of the destination interface |
SendCount | Indicates the number of loopback messages sent |
VlanDropEnable | Identifies whether the VLAN drop is enabled (true or false) |
VlanPriority | Displays the VLAN priority |
Data TLV | Displays the data TLV information |
Mep Linktrace Message Information | |
LtRxUnexplained | Displays the number of unexplained linktrace messages (LTM) that have been received |
LtNextSequence | Displays the sequence number of the next linktrace message |
LtStatus | Displays the status of the linktrace |
LtResult | Displays the result of the linktrace |
TargIsMepId | Identifies whether the target interface has a MEP-ID (true or false) |
TargMepId | Displays the MEP-ID of the target interface |
TargMac | Displays the MAC address of the target interface |
TTL | Displays the TTL value |
EgressId | Displays the egress ID of the linktrace message |
SequenceNum | Displays the sequence number of the linktrace message |
LtFlags | Displays the linktrace flags |
Mep Linktrace Replies | |
SequenceNum | Displays the sequence number returned by a previous transmit linktrace message, indicating which linktrace message response is returned |
ReceiveOrder | Displays the order in which the linktrace initiator received the linktrace replies |
Ttl | Displays the TTL field value for a returned linktrace reply |
Forwarded | Indicates whether the linktrace message was forwarded by the responding MEP |
LastEgressId | Displays the last egress identifier returned in the linktrace reply egress identifier TLV of the linktrace reply The last egress identifier identifies the MEP linktrace initiator that initiated, or the linktrace responder that forwarded, the linktrace message for which this linktrace reply is the response. This is the same value as the egress identifier TLV of that linktrace message. |
TerminalMep | Indicates whether the forwarded linktrace message reached a MEP enclosing its MA |
NextEgressId | Displays the next egress identifier returned in the linktrace reply egress identifier TLV of the linktrace reply. The next egress identifier identifies the linktrace responder that transmitted this linktrace reply and can forward the linktrace message to the next hop. This is the same value as the egress identifier TLV of the forwarded linktrace message, if any. |
Relay | Displays the value returned in the Relay Action field |
ChassisIdSubType | Displays the format of the chassis ID returned in the Sender ID TLV of the linktrace reply, if any. This value is meaningless if the chassis ID has a length of 0 |
ChassisId | Displays the chassis ID returned in the Sender ID TLV of the linktrace reply, if any. The format is determined by the value of the ChassisIdSubType. |
ManAddressDomain | Displays the TDomain that identifies the type and format of the related ManAddress, used to access the SNMP agent of the system transmitting the linktrace reply Received in the linktrace reply Sender ID TLV from that system |
ManAddress | Displays the TAddress that can be used to access the SNMP agent of the system transmitting the CCM Received in the CCM Sender ID TLV from that system |
IngressMac | Displays the MAC address returned in the ingress MAC address field |
Ingress Action | Displays the value returned in the Ingress Action field of the linktrace message |
IngressPortIdSubType | Displays the format of the ingress port ID |
IngressPortId | Displays the ingress port ID; the format is determined by the value of the IngressPortIdSubType |
EgressMac | Displays the MAC address returned in the egress MAC address field |
Egress Action | Displays the value returned in the Egress Action field of the linktrace message |
EgressPortIdSubType | Displays the format of the egress port ID |
EgressPortId | Displays the egress port ID; the format is determined by the value of the EgressPortIDSubType |
Org Specific TLV | Displays all organization-specific TLVs returned in the linktrace reply, if any Includes all octets including and following the TLV length field of each TLV, concatenated |
Eth-Test | |
Peer Mac Addr | Displays the MAC address of the peer (remote) entity |
FrameCount | Displays the number of test frames sent between the MEP and the peer entity |
ByteCount | Displays the number of bytes sent between the MEP and the peer entity |
Current ErrBits | Displays the number of bit errors in the current test |
Current CrcErrs | Displays the number of CRC errors in the current test |
Accumulate ErrBits | Displays the accumulated number of bit errors in the current test |
Accumulate CrcErrs | Displays the accumulated number of CRC errors in the current test |
Delay Measurement Test | |
Peer Mac Addr | Displays the MAC address of the peer (remote) entity |
Delay (us) | Displays the measured delay (in microseconds) for the DM test |
Delay Variation (us) | Displays the measured delay variation (in microseconds) for the DV test |
Table 36: Output Fields: MEP ETH-BN
Label | Description |
Md-index | Displays the MD index of the domain |
Direction | Displays the direction of OAM PDU transmission |
Ma-index | Displays the MA index of the association |
Admin | Displays the administrative status of the MEP |
MepId | Displays the MEP ID |
CCM-Enable | Displays the status of the CCM (enabled or disabled) |
Port | Displays the port number |
VLAN | Displays the configured VLAN on the MEP |
Description | Displays the description |
FngAlarmTime | Displays the fault alarm time |
FngResetTime | Displays the fault alarm reset time |
FngState | Displays the different states of the Fault Notification Generator |
LowestDefectPri | Displays the lowest priority defect (a configured value) that is allowed to generate a fault alarm |
HighestDefect | Displays the highest defect that is present (for example, if defRDICCM and defXconCCM are present, the highest defect is defXconCCM) |
Defect Flags | Displays the number of defect flags |
Mac Address | Displays the MAC address of the MEP |
CcmTx | Displays the total number of CCM transmitted |
CcmPaddingSize | Displays the number of octets used to pad a CCM packet |
CcmSequenceErr | Displays the total number of out-of-sequence CCMs received |
Fault Propagation | Displays the fault propagation configuration for the MEP |
MA-CcmInterval | Displays the CCM transmission interval for all MEPs in the association |
MA-CcmHoldTime | Displays the CCM hold time for all MEPs in the association |
MD-Level | Displays the MD level |
Eth-Ais | Displays the state of the ETH-AIS test (enabled or disabled) |
Eth-BNM Receive | Displays whether ETH-BN receive is enabled or disabled |
Eth-BNM Rx Pacing | Displays the ETH-BN receive update pacing interval time |
MC-LAG State | Displays the MC-LAG state |
CcmLastFailure Frame | Displays the frame that caused the last CCM failure |
XconCcmFailure Frame | Displays the frame that caused the XconCCMFailure |
mip
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays SAPs/bindings provisioned for allowing the default MIP creation.
Output
The following output is an example of MIP information.
statistics
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays the ETH-CFM statistics counters.
Output
The following output is an example of ETH-CFM statistics information.
system-config
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command shows various system level configuration parameters. These global eth-cfm commands are those which are configured directly under the config>eth-cfm context.
Output
The following output is an example of ETH-CFM system configuration information.
ldp-treetrace
Syntax
Context
Supported Platforms
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, 7210 SAS-R6, and 7210 SAS-R12
Description
This command displays OAM LDP treetrace information.
Parameters
Output
The following output is an example of OAM LDP treetrace information.
twamp
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to request TWAMP information.
twamp-light
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to request TWAMP Light information.
reflectors
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays TWAMP Light reflector information.
Output
The following output is an example of OAM TWAMP light information, and Table 37 describes the output fields.
Table 37: Output Fields: TWAMP Light Reflectors
Label | Description |
TWAMP Light Reflector | |
Router/VPRN | The TWAMP Light clients |
Admin | Displays one of the following: Up—the server or prefix is administratively enabled (no shutdown) in configuration Down—the server or prefix is administratively disabled (shutdown) in configuration |
UDP Port | The UDP port number used |
Prefixes | The time since the server process was started, measured in days (d), hours, minutes, and seconds |
Frames Rx | The total number of frames received from session senders |
Frames Tx | The total number of frames sent to session senders |
server
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays information about the TWAMP server. It displays summary information for the ip-prefix in use.
Parameters
ip-prefix/mask | ipv4-prefix | a.b.c.d (host bits must be 0) |
ipv4-prefix-le | [0 to 32] | |
ipv6-prefix | x:x:x:x:x:x:x:x: (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x - [0 to FFFF]H | ||
d - [0 to 255]D | ||
ipv6-prefix-le | [0 to 128] |
Output
The following outputs are examples of TWAMP server information, and Table 38 describes the output fields.
The following output is an example of all TWAMP server information.
The following output is an example of TWAMP server prefix information.
Table 38: Output Fields: TWAMP Server
Label | Description |
Admin State | Displays one of the following: Up — The server or prefix is administratively enabled (no shutdown) in configuration. Down — The server or prefix is administratively disabled (shutdown) in configuration. |
Operational State | Displays one of the following: Up — The server or prefix is operationally enabled. Down — The server or prefix is operationally disabled. |
Up Time | Displays the time since the server process was started, measured in days (d), hours, minutes, and seconds. |
Current Connections | Displays the total number of currently connected clients. |
Max Connections | Displays the maximum number of connected clients. |
Connections Rejected | Displays the number of connection rejections. |
Inactivity Timeout | Displays the configured inactivity timeout for all TWAMP-control connections (inactivity-timeout). |
Current Sessions | Displays the number of current sessions. |
Max Sessions | Displays the maximum number of sessions. |
Sessions Rejected | Displays the number of rejected sessions for the TWAMP client. |
Sessions Aborted | Displays the number of manually aborted sessions for the TWAMP client. |
Sessions Completed | Displays the number of completed sessions for the TWAMP client. |
Test Packets Rx | Displays the number of test packets received. |
Test Packets Tx | Displays the number of test packets transmitted. |
Description | Displays the configured description of the TWAMP server. |
Connection information for TWAMP server prefix | Displays the IP address prefix of a TWAMP server. |
Client | Displays the IP address of the TWAMP client. |
State | Displays the operational state of the TWAMP client. |
Curr Sessions | Displays the number of current sessions for the TWAMP client. |
Idle Time (s) | Displays the total idle time, in seconds, of the TWAMP client. |
No. of Conns for Prefix | Displays the total number of connections for the TWAMP server with the displayed IP address prefix. |
No. of TWAMP Server Prefixes | Displays the total number of displayed TWAMP server IP address prefixes. |
testhead-profile
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command specifies the testhead profile ID to use with this run or session of testhead invocation. The testhead profile must be configure before using the commands under config> test-oam> testhead-profile context.
Output
The following output is an example of testhead profile information, and Table 39 describes the output fields.
Table 39: Ouput Fields: Test OAM Testhead Profile
Label | Description |
Description | Displays the description configured by the user for the test. |
Profile Id | Displays the profile identifier. |
CIR Configured | Displays the value of the CIR configured. |
PIR Configured | Displays the value of the PIR configured. |
Frame Size | Displays the size of the frame. |
CIR Operational | Displays the value of the CIR operational rate configured. |
PIR Operational | Displays the value of the PIR operational rate configured. |
CIR Rule | Displays the adaptation rule configured by the user. |
InPrf Dot1p | Displays the dot1p value used to identify green or in-profile packets. |
Ref. Count | Displays the total number of testhead (completed or running) sessions pointing to a profile or acceptance criteria or a frame payload. |
OutPrf Dot1p | Displays the dot1p value used to identify green or out-of-profile packets. |
Duration Hrs, mins, and secs | Displays the test duration in hours, minutes, and seconds. |
Loss TH | Displays the user configured loss threshold value for comparison with measured value. |
Jitter TH | Displays the user configured jitter threshold value for comparison with measured value. |
InProf Loss TH | Displays the user configured in-profile loss threshold value for comparison with measured value. |
OutProf Loss TH | Displays the user configured out-of-profile loss threshold value for comparison with measured value. |
Latency TH | Displays the user configured latency threshold value for comparison with measured value. |
InProf Latency TH | Displays the user configured in-profile latency threshold value for comparison with measured value. |
OutProf Latency TH | Displays the user configured out-of-profile latency threshold value for comparison with measured value. |
InProf Jitter TH | Displays the user configured in-profile jitter threshold value for comparison with measured value. |
OutProf Jitter TH | Displays the user configured out-of-profile jitter threshold value for comparison with measured value. |
CIR TH | Displays the user configured CIR threshold value for comparison with measured value. |
PIR TH | Displays the user configured PIR threshold value for comparison with measured value. |
Payload Type | Identifies the type of the payload. |
Dst Mac | Displays the value of destination MAC configured by the user to use in the frame generated by the testhead tool |
Src Mac | Displays the value of source MAC configured by the user to use in the frame generated by the testhead tool |
Vlan Tag 1 | Displays the values of the outermost vlan-tag configured by the user to use in the frame generated by the testhead tool. |
Vlan Tag 2 | Displays the values of the second vlan-tag configured by the user to use in the frame generated by the testhead tool. |
Ethertype | Displays the values of the ethertype configured by the user to use in the frame generated by the testhead tool. |
TOS | Displays the values of the IP TOS (Type of Service) configured by the user to use in the frame generated by the testhead tool. |
Src. IP | Displays the values of the source IPv4 address configured by the user to use in the frame generated by the testhead tool. |
L4 Dst Port | Displays the values of the TCP header configured by the user to use in the frame generated by the testhead tool. |
Protocol | Displays the values of the IP protocol value configured by the user to use in the frame generated by the testhead tool. |
Data Pattern | Displays the values of the data pattern configured by the user to use in the frame generated by the testhead tool. |
DSCP | Displays the values of the DSCP configured by the user to use in the frame generated by the testhead tool. |
TTL | Displays the values of the IP TTL (Time-to-Live) value configured by the user to use in the frame generated by the testhead tool. |
Dst. IP | Displays the values of the destination IPv4 address configured by the user to use in the frame generated by the testhead tool. |
L4 Src Port | Displays the values of the source port configured by the user to use in the frame generated by the testhead tool. |
testhead
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays the testhead test identified by the test name and owner.
Parameters
Output
The following output is an example of testhead information, and Table 40 describes the output fields.
Table 40: Ouput Fields: Testhead
Label | Description |
Owner | Displays the owner of the test. |
Name | Displays the name of the test. |
Description | Displays the description for the test type. |
Profile Id | Displays the associated profile ID. |
Accept. Crit. Id | Displays the test acceptance criteria ID to be used by the testhead OAM tool to declare the PASS/FAIL result at the completion of the test. |
Frame Payload Id | Displays frame payload ID, that determines the frame content of the frames generated by the tool. |
Frame Payload Type | Displays the type of frame payload to be used in frames generated by testhead tool. |
Color Aware Test | Displays if color aware tests need to be executed. |
SAP | Displays the SAP ID configured. |
Completed | Displays if the test has been completed. |
Stopped | Displays if the test has been stopped. |
FC | Displays the forwarding class (FC) to use to send the frames generated by the testhead tool. |
Start Time | Displays the start time of the test. |
End Time | Displays the end time of the test. |
Total time taken | Displays the total time taken to execute the test. |
total pkts in us | Displays the total packets in microseconds. |
OutPrf pkts in us | Displays the out-of-profile packets in microseconds. |
InPrf pkts in us | Displays the in-profile packets in microseconds. |
Total Injected | Displays the running count of total injected packets, including marker packets. |
Total Received | Displays the running count of total received packets, including marker packets. |
OutPrf Injected | Displays the running count of total out-of-profile packets, excluding marker packets. |
OutPrf Received | Displays the running count of total out-of-profile packets received, including marker packets. |
InPrf Injected | Displays the running count of total in-profile packets, excluding marker packets. |
InPrf Received | Displays the running count of total in-profile packets received, including marker packets. |
Throughput Configd | Displays the CIR Throughput rate Threshold Configured (in Kbps). |
Throughput Oper | Displays the operational rate used for the configured rate. Operational rate is arrived considering the adaptation rule configured by the user and supported hardware rate. |
Throughput Measurd | Displays the CIR Throughput Measured Value (in Kbps). |
PIR Tput Threshld | Displays the PIR Throughput rate Threshold Configured (in Kbps). |
PIR Tput Meas | Displays the PIR Throughput rate Measured Value (in Kbps). |
FLR Configured | Displays the Frame Loss Ratio Threshold Configured (in-profile). |
FLR Measurd | Displays the Frame Loss Ratio Measured (in-profile). |
FLR Acceptance | Displays Pass, Fail, or Not Applicable. It displays Pass, if the measured value is less than or equal to the configured threshold and displays "Fail" otherwise, and displays "Not Applicable", if the FLR criteria is not used to determine whether the test is in Passed or Failed status. |
OutPrf FLR Conf | Displays the out-of-profile Frame Loss Ratio configured. |
OutPrf FLR Meas | Displays the out-of-profile Frame Loss Ratio measured. |
OutPrf FLR Acep | Displays Pass, Fail, or Not Applicable. It displays Pass, if the measured value is less than or equal to the configured threshold and displays "Fail" otherwise, and displays "Not Applicable", if the out-of-profile FLR criteria is not used to determine whether the test is in Passed or Failed status. |
InPrf FLR Conf | Displays the in-profile Frame Loss Ratio configured. |
InPrf FLR Meas | Displays the in-profile Frame Loss Ratio measured. |
InPrf FLR Acep | Displays Pass, Fail, or Not Applicable. It displays Pass, if the measured value is less than or equal to the configured threshold and displays "Fail" otherwise, and displays "Not Applicable", if the in-profile FLR criteria is not used to determine whether the test is in Passed or Failed status. |
Latency Configd(us) | Displays the Latency Threshold configured (in microseconds) |
Latency Measurd(us) | Displays the Average Latency measured (in microseconds) |
Latency Acceptance | Displays Pass, Fail, or Not Applicable. It displays Pass, if the measured value is less than or equal to the configured threshold and displays "Fail" otherwise, and displays "Not Applicable", if the latency criteria is not used to determine whether the test is in Passed or Failed status. |
OutPrf Lat Conf(us) | Displays the out-of-profile latency configured. |
OutPrf Lat Meas(us) | Displays the out-of-profile latency measured. |
OutPrf Lat Acep | Displays Pass, Fail, or Not Applicable. It displays Pass, if the measured value is less than or equal to the configured threshold and displays "Fail" otherwise, and displays "Not Applicable", if the out-of-profile latency criteria is not used to determine whether the test is in Passed or Failed status. |
InPrf Lat Conf(us) | Displays the in-profile latency configured. |
InPrf Lat Meas(us) | Displays the in-profile latency measured. |
InPrf Lat Acep | Displays Pass, Fail, or Not Applicable. It displays Pass, if the measured value is less than or equal to the configured threshold and displays "Fail" otherwise, and displays "Not Applicable", if the in-profile latency criteria is not used to determine whether the test is in Passed or Failed status. |
Jitter Configd(us) | Displays the Jitter Threshold Configured (in microseconds). |
Jitter Measurd(us) | Displays the Jitter Measured (in microseconds). |
Jitter Acceptance | Displays Pass, Fail, or Not Applicable. It displays Pass, if the measured value is less than or equal to the configured threshold and displays "Fail" otherwise, and displays "Not Applicable", if the jitter criteria is not used to determine whether the test is in Passed or Failed status. |
OutPrf Jit Conf(us) | Displays the out-of-profile Jitter configured. |
OutPrf Jit Meas(us) | Displays the out-of-profile Jitter measured. |
OutPrf Jit Acep | Displays Pass, Fail, or Not Applicable. It displays Pass, if the measured value is less than or equal to the configured threshold and displays "Fail" otherwise, and displays "Not Applicable", if the out-of-profile jitter criteria is not used to determine whether the test is in Passed or Failed status. |
InPrf Jit Conf(us) | Displays the in-profile Jitter configured. |
InPrf Jit Meas(us) | Displays the in-profile Jitter measured. |
InPrf Jit Acep | Displays Pass, Fail, or Not Applicable. It displays Pass, if the measured value is less than or equal to the configured threshold and displays "Fail" otherwise, and displays "Not Applicable", if the in-profile jitter criteria is not used to determine whether the test is in Passed or Failed status. |
Total Pkts. Tx. | Displays the total number of packets (that is, data and marker) transmitted by the testhead session for the duration of the test. |
OutPrf Latency Pkt* | Displays the total number of out-of-profile marker packets received by the testhead session for the duration of the test. |
Total Tx. Fail | Displays the total number of failed transmission attempts by the testhead session for the duration of the test. |
Latency Pkts. Tx | Displays the total number of marker packets transmitted by the testhead session for the duration of the test. |
InPrf Latency Pkt* | Displays the total number of in-profile marker packets received by the testhead session for the duration of the test. |
bin-group
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays data for one or all OAM-PM bin groups.
Parameters
Output
The following output is an example of OAM-PM bin group information.
bin-group-using
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays the list of sessions configured against one or all OAM-PM bin groups.
Parameters
Output
The following output is an example of OAM-PM bin group sessions information.
session
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays the configuration and status information for an OAM-PM session.
Parameters
Output
The following output is an example of OAM-PM session information.
sessions
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays a summary of the OAM-PM sessions.
Parameters
Output
The following output is an example of summary OAM-PM session information.
statistics
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to display OAM-PM delay or synthetic loss statistics.
session
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays OAM-PM session statistics.
Parameters
dmm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to display DMM test statistics.
meas-interval
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays measured interval statistics for DMM tests in the specified session.
Parameters
Output
The following output is an example of DMM measured interval statistics information.
slm
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to display SLM test statistics.
meas-interval
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays measured interval statistics for SLM tests in the specified session
Parameters
Output
The following output is an example of SLM measured interval statistics information.
twamp-light
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to display TWAMP Light test statistics.
meas-interval
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command displays measured interval statistics for TWAMP-Light tests in the specified session.
Parameters
3.11.2.1.15. Monitor Commands
session
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document.
Description
This command monitors the raw measurement interval for the specified session.
Parameters
Output
3.11.2.1.16. Clear Commands
saa
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command clears the SAA results for the latest and the history for this test. If the test name is omitted, all the results for all tests are cleared.
Parameters
session
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command clears the raw measurement interval for the specified session and test.
Parameters
mep
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command clears the specified MEP.
Parameters
statistics
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command clears the ETH-CFM statistics counters.
test-oam
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command clears the Operations, Administration, and Maintenance test parameters.
twamp
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to clear TWAMP server statistics.
server
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command clears TWAMP server statistics.
testhead
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command enables the context to clear teasthead statistics.
result
Syntax
Context
Supported Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
Description
This command clears testhead results from the latest history for the test.
Parameters