<request-ping-l2circuit-virtual-circuit>
Usage
<rpc>
<request-ping-l2circuit-virtual-circuit>
<v1/>
<neighbor>neighbor</neighbor> <!-- mandatory -->
<virtual-circuit-id>virtual-circuit-id</virtual-circuit-id> <!-- mandatory -->
<reply-mode>reply-mode</reply-mode>
<count>count</count>
<source>source</source>
<destination>destination</destination>
<exp>exp</exp>
<detail/>
<size>size</size>
<sweep/>
<logical-system>logical-system</logical-system>
</request-ping-l2circuit-virtual-circuit>
</rpc>
Description
Locate LSP from virtual circuit information
<v1>—Ping using
Layer 2 circuit TLV (type 9)
no-reply - Do not reply
ip-udp - Reply via an IPv4 or IPv6 UDP packet
application-level-control-channel - Reply via application level control channel
<neighbor>—Address
of remote neighbor
no-reply - Do not reply
ip-udp - Reply via an IPv4 or IPv6 UDP packet
application-level-control-channel - Reply via application level control channel
<virtual-circuit-id>—Layer 2 circuit identifier
no-reply - Do not reply
ip-udp - Reply via an IPv4 or IPv6 UDP packet
application-level-control-channel - Reply via application level control channel
<reply-mode>—Reply
mode for ping request
no-reply - Do not reply
ip-udp - Reply via an IPv4 or IPv6 UDP packet
application-level-control-channel - Reply via application level control channel
<count>—Number of
ping requests to send
<source>—IP source
address of echo request
<destination>—IP
address of destination for echo request
<exp>—Forwarding
class
<detail>—Display
detailed output
<size>—Size of lsp
ping request packet
<sweep>—Incremental
ping to find MTU
<logical-system>—Name of logical system