Specifications

3-25
Cisco Wide Area Application Services Command Reference
OL-16451-01
Chapter 3 CLI Commands
cms
Device Modes application-accelerator
central-manager
Usage Guidelines Use the cms config-sync command to enable registered WAAS devices and standby WAAS Central
Manager to contact the primary WAAS Central Manager immediately for a getUpdate (get configuration
poll) request before the default polling interval of 5 minutes. For example, when a node is registered with
the primary WAAS Central Manager and activated, it appears as Pending in the WAAS Central Manager
GUI until it sends a getUpdate request. The cms config-sync command causes the registered node to
send a getUpdate request at once, and the status of the node changes as Online.
Use the cms database create command to initialize the CMS database. Before a node can join a WAAS
network, it must first be registered and then activated. The cms enable global configuration command
automatically registers the node in the database management tables and enables the CMS. Activate the
node using the WAAS Central Manager GUI.
The cms deregister command removes the node from the WAAS network by deleting registration
information and database tables.
To back up the existing management database for the WAAS Central Manager, use the cms database
backup command. For database backups, specify the following items:
• Location, password, and user ID
• Dump format in PostgreSQL plain text syntax
The naming convention for backup files includes the time stamp.
Note For information on the procedure to back up and restore the CMS database on the WAAS Central
Manager, see the Cisco Wide Area Application Services Configuration Guide.
When you use the cms recover identity word command when recovering lost registration information,
or replacing a failed node with a new node that has the same registration information, you must specify
the device recovery key that you configured in the Modifying Config Property,
System.device.recovery.key window of the WAAS Central Manager GUI.
Use the lcm command to configure local/central management (LCM) on a WAE. The LCM feature
allows settings that are configured using the device CLI or GUI to be stored as part of the WAAS
network-wide configuration data (enable or disable).
When you enter the cms lcm enable command, the CMS process running on WAEs and the standby
WAAS Central Manager detects the configuration changes that you made on these devices using CLIs
and sends the changes to the primary WAAS Central Manager.
When you enter the cms lcm disable command, the CMS process running on the WAEs and the standby
WAAS Central Manager does not send the CLI changes to the primary WAAS Central Manager. Settings
configured using the device CLIs will not be sent to the primary WAAS Central Manager.
If LCM is disabled, the settings configured through the WAAS Central Manager GUI will overwrite the
settings configured from the WAEs; however, this rule applies only to those local device settings that
have been overwritten by the WAAS Central Manager when you have configured the local device
settings. If you (as the local CLI user) change the local device settings after the particular configuration
has been overwritten by the WAAS Central Manager, the local device configuration will be applicable
until the WAAS Central Manager requests a full device statistics update from the WAEs (clicking the