sdp-mtu orig-sdp-id size-inc start-octets end-octets [step step-size] [timeout timeout] [interval interval]
oam
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
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 IP/MPLS router. 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-T in the access-uplink mode of operation.
To terminate an sdp-mtu in progress, use the CLI break sequence <Ctrl-C>.
SDP Path MTU tests can be performed using the sdp-mtu size-inc keyword to easily determine the path-mtu of a 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.
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.
Specifies the sdp-id to be used by sdp-ping, expressed as a decimal integer. The far-end address of the specified sdp-id is the expected responder-id within each reply received. The specified sdp-id defines the encapsulation of the SDP tunnel encapsulation used to reach the far end. This can be IP 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 (when the interval timer expires, sdp-ping attempts to send the next request if required).
Specifies that an incremental path MTU test is performed by sending a series of message requests with increasing MTU sizes. The start-octets and end-octets parameters are described as follows.
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 is not 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 are sent.
Specifies the timeout parameter in seconds, expressed as a decimal integer. This value is used to override the default timeout value and is the amount of time that the router waits for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response has not been received. A ‛request timeout’ message is displayed by the CLI for each message request sent that expires. Any response received after the request times out is silently discarded.
Specifies the interval parameter in seconds, expressed as a decimal integer. This parameter is used to override the default request message send interval and defines the minimum amount of time that must expire before the next message request is sent.
If the interval is set to 1 second, and the timeout value is set to 10 seconds, the maximum time between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of a message reply corresponding to the outstanding message request.
The following is an SDP MTU path test sample output.
Sample SDP MTU path test sample output*A:Dut-A# oam sdp-mtu 1201 size-inc 512 3072 step 256
Size Sent Response
----------------------------
512 . Success
768 . Success
1024 . Success
1280 . Success
1536 . Success
1792 . Success
2048 . Success
2304 . Success
2560 . Success
2816 . Success
3072 . Success
Maximum Response Size: 3072
*A:Dut-A#
svc-ping ip-address [service service-id] [local-sdp] [remote-sdp]
<GLOBAL>
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
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-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 |
Specifies the far-end IP address to which to send the svc-ping request message in dotted-decimal notation.
Specifies the service ID of the service being tested. The service ID need not exist on the local to receive a reply message.
Specifies the svc-ping request message should be sent using the same service tunnel encapsulation labeling as service traffic. If local-sdp is specified, the command attempts to use an egress sdp-id bound to the service with the specified far-end IP address with the VC-Label for the service. The far-end address of the specified sdp-id is the expected responder-id within the reply received. The sdp-id defines the encapsulation of the SDP tunnel encapsulation used to reach the far end; this can be IP 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 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) |
Specifies svc-ping reply message from the far-end should be sent using the same service tunnel encapsulation labeling as service traffic. If remote-sdp is specified, the far-end responder attempts to use an egress sdp-id bound to the service with the message originator as the destination IP address with the VC-Label for the service. The sdp-id defines the encapsulation of the SDP tunnel encapsulation used to reply to the originator; this can be IP 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.
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) |
The following sample output is an example of svc-ping information.
Sample outputA:ALU_G7X1>config# oam svc-ping 10.20.1.3 service 1
Service-ID: 1
Err Info Local Remote
-----------------------------------------------------
Type: EPIPE EPIPE
Admin State: Up Up
==> Oper State: Down Down
Service-MTU: 1514 1514
Customer ID: 1 1
IP Interface State: Up
Actual IP Addr: 10.20.1.1 10.20.1.3
Expected Peer IP: 10.20.1.3 10.20.1.1
SDP Path Used: No No
SDP-ID: 1 2
Admin State: Up Up
Operative State: Up Up
Binding Admin State:Up Up
Binding Oper State: Up Up
Binding VC ID: 10 10
Binding Type: Spoke Spoke
Binding Vc-type: Ether Ether
Binding Vlan-vc-tag:N/A N/A
Egress Label: 131070 131068
Ingress Label: 131068 131070
Egress Label Type: Signaled Signaled
Ingress Label Type: Signaled Signaled
Request Result: Send - Reply Received: Responder Service ID Oper-Down
A:ALU_G7X1>config#
vprn-ping service-id source ip-address destination ip-address [fc fc-name] [size size] [ttl vc-label-ttl] [return-control] [interval interval] [send-count send-count] [timeout timeout]
<GLOBAL>
config>saa>test>type
Supported on all 7210 SAS platforms as described in this document
This command performs a VPRN ping.
Specifies the VPRN service ID to diagnose or manage.
Specifies the IP prefix for the source IP address in dotted-decimal notation.
Specifies the IP prefix for the destination IP address in dotted-decimal notation.
Specifies the OAM request packet size in octets, expressed as a decimal integer.
Specifies the TTL value in the VC label for the OAM request, expressed as a decimal integer.
Specifies the response to come on the control plane.
Specifies the interval parameter in seconds, expressed as a decimal integer. This parameter is used to override the default request message send interval and defines the minimum amount of time that must expire before the next message request is sent.
If the interval is set to 1 second 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.
Specifies the number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. Each message request must either timeout or receive a reply before the next message request is sent. The message interval value must be expired before the next message request is sent.
Specifies the timeout parameter in seconds, expressed as a decimal integer. This value is used to override the default timeout value and is the amount of time that the router waits for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response has not been received. Any response received after the request times out is silently discarded.
Specifies the forwarding class of the MPLS echo request encapsulation.
A:PE_1# oam vprn-ping 25 source 10.4.128.1 destination 10.16.128.0
Sequence Node-id Reply-Path Size RTT
----------------------------------------------------------------------------
[Send request Seq. 1.]
1 10.128.0.3:cpm In-Band 100 0ms
----------------------------------------------------------------------------
...
A:PE_1#
----------------------------------------------------------------------------
A:PE_1#
vprn-trace service-id source src-ip destination ip-address [fc fc-name] [size size] [min-ttl vc-label-ttl] [max-ttl vc-label-ttl] [return-control] [send-count send-count] [interval seconds] [timeout timeout]
<GLOBAL>
config>saa>test>type
Supported on all 7210 SAS platforms as described in this document
Performs VPRN trace.
Specifies the VPRN service ID to diagnose or manage.
Specifies the IP prefix for the source IP address in dotted-decimal notation.
Specifies the IP prefix for the destination IP address in dotted-decimal notation.
Specifies the OAM request packet size in octets, expressed as a decimal integer.
Specifies the minimum TTL value in the VC label for the trace test, expressed as a decimal integer.
Specifies the maximum TTL value in the VC label for the trace test, expressed as a decimal integer.
Specifies the OAM reply to a data plane OAM request be sent using the control plane instead of the data plane.
Specifies the number of OAM requests sent for a particular TTL value, expressed as a decimal integer.
Specifies the interval parameter in seconds, expressed as a decimal integer. This parameter is used to override the default request message send interval and defines the minimum amount of time that must expire before the next message request is sent.
If the interval is set to 1 second 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.
Specifies the timeout parameter in seconds, expressed as a decimal integer. This value is used to override the default timeout value and is the amount of time that the router waits for a message reply after sending the message request. Upon the expiration of message timeout, the requesting router assumes that the message response has not been received. Any response received after the request times out is silently discarded.
Specifies the forwarding class of the MPLS echo request encapsulation.
A:PE_1# oam vprn-
trace 25 source 10.4.128.1 destination 10.16.128.0
TTL Seq Reply Node-id Rcvd-on Reply-Path RTT
----------------------------------------------------------------------------
[Send request TTL: 1, Seq. 1.]
1 1 1 10.128.0.4 cpm In-Band 0ms
Requestor 10.128.0.1 Route: 0.0.0.0/0
Vpn Label: 131071 Metrics 0 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65100:1
Responder 10.128.0.4 Route: 10.16.128.0/24
Vpn Label: 131071 Metrics 0 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65001:100
[Send request TTL: 2, Seq. 1.]
2 1 1 10.128.0.3 cpm In-Band 0ms
Requestor 10.128.0.1 Route: 0.0.0.0/0
Vpn Label: 131071 Metrics 0 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65100:1
Responder 10.128.0.3 Route: 10.16.128.0/24
Vpn Label: 0 Metrics 0 Pref 0 Owner local
Next Hops: [1] ifIdx 2 nextHopIp 10.16.128.0
[Send request TTL: 3, Seq. 1.]
[Send request TTL: 4, Seq. 1.]
...
----------------------------------------------------------------------------
A:PE_1#