- Command Summary by Mode
- Preface
- Using the WAAS Command-Line Interface
- Cisco WAAS Software Command Summary
- CLI Commands
- EXEC Mode Commands
- Global Configuration Mode Commands
- Interface Configuration Mode Commands
- Standard ACL Configuration Mode Commands
- Extended ACL Configuration Mode Commands
- Preposition Configuration Mode Commands
- Virtual Blade Configuration Mode Commands
- PKI Certificate Authority Configuration Mode Commands
- PKI Global Settings Configuration Mode Commands
- SSL Accelerated Service Configuration Mode Commands
- SSL Cipher List Configuration Mode Commands
- SSL Global Service Configuration Mode Commands
- SSL Host Peering Service Configuration Mode Commands
- SSL Management Service Configuration Mode Commands
- Acronyms and Abbreviations
- cd
- cifs
- clear arp-cache
- clear cache
- clear cdp
- clear ip
- clear license
- clear logging
- clear statistics
- clear statistics accelerator
- clear statistics connection
- clear transaction-log
- clear users
- clear windows-domain-log
- clock
- cms
- cms secure-store
- configure
- copy cdrom
- copy cdrom wow-recovery
- copy compactflash
- copy disk
- copy ftp
- copy http
- copy running-config
- copy startup-config
- copy sysreport
- copy system-status
- copy tech-support
- copy tftp
- copy virtual-blade
- cpfile
- crypto delete
- crypto export
- crypto generate
- crypto import
- crypto pki
- debug aaa accounting
- debug accelerator
- debug all
- debug authentication
- debug buf
- debug cdp
- debug cli
- debug cms
- debug dataserver
- debug dhcp
- debug dre
- debug egress-method
- debug emdb
- debug epm
- debug flow
- debug generic-gre
- debug key-manager
- debug logging
- debug ntp
- debug print-spooler
- debug rbcp
- debug rpc
- debug snmp
- debug stats
- debug tfo
- debug translog
- debug wafs
- debug wccp
- delfile
- deltree
- dir
- disable
- disk
- dnslookup
- enable
- exit
- find-pattern
- help
- install
- less
- license add
- lls
- ls
- mkdir
- mkfile
- ntpdate
- ping
- pwd
- reload
- rename
- restore
- rmdir
- scp
- script
- setup
- show aaa accounting
- show accelerator
- show alarms
- show arp
- show authentication
- show auto-discovery
- show auto-register
- show banner
- show bypass
- show cdp
- show cifs
- show clock
- show cms
- show cms secure-store
- show crypto
- show debugging
- show device-mode
- show directed-mode
- show disks
- show egress-methods
- show filtering list
- show flash
- show hardware
- show hosts
- show inetd
- show interface
- show inventory
- show ip access-list
- show ip routes
- show kdump
- show kerberos
- show key-manager
- show license
- show logging
- show memory
- show ntp
- show policy-engine application
- show policy-engine status
- show print-services
- show processes
- show radius-server
- show running-config
- show services
- show smb-conf
- show snmp
- show ssh
- show startup-config
- show statistics accelerator
- show statistics aoim
- show statistics application
- show statistics authentication
- show statistics auto-discovery
- show statistics cifs
- show statistics connection
- show statistics connection auto-discovery
- show statistics connection closed
- show statistics connection conn-id
- show statistics connection egress-methods
- show statistics connection optimized
- show statistics connection pass-through
- show statistics crypto ssl ciphers
- show statistics datamover
- show statistics directed-mode
- show statistics dre
- show statistics filtering
- show statistics flow
- show statistics generic-gre
- show statistics icmp
- show statistics ip
- show statistics netstat
- show statistics pass-through
- show statistics peer
- show statistics radius
- show statistics services
- show statistics snmp
- show statistics synq
- show statistics tacacs
- show statistics tcp
- show statistics tfo
- show statistics udp
- show statistics wccp
- show statistics windows-domain
- show statistics windows-print requests
- show synq list
- show sysfs volumes
- show tacacs
- show tcp
- show tech-support
- show telnet
- show tfo tcp
- show transaction-logging
- show user
- show users administrative
- show version
- show virtual-blade
- show wccp
- show windows-domain
- shutdown
- snmp trigger
- ssh
- tcpdump
- telnet
- terminal
- test
- tethereal
- traceroute
- transaction-log
- type
- type-tail
- virtual-blade
- wafs
- whoami
- windows-domain
- write
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
directoryname |
Directory name. |
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
cifs
To control legacy CIFS adapter operations and run-time configurations, use the cifs EXEC command.
cifs auto-discovery {disable | enable | reset-log}
cifs mss value
cifs restart [core | edge]
cifs reverse-dns {active | disable | enable}
cifs session disconnect [client-ip ipaddress | server-ip ipaddress]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
Usage Guidelines
This command controls legacy mode CIFS. To control the transparent CIFS accelerator, use the (config) accelerator cifs command. These two modes are mutually exclusive. For more information on the two WAFS modes, see the chapter "Configuring Wide Area File Services" in the Cisco Wide Area Application Services Configuration Guide.
Use the cifs restart command to restart the WAFS services for a configuration change without having to reboot the WAE.
Examples
The following example shows how to set the TCP maximum segment size (MSS) value to 512 for the CIFS adapter:
WAE# cifs mss 512
Related Commands
clear arp-cache
To clear the ARP cache, use the clear arp-cache EXEC command.
clear arp-cache [ipaddress | interface {GigabitEthernet 1-2/port | PortChannel 1-2 | Standby 1}]
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 ARP cache on the WAAS device:
WAE# clear arp-cache
Related Commands
clear cache
To clear cached objects, use the clear cache EXEC command.
clear cache {cifs | dre}
Syntax Description
cifs |
Clears the CIFS cache. |
dre |
Clears the DRE cache. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
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.
Examples
The following example shows how to clear the CIFS cached objects on the WAAS device:
WAE# clear cache cifs
Related Commands
clear cdp
To clear Cisco Discovery Protocol statistics, use the clear cdp EXEC command.
clear cdp {counters | table}
Syntax Description
cdp |
Resets the Cisco Discovery Protocol (CDP) statistical data. |
counters |
Clears the CDP counters. |
table |
Clears the CDP tables. |
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
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
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
clear logging
To clear syslog messages saved in a disk file, use the clear logging EXEC command.
clear logging
Syntax Description
logging |
Clears the syslog messages saved in the disk file. |
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
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
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 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 transaction-log
To archive working transaction log file, use the clear transaction-log EXEC command.
clear transaction-log {flow}
Syntax Description
transaction-log |
Clears the transaction log. |
flow |
Clears the TFO transaction log. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
The following example shows how to archive the flow transaction log file on the WAAS device:
WAE# clear transaction-log flow
Related Commands
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.
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
(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
windows-domain-log |
Clears the Samba, Kerberos, and Winbind log files. |
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
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
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.
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.
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
cms secure-store
To configure secure store encryption, use the cms secure-store EXEC commands.
cms secure-store {init | open | change | clear | reset}
Syntax Description
Defaults
The standard encryption and key management is the default.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Secure store encryption provides stronger 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.
When you use the cms secure-store EXEC command to enable secure store on the Central Manager, or a WAE device, the WAAS system uses strong encryption algorithms and key management policies to protect certain data on the system. This data includes encryption keys used by applications in the WAAS system, CIFS passwords, and user login passwords.
When you enable secure store on Central Manager, the data is encrypted using a key encryption key generated from the pass phrase you enter 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 must enter a password to enable secure store. The 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
When you first initialize secure store encryption with the cms secure-store init command, this command also opens the secure store, so there is no need to use the cms secure-store open command. 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.
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 WAFS 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 the Central Manager and forget the secure store password, so you cannot open the secure store. This command deletes all encrypted data, certificate and key files, and key manager keys. The secure store is left in the uninitialized state. For the complete procedure for resetting the secure store, see the "Resetting Secure Store Encryption on a Central Manager" section on page 9-15 in the Cisco Wide Area Application Services Configuration Guide.
Examples
The following example shows how to initialize and activate secure store encryption on the WAAS Central Manager:
waas-cm# cms secure-store init
Stopping cms.
*******************************************************************
* 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 pass-phrase:
confirm pass-phrase:
Successfully migrated user passwords
Successfully migrated Cifs preposition password
Successfully migrated Cifs dynamic shares password
Successfully migrated key store
***** WARNING : REBOOTING CM REQUIRES RE-OPENING SECURE STORE MANUALLY. AFTER REBOOT, DISK ENCRYPTION AND CIFS PREPOSITION FEATURES ON REMOTE WAE(S) WILL NOT OPERATE
PROPERLY UNTIL USER RE-OPENS SECURE STORE ON CM BY INPUTTING THE PASSPHRASE *****
successfully initialized and opened secure-store.
Starting cms.
The following example shows how to deactivates secure store encryption:
waas-cm# cms secure-store clear
Secure store clear will result in deletion of CM pki store certificate/private key files
Do you want to continue(yes/no)?yes
Stopping cms.
Successfully migrated user passwords
Successfully migrated Cifs preposition password
Successfully migrated Cifs dynamic shares password
Successfully migrated key store
secure-store clear
Starting cms.
Related CommandsRelated Commands
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
copy cdrom
To copy software release files from a CD-ROM, use the copy cdrom EXEC command.
copy cdrom install filedir filename
Syntax Description
cdrom |
Copies a file from the CD-ROM. |
install filedir filename |
Installs the software release from the directory location and filename specified. |
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
copy cdrom wow-recovery
To recover Windows on a virtual blade without reloading the software, use the copy cdrom wow-recovery EXEC command.
copy cdrom wow-recover install 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 EXEC command to recover the Windows system files of a virtual blade. This command allows you to recover Windows on your virtual blade while the WAAS is running, without having to restart your WAE device.
Examples
The following example shows how to recover Windows on a virtual blade:
WAE# copy cdrom wow-recovery install
Related Commands
copy compactflash
To copy software release files from a CompactFlash card, use the copy compactflash EXEC command.
copy compactflash install filename
Syntax Description
compactflash |
Copies a file from the CompactFlash card. |
install filename |
Installs a software release from an image filename. |
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
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
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 {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.
Upgrading the BIOS
You can remotely upgrade the BIOS on the WAE-511, WAE-512, WAE-611, WAE-612, and the WAE-7326.
All BIOS files needed for a particular hardware model BIOS update are available on Cisco.com as a single .bin package file. This file is a special <WAAS-installable>.bin file that you can install by using the normal software update procedure.
To update the BIOS version on a WAAS device that supports BIOS version updates, you need the following items:
•FTP server with the software files
•Network connectivity between the device to be updated and the server hosting the update files
•Appropriate .bin BIOS update file:
–511_bios.bin
–611_bios.bin
–7326_bios.bin
To remotely install a BIOS update file, use the copy ftp install EXEC command as follows:
WAE# copy ftp install ftp-server remote_file_dir 7326_bios.bin
After the BIOS update file is copied to your system, use the reload EXEC command to reboot as follows:
WAE# reload
The new BIOS takes effect after the system reboots.
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-7326# copy ftp install upgradeserver /bios/update53/derived/ 7326_bios.bin
Enter username for remote ftp server:myusername
Enter password for remote ftp server:*****
Initiating FTP download...
printing one # per 1MB downloaded
Sending:USER myusername
upgradeserver.cisco.com FTP server (Version wu-2.6.1-18) ready.
Password required for myusername.
Sending:PASS ********
Please read the file README_dotfiles
it was last modified on Wed Feb 19 16:10:26 2005- 94 days ago
Please read the file README_first
it was last modified on Wed Feb 19 16:05:29 2005- 94 days ago
User myusername logged in.
Sending:TYPE I
Type set to I.
Sending:PASV
Entering Passive Mode (128,107,193,240,57,37)
Sending:CWD /bios/update53/derived/
CWD command successful.
Sending PASV
Entering Passive Mode (128,107,193,240,146,117)
Sending:RETR 7326_bios.bin
Opening BINARY mode data connection for 7326_bios.bin (834689 bytes).
Fri Jan 7 15:29:07 UTC 2005
BIOS installer running!
Do not turnoff the system till BIOS installation is complete.
Flash chipset:Macronix 29LV320B
0055000.FLS:280000 [80000]
Erasing block 2f:280000 - 28ffff
Erasing block 30:290000 - 29ffff
Erasing block 31:2a0000 - 2affff
Erasing block 32:2b0000 - 2bffff
Erasing block 33:2c0000 - 2cffff
Erasing block 34:2d0000 - 2dffff
Erasing block 35:2e0000 - 2effff
Erasing block 36:2f0000 - 2fffff
Programming block 2f:280000 - 28ffff
Programming block 30:290000 - 29ffff
Programming block 31:2a0000 - 2affff
Programming block 32:2b0000 - 2bffff
Programming block 33:2c0000 - 2cffff
Programming block 34:2d0000 - 2dffff
Programming block 35:2e0000 - 2effff
Programming block 36:2f0000 - 2fffff
SCSIROM.BIN:260000 [20000]
Erasing block 2d:260000 - 26ffff
Erasing block 2e:270000 - 27ffff
Programming block 2d:260000 - 26ffff
Programming block 2e:270000 - 27ffff
PXEROM.BIN:250000 [10000]
Erasing block 2c:250000 - 25ffff
Programming block 2c:250000 - 25ffff
Primary BIOS flashed successfully
Cleanup BIOS related files that were downloaded....
The new software will run after you reload.
WAE-7326#
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
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.
Upgrading the BIOS
You can remotely upgrade the BIOS on the WAE-511, WAE-512, WAE-611, WAE-612, and the WAE-7326. All computer hardware has to work with the software through an interface. The Basic Input Output System (BIOS) provides a computer a built-in starter kit to run the rest of the software from the hard disk drive. The BIOS is responsible for booting the computer by providing a basic set of instructions, performs all the tasks that need to be done at start-up time, such as Power-On Self Test (POST) operations and booting the operating system from the hard disk drive, and provides an interface between the hardware and the operating system in the form of a library of interrupt handlers.
Each time that a key is pressed, the CPU performs an interrupt to read that key, which is similar for other input/output devices, such as serial and parallel ports, video cards, sound cards, hard disk controllers, and so forth. Some older PCs cannot interoperate with all the modern hardware because their BIOS does not support that hardware; the operating system cannot call a BIOS routine to use it. You can solve this problem by replacing the BIOS with a newer one that does support your new hardware or by installing a device driver for the hardware.
All BIOS files needed for a particular hardware model BIOS update are available on Cisco.com as a single .bin package file. This file is a special <WAAS-installable>.bin file that you can install by using the normal software update procedure.
To update the BIOS version on a WAAS device that supports BIOS version updates, you need the following items:
•HTTP server with the software files
•Network connectivity between the device to be updated and the server hosting the update files
•Appropriate .bin BIOS update file:
–511_bios.bin
–611_bios.bin
–7326_bios.bin
To install the BIOS update file on a WAAS device, use the copy http install EXEC command as follows:
WAE# copy http install http-server remote_file_dir 7326_bios.bin [portnumber]
After the BIOS update file is copied to your system, use the reload EXEC command to reboot the WAAS device as follows:
WAE# reload
The new BIOS takes effect after the system reboots.
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-7326# copy ftp install upgradeserver /bios/update53/derived/ 7326_bios.bin
Enter username for remote ftp server:myusername
Enter password for remote ftp server:*****
Initiating FTP download...
printing one # per 1MB downloaded
Sending:USER myusername
upgradeserver.cisco.com FTP server (Version wu-2.6.1-18) ready.
Password required for myusername.
Sending:PASS ********
Please read the file README_dotfiles
it was last modified on Wed Feb 19 16:10:26 2005- 94 days ago
Please read the file README_first
it was last modified on Wed Feb 19 16:05:29 2005- 94 days ago
User myusername logged in.
Sending:TYPE I
Type set to I.
Sending:PASV
Entering Passive Mode (128,107,193,240,57,37)
Sending:CWD /bios/update53/derived/
CWD command successful.
Sending PASV
Entering Passive Mode (128,107,193,240,146,117)
Sending:RETR 7326_bios.bin
Opening BINARY mode data connection for 7326_bios.bin (834689 bytes).
Fri Jan 7 15:29:07 UTC 2005
BIOS installer running!
Do not turnoff the system till BIOS installation is complete.
Flash chipset:Macronix 29LV320B
0055000.FLS:280000 [80000]
Erasing block 2f:280000 - 28ffff
Erasing block 30:290000 - 29ffff
Erasing block 31:2a0000 - 2affff
Erasing block 32:2b0000 - 2bffff
Erasing block 33:2c0000 - 2cffff
Erasing block 34:2d0000 - 2dffff
Erasing block 35:2e0000 - 2effff
Erasing block 36:2f0000 - 2fffff
Programming block 2f:280000 - 28ffff
Programming block 30:290000 - 29ffff
Programming block 31:2a0000 - 2affff
Programming block 32:2b0000 - 2bffff
Programming block 33:2c0000 - 2cffff
Programming block 34:2d0000 - 2dffff
Programming block 35:2e0000 - 2effff
Programming block 36:2f0000 - 2fffff
SCSIROM.BIN:260000 [20000]
Erasing block 2d:260000 - 26ffff
Erasing block 2e:270000 - 27ffff
Programming block 2d:260000 - 26ffff
Programming block 2e:270000 - 27ffff
PXEROM.BIN:250000 [10000]
Erasing block 2c:250000 - 25ffff
Programming block 2c:250000 - 25ffff
Primary BIOS flashed successfully
Cleanup BIOS related files that were downloaded....
The new software will run after you reload.
Related Commands
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
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
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
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
system-status |
Copies the system status to a disk file. |
disk filename |
Name of the file to be created on the disk. |
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
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
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
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
cpfile
To make a copy of a file, use the cpfile EXEC command.
cpfile oldfilename newfilename
Syntax Description
oldfilename |
Name of the file to copy. |
newfilename |
Name of the copy to be created. |
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
crypto delete
To remove SSL certificate and key files, use the crypto delete EXEC command.
crypto delete {ca-certificate filename | pkcs12 filename}
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.
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
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
To export SSL certificate and key files, use the crypto export EXEC command.
crypto export {ca-certificate filename | pkcs12 {factory-self-signed | 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 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 import
To import SSL certificates and key files, use the crypto import EXEC command.
crypto import {ca-certificate filename | pkcs12 filename [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
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 pki
To initialize the PKI managed store, use the crypto pki EXEC command.
crypto pki managed-store initialize
Syntax Description
managed-store |
Specifies managed store commands. |
initialize |
Initializes the PKI managed store. |
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
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
aaa accounting |
(Optional) Enables AAA accounting actions. |
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 on page xix.
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
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 cifs [shell | all]
undebug accelerator cifs [shell | all]
debug accelerator generic [connection | misc | shell | stats | all]
undebug accelerator generic [connection | misc | shell | stats | all]
debug accelerator http [cli | connection | shell | all]
undebug accelerator http [cli | connection | shell | 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 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
central-manager
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 on page xix.
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
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
all |
Enables all debugging. |
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 on page xix.
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
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 {content-request | user | windows-domain}
undebug authentication {content-request | 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 on page xix.
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
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
buf |
(Optional) Enables buffer manager debugging. |
all |
Enables all buffer manager debugging. |
dmbuf |
Enables only dmbuf debugging. |
dmsg |
Enables only dmsg debugging. |
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 on page xix.
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
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 on page xix.
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
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
cli |
(Optional) Enables CLI debugging. |
all |
Enables all CLI debugging. |
bin |
Enables CLI command binary program debugging. |
parser |
Enables CLI command parser debugging. |
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 on page xix.
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
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
cms |
(Optional) Enables CMS debugging. |
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 on page xix.
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
debug dataserver
To monitor and record data server debugging, use the debug dataserver EXEC command. To disable debugging, use the undebug form of this command.
debug dataserver {all | clientlib | server}
undebug dataserver {all | clientlib | server}
Syntax Description
dataserver |
(Optional) Enables data server debugging. |
all |
Enables all data server debugging. |
clientlib |
Enables data server client library module debugging. |
server |
Enables data server module debugging. |
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 on page xix.
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 data server debug monitoring:
WAE# debug dataserver all
Related Commands
debug dhcp
To monitor and record DHCP debugging, use the debug dhcp EXEC command. To disable debugging, use the undebug form of this command.
debug dhcp
undebug dhcp
Syntax Description
dhcp |
(Optional) Enables DHCP debugging. |
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 on page xix.
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 DHCP debug monitoring:
WAE# debug dhcp
Related Commands
debug dre
To monitor and record DRE debugging, use the debug dre EXEC command. To disable debugging, use the undebug form of this command.
debug dre {aggregation | all | cache | connection {aggregation [acl] | cache [acl] | core [acl] | message [acl] | misc [acl] | acl} | core | lz | message | misc}
undebug dre {aggregation | all | cache | connection {aggregation [acl] | cache [acl] | core [acl] | message [acl] | misc [acl] | acl} | core | lz | message | misc}
Syntax Description
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 on page xix.
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 DRE debug monitoring:
WAE# debug dre all
Related Commands
debug egress-method
To monitor and record egress method debugging, use the debug egress-method EXEC command. To disable debugging, use the undebug form of this command.
debug egress-method connection
undebug egress-method connection
Syntax Description
eggress-method connection |
(Optional) Enables egress method connection debugging. |
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 on page xix.
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 egress method debug monitoring:
WAE# debug egress-method connection
Related Commands
debug emdb
To monitor and record embedded database debugging, use the debug emdb EXEC command. To disable debugging, use the undebug form of this command.
debug emdb [level [levelnum]]
undebug emdb [level [levelnum]]
Syntax Description
emdb |
(Optional) Enables embedded database debugging. |
level |
(Optional) Enables the specified debug level for EMDB service. |
levelnum |
(Optional) Debug level to disable. Level 0 disables debugging. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
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 on page xix.
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 embedded database debug monitoring:
WAE# debug emdb all
Related Commands
debug epm
To monitor and record DCE-RPC EPM debugging, use the debug epm EXEC command. To disable debugging, use the undebug form of this command.
debug epm
undebug epm
Syntax Description
epm |
(Optional) Enables DCE-RPC EPM debugging. |
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 on page xix.
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 EPM debug monitoring:
WAE# debug epm
Related Commands
debug flow
To monitor and record network traffic flow debugging, use the debug flow EXEC command. To disable debugging, use the undebug form of this command.
debug flow monitor tcpstat-v1
undebug flow monitor tcpstat-v1
Syntax Description
flow |
(Optional) Enables network traffic flow debugging. |
monitor |
Enables monitor flow performance debugging commands. |
tcpstat-v1 |
Enables tcpstat-v1 debugging. |
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 on page xix.
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 network traffic flow debug monitoring:
WAE# debug flow monitor tcpstat-v1
Related Commands
debug generic-gre
To monitor and record generic GRE egress method debugging, use the debug generic-gre EXEC command. To disable debugging, use the undebug form of this command.
debug generic-gre
undebug generic-gre
Syntax Description
generic-gre |
(Optional) Enables generic GRE egress method debugging. |
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 on page xix.
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 generic GRE egress method debug monitoring:
WAE# debug generic-gre
Related Commands
debug key-manager
To monitor and record Central Manager key manager debugging, use the debug key-manager EXEC command. To disable debugging, use the undebug form of this command.
debug key-manager
undebug key-manager
Syntax Description
key-manager |
(Optional) Enables the Central Manager key manager debugging. |
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 on page xix.
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 Central Manager key manager debug monitoring:
WAE# debug key-manager
Related Commands
debug logging
To monitor and record logging debugging, use the debug logging EXEC command. To disable debugging, use the undebug form of this command.
debug logging all
undebug logging all
Syntax Description
logging |
(Optional) Enables logging debugging. |
all |
Enables all logging debugging. |
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 on page xix.
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 logging debug monitoring:
WAE# debug logging all
Related Commands
debug ntp
To monitor and record NTP debugging, use the debug ntp EXEC command. To disable debugging, use the undebug form of this command.(
debug ntp
undebug ntp
Syntax Description
ntp |
(Optional) Enables NTP debugging. |
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 on page xix.
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 NTP debug monitoring:
WAE# debug ntp
Related Commands
debug print-spooler
To monitor and record print spooler debugging, use the debug print-spooler EXEC command. To disable debugging, use the undebug form of this command.
debug print-spooler {all | brief | errors | warnings}
undebug print-spooler {all | brief | errors | warnings}
Syntax Description
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 on page xix.
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 print spooler debug monitoring:
WAE# debug print-spooler all
Related Commands
debug rbcp
To monitor and record RBCP debugging, use the debug rbcp EXEC command. To disable debugging, use the undebug form of this command.
debug rbcp
undebug rbcp
Syntax Description
rbcp |
(Optional) Enables RBCP debugging. |
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 on page xix.
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 RBCP debug monitoring:
WAE# debug rbcp
Related Commands
debug rpc
To monitor and record remote procedure calls (RPC) debugging, use the debug rpc EXEC command. To disable debugging, use the undebug form of this command.
debug rpc
undebug rpc {detail | trace}
Syntax Description
rpc |
(Optional) Enables the remote procedure calls (RPC) debugging. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
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 on page xix.
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 RPC detail debug monitoring:
WAE# debug rpd detail
Related Commands
debug snmp
To monitor and record SNMP debugging , use the debug snmp EXEC command. To disable debugging, use the undebug form of this command.
debug snmp {all | cli | main | mib | traps}
undebug snmp {all | cli | main | mib | traps}
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 on page xix.
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 SNMP debug monitoring:
WAE# debug snmp all
Related Commands
debug stats
To monitor and record statistics debugging, use the debug stats EXEC command. To disable debugging, use the undebug form of this command.
debug stats {all | collections | computation | history}
undebug stats {all | collections | computation | history}
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 on page xix.
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 statistics debug monitoring:
WAE# debug stat all
Related Commands
debug tfo
To monitor and record TFO flow optimization debugging, use the debug tfo EXEC command. To disable debugging, use the undebug form of this command.
debug tfo {buffer-mgr | connection [auto-discovery | comp-mgr [acl] | conn-mgr [acl] | egress-method [acl] | filtering [acl] | netio-engine [acl] | policy-engine [acl] |
synq [acl] | acl] | stat-mgr | translog}
undebug tfo {buffer-mgr | connection [auto-discovery [acl] | comp-mgr [acl] | conn-mgr [acl] | egress-method [acl] | filtering [acl] | netio-engine [acl] | policy-engine [acl] | synq [acl] | acl] | stat-mgr | translog}
Syntax Description
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 on page xix.
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 TFO flow optimization debug monitoring:
WAE# debug tfo all
Related Commands
debug translog
To monitor and record transaction logging debugging, use the debug translog EXEC command. To disable debugging, use the undebug form of this command.
debug translog {detail | export | info}
undebug translog export
Syntax Description
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 on page xix.
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 transaction logging detail debug monitoring:
WAE# debug translog detail
Related Commands
debug wafs
To set the log level of WAFS running components, use the debug wafs EXEC command. To disable debugging, use the undebug form of this command.
debug wafs {{all | core-fe | edge-fe | manager | utilities} {debug | error | info | warn}}
undebug wafs {{all | core-fe | edge-fe | manager | utilities} {debug | error | info | warn}}
Syntax Description
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 on page xix.
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 set the log level for all WAFS components to error level:
WAE# debug wafs all error
Related Commands
debug wccp
To monitor and record WCCP information debugging, use the debug wccp EXEC command. To disable debugging, use the undebug form of this command.
debug wccp {all | detail | error | events | keepalive | packets | slowstart}
undebug wccp {all | detail | error | events | keepalive | packets | slowstart}
Syntax Description
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 on page xix.
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 WCCP information debug monitoring:
WAE# debug wccp all
Related Commands
delfile
To delete a file from the current directory, use the delfile EXEC command.
delfile filename
Syntax Description
filename |
Name of the file to delete. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the delfile EXEC command to remove a file from a SYSFS partition on the disk drive of the WAAS device.
Examples
The following example shows how to delete a temporary file from the /local1 directory using an absolute path:
WAE# delfile /local1/tempfile
Related Commands
deltree
To remove a directory with all of its subdirectories and files, use the deltree EXEC command.
deltree directory
Syntax Description
directory |
Name of the directory tree to delete. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the deltree EXEC command to remove a directory and all files within the directory from the WAAS SYSFS file system. No warning is given that you are removing the subdirectories and files.
Note Make sure that you do not remove files or directories required for the WAAS device to function properly.
Examples
The following example shows how to delete the testdir directory from the /local1 directory:
WAE# deltree /local1/testdir
Related Commands
dir
To view details of one file or all files in a directory, use the dir EXEC command.
dir [directory]
Syntax Description
directory |
(Optional) Name of the directory to list. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the dir EXEC command to view a detailed list of files contained within the working directory, including information about the file name, size, and time created. The lls EXEC command produces the same output.
Examples
The following example shows how to create a detailed list of all the files for the current directory:
WAE# dir
size time of last change name
------------- ------------------------- -----------
4096 Fri Feb 24 14:40:00 2006 <DIR> actona
4096 Tue Mar 28 14:42:44 2006 <DIR> core_dir
4096 Wed Apr 12 20:23:10 2006 <DIR> crash
4506 Tue Apr 11 13:52:45 2006 dbupgrade.log
4096 Tue Apr 4 22:50:11 2006 <DIR> downgrade
4096 Sun Apr 16 09:01:56 2006 <DIR> errorlog
4096 Wed Apr 12 20:23:41 2006 <DIR> logs
16384 Thu Feb 16 12:25:29 2006 <DIR> lost+found
4096 Wed Apr 12 03:26:02 2006 <DIR> sa
24576 Sun Apr 16 23:38:21 2006 <DIR> service_logs
4096 Thu Feb 16 12:26:09 2006 <DIR> spool
9945390 Sun Apr 16 23:38:20 2006 syslog.txt
10026298 Thu Apr 6 12:25:00 2006 syslog.txt.1
10013564 Thu Apr 6 12:25:00 2006 syslog.txt.2
10055850 Thu Apr 6 12:25:00 2006 syslog.txt.3
10049181 Thu Apr 6 12:25:00 2006 syslog.txt.4
4096 Thu Feb 16 12:29:30 2006 <DIR> var
508 Sat Feb 25 13:18:35 2006 wdd.sh.signed
The following example shows how to display the detailed information for only the logs directory:
WAE# dir logs
size time of last change name
------------- ------------------------- -----------
4096 Thu Apr 6 12:13:50 2006 <DIR> actona
4096 Mon Mar 6 14:14:41 2006 <DIR> apache
4096 Sun Apr 16 23:36:40 2006 <DIR> emdb
4096 Thu Feb 16 11:51:51 2006 <DIR> export
92 Wed Apr 12 20:23:20 2006 ftp_export.status
4096 Wed Apr 12 20:23:43 2006 <DIR> rpc_httpd
0 Wed Apr 12 20:23:41 2006 snmpd.log
4096 Sun Mar 19 18:47:29 2006 <DIR> tfo
Related Commands
disable
To turn off privileged EXEC commands, use the disable EXEC command.
disable
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
Use the WAAS software CLI EXEC mode for setting, viewing, and testing system operations. This command mode is divided into two access levels, user and privileged. To access privileged-level EXEC mode, enter the enable EXEC command at the user access level prompt and specify a privileged EXEC password (superuser or admin-equivalent password) when prompted for a password.
WAE> enable
Password:
The disable command places you in the user-level EXEC shell (notice the prompt change).
Examples
The following example shows how to enter the user-level EXEC mode from the privileged EXEC mode:
WAE# disable
WAE>
Related Commands
disk
To configure disks on a WAAS device, use the disk EXEC command.
disk delete-partitions diskname
disk delete-data-partitions
disk disk-name diskxx replace
disk insert diskname
disk recreate-raid
disk scan-errors diskname
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The WAAS software supports hot-swap functionality for both failed disk replacement and scheduled disk maintenance. On the WAE-612 and WAE-7326, use the disk disk-name diskxx shutdown global configuration command to shut down a disk for scheduled disk maintenance. On the WAE-7341 and WAE-7371, use the disk disk-name diskxx replace EXEC command to shut down a disk. (For the scheduled disk maintenance procedure, see the Cisco Wide Area Application Services Configuration Guide, Chapter 14.)
The disk hot-swap functionality automatically disables a failed disk if the system detects one critical disk alarm. The software removes the failed disk automatically regardless of the setting for disk error-handling.
For WAE-7341 and WAE-7371 models, when you replace a failed disk that was automatically disabled by the software, the disk automatically returns to service. For WAE-612 and WAE-7326 models, when you replace a failed disk that was automatically disabled by the software, use the disk insert EXEC command to bring the disk back into service. For all other models, see the (config) disk disk-name command section.
To identify which disks have been identified as failed or bad, use the show disks failed-disk-id EXEC command. Do not reinsert any disk with a serial number shown in this list.
Note The show disks failed-disk-id command is not available on WAE-7341 and WAE-7371 models.
Use the disk delete-partitions EXEC command to remove all disk partitions on a single disk drive on a WAAS device or to remove the disk partition on the logical drive for RAID-5 systems.
Note When you use the disk delete-partitions EXEC command on the WAE-7341 or WAE-7371 models, the command deletes the entire logical volume. The individual disk name option is not available on these platforms.
Examples
The following example shows how to recreate the RAID-5 array:
WAE# disk recreate-raid
Related Commands
(config) disk logical shutdown
dnslookup
To resolve a host or domain name to an IP address, use the dnslookup EXEC command.
dnslookup {hostname | domainname}
Syntax Description
hostname |
Name of DNS server on the network. |
domainname |
Name of domain. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
The following examples show how the dnslookup command is used to resolve the hostname myhost to IP address 172.31.69.11, abd.com to IP address 192.168.219.25, and an IP address used as a hostname to 10.0.11.0:
WAE# dnslookup myhost
official hostname: myhost.abc.com
address: 172.31.69.11
WAE# dnslookup abc.com
official hostname: abc.com
address: 192.168.219.25
WAE# dnslookup 10.0.11.0
official hostname: 10.0.11.0
address: 10.0.11.0
Related Commands
enable
To access privileged EXEC commands, use the enable EXEC command.
enable
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
Use the WAAS software CLI EXEC mode for setting, viewing, and testing system operations. This command mode is divided into two access levels: user and privileged. To access privileged-level EXEC mode, enter the enable EXEC command at the user access level prompt and specify a privileged EXEC password (superuser or admin-equivalent password) when prompted for a password.
If using TACACS+ authentication, there is an enable password feature in TACACS+ that allows an administrator to define a different enable password for each administrative-level user. If an administrative-level user logs in to the WAAS device with a normal-level user account (privilege level of 0) instead of an admin or admin-equivalent user account (privilege level of 15), that user must enter the admin password to access privileged-level EXEC mode:
WAE> enable
Password:
The above behavior occurs even if the WAAS users are using TACACS+ for login authentication.The disable command takes you from privileged EXEC mode to user EXEC mode.
Examples
The following example shows how to access privileged EXEC mode:
WAE> enable
WAE#
Related Commands
exit
To terminate privileged-level EXEC mode and return to the user-level EXEC mode, use the exit command.
exit
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
All modes
Device Modes
application-accelerator
central-manager
Usage Guidelines
The exit EXEC command is equivalent to pressing Ctrl-Z or entering the end command. Entering the exit command in the user level EXEC shell terminates the console or Telnet session.
Examples
The following example shows how to terminate privileged-level EXEC mode and return to the user-level EXEC mode:
WAE# exit
WAE>
Related Commands
(config) exit
find-pattern
To search for a particular pattern in a file, use the find-pattern command in EXEC mode.
find-pattern {binary reg-express filename | count reg-express filename | lineno reg-express filename | match reg-express filename | nomatch reg-express filename | recursive reg-express filename}
find-pattern case {binary reg-express filename | count reg-express filename | lineno reg-express filename | match reg-express filename | nomatch reg-express filename | recursive reg-express 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 search a file recursively for a case-sensitive pattern:
WAE# find-pattern case recursive admin removed_core
-rw------- 1 admin root 95600640 Oct 12 10:27 /local/local1/core_dir/
core.3.0.0.b5.eh.2796
-rw------- 1 admin root 97054720 Jan 11 11:31 /local/local1/core_dir/
core.cache.3.0.0.b131.cnbuild.14086
-rw------- 1 admin root 96845824 Jan 11 11:32 /local/local1/core_dir/
core.cache.3.0.0.b131.cnbuild.14823
-rw------- 1 admin root 101580800 Jan 11 12:01 /local/local1/core_dir/
core.cache.3.0.0.b131.cnbuild.15134
-rw------- 1 admin root 96759808 Jan 11 12:59 /local/local1/core_dir/
core.cache.3.0.0.b131.cnbuild.20016
-rw------- 1 admin root 97124352 Jan 11 13:26 /local/local1/core_dir/
core.cache.3.0.0.b131.cnbuild.8095
The following example shows how to search a file for a pattern and print the matching lines:
WAE# find-pattern match 10 removed_core
Tue Oct 12 10:30:03 UTC 2004
-rw------- 1 admin root 95600640 Oct 12 10:27 /local/local1/core_dir/
core.3.0.0.b5.eh.2796
-rw------- 1 admin root 101580800 Jan 11 12:01 /local/local1/core_dir/
core.cache.3.0.0.b131.cnbuild.15134
The following example shows how to search a file for a pattern and print the number of matching lines:
WAE# find-pattern count 10 removed_core
3
Related Commands
help
To obtain online help for the command-line interface, use the help EXEC command.
help
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC and global configuration
Device Modes
application-accelerator
central-manager
Usage Guidelines
You can obtain help at any point in a command by entering a question mark (?). If nothing matches, the help list will be empty, and you must back up until entering a ? shows the available options.
Two styles of help are provided:
•Full help is available when you are ready to enter a command argument (for example, show ?) and describes each possible argument.
•Partial help is provided when you enter an abbreviated command and you want to know what arguments match the input (for example, show stat?).
Examples
The following example shows how to display the output of the help EXEC command:
WAE# help
Help may be requested at any point in a command by entering a question mark '?'. If nothing matches, the help list will be empty and you must backup until entering a '?' shows the available options.
Two styles of help are provided:
1. Full help is available when you are ready to enter a command argument.
2. Partial help is provided when an abbreviated argument is entered.
Related Commands
(config) help
install
To install a new software image (such as the WAAS software) into flash on the WAAS device, use the install EXEC command.
install imagefilename
Syntax Description
imagefilename |
Name of the .bin file you want to install. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The install command loads the system image into flash memory and copies components of the optional software to the software file system (swfs) partition.
Note If you are installing a system image that contains optional software, make sure that an SWFS partition is mounted on disk00.
To install a system image, copy the image file to the SYSFS directory local1. Before executing the install command, change the present working directory to the directory where the system image resides. When the install command is executed, the image file is expanded. The expanded files overwrite the existing files on the WAAS device. The newly installed version takes effect after the system image is reloaded.
Note The install command does not accept .pax files. Files should be of the type .bin (for example, cache-sw.bin). Also, if the release being installed does not require a new system image, then it may not be necessary to write to flash memory. If the newer version has changes that require a new system image to be installed, then the install command may result in a write to flash memory.
Close your browser and restart the browser session to the WAAS Central Manager, if you installed a new software image to the primary WAAS Central Manager.
Examples
The following example shows how to load the system image contained in the wae512-cache-300.bin file:
WAE# install wae512-cache-300.bin
Related Commands
less
To display a file using the Less application, use the less EXEC command.
less file_name
Syntax Description
file_name |
Name of the file to be displayed. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Less is a pager application that displays text files one page at a time. You can use Less to view the contents of a file, but not edit it. Less offers some additional features when compared to conventional text file viewer applications such as Type. These features include the following:
•Backward movement—Allows you to move backward in the displayed text. Use k, Ctrl-k, y, or Ctrl-y to move backward. See the summary of Less commands for more details; to view the summary, press h or H while displaying a file in Less.
•Searching and highlighting—Allows you to search for text in the file that you are viewing. You can search forward and backward. Less highlights the text that matches your search to make it easy to see where the match is.
•Multiple file support—Allows you to switch between different files, remembering your position in each file. You can also do a search that spans all the files you are working with.
Examples
The following example shows how to display the text of the syslog.txt file using the Less application:
WAE# less syslog.txt
Related Commands
type
license add
To add a software license to a device, use the license add EXEC command.
license add 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 install the enterprise license:
WAE# license add Enterprise
Related Commands
clear arp-cache license
lls
To view a long list of directory names, use the lls EXEC command.
lls [directory]
Syntax Description
directory |
(Optional) Name of the directory for which you want a long list of files. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The lls command provides detailed information about files and subdirectories stored in the present working directory (including the size, date, time of creation, SYSFS name, and long name of the file). This information can also be viewed with the dir command.
Examples
The following example shows how to display a detailed list of the files in the current directory:
WAE# lls
size time of last change name
-------------- ------------------------- -----------
4096 Fri Feb 24 14:40:00 2006 <DIR> actona
4096 Tue Mar 28 14:42:44 2006 <DIR> core_dir
4096 Wed Apr 12 20:23:10 2006 <DIR> crash
4506 Tue Apr 11 13:52:45 2006 dbupgrade.log
4096 Tue Apr 4 22:50:11 2006 <DIR> downgrade
4096 Sun Apr 16 09:01:56 2006 <DIR> errorlog
4096 Wed Apr 12 20:23:41 2006 <DIR> logs
16384 Thu Feb 16 12:25:29 2006 <DIR> lost+found
4096 Wed Apr 12 03:26:02 2006 <DIR> sa
24576 Sun Apr 16 23:54:30 2006 <DIR> service_logs
4096 Thu Feb 16 12:26:09 2006 <DIR> spool
9951236 Sun Apr 16 23:54:20 2006 syslog.txt
10026298 Thu Apr 6 12:25:00 2006 syslog.txt.1
10013564 Thu Apr 6 12:25:00 2006 syslog.txt.2
10055850 Thu Apr 6 12:25:00 2006 syslog.txt.3
10049181 Thu Apr 6 12:25:00 2006 syslog.txt.4
4096 Thu Feb 16 12:29:30 2006 <DIR> var
508 Sat Feb 25 13:18:35 2006 wdd.sh.signed
Related Commands
ls
To view a list of files or subdirectory names within a directory, use the ls EXEC command.
ls [directory]
Syntax Description
directory |
(Optional) Name of the directory for which you want a list of files. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the ls directory command to list the filenames and subdirectories within a particular directory.
Use the ls command to list the filenames and subdirectories of the current working directory.
Use the pwd command to view the present working directory.
Examples
The following example shows how to display the files and subdirectories that are listed within the root directory:
WAE# ls
actona
core_dir
crash
dbupgrade.log
downgrade
errorlog
logs
lost+found
sa
service_logs
spool
syslog.txt
syslog.txt.1
syslog.txt.2
syslog.txt.3
var
wdd.sh.signed
Related Commands
mkdir
To create a directory, use the mkdir EXEC command.
mkdir directory
Syntax Description
directory |
Name of the directory to create. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
The following example shows how to create a new directory, oldpaxfiles:
WAE# mkdir /oldpaxfiles
Related Commands
mkfile
To create a new file, use the mkfile EXEC command.
mkfile filename
Syntax Description
filename |
Name of the file that you want to create. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the mkfile EXEC command to create a new file in any directory of the WAAS device.
Examples
The following example shows how to create a new file, traceinfo, in the root directory:
WAE# mkfile traceinfo
Related Commands
ntpdate
To set the software clock (time and date) on a WAAS device using an NTP server, use the ntpdate EXEC command.
ntpdate {hostname | ip-address} [key {authentication-key}]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the ntpdate command to find the current time of day and set the current time on the WAAS device to match. You must save the time to the hardware clock using the clock save command if you want to restore the time after a reload.
Examples
The following example shows how to set the software clock on the WAAS device using a NTP server:
WAE# ntpdate 10.11.23.40
Related Commands
ping
To send echo packets for diagnosing basic network connectivity on networks, use the ping EXEC command.
ping {hostname | ip-address}
Syntax Description
hostname |
Hostname of system to ping. |
ip-address |
IP address of system to ping. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
To use the ping command with the hostname argument, make sure that DNS functionality is configured on the WAAS device. To force the timeout of a nonresponsive host, or to eliminate a loop cycle, press Ctrl-C.
Examples
The following example shows how to send echo packets to a machine with address 172.19.131.189 to verify its availability on the network:
WAE# ping 172.19.131.189
PING 172.19.131.189 (172.19.131.189) from 10.1.1.21 : 56(84) bytes of
data.
64 bytes from 172.19.131.189: icmp_seq=0 ttl=249 time=613 usec
64 bytes from 172.19.131.189: icmp_seq=1 ttl=249 time=485 usec
64 bytes from 172.19.131.189: icmp_seq=2 ttl=249 time=494 usec
64 bytes from 172.19.131.189: icmp_seq=3 ttl=249 time=510 usec
64 bytes from 172.19.131.189: icmp_seq=4 ttl=249 time=493 usec
--- 172.19.131.189 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.485/0.519/0.613/0.047 ms
WAE#
pwd
To view the present working directory on a WAAS device, use the pwd EXEC command.
pwd
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 display the current working directory:
WAE# pwd
/local1
Related Commands
reload
To halt the operation and perform a cold restart on a WAAS device, use the reload EXEC command.
reload [force | in m | cancel]
Syntax Description
force |
(Optional) Forces a reboot without further prompting. |
in m |
(Optional) Schedules a reboot after a specified interval (1-10080 minutes). |
cancel |
(Optional) Cancels a scheduled reboot. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
To reboot a WAAS device, use the reload command. If no configurations are saved to flash memory, you are prompted to enter configuration parameters upon a restart. Any open connections are dropped after you enter the reload command, and the file system is reformatted upon restart.
The reload command can include the option to schedule a reload of the software to take effect in a specified number of minutes. After entering this command, you are asked to confirm the reload by typing y and then confirm WCCP shutdown by typing y again (if WCCP is active).
You can use the cancel option to cancel a scheduled reload.
Examples
The following example shows how to halt the operation of the WAAS device and reboot with the configuration saved in flash memory. You are not prompted for confirmations during the process.
WAE# reload force
Related Commands
rename
To rename a file on a WAAS device, use the rename EXEC command.
rename oldfilename newfilename
Syntax Description
oldfilename |
Original filename. |
newfilename |
New filename. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the rename command to rename any SYSFS file without making a copy of the file.
Examples
The following example shows how to rename the errlog.txt file to old_errlog.txt:
WAE# rename errlog.txt old_errlog.txt
Related Commands
restore
To restore the device to its manufactured default status by removing the user data from the disk and flash memory, use the restore EXEC command.
restore {factory-default [preserve basic-config] | rollback}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the restore EXEC command to restore data on a disk and in flash memory to the factory default, while preserving particular time-stamp evaluation data, or to roll back the configuration to the last functional data and device configuration.
This command erases all existing content on the device; however, your network settings are preserved and the device is accessible through a Telnet and Secure Shell (SSH) session after it reboots.
Backing up the Central Manager Database
Before you use the restore factory-default command on your primary WAAS Central Manager or change over from the primary to a standby WAAS Central Manager, make sure that you back up the WAAS Central Manager database and copy the backup file to a safe location that is separate from the WAAS Central Manager. You must halt the operation of the WAAS Central Manager before you enter the backup and restore commands.
By removing the WAAS Central Manager database, all configuration records for the entire WAAS network are deleted. If you do not have a valid backup file or a standby WAAS Central Manager, you must reregister every WAE with the WAAS Central Manager because all previously configured data is lost.
If you used your standby WAAS Central Manager to store the database while you reconfigured the primary, you can register the former primary as a new standby WAAS Central Manager.
If you created a backup file while you configured the primary WAAS Central Manager, you can copy the backup file to this newly reconfigured WAAS Central Manager.
Rolling Back the Configuration
You can roll back the software and configuration of a WAAS device to a previous version using the restore rollback command. You would roll back the software only in cases in which a newly installed version of the WAAS software is not functioning properly.
The restore rollback command installs the last saved WAAS.bin image on the system disk. A WAAS.bin image is created during software installation and stored on the system disk. If the WAAS device does not have a saved version, the software is not rolled back.
Note WAFS to WAAS migration is supported. Rollback from WAAS to WAFS is not supported.
Examples
The following examples show how to use the restore factory-default and restore factory-default preserve basic-config commands. Because configuration parameters and data are lost, prompts are given before initiating the restore operation to ensure that you want to proceed.
WAE# restore factory-default
This command will wipe out all of data on the disks
and wipe out WAAS CLI configurations you have ever made.
If the box is in evaluation period of certain product,
the evaluation process will not be affected though.
It is highly recommended that you stop all active services
before this command is run.
Are you sure you want to go ahead?[yes/no]
WAE# restore factory-default preserve basic-config
This command will wipe out all of data on the disks
and all of WAAS CLI configurations except basic network
configurations for keeping the device online.
The to-be-preserved configurations are network interfaces,
default gateway, domain name, name server and hostname.
If the box is in evaluation period of certain product,
the evaluation process will not be affected.
It is highly recommended that you stop all active services
before this command is run.
Are you sure you want to go ahead?[yes/no]
Note You can enter basic configuration parameters (such as the IP address, hostname, and name server) at this point, or you can enter these parameters later through entries in the command-line interface.
The following example shows how to verify that the restore command has removed data from the SYSFS, WAAS, and PRINTSPOOLFS partitioned file systems:
WAE# show disks details
Physical disk information:
disk00: Normal (h00 c00 i00 l00 - DAS) 140011MB(136.7GB)
disk01: Normal (h00 c00 i01 l00 - DAS) 140011MB(136.7GB)
Mounted filesystems:
MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%
/ root /dev/root 35MB 30MB 5MB 85%
/swstore internal /dev/md1 991MB 333MB 658MB 33%
/state internal /dev/md2 3967MB 83MB 3884MB 2%
/disk00-04 CONTENT /dev/md4 122764MB 33MB 122731MB 0%
/local/local1 SYSFS /dev/md5 3967MB 271MB 3696MB 6%
.../local1/spool PRINTSPOOL /dev/md6 991MB 16MB 975MB 1%
/sw internal /dev/md0 991MB 424MB 567MB 42%
Software RAID devices:
DEVICE NAME TYPE STATUS PHYSICAL DEVICES AND STATUS
/dev/md0 RAID-1 NORMAL OPERATION disk00/00[GOOD] disk01/00[GOOD]
/dev/md1 RAID-1 NORMAL OPERATION disk00/01[GOOD] disk01/01[GOOD]
/dev/md2 RAID-1 NORMAL OPERATION disk00/02[GOOD] disk01/02[GOOD]
/dev/md3 RAID-1 NORMAL OPERATION disk00/03[GOOD] disk01/03[GOOD]
/dev/md4 RAID-1 NORMAL OPERATION disk00/04[GOOD] disk01/04[GOOD]
/dev/md5 RAID-1 NORMAL OPERATION disk00/05[GOOD] disk01/05[GOOD]
/dev/md6 RAID-1 NORMAL OPERATION disk00/06[GOOD] disk01/06[GOOD]
Currently content-filesystems RAID level is not configured to change.
The following example shows how to upgrade or restore an older version of the WAAS software. In the example, version Y of the software is installed (using the copy command), but the administrator has not switched over to it yet, so the current version is still version X. The system is then reloaded (using the reload command), and it verifies that version Y is the current version running.
The following example shows how to roll back the software to version X (using the restore rollback command), and reload the software:
WAE# copy ftp install server path waas.versionY.bin
WAE# show version
Cisco Wide Area Application Services Software (WAAS)
Copyright (c) 1999-2006 by Cisco Systems, Inc.
Cisco Wide Area Application Services Software Release 4.0.0 (build b340 Mar 25 2
006)
Version: fe611-4.0.0.340
Compiled 17:26:17 Mar 25 2006 by cnbuild
System was restarted on Mon Mar 27 15:25:02 2006.
The system has been up for 3 days, 21 hours, 9 minutes, 17 seconds.
WAE# show version last
Nothing is displayed.
WAE# show version pending
WAAS 4.0.1 Version Y
WAE# reload
...... reloading ......
WAE# show version
Cisco Wide Area Application Services Software (WAAS)
...
WAE# restore rollback
WAE# reload
...... reloading ......
Because flash memory configurations were removed after the restore command was used, the show startup-config command does not return any flash memory data. The show running-config command returns the default running configurations.
Related Commands
rmdir
To delete a directory on a WAAS device, use the rmdir EXEC command.
rmdir directory
Syntax Description
directory |
Name of the directory that you want to delete. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the rmdir EXEC command to remove any directory from the WAAS file system. The rmdir command only removes empty directories.
Examples
The following example shows how to delete the oldfiles directory from the local1 directory:
WAE# rmdir /local1/oldfiles
Related Commands
scp
To copy files between network hosts, use the scp command.
scp [4][6][B][C][p][q][r][v] [c cipher] [F config-file] [i id-file] [o ssh_option] [P port] [S program]
[[user @] host : file] [...] [[user-n @] host-n : file-n]
Syntax Description
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The scp command uses SSH for transferring data between hosts.
This command prompts you for passwords or pass phrases when needed for authentication.
Related Commands
script
To execute a script provided by Cisco or check the script for errors, use the script EXEC command.
script {check | execute} file_name
Syntax Description
check |
Checks the validity of the script. |
execute |
Executes the script. The script file must be a SYSFS file in the current directory. |
file_name |
Name of the script file. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The script EXEC command opens the script utility, which allows you to execute Cisco-supplied scripts or check errors in those scripts. The script utility can read standard terminal input from the user if the script you run requires input from the user.
Note The script utility is designed to run only Cisco-supplied scripts. You cannot execute script files that lack Cisco signatures or that have been corrupted or modified.
Examples
The following example shows how to check for errors in the script file test_script.pl:
WAE# script check test_script.pl
setup
To configure basic configuration settings (general settings, device network settings, interception type, disk configuration, and licenses) on the WAAS device or to complete basic configuration after upgrading to the WAAS software, use the setup EXEC command.
setup
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
For instructions on using the setup command, see the Cisco Wide Area Application Services Quick Configuration Guide.
Examples
The following example shows how to access the first screen of the wizard when you enter the setup EXEC command on a WAAS device that is running the WAAS software:
WAE# setup
Step 1: The following defaults can be configured:
Device mode: Application-accelerator
Interception Method: Inline
Management Interface: InlineGroup 1/1
Autosense: yes
Timezone: UTC 0 0
To keep above defaults and continue configuration, press 'y'.
To change above defaults and continue configuration, press 'n' [y]:
show aaa accounting
To display the AAA accounting configuration information for a WAAS device, use the show aaa accounting EXEC command.
show aaa accounting
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the show aaa accounting EXEC command to display configuration information for the following AAA accounting types:
•Exec shell
•Command (for normal users and superusers)
•System
Examples
Table 3-1 describes the fields shown in the show aaa accounting command display.
Related Commands
show accelerator
To display the status and configuration of the application accelerators, use the show accelerator EXEC command.
show accelerator [{cifs | detail | epm | http | mapi | nfs | ssl | video}]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
Examples
Table 3-2 describes the fields shown in the show accelerator command display for all application accelerators. Specific application accelerators display additional configuration status information.
Related Commands
show alarms
To display information about various types of alarms, their status, and history on a WAAS device, use the show alarms EXEC command.
show alarms critical [detail [support]]
show alarms detail [support]
show alarms history [start_num [end_num [detail [support]]]] | critical [start_num [end_num [detail [support]]]]
show alarms major [start_num [end_num [detail [support]]]]
show alarms minor [start_num [end_num [detail [support]]]]
show alarms status
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The Node Health Manager in the WAAS software enables WAAS applications to raise alarms to draw attention in error/significant conditions. The Node Health Manager, which is the data repository for such alarms, aggregates the health and alarm information for the applications, services, and resources (for example, disk drives) that are being monitored on the WAAS device. For example, this feature gives you a mechanism to determine if a WAE is receiving overwhelming number of alarms. These alarms are referred to as WAAS software alarms.
The WAAS software uses SNMP to report error conditions by generating SNMP traps. The following WAAS applications can generate a WAAS software alarm:
•Node Health Manager (alarm overload condition)
•System Monitor (sysmon) for disk failures
The three levels of alarms in the WAAS software are as follows:
•Critical—Alarms that affect the existing traffic through the WAE and are considered fatal (the WAE cannot recover and continue to process traffic).
•Major—Alarms that indicate a major service (for example, the cache service) has been damaged or lost. Urgent action is necessary to restore this service. However, other node components are fully functional and the existing service should be minimally impacted.
•Minor—Alarms that indicate that a condition that will not affect a service has occurred, but that corrective action is required to prevent a serious fault from occurring.
You can configure alarms using the snmp-server enable traps alarms global configuration command.
Use the show alarms critical EXEC command to display the current critical alarms being generated by WAAS software applications. Use the show alarms critical detail EXEC command to display additional details for each of the critical alarms being generated. Use the show alarms critical detail support EXEC command to display an explanation about the condition that triggered the alarm and how you can find out the cause of the problem. Similarly, you can use the show alarms major and show alarms minor EXEC commands to display the details of major and minor alarms.
Use the show alarms history EXEC command to display a history of alarms that have been raised and cleared by the WAAS software on the WAAS device since the last software reload. The WAAS software retains the last 100 alarm raise and clear events only.
Use the show alarms status EXEC command to display the status of current alarms and the alarm overload status of the WAAS device and alarm overload configuration.
Examples
Table 3-3 describes the fields shown in the show alarms history command display.
Table 3-4 describes the fields shown in the show alarms status command display.
Related Commands
(config) alarm overload-detect
(config) snmp-server enable traps
show arp
To display the ARP table for a WAAS device, use the show arp EXEC command.
show arp
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
Use the show arp command to display the Internet-to-Ethernet address translation tables of the Address Resolution Protocol. Without flags, the current ARP entry for the host name is displayed.
Examples
Table 3-5 describes the fields shown in the show arp command display.
show authentication
To display the authentication configuration for a WAAS device, use the show authentication EXEC command.
show authentication {user | content-request}
Syntax Description
user |
Displays authentication configuration for user login to the system. |
content-request |
Displays content request authentication configuration information in the disconnected mode. |
s
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
When the WAAS device authenticates a user through an NTLM, LDAP, TACACS+, RADIUS, or Windows domain server, a record of the authentication is stored locally. As long as the entry is stored, subsequent attempts to access restricted Internet content by the same user do not require additional server lookups. To display the local and remote authentication configuration for user login, use the show authentication user EXEC command.
To display the content request authentication configuration information in the disconnected mode, use the show authentication content-request EXEC command.
Examples
Table 3-6 describes the fields shown in the show authentication user command display.
Table 3-7 describes the field in the show authentication content-request command display.
Related Commands
(config) authentication configuration
show statistics authentication
show auto-discovery
To display Traffic Flow Optimization (TFO) auto-discovery information for a WAE, use the show auto-discovery EXEC command.
show auto-discovery {blacklist [netmask netmask] | list [| {begin regex [regex] | exclude regex [regex] | include regex [regex]}]}
Syntax Description
Command Modes
EXEC
Device Modes
application-accelerator
Examples
The following is sample output from the show auto-discovery list command:
WAE# show auto-discovery list
E: Established, S: Syn, A: Ack, F: Fin, R: Reset
s: sent, r: received, O: Options, P: Passthrough
Src-IP:Port Dst-IP:Port Orig-St Term-St
Related Commands
show statistics auto-discovery
show statistics connection closed
show auto-register
To display the status of the automatic registration feature on a WAE, use the show auto-register EXEC command.
show auto-register
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
Examples
Table 3-8 describes the output in the show auto-register command display.
Related Commands
show banner
To display the message of the day (MOTD), login, and EXEC banner settings, use the show banner EXEC command.
show banner
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
Table 3-9 describes the fields shown in the show banner command display.
Related Commands
show bypass
To display static bypass configuration information for a WAE, use the show bypass EXEC command.
show bypass list
Syntax Description
list |
Displays the bypass list entries. You can have a maximum of 50 entries. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
Examples
Table 3-10 describes the fields shown in the show bypass list command display.
Related Commands
show cdp
To display CDP configuration information, use the show cdp EXEC command.
show cdp entry {* | neighbor} [protocol | version]
show cdp interface
[GigabitEthernet slot/port | InlinePort slot/port/{lan/wan}]
show cdp neighbors
[detail | GigabitEthernet slot/port [detail] | InlinePort slot/port/{lan/wan}[detail]]
show cdp {holdtime | run | timer | traffic}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The show cdp command displays information about how frequently CDP packets are resent to neighbors, the length of time that CDP packets are held by neighbors, the disabled status of CDP Version 2 multicast advertisements, CDP Ethernet interface ports, and general CDP traffic information.
Examples
Table 3-11 describes the fields shown in the show cdp command display.
Table 3-12 describes the fields shown in the show cdp entry neighbor command display.
Table 3-13 describes the fields shown in the show cdp entry neighbor protocol command display.
Table 3-14 describes the fields shown in the show cdp entry neighbor version command display.
Table 3-15 describes the field in the show cdp holdtime command display.
Table 3-16 describes the fields shown in the show cdp interface command display.
Table 3-17 describes the fields shown in the show cdp neighbors command display.
Table 3-18 describes the fields shown in the show cdp neighbors detail command display.
Table 3-19 describes the field in the show cdp run command display.
|
|
---|---|
CDP is XX. |
Whether CDP is enabled or disabled. |
Table 3-20 describes the field in the show cdp timer command display.
|
|
---|---|
cdp timer XX |
Time when CDP information is resent to neighbors. |
Table 3-21 describes the fields shown in the show cdp traffic command display.
Related Commands
show cifs
To display legacy CIFS run-time information, use the show cifs EXEC command.
show cifs auto-discovery [enabled | host-db | last]
show cifs cache {disk-use | entry-count}
show cifs connectivity peers
show cifs mss
show cifs requests {count | waiting}
show cifs sessions {count | list}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
Usage Guidelines
The show cifs command operates on legacy mode WAFS. For information on the transparent CIFS accelerator, use the show accelerator or show statistics accelerator commands.
Use the show cifs cache command to view information about caching efficiency. You might use this command to determine if the cache contains sufficient space or if more space is needed. If you have a performance issue, you might use this command to see whether or not the cache is full.
Use the show cifs connectivity peers command to validate the WAN link state and the Edge to Core connectivity. This command is useful for general monitoring and debugging.
Use the show cifs requests count or show cifs requests waiting command to monitor the load for CIFS traffic. You might also use this command for debugging purposes to isolate requests that are not processing.
Use the show cifs sessions count or show cifs sessions list command to view session information. You might use this command to monitor connected users during peak and off-peak hours.
Examples
The following is sample output from the show cifs connectivity peers command:
WAE# show cifs connectivity peers
In_533202151_2.43.60.38
Related Commands
show clock
To display information about the system clock on a WAAS device, use the show clock EXEC command.
show clock [detail | standard-timezones {all | details timezone | regions | zones region-name}]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The WAAS device has several predefined standard time zones. Some of these time zones have built-in summer time information while others do not. For example, if you are in an eastern region of the United States (US), you must use the US/Eastern time zone that includes summer time information for the system clock to adjust automatically every April and October. There are about 1500 standard time zone names.
Strict checking disables the clock summertime command when you configure a standard time zone is configured. You can configure summer time only if the time zone is not a standard time zone (that is, if the time zone is a customized zone).
The show clock standard-timezones all EXEC command enables you to browse through all standard timezones and choose from these predefined time zones so that you can choose a customized name that does not conflict with the predefined names of the standard time zones. Most predefined names of the standard time zones have two components, a region name and a zone name. You can list time zones by several criteria, such as regions and zones. To display all first level time zone names organized into directories by region, use the show clock standard-timezones region EXEC command.
The show clock command displays the local date and time information and the show clock detail command shows optional detailed date and time information.
Examples
Table 3-22 describes the field in the show clock command display.
|
|
---|---|
Local time |
Day of the week, month, date, time (hh:mm:ss), and year in local time relative to the UTC offset. |
Table 3-23 describes the fields shown in the show clock detail command display.
Related Commands
show cms
To display Centralized Management System (CMS) embedded database content and maintenance status and other information for a WAAS device, use the show cms EXEC command.
show cms {database content {dump filename | text | xml} | info | secure-store}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
Table 3-24 describes the fields shown in the show cms info command display for WAAS application engines.
Table 3-25 describes the fields shown in the show cms info command display for WAAS Central Managers.
Table 3-26 describes the field in the show cms database content text command display.
Table 3-27 describes the field in the show cms database content xml command display.
Related Commands
show cms secure-store
To display secure store status, use the show cms secure-store EXEC command.
show cms secure-store
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 show cms secure-store command will display one of the following status messages (Table 3-28):
Examples
The following is sample output from the show cms secure-store command:
WAE# show cms secure-store
secure-store initialized and open
Related Commands
show crypto
To display crypto layer information, use the show crypto EXEC command.
show crypto {certificate-detail {factory-self-signed | management | filename} | certificates}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
Table 3-29 describes the fields in the show crypto certificate-detail command display.
Table 3-30 describes the fields in the show crypto certificates command display.
Related Commands
show statistics crypto ssl ciphers
show debugging
To display the state of each debugging option that was previously enabled on a WAAS device, use the show debugging EXEC command.
show debugging
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 show debugging command shows which debug options have been enabled or disabled. If there are no debug options configured, the show debugging command shows no output.
The dre, epm, flow, print-spooler, rbcp, tfo, translog, wafs, and wccp command options are supported in the application-accelerator device mode only. The emdb and rpc command options are supported in the central manager device mode only.
The show debugging command displays only the type of debugging enabled, not the specific subset of the command.
Examples
The following is sample output from the show debugging command:
WAE# debug tfo buffer-mgr
WAE# debug tfo connection
WAE# show debugging
tfo bufmgr debugging is on
tfo compmgr debugging is on
tfo connmgr debugging is on
tfo netio debugging is on
tfo statmgr debugging is on
tfo translog debugging is on
In this example, the debug tfo buffer-mgr and the debug tfo connection commands coupled with the show debugging command display the states of tfo buffer-mgr and tfo connection debugging options.
Related Commands
show device-mode
To display the configured or current device mode of a WAAS device, use the show device-mode EXEC command.
show device-mode {configured | current}
Syntax Description
configured |
Displays the configured device mode, which has not taken effect yet. |
current |
Displays the current device mode. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
To display the configured device mode that has not yet taken effect, enter the show device-mode configured EXEC command. For example, if you had entered the device mode central-manager global configuration command on a WAAS device to change its device mode to central manager but have not yet entered the copy run start EXEC command to save the running configuration on the device, then if you were to enter the show device-mode configured command on the WAAS device, the command output would indicate that the configured device mode is central-manager.
Examples
The following is sample output from the show device mode command. It displays the current mode in which the WAAS device is operating.
WAE# show device-mode current
Current device mode: application-accelerator
Table 3-31 describes the field in the show device-mode current command display.
|
|
---|---|
Current device mode |
Current mode in which the WAAS device is operating. |
The following is sample output from the show device configured command. It displays the configured device mode that has not yet taken effect.
WAE# show device-mode configured
Configured device mode: central-manager
Table 3-32 describes the field in the show device-mode configured command display.
|
|
---|---|
Configured device mode |
Device mode that has been configured, but has not yet taken effect. |
Related Commands
show directed-mode
To view the status and port assigned to directed mode on a device, use the show directed-mode EXEC command.
show directed-mode
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
Examples
The following is sample output from the show directed-mode EXEC command:
WAE# show directed-mode
Configuration Status: Enabled
Config Item Mode Value
----------- ---- ------
UDP port Default 4050
This example shows that directed mode is enabled and it is using UDP port 4050.
Related Commands
show statistics connection closed
show disks
To view information about the WAAS device disks, use the show disks EXEC command.
show disks {details | failed-disk-id | failed-sectors [disk_name] | tech-support [details]}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The show disks details EXEC command displays the percentage or amount of disk space allocated to each file system, and the operational status of the disk drives, after reboot.
The WAAS software supports filtering of multiple syslog messages for a single, failed section on IDE, SCSI, and SATA disks.
Proactively Monitoring Disk Health with SMART
The ability to proactively monitor the health of disks is available using SMART. SMART provides you with hard drive diagnostic information and information about impending disk failures.
SMART is supported by most disk vendors and is a standard method used to determine how healthy a disk is. SMART attributes include several read-only attributes (for example, the power on hours attribute, the load and unload count attribute) that provide the WAAS software with information regarding the operating and environmental conditions that may indicate an impending disk failure.
SMART support is vendor and drive technology (IDE, SCSI, and Serial Advanced Technology Attachment [SATA] disk drive) dependent. Each disk vendor has a different set of supported SMART attributes.
Even though SMART attributes are vendor dependent there is a common way of interpreting most SMART attributes. Each SMART attribute has a normalized current value and a threshold value. When the current value exceeds the threshold value, the disk is considered to have "failed." The WAAS software monitors the SMART attributes and reports any impending failure through syslog messages, SNMP traps, and alarms.
To display SMART information, use the show disks tech-support EXEC command. To display more detailed SMART information, enter the show disks tech-support details EXEC command. The output from the show tech-support EXEC command also includes SMART information.
Examples
The following is sample output from the show disks failed-sectors command. It displays a list of failed sectors on all disk drives.
WAE#
show disks failed-sectors
disk00
=========
89923
9232112
disk01
=========
(None)
The following is sample output from the show disks failed-sectors command when you specify a disk drive. It displays a list of failed sectors for disk01.
WAE#
show disks failed-sectors disk01
disk01
=========
(None)
If there are disk failures, a message is displayed, notifying you about this situation when you log in.
Table 3-33 describes the fields shown in the show disks failed-disk-id command display.
|
|
---|---|
Diskxx |
Number and location of the physical disk. |
Alpha-numeric string |
Serial number of the disk. |
Table 3-34 describes the fields shown in the show disks details command display.
The following is sample output from the show disks tech-support command. The output shows that partition 04 and partition 05 on disks disk00 and disk01 are GOOD, and the RAIDed partitions /dev/md4 & /dev/md5 are in NORMAL OPERATION. However, the RAIDed partition /dev/md8 has an issue with one of the drives. Disk04 with partition 00 is GOOD, but the status shows ONE OR MORE DRIVES ABNORMAL because there is no pair on this partition.
WAE#
show disks tech-support
/dev/md4 RAID-1 NORMAL OPERATION disk00/04[GOOD]
disk01/04[GOOD]
/dev/md5 RAID-1 NORMAL OPERATION disk00/05[GOOD]
disk01/05[GOOD]
...
/dev/md8 RAID-1 ONE OR MORE DRIVES ABNORMAL disk04/00[GOOD]
Table 3-35 describes some typical fields in the show disks tech-support command display for a RAID-1 appliance that supports SMART. SMART attributes are vendor dependent; each disk vendor has a different set of supported SMART attributes.
Table 3-36 describes the fields shown in the show disks tech-support command display for a RAID-5 appliance.
Table 3-37 describes the fields in the show disks tech-support details command display for a RAID-1 appliance that supports SMART. Details in this display depend on the drive manufacturer and vary between drives.
Related Commands
show egress-methods
To view the egress method that is configured and that is being used on a particular WAE, use the show egress-methods EXEC command.
show egress-methods
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
Examples
Table 3-38 describes the fields shown in the show egress-methods command display.
Related Commands
show filtering list
To display information about the incoming and outgoing TFO flows that the WAE currently has, use the show filtering list EXEC command.
show filtering list [| {begin regex [regex] | exclude regex [regex] | include regex [regex] }] [| {begin regex [regex] | exclude regex [regex] | include regex [regex]}]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
Usage Guidelines
The show filtering list command lists TCP flows that the WAE is currently optimizing. It also includes TCP flows that are not being optimized but that are being passed through by the WAE. A "P" in the State column indicates a passed through flow.
Examples
The following is sample output from the show filtering list command. It displays TFO connection information for the WAE.
WAE# show filtering list
E: Established, S: Syn, A: Ack, F: Fin, R: Reset
s: sent, r: received, O: Options, P: Passthrough
B: Bypass, L: Last Ack, W: Time Wait, D: Done
T: Timedout, C: Closed
Local-IP:Port Remote-IP:Port Tuple(Mate) State
10.99.11.200:1398 10.99.22.200:80 0xcba709c0(0xcba70a00) E
10.99.11.200:1425 10.99.22.200:80 0xcba70780(0xcba707c0) E
10.99.11.200:1439 10.99.22.200:5222 0xcba703c0(0xcba70b40) Sr
10.99.11.200:1440 10.99.22.200:5222 0xcba70400(0xcba70440) Sr
10.99.22.200:1984 10.99.11.200:80 0xcba70600(0xcba70640) E
10.99.22.200:1800 10.99.11.200:23 0xcba70480(0x0 ) PE
10.99.11.200:1392 10.99.22.200:80 0xcba70f80(0x0 ) E
10.99.22.200:20 10.99.11.200:1417 0xcba701c0(0xcba70180) E
10.99.11.200:1417 10.99.22.200:20 0xcba70180(0x0 ) E
10.99.22.200:1987 10.99.11.200:80 0xcba70240(0xcba70200) E
10.99.11.200:1438 10.99.22.200:5222 0xcba70900(0xcba70580) Sr
10.99.22.200:1990 10.99.11.200:80 0xcba70100(0xcba70140) E
10.99.22.200:80 10.99.11.200:1426 0xcba70740(0xcba70700) E
10.99.22.200:80 10.99.11.200:1425 0xcba707c0(0xcba70780) E
10.99.22.200:1985 10.99.11.200:80 0xcba70a40(0xcba70a80) E
10.99.22.200:80 10.99.11.200:1410 0xcba70500(0xcba70540) E
10.99.22.200:80 10.99.11.200:1398 0xcba70a00(0xcba709c0) E
10.99.22.200:80 10.99.11.200:1392 0xcba70f40(0xcba70f80) E
10.0.19.5:54247 10.1.242.5:80 0xc9e5b400(0xc9e5b100) ED
Note The "ED" state occurs when one socket in the pair is closed (D), but the mate is still established (E).
Related Commands
show statistics auto-discovery
show statistics connection closed
show flash
To display the flash memory version and usage information for a WAAS device, use the show flash EXEC command.
show flash
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
Table 3-39 describes the fields shown in the show flash command display.
show hardware
To display system hardware status for a WAAS device, use the show hardware EXEC command.
show hardware
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 show hardware command lists the system hardware status, including the version number, the startup date and time, the run time since startup, the microprocessor type and speed, the amount of physical memory available, and a list of disk drives.
Examples
Table 3-40 describes the fields shown in the show hardware command display.
Related Commands
show hosts
To view the hosts on a WAAS device, use the show hosts EXEC command.
show hosts
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 show hosts command lists the name servers and their corresponding IP addresses. It also lists the hostnames, their corresponding IP addresses, and their corresponding aliases (if applicable) in a host table summary.
Examples
Table 3-41 describes the fields shown in the show hosts command display.
Related Commands
(config) ip hosts
show inetd
To display the status of TCP/IP services on a WAAS device, use the show inetd EXEC command.
show inetd
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 show inetd EXEC command displays the enabled or disabled status of TCP/IP services on the WAAS device. You can ignore the TFTP service status because TFTP is not supported on WAAS.
Examples
Table 3-42 describes the fields shown in the show inetd command display.
Related Commands
show interface
To display the hardware interface information for a WAAS device, use the show interface EXEC command.
show interface {GigabitEthernet slot/port} | {ide control_num} | {InlineGroup slot/grpnumber} | {InlinePort slot/grpnumber/{lan | wan}} | {PortChannel port-num} | {scsi device_num}
| {standby 1 }
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
The following is sample output from the show interface command. It displays information for inlineGroup 0 in slot 1 configured on the WAE inline network adapter.
WAE612# show interface inlineGroup 1/0
Interface is in intercept operating mode.
Standard NIC mode is off.
Disable bypass mode is off.
VLAN IDs configured for inline interception: All
Watchdog timer is enabled.
Timer frequency: 1600 ms.
Autoreset frequency 500 ms.
The watchdog timer will expire in 1221 ms.
Table 3-43 describes the fields shown in the show interface GigabitEthernet command display.
Table 3-44 describes the fields shown in the show interface InlinePort command display.
Table 3-45 describes the fields shown in the show interface PortChannel command display.
Table 3-46 describes the fields shown in the show interface standby command display.
|
|
---|---|
Description |
Description of the device, as configured by using the description option of the interface global configuration command. |
Interface Standby 1 |
Number that identifies the standby group and the number of associated physical interfaces. |
Member interfaces |
Member interfaces of the standby group. Shows which physical interfaces are part of the standby group. Shows the interface definition, such as GigibitEthernet 1/0, and indicates if the interface is active (has an active layer 2 connection to a switch), primary (configured as primary in the running configuration), and in use (carrying network traffic). |
Type |
Type of interface. Always Ethernet. |
. . . |
The following fields are the same as for a gigabit Ethernet interface, as shown in Table 3-43. |
Related Commands
(config) interface GigabitEthernet
show inventory
To display the system inventory information for a WAAS device, use the show inventory EXEC command.
show inventory
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 show inventory EXEC command allows you to view the UDI for a WAAS device. This identity information is stored in the nonvolatile memory of the WAAS device.
The UDI is electronically accessed by the product operating system or network management application to enable identification of unique hardware devices. The data integrity of the UDI is vital to customers. The UDI that is programmed into the nonvolatile memory of the WAAS device is equivalent to the UDI that is printed on the product label and on the carton label. This UDI is also equivalent to the UDI that can be viewed through any electronic means and in all customer-facing systems and tools. Currently, there is only CLI access to the UDI; there is no SNMP access to the UDI information.
You can also use the show tech-support EXEC command to display the WAAS device UDI.
Examples
Table 3-47 describes the fields shown in the show inventory command display.
Related Commands
show ip access-list
To display the access lists that are defined and applied to specific interfaces or applications on a WAAS device, use the show ip access-list EXEC command.
show ip access-list [acl-name | acl-num]
Syntax Description
Defaults
Displays information about all defined access lists.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use the show ip access-list EXEC command to display the access lists that have been defined on the WAAS device. Unless you identify a specific access list by name or number, the system displays information about all the defined access lists, including the following sections:
•Available space for new lists and conditions
•Defined access lists
•References by interface and application
Examples
Table 3-48 describes the fields shown in the show ip access-list command display.
Related Commands
show ip routes
To display the IP routing table for a WAAS device, use the show ip routes EXEC command.
show ip routes
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 show ip routes command displays the IP route table, which lists all of the different routes that are configured on the WAE. The WAE uses this table to determine the next hop. This table includes routes from three sources: the WAE GigabitEthernet interfaces, any user-configured static routes, and the default gateway. The last line in this table shows the default route.
Examples
Table 3-49 describes the fields shown in the show ip routes command display.
Related Commands
show kdump
To display the kernel crash dump information for a WAAS device, use the show kdump EXEC command.
show kdump
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
Table 3-50 describes the fields shown in the show kdump command display.
Related Commands
show kerberos
To display the Kerberos authentication configuration for a WAAS device, use the show kerberos EXEC command.
show kerberos
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
Table 3-51 describes the fields shown in the show kerberos command display.
Related Commands
show key-manager
To display the key manager information for a WAAS device, use the show key-manager EXEC command.
show key-manager {key-token | status}
Syntax Description
key-token |
Displays the encryption key token for each registered WAE device. |
status |
Displays the encryption status for each registered WAE device. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
central-manager
Examples
Table 3-52 describes the fields shown in the show key-manager key-token command display. The set of fields is displayed for each key used on each WAE registered to the Central Manager.
Related Commands
show license
To display license information for a WAAS device, use the show license EXEC command.
show license
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 is sample output from the show license command. It lists the WAAS licenses, giving the name, status, date applied, and the name of the user that applied the license for each active license.
WAE# show license
License Name Status Activation Date Activated by
----------------------------------------------------------------------
Transport not active
Enterprise active 11/12/2008 admin
Video not active
Virtual-Blade not active
Related Commands
show logging
To display the system message log configuration for a WAAS device, use the show logging EXEC command.
show 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
Use the system message log to view information about events that have occurred on a WAAS device. The syslog.txt file is contained in the /local1 directory.
Examples
The following is sample output from the show logging command. It displays the syslog host configuration on a WAAS device.
WAE# show logging
Syslog to host is disabled
Priority for host logging is set to: warning
Syslog to console is disabled
Priority for console logging is set to: warning
Syslog to disk is enabled
Priority for disk logging is set to: notice
Filename for disk logging is set to: /local1/syslog.txt
Syslog facility is set to *
Syslog disk file recycle size is set to 1000000
Related Commands
show memory
To display memory blocks and statistics for a WAAS device, use the show memory EXEC command.
show memory
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
Table 3-53 describes the fields shown in the show memory command display.
show ntp
To display the NTP parameters for a WAAS device, use the show ntp EXEC command.
show ntp status
Syntax Description
status |
Displays NTP status. |
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
Table 3-54 describes the fields shown in the show ntp status command display.
Related Commands
show policy-engine application
To display application policy information for a WAE, use the show policy-engine application EXEC command.
show policy-engine application {classifier [app-classifier] | dynamic | name}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Device Modes
application-accelerator
Usage Guidelines
Use the show policy-engine application dynamic command to display auto-discovered CIFS file servers that are added to the list (for WAFS legacy mode only). The servers are visible in the dynamic listing for a limited time (3 minutes by default) after any activity stops, and then they are dropped from the dynamic list until another client request causes them to be auto-discovered again.
Examples
Table 3-55 describes the fields shown in the show policy-engine application classifier command display.
Table 3-56 describes the fields shown in the show policy-engine application dynamic command display.
Table 3-57 describes the fields shown in the show policy-engine application name command display.