JUNIPER NETWORKS OS CLI User User Guide

JUNIPER NETWORKS OS CLI User

Nadview

This guide explains how to use the Junos OS command-line interface (CLI) to monitor device status and configure Junos OS devices. It covers CLI modes (operational and configuration), candidate versus active configuration behavior, and common CLI usage features such as online help and command completion.

Documented Specifications and Technical Notes

Quick Start: Accessing the CLI and Making Configuration Changes

1. Ensure your device hardware is set up and Junos OS is installed.
2. Use a direct console connection or network access using SSH or Telnet.
3. Zaloguj się jako root (root has superuser privileges).
4. Start the CLI from your login session.
5. Używać tryb operacyjny commands to display current device status (for monitoring and troubleshooting).
6. Używać tryb konfiguracji to change device settings by adding configuration statements to the candidate configuration (edits do not affect the active configuration until you commit).
7. When finished, commit the candidate configuration so it becomes the operational (active) configuration.

Loading PDF…

−+Fit width100%View FullscreenDownload PDFPrint PDF

×

Loading PDF…

Juniper Networks, Inc.
1133 sposób innowacji
Sunnyvale, Kalifornia 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, logo Juniper Networks, Juniper i Junos są zastrzeżonymi znakami towarowymi firmy Juniper Networks, Inc.
in the United States and other countries. All other trademarks, service marks, registered marks, or registered service
znaki są własnością ich odpowiednich właścicieli.
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 CLI User Guide for Junos OS
Copyright © 2026 Juniper Networks, Inc. Wszelkie prawa zastrzeżone.
Informacje zawarte w tym dokumencie są aktualne na dzień podany na stronie tytułowej.

ZAWIADOMIENIE Z ROKU 2000
Sprzęt i oprogramowanie Juniper Networks są zgodne z rokiem 2000. Junos OS nie ma znanych ograniczeń czasowych do roku 2038. Wiadomo jednak, że aplikacja NTP ma pewne trudności w roku 2036.

UMOWA LICENCYJNA UŻYTKOWNIKA KOŃCOWEGO
Produkt Juniper Networks będący przedmiotem niniejszej dokumentacji technicznej składa się (lub jest przeznaczony do użytku z) oprogramowaniem Juniper Networks. Korzystanie z takiego oprogramowania podlega warunkom Umowy Licencyjnej Użytkownika Końcowego („EULA”) opublikowanej pod adresem https://support.juniper.net/support/eula/. Pobierając, instalując lub używając takiego oprogramowania, wyrażasz zgodę na warunki tej umowy EULA.

O tym przewodniku

The Junos OS command-line interface (CLI) is a command shell specific to Juniper Networks. This
command shell runs on top of the FreeBSD UNIX-based operating system kernel for Junos OS. Using
industry-standard tools and utilities, the CLI provides a powerful set of commands that you can use to
monitor and configure Juniper Networks devices running Junos OS. This guide contains information
about the CLI for Junos OS.
Konwencje dokumentacyjne
For information about the notice icons and text and syntax conventions used in the documentation, see
Documentation Conventions.
POWIĄZANA DOKUMENTACJA
Day One: Exploring the Junos CLI
Day One: Junos for IOS Engineers

About the CLI Guide

The Junos OS CLI Guide explains how to use the command-line interface (CLI). This guide also describes
advanced concepts and device configuration when working with Juniper Networks devices running
Junos OS.
In this guide, you will learn about:
• Using configuration statements to configure network devices
• Managing device configurations
• Using operational commands to monitor devices
• Syntax for configuration statements, operational commands, and environmental commands
For a basic introduction to Junos OS, see the Getting Started Guide for Junos OS. It provides a high-level
description of Junos OS, describes how to access devices, and provides simple step-by-step instructions
for initial device configuration.
For a technical and detailed exploration of Junos OS, see the Overview for Junos OS. It further explains
how Junos OS works and describes the security, configuration, monitoring, and management of network
urządzenia.
Another useful learning resource is Day One: Exploring the Junos CLI.
CLI ponadview
W TEJ SEKCJI
Introducing the Command-Line Interface | 3
CLI Modes, Commands, and Statement Hierarchies—An Overview | 5
Other Tools to Configure and Monitor Juniper Networks Devices | 7
Configure Junos OS in a FIPS Environment | 7
2
The CLI is the software interface used to access your device. You use the CLI to configure the device,
monitor its operations, and adjust the configuration as needed. You access the CLI through a console
connection interface or through a network connection.
Introducing the Command-Line Interface
W TEJ SEKCJI
Key Features of the CLI | 3
The Junos OS CLI is a command shell specific to Juniper Networks that runs on top of the operating
system kernel. Through industry-standard tools and utilities, the CLI provides a powerful set of
commands that you can use to monitor and to configure devices running Junos OS.
The CLI has two modes:
• Operational mode—Use this mode to display the current status of the device. In operational mode,
you enter commands to monitor and to troubleshoot the network operating system, devices, and
łączność sieciowa.
• Configuration mode—Use this mode to configure the device. In this mode, you enter statements to
configure all properties of the device, including interfaces, general routing information, routing
protocols, user access, and several system and hardware properties. Junos OS stores a configuration
as a hierarchy of configuration statements.
When you enter configuration mode, you are viewing and changing a file called the candidate
configuration. You use the candidate configuration file, you make configuration changes without
causing operational changes to the current operating configuration, called the active configuration.
The device does not implement the changes you added to the candidate configuration file dopóki ty
commit the changes. Committing the configuration changes activates the revised configuration on
the device. Candidate configurations enable you to alter your configuration without damaging your
current network operations.
Key Features of the CLI
The CLI commands and statements follow a hierarchical organization and have a regular syntax. The CLI
provides the following features to simplify CLI use:
3
• Consistent command names—Commands that provide the same type of function have the same
name, regardless of the specific device type on which you are operating. For example, all show
commands display software information and statistics, and all clear commands erase various types of
informacje o systemie.
• Lists and short descriptions of available commands—The CLI provides information about available
commands t each level of the command hierarchy. If you type a question mark (?) at any level, you
see a list of the available commands along with a short description of each. This means that if you are
already familiar with Junos OS or with other routing software, you can use many of the CLI
commands without referring to the documentation.
• Command completion—Command completion for command names (keywords) and for command
options is available at each level of the hierarchy. To complete a command or option that you have
partially typed, press the Tab key or the Spacebar. If the partially typed letters begin a string that
uniquely identifies a command, the complete command name appears. Otherwise, a beep indicates
that you have entered an ambiguous command, and the CLI displays possible completions.
Completion also applies to other strings, such as filenames, interface names, usernames, and
configuration statements.
If you have typed the mandatory arguments for executing a command in operational mode or
configuration mode, the CLI displays <[Enter]> as one of the choices when you type a question mark
(?). This output indicates that you have entered the mandatory arguments and can execute the
command at that level without specifying any further options. Likewise, the CLI also displays <[Enter]>
when you reach a specific hierarchy level in the configuration mode and do not need to enter any
more mandatory arguments or statements.
• Industry-standard technology—With FreeBSD UNIX as the kernel, a variety of UNIX utilities are
available on the CLI. For example, możesz:
• Use regular expression matching to locate and to replace values and identifiers in a configuration,
to filter command output, and to examine log file wpisy.
• Use Emacs-based key sequences to move around on a command line and scroll through the
recently executed commands and command output.
• Store and archive Junos OS device files on a UNIX-based file system.
Use standard UNIX conventions to specify filenazwy i ścieżki.
Exit the CLI environment and create a UNIX C shell or Bourne shell to navigate the file system,
manage router processes, and so on.
4
CLI Modes, Commands, and Statement Hierarchies—An Overview
W TEJ SEKCJI
CLI Command Hierarchy | 5
Configuration Statement Hierarchy | 5
Move Among Hierarchy Levels | 6
The Junos OS CLI commands and statements are organized under two command modes and various
hierarchies. The following sections provide an overview of the CLI command modes and the command
and statement hierarchies.
CLI Command Hierarchy
CLI commands are organized in a hierarchy. Commands that perform a similar function are grouped
together under the same level of the hierarchy. For example, all commands that display information
about the system and the system software are under the show system command. All commands that
display information about the routing table are under the show route command.
To execute a command, enter the full command name, starting at the top level of the hierarchy. For
example, to display a brief view of the routes in the routing table, use the command show route brief.
Configuration Statement Hierarchy
The configuration statement hierarchy has two types of statements: Container statements, which are
statements that contain other statements, and leaf statements, which do not contain other statements.
All the container statements and leaf statements together form the configuration hierarchy.
The following illustration shows a part of the hierarchy tree. The protocols statement is a top-level
statement at the trunk of the configuration tree. The ospf, area, and interface statements are all
subordinate container statements of a higher statement; that is, they are branches of the hierarchy tree.
The hello-interval statement is a leaf on the tree.
Figure 1: Configuration Statement Hierarchy Example
5
Move Among Hierarchy Levels
The following table shows the CLI commands you use to navigate the levels of the configuration
statement hierarchy.
Table 1: CLI Configuration Mode Navigation Commands
Opis polecenia
edit hierarchy-level Moves to an existing configuration statement hierarchy or creates a hierarchy and moves
to that level.
exit Moves up the hierarchy to the previous level where you were working. This command is,
in effect, the opposite of the edit command. Alternatively, you can use the quit command.
The exit command and the quit command are interchangeable.
up Moves up the hierarchy one level at a time.
top Moves directly to the top level of the hierarchy.
6
Other Tools to Configure and Monitor Juniper Networks Devices
Apart from the CLI, Junos OS also supports the following applications, scripts, and utilities that enable
you to configure and monitor Juniper Networks devices:
• J-Web GUI—Available on select Juniper Networks devices, the J-Web GUI enables you to monitor,
configure, troubleshoot, and manage the device by means of a browser with HTTP or HTTPS
enabled. For more information, see the J-Web Podręcznik użytkownika interfejsu.
• Junos XML management protocol—The Junos XML management protocol enables you to monitor
and configure Juniper Networks devices. For more information, see the Junos XML Management
Protocol Developer Guide.
• NETCONF API—You can also use the NETCONF XML management protocol to monitor and
configure Juniper Networks devices. For more information, see the NETCONF XML Management
Protocol Developer Guide.
• Commit scripts and self-diagnosis features—You can define scripts to enforce custom configuration
rules, use commit script macros to provide simplified aliases for frequently used configuration
statements, and configure diagnostic event policies and actions associated with each policy. For more
information, see the Junos OS Automation Scripting User Guide.
• MIBs—You can use enterprise-specific and standard MIBS to retrieve information about the hardware
and software components on a Juniper Networks device. For more information about MIBs, see the
Junos OS Network Management Administration Guide for Routing Devices.
Configure Junos OS in a FIPS Environment
With Junos-FIPS you can configure a network of Juniper Networks devices in a FIPS 140-2
środowisko.
The Junos-FIPS software environment requires the installation of FIPS software by a Crypto Officer. In
Junos-FIPS, some Junos OS commands and statements have restrictions and some additional
configuration statements are available. For more information, see the following resources:
• Common Criteria and FIPS Certifications—Provides links to guidelines for configuring Juniper
Networks devices so the secure environment complies with the requirements of public sector
certifications such as Common Criteria and FIPS certification.
• Compliance Advisor—A Web application that provides regulatory compliance information about
Common Criteria, FIPS, Homologation, ROHS2, and USGv6 for Juniper Networks products.
7
ZOBACZ TAKŻE
IPsec Requirements for Junos-FIPS
Configuring IPsec for Enabling Internal Communications Between Routing Engines for Junos OS in
Tryb FIPS
8
2
ROZDZIAŁ
Pierwsze kroki
IN THIS CHAPTER
Getting Started: A Quick Tour of the CLI | 10
Online Help in the CLI | 35
CLI Environment Settings | 42
Getting Started: A Quick Tour of the CLI
W TEJ SEKCJI
Get Started with the Command-Line Interface | 10
Switch Between Operational Mode and Configuration Mode | 12
Use Keyboard Sequences to Navigate and Edit the CLI | 14
Configure a User Account on a Juniper Networks Device | 16
Use the CLI Editor in Configuration Mode | 19
Check the Status of a Juniper Networks Device | 22
Roll Back Configuration Changes | 25
Configure a Routing Protocol | 27
The following topics can help you (the network administrator) get started with the Junos OS CLI to
perform configuration changes, switch between operational mode and configuration mode, create a user
account, and execute some of the basic commands.
NOTE: If you need a basic introduction to Junos OS, see the Getting Started Guide for
Junos OS.
For more in-depth information, as well as to learn how to use Junos OS with Juniper
Networks devices, see the Overview for Junos OS.
This Junos OS CLI Guide assumes that you are familiar with Junos OS concepts and
operation principles.
Get Started with the Command-Line Interface
This topic shows you how to start the Junos OS CLI, view the command hierarchy, and make minor
zmiany konfiguracji.
10
NOTE: Before you begin, make sure that your device hardware is set up and Junos OS is
installed. You must have a direct console connection to the device or network access
using SSH or Telnet. If your device is not set up, follow the installation instructions
provided with the device before proceeding.
To log in to a device and start the CLI:
1. Log in as root.
The root login account has superuser privileges, with access to all commands and statements.
2. Start the CLI:
root# cli
root@>
The > command prompt shows that you are in operational mode. Later, when you enter configuration
mode, the prompt will change to #.
NOTE: If you are using the root account for the first time on the device, remember that
the device ships with no password required for root. The first time you commit a
configuration, you must set a root password. Root access is not allowed over a telnet
session. To enable root access over an SSH connection, you must configure the system
services ssh root-login allow statement.
CLI commands can vary by platform and software release. The CLI includes several ways to get help
about available commands. This section demonstrates some examples showing how to get help:
1. Type ? to show the top-level commands available in operational mode.
root@> ?
Możliwe zakończenia:
clear Clear information in the system
configure Manipulate software configuration information
diagnose Invoke diagnose script
file Dokonywać file operacje
help Provide help information
monitor Show real-time debugging information
mtrace Trace multicast path from source to receiver
ping Ping remote target
quit Exit the management session
11
request Make system-level requests
restart Restart software process
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
2. Typ file ? to show all possible completions for the file rozkaz.
root@> file ?
Możliwe zakończenia:
<[Enter]> Execute this command
archive Archives files from the system
checksum Calculate file suma kontrolna
compare Compare files
copy Copy files (local or remote)
delete Delete files from the system
list List file informacja
rename Rename files
show Show file zawartość
source-address Local address to use in originating the connection
| Pipe through a command
3. Typ file archive ? to show all possible completions for the file archive command.
root@> file archive ?
Możliwe zakończenia:
compress Compresses the archived file using GNU gzip (.tgz)
destination Name of created archive (URL, local, remote, or floppy)
source Path of directory to archive
Switch Between Operational Mode and Configuration Mode
When you monitor and configure a device running Junos OS, you may need to switch between modes .
When you switch between operational mode and configuration mode, the command prompt also
12
changes. The operational mode prompt is a right-angle bracket (>). The configuration mode prompt is a
pound or hash sign (#).
To switch between operational mode and configuration mode:
1. When you log in to the device and type the cli command and press Enter, you are automatically in
operational mode:
—JUNOS 17.2B1.8 built 2018-05-09 23:41:29 UTC
% cli
user@host>
2. To enter configuration mode, type the configure command or the edit command in CLI operational
mode. The prompt in brackets ([edit]), also known as a banner, shows that you are in configuration
mode at the top of the hierarchy. For exampna:
użytkownik@host> skonfiguruj
Wejście do trybu konfiguracji
[redagować]
użytkownik@host#
The CLI prompt changes from user@host> to user@host#, showing that you are in configuration mode,
and a banner appears to indicate the hierarchy level.
3. You can exit configuration mode and return to operational mode in one of the following ways:
• To commit the configuration and exit:
[redagować]
user@host# commit and-quit
zobowiązać się do końca
Wyjście z trybu konfiguracji
user@host>
• To exit without committing:
[redagować]
user@host# exit
13
Wyjście z trybu konfiguracji
user@host>
When you exit configuration mode, the CLI prompt changes from user@host# to user@host>, and the
banner no longer appears. You can enter or exit configuration mode as many times as you wish
without committing your changes.
4. To display the output of an operational mode command such as show while in configuration mode,
issue the run configuration mode command. Then, specify the operational mode command:
[redagować]
user@host# run operational-mode-command
Na przykładample, to display the currently set priority value of the Virtual Router Redundancy Protocol
(VRRP) primary device while you are modifying the VRRP configuration for a backup device:
[edit interfaces xe-4/2/0 unit 0 family inet vrrp-group 27]
user@host# show
virtual-address [ 192.168.1.15 ];
[edit interfaces xe-4/2/0 unit 0 family inet vrrp-group 27]
user@host# run show vrrp detail
Physical interface: xe-5/2/0, Unit: 0, Address: 192.168.29.10/24
Interface state: up, Group: 10, State: backup
Priority: 190, Advertisement interval: 3, Authentication type: simple
Preempt: yes, VIP count: 1, VIP: 192.168.29.55
Dead timer: 8.326, Master priority: 201, Master router: 192.168.29.254
[edit interfaces xe-4/2/0 unit 0 family inet vrrp-group 27]
user@host# set priority …
Use Keyboard Sequences to Navigate and Edit the CLI
You can use keyboard sequences in the Junos OS CLI to navigate and edit the command line. You can
also use keyboard sequences to scroll through a list of recently executed commands. The following table
lists some of the CLI keyboard sequences. They are the same as those used in Emacs.
14
Table 2: CLI Keyboard Shortcuts
Keyboard sequence Action
Ctrl+b Move the cursor back one character.
Esc+b or Alt+b Move the cursor back one word.
Ctrl+f Move the cursor forward one character.
Esc+f or Alt+f Move the cursor forward one word.
Ctrl+a Move the cursor to the beginning of the command line.
Ctrl+e Move the cursor to the end of the command line.
Ctrl+h, Delete,
or Backspace
Delete the character before the cursor.
Ctrl+d Delete the character at the cursor.
Ctrl+k Delete the all characters from the cursor to the end of the command line.
Ctrl+u or Ctrl+x Delete the all characters from the command line.
Ctrl+w, Esc+Backspace,
or Alt+Backspace
Delete the word before the cursor.
Esc+d or Alt+d Delete the word after the cursor.
Ctrl+y Insert the most recently deleted text at the cursor.
Ctrl+l Redraw the current line.
Ctrl+p Scroll backward through the list of recently executed commands.
15
Table 2: CLI Keyboard Shortcuts (Continued)
Keyboard sequence Action
Ctrl+n Scroll forward through the list of recently executed commands.
Ctrl+r Search the CLI history incrementally in reverse order for lines matching the search
smyczkowy.
Esc+/ or Alt+/ Search the CLI history for words for which the current word is a prefix.
Esc+. or Alt+. Scroll backward through the list of recently entered words in a command line.
Esc+number sequence
or Alt+number sequence
Specify the number of times to execute a keyboard sequence.
Configure a User Account on a Juniper Networks Device
This topic describes how to use a root account to log in to a Juniper Networks device and configure a
new user account. You can configure an account for your own use or create a test account.
To configure a new user account on the device:
1. Log in as root and enter configuration mode:
root@host> skonfiguruj
[redagować]
root@host#
The ([edit]) prompt banner shows that you are in configuration edit mode at the top of the
hierarchia.
2. Change to the [edit system login] section of the configuration:
[redagować]
root@host# edit system login
16
[edytuj login do systemu]
root@host#
The prompt in brackets changes to [edit system login] to show that you are at a new level in the
hierarchia.
3. Now add a new user account. In the example, user1 represents a username:
[edytuj login do systemu]
root@host# edit user user1
Ten byłyample adds an account user1.
NOTE: User account names can contain a period (.). For example, you can have a
user account user.1. However, the username cannot begin or end with a period.
4. Configure a full name for the account. If the name includes spaces, enclose the entire name in
quotation marks (” “):
[edit system login user user1]
root@host# set full-name “User One”
5. Configure an account class. The account class sets the user access privileges for the account:
[edit system login user user1]
root@host# set class super-user
6. Configure an authentication method and password for the account:
[edit system login user user1]
root@host# set authentication plain-text-password
Nowe hasło:
Wpisz nowe hasło:
When the new password prompt appears, enter a clear-text password that the system can encrypt,
and then confirm the new password.
17
7. Zatwierdź konfigurację:
[edit system login user user1]
root@host# commit
zobowiązać się do końca
Configuration changes are not active until you commit the configuration. If the commit is
successful, a commit complete message appears.
8. Return to the top level of the configuration, and then exit:
[edit system login user user1]
root@host# top
[redagować]
root@host# exit
Wyjście z trybu konfiguracji
9. Log out of the device:
root@host> exit
% logout Connection closed.
10. To test your changes, log back in with the user account and password you just configured:
login: user1
Hasło: hasło
—JUNOS 17.2B1.8 built 2018-05-09 23:41:29 UTC
user1@host>
When you log in, you should see the new username at the command prompt.
You have successfully used the CLI to view the device status and perform a simple configuration change.
NOTE: For complete information about the commands to issue to configure your device,
including examples, zobacz przewodniki konfiguracji systemu operacyjnego Junos.
18
Use the CLI Editor in Configuration Mode
This topic describes basic commands that you can use to enter configuration mode in the CLI editor. The
topic also describes commands that you use to navigate the configuration hierarchy, get help, and
commit or revert the changes that you make during the configuration session.
Task Command/
Oświadczenie
Example
Edit Your Configuration
Przejdź do trybu konfiguracji.
When you start the CLI, the device is
in operational mode. You must
explicitly enter configuration mode.
When you do, the CLI prompt changes
from user@host> to user@host#, and the
hierarchy level appears in square
nawiasy.
configure user@host> configure
[redagować]
użytkownik@host#
Create a statement hierarchy.
You can use the edit command to
simultaneously create a hierarchy and
move to that new level in the
hierarchy. You cannot use the edit
command to change the value of
identyfikatory.
edit hierarchylevel value
[redagować]
user@host# edit security zones security-zone myzone
[edit security zones security-zone myzone]
użytkownik@host#
Create a statement hierarchy, and set
identifier values.
The set command is like edit, except
that your current level in the hierarchy
nie zmienia się.
set hierarchylevel value
[redagować]
user@host# set security zones security-zone myzone
[redagować]
użytkownik@host#
Navigate the Hierarchy
19
(Dalszy)
Task Command/
Oświadczenie
Example
Navigate down to an existing
hierarchy level. edit hierarchylevel
[redagować]
user@host# edit security zones
[edit security zones]
użytkownik@host#
Navigate up one level in the hierarchy.
up [edit security zones]
user@host# up
[edit security]
użytkownik@host#
Navigate to the top of the hierarchy.
top [edit security zones]
user@host# top
[redagować]
użytkownik@host#
Commit or Revert Changes
Commit your configuration.
commit [edit]
użytkownik@host# zatwierdzenie
zobowiązać się do końca
20
(Dalszy)
Task Command/
Oświadczenie
Example
Roll changes back from the current
sesja.
Use the rollback command to revert all
changes from the current
configuration session. When you run
the rollback command before you exit
your session or commit changes, the
software loads the most recently
committed configuration onto the
device. You must enter the rollback
statement at the edit level in the
hierarchia.
rollback [edit]
user@host# rollback
load complete
Wyjdź z trybu konfiguracji
Commit the configuration, and exit
configuration mode. commit and-quit [edit]
user@host# commit and-quit
user@host>
Exit configuration mode without
committing your configuration.
You must navigate to the top of the
hierarchy using the up or top
commands before you can exit
tryb konfiguracji.
exit [edit]
user@host# exit
The configuration has been changed but not
zaangażowany
Exit with uncommitted changes? [yes,no] (yes)
Uzyskaj pomoc
21
(Dalszy)
Task Command/
Oświadczenie
Example
Display a list of valid options for the
current hierarchy level. ? [edit ]
user@host# edit security zones ?
Możliwe zakończenia:
<[Enter]> Execute this command
> functional-zone Functional zone
> security-zone Security zones
| Pipe through a
rozkaz
[redagować]
ZOBACZ TAKŻE
Understanding CLI Configuration Mode | 51

Check the Status of a Juniper Networks Device

In operational mode, you can use show commands to check the status of the device and monitor the activities on the device.
To help you become familiar with show commands:
• Type show ? to display the list of show commands you can use to monitor the router:

Troubleshooting (Source-Grounded)

• Missing mandatory statement in configuration hierarchy: When you omit a required statement and then move to a different hierarchy level or run a show command in configuration mode, the CLI displays a message indicating which statement is missing (example shown: missing mandatory statement: 'mode').
• Configuration exit without committing (exclusive mode): In configure exclusive mode, exiting can trigger a prompt about discarding uncommitted changes and an auto-rollback to the previously committed state. Use the yes option to discard/rollback, or no to continue editing/commit later.
• Commit/access errors after an automatic rollback: Jeśli używasz commit confirmed and do not confirm within the specified interval, an automatic rollback occurs. After that, the message error: access has been revoked may appear for subsequent commit attempts. To re-lock the configuration for exclusive editing, you must start a new configure exclusive sesja.