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 |
|---|---|---|---|---|---|---|---|
relay-option (DHCP Relay Agent) | relay-option {
option-number option-number;
default-action {
drop;
forward-only;
local-server-group local-server-group;
relay-server-group relay-server-group;
}
equals (ascii ascii-string | hexadecimal hexadecimal-string) {
drop;
forward-only;
lo... | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay group group-name],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ...],
[edit logical-systems logical-system-name ... | Configure the extended DHCP relay agent selective processing that is based on DHCP options in DHCP
client packets and specify the action to perform on client traffic. You can configure support globally or
for a named group of interfaces, and for either DHCP or DHCPv6 relay agent.
The remaining statements are explained ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Using DHCP Option Information to Selectively Process DHCP Client Traffic"
] |
relay-option-82 | relay-option-82 {
circuit-id {
include-irb-and-l2;
keep-incoming-circuit-id ;
no-vlan-interface-name;
prefix prefix;
use-interface-description (logical | device);
use-vlan-id;
}
remote-id {
include-irb-and-l2;
keep-incoming-remote-id ;
... | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay group group-name],
[edit logical-systems logical-system-name forwarding-options dhcp-relay],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name],
[edit logical-systems logical-system-name routing-instances ro... | Enable or disable the insertion of the DHCP relay agent information option (option 82) in DHCP packets
destined for a DHCP server.
To enable insertion of option 82 information in DHCP packets, you must specify at least one of the
circuit-id or remote-id statements.
You can use the relay-option-82 statement and its subo... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
link-selection option added in Junos OS Release 21.2R1. | [
"Using DHCP Relay Agent Option 82 Information"
] |
relay-option-vendor-specific (dhcpv6) | relay-option-vendor-specific {
host-name;
location;
} | [edit forwarding-options dhcp-relay dhcpv6] | Add vendor-specific information to the vendor-specific option (17) field of DHCPv6 control messages on
server-facing interfaces. The vendor-specific information can be a hostname, a location (such as a
unique connection identifier), or both. The hostname can be a string of characters such as Juniper-AB-1.
The location ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [] |
relay-server-group (DHCP Relay Agent Option) | relay-server-group relay-server-group; | [edit forwarding-options dhcp-relay relay-option (default-action | equals | starts-with)],
[edit forwarding-options dhcp-relay dhcpv6 relay-option (default-action | equals | starts-with)],
[edit forwarding-options dhcp-relay group group-name relay-option (default-action | equals | starts-
with)],
[edit forwarding-optio... | Relay DHCP client packets to the specified group of DHCP servers when you use the DHCP relay
selective processing feature. You can configure the relay operation globally or for a group of interfaces,
and for either DHCP or DHCPv6 relay agent. | [
{
"name": "relay-server-group",
"desc": "Name of DHCP server group."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Using DHCP Option Information to Selectively Process DHCP Client Traffic"
] |
relay-source | relay-source interface-name; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit forwarding-options dhcp-relay group group-name interface interface-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay overrides],
[edit logical-systems logical-sys... | Configure DHCP relay server to use the configured loopback address as the source address in both the
IP header and in DHCP messages relayed to the server.
In network configurations where a firewall on the broadband network gateway (BNG) is between the
DHCP relay agent and the DHCP server, only the BNG loopback address ... | [
{
"name": "interface-name",
"desc": "Specify the loopback interface. The interface-name must belo0."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring the DHCP Relay Agent Source Address to Enable DHCP Packets to Pass Through a",
"Firewall"
] |
reliable | (reliable | no-reliable); | [edit logical-systems logical-system-name protocols rsvp interface interface-name],
[edit logical-systems logical-system-name protocols rsvp peer-interface peer-interface-name],
[edit protocols rsvp interface interface-name],
[edit protocols rsvp peer-interface peer-interface-name] | Enable reliable message delivery on the interface.
To have both refresh reduction and reliable delivery, enable both the aggregate and reliable statements.
NOTE: For Junos OS Release 16.1 running on MX Series or PTX Series routers, setting
no-reliable on an interface automatically disables the fast reroute (FRR) scalab... | [] | 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. | [
"Configuring RSVP Refresh Reduction"
] |
remote (Host VPN) | remote {
id remote-id;
} | [edit security host-vpn] | Configure the identity details for authenticating the remote device during IKE negotiations. | [
{
"name": "id remote-id",
"desc": "Specify the remote IKE identity to use when authenticating the host-to-host VPN connection. The identity can be an IP address, a domain name, or an e-mail address. This identity matches the local identity."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 18.3R1. | [] |
remote | remote (inet-address | mac-address) address; | [edit interfaces interface-name unit logical-unit-number family tcc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family tcc] | For Layer 2.5 VPNs employing an Ethernet interface as the TCC router, configure the location of the
remote router. Ethernet TCC is supported on interfaces that carry IPv4 traffic only. Ethernet TCC
encapsulation is supported on 1-port Gigabit Ethernet, 2-port Gigabit Ethernet, 4-port Gigabit Ethernet,
and 4-port Fast E... | [
{
"name": "inet-addressaddress",
"desc": "The IP address of the remote site."
},
{
"name": "mac-address address",
"desc": "The MAC address of the remote site."
}
] | 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 TCC Encapsulation for Layer 2 VPNs and Layer 2 Circuits"
] |
remote-access (Juniper Secure Connect) | remote-access {
client-config name {
application-bypass {
term name {
description description;
protocol protocol;
domain-name domain-name
}
}
biometric-authentication;
certificate {
no-expiry-warning;
... | [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... | [
{
"name": "client-config",
"desc": "Define Juniper Secure Connect remote client configuration parameters."
},
{
"name": "compliance",
"desc": "Configure the compliance rules for the Juniper Secure Connect client’s connection"
},
{
"name": "request",
"desc": ""
},
{
"name": "d... | security | Statement introduced in Junos OS Release 20.3R1.
Support for prelogon compliance rule is added in Junos OS Release 23.1R1.
Support for application bypass is added in Junos OS Release 23.1R1.
Usage of default-profile options is not allowed starting Junos OS Release 23.1R1. | [
"Juniper Secure Connect Administrator Guide"
] |
remote-address (for LMP Control Channel) | remote-address ip-address; | [edit logical-systems logical-system-name protocols link-management peer peer-name lmp-control-
channel control-channel-interface],
[edit protocols link-management peer peer-name lmp-control-channel control-channel-interface] | Specify the remote IP address for the Link Management Protocol (LMP) control channel interface. | [
{
"name": "ip-address",
"desc": "Remote IP address mapped to the LMP control channel interface."
}
] | 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. | [
"Configuring the Remote IP Address for LMP Control Channels"
] |
remote-address (for LMP Traffic Engineering) | remote-address ip-address; | [edit logical-systems logical-system-name protocols link-management te-link te-link-name],
[edit logical-systems logical-system-name protocols link-management te-link te-link-name
interface interface-name],
[edit protocols link-management te-link te-link-name],
[edit protocols link-management te-link te-link-name inte... | Specify the remote IP address for the traffic engineering link. If you configure the remote IP address, you
must also configure the "local-address" on page 10327 statement. | [
{
"name": "ip-address",
"desc": "Remote IP address mapped to the traffic engineering link."
}
] | 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. | [
"Configuring the Remote IP Address for Traffic Engineering Links",
"Configuring the Remote IP Address for Forwarding Adjacencies"
] |
remote-address | remote-address (ipv4-address ipv4-address | ipv6-address ipv6-address); | [edit unified-edge pcef flow-descriptions flow-identifier],
[edit services pcef flow-descriptions flow-identifier] | Specify a remote IP address for the service data flow (SDF) filter.
If you are using Junos OS Subscriber Aware, specify the remote IP address at the [edit unified-edge pcef
flow-descriptions flow-identifier] hierarchy level.
If you are using Junos OS Broadband Subscriber Management, specify the remote IP address at th... | [
{
"name": "ipv4-address",
"desc": "IPv4 address."
},
{
"name": "ipv6-address",
"desc": "IPv6 address."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef flow-descriptions flow-identifier] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series. | [
"Configuring Service Data Flow Filters",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Understanding Application-Aware Policy Control for Subscriber Management"
] |
remote-debug-permission | remote-debug-permission (qfabric-admin | qfabric-operator | qfabric-user); | [edit system login user username authentication]
[edit system root-authentication] | (QFabric systems only) Configure authentication classes that permit or deny user access to individual
components of the QFabric system.
Default
qfabric-user | [
{
"name": "qfabric-admin",
"desc": "Permits a user to log in to individual QFabric system components, view operations, and change component configurations."
},
{
"name": "qfabric-operator",
"desc": "Permits a user to log in to individual QFabric system components and view component operations."
... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D20. | [
"Example: Configuring QFabric System Login Classes",
"Understanding QFabric System Login Classes"
] |
remote-device-management | remote-device-management {
service-device device-name {
access-domain {
vlan-id-list [vlan-id-low-vlan-id-high vlan-id]
}
address ip-address;
dictionary absolute file path;
provisioning-method {
netconf {
bulk-interval milliseconds;
... | [edit routing-instances routing-instance-name system services],
[edit system services] | The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | system—To view this statement in the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Configuring Remote Device Management for Service Provisioning",
"Remote Device Services Manager (RDSM) Overview"
] |
remote-engine | remote-engine engine-id {
user username {
authentication-md5 {
(authentication-key authentication-key | authentication-password authentication-
password);
}
authentication-none;
authentication-sha {
(authentication-key authentication-key | authentication-passw... | [edit snmp v3 usm] | Configure the remote engine information for the user-based security model (USM). To send inform
messages to an SNMPv3 user on a remote device, you must configure the engine identifier for the
SNMP agent on the remote device where the user resides. | [
{
"name": "engine-id",
"desc": "Specify engine identifier in hexadecimal format. Used to compute the security digest for"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [] |
remote-execution (Event Scripts) | remote-execution {
remote-hostname {
passphrase user-password;
username user-login;
}
} | [edit event-options event-script file filename] | Configure connection information for a local or remote host, which the event script can use to connect
to and execute RPCs on the device.
Remote execution details, which include the hostname, username, and passphrase for one or more
hosts, enable an event script to invoke remote procedure calls on a host without encodi... | [
{
"name": "passphrase user-password",
"desc": "User’s password for the host."
},
{
"name": "remote-hostname",
"desc": "Name of the host with which the event script will communicate."
},
{
"name": "username username",
"desc": "User’s login name for the host."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Use RPCs and Operational Mode Commands in Event Scripts",
"Use Event and Remote Execution Details in Event Scripts"
] |
remote-gateway (Tunnel Profile) | remote-gateway {
address server-ip-address;
gateway-name server-name;
} | [edit access tunnel-profile profile-name tunnel tunnel-id] | Specify the IP address and hostname of the remote gateway at the L2TP tunnel endpoint, the LNS.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
remote-gateway | remote-gateway address; | [edit services ipsec-vpn rule rule-name term term-name then] | Define the remote address to which the IPsec traffic is directed. | [
{
"name": "address",
"desc": "Remote IPv4 or IPv6 address."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec Rules"
] |
remote-id (DHCP Relay Agent) | remote-id {
include-irb-and-l2;
keep-incoming-remote-id ;
no-vlan-interface-name;
prefix prefix;
use-interface-description (logical | device);
use-vlan-id;
} | [edit forwarding-options dhcp-relay relay-option-82],
[edit forwarding-options dhcp-relay group group-name relay-option-82],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ... relay-option-82],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options... | 21.2R1
Starting with Junos OS Release 21.2R1, QFX Series switches support the remote-id CLI statement in a
stateless DHCP relay configuration. You can configure stateless DHCP relay using the forward-only CLI
statement at the [edit forwarding-options dhcp-relay] hierarchy level. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Using DHCP Relay Agent Option 82 Information",
"Configuring Option 82 Information"
] |
remote-id (MX Series) | remote-id {
host-name;
use-interface-description (logical | device);
use-string string;
} | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security option-82] | Insert the remote-id suboption of DHCP option 82 (also known as the DHCP relay agent information
option) in DHCP request packet headers before forwarding or relaying requests to a DHCP server. This
suboption provides a trusted identifier for the host system that has forwarded or relayed requests to the
server.
The rema... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring DHCP Option 82 on a Router with Bridge Domain",
"http://tools.ietf.org/html/rfc3046"
] |
remote-id (protocols link-management) | remote-id id-number; | [edit logical-systems logical-system-name protocols link-management te-link te-link-name],
[edit logical-systems logical-system-name protocols link-management te-link te-link-name
interface interface-name],
[edit protocols link-management te-link te-link-name],
[edit protocols link-management te-link te-link-name inte... | Specify the ID assigned to a traffic engineering link or an interface (resource) on the peer node. | [
{
"name": "id-number",
"desc": "ID number for the remote device."
}
] | 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. | [
"Configuring the Remote ID for Traffic Engineering Links"
] |
remote-id (Services) | remote-id {
any-remote-id;
ipv4_addr [ values ];
ipv6_addr [ values ];
key_id [ values ];
fqdn fqdn
distinguished-name container container-string-values |wildcard wildcard-string-values
} | [edit services ipsec-vpn ikepolicy policy-name] | Define the remote identification values to which the IKE policy applies. | [
{
"name": "any-remote-id",
"desc": "Allow any remote address to connect. This option is supported only in dynamic"
},
{
"name": "ipv4_addr [ values ]",
"desc": "Define one or more IPv4 address identification values."
},
{
"name": "ipv6_addr [ values ]",
"desc": "Define one or more IP... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
ipv6_addr option added in Junos OS Release 7.6.
any-remote-id option added in Junos OS Release 8.2.
distinguished-name containercontainer-string-values |wildcard wildcard-string-values option added in Junos OS
Release 19.1. | [
"Configuring IKE Policies"
] |
remote-id (VLAN Authentication Username) | remote-id; | [edit interfaces interface-name auto-configure vlan-ranges authentication username-include] | Include the agent remote identifier (ARI) in the username sent to RADIUS for authentication of the
dynamic VLAN. The ARI is conveyed by the Access-Loop-Remote-ID TLV in an out-of-band ANCP Port
Up message.
NOTE: This statement is not supported for stacked VLANs. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R4. | [
"Configuring a Username for Authentication of Out-of-Band Triggered Dynamic VLANs",
"Configuring VLAN Interface Username Information for AAA Authentication",
"Layer 2 Wholesale with ANCP-Triggered VLANs Overview"
] |
remote-id | remote-id {
host-name host-name;
mac (Option 82);
prefix ( hostname | mac | none);
use-interface-description (logical | device);
use-string string;
} | For platforms with Enhanced Level 2 Software (ELS):
[edit vlans vlan-name forwarding-options dhcp-security option-82]
For platforms without ELS:
[edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-option82],
[edit forwarding-options helpers bootp dhcp-option82],
[edit forwarding-options help... | Insert the remote-id suboption of DHCP option 82 (also known as the DHCP relay agent information
option) in DHCP request packet headers before forwarding or relaying requests to a DHCP server. This
suboption provides a trusted identifier for the host system that has forwarded or relayed requests to the
server.
The rema... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
Hierarchy level [edit vlans vlan-name forwarding-options dhcp-security option-82] introduced in Junos OS
Release 13.2X50-D10. (See Using the Enhanced Layer 2 Software CLI for information about ELS.) | [
"Example: Setting Up DHCP Option 82",
"http://tools.ietf.org/html/rfc3046"
] |
remote-id-mismatch (DHCP Local Server and DHCP Relay Agent) | remote-id-mismatch disconnect; | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay group group-name],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit logical-systems logical-system-name ...],
[edit logical-systems logical-system-name routing-instances routing-inst... | Configure the DHCP local server or DHCP relay agent to detect a mismatch in the Agent Remote ID
value to trigger a new connection request. Information about a subscriber’s service plan is encoded in
the Agent Remote ID, which is conveyed in option 82, suboption 2, for DHCPv4 clients and in option 37
for DHCPv6 clients.... | [] | 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 DHCP-Initiated Service Change Based on Remote ID"
] |
remote-identity | remote-identity {
distinguished-name {
container container-string;
wildcard wildcard-string;
}
hostname hostname;
inet ip-address;
inet6 ipv6-address;
key-id;
user-at-hostname e-mail-address;
} | [edit security ike gateway gateway-name]
[edit system ntp server server-name nts] | Specify the remote IKE identity to exchange with the destination peer to establish communication. If
you do not configure a remote-identity, the device uses the IPv4 or IPv6 address corresponding to the
remote endpoint by default.
For Network Address Translation Traversal (NAT-T), both remote identity and local identit... | [
{
"name": "distinguished-name",
"desc": "Specify identity as the distinguished name (DN) from the certificate. If there is"
},
{
"name": "container container-string",
"desc": "Specify a string for the container."
},
{
"name": "wildcard wildcard-string",
"desc": "Specify a string for ... | 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. | [
"IPsec Overview"
] |
remote-interface-switch | remote-interface-switch connection-name {
interface interface-name.unit-number;
receive-lsp label-switched-path;
transmit-lsp label-switched-path;
} | [edit logical-systems logical-system-name protocols connections],
[edit protocols connections (MPLS)] | Configure MPLS LSP tunnel cross-connects. This makes an association between a CCC interface and
two LSPs, one for transmitting MPLS packets from the local provider edge switch to the remote provider
edge switch and the other for receiving MPLS packets on the local provider edge switch from the
remote provider edge swit... | [
{
"name": "connection-name",
"desc": "Connection name."
},
{
"name": "interface interface-name.unit-number",
"desc": "Interface name. Include the logical portion of the name, which"
},
{
"name": "receive-lsp label-switched-path",
"desc": "Name of the LSP from the connection’s source.... | 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. | [
"Configuring MPLS LSP Tunnel Cross-Connects Using CCC",
"Example: Configuring MPLS on EX8200 and EX4500 Switches",
"Configuring MPLS on Provider Edge EX8200 and EX4500 Switches Using Circuit Cross-Connect",
"Configuring MPLS on Provider Edge Switches Using IP-Over-MPLS",
"MPLS Applications User Guide"
] |
remote-ip-address | remote-ip-address ip-address {
local-ip-address;
announce-interval announce-interval;
asymmetry asymmetry;
delay-request delay-request;
dscp dscp;
grant-duration grant-duration;
sync-interval sync-interval;
} | [edit logical-systems name protocols ptp stateful interface name unicast-mode],
[edit protocols ptp stateful interface name unicast-mode] | Configure remote IP address for PTP stateful parameters | [
{
"name": "ip-address",
"desc": "IP address of remote PTP partner."
},
{
"name": "local-ip-address",
"desc": "IP address on local interface."
},
{
"name": "announce-interval",
"desc": "Log mean interval between announce messages. Range: -3 through 0"
},
{
"name": "asymmetry"... | routing | Statement introduced in Junos OS Release 20.4R1. | [
"Configuring Precision Time Protocol"
] |
remote-ip-host-routes | remote-ip-host-routes {
import [ import ... ];
no-advertise-community;
} | [edit routing-instances name protocols evpn],
[edit protocols evpn] | Allows you to configure virtual machine traffic optimization (VMTO) for EVPN. | [
{
"name": "import",
"desc": "Policy to control the creation of remote IP host routes"
},
{
"name": "no-advertise-community",
"desc": "Enable this option to prevent type-2 MAC and IP community advertisements from being included in type-5 route imports, even though the information may be available... | routing | Statement introduced in Junos OS Release 18.4R1.
The option, no-advertise-community, was introduced in Junos OS Release 19.4R1. | [] |
remote-loop-enable | (remote-loop-enable | no-remote-loop-enable); | [edit interfaces interface-name otn-options odu-delay-management] | Enable the remote interface to loop back the delay measurement pattern to the local interface. Delay is
measured by transmitting a known pattern (delay measurement pattern) in a selected bit of the delay
measurement (DM) field and measuring the number of frames that are missed when the delay
measurement pattern is rece... | [
{
"name": "remote-loop-enable",
"desc": "Enables loopback of the delay measurement pattern at the remote interface."
},
{
"name": "no-remote-loop-enable",
"desc": "Disables loopback of the delay measurement pattern at the remote interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"100-Gigabit DWDM OTN MIC with CFP2-ACO",
"100-Gigabit DWDM OTN PIC with CFP2-ACO (PTX Series)",
"Configuring OTN Interfaces on MIC3-100G-DWDM MIC",
"Configuring OTN Interfaces on PTX-5-100G-WDM PIC",
"Disabling ODU Path Delay Measurement",
"Ena... |
remote-loopback | remote-loopback; | [edit protocols oam ethernet link-fault-management
interface interface-name] | Set the data terminal equipment (DTE) in loopback mode. Remove the statement from the configuration
to take the DTE out of loopback mode. It is used for IEEE 802.3ah Operation, Administration, and
Maintenance (OAM) link fault management (LFM) support.
For Ethernet interfaces on EX Series switches and M320, M120, MX Ser... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Example: Configure Ethernet OAM Link Fault Management",
"Configure Ethernet OAM Link Fault Management"
] |
remote-maintenance-association (OAM) | remote-maintenance-association remote-ma-name; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name maintenance-
association ma-name] | Configure the name of the remote maintenance association. | [
{
"name": "remote-ma-name",
"desc": "Name of the remote maintenance association."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configuring Connectivity Fault Management (CFM)"
] |
remote-mep (EX Series Switch Only) | remote-mep mep-id {
action-profile profile-name;
} | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name mep mep-id ] | Specify the numeric identifier of the remote maintenance association end point (MEP) within the
maintenance association. | [
{
"name": "mep-id",
"desc": "Specify the numeric identifier of the MEP."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configure Ethernet OAM Connectivity Fault Management (CLI Procedure)",
"Junos OS Network Interfaces Configuration Guide"
] |
remote-mep | remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
detect-loc;
} | [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name maintenance-
association ma-name mep mep-id] | Configure the numeric identifier of the remote maintenance association end point (MEP) within the
maintenance association. | [
{
"name": "mep-id",
"desc": "Numeric identifier of the MEP."
}
] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 8.4. | [
"Configuring Connectivity Fault Management (CFM)"
] |
remote-port-range | remote-port-range {
low low-value;
high high-value;
} | [edit unified-edge pcef flow-descriptions flow-identifier],
[edit services pcef flow-descriptions flow-identifier] | Specify the remote port range to identify the subscriber traffic that you want the service data flow (SDF)
filter to detect.
If you are using Junos OS Subscriber Aware, specify the remote port range at the [edit unified-edge pcef
flow-descriptions flow-identifier] hierarchy level.
If you are using Junos OS Broadband Su... | [
{
"name": "high-value",
"desc": "Upper boundary for the remote port range. Range: 1 through 65,535"
},
{
"name": "low-value",
"desc": "Lower boundary for the remote port range. Range: 1 through 65,535"
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef flow-descriptions flow-identifier] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series. | [
"Configuring Service Data Flow Filters",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Understanding Application-Aware Policy Control for Subscriber Management"
] |
remote-ports | remote-ports [number]; | [edit unified-edge pcef flow-description flow-identifier],
[edit services pcef flow-description flow-identifier] | Specify a remote port or list of remote ports to identify the subscriber traffic that you want the service
data flow (SDF) filter to detect.
If you are using Junos OS Subscriber Aware, specify the remote ports at the [edit unified-edge pcef flow-
descriptions flow-identifier] hierarchy level.
If you are using Junos OS ... | [
{
"name": "number",
"desc": "Port number or list of port numbers. You can specify a maximum of three port numbers in a list. Range: 1 through 65,535"
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef flow-descriptions flow-identifier] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series. | [
"Configuring Service Data Flow Filters",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Understanding Application-Aware Policy Control for Subscriber Management"
] |
remote-site-id | remote-site-id remote-site-ID; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn site site-name interface interface-name],
[edit routing-instances routing-instance-name protocols l2vpn site site-name interface interface-
name] | Control the remote interface to which the interface should connect. If you do not explicitly configure the
remote site ID, the order of the interfaces configured for the site determines the default value. This
statement is optional. | [
{
"name": "remote-site-ID",
"desc": "Identifier specifying the interface on the remote PE router the Layer 2 VPN routing"
}
] | 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. | [
"Configuring the Remote Site ID",
"Configuring an MPLS-Based Layer 2 VPN (CLI Procedure)"
] |
remote-traffic-selector | remote-traffic-selector {
(ipv4-prefix ipv4-prefix | ipv6-prefix ipv6-prefix);
port port;
protocol protocol;
} | [edit security host-vpn connections connection-name children child-name] | Configure the remote IPsec traffic to be protected by the child security association. A traffic selector is a
traffic filter that defines and identifies the traffic flow permitted between two systems (a specified pair
of local and remote addresses) that have IPsec protection. | [
{
"name": "(ipv4-prefix ipv4-prefix | ipv6-prefix",
"desc": ""
},
{
"name": "ipv6-prefix)",
"desc": "Specify traffic to be protected by the child security association using either IPv4 or IPv6 with a prefix. The prefix allows for specifying more general traffic."
},
{
"name": "port port"... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 18.3R1. | [] |
remote-vtep-list | remote-vtep-list [remote-vtep-loopback-address ... ]; | [edit routing-instances name],
[edit switch-options] | Configure static remote VXLAN tunnel endpoints (VTEPs). This statement configures VTEPs at the
global level in a Layer 2 (L2) VXLAN gateway device. Specify one or more loopback addresses of the
remote VTEPs.
You don’t configure EVPN as part of a static VXLAN configuration. However, on platforms that support
EVPN-VXLAN ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 14.1R3 and 14.2R1. | [
"Static VXLAN"
] |
remotely-controlled | remotely-controlled; | [edit services nat pool nat-pool-name pgcp] | Configure the addresses and ports in a NAT pool to be remotely controlled by the gateway controller. | [] | interface—To view this statement in the configuration.
interface–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
remove-ie | remove-ie {
version v1 {
number ie-number;
release name;
}
} | [edit security gtp profile profile-name] | Use the remove-ie option to enable the security device to detect and remove 3G-specific attributes
from the GPRS tunneling protocol (GTP) packet header when the packet passes into a 2G network. It
allows you to retain interoperability when roaming between 2G and 3G networks.
From Junos OS Release 20.4R1 onwards, the [e... | [
{
"name": "version v1",
"desc": "To specify GTP version 1."
},
{
"name": "number",
"desc": "To specify the user-configured IE number. IE removal by IE number supports all IEs, ranging"
},
{
"name": "release",
"desc": "To Specify release number. Available options are:"
},
{
"n... | 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. | [
"Example: Removing R6, R7, R8, and R9 Information Elements from GTP Messages",
"Understanding GTPv1 Information Element Removal",
"Example: Removing GTPv1 Information Elements Using IE Number"
] |
remove-private | remove-private; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | When advertising AS paths to remote systems, have the local system strip private AS numbers from the
AS path. The numbers are stripped from the AS path starting at the left end of the AS path (the end
where AS paths have been most recently added). The routing device stops searching for private ASs
when it finds the fir... | [
{
"name": "all",
"desc": "Remove all private AS numbers from the original path. Do not stop the process of removing private AS numbers, even if a public AS number is encountered."
},
{
"name": "nearest",
"desc": "When you use the all and replace options, choose the last (right-most) public AS nu... | 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.
no-peer-loop-check option added in Junos OS Release 15.1. | [
"Example: Removing Private AS Numbers from AS Paths"
] |
remove-when-no-subscribers | remove-when-no-subscribers; | [edit interfaces interface-name auto-configure] | Remove subscriber VLANs automatically when no client sessions (for example, DHCP or PPPoE) exist on
the VLAN. | [] | routing—To view this statement in the configuration.
routing–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Automatically Removing VLANs with No Subscribers"
] |
rename | rename <statement-path> identifier1 to identifier2 | Rename an existing configuration statement or identifier. | [
{
"name": "identifier1",
"desc": "Existing identifier to rename."
},
{
"name": "identifier2",
"desc": "New name of identifier."
},
{
"name": "statement-path",
"desc": "(Optional) Path to an existing statement or identifier. NOTE: For example, to rename interface ge-0/1/0.0 to ge-0/1/... | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Command introduced before Junos OS Release 7.4. | [
"Renaming an Identifier in a Configuration"
] | |
renegotiation (Services) | renegotiation (allow | allow-secure | drop); | [edit services ssl proxy profile profile-name actions] | Specify the renegotiation options. | [
{
"name": "allow",
"desc": "Allow secure and nonsecure renegotiation."
},
{
"name": "allow-secure",
"desc": "Allow secure negotiation only."
},
{
"name": "drop",
"desc": "Drop session on renegotiation request."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [
"Configuring SSL Forward Proxy"
] |
reopen-time | reopen-time seconds; | [edit protocols l2-learning global-mac-move] | (MX Series routers only) Configure the value for the reopen timer.
Default
180 seconds | [
{
"name": "seconds",
"desc": "Time duration after which the port is unblocked."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Configuring MAC Move Parameters"
] |
replace | replace pattern pattern1 with pattern2 <upto n> | Replace identifiers or values in a configuration. | [
{
"name": "pattern1",
"desc": "Text string or regular expression that defines the identifiers or values you want to match."
},
{
"name": "pattern2",
"desc": "Text string or regular expression that replaces the identifiers and values located with pattern1. Juniper Networks uses standard UNIX-styl... | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Command introduced in Junos OS Release 7.6. | [
"Using Global Replace in the Configuration"
] | |
replace-ip-source-with (DHCP Relay Agent) | replace-ip-source-with giaddr; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name
overrides],
[edit logical-system... | Replace the IP source address in DHCP relay request and release packets with the gateway IP address
(giaddr). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Extended DHCP Relay Agent Overview",
"Configure DHCP Relay Agent to Replace Request and Release Packets with Gateway IP address"
] |
replay-attacks | replay-attacks {
threshold value;
} | [edit security alarms potential-violation] | Raise a security alarm when the device detects a replay attack. A replay attack is a form of network
attack in which a valid data transmission is maliciously or fraudulently repeated or delayed.
Default
Replay attacks do not raise security alarms. | [
{
"name": "threshold value",
"desc": "Number of reply attacks up to which an alarm is not raised. When the configured"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"IPsec Overview",
"Monitoring VPN Traffic"
] |
replay-protect (MX Series) | replay-protect {
replay-window-size number-of-packets;
} | [edit security macsec connectivity-association connectivity-association-name] | Enable replay protection for MACsec.
A replay window size specified using the replay-window-size number-of-packets statement must be specified
to enable replay protection. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
replay-protect | replay-protect {
replay-window-size number-of-packets;
} | [edit security macsec connectivity-association connectivity-association-name] | Enable replay protection for MACsec.
A replay window size specified using the "replay-window-size" on page 14931 number-of-packets
statement must be specified to enable replay protection.
When replay protection is enabled, the receiving interface checks the ID number of all packets that have
traversed the MACsec-secure... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15.
Statement introduced on SRX Series Firewalls in Junos OS Release 15.1X49-D60. | [
"Configuring MACsec on EX, QFX and SRX Devices",
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)"
] |
replay-window-size (MX Series) | replay-window-size number-of-packets; | [edit security macsec connectivity-association connectivity-association-name replay-protect] | Specifies the size of the replay protection window.
This statement has to be configured to enable replay protection.
When MACsec is enabled on an Ethernet link, an ID number is assigned to each packet entering the link.
The ID number of the packet is checked by the receiving interface after the packet has traversed the... | [
{
"name": "number-of-packets",
"desc": "Specifies the size of the replay protection window, in packets. When this variable is set to 0, all packets that arrive out-of-order are dropped."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
replay-window-size | replay-window-size number-of-packets; | [edit security macsec connectivity-association connectivity-association-name replay-protect] | Specifies the size of the replay protection window.
This statement has to be configured to enable replay protection.
When MACsec is enabled on an Ethernet link, an ID number is assigned to each packet entering the link.
The ID number of the packet is checked by the receiving interface after the packet has traversed the... | [
{
"name": "number-of-packets",
"desc": "Specifies the size of the replay protection window, in packets. When this variable is set to 0, all packets that arrive out-of-order are dropped."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15.
Statement introduced on SRX Series Firewalls in Junos OS Release 15.1. | [
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec) on Routers",
"Configuring MACsec on EX, QFX and SRX Devices"
] |
replicator | replicator {
inet ip;
vxlan-encapsulation-source-ip (assisted-replicator-ip | ingress-replication-ip | retain-
incoming-source-ip);
} | [edit logical-systems name routing-instances name protocols evpn assisted-replication],
[edit routing-instances name protocols evpn assisted-replication],
[edit protocols evpn assisted-replication] | Configure a device in an EVPN network into the assisted replication (AR) replicator role.
AR helps to optimize broadcast, unknown unicast, and multicast (BUM) traffic in EVPN networks. To
enable AR, you configure devices in the EVPN network to operate as AR replicator and AR leaf devices.
AR replicator devices take on ... | [
{
"name": "inet ip-address",
"desc": "(Required) IPv4 address for the AR tunnel to the AR replicator. This must be a loopback interface configured on the AR replicator device that is part of the EVPN instance."
},
{
"name": "vxlan-encapsulation-",
"desc": ""
},
{
"name": "source-ip",
... | routing | Statement introduced in Junos OS Release 18.4R2 and 19.4R1. | [
"Assisted Replication Multicast Optimization in EVPN Networks"
] |
report (LRF Rule) | report {
collector collector-name;
template template-name;
time-limit time-interval;
volume-limit volume;
} | [edit services lrf profile profile-name rule lrf-rule-name then] | Configure the actions to take if the LRF rule is matched.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
report (Security Log) | report {
database-capacity {
max-db-size;
}
database-filter {
event-category;
exclude;
}
log-share-per-table {
atp log-share;
dns log-share;
idp log-share;
ipsec-vpn log-share;
screen log-share;
session-all log-share;
ut... | [edit security log]
[edit logical-systems name security log]
[edit tenants tenant-name security log] | Set security log report settings.
On-box reporting offers a comprehensive reporting facility where your security management team can
spot a security event when it occurs, immediately access and review pertinent details about the event,
and quickly decide appropriate remedial action.
The on-box reporting feature is enab... | [
{
"name": "report",
"desc": "Enable log report."
},
{
"name": "logs-per-table",
"desc": "Log number for each table."
},
{
"name": "idp",
"desc": "Log number of idp. Range: For SRX300, SRX320, SRX340, SRX345, SRX550, SRX550M, and vSRX Virtual Firewall: 40000 through 80000 Default: 4... | The remaining statements are explained separately. See CLI Explorer. | Statement introduced in Junos OS Release 15.1X49-D100
The [edit logical-systems name security "log" on page 10435] and [edit tenants tenant-name security "log"
on page 10435] hierarchy levels introduced in Junos OS Release 19.1R1.
table-mode option added in Junos OS Release 19.4R1. | [] |
report-ingress-shaping-rate (Dynamic CoS Interfaces) | report-ingress-shaping-rate bps; | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number] | Report the ingress shaping rate in bits per second that is used as the receive speed (Rx) for the LAC to
send to the LNS. The ingress shaping rate is used when the method for deriving the connect speed is
configured as service-profile with the tx-connect-speed statement at the [edit services l2tp] hierarchy level.
NOTE... | [
{
"name": "bps",
"desc": "Ingress shaping rate in bits per second. Range: 1000 through 6,400,000,000,000 (6.4Tbps)"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"L2TP Subscriber Access Lines and Connection Speeds",
"L2TP Subscriber Access Lines and Connection Speeds",
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Classifier to a Subscriber Interface in a Dynamic Profile"
] |
report-interface-descriptions (Access) | report-interface-descriptions; | [edit access] | Enable storing and reporting of interface descriptions through RADIUS. To disable storing and reporting
of interface descriptions, configure the [edit access profile profile-name radius attributes exclude]
statement to exclude the interface description attribute. The description can contain letters, numbers,
and hyphen... | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"Storage and Reporting of Interface Descriptions to Uniquely Identify Subscribers",
"RADIUS Servers and Parameters for Subscriber Access",
"Configuring Authentication and Accounting Parameters for Subscriber Access"
] |
report-local-rule (PCRF Partition) | report-local-rule; | [edit access pcrf partition partition-name] | Configure the Policy and Charging Rule Function (PCRF) partition to send local report downstream
messages by default. If you configure this statement, this generates the same result as if you enabled the
Resource-Allocation-Notification message trigger with the local rule definition.
The following example shows predefi... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
report-resource-allocation (PCRF Partition) | report-resource-allocation; | [edit access pcrf partition partition-name] | Configure the Policy and Charging Rule Function (PCRF) partition to generate reports for resource
allocation failures by default. If you configure this statement, this generates the same result as if you
enabled the Resource-Allocation-Notification message trigger with every rule received from the PCRF.
The following e... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
report-skip | report-skip | [edit security policies from-zone zone-name to-zone zone-name policy policy-name],
[edit security policies global policy policy-name],
[edit security policies stateful-firewall-rule [name] policy [name]],
[edit security policies explicit-proxy profile [name] policy [name] report-skip],
[edit logical-systems logical-sys... | You can configure this command to skip policy reports for a policy.
Adding the policy to the policy allowlist excludes the policy from any policy analysis and excluded it
from appearing in any future report. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.1R1. | [] |
report-successful-resource-allocation (PCRF Partition) | report-successful-resource-allocation; | [edit access pcrf partition partition-name] | Configure the Policy and Charging Rule Function (PCRF) partition to generate reports for both resource
allocation successes and failures by default. If you configure this statement, this generates the same
result as if you enabled the Successful-Resource-Allocation-Notification message trigger with every
CCA-GX-I, CCA-... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
report-zero-oif-gw-on-discard | report-zero-oif-gw-on-discard; | [edit chassis fpc slot-number inline-services] | (MX Series only) For inline active flow monitoring, for only the flow records for rejected, discarded, and
policed flows, set the flow record value to 0 (zero) for the IPFIX information elements ipNextHopIPv6Address
(Element ID 62), egressInterface (Element ID 14), and ipNextHopIPv4Address (Element ID 15). If the repor... | [] | Statement introduced in Junos OS Release 15.1F7. | [] | |
req-option | req-option (dns-server | domain | fqdn | nis-domain | nis-server | ntp-server | sip-domain | sip-
server | time-zone | vendor-spec); | [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] | The configuration options requested by the DHCPv6 client. | [
{
"name": "dns-server",
"desc": "Specify a DNS server."
},
{
"name": "domain",
"desc": "Specify a domain name."
},
{
"name": "fqdn",
"desc": "Specify a fully qualified domain name."
},
{
"name": "nis-domain",
"desc": "Specify a Network Information Service (NIS) domain."
... | 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. | [] |
req-timeout | req-timeout second; | [edit security gtp profile profile-name] | Use the req-timeout option to specify a GTP request message timeout. The default timeout value is 5
seconds.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp profile profile-name] hierarchy level is
replaced by [edit security gtp profile profile-name]. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X46-D35. | [
"Example: Configure the Validity of IP Address in GTP Messages"
] |
request (Chassis Synchronization Source) | request (force-switch | lockout); | [edit chassis synchronization source (bits | gps)],
[edit chassis synchronization source interfaces] | Configure an interface with an upstream clock source to force a switch to another source, provided that
the source is enabled and not locked out, or to lockout a source from the clock selection process. | [
{
"name": "force-switch",
"desc": "Force a switch to the source provided that the source is enabled and not locked out. Only one configured source may be force-switched."
},
{
"name": "lockout",
"desc": "A lockout may be configured for any source. When a lockout is configured for a source, that ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"External Clock Synchronization Overview for ACX Series Routers",
"Configuring External Clock Synchronization for ACX Series Routers",
"Synchronous Ethernet Overview",
"show chassis synchronization"
] |
request (Clock Synchronization) | request (force-switch lockout); | [edit chassis synchronization source interfaces (external-a | external-b | interface interface-
name)],
[edit chassis synchronization source interfaces (external | interface interface-name)],
[edit chassis synchronization source interfaces (external-0/0 | external-1/0 | interface
interface-name)] | Specify the clock selection request criterion. | [
{
"name": "force-switch",
"desc": "Force switching to a clock source, provided the clock source is enabled and not locked out. Only one configured source may be force-switched."
},
{
"name": "lockout",
"desc": "Clock source is not considered by the selection process. Lockout may be configured fo... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2 R4. | [] |
request access-security router-advertisement-guard-block | request access-security router-advertisement-guard-block interface (interface-name) | Initiate the blocking state on an interface or range of interfaces for stateful IPv6 Router Advertisement
(RA) guard. Stateful RA guard learns about legitimate senders of RA messages and stores this
information in order to validate senders of subsequent RA messages. For example, an interface that is in
the learning sta... | [
{
"name": "interface interface-name",
"desc": "Initiate the blocking state on the specified interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Output Fields
This command produces no output. | Command introduced in Junos OS Release 15.1X53-D55. | [
"Configuring Stateful IPv6 Router Advertisement Guard"
] | |
request access-security router-advertisement-guard-forward | request access-security router-advertisement-guard-forward interface (interface-name) | Initiate the forwarding state on an interface or range of interfaces for stateful IPv6 Router
Advertisement (RA) guard. Stateful RA guard learns about legitimate senders of RA messages and stores
this information in order to validate senders of subsequent RA messages. For example, an interface that
is in the learning s... | [
{
"name": "interface interface-name",
"desc": "Initiate the forwarding state on the specified interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Output Fields
This command produces no output. | Command introduced in Junos OS Release 15.1X53-D55. | [
"Configuring Stateful IPv6 Router Advertisement Guard"
] | |
request access-security router-advertisement-guard-learn interface | request access-security router-advertisement-guard-learn interface (interface-name) duration
seconds (forward | block) | Request the learning state on an interface or range of interfaces for stateful IPv6 Router Advertisement
(RA) guard. Stateful RA guard learns about legitimate senders of RA messages and stores this
information in order to validate senders of subsequent RA messages. For example, an interface that is in
the learning stat... | [
{
"name": "interface",
"desc": ""
},
{
"name": "interface-name",
"desc": "Initiate the learning state on the specified interface."
},
{
"name": "duration seconds",
"desc": "Configure the duration of the learning state in seconds. When the learning period ends, the state dynamically t... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Output Fields
This command produces no output. | Command introduced in Junos OS Release 15.1X53-D55. | [
"Configuring Stateful IPv6 Router Advertisement Guard"
] | |
request access-security slaac-snooping unblock | request access-security slaac-snooping unblock
<interface interface-name | all> | Clear an interface that has been blocked by SLAAC snooping. | [
{
"name": "interface (interface-name | all)",
"desc": "Clear SLAAC snooping information for the specified interface or all interfaces."
}
] | clear
Output Fields
This command produces no output.
Sample Output
request access-security slaac-snooping unblock
user@switch> request access-security slaac-snooping unblock | Command introduced in Junos OS Release 19.2R1. | [] | |
request ancp oam interface | request ancp oam interface
(interface-name | interface-set set-name)
<count count>
<timeout duration> | Trigger the access node to run a loopback test on the local loop between the access node and the
customer premises equipment. You must specify either an ANCP interface or an ANCP interface set.
The access node responds to the NAS with the results of the test. | [
{
"name": "interface-name",
"desc": "Name of the ANCP interface on whose local loop the loopback test is run."
},
{
"name": "interface-set set-name",
"desc": "Name of the ANCP interface set on whose local loop the loopback test is run."
},
{
"name": "count count",
"desc": "(Optional)... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request, including the
result of the test, the response code, and the response string returned with the OAM response in the
event of failure, an error code is displayed.
Sample Output
request ancp oam interface
user@host> re... | Command introduced in Junos OS Release 11.4. | [
"ANCP Monitoring and Management"
] | |
request ancp oam neighbor | request ancp oam neighbor
(ip-address ip-address | system-name neighbor-name)
subscriber identifier-string
<count count>
<timeout duration> | Trigger the access node to run a loopback test on the local loop between the access node and the
customer premises equipment. You must specify both the access node and the subscriber. The access
node responds to the NAS with the results of the test. | [
{
"name": "ip-address ip-address",
"desc": "IP address that specifies the access node on whose local loop the loopback test is run."
},
{
"name": "system-name",
"desc": ""
},
{
"name": "neighbor-name",
"desc": "System name that specifies the access node on whose local loop the loopba... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request, including the
result of the test, the response code, and the response string returned with the OAM response in the
event of failure, an error code is displayed.
Sample Output
request ancp oam subscriber
user@host> r... | Command introduced in Junos OS Release 11.4. | [
"ANCP Monitoring and Management"
] | |
request ancp oam port-down | request ancp oam port-down
(neighbor ip-address | subscriber-interface physical-interface-name)
circuit-id aci remote-id ari outer-vlan-id vlan-id | Simulate an ANCP Port Down message on the specified access loop for troubleshooting or to mitigate
an abnormal condition. Triggers removal of the corresponding out-of-band triggered, autosensed
dynamic VLAN session for which no ANCP-sourced information exists. You must specify an ACI, an ARI,
and an outer VLAN tag. Thi... | [
{
"name": "aci",
"desc": "ANCP Access-Loop-Circuit-ID TLV that corresponds to a subscriber interface on the access node; used to identify the access node from which the message is simulated."
},
{
"name": "ari",
"desc": "ANCP Access-Loop-Remote-ID TLV that identifies the subscriber associated wi... | view
Output Fields
When you enter this command, you are provided no feedback on the status of your request. You can
enter the show ancp neighbor detail, show subscribers client-type vlan-oob detail, and the show subscribers
summary commands before and after initiating the Port Down message to verify the operation.
Sam... | Command introduced in Junos OS Release 16.1R4. | [
"Triggering ANCP OAM to Simulate ANCP Port Down and Port Up Messages",
"Layer 2 Wholesale with ANCP-Triggered VLANs Overview"
] | |
request ancp oam port-up | request ancp oam port-up
(neighbor ip-address | subscriber-interface physical-interface-name)
circuit-id aci remote-id ari outer-vlan-id vlan-id | Simulate an ANCP Port Up message on the specified access loop for troubleshooting or to mitigate an
abnormal condition. You must specify an ACI, an ARI, and an outer VLAN tag. This command is
overridden by a genuine ANCP Port Down message, meaning that you cannot use this command to
initiate a Port Up condition when th... | [
{
"name": "aci",
"desc": "ANCP Access-Loop-Circuit-ID TLV that corresponds to a subscriber interface on the access node; used to identify the access node from which the message is simulated."
},
{
"name": "ip-address",
"desc": "IP address that specifies the access node from which the message is ... | view
Output Fields
When you enter this command, you are provided no feedback on the status of your request. You can
enter the show ancp neighbor detail, show subscribers client-type vlan-oob detail, and the show subscribers
summary commands before and after initiating the Port Up message to verify the operation.
Sampl... | Command introduced in Junos OS Release 16.1R4. | [
"Triggering ANCP OAM to Simulate ANCP Port Down and Port Up Messages",
"Layer 2 Wholesale with ANCP-Triggered VLANs Overview"
] | |
request app-engine cleanup | request app-engine cleanup
<compute-cluster compute-cluster-name>
<compute-cluster compute-cluster-name compute-node compute-node-name> | Cleans up temporary files on the Junos V App Engine or the host OS of QFX Series switches. This
command deletes all files from the directories where temporary files are normally stored, such
as /var/tmp and /var/log.
Be sure to collect any temporary files and logs you want to save before running this command. | [
{
"name": "compute-cluster compute-cluster-name compute-node compute-node-name",
"desc": "Name of the compute cluster and"
}
] | view
Output Fields
For a description of the output fields, see Table 127 on page 14975. Output fields are listed in the
approximate order in which they appear.
Table 127: request app-engine cleanup Output Fields
Field Name
Field Description
Compute Cluster
Name of compute cluster.
Compute Node
Name of compute node.
Cle... | Command introduced in Junos OS Release 13.1X51-D10. | [] | |
request app-engine file-copy (crash | log) from-jhost to-vjunos | request app-engine file-copy (crash | log)
from-jhost host-os-filename
to-vjunos vjunos-filename | In Junos OS environments with a host OS, copies core files (crash option) or system log files (log option)
from the host OS to a Junos OS filename.
•
crash option—Core files are copied from the directory where the host OS normally stores core files.
For example, when the host OS is Linux, the source directory is /var/c... | [
{
"name": "from-jhost host-os-filename",
"desc": "Source filename to copy from the host OS."
},
{
"name": "to-vjunos vjunos-filename",
"desc": "Junos OS destination path (with or without a filename) to which the file is"
}
] | view
Output Fields
This command produces no output. To see the results of the copy operation, you can run Junos OS
commands for viewing files, such as file list with the destination directory, show system core-dumps, or show
log.
Sample Output
request app-engine file-copy crash
user@host> request app-engine file-copy c... | Command introduced in Junos OS Release 13.1X51-D10. | [] | |
request auto-configuration reconnect-pending | request auto-configuration reconnect-pending | Initiate reestablishment of Layer 2 wholesale sessions that correspond to access lines that are in the
pending state. Ordinarily, the most likely situations with pending sessions are handled automatically This
statement is intended to be used only when an uncommon condition might prevent automatic
reestablishment. This... | [] | view
Output Fields
When you enter this command, you are provided no feedback on the status of your request. You can
enter the show ancp neighbor detail, show subscribers client-type vlan-oob detail, and the show subscribers
summary commands before and after initiating the Port Up message to verify the operation.
Sampl... | Command introduced in Junos OS Release 16.1R4. | [
"Reestablishing Pending Access Line Sessions for Layer 2 Wholesale",
"Layer 2 Wholesale with ANCP-Triggered VLANs Overview"
] | |
request chassis afeb | request chassis afeb (offline | online | restart) | Control the operation of the compact Forwarding Engine Board (FEB). | [
{
"name": "offline",
"desc": "Take the FEB offline."
},
{
"name": "online",
"desc": "Bring the FEB online."
},
{
"name": "restart",
"desc": "Restart the FEB."
}
] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis afeb online (MX104 Router)
user@host> request chassis afeb online
AFEB is already online | Command introduced in Junos OS Release 13.2. | [] | |
request chassis beacon | request chassis beacon
<all (off | on)>
<fpc slot-number (off | on)>
<interconnect-device name (cb slot-number | fpc slot-number | (off | on)>
<node-device name (off | on)>
NOTE: request chasis beacon is not supported on the PTX10001-36MR. | (QFX Series switches only) Enable or disable the beacon LED on a QFX Series device.
(EX Series switches only) Supports the following for one or all network port status LEDs on a specified
FPC:
•
Enable the beacon for:
•
5 minutes (default)
•
A specified number of minutes (1 through 120)
•
Disable the beacon:
•
Instantl... | [
{
"name": "all",
"desc": "Turn the beacon LED either on or off on all QFabric system Interconnect and Node devices."
},
{
"name": "cb slot-number",
"desc": "Turn the beacon LED either on or off on the Control Board of the QFX3008-I Interconnect device."
},
{
"name": "fpc slot-number",
... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis beacon fpc on (EX Series and QFX Series Switches)
user@switch> request chassis beacon fpc 0 on
Beacon set to ON
request chassis beacon fpc on timer (EX Series Switches)
user@swi... | Command introduced in Junos OS Release 11.1. | [
"How to Locate a Device or Port Using the Chassis Beacon"
] | |
request chassis cb (Security) | request chassis cb (offline | online) slot slot-number | Control the operation (take the CB offline or bring online) of the Control Board (CB). | [
{
"name": "offline",
"desc": "Take the Control Board offline."
},
{
"name": "online",
"desc": "Bring the Control Board online."
},
{
"name": "slot slot-number",
"desc": "Control Board slot number."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis cb (SRX Series)
user@host> request chassis cb offline slot 2 node local
node0:
--------------------------------------------------------------------------
Offline initiated, use "... | Command introduced in Junos OS Release 9.2.
Starting with Junos OS Release 12.1X47-D15, the SRX5K-SCBE (SCB2) is introduced and starting with
Junos OS Release 15.1X49-D10, the SRX5K-SCB3 (SCB3) with enhanced midplane is introduced. | [] | |
request chassis cb | request chassis cb (offline | online) name slot slot-number
request chassis cb (PTX10008 Router)
user@host> request chassis cb offline slot 1
Offline initiated, use "show chassis environment cb" to verify
Output
The following error message is displayed if you try to offine a slot when the related node is online.
roo... | Control the operation of the Control Board (CB). | [
{
"name": "offline",
"desc": "Take the Control Board offline. NOTE: On a QFabric system, to bring the backup Control Board on a QFX3008-I Interconnect device offline, issue the request chassis cb slot backup-slot-number offline command. NOTE: Only backup Control Board can be turned offline or online. To tur... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis cb
user@host> request chassis cb offline slot 1
Backup CB 1 cannot be set offline, backup RE is online
request chassis cb interconnect-device (QFabric System)
user@switch> re... | Command introduced before Junos OS Release 7.4. | [
"Understanding Switching Control Board Redundancy"
] | |
request chassis ccg | request chassis ccg (offline | online) slot slot-number | (PTX5000 Packet Transport Routers) Control the operation of the Centralized Clock Generator (CCG). | [
{
"name": "offline",
"desc": "Take the CCG offline."
},
{
"name": "online",
"desc": "Bring the CCG online."
},
{
"name": "slot slot-number",
"desc": "CCG slot number. Replace slot-number with a value from 0 through 1."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis ccg
user@host> request chassis ccg offline slot 1
CCG 1 is offline, Backup CCG 0 is now online. | Command introduced in Junos OS 12.1x48 . | [
"Clock Sources for PTX Series Packet Transport Routers"
] | |
request chassis cfeb | request chassis cfeb (offline | online | restart) | (M7i and M10i routers only) Control the operation of the Compact Forwarding Engine Board (CFEB). | [
{
"name": "offline",
"desc": "Take the CFEB offline."
},
{
"name": "online",
"desc": "Bring the CFEB online."
},
{
"name": "restart",
"desc": "Restart the CFEB."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis cfeb
user@host> request chassis cfeb offline
CFEB Offlined | Command introduced before Junos OS Release 7.4. | [
"Configuring CFEB Redundancy on the M10i Router",
"CFEB Overview"
] | |
request chassis clock master switch | request chassis clock master switch | (PTX Series Packet Transport Routers only) Control which Centralized Clock Generator (CCG) is the
primary. | [] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis clock primary switch
user@host> request chassis clock master switch
CCG master switch initiated, use “show chassis environment ccg” to verify | Command introduced in Junos OS Release 12.1. | [] | |
request chassis cluster configuration-synchronize | request chassis cluster configuration-synchronize | On the secondary node, you can synchronize the configuration from the primary node to the secondary
node when the secondary node joins the primary node in a cluster. | [] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis cluster configuration-synchronize
{secondary:node1}
user@host> request chassis cluster configuration-synchronize
Performing configuration synchronization from remot... | Command introduced in Junos OS Release 12.1X47-D10. | [
"Understanding Automatic Chassis Cluster Synchronization Between Primary and Secondary Nodes",
"Verifying Chassis Cluster Configuration Synchronization Status",
"NTP Time Synchronization on SRX Series Devices"
] | |
request chassis cluster failover node | request chassis cluster failover node node-number
redundancy-group group-number | For chassis cluster configurations, initiate manual failover in a redundancy group from one node to the
other, which becomes the primary node, and automatically reset the priority of the group to 255. The
failover stays in effect until the new primary node becomes unavailable, the threshold of the redundancy
group reac... | [
{
"name": "node node-number",
"desc": "Number of the chassis cluster node to which the redundancy group fails over."
},
{
"name": "redundancy-group group-number",
"desc": "Number of the redundancy group on which to initiate manual failover."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis cluster failover node
user@host> request chassis cluster failover node 0 redundancy-group 1
Initiated manual failover for redundancy group 1 | Command introduced in Junos OS Release 9.0. | [] | |
request chassis cluster failover redundancy-group | request chassis cluster failover node node-number redundancy-group redundancy-group-number | For chassis cluster configurations, initiate manual failover in a redundancy group from one node to the
other, which becomes the primary node, and automatically reset the priority of the group to 255. The
failover stays in effect until the new primary node becomes unavailable, the threshold of the redundancy
group reac... | [
{
"name": "node node-number",
"desc": "Number of the chassis cluster node to which the redundancy group fails over."
},
{
"name": "redundancy-group group-number",
"desc": "Number of the redundancy group on which to initiate manual failover."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis cluster failover redundancy-group
user@host> request chassis cluster failover redundancy-group 0 node 1
{primary:node0}
user@host> request chassis cluster failover r... | Command introduced in Junos OS Release 9.0. | [
"Initiating a Chassis Cluster Manual Redundancy Group Failover",
"Verifying Chassis Cluster Failover Status"
] | |
request chassis cluster failover reset | request chassis cluster failover reset
redundancy-group group-number | In chassis cluster configurations, undo the previous manual failover and return the redundancy group to
its original settings. | [
{
"name": "redundancy-group group-number",
"desc": "Number of the redundancy group on which to reset manual failover."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis cluster failover reset
user@host> request chassis cluster failover reset redundancy-group 0 | Command introduced in Junos OS Release 9.0. | [] | |
request chassis cluster in-service-upgrade abort (ISSU) | request chassis cluster in-service-upgrade abort | Terminate an upgrade in a chassis cluster during an in-service software upgrade (ISSU). Use this
command to end the ISSU on any nodes in a chassis cluster followed by reboot to terminate the ISSU on
that device. | [] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis cluster in-service-upgrade terminate
user@host> request chassis cluster in-service-upgrade abort
Exiting in-service-upgrade window
Chassis ISSU Aborted | Command introduced in Junos OS Release 11.2. | [
"Upgrading a Chassis Cluster Using In-Service Software Upgrade"
] | |
request chassis device-mode satellite | request chassis device-mode satellite package-name | Manually install satellite software onto a switch before interconnecting the switch as a satellite device
into a Junos Fusion.
There are other methods of installing satellite software onto a satellite device, and each Junos Fusion
has individual requirements for manually installing satellite software. See Configuring J... | [
{
"name": "package-name",
"desc": "The URL to the satellite software package."
}
] | system-control
Sample Output
request chassis device-mode satellite /var/tmp/satellite-3.0R1.1-signed.tgz
user@satellite-device> request chassis device-mode satellite /var/tmp/satellite-3.0R1.1-
signed.tgz | Command introduced in Junos OS Release 14.1X53-D16. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] | |
request chassis device-mode | request chassis device-mode (interconnect-device | node-device | standalone) | Select the operating mode for the device, which acts either as a device within a QFabric system or as a
standalone switch.
NOTE:
•
Issue the request chassis device-mode command only when your management station is
connected directly to the device over a console port connection.
•
Changing the device mode erases all co... | [
{
"name": "interconnect-device",
"desc": "Set the device to operate as an Interconnect device within a QFabric system. To complete the Interconnect device mode conversion process, you must connect the device to the QFabric system management control plane and reboot the device."
},
{
"name": "node-de... | admin
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis device-mode interconnect-device (Starting in Node Device or Standalone
Mode)
user@switch> request chassis device-mode interconnect-device
Device mode set to 'interconnect-device' mode.... | Command introduced in Junos OS Release 11.2.
interconnect-device option introduced in Junos OS Release 13.1 for the QFX Series. | [
"Converting the Device Mode for a QFabric System Component",
"Understanding Interconnect Devices",
"Understanding Node Devices",
"Understanding the QFabric System Hardware Architecture"
] | |
request chassis fabric fpc | request chassis fabric fpc interconnect-device interconnect-device-name slot slot-number
(offline | online) | (QFabric systems only) Set the Interconnect device Flexible PIC Concentrator (FPC) offline or online for
the QFabric system. When the FPC is offline, traffic is redirected to other FPCs and is not lost while you
remove or install an FPC. After issuing this command, you must issue the request chassis fpc command. | [
{
"name": "interconnect-device",
"desc": ""
},
{
"name": "interconnect-device-name",
"desc": "Set the Interconnect device containing the FPC you want to bring either offline or online."
},
{
"name": "slot slot-number",
"desc": "Set the specific FPC slot on the Interconnect device."
... | admin
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis fabric fpc online
user@qfabric> request chassis fabric fpc interconnect-device IC-YW3781 offline slot 15
Graceful offline of the fabric card has been initiated. Please wait 20 seconds ... | Command introduced in Junos OS Release 11.3. | [
"request chassis fpc"
] | |
request chassis fabric pfe | request chassis fabric pfe pfe-number fpc fpc-number offline | Make a specified fabric of the packet forwarding engine (PFE) offline.
This command makes only the specified PFE of the FPC offline and rest of the PFEs of the FPC are not
affected. If a PFE of an FPC is affected because of fabric path wedge errors, the affected PFE is disabled
and the associated fabric goes offline a... | [
{
"name": "pfe-number",
"desc": ""
},
{
"name": "[0–3]",
"desc": ""
},
{
"name": "fpc-number",
"desc": "[0–11] or [0–5] or [0–19] or [0–2], depending on the type of the chassis."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 17.2. | [] | |
request chassis fabric plane | request chassis fabric plane plane-number (offline | online) | (M120 and MX Series routers and EX8200 switches only) Control the operation of the specified fabric
plane.
On an MX480 or MX240 series router, you can configure the active control board for redundancy mode
or increased bandwidth mode. When running in increased bandwidth mode, MX series routers with Trio
chips and the M... | [
{
"name": "offline",
"desc": "Take the fabric plane offline. Use the request chassis fabric plane plane-number offline command to clear a FAULT state on a fabric plane. To bring the fabric plane back online, use the request chassis fabric plane plane-number online command."
},
{
"name": "online",
... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis fabric plane 0 online
user@host> request chassis fabric plane 0 online
Online initiated, use “show chassis fabric plane” to verify
request chassis fabric plane 0 offline
user@ho... | Command introduced in Junos OS Release 8.0. | [] | |
request chassis feb | request chassis feb slot slot-number (offline | online | restart) <force> | Offline, online, restart the specified FEB. Upon restart, the FEB goes offline and online within the
stipulated time. FEB traffic is forwarded before power off. Traffic is recovered after FEB is online.
On ACX7509 routers, when a primary FEB is made offline or restarted, the switchover to backup FEB
does not take place... | [
{
"name": "slot slot-number",
"desc": "FEB slot number. Replace slot-number with the FEB slot number value of your platform."
},
{
"name": "offline",
"desc": "Bring the specified FEB offline."
},
{
"name": "online",
"desc": "Bring the specified FEB online."
},
{
"name": "rest... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis feb (ACX1000 Router)
user@host> request chassis feb slot 0 restart
FEB will be restarted NOW.
request chassis feb (ACX7509 Router) (Primary FEB)
NOTE: Slot 1 is the primary FEB... | Command introduced in Junos OS Release 8.0.
Command support introduced for ACX7509 devices in Junos OS Evolved Release 21.4R1.
Warning message introduced for ACX7509 devices in Junos OS Evolved Release 23.2R2. | [
"Understanding Switching Control Board Redundancy"
] | |
request chassis fpc optical-module amplifier-chain ila firmware-upgrade | request chassis optical-module amplifier-chain ila firmware-upgrade fpc-slot fpc-slot ila ila-
number | To transfer the firmware image from the integrated photonic line card (IPLC) module to a particular
optical inline amplifier (ILA) and issue a firmware upgrade. | [
{
"name": "fpc-slot",
"desc": "Slot number of the FPC or PIC in which the 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 firmware-upgrade
user@host> request chassis fpc optical-module amplifier-chain ila firmware-upgrade fpc-slot 3
ila-number 0
IP... | 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 chassis fpc optical-module amplifier-chain ila hard-reset | request chassis optical-module amplifier-chain ila hard-reset fpc-slot fpc-slot ila ila-number | Apply a hard reset to the optical inline amplifier (ILA). Issuing a hard reset disrupts the network traffic on
the optical ILA. | [
{
"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 hard-reset
user@host> request chassis fpc optical-module amplifier-chain ila hard-reset fpc-slot 3 ila-
number 3
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 chassis fpc optical-module firmware-upgrade | request chassis fpc optical-module firmware-upgrade fpc-slot fpc-slot | Upgrade the firmware of the integrated photonic line card (IPLC) module installed in the Flexible PIC
Concentrator (FPC) or PIC slot. | [
{
"name": "fpc-slot",
"desc": "Slot number of the FPC or PIC in which the IPLC module resides."
}
] | 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 firmware-upgrade
user@host> request chassis fpc optical-module firmware-upgrade fpc-slot 4
IPLC 2 upgrade finished | Statement introduced in Junos OS Release 15.1F6 and 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 chassis fpc slc | request chassis fpc fpc-slot slc slc-id (offline | restart | online) | (Applies to the base system or BSYS). Start, stop or restart the sub line cards (SLCs).
NOTE: On BSYS, entering the request chassis fpc fpc-slot offline/restart/online command
initiates the offline/online/restart process of all the SLCs (sub line cards) of the selected
line card (FPC). On GNF, entering the request chas... | [
{
"name": "fpc-slot",
"desc": "Specify the line card slot."
},
{
"name": "slc-id",
"desc": "Specify the SLC you want to take offline, bring online or restart."
}
] | View | Command introduced in Junos OS Release 21.1R1. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.