- Cisco Unified SRST Manager Roadmap
- Cisco Unified SRST Manager Workflow
-
- Cisco Unified SRST Manager Overview
- Cisco Unified SRST Manager Administration Interfaces
- About the Cisco Unified SRST Manager GUI
- Overview of Initial Configuration Tasks
- Logging In to the Cisco Unified SRST Manager Graphical User Interface
- Configuring E-SRST Site Provisioning
- Using the Setup Wizard
- Configuring Users for Cisco Unified SRST Manager
- Using the Central Call Agent Wizard to Add Cisco Unified Communications Manager Information
- Viewing and Updating the Central Call Agent
- Viewing the Cisco Unified SRST References
- Viewing, Adding, and Removing the Central Call Agent
- Viewing the Cluster Nodes Associated With a Central Call Agent
- Viewing and Provisioning Sites
- Changing the Information for a Single Cisco Unified SRST Site
- Changing the Information for Multiple Cisco Unified SRST Sites at Once
- Using Site Templates
- Creating, Changing, and Viewing a Site Template
-
- Monitoring the Provisioning Status of a Branch Device
- Monitoring the Learned Cisco Unified Communications Manager Express Routers
- Viewing Configuration Changes
- Maintaining the Cisco Unified SRST Manager System
- Viewing Reports
- Backing Up and Restoring Data
- Configuring Backup and Restore
- Backing Up and Restoring Data Using the CLI
- Saving and Reloading the Cisco Unified SRST Manager Configuration
- Glossary
How to Use the Cisco Unified SRST Manager CLI
This chapter provides helpful tips for understanding and configuring the Cisco Unified SRST Manager software using the CLI.
About the Cisco Unified SRST Manager CLI
The Cisco Unified SRST Manager command line interface (CLI) provides additional administrative functionality beyond the GUI. Access the CLI using a secure shell (ssh) client.
Cisco Unified SRST Manager CLI commands have a structure similar to that of Cisco IOS CLI commands. For both interfaces, standard Cisco IOS navigation and command-completion conventions apply. For example, ? lists options, TAB completes a command, and | directs show command output.
The following are differences between the Cisco Unified SRST Manager CLI and the Cisco IOS CLI:
- Standard command names and options do not necessarily apply. A notable example is the command for accessing global configuration mode: the Cisco IOS command is configure terminal ; the network module command is config terminal or config t.
- Cisco Unified SRST Manager employs a last-one-wins rule. For example, if two users both try to set the IP address for the same entity at the same time, the system starts and completes one operation before it starts the next. The last IP address set is the final result.
- The Cisco Unified SRST Manager command modes, EXEC and configuration operate similarly to the EXEC and configuration modes in the Cisco IOS CLI.
- After you enter configuration mode, all the CLI commands can be used in the no form. Example:
Understanding Command Modes
The Cisco Unified SRST Manager command environment is divided into two basic modes:
- EXEC—This is the mode that you are in after you log in to the Cisco Unified SRST Manager command environment. Some Cisco Unified SRST Manager EXEC commands only display or clear parameter values, stop or start the entire system, or start troubleshooting procedures. However, unlike Cisco IOS EXEC mode, Cisco Unified SRST Manager EXEC mode has a few commands that change parameter values.
- Configuration—This mode enables you to make system configuration changes, which are stored in the running configuration. If you later save the running configuration to the startup configuration, the changes made with the configuration commands are restored when you reboot the software.
Cisco Unified SRST Manager configuration mode has various subconfiguration levels. The global configuration mode changes the command environment from EXEC to configuration. You can modify many software parameters at this level. However, certain configuration commands change the environment to more specific configuration modes where modifications to the system are entered. For example, the interface ethernet 0 command changes the environment from config to config-interface. At this point, you can enter or modify interface parameter values.
The commands available to you at any given time depend on the current mode. Entering a question mark (?) at the CLI prompt displays a list of commands available for each command mode. The descriptions in this command reference indicate each command’s environment mode.
Table 15 describes how to access and exit various common command modes of the Cisco Unified SRST Manager software. It also shows examples of the prompts displayed for each mode.
Entering the Command Environment
After you install Cisco Unified SRST Manager and establish IP connectivity with it, use this procedure to enter the command environment.
Note This procedure describes how to enter the Cisco Unified SRST Manager command environment remotely. From the server hosting the Cisco Unified SRST Manager VM, it is possible to enter the command environment by opening a console window for the VM within the vSphere client. When using this method, the IP address, username, and password are not required.
Prerequisites
The following information is required to enter the command environment:
Summary Steps
1. Connect to Cisco Unified SRST Manager using ssh:
2. When prompted, enter the Cisco Unified SRST Manager password.
Detailed Steps
Exiting the Command Environment
To leave the Cisco Unified SRST Manager command environment, in EXEC mode enter the exit command once to exit EXEC mode, and again to exit the application.
The following example illustrates the exit procedure:
Getting Help
Entering a question mark ( ?) at the CLI prompt displays a list of commands available for each command mode. You can also get a list of keywords and arguments associated with any command by using the context-sensitive help feature.
To get help specific to a command mode, a command, a keyword, or an argument, use one of the following commands:
Using the no and default Forms of Commands
Where available, use the no form of a command to disable a function. Use the command without the no keyword to reenable a disabled function or to enable a function that is disabled by default. The command reference entry for each command provides the complete syntax for the configuration commands and describes what the no form of a command does.
Configuration commands can also have a default form, which returns the command settings to the default values. In those cases where a command is disabled by default, using the default form has the same result as using the no form of the command. However, some commands are enabled by default and have variables set to certain default values. In these cases, the default form of the command enables the command and sets the variables to their default values. Where available, the command reference entry describes the effect of the default form of a command if the command does not function the same way as the no form.
Saving Configuration Changes
Starting in EXEC mode, use the following command to copy the running configuration in flash memory to another location:
startup-config | tftp:tftp-server-address} filename
When you copy the running configuration to the startup configuration, enter the command on one line. In the following example, the running configuration is copied to the startup configuration as a file start. In this instance, enter the command on a single line.
When you copy to the FTP or TFTP server, this command becomes interactive and prompts you for the information. You cannot enter the parameters on one line. The following example illustrates this process. In the following example, the running configuration is copied to the FTP server, which requires a username and password. The IP address of the FTP server is 192.0.2.24. The running configuration is copied to the configs directory as file saved_start.
Troubleshooting Configuration Changes
Problem You lost some configuration data.
Recommended Action Copy your changes to the running configuration at frequent intervals. See the “Copying Configurations” section.
Problem You lost configuration data when you rebooted the system.
Explanation You did not save the data before the reboot.
Recommended Action Issue a copy running-config startup-config command to copy your changes from the running configuration to the startup configuration. When Cisco Unified SRST Manager reboots, it reloads the startup configuration.
Note All configuration changes require an explicit “save configuration” operation to preserve them in the startup configuration.