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 |
|---|---|---|---|---|---|---|---|
cellular-options | cellular-options {
roaming-mode (home only | automatic)
gsm-options {
select-profile profile-name;
profiles {
profile-name {
sip-user-id simple-ip-user-id;
sip-password simple-ip-password;
access-point-name apn;
authent... | [edit interfaces interface-name] | Configure options for connecting a 3G wireless modem interface to a cellular network. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [] |
centralized | centralized; | [edit protocols lacp ppm] | Disable distributed periodic packet management (PPM) processing for Link Aggregation Control Protocol
(LACP) packets and run all PPM processing for LACP packets on the Routing Engine.
This statement disables distributed PPM processing for only LACP packets. You can disable distributed
PPM processing for all packets tha... | [] | 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. | [
"Configuring Distributed Periodic Packet Management on an EX Series Switch (CLI Procedure)",
"Configuring Aggregated Ethernet LACP (CLI Procedure)",
"Configuring Distributed Periodic Packet Management",
"Configuring Link Aggregation"
] |
cert-file (Scripts) | cert-file path; | [edit event-options event-script file filename],
[edit system extensions extension-service application file filename],
[edit system scripts commit file filename],
[edit system scripts op file filename],
[edit system scripts snmp file filename] | Specify the certificate file (Root CA or self-signed) that the device uses to validate the server's certificate
when you refresh a local script from an HTTPS server.
When you issue the set refresh or set refresh-from configuration mode command to refresh a single script
or all scripts of a given type from an HTTPS serv... | [
{
"name": "path",
"desc": "Absolute path to the certificate (Root CA or self-signed) in Privacy-Enhanced Mail (PEM) format that is used to validate the certificate of the server from which you refresh the script."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1 and Junos OS Evolved Release 25.2R1. | [
"Configure and Use a Master Source Location for a Script"
] |
certificate (Juniper Secure Connect) | certificate {
no-expiry-warning;
no-pin-request-per-connection;
warn-before-expiry days;
} | [edit security remote-access client-config] | Define certificate identifier parameters for Juniper Secure Connect. | [
{
"name": "no-expiry-warning",
"desc": "Disable certificate expiry warning."
},
{
"name": "no-pin-request-per-connection",
"desc": "Disable certificate pin request per connection."
},
{
"name": "warn-before-expiry",
"desc": "Enable certificate expiration warning in days before the ex... | security | Statement introduced in Junos OS Release 20.3R1. | [
"Juniper Secure Connect Administrator Guide"
] |
certificate | certificate {
local-certificate certificate-id;
peer-certificate-type (pkcs7 | x509-signature);
policy-oids oid;
trusted-ca {
ca-profile ca-profile-name;
trusted-ca-group trusted-ca-group-name;
}
} | [edit security ike policy policy-name] | Specify usage of a digital certificate to authenticate the virtual private network (VPN) initiator and
recipient. | [
{
"name": "local-certificate certificate-id",
"desc": "Specify a particular certificate when the local device has multiple loaded"
},
{
"name": "peer-certificate-type",
"desc": "Specify a preferred type of certificate (PKCS7 or X509)."
},
{
"name": "pkcs7",
"desc": "Public-Key Crypto... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. policy-oids option added in Junos OS Release 12.3X48-
D10. Support for trusted-ca option added in Junos OS Release 18.1R1. | [
"IPsec Overview",
"Certificate Authority Profiles"
] |
certificate-authority (REST API) | certificate-authority certificate-authority-profile-name; | [edit system services rest https mutual-authentication] | Set the server certificate authority profile when configuring mutual authentication. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
certificate-id | certificate-id {
ca-profile ca-profile-name;
challenge-password password;
re-enroll-trigger-time-percentage percentage;
re-generate-keypair;
validity-period days;
} | [edit security auto-re-enrollment] | Specify a router certificate for auto-reenrollment. The ID is the same as that used to get the end entity’s
certificate from the issuing certificate authority. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Auto-Reenrollment of a Router Certificate"
] |
certificate-verification | certificate-verification [ optional | required | warning ] | [edit services unified-access-control] | This option determines whether server certificate verification is required when initiating a connection
between an SRX Series Firewall and a Junos Pulse Access Control Service in a UAC configuration. If no
CA profile contains the certificate authority (CA) that signed the configured server certificate for the
Access Co... | [
{
"name": "optional",
"desc": "Certificate verification is not required. If the CA certificate is not specified in the ca-profile"
},
{
"name": "required",
"desc": "Certificate verification is required. If the CA certificate is not specified in the ca-profile"
},
{
"name": "Default: warn... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Understanding Communications Between the Junos OS Enforcer and the IC Series UAC Appliance",
"Understanding User Role Firewalls"
] |
certificates | certificates {
cache-size bytes;
cache-timeout-negative seconds;
certification-authority ca-profile-name {
ca-name ca-identity;
crl file-name;
encoding (binary | pem);
enrollment-url url-name;
file certificate-filename;
ldap-url url-name;
}
enrollment-... | [edit security] | (Encryption interface on M Series and T Series routers and EX Series switches only) Configure the digital
certificates for IPsec.
The remaining statements are explained separately. See CLI Explorer. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Digital Certificates for an ES PIC"
] |
certification-authority | certification-authority ca-profile-name {
ca-name ca-identity;
crl file-name;
encoding (binary | pem);
enrollment-url url-name;
file certificate-filename;
ldap-url url-name;
} | [edit security certificates] | (Encryption interface on M Series and T Series routers and EX Series switches only) Configure a
certificate authority profile name.
Configure certification authority (CA) for X.509 certificate. | [
{
"name": "profile-name",
"desc": "Name of this CA configuration."
},
{
"name": "ca-name name",
"desc": "Name of the CA."
},
{
"name": "crl filename",
"desc": "Certificate revocation list (CRL) filename."
},
{
"name": "encoding",
"desc": "Certificate encoding, either bina... | 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 the Certificate Authority Properties for an ES PIC",
"Configuring the Certificate Authority Properties for an ES PIC"
] |
ces-psn-channel (tdm-options) | ces-psn-channel {
dmac-address address;
mode mode;
vlan-id-1 vlanid;
vlan-id-2 vlanid;
} | [edit interfaces interface-name tdm-options] | Configure the CES (Circuit Emulation Service) PSN (Packet Switched Networks) Channel parameters. Use
the parameters to specify the destination MAC address, encapsulation type, and vlan tagging. | [
{
"name": "dmac-address",
"desc": ""
},
{
"name": "address",
"desc": "Destination MAC address to be paired with the smart SFP."
},
{
"name": "mode mode",
"desc": "Encapsulation mode for the TDM traffic for further network processing. Possible values are: MEF8 and MPLS. Default mode i... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4. | [] |
cfeb | cfeb slot-number (always | preferred); | [edit chassis redundancy] | On M10i routers only, configure which Compact Forwarding Engine Board (CFEB) is the primary and
which is the backup.
Default
By default, the CFEB in slot 0 is the primary and the CFEB in slot 1 is the backup. | [
{
"name": "slot-number",
"desc": "Specify which slot is the primary and which is the backup."
},
{
"name": "always",
"desc": "Define this CFEB as the sole device."
},
{
"name": "preferred",
"desc": "Define this CFEB as the preferred device of at least two."
}
] | 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 CFEB Redundancy on the M10i Router"
] |
cflowd (Discard Accounting) | cflowd hostname {
aggregation {
autonomous-system;
destination-prefix;
protocol-port;
source-destination-prefix {
caida-compliant;
}
source-prefix;
}
autonomous-system-type (origin | peer);
port port-number;
version format;
} | [edit forwarding-options accounting name output] | Collect an aggregate of sampled flows and send the aggregate to a specified host system that runs the
collection utility cfdcollect.
You can configure up to one version 5 and one version 8 flow format at the [edit forwarding-options
accounting name output] hierarchy level. | [
{
"name": "hostname",
"desc": "The IP address or identifier of the host system (the workstation running the cflowd utility)."
}
] | 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. | [
"Directing Traffic Sampling Output to a Server Running the cflowd Application",
"Enabling Flow Aggregation"
] |
cflowd (Flow Monitoring) | cflowd hostname {
port port-number;
} | [edit forwarding-options monitoring name inet output] | Collect an aggregate of sampled flows and send the aggregate to a specified host system that runs the
collection utility cfdcollect.
You can configure up to eight version 5 flow formats at the [edit forwarding-options monitoring name output]
hierarchy level. Version 8 flow formats are not supported for flow-monitoring ... | [
{
"name": "hostname",
"desc": "IP address or identifier of the host system (the workstation running the cflowd utility)."
}
] | 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. | [
"Enabling Flow Aggregation",
"Directing Traffic Sampling Output to a Server Running the cflowd Application",
"Configuring Passive Flow Monitoring"
] |
cfp-to-et | cfp-to-et; | [edit chassis fpc slot] | Make the interface et-0/1/0 (on the QSFP28 port) available for use. After you configure the set chassis
fpc 0 cfp-to-et command and commit the configuration, you need to restart the FPC by executing the
restart chassis-control command. After the FPC comes online, interface et-0/1/0 is created and
et-0/2/1(on the CFP2 p... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1-S1. | [] |
cgn-pic | cgn-pic; | [edit interfaces interface-name services-options] | Restrict usage of the service PIC to carrier-grade NAT (CGN) or associated services (intrusion detection,
stateful firewall, and softwire). All memory is available for CGN or related services and can be used for
CGN scaling.
The cgn-pic statement is supported only on the MS-DPC, MS-100, MS-400, and MS-500 line cards. T... | [] | 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. | [
"Carrier-Grade NAT Feature Comparison for Junos Address Aware by Type of Interface Card"
] |
chain | chain {
expression boolean-expression;
member (Security IDP) member-name {
attack-type (Security Anomaly) {
(anomaly ...same statements as in [edit security idp custom-attack attack-name
attack-type anomaly] hierarchy level | signature ...same statements as in [edit security idp
custom-att... | [edit security idp custom-attack attack-name attack-type] | Chain attack object combines multiple signatures and/or protocol anomalies into a single object. Traffic
must match all of the combined signatures and/or protocol anomalies to match the chain attack object. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
chain-order (Application Identification) | chain-order; | [edit services application-identification application application-name over protocol-type
signature l4-l7-signature-name] | Read members in order. By default, chain ordering is turned off. If there is only one member, this option
is ignored. | [] | system—To view this statement in the configuration.
system-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 Releases 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960 using the MX-SPC3 services card. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
chained-composite-next-hop | chained-composite-next-hop {
ingress;
transit;
} | [edit logical-systems logical-system-name routing-options forwarding-table],
[edit routing-options forwarding-table]
NOTE: The [edit logical-systems] hierarchy level is not supported on the QFX10000
switches. | Allows you to configure the chained composite next hops for devices handling ingress or transit traffic in
the network.
Chained composite next hops help to facilitate the handling of large volumes of transit traffic in the core
of large networks by allowing the router to process much larger volumes of routes. A chaine... | [
{
"name": "ingress",
"desc": "Enable or disable composite chained next hop for ingress traffic."
},
{
"name": "transit",
"desc": "(PTX and QFX10000) Enable or disable composite chained next hop for transit traffic. Starting in Junos OS Release 14.1, the transit l3vpn statement is enabled by defa... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Accepting Route Updates with Unique Inner VPN Labels in Layer 3 VPNs",
"Chained Composite Next Hops for Transit Devices for VPNs",
"Example: Configuring Chained Composite Next Hops for Direct PE-PE Connections in VPNs",
"transit (Chained Composite Next Hops)"
] |
challenge-length (Static and Dynamic PPP) | challenge-length minimum minimum-length maximum maximum-length; | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit ppp-options chap],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options chap],
[edit interfaces pp0 unit unit-number ppp-options chap] | Modify the length of the Challenge Handshake Authentication Protocol (CHAP) challenge by specifying
the minimum and maximum allowable length, in bytes.
BEST PRACTICE: We recommend that you configure both the minimum length and the
maximum length of the CHAP challenge to at least 16 bytes. | [
{
"name": "minimum-length",
"desc": "Minimum length, in bytes, of the CHAP challenge. Range: 8 through 63 Default: 16"
},
{
"name": "maximum-length",
"desc": "Maximum length, in bytes, of the CHAP challenge. The maximum-length must be equal to or greater than the minimum-length. Range: 8 thro... | 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. | [
"PPP Subscriber Access Networks Overview"
] |
challenge-password | challenge-password password; | [edit security pki auto-re-enrollment certificate-id] | Specify the challenge password used by the certificate authority (CA) for router certificate enrollment
and revocation. This challenge password must be the same used when the router certificate was
originally configured. | [
{
"name": "password",
"desc": "The password required by the CA."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Auto-Reenrollment of a Router Certificate"
] |
change-configuration (Event Policy) | change-configuration {
commands {
"command";
}
commit-options {
check <synchronize>;
force;
log "comment-string";
synchronize;
}
retry count number interval seconds;
user-name username;
} | [edit event-options policy policy-name then] | When the associated event policy is triggered, execute the Junos OS configuration mode commands to
update the candidate configuration and commit the changes.
NOTE: Do not use the change-configuration statement to modify the configuration on dual
Routing Engine devices that have nonstop active routing (NSR) enabled, bec... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configure an Event Policy to Change the Configuration"
] |
channel | channel channel-id {
tunnel-services {
bandwidth(100g | 10g | 1g | 2.5g | 200g | 20g | 300g | 30g | 400g | 40g |
480g | 50g | 60g | 70g | 80g | 90g | bandwidth);
}
} | [edit chassis afeb slot name pfe core],
[edit chassis cfeb slot name pfe core],
[edit chassis feb slot name pfe core],
[edit chassis fpc name pfe core],
[edit chassis lcc name fpc name pfe core],
[edit chassis member name fpc name pfe core],
[edit chassis tfeb slot name pfe core] | Configure the Channel number.
•
The channel (per core) number for ACX7024 and ACX7024X is 2.
•
The channel (per core) number for ACX7100-48L and ACX7100-32C is 8.
•
The channel (per core) number for ACX7509 is 8.
•
The channel (per core) number for ACX7348 and ACX7332 is 4. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 24.1R1 for ACX Series Routers. | [] |
channel-params | channel-params {
name;
ces-psn-dmac-address ces-psn-dmac-address;
ces-psn-mode (MEF8 | MPLS);
ces-psn-vlan-id-1 ces-psn-vlan-id-1;
ces-psn-vlan-id-2 ces-psn-vlan-id-2;
iwf-decap-ecid iwf-decap-ecid;
iwf-encap-ecid iwf-encap-ecid;
... | [edit interfaces interface name tdm-options],
[edit interfaces interface-range name tdm-options] | Channelized TDM interworking functionality (IWF) and CES PSN channel parameters | [
{
"name": "name",
"desc": "Channel number for CES PSN channel params Range: through"
},
{
"name": "ces-psn-dmac-address",
"desc": "Destination MAC-address to be paired with the Smart SFP with CES"
},
{
"name": "encapsulation",
"desc": ""
},
{
"name": "ces-psn-mode",
"des... | [none specified] | Statement introduced in Junos OS Evolved Release 25.4R1 | [] |
channel-speed | channel-speed (10g | 25g | 50g | 100g | disable-auto-speed-detection) ; | [edit chassis fpc slot-number pic pic-number (port port-number | port-range port-range-low port-
range-high)] | Enable the specified port on the Physical Interface Card (PIC) to perform in the specified channel speed.
Additionally, you can disable auto-speed detection.
Default
The default speed of the platform is the maximum speed supported on the platform. Refer Port Settings
for the supported speed details. | [
{
"name": "10g",
"desc": "Set the channel speed to 10g (10-Gigabit Ethernet)."
},
{
"name": "25g",
"desc": "Set the channel speed to 25g (25-Gigabit Ethernet)."
},
{
"name": "50g",
"desc": "Set the channel speed to 50g (50-Gigabit Ethernet)."
},
{
"name": "100g",
"desc": ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Port Settings"
] |
chap (Dynamic PPP) | chap {
challenge-length minimum minimum-length maximum maximum-length;
local-name name;
} | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit ppp-options]
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options] | Specify CHAP authentication in a PPP dynamic profile.
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 9.5.
Support at the [edit dynamic-profiles profile-name interfaces "$junos-interface-ifd-name" unit “$junos-
interface-unit” ppp-options] hierarchy level introduced in Junos OS Release 12.2. | [
"Dynamic Profiles Overview",
"Configuring Dynamic Authentication for PPP Subscribers",
"Attaching Dynamic Profiles to Static PPP Subscriber Interfaces",
"Applying PPP Attributes to L2TP LNS Subscribers per Inline Service Interface"
] |
chap (L2TP) | chap; | [edit access group-profile profile-name ppp ppp-options] | (MX Series routers only) Specify CHAP authentication for PPP subscribers in an L2TP LNS user group
profile. | [] | 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. | [
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
chap | chap {
access-profile name;
challenge-length minimum minimum-length maximum maximum-length;
default-chap-secret name;
local-name name;
passive;
} | [edit interfaces interface-name ppp-options],
[edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options] | Allow each side of a link to challenge its peer, using a “secret” known only to the authenticator and that
peer. The secret is not sent over the link.
By default, PPP CHAP is disabled. If CHAP is not explicitly enabled, the interface makes no CHAP
challenges and denies all incoming CHAP challenges.
For ATM2 IQ interfac... | [] | 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 the PPP Challenge Handshake Authentication Protocol",
"Applying PPP Attributes to L2TP LNS Subscribers with a User Group Profile",
"Applying PPP Attributes to L2TP LNS Subscribers per Inline Service Interface"
] |
charging-id (OCS Partition) | charging-id number; | [edit access ocs partition partition-name] | Include the 3GPP-Charging-Id AVP value in all CCR-GY messages. | [
{
"name": "number",
"desc": "3GPP-Charging-Id AVP value to include in all CCR-GY messages."
}
] | 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 OCS Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between the PCRF, PCEF, and OCS"
] |
charging-service-list | charging-service-list ocs; | [edit access profile profile-name] | Configure the list of charging services with which to communicate for the broadband Policy and
Charging Enforcement Function (BPCEF).
NOTE: Currently, if you configure this statement, you must also configure the
provisioning-order statement to pcrf. | [
{
"name": "ocs",
"desc": "Use Online Charging Services (OCS) as the list of charging services with which to communicate."
}
] | 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. | [
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between the PCRF, PCEF, and OCS"
] |
chassis (QFabric System) | chassis {
interconnect-device {
alarm {
(ethernet (Alarm) | management-ethernet) {
link-down (red | yellow | ignore);
}
}
container-devices {
device-count number;
}
craft-lockout {
alarm {
interfa... | [edit] | Configure chassis-specific properties for the switch.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
chassis (Subscriber Limits) | chassis {
limit limit;
} | [edit system services resource-monitor subscribers-limit client-type name] | Configure the maximum number of subscribers of the specified client type allowed to be logged in on
the chassis. When that number is reached, subsequent logins on the chassis are denied until the current
number of subscribers drops below the maximum allowed. You can also specify the maximum number of
subscribers of a c... | [
{
"name": "limit",
"desc": "Maximum number of subscribers. Range: 1 through 1,000,000"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Limiting Subscribers by Client Type and Hardware Element with Resource Monitor",
"Resource Monitoring for Subscriber Management and Services"
] |
chassis | chassis {
aggregated-devices {...}
alarm {...}
alarm-port {...}
ambient-temperature;
auto-image-upgrade;
auto-satellite-conversion;
cb name {...}
config-button (no-clear | no-rescue);
container-devices {...}
copy-tos-to-outer {...}
craft-lockout;
dedicated-ukern-cpu (B... | [edit] | Configure router chassis properties.
NOTE: Use Feature Explorer to confirm platform and release support for specific
features. | [
{
"name": "config-button",
"desc": "Config button behavior settings."
},
{
"name": "no-clear",
"desc": "Don't reset to factory-default configuration."
},
{
"name": "no-rescue",
"desc": "Don't reset to rescue configuration."
},
{
"name": "disable-fm",
"desc": "Disable Fabr... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | satellite satellite-name option is added in Junos OS Release 24.4R1.
optics option introduced in Junos OS Evolved Release 25.2R1 for PTX Series routers.
Statement introduced before Junos OS Release 7.4. | [] |
chassis-id (Aggregated Ethernet Interface) | chassis-id chassis-id; | [edit interfaces aggregated-ether-options mc-ae] | Specify the chassis ID of the multichassis aggregated Ethernet interface device. LACP uses the chassis
ID to calculate the port number of the multichassis link aggregation group (MC-LAG) physical member
links. | [] | 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. | [] |
chassis-id (LLDP) | chassis-id {
chassis-id-type (chassis-component | interface-alias | interface-name | locally-assigned | mac-
address | network-address | port-component);
chassis-id-value chassis-id-value;
} | [edit logical-systems name protocols lldp],
[edit protocols lldp] | Configure the chassis-id to be used to generate the Chassis ID TLV advertised to the LLDP neighbors. | [
{
"name": "chassis-id-type",
"desc": "Chassis-id-type to be used for Chassis ID TLV generation"
},
{
"name": "chassis-component",
"desc": "User define chassis component name."
},
{
"name": "interface-alias",
"desc": "Interface description or name on which LLDPDU is sent."
},
{
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
check-bytes (Application Identification) | check-bytes max-bytes-to-check; | [edit services application-identification application application-name over protocol-type
signature l4-l7-signature-name member member-name] | Specify the maximum number of bytes to be inspected. This statement applies to TCP and UDP
protocols for stream context. It is not considered for other protocols and contexts. | [
{
"name": "max-bytes-to-check",
"desc": "Number of bytes to be inspected. Range: 1 through 5000 Default: Not configured"
}
] | system—To view this statement in the configuration.
system-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 Releases 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960 using the MX-SPC3 services card. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
check-zero | (check-zero | no-check-zero); | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit logical-systems logical-system-name routing-instances routi... | Check whether the reserved fields in a RIP packet are zero:
•
check-zero—Discard version 1 packets that have nonzero values in the reserved fields and version 2
packets that have nonzero values in the fields that must be zero. This default behavior implements
the RIP version 1 and version 2 specifications.
•
no-check-z... | [] | 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. | [] |
checksum (Scripts) | checksum (md5 | sha-256 | sha1) hash; | [edit event-options event-script file filename],
[edit system scripts commit file filename],
[edit system scripts op file filename],
[edit system scripts snmp file filename],
[edit system extensions extension-service application file filename] | For Junos OS commit scripts, event scripts, op scripts, SNMP scripts, and scripts developed using the
Juniper Extension Toolkit (JET) specify the MD5, SHA-1, or SHA-256 checksum hash. When Junos OS
executes a local commit, event, op, SNMP, or JET script, the system verifies the integrity of the script by
using the conf... | [
{
"name": "md5 hash",
"desc": "MD5 checksum of this script. This option is deprecated starting in Junos OS Releases 18.2R2 and 18.3R1."
},
{
"name": "sha-256 hash",
"desc": "SHA-256 checksum of this script."
},
{
"name": "sha1 hash",
"desc": "SHA-1 checksum of this script. This optio... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 9.5.
Statement introduced for the [edit system extensions extension-service application file filename] hierarchy
level in Junos OS Release 16.1 for MX80, MX104, MX240, MX480, MX960, MX2010, MX2020, vMX
Series.
md5 and sha1 options deprecated in Junos OS Releases 18.2R2 and 18.3R... | [
"Configuring Checksum Hashes for a Commit Script",
"Configuring Checksum Hashes for an Event Script",
"Configuring Checksum Hashes for an Op Script",
"Configuring Checksum Hashes for an SNMP Script",
"Executing an Op Script from a Remote Site"
] |
checksum-validate | checksum-validate {
match (equal | greater-than | less-than | not-equal);
value checksum-value;
} | [edit security idp custom-attack attack-name attack-type signature protocol ipv4]
[edit security idp custom-attack attack-name attack-type signature protocol tcp]
[edit security idp custom-attack attack-name attack-type signature protocol udp]
[edit security idp custom-attack attack-name attack-type signature protocol ... | Allow IDP to validate checksum field against the calculated checksum. | [
{
"name": "value checksum-value",
"desc": "Match a decimal value. Range: 0 through 65,535"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
child-inactivity-timeout | child-inactivity-timeout seconds; | [edit applications application ike-esp-nat] | For an IKE ALG application, configure the ESP session (IPsec data traffic) idle timeout. If no IPsec data
traffic is passed on the ESP session in this time, the session is deleted.
The IKE ALG enables the passing of IKEv1 and IPsec packets through NAPT-44 and NAT64 rules
between IPsec peers that are not NAT-T compliant... | [
{
"name": "seconds",
"desc": "Number of seconds. Default: 800 seconds"
}
] | 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. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring Application Properties"
] |
children | children {
child-name {
esp-proposal esp-proposal;
local-traffic-selector {
(ipv4-prefix ipv4-prefix | ipv6-prefix ipv6-prefix);
port port;
protocol protocol;
}
mode (transport | tunnel);
rekey-time rekey-time;
remote-traffic-select... | [edit security host-vpn connections connection-name] | Configure child details to establish a security association (SA). An SA describes a specific negotiated set
of parameters to protect traffic between two host for a certain period of time. | [
{
"name": "child-name",
"desc": "Specify the child SA name."
},
{
"name": "esp-proposal",
"desc": ""
},
{
"name": "esp-proposal",
"desc": "Specify the algorithms to use in negotiating the child SA from among the pre-selected combinations available, which represent the encryption algo... | 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. | [] |
cipher-list (REST API) | cipher-list [ cipher-1 cipher-2 cipher-3 ...]; | [edit system services rest https] | Specify the set of ciphers the server can use to perform encryption and decryption functions. If this
option is not configured, the server accepts any supported suite that is available. | [
{
"name": "rsa-with-RC4-128-md5",
"desc": "RSA, 128- bit RC4, MD5 hash"
},
{
"name": "rsa-with-RC4-128-sha",
"desc": "RSA, 128-bit RC4, SHA hash"
},
{
"name": "rsa-with-3DES-ede-cbc-sha",
"desc": "RSA, 3DES EDE/CBC, SHA hash"
},
{
"name": "dhe-rsa-with-3DES-ede-cbc-sha",
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
cipher-suite (MACsec) | cipher-suite encryption-algorithm-name; | [edit security macsec connectivity-association connectivity-association-name] | Specify the set of ciphers used to encrypt traffic on an Ethernet link that is secured with Media Access
Control Security (MACsec). The encryption used by MACsec ensures that the data in the Ethernet frame
cannot be viewed by anybody monitoring traffic on the link. MACsec encryption is optional and user-
configurable. ... | [
{
"name": "gcm-aes-128",
"desc": "GCM-AES-128 has a maximum key size of 128 bits."
},
{
"name": "gcm-aes-xpn-128",
"desc": "GCM-AES-XPN-128 has a maximum key size of 128 bits and extended packet number."
},
{
"name": "gcm-aes-256",
"desc": "GCM-AES-256 has a maximum key size of 256 b... | admin— To view this statement in the configuration.
admin-control— To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2R1. | [
"Configuring MACsec on EX, QFX and SRX Devices",
"Configuring Media Access Control Security (MACsec) on Routers"
] |
circuit-id (DHCP Relay Agent) | circuit-id {
include-irb-and-l2;
keep-incoming-circuit-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 forwarding-options dhcp-relay group group-name relay-
option-82... | 21.2R1
Starting with Junos OS Release 21.2R1, QFX Series switches support the circuit-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 8.3.
include-irb-and-l2 , no-vlan-interface-name, and use-vlan-id options added 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.
... | [
"Using DHCP Relay Agent Option 82 Information",
"Configuring Option 82 Information"
] |
circuit-id (VLAN Authentication Username) | circuit-id; | [edit interfaces interface-name auto-configure vlan-ranges authentication username-include] | Include the agent circuit identifier (ACI) in the username sent to RADIUS for authentication of the
dynamic VLAN. The ACI is conveyed by the Access-Loop-Circuit-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"
] |
circuit-id | circuit-id {
prefix {
host-name;
logical-system-name;
routing-instance-name;
}
use-interface-description (device | logical);
use-vlan-id;
} | For platforms with Enhanced Layer 2 Software (ELS):
[edit vlans vlan-name forwarding-options dhcp-security option-82]
For MX Series platforms:
[edit bridge-domains bridge-domain-name forwarding-options dhcp-security option-82] | Configure the circuit-id suboption (suboption 1) of DHCP option 82 (the DHCP relay agent information
option) in DHCP packets destined for a DHCP server. This suboption identifies the circuit (the interface,
the VLAN, or both) on which the DHCP request arrived.
The remaining statements are explained separately. See CLI ... | [] | 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] 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"
] |
circuit-type (DHCP Local Server) | circuit-type; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 authentication username-include],
[edit logic... | Specify that the circuit type is concatenated with the username during the subscriber authentication or
client authentication process. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Specifying Authentication Support"
] |
circuit-type (DHCP Relay Agent) | circuit-type; | [edit forwarding-options dhcp-relay authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name auth... | Specify that the circuit type is concatenated with the username during the subscriber authentication or
client authentication process. Use the statement at the [edit ... dhcpv6] hierarchy levels to configure
DHCPv6 support. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1. | [
"Specifying Authentication Support",
"Creating Unique Usernames for DHCP Clients"
] |
circuit-type (Subscriber Interface) | circuit-type; | [edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication username-include] | Specify that the circuit type is concatenated with the username during the subscriber authentication
process. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring VLAN Interface Username Information for AAA Authentication"
] |
cisco-interoperability | cisco-interoperability send-lip-remove-link-for-link-reject; | [edit interfaces interface-name mlfr-uni-nni-bundle-options] | FRF.16 interoperability settings. | [
{
"name": "send-lip-remove-link-for-link-reject",
"desc": "Send Link Integrity Protocol remove link when an add-link rejection"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring SONET APS Interoperability with Cisco Systems FRF.16"
] |
cisco-nas-port-info (L2TP Tunnel Switching) | cisco-nas-port-info action; | [edit access tunnel-switch-profile profile-name avp] | Define a tunnel profile for subscriber access.
Specify the action taken on the Cisco NAS Port Info AVP (100) in the L2TP packets during tunnel
switching if the AVP is negotiated when the first session is created. | [
{
"name": "action",
"desc": "One of the following actions:"
},
{
"name": "drop",
"desc": "Drop the AVP."
},
{
"name": "regenerate",
"desc": "Regenerate the AVP based on the local policy at the LTS and send it in the switched"
},
{
"name": "relay",
"desc": "Forward the AVP... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"L2TP Tunnel Switching For Multiple-Domain Networks"
] |
civic-based | civic-based {
ca-type name {
ca-value ca-value;
}
country-code country-code;
what what;
} | [edit protocols lldp-med interface (all | interface-name) location] | For Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED), configure the geographic
location to be advertised from the device to the MED. This information is used during emergency calls
to identify the location of the MED.
Default
Disabled. | [
{
"name": "country-code code",
"desc": "(Required) Configure the two-letter ISO 3166 country code in capital ASCII letters; for example, US or DE. The code is part of the location information. Location information is advertised from the device to the MED, and is used during emergency calls to identify the l... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
what modified in Junos OS Release 9.2 for EX Series to display new default. | [
"Example: Setting Up VoIP with 802.1X and LLDP-MED on an EX Series Switch",
"Configuring LLDP-MED (CLI Procedure)"
] |
ckn (MX Series) | ckn hexadecimal-number; | [edit security macsec connectivity-association connectivity-association-name pre-shared-key] | Specifies the connectivity association key name (CKN) for a pre-shared key.
A pre-shared key includes a CKN and a connectivity association key (CAK). A pre-shared key is
exchanged between two devices at each end of a point-to-point link to enable MACsec using dynamic
security keys. The MACsec Key Agreement (MKA) proto... | [
{
"name": "hexadecimal-number",
"desc": "The key name, in hexadecimal format. The key name is 32 hexadecimal characters in length. If you enter a key name that is less then 32 characters long, the remaining characters are set to 0. On MX10003 router, if you configure the length of CKN to the value less tha... | 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"
] |
ckn | ckn hexadecimal-number; | [edit security macsec connectivity-association connectivity-association-name pre-shared-key],
[edit security macsec connectivity-association connectivity-association-name fallback-key] | Specifies the connectivity association key name (CKN) for a preshared key.
A preshared key includes a CKN and a connectivity association key (CAK). A preshared key is exchanged
between two devices at each end of a point-to-point link to enable MACsec using dynamic security
keys. The CKN is a 64-digit hexadecimal number... | [
{
"name": "hexadecimal-number",
"desc": "The key name, in hexadecimal format. The key name is 64 hexadecimal characters in length. To maximize security, we recommend configuring all 64 digits of a CKN. If you enter a key name that is less then 64 characters long, the remaining characters are set to 0. Howev... | 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 devices 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)"
] |
class (CoS-Based Forwarding) | class class-name {
classification-override {
forwarding-class class-name;
}
} | [edit class-of-service forwarding-policy] | Configure CoS-based forwarding class. | [
{
"name": "class-name",
"desc": "Name of the routing policy class."
}
] | 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. | [
"Overriding the Input Classification"
] |
class (Defining Login Classes) | class class-name {
allow-hidden-commands;
no-hidden-commands {
except ["regular expression or command 1" "regular expression or command 2" ...];
}
access-end hh:mm;
access-start hh:mm;
allow-commands "(regular-expression1)|(regular-expression2)...";
allow-commands-regexps ["regular ... | [edit system login] | Define a login class. All users who log in to the router or switch must be in a login class. Therefore, you
must define a Junos OS login class for each user or type of user. You can define any number of login
classes depending on the types of permissions the users need. You may not need to define any login
classes; Jun... | [
{
"name": "class-name",
"desc": "A name you choose for the login class."
},
{
"name": "access-end",
"desc": "Specify the end time in HH:MM (24-hour) format, where HH represents the hours and MM represents the minutes. NOTE: Access start and end times that span across 12:00 AM starting on a speci... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | The class, allow-commands, deny-commands, allow-configuration, deny-configuration, idle-timeout, login-alarms, login-
tip, and permissions statements were introduced before Junos OS Release 7.4.
All of the previously mentioned statements were introduced in Junos OS Release 9.0 for the EX Series.
The login-script state... | [
"Defining Junos OS Login Classes",
"Configuring Time-Based User Access",
"Understanding Junos OS Access Privilege Levels",
"Example: Configuring User Permissions with Access Privileges for Operational Mode Commands",
"Regular Expressions for Allowing and Denying Junos OS Operational Mode Commands,",
"Conf... |
class (Forwarding Class Sets) | class class-name; | [edit class-of-service forwarding-class-sets forwarding-class-set-name] | Group forwarding classes into sets of forwarding classes (priority groups). You can group some or all of
the configured forwarding classes into up to three unicast forwarding class sets and one
multidestination forwarding class set. | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Configuring CoS Hierarchical Port Scheduling (ETS)",
"Example: Configuring Forwarding Class Sets",
"Understanding CoS Forwarding Class Sets (Priority Groups)"
] |
class (Forwarding Classes) | [edit class-of-service forwarding-classes] | Specify the output transmission queue to which to map all input from an associated forwarding class.
This statement enables you to configure up to 16 forwarding classes with multiple forwarding classes
mapped to single queues. If you want to configure up to eight forwarding classes with one-to-one
mapping to output que... | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
},
{
"name": "queue-number",
"desc": "Output queue number."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1.
No-loss option introduced in Junos OS Release 12.3 for the QFX Series.
PFC-priority statement introduced in Junos OS Release 17.4R1 for the QFX Series. | [
"Example: Configuring Forwarding Classes",
"Understanding CoS Forwarding Classes",
"Understanding CoS Forwarding Classes",
"Configuring a Custom Forwarding Class for Each Queue",
"Example: Configuring CoS on EX Series Switches",
"Defining CoS Forwarding Classes (CLI Procedure)",
"Defining CoS Forwarding... | |
class (Unified Edge) | class {
equals value;
has-prefix value;
has-suffix value;
matches value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify the RADIUS AVP class for the incoming RADIUS request from the IP-based subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected.
The remaining statements are explained separately. S... | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
class | class {
alg-logs;
deterministic-nat-configuration-log;
ids-logs;
nat-logs;
packet-logs;
pcp-logs;
session-logs <open | close>;
stateful-firewall-logs ;
urlf-logs;
} | [edit services service-set service-set-name syslog host hostname] | Set the class of applications to be logged to the system log.
Starting in Junos OS Release 17.4R1, you can configure up to a maximum of four system log servers
(combination of local system log hosts and remote system log collectors) for each service set at the [edit
services service-set service-set-name] hierarchy leve... | [
{
"name": "class-name",
"desc": "Enter one of the following values:"
},
{
"name": "alg-logs",
"desc": "Log application-level gateway events."
},
{
"name": "deterministic-nat-configuration-log",
"desc": "Log deterministic NAT sessions."
},
{
"name": "ids-logs",
"desc": "Lo... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2.
deterministic-nat-configuration-log option introduced in Junos OS Release 17.3R1.
You can configure multiple system log hosts from Junos OS Release 17.4R1 onwards.
urlf-logs option introduced in Junos OS Release 18.3R1. | [
"Configuring System Logging for Service Sets"
] |
class-of-service (Dynamic Profiles) | class-of-service {
dynamic-class-of-service-options {
vendor-specific-tags tag;
}
interfaces {
interface-name {
unit logical-unit-number {
classifiers {
type (classifier-name | default);
}
output-traffic-control-... | [edit dynamic-profiles profile-name] | Configure Junos OS CoS features in a dynamic client profile or a dynamic service profile.
Default
If you do not configure any CoS features, all packets are transmitted from output transmission queue 0. | [
{
"name": "service-accounting",
"desc": "(Junos OS Evolved) Enables Packet Forwarding Engine (PFE) to report queue counter statistics to Routing Engine (RE). It includes statistics of eight queue counters. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a l... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
The service-accounting option introduced in Junos OS Evolved Release 25.4R1. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Static Hierarchical Scheduling in a Dynamic Profile"
] |
class-of-service (Protocols MPLS) | class-of-service cos-value; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
ingress],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls label-switch... | Class-of-service (CoS) value given to all packets in the LSP.
The CoS value might affect the scheduling or queuing algorithm of traffic traveling along an LSP. | [
{
"name": "cos-value",
"desc": "CoS value. A higher value typically corresponds to a higher level of service."
}
] | 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 Class of Service for MPLS LSPs",
"Configuring the Ingress Router for Static LSPs",
"Configuring the Intermediate (Transit) and Egress Routers for Static LSPs"
] |
class-of-service (Protocols RSVP) | class-of-service cos-value; | [edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection],
[edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection bypass bypass-name],
[edit protocols rsvp interface interface-name link-protection],
[edit protocols rsvp interface int... | Class-of-service (CoS) value given to all packets in the bypass LSP. You can specify a single CoS value for
all the bypass LSPs traversing an interface. You can also configure CoS values for specific bypass LSPs
traversing an interface.
The CoS value might affect the scheduling or queuing algorithm of traffic traveling... | [
{
"name": "cos-value",
"desc": "CoS value. A higher value typically corresponds to a higher level of service."
}
] | 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 Class of Service for Bypass LSPs"
] |
class-of-service (saegw system) | class-of-service {
reserved-bandwidth {
express percentage;
gbr percentage;
}
downlink-dscp-to-forwarding-class {
classifier classifier-name;
classifier classifier-name {
routing-instance instance-name;
}
}
} | [edit services mobile-edge gateways saegw system] | Configure class-of-service features on Junos Multi-Access User Plane.
See CLI Explorer for the remaining statements. | [] | system | Juniper Networks introduced this statement in Junos OS Release 22.2R1. | [] |
class-usage-profile | class-usage-profile profile-name {
file filename;
interval minutes;
start-time time;
source-classes {
source-class-name;
}
destination-classes {
destination-class-name;
}
} | [edit accounting-options] | Create a class usage profile, which is used to log class usage statistics to a file in the /var/log directory.
The class usage profile logs class usage statistics for the configured source classes on every interface
that has destination-class-usage configured.
For information about configuring source classes, see the J... | [
{
"name": "profile-name",
"desc": "Name of the destination class profile."
},
{
"name": "start-time",
"desc": ""
},
{
"name": "time",
"desc": "(Optional) Specify the start time in yyyy-mm-dd.hh:mm local time format for the accounting profile. Sometimes, if the time at which the recor... | 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 Class Usage Profiles"
] |
classification-key (DHCP Local Server) | classification-key {
circuit-id circuit-id;
mac-address mac-address;
remote-id remote-id;
} | [edit logical-systems name routing-instances name system services dhcp-local-server dual-stack-group
dual-stack-group-name ],
[edit logical-systems name system services dhcp-local-server dual-stack-group dual-stack-group-
name ],
[edit routing-instances name system services dhcp-local-server dual-stack-group dual-stac... | Different mechanisms to identify a single household. | [
{
"name": "circuit-id",
"desc": "Circuit-id as key."
},
{
"name": "mac-address",
"desc": "MAC address of client."
},
{
"name": "remote-id",
"desc": "Remote-id as key."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3. | [
"Single-Session DHCP Dual-Stack Overview"
] |
classification-key (DHCP Relay Agent) | classification-key {
circuit-id circuit-id;
mac-address mac-address;
remote-id remote-id;
} | [edit bridge-domains name forwarding-options dhcp-relay dhcpv6 group name dual-stack-group dual-
stack-group-name ],
[edit bridge-domains name forwarding-options dhcp-relay dual-stack-group dual-stack-group-name ],
[edit forwarding-options dhcp-relay dhcpv6 group name dual-stack-group dual-stack-group-name ],
[edit for... | Different mechanisms to identify a single household. | [
{
"name": "circuit-id",
"desc": "Circuit-id as key"
},
{
"name": "mac-address",
"desc": ""
},
{
"name": "MAC address of client",
"desc": ""
},
{
"name": "remote-id",
"desc": "Remote-id as key"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3. | [
"Single-Session DHCP Dual-Stack Overview"
] |
classification-override | classification-override {
forwarding-class class-name;
} | [edit class-of-service forwarding-policy class class-name] | Override the incoming packet classification, assigning all packets sent to a destination prefix to the same
output transmission queue. | [] | 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. | [
"Overriding the Input Classification",
"Junos OS Routing Protocols Library for Routing Devices"
] |
classifier | classifier {
per-unit-scheduler {
forwarding-class class-name {
loss-priority (high | low);
}
}
} | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile
output-priority-map] | For Gigabit Ethernet IQ and 10-Gigabit Ethernet interfaces only, define the classifier for the output
priority map to be applied to outgoing frames on this interface.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Gigabit Ethernet Policers"
] |
classifiers (Class of Service) | classifiers {
exp classifier-name;
} | [edit class-of-service system-defaults] | Define a unicast or multidestination CoS behavior aggregate (BA) classifier. | [] | 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. | [
"Defining CoS BA Classifiers (DSCP, DSCP IPv6, IEEE 802.1p)",
"Configuring a Global MPLS EXP Classifier",
"Example: Configuring Unicast Classifiers",
"Example: Configuring Multidestination (Multicast, Broadcast, DLF) Classifiers",
"Understanding CoS Classifiers",
"Understanding CoS Classifiers",
"Unders... |
classifiers (Definition) | classifiers {
type classifier-name {
import (classifier-name | default);
forwarding-class class-name {
loss-priority level code-points [ aliases ] [ bit-patterns ];
}
}
} | [edit class-of-service] | Define a CoS behavior aggregate (BA) classifier for classifying packets. You can associate the classifier
with a forwarding class or code-point mapping, and import a default classifier or one that is previously
defined. | [
{
"name": "classifier-name",
"desc": "Name of the aggregate behavior classifier."
},
{
"name": "type",
"desc": "Traffic type: dscp, dscp-ipv6, exp, ieee-802.1, ieee-802.1ad, inet-precedence."
}
] | 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.
ieee-802.1ad option introduced in Junos OS Release 9.2. | [
"Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic"
] |
classifiers (Dynamic CoS Application) | classifiers {
dscp (classifier-name | default);
dscp-ipv6 (classifier-name | default);
ieee-802.1 (classifier-name | default) vlan-tag (inner | outer)
inet-precedence (classifier-name | default);
} | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number] | Apply a CoS behavior aggregate classifier to a dynamic interface. You can apply a default classifier or
one that is previously defined. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Classifier to a Subscriber Interface in a Dynamic Profile",
"classifiers (Definition)"
] |
classifiers (Interfaces) | classifiers {
type (classifier-name | default) family (mpls | inet);
no-default;
} | [edit class-of-service interfaces interface-name ]
[edit class-of-service interfaces interface-name unit logical-unit-number] | Apply a CoS aggregate behavior classifier to a logical or physical interface. You can apply a default
classifier or one that is previously defined.
NOTE: On MX Series routers, you must apply the classifier to a logical interface.
On ACX Series routers, you must apply the classifier to a physical interface.
If you do no... | [
{
"name": "classifier-name",
"desc": "Name of the aggregate behavior classifier."
},
{
"name": "type",
"desc": "Traffic type. Values: dscp, dscp-ipv6, exp, ieee-802.1, inet-precedence NOTE: You can only specify a family for the dscp and dscp-ipv6 types."
}
] | 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.
no-default option added in Junos OS Release 16.1. | [
"Default DSCP and DSCP IPv6 Classifiers",
"Applying Behavior Aggregate Classifiers to Logical Interfaces"
] |
classifiers (Routing Instance) | classifiers {
exp (classifier-name | default);
dscp (classifier-name | default);
dscp-ipv6 (classifier-name | default);
no-default;
} | [edit class-of-service routing-instances routing-instance-name] | For routing instances with VRF table labels enabled, apply a custom MPLS EXP, DSCP, or IEEE802.1
classifier to the routing instance. You can apply the default classifier or one that is previously defined.
If you do not explicitly apply a classifier configuration to the routing instance, the default classifier is
applie... | [
{
"name": "classifier-name",
"desc": "Name of the behavior aggregate MPLS EXP, DSCP, or IEEE802.1 classifier."
}
] | 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.
dscp and dscp-ipv6 support introduced in Junos OS Release 9.6.
no-default option added in Junos OS Release 16.1.
Support for PTX Series routers introduced in Junos OS Evolved Release 22.4R1.
Support for SRX Series firewalls introduced in Junos OS Release 23.4R1. | [
"Applying MPLS EXP Classifiers to Routing Instances",
"Applying Behavior Aggregate Classifiers to Logical Interfaces"
] |
classifiers (VRF) | classifiers {
exp (classifier-name | default);
} | [edit class-of-service routing-instances routing-instance-name] | For routing instances with VRF table labels enabled, apply a custom MPLS EXP classifier to the routing
instance. You can apply the default
MPLS EXP classifier or one that is previously defined.
Default
If you do not include this statement, the default MPLS EXP classifier is applied to the routing instance. | [
{
"name": "classifier-name",
"desc": "Name of the behavior aggregate MPLS EXP classifier."
}
] | 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. | [
"Applying Custom MPLS EXP Classifiers to Routing Instances in Layer 3 VPNs",
"Junos OS Network Interfaces Library for Routing Devices"
] |
clat-ipv6-prefix-length | clat-ipv6-prefix-length (32 | 40 | 48 | 56 | 64 | 96); | [edit services nat rule name term name then translated] | Specify the ipv6 prefix length for CLAT source address. Once you configure this command, source-
address and source-prefix are no more mandatory configuration. It allows the NAT rules to accept the
traffic from different CLAT prefix and apply XLAT464 based on destination-address of the traffic. This
configuration suppo... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [
"464XLAT Overview",
"Configuring 464XLAT Provider-Side Translater for IPv4 Connectivity Across IPv6-Only Network"
] |
clat-prefix (Source NAT Next Gen Services) | clat-prefix clat-prefix; | [edit services nat source rule-set rule-set rule rule-name then source-nat] | Specify the customer-side translator (CLAT) IPv6 source prefix, which is used for 464XLAT.
464XLAT lets an IPv4 client with a private IP address connect to an IPv4 host over an IPv6 network. The
CLAT translates IPv4 source addresses to IPv6 by embedding the IPv4 source address in this IPv6
source prefix. The CLAT then ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
clat-prefix | clat-prefix clat-prefix; | [edit services nat rule rule-name term term-name then translated] | Specify the IPv6 prefix that the customer-side translator (CLAT) uses when performing 464XLAT
translation to IPv6 (the CLAT is not a Juniper Networks product). The Provider-Side Translater (PLAT) on
the MX Series uses the CLAT IPv6 prefix to translate the IPv6 packet back to IPv4. | [] | 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. | [
"464XLAT Overview",
"Configuring 464XLAT Provider-Side Translater for IPv4 Connectivity Across IPv6-Only Network"
] |
cleanup-interval (Accounting Options) | cleanup-interval days; | [edit accounting-options] | Configure the interval to delete files from the local backup directory. | [
{
"name": "days",
"desc": "Number of days after which accounting-options files are to be deleted from the backup directory. Range: 1 through 31 days Default: 1 day"
}
] | 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 Accounting-Data Log Files",
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
clear (ospf | ospf3) database | clear (ospf | ospf3) database
<all>
<advertising-router (router-id | self)>
<area area-id>
<asbrsummary>
<external>
<instance instance-name>
<inter-area-prefix>
<inter-area-router>
<intra-area-prefix>
<link-local>
<lsa-id lsa-id>
<netsummary>
<network>
<nssa>
<opaque-area>
<router> | With the primary Routing Engine, delete entries in the Open Shortest Path First (OSPF) link-state
advertisement (LSA) database. With the backup Routing Engine, delete the OSPF LSA database and sync
the new database with the primary Routing Engine. | [
{
"name": "all",
"desc": "Delete all LSAs other than the system’s own LSAs, which are regenerated. To resynchronize the database, the system destroys all adjacent neighbors that are in the state EXSTART or higher. The neighbors are then reacquired and the databases are synchronized."
},
{
"name": "a... | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear ospf database all
user@host> clear ospf database all | Command introduced before Junos OS Release 7.4.
advertising-router router-id, netsummary, network, nssa, opaque-area, and router options added in Junos OS
Release 8.3.
area area-id option added in Junos OS Release 8.3.
realm option added in Junos OS Release 9.2.
advertising-router (router-id | self) option added in Jun... | [] | |
clear (ospf | ospf3) database-protection | clear (ospf | ospf3) database-protection
<instance instance-name> | Clear the Open Shortest Path First (OSPF) link-state database from its isolated state. Reset the ignore
count, ignore timer, and reset timer, and resume normal operations. | [
{
"name": "instance instance-name",
"desc": "(Optional) Clear the OSPF link-state database for the specified routing instance only."
}
] | clear
Output Fields
This command produces no output.
Sample Output
clear ospf database-protection
user@host> clear ospf database-protection | Command introduced in Junos OS Release 10.2. | [] | |
clear (ospf | ospf3) io-statistics | clear (ospf | osfp3) io-statistics | Clear Open Shortest Path First (OSPF) input and output statistics. | [
{
"name": "none",
"desc": "Clear OSPF input and output statistics."
},
{
"name": "logical-system (all | logical-system-name)",
"desc": "(Optional) Perform this operation on all logical systems or on a particular logical system."
}
] | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear ospf io-statistics
user@host> clear ospf io-statistics | Command introduced before Junos OS Release 7.4. | [] | |
clear (ospf | ospf3) neighbor | clear (ospf | ospf3) neighbor
<all>
<area area-id>
<instance instance-name>
<interface interface-name>
<neighbor> | Tear down Open Shortest Path First (OSPF) neighbor connections. | [
{
"name": "all",
"desc": "Tear down OSPF connections with all neighbors for all routing instances."
},
{
"name": "area area-id",
"desc": "(Optional) Tear down neighbor connections for the specified area only."
},
{
"name": "instance instance-name",
"desc": "(Optional) Tear down neigh... | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear ospf neighbor all
user@host> clear ospf neighbor all | Command introduced before Junos OS Release 7.4.
realm option introduced in Junos OS Release 9.2. | [] | |
clear (ospf | ospf3) overload | clear (ospf | ospf3) overload
<instance instance-name> | Clear the Open Shortest Path First (OSPF) overload bit and rebuild link-state advertisements (LSAs). | [
{
"name": "none",
"desc": "Clear the overload bit and rebuild LSAs for all routing instances."
},
{
"name": "instance instance-name",
"desc": "(Optional) Clear the overload bit and rebuild LSAs for the specified routing instance only."
},
{
"name": "logical-system (all | logical-system-n... | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear ospf overload
user@host> clear ospf overload | Command introduced before Junos OS Release 7.4. | [] | |
clear (ospf | ospf3) statistics | clear (ospf | osfp3) statistics
<instance instance-name> | Clear Open Shortest Path First (OSPF) statistics. | [
{
"name": "none",
"desc": "Clear OSPF statistics."
},
{
"name": "instance instance-name",
"desc": "(Optional) Clear statistics for the specified routing instance only."
},
{
"name": "logical-system (all | logical-system-name)",
"desc": "(Optional) Perform this operation on all logica... | clear
Output Fields
See "show (ospf | ospf3) statistics" on page 17696 for an explanation of output fields.
Sample Output
clear ospf statistics
The following sample output displays OSPF statistics before and after the clear ospf statistics command
is entered:
user@host> show ospf statistics
Packet type T... | Command introduced before Junos OS Release 7.4.
realm option introduced in Junos OS Release 9.2. | [] | |
clear access-security router-advertisement statistics | clear access-security router-advertisement statistics (fail | success) (all | interface interface-name |
vlan vlan-name) | Clear the IPv6 Router Advertisement (RA) guard entries for received RA messages. IF RA guard is
enabled on a switch, the switch examines incoming RA messages and filters them on the basis of a
predefined set of criteria. If the switch validates the sender of the RA message as a legitimate IPv6
router, it forwards the R... | [
{
"name": "all",
"desc": "Clear the RA guard entries on all VLANs."
},
{
"name": "fail",
"desc": "Clear RA guard entries for RA messages that were discarded."
},
{
"name": "interface interface-name",
"desc": "Clear the RA guard entries for the specified interface."
},
{
"name... | view
Output Fields
This command generates no output. | Command introduced in Junos OS Release 15.1X53-D55. | [] | |
clear access-security slaac-snooping binding | clear access-security slaac-snooping binding
<interface (interface-name | all)>
<vlan vlan-name>
<vlan vlan-name routing-instance routing-instance-name>
<vlan vlan-name logical-system logical-system-name> | Clear the SLAAC snooping database information. | [
{
"name": "interface (interface-name | all)",
"desc": "Clear SLAAC snooping information for the specified interface or all interfaces."
},
{
"name": "vlan (vlan-name)",
"desc": "Clear SLAAC snooping information for the specified VLAN."
},
{
"name": "routing-instance(routing-instance-name... | clear
Output Fields
This command produces no output.
Sample Output
clear access-security slaac-snooping binding
user@switch> clear access-security slaac-snooping binding | Command introduced in Junos OS Release 19.2R1. | [] | |
clear access-security slaac-snooping statistics | clear access-security slaac-snooping statistics
<interface (interface-name | all)> | Clear the SLAAC snooping statistics. | [
{
"name": "interface (interface-name | all)",
"desc": "Clear SLAAC snooping statistics for the specified interface or all interfaces."
}
] | clear
Output Fields
This command produces no output.
Sample Output
clear access-security slaac-snooping statistics
user@switch> clear access-security slaac-snooping statistics | Command introduced in Junos OS Release 19.2R1. | [] | |
clear accounting server statistics archival-transfer | clear accounting server statistics archival-transfer | Clears the statistics of transfer attempted, succeeded, and failed for accounting statistics files and router
configuration archives. | [] | clear
Output Fields
When you enter this command, the transfer statistics are cleared.
Sample Output
clear accounting server statistics archival-transfer
user@host> clear accounting server statistics archival-transfer | Command introduced in Junos OS Release 19.2. | [] | |
clear amt statistics | clear amt statistics
<instance instance-name>
<logical-system (all | logical-system-name)> | Clear Automatic Multicast Tunneling (AMT) statistics. | [
{
"name": "none",
"desc": "Clear the multicast statistics for all AMT tunnel interfaces."
},
{
"name": "instance instance-name",
"desc": "(Optional) Clear AMT multicast statistics for the specified instance."
},
{
"name": "logical-system (all | logical-system-name)",
"desc": "(Option... | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear amt statistics
user@host> clear amt statistics | Command introduced in JUNOS Release 10.2. | [] | |
clear amt tunnel | clear amt tunnel
<gateway gateway-ip-addr> <port port-number>
<instance instance-name>
<logical-system (all | logical-system-name)>
<statistics>
<tunnel-interface interface-name> | Clear the Automatic Multicast Tunneling (AMT) multicast state. Optionally, clear AMT protocol statistics. | [
{
"name": "none",
"desc": "Clear multicast state for all AMT tunnel interfaces."
},
{
"name": "gateway gateway-ip-addr port",
"desc": ""
},
{
"name": "port-number",
"desc": "(Optional) Clear the AMT multicast state for the specified gateway address. If no port is specified, clear the... | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear amt tunnel
user@host> clear amt tunnel
clear amt tunnel statistics gateway-address
user@host> clear amt tunnel statistics gateway-address 100.31.1.21 port 4000 | Command introduced in JUNOS Release 10.2. | [] | |
clear ancp access-loop | clear ancp access-loop
(neighbor ip-address | subscriber-interface physical-interface-name)
circuit-id aci
remote-id ari
outer-vlan-id vlan-id | Clear the connection for the subscriber on the specified access loop for an ANCP-triggered, autosensed
dynamic VLAN. The autoconfiguration daemon (autoconfd) deletes any existing cached information
about the subscriber. This command simulates a CPE connection reset as seen when the access node
sends a Port Down message... | [
{
"name": "aci",
"desc": "ANCP Access-Loop-Circuit-ID TLV that identifies the subscriber-side access loop logical port and partially identifies an access loop to clear."
},
{
"name": "ari",
"desc": "ANCP Access-Loop-Remote-ID TLV that uniquely identifies the subscriber on the access loop and par... | clear
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 command before and after clearing the access loop to verify the clear
operation.
Sample Output
clear ancp access-loop
user@host> clear ancp-access-loop neighbor 192.168.25.31... | Command introduced in Junos OS Release 16.1R4. | [
"Clearing ANCP Access Loops",
"Triggering ANCP OAM to Simulate ANCP Port Down and Port Up Messages",
"Layer 2 Wholesale with ANCP-Triggered VLANs Overview"
] | |
clear ancp neighbor | clear ancp neighbor
<ip-address ip-address>
<system-name mac-address> | Clear the ANCP agent connection with all ANCP neighbors or with the specified ANCP neighbor. This
command deletes information for subscribers associated with the neighbor, causing the adjusted traffic
rates to revert to the configured rate for the subscriber interfaces. The neighbor remains configured (its
administrati... | [
{
"name": "none",
"desc": "Clear all ANCP neighbors."
},
{
"name": "ip-address ip-address",
"desc": "(Optional) Clear the ANCP neighbor specified by the IP address."
},
{
"name": "system-name mac-address",
"desc": "(Optional) Clear the ANCP neighbor specified by the MAC address."
}... | clear
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 command before and after clearing the ANCP neighbors to verify the clear
operation.
Sample Output
clear ancp neighbor
user@host> clear ancp neighbor
show ancp neighbor
The... | Command introduced in Junos OS Release 9.4. | [] | |
clear ancp statistics | clear ancp statistics
<ip-address ip-address>
<system-name mac-address> | Clear current statistics accumulated by the ANCP agent for all ANCP neighbors or the specified
neighbor. | [
{
"name": "none",
"desc": "Clear all ANCP statistics."
},
{
"name": "ip-address ip-address",
"desc": "(Optional) Clear statistics for the ANCP neighbor specified by the IP address."
},
{
"name": "system-name mac-address",
"desc": "(Optional) Clear statistics for the ANCP neighbor spe... | clear
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 command before and after clearing the ANCP neighbor statistics to verify the
clear operation.
Sample Output
clear ancp statistics
user@host> clear ancp statistics
show ancp n... | Command introduced in Junos OS Release 13.3. | [] | |
clear ancp subscriber | clear ancp subscriber
<identifier identifier>
<ip-address ip-address>
<system-name mac-address> | Clear the ANCP agent connection with all ANCP subscribers or with the specified ANCP subscriber. This
command deletes information for the subscribers, causing the adjusted traffic rate to revert to the
configured rate for the subscriber interface, but otherwise has no affect on ANCP neighbors. | [
{
"name": "none",
"desc": "Clear all ANCP subscribers."
},
{
"name": "identifier identifier-string",
"desc": "(Optional) Clear the ANCP subscriber identified by the access loop ID."
},
{
"name": "ip-address ip-address",
"desc": "(Optional) Clear all ANCP subscribers on the neighbor s... | clear
Output Fields
When you enter this command, you are provided no feedback on the status of your request. You can
enter the show ancp subscriber command before and after clearing the ANCP neighbors to verify the clear
operation.
Sample Output
show ancp subscriber brief
user@host> show ancp subscriber brief
Loop Ide... | Command introduced in Junos OS Release 11.4. | [] | |
clear arp inspection statistics | clear arp inspection statistics
<interface interface> | Clear ARP inspection statistics. | [
{
"name": "none",
"desc": "Clears ARP statistics on all interfaces."
},
{
"name": "interface interface-names",
"desc": "(Optional) Clear ARP statistics on one or more interfaces."
}
] | clear
Output Fields
This command produces no output.
Sample Output
clear arp inspection statistics
user@switch> clear arp inspection statistics | Command introduced in Junos OS Release 9.0. | [
"Example: Configuring Port Security (non-ELS)",
"Verifying That DAI Is Working Correctly"
] | |
clear arp | clear arp
<all>
<hostname hostname>
<interface interface-name>
<logical-system logical-system-name>
<tenant name>
<vpn vpn> | Remove entries from the Address Resolution Protocol (ARP) table for the current CLI view. To clear
entries for a specific logical system, you must first enter the set cli logical-system logical-system-name
command, and then issue the clear arp command. | [
{
"name": "all",
"desc": "Clear all entries from the ARP table."
},
{
"name": "hostname hostname",
"desc": "(Optional) Clear only the specified host entry from the ARP table."
},
{
"name": "interface interface-name",
"desc": "(Optional) Clear entries only for the specified interface ... | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear arp all
user@host> clear arp all
192.168.71.254 deleted
192.168.65.46 deleted
192.168.64.10 deleted
10.0.12.14 deleted
10.0.17.14 deleted
clear arp logical-syst... | Command introduced before Junos OS Release 7.4.
all option introduced in Junos OS Release 14.2.
tenant option added in Junos OS Release 18.3. | [
"set cli logical-system",
"show dhcp-security arp inspection statistics",
"Port Security Features"
] | |
clear auto-configuration interfaces interface-set | clear auto-configuration interfaces interface-set interface-set-name | Clear a specified dynamic agent circuit identifier (ACI) interface set or access-line identifier (ALI)
interface set on the router. An ACI or ALI interface set is a logical collection of dynamic VLAN subscriber
interfaces that originate at the same household or on the same access-loop port.
You can clear only those ACI... | [
{
"name": "interface-set-name",
"desc": "Name of the empty ACI or ALI interface set that you want to clear. Use the ACI or ALI interface set name generated by the router, such as aci-1003-ge-1/0/0.4001, and not the actual ACI or ALI string found in the DHCP or PPPoE control packets. To view the names of the... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear auto-configuration interfaces interface-set
user@host> clear auto-configuration interfaces interface-set aci-1003-ge-1/0/0.4001
Interface-set aci-1003-ge-1/0/0.4001 deleted
clear auto-configurati... | Command introduced in Junos OS Release 12.2. | [
"Clearing Agent Circuit Identifier Interface Sets",
"Clearing Access-Line-Identifier Interface Sets"
] | |
clear auto-configuration interfaces | clear auto-configuration interfaces interface-name | Clear dynamically created VLAN interfaces.
NOTE: For the clear command to be successful, no interface bindings (for example,
DHCP server bindings) can exist on the dynamic interface. | [
{
"name": "interface-name",
"desc": "Name of a physical or logical interface."
}
] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear auto-configuration interfaces (All Interfaces)
user@host> clear auto-configuration interfaces ge-1/0/0
command-name
10 interfaces removed from device ge-1/0/0
clear auto-configuration interfaces... | Command introduced in Junos OS Release 9.5. | [
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/",
"subscriber-access/subscriber-mgmt-vlan-interface.html",
"Verifying and Managing Dynamic VLAN Configuration"
] | |
clear bfd adaptation | clear bfd adaptation
<all>
<address session-address>
<discriminator discr-number> | Clear adaptation for Bidirectional Forwarding Detection (BFD) sessions. BFD is a simple hello
mechanism that detects failures in a network. Configured BFD interval timers can change, adapting to
network situations. Use this command to return BFD interval timers to their configured values.
The clear bfd adaptation comma... | [
{
"name": "all",
"desc": "Clear adaptation for all BFD sessions."
},
{
"name": "address session-address",
"desc": "(Optional) Clear adaptation for all BFD sessions matching the specified address."
},
{
"name": "discriminator discr-number",
"desc": "(Optional) Clear adaptation for the... | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear bfd adaptation
user@host> clear bfd adaptation | Command introduced before Junos OS Release 7.4. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.