JNCIA-Junos Study Guide—Part 1

If two users are in private mode and both make the same change (For example, User 1 changes the system hostname to
apples while User 2 sets the hostname to oranges), the second commit will fail with an error message to avoid
configuration conflicts. The software places the second user’s changes into effect if User 2 issues a second commit command.
When chassis clustering is in effect, the configure private command is automated. In some other environments, you
might want to require users to use only configure private. When creating user accounts, it is possible to limit the
commands available to users through the assigned properties. We discuss user accounts and their assigned properties later in
this course.
If a user is in configuration mode and has altered the candidate configuration, other users cannot enter configuration mode
using the exclusive or private options. The changes made by the first user must be committed or cancelled prior to any
other users entering configuration mode with the exclusive or private options.

Statement Hierarchy

In configuration mode, you enter commands that affect the statement hierarchy. The statement hierarchy stores configuration
information and is independent of the CLI operational mode command hierarchy. The commands available in configuration
mode are also independent of the commands available in operational mode. For example, CLI operational mode includes a
show command to display specific operational information, while the CLI configuration mode provides a show command to
display the statement hierarchy. The two commands are independent of each other.
The software organizes the statement hierarchy in a tree structure similar to Windows folders or UNIX directories, grouping
related information into a particular branch of the tree.

© 2012 Juniper Networks, Inc. All rights reserved. User Interface Options • Chapter 2–11