Page History

The following CLI operations are available in Configure mode.Click a link to go directly to that topic.

• 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

Anchor
commit commit

commit

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.

Example:

% set addressContext default zone core ipPeer core_peer ipAddress 10.11.12.13 ipPort 5060
% set addressContext default zone peer ipPeer peer_peer ipAddress 10.11.12.14 ipPort 5060
% commit

Optional arguments to include with the commit command are described in the table below.

Anchor
delete delete

delete

Use the delete command to a specific data element, object, profile or configuration.

Command Syntax

% delete
	addressContext
	global
	no-confirm
	oam
	profiles
	system

Command Parameters

Anchor
edit edit

edit

The edit command allows you to edit a particular data element, object, profile or configuration.

Anchor
exit exit

exit

Use the exit operation to exit the Configure mode and revert to System mode.

Anchor
help help

help

The 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.

Anchor
quit quit

quit

The quit operation serves the same function as exit and takes you out of the Configure mode and revert to System mode.

Anchor
request request

request

The 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

The command syntax of this operation is described in detail in CLI System-Level Mode in the section also named Request Command Details - CLI.

Anchor
revert revert

revert

Use the revert operation to revert to the previous configuration state. When prompted, enter y to proceed. To revert without receiving the confirmation prompt, enter revert no-confirm.

Command Example

% revert
All configuration changes will be lost. Proceed? [yes,no] y

Anchor
rollback rollback

rollback

Use operation to roll the database back to the last committed version.

Command Syntax

% rollback <index#>

Command Example

To view rollback options and obtain an index number, enter rollback followed by Tab key. For example:

% rollback <Tab>
Possible completions:
  0 - 2012-08-21 17:43:57 by admin via netconf
  1 - 2012-08-21 15:08:19 by system via system
To rollback to the committed version dated 2012-08-21, enter:
% rollback 1

Anchor
set set

set

Use the set operation to create or modify an object. The objects associated with this command are listed below and defined in subsequent chapters 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.

Anchor
show show

show

The 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.

Anchor
status status

status

The status command displays the status of all users currently logged into CLI.

Command Example

% status
Users currently editing the configuration:
admin ssh (cli from 10.113.130.13) on since 2012-08-22 00:54:50 private mode 

Anchor
top top

top

The 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.

Anchor
up up

up

The up operation is used to exit one level of configuration. In Edit mode, the up command takes you to one level up.