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 vmhost jdm stop (In-Chassis Model) | request vmhost jdm stop | Stops 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 local-file-copy | request vmhost local-file-copy source source_path destination destination_path; | Copy a file or a directory present under /var/public/ directory structure on the hypervisor to a different
name under /var/public/ directory structure. | [
{
"name": "source source-path",
"desc": "Name of the source path from which the file is to be copied."
},
{
"name": "destinationdestination-path",
"desc": "Name of the destination path to which the file is copied."
},
{
"name": "/var/public/sanity_packages",
"desc": ""
},
{
"... | Maintenance
Sample Output
request vmhost local-file-copy (To copy a directory)
user@host> request vmhost local-file-copy source /var/public/sanity_packages destination /var/
public/new_sanity_packages
'/var/public/sanity_packages' -> '/var/public/new_sanity_packages'
'/var/public/sanity_packages/centos-linux-1.img.gz' ... | Command introduced in Junos OS Release 24.2R1 for NFX150, NFX250, and NFX350 devices. | [] | |
request vmhost mode | request vmhost mode [compute | hybrid | throughput | mode-name] | Select the operational mode of the device from a pre-defined list of modes (compute, hybrid, or
throughput) or specify a mode-name for a custom mode.
NOTE:
•
Starting from Junos OS Release 19.3R1, if the same physical CPU is used for both
VNFs and the Junos OS or device components, the request to change the mode fails... | [] | maintenance
Sample Output
request vmhost mode compute
user@host> request vmhost mode compute
warning: Device will be rebooted to change the mode from hybrid to compute
Do you want to continue? [yes,no] (no) | The request vmhost mode command is introduced in Junos OS Release 19.1R1.
The request vmhost mode mode-name command is introduced in Junos OS Release 21.1R1 for NFX250
NextGen and NFX350 devices. | [] | |
request vmhost power-off (NFX Series) | request vmhost power-off | Shut down the Junos OS software and the host OS. | [] | maintenance
Sample Output
request vmhost power-off
user@host> request vmhost power-off
Power-off the vmhost ? [yes,no] (no) yes
Initiating vmhost shutdown... ok
Initiating Junos shutdown... shutdown: [pid 3884]
Shutdown NOW!
ok
*** FINA... | Command introduced in Junos OS Release 18.1R1.
NOTE: request vmhost power-on is not supported on NFX150 and NFX250 (NG) devices. | [] | |
request vmhost power-off | request vmhost power-off
<other routing-engine> | Power off the Routing Engine on which Junos OS and the host OS are running. In a PTX3000, the
Routing and Control Board is powered off.
NOTE: The QFX10002-60C and PTX10002-60C devices do not have primary and
backup routing engines. | [
{
"name": "none",
"desc": "Power off the Routing Engine immediately."
},
{
"name": "other-routing-",
"desc": ""
},
{
"name": "engine",
"desc": "(Optional) Power off the other Routing Engine on which the Junos OS and the host OS are running. For example, if you issue the command from ... | maintenance
Sample Output
request vmhost power-off
request vmhost power-off | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [
"request system power-off"
] | |
request vmhost power-on | request vmhost power-on other-routing-engine | Power on the Routing Engine on which Junos OS and the host OS are running. In a PTX3000, the
Routing and Control Board is powered on. | [
{
"name": "other-routing-",
"desc": ""
},
{
"name": "engine",
"desc": "Power on the other Routing Engine on which the Junos OS and the host OS are running. For example, if you issue the command from the primary Routing Engine, the backup Routing Engine is powered on. Similarly, if you issue the ... | maintenance
Sample Output
request vmhost power-on
user@host> request vmhost power-on other-routing-engine
Routing Engine 1 power-on initiated, use "show chassis routing-engine" to verify | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] | |
request vmhost reboot (NFX Series) | request vmhost reboot [disk1 | disk2] [primary | alternate] | Reboot the Junos OS software and the host OS from the specified disk and the partition within the disk. | [] | maintenance
Sample Output
request vmhost reboot (NFX150)
user@host> request vmhost reboot disk1 primary
Reboot the vmhost ? [yes,no] (no) yes
Switching boot to disk1 primary
Initiating vmhost reboot... ok
Stopping jrestartd: [ OK ]
/etc/init.d/functions: line 286: usleep: command not found
Initiating Junos shutdown.... | Command introduced in Junos OS Release 18.1R1. | [] | |
request vmhost reboot | request vmhost reboot
<disk1>
<disk2>
<network>
<re0 | re1>
<routing engine>
<usb> | Reboot both the Junos OS and the host OS running on the device. | [
{
"name": "none",
"desc": "Reboot the device software immediately."
},
{
"name": "disk1",
"desc": "(Optional) Reboot both Junos OS and the host OS on the Routing Engine and boot the Routing Engine from the primary disk."
},
{
"name": "disk2",
"desc": "(Optional) Reboot both Junos OS ... | maintenance
Sample Output
request vmhost reboot
request vmhost reboot
<disk1>
<disk2>
<in>
<network>
<usb> | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] | |
request vmhost remote-file-copy | request vmhost remote-file-copy
interface {
(in-band | out-of-band);
}
source source-path;
destination destination-path; | Enable remote file copy between the hypervisor and a remote fileserver. The configuration allows
creating an external network interface directly on the hypervisor and associating an IPv4 address with it.
The remote file copy feature allows upload or download operations from or into the NFX device. These
operations are ... | [
{
"name": "in-band",
"desc": "Enable external network access through one of the front panel revenue ports."
},
{
"name": "out-of-band",
"desc": "Enable external network access through the front panel management interface."
},
{
"name": "source source-path",
"desc": "Name of the sourc... | Maintenance
Sample Output
request vmhost remote-file-copy (To upload a file from an NFX device to remote fileserver
using an in-band interface and scp protocol, with user interaction)
user@host> request vmhost remote-file-copy interface in-band source /var/public/1G.dat
destination root@scp://10.10.10.11:22:/var/www/h... | Command introduced in Junos OS Release 24.2R1 for NFX150, NFX250, and NFX350 devices. | [] | |
request vmhost snapshot | request vmhost snapshot
<partition>
<re0 | re1>
<recovery>
<routing-engine> | Create a recovery snapshot of the currently running and active file system partitions on the backup disk
to recover the primary disk in case of failure.
On the device, back up the snapshot of the host OS image along with the Junos OS image. In case of
failure of the primary disk, you can boot from the image available i... | [
{
"name": "none",
"desc": "Create a snapshot from the current disk to the target disk without partitioning the target disk."
},
{
"name": "partition",
"desc": "(Optional) Create a snapshot from the current disk to target disk and partition the target"
},
{
"name": "disk. Contents on the ... | maintenance
Sample Output
request vmhost snapshot
user@host> request vmhost snapshot
warning: Existing data on the target may be lost
Proceed ? [yes,no] (no) yes
warning: Proceeding with vmhost snapshot
Current root details, Device sda, Label: jrootb_P, Partition: sda4
Snapshot admin context from current boo... | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] | |
request vmhost software abort in-service-upgrade | request vmhost software abort in-service-upgrade | Terminate unified in-service software upgrade (unified 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
vmhost software in-service-upgrade command to launch the unified ISSU. | [
{
"name": "in-service-upgrade",
"desc": "Terminate unified ISSU."
}
] | maintenance | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [
"request system software abort"
] | |
request vmhost software add (NFX Series) | request vmhost software add package-name <in>| <no-validate>| <reboot>| <set>| <unlink>|
<upgrade-to-model model-number> | Install or upgrade the Junos OS and host software packages on the device. | [
{
"name": "in",
"desc": "(Optional) Number of minutes to delay before the reboot operation."
},
{
"name": "no-validate",
"desc": "(Optional) When loading a software package or bundle with a different release, suppress"
},
{
"name": "reboot",
"desc": "(Optional) After adding the softw... | maintenance
Sample Output
request vmhost software add (NFX150)
user@host> request vmhost software add /var/public/jinstall-host-nfx-3-x86-64-18.1R1.8-secure-
signed.tgz no-validate reboot
Verified jinstall-host-nfx-3-x86-64-18.1R1.8-secure-signed signed by PackageProductionEc_2018
method ECDSA256+SHA256
Pushing Junos... | Command introduced in Junos OS Release 18.1R1. | [] | |
request vmhost software add | Install Junos OS and host software packages on the device.
For installing the host software as well as Junos OS, specify the package name junos-vmhost-install-
x.tgz in the request vmhost software add command. Junos OS installation alone can be achieved by
specifying the regular package name junos-install-x.tgz in the ... | [
{
"name": "none",
"desc": "Install Junos OS and host software packages on the Routing Engine on the local Virtual Chassis"
},
{
"name": "package-name",
"desc": "Location from which the software package or bundle is to be installed. For example:"
},
{
"name": "/var/tmp/package-name",
... | maintenance
Sample Output
request vmhost software add (Multiple Packages)
user@host> request vmhost software add set [/var/tmp/junos-vmhost-install-ptx-
x86-64-15.1F-20160518.0.tgz /var/tmp/junos-vmhost-jdiag-15.1F-20160518.0.tgz no-validate
Verified /var/tmp/junos-vmhost-install-ptx-x86-64-15.1F-20160518.0.tgz signed... | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] | ||
request vmhost software in-service-upgrade | request vmhost software in-service-upgrade package-name
< no-old-master-upgrade>
< reboot>
< verbose> | Perform a unified in-service software upgrade (ISSU). A unified ISSU enables you to upgrade from one
Junos OS release and host OS release to another with no disruption on the control plane and with
minimal disruption of traffic. For an unified ISSU, graceful Routing Engine switchover (GRES) and
nonstop active routing (... | [
{
"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"... | maintenance
Sample Output
request vmhost software in-service-upgrade
user@host> request vmhost software in-service-upgrade
/var/tmp/junos-vmhost-install-ptx-x86-64-15.1F5.6.tgz reboot
Chassis ISSU Check Done
[Feb 24 01:12:09]: Starting VMHOST ISSU
[Feb 24 01:12:09]:ISSU: Validating Image
FPC 2 will be offlined (In-... | Command introduced in Junos OS Release 15.1F3.
Option introduced in Junos OS Release 18.2R1 for the MX Series routers.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [
"request system software in-service-upgrade"
] | |
request vmhost software rollback | request vmhost software rollback
<re0 | re1>
<routing-engine> | Roll back the Junos OS and the host OS software packages to the previous versions. You can revert to
the previous versions of software packages that were loaded at the last successful request vmhost software
add command. | [
{
"name": "none",
"desc": "Roll back the software packages of the Routing Engine on the local Virtual Chassis member."
},
{
"name": "re0 | re1",
"desc": "(Optional) On devices that support dual or redundant Routing Engines, roll back the software packages in Routing Engine in slot 0 (re0) or sof... | maintenance
Output Fields
Sample Output
request vmhost software rollback
request vmhost software rollback
<reboot>
command-name
user@host> request vmhost software rollback
Current root details, Device sda, Label: jrootp_P, Partition: sda3
Finding alternate root for rollback
Rollback to software on jrootb_P ..... | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] | |
request vmhost software validate | request vmhost software validate package-name | Verify and validate the software package compatibility with the current configuration of the router. | [] | maintenance
Sample Output
request vmhost software validate
request vmhost software validate
<package-name>
<log_collector.sh> | Statement introduced in Junos OS Release 18.4R1
NOTE: The command is supported on the routers with RE-MX-X6, RE-MX-X8, and RE-
PTX-X8 Routing Engines with VM host support only. | [
"request system software abort"
] | |
request vmhost storage | request vmhost storage
request vmhost storage external-ssd initialize slot [0 | 1] public-dir-name [public-disk0 |
public-disk1] force
request vmhost storage external-ssd [add | remove] slot [0 | 1] | Initializes an SSD in the specified external SSD slot. It prompts you to confirm and then formats the
external SSD so that you can use it for NFX350 device.
Adds or removes an external SSD from its slot. This command also checks the configuration for any VNF
path that requires the external disk to be present.
NOTE: Ext... | [
{
"name": "initialize",
"desc": "Initializes an SSD in the specified external SSD slot 0 or slot 1."
},
{
"name": "public-dir-name",
"desc": "Shows the same public-directory path for an SSD even if you move the SSD from"
},
{
"name": "add",
"desc": "Adds an external SSD to slot 0 or ... | maintenance
Sample Output
request vmhost storage (NFX150)
user@host> request vmhost storage ?
Possible completions:
<storage-name> Storage name
self-test-long Long Storage Test
self-test-messages Storage Self Test messages
self-test-short Long Storage Test
request vmhost storage (NFX250 Nex... | Command introduced in Junos OS Release 18.1R1. | [] | |
request vmhost zeroize ztp-option secure | request vmhost zeroize ztp-option secure-(enable | disable) | On secure platforms that run secure ZTP (SZTP), you can switch between using SZTP to using zero-
touch provisioning (ZTP).
NOTE: On MX304 devices without a backup Routing Engine, when you issue the request
vmhost zeroize ztp-option secure-(enable | disable) command, you will see the following
warning on the console: Ba... | [
{
"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 vmhost zeroize ztp-option-enable
user@device> request vmhost zeroize ztp-option secure-enable
request vmhost zeroize ztp-option secure-disable
user@device> request vmhost zeroize ztp-option secure-disable | Command introduced in Junos OS Release 23.4R1. | [
"Switching between Secure Zero Touch Provisioning and Zero Touch Provisioning"
] | |
request vmhost zeroize | request vmhost zeroize
<re0 | re1>
<routing-engine> | Use this command to remove all configuration information on the Routing Engines and reset all key
values. If the device has dual Routing Engines, the command is broadcast to both Routing Engines on the
device. As a result, both Routing Engines are zeroized. The command removes all data files, including
customized confi... | [
{
"name": "none",
"desc": "Remove all configuration information on all the Routing Engines and reset all key values."
},
{
"name": "re0 | re1",
"desc": "(Optional) Remove all configuration information on the Routing Engine in slot 0 (re0) or the Routing Engine in slot 1 (re1). NOTE: The QFX10002... | maintenance
Sample Output
request vmhost zeroize
user@host> request vmhost zeroize
VMHost Zeroization :
Erase all data, including configuration and log files?. In case of Dual RE system, both Routing
Engines will be zeroized [yes,no] (no) yes
re0:
---------------------------------------------------------------------... | Command introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] | |
request vpls-switchover | request vpls-switchover (instance | logical-system | neighbor | vpls-id) | Perform LDP VPLS pseudowire switchover. This provides a way to gracefully recover from pseudowire
failures in such a way that Layer 2 circuit and VPLS services can be restarted when an LDP session with
the remote PE router goes down. | [
{
"name": "instance",
"desc": "Name of the VPLS instance."
},
{
"name": "logical-system",
"desc": "Name of the logical system, or 'all'."
},
{
"name": "neighbor",
"desc": "IP address of the neighbor."
},
{
"name": "vpls-id",
"desc": "Layer 2 circuit ID."
}
] | view
Output Fields
When you enter this command, you are not provided feedback on the status of your request. You can
use the show vpls connections instance command to confirm the switchover.
Sample Output
request vpls-switchover vpls-id
user@host> request vpls-switchover instance VPLS_16040 vpls-id 16040 neighbor 101.... | Command introduced in Junos OS Release 9.2R1. | [
"Redundant Pseudowires for Layer 2 Circuits and VPLS"
] | |
request wlan access-point packet capture | request wlan access-point packet-capture start ap-name interface interface-name duration
duration filename capture-file sizefile-size-max promiscuous filter-mac mac-address | Capture the packets for the interfaces on wireless LAN interface Mini-PIM and to check whether the
packets are received from Wi-Fi interface and sent to JUNOS. In chassis cluster mode, packet capture
command is supported only on active wireless LAN interface. | [
{
"name": "start access-point name",
"desc": "Access point name to start the packet capture."
},
{
"name": "duration",
"desc": "Specify the capture duration. Range: 10 through 3600 seconds"
},
{
"name": "filename",
"desc": "Specify the captured filename."
},
{
"name": "filter... | view
WHAT'S NEXT
Sample Output
request wlan access-point packet capture
user@host> request wlan access-point packet-capture start filename wlan.pcap e09-22-ha-ap
interface Radio1VAP0 duration 10
Starting packet capture
Capture interface: Radio1VAP0
File : wlan.pcap
Duration : 10 seconds
File... | Command introduced in Junos OS release 20.3R1. | [
"Wi-Fi Mini-Physical Interface Module Overview",
"Configure Wi-Fi Mini-PIM"
] | |
request | request <access-security | ancp | chassis | debug | dhcp | dhcpv6 | extension-service | flight-
recorder | interface | ipsec | jdaf | jnu | l2circuit-switchover | lacp | message | mpls |
network-access | path-computation-client | pim | protection-group | routing-engine | security |
services | session | snmp | support... | Stop or reboot router components, switch between primary and backup components, display messages,
and display system information.
CAUTION: Halt the backup Routing Engine before you remove it or shut off the power
to the router; otherwise, you might need to reinstall the Junos OS.
NOTE: If your router contains two Routi... | [] | maintenance | Command introduced before Junos OS Release 7.4. | [
"Overview of Operational Mode Commands"
] | |
request-cache-timeout (RADIUS Snoop Segment) | request-cache-timeout timeout; | [edit access radius snoop-segments segment-name] | Configure the length of time to cache the accounting request that was snooped. If the same request is
received by the MX Series router within this time, the duplicate request is dropped. | [
{
"name": "timeout",
"desc": "Length of time, in seconds. Range: 1 through 30"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Snooping of RADIUS Accounting Requests for IP-Based Subscribers",
"Snooping RADIUS Accounting Requests for IP-Based Subscribers Overview",
"IP-Based Subscriber Setup Overview"
] |
request-chassis-fpc-optical-module-amplifier-chain-ila-soft-reset | request chassis optical-module amplifier-chain ila soft-reset fpc-slot fpc-slot ila ila-number | Apply a soft reset to the optical inline amplifier (ILA). The soft reset does not disrupt the network traffic. | [
{
"name": "fpc-slot",
"desc": "Slot number of the FPC or PIC in which the integrated photonic line card (IPLC) module resides."
},
{
"name": "ila-number",
"desc": "The number assigned to the optical ILA."
}
] | maintenance
Output Fields
When you enter the command, you are provided feedback on the status of your request.
Sample Output
request chassis fpc optical-module amplifier-chain ila soft-reset
user@host> request chassis fpc optical-module amplifier-chain ila soft-reset fpc-slot 3 ila-
number 0
Reset command... | Statement introduced in Junos OS Release 17.1R1. | [
"Integrated Photonic Line Card Base and Expansion Module Overview",
"Understanding the Integrated Photonic Line Card Architecture",
"Understanding How to Configure the Integrated Photonic Line Card"
] | |
request-max-tcp-connections (System Process) | request-max-tcp-connections max-tcp-connections; | [edit system processes dhcp-service] | Specify the number of simultaneous TCP connections that the DHCP relay can request when sending
bulk leasequery messages to DHCP servers. | [
{
"name": "max-tcp-connections",
"desc": "Number of simultaneous connections. Range: 1 through 10 Default: 3"
}
] | system—to view this statement in the configuration.
system-control—to add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring and Using DHCP Individual Leasequery",
"Configuring and Using DHCP Bulk Leasequery"
] |
request-rate (Access) | request-rate rate; | [edit access radius-options] | Configure the number of requests the router can send per second to all configured RADIUS servers
collectively. By limiting the flow of requests from the router to the RADIUS servers, you can prevent the
RADIUS servers from being flooded with requests. | [
{
"name": "rate",
"desc": "Number of requests per second."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"RADIUS Servers and Parameters for Subscriber Access"
] |
request-response | request-response {
grpc {
max-connections max-connections;
routing-instance routing-instance;
ssl {
address ip-address;
hot-reloading;
local-certificate (System) local-certificate;
mutual-authentication {
certificate-authority ... | [edit system services extension-service] | Allow request-response API execution.
Statements are explained separately. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
grpc option introduced in Junos OS Release 16.2. | [] |
request-system-integrity-attestation | request system integrity attestation (pcr-index pcr number | nonce-value | tpm-name) | The Attester is a device on the network that provides evidence to the Verifier on demand. The first part
of that evidence is a signed collection of the TPM's Platform Configuration Registers (PCRs) called a
TPM Quote. To ensure the freshness of the quote, the Verifier sends a random nonce to the Attester to
include in ... | [
{
"name": "nonce-value",
"desc": "Defines a base-64 encoded 20 byte random hex value. A cryptographically generated random number which should not be predictable prior to its issuance from a random number generation function. The random number MUST be derived from an entropy source external to the Attester.... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system integrity attestation nonce-value $NONCE tpm-name $SERIAL_NUMBER
user@host> request system integrity attestation nonce-value $NONCE tpm-name $SERIAL_NUMBER | Command introduced in Junos OS Release 22.4R1. | [] | |
request-system-integrity-log-retrieval | request system integrity log-retrieval log-type | The remaining evidence provided to the Verifier on demand is comprised of the boot event log recorded
by the TPM. The Verifier will compare this log against the TPM Quote for validity. If the log is valid, the
Verifier will check each entry in the log against a known-good entry. Note that as of this release, only
the b... | [
{
"name": "bios",
"desc": "Specifies an event type associated with BIOS/UEFI."
},
{
"name": "ima",
"desc": "Specifies an event type recorded in IMA."
},
{
"name": "netequip_boot",
"desc": "Specifies an event type associated with Network Equipment Boot."
}
] | view | Command introduced in Junos OS Release 22.4R1. | [] | |
request-timeout | request-timeout seconds; | [edit unified-edge diameter-profiles gx-profile profile-name] | Configure the time to wait for a response from the server. | [
{
"name": "seconds",
"desc": "Length of timeout interval. Range: 0 through 65,535 seconds. NOTE: 0 seconds indicates that the request timeout is not be enabled."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [] |
request-type | request-type (get-next-request | get-request | walk-request); | [edit snmp rmon alarm index] | Extend monitoring to a specific SNMP object instance (get-request), or extend monitoring to all object
instances belonging to a MIB branch (walk-request), or extend monitoring to the next object instance after
the instance specified in the configuration (get-next-request). | [
{
"name": "get-next-request",
"desc": "Performs an SNMP get next request."
},
{
"name": "get-request",
"desc": "Performs an SNMP get request."
},
{
"name": "walk-request",
"desc": "Performs an SNMP walk request."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Remote Nework Monitoring (RMON)",
"variable (SNMP RMON)"
] |
request-vmhost-power-cycle-cb | request vmhost power-cycle-cb | Initiates the power cycle for the Chassis. | [] | maintenance
Sample Output
request vmhost power-cycle-cb
user@host> request vmhost power-cycle-cb
Power cycle the Chassis/CB ? [yes,no] (no) yes
Initiating vmhost power-cycle-cb...
warning: Initiating Junos shutdown...
shutdown: [pid 14832]
... | [] | ||
request-vmhost-power-cycle-re | request vmhost power-cycle-re | Initiates the power cycle for the Routing Engine. | [] | maintenance
Sample Output
request vmhost power-cycle-re
user@host> request vmhost power-cycle-re
Power cycle the RE ? [yes,no] (no) yes
Initiating vmhost power-cycle...
warning: Initiating Junos shutdown...
shutdown: [pid 20669]
*** FINA... | Statement introduced in Junos OS Release 22.1R1 | [] | |
requested-ip-network-match (DHCP Local Server) | requested-ip-network-match subnet-mask; | [edit system services dhcp-local-server],
[edit system services dhcp-local-server dhcpv6],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server ...],
[edit logical-systems logical-system-name system services dhcp-local-server ...],
[edit routing-instances ... | Configure the subnet to which the DHCP local server matches the requested IP address (IPv6 address
for DHCPv6 local server). The server accepts and uses the active client’s requested address for address
assignment only when the requested address and the IP address of the DHCP server interface (or IPv6
address of the DH... | [
{
"name": "subnet-mask",
"desc": "Length of the subnet mask. Range:"
},
{
"name": "DHCP: 0 through 31",
"desc": ""
},
{
"name": "DHCPv6: 0 through 127",
"desc": "Default:"
},
{
"name": "DHCP: 8",
"desc": ""
},
{
"name": "DHCPv6: 16",
"desc": ""
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Specifying the Subnet for DHCP Client Address Assignment"
] |
required-depth | required-depth number; | [edit interfaces interface-name atm-options mpls pop-all-labels],
[edit interfaces interface-name fastether-options mpls pop-all-labels],
[edit interfaces interface-name gigether-options mpls pop-all-labels],
[edit interfaces interface-name sonet-options mpls pop-all-labels] | For passive monitoring on ATM, SONET/SDH, Fast Ethernet, and Gigabit Ethernet interfaces only,
specify the number of MPLS labels an incoming packet must have for the pop-all-labels statement to
take effect. For passive monitoring on the MX304 router, MX Series routers with MPCs, and MX series
routers with the LC9600 li... | [
{
"name": "number",
"desc": "Number of MPLS labels on incoming IP packets."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Passive Flow Monitoring for MPLS Encapsulated Packets",
"Interfaces Fundamentals for Junos OS"
] |
reroute-address | reroute-address {
inet address | inet6 address);
} | [edit forwarding-options evpn-vxlan] | Enable fast reroute egress link protection (ELP) on provider edge (PE) devices for access links to
multihomed customer edge (CE) devices in an EVPN-VXLAN fabric. This feature helps to minimize load-
balanced traffic loss when the link from a PE device to a multihomed CE device goes down.
Remote sources load balance tra... | [
{
"name": "inet address",
"desc": "Specify the IPv4 address for an ELP reroute tunnel."
},
{
"name": "inet6 address",
"desc": "Specify the IPv6 address for an ELP reroute tunnel."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3R1. | [
"Fast Reroute for Egress Link Protection with EVPN-VXLAN Multihoming"
] |
reserve ingress-egress-mcast | reserve ingress-egress-mcast <percentage>; | [edit system packet-forwarding-options internal-forwarding-bandwidth] | You can configure the bandwidth of the recycle interface to enable a percentage of the recycle interface
bandwidth for ingress-egress multicast replication.
The following is an example of multicast replication bandwidth calculation:
internal-forwarding-bandwidth = 100Gbps
Reserved ingress-egress-multicast = 40% means
... | [
{
"name": "percentage",
"desc": "Recycle interface bandwidth percentage. Range: 1 through 100 % Default: 100%"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 21.4R1. | [
"Ingress and Egress Multicast Replication using Recycle Replication Model"
] |
reserved (Security IDP Custom Attack) | reserved {
match (equal | greater-than | less-than | not-equal);
value reserved-value;
} | [edit security idp custom-attack ipv4_custom attack-type signature protocol tcp] | Specify the three reserved bits in the TCP header field. | [
{
"name": "value",
"desc": "Match a decimal value. Range: 0 through 7"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
reserved-bandwidth | reserved-bandwidth {
express percentage;
gbr percentage;
} | [edit services mobile-edge gateways saegw system class-of-service] | Reserve a fraction of the system’s bandwidth for the express and guaranteed bit rate forwarding queues
on the virtual routing and forwarding loopback interface on the anchor Packet Forwarding Engine. The
system reserves the same fraction of bandwidth across all anchor Packet Forwarding Engines.
This configuration does ... | [
{
"name": "express",
"desc": ""
},
{
"name": "percentage",
"desc": "Specify the percentage of bandwidth to be reserved for the express queue. Range: 1 through 100 Default: 2"
},
{
"name": "gbr percentage",
"desc": "Specify the percentage of bandwidth to be reserved for each guarant... | system | Juniper Networks introduced this statement in Junos OS Release 22.2R1. | [] |
reset (Security IDP) | reset; | [edit security idp custom-attack attack-name attack-type chain] | Select reset if the compound attack should be matched more than once within a single session or
transaction. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
reset-count | reset-count reset-count; | [edit chassis fabric-card] | Number of times sib can be reset by cmerror | [
{
"name": "reset-count",
"desc": "Range: 1 to 10"
}
] | Statement introduced in Junos OS Release 24.4R1. | [] | |
reset-tracking-bit | reset-tracking-bit; | [edit protocols pim],
[edit protocols pim interface (Protocols PIM) interface-name],
[edit routing-instances routing-instance-name protocols pim],
[edit routing-instances routing-instance-name protocols pim interface (Protocols PIM) interface-
name],
[edit logical-systems logical-system-name protocols pim],
[edit log... | Change the value of a tracking bit (T-bit) field in the LAN prune delay hello option from the default of 1
to 0, which enables join suppression for a multicast interface. When the network starts receiving
multiple identical join messages, join suppression triggers a random timer with a value of 66 through 84
millisecon... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Example: Enabling Join Suppression"
] |
resignal-minimum-bandwidth | resignal-minimum-bandwidth; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name auto-
bandwidth],
[edit protocols mpls label-switched-path lsp-name auto-bandwidth] | Resignal the LSP using the configured minimum bandwidth when an LSP comes back up after going
down. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Automatic Bandwidth Allocation for LSPs"
] |
resiliency | resiliency {
exceptions {
forwarding;
os;
routing;
}
store {
database;
file name {
files number;
(no-world-readable | world-readable);
size size;
}
fwding-file name{
files number;
(no-world-readable | world-readable);
... | [edit system] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1 for MX Series routers.
Statement introduced in Junos Evolved OS Release 22.2R1 for PTX Series routers. | [
"Juniper Resiliency Interface"
] |
resilient-hash | resilient-hash; | [edit interfaces aex aggregated-ether-options]] | Enable resilient hashing for a LAG to minimize remapping of destination paths. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Use of Resillient Hashing to Minimize Flow Remapping"
] |
resize (Ephemeral Database) | resize {
database-size-diff size MB;
database-size-on-disk size MB;
} | [edit system configuration-database ephemeral instance instance-name] | Resize the ephemeral instance's configuration database. The system resizes the database during the
commit operation when it meets the criteria in both the database-size-diff and database-size-on-disk
statements. The system displays Database resize completed after it successfully resizes the configuration
database.
A re... | [
{
"name": "none",
"desc": "Enable database resizing and use the default values for the database-size-diff and database-size-on-disk statements."
},
{
"name": "database-size-diff",
"desc": ""
},
{
"name": "size",
"desc": "Specify the minimum difference between the database size and th... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Managing Ephemeral Configuration Database Space"
] |
resize-ephemeral-default | resize-ephemeral-default {
database-size-diff size MB;
database-size-on-disk size MB;
} | [edit system configuration-database ephemeral] | Resize the default ephemeral configuration database. The system resizes the database during the
commit operation when it meets the criteria in both the database-size-diff and database-size-on-disk
statements. The system displays Database resize completed after it successfully resizes the configuration
database.
A resiz... | [
{
"name": "none",
"desc": "Enable database resizing and use the default values for the database-size-diff and database-size-on-disk statements."
},
{
"name": "database-size-diff",
"desc": ""
},
{
"name": "size",
"desc": "Specify the minimum difference between the database size and th... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Managing Ephemeral Configuration Database Space"
] |
resolution | resolution {
(preserve-nexthop-hierarchy | no-preserve-nexthop-hierarchy);
rib routing-table-name {
import [ policy-names ];
inet-import [ policy-names ];
inet-resolution-ribs [ routing-table-names ];
inet6-import [ policy-names ];
inet6-resolution-ribs [ routing-table-n... | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | Configure the router to perform custom route resolution on protocol next hops of routes in a certain
routing table. The protocol next hop is used to determine the forwarding next hop.
For example, you might want to direct inet.2 route resolution to use topology routing tables :red.inet.0
and :blue.inet.0 for protocol n... | [
{
"name": "disable-auto-resolve-on-scheme-changes",
"desc": "(Optional) Service routes are not re-resolved automatically when resolution schemes are created, deleted, or changed. However, you can manually trigger route re-resolution on resolution scheme changes."
},
{
"name": "inet-import [ policy-n... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
inet6-import and inet6-resolution-ribs options added in Junos OS Release 17.2R1. | [
"Example: Configuring Route Resolution on PE Routers",
"Example: Configuring Route Resolution on Route Reflectors",
"Understanding Multitopology Routing in Conjunction with PIM",
"Example: Configuring Multitopology Routing to Provide Redundancy for Multicast Traffic over",
"Separate Network Paths"
] |
resolution-map | resolution-map name {
mode (color-only | ip-color);
} | [edit logical-systems name policy-options],
[edit policy-options] | Define a set of protocol next hop resolution modes.
A resolution-map can be referred by a new resolution-map action of a policy statement, which is in turn
applied to a VPN service through the routing-instance import-vrf. A given resolution-map may be shared
by multiple policy-statements. | [
{
"name": "name",
"desc": "Resolution Map name."
},
{
"name": "mode",
"desc": "List of resolution modes in order that defines fallback mechanism. Values:"
},
{
"name": "color-only",
"desc": "Color-only protocol next hop resolution mode."
},
{
"name": "ip-color",
"desc": ... | routing | Statement introduced in Junos OS Release 19.2R1-S1. | [
"Color-Based Mapping of VPN Services Overview",
"Static Segment Routing Label Switched Path"
] |
resolution-ribs | resolution-ribs [ routing-table-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options resolution rib],
[edit logical-systems logical-system-name routing-options resolution rib],
[edit routing-instances routing-instance-name routing-options resolution rib],
[edit routing-options resolution rib] | Specify one or more routing tables to use for route resolution.
This statement enables you to override the default routing tables that Junos OS uses for route
resolution. For example, suppose that the resolution routing table is inet.3, but you want to allow
fallback resolution through inet.0. One example use case is ... | [
{
"name": "routing-table-names",
"desc": "Name of one or more routing tables."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring Route Resolution on PE Routers",
"Example: Configuring Multitopology Routing to Provide Redundancy for Multicast Traffic over",
"Separate Network Paths",
"Understanding Multitopology Routing in Conjunction with PIM"
] |
resolve | resolve; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name static (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options static (defaults | route)],
[edit logical-systems logical-system-name r... | Statically configure routes to be resolved to a next hop that is not directly connected. The route is
resolved through the inet.0 and inet.3 routing tables.
NOTE: You cannot configure both resolve and retain options for a statically configured
route because resolved next hops cannot be retained.
Default
Static routes c... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
resolve-vpn | resolve-vpn; | [edit logical-systems logical-system-name protocols bgp family inet labeled-unicast],
[edit logical-systems logical-system-name protocols bgp group group-name family inet labeled-
unicast],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address
family inet labeled-unicast],
[edit log... | Allow labeled routes to be placed in the inet.3 routing table for route resolution. These routes are then
resolved for PE router connections where the remote PE is located across another AS. For a PE router to
install a route in the VRF, the next hop must resolve to a route stored within the inet.3 table. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding Multiprotocol BGP"
] |
resource (Analytics) | resource {
interfaces {
interface-name {
resource-profile profile-name;
}
}
system {
polling-interval {
queue-monitoring interval;
traffic-monitoring interval;
}
resource-profile profile-name;
}
} | [edit services analytics] | Configure network analytics resources such as resource profiles (for interfaces and system), and polling
intervals (for queue and traffic monitoring).
NOTE: The resource statement is not available in Junos OS Releases prior to 13.2X51-
D15.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Network Analytics Overview"
] |
resource (Interfaces) | resource number; | [edit interfaces interface-name radio-router] | This option controls the resource weight (value 1–100). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"PPPoE-Based Radio-to-Router Protocols Overview"
] |
resource-category jtree (Resource Monitor) | resource-category jtree {
resource-type (contiguous-pages | free-dwords | free-pages) {
low-watermark number;
high-watermark number;
}
} | [edit system services resource-monitor] | Define the resource category that you want to monitor and analyze for ensuring system stability,
especially the health and operating efficiency of I-chip-based line cards and Trio-based FPCs on MX
Series routers. The resource category includes detailed CPU utilization, session rate, and session count
statistics. You us... | [
{
"name": "jtree",
"desc": "Specify the Jtree resource category for which you want to monitor the health (working condition), operating efficiency, traffic-handling capacity, and performance status."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Diagnosing and Debugging System Performance by Configuring Memory Resource Usage Monitoring",
"on MX Series Routers"
] |
resource-cleanup | resource-cleanup {
disable;
traceoptions {
file filename files number match regex size size (world-readable | no-world-readable);
flag flag;
level level;
no-remote-trace;
}
} | [edit system processes] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "disable",
"desc": "Disable the resource cleanup process."
}
] | trace—To view this statement in the configuration.
trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
resource-list (Network Management) | resource-list resource-list-name resource-names <all-resources> / <ecmp-group> <ecmp-
member> <efp> <egress-l3-interface> <host-ipv4> <host-ipv6> <ifp> <l3-next-hop> <lpm-ipv4> <lpm-
ipv6-128> <lpm-ipv6-64> <mac> <mpls-ingress> <mpls-swap> <tunnel> <vfp> <vport> <L3_IPMC Table>
<Ingress VLAN XLATE(ING_VLAN_XLATE)> <Eg... | [edit system packet-forwarding-options hw-resource-monitor] | Create a resource list to monitor hardware resource utilization. You can configure multiple resource lists,
but the same resource can only be used once and cannot be duplicated on multiple resource lists.
Configure a resource list with multiple resource names, each resource name separated by a space. To
add all availab... | [
{
"name": "resource-list-name",
"desc": "The name of the resource list."
},
{
"name": "resource-names",
"desc": "The list of resources to monitor."
},
{
"name": "all-resources",
"desc": "All applicable hardware resources."
},
{
"name": "ecmp-group",
"desc": "Equal Cost Mu... | edit | Statement introduced in Junos OS Release 24.2R1. | [
"Hardware Resource Threshold Monitoring"
] |
resource-list (Telemetry) | resource-list {ecmp-group-table | ecmp-member-table | efp | egress-l3-interface | host-ipv4 |
host-ipv6 | ifp | l3-next-hop | lpm-table-ipv4 | lpm-table-ipv6-128 | lpm-table-ipv6-64 | mpls-
ingress-table | mpls-table-swap | tunnel-table | vfp | vport} | [edit forwarding-options pfe-sensor npu-memory],
[edit logical-systems name routing-instances name forwarding-options pfe-sensor npu-memory],
[edit logical-systems name tenants name routing-instances name forwarding-options pfe-sensor npu-
memory],
[edit routing-instances name forwarding-options pfe-sensor npu-memory],... | Specify a list of resources to monitor and export for Packet Forwarding Engine sensors. If you do not
include the resource-list statement, information for all active groups in the system is exported. To see a
list of groups, use the show pfe filter hw summary command.
Export group information to a collector by includin... | [
{
"name": "ecmp-group-table",
"desc": "Retrieve equal-cost multipath (ECMP) group table information."
},
{
"name": "ecmp-member-table",
"desc": "Retrieve ECMP member table information."
},
{
"name": "efp",
"desc": "Retrieve egress filter information."
},
{
"name": "egress-l3-... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
resource-manager (Forwarding-options) | resource-manager {
cpu {
re re;
}
enhanced-logging;
} | [edit security forwarding-options] | Manage the resources for special usage. | [
{
"name": "cpu",
"desc": "Configure CPU resources."
},
{
"name": "enhanced-logging",
"desc": "Configure a dedicated CPU resource for on-box logging on SRX4600."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | enhanced-logging option introduced to assign dedicated CPU resource for on-box logging on SRX4600 in
Junos OS Release 23.1R1.
From Junos OS Release 25.2R1, when you launch vSRX 3.0 instances with even numbers of CPU cores
configured, then by default two CPU cores are allocated to the Routing Engine. This allocation en... | [] |
resource-manager | resource-manager {
traceoptions (Security) {
flag flag;
}
} | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced before Junos OS Release 12.1. | [
"Understanding Traffic Processing on Security Devices"
] |
resource-monitor | resource-monitor {
free-fw-memory-watermark number;
free-heap-memory-watermark number;
free-nh-memory-watermark number;
high-cos-queue-threshold number;
high-threshold number;
no-logging;
no-throttle;
resource-category jtree {
resource-type (contiguous-pages | free-dwords | free-... | [edit system services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1.
high-cos-queue-threshold option introduced in Junos OS Release 17.4R1. | [
"Diagnosing and Debugging System Performance by Configuring Memory Resource Usage Monitoring",
"on MX Series Routers",
"Resource Monitoring for Subscriber Management and Services",
"Resource Monitoring Usage Computation Overview",
"Limiting Subscribers by Client Type and Hardware Element with Resource Monit... |
resource-profiles (Analytics) | resource-profiles {
profile-name {
depth-threshold {
high number;
low number;
}
latency-threshold {
high number;
low number;
}
no-queue-monitoring;
no-traffic-monitoring;
queue-monitoring;
traffic-monitor... | [edit services analytics] | Configure resource profiles that are used as templates for specifying network analytics parameters. You
use resource profiles to enable and disable queue and traffic monitoring, and specify depth and latency
thresholds as applicable. Once you have defined a resource profile, you can apply it specifically to
individual ... | [
{
"name": "profile-name",
"desc": "Specify a name for the resource profile."
},
{
"name": "no-queue-monitoring",
"desc": "Disable queue monitoring."
},
{
"name": "no-traffic-monitoring",
"desc": "Disable traffic monitoring."
},
{
"name": "queue-monitoring",
"desc": "Enabl... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Network Analytics Overview"
] |
resource-watch | resource-watch {
cpu-statistics;
junos-statistics;
orange-zone-enable;
orange-zone-threshold;
red-zone-cpu-threshold;
red-zone-enable;
red-zone-jkl-threshold;
red-zone-snmp-enable;
resource-watch-enable;
} | [edit chassis] | In SRX chassis cluster mode, split brain caused by redundant failover is triggered due to Routing Engine
busy related to CPU overhead causing SRX HA cluster resiliency. To analyze CPU load, Reswatchd is a
process running on Linux, Routing Engine3, and Routing Engine2 to collect and monitor the resource
usage data. You ... | [
{
"name": "cpu-statistics",
"desc": "Display CPU load statistics report. When enable CPU statistics, reswatchd logs CPU idle values /var/log/reswatch_CPU_statistics_[1-5] in .csv format. Range: 0-604800 seconds. Values:"
},
{
"name": "0",
"desc": "Disable"
},
{
"name": "junos-statistic... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS release 20.4R1. | [] |
resources | resources {
node-group node-group-name {
network-domain;
node-device node-device-name;
}
} | [edit fabric] | (QFabric systems only) Define resources within a QFabric system and handle a variety of component
assignments.
The remaining statements are explained separately. See CLI Explorer. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [
"Configuring Node Groups for the QFabric System",
"Understanding Node Groups"
] |
respond-bad-spi (Services IKE Policy) | respond-bad-spi max-responses; | [edit services ipsec-vpn ike policy] | Enable response to invalid IPsec Security Parameter Index (SPI) values. If the security associations (SAs)
between two peers of an IPsec VPN become unsynchronized, the device resets the state of a peer so
that the two peers are synchronized. | [
{
"name": "max-responses",
"desc": "Number of times to respond to invalid SPI values per gateway. Range: 1 through 30 Default: 5"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring IKE Policies"
] |
responder (performance-monitoring) | responder {
delay {
min-query-interval milliseconds;
}
loss {
min-query-interval milliseconds;
}
} | [edit protocols mpls oam performance-monitoring],
[edit protocols mpls label-switched-path lsp-name oam performance-monitoring],
[edit protocols mpls label-switched-path lsp-name primary path-name oam performance-monitoring],
[edit protocols mpls label-switched-path lsp-name secondary path-name oam performance-monitori... | Configure responder options.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Pro-Active Loss and Delay Measurements",
"On-Demand Packet Loss and Delay Measurement for UHP LSPs Overview"
] |
response-cache-timeout (RADIUS Client) | response-cache-timeout seconds; | [edit access radius clients client-name accounting] | Configure the timeout for the RADIUS response cache. This timeout indicates how long to store the
RADIUS response messages (sent for request messages) in the MX Series router response cache. | [
{
"name": "seconds",
"desc": "Length of timeout interval. Range: 5 through 20 seconds Default: 15 seconds"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring RADIUS Clients That Send Accounting Requests for IP-Based Subscribers"
] |
rest | rest {
control {
allowed-sources [ value-list ];
connection-limit limit;
}
enable-explorer;
http {
addresses [ address-list ];
port port-number;
}
https {
addresses [ address-list ];
cipher-list [cipher-1 cipher-2 cipher-3 ... ];
mutual-aut... | [edit system services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "routing-instance",
"desc": ""
},
{
"name": "routing-instance",
"desc": "Specify the routing instance through which the remote server is reachable. This can be the non-default management instance mgmt_junos or a user-defined non-default routing instance. If you do not specify a routing... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2.
routing-instance option introduced in Junos OS Release 20.3R1. | [
"Management Interface in a Non-Default Instance"
] |
restart (JDM) | restart (gracefully | immediately | soft)
<jdmd>
<jdmmon>
<jinventoryd>
<jlinkmon> | Restart daemons belonging to Juniper Device Manager (JDM).
CAUTION: Never restart a software process unless instructed to do so by a customer
support engineer.
NOTE: Starting in Junos OS Release 19.2R1, JDM does not support the jinventoryd
option in the restart command. | [
{
"name": "gracefully",
"desc": "(Optional) Restart a specified module or component by sending the equivalent of a UNIX SIGTERM signal."
},
{
"name": "immediately",
"desc": "(Optional) Immediately restart a module or component by sending the equivalent of a UNIX SIGKILL signal."
},
{
"na... | Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
restart jdmd gracefully
user@jdm> restart jdmd gracefully
Juniper Device Manager service process started, pid 12058 | Command introduced in Junos OS Release 17.4R1. | [
"Generic Guidelines for Using JDM Server Commands"
] | |
restart (Junos OS Evolved) | restart application-name
<gracefully | immediately | soft> | Restart a Junos OS Evolved process.
CAUTION: Never restart a software process unless instructed to do so by a customer
support engineer. A restart might cause the router or switch to drop calls and interrupt
transmission, resulting in possible loss of data.
For Junos OS Evolved, the restart command also triggers a rest... | [
{
"name": "application-name",
"desc": "Specify the name of the application you want to restart. Use the show system applications operational mode command for information about what applications are running."
},
{
"name": "none",
"desc": "Same as gracefully."
},
{
"name": "gracefully",
... | reset
Output Fields
When you enter this command, the system provides feedback on the status of your request.
Sample Output
restart interface-control (Junos OS Evolved)
user@host> restart interface-control
interface-control restart requested
Restarted aggd on re0
Restarted ifmand on re0 | Introduced in Junos OS Evolved Release 19.1R1. | [] | |
restart chassis-control | restart chassis-control
<all-chassis | all-lcc | all-sfc | lcc number | sfc number>
<gracefully | immediately | soft> | Restart the chassis management process.
NOTE: When GRES is configured and the restart chassis-control command is executed on
a TX Matrix Plus router with 3D SIBs, we cannot ascertain which Routing Engine
becomes a primary. This is due to the chassisd restart. The chassis process or chassisd is
responsible for maintain... | [
{
"name": "lcc number",
"desc": "(Routing matrix only) (Optional) Restart the software process for a specific routing node that is connected to a PTX Matrix platform. Replace number with a value from 0 through 3."
},
{
"name": "sfc number",
"desc": "(PTX routers only) (Optional) Restart the soft... | reset
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
restart chassis-control gracefully
user@host> restart chassis-control gracefully
Chassis control process started, pid 1631
restart chassis-control soft
user@host> restart chassis-control soft
Chass... | Command introduced before JUNOS Release 7.4.
Command added in Junos Evolved Release 21.4R1. | [] | |
restart extensible-subscriber-services | restart extensible-subscriber-services | Restart essmd. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
Sample Output
command-name
# restart extensible-subscriber-services | Command introduced in Junos OS Release 15.1. | [] | |
restart | restart
<adaptive-services | audit-process | chassis-control | class-of-service | dialer-services |
diameter-service | dlsw | ethernet-connectivity | event-processing | fibre-channel | firewall |
general-authentication-service | igmp-host-services | interface-control | ipsec-key-management |
isdn-signaling | l2ald ... | Restart a Junos OS process.
CAUTION: Never restart a software process unless instructed to do so by a customer
support engineer. A restart might cause the router or switch to drop calls and interrupt
transmission, resulting in possible loss of data.
The restart command expands all applications names including applicati... | [
{
"name": "none",
"desc": "Same as gracefully."
},
{
"name": "adaptive-services",
"desc": "(Optional) Restart the configuration management process that manages the configuration for stateful firewall, Network Address Translation (NAT), intrusion detection services (IDS), and IP Security (IPsec) ... | reset
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
restart interfaces
user@host> restart interfaces
interfaces process terminated
interfaces process restarted
restart interface-control gracefully
user@host> restart interface-control grac... | Command introduced before Junos OS Release 7.4.
Options added:
•
dynamic-flow-capture in Junos OS Release 7.4.
•
dlsw in Junos OS Release 7.5.
•
event-processing in Junos OS Release 7.5.
•
ppp in Junos OS Release 7.5.
•
l2ald in Junos OS Release 8.0.
•
link-management in Junos Release 8.0.
•
pgcp-service in Junos OS Re... | [
"Overview of Operational Mode Commands"
] | |
restart-duration (Multicast Snooping) | restart-duration seconds; | [edit multicast-snooping-options graceful-restart] | Configure the duration of the graceful restart interval. | [
{
"name": "seconds",
"desc": "Graceful restart duration for multicast snooping."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Example: Configuring Multicast Snooping"
] |
restart-duration (Protocols) | restart-duration seconds; | [edit logical-systems logical-system-name protocols (isis | ospf | ospf3 | pim) graceful-restart],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3 | pim) graceful-restart],
[edit protocols (esis | isis | ospf | ospf3 | pim) graceful-restart],
[edit routing-inst... | Configure the grace period for graceful restart globally.
Additionally, you can individually configure the duration of the graceful restart period for the End
System-to-Intermediate System (ES-IS), Intermediate System-to-Intermediate System (IS-IS), Open
Shortest Path First (OSPF), and OSPFv3 protocols and for Protocol... | [
{
"name": "seconds",
"desc": "Time for the graceful restart period."
},
{
"name": "a particular protocol:",
"desc": ""
},
{
"name": "[edit routing-options graceful-restart] (global setting)",
"desc": "120 through 900"
},
{
"name": "ES-IS",
"desc": "30 through 300"
},
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Enabling Graceful Restart",
"Configuring Graceful Restart for MPLS-Related Protocols",
"Configuring VPN Graceful Restart",
"Configuring Graceful Restart for VPNs",
"Configuring Logical System Graceful Restart",
"Configuring PIM Sparse Mode Graceful Restart"
] |
restart-duration (Routing Options) | restart-duration seconds; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options
graceful-restart],
[edit logical-systems logical-system-name routing-options graceful-restart],
[edit routing-instances routing-instance-name routing-options graceful-restart],
[edit routing-options graceful-restart] | Configure the restart timer for graceful restart. | [
{
"name": "seconds",
"desc": "Configure the time period for the restart to last."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Junos OS High Availability User Guide"
] |
restart-path | restart-path (all | create | echo); | [edit security gtp profile profile-name] | Use the restart-path function to restart a GTP path. By default, the restart path is disabled and then
related function does not work. Tunnels are not deleted when restart counter changes.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp profile profile-name] hierarchy level is
replaced by [edit securi... | [
{
"name": "all",
"desc": "Restart GTP paths by detecting the changed restart number obtained from the Recovery"
},
{
"name": "create",
"desc": "Restart GTP paths by detecting the changed restart number obtained from the Recovery IE"
},
{
"name": "echo",
"desc": "Restart GTP paths by ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. Support. | [
"Understanding GTP Path Restart",
"Example: Restarting a GTPv2 Path"
] |
restart-time (BGP Graceful Restart) | restart-time seconds; | [edit protocols (bgp | rip | ripng) graceful-restart],
[edit logical-systems logical-system-name protocols (bgp | rip | ripng) graceful-restart (Enabling
Globally)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp
graceful-restart],
[edit routing-instances routing-insta... | Configure the duration of the BGP, RIP, or next-generation RIP (RIPng) graceful restart period. | [
{
"name": "seconds",
"desc": "Length of time for the graceful restart period."
},
{
"name": "BGP",
"desc": "1 through 1800 seconds"
},
{
"name": "RIP",
"desc": "1 through 600 seconds"
},
{
"name": "BGP",
"desc": "120 seconds"
},
{
"name": "RIP and RIPng",
"des... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring Graceful Restart Options for BGP",
"Configuring Graceful Restart Options for RIP and RIPng",
"Configuring Graceful Restart for QFabric Systems"
] |
restart-time (Fabric Control) | restart-time seconds; | [edit fabric protocols fabric-control graceful-restart] | Configure the duration of the graceful restart period for the fabric control Routing Engine.
The graceful restart resynchronization process takes longer when the QFabric system contains node
groups that have a large number of VLANs. The graceful-restart duration should, therefore, be set higher
when the QFabric system ... | [
{
"name": "seconds",
"desc": "Duration of the graceful restart period. Default: 300 seconds Range: 300 to 900 seconds"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X52-D10. | [
"Understanding Bridging and VLANs on Switches",
"Understanding Routing Engines in the QFabric System"
] |
restarter (Graceful Restart for BGP Restarter) | restarter {
disable;
stale-time interval;
} | [edit logical-systems logical-system-name protocols bgp family (l2vpn | route-target | inet)
(labeled-unicast | flow) graceful-restart long-lived],
[edit logical-systems logical-system-name protocols bgp group group-name family (l2vpn | route-
target | inet) (labeled-unicast | flow) graceful-restart long-lived],
[edit... | Configure the long-lived graceful restart mechanism for a BGP restarter router to preserve BGP routing
details for a longer period from a failed BGP peer. You can also configure the BGP long-lived graceful
restarter mode negotiation mechanism for a particular address family instead of configuring this
capability for al... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Graceful Restart Options for BGP",
"Junos OS High Availability User Guide"
] |
restore-interval | restore-interval number; | [edit protocols protection-group ethernet-ring ring-name] | Configures the number of minutes that the node does not process any Ethernet ring protection (ERP)
protocol data units (PDUs).. This configuration is a global configuration and applies to all Ethernet rings if
the Ethernet ring does not have a more specific configuration for this value. If no parameter is
configured at... | [
{
"name": "number",
"desc": "Specify the restore interval."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches. | [
"Ethernet Ring Protection Switching Overview",
"Example: Configuring Ethernet Ring Protection Switching on EX Series Switches",
"Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches",
"Supporting ELS",
"Configuring Ethernet Ring Protection Switching on Switches (CLI P... |
restricted-queues | restricted-queues {
forwarding-class class-name queue queue-number;
} | [edit class-of-service] | For M320, MX Series, T Series routers and EX Series switches only, map forwarding classes to restricted
queues.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
retain | (no-retain | retain); | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name static (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options static (defaults | route)],
[edit logical-systems logical-system-name r... | Configure statically configured routes to be deleted from or retained in the forwarding table when the
routing protocol process shuts down normally.
NOTE: You cannot configure both retain and resolve options for a statically configured
route because resolved next hops cannot be retained.
Default
Statically configured ... | [
{
"name": "no-retain",
"desc": "Delete statically configured routes from the forwarding table when the routing protocol process shuts down normally. To explicitly specify that routes be deleted from the forwarding table, include the no-retain statement. Include this statement when configuring an individual ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
retain-hold-resource | retain-hold-resource; | [edit logical-systems name security alg sip (Security)],
[edit logical-systems name tenants name security alg sip (Security)],
[edit security alg sip (Security)],
[edit services alg sip (Security)],
[edit tenants name security alg sip (Security)] | Configure retain-hold-resource to enable the device to not to free media resources for a Session
Initiation Protocol (SIP) Application Layer Gateway (ALG), even when a media stream is placed on hold.
By default, media stream resources are released when the media stream is held. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
reth-count (Chassis Cluster) | reth-count number; | [edit chassis cluster] | Specify the number of redundant Ethernet (reth) interfaces allowed in the chassis cluster. You need to
specify the total number of interfaces in the chassis cluster before redundant Ethernet interfaces are
created. For example, the set chassis cluster reth-count 2 allow you to create two reth interfaces
(example: reth... | [
{
"name": "number",
"desc": "Number of redundant Ethernet interfaces allowed."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [] |
retransmission-attempt (DHCP Client) | retransmission-attempts number; | [edit interfaces interface-name unit logical-unit-number family family dhcp-client] | Specify the number of times the device attempts to retransmit a Dynamic Host Control Protocol (DHCP)
packet fallback. | [
{
"name": "number",
"desc": "Number of retransmit attempts. Range:"
},
{
"name": "For IPv4",
"desc": "0 through 50000 from Junos OS Release 17.3R1 onwards and 0 through 6 on Junos"
},
{
"name": "For IPv6",
"desc": "0 through 9."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10.
Starting with Junos OS Release 17.3R1, on all SRX Series Firewalls and vSRX Virtual Firewall instances,
the CLI option dhcp-clinet at [edit interfaces interface-name unit logical-unit-number family inet] hierarchy is
changed to dhcp to keep consistent with other Ju... | [
"Understanding DHCP Client Operation",
"Minimum DHCP Client Configuration"
] |
retransmission-attempt (DHCPv6 Client) | retransmission-attempt number; | [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet6 dhcpv6-client]
[edit tenants tenant-name interfaces interface-name unit logical-unit-number family inet6 dhcpv6-
client] | Specify the number of times the device retransmits a DHCPv6 client packet if a DHCPv6 server fails to
respond. After the specified number of attempts, no further attempts at reaching a server are made. | [
{
"name": "number",
"desc": "Number of retransmit attempts. Range: 0 through 50000 (from Junos OS Release 20.3R1 onwards) Range: 0 through 9"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10.
The logical-systems and tenants options are introduced in Junos OS Release 18.4R1. | [] |
retransmission-count-established (L2TP) | retransmission-count-established count; | [edit services l2tp tunnel] | Set the maximum number of times control messages are retransmitted for established tunnels.
BEST PRACTICE: Before you downgrade to a Junos OS Release that does not support
this statement, unconfigure the statement by issuing no services l2tp tunnel retransmission-
count-established. | [
{
"name": "count",
"desc": "Number of retransmissions."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"L2TP for Subscriber Access Overview",
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces"
] |
retransmission-count-not-established (L2TP) | retransmission-count-not-established count; | [edit services l2tp tunnel] | Set the maximum number of times control messages are retransmitted for tunnels that are not
established.
BEST PRACTICE: Before you downgrade to a Junos OS Release that does not support
this statement, unconfigure the statement by issuing no services l2tp tunnel retransmission-
count-not-established. | [
{
"name": "count",
"desc": "Number or retransmissions."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"L2TP for Subscriber Access Overview",
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces"
] |
retransmission-interval (DHCP Client) | retransmission-interval seconds; | [edit interfaces interface-name unit logical-unit-number family family dhcp-client] | Specify the initial retransmission interval. Successive retransmission intervals are doubled as per
RFC2131.
NOTE: Though the SRX Series Firewalls implement the exponential backoff, as described
in RFC 2131, the retransmit attempt does not stop when the retransmission interval
reaches 64 seconds. The packet is transmit... | [
{
"name": "seconds",
"desc": "Number of seconds before initial retransmission. Range: The range is 4 through 64. The default is 4 seconds."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10.
Starting with Junos OS Release 17.3R1, on all SRX Series Firewalls and vSRX Virtual Firewall instances,
the CLI option dhcp-clinet at [edit interfaces interface-name unit logical-unit-number family inet] hierarchy is
changed to dhcp to keep consistent with other Jun... | [
"Understanding DHCPv6 Client and Server Identification"
] |
retransmission-interval (DHCP) | retransmission-interval seconds; | [edit interfaces interface-name unit logical-unit-number family inet dhcp] | Specify the time between successive retransmissions of the client DHCP request if a DHCP server fails
to respond. | [
{
"name": "seconds",
"desc": "Number of seconds between successive retransmissions. Range: 4 through 64 seconds Default: 4 seconds"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring a DHCP Client"
] |
retransmission-interval | retransmission-interval milliseconds; | [edit logical-systems logical-system-name protocols link-management peer peer-name lmp-protocol],
[edit protocols link-management peer peer-name lmp-protocol] | Specify how often Link Management Protocol (LMP) sends Config and LinkSummary messages on the
LMP control channel. | [
{
"name": "milliseconds",
"desc": "Length of time between Config messages."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Controlling Message Exchange for LMP Control Channels"
] |
retransmit-interval (Services) | retransmit-interval seconds; | [edit services l2tp tunnel-group name] | Specify the maximum retransmit interval for L2TP tunnels.
NOTE: This statement is not supported for L2TP LNS on MX Series routers. | [
{
"name": "seconds",
"desc": "Interval, in seconds, after which the server retransmits data if no acknowledgment is received."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Timers for L2TP Tunnels"
] |
retransmit-timer (Dynamic Router Advertisement) | retransmit-timer milliseconds; | [edit protocols router-advertisement interface interface-name] | Set the retransmission frequency of neighbor solicitation messages. | [
{
"name": "milliseconds",
"desc": "Retransmission frequency."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"IPv6 WAN Link Addressing with NDRA",
"Dynamic Router Advertisement Configuration Overview"
] |
retransmit-timer | retransmit-timer milliseconds; | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name],
[edit protocols router-advertisement interface interface-name] | Set the retransmission frequency of neighbor solicitation messages. This timer is used to detect when a
neighbor has become unreachable and to resolve addresses. | [
{
"name": "milliseconds",
"desc": "Retransmission frequency."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring IPv6 Interfaces and Enabling Neighbor Discovery",
"Secure IPv6 Neighbor Discovery"
] |
retry (Access LDAP) | retry attempts; | [edit access ldap-server server-address],
[edit access profile profile-name ldap-server server-address] | Specify the number of retries that a device can attempt to contact an LDAP server. | [
{
"name": "attempts",
"desc": "Number of retries that the device is allowed to attempt to contact an LDAP server."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"Example: Configuring RADIUS and LDAP User Authentication"
] |
retry (Adaptive Services Interface) | retry number-of-attempts; | [edit security pki ca-profile ca-profile-name enrollment] | (Adaptive services interfaces only) Specify how many times a router can resend a digital certificate
request. | [
{
"name": "number-of-attempts",
"desc": "Number of enrollment retries."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [] |
retry (Event Policy) | retry count number interval seconds; | [edit event-options policy policy-name then change-configuration] | Specify the number of times that Junos OS attempts the change-configuration event policy action if the
initial attempt fails while acquiring a lock on the configuration database. If you include the retry
statement, you must configure both the count and interval statements.
Default
If you do not include the retry statem... | [
{
"name": "count number",
"desc": "The number of attempts to retry the change-configuration event policy action upon failure of the initial attempt. Range: 0 through 10 Default: 0"
},
{
"name": "interval",
"desc": ""
},
{
"name": "seconds",
"desc": "The time interval specified in s... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configure an Event Policy to Change the Configuration"
] |
retry (RADIUS Server) | retry attempts; | [edit access radius-server address],
[edit access profile profile-name radius-server address] | Configure a limit to the number of times the device can resend a request to the RADIUS server when no
response from the RADIUS server is received. If the number of retries reaches this limit, the RADIUS
server is marked as dead, and the device begins to send requests to other RADIUS servers in the
network element. | [
{
"name": "attempts",
"desc": "Number of attempts allowed. Range: 1 through 10 Default: 3"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement modified in Release 8.5 of Junos OS for SRX Series Firewalls.
Statement introduced in Junos OS Release 17.1 for MX Series Routers. | [
"Configuring RADIUS Servers",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules",
"External Authentication Servers"
] |
retry (Services Flow Collector) | retry number; | [edit services flow-collector] | Configure the maximum number of attempts the flow collector interface make to transfer log files to the
FTP server. | [
{
"name": "number",
"desc": "Maximum number of transfer retry attempts."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Retry Attempts"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.