Table Of Contents
Exec Mode Commands
cd
clear
clock
cms
configure
copy cdrom
copy compactflash
copy disk
copy ftp
copy http
copy running-config
copy startup-config
copy sysreport
copy system-status
copy tech-support
copy tftp
cpfile
debug
delfile
deltree
dir
disable
disk
dnslookup
enable
exit
find-pattern
help
install
less
lls
ls
mkdir
mkfile
ntpdate
no debug
ping
pwd
reload
rename
restore
rmdir
scp
script
setup
show aaa accounting
show alarms
show arp
show authentication
show auto-register
show bypass
show cdp
show clock
show cms
show debugging
show device-mode
show disks
show flash
show hardware
show hosts
show inetd
show interface
show inventory
show ip access-list
show ip routes
show kerberos
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 standby
show startup-config
show statistics authentication
show statistics content-distribution-network
show statistics dre
show statistics dre connection
show statistics dre peer
show statistics epm
show statistics icmp
show statistics ip
show statistics netstat
show statistics radius
show statistics services
show statistics snmp
show statistics tacacs
show statistics tcp
show statistics tfo
show statistics udp
show statistics wccp
show statistics windows-domain
show sysfs
show tacacs
show tcp
show tech-support
show telnet
show tfo accelerators
show tfo auto-discovery
show tfo bufpool
show tfo connection
show tfo filtering
show tfo status
show transaction-logging
show user
show users administrative
show version
show wccp
show windows-domain
shutdown
snmp trigger
ssh
tcpdump
telnet
terminal
tethereal
traceroute
transaction-log
type
type-tail
undebug
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.
In the following example, a user accesses the privileged-level EXEC command line from the user level:
To leave EXEC mode, use the exit command at the system prompt:
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:
The following example shows how to change to a directory using an absolute path:
Related Commands
deltree
dir
lls
ls
mkdir
pwd
clear
To clear the hardware interface, statistics, and other settings, use the clear EXEC command.
clear cdp {counters | table}
clear ip access-list counters [acl-num | acl-name]
clear logging
clear statistics {all | authentication | history | icmp | ip | radius | running | tacacs | tcp | udp |
windows-domain}
clear users administrative
clear windows-domain-log
Syntax Description
cdp
|
Resets the Cisco Discovery Protocol (CDP) statistical data.
|
counters
|
Clears the CDP counters.
|
table
|
Clears the CDP tables.
|
ip access-list
|
Clears the IP access list statistical information.
|
counters
|
Clears the IP access list counters.
|
acl-name
|
(Optional) Clears the counters for the specified access list, identified using an alphanumeric identifier of up to 30 characters, beginning with a letter.
|
acl-num
|
(Optional) Clears the counters for the specified access list, identified using a numeric identifier (standard access list: 1-99; extended access list: 100-199).
|
logging
|
Clears the syslog messages saved in the disk file.
|
statistics
|
Clears the statistics as specified.
|
all
|
Clears all statistics.
|
authentication
|
Clears the authentication statistics.
|
history
|
Clears the statistics history.
|
icmp
|
Clears the ICMP statistics.
|
ip
|
Clears the IP statistics.
|
radius
|
Clears the RADIUS statistics.
|
running
|
Clears the running statistics.
|
tacacs
|
Clears the TACACS+ statistics.
|
tcp
|
Clears the TCP statistics.
|
udp
|
Clears the UDP statistics.
|
windows-domain
|
Clears the Windows domain statistics.
|
users
|
Clears the connections (login) of authenticated users.
|
administrative
|
Clears the connections of administrative users authenticated through a remote login service.
|
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
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, as shown in the following example.
Feb 14 12:17:18 WAE# exec_clear_logging:Syslog cleared
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.
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 windows-domain-log command removes all current entries from the Windows domain log file.
Examples
In the following example, all entries in the syslog.txt file are cleared on the WAAS device:
In the following example, all authentication, RADIUS and TACACS+ information is cleared on the WAAS device:
WAE# clear statistics radius
WAE# clear statistics tacacs
WAE# clear statistics authentication
In the following example, all entries in the Windows domain log file are cleared on the WAAS device:
WAE# clear windows-domain-log
Related Commands
show interface
show wccp
clock
To set clock functions or update the calendar, use the clock EXEC command. Use the no form of this command to clear clock functions and calendar.
clock {read-calendar | set time day month year | update-calendar}
Syntax Description
read-calendar
|
Reads the calendar and updates the system clock.
|
set
|
Sets the time and date.
|
time
|
Current time in hh:mm:ss format (hh: 00-23; mm: 00-59; ss: 00-59).
|
day
|
Day of the month (1-31).
|
month
|
Month of the year (January, February, March, April, May, June, July, August, September, October, November, December).
|
year
|
Year (1993-2035).
|
update-calendar
|
Updates the calendar with the system clock.
|
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 sets the software clock on the WAAS device:
WAE# clock set 13:32:00 01 February 2005
Related Commands
show clock
cms
To configure the Centralized Management System (CMS) embedded database parameters for a WAAS device, use the cms EXEC command.
cms {config-sync | database {backup | create | delete | downgrade [script filename] |
lcm {enable | disable} | maintenance {full | regular} | restore filename | validate} |
deregister [force] | recover {identity word}}
Syntax Description
config-sync
|
Sets the node to synchronize configuration with the WAAS Central Manager.
|
database
|
Creates, backs up, deletes, restores, or validates the CMS-embedded database management tables or files.
|
backup
|
Backs up the database management tables.
|
create
|
Creates the embedded database management tables.
|
delete
|
Deletes the embedded database files.
|
downgrade
|
Downgrades the CMS database.
|
script
|
(Optional) Downgrades the CMS database by applying a downgrade script.
|
filename
|
Downgraded script filename.
|
lcm
|
Configures local/central management on a WAAS device that is registered with the WAAS Central Manager.
|
enable
|
Enables synchronization of the WAAS network configuration of the device with the local CLI configuration.
|
disable
|
Disables synchronization of the WAAS network configuration of the device with the local CLI configuration.
|
maintenance
|
Cleans and reindexes the embedded database tables.
|
full
|
Specifies a full maintenance routine for the embedded database tables.
|
regular
|
Specifies a regular maintenance routine for the embedded database tables.
|
restore
|
Restores the database management tables using the backup local filename.
|
filename
|
Database local backup filename.
|
validate
|
Validates the database files.
|
deregister
|
Removes the registration of the CMS proto device.
|
force
|
(Optional) Forces the removal of the node registration.
|
recover
|
Recovers the identity of a WAAS device.
|
identity
|
Specifies the identity of the recovered device.
|
word
|
Identity of the recovered device.
|
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The WAAS network is a collection of WAAS device and WAAS Central Manager nodes. One primary WAAS Central Manager retains the WAAS network settings and provides other WAAS network nodes with updates. Communication between nodes occurs over secure channels using the Secure Shell Layer (SSL) protocol, where each node on the WAAS network uses a Rivest, Shamir, Adelman (RSA) certificate-key pair to communicate with other nodes.
Use the cms config-sync command to enable registered WAAS devices and standby WAAS Central Manager to contact the primary WAAS Central Manager immediately for a getUpdate (get configuration poll) request before the default polling interval of 5 minutes. For example, when a node is registered with the primary WAAS Central Manager and activated, it appears as Pending in the WAAS Central Manager GUI until it sends a getUpdate request. The cms config-sync command causes the registered node to send a getUpdate request at once, and the status of the node changes as Online.
Use the cms database create command to initialize the CMS database. Before a node can join a WAAS network, it must first be registered and then activated. The cms enable global configuration command automatically registers the node in the database management tables and enables the CMS. The node sends its attribute information to the WAAS Central Manager over the SSL protocol and then stores the new node information. The WAAS Central Manager accepts these node registration requests without admission control and replies with registration confirmation and other pertinent security information required for getting updates. Activate the node using the WAAS Central Manager GUI.
Once the node is activated, it automatically receives configuration updates and the necessary security RSA certificate-key pair from the WAAS Central Manager. This security key allows the node to communicate with any other node in the WAAS network. The cms deregister command removes the node from the WAAS network by deleting registration information and database tables.
To back up the existing management database for the WAAS Central Manager, use the cms database backup command. For database backups, specify the following items:
•
Location, password, and user ID
•
Dump format in PostgreSQL plain text syntax
The naming convention for backup files includes the time stamp.
Note
For information on the procedure to back up and restore the CMS database on the WAAS Central Manager, see the Cisco Wide Area Application Services Configuration Guide.
When you use the cms recover identity word command when recovering lost registration information, or replacing a failed node with a new node that has having 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 Home 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 backs 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 validates the cms database management tables on the WAAS Central Manager named waas-cm:
waas-cm# cms database validate
Management tables are valid
Related Commands
(config) cms
show cms
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
Usage Guidelines
Use this command to enter global configuration mode.
Examples
The following example shows how to enable global configuration mode on a WAAS device:
Related Commands
(config) end
(config) exit
show running-config
show startup-config
copy cdrom
To copy software release files from a CD-ROM, use the copy cdrom EXEC command.
copy cdrom install filedir filename
Syntax Description
cdrom
|
Copies a file from the CD-ROM.
|
install
|
Installs the software release file.
|
filedir
|
Directory location of the software release file.
|
filename
|
Filename of the software release file.
|
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Related Commands
install
reload
show running-config
show startup-config
wafs
write
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
|
Installs a software release file.
|
filename
|
Image filename.
|
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Related Commands
install
reload
show running-config
show startup-config
wafs
write
copy disk
To copy the configuration or image data from a disk to a remote location using FTP or to the startup configuration, use the copy disk EXEC command.
copy disk {ftp {hostname | ip-address} remotefiledir remotefilename localfilename |
startup-config filename}
Syntax Description
disk
|
Copies a local disk file.
|
ftp
|
Copies to a file on an FTP server.
|
hostname
|
Hostname of the FTP server.
|
ip-address
|
IP address of the FTP server.
|
remotefiledir
|
Directory on the FTP server to which the local file is copied.
|
remotefilename
|
Name of the local file once it has been copied to the FTP server.
|
localfilename
|
Name of the local file to be copied.
|
startup-config
|
Copies the configuration file from the disk to startup configuration (NVRAM).
|
filename
|
Name of the existing configuration file.
|
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The copy disk ftp EXEC command copies files from a SYSFS partition to an FTP server. The copy disk startup-config EXEC command copies a startup configuration file to NVRAM.
Related Commands
install
reload
show running-config
show startup-config
wafs
write
copy ftp
To copy software configuration or image data from an FTP server, use the copy ftp EXEC command.
copy ftp {central {hostname | ip-address} remotefiledir remotefilename slotnumber [username
username password | proxy {hostname | ip-address} proxy_portnum [username username
password] | port port-num | md5 md5sum] | disk {hostname | ip-address} remotefiledir
remotefilename localfilename | install {hostname | ip-address} remotefiledir remotefilename}
Syntax Description
ftp
|
Copies a file from an FTP server.
|
central
|
Copies a file to the software upgrade image repository.
|
hostname
|
Hostname of the FTP server.
|
ip-address
|
IP address of the FTP server.
|
remotefiledir
|
Directory on the FTP server where the image file to be copied is located.
|
remotefilename
|
Name of the file to be copied to the image repository.
|
slotnumber
|
Slot location (1-5) into which the upgrade image is to be copied.
|
username
|
(Optional) Specifies FTP authentication.
|
username
|
(Optional) Clear text of the username.
|
password
|
(Optional) Password for FTP authentication.
|
proxy
|
(Optional) Specifies proxy address.
|
hostname
|
(Optional) Hostname of the proxy server.
|
ip-address
|
(Optional) IP address of the proxy server.
|
proxy_portnum
|
(Optional) Port number on the proxy server.
|
username
|
(Optional) Specifies the proxy server authentication username.
|
username
|
(Optional) Clear text of the username.
|
password
|
(Optional) Password for proxy server authentication.
|
port
|
(Optional) Specifies port at which to connect to the FTP server.
|
port-num
|
(Optional) Port number on the FTP server.
|
md5
|
(Optional) Specifies MD5 signature of the file being copied.
|
md5sum
|
(Optional) MD5 signature.
|
disk
|
Copies a file to a local disk.
|
hostname
|
Hostname of the FTP server.
|
ip-address
|
IP address of the FTP server.
|
remotefiledir
|
Directory on the FTP server where the file to be copied is located.
|
remotefilename
|
(Optional) Name of the file to be copied to the local disk.
|
localfilename
|
(Optional) Name of the copied file as it appears on the local disk.
|
install
|
(Optional) Copies the file from an FTP server and installs the software release file to the local device.
|
hostname
|
(Optional) Name of the FTP server.
|
ip-address
|
(Optional) IP address of the FTP server.
|
remotefiledir
|
Remote file directory.
|
remotefilename
|
Remote filename.
|
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The copy ftp disk EXEC command copies a file from an FTP server to a SYSFS partition on the WAAS device.
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 disk and part goes to flash memory. Use the copy ftp central EXEC command to download a software image into the repository from an FTP server.
You can also use the copy ftp install EXEC commands 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.
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 software through an interface. The Basic Input Output System (BIOS) provides such an interface. It gives the 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. It 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. Furthermore, it provides an interface between the hardware and the operating system in the form of a library of interrupt handlers. For instance, each time 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. This problem can be solved 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:
•
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
Caution 
Be
extraordinarily careful when upgrading a Flash BIOS. Make
absolutely sure that the BIOS upgrade patch is the exact one required. If you apply the wrong patch, you can render the system unbootable, making it difficult or impossible to recover even by reapplying the proper patch.
Caution 
Because a failed Flash BIOS update can have dire results, never update a Flash BIOS without first connecting the system to an uninterruptible power supply (UPS).
To install the 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:
The new BIOS takes effect after the system reboots.
Examples
The following example copies an image file from an FTP server and installs the file on the local device:
WAE# copy ftp 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
10.1.1.1 FTP server (Version) Mon Feb 28 10:30:36 EST
Password required for biff.
Entering Passive Mode (128,107,193,244,55,156)
Sending:CWD //ftp-sj.cisco.com/cisco/waas/4.0
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).
###################################################################################
.................................................................
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 dependant 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
upgradeserver.cisco.com FTP server (Version wu-2.6.1-18) ready.
Password required for myusername.
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.
Entering Passive Mode (128,107,193,240,57,37)
Sending:CWD /bios/update53/derived/
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
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
install
reload
show running-config
show startup-config
wafs
write
copy http
To copy configuration or image data from an HTTP server to the WAAS device, use the copy http EXEC command.
copy http {central {hostname | ip-address} remotefiledir remotefilename slotnumber [username
username password | proxy {hostname | ip-address} proxy_portnum [username username
password] | port port-num | md5 md5sum] | install {{hostname | ip-address} remotefiledir
remotefilename}[port port-num [proxy {hostname | ip-address} | username username
password [proxy {hostname | ip-address} proxy_portnum]] | proxy {hostname | ip-address}
proxy_portnum | username username password [proxy {hostname | ip-address}
proxy_portnum]]}
Syntax Description
http
|
Copies the file from an HTTP server.
|
central
|
Copies a file to the software upgrade image repository.
|
hostname
|
Hostname of the HTTP server.
|
ip-address
|
IP address of the HTTP server.
|
remotefiledir
|
Directory on the HTTP server where the image file to be copied is located.
|
remotefilename
|
Name of the file to be copied to the image repository.
|
slotnumber
|
Slot location (1-5) into which the upgrade image is to be copied.
|
username
|
(Optional) Specifies HTTP authentication.
|
username
|
(Optional) Clear text of the username.
|
password
|
(Optional) Password for HTTP authentication.
|
proxy
|
(Optional) Specifies proxy address.
|
hostname
|
(Optional) Hostname of the proxy server.
|
ip-address
|
(Optional) IP address of the proxy server.
|
proxy_portnum
|
(Optional) Port number on the proxy server.
|
username
|
(Optional) Specifies the proxy server authentication username.
|
username
|
(Optional) Clear text of the username.
|
password
|
(Optional) Password for proxy server authentication.
|
port
|
(Optional) Specifies port at which to connect to the HTTP server.
|
port-num
|
(Optional) Port number on the HTTP server.
|
md5
|
(Optional) Specifies MD5 signature of the file being copied.
|
md5sum
|
(Optional) MD5 signature.
|
install
|
Copies the file from an HTTP server and installs the software release file to the local device.
|
hostname
|
Name of the HTTP server.
|
ip-address
|
IP address of the HTTP server.
|
remotefiledir
|
Remote file directory.
|
remotefilename
|
Remote filename.
|
port
|
(Optional) Port to connect to the HTTP server (default is 80).
|
port-num
|
(Optional) HTTP server port number (1-65535).
|
proxy
|
(Optional) Allows the request to be redirected to an HTTP proxy server.
|
hostname
|
(Optional) Name of the HTTP server.
|
ip-address
|
(Optional) IP address of the HTTP server.
|
proxy_portnum
|
(Optional) HTTP proxy server port number (1-65535).
|
username
|
Username to access the HTTP proxy server.
|
username
|
User login name.
|
password
|
Establishes password authentication.
|
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 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 software through an interface. The Basic Input Output System (BIOS) provides such an interface. It gives the 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. It 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. Furthermore, it provides an interface between the hardware and the operating system in the form of a library of interrupt handlers. For instance, each time 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. This problem can be solved 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
Caution 
Be
extraordinarily careful when upgrading a Flash BIOS. Make
absolutely sure that the BIOS upgrade patch is the exact one required. If you apply the wrong patch, you can render the system unbootable, making it difficult or impossible to recover even by reapplying the proper patch.
Caution 
Because a failed Flash BIOS update can have dire results, never update a Flash BIOS without first connecting the system to an uninterruptible power supply (UPS).
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:
The new BIOS takes effect after the system reboots.
Examples
The following example copies an image file from an HTTP server and installs 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
10.1.1.1 FTP server (Version) Mon Feb 28 10:30:36 EST
Password required for biff.
Entering Passive Mode (128,107,193,244,55,156)
Sending:CWD //ftp-sj.cisco.com/cisco/waas/4.0
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).
###################################################################################
.................................................................
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 dependant 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
upgradeserver.cisco.com FTP server (Version wu-2.6.1-18) ready.
Password required for myusername.
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.
Entering Passive Mode (128,107,193,240,57,37)
Sending:CWD /bios/update53/derived/
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
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
install
reload
show running-config
show startup-config
wafs
write
copy running-config
To copy a configuration or image data from the current configuration, use the copy running-config EXEC command.
copy running-config {disk filename | startup-config | tftp {hostname | ip-address}
remotefilename}
Syntax Description
running-config
|
Copies the current system configuration.
|
disk
|
Copies the current system configuration to a disk file.
|
filename
|
Name of the file to be created on disk.
|
startup-config
|
Copies the running configuration to startup configuration (NVRAM).
|
tftp
|
Copies the running configuration to a file on a TFTP server.
|
hostname
|
Hostname of the TFTP server.
|
ip-address
|
IP address of the TFTP server.
|
remotefilename
|
Remote filename of the configuration file to be created on the TFTP server. Use the complete pathname.
|
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 WAAS device's running system configuration 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.
Related Commands
install
reload
show running-config
show startup-config
wafs
write
copy startup-config
To copy configuration or image data from the startup configuration, use the copy startup-config EXEC command.
copy startup-config {disk filename | running-config | tftp {hostname | ip-address}
remotefilename}
Syntax Description
startup-config
|
Copies the startup configuration.
|
disk
|
Copies the startup configuration to a disk file.
|
filename
|
Name of the startup configuration file to be copied to the local disk.
|
running-config
|
Copies the startup configuration to running configuration.
|
tftp
|
Copies the startup configuration to a file on a TFTP server.
|
hostname
|
Hostname of the TFTP server.
|
ip-address
|
IP address of the TFTP server.
|
remotefilename
|
Remote filename of the startup configuration file to be created on the TFTP server. Use the complete pathname.
|
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The copy startup-config EXEC command copies the startup configuration file to a TFTP server or to a SYSFS partition.
Related Commands
install
reload
show running-config
show startup-config
wafs
write
copy sysreport
To copy system troubleshooting information from the device, use the copy sysreport EXEC command.
copy sysreport {disk filename | ftp {hostname | ip-address} remotedirectory remotefilename | tftp
{hostname | ip-address} remotefilename} [start-date {day month | month day} year [end-date
{day month | month day} year]]
Syntax Description
sysreport
|
Generates and saves a report containing WAAS system information in a file.
|
disk
|
Copies system information to a disk file.
|
filename
|
Name of the file to be created on disk. Note that .tar.gz is appended to the filename that you specify.
|
ftp
|
Copies system information to a FTP server.
|
hostname
|
Hostname of the FTP server.
|
ip-address
|
IP address of the FTP server.
|
remotedirectory
|
Remote directory where the system information file is to be created on the FTP server.
|
remotefilename
|
Remote filename of the system information file to be created on the FTP server.
|
tftp
|
Copies system information to a TFTP server.
|
hostname
|
Hostname of the TFTP server.
|
ip-address
|
IP address of the TFTP server.
|
remotefilename
|
Remote filename of the system information file to be created on the TFTP server. Use the complete pathname.
|
start-date
|
Start date of information in the generated system report.
|
day month
|
Start date day of the month (1-31) and month of the year (January, February, March, April, May, June, July, August, September, October, November, December). You can alternately specify the month first, followed by the day.
|
year
|
Start date year (1993-2035).
|
end-date
|
End date of information in the generated system report. If omitted, this date defaults to today's date. The report includes files through the end of this day.
|
day month
|
End date day of the month (1-31) and month of the year (January, February, March, April, May, June, July, August, September, October, November, December). You can alternately specify the month first, followed by the day.
|
year
|
End date year (1993-2035).
|
Defaults
If end-date is not specified, today's date 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 copies 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 copies system information by FTP to the file foo in the root directory of the FTP server named myserver:
WAE# copy sysreport ftp myserver / foo start-date 1 April 2006 end-date April 30 2006
Related Commands
show running-config
show startup-config
wafs
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 disk
|
Copies the system status to a disk file.
|
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
The copy system-status EXEC command creates a file on a SYSFS partition containing hardware and software status information.
Related Commands
install
reload
show running-config
show startup-config
wafs
write
copy tech-support
To copy the configuration or image data from the system to use when working with Cisco TAC, use the copy tech-support EXEC command.
copy tech-support {disk filename | tftp {hostname | ip-address} remotefilename}
Syntax Description
tech-support
|
Copies system information for technical support.
|
disk
|
Copies system information for technical support to disk file.
|
filename
|
Name of the file to be created on disk.
|
tftp
|
Copies system information for technical support to a TFTP server.
|
hostname
|
Hostname of the TFTP server.
|
ip-address
|
IP address of the TFTP server.
|
remotefilename
|
Remote filename of the system information file to be created on the TFTP server. Use the complete pathname.
|
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The copy tech-support tftp EXEC command can copy technical support information to a TFTP server or to a SYSFS partition.
Related Commands
install
reload
show running-config
show startup-config
wafs
write
copy tftp
To copy configuration or image data from a TFTP server, use the copy tftp EXEC command.
copy tftp {disk {hostname | ip-address} remotefilename localfilename | running-config
{hostname | ip-address} remotefilename | startup-config {hostname | ip-address}
remotefilename}
Syntax Description
tftp
|
Copies an image from a TFTP server.
|
disk
|
Copies an image from a TFTP server to a disk file.
|
hostname
|
Hostname of the TFTP server.
|
ip-address
|
IP address of the TFTP server.
|
remotefilename
|
Name of the remote image file to be copied from the TFTP server. Use the complete pathname.
|
localfilename
|
Name of the image file to be created on the local disk.
|
running-config
|
Copies an image from a TFTP server to the running configuration.
|
hostname
|
Hostname of the TFTP server.
|
ip-address
|
IP address of the TFTP server.
|
remotefilename
|
Name of the remote image file to be copied from the TFTP server. Use the complete pathname.
|
startup-config
|
Copies an image from a TFTP server to the startup configuration.
|
hostname
|
Hostname of the TFTP server.
|
ip-address
|
IP address of the TFTP server.
|
remotefilename
|
Name of the remote image file to be copied from the TFTP server. Use the complete pathname.
|
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The copy tftp disk EXEC command copies a file from a TFTP server to disk.
Related Commands
install
reload
show running-config
show startup-config
wafs
write
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
Use this EXEC command to create a copy of a file. Only SYSFS files can be copied.
Examples
The following example shows how to create a copy of a file.
WAE# cpfile fe511-194616.bin fd511-194618.bin
Related Commands
deltree
dir
lls
ls
mkdir
pwd
rename
debug
To monitor and record the WAAS application acceleration and the CIFS caching application functions, use the debug EXEC command. Use the no form of the command to disable debugging.
debug [option]
Note
We recommend that you use the debug command only at the direction of Cisco TAC. (For more information, see the "Obtaining Technical Assistance" section on page xvii.) The performance of the WAAS device degrades when you use the debug command.
Syntax Description
option
|
Specifies the debugger type; see the "" section for valid values.
|
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Note
The following debug command options are supported in the application-accelerator device mode only: dre, epm, print-spooler, tfo, wafs, and wccp.
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 Technical Assistance" section on page xvii.
Use the show debugging command to display enabled debug options.
Valid values for the option argument are as follows:
aaa accounting
|
Records AAA accounting actions.
|
all
|
Enables all debugging options.
|
authentication
print-services
user
|
Debugs authentication.
Debugs print services authentication.
Debugs the user login against the system authentication.
|
buf
all
dmbuf
dmsg
|
Debugs the buffer manager.
Debugs all buffer manager functions.
Debugs the buffer manager dmbuf.
Debugs the buffer manager dmsg.
|
cdp
adjacency
events
ip
packets
|
Records CDP information and actions.
Records the CDP neighbor.
Records the CDP events.
Records CDP IP.
Records the packet-related CDP.
|
cli
all
bin
parser
|
Debugs the CLI command.
Debugs all CLI commands.
Debugs the CLI command binary program.
Debugs the CLI command parser.
|
cms
|
Debugs the CMS.
|
dataserver
all
clientlib
server
|
Debugs the data server.
Debuts all data server functions.
Debugs the data server client library module.
Debugs the data server module.
|
dhcp
|
Debugs the DHCP.
|
dre
aggregation
all
cache
connection
aggregation acl
cache acl
core acl
message acl
misc acl
core
message
misc
|
Enables DRE debugging.
Enables DRE chunk-aggregation debugging.
Enables the debugging of all DRE commands.
Enables DRE cache debugging.
Enables DRE connection debugging.
Enables DRE chunk-aggregation debugging for a specified connection.
Enables DRE cache debugging for a specified connection.
Enables DRE core debugging for a specified connection.
Enables DRE message debugging for a specified connection.
Enables DRE other debugging for a specified connection.
Enables DRE core debugging.
Enables DRE message debugging.
Enables DRE other debugging.
|
emdb
level debug-level
|
Debugs the embedded database.
(Optional) Specifies the debug level (0 through 16).
|
logging
all
|
Debugs logging.
Debugs all logging functions.
|
ntp
|
Debugs NTP.
|
print-spooler
all
brief
errors
warnings
|
Debugs the print spooler feature.
(Optional) Debug the print spooler using all debug features.
(Optional) Debug the print spooler using only brief debug messages.
(Optional) Debug the print spooler using only the error conditions.
(Optional) Debug the print spooler using only the warning conditions.
|
rpc
detail
trace
|
Displays the remote procedure calls (RPC) logs.
Displays the RPC logs of priority "detail" level or higher.
Displays the RPC logs of priority "trace" level or higher.
|
stats
all
collection
computation
history
|
Debugs the statistics.
Debugs all statistics functions.
Debugs the statistics collection.
Debugs the statistics computation.
Debugs the statistics history.
|
tfo
buffer-mgr
connection
auto-discovery acl
comp-mgr acl
conn-mgr acl
filtering acl
netio-engine acl
policy-engine acl
stat-mgr
translog
|
Enables TFO debugging.
Enables TFO buffer manager debugging.
Enables TFO connection debugging.
Enables TFO connection debugging for the auto-discovery module.
Enables TFO connection debugging for the compression module.
Enables TFO connection debugging for the connection manager.
Enables TFO connection debugging for filtering module.
Enables TFO connection debugging for network input/output module.
Enables TFO connection debugging of application policies.
Enables TFO statistics manager debugging.
Enables TFO transaction log debugging.
|
wafs
all
core-fe
edge-fe
manager
utilities
|
Sets the notification level (debug, info, warn, error) at which messages from the WAAS software component and utilities are logged.
Sets the logging level for all software components and utilities at once.
Sets the logging level for the WAE that is acting as a core file engine.
Sets the logging level for WAE that is acting as an edge file engine.
Sets the logging level for the Device Manager.
Sets the logging level for WAAS utilities.
|
wccp
all
detail
error
events
keepalive
packets
slowstart
|
Debugs the WCCP information.
Debugs all WCCP functions.
Debugs the WCCP details.
Debugs the WCCP errors.
Debugs the WCCP events.
Debugs the WCCP keepalives that are sent to the applications.
Debugs the WCCP packet-related information.
Debugs the WCCP slow start.
|
Examples
The following example shows how to enable monitoring of user authentication, verify it is enabled, and then disable monitoring:
WAE# debug authentication user
Debug authentication (user) is ON
WAE# no debug authentication user
The following example shows how to set the logging level to debug for the Core WAEs in your system, then return the logging level to its default (info):
all log level for all components
core-fe log level for Core FE
edge-fe log level for Edge FE
manager log level for Manager
utilities log level for Utilities
WAE# debug wafs core-fe ?
debug set log level to DEBUG
error set log level to ERROR
info set log level to INFO (default)
warn set log level to WARN
WAE# debug wafs core-fe debug
corefe log level set to DEBUG
Note
If the watchdog utility is not running, the message "WAAS is not running" appears.
Related Commands
no debug
show debugging
undebug
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 this EXEC command to remove a file from a SYSFS partition on the disk drive of the WAAS device.
Examples
The following example deletes a temporary file from the /local1 directory using an absolute path.
WAE# delfile /local1/tempfile
Related Commands
cpfile
dir
lls
ls
mkdir
pwd
rename
deltree
To remove a directory along 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 this 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
Be sure you do not remove files or directories required for the WAAS device to function properly.
Examples
The following example deletes the testdir directory from the /local1 directory:
WAE# deltree /local1/testdir
Related Commands
cpfile
dir
lls
ls
mkdir
pwd
rename
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 this EXEC command to view a detailed list of files contained within the working directory, including names, sizes, and time created. The lls EXEC command produces the same output.
Examples
The following example displays a detailed list of all the files for the current directory:
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 displays only the detailed information for the logs directory:
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
lls
ls
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
The WAAS software CLI EXEC mode is used for setting, viewing, and testing system operations. It 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.
Password:
The disable command places you in the user-level EXEC shell (notice the prompt change).
Examples
The following example enters the user-level EXEC mode from the privileged EXEC mode:
Related Commands
enable
disk
To configure disks on a WAAS device, use the disk EXEC command.
disk delete-partitions diskname
disk mark diskname {bad | good}
disk reformat diskname
disk scan-errors diskname
delete-partitions
|
Deletes data on the specified disk drive. After using this command, the WAAS software treats the specified disk drive as blank. All previous data on the drive is inaccessible.
|
diskname
|
Name of the disk from which to delete partitions (disk00, disk01).
|
mark
|
Marks a disk drive as good or bad.
|
diskname
|
Name of the disk to be marked (disk00, disk01).
|
bad
|
Marks the specified disk drive as bad. Using this command makes data on this disk inaccessible. If later this disk is marked good, WAAS software treats it as a blank drive.
|
good
|
Marks the specified disk drive as good.
|
reformat
|
Performs a low-level reformatting of a SCSI disk drive and remaps bad sectors.
Caution  Use this command with extreme caution to avoid loss of data.
|
diskname
|
Name of the disk to be reformatted (disk00, disk01).
|
scan-errors
|
Scans SCSI or IDE disks for errors and remaps the bad sectors, if they are unused.
|
diskname
|
Name of the disk to be scanned for errors (disk00, disk01).
|
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
A WAAS device can use two disk drives for either storage capacity increase or for increased reliability. This is known as Redundant Array of Independent Disks (RAID) and is implemented in WAAS as a software feature.
RAID-1 is automatically applied to any WAAS device that is running the WAAS software and that have two or more disk drives. RAID-1 provides disk mirroring (data is written redundantly to two or more drives). The goal is higher reliability through redundancy. With RAID-1, file system write performance may be affected because each disk write must be executed against two disk drives.
RAID-1 (mirroring) is used for all file systems on the device. This setup ensures reliable execution of the software in all cases.
Note
The WAAS software uses the CONTENT file system for both the Wide Area File Services (WAFS) file system and the data redundancy elimination (DRE) cache.
Manually Marking and Unmarking WAE Disk Drives
A disk drive on a WAAS device can be marked as a good drive, one that is operating properly and being used, or as a bad drive, one that is not operating properly and will not be used after a reload command is executed.
The following scenario shows how to mark disk01 as bad, reload the WAAS device, and then mark disk01 as good so that it can be used again.
1.
Mark disk01 as bad by entering the disk mark EXEC command as follows:
WAE# disk mark disk01 bad
It will be not used after reload.
2.
Display the details about the disks by entering the show disks details EXEC command. Disk01 is now shown with an asterisk (*) because it was marked after the WAAS device was booted. Notice that Disk01 is reported as "Normal" (currently being used).
Physical disk information:
disk00: Normal (h00 c00 i00 l00 - DAS) 76324MB( 74.5GB)
disk01: Normal (h01 c00 i00 l00 - DAS) 76324MB( 74.5GB) (*)
(*) Disk drive won't be used after reload.
MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%
/ root /dev/root 34MB 28MB 6MB 82%
3.
Reload the WAAS device by entering the reload EXEC command. When asked, press Enter to proceed with the reload. After the WAAS device is reloaded, Disk01, which is marked as a bad disk drive, will not be used.
Proceed with reload?[confirm]
4.
After the reload is completed, display the details about the disks by entering the show disks details EXEC command. Disk01 is now shown as "Not used (*)" because Disk01 was detected as bad after the WAE was rebooted.
Physical disk information:
disk00: Normal (h00 c00 i00 l00 - DAS) 76324MB( 74.5GB)
(*) Disk drive won't be used after reload.
5.
Mark disk01 as good by entering the disk mark EXEC command.
WAE# disk mark disk01 good
disk01 is marked as good.
It will be used after reload.
6.
Verify that Disk01 is now marked as "Not used" by entering the show disks details EXEC command. Reload the WAAS device by entering the reload EXEC command. When asked, press Enter to proceed with the reload. After the WAAS device is reloaded, Disk01, which is marked as a good disk drive, will be used again. Use the show disks details EXEC command to verify the disk is operating normally.
Physical disk information:
disk00: Normal (h00 c00 i00 l00 - DAS) 76324MB( 74.5GB)
Proceed with reload?[confirm]
Physical disk information:
disk00: Normal (h00 c00 i00 l00 - DAS) 76324MB( 74.5GB)
disk01: Normal (h01 c00 i00 l00 - DAS) 76324MB( 74.5GB)
Reformatting a SCSI Disk Drive
Use the disk reformat EXEC command to reformat a SCSI disk drive on a WAAS device. The SCSI drive cannot be in use when you execute this command.
Caution 
To avoid loss of data, use this command with extreme caution.
Note
This command is only available on systems with SCSI drives: WAE-611 and WAE-7326.
The following scenario shows how to reformat a SCSI drive:
1.
Mark the SCSI drive as bad. In this example, it is disk01.
WAE# disk mark disk01 bad
2.
Reboot the WAAS device so that the bad disk is not in use.
3.
Reformat the disk. On completion of this command the drive is blank.
WAE# disk reformat disk01
4.
Reboot the WAAS device. Normal software RAID recovery is performed and the reformatted disk is prepared for use.
Removing All Disk Partitions on a Single Disk Drive
Use the disk delete-partitions EXEC command to remove all disk partitions on a single disk drive on WAAS device.
Caution 
After using the
disk delete-partitions EXEC command, the WAAS software treats the specified disk drive as blank. All previous data on the drive is inaccessible.
Use this command when you want to add a new disk drive that was previously used with another operating system (for example, a Microsoft Windows or Linux operating system). When asked if you want to erase everything on the disk, specify "yes" to proceed, as follows:
WAE# disk delete-partitions disk01
This will erase everything on disk. Are you sure? [no] yes
Related Commands
(config) disk
show disks
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
In the following three examples, 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:
official hostname: myhost.abc.com
official hostname: abc.com
official hostname: 10.0.11.0
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
The WAAS software CLI EXEC mode is used for setting, viewing, and testing system operations. It 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.
In TACACS+, there is an enable password feature that allows an administrator to define a different enable password per 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.
Password:
Note
This caveat applies 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:
Related Commands
disable
exit
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
This command is equivalent to the Ctrl-Z or the end command. The exit command issued in the user level EXEC shell terminates the console or Telnet session.
Examples
The following example terminates privileged-level EXEC mode and returns to the user-level EXEC mode:
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 | 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} | count reg-express filename | lineno reg-express
filename | match reg-express filename | nomatch reg-express filename | recursive reg-express
filename}
Syntax Description
binary
|
Does not suppress the binary output.
|
reg-express
|
Regular expression to be matched.
|
filename
|
Filename.
|
case
|
Matches case-sensitive pattern.
|
count
|
Prints the number of matching lines.
|
lineno
|
Prints the line number with output.
|
match
|
Prints the matching lines.
|
nomatch
|
Prints the nonmatching lines.
|
recursive
|
Searches a directory recursively.
|
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use this EXEC command to search for a particular regular expression pattern in a file.
Examples
The following example searches 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/
-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 searches a file for a pattern and prints 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/
-rw------- 1 admin root 101580800 Jan 11 12:01 /local/local1/core_dir/
core.cache.3.0.0.b131.cnbuild.15134
The following example searches a file for a pattern and prints the number of matching lines:
WAE# find-pattern count 10 removed_core
Related Commands
cd
dir
lls
ls
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 the output of the help EXEC command:
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.
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
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.
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 or local2. 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.
Examples
The following example loads the system image contained in the wae511-cache-300.bin file:
WAE# install wae511-cache-300.bin
Related Commands
copy disk
reload
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 an application that displays text files a 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:
•
Backward movement—LESS 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—LESS 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—LESS 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
To display the text of the syslog.txt file using the LESS application, enter the following command:
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
This command provides detailed information about files and subdirectories stored in the present working directory (including 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 provides a detailed list of the files in the current directory:
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
dir
lls
ls
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
To list the filenames and subdirectories within a particular directory, use the ls directory command; to list the filenames and subdirectories of the current working directory, use the ls command. To view the present working directory, use the pwd command.
Examples
The following example lists the files and subdirectories within the root directory:
Related Commands
dir
lls
pwd
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
Usage Guidelines
Use this EXEC command to create a new directory or subdirectory in the WAAS file system.
Examples
The following example creates a new directory, oldpaxfiles:
Related Commands
cpfile
dir
lls
ls
pwd
rename
rmdir
mkfile
To create a new file, use the mkfile EXEC command.
mkfile filename
Syntax Description
filename
|
Name of the file you want to create.
|
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use this EXEC command to create a new file in any directory of the WAAS device.
Examples
The following example creates a new file, traceinfo, in the root directory:
Related Commands
cpfile
dir
lls
ls
mkdir
pwd
rename
ntpdate
To set the software clock (time and date) on a WAAS device using a NTP server, use the ntpdate EXEC command.
ntpdate {hostname | ip-address}
Syntax Description
hostname
|
NTP hostname.
|
ip-address
|
NTP server IP address.
|
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use NTP to find the current time of day and set the current time on the WAAS device to match. The time must be saved to the hardware clock using the clock save command if it is to be restored after a reload.
Examples
The following example sets the software clock on the WAAS device using a NTP server:
Related Commands
clock
(config) clock
show clock
show ntp
no debug
To disable the display of debugging information on a WAAS device, use the no form of a debug command.
no debug command
Note
The following no debug command options are supported in the application-accelerator device mode only: dre, epm, print-spooler, tfo, wafs, and wccp.
Syntax Description
aaa accounting
|
Disables debugging of AAA accounting actions.
|
all
|
Disables all debugging options.
|
authentication
print-services
user
|
Disables authentication debugging.
Disables debugging of WAAS print services authentication.
Disables debugging of the user login against the system authentication.
|
buf
all
dmbuf
dmsg
|
Disables buffer manager debugging.
Disables debugging for all buffer manager functions.
Disables the buffer manager dmbuf debugging.
Debugs the buffer manager dmsg.
|
cdp
adjacency
events
ip
packets
|
Disables the debugging of CDP information and actions.
Disables debugging of CDP neighbor adjacency.
Disables debugging of the CDP events.
Disables debugging of CDP IP.
Disables debugging of packet-related CDP.
|
cli
all
bin
parser
|
Disables CLI command debugging.
Disables debugging of all CLI commands.
Disables debugging of the CLI command binary program.
Disables debugging of the CLI command parser.
|
cms
|
Disables the debugging of CMS.
|
dataserver
all
clientlib
server
|
Disables the debugging of the data server.
Disables the debugging of all data server functions.
Disables the debugging of the data server client library module.
Disables the debugging of the data server module.
|
dhcp
|
Disables the debugging of DHCP.
|
dre
aggregation
all
cache
connection
aggregation acl
cache acl
core acl
message acl
misc acl
core
message
misc
|
Disables DRE debugging.
Disables the debugging of DRE chunk-aggregation debugging.
Disables the debugging of all DRE commands.
Disables DRE cache debugging.
Disables DRE connection debugging.
Disables DRE chunk-aggregation debugging for a specified connection.
Disables DRE cache debugging for a specified connection.
Disables DRE core debugging for a specified connection.
Disables DRE message debugging for a specified connection.
Disables DRE other debugging for a specified connection.
Disables DRE core debugging.
Disables DRE message debugging.
Disables DRE other debugging.
|
emdb
|
Disables the debugging of the embedded database.
|
logging
all
|
Disables the debugging of logging.
Disables the debugging of all logging functions.
|
ntp
|
Disables the debugging of NTP.
|
print-spooler
all
brief
errors
warnings
|
Disables the debugging of the print spooler feature.
(Optional) Disables the debugging of the print spooler using all debug features.
(Optional) Disables the debugging of the print spooler using only brief debug messages.
(Optional) Disables the debugging of the print spooler using only the error conditions.
(Optional) Disables the debugging of the print spooler using only the warning conditions.
|
rpc
detail
trace
|
Disables the debugging of the remote procedure calls (RPC) logs.
Disables the debugging of the RPC logs of priority "detail" level or higher.
Disables the debugging of the RPC logs of priority "trace" level or higher.
|
stats
all
collection
computation
history
|
Disables the debugging of the statistics.
Disables the debugging of all statistics functions.
Disables the debugging of the statistics collection.
Disables the debugging of the statistics computation.
Disables the debugging of the statistics history.
|
tfo
buffer-mgr
connection
auto-discovery acl
comp-mgr acl
conn-mgr acl
filtering acl
netio-engine acl
policy-engine acl
stat-mgr
translog
|
Disables TFO debugging.
Disables TFO buffer manager debugging.
Disables TFO connection debugging.
Disables TFO connection debugging for the auto-discovery module.
Disables TFO connection debugging for the compression module.
Disables TFO connection debugging for the connection manager.
Disables TFO connection debugging for filtering module.
Disables TFO connection debugging for network input/output module.
Disables TFO connection debugging of application policies.
Disables TFO statistics manager debugging.
Disables TFO transaction log debugging.
|
wafs
all
core-fe
edge-fe
manager
utilities
|
Sets the notification level (debug, info, warn, error) at which messages from the WAAS software component and utilities are logged.
Sets the logging level for all software components and utilities at once.
Sets the logging level for WAEs acting as a core file engine.
Sets the logging level for WAEs acting as an edge file engine.
Sets the logging level for the Device Manager.
Sets the logging level for WAAS utilities.
|
wccp
all
detail
error
events
keepalive
packets
slowstart
|
Disables the debugging of WCCP.
Disables the debugging of all WCCP functions.
Disables the debugging of the WCCP details.
Disables the debugging of the WCCP errors.
Disables the debugging of the WCCP events.
Disables the debugging of the WCCP keepalives that are sent to the applications.
Disables the debugging of the WCCP packet-related information.
Disables the debugging of the WCCP slow start.
|
Defaults
No default behavior or values
Command Modes
global configuration
Device Modes
application-accelerator
central-manager
Examples
The following example disables monitoring of user authentication:
WAE# no debug authentication user
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 this command with the hostname argument, be sure that DNS functionality is configured the WAAS device. To force the timeout of a nonresponsive host, or to eliminate a loop cycle, press Ctrl-C.
Examples
The following example sends echo packets to a machine with address 172.19.131.189 to verify its availability on the network:
PING 172.19.131.189 (172.19.131.189) from 10.1.1.21 : 56(84) bytes of
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
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
Usage Guidelines
Use this EXEC command to display the present working directory of the WAAS device.
Examples
The following example displays the current working directory:
Related Commands
cd
dir
lls
ls
reload
To halt and perform a cold restart on a WAAS device, use the reload EXEC command.
reload [force]
Syntax Description
force
|
(Optional) Forces a reboot without further prompting.
|
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 restart. Any open connections are dropped after you issue this command, and the file system is reformatted upon restart.
To save any file system contents to disk from memory before a restart, use the cache synchronize command.
Examples
The following example halts operation of the WAAS device and reboots it with the configuration saved in flash memory. You are not prompted for confirmations during the process.
Related Commands
write
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 this command to rename any SYSFS file without making a copy of the file.
Examples
The following example renames the errlog.txt file to old_errlog.txt:
WAE# rename errlog.txt old_errlog.txt
Related Commands
cpfile
restore
To restore the device to its manufactured default status, removing user data from disk and flash memory, use the restore EXEC command. 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.
restore {factory-default [preserve basic-config] | rollback}
Syntax Description
factory-default
|
Resets the device configuration and data to their manufactured default status.
|
preserve
|
(Optional) Preserves certain configurations and data on the device.
|
basic-config
|
(Optional) Selects basic network configurations.
|
rollback
|
Roll back configuration to the last functional software and device configuration.
|
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use this EXEC command to restore data on 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.
Backing up the Central Manager Database
Be sure to back up the WAAS Central Manager database and copy the backup file to a safe location that is separate from that of the WAAS Central Manager, or change over from the primary to a standby WAAS Central Manager before you use the restore factory-default command on your primary WAAS Central Manager. You must halt the operation of the WAAS Central Manager before you enter the backup and restore commands.
Caution 
This command erases user-specified configuration information stored in the flash image, removes data on disk, user-defined disk partitions, and the entire Central Manager database. User-defined disk partitions that are removed include the SYSFS, WAAS, and PRINTSPOOLFS partitions. The configuration being removed includes the starting configuration of the device.
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 simply 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 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
While WAFS to WAAS migration is supported, rollback from WAAS to WAFS is not supported.
Examples
The following two examples illustrate the results of using 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 IP address, hostname, and name server) at this point, or later through entries in the command-line interface.
In the following example, entering the show disks details command after the restore command is used verifies that the restore command has removed data from the partitioned file systems: SYSFS, WAAS, and PRINTSPOOLFS.
Physical disk information:
disk00: Normal (h00 c00 i00 l00 - DAS) 140011MB(136.7GB)
disk01: Normal (h00 c00 i01 l00 - DAS) 140011MB(136.7GB)
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%
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 first example below, 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 final example shows that the software is rolled back to version X (using the restore rollback command), and the software is reloaded again.
WAE# copy ftp install server path waas.versionY.bin
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
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 pending
Cisco Wide Area Application Services Software (WAAS)
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
reload
show disks
show running-config
show startup-config
show version
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 this EXEC command to remove any directory from the WAAS file system. The rmdir command only removes empty directories.
Examples
The following example deletes the oldfiles directory from the local1 directory:
WAE# rmdir /local1/oldfiles
Related Commands
cpfile
dir
lls
ls
mkdir
pwd
rename
scp
To copy files between network hosts, use the scp command. This command uses SSH for transferring data between hosts.
scp [1][2][4][6][B][C][p][q][r][v] [c cipher] [F config-file] [i id-file] [l limit]
[o ssh_option] [P port] [S program] [[user @] host : file] [...] [[user-n @] host-n : file-n]
Syntax Description
1
|
(Optional) Forces this command to use protocol 1.
|
2
|
(Optional) Forces this command to use protocol 2.
|
4
|
(Optional) Forces this command to use only IPv4 addresses.
|
6
|
(Optional) Forces this command to use only IPv6 addresses.
|
B
|
(Optional) Specifies the batch mode. In this mode, the scp command does not ask for passwords or passphrases.
|
C
|
(Optional) Enables compression. The scp command passes this option to the ssh command to enable compression.
|
p
|
(Optional) Preserves the following information from the source file: modification times, access times, and modes.
|
q
|
(Optional) Disables the display of progress information.
|
r
|
(Optional) Recursively copies directories and their contents.
|
v
|
(Optional) Specifies the verbose mode. Causes the scp and ssh commands to print debugging messages about their progress. This option can be helpful when troubleshooting connection, authentication, and configuration problems.
|
c
|
(Optional) Specifies the cipher to use for encrypting the data being copied. The scp command directly passes this option to the ssh command.
|
cipher
|
The cipher to use for encrypting the data being copied.
|
F
|
(Optional) Specifies an alternative per-user configuration file for Secure Shell (SSH). The scp command directly passes this option to the ssh command.
|
config-file
|
Name of the configuration file.
|
i
|
(Optional) Specifies the file containing the private key for RSA authentication. The scp command directly passes this information to the ssh command.
|
id-file
|
The name of the file containing the private key for RSA authentication.
|
l
|
(Optional) Limits the use of bandwidth.
|
limit
|
The bandwidth to use for copying files in kbps.
|
o
|
(Optional) Passes options to the ssh command in the format used in ssh_config5.
|
ssh_option
|
See the ssh command for more information about the possible options.
|
P
|
(Optional) Specifies the port to connect to on the remote host.
|
port
|
The port to connect to on the remote host.
|
S
|
(Optional) Specifies the program to use for the encrypted connection.
|
program
|
Name of the program to use for the encrypted connection.
|
user
|
(Optional) Username.
|
host
|
(Optional) Hostname.
|
file
|
(Optional) Name of the file to copy.
|
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
The scp command prompts you for passwords or passphrases when needed for authentication.
Related Commands
ssh
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 checks 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, and disk configuration) on the WAAS device, use the setup EXEC command. You can also use the setup EXEC command to complete basic configuration after upgrading to WAAS software.
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 the first screen of the wizard when you enter the setup EXEC command on a WAAS device that is running the WAAS software:
Please choose an interface to configure from the following list:
Press the ESC key at any time to quit this session
show aaa accounting
To display the AAA accounting configuration information for a WAAS device, use the show aaa accounting EXEC command.
show aaa accounting
This command displays configuration information for the following AAA accounting types:
•
Exec shell
•
Command (for normal users and superusers)
•
System
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
Use this EXEC command to display configuration information for the following AAA accounting types:
•
Exec shell
•
Command (for normal users and superusers)
•
System
Examples
The following example displays the current AAA configuration:
Accounting Type Record event(s) Protocol
----------------------------------------------------
Exec shell start-stop tacacs
Command level 0 stop-only tacacs
Command level 15 disabled
Related Commands
(config) aaa accounting
show alarms
To display information on various types of alarms, their status, and history on a WAAS device, use the show alarms EXEC command.
show alarms [critical [detail [support]] | detail [support]] | history [[start_num [end_num [detail
[support]] | detail [support]] | critical [start_num [end_num [detail [support]] | detail
[support]]] | detail [support] | major [start_num [end_num [detail [support]] | detail
[support]]]] | [minor [start_num [end_num [detail [support]]] | detail [support]]]] |
major [detail [support]] | minor [detail [support]] | status]
Syntax Description
critical
|
(Optional) Displays critical alarm information.
|
detail
|
(Optional) Displays detailed information for each alarm.
|
support
|
(Optional) Displays additional information about each alarm.
|
history
|
(Optional) Displays information about the history of various alarms.
|
start_num
|
(Optional) Alarm number that appears first in the alarm history.
|
end_num
|
(Optional) Alarm number that appears last in the alarm history.
|
major
|
(Optional) Displays information about major alarms.
|
minor
|
(Optional) Displays information about minor alarms.
|
status
|
(Optional) Displays the status of various alarms and alarm overload settings.
|
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 (for example, the CIFS service) 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."
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 WAAS software are:
•
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 which 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 which 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 WAAS software on the WAAS device. The WAAS software retains the last 100 alarm raise and clear events only.
Use the show alarm status EXEC command to display the status of current alarms, and the WAAS device's alarm overload status and alarm overload configuration.
Examples
The following sample output for the show alarm history command displays all major alarms generated on the WAAS device since the last software reload:
Op Sev Alarm ID Module/Submodule Instance
-- --- -------------------- -------------------- --------------------
1 C Ma tfo_accl_wellness sysmon accl=CIFS
2 C Cr wafs_edge_down wafs
3 R Ma tfo_accl_wellness sysmon accl=CIFS
4 R Cr wafs_edge_down wafs
5 R Ma core_dump sysmon core
Op - Operation: R-Raised, C-Cleared
Sev - Severity: Cr-Critical, Ma-Major, Mi-Minor
The following sample output of the show alarm history command displays the complete details of alarms 1 through 3 in the alarm history event record:
WAE# show alarms history 1 3 detail support
Op Sev Alarm ID Module/Submodule Instance
-- --- -------------------- -------------------- --------------------
1 C Ma tfo_accl_wellness sysmon accl=CIFS
Apr 12 20:25:58.119 UTC, Processing Error Alarm, #000003, 1000:445005
The CIFS TFO Accelerator application has had a keepalive failure.
Its wellness is in question.
/alm/maj/sysmon/accl=XXXX/tfo_accl_wellness:
A TFO Accelerator application has had a keepalive failure.
The System Monitor issues this to indicate that one of the
TFO Accelerators is failing to perform a wellness update
within the allotted time. The implications are that some
connections may not be optimized properly by TFO and thus
optimization performance may be reduced.
Examine the status of the specified accelerator to verify it
is still operating properly and make adjustments to return
it to full health if necessary.
2 C Cr wafs_edge_down wafs
Apr 12 20:25:30.756 UTC, Processing Error Alarm, #000002, 10000:1000001
/alm/crit/wafs/wafs_edge_down:
This alarm is used to check if the Edge is working.
Please reactivate the Edge component on the device.
3 R Ma tfo_accl_wellness sysmon accl=CIFS
Apr 12 20:24:43.127 UTC, Processing Error Alarm, #000003, 1000:445005
The CIFS TFO Accelerator application has had a keepalive failure.
Its wellness is in question.
/alm/maj/sysmon/accl=XXXX/tfo_accl_wellness:
A TFO Accelerator application has had a keepalive failure.
The System Monitor issues this to indicate that one of the
TFO Accelerators is failing to perform a wellness update
within the allotted time. The implications are that some
connections may not be optimized properly by TFO and thus
optimization performance may be reduced.
Examine the status of the specified accelerator to verify it
is still operating properly and make adjustments to return
it to full health if necessary.
Op - Operation: R-Raised, C-Cleared
Sev - Severity: Cr-Critical, Ma-Major, Mi-Minor
This sample output for the show alarm status command displays the status of critical, major, and minor alarms and the alarm overload status and alarm overload configuration on the WAAS device.
Overall Alarm Status : Major
Device is NOT in alarm overload state.
Device enters alarm overload state @ 10 alarms/sec.
Device exits alarm overload state @ 1 alarms/sec.
Overload detection is ENABLED.
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
Examples
The following example shows the ARP table:
Protocol Address Flags Hardware Addr Type Interface
Internet 10.56.40.17 Adj 00:06:5B:FE:4D:05 ARPA GigabitEthernet1/0
Internet 10.56.40.2 Adj 00:0F:F8:A0:9F:8A ARPA GigabitEthernet1/0
Internet 10.56.40.1 Adj 00:00:0C:07:AC:01 ARPA GigabitEthernet1/0
The show arp command displays the Internet-to-Ethernet address translation tables of the Address Resolution Protocol. Without flags, the current ARP entry for the host name is displayed.
The following table describes the fields shown in the show arp display.
Field
|
Description
|
Protocol
|
Type of protocol.
|
Address
|
IP address of the host name.
|
Flags
|
Current ARP flag status.
|
Hardware Addr
|
Hardware IP address given as six hexadecimal bytes separated by colons.
|
Type
|
Type of wide-area network.
|
Interface
|
Name and slot/port information for the interface.
|
show authentication
To display the authentication configuration for a WAAS device, use the show authentication EXEC command.
show authentication {print-services | user | content-request}
Syntax Description
print-services
|
Displays authentication configuration for WAAS print services.
|
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
The WAAS software supports print service request authentication through the Windows domain server. A print service request authenticates the domain and password of a user with a preconfigured Windows domain server before allowing requests from the user to be served by the WAAS device. To display the authentication for a print services request, use the show authentication print-services EXEC command. To view user authorization for print services, use the show print-services admin-group EXEC command.
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.
Examples
To display the current administrative login authentication and authorization (authentication configuration) on a WAAS device, use the show authentication user EXEC command. The sample output shows the authentication and authorization schemes (for example, local, RADIUS, TACACS+, or Windows domain) that the WAAS device is configured to use to authenticate and authorize administrative login requests.
WAE# show authentication user
Login Authentication: Console/Telnet/Ftp/SSH Session
----------------------------- ------------------------------
Configuration Authentication: Console/Telnet/Ftp/SSH Session
----------------------------- ------------------------------
The following example displays the authentication and authorization information for WAAS print services:
WAE# show authentication print-services
Windows domain server authenticates the Print Services
WAE# show print-services admin-group
There is no configured administrator group for print-services.
The following example displays the content request authentication configuration information in the disconnected mode:
WAE# show authentication content-request
The content request authentication in disconnected mode is disabled
Related Commands
(config) authentication
clear
show statistics authentication
show auto-register
To display the status of a WAE's automatic registration feature, 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
The following example displays the status of the automatic registration feature of a WAE:
Auto registration is disabled.
Related Commands
(config) auto-register
show bypass
To display static bypass configuration information for a WAE, use the show bypass EXEC command.
show bypass list
Syntax Description
list
|
Bypass list entries. Maximum of 50.
|
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
Usage Guidelines
The maximum number of static bypass entries is 50.
Examples
The following example displays a list of entries in the bypass list:
172.16.11.11:0 any-server:0 static-config
any-client:0 172.31.23.23:0 static-config
Related Commands
(config) bypass
show cdp
To display CDP configuration information, use the show cdp EXEC command.
show cdp [entry neighbor [protocol | version [protocol]] | holdtime | interface [FastEthernet
slot/port | GigabitEthernet slot/port] | neighbors [detail | FastEthernet slot/port [detail] |
GigabitEthernet slot/port [detail]] | run | timer | traffic]
Syntax Description
entry
|
(Optional) Displays information for a specific neighbor entry.
|
neighbor
|
Name of CDP neighbor entry.
|
protocol
|
(Optional) CDP protocol information.
|
version
|
(Optional) CDP version.
|
holdtime
|
(Optional) Displays length of time that CDP information is held by neighbors.
|
interface
|
(Optional) Displays interface status and configuration.
|
FastEthernet
|
(Optional) Displays Fast Ethernet configuration.
|
slot/port
|
Fast Ethernet slot (0-3) and port number.
|
GigabitEthernet
|
(Optional) Displays Gigabit Ethernet configuration.
|
slot/port
|
Gigabit Ethernet slot (1-2) and port number.
|
neighbors
|
(Optional) Displays CDP neighbor entries.
|
detail
|
(Optional) Displays detailed neighbor entry information.
|
FastEthernet
|
(Optional) Displays neighbor Fast Ethernet information.
|
slot/port
|
Neighbor Fast Ethernet slot (0-3) and port number.
|
detail
|
Detailed neighbor Fast Ethernet network information.
|
GigabitEthernet
|
(Optional) Displays neighbor Gigabit Ethernet information.
|
slot/port
|
Neighbor Gigabit Ethernet slot (1-2) and port number.
|
detail
|
(Optional) Detailed Gigabit Ethernet neighbor network information.
|
run
|
(Optional) Displays the CDP process status.
|
timer
|
(Optional) Displays the time when CDP information is resent to neighbors.
|
traffic
|
(Optional) Displays CDP statistical information.
|
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
The following examples display CDP information regarding 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:
Sending CDP packets every 60 seconds
Sending a holdtime value of 180 seconds
Sending CDPv2 advertisements is not enabled
WAE# show cdp interface gigabitethernet 1/0
GigabitEthernet1/0 is up, line protocol is up
Sending CDP packets every 60 seconds
WAE# show cdp neighbors gigabitethernet 1/0 detail
Device ID: actona-core1-6513(L)
Platform: cisco WS-C6513, Capabilities: Router Switch IGMP
Interface: GigabitEthernet1/0, Port ID (outgoing port): GigabitEthernet5/30
Cisco Internetwork Operating System Software
IOS (tm) c6sup2_rp Software (c6sup2_rp-PS-M), Version 12.1(26)E, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Fri 24-Dec-04 08:02
VTP Management Domain: 'actona'
Total packets Output: 188242, Input: 186151
Hdr syntax: 0, Chksum error: 0, Encaps failed: 0
No memory: 0, Invalid packet: 0, Fragmented: 0
CDP version 1 advertisements Output: 188242, Input: 93072
CDP version 2 advertisements Output: 0, Input: 93079
Related Commands
(config) cdp
(config-if) cdp
clear
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
detail
|
(Optional) Displays detailed information; indicates the clock source (NTP) and the current summer time setting (if any).
|
standard-timezones
|
(Optional) Displays information about the standard time zones.
|
all
|
Displays all of the standard time zones (approximately 1500 time zones). Each time zone is listed on a separate line.
|
details
|
Displays detailed information for the specified time zone.
|
timezone
|
Name of the time zone.
|
regions
|
Displays the region name of all the standard time zones. All 1500 time zones are organized into directories by region.
|
zones
|
Displays the name of every time zone that is within the specified region.
|
region-name
|
Name of the region.
|
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 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 a standard time zone is configured. You can only configure summertime 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. This enables you to 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.
Examples
The following example shows date and time information, such as day of the week, month, time (hh:mm:ss), and year in local time relative to Israeli Standard Time (UTC plus two hours):
Local time: Wed Apr 6 20:03:56 IST 2005
The following example shows optional detailed date and time information, including local time relative to UTC. In addition to the information shown in the previous example, show clock detail provides the UTC offset, and the local time zone.
Local time: Wed Apr 6 20:10:40 IST 2005
UTC time: Wed Apr 6 18:10:40 UTC 2005
Epoch: 1112811040 seconds
UTC offset: 7200 seconds (2 hours 0 minutes)
The following example shows an excerpt of the output from the show clock standard-timezones all EXEC command. A partial list is shown. Each time zone is listed on a separate line.
WAE # show clock standard-timezones all
.
The following example shows an excerpt of the output from the show clock standard-timezones region EXEC command. As the example shows, all first level time zone names or directories are listed. All 1500 time zones are organized into directories by region.
WAE # show clock standard-timezones regions
The following example shows an excerpt of the output from the show clock standard-timezones zones EXEC command. As the following example shows, this command lists the name of every time zone that is within the specified region (for example, the US region).
WAE # show clock standard-timezones zones US
The following sample shows an excerpt of the output from the show clock standard-timezones details EXEC command. The time zone is case-sensitive. As the following example shows, this command shows details about the specified time zone (for example, the US/Eastern time zone). The command output also includes the standard offset from the GMT.
WAE # show clock standard-timezones details US/Eastern
US/Eastern is standard timezone.
Getting offset information (may take a while) ...
Standard offset from GMT is -300 minutes (-5 hour(s)).
It has built-in summertime.
Summer offset from GMT is -240 minutes. (-4 hour(s)).
Related Commands
clock
(config) clock
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 | processes}
Syntax Description
database
|
Displays embedded database maintenance information.
|
content
|
Writes the database content to a file.
|
dump
|
Dumps all database content to a text file.
|
filename
|
Name of the file to be saved under local1 directory.
|
text
|
Writes the database content to a file in text format.
|
xml
|
Writes the database content to a file in XML format.
|
info
|
Displays CMS application information.
|
processes
|
Displays CMS application processes.
|
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
The following two examples show the result of using the show cms info command on a WAAS device:
Current CDM role = Primary
CMS services information :
Service cms_httpd is running
Service cms_cdm is running
The following example shows the CMS application processes:
Service cms_httpd running
The following example writes the database content to a file in text format:
WAE# show cms database content text
Database content can be found in /local1/cms-db-12-12-2002-17:06:08:070.txt.
The following example writes the database content to a file in XML format:
WAE# show cms database content xml
Database content can be found in /local1/cms-db-12-12-2002-17:07:11:629.xml.
Related Commands
cms
(config) cms
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.
Usage Guidelines
This command displays only the type of debugging enabled, not the specific subset of the command.
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
In the following 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:
WAE# debug tfo buffer-mgr
WAE# debug tfo connection
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
Related Commands
debug
undebug
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.
|
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Usage Guidelines
In the WAAS software release and later releases, you must deploy the WAAS Central Manager on a dedicated appliance. The device mode feature allows you to deploy a WAAS device as either a WAAS Central Manager or a WAE. Because you must deploy a WAAS Central Manager on a dedicated appliance, a WAAS device can only operate in one device mode; either in central-manager mode or application-acclerator mode.
If the configured and current device modes differ, a reload is required for the configured device mode to take effect.
Examples
To display the current device mode of a WAAS device, enter the show device mode EXEC command:
WAE# show device mode
To display the current mode in which the WAAS device is operating, enter the show device-mode current EXEC command:
WAE# show device-mode current
Current device mode: application-accelerator
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:
WAE# show device-mode configured
Configured device mode: central-manager
Related Commands
(config) device mode
show disks
To view information about a WAAS device's disks, use the show disks EXEC command.
show disks {details | failed-sectors [disk_name] | SMART-info [details]}
Syntax Description
details
|
Displays currently effective configurations with more details.
|
failed-sectors
|
Displays a list of failed sectors on all disks.
|
disk_name
|
(Optional) Name of the disk for which failed sectors are displayed (disk00 or disk01).
|
SMART-info
|
Displays hard drive diagnostic information and information about impending disk failures.
|
details
|
(Optional) Displays more detailed SMART disk monitoring information.
|
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. Enter the show disks failed-sectors EXEC command to display a list of failed sectors on all disk drives.
WAE# show disks failed-sectors
To display a list of failed sectors for a only a specific disk drive, specify the name of the disk when entering the show disks failed-sectors command. The following example shows how to display a list of failed sectors for disk01:
WAE# show disks failed-sectors disk01
If there are disk failures, a message is displayed, notifying you about this situation when you log in.
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 or SCSI disk drives) 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 SMART-info EXEC command. To display more detailed SMART information, enter the show disks SMART-info details EXEC command. The output from the show tech-support EXEC command also includes SMART information.
Examples
In the following example, enter the show disks details EXEC command to display detailed information about the current disk configuration on the WAAS device:
Physical disk information:
disk00: Normal (h00 c00 i00 l00 - DAS) 140011MB(136.7GB)
disk01: Normal (h00 c00 i01 l00 - DAS) 140011MB(136.7GB)
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%
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 the output of the show disks SMART-info EXEC command:
WAEA# show disks SMART-info
Device: IBM-ESXS ST3146707LW FN Version: B26B
Serial number: 3KS2YL00000000000CM3
Transport protocol: Parallel SCSI (SPI-4)
Local Time is: Fri Mar 31 13:06:08 2006 UTC
Device supports SMART and is Enabled
Temperature Warning Enabled
Device: IBM-ESXS ST3146707LW FN Version: B26B
Serial number: 3KS1ZTRH00000000CK61
Transport protocol: Parallel SCSI (SPI-4)
Local Time is: Fri Mar 31 13:06:08 2006 UTC
Device supports SMART and is Enabled
Temperature Warning Enabled
The following example displays more detailed SMART output from the show disks SMART-info details EXEC command:
WAE# show disks SMART-info details
Device: IBM-ESXS ST3146707LW FN Version: B26B
Serial number: 3KS2YL94000000000CM3
Transport protocol: Parallel SCSI (SPI-4)
Local Time is: Fri Mar 31 13:06:53 2006 UTC
Device supports SMART and is Enabled
Temperature Warning Enabled
Current Drive Temperature: 33 C
Drive Trip Temperature: 65 C
Vendor (Seagate) cache information
Blocks sent to initiator = 4048936465
Blocks received from initiator = 100130496
Blocks read from cache and sent to initiator = 56503638
Number of read and write commands whose size <= segment size = 10124024
Number of read and write commands whose size > segment size = 0
Errors Corrected Total Total Correction Gigabytes Tot
delay: [rereads/ errors algorithm processed unc
Related Commands
disk
(config) disk
show tech-support
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
The following example displays flash memory information. Note that a new software image has been downloaded, but not yet deployed.
WAAS software version (disk-based code): WAAS-4.0.0-b340
System image: 107 sectors
Bootloader, rescue image, and other reserved areas: 24 sectors
256 sectors total, 125 sectors free.
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
Examples
The following example 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:
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
Compiled 17:26:17 Mar 25 2006 by cnbuild
System was restarted on Mon Mar 27 15:25:01 2006.
The system has been up for 3 days, 21 hours, 15 minutes, 13 seconds.
CPU 0 is GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz (rev 4) running at 3002M
2048 Mbytes of Physical memory.
1 CD ROM drive (HL-DT-ST GCR-8240N)
2 GigabitEthernet interfaces
Manufactured As: WAE-611-K9 [8836PBN]
Related Commands
show hardware
show version
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
Examples
The following show hosts example lists the name servers and their corresponding IP addresses. It also lists the host names, their corresponding IP addresses, and their corresponding aliases (if applicable) in a host table summary:
hostname inet address aliases
-------- ------------ -------
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 status for the tftp service, but you can ignore this line because tftp is not supported on WAAS.
Examples
The following example displays the enabled or disabled status of TCP/IP services on the WAAS device:
Inetd service configurations:
Related Commands
(config) inetd
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 | PortChannel port-num | scsi
device_num | Standby group_num | usb}
Syntax Description
GigabitEthernet
|
Displays the Gigabit Ethernet interface device information (only on suitably equipped systems).
|
slot/port
|
Slot and port number for the Gigabit Ethernet interface. The slot range is 0-3; the port range is 0-3. The slot number and port number are separated with a forward slash character (/).
|
ide
|
Displays the IDE interface device information.
|
control_num
|
IDE controller number (0-1).
|
PortChannel
|
Displays the port channel interface device information.
|
port-num
|
Port number for the port channel interface (1-2).
|
scsi
|
Displays the SCSI interface device information.
|
device_num
|
SCSI device number (0-7).
|
Standby
|
Displays the standby group information.
|
group_num
|
Standby group number (1-4).
|
usb
|
Displays the USB interface device information.
|
Defaults
No default behavior or values
Command Modes
EXEC
Device Modes
application-accelerator
central-manager
Examples
The following example displays information for the Gigabit Ethernet interface slot 1/port 0 configured on the WAAS device:
WAE# show interface GigabitEthernet 1/0
Ethernet address:00:0D:60:84:30:84
Internet address:10.56.41.180
Broadcast address:10.56.43.255
Maximum Transfer Unit Size:1500
Packets Received: 49288883
Input Packets Overruns: 0
Output Packets Dropped: 0
Output Packets Overruns: 0
Output Packets Carrier: 0
Flags:UP BROADCAST RUNNING MULTICAST
Mode: autoselect, full-duplex, 1000baseTX
The following example displays information for the port channel interface configured on the WAAS device:
waas-cm# show interface PortChannel 1
Interface PortChannel 1 (0 physical interface(s)):
Ethernet address:00:00:00:00:00:00
Maximum Transfer Unit Size:1500
Input Packets Overruns: 0
Output Packets Dropped: 0
Output Packets Overruns: 0
Output Packets Carrier: 0
Flags:BROADCAST MASTER MULTICAST
The following example displays information for the SCSI interface configured on the WAAS device:
waas-cm# show interface scsi 1
SCSI interface 0: LSI Chip sym00c000, device id 0xc, revision id 0x2
The following example displays information for the standby interface on the WAAS device:
WAE# show interface Standby 4
Description: This is an interface that acts as a backup
IP address: 10.10.10.4, netmask: 255.0.0.0
Related Commands
(config) interface
show running-config
show startup-config
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. Typically, a WAAS device contains the following three identification items, which make up the UDI:
•
Product ID (PID)
•
Version ID (VID)
•
Serial number (SN)
This identity information is stored in the WAAS device's nonvolatile memory.
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 WAAS device's nonvolatile memory 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's UDI.
Examples
The following example shows the inventory information for a WAE model WAE-511:
PID: WAE-511-K9 VID: 0 SN: serial_number
In the preceding example, serial number is the serial number of the WAE. The version ID is displayed as "0" because the version number is not available.
Related Commands
show tech-support
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
acl-name
|
(Optional) Displays information for a specific access list, using an alphanumeric identifier up to 30 characters, beginning with a letter.
|
acl-num
|
(Optional) Displays information for a specific access list, using a numeric identifier (0-99 for standard access lists and100-199 for extended access lists).
|
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
The following example shows sample output from the show ip access-list command:
492 access list conditions
Standard IP access list 1
1 permit 10.1.1.2
(implicit deny any: 2 matches)
Extended IP access list 100
1 permit tcp host 10.1.1.1 any
2 permit tcp host 10.1.1.2 any
3 permit tcp host 10.1.1.3 any
(implicit fragment permit: 0 matches)
(implicit deny ip any any: 0 matches)
Standard IP access list test
1 permit 1.1.1.1 (10 matches)
(implicit deny: 2 matches)
Interface access list references:
GigabitEthernet 1/0 inbound 100
Application access list references:
The following shows sample output from the show ip access-list command for the access list named test:
WAE# show ip access-list test
Standard IP access list test
1 permit 1.1.1.1 (10 matches)
(implicit deny: 2 matches)
Note
The system displays the number of packets that have matched a condition statement only if the number is greater than zero.
Related Commands
clear
(config) ip access-list
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
Examples
The following example displays the IP routing table:
Destination Gateway Netmask
---------------- ---------------- ----------------
10.56.41.180 0.0.0.0 255.255.255.255
192.168.12.180 0.0.0.0 255.255.255.255
192.168.12.0 0.0.0.0 255.255.255.0
10.56.40.0 0.0.0.0 255.255.252.0
0.0.0.0 10.56.40.1 0.0.0.0
Number of route cache entries: 183
Related Commands
(config) ip
(config-if) ip
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
Usage Guidelines
You can 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 example displays the Kerberos authentication configuration on a WAAS device:
Realm for DNS suffix: WAE.ABC.COM
Name of host running KDC for realm:
Related Commands
clear
(config) logging
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
You can 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 example displays the syslog host configuration on a WAAS device:
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
clear
(config) logging
show sysfs
show memory
To display memory blocks and statistics for a WAAS device, use the show memory