Cisco Wide Area Application Services Command Reference (Software Versions 4.0.1 and 4.0.3) - Exec Mode Commands [Cisco Wide Area Application Services (WAAS) Software] (2024)

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:

WAE> enable

WAE#

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

WAE# exit

WAE>

cd

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

cd directoryname

Syntax Description

Defaults

No default behavior or values

Command Modes

EXEC

application-accelerator

central-manager

Usage Guidelines

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

Examples

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

WAE(config)# cd local1

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

WAE(config)# cd /local1

Related Commands

deltree

dir

lls

ls

mkdir

pwd

clear

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

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE#clear logging

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

Defaults

No default behavior or values

Command Modes

EXEC

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

Defaults

No default behavior or values

Command Modes

EXEC

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

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:

WAE# configure 

WAE(config)# 

Related Commands

(config) end

(config) exit

show running-config

show startup-config

copy cdrom

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

copy cdrom install filedir filename

Syntax Description

Defaults

No default behaviors or values

Command Modes

EXEC

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

Defaults

No default behaviors or values

Command Modes

EXEC

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

Defaults

No default behaviors or values

Command Modes

EXEC

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

Defaults

No default behaviors or values

Command Modes

EXEC

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:

WAE# reload

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

Sending:USER biff

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

2000) ready.

Password required for biff.

Sending:PASS ***** 

User biff logged in.

Sending:TYPE I

Type set to I.

Sending:PASV

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

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

CWD command successful.

Sending PASV

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

Sending:RETR WAAS-4.0.0-k9.bin

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

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

writing flash component:

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

The new software will run after you reload.

The following example shows how to upgrade the BIOS. All output is written to a separate file (/local1/.bios_upgrade.txt) for traceability. The hardware 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

Sending:USER myusername

upgradeserver.cisco.com FTP server (Version wu-2.6.1-18) ready.

Password required for myusername.

Sending:PASS ********

Please read the file README_dotfiles

 it was last modified on Wed Feb 19 16:10:26 2005- 94 days ago

Please read the file README_first

 it was last modified on Wed Feb 19 16:05:29 2005- 94 days ago

User myusername logged in.

Sending:TYPE I

Type set to I.

Sending:PASV

Entering Passive Mode (128,107,193,240,57,37)

Sending:CWD /bios/update53/derived/

CWD command successful.

Sending PASV

Entering Passive Mode (128,107,193,240,146,117)

Sending:RETR 7326_bios.bin

Opening BINARY mode data connection for 7326_bios.bin (834689 bytes).

Fri Jan 7 15:29:07 UTC 2005

BIOS installer running!

Do not turnoff the system till BIOS installation is complete.

Flash chipset:Macronix 29LV320B

0055000.FLS:280000 [80000]

Erasing block 2f:280000 - 28ffff

Erasing block 30:290000 - 29ffff

Erasing block 31:2a0000 - 2affff

Erasing block 32:2b0000 - 2bffff

Erasing block 33:2c0000 - 2cffff

Erasing block 34:2d0000 - 2dffff

Erasing block 35:2e0000 - 2effff

Erasing block 36:2f0000 - 2fffff

Programming block 2f:280000 - 28ffff

Programming block 30:290000 - 29ffff

Programming block 31:2a0000 - 2affff

Programming block 32:2b0000 - 2bffff

Programming block 33:2c0000 - 2cffff

Programming block 34:2d0000 - 2dffff

Programming block 35:2e0000 - 2effff

Programming block 36:2f0000 - 2fffff

SCSIROM.BIN:260000 [20000]

Erasing block 2d:260000 - 26ffff

Erasing block 2e:270000 - 27ffff

Programming block 2d:260000 - 26ffff

Programming block 2e:270000 - 27ffff

PXEROM.BIN:250000 [10000]

Erasing block 2c:250000 - 25ffff

Programming block 2c:250000 - 25ffff

Primary BIOS flashed successfully

Cleanup BIOS related files that were downloaded....

The new software will run after you reload.

WAE-7326#

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

Defaults

HTTP server port: 80

Command Modes

EXEC

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:

WAE# reload

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

Sending:USER biff

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

2000) ready.

Password required for biff.

Sending:PASS ***** 

User biff logged in.

Sending:TYPE I

Type set to I.

Sending:PASV

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

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

CWD command successful.

Sending PASV

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

Sending:RETR WAAS-4.0.0-k9.bin

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

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

writing flash component:

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

The new software will run after you reload.

The following example shows how to upgrade the BIOS. All output is written to a separate file (/local1/.bios_upgrade.txt) for traceability. The hardware 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

Sending:USER myusername

upgradeserver.cisco.com FTP server (Version wu-2.6.1-18) ready.

Password required for myusername.

Sending:PASS ********

Please read the file README_dotfiles

 it was last modified on Wed Feb 19 16:10:26 2005- 94 days ago

Please read the file README_first

 it was last modified on Wed Feb 19 16:05:29 2005- 94 days ago

User myusername logged in.

Sending:TYPE I

Type set to I.

Sending:PASV

Entering Passive Mode (128,107,193,240,57,37)

Sending:CWD /bios/update53/derived/

CWD command successful.

Sending PASV

Entering Passive Mode (128,107,193,240,146,117)

Sending:RETR 7326_bios.bin

Opening BINARY mode data connection for 7326_bios.bin (834689 bytes).

Fri Jan 7 15:29:07 UTC 2005

BIOS installer running!

Do not turnoff the system till BIOS installation is complete.

Flash chipset:Macronix 29LV320B

0055000.FLS:280000 [80000]

Erasing block 2f:280000 - 28ffff

Erasing block 30:290000 - 29ffff

Erasing block 31:2a0000 - 2affff

Erasing block 32:2b0000 - 2bffff

Erasing block 33:2c0000 - 2cffff

Erasing block 34:2d0000 - 2dffff

Erasing block 35:2e0000 - 2effff

Erasing block 36:2f0000 - 2fffff

Programming block 2f:280000 - 28ffff

Programming block 30:290000 - 29ffff

Programming block 31:2a0000 - 2affff

Programming block 32:2b0000 - 2bffff

Programming block 33:2c0000 - 2cffff

Programming block 34:2d0000 - 2dffff

Programming block 35:2e0000 - 2effff

Programming block 36:2f0000 - 2fffff

SCSIROM.BIN:260000 [20000]

Erasing block 2d:260000 - 26ffff

Erasing block 2e:270000 - 27ffff

Programming block 2d:260000 - 26ffff

Programming block 2e:270000 - 27ffff

PXEROM.BIN:250000 [10000]

Erasing block 2c:250000 - 25ffff

Programming block 2c:250000 - 25ffff

Primary BIOS flashed successfully

Cleanup BIOS related files that were downloaded....

The new software will run after you reload.

Related Commands

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

Defaults

No default behaviors or values

Command Modes

EXEC

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

Defaults

No default behaviors or values

Command Modes

EXEC

application-accelerator

central-manager

Usage Guidelines

The copy startup-config EXEC command copies the startup configuration file to a TFTP server or to a SYSFSpartition.

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

Defaults

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

Command Modes

EXEC

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

Defaults

No default behaviors or values

Command Modes

EXEC

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

Defaults

No default behaviors or values

Command Modes

EXEC

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

Defaults

No default behaviors or values

Command Modes

EXEC

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

Defaults

No default behavior or values

Command Modes

EXEC

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 pagexvii.) The performance of the WAAS device degrades when you use the debug command.

Syntax Description

Defaults

No default behavior or values

Command Modes

EXEC

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 pagexvii.

Use the show debugging command to display enabled debug options.

Valid values for the option argument are as follows:

Examples

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

WAE# debug authentication user

WAE# show debugging

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):

WAE# debug wafs ?

 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

Defaults

No default behavior or values

Command Modes

EXEC

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

Defaults

No default behavior or values

Command Modes

EXEC

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

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE# dir  

size time of last change name

------------- ------------------------- -----------

 4096 Fri Feb 24 14:40:00 2006 <DIR> actona

 4096 Tue Mar 28 14:42:44 2006 <DIR> core_dir

 4096 Wed Apr 12 20:23:10 2006 <DIR> crash

 4506 Tue Apr 11 13:52:45 2006 dbupgrade.log

 4096 Tue Apr 4 22:50:11 2006 <DIR> downgrade

 4096 Sun Apr 16 09:01:56 2006 <DIR> errorlog

 4096 Wed Apr 12 20:23:41 2006 <DIR> logs

 16384 Thu Feb 16 12:25:29 2006 <DIR> lost+found

 4096 Wed Apr 12 03:26:02 2006 <DIR> sa

 24576 Sun Apr 16 23:38:21 2006 <DIR> service_logs

 4096 Thu Feb 16 12:26:09 2006 <DIR> spool

 9945390 Sun Apr 16 23:38:20 2006 syslog.txt

 10026298 Thu Apr 6 12:25:00 2006 syslog.txt.1

 10013564 Thu Apr 6 12:25:00 2006 syslog.txt.2

 10055850 Thu Apr 6 12:25:00 2006 syslog.txt.3

 10049181 Thu Apr 6 12:25:00 2006 syslog.txt.4

 4096 Thu Feb 16 12:29:30 2006 <DIR> var

 508 Sat Feb 25 13:18:35 2006 wdd.sh.signed

The following example displays only the detailed information for the logs directory:

WAE# dir logs

size time of last change name

------------- ------------------------- -----------

 4096 Thu Apr 6 12:13:50 2006 <DIR> actona

 4096 Mon Mar 6 14:14:41 2006 <DIR> apache

 4096 Sun Apr 16 23:36:40 2006 <DIR> emdb

 4096 Thu Feb 16 11:51:51 2006 <DIR> export

 92 Wed Apr 12 20:23:20 2006 ftp_export.status

 4096 Wed Apr 12 20:23:43 2006 <DIR> rpc_httpd

 0 Wed Apr 12 20:23:41 2006 snmpd.log

 4096 Sun Mar 19 18:47:29 2006 <DIR> tfo

Related Commands

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

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.

WAE>enable

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:

WAE# disable

WAE>

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

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

disk01 is marked as 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).

WAE#show disks details 

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.

Mounted filesystems:

 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.

WAE#reload 

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.

WAE#show disks details

Physical disk information:

 disk00: Normal (h00 c00 i00 l00 - DAS) 76324MB( 74.5GB)

 disk01: Not used

(*) 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.

WAE#show disks details

Physical disk information:

disk00: Normal (h00 c00 i00 l00 - DAS) 76324MB( 74.5GB)

disk01: Not used

...

WAE#reload 

Proceed with reload?[confirm]

...

WAE#show disks details

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.

WAE#reload

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.

WAE#reload

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

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE# dnslookup myhost

official hostname: myhost.abc.com

 address: 172.31.69.11

WAE# dnslookup abc.com

official hostname: abc.com

 address: 192.168.219.25

WAE# dnslookup 10.0.11.0

official hostname: 10.0.11.0

 address: 10.0.11.0

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

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.

WAE>enable

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:

WAE> enable

WAE#

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

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:

WAE# exit

WAE>

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

Defaults

No default behavior or values

Command Modes

EXEC

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/

core.3.0.0.b5.eh.2796

-rw------- 1 admin root 97054720 Jan 11 11:31 /local/local1/core_dir/

core.cache.3.0.0.b131.cnbuild.14086

-rw------- 1 admin root 96845824 Jan 11 11:32 /local/local1/core_dir/

core.cache.3.0.0.b131.cnbuild.14823

-rw------- 1 admin root 101580800 Jan 11 12:01 /local/local1/core_dir/

core.cache.3.0.0.b131.cnbuild.15134

-rw------- 1 admin root 96759808 Jan 11 12:59 /local/local1/core_dir/

core.cache.3.0.0.b131.cnbuild.20016

-rw------- 1 admin root 97124352 Jan 11 13:26 /local/local1/core_dir/

core.cache.3.0.0.b131.cnbuild.8095

The following example 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/

core.3.0.0.b5.eh.2796

-rw------- 1 admin root 101580800 Jan 11 12:01 /local/local1/core_dir/

core.cache.3.0.0.b131.cnbuild.15134

The following example searches a file for a pattern and prints the number of matching lines:

WAE# find-pattern count 10 removed_core

3

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

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:

WAE# help

Help may be requested at any point in a command by entering a question mark '?'. If nothing matches, the help list will be empty and you must backup until entering a '?' shows the available options.

Two styles of help are provided:

1. Full help is available when you are ready to enter a command argument.

2. Partial help is provided when an abbreviated argument is entered.

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

Defaults

No default behavior or values

Command Modes

EXEC

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

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE# less syslog.txt

lls

To view a long list of directory names, use the lls EXEC command.

lls [directory]

Syntax Description

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE# lls 

size time of last change name

-------------- ------------------------- -----------

 4096 Fri Feb 24 14:40:00 2006 <DIR> actona

 4096 Tue Mar 28 14:42:44 2006 <DIR> core_dir

 4096 Wed Apr 12 20:23:10 2006 <DIR> crash

 4506 Tue Apr 11 13:52:45 2006 dbupgrade.log

 4096 Tue Apr 4 22:50:11 2006 <DIR> downgrade

 4096 Sun Apr 16 09:01:56 2006 <DIR> errorlog

 4096 Wed Apr 12 20:23:41 2006 <DIR> logs

 16384 Thu Feb 16 12:25:29 2006 <DIR> lost+found

 4096 Wed Apr 12 03:26:02 2006 <DIR> sa

 24576 Sun Apr 16 23:54:30 2006 <DIR> service_logs

 4096 Thu Feb 16 12:26:09 2006 <DIR> spool

 9951236 Sun Apr 16 23:54:20 2006 syslog.txt

 10026298 Thu Apr 6 12:25:00 2006 syslog.txt.1

 10013564 Thu Apr 6 12:25:00 2006 syslog.txt.2

 10055850 Thu Apr 6 12:25:00 2006 syslog.txt.3

 10049181 Thu Apr 6 12:25:00 2006 syslog.txt.4

 4096 Thu Feb 16 12:29:30 2006 <DIR> var

 508 Sat Feb 25 13:18:35 2006 wdd.sh.signed

Related Commands

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

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE# ls

actona

core_dir

crash

dbupgrade.log

downgrade

errorlog

logs

lost+found

sa

service_logs

spool

syslog.txt

syslog.txt.1

syslog.txt.2

syslog.txt.3

syslog.txt.4

var

wdd.sh.signed

Related Commands

dir

lls

pwd

mkdir

To create a directory, use the mkdir EXEC command.

mkdir directory

Syntax Description

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE# mkdir /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

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE# mkfile traceinfo

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

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE# ntpdate 10.11.23.40

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

Defaults

No default behavior or values

Command Modes

global configuration

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

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE# ping 172.19.131.189

PING 172.19.131.189 (172.19.131.189) from 10.1.1.21 : 56(84) bytes of

data.

64 bytes from 172.19.131.189: icmp_seq=0 ttl=249 time=613 usec

64 bytes from 172.19.131.189: icmp_seq=1 ttl=249 time=485 usec

64 bytes from 172.19.131.189: icmp_seq=2 ttl=249 time=494 usec

64 bytes from 172.19.131.189: icmp_seq=3 ttl=249 time=510 usec

64 bytes from 172.19.131.189: icmp_seq=4 ttl=249 time=493 usec

--- 172.19.131.189 ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max/mdev = 0.485/0.519/0.613/0.047 ms

WAE#

pwd

To view the present working directory on a WAAS device, use the pwd EXEC command.

pwd

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

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:

WAE# pwd

/local1

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

Defaults

No default behavior or values

Command Modes

EXEC

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.

WAE# reload force

Related Commands

write

rename

To rename a file on a WAAS device, use the rename EXEC command.

rename oldfilename newfilename

Syntax Description

Defaults

No default behavior or values

Command Modes

EXEC

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

Defaults

No default behavior or values

Command Modes

EXEC

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.

WAE# show disks details

Physical disk information:

 disk00: Normal (h00 c00 i00 l00 - DAS) 140011MB(136.7GB)

 disk01: Normal (h00 c00 i01 l00 - DAS) 140011MB(136.7GB)

Mounted filesystems:

 MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%

 / root /dev/root 35MB 30MB 5MB 85%

 /swstore internal /dev/md1 991MB 333MB 658MB 33%

 /state internal /dev/md2 3967MB 83MB 3884MB 2%

 /disk00-04 CONTENT /dev/md4 122764MB 33MB 122731MB 0%

 /local/local1 SYSFS /dev/md5 3967MB 271MB 3696MB 6%

 .../local1/spool PRINTSPOOL /dev/md6 991MB 16MB 975MB 1%

 /sw internal /dev/md0 991MB 424MB 567MB 42%

Software RAID devices:

 DEVICE NAME TYPE STATUS PHYSICAL DEVICES AND STATUS

 /dev/md0 RAID-1 NORMAL OPERATION disk00/00[GOOD] disk01/00[GOOD]

 /dev/md1 RAID-1 NORMAL OPERATION disk00/01[GOOD] disk01/01[GOOD]

 /dev/md2 RAID-1 NORMAL OPERATION disk00/02[GOOD] disk01/02[GOOD]

 /dev/md3 RAID-1 NORMAL OPERATION disk00/03[GOOD] disk01/03[GOOD]

 /dev/md4 RAID-1 NORMAL OPERATION disk00/04[GOOD] disk01/04[GOOD]

 /dev/md5 RAID-1 NORMAL OPERATION disk00/05[GOOD] disk01/05[GOOD]

 /dev/md6 RAID-1 NORMAL OPERATION disk00/06[GOOD] disk01/06[GOOD]

Currently content-filesystems RAID level is not configured to change.

The following example shows how to upgrade or restore an older version of the WAAS software. In the 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

WAE#show version

Cisco Wide Area Application Services Software (WAAS)

Copyright (c) 1999-2006 by Cisco Systems, Inc.

Cisco Wide Area Application Services Software Release 4.0.0 (build b340 Mar 25 2

006)

Version: fe611-4.0.0.340

Compiled 17:26:17 Mar 25 2006 by cnbuild

System was restarted on Mon Mar 27 15:25:02 2006.

The system has been up for 3 days, 21 hours, 9 minutes, 17 seconds.

WAE#show version last

Nothing is displayed.

WAE#show version pending

WAAS 4.0.1 Version Y

WAE#reload

...... reloading ......

WAE#show version

Cisco Wide Area Application Services Software (WAAS)

...

WAE#restore rollback

WAE#reload

...... reloading ......

Because flash memory configurations were removed after the restore command was used, the show startup-config command does not return any flash memory data. The show running-config command returns the default running configurations.

Related Commands

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

Defaults

No default behavior or values

Command Modes

EXEC

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

Command Modes

EXEC

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

Defaults

No default behavior or values

Command Modes

EXEC

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

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:

WAE# setup

Please choose an interface to configure from the following list:

1: GigabitEthernet 1/0

2: GigabitEthernet 2/0

Enter choice:

.

.

.

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

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:

WAE# show aaa accounting

Accounting Type Record event(s) Protocol

----------------------------------------------------

Exec shell start-stop tacacs

Command level 0 stop-only tacacs

Command level 15 disabled 

System start-stop tacacs

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

Defaults

No default behavior or values.

Command Modes

EXEC

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:

WAE# show alarms history

 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.

 Explanation:

 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.

 Action:

 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

 WAFS Edge is down.

 /alm/crit/wafs/wafs_edge_down:

 WAFS Edge is down.

 Explanation:

 This alarm is used to check if the Edge is working.

 Action:

 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.

 Explanation:

 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.

 Action:

 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.

WAE# show alarms status

Critical Alarms : 0

Major Alarms : 1

Minor Alarms : 0

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

application-accelerator

central-manager

Examples

The following example shows the ARP table:

WAE# show arp

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.

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

s

Defaults

No default behavior or values

Command Modes

EXEC

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

----------------------------- ------------------------------

local enabled (primary)

Windows domain disabled