The
CLI includes two modes:
- System Mode—The default mode when you first login to CLI for performing various system-level operations and viewing configuration details, status and statistics.
- Configure Mode—Use this mode to create, modify, view, and delete configurable objects.
Anchor |
---|
SystemMode | SystemMode | System Mode
The following system operations are available from the top-level (System) CLI mode:
change-password
– Change your passwordcommit
– Confirm a pending commitconfigure
– Switch to Configure mode to provision the system.exit
– Exit the management sessionhelp
– View help informationquit
– Exit the management sessionrequest
– Make system-level requestsreset
– Reset the terminalreset-password
– Reset another user's passwordset
– Set CLI propertiesset-path
– Set relative show pathshow
– View information about the systemsource
– Select a CLI configuration file to loadtop
– Exit to top level and optionally run commandup
– Exit one level of configuration
Anchor |
---|
ConfigureMode | ConfigureModeTo access Configure mode, enter the following command from CLI prompt:
Code Block |
---|
|
admin@SBC1> configure <exclusive | private | no-confirm> |
where,
<exclusive | private>
represents the type of configuration access for the session, either Exclusive or Private. The no-confirm
setting can be used in either Exclusive or Private sessions to suppress system prompts for confirmations when entering commands.
If you enter configure
with no argument, the system defaults to the Private session.
The following operations are supported in both Exclusive and Private sessions:
commit
– Commit the current set of changesdelete
– Delete a data elementedit
– Edit a sub-elementexit
– Exit from this levelhelp
– Provide help informationquit
– Exit from this levelrequest
– Make system-level requestsrevert
– Remove latest uncommitted configuration changes from memoryrollback
– Roll back database to last committed versionset
– Set a parameter, flag or configurationshow
– Show a parameterstatus
– Display users currently editing the configurationtop
– Exit to top level and optionally run commandup
– Exit one level of configuration
To exit Configure mode, enter either quit
or exit
.
Excerpt Include |
---|
| CLI Configure Mode |
---|
| CLI Configure Mode |
---|
nopanel | true |
---|
|
Exclusive Session
Allows The Exclusive session allows a user to exclusively configure the system via CLI. Only one exclusive session is possible at a time. An exclusive session cannot start if a private session is in the process of committing changes.
Below is an example of setting configure mode to ‘exclusive’.
Code Block |
---|
|
admin@SBC1> configure exclusive
Entering configuration mode exclusive
Warning: uncommitted changes will be discarded on exit
[ok][2013-07-05 01:53:11]
[edit]
admin@SBC1% |
Info |
---|
|
note |
Uncommitted changes are discarded upon exit from Configure mode. |
Private Session
Multiple private sessions can occur simultaneously. Changes made Committed changes in a private session can be committed to will update the current configuration while other private sessions are open and active. Private sessions are allowed concurrently with an exclusive session; however, but private session users cannot commit their changes until the exclusive session ends.
Note |
---|
A total of six simultaneous sessions are allowed at one time (including the exclusive session). |
Multiexcerpt |
---|
MultiExcerptName | CLI Session Limit |
---|
|
Info |
---|
| Up to 16 simultaneous CLI sessions are allowed. |
|
The following
Here is an example of setting
the a session to ‘private’:
Code Block |
---|
|
admin@SBC1> configure private
Entering configuration mode private
[ok][2013-01-05 17:06:22]
[edit]
admin@SBC1% |
Info |
---|
|
note |
Uncommitted changes are discarded upon exit from Configure mode. |