sdp-mtu orig-sdp-id size-inc start-octetsend-octets[step step-size][timeout timeout][interval interval]
oam
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 specified 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 7705 SAR. OAM request messages sent within an IP SDP must have the "DF" IP header bit set to 1 to prevent message fragmentation.
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 will be 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 a response timeout occurs, the maximum size message replied to indicates the largest size OAM request message that received a valid reply.
To terminate an sdp-mtu in progress, use the CLI break sequence Ctrl-c.
The sdp-mtu command probes the far-end port using the configured MTU of the near-end port, not the configured MTU of the far-end port. For example, a far-end port that is physically capable of receiving jumbo frames would respond to sdp-mtu probes up to the jumbo frame size, regardless of the configured MTU of the far-end port. This assumes that the intermediate transport network can switch frames of this size.
specifies the SDP-ID to be used by sdp-mtu expressed as a decimal integer. The far-end address of the specified SDP-ID is the expected responder-id within each reply received. The specified SDP-ID defines the SDP tunnel encapsulation used to reach the far end — GRE, IP, or MPLS. If orig-sdp-id is invalid or administratively down or unavailable for some reason, the SDP echo request message is not sent and an appropriate error message is displayed (once the interval timer expires, sdp-mtu will attempt to send the next request if required).
indicates that an incremental path MTU test will be performed by sending a series of message requests with increasing MTU sizes
specifies the beginning size in octets of the first message sent for an incremental MTU test, expressed as a decimal integer
specifies the ending size in octets of the last message sent for an incremental MTU test, expressed as a decimal integer. The specified value must be greater than start-octets.
specifies the number of octets to increment the message size request for each message sent for an incremental MTU test, expressed as a decimal integer. The next size message will not be sent until a reply is received or three messages have timed out at the current size.
If the incremented size exceeds the end-octets value, no more messages will be sent.
specifies the amount of time that the router will wait for a message reply after sending the message request. If the timeout expires, the requesting router assumes that the message response will not be received. A "request timeout" message is displayed by the CLI for each message request sent that expires. Any response received after the request times out will be silently discarded.
This value is used to override the default timeout value.
defines the minimum amount of time that must expire before the next message request is sent.
If the interval is set to 1 s, and the timeout value is set to 10 s, then the maximum time between message requests is 10 s and the minimum is 1 s. This depends upon the receipt of a message reply corresponding to the outstanding message request.
This parameter is used to override the default request message send interval.
The following output is an example of SDP MTU path test information.
SDP MTU Path Test Output*A:router 1> sdp-mtu 6 size-inc 512 3072 step 256
Size Sent Response
------- ---- ---------------------------
512 . Success
768 . Success
1024 . Success
1280 . Success
1536 . Success
1792 . Success
2048 . Success
2304 … Request Timeout
2560 … Request Timeout
2816 … Request Timeout
3072 … Request Timeout
Maximum Response Size: 2048
svc-ping ip-address service [service-id][local-sdp][remote-sdp]
oam
This command tests a service ID for correct and consistent provisioning between two service endpoints. The 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 will be sent per command; no count or interval parameter is supported and round-trip time is not calculated. A timeout value of 10 s 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 will be shown as N/A.
To terminate an svc-ping in progress, use the CLI break sequence Ctrl-c.
Upon request timeout, message response, request termination, or request error, the local and remote information described in Table: SVC Ping Report Field will be 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 Service-ID being tested |
Service-ID |
Local Service Type |
The type of service being tested. If service-id does not exist locally, N/A is displayed. |
Apipe, Epipe, Fpipe, Hpipe |
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 will be 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 will be 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. |
Apipe, Epipe, Fpipe, Hpipe |
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 a 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. The sdp-ping command 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 7705 SAR 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 |
Indicates whether the originating 7705 SAR used the originating SDP-ID to send the svc-ping request. If a valid originating SDP-ID is found, is operational and has a valid egress service label, the originating 7705 SAR should use the SDP-ID as the requesting path if sdp-path has been defined. If the originating 7705 SAR uses the originating SDP-ID as the request path, Yes is displayed. If the originating 7705 SAR 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 shut down, 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-Down |
||
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-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 |
||
Originating SDP-ID Binding Oper State |
The local operational state of the originating 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 |
||
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 7705 SAR will not use an SDP-ID as the return path, but the appropriate responding SDP-ID will be displayed. If a valid SDP-ID return path is not found to the originating 7705 SAR that is bound to the service-id, Non-Existent is displayed. |
resp-sdp-id |
Non-Existent |
||
Responding SDP-ID Path Used |
Indicates whether the responding 7705 SAR 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, is operational and has a valid egress service label, the far-end 7705 SAR 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-Down |
||
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-iddoes 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 7705 SAR considers the displayed egress service label operational, Up is displayed. If the originating 7705 SAR 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 7705 SAR for this service-id to the originating 7705 SAR. If service-id does not exist in the remote 7705 SAR, 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 considers its egress service label operational, Up is displayed. If the responding 7705 SAR considers its egress service label inoperative, Down is displayed. If the service-id does not exist or the responder's egress service label is non-existent, N/A is displayed. |
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 7705 SAR. If service-idservice-iddoes not exist locally, N/A is displayed. If service-idexists 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 originator's 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 7705 SAR considers its ingress service label operational, Up is displayed. If the originating 7705 SAR considers its 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 7705 SAR. This is the service label that the far end is expecting to receive for service-id when sending to the originating 7705 SAR. If service-id does not exist in the remote 7705 SAR, N/A is displayed. If service-id exists, but an ingress service label has not been assigned in the remote 7705 SAR, 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 7705 SAR. If the ingress service label is manually defined on the remote 7705 SAR, Manual is displayed. If the ingress service label is dynamically signaled on the remote 7705 SAR, Signaled is displayed. If the service-id does not exist on the remote 7705 SAR, N/A is displayed. |
Manual |
Signaled |
||
N/A |
||
Responders Ingress Service Label State |
The assigned ingress service label state on the remote 7705 SAR. If the remote 7705 SAR considers its ingress service label operational, Up is displayed. If the remote 7705 SAR considers its ingress service label inoperative, Down is displayed. If the service-id does not exist on the remote 7705 SAR or the ingress service label has not been assigned on the remote 7705 SAR, N/A is displayed. |
Up |
Down |
||
N/A |
specifies the far-end IP address to which to send the svc-ping request message in dotted-decimal notation
identifies the service being tested. The Service ID need not exist on the local 7705 SAR to receive a reply message.
This is a mandatory parameter.
specifies that the svc-ping request message should be sent using the same service tunnel encapsulation labeling as service traffic
If local-sdp is specified, the command attempts to use an egress SDP-ID bound to the service with the specified far-end IP address with the VC-Label for the service. The far-end address of the specified SDP-ID is the expected responder-id within the reply received. The SDP-ID defines the SDP tunnel encapsulation used to reach the far end — GRE, IP, or MPLS. On originator egress, the service-ID must have an associated VC-Label to reach the far-end address of the SDP-ID and the SDP-ID must be operational for the message to be sent.
If local-sdp is not specified, the svc-ping request message is sent with GRE encapsulation with the OAM label.
Table: Local SDP Message Results 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/GRE OAM (PLP) |
No |
None |
No Valid SDP-ID Bound |
Yes |
Generic IP/GRE OAM (PLP) |
No |
None |
SDP-ID Valid But Down |
Yes |
Generic IP/GRE OAM (PLP) |
No |
None |
SDP-ID Valid and Up, But No Service Label |
Yes |
Generic IP/GRE OAM (PLP) |
No |
None |
SDP-ID Valid, Up and Egress Service Label |
Yes |
Generic IP/GRE OAM (PLP) |
Yes |
SDP Encapsulation with Egress Service Label (SLP) |
specifies that the svc-ping reply message from the far end should be sent using the same service tunnel encapsulation labeling as service traffic
If remote-sdp is specified, the far end responder attempts to use an egress SDP-ID bound to the service with the message originator as the destination IP address with the VC-Label for the service. The SDP-ID defines the SDP tunnel encapsulation used to reply to the originator — GRE, IP, or MPLS. On responder egress, the service-ID must have an associated VC-Label to reach the originator address of the SDP-ID and the SDP-ID must be operational for the message to be sent. If remote-sdp is not specified, the svc-ping request message is sent with GRE encapsulation with the OAM label.
Table: Remote SDP Message Results 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/GRE OAM (PLP) |
Generic IP/GRE OAM (PLP) |
Invalid Service-ID |
Generic IP/GRE OAM (PLP) |
Generic IP/GRE OAM (PLP) |
No Valid SDP-ID Bound on Service-ID |
Generic IP/GRE OAM (PLP) |
Generic IP/GRE OAM (PLP) |
SDP-ID Valid But Down |
Generic IP/GRE OAM (PLP) |
Generic IP/GRE OAM (PLP) |
SDP-ID Valid and Up, but No Service Label |
Generic IP/GRE OAM (PLP) |
Generic IP/GRE OAM (PLP) |
SDP-ID Valid and Up, Egress Service Label, but VC-ID Mismatch |
Generic IP/GRE OAM (PLP) |
Generic IP/GRE OAM (PLP) |
SDP-ID Valid and Up, Egress Service Label, but VC-ID Match |
Generic IP/GRE OAM (PLP) |
SDP Encapsulation with Egress Service Label (SLP) |
The following output is an example of SVC ping information.
Output Example*A:router1> svc-ping far-end 10.10.10.10 service 101 local-sdp remote-sdp
Service-ID: 101
Err Info Local Remote
-----------------------------------------------------
Type: CPIPE CPIPE
Admin State: Up Up
Oper State: Up Up
Service-MTU: 1000 1000
Customer ID: 1001 1001
==> IP Interface State: Down
Actual IP Addr: 10.10.10.11 10.10.10.10
Expected Peer IP: 10.10.10.10 10.10.10.11
==> SDP Path Used: Yes Yes
SDP-ID: 123 325
Admin State: Up Up
Operative State: Up Up
Binding Admin State:Up Up
Binding Oper State: Up Up
Binding VC ID: 101 101
Binding Type: Spoke Spoke
Binding Vc-type: CesoPsn CesoPsn
Binding Vlan-vc-tag:0 0
==> Egress Label: 131066 131064
Ingress Label: 131064 131066
Egress Label Type: Signaled Signaled
Ingress Label Type: Signaled Signaled
Request Result: Sent - Reply Received