Search Configure mode objects:
This page defines the operations available in Configure mode which can be set to either Exclusive or Private session.
commit– Commit current set of changes
delete– Delete a particular data element
edit– Edit a particular sub-element
exit– Exit from this level
help– Provide help information
quit– Exit from this level
request– Make system-level requests
revert– Revert back to the previous configuration state
rollback– Roll database back to last committed version
set– Set a parameter
show– Show a parameter
status– View status of users currently logged into CLI
top– Exit to top level and optionally run command
up– Exit one level of configuration
When issuing commands in the Configure mode, you must perform a
commit operation for the changes to take effect.
Any command that changes the mode or state of an object must be entered and committed separately. The examples under the
set command description include the appropriate commit entries.
setoperations to commit at one time (equates to modifying approximately 100 field values). To avoid errors, issue the
commitcommand on a regular basis to execute small batches of commands.
Optional arguments to include with the
commit command are described in the table below.
|Confirm a pending commit|
|Commit current set of changes and exit Configuration mode|
|Validate current configuration|
|Add a commit comment|
|Commit current set of changes with a timeout|
|Add a commit label|
|Commit current set of changes; do not query user|
|Specify a persist-id|
delete command to a specific data element, object, profile or configuration.
Objects scoped to a specific IP addressing domain.
Global objects applicable node-wide.
|N/A||Use this option to choose not to receive delete confirmation.|
Operations and Maintenance objects.
Profiles of configuration shared by multiple objects.
edit command allows you to edit a particular data element, object, profile or configuration.
exit operation to exit the Configure mode and revert to System mode.
help operation is a fast and simple means to learn more about the available commands and correct command syntax. For more information, refer to Using CLI Help.
quit operation serves the same function as
exit and takes you out of the Configure mode and revert to System mode.
request operation facilitates system-level requests for the following objects from both System and Configure modes.
addressContext– Objects scoped to a specific IP address domain.
alarms– Alarm Management
global– Global objects that are applicable Node wide
message– Send message to terminal of one or all users
oam– Operations and Maintenance objects.
system– System operations
revert operation to revert to the previous configuration state. When prompted, enter
y to proceed. To revert without receiving the confirmation prompt, enter
Use operation to roll the database back to the last committed version.
rollback options and obtain an index number, enter
rollback followed by Tab key. For example:
set operation to create or modify an object. The objects associated with this command are listed below and defined in subsequent pages in this guide.
addressContext– Objects scoped to a specific IP addressing domain. See Address Context (CLI).
global– Global objects that are applicable Node wide. See Global (CLI).
oam– Operations and Maintenance objects. See Operations and Maintenance (CLI).
profiles– Profiles of configuration shared by multiple objects. See Profiles (CLI).
system– System-level configuration. See System (CLI).
show operation displays the following objects and their attributes and is often used with
set operation (see above) to view results of provisioning activities.
addressContext– Objects scoped to a specific IP addressing domain.
details– Show details.
displaylevel– Use to define the level (1-64) of detail to show.
global– Global objects that are applicable Node wide.
oam– Operations and Maintenance objects.
profiles– Profiles of configuration shared by multiple objects.
system– System-level configuration.
status command displays the status of all users currently logged into CLI.
top operation is used to exit to the top level. In Edit mode, the
top command takes you to the top most level of CLI commands from any level.
up operation is used to exit one level of configuration. In Edit mode, the
up command takes you to one level up.
In this section: