Junos OS: Administration Guide For Security Devices
Junos OS: Administration Guide For Security Devices
Modified: 2017-04-05
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
®
Junos OS Administration Guide for Security Devices
Copyright © 2017, Juniper Networks, Inc.
All rights reserved.
The information in this document is current as of the date on the title page.
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the
year 2038. However, the NTP application is known to have some difficulty in the year 2036.
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
view-configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Chapter 5 Configuring Authentication Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Configuring RADIUS Server Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Example: Configuring a RADIUS Server for System Authentication . . . . . . . . . . 340
Configuring TACACS+ Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Configuring TACACS+ Server Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Specifying a Source Address for the Junos OS to Access External TACACS+
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Configuring the Same Authentication Service for Multiple TACACS+
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Configuring Juniper Networks Vendor-Specific TACACS+ Attributes . . . . . . 345
Example: Configuring a TACACS+ Server for System Authentication . . . . . . . . . 346
Example: Configuring Authentication Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Chapter 8 Configuring Telnet and SSH Access to an SRX Series Appliance . . . . . . . 383
Securing the Console Port Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . 383
Configuring Password Retry Limits for Telnet and SSH Access . . . . . . . . . . . . . . 384
Example: Controlling Management Access on SRX Series Devices . . . . . . . . . . 385
Example: Configuring a Filter to Block Telnet and SSH Access . . . . . . . . . . . . . . 389
The telnet Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
The ssh Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Configuring Outbound SSH Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Configuring the Device Identifier for Outbound SSH Connections . . . . . . . . 397
Sending the Public SSH Host Key to the Outbound SSH Client . . . . . . . . . . 398
Configuring Keepalive Messages for Outbound SSH Connections . . . . . . . 399
Configuring a New Outbound SSH Connection . . . . . . . . . . . . . . . . . . . . . . 399
Configuring the Outbound SSH Client to Accept NETCONF as an Available
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Configuring Outbound SSH Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
allow-configuration-regexps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
authentication-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
authentication-order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
boot-server (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
broadcast-client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
ciphers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
connection-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
client-ia-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
client-identifier (dhcp-client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
client-identifier (dhcpv6-client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
client-list-name (SNMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
client-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
deny-configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
deny-configuration-regexps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
destination (Accounting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
dhcp-attributes (Access IPv4 Address Pools) . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
dhcp-attributes (Access IPv6 Address Pools) . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
dhcp-client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
dhcp-local-server (System Services) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
dhcpv6 (System Services) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
dhcpv6-client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
disable (System Services) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
dlv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
dynamic-pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
dynamic-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
family (Security Forwarding Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
file (System Logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
forwarding-options (Security) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
group (System Services DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
host (SSH Known Hosts) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
hostkey-algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
idle-timeout (System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
interface (System Services DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
interfaces (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
interfaces (Security Zones) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
interface-traceoptions (System Services DHCP) . . . . . . . . . . . . . . . . . . . . . . . . 598
internet-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
kernel-replication (System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
lease-time (dhcp-client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
lockout-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
macs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
max-pre-authentication-packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
multicast-client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
name-server (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
neighbor-discovery-router-advertisement (Access) . . . . . . . . . . . . . . . . . . . . . . 608
ntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
outbound-ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
If the information in the latest release notes differs from the information in the
documentation, follow the product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject
matter experts. These books go beyond the technical documentation to explore the
nuances of network architecture, deployment, and administration. The current list can
be viewed at http://www.juniper.net/books.
Supported Platforms
For the features described in this document, the following platforms are supported:
• SRX Series
• vSRX
If you want to use the examples in this manual, you can use the load merge or the load
merge relative command. These commands cause the software to merge the incoming
configuration into the current candidate configuration. The example does not become
active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple
hierarchies), the example is a full example. In this case, use the load merge command.
If the example configuration does not start at the top level of the hierarchy, the example
is a snippet. In this case, use the load merge relative command. These procedures are
described in the following sections.
1. From the HTML or PDF version of the manual, copy a configuration example into a
text file, save the file with a name, and copy the file to a directory on your routing
platform.
For example, copy the following configuration to a file and name the file ex-script.conf.
Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system {
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
2. Merge the contents of the file into your routing platform configuration by issuing the
load merge configuration mode command:
[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
Merging a Snippet
To merge a snippet, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration snippet into a text
file, save the file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file
ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory
on your routing platform.
commit {
file ex-script-snippet.xsl; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following
configuration mode command:
[edit]
user@host# edit system scripts
[edit system scripts]
3. Merge the contents of the file into your routing platform configuration by issuing the
load merge relative configuration mode command:
For more information about the load command, see CLI Explorer.
Documentation Conventions
Caution Indicates a situation that might result in loss of data or hardware damage.
Laser warning Alerts you to the risk of personal injury from a laser.
Table 2 on page xx defines the text and syntax conventions used in this guide.
Bold text like this Represents text that you type. To enter configuration mode, type the
configure command:
user@host> configure
Fixed-width text like this Represents output that appears on the user@host> show chassis alarms
terminal screen.
No alarms currently active
Italic text like this • Introduces or emphasizes important • A policy term is a named structure
new terms. that defines match conditions and
• Identifies guide names. actions.
Italic text like this Represents variables (options for which Configure the machine’s domain name:
you substitute a value) in commands or
configuration statements. [edit]
root@# set system domain-name
domain-name
Text like this Represents names of configuration • To configure a stub area, include the
statements, commands, files, and stub statement at the [edit protocols
directories; configuration hierarchy levels; ospf area area-id] hierarchy level.
or labels on routing platform • The console port is labeled CONSOLE.
components.
< > (angle brackets) Encloses optional keywords or variables. stub <default-metric metric>;
# (pound sign) Indicates a comment specified on the rsvp { # Required for dynamic MPLS only
same line as the configuration statement
to which it applies.
[ ] (square brackets) Encloses a variable for which you can community name members [
substitute one or more values. community-ids ]
GUI Conventions
Bold text like this Represents graphical user interface (GUI) • In the Logical Interfaces box, select
items you click or select. All Interfaces.
• To cancel the configuration, click
Cancel.
> (bold right angle bracket) Separates levels in a hierarchy of menu In the configuration editor hierarchy,
selections. select Protocols>Ospf.
Documentation Feedback
• Online feedback rating system—On any page of the Juniper Networks TechLibrary site
at http://www.juniper.net/techpubs/index.html, simply click the stars to rate the content,
and use the pop-up form to provide us with information about your experience.
Alternately, you can use the online feedback form at
http://www.juniper.net/techpubs/feedback/.
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or Partner Support Service
support contract, or are covered under warranty, and need post-sales technical support,
you can access our tools and resources online or open a case with JTAC.
• JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
• Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
All users who log in to the device must be in a login class. You can define any number of
login classes. You then apply one login class to an individual user account. With login
classes, you define the following:
• Access privileges users have when they are logged in to the device.
• How long a login session can be idle before it times out and the user is logged off.
You can define any number of login classes and then apply one login class to an individual
user account.
Table 3 on page 3 contains a few predefined login classes. The predefined login classes
cannot be modified.
read-only view
unauthorized None
NOTE:
• You cannot modify a predefined login class name. If you issue the set
command on a predefined class name, the Junos OS appends -local to the
login class name. The following message also appears:
• You cannot issue the rename or copy command on a predefined login class.
Doing so results in the following error message:
Permission Bits
Each top-level CLI command and each configuration statement has an access privilege
level associated with it. Users can execute only those commands and configure and view
only those statements for which they have access privileges. The access privileges for
each login class are defined by one or more permission bits (see Table 4 on page 4).
Two forms for the permissions control the individual parts of the configuration:
• Form that ends in -control—Provides read and write capability for that permission type.
An example is interface-control.
admin Can view user account information in configuration mode and with the show configuration
command.
admin-control Can view user accounts and configure them (at the [edit system login] hierarchy level).
access Can view the access configuration in configuration mode and with the show configuration
operational mode command.
access-control Can view and configure access information (at the [edit access] hierarchy level).
clear Can clear (delete) information learned from the network that is stored in various network
databases (using the clear commands).
configure Can enter configuration mode (using the configure command) and commit configurations
(using the commit command).
control Can perform all control-level operations (all operations configured with the -control
permission bits).
firewall-control Can view and configure firewall filter information (at the [edit firewall] hierarchy level).
interface Can view the interface configuration in configuration mode and with the show configuration
operational mode command.
interface-control Can view chassis, class of service, groups, forwarding options, and interfaces configuration
information. Can configure chassis, class of service, groups, forwarding options, and
interfaces (at the [edit] hierarchy).
maintenance Can perform system maintenance, including starting a local shell on the device and
becoming the superuser in the shell (by issuing the su root command), and can halt and
reboot the device (using the request system commands).
network Can access the network by entering the ping, ssh, telnet, and traceroute commands.
reset Can restart software processes using the restart command and can configure whether
software processes are enabled or disabled (at the [edit system processes] hierarchy
level).
rollback Can use the rollback command to return to a previously committed configuration other
than the most recently committed one.
routing Can view general routing, routing protocol, and routing policy configuration information
in configuration and operational modes.
routing-control Can view general routing, routing protocol, and routing policy configuration information
and configure general routing (at the [edit routing-options] hierarchy level), routing
protocols (at the [edit protocols] hierarchy level), and routing policy (at the [edit
policy-options] hierarchy level).
secret Can view passwords and other authentication keys in the configuration.
secret-control Can view passwords and other authentication keys in the configuration and can modify
them in configuration mode.
security Can view security configuration in configuration mode and with the show configuration
operational mode command.
security-control Can view and configure security information (at the [edit security] hierarchy level).
shell Can start a local shell on the device by entering the start shell command.
snmp Can view SNMP configuration information in configuration and operational modes.
snmp-control Can view SNMP configuration information and configure SNMP (at the [edit snmp]
hierarchy level).
system-control Can view system-level configuration information and configure it (at the [edit system]
hierarchy level).
trace Can view trace file settings in configuration and operational modes.
trace-control Can view trace file settings and configure trace file properties.
view Can use various commands to display current system-wide, routing table, and
protocol-specific values and statistics.
User accounts provide one way for users to access the device. Users can access the
device without accounts if you configured RADIUS or TACACS+ servers. After you have
created an account, the device creates a home directory for the user. An account for the
user root is always present in the configuration. For each user account, you can define
the following:
• Username—Name that identifies the user. It must be unique within the device. Do not
include spaces, colons, or commas in the username.
• User's full name—If the full name contains spaces, enclose it in quotation marks (“ ”).
Do not include colons or commas.
• User identifier (UID)—Numeric identifier that is associated with the user account name.
The identifier range from 100 through 64,000 and must be unique within the device.
If you do not assign a UID to a username, the software assigns one when you commit
the configuration, preferring the lowest available number.
• User's access privilege—You can create login classes with specific permission bits or
use one of the predefined classes.
• Authentication method or methods and passwords that the user can use to access
the device—You can use SSH or an MD5 password, or you can enter a plain-text
password that Junos OS encrypts using MD5-style encryption before entering it in the
password database. If you configure the plain-text-password option, you are prompted
to enter and confirm the password.
Supported Platforms EX Series, M Series, MX Series, OCX1100, PTX Series, QFabric System, QFX Series, SRX Series,
T Series, vSRX
Each top-level CLI command and each configuration statement have an access privilege
level associated with them. Users can execute only those commands and configure and
view only those statements for which they have access privileges. The access privileges
for each login class are defined by one or more permission flags.
For each login class, you can explicitly deny or allow the use of operational and
configuration mode commands that would otherwise be permitted or not allowed by a
privilege level specified in the permissions statement.
enter configuration mode. Two forms of permissions control for individual parts of the
configuration are:
• Form that ends in -control—Provides read and write capability for that permission type.
An example is interface-control.
Table 5 on page 8 lists the Junos OS login class permission flags that you can configure
by including the permissions statement at the [edit system login class class-name]
hierarchy level.
access-control Can view and configure access information at the [edit access]
hierarchy level.
admin-control Can view user accounts and configure them at the [edit system
login] hierarchy level.
clear Can clear (delete) information learned from the network that
is stored in various network databases by using the clear
commands.
firewall-control Can view and configure firewall filter information at the [edit
firewall] hierarchy level.
• [edit chassis]
• [edit class-of-service]
• [edit groups]
• [edit forwarding-options]
• [edit interfaces]
network Can access the network by using the ping, ssh, telnet, and
traceroute commands.
routing Can view general routing, routing protocol, and routing policy
configuration information in configuration and operational
modes.
routing-control Can view general routing, routing protocol, and routing policy
configuration information and can configure general routing at
the [edit routing-options] hierarchy level, routing protocols at
the [edit protocols] hierarchy level, and routing policy at the
[edit policy-options] hierarchy level.
security-control Can view and configure security information at the [edit security]
hierarchy level.
shell Can start a local shell on the router or switch by using the start
shell command.
snmp-control Can view SNMP configuration information and can modify SNMP
configuration at the [edit snmp] hierarchy level.
trace Can view trace file settings and configure trace file properties.
trace-control Can modify trace file settings and configure trace file properties.
Permission flags are used to grant a user access to operational mode commands and
configuration hierarchy levels and statements. By specifying a specific permission flag
on the user's login class at the [edit system login class] hierarchy level, you grant the user
access to the corresponding commands and configuration hierarchy levels and
statements. To grant access to all commands and configuration statements, use the all
permissions flag. For permission flags that grant access to configuration hierarchy levels
and statements, the flags grant read-only privilege to that configuration. For example,
the interface permissions flag grants read-only access to the [edit interfaces] hierarchy
level. The -control form of the flag grants read-write access to that configuration. Using
the preceding example, interface-control grants read-write access to the [edit interfaces]
hierarchy level.
• The all login class permission bits take precedence over extended regular expressions
when a user issues rollback command with rollback permission flag enabled.
• Expressions used to allow and deny commands for users on RADIUS and TACACS+
servers have been simplified. Instead of a single, long expression with multiple
commands (allow-commands=cmd1 cmd2 ... cmdn), you can specify each command
as a separate expression. This new syntax is valid for allow-configuration,
deny-configuration, allow-commands, deny-commands, and all user permission bits.
• Users cannot issue the load override command when specifying an extended regular
expression. Users can only issue the merge, replace, and patch configuration commands.
• If you allow and deny the same commands, the allow-commands permissions take
precedence over the permissions specified by the deny-commands. For example, if you
include allow-commands "request system software add" and deny-commands "request
system software add", the login class user is allowed to install software using the
request system software add command.
• Regular expressions for allow-commands and deny-commands can also include the
commit, load, rollback, save, status, and update commands.
• If you specify a regular expression for allow-commands and deny-commands with two
different variants of a command, the longest match is always executed.
For example, if you specify a regular expression for allow-commands with the
commit-synchronize command and a regular expression for deny-commands with the
commit command, users assigned to such a login class would be able to issue the
commit synchronize command, but not the commit command. This is because
commit-synchronize is the longest match between commit and commit-synchronize
and it is specified for allow-commands.
Likewise, if you specify a regular expression for allow-commands with the commit
command and a regular expression for deny-commands with the commit-synchronize
command, users assigned to such a login class would be able to issue the commit
command, but not the commit-synchronize command. This is because
commit-synchronize is the longest match between commit and commit-synchronize
and it is specified for deny-commands.
Related • Example: Configuring User Permissions with Access Privilege Levels on page 39
Documentation
• Regular Expressions for Allowing and Denying Junos OS Operational Mode Commands,
Configuration Statements, and Hierarchies
With local password authentication, you configure a password for each user allowed to
log in to the device.
RADIUS and TACACS+ are authentication methods for validating users who attempt to
access the device using Telnet. Both are distributed client/server systems—the RADIUS
and TACACS+ clients run on the device, and the server runs on a remote network system.
You can configure the device to use RADIUS or TACACS+ authentication, or both, to
validate users who attempt to access the device. If you set up both authentication
methods, you also can configure which method the device will try first.
Starting with Junos OS Release 15.1X49-D50, new CLI commands are introduced to
configure a system master password to provide stronger encryption for configuration
secrets. The master password encrypts secrets like the RADIUS password, IKE preshared
keys, and other shared secrets in the Junos OS management process (mgd) configuration.
The master password itself is not saved as part of the configuration. The password quality
is evaluated for strength, and the device gives feedback if weak passwords are used.
The master password is used as input to the password based key derivation function
(PBKDF2) to generate an encryption key. the key is used as input to the Advanced
Encryption Standard in Galois/Counter Mode (AES256-GCM). The plain text that the
user enters is processed by the encryption algorithm (with key) to produce the encrypted
text (cipher text). See Figure 1 on page 13
Master
PBKDF2
Password
Key
g043440
The $8$ configuration secrets can only be shared between devices using the same master
password.
Format Description
crypt-algo Encryption/decryption algorithm to be used. Currently only AES256-GCM is supported.
hash-algo Hash (prf) algorithm to be used for the PBKDF2 key derivation.
iterations The number of iterations to use for the PBKDF2 hash function. Current iteration-count default is
100. The iteration count slows the hashing count, thus slowing attacker guesses.
The ASCII64 encoding is Base64 (RFC 4648) compatible, except no padding (character
“=”) is used to keep the strings short. For example:
$8$aes256-gcm$hmac-sha2-256$100$y/4YMC4YDLU$fzYDI4jjN6YCyQsYLsaf8A$Ilu4jLcZarD9YnyD
/Hejww$okhBlc0cGakSqYxKww
When defining a chassis cluster on SRX Series devices, be aware of the following
restrictions:
• For SRX Series devices, first configure the master password on each node, and then
build the cluster. The same master password should be configured on each node.
15.1X49-D50 Starting with Junos OS Release 15.1X49-D50, new CLI commands are
introduced to configure a system master password to provide stronger
encryption for configuration secrets.
By enabling the Trusted Platform Module (TPM) on the SRX devices, the software layer
leverages the use of underlying TPM chip. TPM is a specialized chip that protects certain
secrets at rest such as passwords, private keys and other sensitive data. Instead of storing
the sensitive data in clear text format, this data is now stored in encrypted format using
TPM.
The advantages of TPM are that the data such as the master password and private
key-pairs will be encrypted by enabling TPM.
The TPM chip is available on SRX300, SRX320, SRX340, and SRX345 devices. TPM is
not enabled by default. The secrets are encrypted using the Master Encryption Password
that is set by the user using the CLI. See “Enabling the TPM” on page 15. The Master
Encryption Password is encrypted using TPM’s binding key called Master Binding Key.
You will be prompted to enter the Master Encryption Password twice, to make sure that
these passwords match. The Master Encryption Password is validated for required
password strength.
After Master Encryption Password is set, the system proceeds to encrypt the sensitive
data with the Master Encryption Password.
NOTE: If there is any issue with setting the Master Encryption Password, a
critical ERROR message is logged on the console and the process is aborted.
• TPM enabled/disabled
• TPM ownership
To change the Master Encryption Password, enter the following command from
operational mode:
The system checks if the Master Encryption Password is already configured. If Master
Encryption Password is configured, then you are prompted to enter the current Master
Encryption Password.
The entered Master Encryption Password is validated against the current Master
Encryption Password to make sure these Master Encryption Passwords match. If the
validation succeeds, you will be prompted to enter the new Master Encryption Password
as plain text. You will be asked to enter the key twice to validate the password.
The system then proceeds to re-encrypt the sensitive data with the new Master Encryption
Password. You must wait for this process of re-encryption to complete before attempting
to change the Master Encryption Password again.
If for some reason, the encrypted Master Encryption Password file is lost or corrupted,
the system will not be able to decrypt the sensitive data. The system can only be recovered
by reimporting the sensitive data in clear text, and re-encrypting them.
You can also recover the system by using the CLI command request system zeroize, which
erases all the data on the hard disk.
• Requirements on page 17
• Overview on page 17
• Configuration on page 18
• Verification on page 20
Requirements
No special configuration beyond device initialization is required before configuring this
feature.
Overview
You can add new users to the device’s local database. For each account, you define a
login name and password for the user and specify a login class for access privileges. The
login password must meet the following criteria:
• You can include most character classes in a password (alphabetic, numeric, and special
characters), but not control characters.
• The password must contain at least one change of case or character class.
In this example, you create a login class named operator-and-boot and allow it to reboot
the device. You can define any number of login classes. You then allow the
operator-and-boot login class to use commands defined in the clear, network, reset,
trace, and view permission bits.
Then you create user accounts. User accounts provide enable you to access the device.
(You can access the device without accounts if you configured RADIUS or TACACS+
servers.) You set the username as cmartin and the login class as superuser. Finally, you
define the encrypted password for the user.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
4. Click Add to add a new user. The Add User dialog box appears.
5. In the User name box, type a unique name for the user.
If the full name contains spaces, enclose it in quotation marks. Do not include colons
or commas.
8. In the Password and Confirm Password boxes, enter a login password for the user
and verify your entry.
9. From the Login Class list, select the user’s access privilege:
• operator
• read-only
• unauthorized
10. Click OK in the Add User dialog box and Edit User Management dialog box.
12. If you are done configuring the device, click Commit Options>Commit.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
1. Set the name of the login class and allow the use of the reboot command.
3. Set the username, login class, and encrypted password for the user.
Results From configuration mode, confirm your configuration by entering the show system login
command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
[edit]
user@host# show system login
class operator-and-boot {
permissions [ clear network reset trace view ];
allow-commands "request system reboot";
}
user cmartin {
class superuser;
authentication {
encrypted-password "$1$ABC123";
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Action From operational mode, enter the show system login command.
You use local user template accounts when you need different types of templates. Each
template can define a different set of permissions appropriate for the group of users who
use that template. These templates are defined locally on the device and referenced by
the TACACS+ and RADIUS authentication servers.
When you configure local user templates and a user logs in, Junos OS issues a request
to the authentication server to authenticate the user's login name. If a user is
authenticated, the server returns the local username to the device, which then determines
whether a local username is specified for that login name (local-username for TACACS+,
Juniper-Local-User for RADIUS). If so, the device selects the appropriate local user
template locally configured on the device. If a local user template does not exist for the
authenticated user, the device defaults to the remote template.
• Requirements on page 21
• Overview on page 21
• Configuration on page 22
• Verification on page 23
Requirements
No special configuration beyond device initialization is required before configuring this
feature.
Overview
You can create template accounts that are shared by a set of users when you are using
RADIUS or TACACS+ authentication. When a user is authenticated by a template account,
the CLI username is the login name, and the privileges, file ownership, and effective user
ID are inherited from the template account.
• The authenticated user's record in the RADIUS or TACACS+ server specifies local user,
or the specified local user does not exist locally on the device.
In this example, you create a remote template account and set the username to remote
and the login class for the user as operator. You create a remote template that is applied
to users authenticated by RADIUS or TACACS+ that do not belong to a local template
account.
You then create a local template account and set the username as admin and the login
class as superuser. You use local template accounts when you need different types of
templates. Each template can define a different set of permissions appropriate for the
group of users who use that template.
Configuration
• Creating a Remote Template Account on page 22
• Creating a Local Template Account on page 22
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
• Set the username and the login class for the user.
Results From configuration mode, confirm your configuration by entering the show system login
command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
[edit]
user@host# show system login
user remote {
class operator;
}
If you are done configuring the device, enter commit from configuration mode.
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
1. Set the username and the login class for the user.
Results From configuration mode, confirm your configuration by entering the show system login
command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
[edit]
user@host# show system login
user admin {
class super-user;
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Action From operational mode, enter the show system login command.
A system user can be a member of a class that allows the user to act as a particular kind
of administrator for the system. Requiring a specific role to view or modify an item restricts
the extent of information a user can obtain from the system. It also limits how much of
the system is open to intentional or unintentional modification or observation by a user.
We recommend that you use the following guidelines when you are designing
administrative roles:
• Restrict each user to the smallest set of privileges needed to perform the user’s duties.
• Do not allow any user to belong to a login class containing the shell permission flag.
The shell permission flag allows users to run the start shell command from the CLI.
• Allow users to have rollback permissions. Rollback permissions allow users to undo
an action performed by an administrator but does not allow them to commit the
changes.
You can assign an administrative role to a user by configuring a login class to have the
privileges required for that role. You can configure each class to allow or deny access to
configuration statements and commands by name. These specific restrictions override
and take precedence over any permission flags also configured in the class. You can
assign one of the following role attributes to an administrative user.
• IDS-administrator—Allows the user to monitor and clear the intrusion detection service
(IDS) security logs.
• Cryptographic Administrator
• Audit Administrator
• Configures and deletes the audit review search and sort feature.
• Security Administrator
• Enables, disables, determines, and modifies the audit analysis and audit selection
functions and configures the device to automatically delete audit logs.
• Specifies the limits, network identifiers, and time periods for quotas on controlled
connection-oriented resources.
• Specifies the network addresses permitted to use Internet Control Message Protocol
(ICMP) or Address Resolution Protocol (ARP).
• Queries, modifies, deletes, and creates the information flow or access control rules
and attributes for the unauthenticated information flow security function policy
(SFP), the authenticated information flow SFP, the unauthenticated device services,
and the discretionary access control policy.
• Specifies initial values that override default values when object information is created
under unauthenticated information flow SFP, the authenticated information flow
SFP, the unauthenticated target of evaluation (TOE) services, and the discretionary
access control policy.
• Creates, deletes, or modifies the rules that control the address from which
management sessions can be established.
• Specifies and revokes security attributes associated with the users, subjects, and
objects.
• Specifies the percentage of audit storage capacity at which the device alerts
administrators.
You need to set the security-role attribute in the classes created for these administrative
roles. This attribute restricts which users can show and clear the security logs, actions
that cannot be performed through configuration alone.
For example, you need to set the security-role attribute in the ids-admin class created
for the IDS administrator role if you want to restrict clearing and showing IDS logs to the
IDS administrator role. Likewise, you need to set the security-role to one of the other
admin values to restrict that class from being able to clear and show non-IDS logs only.
This example shows how to configure individual administrative roles for a distinct, unique
set of privileges apart from all other administrative roles.
• Requirements on page 26
• Overview on page 26
• Configuration on page 27
• Verification on page 32
Requirements
No special configuration beyond device initialization is required before configuring this
feature.
Overview
This example configures four users:
When a security-admin class is configured, the privileges for creating administrators are
revoked from the user who created the security-admin class. Creation of new users and
logins is at the discretion of the security-officer.
In this example, you create audit admin, crypto admin, security admin, and ids admin
with permission flags pertaining to this role. Then you allow or deny access to configuration
statements and commands by name for each administrative role. These specific
restrictions take precedence over the permission flags also configured in the class. For
example, only the crypto-admin can run the request system set-encryption-key command,
which requires having the security permission flag to access it. Only the security-admin
can include the system time-zone statement in the configuration, which requires having
the system-control permission flag.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
non-cryptographic-self-test|policy|replay-attacks)|^file (copy|delete|rename)|^request
(security|system set-encryption-key)|^rollback|
^set date|^show security (dynamic-policies|match-policies|policies)|^start shell"
set system login class ids-admin deny-configuration-regexps "security alarms
potential-violation (authentication|cryptographic-self-test|decryption-
failures|encryption-failures|ike-phase1-failures|ike-phase2-failures|
key-generation-self-test|non-cryptographic-self-test|policy|replay-attacks)"
set system login class ids-admin security-role ids-admin
set system login user audit-officer class audit-admin
set system login user crypto-officer class crypto-admin
set system login user security-officer class security-admin
set system login user ids-officer class ids-admin
set system login user audit-officer authentication plain-text-password
set system login user crypto-officer authentication plain-text-password
set system login user security-officer authentication plain-text-password
set system login user ids-officer authentication plain-text-password
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode.
[edit]
user@host# set system login class audit-admin
[edit system login class audit-admin]
user@host# set permissions security
user@host# set permissions trace
user@host# set permissions maintenance
[edit]
user@host# set system login class crypto-admin
[edit]
user@host# set system login class security-admin
[edit]
user@host# set system login class ids-admin
non-cryptographic-self-test|policy|replay-attacks)|^file
(copy|delete|rename)|^request (security|system set-encryption-key)|
^rollback|^set date|^show security (dynamic-policies|match-policies|policies)|^start
shell"
set system login class ids-admin deny-configuration-regexps "security alarms
potential-violation (authentication|cryptographic-self-test|decryption-
failures|encryption-failures|ike-phase1-failures|ike-phase2-failures|
key-generation-self-test|non-cryptographic-self-test|policy|replay-attacks)"
user@host# set security-role ids-administrator
[edit]
user@host# set system login
Results
From configuration mode, confirm your configuration by entering the show system
command. If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.
[edit]
user@host# show system
system {
login {
class audit-admin {
permissions [ maintenance security trace ];
allow-commands "^clear (log|security log)";
deny-commands "^clear (security alarms|system login lockout)|^file
(copy|delete|rename)|^request (security|system
set-encryption-key)|^rollback|^set date|^show security
(alarms|dynamic-policies|match-policies|policies)|^start shell";
security-role audit-administrator;
}
class crypto-admin {
permissions [ admin-control configure maintenance security-control system-control
trace ];
allow-commands "^request (system set-encryption-key)";
authentication {
encrypted-password "$1$ABC123/"; ## SECRET-DATA
}
}
}
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Action From operational mode, enter the show cli authorization command.
The security administrator can configure the number of times a user can try to log in to
the device with invalid login credentials. The device can be locked after the specified
number of unsuccessful authentication attempts. This helps to protect the device from
malicious users attempting to access the system by guessing an account’s password.
The security administrator can unlock the user account or define a time period for the
user account to remain locked.
The system lockout-period defines the amount of time the device can be locked for a
user account after a specified number of unsuccessful login attempts.
The security administrator can configure a period of time after which an inactive session
will be locked and require re-authentication to be unlocked. This helps to protect the
device from being idle for a long period before the session times out.
The system idle-timeout defines length of time the CLI operational mode prompt remains
active before the session times out.
The security administrator can configure a banner with an advisory notice to be displayed
before the identification and authentication screen.
The system message defines the system login message. This message appears before
a user logs in.
This example shows how to configure system retry options to protect the device from
malicious users.
• Requirements on page 34
• Overview on page 34
• Configuration on page 36
• Verification on page 37
Requirements
Before you begin, you should understand “Handling Authorization Failure” on page 33.
Overview
Malicious users sometimes try to log in to a secure device by guessing an authorized user
account’s password. Locking out a user account after a number of failed authentication
attempts helps protect the device from malicious users.
Device lockout allows you to configure the number of failed attempts before the user
account is locked out of the device and configure the amount of time before the user can
attempt to log in to the device again. You can configure the amount of time in-between
failed login attempts of a user account and can manually lock and unlock user accounts.
NOTE:
This example includes the following settings:
• backoff-factor — Sets the length of delay in seconds after each failed login
attempt. When a user incorrectly logs in to the device, the user must wait
the configured amount of time before attempting to log in to the device
again. The length of delay increases by this value for each subsequent login
attempt after the value specified in the backoff-threshold statement. The
default value for this statement is five seconds, with a range of five to ten
seconds.
• lockout-period — Sets the amount of time in minutes before the user can
attempt to log in to the device after being locked out due to the number of
failed login attempts specified in the tries-before-disconnect statement.
When a user fails to correctly login after the number of allowed attempts
specified by the tries-before-disconnect statement, the user must wait the
configured amount of minutes before attempting to log in to the device
again. The lockout-period must be greater than zero. The range at which
you can configure the lockout-period is one through 43,200 minutes.
Once a user is locked out of the device, if you are the security administrator,
you can manually remove the user from this state using the clear system login
lockout <username> command. You can also use the show system login lockout
command to view which users are currently locked out, when the lockout
period began for each user, and when the lockout period ends for each user.
If the security administrator is locked out of the device, he can log in to the
device from the console port, which ignores any user locks. This provides a
way for the administrator to remove the user lock on their own user account.
In this example the user waits for the backoff-threshold multiplied by the backoff-factor
interval, in seconds, to get the login prompt. In this example, the user must wait 5 seconds
after the first failed login attempt and 10 seconds after the second failed login attempt
to get the login prompt. The user gets disconnected after 15 seconds after the third failed
attempt because the tries-before-disconnect option is configured as 3.
The user cannot attempt anther login until 120 minutes has elapsed, unless a security
administrator manually clears the lock sooner.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
[edit ]
user@host# set system login retry-options backoff-factor 5
[edit]
user@host# set system login retry-options backoff-threshold 1
3. Configure the amount of time the device gets locked after failed attempts.
[edit]
user@host# set system login retry-options lockout-period 5
4. Configure the number of unsuccessful attempts during which, the device can remain
unlocked.
[edit]
user@host# set system login retry-options tries-before-disconnect 3
Results From configuration mode, confirm your configuration by entering the show system login
retry-options command. If the output does not display the intended configuration, repeat
the configuration instructions in this example to correct it.
[edit]
user@host# show system login retry-options
backoff-factor 5;
backoff-threshold 1;
lockout-period 5;
tries-before-disconnect 3;
If you are done configuring the device, enter commit from configuration mode.
Verification
Action Attempt three unsuccessful logins for a particular username. The device will be locked
for that username; then log in to the device with a different username. From operational
mode, enter the show system login lockout command.
Meaning When you perform three unsuccessful login attempts with a particular username, the
device is locked for that user for five minutes, as configured in the example. You can verify
that the device is locked for that user by logging in to the device with a different username
and entering the show system login lockout command.
Supported Platforms EX Series, M Series, MX Series, PTX Series, QFX Series, SRX Series, T Series, vSRX
This example shows how to view permissions for a user account and configure the user
permissions with access privileges for a login class. This enables users to execute only
those commands and configure and view only those statements for which they have
access privileges. This prevents unauthorized users from executing or configuring sensitive
commands and statements that could potentially cause damage to the network.
• Requirements on page 39
• Overview on page 40
• Configuration on page 41
• Verification on page 42
Requirements
This example uses the following hardware and software components:
• Configure at least one user assigned to a login class on the Juniper Networks device.
There can be more than one login class, each with varying permission configurations,
and more than one user on the device.
Overview
Each top-level command-line interface (CLI) command and each configuration statement
in Junos OS has an access privilege level associated with it. For each login class, you can
explicitly deny or allow the use of operational and configuration mode commands that
would otherwise be permitted or not allowed by a privilege level. Users can execute only
those commands and configure and view only those statements for which they have
access privileges. To configure access privilege levels, include the permissions statement
at the [edit system login class class-name] hierarchy level.
The access privileges for each login class are defined by one or more permission flags
specified in the permissions statement. Permission flags are used to grant a user access
to operational mode commands, statements, and configuration hierarchies. Permission
flags are not cumulative, so for each login class you must list all the permission flags
needed, including view to display information and configure to enter configuration mode.
By specifying a specific permission flag on the user's login class, you grant the user access
to the corresponding commands, statements, and configuration hierarchies. To grant
access to all commands and configuration statements, use the all permissions flag. The
permission flags provide read-only (“plain” form) and read and write (form that ends in
-control) capability for a permission type.
NOTE: The all login class permission bits take precedence over extended
regular expressions when a user issues a rollback command with the rollback
permission flag enabled.
You can view the permissions for a user account before configuring the access
privileges for those permissions.
[edit]
?
All users who can log in to a device must be in a login class. For each login class, you
can configure the access privileges that the associated users can have when they are
logged in to the device.
To configure access privilege levels for user permissions, include the permissions
statement at the [edit system login class class-name] hierarchy level, followed by the
user permission, the permissions option, and the required permission flags.
Configuration
[edit]
user@host> ?
Possible completions:
clear Clear information in the system
configure Manipulate software configuration information
file Perform file operations
help Provide help information
load Load information from file
monitor Show real-time debugging information
mtrace Trace multicast path from source to receiver
op Invoke an operation script
ping Ping remote target
quit Exit the management session
request Make system-level requests
restart Restart software process
save Save information to file
set Set CLI properties, date/time, craft interface
message
show Show system information
ssh Start secure shell on another host
start Start shell
telnet Telnet to another host
test Perform diagnostic debugging
traceroute Trace route to remote host
The output lists the permissions for the user host. Customized login classes can be
created by configuring different access privileges on these user permissions.
2. Configure an access privilege class to enable user host to configure and view SNMP
parameters only. In this example, this login class is called network-management.
To customize the network-management login class, include the SNMP permission
flags to the configure user permission.
Here, the configured permission flags provide both read (snmp) and read-and-write
(snmp-control) capability for SNMP, and this is the only allowed access privilege
for the network-management login class. In other words, all other access privileges
other than configuring and viewing SNMP parameters are denied.
Results
From configuration mode, confirm your configuration by entering the show system login
command. If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.
Verification
Log in as the username assigned with the new login class, and confirm that the
configuration is working properly.
Action From configuration mode, execute basic SNMP commands at the [edit snmp] hierarchy
level.
[edit snmp]
user@host# set name device1
user@host# set description switch1
user@host# set location Lab1
user@host# set contact example.com
user@host# commit
Meaning The user host assigned to the network-management login class is able to configure
SNMP parameters, as the permission flags specified for this class include both snmp
(read capabilities) and snmp-control (read and write capabilities) permission bits.
Purpose Verify that non-SNMP configuration is denied for the network-management login class.
Action From the configuration mode, execute any non-SNMP configuration, for example,
interfaces configuration.
[edit]
user@host# edit interfaces
Syntax error, expecting <statement> or <identifier>.
Supported Platforms EX Series, M Series, MX Series, PTX Series, QFX Series, SRX Series, T Series, vSRX
Create two access privilege classes on the router or switch, one for configuring and viewing
user accounts only and the second for configuring and viewing SNMP parameters only:
In this example, you create two custom login classes on the router or switch and assign
access privileges to each class through permission flags. The first custom login class is
called user-accounts and it only includes access privileges for configuring and viewing
user accounts. The second custom login class is called network-mgmt and only includes
access privileges for configuring SNMP parameters.
[edit]
system {
login {
class user-accounts {
permissions [ configure admin admin-control ];
}
class network-mgmt {
permissions [ configure snmp snmp-control ];
}
}
}
1. Create the user-accounts custom login class and give it control over user accounts
with the configure admin admin-control permission flag.
2. Create the network-mgmt custom login class and use the configure snmp snmp-control
permission flag to assign it SNMP configuration privileges.
Related • Example: Configuring User Permissions with Access Privilege Levels on page 39
Documentation
Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands
Supported Platforms EX Series, M Series, MX Series, OCX1100, PTX Series, QFabric System, QFX Series, SRX Series,
T Series, vSRX
This example shows how to configure custom login classes and assign access privileges
for operational mode commands. This enables users of the customized login class to
execute only those operational commands for which access privileges have been specified.
This prevents unauthorized users from executing sensitive commands that could
potentially cause damage to the network.
• Requirements on page 44
• Overview and Topology on page 44
• Configuration on page 47
• Verification on page 51
Requirements
This example uses the following hardware and software components:
• Establish a TCP connection between the device and the TACACS+ server. In the case
of the RADIUS server, establish a UDP connection between the device and the RADIUS
server.
• Configure at least one user assigned to a login class on the Juniper Networks device.
There can be more than one login class, each with varying permission configurations,
and more than one user on the device.
access privileges. To configure access privilege levels, include the permissions statement
at the [edit system login class class-name] hierarchy level.
The access privileges for each login class are defined by one or more permission flags
specified in the permissions statement. In addition to this, you can specify extended
regular expressions with the following statements:
The above statements define a user’s access privileges to individual operational mode
commands, configuration statements, and hierarchies. These statements take precedence
over a login class permissions bit set for a user.
Configuration Notes
• You can include one deny-commands and one allow-commands statement in each
login class.
For instance, with the following configuration, a user assigned to login class test is
allowed to install software using the request system software add command, although
the deny-commands statement also includes it:
For instance, for the following configuration, a user assigned to test login class is allowed
to execute the commit synchronize command and not the commit command. This is
because commit-synchronize is the longest match between commit and
commit-synchronize and it is specified for allow-commands.
• If the regular expression contains any spaces, operators, or wildcard characters, enclose
the expression in quotation marks. Regular expressions are not case-sensitive, for
example, allow-commands "show interfaces";
• Modifiers, such as set, log, and count, are not supported within the regular expression
string to be matched. If a modifier is used, then nothing is matched.
Incorrect configuration:
Correct configuration:
• Anchors are required when specifying complex regular expressions with the
allow-commands statement.
For example:
OR
set class test permissions allow-commands "allow-commands ="^(monitor | ping |
show | exit)"
Topology
TCP connection
g043487
R1 TACACS+
Server
In this example, R1 is configured with three customized login classes—Class1, Class2, and
Class3—for specifying access privileges with extended regular expressions using the
allow-commands and deny-commands statements differently.
• Class1—Defines access privileges for the user with the allow-commands statement
only. This login class provides operator-level user permissions, and should provide
authorization for only rebooting the device.
• Class2—Defines access privileges for the user with the deny-commands statement
only. This login class provides operator-level user permissions, and should deny access
to set commands.
• Class3—Defines access privileges for the user with both the allow-commands and
deny-commands statements. This login class provides superuser-level user permissions,
and should provide authorization for accessing interfaces and viewing device
information. It should also deny access to edit and configure commands.
Router R1 has three different users, User1, User2, and User3, assigned to Class1, Class2,
and Class3 login classes, respectively.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires that you navigate various levels in the configuration
Procedure hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
1. Configure the order in which authentication should take place for R1. In this example,
TACACS+ server authentication is first, followed by RADIUS server authentication,
and then the local password.
[edit system]
user@R1# set authentication-order tacplus
user@R1# set authentication-order radius
user@R1# set authentication-order password
[edit system]
user@R1# set tacplus-server 10.209.1.66
user@R1# set tacplus-options enhanced-accounting
user@R1# set accounting destination tacplus server 10.209.1.66
[edit system]
user@R1# set radius-server 10.209.1.66 secret "$ABC123"
user@R1# set radius-options enhanced-accounting
[edit system]
user@R1# set accounting events login
user@R1# set accounting events change-log
user@R1# set accounting events interactive-commands
user@R1# set accounting traceoptions file auditlog
user@R1# set accounting traceoptions flag all
Step-by-Step To specify regular expressions using both the allow-commands and deny-commands
Procedure statements:
1. Configure the Class3 custom login class and assign superuser-level user permissions.
For information on the predefined system login classes, see the Junos OS Login
Classes Overview.
Results
From configuration mode, confirm your configuration by entering the show system
command. If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.
}
login {
class Class1 {
permissions [ clear network reset trace view ];
allow-commands "request system reboot";
}
class Class2 {
permissions [ clear network reset trace view ];
deny-commands set;
}
class Class3 {
permissions all;
allow-commands configure;
deny-commands .*;
}
user User1 {
uid 2001;
class Class1;
authentication {
encrypted-password "$ABC123";
}
}
user User2 {
uid 2002;
class Class2;
authentication {
encrypted-password "$ABC123";
}
}
user User3 {
uid 2003;
class Class3;
authentication {
encrypted-password “$ABC123”;
}
}
}
syslog {
file messages {
any any;
}
}
Verification
Log in as the username assigned with the new login class, and confirm that the
configuration is working properly.
Purpose Verify that the permissions and commands allowed in the Class1 login class are working.
Action From operational mode, run the show system users command.
Meaning The Class1 login class to which User1 is assigned has the operator-level user permissions,
and is allowed to execute the request system reboot command.
The predefined operator login class has the following permission flags specified:
• clear—Can clear (delete) information learned from the network that is stored in various
network databases by using the clear commands.
• network—Can access the network by using the ping, ssh, telnet, and traceroute
commands.
• reset—Can restart software processes by using the restart command and can configure
whether software processes are enabled or disabled at the [edit system processes]
hierarchy level.
• trace—Can view trace file settings and configure trace file properties.
• view—Can use various commands to display current system-wide, routing table, and
protocol-specific values and statistics. Cannot view the secret configuration.
For the Class1 login class, in addition to the above-mentioned user permissions, User1
can execute the request system reboot command. The first output displays the view
permissions as an operator, and the second output shows that the only request command
that User1 can execute as an operator is the request system reboot command.
Purpose Verify that the permissions and commands allowed for the Class2 login class are working.
User2@R1> ?
Possible completions:
clear Clear information in the system
file Perform file operations
help Provide help information
load Load information from file
monitor Show real-time debugging information
mtrace Trace multicast path from source to receiver
op Invoke an operation script
ping Ping remote target
quit Exit the management session
request Make system-level requests
restart Restart software process
save Save information to file
show Show system information
ssh Start secure shell on another host
start Start shell
telnet Telnet to another host
test Perform diagnostic debugging
traceroute Trace route to remote host
User2@R1> set
^
unknown command.
Meaning The Class2 login class to which User2 is assigned has the operator-level user permissions,
and is denied access to all set commands. This is displayed in the command outputs.
The permission flags specified for the predefined operator login class are the same as
that of Class1.
Purpose Verify that the permissions and commands allowed for the Class3 login class are working.
User3@R1> ?
Possible completions:
configure Manipulate software configuration information
User3@R1> configure
Entering configuration mode
[edit]
User3@R1#
Meaning The Class3 login class to which User3 is assigned has the superuser (all) user permissions,
but is allowed to execute the configure command only, and is denied access to all other
operational mode commands. Because the regular expressions specified in the
allow/deny-commands statements take precedence over the user permissions, User3
on R1 has access only to configuration mode, and is denied access to all other operational
mode commands.
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands, Configuration Statements, and Hierarchies on page 68
Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands
Supported Platforms EX Series, M Series, MX Series, OCX1100, PTX Series, QFabric System, QFX Series, SRX Series,
T Series, vSRX
Each operational mode command has an access privilege level associated with it. Access
privileges control the commands that each custom login class can execute, configure,
and view. Custom login classes are groups of users who are assigned with customized
levels of access to different commands and statements. This ensures that each group
of users can only use commands appropriate to their function, preventing unauthorized
users from executing sensitive commands that could potentially cause damage to the
network.
In this example, you create three custom login classes on the router or switch and assign
access privileges for operational mode commands through the allow-commands and
deny-commands settings. Each custom login class uses the same set of permission flags
as the default login class operator, but the login class is allowed or denied certain
operational mode commands. The first custom login class is called operator-and-boot
and it has access to the request system reboot operational mode command. The second
custom login class is called operator-no-set and it is denied access to any set commands.
The third login class is called operator-and-install-but-no-bgp and it has access to the
request system software add and show route operational mode commands, but it is denied
access to the show bgp command.
[edit]
system {
login {
class operator-and-boot {
permissions [ clear network reset trace view ];
allow-commands "request system reboot";
}
class operator-no-set {
permissions [ clear network reset trace view ];
deny-commands "set";
}
class operator-and-install-but-no-bgp {
permissions [ clear network reset trace view ];
allow-commands "(request system software add)|(show route$)";
deny-commands "show bgp";
}
}
}
1. Create the operator-and-boot custom login class, give it operator level permission
flags, and authorize it to use the request system reboot command.
2. Create the operator-no-set custom login class, give it operator level permission flags,
and deny it access to the set command.
Related • Example: Configuring User Permissions with Access Privileges for Operational Mode
Documentation Commands on page 44
This example shows how to configure custom login classes and assign access privileges
to portions of the configuration hierarchy. This enables users of the customized login
class to execute only those configuration statements and hierarchies for which access
privileges have been specified. This prevents unauthorized users from accessing device
configurations that could potentially cause damage to the network.
• Requirements on page 56
• Overview and Topology on page 57
• Configuration on page 63
• Verification on page 67
Requirements
This example uses the following hardware and software components:
• Establish a TCP connection between the device and the TACACS+ server. In the case
of the RADIUS server, establish a UDP connection between the device and the RADIUS
server.
• Configure at least one user assigned to a login class on the Juniper Networks device.
There can be more than one login class, each with varying permission configurations,
and more than one user on the device.
The access privileges for each login class are defined by one or more permission flags
specified in the permissions statement. In addition to this, you can specify extended
regular expressions with the following statements:
These statements perform slower matching, with more flexibility, especially in wildcard
matching. However, it can take a very long time to evaluate all of the possible
statements if a great number of full-path regular expressions or wildcard expressions
are configured, possibly impacting performance.
The above statements define a user’s access privileges to individual operational mode
commands, configuration statements, and hierarchies. These statements take precedence
over a login class permissions bit set for a user.
statements were introduced in Junos OS Release 11.2. In Junos OS Release 11.4, the
allow-configuration and deny-configuration statements were deprecated, but because
these statements were useful in executing simple configurations, these statements were
undeprecated in Junos OS Release 11.4R6, and starting with the 11.4R6 release, both the
allow/deny-configuration and the allow/deny-configuration-regexps statements are
supported.
For example:
This example shows that options is the only matched expression against the first token
of the statement.
[edit system]
login {
class test {
permissions configure;
allow-configuration-regexps .*options;
}
}
This example shows that ssh is the only matched expression against the third token
of the statement.
[edit system]
login {
class test {
permissions configure;
allow-configuration-regexps ".* .* .*ssh";
}
}
In the above example, the three tokens include .*, .*, and .*ssh, respectively.
You can restrict configuration access easily using the deny-configuration statement as
compared to using the deny-configuration-regexps statement. Table 7 on page 59
illustrates the use of both the deny-configuration and deny-configuration-regexps
statements in different configurations to achieve the same result of restricting access
to a particular configuration.
Configuration Notes
• You can include one deny-configuration and one allow-configuration statement in each
login class.
For example, for the following configuration, the login class user can edit the
configuration at the [edit system services] hierarchy level and issue configuration mode
commands (such as commit), in addition to just entering the configuration mode using
the configure command, which is the permission specified by the configure permission
flag:
Likewise, for the following configuration, the login class user can perform all operations
allowed by the all permissions flag, except issuing configuration mode commands
(such as commit) or modifying the configuration at the [edit system services] hierarchy
level:
• To define access privileges to parts of the configuration hierarchy, specify the full paths
in the extended regular expressions with the allow-configuration and deny-configuration
statements. Use parentheses around an extended regular expression that connects
two or more expressions with the pipe (|) symbol.
For example:
For example:
For example:
For instance, with the following configuration, a user assigned to login class test is
allowed to access the [edit system services] configuration hierarchy, although the
deny-configuration statement also includes it:
• Modifiers such as set, log, and count are not supported within the regular expression
string to be matched. If a modifier is used, then nothing is matched.
Incorrect configuration:
Correct configuration:
• You can use the * wildcard character when denoting regular expressions. However, it
must be used as a portion of a regular expression. You cannot use [ * ] or [ .* ] alone.
• You cannot configure the allow-configuration statement with the (interfaces (description
(|.*)) regular expression, as this evaluates to allow-configuration = .* regular expression.
Topology
TCP connection
g043487
R1 TACACS+
Server
In this example, R1 is configured with two customized login classes—Class1 and Class2—for
specifying access privileges with extended regular expressions using the
allow-configuration, deny-configuration, allow-configuration-regexps, and
deny-configuration-regexps statements differently.
• Class1—Define access privileges for the user with the allow-configuration and
deny-configuration statements. This login class should provide access to configure
interfaces hierarchy only, and deny all other access on the device. To do this, the user
permissions should include configure to provide configuration access. In addition to
this, the allow-configuration statement should allow interfaces configuration, and the
deny-configuration statement should deny access to all other configurations. Because
the allow statement takes precedence over the deny statement, the users assigned
to the Class1 login class can access only the [edit interfaces] hierarchy level.
• Class2—Define access privileges for the user with the allow-configuration-regexps and
deny-configuration-regexps statements. This login class provides superuser-level user
permissions, and in addition, explicitly allows configuration under multiple hierarchy
levels for interfaces. It also denies configuration access to the [edit system] and [edit
protocols] hierarchy levels.
Router R1 has two users, User1 and User2, assigned to the Class1 and Class2 login classes,
respectively.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires that you navigate various levels in the configuration
Procedure hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
1. Configure the order in which authentication should take place for R1. In this example,
TACACS+ server authentication is first, followed by RADIUS server authentication,
then the local password.
[edit system]
user@R1# set authentication-order tacplus
user@R1# set authentication-order radius
user@R1# set authentication-order password
[edit system]
user@R1# set tacplus-server 10.209.1.66
user@R1# set tacplus-options enhanced-accounting
user@R1# set accounting destination tacplus server 10.209.1.66
[edit system]
user@R1# set radius-server 10.209.1.66 secret "$ABC123"
user@R1# set radius-options enhanced-accounting
[edit system]
user@R1# set accounting events login
user@R1# set accounting events change-log
user@R1# set accounting events interactive-commands
user@R1# set accounting traceoptions file auditlog
user@R1# set accounting traceoptions flag all
1. Configure the Class1 custom login class and assign configuration user permissions.
1. Configure the Class2 custom login class and assign superuser (all) user permissions.
For information on the predefined system login classes, see Junos OS Login Classes
Overview.
2. Specify the regular expression to allow access to multiple hierarchies under the
[edit interfaces] hierarchy level.
3. Specify the regular expression to deny configuration at the [edit system] and [edit
protocols] hierarchy levels.
Results
From configuration mode, confirm your configuration by entering the show system
command. If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.
enhanced-accounting;
}
accounting {
events [ login change-log interactive-commands ];
traceoptions {
file auditlog;
flag all;
}
destination {
tacplus {
server {
10.209.1.66;
}
}
}
}
login {
class Class1 {
permissions configure;
allow-configuration "interfaces .* unit .*";
deny-configuration .*;
}
class Class2 {
permissions all;
allow-configuration-regexps [ "interfaces .* description .*" "interfaces .* unit .*
description .*" "interfaces .* unit .* family inet address .*" "interfaces.* disable" ];
deny-configuration-regexps [ "system" "protocols" ];
}
user User1 {
uid 2001;
class Class1;
authentication {
encrypted-password "$ABC123";
}
}
user User2 {
uid 2002;
class Class2;
authentication {
encrypted-password "$ABC123";
}
}
}
syslog {
file messages {
any any;
}
}
Verification
Log in as the username assigned with the new login class, and confirm that the
configuration is working properly.
Purpose Verify that the permissions allowed in the Class1 login class are working.
User1@R1> ?
Possible completions:
clear Clear information in the system
configure Manipulate software configuration information
file Perform file operations
help Provide help information
load Load information from file
op Invoke an operation script
quit Exit the management session
request Make system-level requests
save Save information to file
set Set CLI properties, date/time, craft interface message
start Start shell
test Perform diagnostic debugging
User1@R1# edit ?
Possible completions:
> interfaces Interface configuration
Meaning User1 has configure user permissions seen in the first output, and the only configuration
access allowed for User1 is at the interfaces hierarchy level. All other configuration is
denied, as seen in the second output.
[edit interfaces]
User2@R1# set ?
Possible completions:
<interface-name> Interface name
+ apply-groups Groups from which to inherit configuration data
From the configuration mode, access the system and protocols configuration hierarchies.
Meaning User2 has permissions to configure interfaces of R1, but the [edit system] and [edit
protocols] hierarchy levels are denied access, as seen in the output.
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands, Configuration Statements, and Hierarchies on page 68
Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands, Configuration Statements, and Hierarchies
This example shows how to configure custom login classes and assign access privileges
for operational mode commands and to portions of the configuration hierarchy. This
enables users of the customized login class to execute only those commands and access
only those configuration statements and hierarchies for which access privileges have
been specified. This prevents unauthorized users from executing sensitive commands
or accessing device configurations that could potentially cause damage to the network.
• Requirements on page 69
• Overview and Topology on page 69
• Configuration on page 73
• Verification on page 76
Requirements
This example uses the following hardware and software components:
• Establish a TCP connection between the device and the TACACS+ server. In the case
of the RADIUS server, establish a UDP connection between the device and the RADIUS
server.
• Configure at least one user assigned to a login class on the Juniper Networks device.
There can be more than one login class, each with varying permission configurations,
and more than one user on the device.
The access privileges for each login class are defined by one or more permission flags
specified in the permissions statement. In addition to this, you can specify extended
regular expressions with the following statements:
The above statements define a user’s access privileges to individual operational mode
commands, configuration statements, and hierarchies. These statements take precedence
over a login class permissions bit set for a user.
Configuration Notes
• You can include the allow/deny statement only once in each login class.
For instance, with the following configuration, a user assigned to login class test is
allowed to install software using the request system software add command, although
the deny-commands statement also includes it:
For instance, with the following configuration, a user assigned to login class test is
allowed to access the [edit system services] configuration hierarchy, although the
deny-configuration statement also includes it:
For instance, for the following configuration, a user assigned to test login class is allowed
to execute the commit synchronize command and not the commit command. This is
because commit-synchronize is the longest match between commit and
commit-synchronize, and it is specified for allow-commands.
For example, for the following configuration, the login class user can edit the
configuration at the [edit system services] hierarchy level and issue configuration mode
commands (such as commit), in addition to just entering the configuration mode using
the configure command, which is the permission specified by the configure permission
flag:
Likewise, for the following configuration, the login class user can perform all operations
allowed by the all permissions flag, except issuing configuration mode commands
(such as commit) or modifying the configuration at the [edit system services] hierarchy
level:
• To define access privileges to parts of the configuration hierarchy, specify the full paths
in the extended regular expressions with the allow-configuration and deny-configuration
statements. Use parentheses around an extended regular expression that connects
two or more expressions with the pipe (|) symbol.
For example:
• If the regular expression contains any spaces, operators, or wildcard characters, enclose
the expression in quotation marks. Regular expressions are not case-sensitive; for
example, allow-commands "show interfaces".
• Modifiers such as set, log, and count are not supported within the regular expression
string to be matched. If a modifier is used, then nothing is matched.
Incorrect configuration:
Correct configuration:
• Anchors are required when specifying complex regular expressions with the
allow-commands statement.
For example:
OR
set class test permissions allow-commands "allow-commands ="^(monitor | ping |
show | exit)"
For example:
For example:
• You can use the * wildcard character when denoting regular expressions. However, it
must be used as a portion of a regular expression. You cannot use [ * ] or [ .* ] alone.
• You cannot configure the allow-configuration statement with the (interfaces (description
(|.*)) regular expression, as this evaluates to allow-configuration = .* regular expression.
Topology
TCP connection
g043487
R1 TACACS+
Server
The purpose of the Class1 login class is to provide security user permission with access
to only the configure command, and deny access to all other operational mode commands.
The login class again filters the configuration access to only group VPN configuration
under the [edit security] hierarchy, and denies access to the multi-chassis configuration
statement, which is allowed with the security user permissions.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires that you navigate various levels in the configuration
Procedure hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
1. Configure the order in which authentication should take place for R1. In this example,
TACACS+ server authentication is first, followed by RADIUS server authentication,
then the local password.
[edit system]
user@R1# set authentication-order tacplus
user@R1# set authentication-order radius
user@R1# set authentication-order password
[edit system]
user@R1# set tacplus-server 10.209.1.66
user@R1# set tacplus-options enhanced-accounting
user@R1# set accounting destination tacplus server 10.209.1.66
[edit system]
user@R1# set radius-server 10.209.1.66 secret "$ABC123"
user@R1# set radius-options enhanced-accounting
[edit system]
user@R1# set accounting events login
user@R1# set accounting events change-log
user@R1# set accounting events interactive-commands
user@R1# set accounting traceoptions file auditlog
user@R1# set accounting traceoptions flag all
Step-by-Step To specify regular expressions for user permissions with access privileges:
Procedure
1. Configure the Class1 custom login class and assign security user permissions.
Results
From configuration mode, confirm your configuration by entering the show system
command. If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.
}
}
Verification
Log in as the username assigned with the new login class, and confirm that the
configuration is working properly.
Purpose Verify that the permissions and regular expressions allowed in Class1 login class are
working.
Action From the CLI prompt, view the allowed user permissions.
User1@R1> ?
Possible completions:
configure Manipulate software configuration information
From the configuration mode, enter the [edit security] hierarchy and view the allowed
configuration statements.
User1@R1> edit ?
Possible completions:
> group-vpn Group VPN configuration
Meaning User 1 has security user permissions, which allows the user to view the security
configuration in configuration mode and with the show configuration operational mode
command. However, this has been altered with the allow-commands and deny-commands
statements, where User1 is able to enter configuration mode with the configure command
in the allow-commands statement, and is denied access to all other operational mode
commands with the use of the deny-commands .* statement. As a result, even the show
configuration command, which was allowed with the security user permissions, is now
denied. This is displayed in the first output.
In the second output, the allow-configuration statement takes effect, and the only allowed
configuration under the [edit security] hierarchy level is for group VPN.
In the last output, the deny-configuration statement takes effect, and the multi-chassis
configuration statement that is allowed with the security user permissions is denied for
User1.
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Permission flags are used to grant a user access to operational mode commands and
configuration hierarchy levels and statements. By specifying a specific permission flag
on the user's login class at the [edit system login class] hierarchy level, you grant the user
access to the corresponding commands and configuration hierarchy levels and
statements. To grant access to all commands and configuration statements, use the all
permissions flag.
For permission flags that grant access to configuration hierarchy levels and statements,
the flags grant read-only privilege to that configuration. For example, the interface
permissions flag grants read-only access to the [edit interfaces] hierarchy level. The
-control form of the flag grants read-write access to that configuration. Using the
preceding example, interface-control grants read-write access to the [edit interfaces]
hierarchy level.
The permission flags listed in "Related Documentation" grant a specific set of access
privileges. Each permission flag is listed with the operational mode commands and
configuration hierarchy levels and statements for which that flag grants access.
NOTE: Each command listed represents that command and all subcommands
with that command as a prefix. Each configuration statement listed represents
the top of the configuration hierarchy to which that flag grants access.
• access-control on page 85
• admin on page 86
• admin-control on page 90
• all-control on page 91
• clear on page 91
access
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
<clear-mobile-gateway-statistics>
clear unified-edge ggsn-pgw subscribers
<clear-mobile-gateway-subscribers>
clear unified-edge ggsn-pgw subscribers bearer
clear unified-edge ggsn-pgw subscribers charging
<clear-mobile-gateway-subscribers-charging>
clear unified-edge ggsn-pgw subscribers peer
<clear-mobile-gateway-subscribers-peer>
clear unified-edge sgw
clear unified-edge sgw call-admission-control
clear unified-edge sgw call-admission-control statistics
<clear-mobile-sgw-cac-statistics>
clear unified-edge sgw charging
clear unified-edge sgw charging cdr
<clear-mobile-gateway-sgw-charging-clear-cdr>
clear unified-edge sgw charging cdr wfa
<clear-mobile-gateway-sgw-charging-clear-cdr-wfa>
clear unified-edge sgw charging local-persistent-storage
clear unified-edge sgw charging local-persistent-storage statistics
<clear-mobile-gateway-sgw-charging-clear-lps-stats>
clear unified-edge sgw charging path
clear unified-edge sgw charging path statistics
<clear-mobile-gateway-sgw-charging-clear-path-stats>
clear unified-edge sgw charging transfer
clear unified-edge sgw charging transfer statistics
<clear-mobile-gateway-sgw-charging-clear-xfer-stats>
clear unified-edge sgw gtp
clear unified-edge sgw gtp peer
clear unified-edge sgw gtp peer statistics
<clear-mobile-sgw-gtp-peer-statistics>
clear unified-edge sgw gtp statistics
<clear-mobile-sgw-gtp-statistics>
clear unified-edge sgw idle-mode-buffering
clear unified-edge sgw idle-mode-buffering statistics
<clear-mobile-gw-sgw-idle-mode-buffering-statistics>
clear unified-edge sgw ip-reassembly
clear unified-edge sgw ip-reassembly statistics
<clear-mobile-gateways-sgw-ip-reassembly-statistics-sgw>
clear unified-edge sgw statistics
<clear-mobile-sgw-statistics>
clear unified-edge sgw subscribers
<clear-mobile-sgw-subscribers>
clear unified-edge sgw subscribers charging
<clear-mobile-sgw-subscribers-charging>
clear unified-edge sgw subscribers peer
<clear-mobile-sgw-subscribers-peer>
clear unified-edge tdf
clear unified-edge tdf aaa
clear unified-edge tdf aaa radius
clear unified-edge tdf aaa radius client
clear unified-edge tdf aaa radius client statistics
<clear-radius-client-statistics>
clear unified-edge tdf aaa radius network-element
clear unified-edge tdf aaa radius network-element statistics
<clear-radius-network-element-statistics>
clear unified-edge tdf aaa radius server
clear unified-edge tdf aaa radius server statistics
<clear-radius-server-statistics>
clear unified-edge tdf aaa radius snoop-segment
clear unified-edge tdf aaa radius snoop-segment statistics
<clear-radius-snoop-segment-statistics>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
• access-control on page 85
access-control
Can view access configuration information. Can edit access configuration at the [edit
access], [edit logical-systems], [edit routing-instances, and [edit system services] hierarchy
levels.
Configuration
Hierarchy Levels [edit access]
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
• access on page 82
admin
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
<clear-mobile-gateway-sm-ippool-pool-sessions>
clear unified-edge ggsn-pgw address-assignment statistics
<clear-mobile-gateway-sm-ippool-statistics>
clear unified-edge ggsn-pgw call-admission-control
clear unified-edge ggsn-pgw call-admission-control statistics
<clear-mobile-gateway-cac-statistics>
clear unified-edge ggsn-pgw charging
clear unified-edge ggsn-pgw charging cdr
<clear-mobile-gateway-charging-clear-cdr>
clear unified-edge ggsn-pgw charging cdr wfa
<clear-mobile-gateway-charging-clear-cdr-wfa>
clear unified-edge ggsn-pgw charging local-persistent-storage
clear unified-edge ggsn-pgw charging local-persistent-storage statistics
<clear-mobile-gateway-charging-clear-lps-stats>
clear unified-edge ggsn-pgw charging path
clear unified-edge ggsn-pgw charging path statistics
<clear-mobile-gateway-charging-clear-path-stats>
clear unified-edge ggsn-pgw charging transfer
clear unified-edge ggsn-pgw charging transfer statistics
<clear-mobile-gateway-charging-clear-xfer-stats>
clear unified-edge ggsn-pgw diameter
clear unified-edge ggsn-pgw diameter dcca-gy
clear unified-edge ggsn-pgw diameter dcca-gy statistics
<clear-mobile-gateway-aaa-diam-stats-gy>
clear unified-edge ggsn-pgw diameter network-element
clear unified-edge ggsn-pgw diameter network-element statistics
<clear-mobile-gateway-aaa-diam-ne-statistics>
clear unified-edge ggsn-pgw diameter pcc-gx
clear unified-edge ggsn-pgw diameter pcc-gx statistics
<clear-mobile-gateway-aaa-diam-stats-gx>
clear unified-edge ggsn-pgw diameter peer
clear unified-edge ggsn-pgw diameter peer statistics
<clear-mobile-gateway-aaa-diam-peer-statistics>
clear unified-edge ggsn-pgw gtp
clear unified-edge ggsn-pgw gtp peer
clear unified-edge ggsn-pgw gtp peer statistics
<clear-mobile-gateway-gtp-peer-statistics>
clear unified-edge ggsn-pgw gtp statistics
<clear-mobile-gateway-gtp-statistics>
clear unified-edge ggsn-pgw ip-reassembly
clear unified-edge ggsn-pgw ip-reassembly statistics
<clear-mobile-gateways-ip-reassembly-statistics>
clear unified-edge ggsn-pgw statistics
<clear-mobile-gateway-statistics>
clear unified-edge ggsn-pgw subscribers
<clear-mobile-gateway-subscribers>
clear unified-edge ggsn-pgw subscribers bearer
clear unified-edge ggsn-pgw subscribers charging
<clear-mobile-gateway-subscribers-charging>
clear unified-edge ggsn-pgw subscribers peer
<clear-mobile-gateway-subscribers-peer>
clear unified-edge sgw
clear unified-edge sgw call-admission-control
clear unified-edge sgw call-admission-control statistics
<clear-mobile-sgw-cac-statistics>
clear unified-edge sgw charging
clear unified-edge sgw charging cdr
<clear-mobile-gateway-sgw-charging-clear-cdr>
clear unified-edge sgw charging cdr wfa
<clear-mobile-gateway-sgw-charging-clear-cdr-wfa>
clear unified-edge sgw charging local-persistent-storage
Configuration
Hierarchy Levels [edit protocols uplink-failure-detection]
[edit system]
[edit system accounting]
[edit system diag-port-authentication]
[edit system extensions]
[edit system login]
[edit system pic-console-authentication]
[edit system root-authentication]
[edit system services ssh authorized-keys-command]
[edit system services ssh authorized-keys-command-user]
[edit system services ssh ciphers]
[edit system services ssh client-alive-count-max]
[edit system services ssh client-alive-interval]]
[edit system services ssh fingerprint-hash]
[edit system services ssh hostkey-algorithm]
[edit system services ssh key-exchange]
[edit system services ssh macs]
[edit system services ssh max-sessions-per-connection]
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
• admin-control on page 90
admin-control
Can view user account information and configure it at the [edit system] hierarchy level.
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
• admin on page 86
all-control
Can access all operational mode commands and configuration mode commands. Can
modify configuration in all the configuration hierarchy levels.
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
clear
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Can clear (delete) information learned from the network that is stored in various network
databases.
Commands clear
clear access-security
clear access-security router-advertisement-entries
<clear-as-router-advetisement-entry>
clear amt
clear amt statistics
<clear-amt-statistics>
clear amt tunnel
clear-amt-tunnel
clear amt tunnel gateway-address
<clear amt tunnel gateway-address>
clear amt tunnel statistics
<clear-amt-tunnel-statistics>
clear amt tunnel statistics gateway-address
<clear-amt-tunnel-gateway-address-statistics>
clear amt tunnel statistics tunnel-interface
<clear-amt-tunnel-interface-statistics>
clear amt tunnel tunnel-interface
<clear-amt-tunnel-interface<>
clear ancp
clear ancp neighbor
<clear-ancp-neighbor-connection>
clear ancp statistics
<clear-ancp-statistics>
<clear-cli-logical-system>
clear database-replication
clear database-replication statistics
<clear-database-replication-statistics-information>
clear ddos-protection
clear ddos-protection protocols
clear ddos-protection protocols all-fiber-channel-enode
clear ddos-protection protocols all-fiber-channel-enode aggregate
clear ddos-protection protocols all-fiber-channel-enode aggregate culprit-flows
<clear-ddos-all-fc-enode-aggregate-flows>
clear ddos-protection protocols all-fiber-channel-enode aggregate states
<clear-ddos-all-fc-enode-aggregate-states>
clear ddos-protection protocols all-fiber-channel-enode aggregate statistics
<clear-ddos-all-fc-enode-aggregate-statistics>
clear ddos-protection protocols all-fiber-channel-enode culprit-flows
<clear-ddos-all-fc-enode-flows>
clear ddos-protection protocols all-fiber-channel-enode states
<clear-ddos-all-fc-enode-states>
clear ddos-protection protocols all-fiber-channel-enode statistics
<clear-ddos-all-fc-enode-statistics>
clear ddos-protection protocols amtv4
clear ddos-protection protocols amtv4 aggregate
clear ddos-protection protocols amtv4 aggregate culprit-flows
clear ddos-protection protocols amtv4 aggregate states
clear ddos-protection protocols amtv4 aggregate statistics
clear ddos-protection protocols amtv4 culprit-flows
clear ddos-protection protocols amtv4 states
clear ddos-protection protocols amtv4 statistics
clear ddos-protection protocols amtv6
clear ddos-protection protocols amtv6 aggregate
clear ddos-protection protocols amtv6 aggregate culprit-flows
<clear-ddos-amtv6-aggregate-flows>
clear ddos-protection protocols amtv6 aggregate states
<clear-ddos-amtv6-aggregate-states>
clear ddos-protection protocols amtv6 aggregate statistics
<clear-ddos-amtv6-aggregate-statistics>
clear ddos-protection protocols amtv6 culprit-flows
<clear-ddos-amtv6-flows>
clear ddos-protection protocols amtv6 states
<clear-ddos-amtv6-states<>
clear ddos-protection protocols amtv6 statistics
<clear-ddos-amtv6-statistics>
clear ddos-protection protocols ancp aggregate culprit-flows
<clear-ddos-ancp-aggregate-flows>
clear ddos-protection protocols ancp culprit-flows
clear ddos-protection protocols ancp
clear ddos-protection protocols ancp aggregate
clear ddos-protection protocols ancp aggregate states
clear ddos-protection protocols ancp aggregate statistics
<clear-ddos-ancp-aggregate-statistics>
clear ddos-protection protocols ancp states
<clear-ddos-ancp-states>
clear ddos-protection protocols ancp statistics
<clear-ddos-ancp-statistics>
clear ddos-protection protocols ancpv6
clear ddos-protection protocols ancpv6 aggregate
clear ddos-protection protocols ancpv6 aggregate states
<clear-ddos-dhcpv4v6-aggregate-statistics>
clear ddos-protection protocols dhcpv4v6 culprit-flows
<clear-ddos-dhcpv4v6-flows>
clear ddos-protection protocols dhcpv4v6 states
<clear-ddos-dhcpv4v6-states>
clear ddos-protection protocols dhcpv4v6 statistics
<clear-ddos-dhcpv4v6-statistics>
clear-ddos-demuxauto-aggregate-states
clear-ddos-demuxauto-aggregate-statistics
clear-ddos-demuxauto-states
clear-ddos-demuxauto-statistics
clear-ddos-dhcpv4-ack-states
clear ddos-protection protocols dhcpv4 ack statistics
clear-ddos-dhcpv4-ack-statistics
clear ddos-protection protocols dhcpv4 aggregate
clear ddos-protection protocols dhcpv4 aggregate states
clear-ddos-dhcpv4-aggregate-states
clear ddos-protection protocols dhcpv4 aggregate statistics
clear-ddos-dhcpv4-aggregate-statistics
clear ddos-protection protocols dhcpv4 bad-packets
clear ddos-protection protocols dhcpv4 bad-packets states
clear-ddos-dhcpv4-bad-pack-states
clear ddos-protection protocols dhcpv4 bad-packets statistics
clear-ddos-dhcpv4-bad-pack-statistics
clear ddos-protection protocols dhcpv4 bootp
clear ddos-protection protocols dhcpv4 bootp states
clear-ddos-dhcpv4-bootp-states
clear ddos-protection protocols dhcpv4 bootp statistics
clear-ddos-dhcpv4-bootp-statistics
clear ddos-protection protocols dhcpv4 decline
clear ddos-protection protocols dhcpv4 decline culprit-flows
clear ddos-protection protocols dhcpv4 decline states
clear-ddos-dhcpv4-decline-states
clear ddos-protection protocols dhcpv4 decline statistics
clear-ddos-dhcpv4-decline-statistics
clear ddos-protection protocols dhcpv4 discover
clear ddos-protection protocols dhcpv4 discover states
clear-ddos-dhcpv4-discover-states
clear ddos-protection protocols dhcpv4 discover statistics
clear-ddos-dhcpv4-discover-statistics
clear ddos-protection protocols dhcpv4 force-renew
clear ddos-protection protocols dhcpv4 force-renew culprit-flows
clear ddos-protection protocols dhcpv4 force-renew states
clear-ddos-dhcpv4-forcerenew-states
clear ddos-protection protocols dhcpv4 force-renew statistics
clear-ddos-dhcpv4-forcerenew-statistics
clear ddos-protection protocols dhcpv4 inform
clear ddos-protection protocols dhcpv4 inform culprit-flows
clear ddos-protection protocols dhcpv4 inform states
clear-ddos-dhcpv4-decline-states
clear-ddos-dhcpv4-decline-statistics
clear-ddos-dhcpv4-discover-states
clear-ddos-dhcpv4-discover-statistics
clear-ddos-dhcpv4-forcerenew-states
clear-ddos-dhcpv4-forcerenew-statistics
clear ddos-protection protocols dhcpv4 unclassified culprit-flows
clear ddos-protection protocols dhcpv4 unclassified states
clear-ddos-dhcpv4-unclass-states
clear ddos-protection protocols dhcpv4 unclassified statistics
clear-ddos-dhcpv4-unclass-statistics
clear ddos-protection protocols dhcpv6
clear-ddos-dynvlan-states
clear-ddos-dynvlan-statistics
clear-ddos-egpv6-aggregate-states
clear-ddos-egpv6-aggregate-statistics
clear-ddos-egpv6-states
clear-ddos-egpv6-statistics
clear-ddos-eoam-aggregate-states
clear-ddos-eoam-aggregate-statistics
clear-ddos-eoam-states
clear-ddos-eoam-statistics
clear-ddos-esmc-aggregate-states
clear-ddos-esmc-aggregate-statistics
clear-ddos-esmc-states
clear ddos-protection protocols fab-probe states
<clear-ddos-fab-probe-states>
clear ddos-protection protocols fab-probe statistics
<clear-ddos-fab-probe-statistics>
clear-ddos-esmc-statistics
clear ddos-protection protocols firewall-host
clear ddos-protection protocols firewall-host aggregate
clear ddos-protection protocols firewall-host aggregate culprit-flows
clear ddos-protection protocols firewall-host aggregate states
clear-ddos-fw-host-aggregate-states
clear ddos-protection protocols firewall-host aggregate statistics
clear ddos-protection protocols firewall-host states
clear ddos-protection protocols firewall-host statistics
clear-ddos-esmc-statistics
clear-ddos-fw-host-aggregate-states
clear-ddos-fw-host-aggregate-statistics
<clear-ddos-fw-host-statistics>
clear-ddos-fw-host-states
clear ddos-protection protocols frame-relay
clear ddos-protection protocols frame-relay aggregate
clear ddos-protection protocols frame-relay aggregate culprit-flows
clear ddos-protection protocols frame-relay aggregate states
clear ddos-protection protocols frame-relay aggregate statistics
clear ddos-protection protocols frame-relay culprit-flows
clear ddos-protection protocols frame-relay frf15
clear ddos-protection protocols frame-relay frf15 culprit-flows
clear ddos-protection protocols frame-relay frf15 states
clear ddos-protection protocols frame-relay frf15 statistics
clear ddos-protection protocols frame-relay frf16
clear ddos-protection protocols frame-relay frf16 culprit-flows
clear ddos-protection protocols frame-relay frf16 states
clear ddos-protection protocols frame-relay frf16 statistics
clear ddos-protection protocols frame-relay states
clear ddos-protection protocols frame-relay statistics
clear ddos-protection protocols ftp
clear ddos-protection protocols ftp aggregate
clear ddos-protection protocols ftp aggregate culprit-flows
clear ddos-protection protocols ftp aggregate states
clear-ddos-ftp-aggregate-states
clear ddos-protection protocols ftp aggregate statistics
clear-ddos-ftp-aggregate-statistics
clear ddos-protection protocols ftp states
clear-ddos-ftp-states
clear ddos-protection protocols ftp statistics
clear-ddos-ftp-statistics
clear ddos-protection protocols ftpv6
clear ddos-protection protocols ftpv6 aggregate
clear ddos-protection protocols ftpv6 aggregate culprit-flows
clear-ddos-igmp-snoop-aggregate-states
clear ddos-protection protocols igmp-snoop aggregate statistics
clear-ddos-igmp-snoop-aggregate-statistics
clear ddos-protection protocols igmp-snoop states
clear-ddos-igmp-snoop-states
clear ddos-protection protocols igmp-snoop statistics
clear-ddos-igmp-snoop-statistics
clear ddos-protection protocols igmpv4v6
clear ddos-protection protocols igmpv4v6 aggregate
clear ddos-protection protocols igmpv4v6 aggregate states
clear-ddos-igmpv4v6-aggregate-states
clear ddos-protection protocols igmpv4v6 aggregate statistics
clear ddos-protection protocols igmpv4v6 culprit-flows
clear ddos-protection protocols igmpv4v6 states
clear-ddos-igmpv4v6-states
clear ddos-protection protocols igmpv4v6 statistics
clear-ddos-igmpv4v6-statistics
clear ddos-protection protocols igmpv6
clear ddos-protection protocols igmpv6 aggregate
clear ddos-protection protocols igmpv6 aggregate culprit-flows
clear ddos-protection protocols igmpv6 aggregate states
clear ddos-protection protocols igmpv6 aggregate statistics
clear ddos-protection protocols igmpv6 states
clear ddos-protection protocols igmpv6 statistics
<clear-ddos-igmpv6-statistics>clear-ddos-igmp-snoop-states
clear-ddos-igmp-snoop-statistics
clear-ddos-igmp-statistics
clear-ddos-igmpv4v6-aggregate-states
clear-ddos-igmpv4v6-aggregate-statistics
clear-ddos-igmpv4v6-states
clear-ddos-igmpv4v6-statistics
clear-ddos-igmpv6-aggregate-states
clear ddos-protection protocols igmpv6 aggregate statistics
clear-ddos-igmpv6-aggregate-statistics
clear ddos-protection protocols igmpv6 states
clear-ddos-igmpv6-states
clear ddos-protection protocols inline-ka
clear ddos-protection protocols inline-ka aggregate
clear ddos-protection protocols inline-ka aggregate culprit-flows
clear ddos-protection protocols inline-ka aggregate states
clear ddos-protection protocols inline-ka aggregate statistics
clear ddos-protection protocols inline-ka culprit-flows
clear ddos-protection protocols inline-ka states
clear ddos-protection protocols inline-ka statistics
clear ddos-protection protocols inline-svcs
clear ddos-protection protocols inline-svcs aggregate
clear ddos-protection protocols inline-svcs aggregate culprit-flows
clear ddos-protection protocols inline-svcs aggregate states
clear ddos-protection protocols inline-svcs aggregate statistics
clear ddos-protection protocols inline-svcs culprit-flows
clear ddos-protection protocols inline-svcs states
clear ddos-protection protocols inline-svcs statistics
clear ddos-protection protocols ip-fragments
clear ddos-protection protocols ip-fragments aggregate
clear ddos-protection protocols ip-fragments aggregate states
clear-ddos-ip-frag-aggregate-states
clear ddos-protection protocols ip-fragments aggregate statistics
clear ddos-protection protocols ip-fragments culprit-flows
clear ddos-protection protocols ip-fragments first-fragment
clear ddos-protection protocols ip-fragments first-fragment states
clear-ddos-ip-frag-first-frag-states
clear-ddos-ipv6-uncls-aggregate-states
clear ddos-protection protocols ipv6-unclassified aggregate statistics
clear-ddos-ipv6-uncls-aggregate-statistics
clear ddos-protection protocols ipv6-unclassified states
clear-ddos-ipv6-uncls-states
clear ddos-protection protocols ipv6-unclassified statistics
clear-ddos-ipv6-uncls-statistics
clear ddos-protection protocols isis
clear ddos-protection protocols isis aggregate
clear ddos-protection protocols isis aggregate culprit-flows
clear ddos-protection protocols isis aggregate states
clear-ddos-ip-opt-rt-alert-states
clear-ddos-ip-opt-rt-alert-statistics
clear-ddos-ip-opt-states
clear-ddos-ip-opt-statistics
clear-ddos-ip-opt-unclass-states
clear-ddos-ip-opt-unclass-statistics
clear-ddos-ipv4-uncls-aggregate-states
clear-ddos-isis-aggregate-states
clear ddos-protection protocols isis aggregate statistics
<clear-ddos-isis-aggregate-statistics>
clear ddos-protection protocols isis culprit-flows
clear ddos-protection protocols isis states
clear-ddos-isis-states
clear ddos-protection protocols isis statistics
clear-ddos-isis-statistics
clear ddos-protection protocols iso-tcc
clear ddos-protection protocols iso-tcc aggregate
clear ddos-protection protocols iso-tcc aggregate culprit-flows
<clear-ddos-iso-tcc-aggregate-flows>
clear ddos-protection protocols iso-tcc aggregate states
<clear-ddos-iso-tcc-aggregate-states>
clear ddos-protection protocols iso-tcc aggregate statistics
<clear-ddos-iso-tcc-aggregate-statistics>
clear ddos-protection protocols iso-tcc culprit-flows
<clear-ddos-iso-tcc-flows>
clear ddos-protection protocols iso-tcc states
<clear-ddos-iso-tcc-states>
clear ddos-protection protocols iso-tcc statistics
<clear-ddos-iso-tcc-statistics>
clear ddos-protection protocols jfm
clear ddos-protection protocols jfm aggregate
clear ddos-protection protocols jfm aggregate culprit-flows
clear ddos-protection protocols jfm aggregate states
clear-ddos-jfm-aggregate-states
clear ddos-protection protocols jfm aggregate statistics
clear-ddos-jfm-aggregate-statistics
clear ddos-protection protocols jfm states
clear-ddos-jfm-states
clear ddos-protection protocols jfm statistics
<clear-ddos-jfm-statistics>
clear ddos-protection protocols keepalive
clear ddos-protection protocols keepalive aggregate
clear ddos-protection protocols keepalive aggregate culprit-flows
clear ddos-protection protocols keepalive aggregate states
clear ddos-protection protocols keepalive aggregate statistics
clear ddos-protection protocols keepalive culprit-flows
clear ddos-protection protocols keepalive states
clear ddos-protection protocols keepalive statistics
clear ddos-protection protocols l2pt
clear ddos-protection protocols l2pt aggregate
<clear-ddos-ldp-hello-aggregate-statistics>
clear ddos-protection protocols ldp-hello culprit-flows
<clear-ddos-ldp-hello-flows>
clear ddos-protection protocols ldp-hello states
<clear-ddos-ldp-hello-states>
clear ddos-protection protocols ldp-hello statistics
<clear-ddos-ldp-hello-statistics>
clear-ddos-ldp-statistics
clear-ddos-ldp-statistics
clear-ddos-ldpv6-aggregate-states
clear-ddos-ldpv6-aggregate-states
clear-ddos-ldpv6-aggregate-statistics
clear-ddos-ldpv6-aggregate-statistics
clear-ddos-ldpv6-states
clear-ddos-ldpv6-states
clear-ddos-ldpv6-statistics
clear-ddos-ldpv6-statistics
clear-ddos-lldp-aggregate-states
clear-ddos-lldp-aggregate-states
clear-ddos-lldp-aggregate-statistics
clear-ddos-lldp-aggregate-statistics
clear-ddos-lldp-states
clear-ddos-lldp-states
clear-ddos-lldp-statistics
clear-ddos-lldp-statistics
clear-ddos-lmp-aggregate-states
clear-ddos-lmp-aggregate-states
clear-ddos-lmp-aggregate-statistics
clear-ddos-lmp-aggregate-statistics
clear-ddos-lmp-states
clear-ddos-lmp-states
clear-ddos-lmp-statistics
clear-ddos-lmp-statistics
clear-ddos-lmpv6-aggregate-states
clear-ddos-lmpv6-aggregate-states
clear-ddos-lmpv6-states
clear-ddos-lmpv6-statistics
clear-ddos-mac-host-aggregate-states
clear-ddos-mac-host-aggregate-statistics
clear-ddos-mac-host-states
clear-ddos-mac-host-statistics
clear-ddos-mcast-copy-aggregate-states
clear-ddos-mcast-copy-aggregate-statistics
clear-ddos-mcast-copy-states
clear-ddos-mcast-copy-statistics
clear-ddos-mlp-aggregate-states
clear-ddos-mlp-aggregate-statistics
clear-ddos-mlp-aging-exc-states
clear-ddos-mlp-aging-exc-statistics
clear-ddos-mlp-packets-states
clear-ddos-mlp-packets-statistics
clear-ddos-mlp-states
clear-ddos-mlp-statistics
clear-ddos-mlp-unclass-states
clear-ddos-mlp-unclass-statistics
clear-ddos-msdp-aggregate-states
clear-ddos-msdp-aggregate-statistics
clear-ddos-msdp-states
clear-ddos-msdp-statistics
clear-ddos-msdpv6-aggregate-states
clear-ddos-msdpv6-aggregate-statistics
clear-ddos-msdpv6-states
clear-ddos-msdpv6-statistics
clear ddos-protection protocols multihop-bfd
clear ddos-protection protocols multihop-bfd aggregate
clear ddos-protection protocols multihop-bfd aggregate culprit-flows
<clear-ddos-mhop-bfd-aggregate-flows>
clear ddos-protection protocols multihop-bfd aggregate states
<clear-ddos-mhop-bfd-aggregate-states>
clear ddos-protection protocols multihop-bfd aggregate statistics
<clear-ddos-mhop-bfd-aggregate-statistics>
clear ddos-protection protocols multihop-bfd culprit-flows
<clear-ddos-mhop-bfd-flows>
clear ddos-protection protocols multihop-bfd states
<clear-ddos-mhop-bfd-states>
clear ddos-protection protocols multihop-bfd statistics
<clear-ddos-mhop-bfd-statistics>
clear-ddos-mvrp-aggregate-states
clear-ddos-mvrp-aggregate-statistics
clear-ddos-mvrp-states
clear-ddos-mvrp-statistics
clear-ddos-ntp-aggregate-states
clear-ddos-ntp-aggregate-statistics
clear-ddos-ntp-states
clear-ddos-ntp-statistics
clear-ddos-oam-lfm-aggregate-states
clear-ddos-oam-lfm-aggregate-statistics
clear-ddos-oam-lfm-states
clear-ddos-oam-lfm-statistics
clear-ddos-ospf-aggregate-states
clear-ddos-ospf-aggregate-statistics
clear-ddos-ospf-states
clear-ddos-ospf-statistics
clear-ddos-ospfv3v6-aggregate-states
clear ddos-protection protocols ospfv3v6 aggregate statistics
clear-ddos-ospfv3v6-aggregate-statistics
clear ddos-protection protocols ospfv3v6 states
clear-ddos-ospfv3v6-states
clear ddos-protection protocols pimv6
clear-ddos-pim-statistics
clear ddos-protection protocols pim-ctrl
clear ddos-protection protocols pim-ctrl aggregate
clear ddos-protection protocols pim-ctrl aggregate culprit-flows
<clear-ddos-pim-ctrl-aggregate-flows>
clear ddos-protection protocols pim-ctrl aggregate states
<clear-ddos-pim-ctrl-aggregate-states>
clear ddos-protection protocols pim-ctrl aggregate statistics
<clear-ddos-pim-ctrl-aggregate-statistics>
clear ddos-protection protocols pim-ctrl culprit-flows
<clear-ddos-pim-ctrl-flows>
clear ddos-protection protocols pim-ctrl states
<clear-ddos-pim-ctrl-states>
clear ddos-protection protocols pim-ctrl statistics
<clear-ddos-pim-ctrl-statistics>
clear ddos-protection protocols pim-data
clear ddos-protection protocols pim-data aggregate
clear ddos-protection protocols pim-data aggregate culprit-flows
<clear-ddos-pim-data-aggregate-flows>
clear ddos-protection protocols pim-data aggregate states
<clear-ddos-pim-data-aggregate-states>
clear ddos-protection protocols pim-data aggregate statistics
<clear-ddos-pim-data-aggregate-statistics>
clear-ddos-pmvrp-statistics
clear ddos-protection protocols pos
clear ddos-protection protocols pos aggregate
clear ddos-protection protocols pos aggregate states
clear-ddos-pos-aggregate-states
clear ddos-protection protocols pos aggregate statistics
clear-ddos-pos-aggregate-statistics
clear ddos-protection protocols pos states
clear-ddos-pos-states
clear ddos-protection protocols pos statistics
clear-ddos-pos-statistics
clear ddos-protection protocols ppp
clear ddos-protection protocols ppp aggregate
clear ddos-protection protocols ppp aggregate states
clear-ddos-ppp-aggregate-states
clear ddos-protection protocols ppp aggregate statistics
clear-ddos-ppp-aggregate-statistics
clear ddos-protection protocols ppp authentication
clear ddos-protection protocols ppp authentication states
clear-ddos-ppp-auth-states
clear ddos-protection protocols ppp authentication statistics
clear-ddos-ppp-auth-statistics
clear ddos-protection protocols ppp ipcp
clear ddos-protection protocols ppp ipcp states
clear-ddos-ppp-ipcp-states
clear ddos-protection protocols ppp ipcp statistics
clear-ddos-ppp-ipcp-statistics
clear ddos-protection protocols ppp ipv6cp
clear ddos-protection protocols ppp ipv6cp states
clear-ddos-ppp-ipv6cp-states
clear ddos-protection protocols ppp ipv6cp statistics
clear-ddos-ppp-ipv6cp-statistics
clear ddos-protection protocols ppp isis
clear ddos-protection protocols ppp isis states
clear-ddos-ppp-isis-states
clear ddos-protection protocols ppp isis statistics
clear-ddos-ppp-isis-statistics
clear ddos-protection protocols ppp lcp
clear ddos-protection protocols ppp lcp states
clear-ddos-ppp-lcp-states
clear ddos-protection protocols ppp lcp statistics
clear-ddos-ppp-lcp-statistics
clear ddos-protection protocols ppp mplscp
clear ddos-protection protocols ppp mplscp states
clear-ddos-ppp-mplscp-states
clear ddos-protection protocols ppp mplscp statistics
clear-ddos-ppp-mplscp-statistics
clear ddos-protection protocols ppp states
clear-ddos-ppp-states
clear ddos-protection protocols ppp statistics
clear-ddos-ppp-statistics
clear ddos-protection protocols ppp unclassified
clear ddos-protection protocols ppp unclassified states
clear ddos-protection protocols ppp unclassified statistics
<clear-ddos-ppp-unclass-statistics>
clear ddos-protection protocols pppoe
clear ddos-protection protocols pppoe aggregate
clear ddos-protection protocols pppoe aggregate states
clear-ddos-pppoe-aggregate-states
clear ddos-protection protocols pppoe aggregate statistics
clear-ddos-pppoe-aggregate-statistics
clear-ddos-ppp-ipv6cp-states
clear-ddos-ppp-ipv6cp-statistics
clear-ddos-ppp-isis-states
clear-ddos-ppp-isis-statistics
clear-ddos-ppp-lcp-states
clear-ddos-ppp-lcp-statistics
clear-ddos-ppp-mplscp-states
clear-ddos-ppp-mplscp-statistics
clear-ddos-pppoe-aggregate-states
clear-ddos-pppoe-aggregate-statistics
clear-ddos-pppoe-padi-states
clear-ddos-pppoe-padi-statistics
clear-ddos-pppoe-padm-states
clear-ddos-pppoe-padm-statistics
clear-ddos-pppoe-padn-states
clear-ddos-pppoe-padn-statistics
clear-ddos-pppoe-pado-states
clear-ddos-pppoe-pado-statistics
clear-ddos-pppoe-padr-states
clear-ddos-pppoe-padr-statistics
clear-ddos-pppoe-pads-states
clear-ddos-pppoe-pads-statistics
clear-ddos-pppoe-padt-states
clear-ddos-pppoe-padt-statistics
clear-ddos-pppoe-states
clear-ddos-pppoe-statistics
clear-ddos-ppp-states
clear-ddos-ppp-statistics
clear-ddos-ptp-aggregate-states
clear-ddos-ptp-aggregate-statistics
clear-ddos-ptp-states
clear-ddos-ptp-statistics
clear-ddos-pvstp-aggregate-states
clear-ddos-pvstp-aggregate-statistics
clear-ddos-pvstp-states
clear-ddos-pvstp-statistics
clear-ddos-radius-account-states
clear-ddos-radius-account-statistics
clear-ddos-radius-aggregate-states
clear-ddos-radius-aggregate-statistics
clear-ddos-radius-auth-states
clear ddos-protection protocols radius authorization statistics
clear-ddos-radius-auth-statistics
clear ddos-protection protocols pmvrp culprit-flows
clear ddos-protection protocols radius server
clear ddos-protection protocols radius server states
clear-ddos-radius-server-states
clear ddos-protection protocols radius server statistics
clear-ddos-radius-server-statistics
clear ddos-protection protocols radius states
clear-ddos-radius-states
clear ddos-protection protocols radius statistics
clear-ddos-radius-statistics
clear ddos-protection protocols redirect
clear ddos-protection protocols redirect aggregate
clear ddos-protection protocols redirect aggregate states
clear-ddos-redirect-aggregate-states
clear ddos-protection protocols redirect aggregate statistics
clear-ddos-redirect-aggregate-statistics
clear ddos-protection protocols redirect states
clear-ddos-redirect-states
<clear-ddos-services-BSDT-states>
clear ddos-protection protocols services bsdt statistics
<clear-ddos-services-BSDT-statistics>
clear ddos-protection protocols services culprit-flows
<clear-ddos-services-flows>
clear ddos-protection protocols services packet
clear ddos-protection protocols services packet culprit-flows
<clear-ddos-services-packet-flows>
clear ddos-protection protocols services packet states
<clear-ddos-services-packet-states>
clear ddos-protection protocols services packet statistics
<clear-ddos-services-packet-statistics>
clear ddos-protection protocols services states
clear-ddos-services-states
clear ddos-protection protocols services statistics
clear-ddos-services-statistics
clear ddos-protection protocols snmp
clear ddos-protection protocols snmp aggregate
clear ddos-protection protocols snmp aggregate states
clear-ddos-snmp-aggregate-states
clear ddos-protection protocols snmp aggregate statistics
clear ddos-protection protocols snmp culprit-flows
clear ddos-protection protocols snmp states
clear-ddos-snmp-states
clear ddos-protection protocols snmp statistics
clear-ddos-snmp-statistics
clear ddos-protection protocols snmpv6
clear ddos-protection protocols snmpv6 aggregate
clear ddos-protection protocols snmpv6 aggregate states
clear-ddos-snmpv6-aggregate-states
clear ddos-protection protocols snmpv6 aggregate statistics
clear-ddos-snmpv6-aggregate-statistics
clear ddos-protection protocols snmpv6 states
clear-ddos-snmpv6-states
clear ddos-protection protocols snmpv6 statistics
clear-ddos-snmpv6-statistics
clear ddos-protection protocols ssh
clear ddos-protection protocols ssh aggregate
clear ddos-protection protocols ssh aggregate states
clear-ddos-ssh-aggregate-states
clear ddos-protection protocols ssh aggregate statistics
clear-ddos-ssh-aggregate-statistics
clear ddos-protection protocols ssh states
clear-ddos-ssh-states
clear ddos-protection protocols ssh statistics
clear-ddos-ssh-statistics
clear ddos-protection protocols sshv6
clear ddos-protection protocols sshv6 aggregate
clear ddos-protection protocols sshv6 aggregate states
clear-ddos-sshv6-aggregate-states
clear ddos-protection protocols sshv6 aggregate statistics
clear ddos-protection protocols sshv6 culprit-flows
clear ddos-protection protocols sshv6 states
clear-ddos-sshv6-states
clear ddos-protection protocols sshv6 statistics
clear-ddos-sshv6-statistics
clear ddos-protection protocols states
clear-ddos-protocols-states
clear ddos-protection protocols statistics
clear-ddos-protocols-statistics
clear ddos-protection protocols stp
<clear-ddos-re-services-captive-portal-flows>
clear ddos-protection protocols re-services captive-portal states
<clear-ddos-re-services-captive-portal-states>
clear ddos-protection protocols re-services captive-portal statistics
<clear-ddos-re-services-captive-portal-statistics>
clear ddos-protection protocols re-services culprit-flows
<clear-ddos-re-services-flows>
clear ddos-protection protocols re-services states
<clear-ddos-re-services-states>
clear ddos-protection protocols re-services statistics
<clear-ddos-re-services-statistics>
clear ddos-protection protocols re-services-v6
clear ddos-protection protocols re-services-v6 aggregate
clear ddos-protection protocols re-services-v6 aggregate culprit-flows
<clear-ddos-re-services-v6-aggregate-flows>
clear ddos-protection protocols re-services-v6 aggregate states
<clear-ddos-re-services-v6-aggregate-states>
clear ddos-protection protocols re-services-v6 aggregate statistics
<clear-ddos-re-services-v6-aggregate-statistics>
clear ddos-protection protocols re-services-v6 captive-portal
clear ddos-protection protocols re-services-v6 captive-portal culprit-flows
<clear-ddos-re-services-v6-captive-portal-v6-flows>
clear ddos-protection protocols re-services-v6 captive-portal states
<clear-ddos-re-services-v6-captive-portal-v6-states>
clear ddos-protection protocols re-services-v6 captive-portal statistics
<clear-ddos-re-services-v6-captive-portal-v6-statistics>
clear ddos-protection protocols re-services-v6 culprit-flows
<clear-ddos-re-services-v6-flows>
clear ddos-protection protocols re-services-v6 states
<clear-ddos-re-services-v6-states>
clear ddos-protection protocols re-services-v6 statistics
<clear-ddos-re-services-v6-statistics>
clear-ddos-redirect-aggregate-states
clear-ddos-redirect-states
clear-ddos-redirect-statistics
clear-ddos-rip-aggregate-states
clear-ddos-rip-aggregate-statistics
clear-ddos-rip-states
clear-ddos-rip-statistics
clear-ddos-ripv6-aggregate-states
clear-ddos-ripv6-aggregate-statistics
clear-ddos-ripv6-states
clear-ddos-ripv6-statistics
clear-ddos-rsvp-aggregate-states
clear-ddos-rsvp-aggregate-statistics
clear-ddos-rsvp-states
clear-ddos-rsvp-statistics
clear-ddos-rsvpv6-aggregate-states
clear-ddos-rsvpv6-aggregate-statistics
clear-ddos-rsvpv6-states
clear-ddos-rsvpv6-statistics
clear-ddos-services-aggregate-states
clear-ddos-services-aggregate-statistics
clear-ddos-services-states
clear-ddos-services-statistics
clear-ddos-snmp-aggregate-states
clear-ddos-snmp-aggregate-statistics
clear-ddos-snmp-states
clear-ddos-snmp-statistics
clear-ddos-snmpv6-aggregate-states
clear-ddos-snmpv6-aggregate-statistics
clear-ddos-snmpv6-states
clear-ddos-snmpv6-statistics
clear-ddos-ssh-aggregate-states
clear-ddos-ssh-aggregate-statistics
clear-ddos-ssh-states
clear-ddos-ssh-statistics
clear-ddos-sshv6-aggregate-states
clear-ddos-sshv6-aggregate-statistics
clear-ddos-sshv6-states
clear-ddos-sshv6-statistics
clear-ddos-stp-aggregate-states
clear-ddos-stp-aggregate-statistics
clear-ddos-stp-states
clear-ddos-stp-statistics
clear ddos-protection protocols syslog
clear ddos-protection protocols syslog aggregate
clear ddos-protection protocols syslog aggregate culprit-flows
<clear-ddos-syslog-aggregate-flows>
clear ddos-protection protocols syslog aggregate states
<clear-ddos-syslog-aggregate-states>
clear ddos-protection protocols syslog aggregate statistics
<clear-ddos-syslog-aggregate-statistics>
clear ddos-protection protocols syslog culprit-flows
<clear-ddos-syslog-flows>
clear ddos-protection protocols syslog states
<clear-ddos-syslog-states>
clear ddos-protection protocols syslog statistics
<clear-ddos-syslog-statistics>
clear-ddos-tacacs-aggregate-states
clear-ddos-tacacs-aggregate-statistics
clear-ddos-tacacs-states
clear-ddos-tacacs-statistics
clear-ddos-tcp-flags-aggregate-states
clear-ddos-tcp-flags-aggregate-statistics
clear-ddos-tcp-flags-establish-states
clear-ddos-tcp-flags-establish-statistics
clear-ddos-tcp-flags-initial-states
clear-ddos-tcp-flags-initial-statistics
clear-ddos-tcp-flags-states
clear-ddos-tcp-flags-statistics
clear-ddos-tcp-flags-unclass-states
clear-ddos-tcp-flags-unclass-statistics
clear-ddos-telnet-aggregate-states
clear-ddos-telnet-aggregate-statistics
clear-ddos-telnet-states
clear-ddos-telnet-statistics
clear-ddos-telnetv6-aggregate-states
clear-ddos-telnetv6-aggregate-statistics
clear-ddos-telnetv6-states
clear-ddos-telnetv6-statistics
clear-ddos-ttl-aggregate-states
clear-ddos-ttl-aggregate-statistics
clear-ddos-ttl-states
clear-ddos-ttl-statistics
clear-ddos-tun-frag-aggregate-states
clear-ddos-tun-frag-aggregate-statistics
clear-ddos-tun-frag-states
clear-ddos-tun-frag-statistics
clear ddos-protection protocols tunnel-ka
clear ddos-protection protocols tunnel-ka aggregate
clear ddos-protection protocols tunnel-ka aggregate culprit-flows
<clear-ddos-tunnel-ka-aggregate-flows>
clear ddos-protection protocols tunnel-ka aggregate states
<clear-ddos-tunnel-ka-aggregate-states>
clear ddos-protection protocols tunnel-ka aggregate statistics
<clear-ddos-tunnel-ka-aggregate-statistics>
clear ddos-protection protocols tunnel-ka culprit-flows
<clear-ddos-tunnel-ka-flows>
clear ddos-protection protocols tunnel-ka states
<clear-ddos-tunnel-ka-states>
clear ddos-protection protocols tunnel-ka statistics
<clear-ddos-tunnel-ka-statistics>
clear-ddos-vchassis-aggregate-states
clear ddos-protection protocols virtual-chassis aggregate statistics
clear-ddos-vchassis-aggregate-statistics
clear ddos-protection protocols virtual-chassis control-high
clear ddos-protection protocols virtual-chassis control-high states
clear-ddos-vchassis-control-hi-states
clear ddos-protection protocols virtual-chassis control-high statistics
clear-ddos-vchassis-control-hi-statistics
clear ddos-protection protocols virtual-chassis control-low
clear ddos-protection protocols virtual-chassis control-low states
clear-ddos-vchassis-control-lo-states
clear ddos-protection protocols virtual-chassis control-low statistics
clear-ddos-vchassis-control-lo-statistics
clear ddos-protection protocols virtual-chassis states
clear-ddos-vchassis-states
clear ddos-protection protocols virtual-chassis statistics
clear-ddos-vchassis-statistics
clear ddos-protection protocols virtual-chassis unclassified
clear ddos-protection protocols virtual-chassis unclassified culprit-flows
clear ddos-protection protocols virtual-chassis unclassified states
clear-ddos-vchassis-unclass-states
clear ddos-protection protocols virtual-chassis unclassified statistics
clear-ddos-vchassis-unclass-statistics
clear ddos-protection protocols virtual-chassis vc-packets
clear ddos-protection protocols virtual-chassis vc-packets states
clear-ddos-vchassis-vc-packets-states
clear ddos-protection protocols virtual-chassis vc-packets statistics
clear-ddos-vchassis-vc-packets-statistics
clear ddos-protection protocols virtual-chassis vc-ttl-errors
clear ddos-protection protocols virtual-chassis vc-ttl-errors states
clear-ddos-vchassis-vc-ttl-err-states
clear ddos-protection protocols virtual-chassis vc-ttl-errors statistics
clear-ddos-vchassis-vc-ttl-err-statistics
clear ddos-protection protocols vrrp
clear ddos-protection protocols vrrp aggregate
clear ddos-protection protocols vrrp aggregate states
clear-ddos-vrrp-aggregate-states
clear ddos-protection protocols vrrp aggregate statistics
clear ddos-protection protocols vrrp culprit-flows
clear ddos-protection protocols vrrp statistics
clear-ddos-vrrp-statistics
clear ddos-protection protocols vrrpv6
clear ddos-protection protocols vrrpv6 aggregate
clear ddos-protection protocols vrrpv6 aggregate states
clear-ddos-vrrpv6-aggregate-states
clear ddos-protection protocols vrrpv6 aggregate statistics
clear-ddos-vrrpv6-aggregate-statistics
clear ddos-protection protocols vrrpv6 states
clear-ddos-vrrpv6-states
clear ddos-protection protocols vrrpv6 statistics
clear-ddos-uncls-host-rt-v4-flows
clear-ddos-vchassis-aggregate-statistics
clear-ddos-vchassis-control-hi-states
clear-ddos-vchassis-control-hi-statistics
clear-ddos-vchassis-control-lo-states
clear-ddos-vchassis-control-lo-statistics
clear-ddos-vchassis-states
clear-ddos-vchassis-statistics
clear-ddos-vchassis-unclass-states
clear-ddos-vchassis-unclass-statistics
clear-ddos-vchassis-vc-packets-states
clear-ddos-vchassis-vc-packets-statistics
clear-ddos-vchassis-vc-ttl-err-states
clear-ddos-vchassis-vc-ttl-err-statistics
clear-ddos-vrrp-aggregate-states
clear-ddos-vrrp-aggregate-statistics
clear-ddos-vrrp-states
clear-ddos-vrrp-statistics
clear-ddos-vrrpv6-aggregate-states
clear-ddos-vrrpv6-aggregate-statistics
clear-ddos-vrrpv6-states
clear-ddos-vrrpv6-statistics
clear ddos-protection protocols vxlan
clear ddos-protection protocols vxlan aggregate
clear ddos-protection protocols vxlan aggregate culprit-flows
clear-ddos-vxlan-aggregate-flows
clear ddos-protection protocols vxlan aggregate states
<clear-ddos-vxlan-aggregate-states>
clear ddos-protection protocols vxlan aggregate statistics
<clear-ddos-vxlan-aggregate-statistics>
clear ddos-protection protocols vxlan culprit-flows
<clear-ddos-vxlan-flows>
clear ddos-protection protocols vxlan states
<clear-ddos-vxlan-states>
clear ddos-protection protocols vxlan statistics
<clear-ddos-vxlan-statistics>
clear dhcp
clear dhcp client
clear dhcp client binding
<clear-dhcp-client-binding-information>
clear dhcp client statistics
<clear-client-statistics-information>
clear dhcp proxy-client
clear dhcp proxy-client statistics
clear dhcp relay
clear dhcp relay binding
<clear-dhcp-relay-binding-information>
clear dhcp relay binding interface
<clear-dhcp-interface-bindings>
clear dhcp relay statistics
<clear-dhcp-relay-statistics-information>
<clear-dhcp-security-binding>
<clear-dhcp-security-binding-interface>
<clear-dhcp-security-binding-ip-address>
<clear-dhcp-security-binding-statistics>
<clear-dhcp-security-binding-vlan>
clear dhcp relay statistics bulk-leasequery-connections
<clear-dhcp-relay-bulk-leasequery-conn-statistics>
clear dhcp relay statistics leasequery
<clear-dhcp-relay-leasequery-statistics>
clear dhcp server
<clear-subscriber-management-statistics>
clear dot1x
clear dot1x eapol-block
clear dot1x eapol-block interface
<clear-dot1x-eapol-block-interface-session>
clear dot1x eapol-block mac-address
<clear-dot1x-eapol-block-mac-session>
clear dot1x firewall
<clear-dot1x-firewall>
clear dot1x firewall interface
<clear-dot1x-firewall-interface>
clear dot1x interface
<clear-dot1x-interface-session>
clear dot1x mac-address
<clear-dot1x-mac-session>
clear dot1x statistics
<clear-dot1x-statistics>
clear dot1x statistics interface
<clear-dot1x-statistics-interface>
clear error
clear error bpdu
clear error bpdu interface
<clear-bpdu-error>
clear error loop-detect
clear error loop-detect interface
<clear-loop-detect-error>
clear error mac-rewrite
clear error mac-rewrite interface
<clear-mac-rewrite-error>
clear esis
clear esis adjacency
<clear-esis-adjacency>
clear esis statistics
<clear-esis-statistics>
clear ethernet-switching
clear ethernet-switching evpn
clear ethernet-switching evpn arp-table
<clear-ethernet-switching-evpn-arp-table>
clear ethernet-switching mac-learning-log
<clear-ethernet-switching-mac-learning-log>
clear ethernet-switching recovery-timeout
<clear-ethernet-switching-recovery>
clear ethernet-switching recovery-timeout interface
<clear-ethernet-switching-recovery-interface>
clear ethernet-switching satellite
clear ethernet-switching satellite logging
<clear-satellite-control-logging>
clear ethernet-switching satellite vlan-auto-sense
<clear-satellite-control-plane-vlan-auto-sense>
clear ethernet-switching table
<clear-ethernet-switching-table>
clear ethernet-switching table interface
<clear-ethernet-switching-interface-table>
clear ethernet-switching table persistent-learning
<clear-ethernet-switching-table-persistent-learning>
clear ethernet-switching table persistent-learning interface
<clear-ethernet-switching-table-persistent-learning>
clear ethernet-switching table persistent-learning mac
<clear-ethernet-switching-table-persistent-learning-mac>
clear evpn
clear evpn arp-table
<clear-evpn-arp-table>
clear evpn mac-table
<clear-evpn-mac-table>
clear evpn mac-table interface
<clear-evpn-interface-mac-table>
clear evpn nd-table
<clear-evpn-nd-table>
clear extensible-subscriber-services
clear extensible-subscriber-services counters
<clear-extensible-subscriber-services-counters>
clear extensible-subscriber-services sessions
<clear-extensible-subscriber-services-sessions>
clear fabric
<clear-fabric>
clear fabric statistics
<clear-fabric-statistics>
clear firewall
<clear-firewall-counters>
clear firewall all
<clear-all-firewall-conters>
clear firewall log
<clear-firewall-log>
clear firewall policer
clear firewall policer counter
clear firewall policer counter all
<clear-interface-aggregate-fwd-options>
<clear-interface-aggregate-fwd-options-all>
clear helper
clear helper statistics
<clear-helper-statistics-information>
clear igmp
clear igmp membership
<clear-igmp-membership>
clear igmp snooping
clear igmp snooping membership
<clear-igmp-snooping-membership>
clear igmp snooping membership bridge-domain
<clear-igmp-snooping-bridge-domain-membership>
clear igmp snooping membership vlan
<clear-igmp-snooping-vlan-membership>
clear igmp snooping statistics
<clear-igmp-snooping-statistics>
clear igmp snooping statistics bridge-domain
<clear-igmp-snooping-bridge-domain-statistics>
clear igmp snooping statistics vlan
<clear-igmp-snooping-vlan-statistics>
clear igmp statistics
<clear-igmp-statistics>
clear ike
clear ike security-associations
<clear-ike-security-associations>
clear ike statistics
<clear-ike-statistics>
clear ilmi
clear ilmi statistics
<clear-ilmi-statistics>
clear interfaces
clear interfaces interface-set
clear interfaces interface-set statistics
<clear-interface-set-statistics>
clear interfaces interface-set statistics all
<clear-interface-set-statistics-all>
clear interfaces interval
<clear-interfaces-interval>
clear interfaces mac-database
<clear-interfaces-mac-database>
clear interfaces mac-database statistics
<clear-interface-mac-database-statistics>
clear interfaces mac-database statistics all
<clear-interface-mac-database-statistics-all>
clear interfaces statistics
<clear-interfaces-statistics>
clear interfaces statistics all
<clear-interfaces-statistics-all>
clear interfaces transport
<clear-interface-transport-information>
clear interfaces transport optics
<clear-interface-transport-optics-information>
clear interfaces transport optics interval
<clear-interface-transport-optics-interval-information>
clear ipsec
clear ipsec security-associations
<clear-ipsec-security-associations>
clear ipv6
clear ipv6 neighbors
<clear-ipv6-nd-information>
clear ipv6 neighbors all
<clear-ipv6-all-neighbors>
clear isis
clear isis adjacency
<clear-isis-adjacency-information>
clear isis database
<clear-isis-database-information>
clear isis layer2-map
<clear-isis-layer2-map-information>
clear isis overload
<clear-isis-overload-information>
clear isis statistics
<clear-isis-statistics-information>
clear ipv6 router-advertisement
clear lacp
clear lacp statistics
clear l2-learning
clear l2-learning evpn
clear l2-learning evpn arp-statistics
<clear-evpn-arp-statistics>
clear l2-learning evpn arp-statistics interface
<clear-evpn-arp-statistics-interface>
clear l2-learning evpn nd-statistics
<clear-evpn-nd-statistics>
clear l2-learning evpn nd-statistics interface
<clear-evpn-nd-statistics-interface>
clear l2-learning mac-move-buffer
<clear-l2-learning-mac-move-buffer>
clear l2-learning mac-move-buffer active
<clear-l2-learning-mac-move-buffer-active>
clear-l2-learning-redundancy-group
<clear-l2-learning-redundancy-group-statistics>
clear l2-learning remote-backbone-edge-bridges
<clear-l2-learning-remote-backbone-edge-bridges>
clear l2circuit
clear ldp
<clear-cfm-loss-statistics>
clear oam ethernet connectivity-fault-management path-database
<clear-cfm-linktrace-path-database>
clear oam ethernet connectivity-fault-management policer
<clear-cfm-policer-statistics>
clear oam ethernet connectivity-fault-management sla-iterator-history
<clear-cfm-iterator-history>
clear oam ethernet connectivity-fault-management sla-iterator-statistics
<clear-cfm-iterator-statistics>
clear oam ethernet connectivity-fault-management statistics
<clear-cfm-statistics>
clear oam ethernet connectivity-fault-management synthetic-loss-statistics
<clear-cfm-slm-statistics>
clear oam ethernet link-fault-management
clear oam ethernet link-fault-management state
<clear-lfmd-state>
clear oam ethernet link-fault-management statistics
<clear-lfmd-statistics>
clear oam ethernet link-fault-management statistics action-profile
<clear-lfmd-action-profile-statistics>
clear oam ethernet lmi
clear oam ethernet lmi statistics
<clear-elmi-statistics>
clear ospf
clear ospf database
<clear-ospf-database-information>
clear ospf database-protection
<clear-ospf-database-protection>
clear ospf io-statistics
<clear-ospf-io-statistics-information>
clear ospf neighbor
<clear-ospf-neighbor-information>
clear ospf overload
<clear-ospf-overload-information>
clear ospf statistics
<clear-ospf-statistics-information>
clear ospf3
clear ospf3 database
<clear-ospf3-database-information>
clear ospf3 database-protection
<clear-ospf-database-protection>
clear ospf3 io-statistics
<clear-ospf3-io-statistics-information>
clear ospf3 neighbor
<clear-ospf3-neighbor-information>
clear ospf3 overload
<clear-ospf3-overload-information>
clear ospf3 statistics
<clear-ospf3-io-statistics-information>
clear ovsdb
clear ovsdb commit
clear ovsdb commit failures
<clear-ovsdb-commit-failure-information>
clear ovsdb statistics
clear ovsdb statistics interface
clear ovsdb statistics interface all
<clear-ovsdb-interfaces-statistics-all>
clear performance-monitoring
clear performance-monitoring mpls
clear performance-monitoring mpls lsp
<clear-pm-mpls-lsp-information>
clear pfe
clear pfe statistics
clear pfe statistics fabric
clear pfe statistics traffic detail
clear pfe statistics traffic egress-queues fpc
clear pfe statistics traffic multicast
clear pfe statistics traffic multicast fpc
clear pfe tcam-errors
clear pfe tcam-errors all-tcam-stages
<clear-pfe-tcam-errors-all-tcam-stages>
clear pfe tcam-errors app
<clear-pfe-tcam-errors-app>
clear pfe tcam-errors app bd-dtag-validate
<clear-pfe-tcam-errors-app-bd-dtag-validate>
clear pfe tcam-errors app bd-dtag-validate detail
clear pfe tcam-errors app bd-dtag-validate list-related-apps
clear pfe tcam-errors app bd-dtag-validate list-shared-apps
clear pfe tcam-errors app bd-dtag-validate shared-usage
clear pfe tcam-errors app bd-dtag-validate shared-usage detail
clear pfe tcam-errors app bd-tpid-swap
<clear-pfe-tcam-errors-app-bd-tpid-swap>
clear pfe tcam-errors app bd-tpid-swap detail
clear pfe tcam-errors app bd-tpid-swap list-related-apps
clear pfe tcam-errors app bd-tpid-swap list-shared-apps
clear pfe tcam-errors app bd-tpid-swap shared-usage
clear pfe tcam-errors app bd-tpid-swap shared-usage detail
clear pfe tcam-errors app cfm-bd-filter
<clear-pfe-tcam-errors-app-cfm-bd-filter>
clear pfe tcam-errors app cfm-bd-filter detail
clear pfe tcam-errors app cfm-bd-filter list-related-apps
clear pfe tcam-errors app cfm-bd-filter list-shared-apps
clear pfe tcam-errors app cfm-bd-filter shared-usage
clear pfe tcam-errors app cfm-bd-filter shared-usage detail
clear pfe tcam-errors app cfm-filter
<clear-pfe-tcam-errors-app-cfm-filter>
clear pfe tcam-errors app cfm-filter detail
clear pfe tcam-errors app cfm-filter list-related-apps
clear pfe tcam-errors app cfm-filter list-shared-apps
clear pfe tcam-errors app cfm-filter shared-usage
clear pfe tcam-errors app cfm-filter shared-usage detail
clear pfe tcam-errors app cfm-vpls-filter
<clear-pfe-tcam-errors-app-cfm-vpls-filter>
clear pfe tcam-errors app cfm-vpls-filter detail
clear pfe tcam-errors app cfm-vpls-filter list-related-apps
clear pfe tcam-errors app cfm-vpls-filter list-shared-apps
clear pfe tcam-errors app cfm-vpls-filter shared-usage
clear pfe tcam-errors app cfm-vpls-filter shared-usage detail
clear pfe tcam-errors app cfm-vpls-ifl-filter
<clear-pfe-tcam-errors-app-cfm-vpls-ifl-filter>
clear pfe tcam-errors app cfm-vpls-ifl-filter detail
clear pfe tcam-errors app cfm-vpls-ifl-filter list-related-apps
clear pfe tcam-errors app cfm-vpls-ifl-filter list-shared-apps
clear pfe tcam-errors app cfm-vpls-ifl-filter shared-usage
clear pfe tcam-errors app cfm-vpls-ifl-filter shared-usage detail
clear pfe tcam-errors app cos-fc
<clear-pfe-tcam-errors-app-cos-fc>
clear pfe tcam-errors app cos-fc detail
clear pfe tcam-errors app cos-fc list-related-apps
clear pfe tcam-errors app cos-fc list-shared-apps
clear pfe tcam-errors app cos-fc shared-usage
clear pfe tcam-errors app cos-fc shared-usage detail
<clear-pfe-tcam-errors-app-ip-mac-val>
clear pfe tcam-errors app ip-mac-val detail
clear pfe tcam-errors app ip-mac-val list-related-apps
clear pfe tcam-errors app ip-mac-val list-shared-apps
clear pfe tcam-errors app ip-mac-val shared-usage
clear pfe tcam-errors app ip-mac-val shared-usage detail
clear pfe tcam-errors app ip-mac-val-bcast
<clear-pfe-tcam-errors-app-ip-mac-val-bcast>
clear pfe tcam-errors app ip-mac-val-bcast detail
clear pfe tcam-errors app ip-mac-val-bcast list-related-apps
clear pfe tcam-errors app ip-mac-val-bcast list-shared-apps
clear pfe tcam-errors app ip-mac-val-bcast shared-usage
clear pfe tcam-errors app ip-mac-val-bcast shared-usage detail
clear pfe tcam-errors app ipsec-reverse-fil
<clear-pfe-tcam-errors-app-ipsec-reverse-fil>
clear pfe tcam-errors app ipsec-reverse-fil detail
clear pfe tcam-errors app ipsec-reverse-fil list-related-apps
clear pfe tcam-errors app ipsec-reverse-fil list-shared-apps
clear pfe tcam-errors app ipsec-reverse-fil shared-usage
clear pfe tcam-errors app ipsec-reverse-fil shared-usage detail
clear pfe tcam-errors app irb-cos-rw
<clear-pfe-tcam-errors-app-irb-cos-rw>
clear pfe tcam-errors app irb-cos-rw detail
clear pfe tcam-errors app irb-cos-rw list-related-apps
clear pfe tcam-errors app irb-cos-rw list-shared-apps
clear pfe tcam-errors app irb-cos-rw shared-usage
clear pfe tcam-errors app irb-cos-rw shared-usage detail
clear pfe tcam-errors app irb-fixed-cos
<clear-pfe-tcam-errors-app-irb-fixed-cos>
clear pfe tcam-errors app irb-fixed-cos detail
clear pfe tcam-errors app irb-fixed-cos list-related-apps
clear pfe tcam-errors app irb-fixed-cos list-shared-apps
clear pfe tcam-errors app irb-fixed-cos shared-usage
clear pfe tcam-errors app irb-fixed-cos shared-usage detail
clear pfe tcam-errors app irb-inet6-fil
<clear-pfe-tcam-errors-app-irb-inet6-fil>
clear pfe tcam-errors app irb-inet6-fil detail
clear pfe tcam-errors app irb-inet6-fil list-related-apps
clear pfe tcam-errors app irb-inet6-fil list-shared-apps
clear pfe tcam-errors app irb-inet6-fil shared-usage
clear pfe tcam-errors app irb-inet6-fil shared-usage detail
clear pfe tcam-errors app lfm-802.3ah-in
<clear-pfe-tcam-errors-app-lfm-802.3ah-in>
clear pfe tcam-errors app lfm-802.3ah-in detail
clear pfe tcam-errors app lfm-802.3ah-in list-related-apps
clear pfe tcam-errors app lfm-802.3ah-in list-shared-apps
clear pfe tcam-errors app lfm-802.3ah-in shared-usage
clear pfe tcam-errors app lfm-802.3ah-in shared-usage detail
clear pfe tcam-errors app lfm-802.3ah-out
<clear-pfe-tcam-errors-app-lfm-802.3ah-out>
clear pfe tcam-errors app lfm-802.3ah-out detail
clear pfe tcam-errors app lfm-802.3ah-out list-related-apps
clear pfe tcam-errors app lfm-802.3ah-out list-shared-apps
clear pfe tcam-errors app lfm-802.3ah-out shared-usage
clear pfe tcam-errors app lfm-802.3ah-out shared-usage detail
clear pfe tcam-errors app lo0-inet-fil
<clear-pfe-tcam-errors-app-lo0-inet-fil>
clear pfe tcam-errors app lo0-inet-fil detail
clear pfe tcam-errors app lo0-inet-fil list-related-apps
clear pfe tcam-errors app lo0-inet-fil list-shared-apps
clear pfe tcam-errors app lo0-inet-fil shared-usage
detail
clear pfe tcam-errors tcam-stage egress app irb-cos-rw
<clear-pfe-tcam-errors-egress-app-irb-cos-rw>
clear pfe tcam-errors tcam-stage egress app irb-cos-rw detail
clear pfe tcam-errors tcam-stage egress app irb-cos-rw list-related-apps
clear pfe tcam-errors tcam-stage egress app irb-cos-rw list-shared-apps
clear pfe tcam-errors tcam-stage egress app irb-cos-rw shared-usage
clear pfe tcam-errors tcam-stage egress app irb-cos-rw shared-usage detail
clear pfe tcam-errors tcam-stage egress app lfm-802.3ah-out
<clear-pfe-tcam-errors-egress-app-lfm-802.3ah-out>
clear pfe tcam-errors tcam-stage egress app lfm-802.3ah-out detail
clear pfe tcam-errors tcam-stage egress app lfm-802.3ah-out list-related-apps
clear pfe tcam-errors tcam-stage egress app lfm-802.3ah-out list-shared-apps
clear pfe tcam-errors tcam-stage egress app lfm-802.3ah-out shared-usage
clear pfe tcam-errors tcam-stage egress app lfm-802.3ah-out shared-usage detail
clear pfe tcam-errors tcam-stage egress app ptpoe-cos-rw
<clear-pfe-tcam-errors-egress-app-ptpoe-cos-rw>
clear pfe tcam-errors tcam-stage egress app ptpoe-cos-rw detail
clear pfe tcam-errors tcam-stage egress app ptpoe-cos-rw list-related-apps
clear pfe tcam-errors tcam-stage egress app ptpoe-cos-rw list-shared-apps
clear pfe tcam-errors tcam-stage egress app ptpoe-cos-rw shared-usage
clear pfe tcam-errors tcam-stage egress app ptpoe-cos-rw shared-usage detail
clear pfe tcam-errors tcam-stage egress app rfc2544-layer2-out
<clear-pfe-tcam-errors-egress-app-rfc2544-layer2-out>
clear pfe tcam-errors tcam-stage egress app rfc2544-layer2-out detail
clear pfe tcam-errors tcam-stage egress app rfc2544-layer2-out list-related-apps
clear pfe tcam-errors tcam-stage egress app rfc2544-layer2-out list-shared-apps
clear pfe tcam-errors tcam-stage egress app rfc2544-layer2-out shared-usage
clear pfe tcam-errors tcam-stage egress app rfc2544-layer2-out shared-usage
detail
clear pfe tcam-errors tcam-stage ingress
<clear-pfe-tcam-errors-ingress-tcam-stage>
clear pfe tcam-errors tcam-stage ingress app
<clear-pfe-tcam-errors-ingress-app>
clear pfe tcam-errors tcam-stage ingress app cfm-bd-filter
<clear-pfe-tcam-errors-ingress-app-cfm-bd-filter>
clear pfe tcam-errors tcam-stage ingress app cfm-bd-filter detail
clear pfe tcam-errors tcam-stage ingress app cfm-bd-filter list-related-apps
clear pfe tcam-errors tcam-stage ingress app cfm-bd-filter list-shared-apps
clear pfe tcam-errors tcam-stage ingress app cfm-bd-filter shared-usage
clear pfe tcam-errors tcam-stage ingress app cfm-bd-filter shared-usage detail
clear pfe tcam-errors tcam-stage ingress app cfm-filter
<clear-pfe-tcam-errors-ingress-app-cfm-filter>
clear pfe tcam-errors tcam-stage ingress app cfm-filter detail
clear pfe tcam-errors tcam-stage ingress app cfm-filter list-related-apps
clear pfe tcam-errors tcam-stage ingress app cfm-filter list-shared-apps
clear pfe tcam-errors tcam-stage ingress app cfm-filter shared-usage
clear pfe tcam-errors tcam-stage ingress app cfm-filter shared-usage detail
clear pfe tcam-errors tcam-stage ingress app cfm-vpls-filter
<clear-pfe-tcam-errors-ingress-app-cfm-vpls-filter>
clear pfe tcam-errors tcam-stage ingress app cfm-vpls-filter detail
clear pfe tcam-errors tcam-stage ingress app cfm-vpls-filter list-related-apps
clear pfe tcam-errors tcam-stage ingress app cfm-vpls-filter list-shared-apps
clear pfe tcam-errors tcam-stage ingress app cfm-vpls-filter shared-usage
clear pfe tcam-errors tcam-stage ingress app cfm-vpls-filter shared-usage
detail
clear pfe tcam-errors tcam-stage ingress app cfm-vpls-ifl-filter
<clear-pfe-tcam-errors-ingress-app-cfm-vpls-ifl-filter>
clear pfe tcam-errors tcam-stage ingress app cfm-vpls-ifl-filter detail
clear pfe tcam-errors tcam-stage ingress app cfm-vpls-ifl-filter
list-related-apps
detail
clear pfe tcam-errors tcam-stage ingress app ipsec-reverse-fil
<clear-pfe-tcam-errors-ingress-app-ipsec-reverse-fil>
clear pfe tcam-errors tcam-stage ingress app ipsec-reverse-fil detail
clear pfe tcam-errors tcam-stage ingress app ipsec-reverse-fil list-related-apps
clear pfe tcam-errors tcam-stage ingress app ipsec-reverse-fil list-shared-apps
clear pfe tcam-errors tcam-stage ingress app ipsec-reverse-fil shared-usage
clear pfe tcam-errors tcam-stage ingress app ipsec-reverse-fil shared-usage
detail
clear pfe tcam-errors tcam-stage ingress app irb-fixed-cos
<clear-pfe-tcam-errors-ingress-app-irb-fixed-cos>
clear pfe tcam-errors tcam-stage ingress app irb-fixed-cos detail
clear pfe tcam-errors tcam-stage ingress app irb-fixed-cos list-related-apps
clear pfe tcam-errors tcam-stage ingress app irb-fixed-cos list-shared-apps
clear pfe tcam-errors tcam-stage ingress app irb-fixed-cos shared-usage
clear pfe tcam-errors tcam-stage ingress app irb-fixed-cos shared-usage detail
clear pfe tcam-errors tcam-stage ingress app irb-inet6-fil
<clear-pfe-tcam-errors-ingress-app-irb-inet6-fil>
clear pfe tcam-errors tcam-stage ingress app irb-inet6-fil detail
clear pfe tcam-errors tcam-stage ingress app irb-inet6-fil list-related-apps
clear pfe tcam-errors tcam-stage ingress app irb-inet6-fil list-shared-apps
clear pfe tcam-errors tcam-stage ingress app irb-inet6-fil shared-usage
clear pfe tcam-errors tcam-stage ingress app irb-inet6-fil shared-usage detail
clear pfe tcam-errors tcam-stage ingress app lfm-802.3ah-in
<clear-pfe-tcam-errors-ingress-app-lfm-802.3ah-in>
clear pfe tcam-errors tcam-stage ingress app lfm-802.3ah-in detail
clear pfe tcam-errors tcam-stage ingress app lfm-802.3ah-in list-related-apps
clear pfe tcam-errors tcam-stage ingress app lfm-802.3ah-in list-shared-apps
clear pfe tcam-errors tcam-stage ingress app lfm-802.3ah-in shared-usage
clear pfe tcam-errors tcam-stage ingress app lfm-802.3ah-in shared-usage detail
clear pfe tcam-errors tcam-stage ingress app lo0-inet-fil
<clear-pfe-tcam-errors-ingress-app-lo0-inet-fil>
clear pfe tcam-errors tcam-stage ingress app lo0-inet-fil detail
clear pfe tcam-errors tcam-stage ingress app lo0-inet-fil list-related-apps
clear pfe tcam-errors tcam-stage ingress app lo0-inet-fil list-shared-apps
clear pfe tcam-errors tcam-stage ingress app lo0-inet-fil shared-usage
clear pfe tcam-errors tcam-stage ingress app lo0-inet-fil shared-usage detail
clear pfe tcam-errors tcam-stage ingress app lo0-inet6-fil
<clear-pfe-tcam-errors-ingress-app-lo0-inet6-fil>
clear pfe tcam-errors tcam-stage ingress app lo0-inet6-fil detail
clear pfe tcam-errors tcam-stage ingress app lo0-inet6-fil list-related-apps
clear pfe tcam-errors tcam-stage ingress app lo0-inet6-fil list-shared-apps
clear pfe tcam-errors tcam-stage ingress app lo0-inet6-fil shared-usage
clear pfe tcam-errors tcam-stage ingress app lo0-inet6-fil shared-usage detail
clear pfe tcam-errors tcam-stage ingress app mac-drop-cnt
<clear-pfe-tcam-errors-ingress-app-mac-drop-cnt>
clear pfe tcam-errors tcam-stage ingress app mac-drop-cnt detail
clear pfe tcam-errors tcam-stage ingress app mac-drop-cnt list-related-apps
clear pfe tcam-errors tcam-stage ingress app mac-drop-cnt list-shared-apps
clear pfe tcam-errors tcam-stage ingress app mac-drop-cnt shared-usage
clear pfe tcam-errors tcam-stage ingress app mac-drop-cnt shared-usage detail
clear pfe tcam-errors tcam-stage ingress app mrouter-port-in
<clear-pfe-tcam-errors-ingress-app-mrouter-port-in>
clear pfe tcam-errors tcam-stage ingress app mrouter-port-in detail
clear pfe tcam-errors tcam-stage ingress app mrouter-port-in list-related-apps
clear pfe tcam-errors tcam-stage ingress app mrouter-port-in list-shared-apps
clear pfe tcam-errors tcam-stage ingress app mrouter-port-in shared-usage
clear pfe tcam-errors tcam-stage ingress app mrouter-port-in shared-usage
detail
clear pfe tcam-errors tcam-stage ingress app napt-reverse-fil
<clear-pfe-tcam-errors-ingress-app-napt-reverse-fil>
<clear-pgm-negative-acknowledgments>
clear pgm source-path-messages
<clear-pgm-source-path-messages>
clear pgm statistics
<clear-pgm-statistics>
clear pim
clear pim join
<clear-pim-join-state>
clear pim join-distribution
<clear-pim-join-distribution>
clear pim register
<clear-pim-register-state>
clear pim snooping
clear pim snooping join
clear pim snooping statistics
clear pim statistics
<clear-pim-statistics>
clear poe
clear poe telemetries
clear poe telemetries interface
<clear-poe-telemetries-information>
clear ppp
clear ppp statistics
<clear-ppp-statistics-information>
clear pppoe
clear pppoe lockout
<clear-pppoe-lockout-timers>
clear pppoe lockout atm-identifier
<clear-pppoe-lockout-timers-atm>
clear pppoe lockout vlan-identifier
clear pppoe sessions
<clear-pppoe-sessions-information>
clear-pppoe-lockout-timers-vlan
clear pppoe statistics
<clear-pppoe-statistics-information>
clear pppoe statistics interfaces
<clear-pppoe-statistics-interface-information>
clear protection-group
<clear protection-group>
clear protection-group ethernet-ring
<clear-ethernet-ring-information>
clear protection-group ethernet-ring statistics
<clear-ethernet-ring-information>
clear r2cp
clear r2cp radio
<clear-r2cp-radio>
clear r2cp session
<clear-r2cp-session>
clear r2cp statistics
<clear-r2cp-statistics>
clear r2cp statistics radio
clear r2cp statistics session
clear rip
clear rip general-statistics
<clear-rip-general-statistics>
clear rip statistics
<clear-rip-statistics>
clear rip statistics peer
<clear-rip-peer-statistics>
clear ripng
clear ripng general-statistics
<clear-ripng-general-statistic>
clear ripng statistics
<clear-ripng-statistics>
clear rsvp
clear rsvp session
<clear-rsvp-session-information>
clear rsvp statistics
< clear-rsvp-counters-information>
clear security group-vpn
clear security group-vpn member
clear security group-vpn member group
<clear-gvpn-group-information>
clear security group-vpn member ike
clear security group-vpn member ike security-associations
<clear-group-vpn-ike-security-associations>
clear security group-vpn member ipsec
clear security group-vpn member ipsec security-associations
<clear-gvpn-ipsec-security-association>
clear security group-vpn member ipsec security-associations statistics
<clear-gvpn-ipsec-security-association-statistics>
clear security group-vpn member ipsec statistics
<clear-gvpn-ipsec-statistics>
clear services
clear services accounting flow inline-jflow
<clear-services-accounting-inline-jflow-flows>
clear services alg
clear services alg statistics
<clear-services-alg-statistics>
clear services application-aware-access-list
clear services application-aware-access-list statistics
<clear-application-aware-access-list-statistics-interface>
clear services application-aware-access-list statistics interface
<clear-application-aware-access-list-statistics-interface>
clear services application-aware-access-list statistics subscriber
<clear-application-aware-access-list-statistics-subscriber>
clear services application-identification
clear services application-identification application-system-cache
<clear-appid-application-system-cache>
clear services application-identification counter
<clear-appid-counter>
clear services application-identification counter ssl-encrypted-sessions
<clear-appid-counter-encrypted>
clear services application-identification statistics
<clear-appid-application-statistics>
clear services application-identification statistics cumulative
<clear-appid-application-statistics-cumulative>
clear services application-identification statistics interval
<clear-appid-application-statistics-interval>
clear services border-signaling-gateway
clear services border-signaling-gateway denied-messages
<clear-service-bsg-denied-messages>
clear services border-signaling-gateway name-resolution-cache
clear services border-signaling-gateway name-resolution-cache all
<clear-service-border-signaling-gateway-name-resolution-cache-all>
clear services border-signaling-gateway name-resolution-cache by-fqdn
<clear-border-signaling-gateway-name-resolution-cache-by-fqdn>
clear services border-signaling-gateway statistics
<clear-service-border-signaling-gateway-statistics>
clear services captive-portal-content-delivery
clear services captive-portal-content-delivery statistics
clear services captive-portal-content-delivery statistics interface
<clear-cpcdd-interface-statistics>
clear services cos
clear services cos statistics
<clear-services-cos-statistics>
clear services crtp
clear services crtp statistics
<clear-services-crtp-statistics>
clear services dynamic-flow-capture
clear services dynamic-flow-capture criteria
<clear-services-dynamic-flow-capture-criteria>
clear services dynamic-flow-capture sequence-number
clear services flow-collector
<clear-services-flow-collector-information>
clear services flow-collector statistics
<clear-services-flow-collector-statistics>
clear-service-msp-flow-ipaction-table
clear services ha
clear services ha statistics
<clear-service-ha-statistics-information>
clear services hcm
clear services hcm pic-statistics
<clear-services-hcm-pic-statistics>
clear services hcm statistics
<clear-services-hcm-statistics>
clear services ids
<clear-services-ids-tables>
clear services ids destination-table
<clear-services-ids-destination-table>
clear services ids pair-table
<clear-services-ids-pair-table>
clear services ids source-table
<clear-services-ids-source-table>
clear services inline
clear services inline nat
clear services inline nat pool
<clear-inline-nat-pool-information>
clear services inline nat statistics
<clear-inline-nat-statistics>
clear services inline softwire
clear services inline softwire statistics
<clear-inline-softwire-statistics>
clear services ipsec-vpn
clear services ipsec-vpn ipsec
clear services ipsec-vpn ipsec security-associations
<clear-services-ipsec-vpn-security-associations>
clear services ipsec-vpn ike
clear services ipsec-vpn ike security-associations
<clear-services-ike-security-associations>
clear services ipsec-vpn ike statistics
<clear-services-ike-statistics>
clear services pcp
clear services pcp epoch
clear services pcp statistics
clear services ipsec-vpn ipsec statistics
<clear-ipsec-vpn-statistics>
clear services l2tp
<clear-l2tp-destinations-information>
clear services l2tp disconnect-cause-summary
<clear-l2tp-disconnect-cause-summary>
clear services l2tp multilink
<clear-l2tp-multilink-information>
<clear-mobile-gateway-statistics>
clear unified-edge ggsn-pgw subscribers
<clear-mobile-gateway-subscribers>
clear unified-edge ggsn-pgw subscribers bearer
clear unified-edge ggsn-pgw subscribers charging
<clear-mobile-gateway-subscribers-charging>
clear unified-edge ggsn-pgw subscribers peer
<clear-mobile-gateway-subscribers-peer>
clear unified-edge sgw
clear unified-edge sgw call-admission-control
clear unified-edge sgw call-admission-control statistics
<clear-mobile-sgw-cac-statistics>
clear unified-edge sgw charging
clear unified-edge sgw charging cdr
<clear-mobile-gateway-sgw-charging-clear-cdr>
clear unified-edge sgw charging cdr wfa
<clear-mobile-gateway-sgw-charging-clear-cdr-wfa>
clear unified-edge sgw charging local-persistent-storage
clear unified-edge sgw charging local-persistent-storage statistics
<clear-mobile-gateway-sgw-charging-clear-lps-stats>
clear unified-edge sgw charging path
clear unified-edge sgw charging path statistics
<clear-mobile-gateway-sgw-charging-clear-path-stats>
clear unified-edge sgw charging transfer
clear unified-edge sgw charging transfer statistics
<clear-mobile-gateway-sgw-charging-clear-xfer-stats>
clear unified-edge sgw gtp
clear unified-edge sgw gtp peer
clear unified-edge sgw gtp peer statistics
<clear-mobile-sgw-gtp-peer-statistics>
clear unified-edge sgw gtp statistics
<clear-mobile-sgw-gtp-statistics>
clear unified-edge sgw idle-mode-buffering
clear unified-edge sgw idle-mode-buffering statistics
<clear-mobile-gw-sgw-idle-mode-buffering-statistics>
clear unified-edge sgw ip-reassembly
clear unified-edge sgw ip-reassembly statistics
<clear-mobile-gateways-sgw-ip-reassembly-statistics-sgw>
clear unified-edge sgw statistics
<clear-mobile-sgw-statistics>
clear unified-edge sgw subscribers
<clear-mobile-sgw-subscribers>
clear unified-edge sgw subscribers charging
<clear-mobile-sgw-subscribers-charging>
clear unified-edge sgw subscribers peer
<clear-mobile-sgw-subscribers-peer>
clear validation
clear validation database
<clear-validation-database>
clear validation session
<clear-validation-session>
clear validation statistics
<clear-validation-statistics>
clear virtual-chassis
clear virtual-chassis heartbeat
<clear-virtual-chassis-heartbeat-statistics>
<clear virtual-chassis protocol>
clear virtual-chassis protocol statistics
<clear-virtual-chassis-statistics>
<clear-virtual-chassis-port-statistics>
clear vpls
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
configure
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Commands
configure
request snmp
request-snmp-utility-mib-clear
request-snmp-utility-mib-set
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
control
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
field
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
firewall
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
show policer
<get-policer-information>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
firewall-control
Can view and configure firewall filter information at the [edit dynamic-profiles firewall],
[edit firewall], and [edit logical-systems firewall] hierarchy levels.
show policer
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
floppy
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
flow-tap
<clear-mobile-gateway-aaa-statistics>
clear unified-edge ggsn-pgw address-assignment
clear unified-edge ggsn-pgw address-assignment pool
<clear-mobile-gateway-sm-ippool-pool-sessions>
clear unified-edge ggsn-pgw address-assignment statistics
<clear-mobile-gateway-sm-ippool-statistics>
clear unified-edge ggsn-pgw call-admission-control
clear unified-edge ggsn-pgw call-admission-control statistics
<clear-mobile-gateway-cac-statistics>
clear unified-edge ggsn-pgw charging
clear unified-edge ggsn-pgw charging cdr
<clear-mobile-gateway-charging-clear-cdr-wfa>
clear unified-edge ggsn-pgw charging local-persistent-storage
clear unified-edge ggsn-pgw charging local-persistent-storage statistics
<clear-mobile-gateway-charging-clear-lps-stats>
clear unified-edge ggsn-pgw charging path
clear unified-edge ggsn-pgw charging path statistics
<clear-mobile-gateway-charging-clear-path-stats>
clear unified-edge ggsn-pgw charging transfer
clear unified-edge ggsn-pgw charging transfer statistics
<clear-mobile-gateway-charging-clear-xfer-stats>
clear unified-edge ggsn-pgw diameter
clear unified-edge ggsn-pgw diameter dcca-gy
clear unified-edge ggsn-pgw diameter dcca-gy statistics
<clear-mobile-gateway-aaa-diam-stats-gy>
clear unified-edge ggsn-pgw diameter network-element
clear unified-edge ggsn-pgw diameter network-element statistics
<clear-mobile-gateway-aaa-diam-ne-statistics>
clear unified-edge ggsn-pgw diameter pcc-gx
clear unified-edge ggsn-pgw diameter pcc-gx statistics
<clear-mobile-gateway-aaa-diam-stats-gx>
clear unified-edge ggsn-pgw diameter peer
clear unified-edge ggsn-pgw diameter peer statistics
<clear-mobile-gateway-aaa-diam-peer-statistics>
clear unified-edge ggsn-pgw gtp
clear unified-edge ggsn-pgw gtp peer
clear unified-edge ggsn-pgw gtp peer statistics
<clear-mobile-gateway-gtp-peer-statistics>
clear unified-edge ggsn-pgw gtp statistics
<clear-mobile-gateway-gtp-statistics>
clear unified-edge ggsn-pgw ip-reassembly
clear unified-edge ggsn-pgw ip-reassembly statistics
<clear-mobile-gateways-ip-reassembly-statistics>
clear unified-edge ggsn-pgw statistics
<clear-mobile-gateway-statistics>
clear unified-edge ggsn-pgw subscribers
<clear-mobile-gateway-subscribers>
clear unified-edge ggsn-pgw subscribers bearer
clear unified-edge ggsn-pgw subscribers charging
<clear-mobile-gateway-subscribers-charging>
clear unified-edge ggsn-pgw subscribers peer
<clear-mobile-gateway-subscribers-peer>
clear unified-edge sgw
clear unified-edge sgw call-admission-control
clear unified-edge sgw call-admission-control statistics
<clear-mobile-sgw-cac-statistics>
clear unified-edge sgw charging
clear unified-edge sgw charging cdr
<clear-mobile-gateway-sgw-charging-clear-cdr>
clear unified-edge sgw charging cdr wfa
<clear-mobile-gateway-sgw-charging-clear-cdr-wfa>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
flow-tap-control
Can view the flow-tap configuration in configuration mode and can configure flow-tap
configuration information at the [edit services flow-tap], [edit services radius-flow-tap],
and [edit system services flow-tap-dtcp] hierarchy levels.
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
flow-tap-operation
Supported Platforms M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
idp-profiler-operation
interface
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
<clear-mobile-gateway-aaa-diam-ne-statistics>
clear unified-edge ggsn-pgw diameter pcc-gx
clear unified-edge ggsn-pgw diameter pcc-gx statistics
<clear-mobile-gateway-aaa-diam-stats-gx>
clear unified-edge ggsn-pgw diameter peer
clear unified-edge ggsn-pgw diameter peer statistics
<clear-mobile-gateway-aaa-diam-peer-statistics>
clear unified-edge ggsn-pgw gtp
clear unified-edge ggsn-pgw gtp peer
clear unified-edge ggsn-pgw gtp peer statistics
<clear-mobile-gateway-gtp-peer-statistics>
clear unified-edge ggsn-pgw gtp statistics
<clear-mobile-gateway-gtp-statistics>
clear unified-edge ggsn-pgw ip-reassembly
clear unified-edge ggsn-pgw ip-reassembly statistics
<clear-mobile-gateways-ip-reassembly-statistics>
clear unified-edge ggsn-pgw statistics
<clear-mobile-gateway-statistics>
clear unified-edge ggsn-pgw subscribers
<clear-mobile-gateway-subscribers>
clear unified-edge ggsn-pgw subscribers bearer
clear unified-edge ggsn-pgw subscribers charging
<clear-mobile-gateway-subscribers-charging>
clear unified-edge ggsn-pgw subscribers peer
<clear-mobile-gateway-subscribers-peer>
clear unified-edge sgw
clear unified-edge sgw call-admission-control
clear unified-edge sgw call-admission-control statistics
<clear-mobile-sgw-cac-statistics>
clear unified-edge sgw charging
clear unified-edge sgw charging cdr
<clear-mobile-gateway-sgw-charging-clear-cdr>
clear unified-edge sgw charging cdr wfa
<clear-mobile-gateway-sgw-charging-clear-cdr-wfa>
clear unified-edge sgw charging local-persistent-storage
clear unified-edge sgw charging local-persistent-storage statistics
<clear-mobile-gateway-sgw-charging-clear-lps-stats>
clear unified-edge sgw charging path
clear unified-edge sgw charging path statistics
<clear-mobile-gateway-sgw-charging-clear-path-stats>
clear unified-edge sgw charging transfer
clear unified-edge sgw charging transfer statistics
<clear-mobile-gateway-sgw-charging-clear-xfer-stats>
clear unified-edge sgw gtp
clear unified-edge sgw gtp peer
clear unified-edge sgw gtp peer statistics
<clear-mobile-sgw-gtp-peer-statistics>
clear unified-edge sgw gtp statistics
<clear-mobile-sgw-gtp-statistics>
clear unified-edge sgw idle-mode-buffering
clear unified-edge sgw idle-mode-buffering statistics
<clear-mobile-gw-sgw-idle-mode-buffering-statistics>
clear unified-edge sgw ip-reassembly
clear unified-edge sgw ip-reassembly statistics
<clear-mobile-gateways-sgw-ip-reassembly-statistics-sgw>
clear unified-edge sgw statistics
<clear-mobile-sgw-statistics>
clear unified-edge sgw subscribers
<clear-mobile-sgw-subscribers>
clear unified-edge sgw subscribers charging
<clear-mobile-sgw-subscribers-charging>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
interface-control
Can view chassis, class of service (CoS), groups, forwarding options, and interfaces
configuration information. Can edit configuration at the [edit chassis], [edit
class-of-service], [edit groups], [edit forwarding-options], and [edit interfaces] hierarchy
levels.
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
maintenance
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Can perform system maintenance, including starting a local shell on the router and
becoming the superuser in the shell, and can halt and reboot the router.
Commands
clear system commit synchronize-server pending-jobs
<clear-pending-commit-sync-jobs>
clear system reboot
<clear-reboot>
clear-system-services-reverse-information
file archive
<file-archive>
file change-owner
<file-change-owner>
<extract-file>
monitor traffic
request chassis afeb
request chassis beacon
<request-chassis-beacon>
request chassis cb
<request-chassis-cb>
request chassis ccg
<request-chassis-ccg>
<verify-pki-ca-certificate>
request security pki crl
request security pki crl load
<load-pki-crl>
request security pki generate-certificate-request
<generate-pki-certificate-request>
request security pki generate-key-pair
<generate-pki-key-pair>
request security pki local-certificate
request security pki local-certificate enroll
request security pki local-certificate generate-self-signed
<generate-pki-self-signed-local-certificate>
request security pki local-certificate load
<load-pki-local-certificate>
request security pki local-certificate verify
<verify-pki-local-certificate>
request security pki verify-integrity-status
<verify-integrity-status>
request services fips
request services fips authorize
request services fips authorize pic
request services fips zeroize
request services fips zeroize pic
request services flow-collector
request services flow-collector change-destination
<request-services-flow-collector-destination>
request support
request support information
request system
request system boot-media
<request-boot-media>
request system certificate
request system certificate add
request system commit
request system commit server
request system commit server pause
<request-commit-server-pause>
request system commit server queue
request system commit server queue cleanup
<request-commit-server-cleanup>
request system commit server start
<request-commit-server-start>
request system configuration
request system configuration rescue
request system configuration rescue delete
<request-delete-rescue-configuration>
<request-reboot>
request system recover
Configuration
Hierarchy Levels [edit event-options]
[edit security ipsec internal]
[edit security ipsect trusted-channel]
[edit services dynamic-flow-capture traceoptions]
[edit services ggsn]
[edit system fips]
[edit services ggsn rule-space]
[edit system processes daemon-process command]
[edit system scripts]
[edit system scripts commit]
[edit system scripts op]
[edit system scripts snmp]
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
network
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Can access the network by using the ping, ssh, telnet, and traceroute commands.
Commands
mtrace
mtrace from-source
mtrace monitor
mtrace to-gateway
ping
<ping>
ping atm
ping clns
ping ethernet
<request-ping-ethernet>
ping fibre-channel
ping mpls
ping mpls bgp
<request-ping-bgp-lsp>
ping mpls l2circuit
ping mpls l2circuit interface
<request-ping-l2circuit-interface>
ping overlay
<request-ping-overlay>
ping vpls
ping vpls instance
<request-ping-vpls-instance>
request routing-engine
request routing-engine login
<request-routing-engine-login>
request routing-engine login other-routing-engine
<request-login-to-other-routing-engine>
request services flow-collector
request services flow-collector test-file-transfer
<request-services-flow-collector-test-file-transfer>
show host
traceroute clns
traceroute ethernet
<request-traceroute-ethernet>
traceroute monitor
traceroute mpls
traceroute mpls l2vpn
<traceroute-mpls-l2vpn>
traceroute mpls l2vpn fec129
<traceroute-mpls-mspw>
traceroute mpls ldp
<traceroute-mpls-ldp>
traceroute mpls rsvp
<traceroute-mpls-rsvp>
traceroute overlay
<request-traceroute-overlay>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
pgcp-session-mirroring
Supported Platforms M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
<clear-mobile-gateway-sm-ippool-statistics>
clear unified-edge ggsn-pgw call-admission-control
clear unified-edge ggsn-pgw call-admission-control statistics
<clear-mobile-gateway-cac-statistics>
clear unified-edge ggsn-pgw charging
clear unified-edge ggsn-pgw charging cdr
<clear-mobile-gateway-charging-clear-cdr>
clear unified-edge ggsn-pgw charging cdr wfa
<clear-mobile-gateway-charging-clear-cdr-wfa>
clear unified-edge ggsn-pgw charging local-persistent-storage
clear unified-edge ggsn-pgw charging local-persistent-storage statistics
<clear-mobile-gateway-charging-clear-lps-stats>
clear unified-edge ggsn-pgw charging path
clear unified-edge ggsn-pgw charging path statistics
<clear-mobile-gateway-charging-clear-path-stats>
clear unified-edge ggsn-pgw charging transfer
clear unified-edge ggsn-pgw charging transfer statistics
<clear-mobile-gateway-charging-clear-xfer-stats>
clear unified-edge ggsn-pgw diameter
clear unified-edge ggsn-pgw diameter dcca-gy
clear unified-edge ggsn-pgw diameter dcca-gy statistics
<clear-mobile-gateway-aaa-diam-stats-gy>
clear unified-edge ggsn-pgw diameter network-element
clear unified-edge ggsn-pgw diameter network-element statistics
<clear-mobile-gateway-aaa-diam-ne-statistics>
clear unified-edge ggsn-pgw diameter pcc-gx
clear unified-edge ggsn-pgw diameter pcc-gx statistics
<clear-mobile-gateway-aaa-diam-stats-gx>
clear unified-edge ggsn-pgw diameter peer
clear unified-edge ggsn-pgw diameter peer statistics
<clear-mobile-gateway-aaa-diam-peer-statistics>
clear unified-edge ggsn-pgw gtp
clear unified-edge ggsn-pgw gtp peer
clear unified-edge ggsn-pgw gtp peer statistics
<clear-mobile-gateway-gtp-peer-statistics>
clear unified-edge ggsn-pgw gtp statistics
<clear-mobile-gateway-gtp-statistics>
clear unified-edge ggsn-pgw ip-reassembly
clear unified-edge ggsn-pgw ip-reassembly statistics
<clear-mobile-gateways-ip-reassembly-statistics>
clear unified-edge ggsn-pgw statistics
<clear-mobile-gateway-statistics>
clear unified-edge ggsn-pgw subscribers
<clear-mobile-gateway-subscribers>
clear unified-edge ggsn-pgw subscribers bearer
clear unified-edge ggsn-pgw subscribers charging
<clear-mobile-gateway-subscribers-charging>
clear unified-edge ggsn-pgw subscribers peer
<clear-mobile-gateway-subscribers-peer>
clear unified-edge sgw
clear unified-edge sgw call-admission-control
clear unified-edge sgw call-admission-control statistics
<clear-mobile-sgw-cac-statistics>
clear unified-edge sgw charging
clear unified-edge sgw charging cdr
<clear-mobile-gateway-sgw-charging-clear-cdr>
clear unified-edge sgw charging cdr wfa
<clear-mobile-gateway-sgw-charging-clear-cdr-wfa>
clear unified-edge sgw charging local-persistent-storage
clear unified-edge sgw charging local-persistent-storage statistics
<clear-mobile-gateway-sgw-charging-clear-lps-stats>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
pgcp-session-mirroring-control
Configuration
Hierarchy Levels [edit services pgcp gateway session-mirroring]
[edit services pgcp session-mirroring]
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
reset
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Can restart software processes by using the restart command and can configure whether
software processes configured at the [edit system processes] hierarchy level are enabled
or disabled.
restart services
restart services border-signaling-gateway
<restart-border-signaling-gateway-service>
restart services pgcp
<restart-pgcp-service>
restart web-management
<restart-web-management>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
rollback
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Commands rollback
Configuration
Hierarchy Levels [edit]
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
secret
clear unified-edge
clear unified-edge ggsn-pgw
clear unified-edge ggsn-pgw aaa
clear unified-edge ggsn-pgw aaa radius
clear unified-edge ggsn-pgw aaa radius statistics
<clear-mobile-gateway-aaa-radius-statistics>
clear unified-edge ggsn-pgw aaa statistics
<clear-mobile-gateway-aaa-statistics>
clear unified-edge ggsn-pgw address-assignment
clear unified-edge ggsn-pgw address-assignment pool
<clear-mobile-gateway-sm-ippool-pool-sessions>
clear unified-edge ggsn-pgw address-assignment statistics
<clear-mobile-gateway-sm-ippool-statistics>
clear unified-edge ggsn-pgw call-admission-control
clear unified-edge ggsn-pgw call-admission-control statistics
<clear-mobile-gateway-cac-statistics>
clear unified-edge ggsn-pgw charging
clear unified-edge ggsn-pgw charging cdr
<clear-mobile-gateway-charging-clear-cdr>
clear unified-edge ggsn-pgw charging cdr wfa
<clear-mobile-gateway-charging-clear-cdr-wfa>
clear unified-edge ggsn-pgw charging local-persistent-storage
clear unified-edge ggsn-pgw charging local-persistent-storage statistics
<clear-mobile-gateway-charging-clear-lps-stats>
clear unified-edge ggsn-pgw charging path
clear unified-edge ggsn-pgw charging path statistics
<clear-mobile-gateway-charging-clear-path-stats>
clear unified-edge ggsn-pgw charging transfer
clear unified-edge ggsn-pgw charging transfer statistics
<clear-mobile-gateway-charging-clear-xfer-stats>
clear unified-edge ggsn-pgw diameter
clear unified-edge ggsn-pgw diameter dcca-gy
clear unified-edge ggsn-pgw diameter dcca-gy statistics
<clear-mobile-gateway-aaa-diam-stats-gy>
clear unified-edge ggsn-pgw diameter network-element
clear unified-edge ggsn-pgw diameter network-element statistics
<clear-mobile-gateway-aaa-diam-ne-statistics>
clear unified-edge ggsn-pgw diameter pcc-gx
clear unified-edge ggsn-pgw diameter pcc-gx statistics
<clear-mobile-gateway-aaa-diam-stats-gx>
clear unified-edge ggsn-pgw diameter peer
clear unified-edge ggsn-pgw diameter peer statistics
<clear-mobile-gateway-aaa-diam-peer-statistics>
clear unified-edge ggsn-pgw gtp
clear unified-edge ggsn-pgw gtp peer
clear unified-edge ggsn-pgw gtp peer statistics
<clear-mobile-gateway-gtp-peer-statistics>
clear unified-edge ggsn-pgw gtp statistics
<clear-mobile-gateway-gtp-statistics>
clear unified-edge ggsn-pgw ip-reassembly
clear unified-edge ggsn-pgw ip-reassembly statistics
<clear-mobile-gateways-ip-reassembly-statistics>
clear unified-edge ggsn-pgw statistics
<clear-mobile-gateway-statistics>
clear unified-edge ggsn-pgw subscribers
<clear-mobile-gateway-subscribers>
clear unified-edge ggsn-pgw subscribers bearer
clear unified-edge ggsn-pgw subscribers charging
<clear-mobile-gateway-subscribers-charging>
clear unified-edge ggsn-pgw subscribers peer
<clear-mobile-gateway-subscribers-peer>
clear unified-edge sgw
clear unified-edge sgw call-admission-control
clear unified-edge sgw call-admission-control statistics
<clear-mobile-sgw-cac-statistics>
clear unified-edge sgw charging
clear unified-edge sgw charging cdr
<clear-mobile-gateway-sgw-charging-clear-cdr>
clear unified-edge sgw charging cdr wfa
<clear-mobile-gateway-sgw-charging-clear-cdr-wfa>
clear unified-edge sgw charging local-persistent-storage
clear unified-edge sgw charging local-persistent-storage statistics
<clear-mobile-gateway-sgw-charging-clear-lps-stats>
clear unified-edge sgw charging path
clear unified-edge sgw charging path statistics
<clear-mobile-gateway-sgw-charging-clear-path-stats>
clear unified-edge sgw charging transfer
clear unified-edge sgw charging transfer statistics
<clear-mobile-gateway-sgw-charging-clear-xfer-stats>
clear unified-edge sgw gtp
clear unified-edge sgw gtp peer
clear unified-edge sgw gtp peer statistics
<clear-mobile-sgw-gtp-peer-statistics>
clear unified-edge sgw gtp statistics
<clear-mobile-sgw-gtp-statistics>
clear unified-edge sgw idle-mode-buffering
clear unified-edge sgw idle-mode-buffering statistics
<clear-mobile-gw-sgw-idle-mode-buffering-statistics>
clear unified-edge sgw ip-reassembly
clear unified-edge sgw ip-reassembly statistics
<clear-mobile-gateways-sgw-ip-reassembly-statistics-sgw>
clear unified-edge sgw statistics
<clear-mobile-sgw-statistics>
clear unified-edge sgw subscribers
<clear-mobile-sgw-subscribers>
clear unified-edge sgw subscribers charging
<clear-mobile-sgw-subscribers-charging>
clear unified-edge sgw subscribers peer
<clear-mobile-sgw-subscribers-peer>
clear unified-edge tdf
clear unified-edge tdf aaa
clear unified-edge tdf aaa radius
clear unified-edge tdf aaa radius client
clear unified-edge tdf aaa radius client statistics
<clear-radius-client-statistics>
clear unified-edge tdf aaa radius network-element
clear unified-edge tdf aaa radius network-element statistics
<clear-radius-network-element-statistics>
clear unified-edge tdf aaa radius server
clear unified-edge tdf aaa radius server statistics
<clear-radius-server-statistics>
clear unified-edge tdf aaa radius snoop-segment
clear unified-edge tdf aaa radius snoop-segment statistics
<clear-radius-snoop-segment-statistics>
clear unified-edge tdf aaa statistics
<clear-tdf-gateway-aaa-statistics>
clear unified-edge tdf address-assignment
clear unified-edge tdf address-assignment pool
<clear-mobile-gateway-tdf-sm-ippool-pool-sessions>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
secret-control
Can view passwords and other authentication keys in the configuration and can modify
them in configuration mode.
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
security
Commands
clear security
clear security alarms
<clear-security-alarm-information>
clear security idp
clear security idp application-ddos
clear security idp application-ddos cache
<clear-idp-appddos-cache>
<get-idp-predefined-attack-groups>
<get-idp-predefined-attack-group-filters>
<get-idp-predefined-attacks>
<get-idp-predefined-attack-filters>
<get-idp-recent-security-package-information>
show security idp policy-commit-status
<get-idp-policy-commit-status>
<get-idp-recent-security-package-information>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
security-control
Can view and configure security information at the [edit security] hierarchy level.
Commands
clear security
clear security alarms
<clear-security-alarm-information>
clear security idp
clear security idp application-ddos
clear security idp application-ddos cache
<clear-idp-appddos-cache>
<get-idp-attack-table-information>
<get-idp-recent-security-package-information>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
shell
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
snmp
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
<clear-mobile-gateway-tdf-sm-ippool-statistics>
clear unified-edge tdf call-admission-control
clear unified-edge tdf call-admission-control statistics
<clear-tdf-cac-statistics>
clear unified-edge tdf diameter
clear unified-edge tdf diameter network-element
clear unified-edge tdf diameter network-element statistics
<clear-diameter-network-element-statistics>
clear unified-edge tdf diameter pcc-gx
clear unified-edge tdf diameter pcc-gx statistics
<clear-diameter-statistics-gx>
clear unified-edge tdf diameter peer
clear unified-edge tdf diameter peer statistics
<clear-diameter-peer-statistics>
clear unified-edge tdf statistics
<clear-tdf-statistics>
clear unified-edge tdf subscribers
<clear-mobile-tdf-subscribers>
clear unified-edge tdf subscribers peer
<clear-mobile-gateway-tdf-subscribers-peer>
request unified-edge
request unified-edge ggsn-pgw
request unified-edge ggsn-pgw call-trace
<monitor-mobile-gateways-call-trace-start>
request unified-edge ggsn-pgw call-trace clear
<get-mobile-gateways-call-trace-clear>
request unified-edge ggsn-pgw call-trace show
<get-mobile-gateways-call-trace-information>
request unified-edge ggsn-pgw call-trace start
<get-mobile-gateways-call-trace-start-information>
request unified-edge ggsn-pgw call-trace stop
<get-mobile-gateways-call-trace-stop-information>
request unified-edge sgw
request unified-edge sgw call-trace
request unified-edge sgw call-trace clear
<get-mobile-gateways-sgw-call-trace-clear>
request unified-edge sgw call-trace show
<get-mobile-gateways-sgw-call-trace-information>
request unified-edge sgw call-trace start
<get-mobile-gateways-sgw-call-trace-start-information>
request unified-edge sgw call-trace stop
<get-mobile-gateways-sgw-call-trace-stop-information>
request unified-edge tdf
request unified-edge tdf call-trace
request unified-edge tdf call-trace clear
<get-mobile-gateways-tdf-call-trace-clear>
request unified-edge tdf call-trace show
<get-mobile-gateways-tdf-call-trace-information>
request unified-edge tdf call-trace start
<get-mobile-gateways-tdf-call-trace-start-information>
request unified-edge tdf call-trace stop
<get-mobile-gateways-tdf-call-trace-stop-information>
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
system
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
system-control
Can view system-level configuration information and configure it at the [edit system]
hierarchy level.
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
trace
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Can view trace file settings and configure trace file properties.
Commands
clear log
<clear-log>
clear log satellite
<clear-log-satellite>
clear unified-edge
clear unified-edge ggsn-pgw
clear unified-edge ggsn-pgw aaa
clear unified-edge ggsn-pgw aaa radius
clear unified-edge ggsn-pgw aaa radius statistics
<clear-mobile-gateway-aaa-radius-statistics>
clear unified-edge ggsn-pgw aaa statistics
<clear-mobile-gateway-aaa-statistics>
clear unified-edge ggsn-pgw address-assignment
clear unified-edge ggsn-pgw address-assignment pool
<clear-mobile-gateway-sm-ippool-pool-sessions>
clear unified-edge ggsn-pgw address-assignment statistics
<clear-mobile-gateway-sm-ippool-statistics>
clear unified-edge ggsn-pgw call-admission-control
clear unified-edge ggsn-pgw call-admission-control statistics
<clear-mobile-gateway-cac-statistics>
clear unified-edge ggsn-pgw charging
clear unified-edge ggsn-pgw charging cdr
<clear-mobile-gateway-charging-clear-cdr>
clear unified-edge ggsn-pgw charging cdr wfa
<clear-mobile-gateway-charging-clear-cdr-wfa>
clear unified-edge ggsn-pgw charging local-persistent-storage
clear unified-edge ggsn-pgw charging local-persistent-storage statistics
<clear-mobile-gateway-charging-clear-lps-stats>
clear unified-edge ggsn-pgw charging path
clear unified-edge ggsn-pgw charging path statistics
<clear-mobile-gateway-charging-clear-path-stats>
clear unified-edge ggsn-pgw charging transfer
clear unified-edge ggsn-pgw charging transfer statistics
<clear-mobile-gateway-charging-clear-xfer-stats>
clear unified-edge ggsn-pgw diameter
clear unified-edge ggsn-pgw diameter dcca-gy
clear unified-edge ggsn-pgw diameter dcca-gy statistics
<clear-mobile-gateway-aaa-diam-stats-gy>
traceoptions]
[edit dynamic-profiles routing-instances instance protocols bgp group
traceoptions]
[edit dynamic-profiles routing-instances instance protocols bgp traceoptions]
[edit dynamic-profiles routing-instances instance protocols esis traceoptions]
[edit dynamic-profiles routing-instances instance protocols igmp-snooping
traceoptions]
[edit dynamic-profiles routing-instances instance protocols isis traceoptions]
[edit dynamic-profiles routing-instances instance protocols l2vpn traceoptions]
[edit dynamic-profiles routing-instances instance protocols ldp traceoptions]
[edit dynamic-profiles routing-instances instance protocols msdp group peer
traceoptions]
[edit dynamic-profiles routing-instances instance protocols msdp group
traceoptions]
[edit dynamic-profiles routing-instances instance protocols msdp peer
traceoptions]
[edit dynamic-profiles routing-instances instance protocols msdp traceoptions]
[edit dynamic-profiles routing-instances instance protocols mvpn traceoptions]
[edit dynamic-profiles routing-instances instance protocols ospf traceoptions]
[edit dynamic-profiles routing-instances instance protocols pim traceoptions]
[edit dynamic-profiles routing-instances instance protocols rip traceoptions]
[edit dynamic-profiles routing-instances instance protocols ripng traceoptions]
[edit dynamic-profiles routing-instances instance protocols router-discovery
traceoptions]
[edit dynamic-profiles routing-instances instance protocols vpls traceoptions]
[edit dynamic-profiles routing-instances instance routing-options multicast
traceoptions]
[edit dynamic-profiles routing-instances instance routing-options traceoptions]
[edit dynamic-profiles routing-instances instance services mobile-ip
traceoptions]
[edit dynamic-profiles routing-instances instance system services
dhcp-local-server traceoptions]
[edit dynamic-profiles routing-options multicast traceoptions]
[edit fabric protocols bgp group neighbor traceoptions]
[edit fabric protocols bgp group traceoptions]
[edit fabric protocols bgp traceoptions]
[edit fabric routing-instances instance routing-options traceoptions]
[edit fabric routing-options traceoptions]
[edit jnx-example traceoptions]
[edit logical-systems vlans domain forwarding-options dhcp-relay traceoptions]
[edit logical-systems vlans domain forwarding-options dhcp-relay
interface-traceoptions]
[edit logical-systems vlans domain multicast-snooping-options traceoptions]
[edit logical-systems vlans domain protocols igmp-snooping traceoptions]
[edit logical-systems forwarding-options dhcp-relay traceoptions]
[edit logical-systems protocols ancp traceoptions]
[edit logical-systems protocols bgp group neighbor traceoptions]
[edit logical-systems protocols bgp group traceoptions]
[edit logical-systems protocols bgp traceoptions]
[edit logical-systems protocols dot1x traceoptions]
[edit logical-systems protocols dvmrp traceoptions]
[edit logical-systems protocols esis traceoptions]
[edit logical-systems protocols igmp traceoptions]
[edit logical-systems protocols igmp-host traceoptions]
[edit logical-systems protocols ilmi traceoptions]
[edit logical-systems protocols isis traceoptions]
[edit logical-systems protocols l2circuit traceoptions]
[edit logical-systems protocols l2iw traceoptions]
[edit logical-systems protocols lacp traceoptions]
[edit logical-systems protocols layer2-control traceoptions]
[edit logical-systems protocols ldp traceoptions]
traceoptions]
[edit logical-systems routing-instances instance protocols vpls traceoptions]
[edit logical-systems routing-instances instance routing-options multicast
traceoptions]
[edit logical-systems routing-instances instance routing-options traceoptions]
[edit logical-systems routing-instances instance services mobile-ip
traceoptions]
[edit logical-systems routing-instances instance system services
dhcp-local-server traceoptions]
[edit logical-systems routing-instances instance system services
dhcp-local-server interface-traceoptions]
[edit logical-systems routing-options multicast traceoptions]
[edit logical-systems routing-options traceoptions]
[edit logical-systems services mobile-ip traceoptions]
[edit logical-systems system services dhcp-local-server traceoptions]
[edit logical-systems system services dhcp-local-server interface-traceoptions]
[edit multicast-snooping-options traceoptions]
[edit protocols ancp traceoptions]
[edit protocols bgp group neighbor traceoptions]
[edit protocols bgp group traceoptions]
[edit protocols bgp traceoptions]
[edit protocols dot1x traceoptions]
[edit protocols dvmrp traceoptions]
[edit protocols esis traceoptions]
[edit protocols igmp traceoptions]
[edit protocols igmp-host traceoptions]
[edit protocols ilmi traceoptions]
[edit protocols isis traceoptions]
[edit protocols l2circuit traceoptions]
[edit protocols l2iw traceoptions]
[edit protocols lacp traceoptions]
[edit protocols layer2-control traceoptions]
[edit protocols ldp traceoptions]
[edit protocols mld traceoptions]
[edit protocols mld-host traceoptions]
[edit protocols mpls label-switched-path oam traceoptions]
[edit protocols mpls label-switched-path primary oam traceoptions]
[edit protocols mpls label-switched-path secondary oam traceoptions]
[edit protocols mpls oam traceoptions]
[edit protocols msdp group peer traceoptions]
[edit protocols msdp group traceoptions]
[edit protocols msdp peer traceoptions]
[edit protocols msdp traceoptions]
[edit protocols neighbor-discovery secure traceoptions]
[edit protocols protocols oam ethernet fnp]
[edit protocols oam ethernet connectivity-fault-management traceoptions]
[edit protocols oam ethernet link-fault-management traceoptions]
[edit protocols oam ethernet lmi traceoptions]
[edit protocols ospf traceoptions]
[edit protocols pim traceoptions]
[edit protocols ppp monitor-session]
[edit protocols ppp traceoptions]
[edit protocols ppp-service traceoptions]
[edit protocols pppoe traceoptions]
[edit protocols rip traceoptions]
[edit protocols ripng traceoptions]
[edit protocols router-advertisement traceoptions]
[edit protocols router-discovery traceoptions]
[edit protocols rsvp lsp-set traceoptions]
[edit protocols rsvp traceoptions]
[edit routing-instances instance vlans domain multicast-snooping-options
traceoptions]
[edit routing-instances instance vlans domain protocols igmp-snooping
traceoptions]
[edit routing-instances instance multicast-snooping-options traceoptions]
[edit routing-instances instance protocols bgp group neighbor traceoptions]
[edit routing-instances instance protocols bgp group traceoptions]
[edit routing-instances instance protocols bgp traceoptions]
[edit routing-instances instance protocols esis traceoptions]
[edit routing-instances instance protocols igmp-snooping traceoptions]
[edit routing-instances instance protocols isis traceoptions]
[edit routing-instances instance protocols l2vpn traceoptions]
[edit routing-instances instance protocols ldp traceoptions]
[edit routing-instances instance protocols msdp group peer traceoptions]
[edit routing-instances instance protocols msdp group traceoptions]
[edit routing-instances instance protocols msdp peer traceoptions]
[edit routing-instances instance protocols msdp traceoptions]
[edit routing-instances instance protocols mvpn traceoptions]
[edit routing-instances instance protocols ospf traceoptions]
[edit routing-instances instance protocols pim traceoptions]
[edit routing-instances instance protocols rip traceoptions]
[edit routing-instances instance protocols ripng traceoptions]
[edit routing-instances instance protocols router-discovery traceoptions]
[edit routing-instances instance protocols vpls traceoptions]
[edit routing-instances instance routing-options multicast traceoptions]
[edit routing-instances instance routing-options traceoptions]
[edit routing-options multicast traceoptions]
[edit routing-options traceoptions]
[edit security idp traceoptions]
[edit security pki traceoptions]
[edit services adaptive-services-pics traceoptions]
[edit services captive-portal-content-delivery]
[edit services l2tp traceoptions]
[edit services server-load-balance traceoptions]
[edit services logging traceoptions]
[edit services mobile-ip traceoptions]
[edit services ssl traceoptions]
[edit system accounting traceoptions]
[edit system auto-configuration traceoptions]
[edit system ddos-protection traceoptions]
[edit system license traceoptions]
[edit system processes app-engine-virtual-machine-management-service
traceoptions]
[edit system processes datapath-trace-service traceoptions]
[edit system processes dhcp-service interface-traceoptions]
[edit system processes dhcp-service traceoptions]
[edit system processes diameter-service traceoptions]
[edit system processes general-authentication-service traceoptions]
[edit system processes mac-validation traceoptions]
[edit system processes mag-service traceoptions]
[edit system processes process-monitor traceoptions]
[edit system processes resource-cleanup traceoptions]
[edit system processes sdk-service traceoptions]
[edit system processes static-subscribers traceoptions]
[edit system services database-replication traceoptions]
[edit system services dhcp traceoptions]
[edit system services local-policy-decision-function traceoptions]
[edit system services outbound-ssh traceoptions]
[edit system services service-deployment traceoptions]
[edit system services subscriber-management traceoptions]
[edit system services subscriber-management-helper traceoptions]
[edit system services web-management traceoptions]
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
trace-control
Can modify trace file settings and configure trace file properties.
Configuration
Hierarchy Levels [edit vlans domain forwarding-options dhcp-relay interface-traceoptions]
[edit vlans domain forwarding-options dhcp-relay traceoptions]
[edit vlans domain multicast-snooping-options traceoptions]
[edit vlans domain protocols igmp-snooping traceoptions]
[edit demux traceoptions]
[edit dynamic-profiles protocols igmp traceoptions]
[edit dynamic-profiles protocols mld traceoptions]
[edit dynamic-profiles protocols oam ethernet link-fault-management
traceoptions]
[dynamic-profiles protocols oam ethernet lmi]
[edit dynamic-profiles protocols router-advertisement traceoptions]
[edit dynamic-profiles protocols oam gre-tunnel traceoptions]
[edit dynamic-profiles routing-instances instance vlans domain
forwarding-options dhcp-relay traceoptions]
[edit dynamic-profiles routing-instances instance vlans domain
multicast-snooping-options traceoptions]
[edit dynamic-profiles routing-instances instance vlans domain protocols
igmp-snooping traceoptions]
[edit dynamic-profiles routing-instances instance forwarding-options dhcp-relay
traceoptions]
[edit dynamic-profiles routing-instances instance multicast-snooping-options
traceoptions]
[edit dynamic-profiles routing-instances instance protocols bgp group neighbor
traceoptions]
[edit dynamic-profiles routing-instances instance protocols bgp group
traceoptions]
[edit dynamic-profiles routing-instances instance protocols bgp traceoptions]
[edit dynamic-profiles routing-instances instance protocols esis traceoptions]
[edit dynamic-profiles routing-instances instance protocols igmp-snooping
traceoptions]
[edit dynamic-profiles routing-instances instance protocols isis traceoptions]
[edit dynamic-profiles routing-instances instance protocols l2vpn traceoptions]
[edit dynamic-profiles routing-instances instance protocols ldp traceoptions]
[edit dynamic-profiles routing-instances instance protocols msdp group peer
traceoptions]
[edit dynamic-profiles routing-instances instance protocols msdp group
traceoptions]
[edit dynamic-profiles routing-instances instance protocols msdp peer
traceoptions]
[edit dynamic-profiles routing-instances instance protocols msdp traceoptions]
[edit dynamic-profiles routing-instances instance protocols mvpn traceoptions]
[edit dynamic-profiles routing-instances instance protocols ospf traceoptions]
[edit dynamic-profiles routing-instances instance protocols pim traceoptions]
[edit dynamic-profiles routing-instances instance protocols rip traceoptions]
[edit dynamic-profiles routing-instances instance protocols ripng traceoptions]
[edit dynamic-profiles routing-instances instance protocols router-discovery
traceoptions]
[edit dynamic-profiles routing-instances instance protocols vpls traceoptions]
[edit dynamic-profiles routing-instances instance routing-options multicast
traceoptions]
[edit dynamic-profiles routing-instances instance routing-options traceoptions]
[edit dynamic-profiles routing-instances instance services mobile-ip
traceoptions]
[edit dynamic-profiles routing-instances instance system services
dhcp-local-server traceoptions]
[edit dynamic-profiles routing-options multicast traceoptions]
[edit fabric protocols bgp group neighbor traceoptions]
[edit fabric protocols bgp group traceoptions]
[edit fabric protocols bgp traceoptions]
[edit fabric routing-instances instance routing-options traceoptions]
[edit fabric routing-options traceoptions]
[edit forwarding-options dhcp-relay interface-traceoptions]
[edit forwarding-options dhcp-relay traceoptions]
[edit jnx-example traceoptions]
[edit logical-systems vlans domain forwarding-options dhcp-relay
interface-traceoptions]
[edit logical-systems vlans domain forwarding-options dhcp-relay traceoptions]
[edit logical-systems vlans domain multicast-snooping-options traceoptions]
[edit logical-systems vlans domain protocols igmp-snooping traceoptions]
[edit logical-systems forwarding-options dhcp-relay traceoptions]
[edit logical-systems protocols ancp traceoptions]
[edit logical-systems protocols bgp group neighbor traceoptions]
[edit logical-systems protocols bgp group traceoptions]
[edit logical-systems protocols bgp traceoptions]
[edit logical-systems protocols dot1x traceoptions]
[edit logical-systems protocols dvmrp traceoptions]
[edit logical-systems protocols esis traceoptions]
[edit logical-systems protocols igmp traceoptions]
[edit logical-systems protocols igmp-host traceoptions]
[edit logical-systems protocols ilmi traceoptions]
[edit logical-systems protocols isis traceoptions]
[edit logical-systems protocols l2circuit traceoptions]
[edit logical-systems protocols l2iw traceoptions]
[edit logical-systems protocols lacp traceoptions]
[edit logical-systems protocols layer2-control traceoptions]
[edit logical-systems protocols ldp traceoptions]
[edit logical-systems protocols mld traceoptions]
[edit logical-systems protocols mld-host traceoptions]
[edit logical-systems protocols mpls label-switched-path oam traceoptions]
[edit logical-systems protocols mpls label-switched-path primary oam
traceoptions]
[edit logical-systems protocols mpls label-switched-path secondary oam
traceoptions]
[edit logical-systems protocols mpls oam traceoptions]
[edit logical-systems protocols msdp group peer traceoptions]
[edit logical-systems protocols msdp group traceoptions]
[edit logical-systems protocols msdp peer traceoptions]
[edit logical-systems protocols msdp traceoptions]
[edit logical-systems protocols neighbor-discovery secure traceoptions]
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
view
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Can view current system-wide, routing table, and protocol-specific values and statistics.
Commands
clear ipv6 router-advertisement
<clear-ipv6-router-advertisement-information>clear l2circuit auto-sensing
<clear-l2ckt-pw-auto-sensing>
clear services redundancy-group
<clear-services-redundancy-group>
clear services redundancy-group statistics
<clear-services-redundancy-group-statistics>
<clear-services-redundancy-set>
clear services service-sets statistics ids
clear services service-sets statistics ids drops
<clear-service-set-ids-drops-statistics>
clear services traffic-load-balance
clear services traffic-load-balance statistics
<clear-service-traffic-load-balance-statistics>
<request-validation-policy>
show
show access-cac interface-set
<get-access-cac-iflset>
show access-security
show access-security router-advertisement-guard
show access-security router-advertisement-guard entries
<show-as-router-advetisement-entry>
show access-security router-advertisement-guard state
<show-as-ra-state>
show access-security router-advertisement-guard statistics
<get-as-router-advertisement-statistics>
show access-security router-advertisement-guard statistics interface
<get-as-router-advertisement-interface>
show accounting
show amt
show amt statistics
<get-amt-statistics>
show amt summary
<get-amt-summary>
show amt tunnel
<get-amt-tunnel-information>
show amt tunnel gateway-address
<get-amt-tunnel-gateway-address>
show amt tunnel tunnel-interface
<get-amt-tunnel-interface>
show analytics collector
<get-analytics-collector>
show ancp
show ancp cos
<get-ancp-cos-information>
show ancp cos last-update
<get-ancp-cos-last-update-information>
<get-aps-interface-information>
show arp
<get-arp-table-information>
show as-path
<get-as-path>
show as-path domain
<get-as-path-domain>
show auto-configuration
show auto-configuration interfaces
show backup-selection
<get-backup-selection>
show backup-selection instance
<get-backup-selection-instance>
show bfd
show bfd session
<get-bfd-session-information>
<get-bgp-summary-information>
show bridge
show bridge domain
<get-bridge-instance-information>
show chassis
show chassis adc
show chassis alarms
<get-alarm-information>
show chassis alarms fpc
<get-fpc-alarm-information>
show chassis alarms satellite
<get-chassis-alarm-satellite-information>
show chassis beacon
get-chassis-beacon-information>
show chassis beacon cb
<get-chassis-cb-beacon-information>
show chassis environment adc
show chassis environment ccg
<get-environment-ccg-information>
show chassis cfeb
<get-cfeb-information>
show chassis cip
show chassis craft-interface
<get-craft-information>
show chassis environment
<get-environment-information>
show chassis environment cb
<get-environment-cb-information>
show chassis environment cip
<get-environment-cip-information>
show chassis environment feb
<get-environment-feb-information>
show chassis environment fan
show chassis environment fpc
<get-environment-fpc-information>
show chassis environment fpc satellite
<get-chassis-environment-fpc-satellite-info>
show chassis environment fpm
<get-environment-fpm-information>
show chassis environment mcs
<get-environment-mcs-information>
show chassis environment pcg
<get-environment-pcg-information>
show chassis environment pdu
<get-environment-pdu-information>
show chassis environment pem
<get-environment-pem-information>
show chassis environment pem satellite
<get-chassis-environment-pem-satellite-info>
show chassis environment psm
show chassis environment psu
<get-environment-psu-information>
show chassis environment routing-engine
<get-environment-re-information>
show chassis environment routing-engine satellite
<get-chassis-environment-re-satellite-info>
show chassis environment satellite
<get-chassis-environment-satellite-information>
show chassis environment scg
<get-environment-scg-information>
show chassis environment service-node
<get-environment-service-node-information>
show chassis environment sfb
show chassis environment sfm
<get-environment-sfm-information>
get-chassis-fan-satellite-information
show chassis feb
<get-feb-brief-information>
<get-chassis-satellite-cluster-route>
show chassis satellite-cluster statistics
<get-chassis-satellite-cluster-statistics>
show chassis scb
<get-scb-information>
show cli
show cli authorization
<get-authorization-information>
show cli commands
show cli commands
show cli directory
<get-current-working-directory>
show cli history
show cloud-analytics
show cloud-analytics connections
<get-cloud-analytics-connections>
show cloud-analytics discovery-service
<get-cloud-analytics-discovery-service>
show cloud-analytics linecard
<get-cloud-analytics-lc>
show cloud-analytics resources
<get-cloud-analytics-resources>
show cloud-analytics resources-sampling
<get-cloud-analytics-resources-sampling>
show cloud-analytics resources-summary
<get-cloud-analytics-resources-summary>
show cloud-analytics sensors
<sensor-information>
show cloud-analytics streaming-policies
<get-cloud-analytics-streaming-policies>
show configuration
show connections
<get-ccc-information>
show database-replication
show database-replication statistics
<get-database-replication-statistics-information>
get-ddos-bfdv6-violations
show ddos-protection protocols bgp
get-ddos-bgp-information
show ddos-protection protocols bgp aggregate
get-ddos-bgp-aggregate
show ddos-protection protocols bgp parameters
get-ddos-bgp-parameters
show ddos-protection protocols bgp statistics
get-ddos-bgp-statistics
show ddos-protection protocols bgp violations
get-ddos-bgp-violations
show ddos-protection protocols bgpv6
get-ddos-bgpv6-information
show ddos-protection protocols bgpv6 aggregate
get-ddos-bgpv6-aggregate
show ddos-protection protocols bgpv6 parameters
get-ddos-bgpv6-parameters
show ddos-protection protocols bgpv6 statistics
get-ddos-bgpv6-statistics
show ddos-protection protocols bgpv6 violations
get-ddos-bgpv6-violations
show ddos-protection protocols bridge-control
<get-ddos-brg-ctrl-information>
show ddos-protection protocols bridge-control aggregate
<get-ddos-brg-ctrl-aggregate>
show ddos-protection protocols bridge-control aggregate culprit-flows
<get-ddos-brg-ctrl-aggregate-flows>
show ddos-protection protocols bridge-control culprit-flows
<get-ddos-brg-ctrl-flows>
show ddos-protection protocols bridge-control flow-detection
<get-ddos-brg-ctrl-flow-parameters>
show ddos-protection protocols bridge-control parameters
<get-ddos-brg-ctrl-parameters>
show ddos-protection protocols bridge-control statistics
<get-ddos-brg-ctrl-statistics>
show ddos-protection protocols bridge-control violations
<get-ddos-brg-ctrl-violations>show ddos-protection protocols demux-autosense
get-ddos-demuxauto-information
show ddos-protection protocols demux-autosense aggregate
get-ddos-demuxauto-aggregate
show ddos-protection protocols demux-autosense parameters
get-ddos-demuxauto-parameters
show ddos-protection protocols demux-autosense statistics
get-ddos-demuxauto-statistics
show ddos-protection protocols demux-autosense violations
get-ddos-demuxauto-violations
show ddos-protection protocols dhcpv4
get-ddos-dhcpv4-information
show ddos-protection protocols dhcpv4 ack
get-ddos-dhcpv4-ack
show ddos-protection protocols dhcpv4 aggregate
get-ddos-dhcpv4-aggregate
show ddos-protection protocols dhcpv4 bad-packets
get-ddos-dhcpv4-bad-pack
show ddos-protection protocols dhcpv4 bootp
get-ddos-dhcpv4-bootp
show ddos-protection protocols dhcpv4 decline
get-ddos-dhcpv4-decline
show ddos-protection protocols dhcpv4 discover
get-ddos-dhcpv4-discover
show ddos-protection protocols dhcpv4 force-renew
get-ddos-dhcpv4-forcerenew
show ddos-protection protocols dhcpv4 inform
get-ddos-dhcpv4-inform
show ddos-protection protocols dhcpv4 lease-active
get-ddos-dhcpv4-leaseact
show ddos-protection protocols dhcpv4 lease-query
get-ddos-dhcpv4-leasequery
show ddos-protection protocols dhcpv4 lease-unassigned
get-ddos-dhcpv4-leaseuna
show ddos-protection protocols dhcpv4 lease-unknown
get-ddos-dhcpv4-leaseunk
show ddos-protection protocols dhcpv4 nak
get-ddos-dhcpv4-nak
show ddos-protection protocols dhcpv4 no-message-type
get-ddos-dhcpv4-no-msgtype
show ddos-protection protocols dhcpv4 offer
get-ddos-dhcpv4-offer
show ddos-protection protocols dhcpv4 offer culprit-flows
show ddos-protection protocols dhcpv4 parameters
get-ddos-dhcpv4-parameters
show ddos-protection protocols dhcpv4 release
get-ddos-dhcpv4-release
show ddos-protection protocols dhcpv4 renew
get-ddos-dhcpv4-renew
show ddos-protection protocols dhcpv4 request
get-ddos-dhcpv4-request
show ddos-protection protocols dhcpv4 statistics
get-ddos-dhcpv4-statistics
show ddos-protection protocols dhcpv4 unclassified
get-ddos-dhcpv4-unclass
show ddos-protection protocols dhcpv4 violations
get-ddos-dhcpv4-violations
show ddos-protection protocols dhcpv4v6
<get-ddos-dhcpv4v6-information>
show ddos-protection protocols dhcpv4v6 aggregate
<get-ddos-dhcpv4v6-aggregate>
show ddos-protection protocols dhcpv4v6 aggregate culprit-flows
<get-ddos-dhcpv4v6-aggregate-flows>
show ddos-protection protocols dhcpv4v6 culprit-flows
<get-ddos-dhcpv4v6-flows>
show ddos-protection protocols dhcpv4v6 flow-detection
<get-ddos-dhcpv4v6-flow-parameters>
show ddos-protection protocols dhcpv4v6 parameters
<get-ddos-dhcpv4v6-parameters>
show ddos-protection protocols dhcpv4v6 statistics
<get-ddos-dhcpv4v6-statistics>
show ddos-protection protocols dhcpv4v6 violations
<get-ddos-dhcpv4v6-violations>
show ddos-protection protocols dhcpv6
get-ddos-dhcpv6-information
show ddos-protection protocols dhcpv6 advertise
get-ddos-dhcpv6-advertise
show ddos-protection protocols dhcpv6 advertise culprit-flows
show ddos-protection protocols dhcpv6 aggregate
get-ddos-dhcpv6-aggregate
show ddos-protection protocols dhcpv6 confirm
get-ddos-dhcpv6-confirm
show ddos-protection protocols dhcpv6 decline
get-ddos-dhcpv6-decline
show ddos-protection protocols dhcpv6 information-request
get-ddos-dhcpv6-info-req
<get-ddos-eth-tcc-violations>
show ddos-protection protocols exceptions
<get-ddos-exception-information>
show ddos-protection protocols exceptions aggregate
<get-ddos-exception-aggregate>
show ddos-protection protocols exceptions aggregate culprit-flows
<get-ddos-exception-aggregate-flows>
show ddos-protection protocols exceptions culprit-flows
<get-ddos-exception-flows>
show ddos-protection protocols exceptions flow-detection
<get-ddos-exception-flow-parameters>
show ddos-protection protocols exceptions mcast-rpf-err
<get-ddos-exception-mcast-rpf>
show ddos-protection protocols exceptions mcast-rpf-err culprit-flows
<get-ddos-exception-mcast-rpf-flows>
show ddos-protection protocols exceptions mtu-exceeded
<get-ddos-exception-mtu-exceed>
show ddos-protection protocols exceptions mtu-exceeded culprit-flows
<get-ddos-exception-mtu-exceed-flows>
show ddos-protection protocols exceptions parameters
<get-ddos-exception-parameters>
show ddos-protection protocols exceptions statistics
<get-ddos-exception-statistics>
show ddos-protection protocols exceptions unclassified
<get-ddos-exception-unclass>
show ddos-protection protocols exceptions unclassified culprit-flows
<get-ddos-exception-unclass-flows>
show ddos-protection protocols exceptions violations
<get-ddos-exception-violations>
get-ddos-ftp-violations
show ddos-protection protocols ftpv6
get-ddos-ftpv6-information
show ddos-protection protocols ftpv6 aggregate
get-ddos-ftpv6-aggregate
show ddos-protection protocols ftpv6 parameters
get-ddos-ftpv6-parameters
show ddos-protection protocols ftpv6 statistics
get-ddos-ftpv6-statistics
show ddos-protection protocols ftpv6 violations
get-ddos-ftpv6-violations
show ddos-protection protocols garp-reply
<get-ddos-garp-reply-information>
show ddos-protection protocols garp-reply aggregate
<get-ddos-garp-reply-aggregate>
show ddos-protection protocols garp-reply aggregate culprit-flows
<get-ddos-garp-reply-aggregate-flows>
show ddos-protection protocols garp-reply culprit-flows
<get-ddos-garp-reply-flows>
show ddos-protection protocols garp-reply flow-detection
<get-ddos-garp-reply-flow-parameters>
show ddos-protection protocols garp-reply parameters
<get-ddos-garp-reply-parameters>
show ddos-protection protocols garp-reply statistics
<get-ddos-garp-reply-statistics>
show ddos-protection protocols garp-reply violations
<get-ddos-garp-reply-violations>
show ddos-protection protocols gre
get-ddos-gre-information
show ddos-protection protocols gre aggregate
get-ddos-gre-aggregate
show ddos-protection protocols gre hbc
<get-ddos-gre-hbc>
show ddos-protection protocols gre hbc culprit-flows
<get-ddos-gre-hbc-flows>
show ddos-protection protocols gre parameters
get-ddos-gre-parameters
show ddos-protection protocols gre punt
<get-ddos-gre-punt>
show ddos-protection protocols gre punt culprit-flows
<get-ddos-gre-punt-flows>
show ddos-protection protocols gre statistics
get-ddos-gre-statistics
show ddos-protection protocols gre violations
get-ddos-gre-violations
show ddos-protection protocols icmp
get-ddos-icmp-information
show ddos-protection protocols icmp aggregate
get-ddos-icmp-aggregate
show ddos-protection protocols icmp parameters
get-ddos-icmp-parameters
show ddos-protection protocols icmp statistics
get-ddos-icmp-statistics
show ddos-protection protocols icmp violations
get-ddos-icmp-violations
show ddos-protection protocols icmpv6
<get-ddos-icmpv6-information>
show ddos-protection protocols icmpv6 aggregate
<get-ddos-icmpv6-aggregate>
show ddos-protection protocols icmpv6 aggregate culprit-flows
<get-ddos-icmpv6-aggregate-flows>
get-ddos-ip-frag-violations
show ddos-protection protocols ip-options
get-ddos-ip-opt-information
show ddos-protection protocols ip-options aggregate
get-ddos-ip-opt-aggregate
show ddos-protection protocols ip-options non-v4v6
<get-ddos-ip-opt-non-v4v6>
show ddos-protection protocols ip-options parameters
get-ddos-ip-opt-parameters
show ddos-protection protocols ip-options router-alert
get-ddos-ip-opt-rt-alert
show ddos-protection protocols ip-options statistics
get-ddos-ip-opt-statistics
show ddos-protection protocols ip-options unclassified
get-ddos-ip-opt-unclass
show ddos-protection protocols ipmc-reserved culprit-flows
<get-ddos-ipmc-reserved-flows>
show ddos-protection protocols ipmc-reserved flow-detection
<get-ddos-ipmc-reserved-flow-parameters>
show ddos-protection protocols ipmc-reserved parameters
<get-ddos-ipmc-reserved-parameters>
show ddos-protection protocols ipmc-reserved statistics
<get-ddos-ipmc-reserved-statistics>
show ddos-protection protocols ipmc-reserved violations
<get-ddos-ipmc-reserved-violations>
show ddos-protection protocols ipmcast-miss
<get-ddos-ipmcast-miss-information>
show ddos-protection protocols ipmcast-miss aggregate
<get-ddos-ipmcast-miss-aggregate>
show ddos-protection protocols ipmcast-miss aggregate culprit-flows
<get-ddos-ipmcast-miss-aggregate-flows>
show ddos-protection protocols ipmcast-miss culprit-flows
<get-ddos-ipmcast-miss-flows>
show ddos-protection protocols ipmcast-miss flow-detection
<get-ddos-ipmcast-miss-flow-parameters>
show ddos-protection protocols ipmcast-miss parameters
<get-ddos-ipmcast-miss-parameters>
show ddos-protection protocols ipmcast-miss statistics
<get-ddos-ipmcast-miss-statistics>
show ddos-protection protocols ipmcast-miss violations
<get-ddos-ipmcast-miss-violations>
show ddos-protection protocols ip-options violations
get-ddos-ip-opt-violations
show ddos-protection protocols ipv4-unclassified
get-ddos-ipv4-uncls-information
show ddos-protection protocols ipv4-unclassified aggregate
get-ddos-ipv4-uncls-aggregate
show ddos-protection protocols ipv4-unclassified parameters
get-ddos-ipv4-uncls-parameters
show ddos-protection protocols ipv4-unclassified statistics
get-ddos-ipv4-uncls-statistics
show ddos-protection protocols ipv4-unclassified violations
get-ddos-ipv4-uncls-violations
show ddos-protection protocols ipv6-unclassified
get-ddos-ipv6-uncls-information
show ddos-protection protocols ipv6-unclassified aggregate
get-ddos-ipv6-uncls-aggregate
show ddos-protection protocols ipv6-unclassified parameters
get-ddos-ipv6-uncls-parameters
show ddos-protection protocols ipv6-unclassified statistics
get-ddos-ipv6-uncls-statistics
<get-ddos-l3dest-miss-statistics>
show ddos-protection protocols l3dest-miss violations
<get-ddos-l3dest-miss-violations>
show ddos-protection protocols l3mc-sgv-hit-icl
<get-ddos-l3mc-sgv-hit-icl-information>
show ddos-protection protocols l3mc-sgv-hit-icl aggregate
<get-ddos-l3mc-sgv-hit-icl-aggregate>
show ddos-protection protocols l3mc-sgv-hit-icl aggregate culprit-flows
<get-ddos-l3mc-sgv-hit-icl-aggregate-flows>
show ddos-protection protocols l3mc-sgv-hit-icl culprit-flows
<get-ddos-l3mc-sgv-hit-icl-flows>
show ddos-protection protocols l3mc-sgv-hit-icl flow-detection
<get-ddos-l3mc-sgv-hit-icl-flow-parameters>
show ddos-protection protocols l3mc-sgv-hit-icl parameters
<get-ddos-l3mc-sgv-hit-icl-parameters>
show ddos-protection protocols l3mc-sgv-hit-icl statistics
<get-ddos-l3mc-sgv-hit-icl-statistics>
show ddos-protection protocols l3mc-sgv-hit-icl violations
<get-ddos-l3mc-sgv-hit-icl-violations>
show ddos-protection protocols l3mtu-fail
<get-ddos-l3mtu-fail-information>
show ddos-protection protocols l3mtu-fail aggregate
<get-ddos-l3mtu-fail-aggregate>
show ddos-protection protocols l3mtu-fail aggregate culprit-flows
<get-ddos-l3mtu-fail-aggregate-flows>
show ddos-protection protocols l3mtu-fail culprit-flows
<get-ddos-l3mtu-fail-flows>
show ddos-protection protocols l3mtu-fail flow-detection
<get-ddos-l3mtu-fail-flow-parameters>
show ddos-protection protocols l3mtu-fail parameters
<get-ddos-l3mtu-fail-parameters>
show ddos-protection protocols l3mtu-fail statistics
<get-ddos-l3mtu-fail-statistics>
show ddos-protection protocols l3mtu-fail violations
<get-ddos-l3mtu-fail-violations>
show ddos-protection protocols l3nhop
<get-ddos-l3nhop-information>
show ddos-protection protocols l3nhop aggregate
<get-ddos-l3nhop-aggregate>
show ddos-protection protocols l3nhop aggregate culprit-flows
<get-ddos-l3nhop-aggregate-flows>
show ddos-protection protocols l3nhop culprit-flows
<get-ddos-l3nhop-flows>
show ddos-protection protocols l3nhop flow-detection
<get-ddos-l3nhop-flow-parameters>
show ddos-protection protocols l3nhop parameters
<get-ddos-l3nhop-parameters>
show ddos-protection protocols l3nhop statistics
<get-ddos-l3nhop-statistics>
show ddos-protection protocols l3nhop violations
<get-ddos-l3nhop-violations>
show ddos-protection protocols lacp
<get-ddos-lacp-information>
show ddos-protection protocols lacp aggregate
<get-ddos-lacp-aggregate>
show ddos-protection protocols lacp parameters
<get-ddos-lacp-parameters>
show ddos-protection protocols lacp statistics
<get-ddos-lacp-statistics>
show ddos-protection protocols lacp violations
<get-ddos-lacp-violations>
<get-ddos-lmpv6-parameters>
show ddos-protection protocols lmpv6 statistics
<get-ddos-lmpv6-statistics>
show ddos-protection protocols lmpv6 violations
<get-ddos-lmpv6-violations>
show ddos-protection protocols localnh
<get-ddos-localnh-information>
show ddos-protection protocols localnh aggregate
<get-ddos-localnh-aggregate>
show ddos-protection protocols localnh aggregate culprit-flows
<get-ddos-localnh-aggregate-flows>
show ddos-protection protocols localnh culprit-flows
<get-ddos-localnh-flows>
show ddos-protection protocols localnh flow-detection
<get-ddos-localnh-flow-parameters>
show ddos-protection protocols localnh parameters
<get-ddos-localnh-parameters>
show ddos-protection protocols localnh statistics
<get-ddos-localnh-statistics>
show ddos-protection protocols localnh violations
<get-ddos-localnh-violations>
show ddos-protection protocols mac-host
<get-ddos-mac-host-information>
show ddos-protection protocols mac-host aggregate
<get-ddos-mac-host-aggregate>
show ddos-protection protocols mac-host aggregate culprit-flows
<get-ddos-mac-host-aggregate-flows>
show ddos-protection protocols mac-host culprit-flows
<get-ddos-mac-host-flows>
show ddos-protection protocols mac-host flow-detection
<get-ddos-mac-host-flow-parameters>
show ddos-protection protocols mac-host parameters
<get-ddos-mac-host-parameters>
show ddos-protection protocols mac-host statistics
<get-ddos-mac-host-statistics>
show ddos-protection protocols mac-host violations
<get-ddos-mac-host-violations>
show ddos-protection protocols martian-address
<get-ddos-martian-address-information>
show ddos-protection protocols martian-address aggregate
<get-ddos-martian-address-aggregate>
show ddos-protection protocols martian-address aggregate culprit-flows
<get-ddos-martian-address-aggregate-flows>
show ddos-protection protocols martian-address culprit-flows
<get-ddos-martian-address-flows>
show ddos-protection protocols martian-address flow-detection
<get-ddos-martian-address-flow-parameters>
show ddos-protection protocols martian-address parameters
<get-ddos-martian-address-parameters>
show ddos-protection protocols martian-address statistics
<get-ddos-martian-address-statistics>
show ddos-protection protocols martian-address violations
<get-ddos-martian-address-violations>
show ddos-protection protocols mac-host
<get-ddos-mac-host-information>
show ddos-protection protocols mac-host aggregate
<get-ddos-mac-host-aggregate>
show ddos-protection protocols mac-host parameters
<get-ddos-mac-host-parameters>
show ddos-protection protocols mac-host statistics
<get-ddos-mac-host-statistics>
<get-ddos-oam-cfm-parameters>
show ddos-protection protocols oam-cfm statistics
<get-ddos-oam-cfm-statistics>
show ddos-protection protocols oam-cfm violations
<get-ddos-oam-cfm-violations>
show ddos-protection protocols oam-lfm
get-ddos-oam-lfm-information
show ddos-protection protocols oam-lfm aggregate
get-ddos-oam-lfm-aggregate
show ddos-protection protocols oam-lfm parameters
get-ddos-oam-lfm-parameters
show ddos-protection protocols oam-lfm statistics
get-ddos-oam-lfm-statistics
show ddos-protection protocols oam-lfm violations
get-ddos-oam-lfm-violations
show ddos-protection protocols ospf
get-ddos-ospf-information
show ddos-protection protocols ospf aggregate
get-ddos-ospf-aggregate
show ddos-protection protocols ospf parameters
get-ddos-ospf-parameters
show ddos-protection protocols ospf statistics
get-ddos-ospf-statistics
show ddos-protection protocols ospf violations
get-ddos-ospf-violations
show ddos-protection protocols ospf-hello
<get-ddos-ospf-hello-information>
show ddos-protection protocols ospf-hello aggregate
<get-ddos-ospf-hello-aggregate>
show ddos-protection protocols ospf-hello aggregate culprit-flows
<get-ddos-ospf-hello-aggregate-flows>
show ddos-protection protocols ospf-hello culprit-flows
<get-ddos-ospf-hello-flows>
show ddos-protection protocols ospf-hello flow-detection
<get-ddos-ospf-hello-flow-parameters>
show ddos-protection protocols ospf-hello parameters
<get-ddos-ospf-hello-parameters>
show ddos-protection protocols ospf-hello statistics
<get-ddos-ospf-hello-statistics>
show ddos-protection protocols ospf-hello violations
<get-ddos-ospf-hello-violations>
show ddos-protection protocols ospfv3v6
get-ddos-ospfv3v6-information
show ddos-protection protocols ospfv3v6 aggregate
get-ddos-ospfv3v6-aggregate
show ddos-protection protocols ospfv3v6 parameters
get-ddos-ospfv3v6-parameters
show ddos-protection protocols ospfv3v6 statistics
get-ddos-ospfv3v6-statistics
show ddos-protection protocols ospfv3v6 violations
get-ddos-ospfv3v6-violations
show ddos-protection protocols parameters
get-ddos-protocols-parameters
show ddos-protection protocols pfe-alive
get-ddos-pfe-alive-information
show ddos-protection protocols pfe-alive aggregate
get-ddos-pfe-alive-aggregate
show ddos-protection protocols pfe-alive parameters
get-ddos-pfe-alive-parameters
show ddos-protection protocols pfe-alive statistics
get-ddos-pfe-alive-statistics
<get-ddos-pkt-inject-aggregate-flows>
show ddos-protection protocols pkt-inject culprit-flows
<get-ddos-pkt-inject-flows>
show ddos-protection protocols pkt-inject flow-detection
<get-ddos-pkt-inject-flow-parameters>
show ddos-protection protocols pkt-inject parameters
<get-ddos-pkt-inject-parameters>
show ddos-protection protocols pkt-inject statistics
<get-ddos-pkt-inject-statistics>
show ddos-protection protocols pkt-inject violations
<get-ddos-pkt-inject-violations>
get-ddos-ppp-violations
show ddos-protection protocols pppoe
get-ddos-pppoe-information
show ddos-protection protocols pppoe aggregate
get-ddos-pppoe-aggregate
show ddos-protection protocols pppoe padi
get-ddos-pppoe-padi
show ddos-protection protocols pppoe padm
get-ddos-pppoe-padm
show ddos-protection protocols pppoe padn
get-ddos-pppoe-padn
show ddos-protection protocols pppoe pado
get-ddos-pppoe-pado
show ddos-protection protocols pppoe padr
get-ddos-pppoe-padr
show ddos-protection protocols pppoe pads
get-ddos-pppoe-pads
show ddos-protection protocols pppoe padt
get-ddos-pppoe-padt
show ddos-protection protocols pppoe parameters
get-ddos-pppoe-parameters
show ddos-protection protocols pppoe statistics
get-ddos-pppoe-statistics
show ddos-protection protocols pppoe violations
get-ddos-pppoe-violations
show ddos-protection protocols proto-802-1x
<get-ddos-8021x-information>
show ddos-protection protocols proto-802-1x aggregate
<get-ddos-8021x-aggregate>
show ddos-protection protocols proto-802-1x aggregate culprit-flows
get-ddos-8021x-aggregate-flows
show ddos-protection protocols proto-802-1x culprit-flows
<get-ddos-8021x-flows>
show ddos-protection protocols proto-802-1x flow-detection
<get-ddos-8021x-flow-parameters>
show ddos-protection protocols proto-802-1x parameters
<get-ddos-8021x-parameters>
show ddos-protection protocols proto-802-1x statistics
<get-ddos-8021x-statistics>
show ddos-protection protocols proto-802-1x violations
<get-ddos-8021x-violations>
show ddos-protection protocols ptp
get-ddos-ptp-information
show ddos-protection protocols ptp aggregate
get-ddos-ptp-aggregate
show ddos-protection protocols ptp aggregate culprit-flows
show ddos-protection protocols ptp parameters
get-ddos-ptp-parameters
show ddos-protection protocols ptp statistics
get-ddos-ptp-statistics
show ddos-protection protocols ptp violations
get-ddos-ptp-violations
show ddos-protection protocols ptpv6
<get-ddos-ptpv6-information>
show ddos-protection protocols ptpv6 aggregate
<get-ddos-ptpv6-aggregate>
show ddos-protection protocols ptpv6 aggregate culprit-flows
<get-ddos-ptpv6-aggregate-flows>
show ddos-protection protocols ptpv6 culprit-flows
<get-ddos-ptpv6-flows>
show ddos-protection protocols ptpv6 flow-detection
<get-ddos-ptpv6-flow-parameters>
show ddos-protection protocols ptpv6 parameters
<get-ddos-ptpv6-parameters>
show ddos-protection protocols ptpv6 statistics
<get-ddos-ptpv6-statistics>
show ddos-protection protocols ptpv6 violations
<get-ddos-ptpv6-violations>
show ddos-protection protocols pvstp
get-ddos-pvstp-information
show ddos-protection protocols pvstp aggregate
get-ddos-pvstp-aggregate
show ddos-protection protocols pvstp parameters
get-ddos-pvstp-parameters
show ddos-protection protocols pvstp statistics
get-ddos-pvstp-statistics
show ddos-protection protocols pvstp violations
get-ddos-pvstp-violations
show ddos-protection protocols radius
get-ddos-radius-information
show ddos-protection protocols radius accounting
get-ddos-radius-account
show ddos-protection protocols radius aggregate
get-ddos-radius-aggregate
show ddos-protection protocols radius accounting culprit-flows
show ddos-protection protocols radius authorization
get-ddos-radius-auth
show ddos-protection protocols radius parameters
get-ddos-radius-parameters
show ddos-protection protocols radius server
get-ddos-radius-server
show ddos-protection protocols radius statistics
get-ddos-radius-statistics
show ddos-protection protocols radius violations
get-ddos-radius-violations
show ddos-protection protocols re-services
<get-ddos-re-services-information>
show ddos-protection protocols re-services aggregate
<get-ddos-re-services-aggregate>
show ddos-protection protocols re-services aggregate culprit-flows
<get-ddos-re-services-aggregate-flows>
show ddos-protection protocols re-services captive-portal
<get-ddos-re-services-captive-portal>
show ddos-protection protocols re-services captive-portal culprit-flows
<get-ddos-re-services-captive-portal-flows>
show ddos-protection protocols re-services culprit-flows
<get-ddos-re-services-flows>
show ddos-protection protocols re-services flow-detection
<get-ddos-re-services-flow-parameters>
show ddos-protection protocols re-services parameters
<get-ddos-re-services-parameters>
show ddos-protection protocols re-services statistics
<get-ddos-re-services-statistics>
show ddos-protection protocols re-services violations
<get-ddos-re-services-violations>
show ddos-protection protocols re-services-v6
<get-ddos-re-services-v6-information>
show ddos-protection protocols re-services-v6 aggregate
<get-ddos-re-services-v6-aggregate>
show ddos-protection protocols re-services-v6 aggregate culprit-flows
<get-ddos-re-services-v6-aggregate-flows>
show ddos-protection protocols re-services-v6 captive-portal
<get-ddos-re-services-v6-captive-portal-v6>
show ddos-protection protocols re-services-v6 captive-portal culprit-flows
<get-ddos-re-services-v6-captive-portal-v6-flows>
show ddos-protection protocols re-services-v6 culprit-flows
<get-ddos-re-services-v6-flows>
show ddos-protection protocols re-services-v6 flow-detection
<get-ddos-re-services-v6-flow-parameters>
show ddos-protection protocols re-services-v6 parameters
<get-ddos-re-services-v6-parameters>
show ddos-protection protocols re-services-v6 statistics
<get-ddos-re-services-v6-statistics>
show ddos-protection protocols re-services-v6 violations
<get-ddos-re-services-v6-violations>
show ddos-protection protocols redirect
get-ddos-redirect-information
show ddos-protection protocols redirect aggregate
get-ddos-redirect-aggregate
show ddos-protection protocols redirect parameters
get-ddos-redirect-parameters
show ddos-protection protocols redirect statistics
get-ddos-redirect-statistics
show ddos-protection protocols redirect violations
get-ddos-redirect-violations
<get-ddos-sample-dest-flow-parameters>
show ddos-protection protocols sample-dest parameters
<get-ddos-sample-dest-parameters>
show ddos-protection protocols sample-dest statistics
<get-ddos-sample-dest-statistics>
show ddos-protection protocols sample-dest violations
<get-ddos-sample-dest-violations>
show ddos-protection protocols sample-source
<get-ddos-sample-source-information>
show ddos-protection protocols sample-source aggregate
<get-ddos-sample-source-aggregate>
show ddos-protection protocols sample-source aggregate culprit-flows
<get-ddos-sample-source-aggregate-flows>
show ddos-protection protocols sample-source culprit-flows
<get-ddos-sample-source-flows>
show ddos-protection protocols sample-source flow-detection
<get-ddos-sample-source-flow-parameters>
show ddos-protection protocols sample-source parameters
<get-ddos-sample-source-parameters>
show ddos-protection protocols sample-source statistics
<get-ddos-sample-source-statistics>
show ddos-protection protocols sample-source violations
<get-ddos-sample-source-violations>
show ddos-protection protocols services aggregate
<get-ddos-services-aggregate>
show ddos-protection protocols services parameters
<get-ddos-services-parameters>
show ddos-protection protocols services statistics
<get-ddos-services-statistics>
show ddos-protection protocols syslog
<get-ddos-syslog-information>
show ddos-protection protocols syslog aggregate
<get-ddos-syslog-aggregate>
show ddos-protection protocols syslog aggregate culprit-flows
<get-ddos-syslog-aggregate-flows>
show ddos-protection protocols syslog culprit-flows
<get-ddos-syslog-flows>
show ddos-protection protocols syslog flow-detection
<get-ddos-syslog-flow-parameters>
show ddos-protection protocols syslog parameters
<get-ddos-syslog-parameters>
show ddos-protection protocols syslog statistics
<get-ddos-syslog-statistics>
show ddos-protection protocols syslog violations
<get-ddos-syslog-violations>
show ddos-protection protocols services violations
get-ddos-services-violations
show ddos-protection protocols snmp
get-ddos-snmp-information
show ddos-protection protocols snmp aggregate
get-ddos-snmp-aggregate
show ddos-protection protocols snmp aggregate culprit-flows
show ddos-protection protocols snmp parameters
get-ddos-snmp-parameters
show ddos-protection protocols snmp statistics
get-ddos-snmp-statistics
show ddos-protection protocols snmp violations
get-ddos-snmp-violations
show ddos-protection protocols snmpv6
get-ddos-snmpv6-information
show ddos-protection protocols snmpv6 aggregate
get-ddos-snmpv6-aggregate
show ddos-protection protocols snmpv6 aggregate culprit-flows
show ddos-protection protocols snmpv6 parameters
get-ddos-snmpv6-parameters
show ddos-protection protocols snmpv6 statistics
get-ddos-snmpv6-statistics
show ddos-protection protocols snmpv6 violations
get-ddos-snmpv6-violations
show ddos-protection protocols ssh
get-ddos-ssh-information
show ddos-protection protocols ssh aggregate
get-ddos-ssh-aggregate
show ddos-protection protocols ssh parameters
get-ddos-ssh-parameters
show ddos-protection protocols ssh statistics
get-ddos-ssh-statistics
show ddos-protection protocols ssh violations
get-ddos-ssh-violations
show ddos-protection protocols sshv6
get-ddos-sshv6-information
show ddos-protection protocols sshv6 aggregate
get-ddos-sshv6-aggregate
show ddos-protection protocols sshv6 parameters
get-ddos-sshv6-parameters
show ddos-protection protocols sshv6 statistics
<get-ddos-sshv6-statistics>
show ddos-protection protocols sshv6 violations
<get-ddos-sshv6-violations>
show ddos-protection protocols statistics
<get-ddos-protocols-statistics>
show ddos-protection protocols stp
<get-ddos-stp-information>
show ddos-protection protocols stp aggregate
<get-ddos-stp-aggregate>
show ddos-protection protocols stp parameters
<get-ddos-stp-parameters>
show ddos-protection protocols stp statistics
<get-ddos-stp-statistics>
show ddos-protection protocols stp violations
<get-ddos-stp-violations>
show ddos-protection protocols tacacs
<get-ddos-tacacs-information>
show ddos-protection protocols tacacs aggregate
<get-ddos-tacacs-aggregate>
show ddos-protection protocols tacacs parameters
<get-ddos-tacacs-parameters>
show ddos-protection protocols tacacs statistics
<get-ddos-tacacs-statistics>
show ddos-protection protocols tacacs violations
<get-ddos-tacacs-violations>
<get-ddos-ttl-parameters>
show ddos-protection protocols ttl statistics
<get-ddos-ttl-statistics>
show ddos-protection protocols ttl violations
<get-ddos-ttl-violations>
show ddos-protection protocols tunnel-fragment
<get-ddos-tun-frag-information>
show ddos-protection protocols tunnel-fragment aggregate
<get-ddos-tun-frag-aggregate>
show ddos-protection protocols tunnel-fragment aggregate culprit-flows
show ddos-protection protocols tunnel-fragment parameters
<get-ddos-tun-frag-parameters>
show ddos-protection protocols tunnel-fragment statistics
<get-ddos-tun-frag-statistics>
show ddos-protection protocols tunnel-fragment violations
<get-ddos-tun-frag-violations>
show ddos-protection protocols tunnel-ka
<get-ddos-tunnel-ka-information>
show ddos-protection protocols tunnel-ka aggregate
<get-ddos-tunnel-ka-aggregate>
show ddos-protection protocols tunnel-ka aggregate culprit-flows
<get-ddos-tunnel-ka-aggregate-flows>
show ddos-protection protocols tunnel-ka culprit-flows
<get-ddos-tunnel-ka-flows>
show ddos-protection protocols tunnel-ka flow-detection
<get-ddos-tunnel-ka-flow-parameters>
show ddos-protection protocols tunnel-ka parameters
<get-ddos-tunnel-ka-parameters>
show ddos-protection protocols tunnel-ka statistics
<get-ddos-tunnel-ka-statistics>
show ddos-protection protocols tunnel-ka violations
<get-ddos-tunnel-ka-violations>
show ddos-protection protocols unknown-l2mc
<get-ddos-unknown-l2mc-information>
show ddos-protection protocols unknown-l2mc aggregate
<get-ddos-unknown-l2mc-aggregate>
show ddos-protection protocols unknown-l2mc aggregate culprit-flows
<get-ddos-unknown-l2mc-aggregate-flows>
show ddos-protection protocols unknown-l2mc culprit-flows
<get-ddos-unknown-l2mc-flows>
show ddos-protection protocols unknown-l2mc flow-detection
<get-ddos-unknown-l2mc-flow-parameters>
show ddos-protection protocols unknown-l2mc parameters
<get-ddos-unknown-l2mc-parameters>
show ddos-protection protocols unknown-l2mc statistics
<get-ddos-unknown-l2mc-statistics>
show ddos-protection protocols unknown-l2mc violations
<get-ddos-unknown-l2mc-violations>
show ddos-protection protocols unclassified
<get-ddos-uncls-information>
show ddos-protection protocols unclassified aggregate
<get-ddos-uncls-aggregate>
show ddos-protection protocols unclassified parameters
<get-ddos-uncls-parameters>
show ddos-protection protocols unclassified resolve-v4
show ddos-protection protocols unclassified resolve-v4 culprit-flows
show ddos-protection protocols unclassified resolve-v6
show ddos-protection protocols unclassified resolve-v6 culprit-flows
show ddos-protection protocols unclassified statistics
<get-ddos-uncls-statistics>
show ddos-protection protocols unclassified violations
<get-ddos-uncls-violations>
show ddos-protection protocols urpf-fail
<get-ddos-urpf-fail-information>
show ddos-protection protocols urpf-fail aggregate
<get-ddos-urpf-fail-aggregate>
show ddos-protection protocols urpf-fail aggregate culprit-flows
<get-ddos-urpf-fail-aggregate-flows>
show ddos-protection protocols urpf-fail culprit-flows
<get-ddos-urpf-fail-flows>
show ddos-protection protocols urpf-fail flow-detection
<get-ddos-urpf-fail-flow-parameters>
show ddos-protection protocols urpf-fail parameters
<get-ddos-urpf-fail-parameters>
show ddos-protection protocols urpf-fail statistics
<get-ddos-urpf-fail-statistics>
show ddos-protection protocols urpf-fail violations
<get-ddos-urpf-fail-violations>
show ddos-protection protocols vcipc-udp
<get-ddos-vcipc-udp-information>
show ddos-protection protocols vcipc-udp aggregate
<get-ddos-vcipc-udp-aggregate>
show ddos-protection protocols vcipc-udp aggregate culprit-flows
<get-ddos-vcipc-udp-aggregate-flows>
show ddos-protection protocols vcipc-udp culprit-flows
<get-ddos-vcipc-udp-flows>
show ddos-protection protocols vcipc-udp flow-detection
<get-ddos-vcipc-udp-flow-parameters>
show ddos-protection protocols vcipc-udp parameters
<get-ddos-vcipc-udp-parameters>
show ddos-protection protocols vcipc-udp statistics
<get-ddos-vcipc-udp-statistics>
show ddos-protection protocols vcipc-udp violations
<get-ddos-vcipc-udp-violations>
show ddos-protection protocols violations
get-ddos-protocols-violations
show ddos-protection protocols virtual-chassis
get-ddos-vchassis-information
show ddos-protection protocols virtual-chassis aggregate
get-ddos-vchassis-aggregate
show ddos-protection protocols virtual-chassis aggregate culprit-flows
show ddos-protection protocols virtual-chassis control-high
get-ddos-vchassis-control-hi
show ddos-protection protocols virtual-chassis control-low
get-ddos-vchassis-control-lo
show ddos-protection protocols virtual-chassis parameters
get-ddos-vchassis-parameters
show ddos-protection protocols virtual-chassis statistics
get-ddos-vchassis-statistics
show ddos-protection protocols virtual-chassis unclassified
get-ddos-vchassis-unclass
show ddos-protection protocols virtual-chassis vc-packets
get-ddos-vchassis-vc-packets
show ddos-protection protocols virtual-chassis vc-ttl-errors
get-ddos-vchassis-vc-ttl-err
show ddos-protection protocols virtual-chassis violations
get-ddos-vchassis-violations
show ddos-protection protocols vrrp
get-ddos-vrrp-information
show ddos-protection protocols vrrp aggregate
get-ddos-vrrp-aggregate
show ddos-protection protocols vrrp aggregate culprit-flows
show dhcpv6
show dhcpv6 client
show dhcpv6 client binding
get-dhcpv6-client-binding-information
show dhcpv6 client binding interface
<get-dhcpv6-client-binding-information-by-interface>
show dhcpv6 client statistics
<get-dhcpv6-client-statistics-information>
show dhcpv6 proxy-client
show dhcpv6 proxy-client binding
show dhcpv6 proxy-client statistics
<get-proxy-dhcpv6-client-statistics-information>
show dhcpv6 relay
show dhcpv6 relay binding
<get-dhcpv6-relay-binding-information>
show dhcpv6 relay binding interface
<get-dhcpv6-relay-binding-interface>
show dhcpv6 relay binding lease-time-violation
<get-dhcpv6-relay-binding-ltv-information>
show ike
show ike security-associations
<get-ike-security-associations-information>
show ilmi
<get-ilmi-information>
show ilmi interface
<get-ilmi-interface-information>
show ilmi statistics
<get-ilmi-statistics>
show ingress-replication
<get-ingress-replication-information>
show interfaces
<get-interface-information>
show interfaces anchor-group
show interfaces controller
<get-interface-controller-information>
show interfaces destination-class
<get-destination-class-statistics>
show ipv6
show ipv6 neighbors
<get-ipv6-nd-information>
show isis
show isis adjacency
<get-isis-adjacency-information>
show l2-learning
show l2-learning backbone-instance
<get-l2-learning-backbone-instance>
show l2-learning evpn
show l2-learning evpn arp-statistics
<get-evpn-arp-statistics>
show l2-learning evpn arp-statistics interface
<get-evpn-arp-statistics-interface>
show l2-learning evpn nd-statistics
<get-evpn-nd-statistics>
show l2-learning evpn nd-statistics interface
<get-evpn-nd-statistics-interface>
show l2-learning global-information
<get-l2-learning-global-information>
show l2-learning global-mac-count
<get-l2-learning-global-mac-count>
show l2-learning instance
<get-l2-learning-routing-instances>
show l2-learning interface
<get-l2-learning-interface-information>
show l2-learning mac-move-buffer
<get-l2-learning-mac-move-buffer-information>
show l2-learning provider-instance
<get-l2-learning-provider-instance>
show l2-learning redundancy-groups
<get-l2-learning-redundancy-groups>
show l2-learning remote-backbone-edge-bridges
<get-l2-learning-remote-backbone-edge-bridges>
show l2-learning vxlan-tunnel-end-point
show l2-learning vxlan-tunnel-end-point esi
<get-l2-learning-vxlan-esi-info>show l2-learning vxlan-tunnel-end-point remote
<get-l2-learning-vxlan-rvtep-info>
show l2-learning vxlan-tunnel-end-point remote ip
<get-l2-learning-vxlan-rvtep-ip-information>
show l2-learning vxlan-tunnel-end-point remote mac-table
<get-l2-learning-vxlan-rvtep-mactable-information>
show l2-learning vxlan-tunnel-end-point remote vtep-source-interface
<get-l2-learning-vxlan-remote-svtep-ip-information>
show l2-learning vxlan-tunnel-end-point source
<get-l2-learning-vxlan-svtep-info>
show l2-learning vxlan-tunnel-end-point source ip
<get-l2-learning-vxlan-svtep-ip-information>
show l2circuit
show l2circuit auto-sensing
<get-l2ckt-pw-auto-sensing-information>
show l2circuit connections
<get-l2ckt-connection-information>
show l2cpd
show l2cpd task
<get-l2cpd-task-information>
show l2cpd task io
<get-l2cpd-tasks-io-statistics>
show l2cpd task memory
<get-l2cpd-task-memory>
show l2cpd task replication
<get-l2cpd-replication-information>
show l2vpn
show l2vpn connections
<get-l2vpn-connection-information>
show lacp
show lacp interfaces
<get-lacp-interface-information>
show lacp statistics
show lacp statistics interfaces
<get-lacp-interface-statistics>
show lacp timeouts
show ldp
show ldp database
<get-ldp-database-information>
show link-management
<get-lm-information>
show lldp
<get-lldp-information>
show mac-rewrite
show mac-rewrite interface
<get-mac-rewrite-interface-information>
show mld
show mld group
<get-mld-group-information>
<get-mld-snooping-membership-information>
show mld snooping membership bridge-domain
<get-mld-snooping-bridge-domain-membership>
show mld snooping membership vlan
<get-mld-snooping-vlan-membership>
show mld snooping statistics
<get-mld-snooping-statistics-information>
show mld snooping statistics bridge-domain
<get-mld-snooping-bridge-domain-statistics>
show mld snooping statistics vlan
<get-mld-snooping-vlan-statistics>
show mld statistics
<get-mld-statistics-information>
show mobile-ip
show mobile-ip home-agent
show mobile-ip home-agent binding
<get-mip-binding-information>
show mpls
show mpls abstract-hop-membership
<get-mpls-abstract-hop-membership-information>
show mpls admin-groups
<get-mpls-admin-group-information>
<get-msdp-source-active-information>
show mvpn
show mvpn c-multicast
<get-mvpn-c-multicasti-route>
show mvpn instance
<get-mvpn-instance-information>
show network-access
show network-access aaa
show network-access aaa radius-servers
<get-radius-servers-table>
show network-access aaa statistics
<get-aaa-module-statistics>
show nonstop-routing
<get-nonstop-routing-information>
show ntp
show openflow
show openflow capability
show openflow controller
show openflow filters
show openflow flows
show openflow interfaces
show openflow statistics
show openflow statistics flows
show openflow statistics interfaces
show openflow statistics packet
show ospf
show ospf backup
show ospf backup coverage
<get-ospf-backup-coverage-information>
show ospf3
show ospf3 backup
show ospf3 backup coverage
<get-ospf3-backup-coverage-information>
show pim
show pim bidirectional
show pim bidirectional df-election
<get-pim-bidir-df-election-information>
show pim bidirectional df-election interface
<get-pim-bidir-df-election-interface-information>
show pim bootstrap
<get-pim-bootstrap-information>
show policy
show policy conditions
show policy damping
show ppp
show ppp address-pool
<get-ppp-address-pool-information>
show pppoe
show pppoe interfaces
<get-pppoe-interface-information>
show pppoe lockout
<get-pppoe-lockout-information>
show pppoe lockout atm-identifier
<get-pppoe-lockout-atm-information>
show pppoe lockout vlan-identifier
<get-pppoe-lockout-vlan-information>
show protection-group
show protection-group ethernet-aps
<show-protection-group-ethernet-aps>
show protection-group ethernet-ring
show protection-group ethernet-ring aps
<get-raps-pdu-information>
show protection-group ethernet-ring data-channel
<get-ring-data-channel-information>
show protection-group ethernet-ring interface
<get-ring-interface-information>
show protection-group ethernet-ring node-state
<get-raps-state-machine-information>
show protection-group ethernet-ring node-state
show protection-group ethernet-ring statistics
<get-ring-tatistics>
show protection-group ethernet-ring vlan
<get-ring-vlan-information>
show ptp
show ptp clock
get-ptp-clock>
show ptp global-information
get-ptp-global-information>
show ptp hybrid
show ptp hybrid config
<get-ptp-hybrid-mapping>
show ptp hybrid status
<get-ptp-hybrid-status>
show ptp last-tod-update
<get-last-tod-update>
show ptp lock-status
get-ptp-lock-status>
show ptp master
<get-ptp-master>
show ptp path-trace
<get-ptp-path-trace>
show ptp port
<get-ptp-port>
show ptp quality-level-mapping
<get-ptp-quality-level-mapping>
show ptp slave
<get-ptp-slave>
show ptp stateful
<get-ptp-stateful>
show ptp statistics
<get-ptp-statistics>
show r2cp
show r2cp interfaces
<get-r2cp-interface-information>
show r2cp radio
<get-r2cp-radio-information>
show r2cp sessions
<get-r2cp-session-information>
show r2cp statistics
<get-r2cp-statistics>
show redundant-power-system
show redundant-power-system led
show redundant-power-system multi-backup
<get-rps-scale-information>
show redundant-power-system network
<get-rps-network-information>
show redundant-power-system power-supply
show redundant-power-system status
show redundant-power-system upgrade
<get-rps-upgrade-information>
show redundant-power-system version
show rip
show rip general-statistics
<get-rip-general-statistics-information>
show rsvp
show rsvp interface
<get-rsvp-interface-information>
<get-rsvp-session-information>
show sap
show sap listen
<get-sap-listen-information>
show security group-vpn member kek
show security group-vpn member kek security-associations
<get-gvpn-kek-security-associations-information>
show services
show services accounting
<get-service-accounting-information>
<get-appid-application-group-detail>
show services application-identification group summary
<get-appid-application-group-summary>
show services application-identification statistics
show services application-identification statistics application-groups
<get-appid-application-group-statistics>
show services application-identification statistics applications
<get-appid-application-statistics>
show services application-identification status
<get-appid-staus-information>
show services application-identification version
<get-appid-package-version>
<get-inline-sfw-statistics-information>
show services ipsec-vpn
show services ipsec-vpn ike
show services ipsec-vpn ike security-associations
<get-ike-services-security-associations-information>
<get-service-pgcp-conversation-information-gateway>
<twamp-get-probe-results>
show services rpm twamp client session
<twamp-client-test-session>
show services rpm twamp server
<twamp-server-information>
show services rpm twamp server connection
<twamp-server-connection-information>
show services rpm twamp server session
<twamp-server-session-information>
show services server-load-balance
show services server-load-balance external-manager
show services server-load-balance external-manager information
show services server-load-balance external-manager statistics
<get-external-manager-statistics-information>
show services server-load-balance hash-table
<get-hash-table-information>
show services server-load-balance health-monitor
show services server-load-balance health-monitor information
<get-real-server-health-monitor-information>
show services server-load-balance health-monitor statistics
<get-real-server-health-monitor-statistics-information>
show services server-load-balance real-server
show services server-load-balance real-server statistics
<get-real-server-statistics-information>
show services server-load-balance real-server-group
show services server-load-balance real-server-group information
<get-real-server-group-information>
show services server-load-balance real-server-group statistics
<get-real-server-group-statistics-information>
show services server-load-balance sticky
<get-sticky-table-information>
show services server-load-balance virtual-server
show services server-load-balance virtual-server information
<get-virtual-server-information>
show services server-load-balance virtual-server statistics
<get-virtual-server-statistics-information>
show services service-identification
show services service-identification header-redirect
show services service-identification header-redirect statistics
<get-header-redirect-set-statistics-information>
<get-service-set-drop-flow-statistics>
show services service-sets statistics ids
show services service-sets statistics ids drops
<get-service-set-ids-drops-statistics>
show services service-sets statistics jflow-log
<get-service-set-jflow-log-statistics>
show services service-sets statistics packet-drops
<get-service-set-packet-drop-statistics>
<get-service-subs-analysis-information>
show services subscriber
show services subscriber bandwidth
show services subscriber bandwidth client-id
<get-services-subscriber-bandwidth-by-session-id>
show services subscriber bandwidth interface
<get-services-subscriber-bandwidth-by-interface>
show services subscriber bandwidth ip-address
<get-services-subscriber-bandwidth-by-ip-address>
show services subscriber bandwidth service-interface
<get-services-subscriber-bandwidth-by-service-interface>
show services subscriber dynamic-policies
<get-services-subscriber-dynamic-policies>
show services subscriber flows
<get-services-subscriber-flows>
show services subscriber sessions
<get-services-subscriber-session>
show services subscriber statistics
<get-services-subscriber-statistics>
show services traffic-detection-function
show services traffic-detection-function hcm
show services traffic-detection-function hcm statistics
<get-service-tdf-hcm-sessions-stats>
show services traffic-detection-function sessions
<get-service-tdf-sessions-information>
show services traffic-load-balance
show services traffic-load-balance statistics
<get-traffic-load-balance-statistics>
show services unified-access-control
show services unified-access-control authentication-table
<get-uac-auth-table>
show services unified-access-control counters
<get-uac-counters>
show services unified-access-control policies
<get-uac-policies>
show services unified-access-control roles
<get-uac-role-entries>
show services unified-access-control status
<get-uac-status>
show services video-monitoring
<get-service-video-monitoring-information>
show services video-monitoring mdi
<get-service-video-monitoring-mdi-information
show services video-monitoring mdi alarms
<get-services-video-monitoring-mdi-alarms-information>
show services video-monitoring mdi alarms errors
<get-services-video-monitoring-mdi-alarms-errors-information>
show services video-monitoring mdi alarms stats
<get-services-video-monitoring-mdi-alarms-stats-information>
show services video-monitoring mdi errors>
<get-service-video-monitoring-mdi-errors-information>
show services video-monitoring mdi flow
<get-service-video-monitoring-mdi-flows-information>
show services video-monitoring mdi stats
<get-service-video-monitoring-mdi-stats-information>
show shmlog
show shmlog argument-mappings
<get-shmlog-argument-mappings>
show shmlog configuration
<show-shmlog-configuration>
show shmlog entries
<show-shmlog-entries>
show shmlog logs-summary
<show-shmlog-logsummary>
show shmlog statistics
<show-shmlog-statistics>
show snmp
show snmp health-monitor
<get-health-monitor-information>
show snmp v3
<get-snmp-v3-information>
show spanning-tree
show spanning-tree bridge
<get-stp-bridge-information>
show spanning-tree interface
<get-stp-interface-information>
show spanning-tree mstp
show spanning-tree mstp configuration
<get-mstp-configuration-information>
show spanning-tree statistics
<get-stp-interface-statistics>
show spanning-tree statistics bridge
show spanning-tree statistics interface
show spanning-tree statistics routing-instance
<get-stp-routing-instance-statistics>
show spanning-tree stp-buffer
show spanning-tree stp-buffer see-all
show ssl-certificates
<get-ssl-certificate-information>
show static-subscribers
show static-subscribers sessions
<show subscribers
<get-subscribers>
show subscribers summary
<get-subscribers-summary>
<get-syslog-filenames>
show synchronous-ethernet
show synchronous-ethernet esmc
show synchronous-ethernet esmc statistics
show synchronous-ethernet esmc transmit
show synchronous-ethernet global-information
show system
show system alarms
<get-system-alarm-information>
<get-license-key-information>
<get-software-installation-status>
show system software recovery-package
show system software rollback
<show-package-rollback>
<get-lrmuxd-task-memory>
show task memory
show task replication
<get-routing-task-replication-state>
show task snooping
show task snooping io
show task snooping memory
<get-snooping-task-memory-information>
show ted
show ted database
<get-ted-database-information>
show virtual-chassis
show virtual-chassis active-topology
<get-virtual-chassis-active-topology>
show virtual-chassis device-topology
<get-virtual-chassis-device-topology>
show virtual-chassis fast-failover
<get-virtual-chassis-fast-failover>
show virtual-chassis heartbeat
<get-virtual-chassis-heartbeat-information>
show virtual-chassis login
<get-virtual-chassis-login>
show virtual-chassis mode
<get-virtual-chassis-mode-information>
show virtual-chassis protocol
show virtual-chassis protocol adjacency
<get-virtual-chassis-adjacency-information>
show virtual-chassis protocol database
<get-virtual-chassis-database-information>
show virtual-chassis protocol interface
<get-virtual-chassis-interface-information>
show virtual-chassis protocol route
<get-virtual-chassis-route-information>
show virtual-chassis protocol statistics
<get-virtual-chassis-statistics-information>
show virtual-chassis status
<get-virtual-chassis-information>
show virtual-chassis vc-path
<get-virtual-chassis-packet-path>
show virtual-chassis vc-port
<get-virtual-chassis-port-information>
show virtual-chassis vc-port diagnostics
show virtual-chassis vc-port diagnostics optics
<get-virtual-chassis-optics-diagnostics>
show virtual-chassis vc-port lag-hash
<get-virtual-chassis-port-lag-hash-information>
show virtual-chassis vc-port statistics
<get-virtual-chassis-port-statistics>
show vlans
<get-vlan-information>
show vlans operational
<get-operational-vlan-instance-information>
show vlans satellite
<get-satellite-control-bridge-domain>
show vmhost
show vmhost bridge
<get-vmhost-bridge-information>
show vmhost crash
<get-vmhost-crash-information>
show vmhost hardware
<get-vmhost-hardware>
show vmhost information
<get-vmhost-information>
show vmhost logs
<get-vmhost-logs-information>
show vmhost management-if
<get-vmhost-management-if-info>
show vmhost netstat
<get-vmhost-netstat>
show vmhost processes
<get-vmhost-processes-information>
show vmhost resource-usage
<get-vmhost-resource-usage-information>
show vmhost snapshot
<get-vmhost-snapshot-information>
show vmhost status
<get-vmhost-staus>
show vmhost uptime
<get-vmhost-uptime>
show vmhost version
<get-vmhost-version-information>
show vpls
show vpls connections
<get-vpls-connection-information>
show vrrp
show vrrp interface
show vrrp track
test interface
test interface fdl-line-loop
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
view-configuration
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
• Example: Configuring User Permissions with Access Privileges for Operational Mode
Commands on page 44
The Junos OS supports two protocols for central authentication of users on multiple
routers: RADIUS and TACACS+. We recommend RADIUS because it is a multivendor
IETF standard, and its features are more widely accepted than those of TACACS+ or
other proprietary systems. In addition, we recommend using a one-time-password system
for increased security, and that all vendors of these systems support RADIUS.
You should use RADIUS when your priorities are interoperability and performance:
• Performance—RADIUS is much lighter on your routers and switches and for this reason,
network engineers generally prefer RADIUS over TACACS+.
To use RADIUS authentication on the device, configure information about one or more
RADIUS servers on the network by including one radius-server statement at the [edit
system] hierarchy level for each RADIUS server.
For example:
For example:
The source address is a valid IPv4 or IPv6 address configured on one of the router
or switch interfaces. This configuration sets a fixed address as the source address
for locally generated IP packets.
Server address is a unique IPv4 or IPv6 address that is assigned to a particular server
and used to route information to the server. If the Junos OS device has several
interfaces that can reach the RADIUS server, assign an IP address that Junos OS
can use for all its communication with the RADIUS server.
You must specify a password in the secret password statement. If the password
contains spaces, enclose it in quotation marks. The secret password used by the local
router or switch must match that used by the server. The secret password configures
the password that the Junos OS device uses to access the RADIUS server.
For example:
NOTE: You can also specify an accounting port to send accounting packets
with the accounting-port statement. The default is 1813 (as specified in
RFC 2866).
For example:
The example assumes your network includes both RADIUS and TACACS+ servers. In
this example, whenever a user attempts to log in, Junos OS begins by querying the
RADIUS server for authentication. If it fails, it next attempts authentication with locally
configured user accounts. Finally the TACACS+ server is tried.
For example:
You can assign different user templates and login classes to RADIUS-authenticated
users. This allows RADIUS-authenticated users to be granted different administrative
permissions on the Junos OS device. By default, RADIUS-authenticated users use the
remote user template and are assigned to the associated class, which is specified in
the remote user template, if the remote user template is configured. The username
remote is a special case in Junos OS. It acts as a template for users who are
authenticated by a remote server, but do not have a locally-configured user account
on the device. In this method, Junos OS applies the permissions of the remote template
to those authenticated users without a locally defined account. All users mapped to
the remote template are of the same login class.
For example:
For example:
b. Have the RADIUS server specify the name of the user template to be applied to
the authenticated user.
After logging in, the remotely authenticated user retains the same username
that was used to log in. However, the user inherits the user class from the assigned
user template.
Configuration of the RADIUS server depends on the server being used. For
instructions for the Juniper Steel-Belted Radius server, see Steel-Belted Radius
(SBR) Enterprise. For information on using FreeRADIUS, see
http://kb.juniper.net/InfoCenter/index?page=content&id=KB19446.
This example shows how to configure a RADIUS server for system authentication.
Requirements
Before you begin:
• Perform the initial device configuration. See the Getting Started Guide for your device.
• Configure at least one RADIUS server. For more details, see RADIUS Authentication and
Accounting Servers Configuration Overview.
Overview
In this example, you add a new RADIUS server with an IP address of 172.16.98.1 and specify
the shared secret password of the RADIUS server as Radiussecret1. The secret is stored
as an encrypted value in the configuration database. Finally, you specify the source
address to be included in the RADIUS server requests by the device. In most cases you
can use the loopback address of the device, which in this example is 10.0.0.1.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
4. In the RADIUS section, click Add. The Add Radius Server dialog box appears.
6. In the Password and Confirm Password boxes, type the secret password for the server
and verify your entry.
8. In the Source Address box, type the source IP address of the server.
9. In the Retry Attempts box, specify the number of times that the server should try to
verify the user’s credentials.
10. In the Time Out box, specify the amount of time (in seconds) the device should wait
for a response from the server.
12. If you are done configuring the device, click Commit Options>Commit.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit system]
user@host# set radius-server address 172.16.98.1
[edit system]
user@host# set radius-server 172.16.98.1 secret Radiussecret1
[edit system]
user@host# set radius-server 172.16.98.1 source-address 10.0.0.1
Results From configuration mode, confirm your configuration by entering the show system
radius-server command. If the output does not display the intended configuration, repeat
the configuration instructions in this example to correct it.
[edit]
user@host# show system radius-server
radius-server 172.16.98.1 {
secret Radiussecret1;
source-address 10.0.0.1;
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Purpose Verify that the RADIUS server has been configured for system authentication.
Action From operational mode, enter the show system radius-server command.
Supported Platforms M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Supported Platforms
[edit system]
tacplus-server server-address {
port port-number;
secret password;
single-connection;
timeout seconds;
}
You must specify a secret (password) that the local router or switch passes to the
TACACS+ client by including the secret statement. If the password included spaces,
enclose the password in quotation marks. The secret used by the local router or switch
must match that used by the server.
Optionally, you can specify the length of time that the local router or switch waits to
receive a response from a TACACS+ server by including the timeout statement. By default,
the router or switch waits 3 seconds. You can configure this to be a value in the range
from 1 through 90 seconds.
Optionally, you can have the software maintain one open Transmission Control Protocol
(TCP) connection to the server for multiple requests, rather than opening a connection
for each connection attempt by including the single-connection statement.
To configure a set of users that share a single account for authorization purposes, you
create a template user. To do this, include the user statement at the [edit system login]
hierarchy level, as described in Overview of Template Accounts for RADIUS and TACACS+
Authentication.
Specifying a Source Address for the Junos OS to Access External TACACS+ Servers
Supported Platforms
You can specify which source address the Junos OS uses when accessing your network
to contact an external TACACS+ server for authentication. You can also specify which
source address the Junos OS uses when contacting a TACACS+ server for sending
accounting information.
To specify a source address for a TACACS+ server for authentication, include the
source-address statement at the [edit system tacplus-server server-address] hierarchy
level:
To specify a source address for a TACACS+ server for system accounting, include the
source-address statement at the [edit system accounting destination tacplus server
server-address] hierarchy level:
To configure the same authentication service for multiple TACACS+ servers, include
statements at the [edit system tacplus-server] and [edit system tacplus-options] hierarchy
levels. For information about how to configure a TACACS+ server at the [edit system
tacplus-server] hierarchy level, see “Configuring TACACS+ Authentication” on page 343.
To assign the same authentication service to multiple TACACS+ servers, include the
service-name statement at the [edit system tacplus-options] hierarchy level:
service-name is the name of the authentication service. By default, the service name is
set to junos-exec.
The following example shows how to configure the same authentication service for
multiple TACACS+ servers:
[edit system]
tacplus-server {
10.2.2.2 secret "$ABC123"; ## SECRET-DATA
10.3.3.3 secret "$ABC123";## SECRET-DATA
}
tacplus-options {
service-name bob;
}
through an authorization request of the TACACS+ server after authenticating a user. You
do not need to configure these attributes to run the Junos OS with TACACS+.
To specify these attributes, include a service statement of the following form in the
TACACS+ server configuration file:
service = junos-exec {
local-user-name = <username-local-to-router>
allow-commands = "<allow-commands-regex>"
allow-configuration-regexps = "<allow-configuration-regex>"
deny-commands = "<deny-commands-regex>"
deny-configuration-regexps = "<deny-configuration-regex>"
}
Related • Example: Configuring a TACACS+ Server for System Authentication on page 346
Documentation
This example shows how to configure a TACACS+ server for system authentication.
Requirements
Before you begin:
• Perform the initial device configuration. See the Getting Started Guide for your device.
Overview
In this example, you set the IP address to 172.16.98.24 and the shared secret password
of the TACACS+ server to Tacacssecret1. The secret password is stored as an encrypted
value in the configuration database. You then set the loopback source address as 10.0.0.1
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
4. In the TACACS section, click Add. The Add TACACS Server dialog box appears.
6. In the Password and Confirm Password boxes, type the secret password for the server
and verify your entry.
8. In the Source Address box, type the locally configured interface address, which is used
as the source address for TACACS+ packets.
9. In the Retry Attempts box, specify the number of times that the server should try to
verify the user’s credentials.
10. In the Time Out box, specify the amount of time (in seconds) the device should wait
for a response from the server.
12. If you are done configuring the device, click Commit Options>Commit.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit system]
user@host# set tacplus-server address 172.16.98.24
[edit system]
user@host# set tacplus-server 172.16.98.24 secret Tacacssecret1
[edit system]
user@host# set tacplus-server 172.16.98.24 source-address 10.0.0.1
Results From configuration mode, confirm your configuration by entering the show system
tacplus-server command. If the output does not display the intended configuration, repeat
the configuration instructions in this example to correct it.
[edit]
user@host# show system tacplus-server
tacplus-server 172.16.98.24 {
secret Tacacssecret1;
source-address 10.0.0.1;
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Purpose Verify that the TACACS+ server has been configured for system authentication.
Action From operational mode, enter the show system tacplus-server command.
Requirements
Before you begin, perform the initial device configuration. See the Getting Started Guide
for your device.
Overview
You can configure the authentication methods that the device uses to verify that a user
can gain access. For each login attempt, the device tries the authentication methods in
order, starting with the first one, until the password matches. If you do not configure
system authentication, users are verified based on their configured local passwords.
This example configures the device to attempt user authentication with the local password
first, then with the RADIUS server, and finally with the TACACS+ server.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
4. Under Available Methods, select the authentication method the device should use to
authenticate users, and use the arrow button to move the item to the Selected Methods
list. Available methods include:
• RADIUS
• TACACS+
• Local Password
If you want to use multiple methods to authenticate users, repeat this step to add the
additional methods to the Selected Methods list.
5. Under Selected Methods, use the Up Arrow and Down Arrow to specify the order in
which the device should execute the authentication methods.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit]
user@host# insert system authentication-order radius after password
[edit]
user@host# insert system authentication-order tacplus after radius
Results From configuration mode, confirm your configuration by entering the show system
authentication-order command. If the output does not display the intended configuration,
repeat the configuration instructions in this example to correct it.
[edit]
user@host# show system authentication-order
authentication-order [password, radius, tacplus];
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Action From operational mode, enter the show system authentication-order command.
You can manage a Juniper Networks device remotely through the J-Web interface. To
communicate with the device, the J-Web interface uses the Hypertext Transfer Protocol
(HTTP). HTTP allows easy Web access but no encryption. The data that is transmitted
between the Web browser and the device by means of HTTP is vulnerable to interception
and attack. To enable secure Web access, the Juniper Networks devices support HTTP
over Secure Sockets Layer (HTTPS). You can enable HTTP or HTTPS access on specific
interfaces and ports as needed.
The Juniper Networks device uses the Secure Sockets Layer (SSL) protocol to provide
secure device management through the Web interface. SSL uses public-private key
technology that requires a paired private key and an authentication certificate for providing
the SSL service. SSL encrypts communication between your device and the Web browser
with a session key negotiated by the SSL server certificate.
An SSL certificate includes identifying information such as a public key and a signature
made by a certificate authority (CA). When you access the device through HTTPS, an
SSL handshake authenticates the server and the client and begins a secure session. If
the information does not match or the certificate has expired, you cannot access the
device through HTTPS.
Without SSL encryption, communication between your device and the browser is sent
in the open and can be intercepted. We recommend that you enable HTTPS access on
your WAN interfaces.
Related • Generating an SSL Certificate Using the openssl Command on page 356
Documentation
• Generating a Self-Signed SSL Certificate on page 356
1. Enter openssl in the CLI. The openssl command generates a self-signed SSL certificate
in privacy-enhanced mail (PEM) format. It writes the certificate and an unencrypted
1024-bit RSA private key to the specified file.
Replace filename with the name of a file in which you want the SSL certificate to be
written—for example, new.pem.
2. When prompted, type the appropriate information in the identification form. For
example, type US for the country name.
cat new.pem
Copy the contents of this file for installing the SSL certificate.
[edit]
user@host# show system services web-management https
system-generated-certificate
Related • Generating an SSL Certificate Using the openssl Command on page 356
Documentation
2. If you have root login access, you can manually generate the self-signed certificate
by using the following commands:
NOTE: When generating the certificate, you must specify the subject,
e-mail address, and either domain-name or ip-address.
[edit]
root@host# show system services web-management https local-certificate certname
You can use the Management tab to configure IPv4 and loopback addresses on the
device.
4. If you want to enable a loopback address for the device, enter an address and
corresponding subnet mask in the Loopback address section.
5. If you want to enable an IPv4 address for the device, select IPv4 address and enter a
corresponding management port, subnet mask, and default gateway.
You can use the Services tab to specify the type of connections that users can make to
the device. For instance, you can enable secure HTTPS sessions to the device or enable
access to the Junos XML protocol XML scripting API.
4. If you want to enable users to create secure Telnet or secure SSH connections to the
device, select Enable Telnet or Enable SSH.
5. If you want to enable access to the Junos XML protocol XML scripting API, select
Enable Junos XML protocol over clear text or Enable Junos XML protocol over SSL. If
you enable Junos XML protocol over SSL, select the certificate you want to use for
encryption from the Junos XML protocol certificate drop-down list.
6. Select Enable HTTP if you want users to connect to device interfaces over an HTTP
connection. Then specify the interfaces that should use the HTTP connection:
• Enable on all interfaces—Select this option if you want to enable HTTP on all device
interfaces.
• Selected interfaces—Use the arrow buttons to populate this list with individual
interfaces if you want to enable HTTP on only some of the device interfaces.
7. If you want users to connect to device interfaces over a secure HTTPS connection,
select Enable HTTPS. Then select which certificate you want to use to secure the
connection from the HTTPS certificates list and specify the interfaces that should use
the HTTPS connection:
• Enable on all interfaces—Select this option if you want to enable HTTPS on all device
interfaces.
• Selected interfaces—Use the arrow buttons to populate this list with individual
interfaces if you want to enable HTTPS on only some of the device interfaces.
To verify that Web access is enabled correctly, connect to the device using one of the
following methods:
• For HTTP access—In your Web browser, type http://URL or http://IP address.
• For HTTPS access—In your Web browser, type https://URL or https://IP address.
• For SSL Junos XML protocol access—A Junos XML protocol client such as Junos Scope
is required.
This example shows how to configure secure Web access on your device.
Requirements
No special configuration beyond device initialization is required before configuring this
feature.
NOTE: You can enable HTTPS access on specified interfaces. If you enable
HTTPS without specifying an interface, HTTPS is enabled on all interfaces.
Overview
In this example, you import the SSL certificate that you have generated as a new and
private key in PEM format. You then enable HTTPS access and specify the SSL certificate
to be used for authentication. Finally, you specify the port as 8443 on which HTTPS
access is to be enabled.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit security]
user@host# set certificates local new load-key-file /var/tmp/new.pem
2. Enable HTTPS access and specify the SSL certificate and port.
[edit system]
user@host# set services web-management https local-certificate new port 8443
Results From configuration mode, confirm your configuration by entering the show security
command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
[edit]
user@host# show security
certificates {
local {
new {
"-----BEGIN RSA PRIVATE KEY-----\nMIICXQIBAAKBgQC/C5UI4frNqbi
qPwbTiOkJvqoDw2YgYse0Z5zzVJyErgSg954T\nEuHM67Ck8hAOrCnb0YO+SY
Y5rCXLf4+2s8k9EypLtYRw/Ts66DZoXI4viqE7HSsK\n5sQw/UDBIw7/MJ+OpA
... KYiFf4CbBBbjlMQJ0HFudW6ISVBslONkzX+FT\ni95ddka6iIRnArEb4VFCRh+
e1QBdp1UjziYf7NuzDx4Z\n -----END RSA PRIVATE KEY-----\n-----BEGIN
CERTIFICATE----- \nMIIDjDCCAvWgAwIBAgIBADANBgkqhkiG9w0BAQQ ...
FADCBkTELMAkGA1UEBhMCdXMx\nCzAJBgNVBAgTAmNhMRIwEAYDVQQHEwlzdW5ue
HB1YnMxDTALBgNVBAMTBGpucHIxJDAiBgkqhkiG\n9w0BCQEWFW5iaGFyZ2F2YUB
fLUYAnBYmsYWOH\n -----END CERTIFICATE-----\n"; ## SECRET-DATA
}
}
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Action From operational mode, enter the show system services command. The following sample
output displays the sample values for secure Web access:
[edit]
user@host# show system services
web-management {
http;
https {
port 8443;
local-certificate new;
}
}
You can use the Certificates tab to upload SSL certificates to the device, edit existing
certificates on the device, or delete certificates from the device. You can use the
certificates to secure HTTPS and Junos XML protocol sessions.
• If you want to add a new certificate, click Add. The Add Certificate section is
expanded.
• If you want to edit the information for an existing certificate, select it and click Edit.
The Edit Certificate section is expanded.
• If you want to delete an existing certificate, select it and click Delete. (You can skip
the remaining steps in this section.)
6. In the Certificate content box, paste the generated certificate and RSA private key.
7. Click Save.
Related • Generating an SSL Certificate Using the openssl Command on page 356
Documentation
Juniper Networks SRX Series devices support the use of USB modems for remote
management. You can use Telnet or SSH to connect to the device from a remote location
through two modems over a telephone network. The USB modem is connected to the
USB port on the device, and a second modem is connected to a remote management
device such as a PC or laptop computer.
You can configure your device to fail over to a USB modem connection when the primary
Internet connection experiences interruption.
A USB modem connects to a device through modem interfaces that you configure. The
device applies its own modem AT commands to initialize the attached modem. Modem
setup requires that you connect and configure the USB modem at the device and the
modem at the user end of the network.
You use either the J-Web configuration editor or CLI configuration editor to configure the
USB modem and its supporting dialer interfaces.
NOTE: Low-latency traffic such as VoIP traffic is not supported over USB
modem connections.
• A physical interface which uses the naming convention umd0. The device creates this
interface when a USB modem is connected to the USB port.
• A logical interface called the dialer interface. You use the dialer interface, dln, to
configure dialing properties for USB modem connections. The dialer interface can be
configured using Point-to-Point Protocol (PPP) encapsulation. You can also configure
the dialer interface to support authentication protocols—PPP Challenge Handshake
(CHAP) or Password Authentication Protocol (PAP). You can configure multiple dialer
interfaces for different functions on the device. After configuring the dialer interface,
you must configure a backup method such as a dialer backup, a dialer filter, or a dialer
watch.
The USB modem provides a dial-in remote management interface, and supports dialer
interface features by sharing the same dial pool as a dialer interface. The dial pool allows
the logical dialer interface and the physical interface to be bound together dynamically
on a per-call basis. You can configure the USB modem to operate either as a dial-in
console for management or as a dial-in WAN backup interface. Dialer pool priority has
a range from 1 to 255, with 1 designating the lowest priority interfaces and 255 designating
the highest priority interfaces.
• The dialer interface must be configured to use PPP encapsulation. You cannot configure
Cisco High-Level Data Link Control (HDLC) or Multilink PPP (MLPPP) encapsulation
on dialer interfaces.
• The dialer interface can perform backup, dialer filter, and dialer watch functions, but
these operations are mutually exclusive. You can configure a single dialer interface to
operate in only one of the following ways:
• As a dialer filter
The backup dialer interfaces are activated only when the primary interface fails. USB
modem backup connectivity is supported on all interfaces except lsq-0/0/0.
Dialer watch is a backup method that integrates backup dialing with routing capabilities
and provides reliable connectivity without relying on a dialer filter to trigger outgoing USB
modem connections. With dialer watch, the device monitors the existence of a specified
route. If the route disappears, the dialer interface initiates the USB modem connection
as a backup connection.
S7=45 Instructs the modem to wait 45 seconds for a telecommunications service provider
(carrier) signal before terminating the call.
S0=0 Disables the auto answer feature, whereby the modem automatically answers calls.
&C1 Disables reset of the modem when it loses the carrier signal.
E0 Disables the display on the local terminal of commands issued to the modem from
the local terminal.
When the device applies the modem AT commands in the init-command-string command
or the default sequence of initialization commands to the modem, it compares them to
the initialization commands already configured on the modem and makes the following
changes:
• If the commands are the same, the device overrides existing modem values that do
not match. For example, if the initialization commands on the modem include S0=0
and the device’s init-command-string command includes S0=2, the device applies
S0=2.
• If the initialization commands on the modem do not include a command in the device’s
init-command-string command, the device adds it. For example, if the
init-command-string command includes the command L2, but the modem commands
do not include it, the device adds L2 to the initialization commands configured on the
modem.
NOTE: On SRX210 devices, the USB modem interface can handle bidirectional
traffic of up to 19 Kbps. On oversubscription of this amount (that is,
bidirectional traffic of 20 Kbps or above), keepalives do not get exchanged,
and the interface goes down. (Platform support depends on the Junos OS
release in your installation.)
15.1X49-D10 Starting with Junos OS Release 15.1X49-D10, USB modems are no longer
supported for dial backup on SRX300, SRX320, SRX340, SRX345,
SRX550HM devices.
• Example: Configuring a Dialer Interface for USB Modem Dial-In on page 376
1. Install device hardware. For more information, see the Getting Started Guide for your
device.
2. Establish basic connectivity. For more information, see the Getting Started Guide for
your device.
3. Order a US Robotics USB 56k V.92 Modem, model number USR Model 5637
(http://www.usr.com/).
4. Order a public switched telephone network (PSTN) line from your telecommunications
service provider. Contact your service provider for more information.
NOTE: When you connect the USB modem to the USB port on the device,
the USB modem is initialized with the modem initialization string
configured for the USB modem interface on the device.
Suppose you have a branch office router and a head office router each with a USB modem
interface and a dialer interface. This example shows you how to establish a backup
connection between the branch office and head office routers. See Table 9 on page 368
for a summarized description of the procedure.
Table 9: Configuring Branch Office and Head Office Routers for USB Modem Backup Connectivity
Router Location Configuration Requirement Procedure
Branch Office Configure the logical dialer interface on the To configure the logical dialer interface,
branch office router for USB modem dial see “Example: Configuring a USB Modem
backup. Interface” on page 369.
Configure the dialer interface dl0 on the Configure the dialer interface using one
branch office router using one of the following of the following backup methods:
backup methods:
• To configure dl0 as a backup for
• Configure the dialer interface dl0 as the t1-1/0/0 see Example: Configuring
backup interface on the branch office Dialer Interfaces and Backup Methods
router's primary T1 interface t1-1/0/0. for USB Modem Dial Backup.
• Configure a dialer filter on the branch office • To configure a dialer filter on dl0, see
router's dialer interface. Example: Configuring Dialer Interfaces
• Configure a dialer watch on the branch and Backup Methods for USB Modem
office router's dialer interface. Dial Backup.
• To configure a dialer watch on dl0, see
Example: Configuring Dialer Interfaces
and Backup Methods for USB Modem
Dial Backup.
Head Office Configure dial-in on the dialer interface dl0 To configure dial-in on the head office
on the head office router. router, see “Example: Configuring a Dialer
Interface for USB Modem Dial-In” on
page 376.
If the dialer interface is configured to accept only calls from a specific caller ID, the device
matches the incoming call's caller ID against the caller IDs configured on its dialer
interfaces. If an exact match is not found and the incoming call's caller ID has more digits
than the configured caller IDs, the device performs a right-to-left match of the incoming
call's caller ID with the configured caller IDs and accepts the incoming call if a match is
found. For example, if the incoming call's caller ID is 4085321091 and the caller ID
configured on a dialer interface is 5321091, the incoming call is accepted. Each dialer
interface accepts calls from only callers whose caller IDs are configured on it.
See Table 10 on page 368 for a list of available incoming map options.
You can configure the accept-all option for only one of the dialer interfaces
associated with a USB modem physical interface. The dialer interface with the
accept-all option configured is used only if the incoming call's caller ID does not
match the caller IDs configured on other dialer interfaces.
caller Dialer interface accepts calls from a specific caller ID. You can configure a
maximum of 15 caller IDs per dialer interface.
You configure dialer interfaces to support PAP. PAP allows a simple method for a peer
to establish its identity using a two-way handshake during initial link establishment. After
the link is established, an ID and password pair are repeatedly sent by the peer to the
authenticator until authentication is acknowledged or the connection is terminated.
15.1X49-D10 Starting with Junos OS Release 15.1X49-D10, USB modems are no longer
supported for dial backup on SRX300, SRX320, SRX340, and SRX345
devices.
This example shows how to configure a USB modem interface for dial backup.
Requirements
No special configuration beyond device initialization is required before configuring this
feature.
Overview
In this example, you create an interface called as umd0 for USB modem connectivity
and set the dialer pool priority to 25. You also configure a modem initialization string to
autoanswer after a specified number of rings. The default modem initialization string is
AT S7=45 S0=0 V1 X4 &C1 E0 Q0 &Q8 %C0. The modem command S0=0 disables the
modem from autoanswering the calls. Finally, you set the modem to act as a dial-in WAN
backup interface.
Configuration
CLI Quick To quickly configure this example, copy the following command, paste it into a text file,
Configuration remove any line breaks, change any details necessary to match your network configuration,
copy and paste the command into the CLI at the [edit] hierarchy level, and then enter
commit from configuration mode.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
1. Create an interface.
[edit]
user@host# edit interfaces umd0
Results From configuration mode, confirm your configuration by entering the show interface umd0
command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
[edit]
user@host# show interface umd0
modem-options {
init-command-string "ATS0=2 \n";
dialin routable;
}
dialer-options {
pool usb-modem-dialer-pool priority 25;
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Action From configuration mode, enter the show interfaces umd0 extensive command. The
output shows a summary of interface information and displays the modem status.
15.1X49-D10 Starting with Junos OS Release 15.1X49-D10, USB modems are no longer
supported for dial backup on SRX300, SRX320, SRX340, and SRX345
devices.
• Example: Configuring a Dialer Interface for USB Modem Dial-In on page 376
This example shows how to configure a logical dialer interface for an SRX300, SRX320,
SRX340, or SRX345 device.
Requirements
Before you begin:
• Install device hardware and establish basic connectivity. See the Getting Started Guide
for your device.
• Order a US Robotics USB 56k V.92 Modem, model number USR Model 5637, from US
Robotics (http://www.usr.com/).
• Order a dial-up modem for the PC or laptop computer at the remote location from
where you want to connect to the device.
• Order a PSTN line from your telecommunications service provider. Contact your service
provider.
Overview
In this example, you configure a logical dialer interface called dl0 to establish USB
connectivity. You can configure multiple dialer interfaces for different functions on the
device. You add a description to differentiate among different dialer interfaces. For
example, this modem is called USB-modem-remote-management. Configure PPP
encapsulation and set the logical unit as 0. You then specify the name of the dialer pool
as usb-modem-dialer-pool and set the source and destination IP addresses as 172.20.10.2,
and 172.20.10.1, respectively.
NOTE: You cannot configure Cisco High-Level Data Link Control (HDLC) or
Multilink PPP (MLPPP) encapsulation on dialer interfaces used in USB modem
connections.
NOTE: If you configure multiple dialer interfaces, ensure that the same IP
subnet address is not configured on different dialer interfaces. Configuring
the same IP subnet address on multiple dialer interfaces can result in
inconsistency in the route and packet loss. The device might route packets
through another dialer interface with the IP subnet address instead of through
the dialer interface to which the USB modem call is mapped.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
1. Create an interface.
[edit]
user@host# set interfaces dl0
4. Configure the name of the dialer pool to use for USB modem connectivity.
Results From configuration mode, confirm your configuration by entering the show interfaces dl0
command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
[edit]
user@host# show interfaces dl0
description USB-modem-remote-management;
encapsulation ppp;
unit 0 {
family inet {
address 172.20.10.2/32 {
destination 172.20.10.1;
}
}
dialer-options {
pool usb-modem-dialer-pool;
}
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Action From configuration mode, enter the show interfaces dl0 extensive command. The output
shows a summary of dialer interface information.
Logical interface dl0.0 (Index 70) (SNMP ifIndex 75) (Generation 146)
Description: USB-modem-remote-management
Flags: Point-To-Point SNMP-Traps 0x4000 LinkAddress 23-0 Encapsulation: PPP
Dialer:
State: Active, Dial pool: usb-modem-dialer-pool
Dial strings: 220
Subordinate interfaces: umd0 (Index 64)
Activation delay: 0, Deactivation delay: 0
Initial route check delay: 120
Redial delay: 3
Callback wait period: 5
Load threshold: 0, Load interval: 60
Bandwidth: 115200
Traffic statistics:
Input bytes : 24839
Output bytes : 17792
Input packets: 489
Output packets: 340
Local statistics:
Input bytes : 10980
Output bytes : 17792
Input packets: 172
Output packets: 340
Transit statistics:
Input bytes : 13859 0 bps
Output bytes : 0 0 bps
Input packets: 317 0 pps
Output packets: 0 0 pps
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Success
Protocol inet, MTU: 1500, Generation: 136, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 172.20.10.1, Local: 172.20.10.2, Broadcast: Unspecified,
Generation: 134
• Example: Configuring a Dialer Interface for USB Modem Dial-In on page 376
This example shows how to configure a dialer interface for USB modem dial-in.
Requirements
No special configuration beyond device initialization is required before configuring this
feature.
Overview
To enable connections to the USB modem from a remote location, you must configure
the dialer interfaces set up for USB modem use to accept incoming calls. You can
configure a dialer interface to accept all incoming calls or accept only calls from one or
more caller IDs.
If the dialer interface is configured to accept only calls from a specific caller ID, the system
matches the incoming call's caller ID against the caller IDs configured on its dialer
interfaces. If an exact match is not found and the incoming call's caller ID has more digits
than the configured caller IDs, the system performs a right-to-left match of the incoming
call's caller ID with the configured caller IDs and accepts the incoming call if a match is
found. For example, if the incoming call's caller ID is 4085550115 and the caller ID
configured on a dialer interface is 5550115, the incoming call is accepted. Each dialer
interface accepts calls from only callers whose caller IDs are configured on it.
You can configure the following incoming map options for the dialer interface:
You can configure the accept-all option for only one of the dialer interfaces associated
with a USB modem physical interface. The device uses the dialer interface with the
accept-all option configured only if the incoming call's caller ID does not match the
caller IDs configured on other dialer interfaces.
• caller—Dialer interface accepts calls from a specific caller ID—for example, 4085550115.
You can configure a maximum of 15 caller IDs per dialer interface.
The same caller ID must not be configured on different dialer interfaces. However, you
can configure caller IDs with more or fewer digits on different dialer interfaces. For
example, you can configure the caller IDs 14085550115, 4085550115, and 5550115 on
different dialer interfaces.
In this example, you configure the incoming map option as caller 4085550115 for dialer
interface dl0.
Configuration
CLI Quick To quickly configure this example, copy the following command, paste it into a text file,
Configuration remove any line breaks, change any details necessary to match your network configuration,
copy and paste the command into the CLI at the [edit] hierarchy level, and then enter
commit from configuration mode.
[edit]
user@host# edit interfaces dl0
[edit]
user@host# edit unit 0 dialer-options incoming-map caller 4085551515
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the show interface dl0 command.
15.1X49-D10 Starting with Junos OS Release 15.1X49-D10, USB modems are no longer
supported for dial-in to a dialer interface on SRX300, SRX320, SRX340,
and SRX345 devices.
To remotely connect to the USB modem connected to the USB port on the device, you
must configure a dial-up modem connection on the PC or laptop computer at your remote
location. Configure the dial-up modem connection properties to disable IP header
compression.
5. Click Next. The New Connection Wizard: Network Connection Type page appears.
7. Select Dial-up connection, and then click Next. The New Connection Wizard: Connection
Name page appears.
8. In the Company Name box, type the dial-up connection name, for example
USB-modem-connect. Then, click Next. The New Connection Wizard: Phone Number
to Dial page appears.
9. In the Phone number box, type the telephone number of the PSTN line connected to
the USB modem at the device end.
10. Click Next twice, and then click Finish. The Connect USB-modem-connect page
appears.
11. If CHAP is configured on the dialer interface used for the USB modem interface at the
device end, type the username and password configured in the CHAP configuration
in the User name and Password boxes.
13. In the Networking tab, select Internet Protocol (TCP/IP), and then click Properties.
The Internet Protocol (TCP/IP) Properties page appears.
To remotely connect to the device through a USB modem connected to the USB port on
the device:
When the connection is complete, you can use Telnet or SSH to connect to the device.
You can use the CLI configuration editor to override the value of an initialization command
configured on the USB modem or configure additional commands for initializing USB
modems.
You can configure the following modem AT commands to initialize the USB modem:
• The command S0=2 configures the modem to automatically answer calls on the
second ring.
When you configure modem commands in the CLI configuration editor, you must follow
these conventions:
You can override the value of the S0=0 command in the initialization sequence configured
on the modem and add the L2 command.
2. If you are done configuring the device, enter commit from configuration mode.
For SRX300, SRX320, SRX340, and SRX345 devices, if the USB modem does not respond,
you can reset the modem.
CAUTION: If you reset the modem when a call is in progress, the call is
terminated.
To reset the USB modem, in operational mode, enter the following command:
You can use the console port on the device to connect to the device through an RJ-45
serial cable. From the console port, you can use the CLI to configure the device. By default,
the console port is enabled. To secure the console port, you can configure the device to
take the following actions:
• Log out of the console session when you unplug the serial cable connected to the
console port.
• Disable root login connections to the console. This action prevents a non-root user
from performing password recovery operation using the console.
• Disable the console port. We recommend disabling the console port to prevent
unauthorized access to the device, especially when the device is used as customer
premises equipment (CPE) and is forwarding sensitive traffic.
NOTE: It is not always possible to disable the console port, because console
access is important during operations such as software upgrades.
• Log out the console session when the serial cable connected to the console port is
unplugged. Enter
2. If you are done configuring the device, enter commit from configuration mode.
• Configuring Password Retry Limits for Telnet and SSH Access on page 384
To prevent brute force and dictionary attacks, the device performs the following actions
for Telnet or SSH sessions by default:
• After the second password retry, introduces a delay in multiples of 5 seconds between
subsequent password retries.
For example, the device introduces a delay of 5 seconds between the third and fourth
password retry, a delay of 10 seconds between the fourth and fifth password retry, and
so on.
You can configure the password retry limits for Telnet and SSH access. In this example,
you configure the device to take the following actions for Telnet and SSH sessions:
• Introduce a delay in multiples of 5 seconds between password retries that occur after
the second password retry.
1. Set the maximum number of consecutive password retries before a Telnet or SSH or
telnet session is disconnected. The default number is 10, but you can set a number
from 1 through 10.
2. Set the threshold number of password retries after which a delay is introduced between
two consecutive password retries. The default number is 2, but you can specify a value
from 1 through 3.
3. Set the delay (in seconds) between consecutive password retries after the threshold
number of password retries. The default delay is in multiples of 5 seconds, but you
can specify a value from 5 through 10 seconds.
4. Set the minimum length of time (in seconds) during which a Telnet or SSH session
cannot be disconnected. The default is 20 seconds, but you can specify an interval
from 20 through 60 seconds.
5. If you are done configuring the device, enter commit from configuration mode.
This example shows how to control management access on SRX Series devices.
Requirements
No special configuration beyond device initialization is required before configuring this
feature.
Overview
By default, any host on the trusted interface can manage a security device. To limit the
IP addresses that can manage a device, you can configure a firewall filter to deny all,
with the exception of the IP address or addresses to which you want to grant management
access. This example shows how to limit management access to a specific IP addresses
to allow it to manage SRX Series devices.
Configuration
• Configuring an IP Address List to Restrict Management Access to a Device on page 386
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
1. Define a set of host addresses, called "manager-ip", that are allowed to manage
the device.
[edit policy-options]
NOTE: The configured list is referenced in the actual filter, where you
can change your defined set of addresses.
2. Configure a firewall filter to deny traffic from all IP addresses except the IP addresses
defined in the "manager-ip" list. Management traffic that uses any of the listed
destination ports is rejected when the traffic comes from an address in the list.
3. Apply stateless firewall filters to the loopback interface to filter the packets
originating from the hosts to which you are granting management access.
Results From configuration mode, confirm your configuration by entering show configuration
command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
source-address {
0.0.0.0/0;
}
source-prefix-list {
manager-ip except;
}
protocol tcp;
destination-port [ ssh https telnet http ];
}
then {
discard;
}
}
term accept_everything_else {
then accept;
}
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Verifying Interfaces
• show policy-options
• show firewall
• show interfaces
Requirements
You must have access to a remote host that has network connectivity with this device.
Overview
In this example, you create an IPv4 stateless firewall filter that logs and rejects Telnet
or SSH access packets unless the packet is destined for or originates from the
192.168.1.0/24 subnet.
• To match packets destined for or originating from the address 192.168.1.0/24 subnet,
you use the source-address 192.168.1.0/24 IPv4 match condition.
• To match packets destined for or originating from a TCP port, Telnet port, or SSH port,
you use the protocol tcp, port telnet, and telnet ssh IPv4 match conditions.
Configuration
The following example requires you to navigate various levels in the configuration
hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode.
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
set firewall family inet filter local_acl term terminal_access from source-address
192.168.1.0/24
set firewall family inet filter local_acl term terminal_access from protocol tcp
set firewall family inet filter local_acl term terminal_access from port ssh
set firewall family inet filter local_acl term terminal_access from port telnet
set firewall family inet filter local_acl term terminal_access then accept
set firewall family inet filter local_acl term terminal_access_denied from protocol tcp
set firewall family inet filter local_acl term terminal_access_denied from port ssh
set firewall family inet filter local_acl term terminal_access_denied from port telnet
set firewall family inet filter local_acl term terminal_access_denied then log
set firewall family inet filter local_acl term terminal_access_denied then reject
set firewall family inet filter local_acl term default-term then accept
set interfaces lo0 unit 0 family inet filter input local_acl
set interfaces lo0 unit 0 family inet address 127.0.0.1/32
Step-by-Step To configure the stateless firewall filter that selectively blocks Telnet and SSH access:
Procedure
1. Create the stateless firewall filter local_acl.
[edit]
user@myhost# edit firewall family inet filter local_acl
[edit]
user@myhost# show firewall
family inet {
filter local_acl {
term terminal_access {
from {
source-address {
192.168.1.0/24;
}
protocol tcp;
port [ssh telnet];
}
then accept;
}
term terminal_access_denied {
from {
protocol tcp;
port [ssh telnet];
}
then {
log;
reject;
}
}
term default-term {
then accept;
}
}
}
[edit]
user@myhost# show interfaces
lo0 {
unit 0 {
family inet {
filter {
input local_acl;
}
source-address 127.0.0.1/32;
}
}
}
3. If you are done configuring the device, commit your candidate configuration.
[edit]
user@myhost# commit
Verification
Confirm that the configuration is working properly.
Purpose Verify that the actions of the firewall filter terms are taken.
2. From a host at an IP address within the 192.168.1.0/24 subnet, use the ssh hostname
command to verify that you can log in to the device using only SSH. This packet should
be accepted, and the packet header information for this packet should not be logged
in the firewall filter log buffer in the Packet Forwarding Engine.
% cli
user@myhost>
3. From a host at an IP address within the 192.168.1.0/24 subnet, use the telnet hostname
command to verify that you can log in to your router or switch using only Telnet. This
packet should be accepted, and the packet header information for this packet
should not be logged in the firewall filter log buffer in the Packet Forwarding Engine.
host (ttyp0)
login: user
Password:
% cli
user@myhost>
4. Use the show firewall log command to verify that the routing table on the device does
not contain any entries with a source address in the 192.168.1.0/24 subnet.
Purpose Verify that the actions of the firewall filter terms are taken.
2. From a host at an IP address outside of the 192.168.1.0/24 subnet, use the ssh hostname
command to verify that you cannot log in to the device using only SSH. This packet
should be rejected, and the packet header information for this packet should be logged
in the firewall filter log buffer in the Packet Forwarding Engine.
3. From a host at an IP address outside of the 192.168.1.0/24 subnet, use the telnet
hostname command to verify that you can log in to the device using only Telnet. This
packet should be rejected, and the packet header information for this packet should
be logged in the firewall filter log buffer in the PFE.
4. Use the show firewall log command to verify that the routing table on the device does
not contain any entries with a source address in the 192.168.1.0/24 subnet.
You can use the CLI telnet command to open a Telnet session to a remote device:
SRX300
SRX210 SRX320
SRX100 SRX220 SRX240 SRX340 SRX345 SRX1500
3 3 5 3 5 5
To exit the Telnet session and return to the Telnet command prompt, press Ctrl-].
To exit the Telnet session and return to the CLI command prompt, enter quit.
bypass-routing Bypass the routing tables and open a Telnet session only to hosts on directly attached
interfaces. If the host is not on a directly attached interface, an error message is returned.
interface source-interface Open a Telnet session to a host on the specified interface. If you do not include this
option, all interfaces are used.
port port Specify the port number or service name on the host.
routing-instance Use the specified routing instance for the Telnet session.
routing-instance-name
source address Use the specified source address for the Telnet session.
You can use the CLI ssh command to use the secure shell (SSH) program to open a
connection to a remote device:
SRX300
SRX210 SRX320
SRX100 SRX220 SRX240 SRX340 SRX345 SRX1500
3 3 5 3 5 5
bypass-routing Bypass the routing tables and open an SSH connection only to hosts on directly attached
interfaces. If the host is not on a directly attached interface, an error message is returned.
interface source-interface Open an SSH connection to a host on the specified interface. If you do not include this
option, all interfaces are used.
routing-instance Use the specified routing instance for the SSH connection.
routing-instance-name
source address Use the specified source address for the SSH connection.
You can configure a device running the Junos OS to initiate a TCP/IP connection with a
client management application that would be blocked if the client attempted to initiate
the connection (for example, if the device is behind a firewall). The outbound-ssh
command instructs the device to create a TCP/IP connection with the client management
application and to forward the identity of the device. Once the connection is established,
the management application acts as the client and initiates the SSH sequence, and the
device acts as the server and authenticates the client.
To configure the device for outbound SSH connections, include the outbound-ssh
statement at the [edit system services] hierarchy level:
The following topics describe the tasks for configuring the outbound SSH service:
• Configuring the Device Identifier for Outbound SSH Connections on page 397
• Sending the Public SSH Host Key to the Outbound SSH Client on page 398
• Configuring Keepalive Messages for Outbound SSH Connections on page 399
• Configuring a New Outbound SSH Connection on page 399
• Configuring the Outbound SSH Client to Accept NETCONF as an Available
Service on page 399
• Configuring Outbound SSH Clients on page 400
To configure the device identifier of the device, include the device-id statement at the
[edit system services outbound-ssh client client-id] hierarchy level:
MSG-ID: DEVICE-CONN-INFO\r\n
MSG-VER: V1\r\n
DEVICE-ID: <device-id>\r\n
Sending the Public SSH Host Key to the Outbound SSH Client
Each time the router or switch establishes an outbound SSH connection, it first sends
an initiation sequence to the management client. This sequence identifies the router or
switch to the management client. Within this transmission is the value of device-id.
To configure the device identifier of the router or switch, include the device-id statement
at the [edit system services outbound-ssh client client-id] hierarchy level:
MSG-ID: DEVICE-CONN-INFO\r\n
MSG-VER: V1\r\n
DEVICE-ID: <device-id>\r\n
During the initialization of an SSH connection, the client authenticates the identity of the
device using the public SSH host key of the device. Therefore, before the client can initiate
the SSH sequence, it needs the public SSH key of the device. When you configure the
secret statement, the device passes its public SSH key as part of the outbound SSH
connection initiation sequence.
When the secret statement is set and the device establishes an outbound SSH connection,
the device communicates its device ID, its public SSH key, and an SHA1 hash derived in
part from the secret statement. The value of the secret statement is shared between the
device and the management client. The client uses the shared secret to authenticate
the public SSH host key it is receiving to determine whether the public key is from the
device identified by the device-id statement.
Using the secret statement to transport the public SSH host key is optional. You can
manually transport and install the public key onto the client system.
NOTE: Including the secret statement means that the device sends its public
SSH host key every time it establishes a connection to the client. It is then up
to the client to decide what to do with the SSH host key if it already has one
for that device. We recommend that you replace the client’s copy with the
new key. Host keys can change for various reasons and by replacing the key
each time a connection is established, you ensure that the client has the
latest key.
To send the router’s or switch’s public SSH host key when the device connects to the
client, include the secret statement at the [edit system services outbound-ssh client
client-id] hierarchy level:
The following message is sent by the device when the secret attribute is configured:
MSG-ID: DEVICE-CONN-INFO\r\n
MSG-VER: V1\r\n
DEVICE-ID: <device-id>\r\n
HOST-KEY: <public-hot-key>\r\n
HMAC:<HMAC(pub-SSH-host-key, <secret>>)>\r\n
To enable the device to send SSH protocol keepalive messages to the client application,
configure the keep-alive statement at the [edit system services outbound-ssh client
client-id] hierarchy level:
You can also specify the number of retry attempts and set the amount of time before
the reconnection attempts stop. See “Configuring Keepalive Messages for Outbound
SSH Connections” on page 399.
NOTE: Outbound SSH connections support IPv4 and IPv6 address formats.
Configuring DNS
• Configuring DNS Server Caching, DNSSEC, and DNS Proxy on page 403
DNS Overview
DNS Components
DNS includes three main components:
• DNS resolver — Resides on the client side of the DNS. When a user sends a hostname
request, the resolver sends a DNS query request to the name servers to request the
hostname's IP address.
• Name servers — Processes the DNS query requests received from the DNS resolver
and returns the IP address to the resolver.
• Resource records — Data elements that define the basic structure and content of the
DNS.
Related • Example: Configuring the TTL Value for DNS Server Caching on page 404
Documentation
• DNSSEC Overview on page 405
This example shows how to configure the TTL value for a DNS server cache to define
the period for which DNS query results are cached.
Requirements
No special configuration beyond device initialization is required before performing this
task.
Overview
The DNS name server stores DNS query responses in its cache for the TTL period specified
in the TTL field of the resource record. When the TTL value expires, the name server
sends a fresh DNS query and updates the cache. You can configure the TTL value from
0 to 604,800 seconds. You can also configure the TTL value for cached negative
responses. Negative caching is the storing of the record that a value does not exist. In
this example, you set the maximum TTL value for cached (and negative cached)
responses to 86,400 seconds.
Configuration
[edit]
user@host# set system services dns max-cache-ttl 86400
2. Specify the maximum TTL value for negative cached responses, in seconds.
[edit]
user@host# set system services dns max-ncache-ttl 86400
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the show system services command.
DNSSEC Overview
Junos OS devices support the domain name service security extensions (DNSSEC)
standard. DNSSEC is an extension of DNS that provides authentication and integrity
verification of data by using public-key based signatures.
In DNSSEC, all the resource records in a DNS are signed with the private key of the zone
owner. The DNS resolver uses the public key of the owner to validate the signature. The
zone owner generates a private key to encrypt the hash of a set of resource records. The
private key is stored in RRSIG record. The corresponding public key is stored in the DNSKEY
record. The resolver uses the public key to decrypt the RRSIG and compares the result
with the hash of the resource record to verify that it has not been altered.
Similarly, the hash of the public DNSKEY is stored in a DS record in a parent zone. The
zone owner generates a private key to encrypt the hash of the public key. The private key
is stored in the RRSIG record. The resolver retrieves the DS record and its corresponding
RRSIG record and public key. Using the public key, the resolver decrypts the RRSIG record
and compares the result with the hash of the public DNSKEY to verify that it has not been
altered. This establishes a chain of trust between the resolver and the name servers.
• Example: Configuring Secure Domains and Trusted Keys for DNSSEC on page 406
DNS-enabled devices run a DNS resolver (proxy) that listens on loopback address 127.0.0.1
or ::1. The DNS resolver performs a hostname resolution for DNSSEC. Users need to set
name server IP address to 127.0.0.1 or ::1 so the DNS resolver forwards all DNS queries to
DNSSEC instead of to DNS. If the name server IP address is not set, DNS will handle all
queries instead of to DNSSEC.
The following example shows how to set the server IP address to 127.0.0.1:
[edit]
user@host# set system name-server 127.0.0.1
The DNSSEC feature is enabled by default. You can disable DNSSEC in the server by
using the following CLI command:
[edit]
set system services dns dnssec disable
You can load a public key from a file or you can copy and paste the key file from a terminal.
In both cases, you must save the keys to the configuration instead of to a file. The following
example shows how to load a key from a file:
The following example explains how to load the key from a terminal:
If you are done loading the keys from the file or terminal, click commit in the CLI editor.
This example shows how to configure secure domains and trusted keys for DNSSEC.
Requirements
Set the name server IP address so the DNS resolver forwards all DNS queries to DNSSEC
instead of DNS. See “Example: Configuring DNSSEC” on page 405 for more information.
Overview
You can configure secure domains and assign trusted keys to the domains. Both signed
and unsigned responses can be validated when DNSSEC is enabled.
When you configure a domain as a secure domain and if DNSSEC is enabled, all unsigned
responses to that domain are ignored and the server returns a SERVFAIL error code to
the client for the unsigned responses. If the domain is not configured as a secure domain,
unsigned responses will be accepted.
When the server receives a signed response, it checks if the DNSKEY in the response
matches any of the trusted keys that are configured. If it finds a match, the server accepts
the signed response.
You can also attach a DNS root zone as a trusted anchor to a secure domain to validate
the signed responses. When the server receives a signed response, it queries the DNS
root zone for a DS record. When it receives the DS record, it checks if the DNSKEY in the
DS record matches the DNSKEY in the signed response. If it finds a match, the server
accepts the signed response.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
[edit]
user@host# set system services dns dnssec secure-domains domain1.net
user@host# set system services dns dnssec secure-domains domain2.net
[edit]
user@host# set system services dns dnssec trusted-keys key
"domain1.net.ABC123ABCh"
[edit]
user@host# set system services dns dnssec dlv domain domain2.net trusted-anchor
dlv.isc.org
Results From configuration mode, confirm your configuration by entering the show system services
command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
dns {
dnssec {
trusted-keys {
key domain1.net.ABC123ABCh; ## SECRET-DATA
}
dlv {
domain domain2.net trusted-anchor dlv.isc.org;
}
secure-domains {
domain1.net;
domain2.net;
}
}
}
If you are done configuring the device, enter commit from configuration mode.
A dynamic name system (DNS) proxy allows clients to use an SRX300, SRX320, SRX340,
SRX345, SRX550M, or SRX1500 device as a DNS proxy server. A DNS proxy improves
domain lookup performance by caching previous lookups. A typical DNS proxy processes
DNS queries by issuing a new DNS resolution query to each name server that it has
detected until the hostname is resolved.
NOTE: If the proxy cache is not available, the device sends the query to the
configured DNS server, which results in network latency delays.
DNS proxy maintains a cache entry for each resolved DNS query. These entries have a
time-to-live (TTL) timer so the device purges each entry from the cache as it reaches its
TTL and expires. You can clear a cache by using the clear cache command , or the cache
will automatically expire along with TTL when it goes to zero.
You can configure the transport method used to resolve a given domain name—for
example, when the device connects to the corporate network through an IPsec VPN or
any other secure tunnel. When you configure a secure VPN tunnel to transport the domain
names belonging to the corporate network, the DNS resolution queries are not leaked to
the ISP DNS server and are contained within the corporate network.
You can also configure a set of default domain (*) and name servers under the default
domain to resolve the DNS queries for a domain for which a name server is not configured.
Each DNS proxy must be associated with an interface. If an interface has no DNS proxy
configuration, all the DNS queries received on that interface are dropped.
Figure 5 on page 410 shows how the split DNS proxy works in a corporate network.
In the corporate network shown in Figure 5 on page 410, a PC client that points to the SRX
Series device as its DNS server makes two queries—to www.your-isp.com and to
www.intranet.com, The DNS proxy redirects the www.intranet.com, query to the
www.intranet.com DNS server (203.0.113.253), while the www.your-isp.com query is
redirected to the ISP DNS server (209.100.3.130). Although the query for
www.your-isp.com is sent to the ISP DNS server as a regular DNS query using clear text
protocols (TCP/UDP), the query for the www.intranet.com domain goes to the intranet’s
DNS servers over a secure VPN tunnel.
• Domain lookups are usually more efficient. For example, DNS queries meant for a
corporate domain (such as acme.com) can go to the corporate DNS server exclusively,
while all others go to the ISP DNS server. Splitting DNS lookups reduces the load on
the corporate server and can also prevent corporate domain information from leaking
onto the Internet.
• A DNS proxy allows you to transmit selected DNS queries through a tunnel interface,
which prevents malicious users from learning about the internal configuration of a
network. For example, DNS queries bound for the corporate server can pass through
a tunnel interface to use security features such as authentication and encryption.
A DDNS server maintains a list of the dynamically changed addresses and their associated
domain names. The device updates these DDNS servers with this information periodically
or in response to IP address changes. The Junos OS DDNS client supports popular DDNS
servers such as dyndns.org and ddo.jp
The IP address of the internal Web server is translated by Network Address Translation
(NAT) to the IP address of the untrust zone interface on the device. The hostname
abc-host.com is registered with the DDNS server and is associated with the IP address
of the device’s untrust zone interface, which is monitored by the DDNS client on the
device. When the IP address of abc-host.com is changed, the DDNS server is informed
of the new address.
If a client in the network shown in Figure 6 on page 412 needs to access abc-host.com,
the client queries the DNS servers on the Internet. When the query reaches the DDNS
server, it resolves the request and provides the client with the latest IP address of
abc-host.com.
The Junos operating system (Junos OS) incorporates domain name system (DNS)
support, which allows you to use domain names as well as IP addresses for identifying
locations. A DNS server keeps a table of the IP addresses associated with domain names.
Using DNS enables an SRX300, SRX320, SRX340, SRX345, SRX550M, or SRX1500
device to reference locations by domain name (such as www.example.net) in addition
to using the routable IP address.
• DNS proxy cache—The device proxies hostname resolution requests on behalf of the
clients behind the SRX Series device. DNS proxy improves domain lookup performance
by using caching.
• Split DNS—The device redirects DNS queries over a secure connection to a specified
DNS server in the private network. Split DNS prevents malicious users from learning
the network configuration, and thus also prevents domain information leaks. Once
configured, split DNS operates transparently.
To configure the device as a DNS proxy, you enable DNS on a logical interface and
configure DNS proxy servers. Configuring a static cache enables branch office and
corporate devices to use hostnames to communicate. Configuring dynamic DNS (DDNS)
clients allows IP address changes.
Perform the following procedure to configure the device as a DNS proxy server by enabling
DNS proxy on a logical interface—for example, ge-2/0/0.0—and configuring a set of
name servers that are to be used for resolving the specified domain names. You can
specify a default domain name by using an asterisk (*) and then configure a set of name
servers for resolution. Use this approach when you need global name servers to resolve
domain name entries that do not have a specific name server configured.
• Configure view for split DNS, specify the internal IP interface to handle the DNS
query and view the logical subnet address.
• Set a default internal domain name, and specify IP server for forwarding the DNS
query according to their IP addresses.
• Configure view for split DNS, specify the external IP interface to handle the DNS
query and view the logical subnet address.
• Set a default external domain name, and specify IP server for forwarding the DNS
query according to their IP addresses.
[edit]
user@host# commit
• Configure the dns proxy static cache entries to specify the host's IPv4 address.
[edit]
user@host# commit
• Enable client.
[edit]
user@host# commit
DHCP Overview
The Dynamic Host Configuration Protocol (DHCP) can serve as a DHCP local server, a
DHCP client, or a DHCP relay agent.
To configure the DHCP local server on the device, include the dhcp-local-server statement
at the [edit system services] hierarchy level.
NOTE: You cannot configure the DHCP local server and the DHCP relay agent
on the same interface.
In a typical branch network configuration, the DHCP client is on the subscriber’s computer,
and the DHCP local server is configured on the device. The following steps provide a
high-level description of the interaction among the DHCP client, DHCP local server, and
address-assignment pools.
1. The DHCP client sends a discover packet to one or more DHCP local servers in the
network to obtain configuration parameters and an IP address for the subscriber.
2. Each DHCP local server that receives the discover packet then searches its
address-assignment pool for the client address and configuration options. Each local
server creates an entry in its internal client table to keep track of the client state, then
sends a DHCP offer packet to the client.
3. On receipt of the offer packet, the DHCP client selects the DHCP local server from
which to obtain configuration information and sends a request packet indicating the
DHCP local server selected to grant the address and configuration information.
4. The selected DHCP local server sends an acknowledgement packet to the client that
contains the client address lease and configuration parameters. The server and client
installs the host route and ARP entry, and then monitors the lease state.
In a DHCP local server operation, the client address and configuration information reside
in centralized address-assignment pools, that are managed independently from the
DHCP local server and they can be shared by different client applications.
Configuring a DHCP environment that includes a DHCP local server requires two
independent configuration operations, which you can complete in any order. In one
operation, you configure the DHCP local server on the device and specify how the DHCP
local server determines which address-assignment pool to use. In the other operation,
you configure the address-assignment pools used by the DHCP local server. The
address-assignment pools contain the IP addresses, named address ranges, and
configuration information for DHCP clients.
NOTE: The DHCP local server and the address-assignment pools used by
the server must be configured in the same routing instance.
DHCP Client
DHCP configuration consists of configuring DHCP clients and a DHCP local server. A
client configuration determines how clients send a message requesting an IP address,
while a server configuration enables the server to send an IP address back to the client.
For the device to operate as a DHCP client, you configure a logical interface on the device
to obtain an IP address from the DHCP local server in the network. You set the vendor
class ID, lease time, DHCP server address, retransmission attempts, and retry interval.
To configure the DHCP relay agent on the router, include the dhcp-relay statement at
the [edit forwarding-options] hierarchy level.
You can also include the dhcp-relay statement at the following hierarchy level:
The following steps describe, at a high level, how the DHCP client, DHCP relay agent,
and DHCP local server interact in a configuration that includes two DHCP local servers.
1. The DHCP client sends a discover packet to find a DHCP local server in the network
from which to obtain configuration parameters for the subscriber, including an IP
address.
2. The DHCP relay agent receives the discover packet and forwards copies to each of
the two DHCP local servers. The DHCP relay agent then creates an entry in its internal
client table to keep track of the client’s state.
3. In response to receiving the discover packet, each DHCP local server sends an offer
packet to the client. The DHCP relay agent receives the offer packets and forwards
them to the DHCP client.
4. On receipt of the offer packets, the DHCP client selects the DHCP local server from
which to obtain configuration information. Typically, the client selects the server that
offers the longest lease time on the IP address.
5. The DHCP client sends a request packet that specifies the DHCP local server from
which to obtain configuration information.
6. The DHCP local server requested by the client sends an acknowledgement (ACK)
packet that contains the client’s configuration parameters.
7. The DHCP relay agent receives the ACK packet and forwards it to the client.
8. The DHCP client receives the ACK packet and stores the configuration information.
9. If configured to do so, the DHCP relay agent installs a host route and Address
Resolution Protocol (ARP) entry for this client.
10. After establishing the initial lease on the IP address, the DHCP client and the DHCP
local server use unicast transmission to negotiate lease renewal or release.
Considerations
The following considerations apply when you enable a DHCP local server, DHCP relay
agent, or DHCP client in a routing instance:
• The DHCP local server, DHCP relay agent, and DHCP client can be configured in one
routing instance, but the functionality is mutually exclusive on one interface. If the
DHCP client is enabled on one interface, the DHCP local server or the DHCP relay agent
cannot be enabled on that interface.
• The DHCP client, DHCP relay agent and DHCP local server services act independently
in their respective routing instance. The following features can function simultaneously
on a device:
• Multiple routing instances. Each instance can have a DHCP local server, DHCP relay
agent, or DHCP client, or each routing instance can have a DHCP client and DHCP
local server or a DHCP client and DHCP relay agent.
version 12.1X46-D40.2;
system {
/* not compatible with jDHCPd */ <<<<<<
autoinstallation {
usb {
disable;
}
}
NOTE: Before you enable DHCP services in a routing instance, you must
remove all the configuration related to DHCP services that does not include
routing instance support. If you do not do this, the old default routing instance
configuration will override the new routing instance configuration.
NOTE: On all SRX Series devices, logical systems and routing instances are
not supported for a DHCP client in chassis cluster mode.
The Juniper Networks device acts as the DHCP server, providing IP addresses and settings
to hosts, such as PCs, that are connected to device interfaces. The DHCP server is
compatible with the DHCP servers of other vendors on the network.
The device can also operate as a DHCP client and DHCP relay agent.
DHCP is based on BOOTP, a bootstrap protocol that allows a client to discover its own
IP address, the IP address of a server host, and the name of a bootstrap file. DHCP servers
can handle requests from BOOTP clients, but provide additional capabilities beyond
BOOTP, such as the automatic allocation of reusable IP addresses and additional
configuration options.
NOTE: Although a Juniper Networks device can act as a DHCP server, a DHCP
client, or DHCP relay agent at the same time, you cannot configure more than
one DHCP role on a single interface.
NOTE: On all SRX Series devices, DHCPv4 is supported only in Layer 3 mode;
the DHCP server and DHCP client are not supported in Layer 2 transparent
mode.
During the DHCP protocol exchange, the device receives TCP/IP settings from the external
network on its DHCP client interface. Settings include the address of the ISP's DHCP
name server and other server addresses. These settings are propagated to the DHCP
server pools configured on the device to fulfill host requests for IP addresses on the
device's internal network.
The device maintains a log of all client-detected conflicts and removes addresses with
conflicts from the DHCP address pool. To display the conflicts list, you use the show
system services dhcp conflict command. The addresses in the conflicts list remain excluded
until you use the clear system services dhcp conflict command to manually clear the list.
DHCP is not supported on interfaces that are part of a virtual private network (VPN).
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• Understanding DHCP Server Operation on page 447
You can use DHCPv6 client prefix delegation to automate the delegation of IPv6 prefixes
to the customer premises equipment (CPE). With prefix delegation, a delegating device
delegates IPv6 prefixes to a requesting device. The requesting device then uses the
prefixes to assign global IPv6 addresses to the devices on the subscriber LAN. The
requesting device can also assign subnet addresses to subnets on the LAN.
With cascaded prefix delegation, the IPv6 address block is delegated to a DHCPv6 client
that is running on the WAN interface of a customer edge device. The identity association
(IA) for the client is used for the identity association for prefix delegation (IA_PD). The
CE device requests, through DHCPv6, an IPv6 address with the IA type of nontemporary
addresses (IA_NA). Both IA_PD and IA_NA are requesting in the same DHCPv6 exchange.
CUSTOMER
NETWORK
PE CPE
CUSTOMER
NETWORK
g043512
The topology in Figure 7 on page 425shows an SRX Series device acting as the CPE. The
WAN interface links to the provider edge (PE) device and the LAN interfaces link to the
customer networks. The service provider delegates a prefix (delegated-prefix) and an
IPv6 address (cpe-wan-ipv6-address) to a DHCPv6 client. When a requesting device
receives that IPv6 address through the DHCPv6 client, the device must install the IPv6
address on its WAN interface. The DHCPv6 client then divides the delegated prefix into
sub-prefixes and subsequently assigns them to the connected LAN interfaces of the CPE
device, making some subset of the remaining space available for sub-prefix delegation.
A CPE assigns sub-prefixes to its LAN interfaces and broadcasts the sub-prefixes through
device advertisement. In this scenario, the CPE acts as a sub-PE and delegates
sub-prefixes and assigns them to sub-CPEs.
NOTE: The requirements of sub-prefix delegation are the same as for the
prefix delegation defined in RFC 3769.
CUSTOMER
Sub CPE NETWORK
PE CPE
g043513
There can be multi-level sub prefix delegations, see Figure 8 on page 426. The top level
CPE gets a delegated prefix from the PE and delegates the sub prefixes to second level
sub-CPEs, then to the third level sub-CPEs, and finally to the end levels. The end level
sub-CPEs assign the IPv6 address to end hosts through SLAAC, stateless DHCPv6 or
stateful DHCPv6. This is called cascaded prefix delegating.
Related •
Documentation
This example shows how to configure DHCPv6 PD over PPPoE on SRX Series devices.
Requirements
No special configuration beyond the device initialization is required before configuring
this feature.
Overview
The example uses SRX550M devices for configuring DHCPv6 PD over PPPoE. Before
you begin, configure DHCPv6 server to permit in host-inbound traffic and receive DHCPv6
packet. Provide a host-name to establish PPPoE session. To enable IPv6, chassis reboot
is required.
Topology
The following illustration describes DHCPv6 PD over PPPoE topology which provide a
configuration suite using SRX Series devices.
PPPoE 2001:1:1:1::/64
g043753
SRX550M SRX550M SRX550M
DHCPv6 Server DHCPv6 Client (PD) DHCPv6 Client (Auto config)
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
• PPPoE configuration
• Enable IPv6
• PPPoE configuration
• Enable IPv6
• Enable IPv6
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit]
user@host# set interfaces ge-0/0/2 unit 0 family inet6
[edit ]
user@host# set system services dhcp-local-server dhcpv6
2. Configuring PPPoE:
[edit]
user@host# set interfaces ge-0/0/1 unit 0 encapsulation ppp-over-ether
4. Enable IPv6:
[edit]
user@host# set security forwarding-options family inet6 mode flow-based
[edit]
user@host# set access profile prof-ge001 client test_user chap-secret test
[edit]
user@host# set access address-assignment pool v6-pd-pool family inet6 prefix
2001:1:1::/48
[edit]
user@host# set access address-assignment pool v6-pd-pool family inet6 range
vp-pd prefix-length 48
[edit]
[edit]
user@host# set security zones security-zone trust interface pp0.0
host-inbound-traffic system-services dhcpv6
[edit]
user@host# set interfaces ge-0/0/2 unit 0 family inet6
[edit]
user@host# set system services dhcp-local-server dhcpv6 overrides
interface-client-limit 10
[edit]
user@host# set system services dhcp-local-server dhcpv6 overrides
process-inform pool p1
[edit]
user@host# set system services dhcp-local-server dhcpv6 group ipv6 interface
ge-0/0/2.0
2. Configuring PPPoE:
e. Set underlying-interface.
f. Set pppoe-options.
[edit]
user@host# set interfaces pp0 unit 0 family inet6 dhcpv6-client client-type
statefull
[edit]
user@host# set interfaces pp0 unit 0 family inet6 dhcpv6-client client-ia-type
ia-pd
[edit]
user@host# set interfaces pp0 unit 0 family inet6 dhcpv6-client
update-router-advertisement interface ge-0/0/2.0 other-stateful-configuration
[edit]
user@host# set interfaces pp0 unit 0 family inet6 dhcpv6-client
update-router-advertisement interface ge-0/0/2.0 max-advertisement-interval
10
[edit]
user@host# set interfaces pp0 unit 0 family inet6 dhcpv6-client
update-router-advertisement interface ge-0/0/2.0 min-advertisement-interval
5
[edit]
user@host# set interfaces pp0 unit 0 family inet6 dhcpv6-client client-identifier
duid-type duid-11
[edit]
user@host# set interfaces pp0 unit 0 family inet6 dhcpv6-client req-option
dns-server
[edit]
user@host# set interfaces pp0 unit 0 family inet6 dhcpv6-client update-server
[edit]
user@host# set protocols router-advertisement interface pp0.0
4. Enable IPv6
[edit]
user@host# set security forwarding-options family inet6 mode flow-based
[edit]
user@host# set access address-assignment pool p1 family inet6 prefix 2001::/16
[edit]
user@host# set access address-assignment pool p1 family inet6 dhcp-attributes
propagate-settings pp0.0
[edit]
user@host# set security zones security-zone trust interface pp0.0
host-inbound-traffic system-services dhcpv6
[edit]
user@host# set security zones security-zone trust interface ge-0/0/2.0
host-inbound-traffic system-services dhcpv6
[edit]
user@host# set protocols router-advertisement interface fe-0/0/0.0
3. Enable IPv6.
[edit]
user@host# set security forwarding-options family inet6 mode flow-based
[edit]
user@host# set security zones security-zone trust interface pp0.0
host-inbound-traffic system-services dhcpv6
Results
From configuration mode, confirm your configuration by entering the show system services
dhcp-local-server, show interfaces, show protocols, show security forwarding-options,
show access profile prof-ge001, show access address-assignment pool, and show security
zones commands. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
[edit]
user@host# show system services dhcp-local-server
dhcpv6 {
overrides {
interface-client-limit 100;
}
group my-group {
overrides {
interface-client-limit 200;
delegated-pool v6-pd-pool;
}
interface pp0.0set;
interface pp0.0;
}
}
...
[edit]
user@host# show interfaces
ge-0/0/1 {
unit 0 {
encapsulation ppp-over-ether;
}
}
pt-1/0/0 {
vdsl-options {
vdsl-profile auto;
}
}
pp0 {
unit 0 {
ppp-options {
chap {
default-chap-secret "$ABC123"; ## SECRET-DATA
}
}
}
}
ge-0/0/1 {
unit 0 {
encapsulation ppp-over-ether;
}
}
pt-1/0/0 {
vdsl-options {
vdsl-profile auto;
}
}
pp0 {
unit 0 {
ppp-options {
chap {
default-chap-secret "$ABC123"; ## SECRET-DATA
}
}
}
}
...
[edit]
user@host# show protocols
interface pp0.0 {
max-advertisement-interval 20;
min-advertisement-interval 10;
managed-configuration;
other-stateful-configuration;
prefix 3000::1/64;
}
...
[edit]
user@host# show security forwarding-options
family {
inet6 {
mode flow-based;
}
}
...
[edit]
user@host# show access address-assignment
pool v6-pd-pool {
family inet6 {
prefix 2001:1:1::/48;
range vp-pd prefix-length 48;
dhcp-attributes {
dns-server {
3000::1;
}
}
}
}
...
[edit]
user@host# show security zones
security-zone Host {
host-inbound-traffic {
system-services {
all;
}
}
interfaces {
ge-0/0/0.0;
}
}
security-zone trust {
interfaces {
pp0.0 {
host-inbound-traffic {
system-services {
dhcpv6;
}
}
}
}
}
[edit]
user@host# show system services dhcp-local-server
dhcpv6 {
overrides {
interface-client-limit 10;
process-inform {
pool p1;
}
}
group my-group {
overrides {
interface-client-limit 200;
delegated-pool v6-pd-pool;
}
interface pp0.0;
}
group ipv6 {
interface ge-0/0/2.0;
}
}
...
[edit]
user@host# show interfaces
ge-0/0/1 {
unit 0 {
encapsulation ppp-over-ether;
}
}
pt-1/0/0 {
vdsl-options {
vdsl-profile auto;
}
}
pp0 {
unit 0 {
ppp-options {
chap {
default-chap-secret "$ABC123"; ## SECRET-DATA
local-name test_user;
passive;
}
}
pppoe-options {
underlying-interface ge-0/0/1.0;
client;
}
}
}
...
[edit]
user@host# show interfaces pp0
unit 0 {
ppp-options {
chap {
default-chap-secret "$ABC123"; ## SECRET-DATA
local-name test_user;
passive;
}
}
pppoe-options {
underlying-interface ge-0/0/1.0;
client;
}
family inet6 {
dhcpv6-client {
client-type statefull;
client-ia-type ia-pd;
update-router-advertisement {
interface ge-0/0/2.0 {
other-stateful-configuration;
max-advertisement-interval 10;
min-advertisement-interval 5;
}
}
client-identifier duid-type duid-ll;
req-option dns-server;
}
}
}
...
[edit]
user@host# show security forwarding-options
family {
inet6 {
mode flow-based;
}
}
...
[edit]
user@host# show access address-assignment
pool v6-pd-pool {
family inet6 {
prefix 2001:1:1::/48;
range vp-pd prefix-length 48;
dhcp-attributes {
dns-server {
3000::1;
}
}
}
}
pool p1 {
family inet6 {
prefix 2001::/16;
dhcp-attributes {
propagate-settings pp0.0;
}
}
}
...
[edit]
user@host# show access address-assignment
security-zone Host {
host-inbound-traffic {
system-services {
all;
}
}
interfaces {
ge-0/0/0.0;
}
}
security-zone trust {
interfaces {
pp0.0 {
host-inbound-traffic {
system-services {
dhcpv6;
}
}
}
ge-0/0/2.0 {
host-inbound-traffic {
system-services {
dhcpv6;
}
}
}
}
}
security-zone untrust {
interfaces {
pp0.0 {
host-inbound-traffic {
system-services {
dhcpv6;
}
}
}
}
}
[edit]
user@host# show interfaces ge-0/0/0
unit 0 {
family inet6 {
dhcpv6-client {
client-type autoconfig;
client-ia-type ia-na;
req-option dns-server;
}
}
}
...
[edit]
user@host# show protocols
router-advertisement {
interface pp0.0 {
max-advertisement-interval 20;
min-advertisement-interval 10;
managed-configuration;
other-stateful-configuration;
prefix 3000::1/64;
}
interface fe-0/0/0.0;
}
...
[edit]
user@host# show security forwarding-options
family {
inet6 {
mode flow-based;
}
}
...
[edit]
user@host# show security zones
security-zone Host {
host-inbound-traffic {
system-services {
all;
}
}
interfaces {
ge-0/0/0.0;
}
}
security-zone trust {
interfaces {
pp0.0 {
host-inbound-traffic {
system-services {
dhcpv6;
}
}
}
ge-0/0/2.0 {
host-inbound-traffic {
system-services {
dhcpv6;
}
}
}
fe-0/0/0.0 {
host-inbound-traffic {
system-services {
dhcpv6;
}
}
}
}
}
security-zone untrust {
interfaces {
pp0.0 {
host-inbound-traffic {
system-services {
dhcpv6;
}
}
}
}
}
Verification
Confirm that the configuration is working properly.
Action • From operational mode, enter the show dhcpv6 server binding command.
The following output shows the options for the show dhcpv6 server binding command.
[edit]
user@host>show dhcpv6 server binding detail
Session Id: 75
Client IPv6 Prefix: 2001:1:1::/48
Client DUID: LL0x1-3c:94:d5:98:90:01
State:
BOUND(DHCPV6_LOCAL_SERVER_STATE_BOUND)
Lease Expires: 2016-03-26 10:12:37 JST
Lease Expires in: 86213 seconds
Lease Start: 2016-03-25 10:12:37 JST
Last Packet Received: 2016-03-25 10:12:50 JST
Incoming Client Interface: pp0.0
Server Ip Address: 0.0.0.0
Client Prefix Pool Name: v6-pd-pool
Client Id Length: 10
Client Id: /0x00030001/0x3c94d598/0x9001
• From operational mode, enter the show route table inet6.0 command.
The following output shows the options for the show route table inet6.0 command.
[edit]
user@host>show route table inet6.0
inet6.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
• From operational mode, enter the show interfaces pp0.0 terse command.
The following output shows the options for the show interfaces pp0.0 terse command.
[edit]
user@host>show interfaces pp0.0 terse
Interface Admin Link Proto Local Remote
pp0.0 up up inet6 3000::1/64
fe80::b2c6:9a0f:fc7d:6900/64
Purpose Verify that the DHCPv6 Client (PD) has been configured.
Action • From operational mode, enter the show dhcpv6 client binding detail command.
The following output shows the options for the show dhcpv6 client binding detail
command.
[edit]
• From operational mode, enter the show dhcpv6 server binding detail command.
The following output shows the options for the show dhcpv6 server binding detail
command.
[edit]
user@host>show dhcpv6 server binding detail
Session Id: 75
Client IPv6 Prefix: 2001:1:1::/48
Client DUID: LL0x1-3c:94:d5:98:90:01
State:
BOUND(DHCPV6_LOCAL_SERVER_STATE_BOUND)
Lease Expires: 2016-03-26 10:12:37 JST
Lease Expires in: 86213 seconds
Lease Start: 2016-03-25 10:12:37 JST
Last Packet Received: 2016-03-25 10:12:50 JST
Incoming Client Interface: pp0.0
Server Ip Address: 0.0.0.0
Client Prefix Pool Name: v6-pd-pool
Client Id Length: 10
Client Id: /0x00030001/0x3c94d598/0x9001
• From operational mode, enter the show route table inet6.0 command.
The following output shows the options for the show route table inet6.0 command.
[edit]
user@host>show route table inet6.0
inet6.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
*[Local/0] 19:05:19
Local via pp0.0
fe80::3e94:d5ff:fe98:8602/128
*[Local/0] 00:03:48
Local via ge-0/0/2.0
• From operational mode, enter the show interfaces pp0.0 terse command.
The following output shows the options for the show interfaces pp0.0 terse command.
[edit]
user@host>show interfaces pp0.0 terse
Interface Admin Link Proto Local Remote
pp0.0 up up inet6 fe80::3e94:d50f:fc98:8600/64
• From operational mode, enter the show interfaces ge-0/0/2.0 terse command.
The following output shows the options for the show interfaces ge-0/0/2.0 terse
command.
[edit]
user@host>show interfaces ge-0/0/2.0 terse
Interface Admin Link Proto Local Remote
ge-0/0/2.0 up up inet6 2000:1:1:1::1/64
fe80::3e94:d5ff:fe98:8602/64
The following output shows the options for the show ipv6 router-advertisement
command.
[edit]
user@host>show ipv6 router-advertisement
Interface: pp0.0
Advertisements sent: 3, last sent 00:01:56 ago
Solicits received: 0
Advertisements received: 10
Advertisement from fe80::b2c6:9a0f:fc7d:6900, heard 00:00:08 ago
Managed: 1 [0]
Other configuration: 1 [0]
Reachable time: 0 ms
Default lifetime: 60 sec [1800 sec]
Retransmit timer: 0 ms
Current hop limit: 64
Prefix: 3000::/64
Valid lifetime: 2592000 sec
Preferred lifetime: 604800 sec
On link: 1
Autonomous: 1
Interface: ge-0/0/2.0
Advertisements sent: 24, last sent 00:00:03 ago
Solicits received: 0
Advertisements received: 0
Purpose Verify that the DHCPv6 client (Auto) has been configured.
Action • From operational mode, enter the show dhcpv6 client binding detail command.
The following output shows the options for the show dhcpv6 client binding detail
command.
[edit]
user@host>show dhcpv6 client binding detail
Client Interface: fe-0/0/0.0
Hardware Address: 00:26:88:38:b5:00
State: BOUND(DHCPV6_CLIENT_STATE_BOUND)
ClientType: AUTO
Lease Expires: 2016-03-26 10:15:35 JST
Lease Expires in: 86395 seconds
Lease Start: 2016-03-25 10:15:35 JST
Bind Type: IA_NA
Client DUID: LL0x3-00:26:88:38:b5:00
Rapid Commit: Off
Server Ip Address: fe80::3e94:d5ff:fe98:8602
Client IP Address: 2001:1:1:1:226:88ff:fe38:b500/128
Client IP Prefix: 2001:1:1:1::/64
DHCP options:
Name: server-identifier, Value: VENDOR0x00000583-0x414c3131
• From operational mode, enter the show route table inet6.0 command.
The following output shows the options for the show route table inet6.0 command.
[edit]
user@host>show route table inet6.0
inet6.0: 5 destinations, 6 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
The following output shows the options for the show ipv6 router-advertisement
command.
[edit]
user@host>show ipv6 router-advertisement
Interface: fe-0/0/0.0
Advertisements sent: 1, last sent 00:02:45 ago
Solicits received: 0
Advertisements received: 8
Advertisement from fe80::3e94:d5ff:fe98:8602, heard 00:00:02 ago
Managed: 0
Other configuration: 1 [0]
Reachable time: 0 ms
Default lifetime: 30 sec [1800 sec]
Retransmit timer: 0 ms
Current hop limit: 64
Prefix: 2001:1:1:1::/64
Valid lifetime: 86400 sec
Preferred lifetime: 86400 sec
On link: 1
Autonomous: 1
As a DHCP server, a Juniper Networks device can provide temporary IP addresses from
an IP address pool to all clients on a specified subnet, a process known as dynamic
binding. Juniper Networks devices can also perform static binding, assigning permanent
IP addresses to specific clients based on their media access control (MAC) addresses.
Static bindings take precedence over dynamic bindings.
DHCP Options
In addition to its primary DHCP server functions, you can also configure the device to
send configuration settings like the following to clients through DHCP:
• IP address of the boot server and the filename of the boot file to use
• DHCP options defined in RFC 2132, DHCP Options and BOOTP Vendor Extensions
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• Example: Configuring the Device as a DHCP Server on page 454
A typical DHCP server configuration provides the following configuration settings for a
particular subnet on a device interface:
• Domain search suffixes. These suffixes specify the domain search list used by a client
when resolving hostnames with DNS.
• Device solicitation address option (option 32). The IP address excluded from the IP
address pool is reserved for this option.
In addition, the DHCP server might assign a static address to at least one client on the
subnet. Table 13 on page 448 provides the settings and values for the sample DHCP server
configuration.
mylab.net
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• Understanding DHCP Server Operation on page 447
• RFC 3397, Dynamic Host Configuration Protocol (DHCP) Domain Search Option
The following sample output shows the minimum configuration you must use to configure
an SRX300, SRX320, SRX340, SRX345, SRX550M, or SRX1500 device as a DHCP local
server. In this output, the server group is named mobileusers, and the DHCP local server
is enabled on interface ge-1/0/1.0 within the group.
[edit access]
address-assignment {
NOTE: You can configure the DHCP local server in a routing instance by using
the dhcp-local server, interface, and address-assignment statements in the
[edit routing-instances] hierarchy level.
The address-assignment pool feature for SRX300, SRX320, SRX340, SRX345, SRX550M,
and SRX1500 devices enables you to create address pools that can be shared by different
client applications such as DHCPv4 or DHCPv6.
1. Configure the address-assignment pool name and specify the addresses for the pool.
1. Configure the name of the pool and specify the IPv4 family.
[edit access]
user@host# edit address-assignment pool blr-pool family inet
2. Configure the network address and the prefix length of the addresses in the pool.
You can optionally configure multiple named ranges, or subsets, of addresses within an
address-assignment pool. During a dynamic address assignment, a client can be assigned
an address from a specific named range. To create a named range, you specify a name
for the range and define the address range.
[edit access]
user@host# edit address-assignment pool blr-pool family inet
2. Configure the name of the range and the lower and upper boundaries of the addresses
in the range.
You can optionally create a static IPv4 address binding by reserving a specific address
for a particular client. The address is removed from the address-assignment pool so that
it is not assigned to another client. When you reserve an address, you identify the client
host and create a binding between the client MAC address and the assigned IP address.
1. Specify the name of the IPv4 address-assignment pool containing the IP address you
want to reserve for the client.
[edit access]
user@host# edit address-assignment pool blr-pool family inet
2. Specify the name of the client for the static binding, the client MAC address, and the
IP address to reserve for the client. This configuration specifies that the client with
MAC address 01:03:05:07:09:0b is always assigned IP address 192.168.10.2.
This topic describes how to configure TCP/IP settings on a DHCP local server, which
includes a DHCP client and a DHCP local server.
2. Configure the address pool to specify the interface (where update-server is configured)
from which TCP/IP settings can be propagated.
[edit access]
address-assignment {
pool sprint family inet {
network 192.168.2.0/24;
dhcp-attributes {
propagate-settings ge-0/0/1.0;
}
}
}
Purpose View or clear information about client address bindings and statistics for the DHCP local
server.
Action • To display the address bindings in the client table on the DHCP local server:
• To clear the binding state of a DHCP client from the client table on the DHCP local
server:
Requirements
Before you begin:
• Determine the IP address pools and the lease durations to use for each subnet.
• Obtain the MAC addresses of the clients that require permanent IP addresses. Determine
the IP addresses to use for these clients.
• List the IP addresses that are available for the servers and devices on your network;
for example, DNS, NetBIOS servers, boot servers, and gateway devices. See the
Understanding Management Predefined Policy Applications.
• Determine the DHCP options required by the subnets and clients in your network.
Overview
In this example, you configure the device as a DHCP server. You specify the IP address
pool as 192.168.2.0/24 and from a low range of 192.168.2.2 to a high range of 192.168.2.254.
You set the maximum-lease-time to 2,419,200. Then you specify the DNS server IP
address as 192.168.10.2.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the set access hierarchy
level, and then enter commit from configuration mode.
GUI Step-by-Step To configure the device as a DHCP server, specify the DHCP pool information, server
Procedure information, lease time, and option information:
1. In the J-Web interface, select Configure > DHCP > DHCP Services.
3. Specify the IP address that is used as the source address the DHCP server includes
in IP packets when communicating with clients. The address is included in the DHCP
packet in option 54.
4. Specify the subnet information for the IPv4 address-assignment pool. Type
192.168.2.0/24.
7. In the Exclude Addresses box, type the addresses you want excluded from a DHCP
address pool. Type 192.168.0.20
8. Specify the server identifier to assign to any DHCP clients in this address pool. The
identifier can be used to identify a DHCP server in a DHCP message.
9. Specify the domain name to assign to any DHCP clients in this address pool.
10. Specify the next server that DHCP clients need to contact. Type 192.168.10.2
11. Define the maximum amount of time (in seconds) that DHCP should lease an address.
Type 2419200.
12. Define DHCP option 32, the device solicitation address option. You must enter a
numeric value for option code. Select the option type from the list that corresponds
to the option code.
14. If you are done configuring the device, click Commit > Commit.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
1. Configure an interface with an IP address on which the DHCP server will be reachable.
[edit]
user@host# set interfaces ge-0/0/2 unit 0 family inet address 192.168.2.1/24
[edit]
user@host# set system services dhcp-local-server group g1 interface ge-0/0/2.0
3. Create an address pool for IPv4 addresses that can be assigned to clients. The
addresses in the pool must be on the subnet in which the DHCP clients reside. Do
not include addresses that are already in use on the network.
[edit]]
user@host# set access address-assignment pool p1 family inet network
192.168.2.0/24
4. (Optional) Specify the IP address pool range. Define a range of addresses in the
address-assignment pool. The range is a subset of addresses within the pool that
can be assigned to clients. If no range is specified, then all addresses within the pool
are available for assignment. Configure the name of the range and the lower and
upper boundaries of the addresses in the range.
[edit]]
user@host# set access address-assignment pool p1 192.168.2.0/24 address-range
low 192.168.2.2 high 192.168.2.254
5. (Optional) Configure one or more routers as the default gateway on the client’s
subnet.
[edit]
user@host# set access address-assignment pool p1 family inet dhcp-attributes
router 192.168.10.3
6. (Optional) Configure the IP address that is used as the source address for the DHCP
server in messages exchanged with the client. Clients use this information to
distinguish between lease offers.
[edit]
7. (Optional) Specify the maximum time period, in seconds, that a client holds the
lease for an assigned IP address if the client does not renew the lease.
[edit]
user@host# set access address-assignment pool pool1 family inet dhcp-attributes
maximum-lease-time 2419200
[edit]
user@host# set access address-assignment pool pool1 family inet dhcp-attributes
option 98 string test98
[edit]
user@host# set system services static-binding 01:03:05:07:09:0B
fixed-address 192.168.2.50
Results From configuration mode, confirm your configuration by entering the show system services
dhcp-local-server command. If the output does not display the intended configuration,
repeat the configuration instructions in this example to correct it.
[edit]
user@host# show system services dhcp-local-server
pool 192.168.2.0/24 {
address-range low 192.168.2.2 high 192.168.2.254;
maximum-lease-time 2419200;
name-server {
192.168.10.2;
}
option 32 ip-address 192.168.2.33;
}
static-binding 01:03:05:07:09:0B {
fixed-address {
192.168.2.50;
}
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Purpose Verify that the DHCP binding database reflects the DHCP server configuration.
• show dhcp server binding command to display all active bindings in the database.
• show dhcp server binding address detail command (where address is the IP address of
the client) to display more information about a client.
IP address 192.0.2.2
Hardware address 00:a0:12:00:13:02
Pool 192.0.2.0/24
Interface fe-0/0/0, relayed by 192.0.2.200
Lease information:
Type DHCP
Obtained at 2004-05-02 13:01:42 PDT
Expires at 2004-05-03 13:01:42 PDT
State active
DHCP options:
Name: name-server, Value: { 6.6.6.6, 6.6.6.7 }
Name: domain-name, Value: mydomain.tld
Code: 32, Type: ip-address, Value: 192.0.2.33
Purpose Verify that the DHCP server operation has been configured.
• show dhcp server statistics command to verify the DHCP server statistics.
Packets dropped:
Total 0
Messages received:
BOOTREQUEST 45
DHCPDECLINE 0
DHCPDISCOVER 1
DHCPINFORM 39
DHCPRELEASE 0
DHCPREQUEST 5
DHCPLEASEQUERY 0
DHCPBULKLEASEQUERY 0
Messages sent:
BOOTREPLY 6
DHCPOFFER 1
DHCPACK 3
DHCPNAK 2
DHCPFORCERENEW 0
DHCPLEASEUNASSIGNED 0
DHCPLEASEUNKNOWN 0
DHCPLEASEACTIVE 0
DHCPLEASEQUERYDONE 0
15.1X49-D60 Starting with Junos OS Release 15.1X49-D60, the legacy DHCPD (DHCP
daemon) configuration on all SRX Series devices is being deprecated.
and only the new JDHCP CLI is supported.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• Understanding DHCP Server Operation on page 447
A Juniper Networks device can act as a DHCP client, receiving its TCP/IP settings and
the IP address for any physical interface in any security zone from an external DHCP
server. The device can also act as a DHCP server, providing TCP/IP settings and IP
addresses to clients in any zone. When the device operates as a DHCP client and a DHCP
server simultaneously, it can transfer the TCP/IP settings learned through its DHCP client
module to its default DHCP server module. For the device to operate as a DHCP client,
you configure a logical interface on the device to obtain an IP address from the DHCP
server in the network. You set the vendor class ID, lease time, DHCP server address,
retransmission attempts, and retry interval. You can renew DHCP client releases.
DHCP client operations are supported on all SRX Series devices in chassis cluster mode.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• Understanding DHCP Relay Agent Operation on page 471
The following sample output shows the minimum configuration you must use to configure
an SRX300, SRX320, SRX340, SRX345, SRX550M, or SRX1500 device as a DHCP client.
In this output, the interface is ge-0/0/0 and the logical unit is 0.
[edit interfaces]
ge-0/0/0 {
unit 0 {
family inet {
dhcp-client
}
}
}
You use the dhcp-attributes statement to configure DHCP client-specific attributes for
address-assignment pools.
[edit access]
user@host# edit address-assignment pool blr-pool family inet
For the device to operate as a DHCP client, you configure a logical interface on the device
to obtain an IP address from the DHCP local server in the network. You can then set the
client-identifier, options no-hostname, lease time, retransmission attempts, retry interval,
preferred DHCP local server address, and vendor class ID.
1. Configure the DHCP client identifier prefix as the routing instance name.
2. Configure the DHCP options no-hostname if you do not want the client to send
hostname (RFC option code 12) in the packets.
5. Set the interval (in seconds) allowed between retransmission attempts. The range
is 4 through 64. The default is 4 seconds.
Purpose View or clear information about client address bindings and statistics for the DHCP client
on SRX300, SRX320, SRX340, SRX550M, and SRX1500 devices.
Action • To display the address bindings in the client table on the DHCP client:
• To clear the binding state of a DHCP client from the client table on the DHCP client:
Requirements
Before you begin:
• Determine the IP address pools and the lease durations to use for each subnet. You
can use the show system services dhcp pool CLI command to view information on DHCP
address pools.
• Obtain the MAC addresses of the clients that require permanent IP addresses. Determine
the IP addresses to use for these clients.
• List the IP addresses that are available for the servers and devices on your network;
for example, DNS, NetBIOS servers, boot servers, and gateway devices. See the
Understanding Management Predefined Policy Applications.
• Determine the DHCP options required by the subnets and clients in your network. See
Creating User-Defined DHCP Options Not Included in the Default Junos Implementation
of the DHCP Server
Overview
In this example, you configure the device as a DHCP client. You specify the interface as
ge-0/0/2, set the logical unit as 0, and create a DHCP inet family. You then specify the
DHCP client identifier as 00:0a:12:00:12:12 in hexadecimal. You use hexadecimal if the
client identifier is a MAC address. You set the options no-hostname if you do not want
the DHCP client to send the hostname with the packets. You set the DHCP lease time
as 86,400 seconds. The range is from 60 through 2,147,483,647 seconds.
Then you set the number of retransmission attempts to 6. The range is from 0 through
6, and the default is 4. You set the retransmission interval to 5 seconds. The range is from
4 through 64, and the default is 4 seconds. Finally, you set the IPv4 address of the
preferred DHCP server to 10.1.1.1 and the vendor class ID to ether.
Release 15.1X49-D60 and later releases on a device that already has the
DHCPD configuration, the following warning messages are displayed:
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
set interfaces ge-0/0/2 unit 0 family inet dhcp-client client-identifier prefix host-name
set interfaces ge-0/0/2 unit 0 family inet dhcp-client lease-time 86400
set interfaces ge-0/0/2 unit 0 family inet dhcp-client retransmission-attempt 6
set interfaces ge-0/0/2 unit 0 family inet dhcp-client retransmission-interval 5
set interfaces ge-0/0/2 unit 0 family inet dhcp-client server-address 192.168.2.1
set interfaces ge-0/0/2 unit 0 family inet dhcp-client vendor-id ether
set interfaces ge-0/0/2 unit 0 family inet dhcp-client options no-hostname
6. Set the DHCP lease time in seconds. This is the lease time in seconds requested in a
DHCP client protocol packet; the range is 60 through 2,147,483,647. Type 86400.
8. Set the retransmission interval in seconds to 5. This is the number of seconds between
successive transmissions. The range is 4 through 64. The default is 4 seconds.
9. Set the IPv4 address of the preferred DHCP server. Type 192.168.2.1.
10. Set the vendor class ID. This is the vendor class identification for the DHCP client.
Type ether.
11. Configure options no-hostname if you do not want the client to send hostname in the
packets (RFC option code 12).
13. If you are done configuring the device, click Commit >.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit]
user@host# edit interfaces ge-0/0/2 unit 0 family inet dhcp-client
5. Set the interval (in seconds) allowed between retransmission attempts. The range
is 4 through 64. The default is 4 seconds.
8. Configure options no-hostname if you do not want the client to send the hostname
in packets.
Results From configuration mode, confirm your configuration by entering the show interfaces
ge-0/0/2 unit 0 family inet command. If the output does not display the intended
configuration, repeat the configuration instructions in this example to correct it.
[edit]
user@host# show interfaces ge-0/0/2 unit 0 family inet
dhcp-client {
client-identifier hexadecimal 00:0a:12:00:12:12;
options no-hostname;
lease-time 86400;
retransmission-attempt 6;
retransmission-interval 5;
server-address 192.168.2.1;
update-server;
vendor-id ether;
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Purpose Verify that the DHCP client information has been configured.
• show dhcp client binding command to display the binding state of a Dynamic Host
Configuration Protocol (DHCP) client.
Packets dropped:
Total 2
Send error 2
Messages received:
BOOTREPLY 6
DHCPOFFER 4
DHCPACK 2
DHCPNAK 0
DHCPFORCERENEW 0
Messages sent:
BOOTREQUEST 39
DHCPDECLINE 0
DHCPDISCOVER 23
DHCPREQUEST 16
DHCPINFORM 0
DHCPRELEASE 0
DHCPRENEW 0
DHCPREBIND 0
15.1X49-D60 Starting with Junos OS Release 15.1X49-D60, the legacy DHCPD (DHCP
daemon) configuration on all SRX Series devices is being deprecated
and only the new JDHCP CLI is supported.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• Understanding DHCP Server Operation on page 447
A Juniper Networks device operating as a DHCP relay agent forwards incoming requests
from BOOTP and DHCP clients to a specified BOOTP or DHCP server. Client requests
can pass through virtual private network (VPN) tunnels.
You cannot configure a single device interface to operate as both a DHCP client and a
DHCP relay.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• Understanding DHCP Server Operation on page 447
The following sample output shows the minimum configuration you must use to configure
an SRX Series device as a DHCP relay agent. In this output, the active server group is
named server-1 and its IP address is 203.0.113.1. The DHCP relay agent configuration is
applied to a group named bob. Within this group, the DHCP relay agent is enabled on
interface ge-1/0/1.0.
[edit forwarding-options]
dhcp-relay {
server-group {
server-1 {
203.0.113.1;
}
}
active-server-group server-1;
group bob {
interface ge-1/0/1.0;
}
}
Purpose View or clear address bindings or statistics for DHCP relay agent clients.
Action • To display the address bindings for DHCP relay agent clients:
To clear or view information about client bindings and statistics in a routing instance, run
the following commands:
NOTE: On all SRX Series devices, DHCP relay is unable to update the binding
status based on DHCP_RENEW and DHCP_RELEASE messages.
This example shows how to configure the device as a BOOTP or DHCP relay agent.
Requirements
No special configuration beyond device initialization is required before configuring this
feature.
Overview
In this example, you enable the DHCP relay agent to relay BOOTP or DHCP messages to
a BOOTP server. You enable VPN encryption to allow client requests to pass through the
VPN tunnel. You specify the IP time-to-live value to be set in responses to the client as
20. The range is from 1 through 255. You then set the maximum number of hops allowed
per packet to 10. The range is from 4 through 16.
Then you specify the minimum number of seconds before requests are forwarded as
300. The range is from 0 through 30,000 seconds. You set the description of the server
(the value is a string), and you specify a valid server name or address to the server to
forward (the value is an IPv4 address). You define the routing instance, whose value is
a nonreserved text string of 128 or fewer characters. You then specify the incoming BOOTP
or DHCP request forwarding interface as ge-0/0/0. You enable the broadcast option if
the Layer 2 interface is unknown.
You then specify the IP time-to-live value to be set in responses to the client as 30. The
range is from 1 through 255. You set the description of the server as text and the DHCP
option as 82. You set the maximum number of hops allowed per packet to 20 and specify
the minimum number of seconds as 400 before requests are forwarded. You enable the
no listen option. Finally, you enable VPN encryption to allow client requests to pass
through the VPN tunnel.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
2. Select the DHCP relay agent check box to enable the BOOTP/DHCP relay agent.
10. Define the routing instance. Next to Routing instance, click Add new entry.
11. In the Name box, type rt-i-1 and click OK. A routing instance is optional.
12. Add a new interface. Next to Interface, click Add new entry.
13. In the Interface name box, type the interface name. For example, type ge-0/0/0.
23. If you are done configuring the device, click Commit Options>Commit.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit]
user@host# edit forwarding-options helpers bootp
user@host# set relay agent-option
2. Enable VPN encryption to allow client requests to pass through VPN tunnel.
17. Enable VPN encryption to allow client requests to pass through the VPN tunnel.
Results From configuration mode, confirm your configuration by entering the show
forwarding-options command. If the output does not display the intended configuration,
repeat the configuration instructions in this example to correct it.
[edit]
user@host# show forwarding-options
helpers {
bootp {
relay-agent-option;
description text;
server 198.51.110.2 routing-instance rt-i-1;
maximum-hop-count 10;
minimum-wait-time 300;
client-response-ttl 20;
vpn;
interface {
ge-0/0/0 {
no-listen;
broadcast;
description text;
maximum-hop-count 20;
minimum-wait-time 400;
client-response-ttl 30;
vpn;
dhcp-option82;
}
}
}
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Purpose Verify that the DHCP Relay statistics have been configured.
Action From operational mode, enter the show system services dhcp relay-statistics command.
15.1X49-D60 Starting with Junos OS Release 15.1X49-D60, the legacy DHCPD (DHCP
daemon) configuration on all SRX Series devices is being deprecated
and only the new JDHCP CLI is supported.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• Understanding DHCP Relay Agent Operation on page 471
The DHCPv6 server configuration usually consists of DHCPv6 options for clients, an IPv6
prefix, an address pool that contains IPv6 address ranges and options, and a security
policy to allow DHCPv6 traffic. In a typical setup the provider Juniper Networks device is
configured as an IPv6 prefix delegation server that assigns addresses to the customer
edge device. The customer’s edge router then provides addresses to internal devices.
To configure DHCPv6 local server on a device, you include the DHCPv6 statement at the
[edit system services dhcp-local-server] hierarchy level. You then create an address
assignment pool for DHCPv6 that is configured in the [edit access address-assignment
pool] hierarchy level using the family inet6 statement.
You can also include the dhcpv6 statement at the [edit routing-instances
routing-instance-name system services dhcp-local-server] hierarchy.
• Configuring a Named Address Range for Dynamic Address Assignment on page 486
For the DHCPv6 server to allow DHCPv6 requests, you must create a security policy to
enable DHCPv6 traffic. In this example, the zone my-zone allows DHCPv6 traffic from
the zone untrust, and the ge-0/0/3.0 interface is configured with the IPv6 address
2001:db8:3001::1.
3. If you are done configuring the device, enter commit from configuration mode.
This example shows how to configure DHCPv6 server options on SRX1500, SRX5400,
SRX5600, and SRX5800 devices.
Requirements
Before you begin:
• Determine the grace period, maximum lease time, or any custom options that should
be applied to clients.
• List the IP addresses that are available for the devices on your network; for example,
DNS and SIP servers.
Overview
In this example, you set a default client limit as 100 for all DHCPv6 groups. You then
create a group called my-group that contains at least one interface. In this case, the
interface is ge-0/0/3.0. You set a range of interfaces using the upto command and set
a custom client limit as 200 for group my-group that overrides the default limit. Finally,
you configure interface ge-0/0/3.0 with IPv6 address 2001:db8:3001::1/64 and set router
advertisement for interface ge-0/0/3.0. Starting with Junos OS Release 15.X49-D70,
you can add the option dynamic-server to dynamically support prefix and attributes that
are updated by the WAN server.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit]
user@host# edit system services dhcp-local-server dhcpv6
3. Add a dynamic server that automatically adds prefix and attributes that are updated
by the WAN server.
[edit]
user@host# edit system services dhcp-local-server dhcpv6 dynamic-server
[edit interfaces]
user@host# set ge-0/0/3 unit 0 family inet6 address 2001:db8:3000::1/64
[edit protocols]
user@host# set router-advertisement interface ge-0/0/3.0 prefix
2001:db8:3000::/64
Results From configuration mode, confirm your configuration by entering the show system services
dhcp-local-server, show interfaces ge-0/0/3, and show protocols commands. If the output
does not display the intended configuration, repeat the configuration instructions in this
example to correct it.
[edit]
user@host# show system services dhcp-local-server
dhcpv6 {
dynamic-server
overrides {
interface-client-limit 100;
}
group my-group {
overrides {
interface-client-limit 200;
}
interface ge-0/0/3.0 {
upto ge-0/0/6.0;
}
}
}
[edit]
user@host# show interfaces ge-0/0/3
unit 0 {
family inet6 {
address 2001:db8:3000::1/64;
}
}
[edit]
user@host# show protocols
router-advertisement {
interface ge-0/0/3.0 {
prefix 2001:db8:3000::1/64;
}
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Purpose Verify that the client address bindings and statistics for the DHCPv6 local server have
been configured
• show dhcpv6 server binding command to display the address bindings in the client
table on the DHCPv6 local server.
• show dhcpv6 server statistics command to display the DHCPv6 local server statistics.
• clear dhcpv6 server bindings all command to clear all DHCPv6 local server bindings.
You can clear all bindings or clear a specific interface, or routing instance.
• clear dhcpv6 server statistics command to clear all DHCPv6 local server statistics.
15.1X49-D70 Starting with Junos OS Release 15.X49-D70, you can add the option
dynamic-server to dynamically support prefix and attributes that are
updated by the WAN server.
• Configuring a Named Address Range for Dynamic Address Assignment on page 486
Requirements
Before you begin:
• Specify the name of the address-assignment pool and configure addresses for the
pool.
Overview
In this example, you configure an address-pool called my-pool and specify the IPv6 family
as inet6. You configure the IPv6 prefix as 2001:db8:3000:1::/64, the range name as range1,
and the IPv6 range for DHCPv6 clients from a low of 2001:db8:3000:1::/64 to a high of
2001:db8:3000:200::/64. You can define the range based on the lower and upper
boundaries of the prefixes in the range or based on the length of the prefixes in the range.
Finally, you specify the DHCPv6 attribute for the DNS server as 2001:db8:3001::1, the
grace period as 3600, and the maximum lease time as 120.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit access]
user@host# edit address-assignment pool my-pool family inet6
2. Configure the IPv6 prefix, the range name, and IPv6 range for DHCPv6 clients.
3. Configure the DHCPv6 attribute for the DNS server for the address pool.
Results From configuration mode, confirm your configuration by entering the show access
address-assignment command. If the output does not display the intended configuration,
repeat the configuration instructions in this example to correct it.
[edit]
user@host# show access address-assignment
pool my-pool {
family inet6 {
prefix 2001:db8:3000:1::/64;
range range1 {
low 2001:db8:3000:1::/64 ;
high 2001:db8:3000:200::/64;
}
dhcp-attributes {
maximum-lease-time 120;
grace-period 3600;
dns-server {
2001:db8:3001::1;
}
}
}
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Verifying Configuration
Action From operational mode, enter the show access address-assignment command.
• Configuring a Named Address Range for Dynamic Address Assignment on page 486
You can optionally configure multiple named ranges, or subsets of addresses, within an
address-assignment pool. During dynamic address assignment, a client can be assigned
an address from a specific named range. To create a named range, you specify a name
for the range and define the address range and DHCPv6 attributes.
1. Specify the name of the address-assignment pool and the IPv6 family.
[edit access]
user@host# edit address-assignment pool my-pool2 family inet6
2. Configure the IPv6 prefix and then define the range name and IPv6 range for DHCPv6
clients. You can define the range based on the lower and upper boundaries of the
prefixes in the range, or based on the length of the prefixes in the range.
4. If you are done configuring the device, enter commit from configuration mode.
Address-assignment pool linking enables you to specify a secondary address pool for
the device to use when the primary address-assignment pool is fully allocated. When
the primary pool has no available addresses remaining, the device automatically switches
over to the linked secondary pool and begins allocating addresses from that pool. The
device uses a secondary pool only when the primary address-assignment pool is fully
allocated.
You can create a chain of multiple linked pools. For example, you can link pool A to pool
B, and link pool B to pool C. When pool A has no available addresses, the device switches
to pool B for addresses. When pool B is exhausted, the device switches to pool C. There
is no limit to the number of linked pools in a chain. However, you cannot create multiple
links to or from the same pool—a pool can be linked to only one secondary pool, and a
secondary pool can be linked from only one primary pool.
Related • Configuring a Named Address Range for Dynamic Address Assignment on page 451
Documentation
Table 14 on page 488 describes the DHCPv6 client attributes for configuring IPv6
address-assignment pools.
Related • Configuring a Named Address Range for Dynamic Address Assignment on page 486
Documentation
For SRX1500, SRX5400, SRX5600, and SRX5800 devices, you can create an
address-assignment pool that is explicitly used for router advertisement address
assignment. You populate the address-assignment pool using the standard procedure,
but you additionally specify that the pool is used for router advertisement.
3. If you are done configuring the device, enter commit from configuration mode.
Related • Configuring a Named Address Range for Dynamic Address Assignment on page 486
Documentation
Each DHCPv6 client and server is identified by a DHCP unique identifier (DUID). The DUID
is unique across all DHCPv6 clients and servers, and it is stable for any specific client or
server. DHCPv6 clients use DUIDs to identify a server in messages where a server needs
to be identified. DHCPv6 servers use DUIDs to determine the configuration parameters
to be used for clients and in the association of addresses with clients.
The DUID is a 2-octet type code represented in network byte order, followed by a variable
number of octets that make up the actual identifier; for example,
The duid-llt DUID consists of a 2-octet type field that contains the value 1, a 2-octet
hardware type code, 4 octets that signify a time value, followed by the Link Layer address
of any one network interface that is connected to the DHCP device at the time that the
DUID is generated.
The vendor DUID is assigned by the vendor to the device and contains the vendor's
registered private enterprise number as maintained by the identity association for
nontemporary addresses (IA_NA) assignment, followed by a unique identifier assigned
by the vendor.
The duid-ll DUID contains a 2-octet type field that stores the value 3, and a 2-octet
network hardware type code, followed by the Link Layer address of any one network
interface that is permanently connected to the client or server device.
A Juniper Networks device can act as a Dynamic Host Configuration Protocol version 6
(DHCPv6) client, receiving its TCP/IP settings and the IPv6 address for any physical
interface in any security zone from an external DHCPv6 server. When the device operates
as a DHCPv6 client and a DHCPv6 server simultaneously, it can transfer the TCP/IP
settings learned through its DHCPv6 client module to its default DHCPv6 server module.
For the device to operate as a DHCPv6 client, you configure a logical interface on the
device to obtain an IPv6 address from the DHCPv6 server in the network.
DHCPv6 client support for Juniper Networks devices includes the following features:
• Rapid commit
• TCP/IP propagation
• Auto-prefix delegation
To configure the DHCPv6 client on the device, include the dhcpv6-client statement at
the [edit interfaces] hierarchy level.
• Temporary addresses
• Reconfigure messages
This topic describes the minimum configuration you must use to configure an SRX300,
SRX320, SRX340, SRX345, SRX550M, or SRX1500 device as a DHCPv6 client.
[edit]
user@host# set interfaces ge-0/0/0 unit 0 family inet6 dhcpv6-client
2. Configure the DHCPv6 client type. The client type can be autoconfig or statefull.
• To enable DHCPv6 auto configuration mode, configure the client type as autoconfig.
4. Configure the DHCPv6 client identifier by specifying the DHCP unique identifier (DUID)
type. The following DUID types are supported:
• dns-server
• domain
• ntp-server
• sip-domain
• sip-server
2. Set the number of attempts allowed to retransmit a DHCPv6 client protocol packet.
5. Configure the two-message (rapid commit) exchange option for address assignment.
• Temporary addresses
• Reconfigure messages
[edit]
user@host# set interfaces ge-0/0/0 unit 0 family inet6 dhcpv6-client
The DHCPv6 client requests IPv6 addresses and prefixes from the DHCPv6 server. Based
on the DHCPv6 server’s response, the DHCPv6 client assigns the IPv6 addresses to
interfaces and sets a lease time for all valid responses. When the lease time expires, the
DHCPv6 client renews the lease from the DHCPv6 server.
[edit]
user@host# set interfaces ge-0/0/0 unit 0 family inet6 dhcpv6-client
You can use DHCPv6 client prefix delegation to automate the delegation of IPv6 prefixes
to the customer premises equipment (CPE). With prefix delegation, a delegating router
delegates IPv6 prefixes to a requesting router. The requesting router then uses the prefixes
to assign global IPv6 addresses to the devices on the subscriber LAN. The requesting
router can also assign subnet addresses to subnets on the LAN.
The DHCPv6 client can obtain configuration parameters from a DHCPv6 server through
a rapid two-message exchange (solicit and reply). When the rapid commit option is
enabled by both the DHCPv6 client and the DHCPv6 server, the two-message exchange
is used, rather than the default four-method exchange (solicit, advertise, request, and
reply). The two-message exchange provides faster client configuration and is beneficial
in environments in which networks are under a heavy load.
To configure the DHCPv6 client to support the DHCPv6 rapid commit option on SRX300,
SRX320, SRX340, SRX550M, and SRX1500 devices:
[edit]
user@host# set interfaces ge-0/0/0 unit 0 family inet6 dhcpv6-client
A DHCPv6 client configured in autoconfig mode acts as a stateful client, a stateless client
(DHCPv6 server is required for TCP/IP configuration), and stateless–no DHCP client,
based on the managed (M) and other configuration (O) bits in the received router
advertisement messages.
If the managed bit is 1 and the other configuration bit is 0, the DHCPv6 client acts as a
stateful client. In stateful mode, the client receives IPv6 addresses from the DHCPv6
server, based on the identity association for nontemporary addresses (IA_NA) assignment.
If the managed bit is 0 and the other configuration bit is 1, the DHCPv6 client acts as a
stateless client. In stateless mode, the addresses are automatically configured, based
on the prefixes in the router advertisement messages received from the router. The
stateless client receives configuration parameters from the DHCPv6 server.
If the managed bit is 0 and the other configuration bit is also 0, the DHCPv6 client acts
as a stateless–no DHCP client. In the stateless–no DHCP mode, the client receives IPv6
addresses from the router advertisement messages.
You can enable or disable the propagation of TCP/IP settings received on the device
acting as a DHCPv6 client. The settings can be propagated to the server pool running on
the device. This topic describes how to configure TCP/IP settings on a DHCPv6 client,
where both the DHCPv6 client and DHCPv6 server are on the same device.
2. Configure the address pool to specify the interface (where update-server is configured)
from which TCP/IP settings can be propagated.
[edit access]
user@host# set address-assignment pool 2 family inet6 dhcp-attributes
propagate-settings ge-0/0/0
• Example: Configuring the Device as a DHCP Server in Chassis Cluster Mode on page 501
• Example: Configuring the Device as a DHCP Client in Chassis Cluster Mode on page 507
This example shows how to configure a DHCP server in chassis cluster mode.
Requirements
This example uses the following hardware and software components:
• Determine the IP address pools and the lease durations to use for each subnet.
• Obtain the MAC addresses of the clients that require permanent IP addresses. Determine
the IP addresses to use for these clients.
• List the IP addresses that are available for the servers and devices on your network;
for example, DNS, NetBIOS servers, boot servers, and gateway devices.
• Determine the DHCP options required by the subnets and clients in your network.
Overview
In this example, you configure two SRX Series devices as DHCP servers and a third SRX
Series device as a DHCP client. Configure the two DHCP servers in chassis cluster mode.
For the DHCP server, configure the SRX Series device as a DHCP local server with minimum
DHCP local server configurations. You specify the server group as g1 and enable the DHCP
local server on interface reth1.
For the DHCP client, you specify the interface as ge-0/0/1, set the logical unit as 0, and
create a DHCP inet family. You then specify the DHCP client identifier as 00:0a:12:00:12:12
in hexadecimal. You use hexadecimal if the client identifier is a MAC address. You set
the DHCP lease time as 86,400 seconds. The range is from 60 through 2,147,483,647
seconds.
You set the number of retransmission attempts to 6. The range is from 0 through 6, and
the default is 4. You set the retransmission interval to 5 seconds. The range is from 4
through 64, and the default is 4 seconds. Finally, you set the IPv4 address of the preferred
DHCP server to 10.1.1.1 and the vendor class ID to ether.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit access]
user@host# set address-assignment pool p1 family inet network 203.0.113.1/10
user@host# set address-assignment pool p1 family inet range r1 low 203.0.113.5
user@host# set address-assignment pool p1 family inet range r1 high 203.0.113.20
{primary:node0}[edit]
user@host# set chassis cluster reth-count 4
{primary:node0}[edit]
user@host# set chassis cluster control-link-recovery
{primary:node0}[edit]
user@host# set chassis cluster heartbeat-interval 2000
{primary:node0}[edit]
user@host# set chassis cluster redundancy-group 0 node 0 priority 200
user@host# set chassis cluster redundancy-group 0 node 1 priority 1
{primary:node0}[edit]
user@host# set interfaces ge-0/0/1 gigether-options redundant-parent reth1
user@host# set interfaces ge-6/0/1 gigether-options redundant-parent reth1
user@host# set interfaces reth1 redundant-ether-options redundancy-group 1
user@host# set interfaces reth1 unit 0 family inet address 10.1.1.1/24
[edit]
user@host# edit interfaces ge-0/0/1 unit 0 family inet dhcp-client
5. Set the interval (in seconds) allowed between retransmission attempts. The range
is 4 through 64. The default is 4 seconds.
Results From configuration mode, confirm your configuration by entering the show commands.
If the output does not display the intended configuration, repeat the configuration
instructions in this example to correct it.
[edit]
[edit]
user@host# show access address-assignment
pool p1 {
family inet {
network 203.0.113.1/10;
range r1 {
low 203.0.113.5;
high 203.0.113.20;
}
}
}
[edit]
user@host# show chassis cluster
control-link-recovery;
reth-count 4;
heartbeat-interval 2000;
redundancy-group 0 {
node 0 priority 200;
node 1 priority 1;
}
[edit]
user@host# show interfaces reth1
redundant-ether-options {
redundancy-group 1;
}
unit 0 {
family inet {
address 10.1.1.1.24;
}
}
[edit]
user@host# show interfaces ge-0/0/1 unit 0 family inet
dhcp-client {
client-identifier user-id ascii 00:0a:12:00:12:12;
lease-time 86400;
retransmission-attempt 6;
retransmission-interval 5;
server-address 10.1.1.1;
vendor-id ether;
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Purpose Verify that the DHCP server is working in chassis cluster mode.
Action From operational mode, enter the show dhcp server binding and show dhcp server statistics
commands.
Packets dropped:
Total 0
dhcp-service total 0
Messages received:
BOOTREQUEST 2
DHCPDECLINE 0
DHCPDISCOVER 1
DHCPINFORM 0
DHCPRELEASE 0
DHCPREQUEST 1
Messages sent:
BOOTREPLY 2
DHCPOFFER 1
DHCPACK 0
DHCPNAK 0
DHCPFORCERENEW 0
Meaning The sample output shows that DHCP servers configured in the example work in a chassis
cluster.
15.1X49-D60 Starting with Junos OS Release 15.1X49-D60, the legacy DHCPD (DHCP
daemon) configuration on all SRX Series devices has been deprecated
and only the new DHCP CLI is supported.
This example shows how to configure the device as a DHCP client in chassis cluster
mode.
Requirements
This example uses the following hardware and software components:
• Determine the IP address pools and the lease durations to use for each subnet.
• Obtain the MAC addresses of the clients that require permanent IP addresses. Determine
the IP addresses to use for these clients.
• List the IP addresses that are available for the servers and devices on your network;
for example, DNS, NetBIOS servers, boot servers, and gateway devices.
• Determine the DHCP options required by the subnets and clients in your network.
Overview
In this example, you configure two SRX Series devices as DHCP clients and a third SRX
Series device as a DHCP server. Configure the two DHCP clients in chassis cluster mode.
For DHCP clients, you specify the interface as reth1, set the logical unit as 0, and create
a DHCP inet family. You then specify the DHCP client identifier as 00:0a:12:00:12:12 in
hexadecimal. You use hexadecimal if the client identifier is a MAC address. You set the
options no-hostname if you do not want the DHCP client to send the hostname with the
packets. You set the DHCP lease time as 86,400 seconds. The range is from 60 through
2,147,483,647 seconds. You set the number of retransmission attempts to 6. The range
is from 0 through 6, and the default is 4. You set the retransmission interval to 5 seconds.
The range is from 4 through 64, and the default is 4 seconds. Finally, you set the IPv4
address of the preferred DHCP server to 203.0.113.1 and the vendor class ID to ether.
For the DHCP server, configure the SRX Series device as a DHCP local server with minimum
DHCP local server configurations. You specify the server group as g1 and enable the DHCP
local server on interface ge-0/0/2.0.
Configuration
CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.
Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
[edit]
user@host# edit interfaces reth1 unit 0 family inet dhcp-client
3. Set the hostname if you do not want the DHCP client to send hostname in the
packets (RFC option code 12).
6. Set the interval (in seconds) allowed between retransmission attempts. The range
is 4 through 64. The default is 4 seconds.
{primary:node0}[edit]
user@host# set chassis cluster reth-count 2
{primary:node0}[edit]
user@host# set chassis cluster control-link-recovery
{primary:node0}[edit]
user@host# set chassis cluster heartbeat-interval 1000
{primary:node0}[edit]
user@host# set chassis cluster redundancy-group 1 node 0 priority 100
{primary:node0}[edit]
user@host# set interfaces ge-0/0/1 gigether-options redundant-parent reth1
user@host# set interfaces reth1 redundant-ether-options redundancy-group 1
[edit interfaces]
user@host# set interfaces ge-0/0/2 unit 0 family inet address 203.0.113.1/24
[edit access]
user@host# set address-assignment pool p1 family inet network 203.0.113.0/24
user@host# set address-assignment pool p1 family inet range r1 low 203.0.113.5
user@host# set address-assignment pool p1 family inet range r1 high 203.0.113.20
Results From configuration mode, confirm your configuration by entering the show commands.
If the output does not display the intended configuration, repeat the configuration
instructions in this example to correct it.
[edit]
user@host# show interfaces reth1 unit 0 family inet
dhcp-client {
client-identifier user-id ascii 00:0a:12:00:12:12;
options no-hostname;
lease-time 86400;
retransmission-attempt 6;
retransmission-interval 5;
server-address 203.0.113.1;
vendor-id ether;
}
[edit]
user@host# show chassis cluster
control-link-recovery;
reth-count 2;
heartbeat-interval 1000;
redundancy-group 0 {
node 0 priority 100;
node 1 priority 1;
}
redundancy-group 1{
node 0 priority 100;
node 1 priority 1;
}
[edit]
user@host# show interfaces reth1
redundant-ether-options {
redundancy-group 1;
}
[edit]
user@host# show access address-assignment
pool p1 {
family inet {
network 203.0.113.0/24;
range r1 {
low 203.0.113.5;
high 203.0.113.20;
}
}
}
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Purpose Verify that the DHCP client is working in chassis cluster mode.
Action From operational mode, enter the show dhcp client binding, show dhcp client statistics
and show dhcp client binding interface reth1 detail commands.
Packets dropped:
Total 4
Send error 4
Messages received:
BOOTREPLY 3
DHCPOFFER 1
DHCPACK 2
DHCPNAK 0
DHCPFORCERENEW 0
Messages sent:
BOOTREQUEST 0
DHCPDECLINE 0
DHCPDISCOVER 5
DHCPREQUEST 8
DHCPINFORM 0
DHCPRELEASE 1
DHCPRENEW 0
DHCPREBIND 0
DHCP options:
Name: dhcp-lease-time, Value: 1 day
Name: server-identifier, Value: 10.1.1.1
Name: subnet-mask, Value: 255.255.255.0
Meaning The sample output shows that DHCP clients configured in the example work in a chassis
cluster.
You can use the J-Web user interface and the CLI to perform routine file management
operations such as archiving log files and deleting unused log files, cleaning up temporary
files and crash files, and downloading log files from the routing platform to your computer.
You can also encrypt the configuration files with the CLI to prevent unauthorized users
from viewing sensitive configuration information.
Before you perform any file management tasks, you must perform the initial device
configuration described in the Getting Started Guide for your device.
To disable the encryption of configuration files on a device and make them readable to
all:
2. Verify your permission to decrypt configuration files on this device by entering the
encryption key for the device.
[edit]
user@host# edit system
user@host# set no-encrypt-configuration-files
[edit]
user@host# commit
commit complete
To configure an encryption key in EEPROM and determine the encryption process, enter
one of the request system set-encryption-key commands in operational mode described
in Table 15 on page 517.
request system set-encryption-key Sets the encryption key and enables default configuration file
encryption:
request system set-encryption-key algorithm des Sets the encryption key and specifies configuration file
encryption by DES.
request system set-encryption-key unique Sets the encryption key and enables default configuration file
encryption with a unique encryption key that includes the
chassis serial number of the device.
request system set-encryption-key des unique Sets the encryption key and specifies configuration file
encryption by DES with a unique encryption key.
2. Configure an encryption key in EEPROM and determine the encryption process; for
example, enter the request system set-encryption-key command.
3. At the prompt, enter the encryption key. The encryption key must have at least six
characters.
[edit]
user@host# edit system
user@host# set encrypt-configuration-files
[edit]
user@host# commit
commit complete
When you modify the encryption key, the configuration files are decrypted and then
reencrypted with the new encryption key.
2. Configure a new encryption key in EEPROM and determine the encryption process;
for example, enter the request system set-encryption-key command.
3. At the prompt, enter the new encryption key. The encryption key must have at least
six characters.
You can use the J-Web user interface to rotate log files and delete unnecessary files on
the device. If you are running low on storage space, the file cleanup procedure quickly
identifies files that can be deleted.
• Rotates log files—Archives all information in the current log files and creates fresh log
files.
• Deletes log files in /var/log—Deletes any files that are not currently being written to.
• Deletes temporary files in /var/tmp—Deletes any files that have not been accessed
within two days.
• Deletes all crash files in /var/crash—Deletes any core files that the device has written
during an error.
• Deletes all software images (*.tgz files) in /var/sw/pkg—Deletes any software images
copied to this directory during software upgrades.
To rotate log files and delete unnecessary files with the J-Web user interface:
2. In the Clean Up Files section, click Clean Up Files. The device rotates log files and
identifies the files that can be safely deleted.
The J-Web user interface displays the files that you can delete and the amount of
space that will be freed on the file system.
• To delete the files and return to the Files page, click OK.
• To cancel your entries and return to the list of files in the directory, click Cancel.
You can use the CLI request system storage cleanup command to rotate log files and
delete unnecessary files on the device. If you are running low on storage space, the file
cleanup procedure quickly identifies files that can be deleted.
• Rotates log files—Archives all information in the current log files, deletes old archives,
and creates fresh log files.
• Deletes log files in /var/log—Deletes any files that are not currently being written to.
• Deletes temporary files in /var/tmp—Deletes any files that have not been accessed
within two days.
• Deletes all crash files in /var/crash—Deletes any core files that the device has written
during an error.
• Deletes all software images (*.tgz files) in /var/sw/pkg—Deletes any software images
copied to this directory during software upgrades.
To rotate log files and delete unnecessary files with the CLI:
2. Rotate log files and identify the files that can be safely deleted.
The device rotates log files and displays the files that you can delete.
NOTE: You can issue the request system storage cleanup dry-run command
to review the list of files that can be deleted with the request system storage
cleanup command, without actually deleting the files.
NOTE:
On SRX Series devices, the /var hierarchy is hosted in a separate partition
(instead of the root partition). If Junos OS installation fails as a result of
insufficient space:
• Use the request system storage cleanup command to delete temporary files.
• Delete any user-created files in both the root partition and under the /var
hierarchy.
Deleting Files
You can use the J-Web user interface to delete an individual file from the device. When
you delete the file, it is permanently removed from the file system.
CAUTION: If you are unsure whether to delete a file from the device, we
recommend using the Cleanup Files tool. This tool determines which files can
be safely deleted from the file system.
2. In the Download and Delete Files section, click one of the following file types:
• Log Files—Lists the log files located in the /var/log directory on the device.
• Temporary Files—Lists the temporary files located in the /var/tmp directory on the
device.
• Old Junos OS—Lists the software images in the (*.tgz files) in the /var/sw/pkg
directory on the device.
• Crash (Core) Files—Lists the core files located in the /var/crash directory on the
device.
The J-Web user interface displays the files located in the directory.
4. Click Delete.
The J-Web user interface displays the files you can delete and the amount of space
that will be freed on the file system.
• To delete the files and return to the Files page, click OK.
• To cancel your entries and return to the list of files in the directory, click Cancel.
Junos OS keeps a backup image of the software that was previously installed so that
you can downgrade to that version of the software if necessary. You can use the J-Web
user interface to delete this backup image. If you delete this image, you cannot downgrade
to this particular version of the software.
2. Review the backup image information listed in the Delete Backup Junos Package
section.
3. Click the Delete backup Junos package link to delete the backup image.
• To delete the backup image and return to the Files page, click OK.
• To cancel the deletion of the backup image and return to the Files page, click Cancel.
Downloading Files
You can use the J-Web user interface to download a copy of an individual file from the
device. When you download a file, it is not deleted from the file system.
2. In the Download and Delete Files section, click one of the following file types:
• Log Files—Lists the log files located in the /var/log directory on the device.
• Temporary Files—Lists the temporary files located in the /var/tmp directory on the
device.
• Old Junos OS—Lists the software images located in the (*.tgz files) in the /var/sw/pkg
directory on the device.
• Crash (Core) Files—Lists the core files located in the /var/crash directory on the
device.
The J-Web user interface displays the files located in the directory.
Supported Platforms EX Series, M Series, MX Series, OCX1100, PTX Series, QFX Series, SRX Series, T Series
With RADIUS accounting enabled, Juniper Networks routers or switches, acting as RADIUS
clients, can notify the RADIUS server about user activities such as software logins,
configuration changes, and interactive commands. The framework for RADIUS accounting
is described in RFC 2866.
• login—Audit logins
server {
server-address {
accounting-port port-number;
secret password;
source-address address;
retry number;
timeout seconds;
}
}
server-address specifies the address of the RADIUS server. To configure multiple RADIUS
servers, include multiple server statements.
NOTE: If you enable RADIUS accounting at the [edit access profile profile-name
accounting-order] hierarchy level, accounting is triggered on the default port
of 1813 even if you do not specify a value for the accounting-port statement.
You must specify a secret (password) that the local router or switch passes to the RADIUS
client by including the secret statement. If the password contains spaces, enclose the
entire password in quotation marks (“ “).
In the source-address statement, specify a source address for the RADIUS server. Each
RADIUS request sent to a RADIUS server uses the specified source address. The source
address is a valid IPv4 address (in case if radius-server address is IPv4) or IPv6 address
(in case if radius-server address is IPv6) configured on one of the router or switch
interfaces.
Optionally, you can specify the number of times that the router or switch attempts to
contact a RADIUS authentication server by including the retry statement. By default, the
router or switch retries three times. You can configure the router or switch to retry from
1 through 10 times.
Optionally, you can specify the length of time that the local router or switch waits to
receive a response from a RADIUS server by including the timeout statement. By default,
the router or switch waits 3 seconds. You can configure the timeout to be from 1 through
90 seconds.
Starting with Junos OS Release 14.1, you can configure the enhanced-accounting statement
to view the attribute values of a logged in user. If you use the enhanced-accounting
statement at the [edit system radius-options] hierarchy level, the RADIUS attributes such
as access method, remote port, and access privileges can be audited. You can limit the
number of attribute values to be displayed for auditing by using the enhanced-avs-max
<number> statement at the [edit system accounting] hierarchy level.
When a Juniper Networks router or switch is configured with RADIUS accounting, it sends
Accounting-Start and Accounting-Stop messages to the RADIUS server. These messages
contain information about user activities such as software logins, configuration changes,
and interactive commands. This information is typically used for monitoring a network,
collecting usage statistics, and ensuring that users are billed properly.
The following example shows three servers (10.5.5.5, 10.6.6.6, and 10.7.7.7) configured
for RADIUS accounting:
system {
accounting {
events [ login change-log interactive-commands ];
destination {
radius {
server {
10.5.5.5 {
accounting-port 3333;
secret $ABC123;
source-address 10.1.1.1;
retry 3;
timeout 3;
}
10.6.6.6 secret $ABC123;
10.7.7.7 secret $ABC123;
}
}
}
}
}
14.1 Starting with Junos OS Release 14.1, you can configure the
enhanced-accounting statement to view the attribute values of a logged
in user.
If you configure your SRX300, SRX320, SRX340, SRX345, SRX550M, or SRX1500 devices
to capture accounting data in log files, set the location for your accounting files to the
DRAM.
The default location for accounting files is the cfs/var/log directory on the CompactFlash
(CF) card. The nonpersistent option minimizes the read/write traffic to your CF card. We
recommend that you use the nonpersistent option for all accounting files configured on
your system.
2. Create an accounting data log file in DRAM and replace filename with the name of
the file.
[edit]
user@host# edit accounting-options file filename
[edit]
user@host# set file filename nonpersistent
CAUTION: If log files for accounting data are stored on DRAM, these files are
lost when the device reboots. Therefore, we recommend that you back up
these files periodically.
• License ID—Alphanumeric string that uniquely identifies the license key. When a license
is generated, it is given a license ID.
• License data—Block of binary data that defines and stores all license key objects.
For example, in the following typical license key, the string XXXXXXXXXX is the license
ID, and the trailing block of data is the license data:
The license data defines the device ID for which the license is valid and the version of the
license.
Feature Summary
Feature Name of the licensed feature:
Licenses Used Number of licenses currently being used on the device. Usage is determined by the
configuration on the device. If a feature license exists and that feature is configured, the
license is considered used.
Licenses Installed Number of licenses installed on the device for the particular feature.
Licenses Needed Number of licenses required for legal use of the feature. Usage is determined by the
configuration on the device: If a feature is configured and the license for that feature is not
installed, a single license is needed.
Installed Licenses
ID Unique alphanumeric ID of the license.
Group If the license defines a group license, this field displays the group definition.
If the license requires a group license, this field displays the required group definition.
NOTE: Because group licenses are currently unsupported, this field is always blank.
Enabled Features Name of the feature that is enabled with the particular license.
Expiry Verify that the expiration information for the license is correct.
For Junos OS, only permanent licenses are supported. If a license has expired, it is shown as
invalid.
For information about how to purchase a software license, contact your Juniper Networks
sales representative at http://www.juniper.net/in/en/contact-us/. Platform support
depends on the Junos OS release in your installation.
Each feature license is tied to exactly one software feature, and that license is valid for
exactly one device.
NOTE: For the most up-to-date license models available, contact your Juniper
account team.
2. Under Installed Licenses, click Display Keys to display all the license keys installed on
the device.
A screen displaying the license keys in text format appears. Multiple licenses are
separated by a blank line.
2. Under Installed Licenses, click Download Keys to download all the license keys installed
on the device to a single file.
3. Select Save it to disk and specify the file to which the license keys are to be written.
1. Gather the authorization code that you received when you purchased your license as
well as your device serial number.
https://www.juniper.net/lcrs/generateLicense.do
3. Enter the device serial number and authorization code in the webpage and click
Generate. Depending on the type of license you purchased, you will receive one of the
following responses:
• License key—If you purchased a perpetual license, you will receive a license key
from the licensing management system. You can enter this key directly into the
system to activate the feature on your device.
1. From operational mode, save the installed license keys to a file or URL.
For example, the following command saves the installed license keys to a file named
license.config:
NOTE: The request system license update command will always use the
default Juniper license server https://ae1.juniper.net
You can only use this command to update subscription-based licenses (such as
UTM).
Requirements
Before you begin, confirm that your Junos OS feature requires you to purchase, install,
and manage a separate software license.
Overview
You can add a license key from a file or URL, from a terminal, or from the J-Web user
interface. Use the filename option to activate a perpetual license directly on the device.
(Most feature licenses are perpetual.) Use the url to send a subscription-based license
key entitlement (such as UTM) to the Juniper Networks licensing server for authorization.
If authorized, the server downloads the license to the device and activates it.
Configuration
CLI Quick To quickly configure this section of the example, copy the following commands, paste
Configuration them into a text file, remove any line breaks, change any details necessary to match your
network configuration, copy and paste the commands into the CLI at the [edit] hierarchy
level, and then enter commit from configuration mode.
From operational mode, you can add a license key in either way:
3. Do one of the following, using a blank line to separate multiple license keys:
• In the License File URL box, type the full URL to the destination file containing the
license key to be added.
• In the License Key Text box, paste the license key text, in plain-text format, for the
license to be added.
NOTE: If you added the SRX100 Memory Upgrade license, the device
reboots immediately and comes back up as a high-memory device.
2. When prompted, enter the license key, separating multiple license keys with a blank
line. If the license key you enter is invalid, an error is generated when you press Ctrl-D
to exit license entry mode.
NOTE: If you added the SRX100 Memory Upgrade license, the device
reboots immediately and comes back up as a high-memory device.
Results From operational mode, confirm your configuration by entering the show system license
command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
License usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
bgp-reflection 0 1 0 permanent
Licenses installed:
License identifier: G0300000xxxx
License version: 2
Valid for device: JN001875AB
Features:
bgp-reflection - Border Gateway Protocol route reflection
permanent
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Purpose Verify that the expected licenses have been installed and are active on the device.
Action From operational mode, enter the show system license command.
The output shows a list of the licenses used and a list of the licenses installed on the
device and when they expire.
Purpose Verify that the licenses fully cover the feature configuration on the device.
Action From operational mode, enter the show system license usage command.
The output shows a list of the licenses installed on the device and how they are used.
Purpose Verify that the license keys were installed on the device.
Action From operational mode, enter the show system license keys command.
The output shows a list of the license keys installed on the device. Verify that each
expected license key is present.
Requirements
Before you delete a license key, confirm that it is no longer needed.
Overview
You can delete a license key from the CLI or J-Web user interface. In this example, the
license ID is G0300000xxxx.
Configuration
CLI Quick To quickly configure this section of the example, copy the following commands, paste
Configuration them into a text file, remove any line breaks, change any details necessary to match your
network configuration, copy and paste the commands into the CLI at the [edit] hierarchy
level, and then enter commit from configuration mode.
2. Select the check box of the license or licenses you want to delete.
3. Click Delete.
NOTE: If you deleted the SRX100 Memory Upgrade license, the device
reboots immediately and comes back up as a low-memory device.
NOTE: If you deleted the SRX100 Memory Upgrade license, the device
reboots immediately and comes back up as a low-memory device.
Results From configuration mode, confirm your deletion by entering the show system license
command. The license key you deleted will be removed. If the output does not display
the intended configuration, repeat the configuration instructions in this example to correct
it.
If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the configuration is working properly.
Purpose Verify that the expected licenses have been removed from the device.
Action From operational mode, enter the show system license command.
Configuration Statements
address-assignment (Access)
Syntax address-assignment {
abated-utilization percentage;
abated-utilization-v6 percentage;
high-utilization percentage;
high-utilization-v6 percentage;
neighbor-discovery-router-advertisement ndra-name;
pool pool-name {
family {
inet {
dhcp-attributes {
boot-file boot-file-name;
boot-server boot-server-name;
domain-name domain-name;
grace-period seconds;
maximum-lease-time (seconds | infinite);
name-server ipv4-address;
netbios-node-type (b-node | h-node | m-node | p-node);
next-server next-server-name;
option dhcp-option-identifier-code {
array {
byte [8-bit-value];
flag [ false| off |on |true];
integer [32-bit-numeric-values];
ip-address [ip-address];
short [signed-16-bit-numeric-value];
string [character string value];
unsigned-integer [unsigned-32-bit-numeric-value];
unsigned-short [16-bit-numeric-value];
}
byte 8-bit-value;
flag (false | off | on | true);
integer 32-bit-numeric-values;
ip-address ip-address;
short signed-16-bit-numeric-value;
string character string value;
unsigned-integer unsigned-32-bit-numeric-value;
unsigned-short 16-bit-numeric-value;
}
option-match {
option-82 {
circuit-id match-value {
range range-name;
}
remote-id match-value;
range range-name;
}
}
}
propagate-ppp-settings [interface-name];
propagate-settings interface-name;
router ipv4-address;
server-identifier ip-address;
sip-server {
ip-address ipv4-address;
name sip-server-name;
}
tftp-server server-name;
wins-server ipv4-address;
}
host hostname {
hardware-address mac-address;
ip-address reserved-address;
}
network network address;
range range-name {
high upper-limit;
low lower-limit;
}
excluded-range range-name
high upper-limit;
low lower-limit;
}
xauth-attributes {
primary-dns ip-address;
primary-wins ip-address;
secondary-dns ip-address;
secondary-wins ip-address;
}
}
inet6 {
dhcp-attributes {
dns-server ipv6-address;
grace-period seconds;
maximum-lease-time (seconds | infinite);
option dhcp-option-identifier-code {
array {
byte [8-bit-value];
flag [ false| off |on |true];
integer [32-bit-numeric-values];
ip-address [ip-address];
short [signed-16-bit-numeric-value];
string [character string value];
unsigned-integer [unsigned-32-bit-numeric-value];
unsigned-short [16-bit-numeric-value];
}
byte 8-bit-value;
flag (false | off | on | true);
integer 32-bit-numeric-values;
ip-address ip-address;
short signed-16-bit-numeric-value;
string character string value;
unsigned-integer unsigned-32-bit-numeric-value;
unsigned-short 16-bit-numeric-value;
}
propagate-ppp-settings [interface-name];
sip-server-address ipv6-address;
sip-server-domain-name domain-name;
}
prefix ipv6-network-prefix;
range range-name {
high upper-limit;
low lower-limit;
prefix-length delegated-prefix-length;
}
excluded-range range-name
high upper-limit;
low lower-limit;
}
}
link pool-name;
}
}
Release Information Statement introduced in Junos OS Release 10.4 for SRX300, SRX320, SRX340, SRX345,
SRX550HM devices.
Description The address-assignment pool feature enables you to create IPv4 and IPv6 address pools
that different client applications can share. For example, multiple client applications,
such as DHCPv4 or DHCPv6, can use an address-assignment pool to provide addresses
for their particular clients.
address-pool (Access)
allow-configuration
Description Explicitly allow configuration access to the specified levels in the hierarchy even if the
permissions set with the permissions statement do not grant such access by default.
Default If you omit this statement and the deny-configuration statement, users can edit only
those commands for which they have access privileges through the permissions statement.
allow-configuration-regexps
Description Explicitly allow configuration access to specified hierarchies using regular expressions
even if the permissions set with the permissions statement allow that access.
Default If you do not configure this statement or the deny-configuration-regexps statement, users
can edit only those commands for which they have access privileges set with the
permissions statement.
authentication-key
Description Configure Network Time Protocol (NTP) authentication keys so that the SRX Series
device can send authenticated packets. If you configure the SRX Series device to operate
in authenticated mode, you must configure a key.
Both the keys and the authentication scheme (MD5) must be identical between a set of
peers sharing the same key number.
value password—The key itself, which can be from 1 through 8 ASCII characters. If the key
contains spaces, enclose it in quotation marks.
authentication-order
Description Configure the order in which the software tries different user authentication methods
when attempting to authenticate a user. For each login attempt, the software tries the
authentication methods in order, starting with the first one, until the password matches.
Default If you do not include the authentication-order statement, users are verified based on their
configured passwords.
Options One or more of the following authentication methods listed in the order in which they
must be tried:
• password—Use the password configured for the user with the authentication statement
at the [edit system login user] hierarchy level.
boot-server (NTP)
Description Configure the server that NTP queries when the SRX Series device boots to determine
the local date and time.
When you boot the SRX Series device, it issues an ntpdate request, which polls a network
server to determine the local date and time. You need to configure a server that the SRX
Series device uses to determine the time when the SRX Series device boots. You can
configure either an IP address or a hostname for the boot server. If you configure a
hostname instead of an IP address, the ntpdate request resolves the hostname to an IP
address when the SRX Series device boots up.
If you configure an NTP boot server, then when the SRX Series device boots, it immediately
synchronizes with the boot server even if the NTP process is explicitly disabled or if the
time difference between the client and the boot server exceeds the threshold value of
1000 seconds.
broadcast
Description Configure the SRX Series device to operate in broadcast mode with the remote system
at the specified address. In this mode, the SRX Series device sends periodic broadcast
messages to a client population at the specified broadcast or multicast address. Normally,
you include this statement only when the SRX Series device is operating as a transmitter.
Options address—The broadcast address on one of the local networks or a multicast address
assigned to NTP. You must specify an address, not a hostname. If the multicast
address is used, it must be 224.0.1.1.
key key-number—(Optional) All packets sent to the address include authentication fields
that are encrypted using the specified key number.
Range: Any unsigned 32-bit integer
version value—(Optional) Specify the version number to be used in outgoing NTP packets.
Range: 1 through 4
Default: 4
broadcast-client
Syntax broadcast-client;
Description Configure the SRX Series device to listen for broadcast messages on the local network
to discover other servers on the same subnet.
ciphers
Description Specify the set of ciphers the SSH server can use to perform encryption and decryption
functions.
Options • 3des-cbc—Triple Data Encryption Standard (DES) in Cipher Block Chaining (CBC)
mode.
NOTE: Ciphers represent a set. To configure SSH ciphers use the set command
as shown in the following example:
Related • Configuring SSH Service for Remote Access to the Router or Switch
Documentation
• key-exchange
connection-limit
Description Configure the maximum number of connection sessions for each type of system services
(finger, ftp, ssh, telnet, xnm-clear-text, or xnm-ssl) per protocol (either IPv6 or IPv4).
Options limit—Maximum number of established connections per protocol (either IPv6 or IPv4).
On SRX5400, SRX5600, and SRX5800 devices, the range and default value are as
follows:
Range: 1 through 250
Default: 75
On SRX300, SRX320, SRX340, and SRX345, and SRX550M devices, the range is as
follows:
Range: 1 through 5
client-ia-type
Syntax client-ia-type {
ia-na;
ia-pd;
}
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family inet6 dhcpv6-client]
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX550M, and SRX1500 devices.
client-identifier (dhcp-client)
Syntax client-identifier {
user-id {ascii ascii hexadecimal hexadecimal;
use-interface-description {logical |device};
prefix [host-name routing-instance-name];
}
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcp-client]
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Options The remaining statements are explained separately. See CLI Explorer.
client-identifier (dhcpv6-client)
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client]
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
client-list-name (SNMP)
Description Specify the name of the list of SNMP network management system (NSM) clients that
are authorized to collect information about network operations. You cannot use an SNMP
client list and individually configured SNMP clients in the same configuration.
Options client-list-name — Name of the client list. Client list is the list of IP address prefixes defined
with the prefix-list statement in the policy-options hierarchy.
client-type
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family inet6 dhcpv6-client]
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX550M, and SRX1500 devices.
deny-configuration
Description Explicitly deny configuration access to the specified levels in the hierarchy even if the
permissions set with the permissions statement grant such access by default.
Default If you omit this statement and the allow-configuration statement, users can edit those
levels in the configuration hierarchy for which they have access privileges through the
permissions statement.
deny-configuration-regexps
Description Explicitly deny configuration access to specified hierarchies using regular expressions
even if the permissions set with the permissions statement allow that access.
Default If you do not configure this statement or the deny-configuration-regexps statement, users
can edit only those commands for which they have access privileges set with the
permissions statement.
destination (Accounting)
Syntax destination {
radius {
server {
server-address {
accounting-port port-number;
max-outstanding-requests value;
port port-number;
retry value;
secret password;
source-address source-address;
timeout seconds;
}
}
}
tacplus {
server {
server-address {
port port-number;
secret password;
single-connection;
timeout seconds;
}
}
}
}
Options The remaining statements are explained separately. See CLI Explorer.
Syntax dhcp-attributes {
boot-file boot-file-name;
boot-server boot-server-name;
domain-name domain-name;
grace-period seconds;
maximum-lease-time (seconds | infinite);
name-server ipv4-address;
netbios-node-type (b-node | h-node | m-node | p-node);
next-server next-server-name;
option dhcp-option-identifier-code {
array {
byte [8-bit-value];
flag [ false| off |on |true];
integer [32-bit-numeric-values];
ip-address [ip-address];
short [signed-16-bit-numeric-value];
string [character string value];
unsigned-integer [unsigned-32-bit-numeric-value];
unsigned-short [16-bit-numeric-value];
}
byte 8-bit-value;
flag (false | off | on | true);
integer 32-bit-numeric-values;
ip-address ip-address;
short signed-16-bit-numeric-value;
string character string value;
unsigned-integer unsigned-32-bit-numeric-value;
unsigned-short 16-bit-numeric-value;
}
option-match {
option-82 {
circuit-id match-value {
range range-name;
}
remote-id match-value;
range range-name;
}
}
}
propagate-ppp-settings [interface-name];
propagate-settings interface-name;
router ipv4-address;
server-identifier ip-address;
sip-server {
ip-address ipv4-address;
name sip-server-name;
}
tftp-server server-name;
wins-server ipv4-address;
}
Description Configure attributes for IPv4 address pools that can be used by different clients. The
DHCP attributes for this statement uses standard IPv4 DHCP options.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
Syntax dhcp-attributes {
dns-server ipv6-address;
grace-period seconds;
maximum-lease-time (seconds | infinite);
option dhcp-option-identifier-code {
array {
byte [8-bit-value];
flag [ false| off |on |true];
integer [32-bit-numeric-values];
ip-address [ip-address];
short [signed-16-bit-numeric-value];
string [character string value];
unsigned-integer [unsigned-32-bit-numeric-value];
unsigned-short [16-bit-numeric-value];
}
byte 8-bit-value;
flag (false | off | on | true);
integer 32-bit-numeric-values;
ip-address ip-address;
short signed-16-bit-numeric-value;
string character string value;
unsigned-integer unsigned-32-bit-numeric-value;
unsigned-short 16-bit-numeric-value;
}
propagate-ppp-settings [interface-name];
sip-server-address ipv6-address;
sip-server-domain-name domain-name;
}
Description Configure attributes for address pools that can be used by different clients.
Options • dns-server IPv6-address—Specify a DNS server to which clients can send DNS queries.
• grace-period seconds —Specify the grace period offered with the lease.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
dhcp-client
Syntax dhcp-client {
client-identifier {
prefix {
host-name;
logical-system-name;
routing-instance-name;
}
use-interface-description (device | logical);
user-id (ascii string| hexadecimal string);
}
lease-time (length | infinite);
retransmission-attempt value;
retransmission-interval seconds;
server-address server-address;
update-server;
vendor-id vendor-id ;
}
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Options The remaining statements are explained separately. See CLI Explorer.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
Syntax dhcp-local-server {
dhcpv6 {
authentication {
password password;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name;
interface-name;
logical-system-name;
relay-agent-interface-id;
relay-agent-remote-id;
relay-agent-subscriber-id;
routing-instance-name;
user-prefix user-prefix;
}
}
dynamic-profile {
profile-name;
aggregate-clients {
merge;
replace;
}
junos-default-profile;
use-primary dynamic-profile-name;
}
group group-name {
authentication {
password password;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name;
interface-name;
logical-system-name;
relay-agent-interface-id;
relay-agent-remote-id;
relay-agent-subscriber-id;
routing-instance-name;
user-prefix user-prefix;
}
}
dynamic-profile {
profile-name;
aggregate-clients {
merge;
replace;
}
junos-default-profile;
use-primary dynamic-profile;
}
interface interface-name {
dynamic-profile {
profile-name;
aggregate-clients {
merge;
replace;
}
junos-default-profile;
use-primary dynamic-profile-name;
}
exclude;
overrides {
delegated-pool pool-name;
interface-client-limit number;
process-inform {
pool pool-name;
}
rapid-commit ;
}
service-profile service-profile-name
trace ;
upto interface-name;
}
liveness-detection {
failure-action {
clear-binding;
clear-binding-if-interface-up;
log-only;
}
method {
bfd {
detection-time {
threshold milliseconds;
}
holddown-interval interval;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
session-mode (automatic | multihop | single-hop);
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (0 | 1 | automatic);
}
}
overrides {
delegated-pool pool-name;
interface-client-limit number;
process-inform {
pool pool-name;
}
rapid-commit ;
}
reconfigure {
attempts number;
clear-on-abort;
strict;
timeout number;
token token-name;
trigger {
radius-disconnect;
}
}
service-profile service-profile-name;
}
liveness-detection {
failure-action {
clear-binding;
clear-binding-if-interface-up;
log-only;
}
method {
bfd {
detection-time {
threshold milliseconds;
}
holddown-interval interval;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
session-mode (automatic | multihop | single-hop);
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (0 | 1 | automatic);
}
}
overrides {
delegated-pool pool-name;
interface-client-limit number;
process-inform {
pool pool-name;
}
rapid-commit ;
}
reconfigure {
attempts number;
clear-on-abort;
strict;
timeout number;
token token-name;
trigger {
radius-disconnect;
}
}
service-profile service-profile-name;
}
group group-name {
interface interface-name {
exclude;
upto upto-interface-name;
}
}
}
Description Configure DHCP Local Server for DHCPv6, forwarding snoop (unicast) packets, and
setting traceoptions.
Options The remaining statements are explained separately. See CLI Explorer.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
Syntax dhcpv6 {
authentication {
password password;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name;
interface-name;
logical-system-name;
relay-agent-interface-id;
relay-agent-remote-id;
relay-agent-subscriber-id;
routing-instance-name;
user-prefix user-prefix;
}
}
dynamic-profile {
profile-name;
aggregate-clients {
merge;
replace;
}
junos-default-profile;
use-primary dynamic-profile-name;
}
group group-name {
authentication {
password password;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name;
interface-name;
logical-system-name;
relay-agent-interface-id;
relay-agent-remote-id;
relay-agent-subscriber-id;
routing-instance-name;
user-prefix user-prefix;
}
}
dynamic-profile {
profile-name;
aggregate-clients {
merge;
replace;
}
junos-default-profile;
use-primary dynamic-profile;
}
interface interface-name {
dynamic-profile {
profile-name;
aggregate-clients {
merge;
replace;
}
junos-default-profile;
use-primary dynamic-profile-name;
}
exclude;
overrides {
delegated-pool pool-name;
interface-client-limit number;
process-inform {
pool pool-name;
}
rapid-commit ;
}
service-profile service-profile-name
trace ;
upto interface-name;
}
liveness-detection {
failure-action {
clear-binding;
clear-binding-if-interface-up;
log-only;
}
method {
bfd {
detection-time {
threshold milliseconds;
}
holddown-interval interval;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
session-mode (automatic | multihop | single-hop);
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (0 | 1 | automatic);
}
}
overrides {
delegated-pool pool-name;
interface-client-limit number;
process-inform {
pool pool-name;
}
rapid-commit ;
}
reconfigure {
attempts number;
clear-on-abort;
strict;
timeout number;
token token-name;
trigger {
radius-disconnect;
}
}
service-profile service-profile-name;
}
liveness-detection {
failure-action {
clear-binding;
clear-binding-if-interface-up;
log-only;
}
method {
bfd {
detection-time {
threshold milliseconds;
}
holddown-interval interval;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
session-mode (automatic | multihop | single-hop);
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (0 | 1 | automatic);
}
}
overrides {
delegated-pool pool-name;
interface-client-limit number;
process-inform {
pool pool-name;
}
rapid-commit ;
}
reconfigure {
attempts number;
clear-on-abort;
strict;
timeout number;
token token-name;
trigger {
radius-disconnect;
}
}
service-profile service-profile-name;
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
dhcpv6-client
Syntax dhcpv6-client {
client-ia-type {
ia-na;
ia-pd;
}
client-identifier duid-type (duid-ll | duid-llt | vendor);
client-type (autoconfig | statefull);
rapid-commit;
req-option (dns-server | domain | fqdn | nis-domain | nis-server | ntp-server | sip-domain
| sip-server |time-zone | vendor-spec);
retransmission-attempt number;
update-router-advertisement {
interface interface-name;
}
update-server;
}
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX550M, and SRX1500 devices.
Description Configure the Dynamic Host Configuration Protocol version 6 (DHCPv6) client.
Options client-ia-type— Identity association type for DHCPv6 client. This statement is mandatory.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• Minimum DHCPv6 Client Configuration on page 492
Syntax disable;
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
dlv
Syntax dlv {
domain-name domain-name trusted-anchor trusted-anchor;
}
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
dynamic-pool
Syntax address-assignment {
dynamic-pool <dynamic-pool>{
family {
inet6 {
from-interface <interface>;
delegated-prefix-length <network-prefix-length>;
range <range-name> {
masked-low <masked-low>;
masked-high <masked-high>;
prefix-length <prefix-length>;
}
dhcp-attributes {
dns-server <address>;
t1-percentage <t1-percentage>;
t2-percentage <t2-percentage>;
preferred-lifetime <preferred-lifetime>;
valid-lifetime <valid-lifetime>;
}
}
}
}
}
Description Configure the dynamic pool updated by the client running on the WAN interface.
dynamic-server
Syntax dhcpv6 {
dynamic-server {
group <group> {
neighbor-discovery-router-advertisement <ndra-pool>;
interface <interface> {
overrides {
delegated-pool <delegated-pool>;
ia-na-pool <ia-na-pool>;
process-inform {
pool <pool>;
}
}
}
}
}
}
Syntax family {
inet6 {
mode (drop | flow-based | packet-based);
}
iso {
mode packet-based;
}
mpls {
mode packet-based;
}
}
Options The remaining statements are explained separately. See CLI Explorer.
Release Information Statement introduced before Junos OS Release 12.1X47 for SRX Series.
• no-binary-data—Do not mark the file such that it contains binary data.
• start-time—Specify the start time for file transmission. Enter the start time in the
yyyy-mm-dd.hh:mm format.
• brief—Omit English language text from the end of the logged message.
forwarding-options (Security)
Syntax forwarding-options {
family {
inet6 {
mode (drop | flow-based | packet-based);
}
iso {
mode packet-based;
}
mpls {
mode packet-based;
}
}
}
Description Determine how the inet6, iso, and mpls protocol families manage security forwarding
options.
NOTE:
• Packet-based processing is not supported on the following SRX Series
devices: SRX5400, SRX5600, and SRX5800.
• On SRX Series devices, the default mode for processing traffic is flow mode.
To configure an SRX Series device as a border router, you must change the
mode from flow-based processing to packet-based processing. Use the
set security forwarding-options family mpls mode packet-based statement
to configure the SRX device to packet mode. You must reboot the device
for the configuration to take effect.
Options The remaining statements are explained separately. See CLI Explorer.
failure-action {
clear-binding;
clear-binding-if-interface-up;
log-only;
}
method {
bfd {
detection-time {
threshold milliseconds;
}
holddown-interval interval;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
session-mode (automatic | multihop | single-hop);
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (0 | 1 | automatic);
}
}
overrides {
delegated-pool pool-name;
interface-client-limit number;
process-inform {
pool pool-name;
}
rapid-commit ;
}
reconfigure {
attempts number;
clear-on-abort;
strict;
timeout number;
token token-name;
trigger {
radius-disconnect;
}
}
service-profile service-profile-name;
}
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• DHCP Server Configuration Overview on page 448
• rsa-key rsa-key—RSA public key algorithm, which supports encryption and digital
signatures for SSH version 1 and SSH version 2
• rsa1-key rsa1-key—RSA public key algorithm, which supports encryption and digital
signatures for SSH version 1
Related • Generating an SSL Certificate Using the openssl Command on page 356
Documentation
• Generating a Self-Signed SSL Certificate on page 356
hostkey-algorithm
Description Allow or disallow a host-key signature algorithm for the SSH host to use to authenticate
another host.
NOTE: DSA keys are not supported in FIPS, so the ssh-dss option is not
available on systems operating in FIPS mode.
Related • Generating an SSL Certificate Using the openssl Command on page 356
Documentation
• Generating a Self-Signed SSL Certificate on page 356
idle-timeout (System)
Release Information Statement introduced in Junos OS Release 16.1 for the M Series, MX Series, and PTX
Series.
Statement introduced in Junos OS Release 15.1X49-D70 for the vSRX, SRX4100, SRX4200
and SRX1500 devices.
Description Configure the maximum time for which the C shell or CLI console session can be idle.
The user (including the root user) is logged out after the expiry of idle-timeout.
Description Specify one or more interfaces, or a range of interfaces, that are within a specified group
on which the DHCP local server is enabled. You can repeat the interface interface-name
statement to specify multiple interfaces within a group, but you cannot specify the same
interface in more than one group.
• upto upto-interface-name—The upper end of the range of interfaces; the lower end of
the range is the interface-name entry. The interface device name of the
upto-interface-name must be the same as the device name of the interface-name.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• DHCP Server Configuration Overview on page 448
interfaces (ARP)
Syntax interfaces {
interface-name {
aging-timer minutes;
}
}
Description Specify the Address Resolution Protocol (ARP) aging timer in minutes for a logical
interface.
Default: 20
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• DHCP Server Configuration Overview on page 448
Description Specify the set of interfaces that are part of the zone.
Syntax interface-traceoptions {
file {
filename ;
files number;
match regular-expression;
size maximum-file-size;
(world-readable | no-world-readable);
}
flag flag;
level (all | error | info | notice | verbose | warning);
no-remote-trace;
}
Description Configure extended DHCP local server tracing operations that can be enabled on a specific
interface or group of interfaces. You use the interface interface-name trace statement at
the [edit system services group group-name] hierarchy level to enable the tracing operation
on the specific interfaces.
Options file-name—Name of the file to receive the output of the tracing operation. Enclose the
name in quotation marks (“ ”). All files are placed in a file named jdhcpd in the
directory /var/log. If you include the file statement, you must specify a filename.
files number—(Optional) Maximum number of trace files. When a trace file named
trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and
so on, until the maximum number of trace files is reached. Then the oldest trace file
is overwritten. If you specify a maximum number of files, you also must specify a
maximum file size with the size option.
Range: 2 through 1000
Default: 3 files
flag flag—Tracing operation to perform. To specify more than one tracing operation,
include multiple flag statements. You can include the following flags:
match regular-expression—(Optional) Refine the output to include lines that contain the
regular expression.
size size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB),
or gigabytes (GB). If you specify a maximum file size, you also must specify a
maximum number of trace files with the files option.
Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 10 KB through 1 GB
Default: 128 KB
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• DHCP Server Configuration Overview on page 448
internet-options
Syntax internet-options {
icmpv4-rate-limit {
bucket size seconds;
packet-rate packet-rate;
}
icmpv6-rate-limit {
bucket size seconds;
packet-rate packet-rate;
}
ipv6-duplicate-addr-detection-transmits number;
no-path-mtu-discovery;
no-source-quench;
no-tcp-reset;
no-tcp-rfc1323;
no-tcp-rfc1323-paws;
path-mtu-discovery;
source-port {
upper-limit range;
}
source-quench;
tcp-drop-synfin-set;
}
• no-tcp-reset—Do not send RST TCP packets for packets sent to non-listening ports.
• tcp-drop-synfin-set—Drop TCP packets that have both SYN and FIN flags.
kernel-replication (System)
Syntax kernel-replication;
lease-time (dhcp-client)
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcp-client]
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Specify the time to negotiate and exchange Dynamic Host Configuration Protocol (DHCP)
information.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
location
Syntax location {
altitude feet;
building name;
country -code code;
floor number;
hcoord horizontal-coordinate;
lata service-area;
latitude degrees;
longitude degrees;
npa-nxx number;
postal-code postal-code;
rack number;
vcoord vertical-coordinate;
}
• npa-nxx number—First six digits of the phone number (area code and exchange).
lockout-period
Description Configure the amount of time before the user can attempt to log in to the router after
being locked out due to the number of failed login attempts specified in the
tries-before-disconnect statement.
Options minutes—Amount of time before the user can attempt to log in after being locked out.
Default: Off
Range: 1 through 43200
Related • Limiting the Number of User Login Attempts for SSH and Telnet Sessions
Documentation
• Handling Authorization Failure on page 33
• retry-options
macs
Description Specify the set of message authentication code (MAC) algorithms that the SSH server
can use to authenticate messages.
Options Specify one or more of the following MAC algorithms to authenticate messages:
Related • key-exchange
Documentation
• ciphers on page 557
max-pre-authentication-packets
Description Define the number of pre-authentication SSH packets that the SSH server will accept
prior to user authentication.
Options value—Maximum number of pre-authentication SSH packets that the server will accept.
Range: 20 through 2147483647.
Default: 128
multicast-client
Description For NTP, configure the SRX Series device to listen for multicast messages on the local
network to discover other servers on the same subnet.
Options address—(Optional) One or more IP addresses. If you specify addresses, the SRX Series
device joins those multicast groups.
Default: 224.0.1.1.
name-server (Access)
Hierarchy Level [edit access address-assignment pool <name> family (inet | inet6) xauth-attributes]
neighbor-discovery-router-advertisement (Access)
Description Configure the name of the address-assignment pool used to assign the router
advertisement prefix.
Related
Documentation
ntp
Syntax ntp {
authentication-key key-number type md5 value <password>;
boot-server <address>;
broadcast <address> <key key-number> <routing-instance routing-instance-name> <version
value> <ttl value>;
broadcast-client;
multicast-client <address>;
peer address <key key-number> <version value> <prefer>;
server address <key key-number> <version value> <prefer>;
source-address source-address <routing-instance routing-instance-name>;
trusted-key [key-numbers];
}
Description Configure Network Time Protocol (NTP) on the SRX Series device.
outbound-ssh
Syntax outbound-ssh {
client client-id {
address address {
port port-number;
retry number;
timeout seconds;
}
device-id device-id;
keep-alive {
retry number;
timeout seconds;
}
reconnect-strategy (in-order | sticky);
secret password;
services netconf;
}
traceoptions {
file filename <files number> <match regex> <size size> <world-readable |
no-world-readable>;
flag flag;
no-remote-trace;
}
}
Options client client-id—Defines a device-initiated connection. This value serves to uniquely identify
the outbound-ssh configuration stanza. Each outbound-ssh stanza represents a
single outbound SSH connection. Thus, the administrator is free to assign the client-id
any meaningful unique value.
port port-number—Specifies the port at which a server listens for outbound SSH connection
requests.
retry number—Specifies the maximum number of connection attempts a device can make
to the specified IP address. The default is three attempts.
timeout seconds—Specifies how long the application waits between attempts to reconnect
to the specified IP address, in seconds. The default is 15 seconds.
device device-id—Identifies the device to the management client. Each time the device
establishes an outbound SSH connection, it first sends an initiation sequence
(device-id) to the management client.
keep-alive—Enables the device to send SSH protocol keepalive messages to the client
application. The timeout statement specifies how long the device waits to receive
data before sending a request for acknowledgment from the application. The default
is 15 seconds. The retry statement specifies how many keepalive messages the router
sends without receiving a response from the client. When that number is exceeded,
the device disconnects from the application, ending the outbound SSH connection.
The default is three retries.
secret password—Sends the device’s public SSH host key when the device connects to
the client.
Syntax overrides {
interface-client-limit number;
}
Description Override the default configuration settings for the extended DHCP local server. Specifying
the overrides statement with no subordinate statements removes all DHCP local server
overrides at that hierarchy level.
• To override global DHCP local server configuration options, include the overrides
statement and its subordinate statements at the [edit system services dhcp-local-server]
hierarchy level.
Options interface-client-limit number—Sets the maximum number of DHCP clients per interface
allowed for a specific group or for all groups. A group specification takes precedence
over a global specification for the members of that group.
Range: 1 through 500,000
Default: No limit
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
peer (NTP)
Description For NTP, configure the SRX Series device to operate in symmetric active mode with the
remote system at the specified address. In this mode, the SRX Series device and the
remote system can synchronize with each other. This configuration is useful in a network
in which either the SRX Series device or the remote system might be a better source of
time.
Options address—Address of the remote system. You must specify an address, not a hostname.
key key-number—(Optional) All packets sent to the address include authentication fields
that are encrypted using the specified key number.
Range: Any unsigned 32-bit integer
prefer—(Optional) Mark the remote system as the preferred host, which means that if
all other factors are equal, this remote system is chosen for synchronization among
a set of correctly operating systems.
version value—(Optional) Specify the NTP version number to be used in outgoing NTP
packets.
Range: 1 through 4
Default: 4
prefix
Syntax prefix {
host-name;
logical-system-name;
routing-instance-name;
}
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcp-client
client-identifier]
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Related
Documentation
profilerd
Syntax profilerd {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
}
• failover—Configure the device to reboot if the software process fails four times within
30 seconds, and specify the software to use during the reboot.
proxy
Syntax proxy {
password password;
port port-number;
server url;
username user-name;
}
radius-options
Syntax radius-options {
attributes {
nas-ip-address nas-ip-address;
}
password-protocol mschap-v2;
}
Release Information Statement introduced in Junos OS Release 8.5. Support for network access server (NAS)
IPv6 address added in Junos OS Release 12.1X47-D15 for SRX1500, SRX5400, SRX5600,
and SRX5800 devices.
Description Configure RADIUS options for the NAS-IP address for outgoing RADIUS packets and
password protocol used in RADIUS packets.
radius-server
Release Information Statement introduced in Junos OS Release 8.5. Support for IPv6 source address added
in Junos OS Release 12.1X47-D15 for SRX1500, SRX5400, SRX5600, and SRX5800
devices.
Description Configure RADIUS server address for subscriber access management, Layer 2 Tunnelling
Protocol (L2TP), or (Point-to-Point Protocol (PPP).
Default: 1813
Default: 1812
• retry value—Number of times that the router is allowed to attempt to contact a RADIUS
server.
Range: 1 through 10
Default: 3
Default: 3 seconds
rapid-commit
Syntax rapid-commit;
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client]
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX550M, and SRX1500 devices.
Description Used to signal the use of the two-message exchange for address assignment.
Syntax reconfigure {
attempts number;
clear-on-abort;
strict;
timeout number;
token token-name;
trigger {
radius-disconnect;
}
}
Description Enable dynamic reconfiguration triggered by the DHCP local server of all DHCP clients
or only the DHCP clients serviced by the specified group of interfaces. A group
configuration takes precedence over a DHCP local server configuration.
clear-on-abort —Delete all DHCP clients or only the DHCP clients serviced by the specified
group of interfaces when reconfiguration fails; that is, when the maximum number
of retry attempts have been made without success. A group configuration takes
precedence over a DHCP local server configuration.
strict —Configure the system to only allow packets that contain the reconfigure accept
option.
Default: 2 seconds
token token-name—Configure a plain-text token for all DHCP clients or only the clients
specified by the specified group of interfaces. The default is null (empty string).
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
• DHCP Server Configuration Overview on page 448
req-option
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client]
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX550M, and SRX1500 devices.
retransmission-attempt (dhcp-client)
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcp-client]
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Specify the number of times the device attempts to retransmit a Dynamic Host Control
Protocol (DHCP) packet fallback.
Range: 0 through 6
retransmission-attempt (dhcpv6-client)
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client]
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX550M, and SRX1500 devices.
Description Specify the number of times the device retransmits a DHCPv6 client packet if a DHCPv6
server fails to respond. After the specified number of attempts, no further attempts at
reaching a server are made.
Related
Documentation
retransmission-interval (dhcp-client)
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcp-client]
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Specify the initial retransmission interval. Successive retransmission intervals are doubled
as per RFC2131.
NOTE: Though the SRX series devices implement the exponential backoff,
as described in RFC 2131, the retransmit attempt does not stop when the
retransmission interval reaches 64 seconds. The packet is transmitted till
the retransmission attempt is reached. For example, if you configure the
retransmission-attempt to 5 and the retransmission-interval to 20, the sequence
of retransmission-interval is 20, 40, 80, 160, 320.
root-authentication
Syntax root-authentication {
encrypted-password password;
load-key-file URL;
plain-text-password;
ssh-dsa public-key {
<from pattern-list>;
}
ssh-rsa public-key {
<from pattern-list>;
}
}
• plain-text-password—The CLI prompts you for a password encrypts it, and stores the
encrypted version in its user database.
single-connection
Syntax single-connection;
Description Optimize the attempt to connect to a TACACS+ server. Junos OS maintains one open
TCP connection to the server for multiple requests rather than opening a connection for
each connection attempt.
server (NTP)
Description For NTP, configure the SRX Series device to operate in client mode with the remote
system at the specified address. In this mode, the SRX Series device can be synchronized
with the remote system, but the remote system can never be synchronized with the SRX
Series device.
If the NTP client time drifts so that the difference in time from the NTP server exceeds
128 milliseconds, the client is automatically stepped back into synchronization. If the
offset between the NTP client and server exceeds the 1000-second threshold, the client
still synchronizes with the server, but it also generates a system log message noting that
the threshold was exceeded.
Options address—Address of the remote system. You must specify an address, not a hostname.
prefer—(Optional) Mark the remote system as the preferred host, which means that if
all other things are equal, this remote system is chosen for synchronization among
a set of correctly operating systems.
version value—(Optional) Specify the version number to be used in outgoing NTP packets.
Range: 1 through 4
Default: 4
server-address (dhcp-client)
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcp-client]
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Specify the preferred DHCP server address that is sent to DHCP clients.
Related
Documentation
Description Specify a source address for each configured TACACS+ server, RADIUS server, or NTP
server, or the source address to record in system log messages that are directed to a
remote machine.
Options source-address—A valid IP address configured on one of the SRX Series devices. For
system logging, the address is recorded as the message source in messages sent to
the remote machines specified in all host hostname statements at the [edit system
syslog] hierarchy level, but not for messages directed to the other Routing Engine.
ssh-known-hosts
Syntax ssh-known-hosts {
fetch-from-server server-name;
host hostname {
dsa-key dsa-key;
ecdsa-sha2-nistp256-key ecdsa-sha2-nistp256-key;
ecdsa-sha2-nistp384-key ecdsa-sha2-nistp384-key;
ecdsa-sha2-nistp521-key ecdsa-sha2-nistp521-key;
rsa-key rsa-key;
rsa1-key rsa1-key;
}
load-key-file key-file;
}
Description Configure SSH support for known hosts and for administering SSH host key updates.
Related
Documentation
static-subscribers
Syntax static-subscribers {
disable;
}
Description Associate subscribers with statically configured interfaces, and provide dynamic service
activation for these subscribers.
statistics-service
Syntax statistics-service {
command binary-file-path;
disable;
}
Description Specify the Packet Forwarding Engine (PFE) statistics service management process.
subscriber-management
Syntax subscriber-management {
command binary-file-path;
disable;
}
subscriber-management-helper
Syntax subscriber-management-helper {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
}
• failover—Configure the device to reboot if the software process fails four times within
30 seconds, and specify the software to use during the reboot.
Description Use to set a master password in a hidden configuration within the Junos OS configuration
database.
tacplus
Syntax tacplus {
server server-address {
port port-number;
secret password;
single-connection;
source-address source-address;
timeout seconds;
}
}
• port number—Configure the port number on which to contact the TACACS+ server.
• timeout seconds—Configure the amount of time that the local device waits to receive
a response from a TACACS+ server.
Related • Example: Configuring a TACACS+ Server for System Authentication on page 346
Documentation
tacplus-options
Supported Platforms EX Series, M Series, MX Series, OCX1100, PTX Series, QFabric System, QFX Series, SRX Series,
T Series
Syntax tacplus-options {
(exclude-cmd-attribute | no-cmd-attribute-value);
enhanced-accounting;
service-name service-name;
timestamp-and-timezone;
}
exclude-cmd-attribute—Exclude the cmd attribute value completely from start and stop
accounting records to enable logging of accounting records in the correct log file on
a TACACS+ server.
timestamp-and-timezone—Include this statement if you want start time, stop time, and
timezone attributes included in start/stop accounting records.
Related • Configuring the Same Authentication Service for Multiple TACACS+ Servers on page 345
Documentation
• Configuring TACACS+ System Accounting
• enhanced-accounting
tacplus-server
Supported Platforms EX Series, M Series, PTX Series, SRX Series, T Series, vSRX
• secret—Password to use with the RADIUS or TACACS+ server. The secret password
used by the local router or switch must match that used by the server. Password to
use; can include spaces included in quotation marks.
• timeout—The amount of time that the local device waits to receive a response from a
RADIUS or TACACS+ server. The timeout range is 1 through 90 seconds. The default
is 3 seconds.
Related • Example: Configuring a TACACS+ Server for System Authentication on page 346
Documentation
Syntax traceoptions {
file {
filename ;
files number;
match regular-expression;
size maximum-file-size;
(world-readable | no-world-readable);
}
flag flag;
no-remote-trace;
}
• filename—Name of the file to receive the output of the tracing operation. Enclose
the name within quotation marks. All files are placed in the directory /var/log. By
default, the name of the file is the name of the process being traced.
• files number—Maximum number of trace files. When a trace file named trace-file
reaches its maximum size, it is renamed totrace-file.0 , then trace-file.1, and so on,
until the maximum number of trace files is reached. The oldest archived file is
overwritten.
If you specify a maximum number of files, you also must specify a maximum file size
with the size option and a filename.
Default: 10 files
• match regular-expression—Refine the output to include lines that contain the regular
expression.
If you specify a maximum number of files, you also must specify a maximum file size
with the size option and a filename.
Range: 10 KB through 1 GB
Default: 128 KB
• flag—Specify the tracing operation to perform. To specify more than one tracing
operation, include multiple flag statements. You can include the following flags.
trusted-key
Description For NTP, configure the keys you are allowed to use when you configure the SRX Series
device to synchronize its time with other systems on the network.
Options key-numbers—One or more key numbers. Each key can be any 32-bit unsigned integer
except 0.
uac-service
Syntax uac-service {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
}
• failover—Configure the device to reboot if the software process fails four times within
30 seconds, and specify the software to use during the reboot.
update-router-advertisement
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client]
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX550M, and SRX1500 devices.
Related
Documentation
update-server (dhcp-client)
Syntax update-server;
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcp-client]
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Related
Documentation
update-server (dhcpv6-client)
Syntax update-server;
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client]
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX550M, and SRX1500 devices.
Related
Documentation
usb-control
Syntax usb-control {
command binary-file-path;
disable;
}
Release Information Statement introduced in Junos OS Release 8.5 for SRX300, SRX320, SRX340, SRX345,
and SRX550M devices.
use-interface
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcp-client
client-identifier]
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description The description configured at the physical or logical interface level is used for client
identification.
Related
Documentation
user-id
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcp-client
client-identifier]
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Specify an ASCII or hexadecimal user ID for the Dynamic Host Configuration Protocol
(DHCP) client.
Related
Documentation
vendor-id
Hierarchy Level [edit interfaces interface-name unit logical-unit-number family family dhcp-client]
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Configure a vendor class ID for the Dynamic Host Configuration Protocol (DHCP) client.
Related
Documentation
Syntax vpn;
Description For Dynamic Host Configuration Protocol (DHCP) or BOOTP client request forwarding,
enable virtual private network (VPN) encryption for a client request to pass through a
VPN tunnel.
Related • DHCP Server, Client, and Relay Agent Overview on page 423
Documentation
watchdog
Syntax watchdog {
disable;
enable;
timeout value;
}
Description Enable or disable the watchdog timer when Junos OS encounters a problem.
web-management
Syntax web-management {
disable;
failover (alternate-media | other-routing-engine);
}
• failover—Configure the device to reboot if the software process fails four times within
30 seconds, and specify the software to use during the reboot.
Syntax web-management {
http {
interfaces interface-names ;
port port;
}
https {
interfaces interface-names;
local-certificate name;
pki-local-certificate name;
system-generated-certificate name;
port port;
}
management url management url;
session {
idle-timout minutes;
session-limit number;
}
traceoptions {
file {
filename;
files number;
match regular-expression;
size maximum-file-size;
(no-world-readable | world-readable);
}
flag flag;
level level;
no-remote-trace;
}
}
Description Configure settings for HTTP or HTTPS access. HTTP access allows management of the
device using the J-Web interface. HTTPS access allows secure management of the device
using the J-Web interface. With HTTPS access, communication is encrypted between
your browser and the webserver for your device.
The Web management HTTP and HTTPS interfaces are changed to fxp0.0
and from ge-0/0/1.0 through ge-0/0/7.0.
Range: 0 through 16
http—Configure HTTP.
https—Configure HTTPS.
• filename—Name of the file to receive the output of the tracing operation. Enclose
the name in quotation marks. All files are placed in the directory /var/log. By
default, the name of the file is the name of the process being traced.
• files number— Maximum number of trace files. When a trace file named trace-file
reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and so on,
until the maximum number of trace files is reached. Then the oldest trace file
is overwritten.
If you specify a maximum number of files, you also must specify a maximum
file size with the size maximum file-size option.
Default: 10 files
• match regular-expression—Refine the output to include lines that contain the regular
expression.
Range: 10 KB through 1 GB
Default: 128 KB
If you specify a maximum file size, you also must specify a maximum number of
trace files with the files number option.
• flag flag—Specify which tracing operation to perform. To specify more than one
tracing operation, include multiple flag statements. You can include the following
flags.
• configuration—Trace configuration.
Operational Commands
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Clear the binding state of a Dynamic Host Configuration Protocol (DHCP) client from
the DHCP client table.
Options all—(Optional) Clear the binding state for all DHCP clients.
interface <interface-name>—(Optional) Clear the binding state for DHCP clients on the
specified interface.
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Clear all Dynamic Host Configuration Protocol (DHCP) client statistics.
interface—(Optional) Clear the statistics for DHCP clients on the specified interface.
routing-instance —(Optional) Clear the statistics for DHCP clients on the specified routing
instance. If you do not specify a routing instance, statistics are cleared for the default
routing instance.
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Clear the binding state of a Dynamic Host Configuration Protocol (DHCP) client from
the client table.
Options all—(Optional) Clear the binding state for all DHCP clients.
ip-address— (Optional) Clear the binding state for the DHCP client, using the specified
IP address.
mac-address—(Optional) Clear the binding state for the DHCP client, using the specified
MAC address.
interface interface-name—(Optional) Clear the binding state for DHCP clients on the
specified interface
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Clear all Dynamic Host Configuration Protocol (DHCP) relay statistics.
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Clear the binding state of a Dynamic Host Configuration Protocol (DHCP) client from
the client table on the DHCP local server.
Options all—(Optional) Clear the binding state for all DHCP clients.
ip-address— (Optional) Clear the binding state for the DHCP client, using the specified
IP address.
mac-address—(Optional) Clear the binding state for the DHCP client, using the specified
MAC address.
interface interface-name—(Optional) Clear the binding state for DHCP clients on the
specified interface.
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Clear all Dynamic Host Configuration Protocol (DHCP) local server statistics.
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Clear the binding state of a Dynamic Host Configuration Protocol (DHCPv6) client from
the DHCPv6 client table.
Options all—(Optional) Clear the binding state for all DHCPv6 clients.
interface interface-name—(Optional) Clear the binding state for DHCPv6 clients on the
specified interface.
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Clear the binding state of a DHCPv6 client from the client table on the DHCPv6 local
server.
Options • all—(Optional) Clear the binding state for all DHCPv6 clients.
• client-id—(Optional) Clear the binding state for the DHCPv6 client with the specified
client ID (option 1).
• ip-address—(Optional) Clear the binding state for the DHCPv6 client with the specified
address.
• session-id—(Optional) Clear the binding state for the DHCPv6 client with the specified
session ID.
Description Clear private and public SSH key pair for the specified files.
List of Sample Output clear security ssh key-pair-identity sample on page 668
Output Fields
Sample Output
Description Unlock the user account locked as a result of invalid login attempts.
file archive
Description Archive, and optionally compress, one or multiple local system files as a single file, locally
or at a remote location.
Options destination destination—Name of the created archive. Specify the destination as a URL
or filename.
compress—(Optional) Compress the archived file with the GNU zip (gzip) compression
utility. The compressed files have the suffix .tgz.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
The following sample command archives all message files in the local directory
/var/log/messages as the single file messages-archive.tar.
The following sample command archives one message file in the local directory
/var/log/messages as the single file messages-archive.tar.
The following sample command archives and compresses all message files in the local
directory /var/log/messages as the single file messages-archive.tar.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Description Calculate the Secure Hash Algorithm 2 family (SHA-256) checksum of a file.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
SHA256 (/var/db/scripts/commitscript.slax) =
94c2b061fb55399e15babd2529453815601a602b5c98e5c12ed929c9d343dd71
file compare
Description Compare two local files and describe the differences between them in default, context,
or unified output styles:
• default—In the first line of output, c means lines were changed between the two files,
d means lines were deleted between the two files, and a means lines were added
between the two files. The numbers preceding this alphabetical marker represent the
first file, and the lines after the alphabetical marker represent the second file. A left
angle bracket (<) in front of output lines refers to the first file. A right angle bracket (>)
in front of output lines refers to the second file.
• context—The display is divided into two parts. The first part is the first file; the second
part is the second file. Output lines preceded by an exclamation point (!) have changed.
Additions are marked with a plus sign (+), and deletions are marked with a
minus sign (-).
• unified—The display is preceded by the line number from the first and the second file
(xx,xxx,x). Before the line number, additions to the file are marked with a plus sign (+),
and deletions to the file are marked with a minus sign (-). The body of the output
contains the affected lines. Changes are viewed as additions plus deletions.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
file copy
Description Copy files from one location to another location on the local device or to a location on a
remote device that is reachable by the local device.
You can use the set system services xnm-ssl sslv3-support command to enable
SSLv3 for a Junos XML protocol client application to use as the protocol to
connect to the Junos XML protocol server on a device, and you can use the
file copy source destination sslv3-support command to enable the copying of
files from an SSLv3 URL.
List of Sample Output Copy a File from the Local Device to a Personal Computer on page 678
Copy a Configuration File Between Routing Engines on page 679
Copy a Log File Between Routing Engines on page 679
Copy a File Using FTP on page 679
Copy a File Using FTP and Requiring a Password on page 679
Copy a File Using Secure Copy on page 679
Sample Output
The following are examples of a variety of file copy scenarios.
The following sample command copies a configuration file from Routing Engine 0 to
Routing Engine 1:
The following sample command copies a log file from Routing Engine 0 to Routing Engine
1:
To use FTP where you require more privacy and are prompted for a password:
file delete
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
file delete
user@host> file list /var/tmp
dcd.core
rpd.core
snmpd.core
file list
Additional Information The default directory is the home directory of the user logged in to the device. To view
available directories, enter a space and then a slash (/) after the file list command. To
view files within a specific directory, include a slash followed by the directory and,
optionally, subdirectory name after the file list command.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
file list
user@host> file list /var/tmp
dcd.core
rpd.core
snmpd.core
file rename
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
file rename
The following example lists the files in /var/tmp, renames one of the files, and then
displays the list of files again to reveal the newly named file.
file show
encoding (base64 | raw)—(Optional) Encode file contents with base64 encoding or show
raw text.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
file show
user@host> file show /var/log/messages
Apr 13 21:00:08 romney /kernel: so-1/1/2: loopback suspected; going to standby.
Apr 13 21:00:40 romney /kernel: so-1/1/2: loopback suspected; going to standby.
Apr 13 21:02:48 romney last message repeated 4 times
Apr 13 21:07:04 romney last message repeated 8 times
Apr 13 21:07:13 romney /kernel: so-1/1/0: Clearing SONET alarm(s) RDI-P
Apr 13 21:07:29 romney /kernel: so-1/1/0: Asserting SONET alarm(s) RDI-P
...
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Initiates a renew request for the specified clients if they are in the bound state.
Options all—Initiate renew requests for all DHCP clients. If you specify a routing instance, renew
requests are initiated for all DHCP clients within that routing instance.
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Initiate a renew request for the specified DHCPv6 clients if they are in the bound state.
Options all—Initiate renew requests for all DHCPv6 clients. If you specify a routing instance, renew
requests are initiated for all DHCPv6 clients within that routing instance.
Description Generate the SSH private and public key pair for a specified identity. The private and
public key files are stored in the /var/db directory, which is accessible through root only.
Filenames are based on the identity-name with extensions. The files are similar to the
certificate files that are stored in Junos OS.
Options • passphrase— An SSH identity generated with a passphrase. The passphrase is used
to protect the private key file stored in the file system. This option does not allow the
user to enter a weak passphrase, which ensures stronger security. A Private key is used
to connect to a remote server and is never displayed or transferred between servers,
even if the system is compromised. The private key can be used to connect to a remote
server if the passphrase is not known.
• identity-name—Identity name.
List of Sample Output request security ssh key-pair-identity generate on page 686
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Description Use this command to set or replace the password (in plain text).
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Release Information Command introduced in Junos OS Release 11.2 for SRX300, SRX320, SRX345, and
SRX550M devices.
Description Prepare the system for autorecovery of configuration, licenses, and disk information.
Options save—Save the current state of the disk partitioning, configuration, and licenses for
autorecovery.
The active Junos OS configuration is saved as the Junos rescue configuration, after
which the rescue configuration, licenses, and disk partitioning information is saved
for autorecovery. Autorecovery information must be initially saved using this
command for the autorecovery feature to verify integrity of data on every bootup.
NOTE:
• Any recovery performed at a later stage will restore the data to the
same state as it was when the save command was executed.
List of Sample Output request system autorecovery state save on page 689
request system autorecovery state recover on page 689
request system autorecovery state clear on page 689
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Sample Output
Configuration:
File Recovery Information Integrity Check Action / Status
rescue.conf.gz Saved Passed None
Licenses:
File Recovery Information Integrity Check Action / Status
JUNOS282736.lic Saved Passed None
JUNOS282737.lic Saved Failed Recovered
BSD Labels:
Slice Recovery Information Integrity Check Action / Status
s1 Saved Passed None
s2 Saved Passed None
s3 Saved Passed None
s4 Saved Passed None
Sample Output
Description Use to display plain text versions of obfuscated ($9) or encrypted ($8) passwords. If
the password was encrypted using the new $8$ method, you are prompted for the master
password.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
// Decrypting a $9 password
user@host> request system decrypt password $9$ABC123
Plaintext password: mysecret
Sample Output
// Decrypting a $8 password
user@host> request system decrypt password $8$ABC123
Master password:
Plaintext password: mysecret
(Simple passwords like "mysecret" are discouraged. This is an example only.)
Release Information Command introduced in Junos OS Release 11.2 for SRX300, SRX320, SRX340, SRX345,
and SRX550M devices.
Command introduced in Junos OS Release 13.2X50-D15 for EX Series switches.
Description Abort a download. The download instance is stopped and cannot be resumed. Any
partially downloaded file is automatically deleted to free disk space. Information regarding
the download is retained and can be displayed with the show system download command
until a request system download clear operation is performed.
NOTE: Only downloads in the active, paused, and error states can be aborted.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Release Information Command introduced in Junos OS Release 11.2 for SRX300, SRX320, SRX340, SRX345,
and SRX550M devices.
Command introduced in Junos OS Release 13.2X50-D15 for EX Series switches.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Release Information Command introduced in Junos OS Release 11.2 for SRX300, SRX320, SRX340, SRX345,
and SRX550M devices.
Command introduced in Junos OS Release 13.2X50-D15 for EX Series switches.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Release Information Command introduced in Junos OS Release 11.2 for SRX300, SRX320, SRX340, SRX345,
and SRX550M devices.
Command introduced in Junos OS Release 13.2X50-D15 for EX Series switches.
Description Resume a download that has been paused. Download instances that are not in progress
because of an error or that have been explicitly paused by the user can be resumed by
the user. The file will continue downloading from the point where it paused. By default,
the download resumes with the same bandwidth specified with the request system
download start command. The user can optionally specify a new (maximum) bandwidth
with the request system download resume command.
NOTE: Only downloads in the paused and error states can be resumed.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Syntax request system download start (sftp-url | delay | identity-file | login | max-rate | passphrase
| save as )
Release Information Command introduced in Junos OS Release 11.2 for SRX300, SRX320, SRX340, SRX345,
and SRX550M devices.
Command introduced in Junos OS Release 13.2X50-D15 for EX Series switches.
Description Create a download instance and identify it with a unique integer called the download ID.
Options sftp-url—(Required) The FTP or HTTP URL location of the file to be downloaded securely.
delay—(Optional) The number of hours after which the download should start (range
from 1 through 48 hours).
identity-file—(Required) The name of the file requesting a Secure FTP (SFTP) download.
The SFTP in smart download leverages public key authentication to authenticate a
download request. Users need to generate a private or public key pair before starting a
download, and then upload a public key to an SFTP server.
login—(Optional) The username and password for the server in the format
username:password.
passphrase—(Required) The passphrase to protect the private key file stored on the file
system. This option does not allow the user to enter a weak passphrase, which ensures
stronger security.
save-as—(Optional) The filename to be used for saving the file in the /var/tmp location.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
re—Upgrade baseboard BIOS/FPGA. There is an active BIOS image and a backup BIOS
image.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Options trial—Starts autoupdating trial license keys from the LMS server.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Trying to update license keys from https://ae1.juniper.net has been sent, use
show system license to check status.
Description Bring Flexible PIC Concentrators (FPCs) offline before Routing Engines are shut down.
List of Sample Output request system halt power-off fpc on page 699
request system power-off power-off fpc on page 699
request system reboot power-off fpc on page 699
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
To view the status of the Dynamic Host Configuration Protocol (DHCP) clients on the
specified interfaces, enter the show system services dhcp client interface-name command.
Options • release interface-name —Clears other resources received earlier from the server, and
reinitializes the client state to INIT for the particular interface.
• renew interface-name —Reacquires an IP address from the server for the interface.
When you use this option, the command sends a discover message if the client state
is INIT and a renew request message if the client state is BOUND. For all other states
it performs no action.
Related • dhcp
Documentation
• show system services dhcp client on page 758
Description Back up the currently running and active file system partitions on the device.
Options • factory— (Optional) Specifies that only the files shipped from the factory are included
in the snapshot.
NOTE: USB option is available on all SRX series devices; hard disk and
compact-flash options are available only on SRX5800, SRX5600, and
SRX5400 devices; media internal option is available only on SRX300,
SRX320, SRX340, SRX345, and SRX550M devices.
• external— Copies the snapshot to an external storage device. This option is available
for the compact flash on the SRX650 Services Gateway.
• node—(Optional) Specify the archive data and executable areas of a specific node.
• partition—(Default) Specify that the target media should be repartitioned before the
backup is saved to it.
• slice—(Optional) Take a snapshot of the root partition the system has currently booted
from to another slice in the same media.
• alternate—(Optional) Store the snapshot on the other root partition in the system.
NOTE: The slice option cannot be used along with the other request system
snapshot options, because the options are mutually exclusive. If you use
the factory, media, or partition option, you cannot use the slice option; if
you use the slice option, you cannot use any of the other options.
List of Sample Output request system snapshot media hard-disk on page 702
request system snapshot media usb (when usb device is missing on page 702
request system snapshot media compact-flash on page 703
request system snapshot partition on page 703
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Release Information Command introduced in Junos OS Release 11.2 for SRX300, SRX320, SRX340, SRX345,
and SRX550M devices.
Description Abort an in-band cluster upgrade (ICU). This command must be issued from a router
session other than the one on which you issued the request system in-service-upgrade
command that launched the ICU. If an ICU is in progress, this command aborts it. If the
node is being upgraded, this command will cancel the upgrade. The command is also
helpful in recovering the node in case of a failed ICU.
List of Sample Output request system software abort in-service-upgrade on page 704
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Release Information Partition option introduced in the command in Junos OS Release 10.1.
Description Install the new software package on the device, for example: request system software
add junos-srxsme-10.0R2-domestic.tgz no-copy no-validate partition reboot.
Options • delay–restart—Install the software package but does not restart the software process.
• no-copy—Install the software package but does not saves the copies of package files.
Options • at time (Optional)— Specify the time at which to reboot the device. You can specify
time in one of the following ways:
• +minutes— Reboot the device in the number of minutes from now that you specify.
• yymmddhhmm— Reboot the device at the absolute time on the date you specify.
Enter the year, month, day, hour (in 24-hour format), and minute.
• hh:mm— Reboot the device at the absolute time you specify, on the current day.
Enter the time in 24-hour format, using a colon (:) to separate hours from minutes.
• in minutes(Optional)— Specify the number of minutes from now to reboot the device.
This option is a synonym for the at +minutes option
• media type(Optional)— Specify the boot device to boot the device from:
• message “text” (Optional)— Provide a message to display to all system users before
the device reboots.
Description Revert to the software that was loaded at the last successful request system software
add command. .
Description Erases all configuration information and resets all key values. The command removes
all data files, including customized configuration and log files, by unlinking the files from
their directories.
The command removes all user-created files from the system including all plain-text
passwords, secrets, and private keys for SSH, local encryption, local authentication,
IPsec, RADIUS, TACACS+, and SNMP.
This command reboots the device and sets it to the factory default configuration. After
the reboot, you cannot access the device through the management Ethernet interface.
Log in through the console as root and start the Junos OS CLI by typing cli at the prompt.
Options media—(Optional) In addition to removing all configuration and log files, the media option
causes memory and the media to be scrubbed, removing all traces of any user-created
files. Every storage device attached to the system is scrubbed, including disks, flash
drives, removable USBs, and the like. The duration of the scrubbing process is
dependent on the size of the media being erased. As a result, the request system
zeroize media operation can take considerably more time than the request system
zeroize operation. However, the critical security parameters are all removed at the
beginning of the process.
Sample Output
restart (Reset)
Syntax restart
<application-identification |application-security |audit-process |commitd-service
|chassis-control | class-of-service |database-replication |datapath-trace-service |ddns
|dhcp |dhcp-service |dynamic-flow-capture |disk-monitoring |event-processing |
ethernet-connectivity-fault-management |ethernet-link-fault-management
|extensible-subscriber-services |fipsd |firewall |firewall-authentication-service
|general-authentication-service |gracefully |gprs-process |idp-policy |immediately
|interface-control | ipmi |ipsec-key-management |jflow-service |jnu-management
|jnx-wmicd-service |jsrp-service |kernel-replication |l2-learning |l2cpd-service |lacp
|license-service |logical-system-service |mib-process |mountd-service |named-service
|network-security |network-security-trace |nfsd-service |ntpd-service |pgm
|pic-services-logging |profilerd |pki-service |remote-operations |rest-api |routing |sampling
|sampling-route-record |scc-chassisd |secure-neighbor-discovery |security-intelligence
|security-log |services |service-deployment |simple-mail-client-service |soft |snmp
|static-routed |statistics-service |subscriber-management |subscriber-management-helper
|system-log-vital |tunnel-oamd |uac-service |user-ad-authentication |vrrp
|web-management >
• lacp—(Optional) Restart the Link Aggregation Control Protocol (LACP) process. LACP
provides a standardized means for exchanging information between partner systems
on a link. The LACP process allows link aggregation control instances to reach
agreement on the identity of the LAG to which a link belongs, moves the link to that
LAG, and enables the transmission and reception processes for the link to function in
an orderly manner.
• l2-learning—(Optional) Restart the Layer 2 (L2) address flooding and learning process.
• mib-process—(Optional) Restart the MIB version II process, which provides the router's
MIB II agent.
• mountd-service—(Optional) Restart the service for Network File System (NFS) mount
requests.
• nfsd-service—(Optional) Restart the remote NFS server process, which provides remote
file access for applications that need NFS-based transport.
• pgm—(Optional) Restart the process that implements the Pragmatic General Multicast
(PGM) protocol for assisting in the reliable delivery of multicast packets.
• pic-services-logging—(Optional) Restart the logging process for some PICs. With this
process, also known as fsad (the file system access daemon), PICs send special logging
information to the Routing Engine for archiving on the hard disk.
• snmp—(Optional) Restart the SNMP process, which enables the monitoring of network
devices from a central location and provides the router's or switch’s SNMP master
agent.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
restart interfaces
user@host> restart interfaces
interfaces process terminated
interfaces process restarted
Use the restart operational commands to restart software processes on the device.
Operational commands are organized alphabetically.
Related • restart
Documentation
List of Sample Output show chassis routing-engine (Sample 1 - SRX550M) on page 716
show chassis routing-engine (Sample 2 - vSRX) on page 716
Output Fields Table 17 on page 715 lists the output fields for the show chassis routing-engine command.
Output fields are listed in the approximate order in which they appear.
NOTE: Starting with Junos OS Release 15.1x49-D70, there is a change in the method for
calculating the memory utilization by a Routing Engine. The inactive memory is now
subtracted from the total available memory. There is thus, a decrease in the reported
value for used memory; as the inactive memory is now considered as free.
CPU utilization Current CPU utilization statistics on the control plane core.
User Current CPU utilization in user mode on the control plane core.
Background Current CPU utilization in nice mode on the control plane core.
Kernel Current CPU utilization in kernel mode on the control plane core.
Interrupt Current CPU utilization in interrupt mode on the control plane core.
Idle Current CPU utilization in idle mode on the control plane core.
Uptime Length of time the Routing Engine has been up (running) since the last start.
Last reboot reason Reason for the last reboot of the Routing Engine.
Load averages The average number of threads waiting in the run queue or currently executing over 1-,
5-, and 15-minute periods.
Sample Output
Sample Output
Interrupt 6 percent
Idle 88 percent
Model VSRX RE
Start time 2015-03-03 07:04:18 UTC
Uptime 2 days, 11 hours, 51 minutes, 11 seconds
Last reboot reason Router rebooted after a normal shutdown.
Load averages: 1 minute 5 minute 15 minute
0.07 0.04 0.06
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series, vSRX
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Display the address bindings in the Dynamic Host Configuration Protocol (DHCP) client
table.
Options address—(Optional) Display DHCP binding information for a specific client identified by
one of the following entries:
• ip-address—The specified IP address.
Output Fields Table 18 on page 720 lists the output fields for the show dhcp client binding command.
Output fields are listed in the approximate order in which they appear.
State State of the address binding table on the DHCP local server.
Lease Expires Date and time at which the client’s IP address lease expires.
Lease Start Date and time at which the client’s IP address lease started.
Sample Output
DHCP Options :
Name: name-server, Value: [ 10.209.194.131, 198.51.110.2, 192.0.2.3
]
Name: server-identifier, Value: 10.1.1.1
Name: router, Value: [ 10.1.1.80 ]
Name: domain-name, Value: example-50
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Output Fields Table 19 on page 723 lists the output fields for the show dhcp client statistics command.
Output fields are listed in the approximate order in which they appear.
Packets dropped Number of packets discarded by the DHCP local server because
of errors. Only nonzero statistics appear in the Packets dropped
output. When all of the Packets dropped statistics are 0 (zero),
only the Total field appears.
Sample Output
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Display the address bindings in the Dynamic Host Configuration Protocol (DHCP) relay
client table.
Options address—(Optional) Display DHCP binding information for a specific client identified by
one of the following entries:
• ip-address—The specified IP address.
Output Fields Table 20 on page 725 lists the output fields for the show dhcp relay binding command.
Output fields are listed in the approximate order in which they appear.
Obtained at Date and time at which the client’s IP address lease started.
Expires at Date and time at which the client’s IP address lease expires.
State State of the address binding table on the DHCP local server.
Sample Output
Lease information:
Type DHCP
Obtained at 2007-01-17 11:28:47 PST
Expires at 2007-01-17 11:38:47 PST
Lease information:
Type DHCP
Obtained at 2007-01-17 11:28:47 PST
Expires at 2007-01-17 11:38:47 PST
State rebind
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Options routing-instance—(Optional) Display the DHCP relay statistics on the specified routing
instance.
Output Fields Table 21 on page 728 lists the output fields for the show dhcp relay statistics command.
Output fields are listed in the approximate order in which they appear.
Sample Output
Messages sent:
BOOTREPLY 0
DHCPOFFER 0
DHCPACK 0
DHCPNAK 0
DHCPFORCERENEW 0
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Display the address bindings in the client table on the Dynamic Host Configuration
Protocol (DHCP) local server.
Options interface <interface name>—(Optional) Display information about active client bindings
on the specified interface.
brief | detail | summary—(Optional) Display the specified level of output about active
client bindings. The default is brief, which produces the same output as show dhcp
server binding.
MAC address—Display DHCP binding information for a specific client identified by the
specified MAC address.
Output Fields Table 22 on page 730 lists the output fields for the show dhcp server binding command.
Output fields are listed in the approximate order in which they appear.
Obtained at Date and time at which the client’s IP address lease started.
Expires at Date and time at which the client’s IP address lease expires.
State State of the address binding table on the DHCP local server.
Sample Output
Lease information:
Type DHCP
Obtained at 2007-01-17 11:28:47 PST
Expires at 2007-01-17 11:38:47 PST
State rebind
Release Information Statement introduced in Junos OS Release 12.1X44-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Display Dynamic Host Configuration Protocol (DHCP) local server statistics.
Output Fields Table 23 on page 732 lists the output fields for the show dhcp server statistics command.
Output fields are listed in the approximate order in which they appear.
Packets dropped Number of packets discarded by the DHCP local server because of errors. Only nonzero statistics
appear in the Packets dropped output. When all of the Packets dropped statistics are 0 (zero), only
the Total field appears.
Sample Output
Messages received:
BOOTREQUEST 0
DHCPDECLINE 0
DHCPDISCOVER 0
DHCPINFORM 0
DHCPRELEASE 0
DHCPREQUEST 0
Messages sent:
BOOTREPLY 0
DHCPOFFER 0
DHCPACK 0
DHCPNAK 0
DHCPFORCERENEW 0
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Description Display the address bindings in the Dynamic Host Configuration Protocol version 6
(DHCPv6) client table.
Output Fields Table 24 on page 734 lists the output fields for the show dhcpv6 client binding command.
Output fields are listed in the approximate order in which they appear.
Lease Expires Date and time at which the client’s IP address lease expires.
Lease Start Date and time at which the client’s IP address lease started.
Client Type The type of DHCPv6 client. The client type can be autoconfig or stateful.
Sample Output
DHCP options:
Name: server-identifier, Value: LL_TIME0x1-0x17acddab-00:30:48:5d:5b:f7
Name: vendor-opts, Value: 000005830002aaaa
Name: sip-server-list, Value: 2000::300 2000::302 2000::303 2000::304
Name: dns-recursive-server, Value: 2000::ff2000::fe
Name: domain-search-list, Value: 076578616d706c6503636f6d00
Release Information Statement introduced in Junos OS Release 12.1X45-D10 for SRX300, SRX320, SRX340,
SRX345, SRX550M, and SRX1500 devices.
Output Fields Table 25 on page 736 lists the output fields for the show dhcpv6 client statistics command.
Output fields are listed in the approximate order in which they appear.
Dhcpv6 Packets dropped Number of packets discarded by the DHCPv6 local server
because of errors. Only nonzero statistics appear in the DHCPv6
Packets dropped output. When all of the Packets dropped
statistics are 0 (zero), only the Total field appears.
Sample Output
Messages sent:
DHCPV6_DECLINE 0
DHCPV6_SOLICIT 3
DHCPV6_INFORMATION_REQUEST 6
DHCPV6_RELEASE 1
DHCPV6_REQUEST 2
DHCPV6_CONFIRM 0
DHCPV6_RENEW 0
DHCPV6_REBIND 0
Messages received:
DHCPV6_ADVERTISE 3
DHCPV6_REPLY 3
DHCPV6_RECONFIGURE 0
Description Display the address bindings in the client table for DCHPv6 local server.
Options • brief | detail | summary—(Optional) Display the specified level of output about active
client bindings. The default is brief, which produces the same output as show dhcpv6
server binding.
Output Fields Table 26 on page 739 lists the output fields for the show dhcpv6 server binding command.
Output fields are listed in the approximate order in which they appear.
number clients, Summary counts of the total number of DHCPv6 clients and the number of summary
(number init, DHCPv6 clients in each state.
number bound,
number selecting,
number requesting,
number renewing,
number releasing)
State State of the address binding table on the DHCPv6 local server: brief
detail
• BOUND—Client has active IP address lease.
• INIT—Initial state.
• RELEASE—Client is releasing IP address lease.
• RECONFIGURE—Client has received reconfigure message from server.
• RENEWING—Client sending request to renew IP address lease.
• REQUESTING—Client requesting a DHCPv6 server.
• SELECTING—Client receiving offers from DHCPv6 servers.
Lease expires Date and time at which the client’s IP address lease expires. detail
Lease Start Date and time at which the client’s address lease was obtained. detail
Sample Output
State: BOUND(bound)
Lease Expires: 2009-07-21 10:41:15 PDT
Lease Expires in: 86308 seconds
Lease Start: 2009-07-20 10:41:15 PDT
Incoming Client Interface: ge-1/0/0.0
Server Ip Address: 0.0.0.0
Server Interface: none
Client Id Length: 14
Client Id:
/0x00010001/0x02e159c0/0x00109400/0x0001 Server Id:
<VENDOR 2198142976/4a4e313132414343374146430000000000000000>
Session Id: 7
Client IPv6 Prefix: 2001:bd8:1111:2222::/64
Client DUID: LL_TIME0x1-0x2e159c0-00:10:94:00:00:02
State: BOUND(bound)
Lease Expires: 2009-07-21 10:41:15 PDT
Lease Expires in: 86308 seconds
Lease Start: 2009-07-20 10:41:15 PDT
Incoming Client Interface: ge-1/0/0.0
Server Ip Address: 0.0.0.0
Server Interface: none
Client Id Length: 14
Client Id:
State: BOUND(bound)
Lease Expires: 2009-07-21 10:41:15 PDT
Lease Expires in: 86136 seconds
Lease Start: 2009-07-20 10:41:15 PDT
Incoming Client Interface: ge-1/0/0.0
Server Ip Address: 0.0.0.0
Server Interface: none
Client Id Length: 14
Client Id:
/0x00010001/0x02e159c0/0x00109400/0x0002 Server Id:
<VENDOR 2198142976/4a4e313132414343374146430000000000000000>
State: BOUND(bound)
Lease Expires: 2009-07-21 10:41:15 PDT
Lease Expires in: 86136 seconds
Lease Start: 2009-07-20 10:41:15 PDT
Incoming Client Interface: ge-1/0/0.0
Server Ip Address: 0.0.0.0
Server Interface: none
Client Id Length: 14
Client Id:
/0x00010001/0x02e159c0/0x00109400/0x0002
Output Fields Table 27 on page 744 lists the output fields for the show dhcpv6 server statistics command.
Output fields are listed in the approximate order in which they appear.
Dhcpv6 Packets Number of packets discarded by the DHCPv6 local server because of errors. Only nonzero statistics
dropped appear in the Packets dropped output. When all of the Packets dropped statistics are 0 (zero), only
the Total field appears.
Sample Output
Messages received:
DHCPV6_DECLINE 0
DHCPV6_SOLICIT 9
DHCPV6_INFORMATION_REQUEST 0
DHCPV6_RELEASE 0
DHCPV6_REQUEST 5
DHCPV6_CONFIRM 0
DHCPV6_RENEW 0
DHCPV6_REBIND 0
DHCPV6_RELAY_FORW 0
Messages sent:
DHCPV6_ADVERTISE 9
DHCPV6_REPLY 5
DHCPV6_RECONFIGURE 0
DHCPV6_RELAY_REPL 0
Output Fields Table 28 on page 746 lists the output fields for the show firewall command. Output fields
are listed in the approximate order in which they appear.
Filter Name of a filter that has been configured with the filter at the [edit firewall] hierarchy level.
When an interface-specific filter is displayed, the name of the filter is followed by the full interface
name and by either -i for an input filter or -o for an output filter.
When dynamic filters are displayed, the name of the filter is followed by the full interface name and
by either -in for an input filter or -out for an output filter. When a logical system–specific filter is
displayed, the name of the filter is prefixed with two underscore (__) characters and the name of the
logical system (for example, __ls1/filter1).
• Name—Name of a filter counter that has been configured with the counter firewall filter action.
• Bytes—Number of bytes that match the filter term under which the counter action is specified.
• Packets—Number of packets that matched the filter term under which the counter action is specified.
• Name—Name of policer.
• Bytes—Number of bytes that match the filter term under which the policer action is specified. This
is only the number out-of-specification (out-of-spec) byte counts, not all the bytes in all packets
policed by the policer.
• Packets—Number of packets that matched the filter term under which the policer action is specified.
This is only the number of out-of-specification (out-of-spec) packet counts, not all packets policed
by the policer.
Sample Output
show firewall
user@host> show firewall
Filter: ef_path
Counters:
Name Bytes Packets
def-count 0 0
video-count 0 0
voice-count 0 0
Filter: __default_bpdu_filter__
Filter: deep
Counters:
Name Bytes Packets
deep2 302076 5031
Filter: deep-flood
Counters:
Name Bytes Packets
deep_flood_def 302136 5032
deep1 0 0
Policers:
Name Packets
deep-pol-op-first 0
Options • brief identity-name—Display the brief information for a specified identity. If an identity
is not specified, the command will list brief information of all identities.
List of Sample Output show security ssh key-pair-identity brief on page 748
show security ssh key-pair-identity brief sample on page 748
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
Description Display the current status of the Trusted Platform Module (TPM) such as:
• TPM enabled/disabled
• TPM ownership
Related • Using Trusted Platform Module to Bind Secrets on SRX Series Devices on page 14
Documentation
• request security tpm master-encryption-password set on page 687
Sample Output
Release Information Command introduced in Junos OS Release 11.2 for SRX300, SRX320, SRX340, SRX345,
and SRX550M devices.
Output Fields Table 29 on page 750 lists the output fields for the show system autorecovery state
command. Output fields are listed in the approximate order in which they appear.
File The name of the file on which autorecovery checks are performed.
Recovery Information Indicates whether autorecovery information for the file or slice has been saved.
Integrity Check Displays the status of the file's integrity check (passed or failed).
Action / Status Displays the status of the item, or the action required to be taken for that item.
Sample Output
Configuration:
File Recovery Information Integrity Check Action / Status
rescue.conf.gz Saved Passed None
Licenses:
File Recovery Information Integrity Check Action / Status
JUNOS282736.lic Saved Passed None
JUNOS282737.lic Not Saved Not checked Requires save
BSD Labels:
Release Information Command introduced in Junos OS Release 11.2 for SRX300, SRX320, SRX340, SRX345,
and SRX550M devices.
Description Display a brief summary of all the download instances along with their current state and
extent of progress. If a download-id is provided, the command displays a detailed report
of the particular download instance.
Output Fields Table 30 on page 752 lists the output fields for the show system download command.
Output fields are listed in the approximate order in which they appear.
URL Displays the URL from which the file was downloaded.
Sample Output
Download ID : 1
Status : Active
Progress : 6%
URL : ftp://ftp-server//tftpboot/1m_file
Local Path : /var/tmp/1m_file
Maximum Rate : 1k
Creation Time : May 4 06:28:36
Scheduled Time : May 4 06:28:36
Start Time : May 4 06:28:37
Error Count : 0
Release Information Command introduced in Junos OS Release 9.5. Logical system status option added in
Junos OS Release 11.2.
Description Display licenses and information about how licenses are used.
keys—(Optional) Display a list of license keys. Use this information to verify that each
expected license key is present.
status—(Optional) Display license status for a specified logical system or for all logical
systems.
Output Fields Table 31 on page 754 lists the output fields for the show system license command. Output
fields are listed in the approximate order in which they appear.
Feature name Name assigned to the configured feature. You use this information to verify that all the features for
which you installed licenses are present.
Licenses used Number of licenses used by the device. You use this information to verify that the number of licenses
used matches the number configured. If a licensed feature is configured, the feature is considered
used.
Licenses needed Number of licenses required for features being used but not yet properly licensed.
Expiry Time remaining in the grace period before a license is required for a feature being used.
Logical system license Displays whether a license is enabled for a logical system.
status
Sample Output
License usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
av_key_kaspersky_engine 1 1 0 2012-03-30
01:00:00 IST
wf_key_surfcontrol_cpa 0 1 0 2012-03-30
01:00:00 IST
dynamic-vpn 0 1 0 permanent
ax411-wlan-ap 0 2 0 permanent
Licenses installed:
License identifier: JUNOS301998
License version: 2
Valid for device: AG4909AA0080
Features:
av_key_kaspersky_engine - Kaspersky AV
date-based, 2011-03-30 01:00:00 IST - 2012-03-30 01:00:00 IST
Features:
av_key_kaspersky_engine - Kaspersky AV
date-based, 2011-03-30 01:00:00 IST - 2012-03-30 01:00:00 IST
Supported Platforms EX Series, M Series, MX Series, PTX Series, SRX Series, T Series
Output Fields Table 32 on page 757 lists the output fields for the show system login lockout command.
Output fields are listed in the approximate order in which they appear.
Lockout start Date and time the username was locked All levels
Lockout end Date and time the username was unlocked All levels
Sample Output
List of Sample Output show system services dhcp client on page 759
show system services dhcp client ge-0/0/34.0 on page 760
show system services dhcp client statistics on page 760
Output Fields Table 33 on page 758 lists the output fields for the show system services dhcp client
command. Output fields are listed in the approximate order in which they appear.
Table 33: show system services dhcp client Output Fields (continued)
Field Name Field Description
Lease Expires in (EX Series switches only) Time the current lease expires in (seconds).
Sample Output
DHCP options:
Name: server-identifier, Value: 10.0.0.1
Code: 1, Type: ip-address, Value: 255.255.255.0
Sample Output
DHCP options:
Name: server-identifier, Value: 10.0.0.1
Code: 1, Type: ip-address, Value: 255.255.255.0
Sample Output
Related • dhcp
Documentation
List of Sample Output show system services dhcp relay-statistics on page 762
Output Fields Table 34 on page 761 lists the output fields for the show system services dhcp
relay-statistics command. Output fields are listed in the approximate order in which they
appear.
Dropped packets Total DHCP packets dropped for the following reasons:
Sample Output
Description Display the snapshot information for both root partitions on SRX Series devices
Related • Example: Creating a Snapshot and Using It to Boot an SRX Series Device
Documentation
List of Sample Output show system snapshot media internal on page 763
show system snapshot media usb on page 763
Sample Output
Description Display the partitioning scheme details on SRX300, SRX320, SRX340, SRX345, and
SRX550HM devices.
Related • Example: Installing Junos OS on SRX Series Devices Using the Partition Option
Documentation
List of Sample Output show system storage partitions (single root partitioning) on page 764
show system storage partitions (USB) on page 764
Partitions Information:
Partition Size Mountpoint
s1a 293M altroot
s2a 293M /
s3e 24M /config
s3f 342M /var
s4a 30M recovery
Partitions Information:
Partition Size Mountpoint
s1a 293M /
s2a 293M altroot
s3e 24M /config
s3f 342M /var
s4a 30M recovery