1 Introduction
This document provides an overview of the Ericsson Command-Line Interface (ECLI). The ECLI is a terminal-based CLI, which allows you to monitor and manage the Managed Element (ME). It is based on industry de facto standard patterns to make it easy for you to learn how to manage the system.
The ECLI enables you to interact with the Management Information Base (MIB) through common, generic-purpose commands.
1.1 Related Information
For a complete description about the ECLI, including descriptions of all commands, key combinations, error messages, character support, and examples, refer to Interwork Description Ericsson Command-Line Interface.
For information on the Managed Object Model (MOM), Managed Object Classes (MOCs), Managed Objects (MOs), and related concepts mentioned in this document, refer to Managed Object Model User Guide.
1.2 Key Features of ECLI
The key features of the ECLI are described in Table 1.
|
Feature |
Description |
|---|---|
|
Access control |
The result of the ECLI commands manipulating the MIB is subject to authentication and authorization. If you have no permission to access an MO instance or attribute, then operations behave as if the MO instance does not exist. |
|
Auto-completion |
By pressing the Tab key, all possible ECLI command completions are displayed and unique completions are added to the command line. |
|
Context-sensitive help |
By pressing the ? key, a description of the ECLI command element is displayed. |
|
ECLI modes |
2 ECLI modes are supported. Exec mode is intended for observation and executing actions. Config mode is used for changing the ME configuration. |
|
Model driven |
The ECLI command elements and their properties are defined in the MOM as MOCs, attributes, and actions. |
|
Navigation |
The position in the MO tree can be changed. The position determines the context of the ECLI command. |
|
Security |
|
|
Transactions |
Configuration changes are applied through atomic transactions. Thus, it is ensured that all or none of the operations are executed. |
2 ECLI Modes
The ECLI provides the following two modes:
- Exec mode – Displays the status of the ME. In this mode, you enter commands to monitor the ME, display its configuration, and execute actions.
- Config mode – Used to change the ME configuration. In this mode, you start a configuration transaction to the MIB, enter commands to change the ME configuration, and commit the changes.
As shown in Figure 1, when you initiate an ECLI session, you always enter Exec mode, which is the default mode.
Some of the basic ECLI commands are described in Table 2.
|
Command |
Description |
|---|---|
|
abort |
Discards the changes in the transaction, terminates the transaction, and returns to Exec mode. When used with argument -s, the ECLI remains in Config mode and starts a new transaction instead of returning to Exec mode. |
|
commit |
Validates the transaction, commits the configuration changes, keeps the ECLI position, and returns to Exec mode. When used with argument -s, the ECLI remains in Config mode and starts a new transaction instead of returning to Exec mode. |
|
configure |
Enters Config mode and initiates a new configuration transaction. |
|
end |
Returns from Config mode to Exec mode when there are no changes in the configuration transaction. Use command abort or commit if you wish to return to the Exec mode after entering configuration changes. |
|
exit |
Exits the ECLI session. |
3 Start an ECLI Session
To start an ECLI session:
- Use a terminal and start the SSH session.
Example of logon with OpenSSH client:
ssh <user>@<target_host> -p 22
The options are as follows:
- <user> – Username.
- <target_host> – The OAM virtual IP address of the ME.
- -p (port number) – TCP port 22 is default.
Root user access is denied.
- Wait for the session to start.
4 Use ECLI Online Features
The ECLI provides online and context-sensitive help. It enables you to access information and learn about the commands, the MIB, and the MOM without relying on the documentation library.
4.1 Static Help
Command help provides static help about the ECLI. The command is described in Table 3.
|
Command |
Description |
|---|---|
|
help |
Displays a quick ECLI introduction and a summary of the main commands applicable to the ECLI mode (Exec or Config). |
4.2 Information Model Help
Command help also provides information model help. The command is described Table 4.
|
Command |
Description |
|---|---|
|
help -t |
Displays the whole MOC tree from the top MOC ManagedElement. |
|
help -t -m <moc_name> |
Displays the subtree beneath a MOC. |
|
help -m <moc_name> |
Displays detailed information about a MOC. |
4.3 Context-Sensitive Help
By pressing the ? key, you can request context-sensitive help on the ECLI commands and MOM elements (MOCs, attributes, and actions). The returned output depends on your input, the ECLI mode, and the ECLI position. Online help is only available for commands and model elements that can be auto-completed in the current ECLI mode.
The following examples show how to use the ? key to trigger context-sensitive help:
>show?
show Command Display information |
>show ?
--moc Option to select a specific child
MOC under the current DN
--recursive Display all information
--sort Sort the MO instances in
numerical/alphabetical order
--verbose Display verbose information
-m Option to select a specific child
MOC under the current DN
-r Display all information
-s Sort the MO instances in
numerical/alphabetical order
-v Display verbose information
+ManagedElement The top-level class in the Common
Information Model is Managed Element
root Managed Object Class.
|
>show -v -?
--recursive Display all information -r Display all information |
(config-ManagedElement=NODE06ST)>userLabel?
userLabel String [optional] A freetext string for additional information to assist Managed Element identification. |
4.4 Auto-Completion
The Tab key can be used at any point on the command line to either autocomplete the line or (if more than one option for completion exists) display all the valid options matching what has been typed so far, for example:
>dn ManTab
>dn ManagedElement=NODE06ST
>dn ManagedElement=NODE06ST,Tab
CSCF-Application=CSCF CscfDomainRoutingApplication=CscfDomainRouting CscfEosApplication=CscfEos DIA-CFG-Application=DIA DNS-Application=DNS ExtNetSel-Application LdapClientApplication=LdapClientApplication NumberNormalisation=NumberNormalisation SigComp-Subsystem=SigComp SystemFunctions=1 Transport=1 |
>dn ManagedElement=NODE06ST,
>dn ManagedElement=NODE06ST,cscfTab
CSCF-Application=CSCF CscfDomainRoutingApplication=CscfDomainRouting CscfEosApplication=CscfEos |
>dn ManagedElement=NODE06ST,cscf
5 Navigate in MIB
Navigation allows you to change the ECLI position without changing the configuration.
The commands described in Table 5 are used to navigate in the MIB.
|
Command |
Description |
|---|---|
|
<RDN> |
Changes the ECLI position to the Relative Distinguished Name (RDN), which is the address of an MO instance in relation to its parent MO. Example: >ManagedElement=NODE06ST |
|
dn |
Navigates to any position in the MIB. Example: >dn ManagedElement=NODE06ST,SystemFunctions=1 |
|
back [-h] |
Navigates back to the previous position in the MO tree. With option -h, the 10 previous positions in the MO tree are listed without changing the current position. |
|
show-dn |
Displays your position in the MIB. |
|
top |
|
|
up |
|
|
.. |
Changes the ECLI position to the parent MO. Command .. can be part of the RDN navigation command, for example, (SysM=1)>..,Fm=1. |
- Note:
- In Config mode, command <RDN> creates the corresponding MO if it does not exist.
6 Display ME Status
The commands described in Table 6 are used to display the ME status.
|
Command |
Description |
|---|---|
|
show |
Displays the configuration and state information as MO properties. Without argument, only those attributes are displayed that have a non-default value assigned. With argument -v, all attributes are displayed. With argument -r child MO instances are displayed recursively. |
|
show-table |
Displays configuration and state information in tabular format. |
|
show-config |
Displays the output in configuration format. The format is also a valid input for the ECLI. Thus, copy/paste or terminal input/output redirection allows configuration copy. |
7 Change ME Configuration
You can change the ME configuration by explicitly creating MOs, updating MOs (setting and changing MO attributes), and deleting MOs.
Risk of data loss or data corruption.
Ensure to commit the changes to make them effective.
The commands described in Table 7 are used to change the ME configuration and can only be used in Config mode.
|
Command |
Description |
|---|---|
|
<RDN> Example: (config-Snmp=1)>SnmpTargetV1=OSS_v1 |
Creates an MO if it does not exist. |
|
<attribute_name>=<attribute_value> Example: (config-SnmpTargetV1=OSS_v1)>address=192.0.2.10 |
Sets or changes a simple attribute value. |
|
no <attribute_name> Example: (SnmpTargetV2C)>no informRetryCount |
Deletes an attribute value. |
|
no <RDN> Example: (config-Snmp=1)>no SnmpTargetV3=OSS_v3 |
Deletes an MO. |
8 Execute MO Actions
An MO action is a command that you can use only when the ECLI is positioned at the proper MO. Actions are used to trigger MO-specific operations.
Risk of data loss or data corruption.
Unless stated otherwise, only execute actions in Exec mode to minimize the risk to misconfigure the system.
The command syntax to execute actions is described in Table 8.
|
Command |
Description |
|---|---|
|
[.,] <action_name> [--<action_parameter_name> <action_parameter_value>] ... Example: (Schema=2)export --uri sftp://user@10.64.88.91/tmp/ --password userpwd |
Executes an action. |
If <action_name> is conflicting with any command name, give the action request as '.,<action_name>' if the action must be executed from the current Distinguished Name.

Contents
