Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Supported Platforms

 

Related Documentation

 

Forms of the configure Command

The Junos OS supports three forms of the configure command: configure, configure private, and configure exclusive. These forms control how users edit and commit configurations and can be useful when multiple users configure the software. See Table 1.

Table 1: Forms of the configure Command

Command

Edit Access

Commit Access

configure

  • No one can lock the configuration. All users can make configuration changes.

    When you enter configuration mode, the CLI displays the following information:

    • A list of other users editing the configuration.
    • Hierarchy levels the users are viewing or editing.
    • Whether the configuration has been changed, but not committed.
    • When multiple users enter conflicting configurations, the most recent change to be entered takes precedence.
  • No one can lock the configuration. All users can commit all changes to the configuration.
  • If you and another user make changes and the other user commits changes, your changes are committed as well.

configure exclusive

  • One user locks the configuration and makes changes without interference from other users.
  • Other users can enter and exit configuration mode, but they cannot commit the configuration.
  • If you enter configuration mode while another user has locked the configuration (with the configure exclusive command), the CLI displays the user and the hierarchy level the user is viewing or editing.
  • If you enter configuration mode while another user has locked the configuration, you can forcibly log out that user with the request system logout operational mode command. For details, see the Junos OS Operational Mode Commands.

configure private

  • Multiple users can edit the configuration at the same time.
  • Each user has a private candidate configuration to edit independently of other users.
  • When multiple users enter conflicting configurations, the first commit operation takes precedence over subsequent commit operations.
  • When you commit the configuration, the router verifies that the operational (running) configuration has not been modified by another user before accepting your private candidate configuration as the new operational configuration.
  • If the configuration has been modified by another user, you can merge the modifications into your private candidate configuration and attempt to commit again.
 

Related Documentation

 

Published: 2012-11-27

Supported Platforms

 

Related Documentation

 

Published: 2012-11-27

Previous Page Next Page