The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Administrator with level 0 privilege—This administrator has read-only access privilege on the interface.
Administrator with level 1 privilege—This administrator has both read and write access privilege on the interface.
Note | Administrators can execute CLI commands based on the privileges defined for each of them. |
After the administrators with the various privileges are created, you can start the CLI session.
Note | This procedure applies to both Cisco Unified Communications Manager and the IM and Presence Service. The Operating System for Cisco Unified Communications Manager is called the Cisco Unified Operating System. The Operating System for the IM and Presence Service is called the Cisco Unified IM and Presence Operating System. To start a CLI session for the IM and Presence Service, you must use the Cisco Unified IM and Presence Operating System. |
You can access the Cisco Unified Operating System (or, for the IM and Presence Service, the Cisco Unified IM and Presence Operating System) remotely or locally:
Ensure you have the following information that is defined during installation:
You will need this information to log in to the Cisco Unified Operating System.
To complete commands, use Tab:
Enter the start of a command and press Tab to complete the command. For example, if you enter se and press Tab, set is completed.
Enter a full command name and press Tab to display all the commands or subcommands that are available. For example, if you enter set and press Tab, you see all the set subcommands. An * identifies the commands that have subcommands.
If you reach a command, keep pressing Tab, and the current command line repeats; this indicates that no additional expansion is available.
You can get two kinds of help about any command:
Detailed help that includes a definition of the command and an example of its use
Short query help that includes only command syntax
If you want to: |
At the CLI prompt: |
---|---|
Get detailed help |
Enter help command Where command specifies the command name or the command and parameter. See "Detailed Help Example." |
Query only command syntax |
Enter command? Where command represents the command name or the command and parameter. See "Query Example." |
If you enter a ? after a menu command, such as set, it acts like the Tab key and lists the commands that are available.
admin:help file list activelog activelog help: This will list active logging files options are: page - pause output detail - show detailed listing reverse - reverse sort order date - sort by date size - sort by size file-spec can contain '*' as wildcards Example: admin:file list activelog platform detail 02 Dec,2004 12:00:59 <dir> drf 02 Dec,2004 12:00:59 <dir> log 16 Nov,2004 21:45:43 8,557 enGui.log 27 Oct,2004 11:54:33 47,916 startup.log dir count = 2, file count = 2
admin:file list activelog?Syntax: file list activelog file-spec [options] file-spec mandatory file to view options optional page|detail|reverse|[date|size]
You can stop most interactive commands by entering the Ctrl-C key sequence, as shown in the following example:
admin:utils system upgrade initiateWarning: Do not close this window without first exiting the upgrade command. Source: 1) Remote Filesystem 2) DVD/CD q) quit Please select an option (1 - 2 or "q" ): Exiting upgrade command. Please wait... Control-C pressed admin:
Note | If you execute the command utils system switch-version and enter Yes to start the process, entering Ctrl-C exits the command but does not stop the switch-version process. |
At the CLI prompt, enter quit. If you are logged in remotely, you get logged off, and the ssh session is dropped. If you are logged in locally, you get logged off, and the login prompt returns.