Feedback
Table Of Contents
show policy-engine application
show statistics authentication
show statistics content-distribution-network
show statistics dre connection
show statistics windows-domain
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> enableWAE#To leave EXEC mode, use the exit command at the system prompt:
WAE# exitWAE>cd
To change from one directory to another directory in the WAAS software, use the cd EXEC command.
cd directoryname
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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 local1The following example shows how to change to a directory using an absolute path:
WAE(config)# cd /local1Related Commands
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
Device Modesapplication-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 clearedThe 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 loggingIn the following example, all authentication, RADIUS and TACACS+ information is cleared on the WAAS device:
WAE# clear statistics radiusWAE# clear statistics tacacsWAE# clear statistics authenticationIn the following example, all entries in the Windows domain log file are cleared on the WAAS device:
WAE# clear windows-domain-logRelated Commands
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
Device Modesapplication-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 2005Related Commands
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
Device Modesapplication-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:
•
•
The naming convention for backup files includes the time stamp.
Note
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 backupcreating 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 validateManagement tables are validRelated Commands
configure
To enter global configuration mode, use the configure EXEC command. You must be in global configuration mode to enter global configuration commands.
configure
To exit global configuration mode, use the end or exit commands. You can also press Ctrl-Z to exit from global configuration mode.
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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# configureWAE(config)#Related Commands
copy cdrom
To copy software release files from a CD-ROM, use the copy cdrom EXEC command.
copy cdrom install filedir filename
Syntax Description
cdrom
Copies a file from the CD-ROM.
install
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 Modesapplication-accelerator
central-manager
Related Commands
copy compactflash
To copy software release files from a CompactFlash card, use the copy compactflash EXEC command.
copy compactflash install filename
Syntax Description
compactflash
Copies a file from the CompactFlash card.
install
Installs a software release file.
filename
Image filename.
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Related Commands
copy disk
To copy the configuration or image data from a disk to a remote location using FTP or to the startup configuration, use the copy disk EXEC command.
copy disk {ftp {hostname | ip-address} remotefiledir remotefilename localfilename | startup-config filename}
Syntax Description
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modesapplication-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
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
Device Modesapplication-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:
•
•
•
–
–
–
Caution
Caution
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.binAfter the BIOS update file is copied to your system, use the reload EXEC command to reboot as follows:
WAE# reloadThe 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.binEnter username for remote ftp server:biffEnter password for remote ftp server:*****Initiating FTP download...printing one # per 1MB downloadedSending:USER biff10.1.1.1 FTP server (Version) Mon Feb 28 10:30:36 EST2000) ready.Password required for biff.Sending:PASS *****User biff logged in.Sending:TYPE IType set to I.Sending:PASVEntering Passive Mode (128,107,193,244,55,156)Sending:CWD //ftp-sj.cisco.com/cisco/waas/4.0CWD command successful.Sending PASVEntering Passive Mode (128,107,193,244,55,156)Sending:RETR WAAS-4.0.0-k9.binOpening 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.binEnter username for remote ftp server:myusernameEnter password for remote ftp server:*****Initiating FTP download...printing one # per 1MB downloadedSending:USER myusernameupgradeserver.cisco.com FTP server (Version wu-2.6.1-18) ready.Password required for myusername.Sending:PASS ********Please read the file README_dotfilesit was last modified on Wed Feb 19 16:10:26 2005- 94 days agoPlease read the file README_firstit was last modified on Wed Feb 19 16:05:29 2005- 94 days agoUser myusername logged in.Sending:TYPE IType set to I.Sending:PASVEntering Passive Mode (128,107,193,240,57,37)Sending:CWD /bios/update53/derived/CWD command successful.Sending PASVEntering Passive Mode (128,107,193,240,146,117)Sending:RETR 7326_bios.binOpening BINARY mode data connection for 7326_bios.bin (834689 bytes).Fri Jan 7 15:29:07 UTC 2005BIOS installer running!Do not turnoff the system till BIOS installation is complete.Flash chipset:Macronix 29LV320B0055000.FLS:280000 [80000]Erasing block 2f:280000 - 28ffffErasing block 30:290000 - 29ffffErasing block 31:2a0000 - 2affffErasing block 32:2b0000 - 2bffffErasing block 33:2c0000 - 2cffffErasing block 34:2d0000 - 2dffffErasing block 35:2e0000 - 2effffErasing block 36:2f0000 - 2fffffProgramming block 2f:280000 - 28ffffProgramming block 30:290000 - 29ffffProgramming block 31:2a0000 - 2affffProgramming block 32:2b0000 - 2bffffProgramming block 33:2c0000 - 2cffffProgramming block 34:2d0000 - 2dffffProgramming block 35:2e0000 - 2effffProgramming block 36:2f0000 - 2fffffSCSIROM.BIN:260000 [20000]Erasing block 2d:260000 - 26ffffErasing block 2e:270000 - 27ffffProgramming block 2d:260000 - 26ffffProgramming block 2e:270000 - 27ffffPXEROM.BIN:250000 [10000]Erasing block 2c:250000 - 25ffffProgramming block 2c:250000 - 25ffffPrimary BIOS flashed successfullyCleanup BIOS related files that were downloaded....The new software will run after you reload.WAE-7326#Related Commands
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
Device Modesapplication-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:
•
•
•
–
–
–
Caution
Caution
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# reloadThe 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.binEnter username for remote ftp server:biffEnter password for remote ftp server:*****Initiating FTP download...printing one # per 1MB downloadedSending:USER biff10.1.1.1 FTP server (Version) Mon Feb 28 10:30:36 EST2000) ready.Password required for biff.Sending:PASS *****User biff logged in.Sending:TYPE IType set to I.Sending:PASVEntering Passive Mode (128,107,193,244,55,156)Sending:CWD //ftp-sj.cisco.com/cisco/waas/4.0CWD command successful.Sending PASVEntering Passive Mode (128,107,193,244,55,156)Sending:RETR WAAS-4.0.0-k9.binOpening 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.binEnter username for remote ftp server:myusernameEnter password for remote ftp server:*****Initiating FTP download...printing one # per 1MB downloadedSending:USER myusernameupgradeserver.cisco.com FTP server (Version wu-2.6.1-18) ready.Password required for myusername.Sending:PASS ********Please read the file README_dotfilesit was last modified on Wed Feb 19 16:10:26 2005- 94 days agoPlease read the file README_firstit was last modified on Wed Feb 19 16:05:29 2005- 94 days agoUser myusername logged in.Sending:TYPE IType set to I.Sending:PASVEntering Passive Mode (128,107,193,240,57,37)Sending:CWD /bios/update53/derived/CWD command successful.Sending PASVEntering Passive Mode (128,107,193,240,146,117)Sending:RETR 7326_bios.binOpening BINARY mode data connection for 7326_bios.bin (834689 bytes).Fri Jan 7 15:29:07 UTC 2005BIOS installer running!Do not turnoff the system till BIOS installation is complete.Flash chipset:Macronix 29LV320B0055000.FLS:280000 [80000]Erasing block 2f:280000 - 28ffffErasing block 30:290000 - 29ffffErasing block 31:2a0000 - 2affffErasing block 32:2b0000 - 2bffffErasing block 33:2c0000 - 2cffffErasing block 34:2d0000 - 2dffffErasing block 35:2e0000 - 2effffErasing block 36:2f0000 - 2fffffProgramming block 2f:280000 - 28ffffProgramming block 30:290000 - 29ffffProgramming block 31:2a0000 - 2affffProgramming block 32:2b0000 - 2bffffProgramming block 33:2c0000 - 2cffffProgramming block 34:2d0000 - 2dffffProgramming block 35:2e0000 - 2effffProgramming block 36:2f0000 - 2fffffSCSIROM.BIN:260000 [20000]Erasing block 2d:260000 - 26ffffErasing block 2e:270000 - 27ffffProgramming block 2d:260000 - 26ffffProgramming block 2e:270000 - 27ffffPXEROM.BIN:250000 [10000]Erasing block 2c:250000 - 25ffffProgramming block 2c:250000 - 25ffffPrimary BIOS flashed successfullyCleanup BIOS related files that were downloaded....The new software will run after you reload.Related Commands
copy running-config
To copy a configuration or image data from the current configuration, use the copy running-config EXEC command.
copy running-config {disk filename | startup-config | tftp {hostname | ip-address} remotefilename}
Syntax Description
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modesapplication-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
copy startup-config
To copy configuration or image data from the startup configuration, use the copy startup-config EXEC command.
copy startup-config {disk filename | running-config | tftp {hostname | ip-address} remotefilename}
Syntax Description
Defaults
No default behaviors or values
Command Modes
EXEC
Device Modesapplication-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
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
Device Modesapplication-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 2006The 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 2006Related Commands
copy system-status
To copy status information from the system for debugging, use the copy system-status EXEC command.
copy system-status disk filename
Syntax Description
system-status 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 Modesapplication-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
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
Device Modesapplication-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
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
Device Modesapplication-accelerator
central-manager
Usage Guidelines
The copy tftp disk EXEC command copies a file from a TFTP server to disk.
Related Commands
cpfile
To make a copy of a file, use the cpfile EXEC command.
cpfile oldfilename newfilename
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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.binRelated Commands
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
Syntax Description
option
Specifies the debugger type; see the "" section for valid values.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Note
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:
Examples
The following example shows how to enable monitoring of user authentication, verify it is enabled, and then disable monitoring:
WAE# debug authentication userWAE# show debuggingDebug authentication (user) is ONWAE# no debug authentication userThe 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 componentscore-fe log level for Core FEedge-fe log level for Edge FEmanager log level for Managerutilities log level for UtilitiesWAE# debug wafs core-fe ?debug set log level to DEBUGerror set log level to ERRORinfo set log level to INFO (default)warn set log level to WARNWAE# debug wafs core-fe debugcorefe log level set to DEBUG
Note
Related Commands
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
Device Modesapplication-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/tempfileRelated Commands
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
Device Modesapplication-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
Examples
The following example deletes the testdir directory from the /local1 directory:
WAE# deltree /local1/testdirRelated Commands
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
Device Modesapplication-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# dirsize time of last change name------------- ------------------------- -----------4096 Fri Feb 24 14:40:00 2006 <DIR> actona4096 Tue Mar 28 14:42:44 2006 <DIR> core_dir4096 Wed Apr 12 20:23:10 2006 <DIR> crash4506 Tue Apr 11 13:52:45 2006 dbupgrade.log4096 Tue Apr 4 22:50:11 2006 <DIR> downgrade4096 Sun Apr 16 09:01:56 2006 <DIR> errorlog4096 Wed Apr 12 20:23:41 2006 <DIR> logs16384 Thu Feb 16 12:25:29 2006 <DIR> lost+found4096 Wed Apr 12 03:26:02 2006 <DIR> sa24576 Sun Apr 16 23:38:21 2006 <DIR> service_logs4096 Thu Feb 16 12:26:09 2006 <DIR> spool9945390 Sun Apr 16 23:38:20 2006 syslog.txt10026298 Thu Apr 6 12:25:00 2006 syslog.txt.110013564 Thu Apr 6 12:25:00 2006 syslog.txt.210055850 Thu Apr 6 12:25:00 2006 syslog.txt.310049181 Thu Apr 6 12:25:00 2006 syslog.txt.44096 Thu Feb 16 12:29:30 2006 <DIR> var508 Sat Feb 25 13:18:35 2006 wdd.sh.signedThe following example displays only the detailed information for the logs directory:
WAE# dir logssize time of last change name------------- ------------------------- -----------4096 Thu Apr 6 12:13:50 2006 <DIR> actona4096 Mon Mar 6 14:14:41 2006 <DIR> apache4096 Sun Apr 16 23:36:40 2006 <DIR> emdb4096 Thu Feb 16 11:51:51 2006 <DIR> export92 Wed Apr 12 20:23:20 2006 ftp_export.status4096 Wed Apr 12 20:23:43 2006 <DIR> rpc_httpd0 Wed Apr 12 20:23:41 2006 snmpd.log4096 Sun Mar 19 18:47:29 2006 <DIR> tfoRelated Commands
disable
To turn off privileged EXEC commands, use the disable EXEC command.
disable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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> enablePassword:
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# disableWAE>Related Commands
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
Command Modes
EXEC
Device Modesapplication-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
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.
WAE# disk mark disk01 baddisk01 is marked as bad.It will be not used after reload.2.
WAE# show disks detailsPhysical 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.
WAE# reloadProceed with reload?[confirm]...4.
WAE# show disks detailsPhysical disk information:disk00: Normal (h00 c00 i00 l00 - DAS) 76324MB( 74.5GB)disk01: Not used(*) Disk drive won't be used after reload....5.
WAE# disk mark disk01 gooddisk01 is marked as good.It will be used after reload.6.
WAE# show disks detailsPhysical disk information:disk00: Normal (h00 c00 i00 l00 - DAS) 76324MB( 74.5GB)disk01: Not used...WAE# reloadProceed with reload?[confirm]...WAE# show disks detailsPhysical 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
Note
The following scenario shows how to reformat a SCSI drive:
1.
WAE# disk mark disk01 bad2.
WAE# reload3.
WAE# disk reformat disk014.
WAE# reloadRemoving 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
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 disk01This will erase everything on disk. Are you sure? [no] yesRelated Commands
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
Device Modesapplication-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 myhostofficial hostname: myhost.abc.comaddress: 172.31.69.11WAE# dnslookup abc.comofficial hostname: abc.comaddress: 192.168.219.25WAE# dnslookup 10.0.11.0official hostname: 10.0.11.0address: 10.0.11.0enable
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 Modesapplication-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> enablePassword:
Note
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> enableWAE#Related Commands
exit
To terminate privileged-level EXEC mode and return to the user-level EXEC mode, use the exit command.
exit
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
All modes
Device Modesapplication-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# exitWAE>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
Device Modesapplication-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.8095The following example searches a file for a pattern and prints the matching lines:
WAE# find-pattern match 10 removed_coreTue 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.15134The following example searches a file for a pattern and prints the number of matching lines:
WAE# find-pattern count 10 removed_core3Related Commands
help
To obtain online help for the command-line interface, use the help EXEC command.
help
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC and global configuration
Device Modesapplication-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:
•
•
Examples
The following example shows the output of the help EXEC command:
WAE# helpHelp 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
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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
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.binRelated Commands
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
Device Modesapplication-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:
•
•
•
Examples
To display the text of the syslog.txt file using the LESS application, enter the following command:
WAE# less syslog.txtlls
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
Device Modesapplication-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# llssize time of last change name-------------- ------------------------- -----------4096 Fri Feb 24 14:40:00 2006 <DIR> actona4096 Tue Mar 28 14:42:44 2006 <DIR> core_dir4096 Wed Apr 12 20:23:10 2006 <DIR> crash4506 Tue Apr 11 13:52:45 2006 dbupgrade.log4096 Tue Apr 4 22:50:11 2006 <DIR> downgrade4096 Sun Apr 16 09:01:56 2006 <DIR> errorlog4096 Wed Apr 12 20:23:41 2006 <DIR> logs16384 Thu Feb 16 12:25:29 2006 <DIR> lost+found4096 Wed Apr 12 03:26:02 2006 <DIR> sa24576 Sun Apr 16 23:54:30 2006 <DIR> service_logs4096 Thu Feb 16 12:26:09 2006 <DIR> spool9951236 Sun Apr 16 23:54:20 2006 syslog.txt10026298 Thu Apr 6 12:25:00 2006 syslog.txt.110013564 Thu Apr 6 12:25:00 2006 syslog.txt.210055850 Thu Apr 6 12:25:00 2006 syslog.txt.310049181 Thu Apr 6 12:25:00 2006 syslog.txt.44096 Thu Feb 16 12:29:30 2006 <DIR> var508 Sat Feb 25 13:18:35 2006 wdd.sh.signedRelated Commands
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
Device Modesapplication-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# lsactonacore_dircrashdbupgrade.logdowngradeerrorloglogslost+foundsaservice_logsspoolsyslog.txtsyslog.txt.1syslog.txt.2syslog.txt.3syslog.txt.4varwdd.sh.signedRelated Commands
mkdir
To create a directory, use the mkdir EXEC command.
mkdir directory
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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 /oldpaxfilesRelated Commands
mkfile
To create a new file, use the mkfile EXEC command.
mkfile filename
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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 traceinfoRelated Commands
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
Device Modesapplication-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.40Related Commands
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
Syntax Description
Defaults
No default behavior or values
Command Modes
global configuration
Device Modesapplication-accelerator
central-manager
Examples
The following example disables monitoring of user authentication:
WAE# no debug authentication userping
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
Device Modesapplication-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.189PING 172.19.131.189 (172.19.131.189) from 10.1.1.21 : 56(84) bytes ofdata.64 bytes from 172.19.131.189: icmp_seq=0 ttl=249 time=613 usec64 bytes from 172.19.131.189: icmp_seq=1 ttl=249 time=485 usec64 bytes from 172.19.131.189: icmp_seq=2 ttl=249 time=494 usec64 bytes from 172.19.131.189: icmp_seq=3 ttl=249 time=510 usec64 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 lossround-trip min/avg/max/mdev = 0.485/0.519/0.613/0.047 msWAE#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 Modesapplication-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/local1Related Commands
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
Device Modesapplication-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 forceRelated Commands
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
Device Modesapplication-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.txtRelated Commands
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
Device Modesapplication-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
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
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-defaultThis command will wipe out all of data on the disksand 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 servicesbefore this command is run.Are you sure you want to go ahead?[yes/no]WAE# restore factory-default preserve basic-configThis command will wipe out all of data on the disksand all of WAAS CLI configurations except basic networkconfigurations 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 servicesbefore this command is run.Are you sure you want to go ahead?[yes/no]
Note
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 detailsPhysical 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.binWAE# show versionCisco 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 2006)Version: fe611-4.0.0.340Compiled 17:26:17 Mar 25 2006 by cnbuildSystem 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 lastNothing is displayed.WAE# show version pendingWAAS 4.0.1 Version YWAE# reload...... reloading ......WAE# show versionCisco Wide Area Application Services Software (WAAS)...WAE# restore rollbackWAE# reload...... reloading ......Because flash memory configurations were removed after the restore command was used, the show startup-config command does not return any flash memory data. The show running-config command returns the default running configurations.
Related Commands
rmdir
To delete a directory on a WAAS device, use the rmdir EXEC command.
rmdir directory
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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/oldfilesRelated Commands
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
Device Modesapplication-accelerator
central-manager
Usage Guidelines
The scp command prompts you for passwords or passphrases when needed for authentication.
Related Commands
script
To execute a script provided by Cisco or check the script for errors, use the script EXEC command.
script {check | execute} file_name
Syntax Description
check
Checks the validity of the script.
execute
Executes the script. The script file must be a SYSFS file in the current directory.
file_name
Name of the script file.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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
Examples
The following example checks for errors in the script file test_script.pl:
WAE# script check test_script.plsetup
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 Modesapplication-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# setupPlease choose an interface to configure from the following list:1: GigabitEthernet 1/02: GigabitEthernet 2/0Enter choice:...Press the ESC key at any time to quit this sessionshow 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:
•
•
•
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Use this EXEC command to display configuration information for the following AAA accounting types:
•
•
•
Examples
The following example displays the current AAA configuration:
WAE# show aaa accountingAccounting Type Record event(s) Protocol----------------------------------------------------Exec shell start-stop tacacsCommand level 0 stop-only tacacsCommand level 15 disabledSystem start-stop tacacsRelated Commands
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
Device Modesapplication-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:
•
•
The three levels of alarms in WAAS software are:
•
•
•
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 historyOp Sev Alarm ID Module/Submodule Instance-- --- -------------------- -------------------- --------------------1 C Ma tfo_accl_wellness sysmon accl=CIFS2 C Cr wafs_edge_down wafs3 R Ma tfo_accl_wellness sysmon accl=CIFS4 R Cr wafs_edge_down wafs5 R Ma core_dump sysmon coreOp - Operation: R-Raised, C-ClearedSev - Severity: Cr-Critical, Ma-Major, Mi-MinorThe 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 supportOp Sev Alarm ID Module/Submodule Instance-- --- -------------------- -------------------- --------------------1 C Ma tfo_accl_wellness sysmon accl=CIFSApr 12 20:25:58.119 UTC, Processing Error Alarm, #000003, 1000:445005The 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 theTFO Accelerators is failing to perform a wellness updatewithin the allotted time. The implications are that someconnections may not be optimized properly by TFO and thusoptimization performance may be reduced.Action:Examine the status of the specified accelerator to verify itis still operating properly and make adjustments to returnit to full health if necessary.2 C Cr wafs_edge_down wafsApr 12 20:25:30.756 UTC, Processing Error Alarm, #000002, 10000:1000001WAFS 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=CIFSApr 12 20:24:43.127 UTC, Processing Error Alarm, #000003, 1000:445005The 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 theTFO Accelerators is failing to perform a wellness updatewithin the allotted time. The implications are that someconnections may not be optimized properly by TFO and thusoptimization performance may be reduced.Action:Examine the status of the specified accelerator to verify itis still operating properly and make adjustments to returnit to full health if necessary.Op - Operation: R-Raised, C-ClearedSev - Severity: Cr-Critical, Ma-Major, Mi-MinorThis 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 statusCritical Alarms : 0Major Alarms : 1Minor Alarms : 0Overall Alarm Status : MajorDevice 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 Modesapplication-accelerator
central-manager
Examples
The following example shows the ARP table:
WAE# show arpProtocol Address Flags Hardware Addr Type InterfaceInternet 10.56.40.17 Adj 00:06:5B:FE:4D:05 ARPA GigabitEthernet1/0Internet 10.56.40.2 Adj 00:0F:F8:A0:9F:8A ARPA GigabitEthernet1/0Internet 10.56.40.1 Adj 00:00:0C:07:AC:01 ARPA GigabitEthernet1/0The 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
Device Modesapplication-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 userLogin Authentication: Console/Telnet/Ftp/SSH Session----------------------------- ------------------------------local enabled (primary)Windows domain disabledRadius disabledTacacs+ disabledConfiguration Authentication: Console/Telnet/Ftp/SSH Session----------------------------- ------------------------------local enabled (primary)Windows domain disabledRadius disabledTacacs+ disabledThe following example displays the authentication and authorization information for WAAS print services:
WAE# show authentication print-servicesWindows domain server authenticates the Print ServicesWAE# show print-services admin-groupThere 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-requestThe content request authentication in disconnected mode is disabledRelated Commands
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 Modesapplication-accelerator
Examples
The following example displays the status of the automatic registration feature of a WAE:
WAE# show auto-registerAuto registration is disabled.Related Commands
show bypass
To display static bypass configuration information for a WAE, use the show bypass EXEC command.
show bypass list
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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:
WAE# show bypass listClient Server Entry type------ ------ ----------172.16.11.11:0 any-server:0 static-configany-client:0 172.31.23.23:0 static-configRelated Commands
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
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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:
WAE# show cdpGlobal CDP information:Sending CDP packets every 60 secondsSending a holdtime value of 180 secondsSending CDPv2 advertisements is not enabledWAE# show cdp holdtime180 secondsWAE# show cdp interface gigabitethernet 1/0GigabitEthernet1/0 is up, line protocol is upEncapsulation ARPASending CDP packets every 60 secondsHoldtime is 180 secondsWAE# show cdp neighbors gigabitethernet 1/0 detailDevice ID: actona-core1-6513(L)Entry address(es):IP address: 10.10.40.3Platform: cisco WS-C6513, Capabilities: Router Switch IGMPInterface: GigabitEthernet1/0, Port ID (outgoing port): GigabitEthernet5/30Holdtime : 124 secVersion :Cisco Internetwork Operating System SoftwareIOS (tm) c6sup2_rp Software (c6sup2_rp-PS-M), Version 12.1(26)E, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2005 by cisco Systems, Inc.Compiled Fri 24-Dec-04 08:02advertisement version: 2VTP Management Domain: 'actona'Native VLAN: 1WAE# show cdp trafficCDP counters :Total packets Output: 188242, Input: 186151Hdr syntax: 0, Chksum error: 0, Encaps failed: 0No memory: 0, Invalid packet: 0, Fragmented: 0CDP version 1 advertisements Output: 188242, Input: 93072CDP version 2 advertisements Output: 0, Input: 93079Related Commands
show clock
To display information about the system clock on a WAAS device, use the show clock EXEC command.
show clock [detail | standard-timezones {all | details timezone | regions | zones region-name}]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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):
WAE# show clockLocal time: Wed Apr 6 20:03:56 IST 2005The 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.
WAE# show clock detailLocal time: Wed Apr 6 20:10:40 IST 2005UTC time: Wed Apr 6 18:10:40 UTC 2005Epoch: 1112811040 secondsUTC 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 allAfrica/AbidjanAfrica/AccraAfrica/Addis_AbabaAfrica/AlgiersAfrica/AsmeraAfrica/BamakoAfrica/BanguiAfrica/BanjulAfrica/BissauAfrica/BlantyreAfrica/BrazzavilleAfrica/BujumburaAfrica/CasablancaAfrica/CeutaAfrica/ConakryAfrica/DakarAfrica/Dar_es_SalaamAfrica/Djibouti...
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 regionsAfrica/America/Antarctica/Arctic/Asia/Atlantic/Australia/Brazil/CET...US/UTCUniversalW-SUWETZuluThe 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 USZones within region US======================US/AlaskaUS/AleutianUS/ArizonaUS/CentralUS/East-IndianaUS/EasternUS/HawaiiUS/Indiana-StarkeUS/MichiganUS/MountainUS/PacificUS/SamoaThe 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/EasternUS/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
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
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following two examples show the result of using the show cms info command on a WAAS device:
WAE# show cms infoCDN information :Model = CDM4630Node Id = 91Device Mode = cdmCurrent CDM role = PrimaryCMS services information :Service cms_httpd is runningService cms_cdm is runningThe following example shows the CMS application processes:
WAE# show cms processesService cms_httpd runningService cms_cdm runningThe following example writes the database content to a file in text format:
WAE# show cms database content textDatabase 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 xmlDatabase content can be found in /local1/cms-db-12-12-2002-17:07:11:629.xml.Related Commands
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 Modesapplication-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-mgrWAE# debug tfo connectionWAE# show debuggingtfo bufmgr debugging is ontfo compmgr debugging is ontfo connmgr debugging is ontfo netio debugging is ontfo statmgr debugging is ontfo translog debugging is onRelated Commands
show device-mode
To display the configured or current device mode of a WAAS device, use the show device-mode EXEC command.
show device-mode {configured | current}
Syntax Description
configured
Displays the configured device mode, which has not taken effect yet.
current
Displays the current device mode.
Command Modes
EXEC
Device Modesapplication-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 currentCurrent device mode: application-acceleratorTo 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 configuredConfigured device mode: central-managerRelated Commands
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
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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-sectorsdisk00=========899239232112disk01=========(None)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 disk01disk01=========(None)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:
WAE# show disks detailsPhysical 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 the output of the show disks SMART-info EXEC command:
WAEA# show disks SMART-info=== disk00 ===Device: IBM-ESXS ST3146707LW FN Version: B26BSerial number: 3KS2YL00000000000CM3Device type: diskTransport protocol: Parallel SCSI (SPI-4)Local Time is: Fri Mar 31 13:06:08 2006 UTCDevice supports SMART and is EnabledTemperature Warning EnabledSMART Health Status: OK=== disk01 ===Device: IBM-ESXS ST3146707LW FN Version: B26BSerial number: 3KS1ZTRH00000000CK61Device type: diskTransport protocol: Parallel SCSI (SPI-4)Local Time is: Fri Mar 31 13:06:08 2006 UTCDevice supports SMART and is EnabledTemperature Warning EnabledSMART Health Status: OKThe following example displays more detailed SMART output from the show disks SMART-info details EXEC command:
WAE# show disks SMART-info details=== disk00 ===Device: IBM-ESXS ST3146707LW FN Version: B26BSerial number: 3KS2YL94000000000CM3Device type: diskTransport protocol: Parallel SCSI (SPI-4)Local Time is: Fri Mar 31 13:06:53 2006 UTCDevice supports SMART and is EnabledTemperature Warning EnabledSMART Health Status: OKCurrent Drive Temperature: 33 CDrive Trip Temperature: 65 CVendor (Seagate) cache informationBlocks sent to initiator = 4048936465Blocks received from initiator = 100130496Blocks read from cache and sent to initiator = 56503638Number of read and write commands whose size <= segment size = 10124024Number of read and write commands whose size > segment size = 0Error counter log:Errors Corrected Total Total Correction Gigabytes Totaldelay: [rereads/ errors algorithm processed uncRelated Commands
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 Modesapplication-accelerator
central-manager
Examples
The following example displays flash memory information. Note that a new software image has been downloaded, but not yet deployed.
WAE# show flashWAAS software version (disk-based code): WAAS-4.0.0-b340System image on flash:Version: 4.0.0.340System flash directory:System image: 107 sectorsBootloader, rescue image, and other reserved areas: 24 sectors256 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 Modesapplication-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:
WAE# show hardwareCisco 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 2006)Version: fe611-4.0.0.340Compiled 17:26:17 Mar 25 2006 by cnbuildSystem 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 3002MHz.Total 1 CPU.2048 Mbytes of Physical memory.1 CD ROM drive (HL-DT-ST GCR-8240N)2 GigabitEthernet interfaces1 Console interfaceManufactured As: WAE-611-K9 [8836PBN]BIOS Information:Vendor : IBM...Related Commands
show hosts
To view the hosts on a WAAS device, use the show hosts EXEC command.
show hosts
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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:
WAE# show hostsDomain names:------------Name Server(s):-------------Host Table:hostname inet address aliases-------- ------------ -------Edge-WAE1 10.10.10.32show 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 Modesapplication-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:
WAE# show inetdInetd service configurations:ftp enablercp disabledtftp disabledRelated Commands
show interface
To display the hardware interface information for a WAAS device, use the show interface EXEC command.
show interface {GigabitEthernet slot/port | ide control_num | PortChannel port-num | scsi device_num | Standby group_num | usb}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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/0Type:EthernetEthernet address:00:0D:60:84:30:84Internet address:10.56.41.180Broadcast address:10.56.43.255Netmask:255.255.252.0Maximum Transfer Unit Size:1500Metric:1Packets Received: 49288883Input Errors: 0Input Packets Dropped: 0Input Packets Overruns: 0Input Packets Frames: 0Packet Sent: 547899Output Errors: 0Output Packets Dropped: 0Output Packets Overruns: 0Output Packets Carrier: 0Output Queue Length:1000Collisions: 0Interrupts:18Base address:0x2000Flags:UP BROADCAST RUNNING MULTICASTMode: autoselect, full-duplex, 1000baseTXThe following example displays information for the port channel interface configured on the WAAS device:
waas-cm# show interface PortChannel 1Interface PortChannel 1 (0 physical interface(s)):---------------------Type:EthernetEthernet address:00:00:00:00:00:00Maximum Transfer Unit Size:1500Metric:1Packets Received: 0Input Errors: 0Input Packets Dropped: 0Input Packets Overruns: 0Input Packets Frames: 0Packet Sent: 0Output Errors: 0Output Packets Dropped: 0Output Packets Overruns: 0Output Packets Carrier: 0Output Queue Length:0Collisions: 0Flags:BROADCAST MASTER MULTICASTThe following example displays information for the SCSI interface configured on the WAAS device:
waas-cm# show interface scsi 1SCSI interface 0: LSI Chip sym00c000, device id 0xc, revision id 0x2The following example displays information for the standby interface on the WAAS device:
WAE# show interface Standby 4Standby Group: 4Description: This is an interface that acts as a backupIP address: 10.10.10.4, netmask: 255.0.0.0Member interfaces: noneActive interface: noneRelated Commands
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 Modesapplication-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:
•
•
•
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:
WAE# show inventoryPID: WAE-511-K9 VID: 0 SN: serial_numberIn 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 ip access-list
To display the access lists that are defined and applied to specific interfaces or applications on a WAAS device, use the show ip access-list EXEC command.
show ip access-list [acl-name | acl-num]
Syntax Description
Defaults
Displays information about all defined access lists.
Command Modes
EXEC
Device Modesapplication-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:
•
•
•
Examples
The following example shows sample output from the show ip access-list command:
WAE# show ip access-listSpace available:47 access lists492 access list conditionsStandard IP access list 1 1 permit 10.1.1.22 deny 10.1.2.1(implicit deny any: 2 matches)total invocations: 2Extended IP access list 1001 permit tcp host 10.1.1.1 any2 permit tcp host 10.1.1.2 any3 permit tcp host 10.1.1.3 any(implicit fragment permit: 0 matches)(implicit deny ip any any: 0 matches)total invocations: 0Standard IP access list test1 permit 1.1.1.1 (10 matches)2 permit 1.1.1.33 permit 1.1.1.2(implicit deny: 2 matches)total invocations: 12Interface access list references:GigabitEthernet 1/0 inbound 100Application access list references:tftp_server standard 1UDP ports: 69The following shows sample output from the show ip access-list command for the access list named test:
WAE# show ip access-list testStandard IP access list test1 permit 1.1.1.1 (10 matches)2 permit 1.1.1.33 permit 1.1.1.2(implicit deny: 2 matches)total invocations: 12
Note
Related Commands
show ip routes
To display the IP routing table for a WAAS device, use the show ip routes EXEC command.
show ip routes
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the IP routing table:
WAE# show ip routesDestination Gateway Netmask---------------- ---------------- ----------------10.56.41.180 0.0.0.0 255.255.255.255192.168.12.180 0.0.0.0 255.255.255.255192.168.12.0 0.0.0.0 255.255.255.010.56.40.0 0.0.0.0 255.255.252.00.0.0.0 10.56.40.1 0.0.0.0Number of route cache entries: 183Related Commands
show kerberos
To display the Kerberos authentication configuration for a WAAS device, use the show kerberos EXEC command.
show kerberos
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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:
WAE# show kerberosKerberos Configuration:-----------------------Local Realm: WAE.ABC.COMDNS suffix: wae.abc.comRealm for DNS suffix: WAE.ABC.COMName of host running KDC for realm:Master KDC: 0.0.0.0Port: 88Related Commands
show logging
To display the system message log configuration for a WAAS device, use the show logging EXEC command.
show logging
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-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:
WAE# show loggingSyslog to host is disabledPriority for host logging is set to: warningSyslog to console is disabledPriority for console logging is set to: warningSyslog to disk is enabledPriority for disk logging is set to: noticeFilename for disk logging is set to: /local1/syslog.txtSyslog facility is set to *Syslog disk file recycle size is set to 1000000Related Commands
show memory
To display memory blocks and statistics for a WAAS device, use the show memory EXEC command.
show memory
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays information about the blocks in memory:
WAE# show memoryTotal physical memory : 510164 KBTotal free memory : 43220 KBTotal memory shared : 0 KBTotal buffer memory : 12768 KBTotal cached memory : 344472 KBTotal swap : 509940 KBTotal free swap : 509940 KBshow ntp
To display the NTP parameters for a WAAS device, use the show ntp EXEC command.
show ntp status
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the current NTP parameters for a WAAS device. With the first attempt, it is determined that NTP has not been configured. After configuring NTP, the parameters are then displayed.
WAE# show ntp statusntp disabledserver list:WAE(config)# ntp server 172.16.10.80 172.16.10.150WAE(config)# exitWAE(config)# show ntp statusntp enabledserver list: 172.16.10.80 172.16.10.50remote refid st t when poll reach delay offset jitter==============================================================================ntp-sj1.abc.c 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00ntp-sj2.abc.c 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00The following table describes the fields shown in the show ntp status display.
Related Commands
show policy-engine application
To display application policy information for a WAE, use the show policy-engine application EXEC command.
show policy-engine application {classifier [app-classifier] | dynamic | name}
Syntax Description
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example displays information about the specified application classifier Oracle for a WAE:
WEA# show policy-engine application classifier OracleOracle (0)match (0, id=0) dst port eq 66match (1, id=1) dst port eq 1521match (2, id=2) dst port eq 1525The following example displays application dynamic match information:
WEA# show policy-engine application dynamicDynamic Match Freelist Information:Allocated: 8192 In Use: 0 Max In Use: 0 Allocations: 0Individual Dynamic Match Information:--No Application Dynamic Matches are currently active.--The following example displays the application names list:
WEA# show policy-engine application nameNumber of Applications: 121) Authentication (15)2) Backup (18)3) Call-Management (17)4) Conferencing (8)5) Console (4)6) Content-Management (21)7) Directory-Services (6)8) Email-and-Messaging (12)9) Enterprise-Applications (13)10) File-System (2)11) File-Transfer (16)12) Instant-Messaging (22)Related Commands
(config) policy-engine application classifier
(config) policy-engine application map adaptor EPM
(config) policy-engine application map adaptor WAFS accept
(config) policy-engine application map adaptor WAFS transport
(config) policy-engine application map basic delete
(config) policy-engine application map basic disable
(config) policy-engine application map basic insert
(config) policy-engine application map basic list
(config) policy-engine application map basic move
(config) policy-engine application map basic name
(config) policy-engine application map other optimize DRE
(config) policy-engine application map other optimize full
(config) policy-engine application map other pass-through
(config) policy-engine application name
show policy-engine status
To display high-level information about a WAE's policy engine, use the show policy-engine status EXEC command. This information includes the usage of the available resources, which include application names, classifiers, and conditions.
show policy-engine status
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
To display high-level information about a WAE's policy engine:
WEA# show policy-engine statuspolicy-engine resources usage:Total Used Available----- ---- ---------Application names 256 28 228Classifiers 512 146 366Conditions 1024 321 703Related Commands
(config) policy-engine application classifier
(config) policy-engine application map adaptor EPM
(config) policy-engine application map adaptor WAFS accept
(config) policy-engine application map adaptor WAFS transport
(config) policy-engine application map basic delete
(config) policy-engine application map basic disable
(config) policy-engine application map basic insert
(config) policy-engine application map basic list
(config) policy-engine application map basic move
(config) policy-engine application map basic name
(config) policy-engine application map other optimize DRE
(config) policy-engine application map other optimize full
(config) policy-engine application map other pass-through
(config) policy-engine application name
show print-services
To display administrative users who have access to configuration privileges, print services, or print service processes on a WAAS device, use the show print-services EXEC command.
show print-services {admin-group | drivers user username | process}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
To view print service configuration information by administrative group:
WAE# show print-services admin-groupAdministrator Group for print-services is : cupsAdminIf there is no administrative group set, the output looks like this:
WAE# show print-services admin-groupThere is no configured administrator group for print-services.To view print service configuration information by the print service process:
WAE# show print-services processPrint server is not running.Print spooler is not running.Related Commands
show processes
To display CPU or memory processes for a WAAS device, use the show processes EXEC command.
show processes [cpu | debug pid | memory | system [delay 1-60 | count 1-100]]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Use the EXEC commands shown in this section to track and analyze system CPU utilization.
The show processes debug command displays extensive internal system call information and a detailed account of each system call (along with arguments) made by each process and the signals it has received.
Use the show processes system command to display system load information in terms of updates. The delay option specifies the delay between updates, in seconds. The count option specifies the number of updates that are displayed. This command displays these items:
•
•
•
Note
Examples
The following example displays information about overall system utilization:
WAE# show processes cpuCPU average usage since last reboot:cpu: 0.20% User, 0.47% System, 1.41% User(nice), 97.92% Idle--------------------------------------------------------------------PID STATE PRI User T SYS T COMMAND----- ----- --- ------ ------ --------------------1 S 0 350 94 (init)2 S 0 0 0 (migration/0)3 S 19 0 0 (ksoftirqd/0)4 S -10 0 0 (events/0)5 S -10 0 0 (khelper)The following example displays information about memory utilization:
WAE# show processes memoryTotal Used Free Shared Buffers Cached2120081408 786411520 1333669888 0 56590336 614592512Swap Total Used Free2107498496 0 2107498496PID State TTY %MEM VM Size RSS (pages) Name------ ----- ------ ----- ---------- ----------- ----1 S 0 0.0 1445888 135 (init)2 S 0 0.0 0 0 (migration/0)3 S 0 0.0 0 0 (ksoftirqd/0)4 S 0 0.0 0 0 (events/0)The following table describes the fields shown in the show processes displays.
show radius-server
To display RADIUS configuration information for a WAAS device, use the show radius-server EXEC command.
show radius-server
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the RADIUS configuration information for the WAAS:
WAE# show radius-serverRadius Configuration:---------------------Radius Authentication is onTimeout = 5Retransmit = 3Key = ****Servers-------The following table describes the fields shown in the show radius-server display.
Related Commands
show running-config
To display a WAAS device's current running configuration information on the terminal, use the show running-config EXEC command. This command replaces the write terminal command.
show running-config
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Use this EXEC command in conjunction with the show startup-config command to compare the information in running memory to the startup configuration used during bootup.
Examples
The following example displays the currently running configuration of a WAAS device:
WAE# show running-config! WAAS version 4.0.0!device mode central-manager!!hostname waas-cm!!!!!exec-timeout 60!!primary-interface GigabitEthernet 1/0!!...Related Commands
show services
To display services-related information for a WAAS device, use the show services EXEC command.
show services {ports [port-num] | summary}
Syntax Description
ports
Displays services by port number.
port-num
(Optional) Up to 8 port numbers (1-65535).
summary
Displays the services summary.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays a summary of the services:
WAE# show services summaryService Ports-----------------------------------------------------CMS 1100 5256NLM 4045WAFS 1099emdb 5432MOUNT 3058MgmtAgent 5252WAFS_tunnel 4050CMS_db_vacuum 5257show smb-conf
To view a WAAS device's current values of the Samba configuration file, smb.conf, use the show smb-conf EXEC command.
show smb-conf
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
This command displays the global, print$, and printers parameters values of the smb.conf file for troubleshooting purposes. For a description of these parameters and their values, see "(config) smb-conf" command.
Examples
The following example displays all of the parameter values for the current configuration:
WAE# show smb-confCurrent smb-conf configurations -->smb-conf section "global" name "ldap ssl" value "start_tls"smb-conf section "printers" name "printer admin" value "root"Output of current smb.conf file on disk -->==============================================# File automatically generated[global]idmap uid = 70000-200000idmap gid = 70000-200000winbind enum users = nowinbind enum groups = nowinbind cache time = 10winbind use default domain = yesprintcap name = cupsload printers = yesprinting = cupscups options = "raw"force printername = yeslpq cache time = 0log file = /local/local1/errorlog/samba.logmax log size = 50socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192smb ports = 50139local master = nodomain master = nopreferred master = nodns proxy = notemplate homedir = /local/local1/template shell = /admin-shellldap ssl = start_tlscomment = Comment:netbios name = MYFILEENGINErealm = ABCwins server = 10.10.10.1password server = 10.10.10.10security = domain[print$]path = /state/samba/printersguest ok = yesbrowseable = yesread only = yeswrite list = root[printers]path = /local/local1/spool/sambabrowseable = noguest ok = yeswritable = noprintable = yesprinter admin = root==============================================Related Commands
show snmp
To check the status of SNMP communications for a WAAS device, use the show snmp EXEC command.
show snmp {alarm-history | engine ID | event | group | stats | user}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
This EXEC command provides information on various SNMP variables and statistics on SNMP operations.
Examples
The following example displays the SNMP alarm history information:
WAE# show snmp alarm-historyIndex Type Sev Alarm ID ModuleID Category Descr----- ---- --- -------- -------- -------- -----1 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The rtspg service died.2 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The mediacache service died.3 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The sshdaemon service died.4 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The cache service died.5 R Ma 330003 2000 3 Raise-Alarm: nodemgr: The ntpd service died.6 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The mediacache service died.7 R Ma 445001 1000 3 Raise-Alarm: Kernel Crash files and / or User Core files detected8 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The cache service died.9 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The mediacache service died.10 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The rpc_httpd service died.11 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The rpc_httpd service died.12 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The cache service died.13 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The mediacache service died.14 R Ma 330003 2000 3 Raise-Alarm: nodemgr: The ntpd service died.15 R Ma 330003 2000 3 Raise-Alarm: nodemgr: The ntpd service died.16 R Mi 330004 2000 3 Raise-Alarm: nodemgr: The mediacache service died.WAE#The following table describes the fields shown in the show snmp alarm-history display.
The following table summarizes the mapping of module names to modules IDs.
AD_DATABASE
8000
NHM
1
NHM/NHM
2500
nodemgr
2000
standby
4000
sysmon
1000
UNICAST_DATA_RECEIVER
5000
UNICAST_DATA_SENDER
6000
The following table summarizes the mapping of category names to category IDs.
Communications
1
Service Quality
2
Processing Error
3
Equipment
4
Environment
5
Content
6
The following examples display the SNMP engine ID and SNMP statistical data:
WAE# show snmp engineIDLocal SNMP Engine ID: 00000009000000A11A3829CEWAE# show snmp statsContact: username, system admin, user@cisco.com 555-1111Location: Building 2, Floor 1, LabA146 SNMP packets input0 Bad SNMP version errors0 Unknown community name0 Illegal operation for community name supplied0 Encoding errors0 Number of requested variables120 Number of altered variables0 Get-request PDUs0 Get-next PDUs120 Set-request PDUs146 SNMP packets output0 Too big errors2048 Maximum packet size0 No such name errors0 Bad values errors0 General errors146 Response PDUs0 Trap PDUsThe following table describes the fields shown in the show snmp stats display.
The following example displays information about the SNMP events set using the "snmp trigger" command:
WAE# show snmp eventMgmt Triggers:(1): Owner: CLI(1): 01 , Comment: isValid == 0, Sample: Abs, Freq: 120Test: BooleanObjectOwner: CLI, Object: CLI1Boolean Entry:Value: 0, Cmp: 2, Start: 1ObjOwn: , Obj: , EveOwn: CLI, Eve: CLI_EVENTDelta Value Table:(0): Thresh: , Exis: 1, Read: 0, OID: isValid.0 , val: 1(2): 02 , Comment: daysLeft, Sample: Abs, Freq: 120Test: BooleanObjectOwner: CLI, Object: CLI2Boolean Entry:Value: 10, Cmp: 3, Start: 1ObjOwn: , Obj: , EveOwn: CLI, Eve: CLI_EVENTDelta Value Table:(0): Thresh: , Exis: 1, Read: 0, OID: daysLeft.0 , val: 99999(3): 03 , Comment: esConTabIsConnected, Sample: Abs, Freq: 60Test: BooleanObjectOwner: CLI, Object: CLI3Boolean Entry:Value: 0, Cmp: 2, Start: 1ObjOwn: , Obj: , EveOwn: CLI, Eve: CLI_EVENTDelta Value Table:(4): 04 , Comment: esConnectedSessionCount, Sample: Abs, Freq: 120Test: BooleanObjectOwner: CLI, Object: CLI4Boolean Entry:Value: 80, Cmp: 5, Start: 1ObjOwn: , Obj: , EveOwn: CLI, Eve: CLI_EVENTDelta Value Table:(5): 05 , Comment: esCifsOpenFiles, Sample: Abs, Freq: 60Test: BooleanObjectOwner: CLI, Object: CLI5Boolean Entry:Value: 4500, Cmp: 5, Start: 1ObjOwn: , Obj: , EveOwn: CLI, Eve: CLI_EVENTDelta Value Table:(6): 06 , Comment: esEvictedAge, Sample: Abs, Freq: 60Test: BooleanObjectOwner: CLI, Object: CLI6Boolean Entry:Value: 120960000, Cmp: 3, Start: 1ObjOwn: , Obj: , EveOwn: CLI, Eve: CLI_EVENTDelta Value Table:Mgmt Events:(1): Owner: CLI(1)Name: CLI_EVENT, Comment: , Action: Notify, Enabled: 1 Status: 1Notification Entry:ObjOwn: , Obj: , OID: 0.0Object Table:Failures: Event = 0, Trigger = 0Related Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server notify inform
show ssh
To display the status and configuration information of the Secure Shell (SSH) service for a WAAS device, use the show ssh EXEC command.
show ssh
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the status and configuration of the SSH service:
WAE# show sshSSH server supports SSH2 protocol (SSH1 compatible).Ssh service is not enabled.Currently there are no active ssh sessions.Number of successful SSH sessions since last reboot: 0Number of failed SSH sessions since last reboot: 0SSH key has not been generated or previous key has been removed.SSH login grace time value is 300 seconds.Allow 3 password guess(es).Related Commands
show standby
To display information about a standby interface on a WAAS device, use the show standby EXEC command.
show standby
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
In the following sample command output, one standby group (Standby Group 1) is configured on this WAAS device. The command output also shows which member interface is the active interface. In this case, the active interface is the Gigabit Ethernet slot 1/port 0 interface.
WAE# show standbyStandby Group: 1Description: This a backup for Gigabit Ethernet 1/0.IP address: 192.168.10.10, netmask: 255.0.0.0Member interfaces:GigabitEthernet 2/0 priority: 100Active interface: GigabitEthernet 1/0Maximum errors allowed on the active interface: 500
Note
Related Commands
show startup-config
To display the startup configuration for a WAAS device, use the show startup-config EXEC command.
show startup-config
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Use this EXEC command to display the configuration used during an initial bootup, stored in NVRAM. Note the difference between the output of this command versus the show running-config command.
Examples
The following example displays the configuration saved for use on startup of the WAAS device:
WAE# show startup-config! WAAS version 4.0.0!device mode central-manager!!hostname Edge-WAE1!!!!!exec-timeout 60!!primary-interface GigabitEthernet 1/0!!!interface GigabitEthernet 1/0ip address 10.10.10.33 255.255.255.0exitinterface GigabitEthernet 2/0shutdown...Related Commands
show statistics authentication
To display authentication statistics for a WAAS device, use the show statistics authentication EXEC command.
show statistics authentication
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Authentication statistics display the number of access requests, denials, and allowances recorded. Use the show statistics authentication command to display the number of authentication accesses recorded.
Examples
The following example displays the statistics related to authentication on the WAAS device:
WAE# show statistics authenticationAuthentication Statistics--------------------------------------Number of access requests: 115Number of access deny responses: 12Number of access allow responses: 103Related Commands
show statistics content-distribution-network
To display the status of a WAE or device group that are registered with a WAAS Central Manager, use the show statistics content-distribution-network EXEC command. This command is available on only WAAS Central Managers.
show statistics content-distribution-network device status device_id
Syntax Description
device status
Displays the status of a WAE or device group that is registered with the WAAS Central Manager.
device_id
Name or ID of the device or device group.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modescentral-manager
Usage Guidelines
Use the show statistics content-distribution-network EXEC command to display the identification details about a WAE or WAEs in a device group, and verify if a WAE is online.
Examples
The following example displays the identification details of a WAE that that is registered with the WAAS Central Manager:
WAE# show statistics content-distribution-network device status edge-wae-11Device id="CdmConfig_142" name="edge-wae-11" status="Online";show statistics dre
To display Data Redundancy Elimination (DRE) general statistics for a WAE, use the show statistics dre EXEC command.
show statistics dre
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example displays DRE statistics:
WEA# show statistics dreCache:Total disk: 47622 MB, RAM size: 297 MB, Status: UsableUsed disk: 28 MB, Oldest Data (age): 23 days 20 hoursCompleted Connections: 2030Encode:Overall: msg: 3620, in: 6181 KB, out: 5335 KB, ratio: 13.69%DRE: msg: 3620, in: 6181 KB, out: 6352 KB, ratio: 0.00%LZ: msg: 3619, in: 6321 KB, out: 5305 KB, ratio: 16.08%Bypass: msg: 3252, in: 4901 KB,Latency(Last 3 sec): max 3 ms, avg 0 msDecode:Overall: msg: 7162, in: 4969 KB, out: 209 MB, ratio: 97.69%DRE: msg: 7162, in: 5056 KB, out: 209 MB, ratio: 97.65%LZ: msg: 510, in: 1073 KB, out: 1160 KB, ratio: 7.46%Bypass: msg: 29, in: 289 KBLatency (Last 3 sec): max 1 ms, avg 0 msRelated Commands
show statistics dre connection
show statistics dre connection
To display Data Redundancy Elimination (DRE) connection statistics for a WAE, use the show statistics dre connection EXEC command.
This command displays the statistics for individual TCP connections on which DRE compression is being applied. This information is updated in real time.
show statistics dre connection [active [client-ip {ip_address | hostname} | client-port port |
id connection_id | last | peer-no peer_id | server-ip {ip_address | hostname} | server-port port] | client-ip {ip_address | hostname} | client-port port | id connection_id | last | peer-no peer_id | server-ip {ip_address | hostname} | server-port port]Syntax Description
Command Modes
EXEC
Device Modesapplication-accelerator
Usage Guidelines
Using this command without any options displays a one-line summary of all the TCP connections on the WAE for which DRE is applied. To obtain detailed stastistics for a connection, use the command options to filter the connection.
Examples
The following example displays all active connection statistics:
WEA# show statistics dre connectionConn-ID Client-ip:port Server-ip:port Encode-in Decode-in PID Status1151 10.10.10.10:2562 10.10.10.11:80 590 B 0 B 3 Closed-694s1150 10.10.10.10:2561 10.10.10.11:80 590 B 0 B 3 Closed-694s1149 10.10.10.10:2560 10.10.10.11:80 2440 B 0 B 3 Closed-694sRelated Commands
show statistics dre connection
show statistics dre peer
To display Data Redundancy Elimination (DRE) peer statistics for a WAE, use the show statistics dre peer EXEC command.
show statistics dre peer {context context-value [ip ip-address | peer-id peer-id |
peer-no peer-no] | ip ip-address [context context-value | ip ip-address | peer-id peer-id | peer-no peer-no] | peer-id peer-id [context context-value | ip ip-address | peer-no peer-no] |
peer-no peer-no [context context-value | ip ip-address | peer-id peer-id]}Syntax Description
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example displays DRE peer statistics:
WAE# show statistics dre peerpeer-no: 0 Hostname: dc-425-jsmithPeer-IP: 10.10.10.40 MAC-address: 00:0d:00:11:41:8e-----------------------------------------------------------------Cache:Used disk: 24 MB, Age: 23 days 21 hoursConnections:Total (cumulative) : 67Concurrent (Last 2 min): max 23, avg 22Encode:Overall: msg: 278, in: 1290 KB, out: 1254 KB, ratio: 2.82%DRE: msg: 278, in: 1290 KB, out: 1301 KB, ratio: 0.00%LZ: msg: 277, in: 1271 KB, out: 1224 KB, ratio: 3.71%Bypass: msg: 25, in: 12638 B,Latency(Last 3 sec): max 3 ms, avg 0 msDecode:Overall: msg: 42, in: 34694 B, out: 147 KB, ratio: 77.05%DRE: msg: 42, in: 121 KB, out: 147 KB, ratio: 17.62%LZ: msg: 42, in: 34694 B, out: 121 KB, ratio: 72.14%Bypass: msg: 0, in: 0 BLatency (Last 3 sec): max 1 ms, avg 0 msRelated Commands
show statistics dre connection
show statistics epm
To display EndPoint Mapper (EPM) statistics for a WAE, use the show statistics epm EXEC command. This command displays the number of total requests and responses recorded.
show statistics epm
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example displays EPM statistics for a WAE:
WAE# show statistics epmEPM statistics--------------Total requests = 1108success = 781fault = 0Total responses = 781success = 0UUID not configured = 695service unavailable = 86fault = 0Related Commands
(config) policy-engine application map adaptor EPM
show statistics icmp
To display ICMP statistic for a WAAS device, use the show statistics icmp EXEC command.
show statistics icmp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the ICMP-related statistics on the WAAS device:
WAE# show statistics icmpICMP statistics---------------ICMP messages received = 1351ICMP messages receive failed = 190Destination unreachable = 431Timeout in transit = 1Wrong parameters = 0Source quenches = 0Redirects = 0Echo requests = 729Echo replies = 0Timestamp requests = 0Timestamp replies = 0Address mask requests = 0Address mask replies = 0ICMP messages sent = 2280ICMP messages send failed = 0Destination unreachable = 1551Time exceeded = 0Wrong parameters = 0Source quenches = 0Redirects = 0Echo requests = 0Echo replies = 729Timestamp requests = 0Timestamp replies = 0Address mask requests = 0Address mask replies = 0Related Commands
show statistics ip
To display IP statistics for a WAAS device, use the show statistics ip EXEC command.
show statistics ip
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the IP-related statistics on the WAAS device:
WAE# show statistics ipIP statistics-------------Total packets in = 19959308with invalid header = 0with invalid address = 0forwarded = 0unknown protocol = 0discarded = 0delivered = 10074121Total packets out = 44784dropped = 0dropped (no route) = 0Fragments dropped after timeout = 0Reassemblies required = 0Packets reassembled = 0Packets reassemble failed = 0Fragments received = 0Fragments failed = 0Fragments created = 0Related Commands
show statistics netstat
To display Internet socket connection statistics for a WAAS device, use the show statistics netstat EXEC command.
show statistics netstat
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the Internet socket connection statistics on the WAAS device:
WAE# show statistics netstatActive Internet connections (w/o servers)Proto Recv-Q Send-Q Local Address Foreign Address Statetcp 0 4 10.10.41.180:23 10.10.230.11:3105 ESTABLISHEDshow statistics radius
To display RADIUS authentication statistics for a WAAS device, use the show statistics radius EXEC command.
show statistics radius
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the RADIUS-related statistics on the WAAS device:
WAE# show statistics radiusRADIUS Statistics-----------------------------------------------Authentication:Number of access requests: 0Number of access deny responses: 0Number of access allow responses: 0Authorization:Number of authorization requests: 0Number of authorization failure responses: 0Number of authorization success responses: 0Accounting:Number of accounting requests: 0Number of accounting failure responses: 0Number of accounting success responses: 0Related Commands
show statistics services
To display services statistics for a WAAS device, use the show statistics services EXEC command.
show statistics services
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the service-related statistics for each port on the WAAS device:
WAE# show statistics servicesPort StatisticsPort Total Connections---------------------------------------------------------------20 021 022 023 042 049 053 069 080 0123 0137 0138 0139 0161 0443 0514 02048 03130 0Related Commands
show statistics snmp
To display SNMP statistics for a WAAS device, use the show statistics snmp EXEC command.
show statistics snmp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the SNMP statistics:
WAE# show statistics snmpContact: Mary Brown, system admin, mbrown@acme.com 555-1111Location: Building 2, Floor 1, LabA146 SNMP packets input0 Bad SNMP version errors0 Unknown community name0 Illegal operation for community name supplied0 Encoding errors0 Number of requested variables120 Number of altered variables0 Get-request PDUs0 Get-next PDUs120 Set-request PDUs146 SNMP packets output0 Too big errors2048 Maximum packet size0 No such name errors0 Bad values errors0 General errors146 Response PDUs0 Trap PDUsSee the "show snmp" commands for a description of the fields shown in the show snmp stats display.
Related Commands
show statistics tacacs
To display TACACS+ authentication and authorization statistics for a WAAS device, use the show statistics tacacs EXEC command.
show statistics tacacs
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the TACACS+-related statistics on the WAAS device:
WAE# show statistics tacacsTACACS+ Statistics-----------------------------------------------------------Authentication:Number of access requests: 3Number of access deny responses: 1Number of acess allow responses: 2Authorization:Number of authorization requests: 1Number of authorization failure responses: 0Number of authorization success responses: 1Related Commands
show statistics tcp
To display TCP statistics for a WAAS device, use the show statistics tcp EXEC command.
show statistics tcp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the TCP-related statistics on the WAAS device:
WAE# show statistics tcpTCP statistics--------------Server connection openings = 12Client connection openings = 194Failed connection attempts = 0Connections established = 0Connections resets received = 0Connection resets sent = 7791Segments received = 11368Segments sent = 10895Bad segments received = 0Segments retransmitted = 28Retransmit timer expirations = 28Server segments received = 135Server segments sent = 143Server segments retransmitted = 0Client segments received = 3438Client segments sent = 10752Client segments retransmitted = 28TCP extended statistics-----------------------Sync cookies sent = 0Sync cookies received = 0Sync cookies failed = 0Embryonic connection resets = 0Prune message called = 0Packets pruned from receive queue = 0Out-of-order-queue pruned = 0Out-of-window Icmp messages = 0Lock dropped Icmp messages = 0Arp filter = 0Time-wait sockets = 10Time-wait sockets recycled = 0Time-wait sockets killed = 0PAWS passive = 0PAWS active = 0PAWS established = 0Delayed acks sent = 82Delayed acks blocked by socket lock = 0Delayed acks lost = 5Listen queue overflows = 0Connections dropped by listen queue = 0TCP packets queued to prequeue = 0TCP packets directly copied from backlog = 0TCP packets directly copied from prequeue = 0TCP prequeue dropped packets = 0TCP header predicted packets = 324Packets header predicted and queued to user = 0TCP pure ack packets = 1340TCP header predicted acks = 106TCP Reno failures = 0TCP SACK failures = 1TCP loss failures = 0TCP fast retransmissions = 0TCP forward retransmissions = 0TCP slowstart retransmissions = 0TCP Timeouts = 12TCP Reno recovery fail = 0TCP Sack recovery fail = 0TCP scheduler failed = 0TCP receiver collapsed = 0TCP DSACK old packets sent = 12TCP DSACK out-of-order packets sent = 0TCP DSACK packets received = 0TCP DSACK out-of-order packets received = 0TCP connections abort on sync = 0TCP connections abort on data = 0TCP connections abort on close = 0TCP connections abort on memory = 0TCP connections abort on timeout = 3TCP connections abort on linger = 0TCP connections abort failed = 0TCP memory pressures = 0Related Commands
show statistics tfo
To display Traffic Flow Optimization (TFO) statistics for a WAE, use the show statistics tfo EXEC command.
show statistics tfo [application app-name | pass-through | peer | saving app-name]
Syntax Description
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example displays TFO statistics for the application Other on a WAE:
WAE# show statistics tfo application OtherApplication In out---------------------- ----------------------OtherOptimized:Bytes 0 0Packets 0 0Non Optimized:Bytes 35448 22664Packets 554 531Internal Client:Bytes 0 0Packets 0 0Internal Server:Bytes 347701 1248795Packets 4759 4586PT No Peer:Bytes 0 0Packets 0 0PT Configured:Bytes 0 0Packets 0 0PT Intermediate:Bytes 0 0Related Commands
show statistics udp
To display User Datagram Protocol (UDP) statistics for a WAAS device, use the show statistics udp EXEC command.
show statistics udp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the UDP-related statistics on the WAAS device:
WAE# show statistics udpUDP statistics--------------Packets received = 222616Packets to unknown port received = 904Packet receive error = 0Packet sent = 25821show statistics wccp
To display WCCP statistics for a WAE, use the show statistics wccp EXEC command.
show statistics wccp gre
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
Usage Guidelines
GRE is a Layer 3 technique that allows datagrams to be encapsulated into IP packets at the WCCP-enabled router and then redirected to a WAE (the transparent proxy server). At this intermediate destination, the datagrams are decapsulated and then routed to an origin server to satisfy the request if a cache miss occurs. In doing so, the trip to the origin server appears to the inner datagrams as one hop. Usually, the redirected traffic using GRE is referred to as GRE tunnel traffic. With GRE, all redirection is handled by the router software.
With WCCP redirection, a Cisco router does not forward the TCP SYN packet to the destination because the router has WCCP enabled on the destination port of the connection. Instead, the WCCP-enabled router encapsulates the packet using GRE tunneling and sends it to the WAE that has been configured to accept redirected packets from this WCCP-enabled router.
After receiving the redirected packet, the WAE does the following:
1.
2.
a.
b.
For example, a WAE would not accept the request because it is configured to bypass requests that originate from a certain set of clients or that are destined to a particular set of servers.
Examples
The following example displays WCCP GRE statistics for the WAE:
WAE# show statistics wccp greTransparent GRE packets received: 3000622Transparent non-GRE packets received: 0Transparent non-GRE packets passed through: 0Total packets accepted: 245Invalid packets received: 0Packets received with invalid service: 0Packets received on a disabled service: 0Packets received too small: 0Packets dropped due to zero TTL: 0Packets dropped due to bad buckets: 0Packets dropped due to no redirect address: 0Packets dropped due to loopback redirect: 0Connections bypassed due to load: 0Packets sent back to router: 168Packets sent to another WAE: 0GRE fragments redirected: 0Packets failed GRE encapsulation: 0Packets dropped due to invalid fwd method: 0Packets dropped due to insufficient memory: 0Packets bypassed, no conn at all: 0Packets bypassed, no pending connection: 168Packets due to clean wccp shutdown: 0Packets bypassed due to bypass-list lookup: 0Packets received with client IP addresses: 0Conditionally Accepted connections: 0Conditionally Bypassed connections: 0L2 Bypass packets destined for loopback: 0Packets w/WCCP GRE received too small: 0Packets dropped due to IP access-list deny: 3000209Packets fragmented for bypass: 0Packets dropped due to no route found 0WAE#The following table describes the fields shown in the show statistics wccp gre display.
Related Commands
show statistics windows-domain
To display Windows domain server information for a WAAS device, use the show windows-domain EXEC command.
show statistics windows-domain
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
After entering the show windows-domain EXEC command to view the Windows domain server statistics, you can clear the counters for these statistics by entering the clear statistics windows-domain EXEC command.
Examples
The following example displays the Windows domain server statistics:
WAE# show statistics windows-domainWindows Domain Statistics-----------------------------------------------Authentication:Number of access requests: 9Number of access deny responses: 3Number of access allow responses: 6Authorization:Number of authorization requests: 9Number of authorization failure responses: 3Number of authorization success responses: 6Accounting:Number of accounting requests: 0Number of accounting failure responses: 0Number of accounting success responses: 0Related Commands
show sysfs
To display system file system (sysfs) information for a WAAS device, use the show sysfs EXEC command.
show sysfs volumes
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
The system file system (sysfs) stores log files, including transaction logs, syslogs, and internal debugging logs. It also stores system image files and operating system files.
Examples
The following example displays the disk volume number and its size:
WAE# show sysfs volumessysfs 00: /local/local1 17775600KB 96% freesysfs 01: /local/local2 17782768KB 99% freesysfs 02: /local/local3 17782768KB 99% freesysfs 03: /local/local4 17782768KB 99% freesysfs 04: /local/local5 15684592KB 99% freeRelated CommandsRelated Commands
show tacacs
To display TACACS+ authentication protocol configuration information for a WAAS device, use the show tacacs EXEC command.
show tacacs
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the TACACS+ configuration on the WAAS device:
WAE# show tacacsLogin Authentication for Console/Telnet Session: disabledConfiguration Authentication for Console/Telnet Session: disabledTACACS+ Configuration:---------------------TACACS+ Authentication is offKey =Timeout = 5Retransmit = 2Password type: papServer Status---------------------------- ------192.168.2.5 primaryThe following table describes the fields shown in the show tacacs display.
Related Commands
show tcp
To display TCP configuration information for a WAAS device, use the show tcp EXEC command.
show tcp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the TCP configuration on the WAAS device:
WAE# show tcp==TCP Configuration==TCP keepalive timeout 90 secTCP keepalive probe count 4TCP keepalive probe interval 75 secTCP explicit congestion notification disabledTCP cwnd base value 2TCP initial slowstart threshold value 2TCP increase(multiply) retransmit timer by 1TCP memory_limit - Low water mark: 360 MB, High water mark (pressure): 380 MB,High water mark (absolute): 400 MBRelated Commands
show tech-support
To view information necessary for Cisco's TAC to assist you, use the show tech-support EXEC command.
show tech-support [page]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Use this command to view system information necessary for TAC to assist you with a WAAS device. We recommend that you log the output to a disk file. (See the "(config) logging" command.)
Examples
The following example displays technical support information:
Note
WAE# show tech-support------------------ version and hardware --------------------Cisco Wide Area Application Services Software (WAAS)Copyright (c) 1999-2006 by Cisco Systems, Inc....Version: ce510-4.0.0.180Compiled 18:08:17 Feb 16 2006 by cnbuildSystem was restarted on Fri Feb 17 23:09:53 2006.The system has been up for 5 weeks, 3 days, 2 hours, 9 minutes, 49 seconds.CPU 0 is GenuineIntel Intel(R) Celeron(R) CPU 2.40GHz (rev 2) running at 2401MHz.Total 1 CPU.512 Mbytes of Physical memory....BIOS Information:Vendor : IBMVersion : -[PLEC52AUS-C.52]-Rel. Date : 05/19/03...List of all disk drives:Physical disk information:disk00: Normal (IDE disk) 76324MB( 74.5GB)disk01: Normal (IDE disk) 76324MB( 74.5GB)Mounted filesystems:MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%/ root /dev/root 31MB 26MB 5MB 83%/sw internal /dev/md0 991MB 430MB 561MB 43%/swstore internal /dev/md1 991MB 287MB 704MB 28%/state internal /dev/md2 3967MB 61MB 3906MB 1%/disk00-04 CONTENT /dev/md4 62539MB 32MB 62507MB 0%/local/local1 SYSFS /dev/md5 3967MB 197MB 3770MB 4%.../local1/spool PRINTSPOOL /dev/md6 991MB 16MB 975MB 1%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/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]...Currently content-filesystems RAID level is not configured to change.------------------ running configuration -------------------! WAAS version 4.0.0!!...------------------ processes --------------------CPU average usage since last reboot:cpu: 0.00% User, 1.79% System, 3.21% User(nice), 95.00% Idle--------------------------------------------------------------------PID STATE PRI User T SYS T COMMAND----- ----- --- ------ ------ --------------------1 S 0 20138 21906 (init)2 S 0 0 0 (migration/0)3 S 19 0 0 (ksoftirqd/0)4 S -10 0 0 (events/0)5 S -10 0 0 (khelper)17 S -10 0 0 (kacpid)93 S -10 0 0 (kblockd/0)...show telnet
To display Telnet services configuration for a WAAS device, use the show telnet EXEC command.
show telnet
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays whether or not Telnet is enabled on the WAAS device:
WAE# show telnettelnet service is enabledRelated Commands
show tfo accelerators
To display Traffic Flow Optimization (TFO) accelerators information for a WAE, use the show tfo accelerators EXEC command.
show tfo accelerators
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example displays TFO accelerator information for the WAE:
WAE# show tfo acceleratorsName: TFO State: Registered, Handling Level: 100%Keepalive timeout: 3.0 seconds, Session timeouts: 0, Total timeouts: 0Last keepalive received 00.5 Secs agoLast registration occurred 11:21:43:38.4 Days:Hours:Mins:Secs agoName: EPM State: Registered, Handling Level: 100%Keepalive timeout: 5.0 seconds, Session timeouts: 0, Total timeouts: 0Last keepalive received 00.2 Secs agoLast registration occurred 11:21:43:36.7 Days:Hours:Mins:Secs agoName: CIFS State: Not Registered, Handling Level: 0%Keepalive timeout: 0.0 seconds, Session timeouts: 0, Total timeouts: 0Last keepalive received -Never-Last Registration occurred -Never-Related Commands
show tfo auto-discovery
To display Traffic Flow Optimization (TFO) auto-discovery statistics for a WAE, use the show tfo auto-discovery EXEC command.
show tfo auto-discovery
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example displays TFO auto-discovery statistics for the WAE:
WAE# show tfo auto-discoveryAuto discovery structure allocations failure: 0Auto discovery structure allocations success: 8207Auto discovery structure deallocations: 8207Auto discovery table bucket overflows: 0Auto discovery table overflows: 0Auto discovery table entry adds: 8207Auto discovery table entry drops: 8207Auto discovery table lookups: 8207Auto discovery table entry count: 0Packets sent during auto discovery: 8207Packets received during auto discovery: 16414Number of route lookup failures: 0Number of successful route lookups: 0Bind hash add failures: 0Accept socket pair allocation failures: 0Sock allocation failures: 0Sock(u) allocation failures: 0Connect socket lookup failures: 0Auto discovery failures: 8207Number of resets received during auto discovery: 0Packet memory allocation failures: 0Auto discovery failures due to insuff. option space: 0Invalid connection state during auto discovery: 0Auto discovery failures due to missing ack conf: 0Successful auto discovery to internal server: 0Successful auto discovery to external server: 0Successful auto discovery for an internal client: 0Successful auto discovery for an external client: 0Intermediate device: 0SYNs found with our device id: 0Related Commands
show statistics tfo
show tfo accelerators
show tfo bufpool
show tfo connection
show tfo filtering
show tfo statusshow tfo bufpool
To display Traffic Flow Optimization (TFO) buffer pool information for a WAE, use the show tfo bufpool EXEC command.
show tfo bufpool {accounting | from-index index | owner-connection conn-id |
owner-module {RElib | tcpproxy} [from-index index | owner-connectionconn-id |
state {free | in-use} [from-index index | owner-connection conn-id | to-index index] |
to-index index] | state {free | in-use} [from-index index | owner-connectionconn-id |
to-index index] | to-index index}Syntax Description
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example displays TFO buffer pool information for the WAE:
WAE# show tfo bufpool accountingTotal buffer pool size: 80740352 bytesFree buffer: 80740352 bytes, in 78848 units (unit size: 1024 bytes)Used buffer: 0 bytes, in 0 unitsBuffer usage by module:Tcpproxy: using 0 bytes, in 0 unitsRElib: using 0 bytes, in 0 unitsLZlib: using 0 bytes, in 0 unitsBuffer usage by connection:Related Commands
show tfo accelerators
show tfo auto-discovery
show tfo connection
show tfo filtering
show tfo status
show statistics tfoshow tfo connection
To display Traffic Flow Optimization (TFO) connection information for a WAE, use the show tfo connection EXEC command.
show tfo connection [[summary] | [client-ip host-address | client-port port | peer-id mac |
server-ip host-address | server-port port]]Syntax Description
Command Modes
EXEC
Device Modesapplication-accelerator
Usage Guidelines
Using this command without options displays detailed information about each of the TFO connections for a WAE. To display a summary list of the connections, use the summary option.
For the listed connections that have the F, D or L optimization policy, you can find additional information on DRE statistics by using the show statistics dre connection command with the id option to identify a specific connection id.
Examples
The following example displays a summary of TFO optimized connections for the WAE:
WAE# show tfo connection summaryOptimized Connection ListPolicy summary order: Our's, Peer's, Negotiated, AppliedF: Full optimization, D: DRE only, L: LZ Compression, T: TCP OptimizationLocal-IP:Port Remote-IP:Port ConId PeerId Policy10.77.156.99:59950 10.77.156.106:10005 21 00:11:25:ac:3e:04 F,F,F,F10.77.156.99:59951 10.77.156.106:10007 22 00:11:25:ac:3e:04 F,F,F,F10.77.156.99:59952 10.77.156.106:10008 23 00:11:25:ac:3e:04 F,F,F,F10.77.156.99:59953 10.77.156.106:10009 24 00:11:25:ac:3e:04 F,F,F,F10.77.156.99:59954 10.77.156.106:10010 25 00:11:25:ac:3e:04 F,F,F,FRelated Commands
show statistics dre connection
show tfo filtering
To display information about the incoming and outgoing TFO flows that the WAE currently has, use the show tfo filtering EXEC command.
show tfo filtering [list]
Syntax Description
Command Modes
EXEC
Device Modesapplication-accelerator
Usage Guidelines
This command lists TCP flows that the WAE is currently optimizing. It also includes TCP flows that are not being optimized but that are being passed through by the WAE. A "P" in the State column indicates a passed through flow.
Examples
The following examples display TFO connection information for the WAE:
WAE# show tfo filteringNumber of filtering tuples: 2Packets dropped due to ttl expiry: 0Packets dropped due to bad route: 0Syn packets dropped with our own id in the options: 0Syn packets received and dropped on estab. conn: 0Syn-Ack packets received and dropped on estab. conn: 0Packets recvd on in progress conn. and not handled: 0Packets dropped due to peer connection alive: 0Packets dropped due to invalid TCP flags: 0WAE# show tfo filtering listE: Established, S: Syn, A: Ack, F: Fin, R: Resets: sent, r: received, O: Options, P: PassthroughB: Bypass, T: Timedout, C: ClosedLocal-IP:Port Remote-IP:Port Tuple(Mate) State10.99.11.200:1398 10.99.22.200:80 0xcba709c0(0xcba70a00) E10.99.11.200:1425 10.99.22.200:80 0xcba70780(0xcba707c0) E10.99.11.200:1439 10.99.22.200:5222 0xcba703c0(0xcba70b40) Sr10.99.11.200:1440 10.99.22.200:5222 0xcba70400(0xcba70440) Sr10.99.22.200:1984 10.99.11.200:80 0xcba70600(0xcba70640) E10.99.22.200:1800 10.99.11.200:23 0xcba70480(0x0 ) PE10.99.11.200:1392 10.99.22.200:80 0xcba70f80(0x0 ) E10.99.22.200:20 10.99.11.200:1417 0xcba701c0(0xcba70180) E10.99.11.200:1417 10.99.22.200:20 0xcba70180(0x0 ) E10.99.22.200:1987 10.99.11.200:80 0xcba70240(0xcba70200) E10.99.11.200:1438 10.99.22.200:5222 0xcba70900(0xcba70580) Sr10.99.22.200:1990 10.99.11.200:80 0xcba70100(0xcba70140) E10.99.22.200:80 10.99.11.200:1426 0xcba70740(0xcba70700) E10.99.22.200:80 10.99.11.200:1425 0xcba707c0(0xcba70780) E10.99.22.200:1985 10.99.11.200:80 0xcba70a40(0xcba70a80) E10.99.22.200:80 10.99.11.200:1410 0xcba70500(0xcba70540) E10.99.22.200:80 10.99.11.200:1398 0xcba70a00(0xcba709c0) E10.99.22.200:80 10.99.11.200:1392 0xcba70f40(0xcba70f80) ERelated Commands
show tfo status
To display global Traffic Flow Optimization (TFO) status information for a WAE, use the show tfo status EXEC command.
show tfo status
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example displays global TFO status information for the WAE:
WEA# show tfo statusOptimization Status:Configured: optimize fullCurrent: optimize fullTFO is up since Sat Feb 25 13:18:51 2006TFO is functioning normally.Total number of optimized connections since start: 0Number of active connections: 0Total number of peers: 0Related Commands
show transaction-logging
To display the transaction log configuration settings and a list of archived transaction log files for a WAE, use the show transaction-logging EXEC command.
show transaction-logging
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
Usage Guidelines
To display information about the current configuration of transaction logging on a WAE, use the show transaction-log or show transaction-logging EXEC commands. Both of these EXEC commands display the same output. Transaction log file information is displayed for HTTP and WMT MMS caching proxy transactions and TFTP and ICAP transactions.
Note
Examples
The following example displays information about the current configuration of transaction logging on a WAE:
WAAE# show transaction-loggingTransaction log configuration:---------------------------------------TFO Logging is disabled.TFO Archive interval: every-day every 1 hourTFO Maximum size of archive file: 2000000 KBTFO logging to remote syslog host is disabled.TFO remote syslog host is not configured.TFO facility is the default "*" which is "user".Exporting files to ftp servers is disabled.Related Commands
show user
To display user identification number and username information for a particular user of a WAAS device, use the show user EXEC command.
show user {uid number | username name}
Syntax Description
Command Default
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following examples display user-specific configuration information based on username and user identification, respectively:
WAE# show user username jdoeUid : 1426Username : jdoePassword : *****Privilege : super userConfigured in : Local databaseWAE# show user uid 1426Uid : 1426Username : jdoePassword : *****Privilege : super userConfigured in : Local databaseRelated Commands
show users administrative
To display users with administrative privileges to the WAAS device, use the show users EXEC command.
show users administrative
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays user who have administrative privileges:
WAE# show users administrativeUID USERNAME0 adminRelated Commands
show version
To display version information about the WAAS software that is running on the WAAS device, use the show version EXEC command.
show version [last | pending]
Syntax Description
last
Displays the version information for the last saved image.
pending
Displays the version information for the pending upgraded image.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays the version information for the last saved image:
WAE# show version lastSaved version is WAAS 4.0.0-b330, built on 18:28:11 Mar 23 2006 by cnbuildIt can be restored by running restore rollback commandThe following example displays the version information for the pending upgraded image:
WAE# show versionCisco 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 2006)Version: fe611-4.0.0.340Compiled 17:26:17 Mar 25 2006 by cnbuildSystem was restarted on Mon Mar 27 15:25:01 2006.The system has been up for 3 days, 21 hours, 26 minutes, 15 seconds.show wccp
To display Web Cache Connection Protocol (WCCP) information for a WAE, use the show wccp EXEC command.
show wccp file-engines
show wccp flows {cifs-cache | tcp-promiscuous} [summary]
show wccp gre
show wccp masks {cifs-cache | tcp-promiscuous} [summary]
show wccp modules
show wccp routers
show wccp services [detail]
show wccp slowstart {cifs-cache | tcp-promiscuous} [summary]
show wccp status
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example shows the output of the show wccp gre command:
WAE# show wccp greTransparent GRE packets received: 0Transparent non-GRE packets received: 0Transparent non-GRE packets passed through: 0Total packets accepted: 0Invalid packets received: 0Packets received with invalid service: 0Packets received on a disabled service: 0Packets received too small: 0Packets dropped due to zero TTL: 0Packets dropped due to bad buckets: 0Packets dropped due to no redirect address: 0Packets dropped due to loopback redirect: 0Connections bypassed due to load: 0Packets sent back to router: 0Packets sent to another CE: 0GRE fragments redirected: 0Packets failed GRE encapsulation: 0Packets dropped due to invalid fwd method: 0Packets dropped due to insufficient memory: 0Packets bypassed, no conn at all: 0Packets bypassed, no pending connection: 0Packets due to clean wccp shutdown: 0Packets bypassed due to bypass-list lookup: 0For a description of the fields in the output of the show wccp gre command, see the show statistics wccp command.
The following example shows the output of the show wccp modules command:
WAE# show wccp modulesModules registered with WCCP on this WAEModule Socket Expire(sec) Name Supported Services------ ------ ----------- --------------- ------------------0 18 3 ? CIFS CacheThe following example shows the output of the show wccp services command:
WAE# show wccp servicesServices configured on this File EngineTCP Promiscuous 61TCP Promiscuous 62The following example is partial output from the show wccp services detail command:
WAE# show wccp services detailService Details for TCP Promiscuous 61 ServiceService Enabled : YesService Priority : 34Service Protocol : 6Application : UnknownService Flags (in Hex) : 501Service Ports : 0 0 0 0: 0 0 0 0Security Enabled for Service : NoMulticast Enabled for Service : NoWeight for this Web-CE : 0Negotiated forwarding method : GRENegotiated assignment method : HASHNegotiated return method : GREReceived Values:Source IP mask (in Hex) : 0Destination IP mask (in Hex) : 0Source Port mask (in Hex) : 0Destination Port mask (in Hex) : 0Calculated Values:Source IP mask (in Hex) : 0Destination IP mask (in Hex) : 1741Source Port mask (in Hex) : 0Destination Port mask (in Hex) : 0Service Details for TCP Promiscuous 62 ServiceService Enabled : YesService Priority : 34Service Protocol : 6Application : UnknownService Flags (in Hex) : 502Service Ports : 0 0 0 0: 0 0 0 0Security Enabled for Service : NoMulticast Enabled for Service : NoWeight for this Web-CE : 0Negotiated forwarding method : GRENegotiated assignment method : HASHNegotiated return method : GREReceived Values:Source IP mask (in Hex) : 0Destination IP mask (in Hex) : 0Source Port mask (in Hex) : 0Destination Port mask (in Hex) : 0Calculated Values:Source IP mask (in Hex) : 0Destination IP mask (in Hex) : 1741Source Port mask (in Hex) : 0Destination Port mask (in Hex) : 0The following example is the output from the show wccp routers command:
WAE# show wccp routersRouter Information for Service: TCP Promiscuous 61Routers Configured and Seeing this File Engine(1)Router Id Sent To Recv ID0.0.0.0 10.10.20.1 00000000Routers not Seeing this File Engine10.10.20.1Routers Notified of but not Configured-NONE-Multicast Addresses Configured-NONE-Router Information for Service: TCP Promiscuous 62Routers Configured and Seeing this File Engine(1)Router Id Sent To Recv ID0.0.0.0 10.10.20.1 00000000Routers not Seeing this File Engine10.10.20.1Routers Notified of but not Configured-NONE-Multicast Addresses Configured-NONE-The following example is the output from the show wccp status command:
WAE# show wccp statusWCCP version 2 is enabled and currently activeRelated Commands
show windows-domain
To display Windows domain configuration information for a WAAS device, use the show windows-domain EXEC command.
show windows-domain
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Examples
The following example displays Windows domain configuration information:
WAE# show windows-domainLogin Authentication for Console/Telnet Session: disabledConfiguration Authentication for Console/Telnet Session: disabledWindows domain Configuration:-----------------------------Workgroup:Comment:Net BIOS:Realm:WINS Server: 0.0.0.0Password Server: 0.0.0.0Security: domainAdministrative groups:Super user group:Normal user group:Related Commands
shutdown
To shut down the WAAS device use the shutdown EXEC command.
shutdown [poweroff]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
A controlled shutdown refers to the process of properly shutting down a WAAS device without turning off the power on the device. With a controlled shutdown, all of the application activities and the operating system are properly stopped on a WAE, but the power remains on. Controlled shutdowns of a WAAS device can help you minimize the downtime when the WAAS device is being serviced.
Caution
Note
The shutdown EXEC command facilitates a proper shutdown for WAAS device, and is supported on all WAE hardware models. The shutdown poweroff command is also supported by all of the WAE hardware models as they support the ACPI.
The shutdown command closes all applications and stops all system activities, but keeps the power on. The fans continue to run and the power LED is on, indicating that the device is still powered on. The device console displays the following menu after the shutdown process is completed:
================= SHUTDOWN SHELL =================System has been shut down.You can0. Power down system by pressing and holding power button1. Reload system by software2. Power down system by software[1-2]?The shutdown poweroff command closes all applications and the operating system, stops all system activities, and turn off the power. The fans stop running and the power LED starts flashing, indicating that the device has been powered off.
Note
The following table describes the shutdown-only operation and the shutdown poweroff operation for a WAAS device.
You can enter the shutdown EXEC command from a console session or from a remote session (Telnet or SSH version 1 or SSH version 2) to perform shutdown on a WAAS device.
To perform a shutdown on a WAAS device, enter the shutdown EXEC command as follows:
WAE# shutdownWhen you are asked if you want to save the system configuration, enter yes.
System configuration has been modified. Save?[yes]:yesWhen you are asked if you want to proceed with the shutdown, press Enter to proceed with the shutdown operation.
Device can not be powered on again through software after shutdown.Proceed with shutdown?[confirm]A message appears, reporting that all services are being shut down on this WAE.
Shutting down all services, will timeout in 15 minutes.
shutdown in progress ..System halted.After the system is shut down (the system has halted), a WAAS software shutdown shell displays the current state of the system (for example, "System has been shut down") on the console. You are asked whether you want to perform a software power off (the Power down system by software option), or if you want to reload the system through the software.
================= SHUTDOWN SHELL =================System has been shut down.You can eitherPower down system by pressing and holding power buttonor1. Reload system through software2. Power down system through softwareTo power down the WAAS device, press and hold the power button on the WAAS device, or use one of the following methods to perform a shutdown poweroff:
•
================= SHUTDOWN SHELL =================System has been shut down.You can eitherPower down system by pressing and holding power buttonor1. Reload system through software2. Power down system through software•
WAE# shutdown poweroffWhen you are asked if you want to save the system configuration, enter yes.
System configuration has been modified. Save?[yes]:yesWhen you are asked to confirm your decision, press Enter.
Device can not be powered on again through software after poweroff.Proceed with poweroff?[confirm]Shutting down all services, will timeout in 15 minutes.poweroff in progress ..Power down.Examples
In the following example, the shutdown command is used to close all applications and stop all system activities.
WAE1# shutdownSystem configuration has been modified. Save?[yes]:yesDevice can not be powered on again through software after shutdown.Proceed with shutdown?[confirm]Shutting down all services, will timeout in 15 minutes.shutdown in progress ..System halted.In the following example, the shutdown poweroff command is used to close all applications, stop all system activities, and then turn off power to the WAAS device.
WAE2# shutdown poweroffSystem configuration has been modified. Save?[yes]:yesDevice can not be powered on again through software after poweroff.Proceed with poweroff?[confirm]Shutting down all services, will timeout in 15 minutes.poweroff in progress ..Power down.snmp trigger
To configure thresholds for a user-selected MIB object for monitoring purposes on a WAAS device, use the snmp trigger EXEC command. Use the no form of this command to return the setting to the default value.
snmp trigger {create mibvar [wildcard] [wait-time [absent [LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE] | equal [absolute value [[LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE] | delta value [LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE]] | falling [absolute value [LINE | mibvar1 mibvar] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE] | delta value [LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE]] | greater-than [absolute value [LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE] | delta value [LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE]] | less-than [absolute value [LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE] | delta value [LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE]] | on-change [[LINE | mibvar1 mibvar1][LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE]] | present [LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE] | rising [absolute value [LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE] | delta value [LINE | mibvar1 mibvar1] [LINE | mibvar2 mibvar2] [LINE | mibvar3 mibvar3] [LINE]]]] | delete mibvar}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Using the snmp trigger global configuration command, you can define additional SNMP traps for other MIB objects of interest to your particular configuration. You can select any MIB object from any of the support MIBs for your trap. The trap can be triggered based on a variety of tests:
•
•
•
•
•
•
•
•
The threshold value can be based on an absolute sample type or on a delta sample type. An absolute sample type is one in which the test is evaluated against a fixed integer value between zero and 4294967295. A delta sample type is one in which the test is evaluated against the change in the MIB object value between the current sampling and the previous sampling.
After you configure SNMP traps, you must use the snmp-server enable traps event global configuration command for the event traps you just created to be generated. Also, to preserve SNMP trap configuration across a system reboot, you must configure event persistence using the snmp mib persist event global configuration command, and save the MIB data using the write mib-data EXEC command.
Examples
The following example shows how to create a threshold for the MIB object esConTabIsConnected so that a trap is sent when the connection from the Edge WAE to the Core WAE is lost:
WAE# snmp trigger create esConTabIsConnected ?<60-600> The number of seconds to wait between trigger samplewildcard Option to treat the MIB variable as wildcardedWAE# snmp trigger create esConTabIsConnected wildcard 600 ?absent Absent existence testequal Equality threshold testfalling Falling threshold testgreater-than Greater-than threshold testless-than Less-than threshold teston-change Changed existence testpresent Present present testrising Rising threshold testWAE# snmp trigger create esConTabIsConnected wildcard 600 falling ?absolute Absolute sample typedelta Delta sample typeWAE# snmp trigger create esConTabIsConnected wildcard 600 falling absolute ?<0-4294967295> Falling threshold valueWAE# snmp trigger create esConTabIsConnected wildcard 600 falling absolute 1 ?LINE Trigger-commentmibvar1 Optional mib object to add to the notificationWAE# snmp trigger create esConTabIsConnected wildcard 600 falling absolute 1 "Lost the connection with the core server."WAE# configureWAE(config)# snmp-server enable traps eventOnce you have configured the WAE to send SNMP traps, you can view the results of these newly created traps using the show snmp events EXEC command.
You can also delete user-created SNMP traps. The following example shows how to delete the trap set for esConTabIsConnected that we created in the previous example.
WAE# snmp trigger delete esConTabIsConnectedRelated Commands
(config) snmp-server community
(config) snmp-server enable traps
(config) snmp-server notify inform
ssh
To allow secure encrypted communications between an untrusted client machine and a WAAS device over an insecure network, use the ssh EXEC command.
ssh options
Syntax Description
options
The options to use with the ssh EXEC command. For more information about the possible options, see Request for Comments (RFC 4254) at http://www.rfc-archive.org/getrfc.php?rfc=4254.
Defaults
By default, the Secure Shell (SSH) feature is disabled on a WAAS device.
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
SSH consists of a server and a client program. Like Telnet, you can use the client program to remotely log in to a machine that is running the SSH server, but unlike Telnet, messages transported between the client and the server are encrypted. The functionality of SSH includes user authentication, message encryption, and message authentication.
Note
Related Commands
tcpdump
To dump network traffic, use the tcpdump EXEC command.
tcpdump [LINE]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
TCPdump is a utility that allows a user to intercept and capture packets passing through a network interface, making it useful for troubleshooting network applications.
During normal network operation, only the packets which are addressed to a network interface are intercepted and passed on to the upper layers of the TCP/IP protocol layer stack. Packets which are not addressed to the interface are ignored. In Promiscuous mode, the packets which are not intended to be received by the interface are also intercepted and passed on to the higher levels of the protocol stack. TCPdump works by putting the network interface into promiscuous mode. TCPdump uses the free libpcap (packet capture library).
Use the -h option to view the options available, as shown in this example:
WAE# tcpdump -htcpdump version 3.8.1 (jlemon)libpcap version 0.8Usage: tcpdump [-aAdDeflLnNOpqRStuUvxX] [-c count] [ -C file_size ][ -E algo:secret ] [ -F file ] [ -i interface ] [ -r file ][ -s snaplen ] [ -T type ] [ -w file ] [ -y datalinktype ][ expression ]Examples
The following example starts a network traffic dump to a file named tcpdump.txt:
WAE# tcpdump -F tcpdump.txtRelated Commands
telnet
To log in to a WAAS device using the Telnet client, use the telnet EXEC command.
telnet {hostname | ip-address} [portnum]
Syntax Description
hostname
Hostname of the network device.
ip-address
IP address of the network device.
portnum
(Optional) Port number (1-65535). Default port number is 23.
Defaults
The default port number is 23.
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
UNIX shell functions such as escape and the suspend command are not available in the Telnet client. Multiple Telnet sessions are also not supported. This Telnet client allows you to specify a destination port.
Examples
The following examples show several ways you can log in to a WAAS device using the Telnet client:
WAE# telnet cisco-waeWAE# telnet 10.168.155.224WAE# telnet cisco-wae 2048WAE# telnet 10.168.155.224 2048Related Commands
terminal
To set the number of lines displayed in the console window, or to display the current console debug command output, use the terminal EXEC command.
terminal {length length | monitor [disable]}
Syntax Description
Defaults
The default is 24 lines.
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
When 0 is entered as the length parameter, the output to the screen does not pause. For all nonzero values of length, the -More- prompt is displayed when the number of output lines matches the specified length number. The -More- prompt is considered a line of output. To view the next screen, press the Spacebar. To view one line at a time, press the Enter key.
The terminal monitor command allows a Telnet session to display the output of the debug commands that appear on the console. Monitoring continues until the Telnet session is terminated.
Examples
The following example sets the number of lines to display to 20:
WAE# terminal length 20The following example configures the terminal for no pausing:
WAE# terminal length 0Related Commands
All show commands
tethereal
To analyze network traffic from the command line, use the tethereal EXEC command.
tethereal [LINE]
Syntax Description
Defaults
No default behavior values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Tethereal is the command line version of the network traffic analyzer tool Ethereal. Like TCPdump, it also uses the packet capture library (libpcap). Aside from network traffic analysis, Tethereal also provides facilities for decoding packets.
The following example shows the options available with the WAAS tethereal command:
WAE# tethereal -hThis is GNU tethereal 0.10.6(C) 1998-2004 Gerald Combs <gerald@ethereal.com>Compiled with GLib 1.2.9, with libpcap 0.6, with libz 1.1.3, without libpcre,without UCD-SNMP or Net-SNMP, without ADNS.NOTE: this build does not support the "matches" operator for Ethereal filtersyntax.Running with libpcap (version unknown) on Linux 2.4.16.tethereal [ -vh ] [ -DlLnpqSVx ] [ -a <capture autostop condition> ] ...[ -b <number of ring buffer files>[:<duration>] ] [ -c <count> ][ -d <layer_type>==<selector>,<decode_as_protocol> ] ...[ -f <capture filter> ] [ -F <output file type> ] [ -i <interface> ][ -N <resolving> ] [ -o <preference setting> ] ... [ -r <infile> ][ -R <read filter> ] [ -s <snaplen> ] [ -t <time stamp format> ][ -T pdml|ps|psml|text ] [ -w <savefile> ] [ -y <link type> ][ -z <statistics string> ]Valid file type arguments to the "-F" flag:libpcap - libpcap (tcpdump, Ethereal, etc.)rh6_1libpcap - RedHat Linux 6.1 libpcap (tcpdump)suse6_3libpcap - SuSE Linux 6.3 libpcap (tcpdump)modlibpcap - modified libpcap (tcpdump)nokialibpcap - Nokia libpcap (tcpdump)lanalyzer - Novell LANalyzerngsniffer - Network Associates Sniffer (DOS-based)snoop - Sun snoopnetmon1 - Microsoft Network Monitor 1.xnetmon2 - Microsoft Network Monitor 2.xngwsniffer_1_1 - Network Associates Sniffer (Windows-based) 1.1ngwsniffer_2_0 - Network Associates Sniffer (Windows-based) 2.00xvisual - Visual Networks traffic capture5views - Accellent 5Views captureniobserverv9 - Network Instruments Observer version 9default is libpcapRelated Commands
traceroute
To trace the route between a WAAS device to a remote host, use the traceroute EXEC command.
traceroute {hostname | ip-address}
Syntax Description
Defaults
No default behavior values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Traceroute is a widely available utility on most operating systems. Much like ping, it is a valuable tool for determining connectivity in a network. Ping allows the user to find out if there is a connection between two end systems. Traceroute does this as well, but also lists the intermediate routers between the two systems. Users can therefore see the possible routes packets can take from one system to another. Use traceroute to find the route to a remote host, when either the hostname or the IP address is known.
Examples
The following example traces the route between the WAAS device and a device with an IP address of 10.0.0.0:
WAE# traceroute 10.0.0.0traceroute to 10.0.0.0 (10.0.0.0), 30 hops max, 38 byte packets1 sblab2-rtr.abc.com (192.168.10.1) 0.959 ms 0.678 ms 0.531 ms2 192.168.1.1 (192.168.1.1) 0.665 ms 0.576 ms 0.492 ms3 172.24.115.66 (172.24.115.66) 0.757 ms 0.734 ms 0.833 ms4 sjc20-sbb5-gw2.abc.com (192.168.180.93) 0.683 ms 0.644 ms 0.544 ms5 sjc20-rbb-gw5.abc.com (192.168.180.9) 0.588 ms 0.611 ms 0.569 ms6 sjce-rbb-gw1.abc.com (172.16.7.249) 0.746 ms 0.743 ms 0.737 ms7 sj-wall-2.abc.com (172.16.7.178) 1.505 ms 1.101 ms 0.802 ms8 * * *9 * * *...29 * * *30 * * *Related Commands
transaction-log
To force the exporting or the archiving of the transaction log, use the transaction-log EXEC command.
transaction-log {export | tfo force archive}
Syntax Description
export
Forces the archiving of a WAE's transaction file.
tfo force archive
Forces the archiving of the Traffic Flow Optimization (TFO) transaction log file.
Command Modes
EXEC
Device Modesapplication-accelerator
Examples
The following example forces the archiving of the transaction file on the WAE:
WAE# transaction-log exportThe following example forces the archiving of a WAE's TFO transaction log file:
WAE# transaction-log tfo force archiveRelated Commands
type
To display a file, use the type EXEC command.
type filename
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Use this EXEC command to display the contents of a file within any file directory on a WAAS device. This command may be used to monitor features such as transaction logging or system logging (syslog).
Examples
The following example shows how to display the contents of the syslog.txt file:
WAE# type /local1/syslog.txtRelated Commands
type-tail
To view a specified number of lines of the end of a log file, to view the end of the file continuously as new lines are added to the file, to start at a particular line in the file, or to include or exclude specific lines in the file, use the type-tail command in EXEC mode.
type-tail filename [line | follow | | {begin LINE | exclude LINE | include LINE}]
Syntax Description
Defaults
Last ten lines are shown.
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
This EXEC command allows you to monitor a log file by letting you view the end of the file. You can specify the number of lines at the end of the file that you want to view, or you can follow the last line of the file as it continues to log new information. To stop the last line from continuously scrolling as with the follow option, use the key sequence Ctrl-C.
You can further indicate the type of information to display using the output modifiers. These allow you to include or exclude specific lines or to indicate where to begin displaying the file.
Examples
The following example looks for a list of log files in the /local1 directory and then displays the last ten lines of the syslog.txt file. In this example, the number of lines to display is not specified, so the default of ten lines is used:
WAE# ls /local1actonacore_dircrashdbupgrade.logdowngradeerrorloglogslost+foundsaservice_logsspoolsyslog.txtsyslog.txt.1syslog.txt.2syslog.txt.3syslog.txt.4varwdd.sh.signedWAE# type-tail /local1/syslog.txtApr 17 00:21:09 edge-wae-11 java: %CE-CMS-4-700001: unable to get httpsequest throughput stats(error 4)Apr 17 00:21:09 edge-wae-11 java: %CE-CMS-4-700001: ds_getStruct got errr : 4 for key stat/cache/ftp connection 5Apr 17 00:21:09 edge-wae-11 java: %CE-CMS-4-700001: ds_getStruct: unableto get `stat/cache/ftp' from dataserverApr 17 00:21:09 edge-wae-11 java: %CE-CMS-4-700001: unable to get ftp-ovr-http request throughput stats(error 4)Apr 17 00:21:09 edge-wae-11 java: %CE-CMS-4-700001: setValues getMethodall ...Apr 17 00:21:09 edge-wae-11 java: %CE-CMS-4-700001: setValues found...Apr 17 00:21:48 edge-wae-11 java: %CE-CMS-4-700001: ds_getStruct got errr : 4 for key stat/cache/http/perf/throughput/requests/sum connection 5Apr 17 00:21:48 edge-wae-11java: %CE-CMS-4-700001: ds_getStruct: unableto get `stat/cache/http/perf/throughput/requests/sum' from dataserverApr 17 00:21:48 edge-wae-11 java: %CE-CMS-4-700001: unable to get http rquest throughput stats(error 4)Apr 17 00:23:20 edge-wae-11 java: %CE-TBD-3-100000: WCCP_COND_ACCEPT: TULE DELETE conditional accept tuple {Source IP [port] = 0.0.0.0 [0] DestinatioIP [port] = 32.60.43.2 [53775] }returned error: -1 errno 9The following example follows the syslog.txt file as it grows:
WAE# type-tail /local1/syslog.txt followundebug
To disable debugging functions, use the undebug EXEC command. Also see the debug EXEC command. See the "debug" command for more information about debug functions.
undebug [aaa accounting | all | authentication [print-services | user] | buf [all | dmbuf | dmsg] | cdp [adjacency | events | ip | packets] | cli [all | bin | parser] | dataserver [all | clientlib | server] | dhcp | logging [all] | ntp | print-spooler [all | brief | errors | warnings] | snmp [all | cli | main | mib | traps] | wccp [all | detail | error | events | keepalive | packets | slowstart]]
Note
Syntax Description
Valid values for the option argument are as follows:
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
We recommend that the debug and undebug commands be used only at the direction of Cisco Systems technical support personnel.
Related Commands
wafs
To backup, restore, or create a system report about the Wide Area File Services (WAFS)-related network configuration, plus the configurations of file servers, printers, users, and so forth, on a WAE, use the wafs EXEC command.
wafs {backup-config filename | restore-config filename |
sysreport [filename | date-range from_date end_date filename]}
Note
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
Usage Guidelines
The wafs backup-config EXEC command is used when back up of basic network configuration is not sufficient (performed using the copy running-config command), for example, when you want to back up system configurations before making any changes using the WAAS CLI global configuration mode and you want to protect the current configuration from loss of data by erroneous operations.
The wafs restore-config automatically performs a reload function. We strongly recommend that you re-register your WAE on completion of this command.
This wafs command is also useful when backup and system restoration, or generation of a system report, are not available from the WAAS Central Manager GUI.
Examples
The following example creates a backup file of the WAFS configuration information:
WAE# wafs ?backup-config backup system configurations to a file.restore-config restore system configurations from a file. WARNING: Afterrestoring configuration, the system needs to be restarted andre-registered.sysreport system report to a fileWAE# wafs backup-config backup.tar.gzsystem configuration is stored in file /local/local1/backup.tar.gzThe following example restores a system with previously saved WAAS configuration information:
WAE# wafs restore-config backup.tar.gzRestoring configurations ...After upload is completed the File Engine will be reloaded. We strongly recommend you re-register after the engine is reloaded.Related Commands
whoami
To display the username of the current user, use the whoami EXEC command.
whoami
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Use this EXEC command to display the username of the current user.
Examples
The following example displays your username:
WAE# whoamiadminRelated Commands
windows-domain
To access the Windows domain utilities on a WAAS device, use the windows-domain EXEC command.
windows-domain diagnostics {findsmb | getent | net | nmblookup | smbclient | smbstatus | smbtree | tdbbackup | tdbdump | testparm | wbinfo}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Use this command to activate the selected Windows domain diagnostic utility.
The following example shows the options available for the Get Entity utility:
WAE# windows-domain diagnostics getent --helpUsage: getent [OPTION...] database [key ...]getent - get entries from administrative database.-s, --service=CONFIG Service configuration to be used-?, --help Give this help list--usage Give a short usage message-V, --version Print program versionMandatory or optional arguments to long options are also mandatory or optionalfor any corresponding short options.Supported databases:aliases ethers group hosts netgroup networks passwd protocols rpcservices shadowThe following example shows the options available for the NMB Lookup Utility for troubleshooting NetBIOS name resolution and browsing:
WAE# windows-domain diagnostics nmblookup -hUsage: [-?TV] [--usage] [-B BROADCAST-ADDRESS] [-f VAL] [-U STRING] [-M VAL][-R VAL] [-S VAL] [-r VAL] [-A VAL] [-d DEBUGLEVEL] [-s CONFIGFILE][-l LOGFILEBASE] [-O SOCKETOPTIONS] [-n NETBIOSNAME] [-W WORKGROUP][-i SCOPE] <NODE> ...The following example shows the options available for the Samba Client Utility for troubleshooting the Windows environment and integration:
WAE# windows-domain diagnostics smbclient -hUsage: [-?EgVNkP] [--usage] [-R NAME-RESOLVE-ORDER] [-M HOST] [-I IP] [-L HOST][-t CODE] [-m LEVEL] [-T <c|x>IXFqgbNan] [-D DIR] [-c STRING] [-b BYTES][-p PORT] [-d DEBUGLEVEL] [-s CONFIGFILE] [-l LOGFILEBASE][-O SOCKETOPTIONS] [-n NETBIOSNAME] [-W WORKGROUP] [-i SCOPE][-U USERNAME] [-A FILE] [-S on|off|required] service <password>The following example shows the options available for the TDB Backup Utility:
WAE# windows-domain diagnostics tdbbackup -hUsage: tdbbackup [options] <fname...>-h this help message-s suffix set the backup suffix-v verify mode (restore if corrupt)The following example shows the use of the -u option of the WinBind Utility to view the information about a user registered in a Windows domain:
WAE# windows-domain diagnostics wbinfo -uadministratorguestuser98tuser1WAE# show user username user98Uid : 70012Username : user98Password : *****Privilege : super userConfigured in : Windows Domain databaseWAE# show user uid 70012Uid : 70012Username : user98Password : *****Privilege : super userConfigured in : Windows Domain databaseThe following example shows how to register a Windows domain:
WAE# windows-domain diagnosticsnet join -S<domain server> -U<domain admin username>%<domain admin password>Related Commands
write
To save startup configurations on a WAAS device, use the write EXEC command.
write [erase | memory | mib-data | terminal]
Syntax Description
Defaults
The configuration is written to NVRAM by default.
Command Modes
EXEC
Device Modesapplication-accelerator
central-manager
Usage Guidelines
Use this command to either save running configurations to NVRAM or to erase memory configurations. Following a write erase command, no configuration is held in memory, and a prompt for configuration specifics occurs after you reboot the WAAS device.
Use the write terminal command to display the current running configuration in the terminal session window. The equivalent command is show running-config.
Examples
The following example saves the current startup configuration to memory:
WAE# write memoryRelated Commands
