Cisco Wide Area Application Services Command Reference (Software Version 4.4.1)

EXEC Mode Commands

Use the EXEC mode for setting, viewing, and testing system operations. In general, the user EXEC commands allow you to connect to remote devices, change terminal line settings on a temporary basis, perform basic tests, and list system information.

The EXEC mode is divided into two access levels: user and privileged.

The user EXEC mode is used by local and general system administrators, while the privileged EXEC mode is used by the root administrator. Use the enable and disable commands to switch between the two levels. Access to the user-level EXEC command line requires a valid password.

The user-level EXEC commands are a subset of the privileged-level EXEC commands. The user-level EXEC prompt is the hostname followed by a right angle bracket (>). The prompt for the privileged-level EXEC command line is the pound sign (#). To execute an EXEC command, enter the command at the EXEC system prompt and press the Return key.

Note You can change the hostname using the hostname global configuration command.

The following example shows how to access the privileged-level EXEC command line from the user level:

WAE> enable

WAE#

To leave EXEC mode, use the exit command at the system prompt:

WAE# exit

WAE>

cd

To change from one directory to another directory in the WAAS software, use the cd EXEC command.

cd directoryname

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use this command to navigate between directories and for file management. The directory name becomes the default prefix for all relative paths. Relative paths do not begin with a slash (/). Absolute paths begin with a slash (/).

Examples

The following example shows how to change to a directory using a relative path:

WAE(config)# cd local1

The following example shows how to change to a directory using an absolute path:

WAE(config)# cd /local1

Related Commands

deltree

dir

lls

ls

mkdir

pwd

clear arp-cache

To clear the ARP cache, use the clear arp-cache EXEC command.

clear arp-cache [ipaddress | interface {GigabitEthernet slot/port | PortChannel index | Standby grpNumber | TenGigabitEthernet slot/port | InlinePort slot/grpnumber {lan | wan}}]

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Examples

The following example shows how to clear the ARP cache on the WAAS device:

WAE# clear arp-cache

Related Commands

license add

show interface

show license

show wccp

clear bmc

To clear the BMC logs and events, use the clear bmc EXEC command.

clear bmc [event-log]

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Examples

The following example shows how to clear the entries recorded in the bmc system event log on the WAAS device:

WAE# clear bmc event-log

Related Commands

show bmc

clear cache

To clear cached objects, use the clear cache EXEC command.

clear cache {cifs | dre}

clear cache http-metadatacache https {conditional-response | redirect-response | unauthorized-response}

clear cache http-metadatacache {all | conditional-response | redirect-response | unauthorized-response} [url]

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Usage Guidelines

After you use the clear cache dre command, the first 1 MB of data is not optimized. The Cisco WAAS software does not optimize the first 1 MB of data after a restart of the tcpproxy service. The data that is transmitted after the first 1 MB of data will be optimized according to the configured policy.

The clear cache dre command may cause the system to reboot, but you are asked to confirm before the command continues and you are given a chance to save any configuration changes that have been made to the running configuration.

The clear cache dre command does not delete the DRE cache contents but expires it by removing markers in the content to prevent reuse. If you want to delete the cache contents, use the disk delete-data-partitions command.

Examples

The following example shows how to clear the CIFS cached objects on the WAAS device:

WAE# clear cache cifs

The following example shows how to clear the HTTP metadata cache for conditional responses:

WAE# clear cache http-metadatacache conditional-response

Related Commands

license add

show cache http-metadatacache

show interface

show license

show wccp

clear cdp

To clear Cisco Discovery Protocol statistics, use the clear cdp EXEC command.

clear cdp {counters | table}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to clear the CDP counter statistics on the WAAS device:

WAE# clear cdp counters

Related Commands

license add

show interface

show license

show wccp

clear ip

To clear IP access list statistics, use the clear ip EXEC command.

clear ip access-list counters [acl-num | acl-name]

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to clear the IP access list counters on the WAAS device:

WAE# clear ip access-list counters

Related Commands

license add

show interface

show license

show wccp

clear license

To clear licensing configuration, use the clear license EXEC command.

clear license [license-name]

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to clear the licensing configuration on the WAAS device:

WAE# clear license

Related Commands

license add

show interface

show license

show wccp

clear logging

To clear syslog messages saved in a disk file, use the clear logging EXEC command.

clear logging

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

The clear logging command removes all current entries from the syslog.txt file but does not make an archive of the file. It puts a "Syslog cleared" message in the syslog.txt file to indicate that the syslog has been cleared.

Examples

The following example shows how to clear all entries in the syslog.txt file on the WAAS device:

WAE# clear logging

Feb 14 12:17:18 WAE# exec_clear_logging:Syslog cleared

Related Commands

license add

show interface

show license

show wccp

clear statistics

To reset statistics data, use the clear statistics EXEC command.

clear statistics {all | aoim | authentication | auto-discovery {all | blacklist} | datamover | directed-mode | dre [global] | filtering | flow monitor tcpstat-v1 | generic-gre | icmp | inline | ip | pass-through | peer dre | radius | synq | tacacs | tcp | tfo | udp | wccp | windows-domain | windows-print}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

The clear statistics command clears all statistical counters from the parameters given. Use this command to monitor fresh statistical data for some or all features without losing cached objects or configurations.

Not all command options are applicable for a device in central-manager mode.

Examples

The following example shows how to clear all authentication, RADIUS and TACACS+ information on the WAAS device:

WAE# clear statistics radius

WAE# clear statistics tacacs

WAE# clear statistics authentication

Related Commands

clear statistics accelerator

clear statistics connection

clear statistics accelerator

To clear all global statistics, use the clear statistics accelerator EXEC command.

clear statistics accelerator {cifs | epm | generic | http | mapi | nfs | ssl | video}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Examples

The following example shows how to clear the statistics for the CIFS application accelerator on the WAAS device:

WAE# clear statistics accelerator cifs

Related Commands

clear statistics

clear statistics connection

clear statistics connection

To clear connection statistics, use the clear statistics connection EXEC command.

clear statistics connection conn-id connection_id

clear statistics connection optimized [client-ip {ip_address | hostname} | client-port port | {cifs | epm | http | mapi | nfs | ssl | tfo | video} dre | peer-id peer_id | server-ip {ip_address | hostname} | server-port port]

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Examples

The following example shows how to clear the connection 1 statistics on the WAAS device:

WAE# clear statistics connection conn-id 1

Related Commands

clear statistics

clear statistics accelerator

clear statistics vn-service vpath

To clear VPATH statistics for your vWAAS device, use the clear statistics vn-service vpath EXEC command.

clear statistics vn-service vpath

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

The clear statistics vn-service vpath command removes all current entries from the syslog.txt file but does not make an archive of the file. It puts a "Syslog cleared" message in the syslog.txt file to indicate that the syslog has been cleared.

Examples

The following example shows how to clear all VPATH entries in the syslog.txt file on the vWAAS device:

WAE# clear statistics vn-service vpath

Related Commands

show statistics vn-service vpath

(config) vn-service vpath

clear transaction-log

To archive a working transaction log file, use the clear transaction-log EXEC command.

clear transaction-log {accelerator | flow}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Examples

The following example shows how to archive the flow transaction log file on the WAAS device:

WAE# clear transaction-log flow

Related Commands

license add

show interface

show license

show wccp

clear users

To clear user connections or to unlock users that have been locked out, use the clear users EXEC command.

clear users [administrative | locked-out {all | username username}]

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

The clear users administrative command clears the connections for all administrative users who are authenticated through a remote login service, such as TACACS. This command does not affect an administrative user who is authenticated through the local database. Only locally authenticated administrative users can run this command.

The clear users locked-out command unlocks user accounts that have been locked out. If a strong password policy is enabled (see the (config) authentication strict-password-policy command) a user account will be locked out if the user fails three consecutive login attempts. (This restriction does not apply to the admin account.)

Examples

The following example shows how to clear the connections of all authenticated users:

WAE(config)# clear users

The following example shows how to clear the connections of all administrative users authenticated through a remote login service (it does not affect administrative users authenticated through the local database):

WAE(config)# clear users administrative

The following example shows how to unlock all locked-out user accounts:

WAE(config)# clear users locked-out all

The following example shows how to unlock the account for username darcy:

WAE(config)# clear users locked-out username darcy

Related Commands

clear arp-cache

(config) authentication strict-password-policy

clear windows-domain-log

To clear the Windows domain server log file, use the clear windows-domain-log EXEC command.

clear windows-domain-log

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to clear all entries in the Windows domain log file on the WAAS device:

WAE# clear windows-domain-log

Related Commands

license add

show interface

show license

show wccp

clock

To set clock functions or update the calendar, use the clock EXEC command.

clock {read-calendar | set time day month year | update-calendar}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

If you have an outside source on your network that provides time services (such as a NTP server), you do not need to set the system clock manually. When setting the clock, enter the local time. The WAAS device calculates the UTC based on the time zone set by the clock timezone global configuration command.

Two clocks exist in the system: the software clock and the hardware clock. The software uses the software clock. The hardware clock is used only at bootup to initialize the software clock.

The set keyword sets the software clock.

Examples

The following example shows how to set the software clock on the WAAS device:

WAE# clock set 13:32:00 01 February 2005

Related Commands

show clock

cms

To configure the Centralized Management System (CMS) embedded database parameters for a WAAS device, use the cms EXEC command.

cms {config-sync | deregister [force] | lcm {enable | disable} | maintenance {full | regular} | recover {identity word} | restore filename | validate}

cms database {backup | create | delete | downgrade [script filename]}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

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 for a device that is already registered with the WAAS Central Manager. Then use the cms enable command to enable the CMS. For a device that is not registered with a WAAS Central Manager, use only the cms enable command to initialize the CMS database tables, register the node, and enable the CMS.

Note For a vWAAS device, the model type must be configured before enabling management services.

Before a node can join a WAAS network, it must first be registered and then activated. Activate the node by using the WAAS Central Manager GUI.

The cms deregister command removes the node from the WAAS network by deleting registration information and database tables.

The cms deregister force command forces the removal of the node from the WAAS network by deleting registration information and database tables. If disk encryption is enabled on the device, it is disabled after you confirm this action. All data in encrypted file systems and imported certificates and private keys for the SSL accelerator are lost after a reload.

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 and the WAAS version number.

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.

Note Do not run multiple instances of the cms database backup command simultaneously on a device. If a backup is in progress, you must wait for it to finish before using the command again.

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.

Note All CMS-related commands are disabled when running the cms restore command.

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 Force full database update button from the Device Dashboard window of the WAAS Central Manager GUI triggers a full update). When the WAAS Central Manager requests a full update from the device, the WAAS Central Manager settings will overwrite the local device settings.

Examples

The following example shows how to back up the cms database management tables on the WAAS Central Manager named waas-cm:

waas-cm# cms database backup 

creating backup file with label `backup'

backup file local1/acns-db-9-22-2002-17-36.dump is ready. use `copy' commands to move the 
backup file to a remote host.

The following example shows how to validate the cms database management tables on the WAAS Central Manager named waas-cm:

waas-cm# cms database validate 

Management tables are valid

Related Commands

(config) cms

show cms

cms secure-store

To configure secure store encryption, use the cms secure-store EXEC commands.

cms secure-store {init | open | change | clear | reset | mode{user-passphrase | auto-passphrase}}

Syntax Description

Defaults

A new Central Manager is configured for auto-generated passphrase mode with the secure store open.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Secure store encryption provides strong encryption and key management for your WAAS system. The WAAS Central Manager and WAE devices use secure store encryption for handling passwords, managing encryption keys, and for data encryption.

On a new Central Manager, secure store is initialized and open and in auto-generated passphrase mode. The only options are to change the pass phrase (which sets the secure store to user-provided passphrase mode) or to change to user-provided passphrase mode. To change to user-provided passphrase mode, use the cms secure-store mode user-passphrase command.

For secure store on the Central Manager, the data is encrypted using a key encryption key generated from the pass phrase with SHA-1 hashing and an AES 256-bit algorithm. When you enable secure store on a WAE device, the data is encrypted using a 256-bit key encryption key generated by SecureRandom, a cryptographically strong pseudorandom number. You can use your own password to enable secure store, but it is not necessary in auto-generated passphrase mode (the default), where the Central Manager generates a unique password automatically. A user-supplied password must conform to the following rules:

•Be 8 to 64 characters in length

•Contain characters only from the allowed set: A-Za-z0-9~%'!#$^&*()|;:,"<>/

•Contain at least one digit

•Contain at least one lowercase and one uppercase letter

If you are using the user-provided passphrase mode, when you reboot the Central Manager, you must manually reopen secure store using the cms secure-store open command. Until you open the secure store, a critical alarm is displayed on the Central Manager and services that use encryption (such as the SSL application accelerator) are not available. If you are using the auto-generated passphrase mode (the default), the Central Manager automatically opens the secure store after a reboot by using its own generated pass phrase.

The secure store passphrase mode on the primary Central Manager is replicated to the standby Central Manager (within the standard replication time). If the primary Central Manager is switched to auto-generated passphrase mode, the standby Central Manager secure store changes to the open state. If the primary Central Manager is switched to user-provided passphrase mode or the passphrase is changed, the standby Central Manager secure store changes to the initialized but not open state and an alarm is raised. You must manually open the secure store on the standby Central Manager.

When you enable secure store on a WAE, the WAE initializes and retrieves a new encryption key from the Central Manager. The WAE uses this key to encrypt user passwords, CIFS preposition and dynamic share credentials, and CIFS password credentials stored on the WAE. When you reboot the WAE after enabling secure store, the WAE retrieves the key from the Central Manager automatically, allowing normal access to the data that is stored in the WAAS persistent storage. If key retrieval fails, an alarm is raised and secure store will be in the initialized but not open state. You must open secure store manually.

If you have made any other CLI configuration changes on a WAE within the datafeed poll rate time interval (5 minutes by default) before you entered the cms secure-store command, you will lose those prior configuration changes and you will need to redo them.

Use the cms secure-store reset command if you reload a Central Manager that is configured in user-provided passphrase mode and you forget the secure store password. This command deletes all encrypted data, certificate and key files, and key manager keys. The secure store is left in the open state using auto-generated passphrase mode. For the complete procedure for resetting the secure store, see the "Resetting Secure Store Encryption on a Central Manager" section on page 9-17 in the Cisco Wide Area Application Services Configuration Guide.

Examples

The following example shows how to change the pass phrase mode of the secure store encryption on the WAAS Central Manager:

waas-cm# cms secure-store mode user-passphrase

Stopping cms.

Do you wish to switch to User-provided passphrase mode? [yes]/no :y

The passphrase must adhere to the following rules

*******************************************************************

* 1) Must be between 8 to 64 characters in length                 *

* 2) Allowed character set is A-Za-z0-9~%'!#$^&*()|;:,"<>/*

* 3) Must contain at least one digit                              *

* 4) Must contain at least one lowercase and one uppercase letter *

*******************************************************************

Enter new passphrase:

Confirm passphrase:

Starting cms.

Related CommandsRelated Commands

show cms secure-store

configure

To enter global configuration mode, use the configure EXEC command. You must be in global configuration mode to enter global configuration commands.

configure

To exit global configuration mode, use the end or exit commands. You can also press Ctrl-Z to exit from global configuration mode.

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to enable global configuration mode on a WAAS device:

WAE# configure 

WAE(config)# 

Related Commands

(config) end

(config) exit

show running-config

show startup-config

copy cdrom

To copy software release files from a CD-ROM, use the copy cdrom EXEC command.

copy cdrom install filedir filename

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to copy a software release file from a CD-ROM:

WAE# copy cdrom install 

Related Commands

install

reload

show running-config

show startup-config

write

copy cdrom wow-recovery

To recover Windows on WAAS on a virtual blade from a CD, use the copy cdrom wow-recovery EXEC command.

copy cdrom wow-recovery filedir filename

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the copy cdrom wow-recovery command to recover the Windows on WAAS system files of a virtual blade. This command allows you to recover Windows on your virtual blade while the WAAS software is running, without having to restart your WAE device.

This command is available only on platforms that have a CD-ROM drive. For platforms without a CD-ROM drive, use the copy usb wow-recovery EXEC command.

Examples

The following example shows how to recover Windows on a virtual blade from a CD:

WAE# copy cdrom wow-recovery WoW_RECOVERY

Related Commands

copy ftp

copy cdrom

copy usb

virtual-blade

(config) virtual-blade

copy compactflash

To copy software release files from a CompactFlash card, use the copy compactflash EXEC command.

copy compactflash install filename

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to copy a software release file from a CompactFlash card:

WAE# copy compactflash install

Related Commands

install

reload

show running-config

show startup-config

write

copy disk

To copy the configuration or image data from a disk to a remote location using FTP or to the startup configuration, use the copy disk EXEC command.

copy disk {ftp {hostname | ip-address} remotefiledir remotefilename localfilename | startup-config filename}

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the copy disk ftp EXEC command to copy files from a SYSFS partition to an FTP server. Use the copy disk startup-config EXEC command to copy a startup-configuration file to NVRAM.

Examples

The following example shows how to copy a startup-configuration file to NVRAM:

WAE# copy disk startup-config

Related Commands

install

reload

show running-config

show startup-config

write

copy ftp

To copy software configuration or image data from an FTP server, use the copy ftp EXEC command.

copy ftp disk {hostname | ip-address} remotefiledir remotefilename localfilename

copy ftp install {bios | bmc | image {hostname | ip-address}} remotefiledir remotefilename

copy ftp virtual-blade vb_num disk vb_disk {hostname | ip-address} remotefiledir remotefilename

copy ftp wow-recovery {hostname | ip-address} remotefiledir remotefilename

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the copy ftp disk EXEC command to copy a file from an FTP server to a SYSFS partition on the WAAS device. To show progress, this command prints a number sign (#) for each 1 MB of data that is copied.

Use the copy ftp install EXEC command to install an image file from an FTP server on a WAAS device. Part of the image goes to a disk and part goes to flash memory.

You can also use the copy ftp install EXEC command to redirect your transfer to a different location. A username and a password have to be authenticated with a primary domain controller (PDC) before the transfer of the software release file to the WAAS device is allowed.

Use the copy ftp wow-recovery EXEC command to copy a Windows operating system image from an FTP server to a virtual blade partition on the WAAS device.

To show progress, this command prints a number sign (#) for each 1 MB of data that is copied.

Examples

The following example shows how to copy an image file from an FTP server and install the file on the local device:

WAE# copy ftp install 10.1.1.1 cisco/waas/4.1 WAAS-4.1.1-k9.bin

Enter username for remote ftp server:biff

Enter password for remote ftp server:*****

Initiating FTP download...

printing one # per 1MB downloaded

Sending:USER biff

10.1.1.1 FTP server (Version) Mon Feb 28 10:30:36 EST

2000) ready.

Password required for biff.

Sending:PASS ***** 

User biff logged in.

Sending:TYPE I

Type set to I.

Sending:PASV

Entering Passive Mode (128,107,193,244,55,156)

Sending:CWD //ftp-sj.cisco.com/cisco/waas/4.0

CWD command successful.

Sending PASV

Entering Passive Mode (128,107,193,244,55,156)

Sending:RETR WAAS-4.1.1-k9.bin

Opening BINARY mode data connection for ruby.bin (87376881 bytes).

###################################################################################

writing flash component:

.................................................................

The new software will run after you reload.

The following example shows how to upgrade the BIOS. All output is written to a separate file (/local1/.bios_upgrade.txt) for traceability. The hardware-dependent files that are downloaded from Cisco.com for the BIOS upgrade are automatically deleted from the WAAS device after the BIOS upgrade procedure has been completed.

WAE# copy ftp install upgradeserver /bios/update53/derived/ bios.bin

Enter username for remote ftp server:myusername

Enter password for remote ftp server:*****

Initiating FTP download...

 .

 .

 .

Primary BIOS flashed successfully

Cleanup BIOS related files that were downloaded....

The new software will run after you reload.

WAE#

The following example shows how to copy a Windows image file from an FTP server and install the file on the virtual blade:

WAE# copy ftp wow-recovery 10.1.1.1 /cisco/waas/4.1 windows.iso

Enter username for remote ftp server:biff

Enter password for remote ftp server:*****

Initiating FTP download...

Related Commands

install

reload

show running-config

show startup-config

write

copy http

To copy configuration or image files from an HTTP server to the WAAS device, use the copy http EXEC command.

copy http install {hostname | ip-address}remotefiledir remotefilename [port portnum] [proxy proxy_portnum] [username username password]

Syntax Description

Defaults

HTTP server port: 80

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the copy http install EXEC command to install an image file from an HTTP server and install it on a WAAS device. It transfers the image from an HTTP server to the WAAS device using HTTP as the transport protocol and installs the software on the device. Part of the image goes to a disk and part goes to flash memory. Use the copy http central EXEC command to download a software image into the repository from an HTTP server.

You can also use the copy http install EXEC commands to redirect your transfer to a different location or HTTP proxy server by specifying the proxy hostname | ip-address option. A username and a password have to be authenticated with a primary domain controller (PDC) before the transfer of the software release file to the WAAS device is allowed.

Examples

The following example shows how to copy an image file from an HTTP server and install the file on the WAAS device:

WAE# copy http install 10.1.1.1 //ftp-sj.cisco.com/cisco/waas/4.0 WAAS-4.0.0-k9.bin

Enter username for remote ftp server:biff

Enter password for remote ftp server:*****

Initiating FTP download...

printing one # per 1MB downloaded

Sending:USER biff

10.1.1.1 FTP server (Version) Mon Feb 28 10:30:36 EST

2000) ready.

Password required for biff.

Sending:PASS ***** 

User biff logged in.

Sending:TYPE I

Type set to I.

Sending:PASV

Entering Passive Mode (128,107,193,244,55,156)

Sending:CWD //ftp-sj.cisco.com/cisco/waas/4.0

CWD command successful.

Sending PASV

Entering Passive Mode (128,107,193,244,55,156)

Sending:RETR WAAS-4.0.0-k9.bin

Opening BINARY mode data connection for ruby.bin (87376881 bytes).

###################################################################################

writing flash component:

.................................................................

The new software will run after you reload.

The following example shows how to upgrade the BIOS. All output is written to a separate file (/local1/.bios_upgrade.txt) for traceability. The hardware-dependent files that are downloaded from Cisco.com for the BIOS upgrade are automatically deleted from the WAAS device after the BIOS upgrade procedure has been completed.

WAE# copy ftp install upgradeserver /bios/update53/derived/ bios.bin

Enter username for remote ftp server:myusername

Enter password for remote ftp server:*****

Initiating FTP download...

 .

 .

 .

Related Commands

install

reload

show running-config

show startup-config

write

copy running-config

To copy a configuration or image data from the current configuration, use the copy running-config EXEC command.

copy running-config {disk filename | startup-config | tftp {hostname | ip-address} remotefilename}

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the copy running-config EXEC command to copy the running system configuration of the WAAS device to a SYSFS partition, flash memory, or TFTP server. The copy running-config startup-config EXEC command is equivalent to the write memory EXEC command.

Examples

The following example shows how to copy the current system configuration to startup configuration (NVRAM):

WAE# copy running-config startup-config

Related Commands

install

reload

show running-config

show startup-config

write

copy startup-config

To copy configuration or image data from the startup configuration, use the copy startup-config EXEC command.

copy startup-config {disk filename | running-config | tftp {hostname | ip-address} remotefilename}

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the copy startup-config EXEC command to copy the startup configuration file to a TFTP server or to a SYSFS partition.

Examples

The following example shows how to copy the startup configuration file to the running configuration:

WAE# copy startup-config running-config

Related Commands

install

reload

show running-config

show startup-config

write

copy sysreport

To copy system troubleshooting information from the device, use the copy sysreport EXEC command.

copy sysreport disk filename

copy sysreport ftp {hostname | ip-address} remotedirectory remotefilename

copy sysreport tftp {hostname | ip-address} remotefilename} [start-date {day month | month day} year [end-date {day month | month day} year]]

Syntax Description

Defaults

If end-date is not specified, today is used.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

The copy sysreport command consumes significant CPU and disk resources and can adversely affect system performance while it is running.

Examples

The following example shows how to copy system information to the file mysysinfo on the local WAAS device:

WAE# copy sysreport disk mysysinfo start-date 1 April 2006 end-date April 30 2006

The following example shows how to copy system information by FTP to the file foo in the root directory of the FTP server named myserver:

WAE# copy sysreport ftp myserver / foo start-date 1 April 2006 end-date April 30 2006

Related Commands

show running-config

show startup-config

copy system-status

To copy status information from the system for debugging, use the copy system-status EXEC command.

copy system-status disk filename

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the copy system-status EXEC command to create a file on a SYSFS partition that contains hardware and software status information.

Examples

The following example shows how to copy the system status to a disk file:

WAE# copy system-status disk file1

Related Commands

install

reload

show running-config

show startup-config

write

copy tech-support

To copy the configuration or image data from the system to use when working with Cisco TAC, use the copy tech-support EXEC command.

copy tech-support {disk filename | ftp {hostname | ip-address} remotedirectory remotefilename | tftp {hostname | ip-address} remotefilename}

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the copy tech-support tftp EXEC command to copy technical support information to a TFTP server or to a SYSFS partition.

Examples

The following example shows how to copy system information for tech support to a disk file:

WAE# copy tech-support disk file1

Related Commands

install

reload

show running-config

show startup-config

write

copy tftp

To copy configuration or image data from a TFTP server, use the copy tftp EXEC command.

copy tftp disk {hostname | ip-address} remotefilename localfilename

copy tftp running-config {hostname | ip-address} remotefilename

copy tftp startup-config {hostname | ip-address} remotefilename

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to copy configuration or image data from a TFTP server to the running configuration:

WAE# copy tftp running-config

Related Commands

install

reload

show running-config

show startup-config

write

copy usb

To copy files from an external USB drive, use the copy usb EXEC command.

copy usb { install | wow-recovery filename}

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Use the copy usb wow-recovery command to recover the Windows on WAAS system files of a virtual blade. This command allows you to recover Windows on your virtual blade while the WAAS software is running, without having to restart your WAE device.

This command is available only on platforms without a CD-ROM drive. For platforms with a CD-ROM drive, use the copy cdrom wow-recovery install EXEC command.

Examples

The following example shows how to recover Windows on a virtual blade from an external USB:

WAE# copy usb wow-recovery WoW_RECOVERY

Related Commands

copy cdrom wow-recovery

copy ftp

install

reload

show running-config

show startup-config

write

copy virtual-blade

To copy software configuration or image data from a virtual blade disk image to an FTP server, use the copy virtual-blade EXEC command.

copy virtual-blade vb_num disk vb_disk ftp {hostname | ip-address} remotefiledir remotefilename

Syntax Description

Defaults

No default behaviors or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to copy an image file from a virtual blade to an FTP server:

WAE# copy virtual-blade 1 disk 1 ftp 10.75.16.234 / file.img

Related Commands

copy ftp

install

reload

show running-config

show startup-config

write

cpfile

To make a copy of a file, use the cpfile EXEC command.

cpfile oldfilename newfilename

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Only SYSFS files can be copied.

Examples

The following example shows how to create a copy of a file:

WAE# cpfile fe512-194616.bin fd512-194618.bin

Related Commands

deltree

dir

lls

ls

mkdir

pwd

rename

crypto delete

To remove SSL certificate and key files, use the crypto delete EXEC command.

crypto delete {ca-certificate filename | pkcs12 {filename | admin }}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Usage Guidelines

Use the crypto delete EXEC command to remove a certificate from your WAE's secure store. If you only want to disassociate a certificate from an accelerated service, use no server-cert-key in crypto ssl services accelerated-service mode.

If you use the crypto delete pkcs12 admin command to delete a custom certificate and key that were installed for the Central Manager admin service, the admin service uses its built-in self-signed certificate.

Examples

The following example shows how to delete the CA certificate file mycert.ca:

WAE# crypto delete ca-certificate mycert.ca

Related Commands

crypto export

crypto generate

crypto import

crypto export

To export SSL certificate and key files, use the crypto export EXEC command.

crypto export {ca-certificate filename | pkcs12 {factory-self-signed | admin | filename} {pem-cert-key | pem-cert-only | pem-key-only | pkcs12}}{disk pathname | ftp address | sftp address | terminal | tftp address}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Examples

The following example shows how to export a CA certificate file named mycert.ca to an FTP server:

WAE# crypto export ca-certificate mycert.ca ftp 1.2.3.4 dir1 mycert.ca

The following example shows how to export the certificate and private key from a PKCS12 file named myfile.p12 to a PEM file on the local1 directory on the hard drive:

WAE# crypto export pkcs12 myfile.p12 pkcs12 disk /local1/myfile.p12

Related Commands

crypto delete

crypto generate

crypto import

crypto generate

To generate a self-signed certificate or a certificate signing request, use the crypt generate EXEC command.

crypto generate {csr rsa modulus {1024 | 1536 | 2048 | 512 | 768}{disk pathname | ftp address | sftp address | terminal | tftp address} | self-signed-cert filename [exportable] rsa modulus {1024 | 1536 | 2048 | 512 | 768}}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to create an exportable self-signed certificate. The certificate file is named myfile.p12 and is created using a 512-bit RSA modulus.

WAE# crypto generate self-signed-cert myfile.p12 exportable rsa modulus 512

Generating a 512 bit RSA private key

..........++++++++++++

...++++++++++++

-----

You are about to be asked to enter information that will be incorporated

into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [US]:US

State or Province Name (full name) [California]:<cr> (Press Enter to accept the default.)

Locality Name (eg, city) [San Jose]:San Jose

Organization Name (eg, company) [Cisco Systems]:

Organizational Unit Name (eg, section) [ADBU]:

Common Name (eg, YOUR name) [www.cisco.com]:

Email Address [tac@cisco.com]:

WAE#

Related Commands

crypto delete

crypto export

crypto import

crypto import

To import SSL certificates and key files, use the crypto import EXEC command.

crypto import {ca-certificate filename | pkcs12 { filename | admin} [exportable]}{pem-cert-key | pkcs12}}{disk pathname | ftp address | sftp address | terminal | tftp address}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Usage Guidelines

The Central Manager admin service uses a self-signed certificate and key by default. You can use the crypto import pkcs12 admin command to import a custom certificate and key in PKCS12 or PEM format. If you delete the custom certificate and key, the self-signed certificate and key again become active.

Note DSA certificates and keys cannot be imported.

Examples

The following example shows how to import a CA certificate file named mycert.ca from a TFTP server:

WAE# crypto import ca-certificate mycert.ca tftp 00.00.00.00

Related Commands

crypto delete

crypto export

crypto generate

crypto pki

To initialize the PKI managed store, use the crypto pki EXEC command.

crypto pki managed-store initialize

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Examples

The following example shows how to initialize the PKI managed store:

WAE# crypto pki managed-store initialize

Related Commands

crypto export

crypto generate

crypto import

debug aaa accounting

To monitor and record AAA accounting debugging, use the debug aaa accounting EXEC command. To disable debugging, use the undebug form of this command.

debug aaa accounting

undebug aaa accounting

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Because the performance of the WAAS device degrades when you use the debug command, we recommend that you use this command only at the direction of Cisco TAC. For more information, see the "Obtaining Documentation and Submitting a Service Request" section.

If the watchdog utility is not running, the message "WAAS is not running" appears.

Use the show debugging command to display enabled debug options.

The output associated with the debug command is written to either the syslog file in /local1/syslog.txt or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.

The debug log file associated with a module will be rotated to a backup file when the current file reaches its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file number.

For any debug command, system logging must be enabled. The command to enable logging is the logging disk enable global configuration command, which is enabled by default.

If a debug command module uses the syslog for debug output, then you must use the logging disk priority debug global configuration command (the default is logging disk priority notice).

If a debug command module uses the debug log for output, then the output can be filtered based on the priority level configuration for the four different levels of debug log output, as follows:

•For filtering on critical debug messages only, use the logging disk priority critical global configuration command.

•For filtering on critical and error level debug messages, use the logging disk priority error global configuration command.

•For filtering on critical, error, and trace debug level debug messages, use the logging disk priority debug global configuration command.

•For seeing all debug log messages, which include critical, error, trace and detail messages, use the logging disk priority detail global configuration command.

Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher priority will be automatically written to the debug log associated with a module.

We recommend that you use the debug and undebug commands only at the direction of Cisco Systems technical support personnel.

Examples

The following example shows how to enable AAA accounting debug monitoring:

WAE# debug aaa accounting

Related Commands

show debugging

debug aaa authorization

To monitor and record AAA authorization debugging, use the debug aaa authorization EXEC command. To disable debugging, use the undebug form of this command.

debug aaa authorization

undebug aaa authorization

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Because the performance of the WAAS device degrades when you use the debug command, we recommend that you use this command only at the direction of Cisco TAC. For more information, see the "Obtaining Documentation and Submitting a Service Request" section.

If the watchdog utility is not running, the message "WAAS is not running" appears.

Use the show debugging command to display enabled debug options.

The output associated with the debug command is written to either the syslog file in /local1/syslog.txt or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.

The debug log file associated with a module will be rotated to a backup file when the current file reaches its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file number.

For any debug command, system logging must be enabled. The command to enable logging is the logging disk enable global configuration command, which is enabled by default.

If a debug command module uses the syslog for debug output, then you must use the logging disk priority debug global configuration command (the default is logging disk priority notice).

If a debug command module uses the debug log for output, then the output can be filtered based on the priority level configuration for the four different levels of debug log output, as follows:

•For filtering on critical debug messages only, use the logging disk priority critical global configuration command.

•For filtering on critical and error level debug messages, use the logging disk priority error global configuration command.

•For filtering on critical, error, and trace debug level debug messages, use the logging disk priority debug global configuration command.

•For seeing all debug log messages, which include critical, error, trace and detail messages, use the logging disk priority detail global configuration command.

Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher priority will be automatically written to the debug log associated with a module.

We recommend that you use the debug and undebug commands only at the direction of Cisco Systems technical support personnel.

Examples

The following example shows how to enable AAA authorization debug monitoring:

WAE# debug aaa authorization

Related Commands

show debugging

debug accelerator

To monitor and record accelerator debugging, use the debug accelerator EXEC command. To disable debugging, use the undebug form of this command.

debug accelerator generic [connection | misc | shell | stats | all]

undebug accelerator generic [connection | misc | shell | stats | all]

debug accelerator http [bypass-list | cli | conditional-response | connection | dre-hints | metadatacache | redirect-response | shell | subnet | supress-server-encoding | transaction | unauthorized-response | all]

undebug accelerator http [bypass-list | cli | conditional-response | connection | dre-hints | metadatacache | redirect-response | shell | subnet | supress-server-encoding | transaction | unauthorized-response | all]

debug accelerator mapi [all | Common-flow | DCERPC-layer | EMSMDB-layer | IO | ROP-layer | ROP-parser | RCP-parser | shell | Transport | Utilities]

undebug accelerator mapi [all | Common-flow | DCERPC-layer | EMSMDB-layer | IO | ROP-layer | ROP-parser | RCP-parser | shell | Transport | Utilities]

debug accelerator nfs [async-write | attributes-cache | nfs-v3 | read-ahead | rpc | shell | utils | all]

undebug accelerator nfs [async-write | attributes-cache | nfs-v3 | read-ahead | rpc | shell | utils | all]

debug accelerator ssl [accelerated-svc | alarm | all | am | am-generic-svc | bio | ca | ca-pool | cipherlist | client-to-server | dataserver | flow-shutdown | generic | ocsp | oom-manager | openssl-internal | parser | peering-svc | session-cache | shell | sm-alert | sm-generic| sm-io | sm-pipethrough | synchronization | verify | waas-to-waas]

undebug accelerator ssl [accelerated-svc | alarm | all | am | am-generic-svc | bio | ca | ca-pool | cipherlist | client-to-server | dataserver | flow-shutdown | generic | ocsp | oom-manager | openssl-internal | parser | peering-svc | session-cache | shell | sm-alert | sm-generic| sm-io | sm-pipethrough | synchronization | verify | waas-to-waas]

debug accelerator video [all | gateway | shell | windows-media
[client-ip ip-addr | server-ip ip-addr]]

undebug accelerator video [all | gateway | shell | windows-media
[client-ip ip-addr | server-ip ip-addr]]

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Usage Guidelines

The output associated with the debug accelerator name module command for an application accelerator is written to the file nameao-errorlog.current, where name is the accelerator name. The accelerator information manager debug output is written to the file aoim-errorlog.current.

Because the performance of the WAAS device degrades when you use the debug command, we recommend that you use this command only at the direction of Cisco TAC. For more information, see the "Obtaining Documentation and Submitting a Service Request" section.

If the watchdog utility is not running, the message "WAAS is not running" appears.

Use the show debugging command to display enabled debug options.

The output associated with the debug command is written to either the syslog file in /local1/syslog.txt or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.

The debug log file associated with a module will be rotated to a backup file when the current file reaches its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file number.

For any debug command, system logging must be enabled. The command to enable logging is the logging disk enable global configuration command, which is enabled by default.

If a debug command module uses the syslog for debug output, then you must use the logging disk priority debug global configuration command (the default is logging disk priority notice).

If a debug command module uses the debug log for output, then the output can be filtered based on the priority level configuration for the four different levels of debug log output, as follows:

•For filtering on critical debug messages only, use the logging disk priority critical global configuration command.

•For filtering on critical and error level debug messages, use the logging disk priority error global configuration command.

•For filtering on critical, error, and trace debug level debug messages, use the logging disk priority debug global configuration command.

•For seeing all debug log messages, which include critical, error, trace and detail messages, use the logging disk priority detail global configuration command.

Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher priority will be automatically written to the debug log associated with a module.

We recommend that you use the debug and undebug commands only at the direction of Cisco Systems technical support personnel.

Examples

The following example shows how to enable all accelerator debug monitoring:

WAE# debug accelerator all

Related Commands

show debugging

debug all

To monitor and record all debugging, use the debug all EXEC command. To disable debugging, use the undebug form of this command.

debug all

undebug all

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Because the performance of the WAAS device degrades when you use the debug command, we recommend that you use this command only at the direction of Cisco TAC. For more information, see the "Obtaining Documentation and Submitting a Service Request" section.

If the watchdog utility is not running, the message "WAAS is not running" appears.

Use the show debugging command to display enabled debug options.

The output associated with the debug command is written to either the syslog file in /local1/syslog.txt or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.

The debug log file associated with a module will be rotated to a backup file when the current file reaches its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file number.

For any debug command, system logging must be enabled. The command to enable logging is the logging disk enable global configuration command, which is enabled by default.

If a debug command module uses the syslog for debug output, then you must use the logging disk priority debug global configuration command (the default is logging disk priority notice).

If a debug command module uses the debug log for output, then the output can be filtered based on the priority level configuration for the four different levels of debug log output, as follows:

•For filtering on critical debug messages only, use the logging disk priority critical global configuration command.

•For filtering on critical and error level debug messages, use the logging disk priority error global configuration command.

•For filtering on critical, error, and trace debug level debug messages, use the logging disk priority debug global configuration command.

•For seeing all debug log messages, which include critical, error, trace and detail messages, use the logging disk priority detail global configuration command.

Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher priority will be automatically written to the debug log associated with a module.

We recommend that you use the debug and undebug commands only at the direction of Cisco Systems technical support personnel.

Examples

The following example shows how to enable all debug monitoring:

WAE# debug all

Related Commands

show debugging

debug authentication

To monitor and record authentication debugging, use the debug authentication EXEC command. To disable debugging, use the undebug form of this command.

debug authentication {user | windows-domain}

undebug authentication {user | windows-domain}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Because the performance of the WAAS device degrades when you use the debug command, we recommend that you use this command only at the direction of Cisco TAC. For more information, see the "Obtaining Documentation and Submitting a Service Request" section.

If the watchdog utility is not running, the message "WAAS is not running" appears.

Use the show debugging command to display enabled debug options.

The output associated with the debug command is written to either the syslog file in /local1/syslog.txt or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.

The debug log file associated with a module will be rotated to a backup file when the current file reaches its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file number.

For any debug command, system logging must be enabled. The command to enable logging is the logging disk enable global configuration command, which is enabled by default.

If a debug command module uses the syslog for debug output, then you must use the logging disk priority debug global configuration command (the default is logging disk priority notice).

If a debug command module uses the debug log for output, then the output can be filtered based on the priority level configuration for the four different levels of debug log output, as follows:

•For filtering on critical debug messages only, use the logging disk priority critical global configuration command.

•For filtering on critical and error level debug messages, use the logging disk priority error global configuration command.

•For filtering on critical, error, and trace debug level debug messages, use the logging disk priority debug global configuration command.

•For seeing all debug log messages, which include critical, error, trace and detail messages, use the logging disk priority detail global configuration command.

Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher priority will be automatically written to the debug log associated with a module.

We recommend that you use the debug and undebug commands only at the direction of Cisco Systems technical support personnel.

Examples

The following example shows how to enable user authentication debug monitoring, verify that it is enabled, and then disable debug monitoring:

WAE# debug authentication user

WAE# show debugging

Debug authentication (user) is ON

WAE# no debug authentication user

Related Commands

show debugging

debug auto-discovery

To trace connections in the auto discovery module, use the debug auto-discovery EXEC command. To disable debugging, use the undebug form of this command.

debug auto-discoveryconnection

undebug auto-discovery connection

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

Usage Guidelines

Because the performance of the WAAS device degrades when you use the debug command, we recommend that you use this command only at the direction of Cisco TAC. For more information, see the "Obtaining Documentation and Submitting a Service Request" section.

If the watchdog utility is not running, the message "WAAS is not running" appears.

Use the show debugging command to display enabled debug options.

The output associated with the debug command is written to either the syslog file in /local1/syslog.txt or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.

The debug log file associated with a module will be rotated to a backup file when the current file reaches its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file number.

For any debug command, system logging must be enabled. The command to enable logging is the logging disk enable global configuration command, which is enabled by default.

If a debug command module uses the syslog for debug output, then you must use the logging disk priority debug global configuration command (the default is logging disk priority notice).

If a debug command module uses the debug log for output, then the output can be filtered based on the priority level configuration for the four different levels of debug log output, as follows:

•For filtering on critical debug messages only, use the logging disk priority critical global configuration command.

•For filtering on critical and error level debug messages, use the logging disk priority error global configuration command.

•For filtering on critical, error, and trace debug level debug messages, use the logging disk priority debug global configuration command.

•For seeing all debug log messages, which include critical, error, trace and detail messages, use the logging disk priority detail global configuration command.

Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher priority will be automatically written to the debug log associated with a module.

We recommend that you use the debug and undebug commands only at the direction of Cisco Systems technical support personnel.

Examples

The following example shows how to enable auto discovery connection debugging:

WAE# debug auto-discovery connection

Related Commands

show debugging

debug buf

To monitor and record buffer manager debugging, use the debug buf EXEC command. To disable debugging, use the undebug form of this command.

debug buf {all | dmbuf | dmsg}

undebug buf {all | dmbuf | dmsg}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Because the performance of the WAAS device degrades when you use the debug command, we recommend that you use this command only at the direction of Cisco TAC. For more information, see the "Obtaining Documentation and Submitting a Service Request" section.

If the watchdog utility is not running, the message "WAAS is not running" appears.

Use the show debugging command to display enabled debug options.

The output associated with the debug command is written to either the syslog file in /local1/syslog.txt or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.

The debug log file associated with a module will be rotated to a backup file when the current file reaches its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file number.

For any debug command, system logging must be enabled. The command to enable logging is the logging disk enable global configuration command, which is enabled by default.

If a debug command module uses the syslog for debug output, then you must use the logging disk priority debug global configuration command (the default is logging disk priority notice).

If a debug command module uses the debug log for output, then the output can be filtered based on the priority level configuration for the four different levels of debug log output, as follows:

•For filtering on critical debug messages only, use the logging disk priority critical global configuration command.

•For filtering on critical and error level debug messages, use the logging disk priority error global configuration command.

•For filtering on critical, error, and trace debug level debug messages, use the logging disk priority debug global configuration command.

•For seeing all debug log messages, which include critical, error, trace and detail messages, use the logging disk priority detail global configuration command.

Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher priority will be automatically written to the debug log associated with a module.

We recommend that you use the debug and undebug commands only at the direction of Cisco Systems technical support personnel.

Examples

The following example shows how to enable all buffer manager debug monitoring:

WAE# debug buff all

Related Commands

show debugging

debug cdp

To monitor and record CDP debugging, use the debug cdp EXEC command. To disable debugging, use the undebug form of this command.

debug cdp {adjacency | events | ip | packets}

undebug cdp {adjacency | events | ip | packets}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Because the performance of the WAAS device degrades when you use the debug command, we recommend that you use this command only at the direction of Cisco TAC. For more information, see the "Obtaining Documentation and Submitting a Service Request" section.

If the watchdog utility is not running, the message "WAAS is not running" appears.

Use the show debugging command to display enabled debug options.

The output associated with the debug command is written to either the syslog file in /local1/syslog.txt or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.

The debug log file associated with a module will be rotated to a backup file when the current file reaches its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file number.

For any debug command, system logging must be enabled. The command to enable logging is the logging disk enable global configuration command, which is enabled by default.

If a debug command module uses the syslog for debug output, then you must use the logging disk priority debug global configuration command (the default is logging disk priority notice).

If a debug command module uses the debug log for output, then the output can be filtered based on the priority level configuration for the four different levels of debug log output, as follows:

•For filtering on critical debug messages only, use the logging disk priority critical global configuration command.

•For filtering on critical and error level debug messages, use the logging disk priority error global configuration command.

•For filtering on critical, error, and trace debug level debug messages, use the logging disk priority debug global configuration command.

•For seeing all debug log messages, which include critical, error, trace and detail messages, use the logging disk priority detail global configuration command.

Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher priority will be automatically written to the debug log associated with a module.

We recommend that you use the debug and undebug commands only at the direction of Cisco Systems technical support personnel.

Examples

The following example shows how to enable CDP events debug monitoring:

WAE# debug cdp events

Related Commands

show debugging

debug cli

To monitor and record CLI debugging, use the debug cli EXEC command. To disable debugging, use the undebug form of this command.

debug cli {all | bin | parser}

undebug cli {all | bin | parser}

Syntax Description

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Because the performance of the WAAS device degrades when you use the debug command, we recommend that you use this command only at the direction of Cisco TAC. For more information, see the "Obtaining Documentation and Submitting a Service Request" section.

If the watchdog utility is not running, the message "WAAS is not running" appears.

Use the show debugging command to display enabled debug options.

The output associated with the debug command is written to either the syslog file in /local1/syslog.txt or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.

The debug log file associated with a module will be rotated to a backup file when the current file reaches its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file number.

For any debug command, system logging must be enabled. The command to enable logging is the logging disk enable global configuration command, which is enabled by default.

If a debug command module uses the syslog for debug output, then you must use the logging disk priority debug global configuration command (the default is logging disk priority notice).

If a debug command module uses the debug log for output, then the output can be filtered based on the priority level configuration for the four different levels of debug log output, as follows:

•For filtering on critical debug messages only, use the logging disk priority critical global configuration command.

•For filtering on critical and error level debug messages, use the logging disk priority error global configuration command.

•For filtering on critical, error, and trace debug level debug messages, use the logging disk priority debug global configuration command.

•For seeing all debug log messages, which include critical, error, trace and detail messages, use the logging disk priority detail global configuration command.

Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher priority will be automatically written to the debug log associated with a module.

We recommend that you use the debug and undebug commands only at the direction of Cisco Systems technical support personnel.

Examples

The following example shows how to enable all CLI debug monitoring:

WAE# debug cli all

Related Commands

show debugging

debug cms

To monitor and record CMS debugging, use the debug cms EXEC command. To disable debugging, use the undebug form of this command.

debug cms

undebug cms

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

EXEC

Device Modes

application-accelerator

central-manager

Usage Guidelines

Because the performance of the WAAS device degrades when you use the debug command, we recommend that you use this command only at the direction of Cisco TAC. For more information, see the "Obtaining Documentation and Submitting a Service Request" section.

If the watchdog utility is not running, the message "WAAS is not running" appears.

Use the show debugging command to display enabled debug options.

The output associated with the debug command is written to either the syslog file in /local1/syslog.txt or the debug log associated with the module in the file /local1/errorlog/module_name-errorlog.current.

The debug log file associated with a module will be rotated to a backup file when the current file reaches its maximum size. The backup files are named as follows: name-errorlog.#, where # is the backup file number.

For any debug command, system logging must be enabled. The command to enable logging is the logging disk enable global configuration command, which is enabled by default.

If a debug command module uses the syslog for debug output, then you must use the logging disk priority debug global configuration command (the default is logging disk priority notice).

If a debug command module uses the debug log for output, then the output can be filtered based on the priority level configuration for the four different levels of debug log output, as follows:

•For filtering on critical debug messages only, use the logging disk priority critical global configuration command.

•For filtering on critical and error level debug messages, use the logging disk priority error global configuration command.

•For filtering on critical, error, and trace debug level debug messages, use the logging disk priority debug global configuration command.

•For seeing all debug log messages, which include critical, error, trace and detail messages, use the logging disk priority detail global configuration command.

Regardless of the priority level configuration, any syslog messages at the LOG_ERROR or higher priority will be automatically written to the debug log associated with a module.

We recommend that you use the debug and undebug commands only at the direction of Cisco Systems technical support personnel.

Examples

The following example shows how to enable CMS debug monitoring:

WAE# debug cms

Related Commands

show debugging

debug connection