2.1. cmd¶

Execute remote commands on the NETCONF server.

2.1.2. cmd reboot¶

vsr> cmd reboot [delay <uint32>] [cancel] [force]

Schedule a system reboot after a grace period.

Input Parameters¶

delay <uint32>: The number of seconds to wait before reboot. During that time, it is possible to cancel the reboot.
cancel: If defined, cancel a pending reboot.
force: If defined, force reboot even if startup configuration is different than running configuration.

2.1.3. cmd poweroff¶

vsr> cmd poweroff [delay <uint32>] [cancel] [force]

Schedule a system poweroff after a grace period.

Input Parameters¶

delay <uint32>: The number of seconds to wait before poweroff. During that time, it is possible to cancel the poweroff.
cancel: If defined, cancel a pending poweroff.
force: If defined, force poweroff even if startup configuration is different than running configuration.

2.1.4. cmd ping¶

vsr> cmd ping [vrf <string>] [l3vrf <string>] [count <uint16>] [packetsize <uint16>] \
...            [nodns] [ipv6] [source <string>] [rate <uint16>] <destination>

Send ICMP ECHO_REQUEST messages to network hosts and print their responses.

Input Parameters¶

vrf <string>: The VRF in which to send the ICMP ECHO_REQUESTs. By default, they are sent in the ‘main’ vrf.
l3vrf <string>: Specify the l3vrf.
count <uint16>: Stop after sending count ECHO_REQUEST packets.
packetsize <uint16>: Specifies the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data.
nodns: Numeric output only. No attempt will be made to lookup symbolic names for host addresses.
ipv6: Force IPv6 operation only. By default, it is detected from the destination. If destination is a host name, ipv4 is used by default unless this flag is set.
source <string>: Either an address, or an interface name. If interface is an address, it sets source address to specified interface address. If interface in an interface name, it sets source interface to specified interface. For IPv6, when doing ping to a link-local scope address, link specification (by the ‘%’-notation in destination, or by this option) is required.
rate <uint16>: The number of packets to send per second. By default, 1 packet is sent every second.
<destination> (mandatory): The destination host (name or IP address).

2.1.5. cmd traceroute¶

vsr> cmd traceroute [vrf <string>] [l3vrf <string>] [nodns] [ipv6] [source SOURCE] \
...            [source-interface <string>] <host>

Display the route (path) that was used to connect to a certain IP address or hostname. It also measures the transit delays among hops.

Input Parameters¶

vrf <string>

The VRF in which the packets are sent by traceroute. By default, they are sent in the ‘main’ vrf.

l3vrf <string>

Specify the l3vrf.

nodns

Do not try to map IP addresses to host names when displaying them.

ipv6

Force IPv6 operation only. By default, it is detected from the destination. If destination is a host name, ipv4 is used by default unless this flag is set.

source SOURCE

Chooses an alternative source address. Note that an address of one of the interfaces must be selected. By default, the address of the outgoing interface is used.

SOURCE

An IPv4 or IPv6 address.

source-interface <string>

Specifies the interface through which traceroute should send packets. By default, the interface is selected according to the routing table.

<host> (mandatory)

The destination host (name or IP address).

2.1.6. cmd traffic-capture¶

vsr> cmd traffic-capture [vrf <string>] [count <uint16>] [filter <pcap-expr>] <ifname> \
...            [details]

Print traffic flowing on a network interface.

Input Parameters¶

vrf <string>: The VRF in which to capture traffic. This must be the VRF the interface belongs to. By default, the interface is assumed to be in the ‘main’ vrf.
count <uint16>: Stop after capturing count packets.
filter <pcap-expr>: Optional filter expression. This must be a valid PCAP filter. See https://www.tcpdump.org/manpages/pcap-filter.7.html for more details.
<ifname> (mandatory): The name of the network interface on which to monitor traffic.
details: Show verbose packets.

2.1.7. cmd traffic-capture new¶

vsr> cmd traffic-capture new [name <name>] [vrf <string>] [count <uint16>] [filter <pcap-expr>] \
...            <ifname>

Capture traffic flowing on a network interface.

Input Parameters¶

name <name>: The name of the capture file. If not set a unique name will be automatically chosen (in format YYYY-MM-DD_HH-MM-SS.<ifname>.pcap). otherwise, if the file already exists it will be overwritten.
vrf <string>: The VRF in which to capture traffic. This must be the VRF the interface belongs to. By default, the interface is assumed to be in the ‘main’ vrf.
count <uint16>: Stop after capturing count packets.
filter <pcap-expr>: Optional filter expression. This must be a valid PCAP filter. See https://www.tcpdump.org/manpages/pcap-filter.7.html for more details.
<ifname> (mandatory): The name of the network interface on which to monitor traffic.

2.1.8. cmd traffic-capture list¶

vsr> cmd traffic-capture list

List captured traffic flow.

2.1.9. cmd traffic-capture read¶

vsr> cmd traffic-capture read <name>

Read a captured traffic flow.

Input Parameters¶

<name> (mandatory): The name of the capture to read.

2.1.10. cmd traffic-capture export¶

vsr> cmd traffic-capture export [vrf <string>] url URL [user <string>] [password <string>] <name>

Export a captured traffic flow.

Input Parameters¶

vrf <string>

The VRF in which remote access is done. By default, they are sent in the ‘main’ vrf.

url URL (mandatory)

The destination URL.

`URL` values	Description
<sftp-url>	An SFTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<scp-url>	An SCP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<smtp-url>	An SMTP(S) email URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<ftp-url>	An FTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<tftp-url>	A TFTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2].
<http-url>	An HTTP(S) file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.

user <string>

The URL user name (not percent-encoded). If specified, the user name should not be included in the URL.

password <string>

The URL password (not percent-encoded). If specified, the user name should not be included in the URL.

<name> (mandatory)

The name of the capture to export.

2.1.11. cmd traffic-capture flush¶

vsr> cmd traffic-capture flush

Flush all captured traffic flow.

2.1.12. cmd traffic-capture delete¶

vsr> cmd traffic-capture delete <name>

Delete a captured traffic flow.

Input Parameters¶

<name> (mandatory): The name of the capture to delete.

2.1.13. cmd identify-port¶

vsr> cmd identify-port NAME [duration <uint16>]

Initiate adapter-specific action intended to enable an operator to easily identify a physical network interface by sight. Typically this involves blinking one or more LEDs on the specific network port.

Input Parameters¶

NAME (mandatory)

The port name.

NAME	PCI port name.

duration <uint16>

Length of time to perform the identification, in seconds.

2.1.14. cmd troubleshooting-report¶

vsr> cmd troubleshooting-report list
vsr> cmd troubleshooting-report delete <name>
vsr> cmd troubleshooting-report flush
vsr> cmd troubleshooting-report new
vsr> cmd troubleshooting-report export [vrf <string>] url URL [user <string>] [password <string>] \
...            <name>

Manage troubleshooting reports.

Input Parameters¶

list

List existing troubleshooting reports.

delete

Delete an existing troubleshooting report.

<name> (mandatory): The name of the report to delete.

flush

Delete all existing troubleshooting reports.

new

Generate a new troubleshooting report.

export

Export an existing troubleshooting report to a remote server via SFTP.

vrf <string>

The VRF in which remote access is done. By default, they are sent in the ‘main’ vrf.

url URL (mandatory)

The destination URL.

`URL` values	Description
<sftp-url>	An SFTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<scp-url>	An SCP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<smtp-url>	An SMTP(S) email URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<ftp-url>	An FTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<tftp-url>	A TFTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2].
<http-url>	An HTTP(S) file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.

user <string>

The URL user name (not percent-encoded). If specified, the user name should not be included in the URL.

password <string>

The URL password (not percent-encoded). If specified, the user name should not be included in the URL.

<name> (mandatory)

The name of the report to export.

2.1.15. cmd dns proxy clear-cache¶

vsr> cmd dns proxy clear-cache [vrf <string>]

Clear DNS proxy cache.

Input Parameters¶

vrf <string>: Specify the VRF.

2.1.16. cmd dhcp-client renew-lease¶

vsr> cmd dhcp-client renew-lease [vrf <string>] [l3vrf <string>] IFNAME

Renew DHCP client lease period.

Input Parameters¶

vrf <string>

Specify the VRF.

l3vrf <string>

Specify the l3vrf.

IFNAME (mandatory)

The interface name.

IFNAME

An interface name.

2.1.17. cmd bgp rpki ssh-key create¶

Note

requires a Product License.

vsr> cmd bgp rpki ssh-key create type TYPE name <string>

Create SSH keys.

Input Parameters¶

type TYPE (mandatory)

SSH key type.

`TYPE` values	Description
rsa-1024	RSA in 1024 bits.
rsa-2048	RSA in 2048 bits.
rsa-4096	RSA in 4096 bits.
ecdsa-256	ECDSA in 256 bits.
ecdsa-384	ECDSA in 384 bits.
ecdsa-521	ECDSA in 521 bits.
ed25519	EDDSA in 25519 bits.

name <string> (mandatory)

Name of the new key pair.

2.1.18. cmd bgp rpki ssh-key list¶

Note

requires a Product License.

vsr> cmd bgp rpki ssh-key list [detail]

List SSH keys.

Input Parameters¶

detail: Show public key.

2.1.19. cmd bgp rpki ssh-key delete¶

Note

requires a Product License.

vsr> cmd bgp rpki ssh-key delete <string>

Delete SSH keys.

Input Parameters¶

<string> (mandatory): Delete an existing key pair.

2.1.20. cmd bgp rpki ssh-host add¶

Note

requires a Product License.

vsr> cmd bgp rpki ssh-host add HOST [port PORT] [vrf VRF]

Add host to routing known hosts.

Input Parameters¶

HOST (mandatory)

Host name to add to known hosts.

HOST

The domain-name type represents a DNS domain name. Fully quallified left to the models which utilize this type. Internet domain names are only loosely specified. Section 3.5 of RFC 1034 recommends a syntax (modified in Section 2.1 of RFC 1123). The pattern above is intended to allow for current practice in domain name use, and some possible future expansion. It is designed to hold various types of domain names, including names used for A or AAAA records (host names) and other records, such as SRV records. Note that Internet host names have a stricter syntax (described in RFC 952) than the DNS recommendations in RFCs 1034 and 1123, and that systems that want to store host names in schema nodes using the domain-name type are recommended to adhere to this stricter standard to ensure interoperability. The encoding of DNS names in the DNS protocol is limited to 255 characters. Since the encoding consists of labels prefixed by a length bytes and there is a trailing NULL byte, only 253 characters can appear in the textual dotted notation. Domain-name values use the US-ASCII encoding. Their canonical format uses lowercase US-ASCII characters. Internationalized domain names MUST be encoded in punycode as described in RFC 3492.

port PORT

Use a specific port to join the remote host.

PORT	A 16-bit port number used by a transport protocol such as TCP or UDP.

vrf VRF

Specify the VRF.

VRF	The vrf name.

2.1.21. cmd bgp rpki ssh-host delete¶

Note

requires a Product License.

vsr> cmd bgp rpki ssh-host delete HOST-NAME

Delete host from routing known hosts.

Input Parameters¶

HOST-NAME (mandatory)

Host name to remove from known hosts.

HOST-NAME

The domain-name type represents a DNS domain name. Fully quallified left to the models which utilize this type. Internet domain names are only loosely specified. Section 3.5 of RFC 1034 recommends a syntax (modified in Section 2.1 of RFC 1123). The pattern above is intended to allow for current practice in domain name use, and some possible future expansion. It is designed to hold various types of domain names, including names used for A or AAAA records (host names) and other records, such as SRV records. Note that Internet host names have a stricter syntax (described in RFC 952) than the DNS recommendations in RFCs 1034 and 1123, and that systems that want to store host names in schema nodes using the domain-name type are recommended to adhere to this stricter standard to ensure interoperability. The encoding of DNS names in the DNS protocol is limited to 255 characters. Since the encoding consists of labels prefixed by a length bytes and there is a trailing NULL byte, only 253 characters can appear in the textual dotted notation. Domain-name values use the US-ASCII encoding. Their canonical format uses lowercase US-ASCII characters. Internationalized domain names MUST be encoded in punycode as described in RFC 3492.

2.1.22. cmd certificate import¶

Note

requires a Product License.

vsr> cmd certificate import [vrf VRF] [name NAME] url URL [private-key-url PRIVATE-KEY-URL] \
...            [user <string>] [password <string>] [force]

Import a X509 certificate from network, in PEM format.

Input Parameters¶

vrf VRF

The vrf in which the import is performed.

VRF	The vrf name.

name NAME

The name to assign of the certificate.

NAME	Certificate name.

url URL (mandatory)

The URL from which to download the certificate in PEM format.

`URL` values	Description
<http-url>	An HTTP(S) file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<sftp-url>	An SFTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<scp-url>	An SCP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<ftp-url>	An FTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<tftp-url>	A TFTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2].

private-key-url PRIVATE-KEY-URL

The URL from which to download the certificate private key in PEM format.

`PRIVATE-KEY-URL` values	Description
<http-url>	An HTTP(S) file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<sftp-url>	An SFTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<scp-url>	An SCP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<ftp-url>	An FTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<tftp-url>	A TFTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2].

user <string>

Both the url and private-key-url user name (NOT URL-encoded). If specified, the user name must NOT be included in the URLs.

password <string>

Both the url and private-key-url password (NOT URL-encoded). If specified, the password must NOT be included in the URLs.

force

Delete the certificate if it exists, this will allow update behavior for the import command.

2.1.23. cmd certificate export¶

Note

requires a Product License.

vsr> cmd certificate export [vrf VRF] [name NAME] url URL [user <string>] [password <string>]

Export a X509 certificate in PEM format.

Input Parameters¶

vrf VRF

The vrf in which the export is performed.

VRF	The vrf name.

name NAME

The name of the certificate.

NAME	Certificate name.

url URL (mandatory)

The URL where the certificate is updloaded.

`URL` values	Description
<http-url>	An HTTP(S) file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<sftp-url>	An SFTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<scp-url>	An SCP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<ftp-url>	An FTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2]. The :/?#[]@!$&’()*+,;= characters in the user and password must be percent-encoded (e.g: ‘?’ becomes ‘%3f’). See RFC 3986 section 2.1. For convenience, you should use the separate user and password fields.
<tftp-url>	A TFTP file URL. IPv6 addresses must be surrounded by square brackets [1234:bada::2].

user <string>

The URL user name (not percent-encoded). If specified, the user name should not be included in the URL.

password <string>

The URL password (not percent-encoded). If specified, the user name should not be included in the URL.

2.1.24. cmd certificate add¶

Note

requires a Product License.

vsr> cmd certificate add [name NAME] data <string> [private-key <string>]

Add a X509 certificate in PEM format.

Input Parameters¶

name NAME

The name to assign to the certificate.

NAME	Certificate name.

data <string> (mandatory)

PEM-encoded X509 certificate.

private-key <string>

PEM-encoded X509 private key.

2.1.25. cmd certificate delete¶

Note

requires a Product License.

vsr> cmd certificate delete name NAME

Delete a X509 certificate.

Input Parameters¶

name NAME (mandatory)

The name of the certificate.

NAME	Certificate name.

2.1. cmd¶

2.1.1. cmd banner¶

Input Parameters¶

2.1.2. cmd reboot¶

Input Parameters¶

2.1.3. cmd poweroff¶

Input Parameters¶

2.1.4. cmd ping¶

Input Parameters¶

2.1.5. cmd traceroute¶

Input Parameters¶

2.1.6. cmd traffic-capture¶

Input Parameters¶

2.1.7. cmd traffic-capture new¶

Input Parameters¶

2.1.8. cmd traffic-capture list¶

2.1.9. cmd traffic-capture read¶

Input Parameters¶

2.1.10. cmd traffic-capture export¶

Input Parameters¶

2.1.11. cmd traffic-capture flush¶

2.1.12. cmd traffic-capture delete¶

Input Parameters¶

2.1.13. cmd identify-port¶

Input Parameters¶

2.1.14. cmd troubleshooting-report¶

Input Parameters¶

2.1.15. cmd dns proxy clear-cache¶

Input Parameters¶

2.1.16. cmd dhcp-client renew-lease¶

Input Parameters¶

2.1.17. cmd bgp rpki ssh-key create¶

Input Parameters¶

2.1.18. cmd bgp rpki ssh-key list¶

Input Parameters¶

2.1.19. cmd bgp rpki ssh-key delete¶

Input Parameters¶

2.1.20. cmd bgp rpki ssh-host add¶

Input Parameters¶

2.1.21. cmd bgp rpki ssh-host delete¶

Input Parameters¶

2.1.22. cmd certificate import¶

Input Parameters¶

2.1.23. cmd certificate export¶

Input Parameters¶

2.1.24. cmd certificate add¶

Input Parameters¶

2.1.25. cmd certificate delete¶

Input Parameters¶