In this section:
The SBC Core CLI includes two modes:
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 configurationTo access Configure mode, enter the following command from the CLI prompt:
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 configurationTo exit Configure mode, enter either quit
or exit
.
The SBC limits the number of set
operations to commit at one time (equates to modifying approximately 100 field values). To avoid errors, issue the commit
command on a regular basis to execute small batches of commands.
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’.
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%
Uncommitted changes are discarded upon exit from Configure mode.
Multiple private sessions can occur simultaneously. Committed changes in a private session will update the current configuration while other private sessions are open and active. Private sessions are allowed concurrently with an exclusive session; however, private session users cannot commit their changes until the exclusive session ends.
Up to 16 simultaneous CLI sessions are allowed.
The following is an example of setting a session to ‘private’:
admin@SBC1> configure private Entering configuration mode private [ok][2013-01-05 17:06:22] [edit] admin@SBC1%
Uncommitted changes are discarded upon exit from Configure mode.