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
From a web client
workstation, such as the workstation that you use for Cisco Unified Operating
System Administration, you can use SSH to connect securely to the Cisco Unified
You can access the Cisco
Unified Operating System CLI directly by using the monitor and keyboard that
you used during installation or by using a terminal server that is connected to
the serial port. Use this method if a problem exists with the IP address.
Before You Begin
Ensure you have the following information that is defined
A primary IP address and
An administrator ID
You will need this information to log in to the Cisco Unified
Perform one of the following actions depending on your method of
From a remote system, use SSH to connect securely to the Cisco
Unified Operating System. In your SSH client, enter
adminname specifies the Administrator ID and
hostname specifies the hostname that was
defined during installation.
From a direct connection, you receive this prompt
where ipt-1 represents the host name of the
Enter the administrator ID that was defined during
Enter the password that was defined at installation.
The CLI prompt displays. The prompt represents the Administrator
ID; for example:
You can now use any CLI command.
Tab completes command
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
command specifies the command name or the
command and parameter. See
"Detailed Help Example."
Query only command syntax
command represents the command name or the
command and parameter. See
If you enter a ?
after a menu command, such as set, it acts like the
Tab key and lists the commands that are
Detailed Help Example:
admin:help file list activelog
This will list active logging files
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
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]
Ctrl-C exits command
You can stop most interactive commands by entering the
Ctrl-C key sequence, as shown in the following
Exiting a Command with Ctrl-C
admin:utils system upgrade initiateWarning: Do not close this window without first exiting the upgrade command.
1) Remote Filesystem
Please select an option (1 - 2 or "q" ):
Exiting upgrade command. Please wait...
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
Quit CLI session
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.