command stringlengths 2 75 | syntax stringlengths 0 289k | hierarchy_level stringlengths 0 6.91k | description stringlengths 0 45.2k | options listlengths 0 499 | required_privilege_level stringlengths 0 330k | release_information stringlengths 0 3.14k | related_documentation listlengths 0 22 |
|---|---|---|---|---|---|---|---|
request system process terminate | request system process terminate process-id | Terminate any process that you specify with the process identification number (process ID or pid). The
request system process terminate command is an alternative to using the restart command. The restart
command terminates and restarts a process that you specify by process name, but limits you to only
certain well-know... | [
{
"name": "process-id",
"desc": "Identification number for a process. Range: 1 through 99999"
}
] | maintenance
Output Fields
When you enter this command, you are not provided feedback on the status of your request. You can
use the show system processes extensive command to confirm the process that was terminated.
Sample Output
request system process terminate
user@host> request system process terminate 1514 | Command introduced before Junos OS Release 7.4. | [
"Junos OS Routing Processes"
] | |
request system reboot (Junos OS Evolved) | request system reboot
<at time>
<hitless> | <hitless no-confirm>
<in minutes>
<message "text"> | Reboot the entire system (all nodes).
To reboot a single node, use the request node reboot command instead. | [
{
"name": "none",
"desc": "Reboot the software immediately."
},
{
"name": "at time",
"desc": "(Optional) Time at which to reboot the software, specified in one of the following ways:"
},
{
"name": "now",
"desc": "Stop or reboot the software immediately. This is the default."
},
{... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system reboot
user@host-re0> request system reboot
The entire system (all nodes) will reboot causing traffic loss, do you wish to continue?
[yes,no] (no) yes
*** System shutdown message... | Command introduced in Junos OS Evolved Release 18.3R1.
Option to set a future date and time introduced in Junos OS Evolved Release 25.2R1.
hitless and hitless no-confirm options introduced in Junos OS Evolved release 25.4R1 for QFX Series
devices. | [] | |
request system reboot (Junos OS with Upgraded FreeBSD) | request system reboot
<at time>
<both-routing-engines>
<in minutes>
<junos>
<message "text">
<network>
<oam>
<other-routing-engine>
<usb> | For devices running FreeBSD Release 10 or above, use this command to reboot the device software. | [
{
"name": "none",
"desc": "Reboot the device software immediately."
},
{
"name": "at time",
"desc": "(Optional) Time at which to reboot the software, specified in one of the following ways:"
},
{
"name": "now",
"desc": "Stop or reboot the software immediately. This is the default."
... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system reboot
user@host> request system reboot
Reboot the system ? [yes,no] (no)
request system reboot (at 2300)
user@host> request system reboot at 2300 message “Maintenance time!” ... | Command introduced in Junos OS Release 15.1.
Command introduced for all platforms using Junos OS with upgraded FreeBSD. To find which platforms
in which releases use Junos OS with upgraded FreeBSD, see Feature Explorer, enter freebsd, and select
Junos kernel upgrade to FreeBSD 10+. | [
"clear system reboot"
] | |
request system reboot (Junos OS) | request system reboot
<all-members | local | member member-id>
<at time>
<in minutes>
<in-service>
<hypervisor>
<junos | network | oam | usb>
<message “text”>
<slice slice> | Use this command to reboot the device software.
This command can be used on standalone devices and on devices supported in a Virtual Chassis, Virtual
Chassis Fabric, or QFabric system.
Starting with Junos OS Release 15.1F3, the request system reboot command reboots only the guest
operating system on the PTX5000 with RE... | [
{
"name": "none",
"desc": "Reboot the software immediately. NOTE: On EX Series and QFX Series switches, the device waits for one minute before rebooting. To reboot the device immediately, use the request system reboot at now command."
},
{
"name": "all-members |",
"desc": ""
},
{
"name":... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system reboot
user@host> request system reboot
Reboot the system ? [yes,no] (no)
request system reboot (at 2300)
user@host> request system reboot at 2300 message ?Maintenance time!? ... | Command introduced before Junos OS Release 7.4.
Option other-routing-engine introduced in Junos OS Release 8.0.
Option sfc introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Option partition changed to slice in Junos OS Release 10.0 for EX Series switches.
Option both-routing-engines introduced in Junos ... | [] | |
request system reboot (SRX Series) | request system reboot <at time> <in minutes><media><message “text”> | Reboot the software. | [
{
"name": "at time (Optional)",
"desc": "Specify the time at which to reboot the device. You can specify time in one of"
},
{
"name": "the following ways:",
"desc": ""
},
{
"name": "now",
"desc": "Reboot the device immediately. This is the default."
},
{
"name": "+minutes",
... | maintenance | Command introduced in Junos OS Release 10.1.
Command hypervisor option introduced in Junos OS Release 15.1X49-D10 for vSRX Virtual Firewall. | [
"request system software rollback (SRX Series)"
] | |
request system reboot usb (SRX Series) | request system reboot usb <yes|no> | Use this command to boot from the USB, without power cycling the SRX device. This command helps to
detect USB with a soft reboot and provides the user with control over the boot sequence for soft reboot
without turning off the device. | [
{
"name": "yes – Reboot system",
"desc": "No – Do not reboot system"
}
] | maintenance | Command introduced in Junos OS Release 21.2R1. | [] | |
request system recover | request system recover (junos-volume | oam-volume)
<(all-members | local | member member-id)> | For devices running FreeBSD 10 or above, use this command to recover a specified volume of the
system.
Guest network functions (GNFs) do not support the recover option under the request system command.
See Components of Junos Node Slicing for more details on GNF. | [
{
"name": "(all-members |",
"desc": ""
},
{
"name": "local | member",
"desc": ""
},
{
"name": "member-id)",
"desc": "(EX Series Virtual Chassis only) (Optional) Specify the members who need to recover archive data and executable areas in a Virtual Chassis:"
},
{
"name": "all-... | view
Sample Output
request system recover junos-volume (While booted on the /junos volume)
user@host> request system recover junos-volume
ERROR: You are currently running on the Junos volume
ERROR: A recovery of the Junos volume is not possible
request system recover junos-volume (While booted on the /oam volume)
user@... | Command introduced in Junos OS Release 15.1.
Command introduced for all platforms using Junos OS with upgraded FreeBSD. To find which platforms
in which releases use Junos OS with upgraded FreeBSD, see Feature Explorer, enter freebsd, and select
Junos kernel upgrade to FreeBSD 10+.
Options (all-members | local | member... | [] | |
request system restore state path | request system restore state path /host/tmp/ folder | Use this command to restore your backup JDM configuration from the /host/tmp/ folder. | [] | Command introduced in Junos OS Release 23.1R1. | [
"Generic Guidelines for Using JDM Server Commands"
] | ||
request system save state path | request system save state path /host/tmp/ folder | Use this command to back up your JDM configuration to the /host/tmp/ folder. | [] | Command introduced in Junos OS Release 23.1R1. | [
"Generic Guidelines for Using JDM Server Commands"
] | ||
request system scripts add (Chassis Cluster) | request system scripts add package-name <no-copy | unlink>
<master>
<backup> | CLI command to install AI-Script install packages on SRX Series Firewalls in a chassis cluster. | [
{
"name": "package-name",
"desc": "Specify AI-Script install package name."
},
{
"name": "no-copy",
"desc": "(Optional) Do not save a copy of the AI script package file."
},
{
"name": "unlink",
"desc": "(Optional) Remove the AI script package after successful installation."
},
{
... | maintenance
Sample Output
request system scripts add package-name
user@host> request system scripts add jais-5.0R1.0-signed.tgz master
[: -a: unexpected operator
grep: /etc/db/pkg/jais/+COMMENT: No such file or directory
Installing package '/var/tmp/jais-5.0R4.0-signed.tgz' ...
Verified jais-5.0R4.0.tgz signed by ... | Command introduced before Junos OS Release 9.0. The options master and backup are introduced in Junos
OS Release 15.1X49-D50. | [
"Understanding Automatic Chassis Cluster Synchronization Between Primary and Secondary Nodes"
] | |
request system scripts add | request system scripts add <package-name>
<no-copy>
<unlink> | Use this command to install AI-Script (jais) packages on Juniper Networks devices. | [
{
"name": "no-copy",
"desc": "Don't save a copy of the jais package file. user@host> request system scripts add no-copy <package-name> If you use the no-copy option during the jais installation, the jais package cannot be rolled back."
},
{
"name": "unlink",
"desc": "Remove the package after suc... | maintenance | Command introduced before Junos OS Release 9.0. | [] | |
request system scripts convert | request system scripts convert (slax-to-xslt | xslt-to-slax) source source/filename destination destination/
<filename> <partial> <version (1.0 | 1.1)> | Convert an Extensible Stylesheet Language Transformations (XSLT) script to Stylesheet Language
Alternative syntaX (SLAX), or convert a SLAX script to XSLT. | [
{
"name": "destination",
"desc": ""
},
{
"name": "destination/",
"desc": ""
},
{
"name": "<filename>",
"desc": "Path and filename for the converted file. Optionally, you can specify a filename for the converted file. If you do not specify a filename, the software assigns one automati... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system scripts convert slax-to-xslt
user@host> request system scripts convert slax-to-xslt source /var/db/scripts/op/script1.slax
destination /var/db/scripts/op
conversion complete
req... | Command introduced in Junos OS Release 8.2.
partial and version options added in Junos OS Release 12.2. | [
"Converting Scripts Between SLAX and XSLT"
] | |
request system scripts delete | request system scripts delete <package-name> | (Junos OS only) Use this command to delete AI-Script (jais) packages on Juniper Networks devices. | [] | maintenance | Command introduced before Junos OS Release 9.0.
NOTE: This command is not supported on Junos OS Evolved. AI-Scripts and Service
Now are not supported on Junos OS Evolved. | [] | |
request system scripts event-scripts reload | request system scripts event-scripts reload | Reload all active SLAX and XSLT event scripts into the eventd process’ memory. This enables you to
replace or update an existing event script on the device and refresh the event policy embedded in the
script without changing the device’s configuration or disrupting operations. | [
{
"name": "reload",
"desc": "Reload all active SLAX and XSLT event-scripts."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system scripts event-scripts reload
user@host> request system scripts event-scripts reload
Event scripts loaded | Command introduced in Junos OS Release 9.0. | [
"Replace an Event Script"
] | |
request system scripts refresh-from | request system scripts refresh-from (commit | event | extension-service | op | snmp) file
filename url url cert-file path
<routing-instance routing-instance-name>
<sync> | Refresh a local script from a remote source at the specified URL. The system uses the script type to
determine the directory on the device where the script resides. If you include the sync option, the system
refreshes the script on the requesting Routing Engine and then synchronizes the script on the other
Routing Engi... | [
{
"name": "(commit | event |",
"desc": ""
},
{
"name": "extension-service | op",
"desc": ""
},
{
"name": "| snmp)",
"desc": "Specify in which scripts subdirectory the script resides: commit, event, jet, op, or snmp."
},
{
"name": "cert-file path",
"desc": "Absolute path t... | maintenance
Sample Output
request system scripts refresh-from
The following command refreshes the op script config.slax from the remote source at the specified URL.
user@host> request system scripts refresh-from op file config.slax url http://host1.juniper.net/
config.slax
config.slax 100% ... | Command introduced in Junos OS Release 10.1.
sync option introduced in Junos OS Release 13.2.
extension-service and routing-instance options introduced in Junos OS Release 18.1R1.
cert-file option introduced in Junos OS Release 21.2R1. | [
"Refreshing a Script from an Alternate Location",
"Example: Refreshing a Script from an Alternate Source",
"Example: Configuring and Refreshing from the Master Source for a Script",
"Synchronizing Scripts Between Routing Engines"
] | |
request system scripts rollback | request system scripts rollback | (Junos OS only) Use this command to roll back to most recent installation of AI-Scripts (jais) package. | [] | maintenance | Command introduced before Junos OS Release 9.0.
NOTE: This command is not supported on Junos OS Evolved. AI-Scripts and Service
Now are not supported on Junos OS Evolved. | [] | |
request system scripts synchronize | request system scripts synchronize (all | commit | event | jet | lib | op | snmp)
<file filename>
<newer-than YYYY-MM-DD.HH:MM:SS> | On dual Routing Engine devices, synchronize scripts from the requesting Routing Engine to the other
Routing Engine.
Specify all to synchronize all scripts present on the requesting Routing Engine to the responding
Routing Engine. Specify commit, event, jet, lib, op, or snmp to synchronize all scripts of the given type ... | [
{
"name": "(all | commit | event | jet | lib",
"desc": ""
},
{
"name": "| op | snmp)",
"desc": "Synchronize all scripts or all scripts of a given type that are present on the requesting Routing Engine to the responding Routing Engine."
},
{
"name": "file filename",
"desc": "(Optional... | maintenance
Sample Output
request system scripts synchronize all
The following command synchronizes all scripts from the requesting Routing Engine to the responding
Routing Engine.
user@host> request system scripts synchronize all
user@host>
request system scripts synchronize commit file
The following command synchron... | Command introduced in Junos OS Release 13.2. | [
"Synchronize Scripts Between Routing Engines"
] | |
request system services dhcp | request system services dhcp (release interface-name | renew interface-
name) | Release or renew the acquired IP address for a specific interface.
To view the status of the Dynamic Host Configuration Protocol (DHCP) clients on the specified
interfaces, enter the show system services dhcp client interface-name command. | [
{
"name": "release interface-name",
"desc": "Clears other resources received earlier from the server, and reinitializes the"
},
{
"name": "renew interface-name",
"desc": "Reacquires an IP address from the server for the interface. When you use this"
}
] | maintenance
Output Fields
This command produces no output. | Command introduced in Junos OS Release 8.5. | [] | |
request system snapshot (Junos OS Evolved) | request system snapshot
<configuration | no-configuration>
<routing-engine (both | local)> | On devices running Junos OS Evolved, take a “snapshot” of the files currently used to run the device and
copy the files onto the alternate solid-state drive (SSD). The snapshot contains the complete contents of
the /soft, /config, and /root directories, which include the current and all rollback software images,
copies... | [
{
"name": "none",
"desc": "Take a snapshot of the local Routing Engine."
},
{
"name": "configuration",
"desc": "Copy the /config directory and the configuration stored for each installed software version to the alternate SSD as part of the snapshot. This is the default."
},
{
"name": "no... | view
Output Fields
When you enter this command, the system provides feedback on the status of your request.
Sample Output
request system snapshot (Junos OS Evolved)
user@host> request system snapshot
-------------------------------
node: re0
-------------------------------
........
Starting Snapshot in device /dev/sdb
... | Command introduced in Junos OS Evolved Release 20.4R2.
routing-engine both and local options added in Junos OS Evolved Release 22.4R1.
configuration and no-configuration options added in Junos OS Evolved Release 23.4R1. | [
"Back up and Recover Software with Snapshots"
] | |
request system snapshot (Junos OS with FreeBSD Prior to Release 10) | request system snapshot
<all-chassis | all-lcc | lcc number | sfc number>
<config-partition>
<partition>
<root-partition> | •
On routers and firewalls running Junos OS, back up the currently running and active file system
partitions to standby partitions that are not running. Specifically, the root file system (/) is backed up
to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on the flash
drive, and ... | [
{
"name": "none",
"desc": "Back up the currently running software as follows: On the router or firewall, back up the currently running and active file system partitions to standby partitions that are not running. Specifically, the root file system (/) is backed up to /altroot, and /config is backed up to /... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system snapshot (Routers)
user@host> request system snapshot
umount: /altroot: not currently mounted
Copying / to /altroot.. (this may take a few minutes)
umount: /altconfig: not cur... | Command introduced before Junos OS Release 7.4.
Options <config-partition> and <root-partition> introduced in Junos OS Release 13.1 for M Series, MX
Series, T Series, and TX Series routers.
Option media usb-port-number introduced in Junos OS Release 13.2 for MX104 routers.
Options <config-partition>, <root-partition>, ... | [] | |
request system snapshot (Junos OS with Upgraded FreeBSD) | request system snapshot
<configuration>
<delete snapshot-name>
<load snapshot-name>
<media type>
<name snapshot-name>
<no-configuration>
<recovery> | Junos OS with upgraded FreeBSD has two types of snapshots:
•
Recovery snapshot
•
Non-recovery snapshot
Recovery snapshots—Use the request system snapshot recovery command to create a recovery snapshot.
The recovery snapshot contains copies of the packages and configuration taken at the time of the
snapshot. The recove... | [
{
"name": "none",
"desc": "On the router or switch, back up the currently running and active file system partitions to standby partitions that are not running. Specifically, this creates a non-recovery snapshot named snap.< date>.< time> which is stored in /packages/ sets."
},
{
"name": "configurati... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system snapshot recovery
user@host> request system snapshot recovery
Creating image ...
Compressing image . . .
Image size is 777MB
Recovery snapshot created successfully
request system ... | Command introduced in Junos OS Release 15.1.
Command introduced for all platforms using Junos OS with upgraded FreeBSD. To find which platforms
in which releases use Junos OS with upgraded FreeBSD, see Feature Explorer, enter freebsd, and select
Junos kernel upgrade to FreeBSD 10+.
configuration and no-configuration op... | [] | |
request system snapshot (Maintenance) | request system snapshot
<config-partition>
<media (compact-flash | hard-disk | internal | usb)>
<partition>
<root-partition>
<factory>
<node (all | local | node-id | primary)>
<slice (alternate) > | Use this command to back up the currently running and active file system partitions on the device. | [
{
"name": "config-partition",
"desc": "Creates a snapshot of the configuration partition only and stores it onto the"
},
{
"name": "root-partition",
"desc": "Creates a snapshot of the root partition only and stores it onto the default /altroot on"
},
{
"name": "factory",
"desc": "(Op... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system snapshot config-partition
user@host> request system snapshot config-partition
Doing the initial labeling...
Verifying compatibility of destination media partitions...
Running new... | Command introduced in Junos OS Release 10.2. | [] | |
request system software abort in-service-upgrade (ICU) | request system software abort in-service-upgrade | Use this command to terminate an in-band cluster upgrade (ICU).
This command must be issued from a router session other than the one on which you issued the request
system in-service-upgrade command that launched the ICU. If an ICU is in progress, this command
terminates it. If the node is being upgraded, this command ... | [] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software abort in-service-upgrade
user@host> request system software abort in-service-upgrade
In-Service-Upgrade aborted | Command introduced in Junos OS Release 15.1X49-D35. | [
"Upgrading Devices in a Chassis Cluster Using ICU"
] | |
request system software abort | request system software abort in-service-upgrade | Terminate a unified in-service software upgrade (ISSU). The unified ISSU must be in progress and you
must issue this command from a router session other than the one on which you issued the request system
in-service-upgrade command that launched the unified ISSU. | [] | view
Output Fields
When you enter the request system software abort command on a new router session, you are provided
feedback on the status of your request in the router session on which you issued the request system
software in-service-upgrade command.
Sample Output
request system software abort (New Router Session)
... | Command introduced in JUNOS Release 9.0. | [
"Getting Started with Unified In-Service Software Upgrade",
"Example: Performing a Unified ISSU"
] | |
request system software activate (Junos OS Evolved) | request system software activate with-old-snapshot-config version
<reboot> | Set the specified software version with its corresponding configuration as the next boot version. You can
activate any installed software version except the current version.
You can only activate a software version with the saved configuration corresponding to that version.
Alternatively, to use the active configuratio... | [
{
"name": "version",
"desc": "Software version to set as the next boot version."
},
{
"name": "with-old-snapshot-config",
"desc": "Use the configuration last saved for the specified software version."
},
{
"name": "reboot",
"desc": "(Optional) After activating the software version, r... | maintenance
Output Fields
When you enter this command, the system provides feedback on the status of your request.
Sample Output
request system software activate with-old-snapshot-config
user@host-re0> request system software activate with-old-snapshot-config junos-evo-install-ptx-
x86-64-25.4R1.8-EVO
Download and Val... | Command introduced in Junos OS Evolved Release 25.4R1. | [
"Stage and Activate Junos OS Evolved Software"
] | |
request system software add (Junos OS Evolved) | request system software add package-name
<force>
<no-confirm>
<reboot | restart>
<stage>
<allow-bundled-keys>
<validate | no-validate> | Install a software package on all Routing Engines in a cluster, as seen in the output of the show system
nodes operational mode command. The default option is validate. We recommend that you always
download the software image to /var/tmp only. For another way to validate the configuration before
trying to install the s... | [
{
"name": "package-name",
"desc": "Specify the location from which to download the software package or bundle. You can specify the location as either the URL of a remote location or the pathname of a local package. For example:"
},
{
"name": "/var/tmp/package-name",
"desc": "For a software packa... | maintenance
Output Fields
When you enter this command, the system provides feedback on the status of your request.
Sample Output
request system software add
user@host-re0> request system software add /var/tmp/ptxinstall.iso
Adding software images. This process can take several minutes. Please be patient...
Download and... | The following options are deprecated in Junos OS Evolved Release 18.3R1: best-effort-load, delay-restart,
no-copy, on-primary, (re0 | re1), set, unlink, validate, validate-on-host, and validate-on-routing-engine.
Support for jfirmware software packages introduced in Junos OS Evolved Release 24.4R1.
stage option introdu... | [] | |
request system software add (Junos OS) | request system software add package-name
<best-effort-load>
<delay-restart>
<force>
<force-host>
<no-copy>
<no-validate>
<reboot>
<unlink>
<upgrade-with-config>
<validate> | Install a software package or bundle on the device.
We recommend that you always download the software image to /var/tmp only. On EX Series and QFX
Series switches, you must use the /var/tmp directory. Other directories are not supported.
Starting in Junos OS Release 23.4R1 for MX Series routers, you can configure the ... | [
{
"name": "package-name",
"desc": "Location from which the software package or bundle is to be installed. package-name can be either the URL of a remote location or the pathname of a local package. For example:"
},
{
"name": "/var/tmp/package-name",
"desc": "For a software package or bundle that... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software add validate
user@host> request system software add validate /var/tmp/ jinstall-7.2R1.7-domestic-signed.tgz
Checking compatibility with configuration
Initializing...
Us... | Command introduced before Junos OS Release 7.4.
best-effort-load and unlink options added in Junos OS Release 7.4.
set [package-name1 package-name2] option added in Junos OS Release 11.1 for EX Series switches. Added in
Junos OS Release 12.2 for MX Series routers.
On EX Series switches, the set [package-name1 package-n... | [
"Format for Specifying Filenames and URLs in Junos OS CLI Commands",
"Installing Software Packages on QFX Series Devices (Junos OS)",
"Upgrading Software on a QFabric System",
"Managing Satellite Software Upgrade Groups in a Junos Fusion"
] | |
request system software add (Maintenance) | request system software add package-name | Use this command to install new software package on the device, for example: request system software
add junos-srxsme-10.0R2-domestic.tgz no-copy no-validate partition reboot. | [
{
"name": "delay–restart",
"desc": "Install the software package but does not restart the software process."
},
{
"name": "best-effort-load",
"desc": "Activate a partial load and treat parsing errors as warnings instead of errors."
},
{
"name": "no-copy",
"desc": "Install the softwar... | maintenance | Partition option introduced in the command in Junos OS Release 10.1. | [] | |
request system software add optional://auto-snapshot | request system software add optional://auto-snapshot | Activates the optional auto-snapshot package to generate a recovery snapshot after the next reboot.
Issue this command before you upgrade the software. Then, when the device reboots after the software
upgrade, the system automatically generates a recovery snapshot. Enabling auto-snapshot ensures a
recovery image for th... | [] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software add optional://auto-snapshot
user@host> request system software add optional://auto-snapshot
Verified auto-snapshot signed by PackageDevelopmentECP256_2022 method ECDSA25... | Command introduced in Junos OS Release 22.1R2. | [] | |
request system software add restart | request system software add package-name restart | Perform a unified in-service software upgrade (unified ISSU) to a more recent version of Junos OS
Evolved. A unified ISSU involves minimal disruption of the control plane and data plane traffic. The
software is upgraded by using an application-level restart or warm restart instead of a reboot, when
possible. Use the re... | [
{
"name": "package-name",
"desc": "Path and filename of the software package to be installed."
}
] | maintenance
Sample Output
request system software add restart
user@host> request system software add /var/home/regress/junos-evo-install-qfx-ms-
x86-64-22.1-202203012330.0-EVO.iso restart
Adding software images. This process can take several minutes. Please be patient...
Download and Validate in Progress
re0: Starting... | Command introduced in Junos OS Evolved Release 22.1R1. | [] | |
request system software configuration-backup | request system software configuration-backup (path) | Use this command to save the currently active configuration and any installation-specific parameters
such as a configuration that you have entered outside of the CLI, director group IP addresses, and the
default partition IP address. | [
{
"name": "path",
"desc": "(QFabric System) Provide the path to the location of the backup configuration files. You can save"
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy.
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software configuration-backup
user@switch ... | Command introduced in Junos OS Release 11.3. | [] | |
request system software configuration-restore | request system software configuration-restore (path) | Use this command to restore a previously saved configuration and any installation-specific parameters,
such as a configuration that you have entered outside of the CLI, director group IP addresses, and the
default partition IP address. | [
{
"name": "path",
"desc": "(QFabric System) Provide the path to the location of the backup configuration files. The path can"
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy.
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software configuration-restore
user@switch ... | Command introduced in Junos OS Release 11.3. | [
"Performing a QFabric System Recovery Installation on the Director Group"
] | |
request system software delete (Junos OS Evolved) | request system software delete
<force>
<package-name>
<archived>
<all-third-party-packages> | Use this command to remove a software package from the device, as long as it is not the software
version currently running on the system. The force option is required if the requested version is the
rollback version.
CAUTION: Before removing a software package, make sure that you have already placed
the new software p... | [
{
"name": "package-name",
"desc": "Name of the Junos OS Evolved package running on the device. Type the package-name explicitly and do not use the tab key to auto-complete the command. You can see this package name by issuing the show system software list operational mode command."
},
{
"name": "all... | maintenance
Output Fields
When you enter this command, the system provides feedback on the status of your request.
Sample Output
request system software delete (Junos OS Evolved)
user@host> request system software delete junos-evo-install-qfx-fixed-
x86-64-18.3I20180911102422
Removing version 'junos-evo-install-qfx-f... | all-third-party-packages option introduced in Junos OS Evolved Release 19.4R2.
archived option added in Junos OS Evolved Release 20.4R2.
Support for deleting jfirmware packages introduced in Junos OS Evolved Release 24.4R1. | [] | |
request system software delete (Junos OS) | request system software delete
<upgrade-group [all |upgrade-group-name]>
<version version-string> | Use this command to remove a software package or bundle from the device.
CAUTION: Before removing a software package or bundle, make sure that you have
already placed the new software package or bundle that you intend to load onto the
device. | [
{
"name": "software-package",
"desc": "Software package or bundle name. You can see this software package name by using the show system software command. Type the software package name explicitly and do not use the tab key to auto-complete the command. You can delete any or all of the following software bun... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software delete jdocs
The following example displays the system software packages before and after the jdocs package is
deleted through the request system software delete command:... | Command introduced before Junos OS Release 7.4.
set [package-name package-name] option added in Junos OS Release 12.2.
reboot option introduced in Junos OS Release 12.3.
upgrade-group and version options introduced in Junos OS Release 14.2R3 for Junos Fusion. | [
"Managing Satellite Software Upgrade Groups in a Junos Fusion"
] | |
request system software delete-backup | request system software delete-backup | (Junos OS only) Use this command to delete the backup image previously created. Junos OS keeps a
backup image of the software that was previously installed so that you can downgrade to that version of
the software if necessary. If you delete this image, you cannot downgrade to the particular version of
the software. No... | [] | maintenance
Output Fields
Sample Output
request system software system-backup
user@host> request system software delete-backup
Delete backup system software package [yes,no] | Command introduced in Junos OS Release 9.6R1. | [] | |
request system software download | request system software download path/package-name | Use this command to download a software package from a location on the director device, mounted
external USB flash drive, remote FTP or SCP location, or other location. | [
{
"name": "path",
"desc": "Location where the software package is located. For example:"
},
{
"name": "/pbdata/packages/package-name",
"desc": "For a software package that is being installed from a local"
},
{
"name": "protocol://hostname/pathname/package-name",
"desc": "For a softwa... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software download
user@switch> request system software download ftp://ftp.install-directory/jinstall-
qfabric-11.3X30.6.rpm
% Total % Received % Xferd Average Speed Time ... | Command introduced in Junos OS Release 11.3. | [
"Installing Software Packages on QFX Series Devices"
] | |
request system software format-qfabric-backup | request system software format-qfabric-backup | (QFabric systems only) Copy the install media files from a USB flash drive to your QFabric system
recovery directory on the Director group. You must issue this command before you can use the request
system software system-backup and request system software system-backup copy-to-usb commands. | [
{
"name": "none",
"desc": "Copy the install media files from a USB flash drive to a Director group recovery directory."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software format-qfabric-backup
user@qfabric> request system software format-qfabric-backup
Copying QFabric USB template image from /dev/sdb(Unigen,PQS4000,4009 MB)...... | Command introduced in Junos OS Release 13.1. | [
"Performing System Backup and Recovery for a QFabric System",
"Performing a QFabric System Recovery Installation on the Director Group"
] | |
request system software in-service-upgrade (Maintenance) | request system software in-service-upgrade image_name
<no-copy>
<no-old-master-upgrade>
<no-sync>
<no-tcp-syn-check>
<no-validate>
<status>
<unlink> | The in-service software upgrade (ISSU) feature allows a chassis cluster pair to be upgraded from
supported Junos OS versions with a traffic impact similar to that of redundancy group failovers. Before
upgrading, you must perform failovers so that all redundancy groups are active on only one device. We
recommend that gr... | [
{
"name": "image_name",
"desc": "Specify the location and name of the software upgrade package to be installed."
},
{
"name": "no-copy",
"desc": "(Optional) Install the software upgrade package but do not save the copies of package files."
},
{
"name": "no-old-master-upgrade",
"desc"... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software in-service-upgrade status (SRX1500, SRX4100, SRX4200, SRX4600,
SRX5400, SRX5600, and SRX5800)
user@host> request system software in-service-upgrade status
[Apr 29 01:31:1... | For SRX5400, SRX5600, and SRX5800 devices, command introduced in Junos OS Release 9.6. For
SRX5400 devices, the command is introduced in Junos OS Release 12.1X46-D20. For SRX300, SRX320,
SRX340, and SRX345 devices, command introduced in Junos OS Release 15.1X49-D40. For SRX1500
devices, command introduced in Junos OS ... | [
"request system software rollback (SRX Series)",
"request system software in-service-upgrade (MX Series 5G Universal"
] | |
Routing Platforms and EX9200 Switches) | request system software in-service-upgrade package-name
<no-copy>
<no-old-master-upgrade>
<reboot>
<unlink> | Perform a unified in-service software upgrade (unified ISSU). Unified ISSU enables you to upgrade from
one Junos OS release to another with no disruption on the control plane and with minimal disruption of
traffic. Unified ISSU is supported only by dual Routing Engine platforms. In addition, graceful Routing
Engine swi... | [
{
"name": "package-name",
"desc": "Location from which the software package or bundle is to be installed. For example:"
},
{
"name": "/var/tmp/package-name",
"desc": "For a software package or bundle that is being installed"
},
{
"name": "protocol://hostname/pathname/package-name",
"... | view
Output Fields
When you enter this command, you are provided feedback about the status of your request.
Sample Output
request system software in-service-upgrade reboot
{master}
user@host> request system software in-service-upgrade /var/tmp/jinstall-11.2B2.1-domestic-
signed.tgz reboot
Chassis ISSU Check Done
ISSU:... | Command introduced in Junos OS Release 11.2. | [] | |
request system software in-service-upgrade | Syntax (QFX Series)
request system software in-service-upgrade package-name | Perform a unified in-service software upgrade (ISSU). A unified ISSU enables you to upgrade from one
Junos OS release to another with no disruption on the control plane and with minimal disruption of
traffic.
On QFX5100 and QFX5200 switches, enable nonstop active routing (NSR) and nonstop bridging (NSB). | [
{
"name": "package-name",
"desc": "Location from which the software package or bundle is to be installed. For example:"
},
{
"name": "/var/tmp/package-name",
"desc": "For a software package or bundle that is being installed from"
},
{
"name": "protocol://hostname/pathname/package-name",
... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software in-service-upgrade reboot
{master}
user@host> request system software in-service-upgrade /var/tmp/jinstall-9.0-20080114.2-domestic-signed.tgz
reboot
ISSU: Validating Image
PIC... | Command introduced in Junos OS Release 9.0.
status option introduced in Junos OS Release 19.4R1 for MX240, MX480, MX960, MX2010, MX2020,
PTX3000, and PTX5000 devices.
handle-incompatible-config option introduced in Junos OS Release 22.1R1 for MX960, MX10003,
MX10008, MX10016, MX2010, and MX2020 devices.
enhanced-mode o... | [
"Getting Started with Unified In-Service Software Upgrade",
"Performing an In-Service Software Upgrade (ISSU) with Non-Stop Routing",
"Example: Performing a Unified ISSU"
] | |
request system software nonstop-upgrade (QFabric Systems) | request system software nonstop-upgrade package-name
<fabric >
<director-group>
<node-group name> | Nonstop software upgrade enables you to upgrade a QFabric system with minimal packet loss and
maximum uptime. You should upgrade the devices in the following order: Director group, fabric controls
and Interconnect devices, and network and server Node groups.
NOTE: Before you perform a nonstop software upgrade, contact... | [
{
"name": "package-name",
"desc": "Location from which the software is to be installed. For example:"
},
{
"name": "protocol://hostname/pathname/package-name",
"desc": "For a software package or bundle that"
},
{
"name": "the following:",
"desc": ""
},
{
"name": "ftp",
"d... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software nonstop-upgrade director-group
user@qfabric> request system software nonstop-upgrade director-group jinstall-qfabric-12.2X50-
D10.3.rpm
Validating update package jinstal... | Command introduced in Junos OS Release 12.2. | [
"Nonstop Software Upgrade Checklist for QFabric Systems",
"Performing a Nonstop Software Upgrade on the QFabric System",
"Verifying Nonstop Software Upgrade for QFabric Systems"
] | |
request system software nonstop-upgrade | request system software nonstop-upgrade (package-name | set [package-name package-name])
<force-host>
<no-copy>
<no-old-master-upgrade>
<reboot >
<unlink>
<update-firmware> | Perform a nonstop software upgrade (NSSU) on a switch with redundant Routing Engines or on a Virtual
Chassis or Virtual Chassis Fabric (VCF). The behavior of this command depends on the type of switch,
Virtual Chassis, or VCF where you run it, as follows:
•
When you run this command on any of the following Virtual Cha... | [
{
"name": "package-name",
"desc": "Location of the software package or bundle to be installed. For example:"
},
{
"name": "/var/tmp/package-name",
"desc": "For a software package or bundle installed from a local directory"
},
{
"name": "protocol://hostname/pathname/package-name",
"de... | maintenance
Output Fields
This command reports feedback on the status of the request. Some functions are shared between NSSU
and the in-service software upgrade (ISSU) feature, so you might see what appear to be ISSU messages
as well as NSSU messages in the output from this command.
Sample Output
request system softwa... | Command introduced in Junos OS Release 10.4.
Option set [package-name package-name] added in Junos OS Release 12.1 for EX Series switches.
Option update-firmware added in Junos OS Release 25.4R1. | [
"Upgrading Software on an EX6200 or EX8200 Standalone Switch Using Nonstop Software Upgrade",
"(CLI Procedure)",
"Upgrading Software on an EX8200 Virtual Chassis Using Nonstop Software Upgrade (CLI Procedure)",
"Upgrading Software on a Virtual Chassis and Mixed Virtual Chassis Using Nonstop Software Upgrade",... | |
request system software recover-from-restore-point | request system software recover-from-restore-point | Use to command to rollback to a previously created restore-point.
Rolling back to a previously created restore-point might disrupt traffic, as both Director devices reboot
from the restore-point partition. | [] | configure
Sample Output
request system software recover-from-restore-point
root@qfabric> request system software recover-from-restore-point
Start Restore
Checking if the restore-point exists
LogVol00 has the root filesystem
Found Restore-Point: Fri Aug 15 07:42:39 UTC 2014 /dev/VolGroup00/LogVol03
Mountin... | Command introduced in Junos OS Release 14.1X53-D15. | [] | |
request system software recovery-package | request system software recovery-package ( add package-name | delete package-name | extract (ex-
xre200-package | ex-8200-package) package-name)
<backup>
<master> | Add, remove, or extract a software recovery package for the EX8200 switch or the XRE200 External
Routing Engine in an EX8200 Virtual Chassis.
Use this command to load a software recovery package onto the USB flash drive of the external Routing
Engine and then extract it to the recovery partition of the external Routing... | [
{
"name": "add package-name backup |",
"desc": ""
},
{
"name": "master",
"desc": "Load the EX8200 software recovery package or the XRE200 software recovery package onto the USB flash drive of the external Routing Engine. NOTE: You can have up to five software recovery packages loaded in the USB ... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software recovery-package add
user@external-routing-engine> request system software recovery-package add /tftpboot/jinstall-ex-
xre200-11.1I20110608_1356_pravasp-domestic.tgz
...-... | Command introduced in Junos OS Release 12.2. | [] | |
request system software restore-point | request system software restore-point | Use this command to create a restore-point. A restore-point is a snapshot of the software on the
QFabric system as well as the configuration that can be rolled back to in cases where a software upgrade
or configuration changes have made the QFabric system unstable or inoperable. | [] | configure
Sample Output
request system software restore-point
root@qfabric> request system software restore-point
Checking if director-device upgrade is currently in progress.
Checking VM status.
Checking for communication between director devices.
Checking inventory status of all components.
Checking Server INE passwo... | Command introduced in Junos OS Release 14.1X53-D15. | [] | |
request system software rollback (Junos OS Evolved) | request system software rollback reboot
<no-validate>
<package-name version>
<with-old-snapshot-config> | Use this command to revert to the last successfully installed package before the last-issued request system
software (add | delete) command. By default, once the software is rolled back, the device uses the current
configuration file. You can use this command on either Routing Engine in a dual-Routing Engine system.
On... | [
{
"name": "package-name version",
"desc": "Select any installed version for the rollback. The request system software rollback operational mode command uses the version instead of the package-name. You can see the available versions by using the show system software list operational mode command. If you do ... | maintenance
Output Fields
When you enter this command, the system provides feedback on the status of your request.
Sample Output
request system software rollback with-old-snapshot-config
user@host> request system software rollback junos-evo-install-ptx-x86-64-20.4-202103141559.0
with-old-snapshot-config
Starting softw... | validate and no-validate options introduced for Junos OS Evolved Release 18.3R1.
package-name version option introduced for Junos OS Evolved Release 18.3R1.
with-old-snapshot-config option introduced for Junos OS Evolved Release 18.3R1. | [] | |
request system software rollback (Junos OS) | request system software rollback <node-id> | Use this command to revert to the last successfully installed package before the request system software
(add | delete) command. It uses the copy stored in the /var/sw/pkg directory.
Additional Information
•
On Junos Fusion, the request system software rollback command can be used to roll back the version of
satellite ... | [
{
"name": "all-members",
"desc": "(EX4200 switches and MX Series routers only) (Optional) Attempt to roll back to the previous set of packages on all members of the Virtual Chassis configuration."
},
{
"name": "device-alias",
"desc": ""
},
{
"name": "alias-name",
"desc": "(Junos Fusi... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software rollback
user@host> request system software rollback
Verified SHA1 checksum of ./jbase-7.2R1.7.tgz
Verified SHA1 checksum of ./jdocs-7.2R1.7.tgz
Verified SHA1 checksum o... | Command introduced before Junos OS Release 7.4.
reboot option introduced in Junos OS Release 12.3.
device-alias, satellite, and upgrade-group options introduced in Junos OS Release 14.2R3 for Junos Fusion.
force option deprecated in Junos OS Release 15.1 for Junos OS with Upgraded FreeBSD.
To find which platforms in wh... | [] | |
request system software stage (Junos OS Evolved) | request system software stage version | Validate the active configuration against an installed software version and copy the validated
configuration to the /data directory associated with that software version. If the validation fails, the
system returns the validation errors and does not copy the configuration.
If you run the command against an activated so... | [
{
"name": "version",
"desc": "Software version that is already installed on the device."
}
] | maintenance
Output Fields
When you enter this command, the system provides feedback on the status of your request.
Sample Output
request system software stage
user@host-re0> request system software stage junos-evo-install-ptx-x86-64-25.4R1.8-EVO
Software staging in progress...
re0: Validating current config for staged... | Command introduced in Junos OS Evolved Release 25.4R1. | [
"Stage and Activate Junos OS Evolved Software"
] | |
request system software sync | request system software sync (current | rollback | all-versions) | Use this command on the primary Routing Engine of a system to synchronize the software and
configurations from the primary Routing Engine to the other nodes and reboot the other nodes. The
configurations are synchronized even if the images are identical. If specified on the backup Routing
Engine, the command fails. Thi... | [
{
"name": "current |",
"desc": ""
},
{
"name": "rollback |",
"desc": ""
},
{
"name": "all-versions",
"desc": "Specify which software version (current, rollback, or all versions) to sync to the other node: For the current option, the system syncs the current version from the primary ... | view
Sample Output
request system software sync current
user@host-re0> request system software sync current
warning: Erase software versions present on the other RE node and sync software versions from
Master RE node
Erase software versions on the other RE and sync from Master RE? [yes,no] (no) yes
The current version... | Command introduced in Junos OS Evolved Release 18.3R1. | [] | |
request system software system-backup | request system software system-backup
<usb-create> | (QFabric systems only) Save a copy of the current QFabric system configuration file and the current
software package for recovery purposes. You can use these saved files to restore your QFabric system to
full operation after a system failure or shutdown. | [
{
"name": "none",
"desc": "Copy the QFabric system software package and system configuration file to a Director group recovery directory. NOTE: If this command fails, insert a Juniper Networks software installation USB flash drive into the primary Director device and issue the request system software format... | maintenance
Output Fields
When you enter these commands, you are provided feedback on the status of your request.
Sample Output
request system software system-backup
user@qfabric> request system software system-backup
user@qfabric>
request system software system-backup usb-create
user@qfabric> request system software ... | Command introduced in Junos OS Release 13.1. | [
"Performing System Backup and Recovery for a QFabric System",
"request system software configuration-backup",
"Performing a QFabric System Recovery Installation on the Director Group"
] | |
request system software validate (Junos OS Evolved) | request system software validate package-name
<restart> | Use this command to validate the candidate software package against the current configuration of the
node. The configuration check does not change the current software or the file system.
You can use the request system software validate command before using the request system software add
restart command to determine i... | [
{
"name": "package-name",
"desc": "Specify the location from which to download the software package or bundle. You can specify the location as either the URL of a remote location or the pathname of a local package. For example:"
},
{
"name": "/var/tmp/package-name",
"desc": "For a software packa... | maintenance
Output Fields
When you enter this command, the system provides feedback on the status of your request.
Sample Output
request system software validate /var/tmp/package-name
user@host-re0> request system software validate /var/tmp/ptxinstall.iso
Validating software image /var/tmp/ptxinstall.iso...
Download an... | restart option added in Junos OS Evolved Release 18.3R1. | [] | |
request system software validate (Junos OS) | request system software validate <package-name>
<member member-id>
<on (host host <username username> | routing-engine routing-engine)>
<set [package-name package-name]>
<upgrade-with-config>
<upgrade-with-config-format format> | Use this command to validate candidate software against the current configuration of the router, the
switch, or a remote host. | [
{
"name": "lcc number",
"desc": "(TX Matrix routers and TX Matrix Plus routers only) (Optional) On a TX Matrix router, validate the software bundle or package on a specific T640 router (or line-card chassis) that is connected to the TX Matrix router. On a TX Matrix Plus router, validate the software bundle ... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software validate (Successful Case)
user@host> request system software validate /var/sw/pkg/
jbundle-5.3I20020124_0520_sjg.tgz
Checking compatibility with configurat... | Command introduced before Junos OS Release 7.4.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
set [package-namepackage-name] option added in Junos OS Release 12.2 for M Series, MX Series, T Series
routers.
upgrade-with-config and upgrade-with-config-format format options added in Junos OS... | [
"Routing Matrix with a TX Matrix Plus Router Solutions Page"
] | |
request system software validate in-service-upgrade | request system software validate in-service-upgrade package-name
<enhanced-mode> | Perform a compatibility check to ensure that the software and hardware components and the
configuration on the device support unified ISSU. The request system software validate in-service-upgrade
command enables you to detect any compatibility issues before actually issuing the request system
software in-service-upgrad... | [
{
"name": "package-name",
"desc": "Location from which the software package or bundle is to be installed. For example:"
},
{
"name": "/var/tmp/package-name",
"desc": "For a software package or bundle that is being installed from a"
},
{
"name": "protocol://hostname/pathname/package-name"... | view
Output Fields
When you enter this command, Junos OS displays the status of your request.
Sample Output
request system software validate in-service-upgrade
{master}
user@host> request system software validate in-service-upgrade /var/tmp/jinstall-9.0-20080114.2-domestic-
signed.tgz reboot
Checking compatibility with... | Command introduced in Junos OS Release 9.6. | [
"Getting Started with Unified In-Service Software Upgrade",
"Example: Performing a Unified ISSU"
] | |
request system software validate on (Junos OS with Upgraded FreeBSD) | request system software validate on
<host host-name [ username user-name ]>
<routing-engine (re0 | re1)> | Use this command to validate the current configuration on a Routing Engine that is not running Junos
OS with upgraded FreeBSD or a remote host.
Direct validation of a running configuration is not possible on a device running Junos OS with upgraded
FreeBSD. Nevertheless, validation is an important step in the installati... | [
{
"name": "host host-name",
"desc": ""
},
{
"name": "[ username user-name ]",
"desc": "Validate the current configuration on a remote host. The host-name is resolved through DNS. Optionally, you can supply a username to employ on the remote host. If you omit the username option, the currently lo... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software validate on host
user@host> request system software validate on host remote-validator
The authenticity of host 'remote-validator (192.168.164.174)' can't be established.
... | Command introduced in Junos OS Release 15.1 for supported platforms. See Feature Explorer. | [
"Release Information for Junos OS with Upgraded FreeBSD"
] | |
request system software validate-restart (Junos OS Evolved) | request system software validate-restart package-name | Verify the new package against the current configuration to ensure that it supports unified in-service
software upgrade (unified ISSU). The command output also indicates which applications can be
upgraded by using an application-level restart or an in-service kernel warm restart. Use this command
before you run request... | [
{
"name": "package-name",
"desc": "Specify the location from which to download the software package or bundle. You can specify the location as either the URL of a remote location or the pathname of a local package. For example:"
},
{
"name": "/var/tmp/package-name",
"desc": "For a software packa... | maintenance
Sample Output
request system software validate-restart
user@host> request system software validate-restart /var/home/regress/junos-evo-install-qfx-ms-
x86-64-22.2-202203012330.0-EVO.iso
Validating software image and getting ISSU services impact /var/home/regress/junos-evo-install-
qfx-ms-x86-64-22.1-202203... | Command introduced in Junos OS Evolved Release 22.1R1. | [] | |
request system storage cleanup (Junos OS Evolved) | request system storage cleanup (dry-run | force-deep | no-confirm) | Use this command to free storage space on the router or switch by rotating log files and proposing a list
of files for deletion.
The Junos OS Evolved implementation of the request system storage cleanup command is slightly different
from the implementation on Junos OS:
•
The system prompts you to specify the dry-run op... | [
{
"name": "dry-run",
"desc": "(Prompted if not specified) List the files proposed for deletion (without deleting the files)."
},
{
"name": "force-deep",
"desc": "(Optional) Deep clean all temporary files and rotate logs. This option cleans up all the user-created files under the /tmp and /var/tm... | maintenance
Sample Output
request system storage cleanup (Junos OS Evolved)
user@host-re0> request system storage cleanup
Please check the list of files to be deleted using the dry-run option.
Continue anyway without checking? [yes,no] (no) yes
-------------------------------
node: fpc0
---------------------------... | Command introduced in Junos OS Evolved Release 20.4R2. | [] | |
request system storage cleanup (Junos OS) | request system storage cleanup
<dry-run>
<no-confirm>
<re0 | re1 | routing-engine (backup | both | local | master | other)> | Use this command to free storage space on the router or switch by rotating log files and proposing a list
of files for deletion. On a QFabric system, you can delete debug files located on individual devices or on
the entire QFabric system. | [
{
"name": "all-members",
"desc": "(EX4200 switches and MX Series routers only) (Optional) Delete files on the Virtual Chassis primary Routing Engine only. To delete files on the other members of the Virtual Chassis configuration, log in to each backup Routing Engine and delete the files using the request sy... | maintenance
Output Fields
Table 150 on page 15965 describes the output fields for the request system storage cleanup command.
Output fields are listed in the approximate order in which they appear.
Table 150: request system storage cleanup Output Fields
Field Name
Field Description
List of files to delete:
Shows list o... | Command introduced in Junos OS Release 7.4.
dry-run option introduced in Junos OS Release 7.6.
satellite option introduced in Junos OS Release 14.2R3.
no-confirm and (re0 |re1 | routing-engine (backup | both | local | master | other)) options introduced in
Junos OS 17.3R1. | [] | |
request system storage cleanup (SRX Series) | request system storage cleanup <dry-run> | Use this command to free storage space on the device by rotating log files and proposing a list of files
for deletion. | [
{
"name": "dry-run",
"desc": "(Optional) List files proposed for deletion (without deleting them). Additional Information If logging is configured and being used, the dry-run option rotates the log files. In that case, the output displays the message “Currently rotating log files, please wait.” If no loggin... | maintenance
Output Fields
Table 151 on page 15977 describes the output fields for the request system storage cleanup command.
Output fields are listed in the approximate order in which they appear.
Table 151: request system storage cleanup Output Fields
Field Name
Field Description
List of files to delete:
Shows list o... | Command introduced in Junos OS Release 9.2. | [
"Cleaning Up Files with the CLI"
] | |
request system yang add | request system yang add package package-name module [modules]
<action-script [scripts]>
<translation-script [scripts]>
<deviation-module [modules]>
<proxy-xml>
<snmp> | Define a new YANG package with the modules, deviation modules, and scripts that are added to the
device as part of the package, and merge the data models defined in the modules with the Junos OS
schema. When you add a custom YANG data model to the device, you must also add at least one
translation script or one action ... | [
{
"name": "action-script",
"desc": ""
},
{
"name": "[scripts]",
"desc": "List of paths for one or more action scripts to add to the device as part of the package."
},
{
"name": "module",
"desc": ""
},
{
"name": "[modules]",
"desc": "List of paths for one or more YANG modu... | maintenance
Sample Output
request system yang add
user@host> request system yang add package p1 module [yang/if.yang yang/if-aggregate.yang
yang/if-show.yang] deviation-module yang/deviation/if-devs.yang translation-script translation/
if.slax action-script action/if-show.py
YANG modules validation : START
YANG modul... | Command introduced in Junos OS Release 16.1R1.
proxy-xml option introduced in Junos OS Release 17.3R1 on MX Series and PTX Series routers.
snmp option introduced in Junos OS Release 18.3R1. | [
"Managing YANG Packages, Modules, and Scripts on Devices Running Junos OS",
"Understanding the Management of Nonnative YANG Modules on Devices Running Junos OS",
"Configure a NETCONF Proxy Telemetry Sensor in Junos",
"Customized SNMP MIBs for Syslog Traps"
] | |
request system yang delete | request system yang delete package-name | Remove the given YANG package and all of its modules and scripts from the device, and remove the
data models associated with that package from the Junos OS schema.
CAUTION: Before you delete a YANG package, ensure that the active configuration
does not contain configuration data that has dependencies on the data models... | [
{
"name": "package-name",
"desc": "Name of the YANG package to remove."
}
] | maintenance
Sample Output
request system yang delete
user@host> request system yang delete p1
Building schema and reloading /config/juniper.conf.gz ...
Activating /config/juniper.conf.gz ...
mgd: commit complete
Restarting mgd ...
WARNING: cli has been replaced by an updated version:
CLI release 16.1R1 built by builde... | Command introduced in Junos OS Release 16.1R1. | [
"Managing YANG Packages, Modules, and Scripts on Devices Running Junos OS",
"Understanding the Management of Nonnative YANG Modules on Devices Running Junos OS"
] | |
request system yang disable | request system yang disable package-name | Disable the translation scripts associated with the given YANG package.
Translation scripts convert configuration data corresponding to YANG data models into Junos OS syntax
and add the translated configuration data as a transient change in the checkout configuration during the
commit operation. Translation scripts are... | [
{
"name": "package-name",
"desc": "Name of the YANG package for which to disable translation."
}
] | maintenance
Sample Output
request system yang disable
user@host> request system yang disable p1
user@host> | Command introduced in Junos OS Release 16.1R1. | [
"Disabling and Enabling YANG Translation Scripts on Devices Running Junos OS",
"Creating Translation Scripts for YANG Configuration Models"
] | |
request system yang enable | request system yang enable package-name | Enable the translation scripts associated with the given YANG package.
Translation scripts convert configuration data corresponding to YANG data models into Junos OS syntax
and add the translated configuration data as a transient change in the checkout configuration during the
commit operation. Translation scripts are ... | [
{
"name": "package-name",
"desc": "Name of the YANG package for which to enable translation."
}
] | maintenance
Sample Output
request system yang enable
user@host> request system yang enable p1
user@host> | Command introduced in Junos OS Release 16.1R1. | [
"Disabling and Enabling YANG Translation Scripts on Devices Running Junos OS",
"Creating Translation Scripts for YANG Configuration Models"
] | |
request system yang update | request system yang update package-name action-script [scripts] deviation-module [modules]
module [modules] proxy-xml [file-path-names] translation-script [scripts] | Update an existing YANG package to include new or modified YANG modules or scripts, and merge the
updated data models in that package with the Junos OS schema.
When you update a package, the device stores copies of the new and modified module and script files.
Junos OS then rebuilds its schema to include the changes to... | [
{
"name": "package-name",
"desc": "Name of the YANG package to update."
},
{
"name": "action-script [scripts]",
"desc": "List of paths for one or more action scripts to add to or update in the package."
},
{
"name": "deviation-module",
"desc": ""
},
{
"name": "[modules]",
... | maintenance
Sample Output
request system yang update
user@host> request system yang update p1 module yang/if.yang
YANG modules validation : START
YANG modules validation : SUCCESS
TLV generation: START
TLV generation: SUCCESS
Building schema and reloading /config/juniper.conf.gz ...
Activating /config/juniper.conf.gz .... | Command introduced in Junos OS Release 16.1R1.
proxy-xml option introduced in Junos OS Release 17.3R1 on MX Series and PTX Series routers. | [
"Managing YANG Packages, Modules, and Scripts on Devices Running Junos OS",
"Configure a NETCONF Proxy Telemetry Sensor in Junos"
] | |
request system yang validate | request system yang validate action-script [scripts] module [modules] proxy-xml module [modules]
translation-script [scripts] | Validate the syntax of one or more YANG modules, translation scripts, or action scripts. | [
{
"name": "action-script scripts",
"desc": "List of paths for one or more action scripts to validate."
},
{
"name": "module modules",
"desc": "List of paths for one or more YANG modules to validate."
},
{
"name": "proxy-xml module",
"desc": ""
},
{
"name": "modules",
"des... | maintenance
Sample Output
request system yang validate
user@host> request system yang validate module [yang/if.yang yang/if-aggregate.yang] translation-
script translation/if.slax
YANG modules validation : START
YANG modules validation : SUCCESS
Scripts syntax validation : START
script check succeeds
Scripts syntax val... | Command introduced in Junos OS Release 16.1R1.
proxy-xml option introduced in Junos OS Release 17.3R1 on MX Series and PTX Series routers. | [
"Managing YANG Packages, Modules, and Scripts on Devices Running Junos OS",
"Understanding the Management of Nonnative YANG Modules on Devices Running Junos OS",
"Configure a NETCONF Proxy Telemetry Sensor in Junos"
] | |
request system zeroize (Junos OS Evolved) | request system zeroize <(disk1 | disk2)> | Use this command to sanitize the disks on a Routing Engine, to make it difficult to access data on the
disks, using various levels of sanitization corresponding to degrees of difficulty, as defined in the NIST
800-88 standard. If the device has two Routing Engines, the command is broadcast to both Routing
Engines on th... | [
{
"name": "(disk1 |",
"desc": ""
},
{
"name": "disk2)",
"desc": "(For Routing Engines that contain two disks only. For Routing Engines that contain only one disk, the (disk1|disk2) option does not apply.) The disk1 and disk2 options refer to the absolute disk; that is, to the primary disk and to... | maintenance
Sample Output
request system zeroize
user@host> request system zeroize
warning: System will be rebooted and may not boot without configuration
Erase all data, including configuration and log files?. In case of Dual RE system, both Routing
Engines will be zeroized [yes,no] (yes)
Example: Console logs for S... | Command introduced in Junos OS Evolved Release 18.3R1.
Secure erase capability according to the NIST 800-88 standard introduced in Junos OS Evolved Release
21.3R1.
disk1 and disk2 options introduced in Junos OS Evolved Release 23.4R1.
Support for NIST PURGE capability for SATA drives introduced in Junos OS Evolved 24.4... | [
"NIST Special Publication 800-88, Guidelines for Media Sanitization"
] | |
request system zeroize (Junos OS) | request system zeroize
<media>
<local> | Use this command to remove all configuration information on the Routing Engines and reset all key
values on the device where you run the command.
•
If the device has dual Routing Engines, the command is broadcast to all Routing Engines on the
device. As a result, both Routing Engines are zeroized.
•
In a Virtual Chassi... | [
{
"name": "media",
"desc": "(Optional) In addition to removing all configuration and log files, causes memory and the media to be scrubbed, removing all traces of any user-created files. Every storage device attached to the system is scrubbed, including disks, flash drives, removable USBs, and so on. The du... | maintenance
Sample Output
request system zeroize
user@host> request system zeroize
warning: System will be rebooted and may not boot without configuration
Erase all data, including configuration and log files?. In case of Dual RE system, both Routing
Engines will be zeroized [yes,no] (no) yes
0 1 1 0 0 0 done
syncing ... | Command introduced before Junos OS Release 9.0.
Option media added in Junos OS Release 11.4 for EX Series switches.
Option local added in Junos OS Release 14.1. | [
"Reverting to the Default Factory Configuration for the EX Series Switch",
"Reverting to the Rescue Configuration for the EX Series Switch",
"Reverting to the Default Factory Configuration",
"Reverting to the Rescue Configuration",
"Reverting to the Default Factory Configuration by Using the request system ... | |
request system zeroize ztp-option secure | request system zeroize ztp-option secure-(enable | disable) | On secure devices, you can switch between using secure zero-touch provisioning (SZTP) and zero-touch
provisioning (ZTP). | [
{
"name": "enable",
"desc": "The CLI checks to see if the device is a secure device. If the device is secure, the process ends. The next time the device boots, the device uses secure ZTP as the provisioning solution. If the device is not a secure device, you will receive an error message that says the devic... | maintenance
Sample Output
request system zeroize ztp-option secure-enable
user@device> request system zeroize ztp-option secure-enable
request system zeroize ztp-option secure-disable
user@device> request system zeroize ztp-option secure-disable | Command introduced in Junos OS Evolved Release 23.2. | [
"Switching between Secure Zero Touch Provisioning and Zero Touch Provisioning"
] | |
request system zeroize | request system zeroize <media> | Use this command to remove all configuration information and resets all key values. The command
removes all data files, including customized configuration and log files, by unlinking the files from their
directories. If the device has two Routing Engines, the command is broadcast to both Routing Engines on
the device. ... | [
{
"name": "media",
"desc": "(Optional) In addition to removing all configuration and log files, the media option causes memory and the media to be scrubbed, removing all traces of any user-created files. Every storage device attached to the system is scrubbed, including disks, flash drives, removable USBs, ... | Not applicable.
Sample Output
request system zeroize
user@host> request system zeroize
warning: System will be rebooted and may not boot without configuration
Erase all data, including configuration and log files?. In case of Dual RE system, both Routing
Engines will be zeroized [yes,no] (no) yes
warning: ze... | [
"request system software rollback (SRX Series)"
] | ||
request unified-edge tdf call-trace clear | request unified-edge tdf call-trace clear | Clear the completed or duplicate subscriber call traces on one or more TDF gateways. | [] | unified-edge
Output Fields
No message is displayed on successful execution of this command; otherwise an error message is
displayed.
Sample Output
request unified-edge tdf call-trace clear
user@host> request unified-edge tdf call-trace clear | Statement introduced in Junos OS Release 17.1. | [] | |
request unified-edge tdf call-trace show | request unified-edge tdf call-trace show
<all | completed | current>
<brief | detail> | Display the information related to subscriber call tracing on one or more TDF gateways. | [
{
"name": "none",
"desc": "(Same as brief) Display information related to subscriber call tracing in brief."
},
{
"name": "all | completed | current",
"desc": "(Optional) Display call trace information for the following:"
},
{
"name": "all",
"desc": "All calls."
},
{
"name": ... | unified-edge
Output Fields
Table 152 on page 16011 lists the output fields for the request unified-edge tdf call-trace show command.
Output fields are listed in the approximate order in which they appear.
Table 152: request unified-edge tdf call-trace show Output Fields
Field Name
Field Description
Level of Output
Ide... | Statement introduced in Junos OS Release 17.1. | [] | |
request unified-edge tdf call-trace start | request unified-edge tdf call-trace start
<imsi imsi>
<msisdn msisdn>
<next-call next-call>
<routing-instance routing-instance>
<subscriber-name string>
<user-name string>
<v4-addr v4-addr>
<v6-addr v6-addr> | Start TDF subscriber call tracing. | [
{
"name": "none",
"desc": "Start call tracing for all TDF subscribers."
},
{
"name": "imsi imsi",
"desc": "(Optional) Start the call tracing for subscribers with the specified International Mobile Subscriber Identity (IMSI) number."
},
{
"name": "msisdn msisdn",
"desc": "(Optional) S... | unified-edge
Output Fields
Table 153 on page 16015 lists the output fields for the request unified-edge tdf call-trace start command.
Output fields are listed in the approximate order in which they appear.
Table 153: request unified-edge tdf call-trace start Output Fields
Field Name
Field Description
Session PIC
Identi... | Statement introduced in Junos OS Release 17.1. | [] | |
request unified-edge tdf call-trace stop | request unified-edge tdf call-trace stop
<all>
<identifier call-trace-identifier> | Stop the previously configured subscriber call tracing on one or more TDF gateways. | [
{
"name": "none",
"desc": "(Same as all) Stop all subscriber call tracing."
},
{
"name": "all",
"desc": "(Optional) Stop all subscriber call tracing."
},
{
"name": "identifier call-trace-identifier",
"desc": "(Optional) Stop call tracing for the specified call trace identifier."
}
... | unified-edge
Output Fields
Table 154 on page 16018 lists the output fields for the request unified-edge tdf call-trace stop command.
Output fields are listed in the approximate order in which they appear.
Table 154: request unified-edge tdf call-trace stop Output Fields
Field Name
Field Description
Session PIC
Identif... | Statement introduced in Junos OS Release 17.1. | [] | |
request validation policy | request validation policy
<instance instance-name>
<logical-system logical-system-name>
<record ip-prefix> | When BGP origin validation is configured, manually request a route validation record policy to be
reevaluated. This command causes dependent route validation records to be reevaluated. Dependent
route validation records are exactly matching and more specific records. | [
{
"name": "none",
"desc": "Request a policy reevaluation of all dependent route validation records."
},
{
"name": "instance instance-name",
"desc": "(Optional) Request a policy reevaluation of all dependent route validation records for the specified routing instance. The instance name can be pri... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request validation policy
user@host> request validation policy
Enqueued 1 IPv4 records
Enqueued 0 IPv6 records | Command introduced in Junos OS Release 12.2. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] | |
request virtual-chassis device-reachability | request virtual-chassis device-reachability test-name name (source-fpc source-fpc-id | source-
ip-address source-ip-address) (destination-device device-id | destination-fpc destination-fpc-id
| destination-ip-address destination-ip-address)
<probe-count count>
<probe-interval interval>
<probe-pattern pattern>
<test-c... | Run a Virtual Chassis device reachability test. A Virtual Chassis device reachability test sends ping
packets from one member of a Virtual Chassis to another member of a Virtual Chassis directly through
the Virtual Chassis connections. The receiving Virtual Chassis member sends reply packets to confirm
receipt of the p... | [
{
"name": "test-name name",
"desc": "Specify the name of the test. The name can be any single-word character string. Spaces are not allowed."
},
{
"name": "source-fpc source-fpc-id",
"desc": "Specify the FPC that sends the first ping message."
},
{
"name": "source-ip-address",
"desc"... | system-control
Output Fields
Table 155 on page 16023 lists the output fields for the request virtual chassis device reachability
command. Output fields are listed in the approximate order in which they appear.
Table 155: request virtual chassis device reachability Output Fields
Field Name
Field Description
Test Name
T... | Command introduced in Junos OS Release 11.2. | [
"Verifying Connectivity Between Virtual Chassis Member Devices"
] | |
request virtual-chassis member-id delete (MX Series Virtual Chassis) | request virtual-chassis member-id delete
<force> | Remove (delete) the member ID from a router or switch that you want to remove from a Virtual Chassis
configuration.
NOTE: Issuing the command to remove the member ID causes the device to reboot, and
requires you to confirm that you want to proceed with this operation. If you do not
confirm the operation, the software c... | [] | system-control
Sample Output
request virtual-chassis member-id delete
user@host> request virtual-chassis member-id delete
This command will disable virtual-chassis mode and reboot the system.
Continue? [yes,no] (no) | Command introduced in Junos OS Release 11.2. | [
"Deleting Member IDs in a Virtual Chassis Configuration",
"Example: Deleting a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms"
] | |
request virtual-chassis member-id set | request virtual-chassis member-id set member member-id
<slots-per-chassis slot-count> | Assign (set) a member ID and, optionally, a slot count to a router or switch that you want to add as a
member of a Virtual Chassis configuration.
NOTE: Issuing the request virtual-chassis member-id set command causes the device to
reboot, and requires you to confirm that you want to proceed with this operation. If you
... | [
{
"name": "member",
"desc": ""
},
{
"name": "member-id",
"desc": "Assign the numeric value that identifies a member router or switch in a Virtual Chassis configuration. When you assign a member ID to a router or switch, assign the same member ID defined for this device in the preprovisioned conf... | system-control
Sample Output
request virtual-chassis member-id set (Assigning a Member ID)
user@host> request virtual-chassis member-id set member 0
This command will enable virtual-chassis mode and reboot the system.
Continue? [yes,no] (no)
request virtual-chassis member-id set (Assigning a Member ID and Slot Count)... | Command introduced in Junos OS Release 11.2.
slots-per-chassis option added in Junos OS Release 15.1 for MX960 routers, MX2010 routers, and
MX2020 routers. | [
"Configuring Member IDs for a Virtual Chassis",
"Configuring an EX9200 Virtual Chassis",
"Example: Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a",
"Virtual Chassis"
] | |
request virtual-chassis mode | request virtual-chassis mode
fabric
mixed <ieee-clause-82>
hgoe
network-port
<disable>
<reboot>
<all-members> | <local> | <member member-id> | Enable special device modes when operating as part of a Virtual Chassis or Virtual Chassis Fabric (VCF).
Supported device modes include:
•
Fabric mode—Enable the device to operate as part of a VCF. You must set fabric mode on all of the
devices in a VCF.
•
Mixed mode—Enable the device to operate in a mixed Virtual Chas... | [
{
"name": "all-members",
"desc": "(Optional) Set the Virtual Chassis mode for all members of the Virtual Chassis or VCF."
},
{
"name": "disable",
"desc": "Disable the specified Virtual Chassis mode setting if it was previously enabled. You must include at least one of the supported modes that yo... | system-control
Sample Output
request virtual-chassis mode mixed
user@switch> request virtual-chassis mode mixed
Sample Output
request virtual-chassis mode fabric mixed reboot
user@switch> request virtual-chassis mode fabric mixed reboot
Sample Output
request virtual-chassis mode mixed (with IEEE Clause 82 mode for EX4... | Command introduced in Junos OS Release 11.1.
fabric mode introduced in Junos OS Release 13.2X51-D20 for EX Series switches and QFX Series
devices in a Virtual Chassis Fabric (VCF).
ieee-clause-82 mixed-mode option introduced for EX4300 switches mixed with EX4300 multigigabit
switches in a Virtual Chassis in Junos OS Re... | [
"Understanding Mixed EX Series and QFX Series Virtual Chassis",
"Understanding Mixed Virtual Chassis Fabric",
"Configuring a Mixed Virtual Chassis with EX4200, EX4500, and EX4550 Member Switches (CLI",
"Procedure)",
"Configuring an EX2300, EX3400, or EX4300 Virtual Chassis",
"Configuring EX4600 Switches i... | |
request virtual-chassis reactivate | request virtual-chassis reactivate | Reactivate a device that has been assigned a member ID but is not currently connected to the Virtual
Chassis or VCF.
You can use this command to reactivate a device that was previously part of the Virtual Chassis or VCF
but whose status is no longer Prsnt. | [] | system-control
Sample Output
request virtual-chassis reactivate
user@switch> request virtual-chassis reactivate | Command introduced in Junos OS Release 9.3. | [
"Verifying the Member ID, Role, and Neighbor Member Connections of a Virtual Chassis Member",
"Verifying the Member ID, Role, and Neighbor Member Connections of an EX8200 Virtual Chassis",
"Member"
] | |
request virtual-chassis recycle | request virtual-chassis recycle member-id member-id | Make a previously used member ID available for reassignment.
When you remove a member switch from the Virtual Chassis configuration, the primary reserves that
member ID. To make the member ID available for reassignment, you must use this command.
NOTE: You must run this command from the Virtual Chassis member in the p... | [
{
"name": "member-id member-id",
"desc": "Specify the member ID that you want to make available for reassignment to a different member."
}
] | system-control
Sample Output
request virtual-chassis recycle member-id 3
user@switch> request virtual-chassis recycle member-id 3
Sample Output
request virtual-chassis recycle member-id 1
user@external-routing-engine> request virtual-chassis recycle member-id 1 | Command introduced in Junos OS Release 9.0. | [
"Removing or Replacing a Member Switch of a Virtual Chassis Configuration"
] | |
request virtual-chassis renumber | request virtual-chassis renumber member-id old-member-id new-member-id new-member-id | Renumber a member of a Virtual Chassis configuration.
NOTE: You must run this command from the Virtual Chassis member in the primary role. | [
{
"name": "member-id old-member-id",
"desc": "Specify the ID of the member that you wish to renumber."
},
{
"name": "new-member-id new-member-id",
"desc": "Specify an unassigned member ID."
}
] | system-control
Sample Output
request virtual-chassis renumber member-id 5 new-member-id 4
user@switch> request virtual-chassis renumber member-id 5 new-member-id 4
request virtual-chassis renumber member-id 1 new-member-id 0
user@external-routing-engine> request virtual-chassis renumber member-id 1 new-member-id 0 | Command introduced in Junos OS Release 9.0. | [
"Removing or Replacing a Member Switch of a Virtual Chassis Configuration"
] | |
request virtual-chassis routing-engine master switch | request virtual-chassis routing-engine master switch
<check> | Change the primary role in an MX Series Virtual Chassis or EX9200 Virtual Chassis by switching the
global roles of the primary router or switch and backup router or switch in the Virtual Chassis
configuration. The request virtual-chassis routing-engine master switch command must be issued from the
primary router or swi... | [
{
"name": "check",
"desc": "(Optional) Perform a check from the primary router or switch to determine whether the member routers or switches are ready for GRES from a database synchronization perspective, without initiating the GRES operation itself."
}
] | system-control
Sample Output
request virtual-chassis routing-engine master switch (From Primary Router)
{master:member0-re0}
user@host> request virtual-chassis routing-engine master switch
Do you want to continue ? [yes,no] (no)
request virtual-chassis routing-engine master switch (Error When Configuration Not
Synchron... | Command introduced in Junos OS Release 11.2.
Option check introduced in Junos OS Release 12.2. | [
"Switching the Global Primary and Backup Roles in a Virtual Chassis Configuration",
"Determining GRES Readiness in a Virtual Chassis Configuration",
"Switchover Behavior in an MX Series Virtual Chassis",
"Primary-role Election in a Virtual Chassis"
] | |
request virtual-chassis vc-port (Dedicated VCP) | request virtual-chassis vc-port set interface vcp-interface-name
<member member-id> <disable> | Disable or enable a Virtual Chassis port (VCP) on a dedicated VCP.
Configure a Gigabit Ethernet link on an EX8200 switch as a VCP in an EX8200 Virtual Chassis. You can
use this command only to configure a link between two EX8200 member switches as a VCP link; all
other links in an EX8200 Virtual Chassis are automatical... | [
{
"name": "interface vcp-interface-",
"desc": ""
},
{
"name": "name",
"desc": "Name of the interface to enable or disable. If you omit member member-id in an EX4200 Virtual Chassis, EX4500 Virtual Chassis, EX4550 Virtual Chassis, mixed Virtual Chassis, this command defaults to disabling or enabl... | system-control
Sample Output
request virtual-chassis vc-port set interface vcp-0 disable (EX4200 Virtual Chassis)
user@switch> request virtual-chassis vc-port set interface vcp-0 disable
To check the results of this command, use the "show virtual-chassis vc-port" on page 28757 command.
request virtual-chassis vc-port... | Command introduced in Junos OS Release 9.0. | [
"Understanding Virtual Chassis Components"
] | |
request virtual-chassis vc-port delete (MX Series Virtual Chassis) | request virtual-chassis vc-port delete fpc-slot fpc-slot-number pic-slot pic-slot-number port
port-number
<(local | member member-id)> | Remove (delete) a Virtual Chassis port from a member router in an MX Series Virtual Chassis
configuration. After a Virtual Chassis port is created, it is renamed vcp-slot/pic/port, and is no longer
available for configuration as a standard network port. After you remove a Virtual Chassis port, it
becomes available to t... | [
{
"name": "fpc-slot fpc-slot-number",
"desc": "Number of the Flexible PIC Concentrator (FPC) slot on which the Virtual Chassis port resides. The slot number corresponds to the Modular Port Concentrator (MPC) slot number. Replace fpc-slot-number with a value appropriate for your router:"
},
{
"name":... | system-control
Sample Output
request virtual-chassis vc-port delete (Remove vcp-3/2/1)
user@host> request virtual-chassis vc-port delete fpc-slot 3 pic-slot 2 port 1
vc-port successfully deleted | Command introduced in Junos OS Release 11.2. | [
"Deleting Virtual Chassis Ports in a Virtual Chassis Configuration",
"Example: Deleting a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms"
] | |
request virtual-chassis vc-port diagnostics optics | request virtual-chassis vc-port diagnostics optics | Run a digital optical monitoring (DOM) scan on the optical ports configured as Virtual Chassis ports
(VCPs).
Enter the show virtual-chassis vc-port diagnostics optics command to view the results of the diagnostic
scan.
On certain EX Series switches, you must enter the request virtual-chassis vc-port diagnostics optics
... | [] | system-control
Sample Output
request virtual-chassis vc-port diagnostics optics
user@switch> request virtual-chassis vc-port diagnostics optics
fpc0:
--------------------------------------------------------------------------
vc-port Diagnostics Optics Done | Command introduced in Junos OS Release 13.2X50-D10. | [] | |
request virtual-chassis vc-port set (MX Series Virtual Chassis) | request virtual-chassis vc-port set fpc-slot fpc-slot-number pic-slot pic-slot-number port port-
number
<(local | member member-id)> | Create (set) a Virtual Chassis port on an MX Series router through which the router connects to other
member routers in the Virtual Chassis. You can create Virtual Chassis ports only on Modular Port
Concentrator/Modular Interface Card (MPC/MIC) network ports on MX Series routers.
After a Virtual Chassis port is created... | [
{
"name": "fpc-slot fpc-slot-number",
"desc": "Number of the Flexible PIC Concentrator (FPC) slot on which the Virtual Chassis port resides. The slot number corresponds to the Modular Port Concentrator (MPC) slot number. Replace fpc-slot-number with a value appropriate for your router:"
},
{
"name":... | system-control
Sample Output
request virtual-chassis vc-port set (No Existing Network Port)
user@host> request virtual-chassis vc-port set fpc-slot 1 pic-slot 1 port 0
vc-port successfully set
request virtual-chassis vc-port set (Existing Network Port Converted)
user@host> request virtual-chassis vc-port set fpc-slot 2... | Command introduced in Junos OS Release 11.2. | [
"Configuring Virtual Chassis Ports to Interconnect Member Routers or Switches",
"Example: Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a",
"Virtual Chassis",
"Guidelines for Configuring Virtual Chassis Ports"
] | |
request virtual-chassis vc-port | request virtual-chassis vc-port (set | delete)
<fpc-slot fpc-slot> pic-slot pic-slot port port-number
interface interface-name
<member | local>
member-id | Set a port to operate as a Virtual Chassis port (VCP), or delete the VCP setting on a port. See Virtual
Chassis Port Options for details on which ports you can set as VCPs on different switches. After setting
a port as a VCP, you can’t use the port for any other purpose unless you remove the VCP setting.
You can specif... | [
{
"name": "set",
"desc": "Set a port as a VCP to convert an uplink or network port into a VCP."
},
{
"name": "delete",
"desc": "Delete the VCP setting on a port to convert a VCP back into an uplink or network port."
},
{
"name": "pic-slot pic-slot",
"desc": "Number of the PIC slot fo... | system-control
Sample Output
request virtual-chassis vc-port set pic-slot 1 port 0
user@switch> request virtual-chassis vc-port set pic-slot 1 port 0
To check the results of this command, use the "show virtual-chassis vc-port" on page 28757 command.
request virtual-chassis vc-port set pic-slot 1 port 1 member 3
user@s... | Command introduced in Junos OS Release 9.0.
Option fpc-slot introduced in Junos OS Release 10.4 for EX Series switches. | [
"request virtual-chassis vc-port (Dedicated VCP)",
"Virtual Chassis Port (VCP) Interface Names in an EX8200 Virtual Chassis",
"Understanding Virtual Chassis Components"
] | |
request virtual-network-functions | request virtual-network-functions vnf-name (add-image | all-servers | delete-image | force | restart | server |
start | stop) | Start, stop or restart the VNFs. Also, you can add or remove the base image.
NOTE: You can issue these commands either on both the servers (server0 and server1)
or on one specific server. | [
{
"name": "vnf-name",
"desc": "Name of the VNF."
},
{
"name": "add-image",
"desc": "Add the base image to the VNF repository."
},
{
"name": "all-servers",
"desc": "Issue the command on both the servers."
},
{
"name": "delete-image",
"desc": "Delete the base image from the... | View | Command introduced in Junos OS Release 17.2R1.
The force option is available from Junos OS Release 17.4R1. | [
"Generic Guidelines for Using JDM Server Commands"
] | |
request vmhost cleanup (NFX Series) | request vmhost cleanup | Clean up temporary files, crash generated files, and log files located in the /var/tmp, /var/crash,
and /var/log directories respectively on the host OS. | [] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request. | Command introduced in Junos OS Release 18.1R1. | [] | |
request vmhost cleanup | request vmhost cleanup
invoke-on;
(re0 | re1);
routing engine; | Clean up temporary files, crash generated files, and log files located in the /var/tmp, /var/crash,
and /var/log directories respectively on the host OS.
NOTE: You can clean up files of any format in the /var/tmp and /var/crash location.
However, you can cleanup only the .gz format files in the /var/log/ location. | [
{
"name": "none",
"desc": "Clean up temporary files, crash generated files, and log files located in the /var/tmp, /var/crash,"
},
{
"name": "dry-run",
"desc": "(Optional) List the clean up candidates; do not remove them."
},
{
"name": "invoke-on",
"desc": "(Optional) Clean up tempor... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request. | Command introduced in Junos OS Release 15.1F3.
dry-run option introduced in Junos OS Release 24.4.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] | |
request vmhost copy jnode-to-vjunos | request vmhost copy jnode-to-vjunos from-jnode host-filename to-vjunos junos-filename | Copy files from Linux host to Junos OS. | [
{
"name": "from-jnode host-filename",
"desc": "Name of the host file to be copied."
},
{
"name": "to-vjunos junos-filename",
"desc": "Name of the Junos OS file to which the host file is copied."
}
] | maintenance | Command introduced in Junos OS Release 18.4R1 on Enhanced Automation variants of Junos OS. For
more information, see Overview of Junos Automation Enhancements on Devices Running Junos OS
with Enhanced Automation. | [] | |
request vmhost copy vjunos-to-jnode | request vmhost copy vjunos-to-jnode from-vjunos junos-filename to-jnode host-filename | Copy files from Junos OS to Linux host. | [
{
"name": "from-vjunos junos-filename",
"desc": "Name of the Junos OS file to be copied."
},
{
"name": "to-jnode host-filename",
"desc": "Name of the host file to which to copy the file."
}
] | maintenance | Command introduced in Junos OS Release 18.4R1 on Enhanced Automation variants of Junos OS. For
more information, see Overview of Junos Automation Enhancements on Devices Running Junos OS
with Enhanced Automation. | [] | |
request vmhost file-copy (NFX Series) | request vmhost file-copy (crash|log) from-jnode host file-name to-vjunos host file-name | Copy crash files or log files from the host OS to Junos OS. You can use these files for analysis and
debugging purposes. | [
{
"name": "crash",
"desc": "Files in /var/crash on the host."
},
{
"name": "from-jnode filename",
"desc": "Name of the host file to be copied."
},
{
"name": "log",
"desc": "Files in /var/log on the host."
},
{
"name": "to-vjunos filename",
"desc": "Name of the Junos OS fi... | maintenance
Sample Output
request vmhost file-copy
user@host> request vmhost file-copy log from-jnode daemon.log to-vjunos /var/tmp
:/var/tmp # ls -lrt daemon.log
-rw-r--r-- 1 root wheel 1035126 Mar 4 20:33 daemon.log | Command introduced in Junos OS Release 18.1R1. | [] | |
request vmhost file-copy | request vmhost file-copy
from-jnode filename{
(crash | log);
to-vjunos directory filename;
}
invoke-on; | Copy crash files or log files from the host OS to Junos OS. You can use these files for analysis and
debugging purposes. | [
{
"name": "crash",
"desc": "Files in /var/crash on the host."
},
{
"name": "from-jnode filename",
"desc": "Name of the host file to be copied."
},
{
"name": "log",
"desc": "Files in /var/log on the host."
},
{
"name": "to-vjunos directory/",
"desc": ""
},
{
"name"... | maintenance
Sample Output
request vmhost file-copy
user@host> request vmhost file-copy from-jnode messages log to-vjunos /var/tmp/linux_log_file
user@host> file list /var/tmp/linux_log_file detail
-rw-r----- 1 root wheel 7253996 Mar 2 23:08 /var/tmp/linux_log_file
total files: 1 | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX.
Command introduced in Junos OS Release 18.1R1 for NFX150 devices.
Command introduced in Junos OS Release 18.4R1 for NFX250 (NG) devices.
Command introduced in Junos OS Release 19.1R1 for NFX350 devices. | [] | |
request vmhost halt (NFX Series) | request vmhost halt | Stop the host OS and Junos OS running on the device. | [] | maintenance
Sample Output
request vmhost halt
user@host> request vmhost halt
Halt the vmhost ? [yes,no] (no) yes
Initiating vmhost halt... ok
Initiating Junos shutdown... shutdown: [pid 8782]
Shutdown NOW!
ok
Junos shutdown is in progress...
... | Command introduced in Junos OS Release 18.1R1. | [] | |
request vmhost halt | request vmhost halt
<re0 | re1>
<routing-engine> | Stop the host OS and Junos OS running on the device. | [
{
"name": "none",
"desc": "Stop the host OS and Junos OS on the device."
},
{
"name": "re0 | re1",
"desc": "(Optional) On devices that support dual or redundant Routing Engines, stop the host OS and Junos OS running on the Routing Engine in slot 0 (re0) or the Routing Engine in slot 1 (re1)."
... | maintenance
Sample Output
request vmhost halt
request vmhost halt | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] | |
request vmhost hard-disk-test | request vmhost hard-disk-test {disk disk-name|long|short|show-status} | Run memory and diagnostics monitoring test on the solid-state drive (SSD). The test output provides
information about the various attributes of the SSD that is help monitor the status of the hard disk
memory. | [
{
"name": "disk disk-name",
"desc": "Name of the SSD."
},
{
"name": "long",
"desc": "Run extended Self-Monitoring, Analysis and Reporting Technology (SMART) tests of the SSD."
},
{
"name": "short",
"desc": "Run short SMART tests of the SSD."
},
{
"name": "show-status",
"d... | maintenance
Sample Output
request vmhost hard-disk-test
user@host> request vmhost hard-disk-test show-status disk /dev/sda
smartctl 5.42 2014-07-28 r3460 [x86_64-linux-3.10.79-ovp-rt74-WR6.0.0.20_preempt-rt] (local
build)Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFOR... | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] | |
request vmhost jdm add (In-Chassis Model) | request vmhost jdm add package-name | Adds the Juniper Device Manager (JDM) software package. This command is applicable to in-chassis
Junos node slicing. | [
{
"name": "add package-name",
"desc": "Add the Juniper Device Manager (JDM) software package. You need to type the package name after the command add."
}
] | maintenance | Command introduced in Junos OS Release 19.1R1. | [
"Generic Guidelines for Using JDM Server Commands"
] | |
request vmhost jdm delete (In-Chassis Model) | request vmhost jdm delete | Uninstalls the Juniper Device Manager (JDM). This command is applicable to in-chassis Junos node
slicing. | [] | maintenance | Command introduced in Junos OS Release 19.1R1. | [
"Generic Guidelines for Using JDM Server Commands"
] | |
request vmhost jdm login (In-Chassis Model) | request vmhost jdm login | Logs in to the Juniper Device Manager (JDM). This command is applicable to in-chassis Junos node
slicing.
NOTE: To log in to JDM, you must be a root user. | [] | maintenance
Sample Output
request vmhost jdm login
root@router> request vmhost jdm login
****************************************************************************
* The Juniper Device Manager (JDM) must only be used for orchestrating the *
* Virtual Machines for Junos Node Slicing *
* *
* Host Linux Distro: Wind Riv... | Command introduced in Junos OS Release 19.1R1. | [
"Generic Guidelines for Using JDM Server Commands"
] | |
request vmhost jdm start (In-Chassis Model) | request vmhost jdm start | Starts the Juniper Device Manager (JDM). This command is applicable to in-chassis Junos node slicing. | [] | maintenance
Sample Output
request vmhost jdm start
user@router> request vmhost jdm start
Starting JDM
Starting jdm: Domain jdm defined from
/vm/vm/iapps/jdm//install/juniper/lxc/jdm/current/config/jdm.xml
Domain jdm started | Command introduced in Junos OS Release 19.1R1. | [
"Generic Guidelines for Using JDM Server Commands"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.