|
|
This appendix provides a summary of the commands used to configure your Cisco Cache Engine.
The commands are grouped alphabetically in three categories: general (EXEC) commands, global configuration commands, and show (EXEC) commands.
The command-line interface (CLI) uses the following conventions:
Command descriptions use the following conventions:
Enter commands by typing their names at the EXEC prompt and pressing the Return key.
There is two EXEC prompt levels: privileged and user. The enable/disable command switches between the two EXEC levels. The user EXEC level prompt is available to users if they enter a password. This prompt is the server name followed by a pound sign (#), as in this example:
Console#
Use the following key sequences to edit commands when you type commands at the EXEC prompt:
As a shortcut, you can abbreviate commands to the fewest letters that make them unique. For example, letters sho can be entered for the show command, for example.
Certain EXEC commands display multiple screens with the following prompt at the bottom of the screen:
--More--
Press the Spacebar to continue the output or press Return to display the next line. Press any other key to return to the prompt. Also, at the --More-- prompt, you can enter a ? to display the help message.
To get out of EXEC mode, use the exit command at the system prompt:
Console# exit
To enter the global configuration mode, use the configure EXEC command. You must be in global configuration mode to enter global configuration commands.
Console# configure
Console(config)#
To exit global configuration mode, use the end global configuration command:
Console(config)# end
You can also exit global configuration mode, by entering the exit command or pressing Ctrl-Z.
To enter the interface configuration mode, from the global configuration mode prompt enter the interface you with to configure:
Console(config)# interface ethernet 0
Console(config-if)#
The interface configuration commands are:
autosense
bandwidth
exit
fullduplex
halfduplex
ip
no
These commands are described in the section following the global configuration commands.
To exit interface configuration mode, enter exit to return to global configuration mode:
cache4J(config-if)# exit
cache4J(config)#
The user interface provides error isolation in the form of an error indicator, a caret symbol (^). The ^ symbol appears at the point in the command string where you have entered an incorrect command, keyword, or argument.
In the following example, suppose you want to set the clock. Use context-sensitive help to check the syntax for setting the clock.
An example of a mistake is:
Console# clock set 1222
^
% Invalid input detected at `^' marker.
Console# clock ?
set Set the time and date
Console# clock
The help output shows that the set keyword is required. Check the syntax for entering the time:
Console# clock set ?
hh:mm:ss Current time
Console# clock set
Enter the current time:
Console# clock set 13:32:00
% Incomplete command.
The system indicates that you need to provide additional arguments to complete the command. Press the Up Arrow to automatically repeat the previous command entry. Then add a space and question mark (?) to reveal the additional arguments:
Console# clock set 13:32:00 ?
<1-31> Day of the month
January Month of the year
Now you can complete the command entry:
Console# clock set 13:32:00 23 February 97
^
% Invalid input detected at '^' marker.
The caret symbol (^) and help response indicate an error at 97. To list the correct syntax, enter the command up to the point where the error occurred and then enter a question mark (?):
Console# clock set 13:32:00 23 February ?
<1993-2035> Year
Console# clock set 13:32:00 23 February
Enter the year using the correct syntax and press Return to execute the command:
Console# clock set 13:32:00 23 February 1997
You can obtain help when you enter commands by using the following methods:
Console# cl?
clear clock
Console# clock ?
clear Clear the current time from the battery-backed clock
save Save the current time into the battery-backed clock
set Set the local time and date
To avoid losing new configurations, save them to NVRAM:
Console# copy running-config startup-config
Console# Ctrl-Z
Console# write
See the command description for the copy running-config startup-config command for more information on the running versus saved configuration modes.
Ctrl-Z does not save the configuration, it just exits you from the global configuration mode.
The general (or EXEC) Cache Engine commands are entered in the EXEC mode. This section describes the following EXEC commands.
To synchronize the cache file system contents from memory to disk, use the cache sync EXEC command.
cache syncTo clear the disk of all cached content, use the cache clear EXEC command.
cache clearclear Clears the cache.
sync Synchronizes the cache.
Use the cache clear command to remove all cached contents from the cache file system. The equivalent to this command is the clear cache command. Both of these commands will erase, reformat, and remount the cache file system to disk. The cache clear command also performs these operations for all CFS file systems.
 | Caution This command is irreversible and all cached content will be erased. Use this command only if you are certain you need to do this. |
The cache sync command synchronizes the cache file system contents from memory to disk. Although synchronization is performed at regular intervals while the Cache Engine is running, this command can be used to ensure all data is written to disk before resetting or turning off the Cache Engine. Synchronization can also be done using the cfs sync command.
Console# cache clear
clear cache
cfs
To change directory, use the cd EXEC command.
cd {directoryname}directoryname Name of the directory.
Use this command to maneuver 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 "/".
Relative path:
Console# cd etc
Absolute path:
Console# cd /local/etc
dir
lls
ls
mkdir
pwd
rmdir
type
To manipulate the cache object file system of the Cache Engine, use the cfs EXEC command.
cfs {mount volname | unmount volname | format volname | sync volname}mount Mounts a cache file system.
unmount Amounts a cache file system.
format Erases and formats or creates a file system for caching.
sync Synchronizes a cache file system.
volname Volume name (for example, c0t0d0s3).
The cfs (cache file system) is the portion of the drive that saves the cache objects retrieved from the web. This does not effect the dosfs partition, which saves user data, such as syslog.
The cfs commands are used to manage the cache object file system.
The cfs format command creates the cache file system internal "dbs" for the cfs partition of the disk if the volume is unmounted. It formats the cfs partition to prepare it for a cfs mount. The cfs mount command creates and maps data structures in memory to the cfs partition.
The cfs unmount command frees the in-memory data structures that maps to the physical (disk) cfs partition.
The cfs sync command synchronizes the cache file system contents from memory to disk. Although synchronization is performed at regular intervals while the Cache Engine is running, this command can be usd to ensure all data is written to disk before resetting or turning off the Cache Engine. Synchronization can also be done with the cache sync command.
Use the show cfs command to find out what volume names and types.
Console# cfs sync c0t0d0s3
show cfs
cache clear
clear cache
To check if superuser accounts are password protected, use the check EXEC command.
check superuser passwordssuperuser Keyword.
passwords Keyword.
By default, superuser accounts are not password protected.
This command will display whether or not the superuser account is password protected. To configure a superuser password, from global configuration mode, use the user modify command. A superuser is defined as an administrator or user with full read and write privileges to the cache files and utilities.
Console# check superuser passwords
----------------------------------------------------------------------
All super-user accounts are password protected
----------------------------------------------------------------------
user modify
show user
To clear the HTTP object cache, the hardware interface, statistics, or WCCP settings, use the clear EXEC command.
clear {cache | interface serial number | statistics {all | history | icp {all | client | server | running} | wccp {bypass-counters | bypass-list}}cache Clears the HTTP object cache.
interface Clears the Hardware interface.
serial Serial device.
number Serial interface number (for example, 0).
statistics Clears HTTP object cache statistics.
all Clears all statistics.
history Clears the statistics history.
icp Clears ICP statistics.
all Clears all ICP statistics.
client Clears ICP client statistics
server Clears ICP server statistics.
running Clears the running statistics.
wccp Clears wccp settings.
bypass-counters Clears the AUTH and LOAD bypass counters.
bypass-list Clears the AUTH and LOAD bypass lists.
The clear cache command is used to clear all stored objects (cached content) from the cache file system. In its entirety, this command unmounts, reformats, and remounts the cache file system, thus erasing all stored objects. The cache clear command is the equivalent to the clear cache command.
The clear interface command clears the statistics presented by the show interface command.
The clear statistics command clears all statistical counters from the parameters given. Use this command to monitor fresh statistical data for some or all features without losing cached objects or configurations.
The clear wccp command clears wccp authentication bypass client/server pairs, load-bypass lists, and bypass statistics. Refer to the wccp EXEC commands for further information.
Console# clear cache
show statistics
show interface
show wccp
To set, clear, or save the battery-backed clock functions, use the clock EXEC command.
clock {clear | save | set hh:mm:ss day month year}clear Clears the system clock settings.
save Saves the system clock settings.
set Sets the system clock.
hh:mm:ss Current time (for example, 13:32:00).
day Day of the month (for example, 1 to 31).
month Current month (for example, January, February).
year Current year (for example, 1999).
If you have an outside source on your network that provides time services (such as an NTP server), you do not need to set the system clock manually. When setting the clock, enter the local time. The Cache Engine adjusts to GMT8 based on the time zone set in global configuration mode.
There are two clocks in the system; the software clock and the hardware clock. The software uses the software clock. The hardware clock is used only at boot to initialize the software clock.
The set keyword sets the software clock and saves the value in the hardware clock.
The save keyword writes the current value of the software clock into the hardware clock. This is used to update the hardware clock with the correct time as maintained by NTP. NTP adjusts only the software clock.
The clear keyword forces the hardware clock to zero (January 1, 1970), which ensures that the time at boot is the NTP time or obviously invalid.
Console# clock set 13:32:00 22 April 1999
clock timezone
show clock
To enter global configuration mode, use the configure EXEC command. You must be in global configuration mode to enter global configuration commands.
configureTo exit global configuration mode, use the end global configuration command. You may also use Ctrl-Z or exit.
This command has no arguments or keywords.
Use this command to enter global configuration mode.
Console# configure
Enter configuration commands, one per line. End with CNTL/Z.
Console(config)#
show running-config
show startup-config
end
exit
Ctrl-Z
To copy configuration or image data from a source to a destination, use the copy EXEC command.
copy {disk flash imagename | disk startup-config filename | flash disk imagename | running-config disk filename | running-config startup-config | running-config tftp | startup-config disk filename | startup-config tftp | tech-support disk filename | tech-support tftp | tftp disk | tftp flash}disk Copies image or configuration from or to disk.
flash Copies image from or to Flash memory.
running-config Copies from current system configuration.
startup-config Copies from or to startup configuration.
tech-support Copies system information for technical support.
tftp Copies image from or to TFTP server.
imagename Image name (for example, /local/bin).
filename Filename of configuration.
Use the copy running-config startup-config command to save configuration to NVRAM memory. This command is equivalent to the write command.
The copy flash disk imagename command will copy the image from the Flash memory to the disk.
The copy disk flash imagename command will copy the image from the disk to the flash.
The copy tftp flash command will copy the image from a TFTP server to Flash memory.
The copy tech-support tftp command will copy technical support information to a TFTP server. You will be prompted for the server address following this command.
Console# copy disk flash /local/bin
write
show running-config
show startup-config
To copy one filename to another filename, use the cpfile EXEC command.
cpfile oldfilename newfilenameoldfilename Name of the old file from which to copy.
newfilename Name of the new file to copy to.
Use this command to copy one filename to another. This command only copies dosfs files.
Console# cpfile ce500-194616.bin cd500-194618.bin
copy
dir
lls
ls
mkfile
rmdir
rmname
To enable debugging for a variety of services, use the debug EXEC mode command. The no form of this command disables the debugging functions.
debug {all | cron | ftp-server | http httpsubcommands debugsubcommands | icp icpsubcommands debugsubcommands | inetd | logging loggingsubcommands | ntp debuglevel | radius radiussubcommands debugsubcommands | rcpd | snmp snmpsubcommands debugsubcommands | stats statssubcommands | tftp-server | translog translogsubcommands | wccp wccpsubcommands | wi wisubcommands debugsubcommands}all Enable all debugging.
cron CRON.
ftp-server FTP server.
http HTTP debug commands.
icp Internet Cache Protocol debug commands.
inetd INETD Daemon.
logging LOG debug commands
ntp Sets the debug level.
radius RADIUS debug commands.
rcpd RCPD.
snmp SNMP debug commands.
stats STATS debug commands.
tftp-server TFTP server.
translog Transaction log debug commands.
wccp WCCP information.
wi Web Interface debug commands.
debuglevel NTP debug level (0 to 100).
httpsubcommands:
all HTTP all debug.
cache HTTP cache debug.
header HTTP header debug.
hit HTTP hit debug.
miss HTTP miss debug.
proxy HTTP proxy debug.
server HTTP server debug.
debugsubcommands:
all All debug.
error Error debug.
proc Procedure debug.
trace Trace debug.
icpsubcommands:
all ICP all modules debug.
client ICP client module debug.
ex ICP ex module debug.
heal ICP healing module debug.
main ICP main module debug.
parse ICP parse module debug.
print ICP print module debug.
server ICP server module debug.
utils ICP utility module debug.
loggingsubcommands:
all Logging all debug.
events Logging events debug.
url-track Logging URL tracking debug.
radiussubcommands:
all RADIUS debug all.
api RADIUS API debug.
app RADIUS application debug.
cli RADIUS CLI debug.
snmpsubcommands:
all SNMP all modules debug.
basic SNMP basic module debug.
cachefarm SNMP cache farm module debug.
diagdump SNMP diagdump module debug.
dns SNMP DNS module debug.
events SNMP events module debug.
farm SNMP farm module debug.
fresh SNMP fresh module debug.
icp_client SNMP ICP client module debug.
icp_server SNMP ICP server module debug.
ims SNMP IMS module debug.
log SNMP log module debug.
main SNMP main module debug.
parse SNMP parse module debug.
perf SNM P performance module debug.
print SNMP print module debug.
proxy SNMP proxy module debug.
req SNMP required module debug.
save SNMP save module debug.
tcp SNMP TCP module debug.
time SNMP time module debug.
trap SNMP trap module debug.
url SNMP URL module debug.
usage SNMP usage module debug.
statssubcommands:
all Stats all debug.
collection Stats collection debug.
computation Stats computation debug.
history Stats history debug.
translogsubcommands:
all All transaction log debugging.
daemon Transaction log daemon debugging.
file-manager Transaction log file manager debugging.
logging Transaction log entry generation.
wccpsubcommands:
all WCCP turn on all debugging.
events WCCP events.
packets WCCP packet-related information.
wisubcommands:
admin Web Interface admin module debug.
all Web Interface all modules debug.
basic Web Interface basic module debug.
bypass Web Interface bypass module debug.
clustering Web Interface clustering module debug.
dns Web Interface DNS module debug.
events Web Interface events module debug.
filesystem Web Interface file system module debug.
fresh Web Interface fresh module debug.
hardware Web Interface hardware module debug.
icp_client Web Interface ICP client module debug.
icp_server Web Interface ICP server module debug.
monitor Web Interface monitor module debug.
persistent Web Interface persistent module debug.
proxy Web Interface proxy module debug.
radius Web Interface radius module debug.
revproxy Web Interface RevProxy module debug.
routing Web Interface routing module debug.
snmp Web Interface SNMP module debug.
syslog Web Interface syslog module debug.
tcp Web Interface TCP module debug.
time Web Interface time module debug.
translog Web Interface translog module debug.
urlfilter Web Interface URL filter module debug.
wccpenable Web Interface WCCP enable module debug.
wccpmain Web Interface WCCP module debug.
webcache Web Interface web cache module debug.
Use the debug command to monitor specific processes and packet transfers for each of the above functions. To turn off debugging, use the no debug command or undebug command.
The output of this command appears on the console, not in the Telnet window, and the amount of the output might be prodigious.
Console# debug http cache trace
Console# no debug http cache trace
no debug
show debug
undebug
To remove a file, use the del EXEC command.
del filename
filename Name of the file to delete.
Use this command to remove a file from any directory. Note that some files are necessary for proper functionality and should not be removed.
Console# del /local/tempfile
cpfile
deltree
mkdir
mkfile
rmdir
To remove a directory recursively and all file that it contains, use the deltree EXEC command.
deltree directorydirectory Name of the directory tree to delete.
Use this command to remove a directory and all files within the directory from the cache (dosfs file system). Do not remove necessary files or directories, such as log files or directories, for proper functionality. It may not be possible to move a log file to a new directory without losing functionality.
Console# deltree /local
del
To view a long list of files in a directory, use the dir EXEC command.
dir [directory]directory (Optional) Name of the directory to list.
Use this command to view a detailed list of files contained within the working directory including names, sizes, and time created. The equivalent command is lls.
Console# dir /local
size date time name LongName
---------- ------- ------ ----------- ----------------
512 Dec-31-1987 17:02:32 ETC <DIR> etc
512 Dec-31-1987 17:02:32 TFTPBOOT <DIR> tftpboot
512 Dec-31-1987 17:02:32 VAR <DIR> var
512 Jan-07-1988 09:47:52 LIB <DIR> lib
4385154 Apr-22-1999 12:25:36 CE25.PAX ce25.pax
3395136 Dec-31-1987 17:11:36 CE500-~1.CUS ce500-194b16.bin.dbg.cus1
3412352 Apr-22-1999 12:26:54 CE500-~2.CUS
ce500-194b18.bin.dbg.cus1
4 DIR(S), 3 FILE(S) 11192642 bytes
2125889536 bytes AVAILABLE ON VOLUME /c0t0d0s1
lls
ls
To turn off privileged EXEC commands, use the disable command.
disableThis command has no arguments or keywords.
The disable command places you in EXEC mode. To turn privileged EXEC mode back on, use the enable command.
Console# disable
enable
To configure the Cache Engine's disks, use the disk EXEC command.
disk {partition devname | prepare devname}{dosfs | cfs}partition Partitions the hard disk.
devname Device name.
prepare Partitions and formats volumes on a hard disk.
cfs Cache file system.
dosfs DOS file system.
Disk partition allocates portions of a disk for the specified file systems. The partition sizes are not user configurable. Use the show disks command to obtain the names of installed disks.
| Caution Partitioning a disk destroys all of its contents. After partitioning, each file system must be formatted and mounted before it can be used. |
Using the disk prepare command is a shortcut in preparing a disk. It partitions the disk and then formats and mounts all the partitions.
Console# disk partition boot
show disk-partitions
show disks
To clear the DNS cache, use the dns-cache EXEC command.
dns-cache {clear}clear Clears the DNS cache.
Use the dns-cache clear EXEC command to clear all stored DNS entries. This does not erase any cached HTPP related objects.
To configure the DNS cache, use the dns-cache enable or dns-cache size global configuration command. You must also configure a DNS server as well as your domain name. See the ip name-server and ip domain-name commands for more information.
Console# dns-cache clear
dns-cache enable (global configuration command)
dns-cache size (global configuration command)
domain-name
ip name-server
To configure the DOS file system, use the dosfs EXEC command.
dosfs [check volname | format volname | label devicename | mount volname mountmode | repair repairmode volname | sync syncdevice | unmount volname]check (Optional) Checks dos file system.
devicename (Optional) Device name.
format (Optional) Erases and formats a file system on a disk device.
label (Optional) Sets a device volume label.
mount (Optional) Mounts a disk or volume file system.
volname (Optional) Volume name.
mountmode:
rdonly (Optional) Read only.
rdwr (Optional) Read write.
repair (Optional) Checks and repairs an uvfat/dos file system.
repairmode:
automatic (Optional) Automatic (not interactive) repair.
interactive (Optional) User-interactive repair.
sync (Optional) Synchronizes a disk device.
syncdevice (Optional) Absolute device name.
unmount (Optional) Unmounts a disk or volume file system.
volname (Optional) Volume name.
Use this command to format and mount the DOS file systems after partitioning disks. Use this command to repair DOS file systems that are causing errors.
The default configuration has only one DOS file system. This file system is created on the first disk in the system and has a special name "/local." This file system contains various files necessary for correct functioning of the Cache Engine.
Console# dosfs format /local
show dosfs volumes
cd
copy
cpfile
del
deltree
dir
ls
mkdir
mkfile
To turn on privileged commands, use the enable EXEC command.
enableThis command has no arguments or keywords.
To return to privileged EXEC mode from user EXEC mode, use the enable command.
The disable command takes you from privileged EXEC mode back to user EXEC mode.
Console> enable
Console#
disable
To exit any configuration mode or close an active terminal session and terminate an EXEC mode session, use the exit EXEC command.
exitThis command has no arguments or keywords.
EXEC and global configuration
Use the exit command in global configuration mode to return to EXEC mode. You can also press Ctrl-Z or use the end command from any configuration mode to return to EXEC mode.
Use the exit command in EXEC command mode to close an active terminal session and terminate the EXEC mode session.
Console# exit
end
To get online help for the command-line interface, use the help EXEC or global configuration command.
helpThis command has no arguments or keywords.
You can get 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:
Console# help
To install a new version of Cache Engine software, use the install EXEC command.
install paxfilenamepaxfilename Name of the pax file you want to install.
Install and run the paxfilename in the /local directory only. By default, a pax file is stored in the local directory using a file transfer protocol. All files contained in the pax file overwrite all files in the Cache Engine when the install command is used. The new version will not take effect until the Cache Engine has been reloaded.
Console# install ce25.pax
reload
To view a long list of directory names, use the lls EXEC command.
lls [directory]directory (Optional) Name of the directory for which you want a long list of files.
This command provides detailed information about files and subdirectories stored in the present working directory to be viewed (including size, date, time of creation, DOS name, and long name of the file). This information can also be viewed with the dir command.
Console# lls
Console# lls /local
size date time name LongName
---------- ------- ------ ----------- ----------------
512 Dec-31-1987 17:02:32 ETC <DIR> etc
512 Dec-31-1987 17:02:32 TFTPBOOT <DIR> tftpboot
512 Dec-31-1987 17:02:32 VAR <DIR> var
512 Jan-07-1988 09:47:52 LIB <DIR> lib
4385154 Apr-22-1999 12:25:36 CE25.PAX ce25.pax
4 DIR(S), 3 FILE(S) 11192642 bytes
2125922304 bytes AVAILABLE ON VOLUME /c0t0d0s1
dir
ls
To view a list of files or subdirectory names within a directory, use the ls EXEC command.
ls [directory]directory (Optional) Name of the directory for which you want a list of files.
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.
Console# ls /local
etc
tftpboot
var
lib
ce25.pax
2125922304 bytes AVAILABLE ON VOLUME /c0t0d0s1
dir
lls
pwd
To create a directory, use the mkdir EXEC command.
mkdir directorydirectory Name of the directory you want to create.
Use this command to create a new directory or subdirectory in the Cache Engine file system.
Console# mkdir /oldpaxfiles
dir
lls
ls
pwd
rmdir
To create a new file, use the mkfile EXEC command.
mkfile filenamefilename Name of the file you want to create.
Use this command to create a new file in any directory of the Cache Engine.
Console# mkfile traceinfo
lls
ls
mkdir
To disable the debugging functions, use the no debug EXEC command.
no debug {all | cron | ftp-server | http httpsubcommands debugsubcommands | icp icpsubcommands debugsubcommands | inetd | logging loggingsubcommands | ntp debuglevel | radius radiussubcommands debugsubcommands | rcpd | snmp snmpsubcommands debugsubcommands | stats statssubcommands | tftp-server | translog translogsubcommands | wccp wccpsubcommands | wi wisubcommands debugsubcommands}See the syntax description for the debug command.
Use this command to turn off debugging functions that are enabled on the Cache Engine. Use the no debug all command to turn of all debugging, or to turn off a specific debugging function, use the no debug command with the exact string used to enable the debugging.
Console# no debug http all error
debug
no debug
show debug
undebug
To set the software clock (time and date) using an NTP server, use the ntpdate EXEC command.
ntpdate {hostname | ip-address}hostname NTP host name.
ip-address NTP server IP address.
Use the NTP protocol to find the current time of day and set the Cache Engine current time 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.
Console# ntpdate 10.11.23.40
clock clear
clock save
clock set
show clock
To send echo packets for diagnosing basic network connectivity on networks, use the ping (packet internet groper) EXEC command.
ping {hostname | ip-address}hostname Host name of system to ping.
ip-address IP address of system to ping.
To use this command with the hostname argument, be sure DNS functionality is configured on your Cache Engine. To force the timeout of a nonresponsive host, or to eliminate a loop cycle, enter Ctrl-C.
Console# ping mycacheengine
To show the current directory, use the pwd EXEC command.
pwdThis command has no arguments or keywords.
Use this command to display the present working directory of the Cache Engine.
Console# pwd
cd
dir
lls
ls
To halt and perform a cold restart on your Cache Engine, use the reload EXEC command.
reloadThis command has no arguments or keywords.
| Caution You will lose all cached objects after issuing this command, and the cached objects cannot be recovered once lost. |
To reboot the Cache Engine, use the reload command. If no configurations are saved to Flash memory, you will be prompted to enter configuration parameters upon restart. Any open connections will be dropped after issuing this command, and the file system will be reformatted upon restart. To save any file system contents to disk from memory before a restart, use the cache sync command.
Console# reload
cache sync
write
write erase
To rename a file on your Cache Engine, use the rename EXEC command.
rename source destinationsource Source file or path name of the file you want to rename.
destination Destination file or path name of the new file.
Use this command to rename any file within the Cache Engine. Certain files cannot be renamed without interfering with functionality of the feature associated with the file.
Console# rename ce25.pax ce6399.pax
cpfile
To delete a directory, use the rmdir EXEC command.
rmdir directorydirectory Name of the directory you want to delete.
Use this command to remove any directory from the Cache Engine file system. This is not a recursive command; therefore, you are queried whether to delete any files in the directory.
Console# rmdir /local/oldpaxfiles
lls
ls
mkdir
To display the current terminal commands, use the terminal EXEC command.
terminal monitormonitor Monitors debug commands.
This command makes a Telnet session the terminal. This causes all software output to go to this session. Since there is only one active terminal in the system, this session redirects all software output from all other Telnet sessions to this session.
Console# terminal monitor
Console is always monitored
To display a file, use the type EXEC command.
type filenamefilename Name of file.
Use this command to display the contents of a file within any Cache Engine file directory. This command may be used to monitor features such as transaction logging, system logging (syslog), or to manage files such as badurl.lst for URL filtering.
Console# type badurl.lst
cpfile
dir
lls
ls
mkfile
To disable debugging functions, use the undebug EXEC command. Also see the debug EXEC command.
undebug {all | cron | ftp-server | http httpsubcommands debugsubcommands | icp icpsubcommands debugsubcommands | inetd | logging loggingsubcommands | ntp debuglevel | radius radiussubcommands debugsubcommands | rcpd | snmp snmpsubcommands debugsubcommands | stats statssubcommands | tftp-server | translog translogsubcommands | wccp wccpsubcommands | wi wisubcommands debugsubcommands}See the syntax description for the debug command.
Use this command to turn off debugging functions that are enabled on the Cache Engine. Use the undebug all command to turn off all debugging, or to turn off a specific debugging function, use the undebug command with the exact string used to enable the debugging.
The equivalent command is no debug.
Console# undebug icp all
debug
no debug
show debug
To display the current user's name, use the whoami EXEC command.
whoamiThis command has no arguments or keywords.
Use this command to display the current user's username and user identification number.
Console# whoami
admin
pwd
To write running configurations to memory or to a terminal session, use the write EXEC command.
write [erase | memory | terminal]erase (Optional) Erases startup configuration from NVRAM.
memory (Optional) Writes the configuration to NVRAM. This is the default.
terminal (Optional) Writes the configuration to a terminal session.
memory
Use this command to either save running configurations to NVRAM or to erase memory configurations. Following a write erase command, no configurations is held in memory and a prompt for configuration specifics occurs after rebooting the Cache Engine.
Use the write terminal command to display the current running configuration in the terminal session window. The equivalent command is show running-config.
Console# write
copy running-config startup-config
show running-config
The global configuration Cache Engine commands are entered in the global configuration mode. The section describes the following global configuration commands.
To configure the bypass feature, use the bypass global configuration command. To disable this function, use the no form of this command.
bypass {auth-traffic enable | list timer minutes | load {enable | in-interval seconds | out-interval seconds | time-interval minutes}auth-traffic Authenticated traffic bypass configuration.
enable Enable bypassing authenticated traffic.
list Bypass list configuration.
timer Bypass entry removal timer in minutes
load Bypass load configuration.
enable Enable Bypass Load.
in-interval Time interval between buckets coming back.
out-interval Time interval between bypassing buckets
time-interval Time that a bucket is bypassed
minutes Bypass list entry timer or time interval in minutes (1 to 1440)
seconds Time interval in seconds (4 to 600).
in-interval 60 seconds.
out-interval 4 seconds.
time-interval 10 minutes.
The bypass feature is only available when WCCP Version 2 is enabled. The Cache Engine can only bypass WCCP-redirected traffic, not proxy-style requests.
Load Bypass. If a Cache Engine becomes overwhelmed with traffic, use the bypass load enable command option to enable the load bypass feature to re-route overload traffic back to the Internet.
in-interval (Time interval between buckets coming back). Once the time interval allotted to bypass mode has been surpassed, the Cache Engine will begin to pick up bypassed traffic one bucket at a time. The time between the return, or pick-up, of each bucket is measured in seconds.
out-interval (Time interval between bypassing buckets). Once the Cache Engine becomes overwhelmed with traffic, it will bypass one bucket at a time until it is no longer over-loaded. The amount of time between the bypassing of one bucket and the next is the time interval between bypassing buckets.
time-interval (Time that a bucket is bypassed). Once a bucket (or numerous buckets) has been bypassed, and the Cache Engine is in bypass mode, it will not attempt to pick up the bypassed load for this set number of minutes.
Authentication Traffic. Some websites, due to IP authentication, may not allow the Cache Engine to connect directly on behalf of the client. In order to avoid a disruption of service, use the bypass auth-traffic enable command option so that the Cache Engine can generate a dynamic access-list for these client-server pairs. Authentication bypass can also propagate upstream and downstream in the case of hierachical caching.
The following example enables and disables the authentication traffic option:
Console(config)# bypass auth-traffic enable
Console(config)# no bypass auth-traffic enable
To set the time zone for display purposes, use the clock timezone global configuration command. To disable this function, use the no form of this command.
clock timezone {zone hours} [minutes]zone Name of the time zone to be displayed when standard time is in effect.
hours Offset from GMT.
minutes (Optional) Minutes offset from GMT/UTC.
Use this command in conjunction with the clock set command when a NTP server is not being used to find the current time of day.
Use this command to set the time zone parameters for the location of the Cache Engine. This information is used to set the GMT offset against the time entered with the clock set command.
The following example sets the timezone to Pacific Standard Time and offsets 8 hours behind UTC:
Console(config)# clock timezone PST -8
Console(config)# no clock timezone
clock
show clock
To set a CRON task, use the cron global configuration command. To disable a CRON task, use the no form of this command.
cron {del-tab entryid | file tabfile | save-tab | tab-entry tabentry}del-tab Deletes tab.
file CRON tab file.
save-tab CRON save tab.
tab-entry CRON tab entry.
entryid Entry ID (1 to 1,000).
tabfile CRON tab filename.
tabentry CRON tab entry line.
The cron command is used to set up CRON tasks.
To view your existing CRON configurations, use the show cron command. For example:
Console# show cron
==CRON Configuration==
CRON tab file: /local/etc/crontab
Legend 1: min hr day-of-mon mon day-of-wk tclsh script-name
Legend 2: min hr day-of-mon mon day-of-wk tcl tcl-cmd
Sample: 0 5 * * * tclsh /local/test.tcl
Console(config)# cron sav-tab
Console(config)# no cron sav-tab
show cron
To configure the DNS cache, use the dns-cache global configuration command. To disable the DNS cache, use the no form of this command.
dns-cache {enable | size maxsize}enable Enables the DNS cache.
size Sets the DNS cache size.
maxsize Maximum number of cache records (256 to 2,048).
To enable caching of DNS entries, use the dns-cache enable command as well as the dns-cache size command. Cache size refers to the maximum number of DNS entries that will be cached at one time.
Console(config)# dns-cache enable
Console(config)# dns-cache size 512
Console(config)# no dns-cache enable
Console(config)# no dns-cache size
dns-cache clear
To exit global configuration mode, use the end global configuration command.
endThis command has no arguments or keywords.
Use the end command to exit global configuration mode after completing any changes to the running configuration. This will not save any new configurations to NVRAM. You must use the write command to save the configuration.
You may press Ctrl-Z to exit global configuration mode.
Console(config)# end
Console#
exit
Ctrl-Z
To customize how the Cache Engine should handle errors, use the error-handling global configuration command.
error-handling {reset-connection | send-cache-error | transparent}reset-connection Reset TCP connection without specifying any error.
send-cache-error Send Cache error.
transparent Make the Cache Engine look transparent to the client.
Error handling refers to when a Cache Engine cannot gain access to a site requested by a client. In Version 2.0.1, the Cache Engine returned a generic "cache server cannot reach destination" HTML page. To use the tranparent option, you must be using WCCP Version 2. If you choose the transparent option, the Cache Engine will send a re-issue request remark to the client, and generate a bypass entry for the site requested. The client re-issues the request without knowledge of the Cache Engine, and the Cache Engine will not service future requests. Thus the error messages will be transparent.
Console(config)# error-handling transparent
Console#
To configure the length of time that an inactive terminal session window will remain open, use the exec-timeout global configuration command. To disable the exec timeout, use the no form of this command.
exec-timeout timeouttimeout Timeout in minutes (0 to 44,640).
Use this command to establish the length of time, in minutes, that an inactive terminal session window will remain open. After 150 minutes, it will disconnect itself.
Console(config)# exec-timeout 100
Console(config)# no exec-timeout
To exit any configuration mode or close an active terminal session and terminate EXEC mode session, use the exit EXEC command.
exitThis command has no arguments or keywords.
EXEC and global configuration
Use the exit command in global configuration mode to return to EXEC mode.
Use the exit command in EXEC command mode to close an active terminal session and terminate the EXEC mode session.
You can press Ctrl-Z or use the end command from any configuration mode to return to EXEC mode.
Console# exit
end
Ctrl-Z
To configure user group parameters, use the group global configuration command.
group {add groupname | delete group-id | delete groupname | modify group-id | modify groupname}add Adds a group name.
delete Deletes a group name or ID.
modify Modifies a group name or group ID.
groupname Group name.
group-id Group ID.
Use this command to create a new group of users or to modify an existing group. User groups are used to allow unique accessibility to the cache file system, or to the Cache Engine itself on a group-by-group basis.
Console(config)# group add pubs
user
To get online help for the command-line interface, use the help EXEC or global configuration command.
helpThis command has no arguments or keywords.
You can get 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:
Console(config)# help
To configure the Cache Engine's network name, use the hostname global configuration command. To reset the host name to the default setting, use the no form of this command.
hostname namename New host name for the Cache Engine; the name is case sensitive.The name may be from 1 to 22 alphanumeric characters.
The default host name is CE550.
Use this command to configure the host name for the Cache Engine. The host name is used in prompts and default configuration filenames.
The following example changes the host name to sandbox:
Console(config)# hostname sandbox
sandbox(config)#
Console(config)# no hostname
CE550(config)#
To configure HTTP related parameters, use the http global configuration command. To disable HTTP related parameters, use the no form of this command.
http {age-multiplier text texttime binary bintime | cache-authenticated | cache-cookies | cache-miss {retrieve | revalidate} | cluster maxdelay delaysecs | max-ttl days hours minutes seconds | persistent-connections {enable | timeout secs | proxy {incoming port | outgoing {hostname | ip-address} port [no-local-domain] | reval-each-request {all | none | text} | serve-ims text texttime binary bintime}age-mulitplier HTTP/1.0 caching heuristic modifier for text objects.
text Heuristic modifier for text object.
texttime Expiration time of text objects as a percentage of their age (0 to 100).
binary Heuristic modifier for binary object.
bintime Expiration time of binary objects as a percentage of their age (0 to 100).
cache-authenticated Cache and revalidate authenticated web objects.
cache-cookies Cache web objects with associated cookies.
cache-miss Configuration for the handling of `no-cache' requests.
retrieve Retrieve the object from the origin.
revalidate Revalidate the object with the origin before serving.
cluster max-delay Maximum delay to wait for a response.
delaysecs Maximum delay in seconds (0 to 10).
max-ttl Maximum time to live for objects in the cache.
days Maximum time to live for units in days.
hours Maximum time to live for units in hours.
minutes Maximum time to live for units in minutes.
seconds Maximum time to live for units in seconds.
persistent-connections Persistent connections configuration options.
enable Enable persistent connections.
timeout secs Persistent connection timeout in seconds (1 to 86,400).
proxy Configuration parameters for proxy-mode.
incoming Configuration for incoming proxy-mode requests.
port Port to listen for requests (1 to 32,768).
outgoing Configuration to direct outgoing request to another proxy-server.
hostname Host name of outgoing proxy.
ip-address IP address of outgoing proxy.
port Port to listen for requests (1 to 32,768).
no-local-domain Do not use Outgoing HTTP Proxy for Local Domain.
reval-each-request Configuration of revalidation for every request.
all Revalidates all objects on every request.
none Do not revalidate for each request.
text Revalidate text objects on every request.
serve-ims Configuration for the handling of If-Modified-Since (IMS) requests for text objects.
text Modify handling of If-Modified-Since requests for text objects.
texttime Percentage of age to serve the object without revalidation (0 to 100).
binary Modify handling of If-Modified-Since requests for binary objects.
bintime Percentage of age to serve the object without revalidation (0 to 100).
age-mulitplier Default is 30 percent for text and 60 percent for binary objects.
max-ttl Default is 3 for text and 7 days for binary objects.
serve-ims Default is 50 percent of maximum age for text and 80 percent of maximum age for binary objects.
cache-cookies Default is No.
cache-authenticated Default is No.
cache reval-each-request Default is None.
cache-miss Default is to retrieve.
cluster Maximum delay is 2 seconds.
incoming proxy Default is disabled.
outgoing proxy Default is disabled.
persistent conn Default is enabled.
Connection timeout 15 seconds.
Maximum idle time 1000 seconds.
Use these commands to configure specific parameters for caching HTTP objects.
The age-multiplier command enables the Cache Engine to determine the age of an object by multiplying the length of time since the object's last-modified-date by the configured percentage. This establishes an approximate date of expiration from the cache.
The max-ttl command sets the upper limit on estimated expiration dates. If an object has an explicit expiration date, this takes precedence over the configurable TTL (time to live).
The serve-ims command responds to an If-Modified-Since request issued from a client browser by serving the object directly from the cache without revalidating with the origin server if the object is less then the configured percentage of its maximum age.
The cache-cookies command enables the Cache Engine to cache binary served with HTTP set-cookies headers and no explicit expiration information.
The cache-authenticated command enables the Cache Engine to cache authenticated content. If enables, the Cache Engine will not serve authenticated objects without first revalidating the authentication header attached to the cached object.
The cache reval-each-request command enables the Cache Engine to revalidate all objects requested from the cache (text only if only text (HTML pages) should be revalidated each time or none to disable this function).
The cache-miss revalidate command revalidates a cache-miss request forced by the client (shift-reload). The cache-miss retrieve command forces a new object retrieval.
The cluster command modifies the healing mode parameters. A cluster refers to a group of two or more caches within a single WCCP Version 2 environment. Healing mode describes the addition of a cache engine to an existing network, and the resulting "healing" time it takes to fill the cache with content. To disable healing mode, you must set the number of misses to 0.
The proxy mode command enables the Cache Engine to operate in environments where the WCCP is not enabled, or where client browsers have previously been configured to use a legacy proxy server. You must configure the proxy incoming port to accept proxy style requests using the proxy incoming port command. To enable an outgoing (upstream) proxy server, use the proxy outgoing hostname port command (where hostname is the system name or IP address of the outgoing proxy server, and port is the port number designated by the outgoing (upstream) server to accept proxy requests. Select the no-local-domain option if you do not want to use the outgoing HTTP proxy for local domain.
The persistent-connections enable command enables persistent-connections on the Cache Engine. To configure the number of seconds the Cache Engine should wait for a connection response before it times out, use the connection time-out command. To set the number of seconds, the Cache Engine should allow an idle persistent connection to remain open, use the max-idle command.
Console(config)# http age-multiplier text 30 bin 60
Console(config)# http reval-each-request text
Console(config)# no http age-multiplier text 30 bin 60
Console(config)# no http reval-each-request text
show http
To configure the Internet Configuration Protocol (ICP) client and server, use the icp global configuration command. To disable the ICP client and server, use the no form of this command.
icp {client {add-remote-server {hostname | ip-address} {parent | sibling} icp-port icpport | enable | exclude line | max-fail retries | max-wait timeout | modify-remote-server {hostname | ip-address} {http-port port | icp-port port | parent | restrict line | sibling} | server {enable | port port | remote-client {hostname | ip-address} {fetch | no-fetch}}client ICP client functionality:
add-remote-server Adds an ICP client remote server.
hostname Host name or IP address.
ip-address IP address.
parent ICP server acts like a parent.
sibling ICP server acts like a sibling.
icp-port ICP port.
icpport ICP port number to send remote requests (0 to 65,535).
http-port HTTP port.
httpport HTTP port to send requests (0 to 65,535).
enable Enables the ICP client.
exclude ICP client local domain.
line space delimited local domain list.
max-fail Number of retries.
retries Number of retries (0 to 100).
max-wait Timeout period of ICP responses in seconds.
timeout Timeout period for ICP responses in seconds (0 to 30).
modify-remote-server Modify the ICP client remote server parameters.
hostname Host name or IP address.
http-port HTTP port.
port HTTP port number to send requests (0 to 65,535).
icp-port ICP port.
port ICP port number to send requests (0 to 65,535).
parent ICP remote server acts like a parent.
restrict Restricted list of domains.
line Space delimited local domain list.
sibling ICP remote server acts like a sibling.
server ICP server functionality:
enable Enables the ICP client.
port ICP server port to listen for ICP requests.
port ICP port number to send requests (0 to 65,535).
remote-client ICP server remote client.
hostname Host name or IP address.
fetch ICP remote client fetch.
no-fetch ICP remote client do not fetch miss.
Use these commands to establish and configure the ICP server and client functionality of the Cache Engine. Configurations made without enabling ICP functionality will be stored within the configuration until removed. To enable the ICP server or client functionality, use the icp {server | client} enable} command. Be sure to enable the ICP on any other Cache Engines or ICP servers/clients within the ICP environment to ensure proper service. You may monitor the statistical data of ICP service using the show statistics icp EXEC command.
Console(config)# icp client enable
Icp Client started
Console(config)# no icp client enable
Icp Client disabled
show icp client
show icp server
show statistics icp
To configure, enable, and disable TCP/IP services, use the inetd global configuration command. To disable TCP/IP services, use the no form of this command.
inetd {enable service tasks}enable Enables TCP/IP service.
service Name of the service to be enabled: echo, discard, chargen, ftp, rcp, telnet, and tftp.
tasks Maximum number of concurrent tasks.
echo Disabled.
discard Disabled.
chargen Disabled.
ftp Five sessions.
rcp Five sessions.
telnet Three sessions.
tftp Five sessions.
Use these commands to configure the parameters of TCP/IP services on the Cache Engine. The limit for any service is a maximum of 20 tasks. Use the show inetd command to list current inetd configurations and the number of current tasks running.
Console(config)# inetd enable ftp 5
Console(config)# no netd enable ftp
show inetd
To configure an Ethernet or SCSI interface, use the interface global configuration command. To disable an Ethernet or SCSI interface, use the no form of this command.
interface ethernet numberethernet The Ethernet IEEE 802.3 interface to configure.
number The Ethernet interface number (0 or 1).
Use the interface command to begin interface configuration, such as setting an IP address for an interface, a subnet mask for an interface, broadcast address, or manual set speed/duplex for an interface.
Console(config)# interface ethernet 0
Console(config-if)# ?
Configure Interface commands:
autosense Interface autosense
bandwidth Interface speed
exit Exit from interface mode
fullduplex Interface fullduplex
halfduplex Interface halfduplex
ip Interface Internet Protocol Config commands
no Negate a command or set its defaults
Console(config-if)# exit
Console(config)#
Console(config)# no interface ethernet 0
show interface
To define a default gateway, use the ip default-gateway global configuration command. To delete the IP default gateway, use the no form of this command.
ip default-gateway ip-addressip-address IP address of the default gateway.
Disabled
The default gateway is used to route IP packets when there is no specific route found to the destination.
Console(config)# ip default-gateway 192.31.7.18
Console(config)# no ip default-gateway
To define a default domain name, use the ip domain-name global configuration command. To remove the IP default domain name, use the no form of this command.
ip domain-name namename Domain name.
Enabled
This configuration allows the Cache Engine to resolve any unqualified host names. Any IP host name that does not contain a domain name will have the configured domain name appended to it. This appended name is resolved by the DNS server and then added to the host table. There must also be a DNS server enabled on the Cache Engine for host name resolution to work correctly. To do this, use the ip name-server hostname command.
Console(config)# ip domain-name cisco.com
Console(config)# no ip domain-name
ip domain-name
ip name-server
To specify the address of one or more name servers to use for name and address resolution, use the ip name-server global configuration command. To disable IP name servers, use the no form of this command.
ip name-server ip-addressip-address Domain server IP address (maximum of 8).
For proper resolution of host name to IP address or IP address to host name, the Cache Engine uses DNS servers. Use the ip name-server command to point the Cache Engine to a specific DNS server. You may configure up to eight servers.
Console(config)# ip name-server 10.11.12.13
Console(config)# no ip name-server 10.11.12.13
no ip name-server
ip domain-name
To configure static IP routing, use the ip route global configuration command. To disable an IP routing, use the no form of this command.
ip route destination netmask gatewaydestination Destination network IP address.
netmask Destination network subnet mask address.
gateway Destination network gateway IP address.
Disabled
Use the ip route command to an add net/host specific static route. Any IP packet designated to the net/host will then use the route specified.
Console(config)# ip route 171.69.227.128 ffffff80 171.69.227.250
Console(config)# no ip route 171.69.227.128 ffffff80 171.69.227.250
show ip route
To configure logging, use the logging global configuration command. To disable logging functions, use the no form of this command.
logging {hostname | ip-address | console conditions | disk filename conditions | event-export events conditions export | facility export | on | recycle size | trap conditions}hostname Syslog server host name.
ip-address IP address.
console Sets console logging level.
conditions Use one of these keywords:
alerts — Immediate action needed.
critical — Immediate action needed.
debugging — Debugging messages.
emergencies —System is unusable.
errors — Error conditions.
informational — Informational messages.
notification — Normal but significant conditions.
warnings — Warning conditions.
disk Stores log in a file.
filename filename to store log.
event-export Syslog event export configuration.
events Use one of these keywords:
critical-events — Exports critical events.
notice-events — Exports notice events.
url-tracking — Tracks URLs to syslog.
warning-events — Exports warning events.
export Use one of these keywords:
cron/at — CRON.
daemon — System Daemons.
kernel — Kernel.
line-printer — Line printer system.
local0 — Local Use.
local1 — Local Use.
local2 — Local Use.
local3 — Local Use.
local4 — Local Use.
local5 — Local Use.
local6 — Local Use.
local7 — Local Use.
mail — USENET News.
news — Mail System.
security — Authorization system.
syslog — Syslog itself.
user — User process.
uucp — UUCP System.
facility Facility parameter for syslog messages.
on Enables logging to all destinations.
recycle Sets log file recycling.
size Size in bytes (1 to 50000000).
trap Sets syslog server logging level.
These are the defaults when no other options are configured by the user:
Use this command to set specific parameters for Syslog. Syslog is always enabled internally, and the files are found in /local/var/log/syslog.txt. To configure the Cache Engine to send varying levels of event messages to an external syslog host, use the syslog hostname command. Syslog can be configured to send various levels of messages to the console using the logging console conditions command. It can also be configured to export event messages using the logging event-export events command.
Console(config)# logging console warnings
Console(config)# no logging console warnings
To undo a global configuration command or set its defaults, use the no form of a command to undo the original command
no commandcommand Use the following keyword and its associated syntax:
clock timezone — Configures time zone.
cron — CRON commands.
dns-cache — DNS cache commands.
end — Exits from configure mode.
exec-timeout — Exec timeout.
exit — Exits global configuration mode.
hostname — Sets system's network name.
http — HTTP related configuration parameters.
icp — Internet cache protocol commands.
inetd — INETD configuration command.
interface — Selects an interface to configure.
ip — Internet protocol configuration commands.
logging — System logging (syslog) commands.
ntp — NTP configuration commands.
radius — Configuration commands for RADIUS authentication.
snmp-server — Modifies SNMP parameters.
tcp — TCP user configure.
terminal — Current terminal commands.
tftp-server — TFTP-server commands.
transaction-log — Configuration commands for transaction logging.
trusted-host — Trusted host commands.
url-filter — Enables URL blocking.
wccp — Web Cache Communication Protocol (WCCP).
Use the no command to disable functions or negate a command. If you need to negate a specific command, such as the default gateway IP address, you must include the specific string in your command, such as no ip default-gateway ip-address. To disable a function currently enabled on the Cache Engine, simply use the no function command.
Console(config)# wccp version 2
Console(config)# no wccp version 2
To configure the Network Time Protocol (NTP) and to allow the system clock to be synchronized by a time server, use the ntp server global configuration command. To disable this function, use the no form of this command.
ntp server {hostname | ip-address}hostname Host name of the time server providing the clock synchronization (maximum of 4).
ip-address NTP server IP address of the time server providing the clock synchronization (maximum of 4).
The default NTP version number is 3.
Use this command to synchronize the Cache Engine clock with the specified server. The server will not synchronize to this machine.
Console(config)# ntp server 172.16.22.44
Console(config)# no ntp server 172.16.22.44
clock
show clock
show ntp
To configure RADIUS authentication parameters, use the radius global configuration command.To disable RADIUS authentication parameters, use the no form of this command.
radius {auth-timeout value | server {hostname | ip-address} port password {enable | disable}}auth-timeout Configures RADIUS authentication timeout.
value Timeout value in minutes (1 to 60).
server Adds a RADIUS server.
hostname Host name of RADIUS server.
ip-address IP address of RADIUS server.
port Port of RADIUS server (1 to 32,7680).
password Shared secret password for the RADIUS server authentication.
enable Enables the RADIUS server.
disable Disables the RADIUS server.
The radius command is used to configure the RADIUS authentication parameters.
Console(config)# radius server 171.71.90.121 70 password enable
Console(config)# no radius server 171.71.90.121 70 password enable
To set up the community access string to permit access to the SNMP protocol, use the snmp-server community global configuration command. Use the no form of this command to remove the previously configured community string.
snmp-server community stringstring Community string that acts like a password and permits access to the SNMP protocol.
By default, an SNMP community string permits read-only access to all objects.
The first snmp-server command that you enter enables both versions of SNMP. Cisco does not support sets. The no snmp-server command disables both versions of SNMP (SNMPv1 and SNMPv2C).
The following example assigns the string comaccess to SNMP:
Console(config)# snmp-server community comaccess
The following example removes the previously defined community string.
Console(config)# no snmp-server community
The following example disables both versions of SNMP without removing a previously defined community string:
Console(config)# no snmp-server
To set the system contact (sysContact) string, use the snmp-server contact global configuration command. Use the no form of this command to remove the system contact information.
snmp-server contact lineline String that describes the system contact information.
No system contact string is set.
The system contact string is the value stored in the MIB-II system group sysContact object.
The following is an example of a system contact string:
Console# snmp-server contact Dial System Operator at beeper # 27345
Console# no snmp-server contact
snmp-server location
show snmp
To enable the Cisco Cache Engine to send SNMP traps, use the snmp-server enable traps global configuration command. Use the no form of this command to disable SNMP notifications.
snmp-server enable trapsThis command has no arguments or keywords.
This command is disabled by default. No traps are enabled.
If you do not enter an snmp-server enable traps command, no traps are sent. In order to configure this, you must enter the snmp-server enable traps command.
The snmp-server enable traps command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP traps. To send traps, you must configure at least one snmp-server host command.
For a host to receive a trap, both the snmp-server enable traps command and the snmp-server host command for that host must be enabled.
In addition, SNMP must be enabled with the snmp-server community command.
The following example enables the router to send all traps to the host 172.30.2.160 using the community string public:
Console(config)# snmp-server enable traps
Console(config)# snmp-server host 172.30.2.160 public
Console(config)# no snmp-server enable traps
snmp-server host
snmp-server community
To specify the recipient of an SNMP trap operation, use the snmp-server host global configuration command. Use the no form of this command to remove the specified host.
snmp-server host {hostname | ip-address} stringhostname Host name of SNMP TRAP host.
ip-address IP address of SNMP TRAP host.
string Password-like community string sent with the trap operation.
This command is disabled by default. No traps are sent.
The version of the SNMP protocol used to send the traps is SNMPv1.
If you do not enter an snmp-server host command, no traps are sent. To configure the Cisco Cache Engine product to send SNMP traps, you must enter at least one snmp-server host command. To enable multiple hosts, you must issue a separate snmp-server host command for each host. The maximum number of snmp-server host commands is four.
When multiple snmp-server host commands are given for the same host, the community string in the last command is used.
The snmp-server host command is used in conjunction with the snmp-server enable traps command to enable SNMP traps.
In addition, SNMP must be enabled with the snmp-server community command.
The following example sends the SNMP traps defined in RFC 1157 to the host specified by the IP address 172.30.2.160. The community string sent n the trap message is defined as comaccess.
Console(config)# snmp-server enable traps
Console(config)# snmp-server host 172.30.2.160 comaccess
Console(config)# no snmp-server host 172.30.2.160
snmp-server enable traps
snmp-server community
To set the system location string, use the snmp-server location global configuration command. Use the no form of this command to remove the location string.
snmp-server location lineline String that describes the physical location of this node.
No system location string is set.
The system location string is the value stored in the MIB-II system group system location object.
You can see the system location string with the show snmp EXEC command.
The following is an example of a system location string:
Console(config)# snmp-server location Building 3/Room 214
show snmp
snmp-server contact
To configure TCP parameters, use the tcp global configuration command. To disable TCP parameters, use the no form of this command.
tcp {client-mss size | client-receive-buffer kbytes | client-rw-timeout seconds | client-satellite | client-send-buffer kbytes | cwnd-base factor | init-ssthresh value | keepalive-probe-cnt count | keepalive-probe-interval seconds | keepalive-timeout seconds | listen-queue length server-receive-buffer kbytes | server-mss size | server-rw-timeout seconds | server-satellite | server-send-buffer kbytes}client-mss Client TCP maximum segment sixe.
size Maximum segment size (512 to 1460).
client-receive-buffer Client connection's receive buffer size.
kbytes Client buffer size (8 to 1024) in kilobytes.
client-rw-timeout Client connection's read/write timeout.
seconds Timeout (1 to 3600) in seconds.
client-satellite Client TCP compliance to RFC1323 standard.
client-send-buffer Client connection's send buffer size.
kbytes Server buffer size (1 to 1024) in kilobytes.
cwnd-base TCP cwnd base factor.
factor Factor value (1 to 16).
init-ssthresh TCP initial smooth threshold.
value Treshold value (2920-1073741824).
keepalive-probe-cnt TCP keepalive probe counts.
count Times (1 to 10).
keepalive-probe-interval TCP keepalive probe interval.
seconds Seconds (1 to 300).
keepalive-timeout TCP keepalive timeout.
seconds Seconds (1 to 3,600).
listen-queue Maximum size of TCP listen queue.
length Listen queue length (1 to 1,000).
server-mss Server TCP maximum segment size.
size Maximum segment size (512 to 1460).
server-receive-buffer Server connection receive buffer size.
kbytes Buffer size (1 to 128) in kilobytes.
server-rw-timeout Server connection read/write timeout.
seconds Timeout (1 to 3,600) in seconds.
server-satellite Server TCP compliance to RFC1323 standard.
server-send-buffer Server connection send buffer size.
kbytes Buffer size (1 to 128) in kilobytes.
tcp client-receive-buffer 8 kilobytes
tcp client-rw-timeout 30 seconds
tcp client-send-buffer 8 kilobytes
tcp keepalive-probe-cnt 4
tcp keepalive-probe-interval 75 seconds
tcp keepalive-timeout 300 seconds
tcp server-receive-buffer 8 kilobytes
tcp server-rw-timeout 120 seconds
tcp server-send-buffer 8 kilobytes
In nearly all environments, the default TCP setting will be adequate.
You must reboot the Cache Engine when changes are made to the TCP maximum segment size client-mss or server-mss setting in order for this option to take effect. Please save the configuration and reboot the Cache Engine.
You must reboot the Cache Engine when changes are made to the TCP satellite client-satellite or server-satellite setting in order for this option to take effect.
You must reboot the Cache Engine when changes are made to the listen-queue setting in order for this option to take effect.
Console(config)# tcp client-receive-buffer 100
Console(config)# no tcp client-receive-buffer 100
show tcp
To configure the current terminal commands, use the terminal global configuration command. To disable the this function, use the no form of this command.
terminal length lineslength Keyword.
lines Number of lines on screen (0 to 512). Select 0 for no pausing.
Use this command to set the number of lines displayed in the console window at one time before pausing. This command is useful for monitoring output from all show commands in the EXEC mode, some of which require more than one screen length when complete. Once the limit has been reached, the -More- prompt is displayed. To view the next screen, use the Space bar. To view one line at a time, use the Enter key. To exit the show command output, use the Esc key or any other keystroke.
Console(config)# terminal length 0
Console(config)# no terminal length 0
All show commands.
To enable transaction logs, use the transaction-logs global configuration command. To disable transaction logs, use the no form of this command.
transaction-logs {destination disk | interval time}destination Location to store log files.
disk Logs to the disk to the file (/local/var/log/working.log).
interval Working log file is archived after this interval.
time Interval time in seconds (1 Day = 86400 sec) (120 to 60,4800).
The default is 86,400 second interval.
Use these commands to record all transactions serviced by the Cache Engine. To enable the feature, use the transaction-logs destination disk command. To configure the length of each working log (in seconds), use the transaction-logs interval time command. If no interval is configured, the Cache Engine will default to 86,400 seconds. Each working log is archived after the time interval allotted, and is stored as the archive log until over-written by a newly completed working log. Both log files can be found in the /local/var/log directory.
Console(config)# transaction-logs destination /local
Console(config)# no transaction-logs destination /local
show transaction-logging
type working log
type archive log
To enable trusted hosts on your Cache Engine, use the trusted-host global configuration command. To disable trusted hosts, use the no form of this command.
trusted-host {hostname | ip-address | domain-lookup}hostname Host name.
ip-address IP Address.
domain-lookup Trusted host checking.
No trusted hosts is the default.
To allow reception of files (for example, rcp) from specified hosts, these hosts must be identified using the trusted-host hostname command. It is necessary to also enable this feature using the trusted-host domain-lookup command.
Console(config)# trusted-host 171.71.90.33
Console(config)# no trusted-host domain-lookup
show trusted-hosts
To enable URL blocking, use the url-filter global configuration command. To disable URL blocking, use the no form of this command.
url-filter {bad-sites-block | good-sites-allow} [custom-message]bad-sites-block Block access to sites listed in badurl.lst file.
good-sites-allow Allows access only to sites listed in goodurl.lst file.
custom-message Display customized URL blocking message from block.html file.
Use this command to either block access to restricted sties or allow access only to selected sites. Only one type of URL-filtering may be enabled at one time. Lists of allowed or restricted sites must also exist in the file system for proper functionality. To create URL lists, open a plain text file using the www.domain.com format. The filenames must be badurl.lst for the bad-site-block keyword, and goodurl.lst for the good-sites-allow keyword. Using FTP, put these lists into the /local/etc directory of the Cache Engine.
This custom-message option allows you to customize the blocked message that is sent back to a user when a request from the client matches a blocked URL. This flexibility is provided by allowing you to create your own HTML page called block.html and place it in the /local/etc/ directory. If you want to embed graphics into the HTML page, place the corresponding graphics gif/jpeg file in the /local/lib/gui/pub directory.
An example of the block.html file is:
<HTML>
<HEAD>
<TITLE>
URL Blocked
</TITLE>
</HEAD>
<BODY>
The site you are trying to view is blocked. Please contact your system
administrator if you need to unblock this site <IMG_SRC =
/local/lib/gui/pub/stop.gif width=492 height=94 border=0>
</BODY>
</HTML>
Once you have created your customized block.html page, you can turn on this feature from the CLI. To turn on the customized URL blocking message, enter:
url-filter bad-sites-allow custom-messageTo turn on the customized URL blocking message, enter:
url-filter bad-sites-allowConsole(config)# url-filter bad-sites-block
Console(config)# no url-filter
show url-filtering
To configure user accounts on your Cache Engine, use the user global configuration command.
user add username [capability] [admin-access]add Adds new user information.
delete Deletes the user information.
mod Changes the user information.
username Name of the user.
capability (Optional) Add capability to a new user. Use with add keyword.
add-capability Add capability to an existing user. Use with modify keyword.
del-capability Delete capability to an existing user. Use with modify or delete keyword.
Capability options:
admin-access — Every possible access to Cache Engine.
ftp-access — FTP access to the Cache Engine.
http-access — HTTP (Web) access to the Cache Engine.
telnet-access — Telnet access to the Cache Engine.
password Password. Password options:
0 — Specifies clear-text password will follow (default).
1 — Specifies type 1 encrypted password will follow.
word User password.
username Name of the user.
name Username.
uid User's ID number. ID number options:
numberA — User ID number (2001 to 2147483647).
numberD — User ID number (1 to 2147483647).
numberM — User ID number (0 to 2147483647).
Default users upon first boot-up (for example, admin).
Use this command to configure new users to the Cache Engine or to modify or delete existing users. You may use this command to modify user passwords, user identification numbers, or access to the Cache Engine allowed for each user. Capabilities (access) include ftp-access, http-access, and telnet-access or complete access to the cache is possible using the admin-access option. Up to 50 users may be configured.
Console(config)# user add rich
Operation successful
show user
show users
list-number Router list number (1 to 8).
port-number Port number (1 to 16000). The port number specifies the outgoing port destinations of all traffic redirected to the Cache Engine.
hash-destination-ip Load balancing hash - Destination IP.
hash-destination-port Load balancing hash - Destination Port.
hash-source-ip Load balancing hash - Source IP.
hash-source-port Load balancing hash - Source Port.
password word Authentication WCCP service password (key).
weight Weight percentage (0 to 100).
hash-destination-ip
The custom web-cache service allows custom configured outgoing port HTTP requests.
The appropriate Router List should be configured from Enable WCCP service GUI page or through CLI commands. Only limited router IP addresses will be queried. Those router's IP addresses should be entered to the list and will be associated with this service. Each List could consist up to 32 addresses. Eight Router Lists are available for configuration. You have to select the Router List number during the custom transparent caching service configuration. An error message will be displayed if empty Router List was selected.
The weight option enables manual control of load balancing. Total value collected from all Cache Engines is added to establish a percentage of the total load. If the entered number is outside of the 0 to 100 range, an error message is displayed.
Hashing specifies how traffic should be load balanced between mutiple caches. If there is only one Cache Engine present, selecting the hashing algorithm should make no impact because al the traffic will be directed towards it. You should configure hashing for the custom web-cache service. You can select one or more of the configurable options. The default hash is Destination IP.
Console(config)# wccp custom-web-cache router-list-num 5 port 82 weight
30 password Test hash-destination-ip hash-source-ip
Console(config)# no wccp custom-web-cache
To enble flow redirection, use the wccp flow-redirect command. To use this command, you must be using WCCP Version 2.
wccp flow-redirectThis command has no argument or keywords.
Disabled.
Use the wccp flow-redirect command to enable flow redirection.
Console(config)# wccp flow-redirect enable
Console(config)# no wccp flow-redirect enable
To configure a WCCP version 1 router IP address, use the wccp home-router global configuration command. To disable this function, use the no form of this command.
wccp home-router ip-addressip-address Home router's IP address.
Disabled.
To use WCCP Version 1 with the Cache Engine, you must also point the Cache Engine to a designated home router. Use the wccp home-router ip-address command to do this. This may also be the address of the IP default gateway.
Make sure that WCCP Version 1 is enabled on the router.
Console(config)# wccp home-router 171.71.65.243
Console(config)# no wccp home-router 171.71.65.243
show wccp routes
wccp version 1
To enable WCCP version 2 reverse proxy service, use the wccp reverse-proxy global configuration command. To disable this function, use the no form of this command.
wccp reverse-proxy router-list-num number [password key] [weight percentage]router-list-num Router list number.
number Router list number (1 to 8).
password (Optional) Authentication password (key) for the router.
key (Optional) Password for the router.
weight (Optional) Weight percentage for the router.
percentage (Optional) Percentage of load (1 to 100) that the system carries as compared to others.
Disabled.
This command applies only to WCCP Version 2.
You must set the wccp router list command before you use this command.
The options do not have to be specified in order. For example, you may specify the password or weight only.
By default, the router does load balancing across the various Cache Engines in a cluster based on the destination IP address (for example, web server IP address). When WCCP reverse-proxy is enabled, the router does load-balancing in a cluster based on the source IP address (for example, client's browser IP address).
To enable the use of a password for a secure reverse-proxy cache within a cluster, use the password key command to be sure to enable all other caches and routers within the cluster with the same password.
To specify the amount of total load to be assigned to each cache within a cluster, use the weight command. This value is totaled with weight values assigned to other caches within the cluster, and this total is used to discern the percentage of total load assigned to each cache. If one or more Cache Engines within the cluster are configured with a weight value, than only those with a weight assignment will be given a load allotment.
Console(config)# wccp reverse-proxy router-list-num 8 password key
weight 100
Console(config)# no wccp reverse-proxy
show wccp cache-engines
show wccp services
wccp router-list
wccp version 2
To configure a router list for WCCP Version 2, use the wccp router-list global configuration command. To disable this function, use the no form of this command.
wccp router-list number ip-addressnumber Number of router lists (1 to 8).
ip-address IP address (1 to 6).
Disabled.
Use this command to configure various router lists for use with WCCP Version 2 services. For example, you may run WCCP Version 2 web-cache service using one router list, and reverse-proxy using another. This allows you to switch the cache between WCCP Version 2 environments by changing the router list for the service running without having to reconfigure groups of routers or caches. You may add up to eight router lists and up to six IP addresses per list.
Console(config)# wccp router-list 7 171.71.68.98
Console(config)# no wccp router-list 7 171.71.68.98
wccp reverse-proxy
wccp web-cache
wccp version 2
To configure the WCCP Version, use the wccp version global configuration command. Use the no form of the command to disable the currently running version. To disable this function, use the no form of this command.
wccp version {1 | 2}1 WCCP Version 1.
2 WCCP Version 2.
Version 1.
WCCP allows transparent caching of web content. For a detailed description of both versions, see Appendix B and C. It is necessary to disable WCCP Version 1 before enabling WCCP Version 2, and vice-versa. Be sure the router(s) used in the WCCP environment are running an image compatible with the version configured on the cache.
Console(config)# no wccp version 1
Console(config)# wccp version 2
wccp home-router
To instruct the router to run the web-cache service with WCCP Version 2, use the wccp web-cache global configuration command. To disable this function, use the no form of this command.
wccp web-cache route-list-num number [password key] [weight percentage]route-list-num Router list number.
number Number of the router list (1 to 8).
password (Optional) Authentication password (key) for the router.
key (Optional) Password for the router.
weight (Optional) Weight percentage for the router.
percentage (Optional) Weight of load (1 to 100) that the system carries as compared to others.
Use this command to enable web-cache service with WCCP Version 2. With web-cache service, the router balances the traffic load within a cache cluster based on the destination IP address (for example, web-server IP address).
You must set the wccp router-list command before you use this command.
Both weight and password are optional and may be used together or separately.
To enable the use of a password for a secure web-cache cluster, use password key and be sure to enable all other caches and routers within the cluster with the same password.
To specify a certain amount of total load to be assigned to each cache within a cluster, use the weight command. This value is totaled with weight values assigned to other caches within the cluster, and this total is used to discern the percentage of total load assigned to each cache. If one or more Cache Engines within the cluster are configured with a weight value, than only those caches within the cluster that do have a weight assignment will be given a load allotment. By default, a router will divide the load evenly between the number of caches within a cache cluster.
Console(config)# wccp web-cache router-list-num 1
Console(config)# no wccp web-cache
show wccp cache-engines
show wccp services
wccp version 2
The interface configuration Cache Engine commands are entered in the interface configuration mode.
To enter the interface configuration mode, enter the following commands:
Console# config
Console(config)# interface ?
ethernet Select an ethernet interface to configure
Console(config)# interface ethernet 0
Console(config-if)# ?
Configure Interface commands:
autosense Interface autosense
bandwidth Interface speed
exit Exit from interface mode
fullduplex Interface fullduplex
halfduplex Interface halfduplex
ip Interface Internet Protocol Config commands
no Negate a command or set its defaults
To exit the interface configuration mode, enter exit to return to the global configuration mode.
Console(config-if)# exit
Console(config)#
The section describes the following interface configuration commands.
To enable auto sense on a interface, use the autosense interface configuration command. To disable this function, use the no form of this command.
autosenseThis command has no arguments or keywords.
Use this command to auto sense on a interface.
Console(config-if)# autosense
Console(config-if)# no autosense
To configure an interface bandwidth, use the bandwidth interface configuration command. To disable this function, use the no form of this command.
bandwidth mbitsmbits 10 megabits (10-10).
100 megabits (100-100).
Use this command to set the bandwidth of an interface to either 10 or 100 megabits.
Console(config-if)# bandwidth 10
Console(config-if)# no bandwidth
To exit the Interface Config mode, use the exit interface configuration command.
exitThis command has no arguments or keywords.
Use this command to return to the global configuration mode from the interface configuration mode.
Console(config-if)# exit
Console(config)#
To configure an interface full duplex, use the fullduplex interface configuration command. To disable this function, use the no form of this command.
fullduplexThis command has no arguments or keywords.
Use this command to configure an interface for full duplex. Full duplex allows data to travel in both directions at the same time through an interface or a cable per instance. A half-duplex setting ensures that data only travels in one direction at any given time. Full duplex is obviously faster, but sometimes the interfaces can't seem to handle it for some reason. If you run into collisions or other sorts of problems, you may want to configure an interface for half duplex rather than full duplex.
Console(config-if)# fullduplex
Console(config-if)# no fullduplex
halfduplex
To configure an interface half duplex, use the halfduplex interface configuration command. To disable this function, use the no form of this command.
halfduplexThis command has no arguments or keywords.
Use this command to configure an interface for half duplex. Full duplex allows data to travel in both directions at the same time through an interface or a cable per instance. A half-duplex setting ensures that data only travels in one direction at any given time. Full duplex is obviously faster, but sometimes the interfaces cannot seem to handle it for some reason. If you run into collisions or other sorts of problems, you may want to configure an interface for half duplex rather than full duplex.
Console(config-if)# halfduplex
Console(config-if)# no halfduplex
fullduplex
To configure the IP interface, use the ip interface configuration command. To disable this function, use the no form of this command.
ip {address ip-address ip-subnet | broadcast-address ip-address}address Sets the IP address of an interface.
broadcast-address Sets the broadcast address of an interface.
ip-address IP address.
ip-subnet IP subnet mask.
Use this command to set or change the IP address and subnet mask of the Cache Engine (Interface ethernet 0). The Cache Engine requires a reboot in order for the new IP address to take effect.
Console(config-if)# ip address 12.10.10.10 255.0.0.0
Console(config-if)# no ip broadcast-address
To negate a command or set its defaults, use the no interface configuration command.
no {autosense | bandwidth | fullduplex | halfduplex | ip}autosense Interface autosense.
bandwidth Interface speed.
fullduplex Interface fullduplex.
halfduplex Interface halfduplex.
ip Interface Internet Protocol (IP) configuration commands.
Use this command to negate a interface configuration mode command or set its defaults. See the interface configuration command descriptions for syntax options and descriptions.
Console(config-if)# no autosense
The show Cache Engine commands are entered in the EXEC mode. The following show commands are described in the following pages:
To view access to a particular path, group, user, use the show access EXEC command.
show access pathname {groupname name | username name}pathname Absolute pathname of a file or a directory.
groupname Group name.
username Username.
name Group or username whose access rights is to be shown.
Use this command to view access for a user or group to a particular path in the cache file system.
Console# show access /local/etc groupname name username name
show user
show users
To display the Address Resolution Protocol (ARP) table, use the show arp EXEC command.
show arpThis command has no arguments or keywords.
Console# show arp
LINK LEVEL ARP TABLE
destination gateway flags Refcnt Use
Interface
171.69.227.129 00:e0:b0:e2:6d:a2 405 1 0 fei0
Console#
To display authentication bypass or load bypass statistics, use the show bypass command.
show bypass statistics {auth-traffic | load}
auth-traffic Display Auth Bypass Statistics.
load Display Load Bypass statistics.
Console#show bypass statistics auth-traffic
Total number of connections bypassed = 0
Number of Entries in Bypass list = 0
Console#show bypass statistics load
Load Bypass is enabled
System is currently in non-bypass mode
Total number of connections bypassed = 0
Total number of packets bypassed = 0
System changes Bypass to Normal mode = 0
System changes Normal to Bypass mode = 0
MODULE Normal Overload Cumulative Secs
------ ------ -------- ---------------
net bufs 0 0 0
net bufs 0 0 0
tF2000a 0 0 0
tCfsV000 0 0 0
tCfsC000 0 0 0
tF2001a 0 0 0
tCfsV001 0 0 0
tCfsC001 0 0 0
ceworkq 0 0 0
To view information about your cache file system, use the show cfs EXEC command.
show cfs {statistics | volumes}statistics Displays the cache file system statistics.
volumes Displays the cache file system volumes.
Console# show cfs statistics
Filesystem Statistics for volume /c0t0d0s3 Status: mounted
Disk Wraps 0
Inode Hits 0
Inode Misses 0
CFS Read error 0
CFS Write error 0
Inode load error 0
Attribute load error 0
CFS object Truncations 0
Truncated CFS object Flushes 0
Filesystem Statistics for volume /c0t1d0s3 Status: mounted
Disk Wraps 0
Inode Hits 0
Inode Misses 0
CFS Read error 0
CFS Write error 0
Inode load error 0
Attribute load error 0
CFS object Truncations 0
Truncated CFS object Flushes 0
Console# show cfs volumes
/c0t0d0s3: mounted
/c0t1d0s3: mounted
cfs
To display the system clock, use the show clock EXEC command
show clock [detail]detail (Optional) Display detailed information; Indicates the clock source (NTP) and the current summer-time setting (if any).
Console# show clock
Wed Apr 28 20:52:48 1999 GMT
Console show clock detail
Tue Jun 1 14:48:18 1999 GMT
Tue Jun 1 07:48:18 1999 LocalTime
Epoch: 928248498 seconds
UTC offset: -25200 seconds (-7 hr 0 min)
timezone: PST
summerzone: PDT
summer offset: 0 minutes
daylight: summer
clock clear
clock set
To displays CRON information, use the show cron EXEC command.
show cronThis command has no arguments or keywords.
Console# show cron
==CRON Configuration==
CRON tab file: /local/etc/crontab
Legend 1: min hr day-of-mon mon day-of-wk tclsh script-name
Legend 2: min hr day-of-mon mon day-of-wk tcl tcl-cmd
Sample: 0 5 * * * tclsh /local/test.tcl
Crontab for user: "root"
Id Type Source Entry
1 log_recycle api 0 * * * * tclsh
/local/lib/tcl/recycle.tcl 50000
00 /local/var/log/syslog.txt
To display the state of each debugging option, use the show debugging EXEC command.
show debuggingThis command has no arguments or keywords.
This command will only display the TYPE of debugging enabled, not the specific subset of the command. For example, it shows ICP debugging is enabled, but will not define if that debugging is monitoring ICP client or server packet transfer.
Console# debug icp client trace
Console# show debugging
icp debugging is on
debug
no debug
undebug
To view information about your disk partitions, use the show disk-partitions EXEC command.
show disk-partitions devnamedevname Device name.
Use this command to display partition information about a particular disk. The command show disks displays the names of the disks currently attached to the Cache Engine.
Console# show disk-partitions devname
disk partition
disk prepare
show disks
To view information about your disks, use the show disks EXEC command.
show disksThis command has no arguments or keywords.
The command show disks displays the names of the disks currently attached to the Cache Engine. You can partition a disk using the disk partition command.
Console# show disks
/c0t0d0 (scsi bus 0, unit 0, lun 0)
/c0t1d0 (scsi bus 0, unit 1, lun 0)
disk partition
disk prepare
show disk-partitions
To display DNS cache information, use the show dns-cache EXEC command.
show dns-cacheThis command has no arguments or keywords.
Console# show dns-cache
-- DNS Cache Configuration --
DNS cache: ON
Max cache size: 1024
Hash table size: 256
--- DNS Cache Statistics ---
Hit: 0 Miss: 1 Expire: 0 Total Access: 1
Add: 1 Del: 0 Update: 0 Drain: 0 Total Rec: 1
To view DOS file system information, use the show dosfs EXEC command.
show dosfs {config volname | label devicename | volumes}config Displays the DOS file system configuration for specified volume.
label Displays device volume label.
volumes DOS volumes.
volname Volume name.
devicename Device name.
Console# show dosfs volumes
/c0t0d0s1: mounted
/c0t1d0s1: not mounted
/local: mounted
dosfs
cfs
show cfs
To display a number of system events by category, use the show events EXEC command.
show events number {all | critical | notice | warning}number Number of events to display (1 to 65,535).
all Shows all events.
critical Shows critical events.
notice Shows notice events.
warning Shows warning events.
Use this command to show the chosen number of events by category.
Console# show events 10 notice
Notice: Waiting for admin traffic on port 8001
Thu, 01 Jan 1970 00:00:10 GMT
Notice: Waiting for Web traffic on port 80
Thu, 01 Jan 1970 00:00:09 GMT
Notice: Waiting for Web Proxy traffic on port 8080
Thu, 01 Jan 1970 00:00:10 GMT
Notice: Waiting for admin traffic on port 8001
Thu, 01 Jan 1970 00:00:10 GMT
Notice: Waiting for Web traffic on port 80
cepro#
To display information about the Cache Engine's file descriptors, use the show file-descriptors EXEC command.
show file-descriptorsThis command has no arguments or keywords.
Console# show file-descriptors
fd name drv
4 /tyCo/0 1 in out err
9 (socket) 6
10 (socket) 6
11 (socket) 6
12 (socket) 6
15 (socket) 6
18 /pipe/ring 2
19 /pipe/log 2
20 /c0t0d0s1/_uv_acl_.db 3
21 /raw0 5
22 /raw1 5
23 /raw2 5
24 /raw3 5
25 /raw4 5
26 /raw5 5
27 /raw6 5
28 /raw7 5
29 /null 0
36 (socket) 6
37 (socket) 6
38 /local/events.dat 4
39 /local/radius.dat 4
50 (socket) 6
To display the Flash memory content, such as file code names, version numbers, and sizes, use the show flash EXEC command.
show flashThis command has no arguments or keywords.
Console# show flash
System flash directory:
File Length Name/status
1 3412352 system image
[655360 read only, 3674496 bytes used, 3731072 available, 8388608 total]
To display a user group configured on the Cache Engine, use the show group EXEC command.
show group {gid gidnumber | groupname name | users {gid gidnumber | groupname name}}gid Group Identification Number (GID).
gidnumber Group ID of group (0 to 2147483647).
groupname Group name.
name Group name.
users Users in group.
Console# show group gid 1004
GroupName: LocalUsers
Gid: 1004
Number of Users in Group: 10
To display all groups configured on the Cache Engine, use the show groups EXEC command.
show groupsThis command has no arguments or keywords.
Console# show groups
There are 4 groups(s)
GID GROUPNAME
0 root
1000 everyone
1001 nogroup
1004 LocalUsers
To display system hardware status, use the show hardware EXEC command.
show hardwareThis command has no arguments or keywords.
Console# show hardware
Cisco Cache Engine
Copyright (c) 1986-1999 by Cisco Systems, Inc.
Image text-base 0x108000, data_base 0x425a5c
System restarted by Power Up
The system has been up for 19 hours, 43 minutes, 21 seconds.
System booted from fei
Cisco Cache Engine CE505 with CPU AMD-K6 (model 7) (rev. 0) AuthenticAMD
2 Ethernet/IEEE 802.3 interfaces
1 Console interface.
134213632 bytes of Physical Memory
131072 bytes of ROM memory.
8388608 bytes of flash memory.
show version
To view the hosts on your Cache Engine, use the show hosts EXEC command.
show hostsThis command has no arguments or keywords.
Console# show hosts
Domain name = cisco.com
Name Servers:
-----------
ip address
ip address
Host Table:
hostname inet address aliases
-------- ------------ -------
localhost ip address
Rich's_cache ip address
To display the HTTP related caching parameters, use the show http EXEC command.
show http {age-mult | all | cache-authenticated | cache-cookies | cache-miss | cluster | max-ttl | persistent-connections | proxy | reval-each-request | serve-ims}age-mult HTTP caching hueristic modifiers.
all All HTTP related caching parameters.
cache-authenticated Caching of authenticated web objects.
cache-cookies Caching of web objects with associated cookies.
cache-miss Handling of 'no-cache' requests.
cluster Cluster healing configuration.
max-ttl Maximum time to live for objects in the cache.
persistent-connections Persistent connections configuration.
proxy Proxy mode configuration.
reval-each-request Configuration of revalidation for every request.
serve-ims Handling of If-Modified-Since requests.
Console# show http proxy
Incoming Proxy-Mode:
Servicing proxy mode connections on port 8080.
Outgoing Proxy-Mode:
Not using outgoing proxy mode.
To display the ICP client, root, or server information, use the show icp EXEC command.
show icp {client | root | server}client Shows ICP client detailed information.
root Shows ICP brief client/server information.
server Shows ICP server detailed information.
Console# show icp client
ICP client is disabled
max wait for replies = 2 seconds
remove from wait list after 20 failures
local_domain ""
Number of remote servers = 0
Total Icp Requests: 0
Total Icp Hits : 0
icp client
icp server
To display TCP/IP services, which include echo, discard, charger, ftp, rcp, telnet, and tftp, use the show inetd EXEC command.
show inetdThis command has no arguments or keywords.
Console# show inetd
Inetd task ID: 7fbc400
Inetd running configuration:
Service Port Proto Func Max Live Total Acpt Rej
Stck Lock
echo 7 tcp 1d863c 0 0 0 0 0
2048 0
echo 7 udp 1d86dc 0 0 0 0 0
2048 0
discard 9 tcp 1d875c 0 0 0 0 0
2048 0
discard 9 udp 1d87cc 0 0 0 0 0
2048 0
chargen 19 tcp 1d884c 0 0 0 0 0
2048 0
chargen 19 udp 1d88fc 0 0 0 0 0
2048 0
ftp 21 tcp 2b9df0 10 0 0 0 0
4096 0
rcp 514 tcp 1ec45c 5 0 0 0 0
4096 0
tftp 69 udp 2bdf2c 5 0 0 0 0
12288 0
telnet 23 tcp 2b81f0 3 0 0 0 0
4096 0
inetd
To display hardware interfaces, use the show interface EXEC command.
show interface {ethernet number | scsi number}ethernet Ethernet interface device.
number Ethernet interface number.
scsi SCSI interface device.
number SCSI interface number.
Console# show interface scsi 0
Max Transfer Size: 16777215
Sync: yes
Disconnect: yes
Wide: yes
set interface
To display IP information, use the show ip EXEC command.
show ip routesroutes Displays routing table.
The following example shows how to display sl0 and sc0:
Console# show ip routes
Destination Mask TOS Gateway Flags RefCnt Use
In
terface Proto
0.0.0.0 0 0 171.69.227.129 3 1 17080
fe
i0 0
127.0.0.1 0 0 127.0.0.1 5 2 4
lo
0 0
171.69.227.128 ffffff80 0 171.69.227.250 101 0 0
fe
i0 0
ip route
no ip route
To display the system message log configuration, use the show logging EXEC command.
show loggingThis command has no arguments or keywords.
Console# show logging
logging: on
priority of messages for console: warnings
priority of messages for file: debugging
log file: /local/var/log/syslog.txt
log file recycle size: 5000000
To display memory blocks and statistics, use the show memory EXEC command.
show memory freefree Free blocks.
Console# show memory free
FREE LIST:
num addr size
--- ---------- ----------
1 0x4e6cc28 56
2 0x4e6ca04 284
3 0x7fec8f8 5788
4 0x36dec00 20
5 0x36d01d8 32
6 0x36d0560 28
7 0x2daee7c 9485348
8 0x7fd7000 3868
9 0x3711000 236
SUMMARY:
status bytes blocks avg block max block
------ --------- -------- ---------- ----------
current
free 9495660 9 1055073 9485348
alloc 76750080 2525 30396 -
cumulative
alloc 76789352 2883 26635 -
Page Freelist:
num address npages canfree
--- ---------- ---------- -------
0 0x6eba000 16 0 0
1 0x6eaf000 5 0 0
2 0x4e7d000 8232 0 0
To display the NTP parameters, use the show ntp EXEC command.
show ntp statusstatus NTP status.
Console# show ntp status
NTP subsystem
-------------
servers:
ntp
To display CPU or memory processes, use the show processes EXEC command.
show processes [cpu | memory]cpu (Optional) CPU utilization.
memory (Optional) Memory allocation of information.
Console# show processes cpu
Current CPU Percentage = 0
Peak CPU Percentage = 22
Console# show processes memory
Pages:
page size pages free hiwat lowat total
--------- ------- ------ ------ ------ -------
4096 17720 14839 25103 2091 29535
Type:
bytes blocks sizes max byt tot blk pagw
--------- ------ ------- -------- ------- ----
unknown 1600 100 0x10 1616 104 0
fcache bufhdr 12800 100 0x80 12800 100 0
fcache buffer 614400 100 0x3000 614400 100 0
fcache IO 0 0 0x80 256 46 0
fcache phys 409984 14 0x12040 409984 14 0
confval 192 3 0x350 960 402 0
task 71280 270 0x210 71808 500 0
stack 1257472 135 0x1f800 1323008 250 0
DB misc 2048 2 0x400 2048 2 0
DB hashtab 1024 1 0x400 1024 1 0
DB open 128 1 0x80 128 1 0
DB bufhead 64 2 0x20 64 2 0
DB cache 8192 2 0x1000 8192 2 0
DB databuf 0 0 0xb0 160 244 0
DB api 32 1 0x60 96 123 0
--More--
Console# show processes
NAME ENTRY TID PRI STATUS PC SP ERRNO
DELAY
---------- ------------ -------- --- ---------- -------- --------
------- -----
tExcTask 3ca048 3a71aec 0 PEND 3fa981 3a71a5c
3006b 0
tLogTask 39a21c 3a6f1d4 0 PEND 3fa981 3a6ed3c
0 0
tWdbTask 3c46d4 161a18c 3 PEND 3c5a19 1619878
0 0
tScsiTask 3f5920 15ec514 5 PEND 3c5a19 15ec4b4
0 0
tF2000a 1260e8 7df1c00 25 PEND 3c5a19 7ddaf84
0 0
tF2000b 1260e8 7df1e00 25 PEND 3c5a19 7dc9f84
0 0
tF2001a 1260e8 7dc8e00 25 PEND 3c5a19 7507f84
0 0
tF2001b 1260e8 74f5000 25 PEND 3c5a19 74f6f84
0 0
tNetTask 3b201c 162a578 50 PEND 3c5a19 162a52c
41 0
tWCCP2 34e978 74eb200 60 PEND+T 3c5a19 74e8734
3d0004 27
tHotSpot 34b9b0 749a400 60 DELAY 39b996 74b1fa4
0 64
tDtimer 1214d8 7fb1000 75 DELAY 39b996 7f73fa8
0 7
tTtyUtil 264a18 74f5800 75 PEND 3fa981 74eef80
0 0
tOvrldDaemo281120 74a2400 75 PEND 3c5a19 749cfb0
0 0
tHealSrv 336340 74df000 75 PEND+T 3c5a19 74a870c
3d0004 2224
tCfsC000 244ed4 7dc8c00 98 PEND+T 3c5a19 7d93f58
3d0004 210
tCfsC001 244ed4 74f5400 98 PEND+T 3c5a19 74f3f58
3d0004 266
tCfsV000 224a4c 7dc8200 99 PEND+T 3c5a19 7d82f74
3d0004 150
tCfsT000 224d1c 7dc8400 99 PEND 3c5a19 794cfa4
0 0
--More--
To show RADIUS information, use the show radius EXEC command.
show radiusThis command has no arguments or keywords.
Console# show radius
No Radius servers are configured.
To display the current running configuration information on the terminal, use the show running-config EXEC command. This command replaces the write terminal command.
show running-configThis command has no arguments or keywords.
Use this command in conjunction with the show startup-config command to compare the information in running memory to the startup configuration used during boot-up.
Console# show running-config
Building configuration...
Current configuration:
!
!
!
group add admin gid 0
group add everyone gid 1000
!
user add admin uid 0 password 1 "ceSzbyeb" capability admin-access
user add britt uid 2001
!
!
!
hostname Rich's_cache
!
interface ethernet 0
ip address 171.69.227.250 255.255.255.128
ip broadcast-address 171.69.227.255
exit
!
!
interface ethernet 1
exit
--More--
configure
copy running-config
copy startup-config
To check the status of SNMP communications, use the show snmp EXEC command.
show snmpThis command has no arguments or keywords.
This command provides counter information for SNMP operations.
Console# show snmp
Contact: Mary Brown, system admin, mbrown@acme.com 555-1111
Location: Building 2, 1st floor, Lab 1
37 SNMP packets input
0 Bad SNMP version errors
4 Unknown community name
0 Illegal operation for community name supplied
0 Encoding errors
24 Number of requested variables
0 Number of altered variables
0 Get-request PDUs
28 Get-next PDUs
0 Set-request PDUs
78 SNMP packets output
0 Too big errors
0 No such name errors
0 Bad values errors
0 General errors
24 Response PDUs
13 Trap PDUs
Table A-1 describes the fields shown in the display.
| Field | Description |
|---|---|
SNMP packets input | Total number of SNMP packets input. |
Bad SNMP version errors | Number of packets with an invalid SNMP version. |
Unknown community name | Number of SNMP packets with an unknown community name. |
Illegal operation for community name supplied | Number of packets requesting an operation not allowed for that community. |
Encoding errors | Number of SNMP packets that were improperly encoded. |
Number of requested variables | Number of variables requested by SNMP managers. |
Number of altered variables | Number of variables altered by SNMP managers. |
Get-request PDUs | Number of get requests received. |
Get-next PDUs | Number of get-next requests received. |
Set-request PDUs | Number of set requests received. |
SNMP packets output | Total number of SNMP packets sent by the router. |
Too big errors | Number of SNMP packets that were larger than the maximum packet size. |
Maximum packet size | Maximum size of SNMP packets. |
No such name errors | Number of SNMP requests that specified a MIB object which does not exist. |
Bad values errors | Number of SNMP set requests that specified an invalid value for a MIB object. |
General errors | Number of SNMP set requests that failed due to some other error. (It was not a noSuchName error, badValue error, or any of the other specific errors.) |
Response PDUs | Number of responses sent in reply to requests. |
Trap PDUs | Number of SNMP traps sent. |
snmp-server chassis-id
To get stack trace information from your Cache Engine, use the show stacktrace EXEC command.
show stacktrace {task-ID | exception}task-ID Hexadecimal number without a 0x prefix (0 to ffffffff).
exception Stack trace on previous exception.
Console# show stacktrace execption
To show the configuration, use the show startup-config EXEC command.
show startup-configThis command has no arguments or keywords.
Use this command to display the configuration used during an initial boot-up, stored in NVRAM.
Console# show startup-config
configure
copy running-config
show running-config
To display Cache Engine statistics, use the show statistics EXEC command.
show statistics {http {ims | performance | requests | savings | usage} | icmp | icp {client | server} | ip | mbuf | routing | tcp | udp}http Displays HTTP caching statistics.
ims If-Modified-Since statistics.
performance Performance statistics.
requests Requests statistics.
savings Savings statistics.
usage Usage statistics.
icmp Displays ICMP statistics.
icp Displays ICP caching statistics.
client ICP client statistics.
server ICP Server statistics.
ip Displays IP statistics.
mbuf Displays mbuf statistics.
routing Displays Routing statistics.
tcp Displays TCP statistics.
udp Displays UDP statistics.
To clear statistics without affecting configurations, use the clear statistics command. This will set all counters to zero.
Consolet# show statistics icmp
ICMP:
0 call to icmp_error
0 error not generated because old message was icmp
Output histogram:
echo reply: 37
0 message with bad code fields
0 message < minimum length
0 bad checksum
0 message with bad length
Input histogram:
destination unreachable: 1091
echo: 37
37 message responses generated
clear statistics
To display TCP configuration information, use the show tcp EXEC command.
show tcpThis command has no arguments or keywords.
Console# show tcp
==TCP Configuration==
TCP keepalive timeout 300 sec
TCP keepalive probe count 4
TCP keepalive probe interval 75 sec
TCP client max segment size 1460
TCP server max segment size 1460
TCP client satellite (RFC1323) disable
TCP server satellite (RFC1323) disable
TCP server R/W timeout 120 sec
TCP client R/W timeout 120 sec
TCP server send buffer 8 k
TCP server receive buffer 32 k
TCP client send buffer 32 k
TCP client receive buffer 8 k
TCP Listen Queue 200
TCP init ssthresh 65536
TCP cwnd base 2
To view information necessary for Cisco's Technical Assistance Center (TAC) to assist you, use the show tech-support EXEC command.
show tech-support [page]page (Optional) Page through output.
Use this command to view system necessary for TAC to assist you with your Cache Engine. This is a lengthly display and you may wish to manage the output using the terminal length command.
Console# show tech-support
---------------------show version---------------------
To show the transaction log summaries or to show transaction log settings, use the show transaction-logging EXEC command.
show transaction-logging [entries number]entries (Optional) Displays the last number of entries to the working log file
number (Optional) Number of entries to display (1 to 256).
Use the show transaction-logging command to display the current settings for the transaction logging feature. Use the show transaction-logging entries number command to display the last entries to the working log files. Transaction logging must be enabled in order for the show entries command to work.
Console# show transaction-logging
Transaction Logs:
Logging transactions to local disk
Current Archive Interval: 86400 sec.
Working Log file - size: 0
age: 1739
Archive Log file - size: 0
To show which hosts are trusted on the Cache Engine, use the show trusted-hosts EXEC command.
show trusted-hostsThis command has no arguments or keywords.
Console# show trusted-hosts
Trusted Host checking: ON
ip-address/bert
ip-address/ernie
To display URL filter information, use the show url-filter EXEC command.
show url-filterThis command has no arguments or keywords.
Console# show url-filter
block bad sites.
please look at /local/etc/badurl.lst
To display user information, use the show user EXEC command.
show user {uid number | username name}uid User ID keyword.
number User ID number (0 to 2147483647).
username User's name keyword.
name Username.
Console# show user username rich
Username : rich
Uid : 5001
Number of Groups : 1
Primary Group : everyone (1000)
Password :
Comment :
HomeDir : /local
Capability : no-access
show groups
show users
To display all users, use the show users EXEC command.
show usersThis command has no arguments or keywords.
Console# show users
There are 2 user(s)
UID USERNAME
0 admin
5001 rich
show groups
show user
To display the current software on your Cache Engine, use the show version EXEC command.
show versionThis command has no arguments or keywords.
Console# show version
Cisco Cache Engine
Image text-base 0x108000, data_base 0x425a5c
System restarted by Power Up
The system has been up for 7 hours, 15 minutes, 14 seconds.
System booted from fei
To display WCCP information, use the show wccp EXEC command.
show wccp {auth-bypass-list | bypass-statistics | chache-engines | load-bypass-list | routers | services}auth-bypass-list Shows IP authentication bypass list.
bypass-statistics Shows IP authentication bypass counts.
cache-engines Shows WCCP Cache Engine Information.
load-bypass-list Shows load bypass list.
routers Shows WCCP router list.
services Shows WCCP services configured.
Console# show wccp routers
Routers Seeing this Cache Engine
Router Id Sent To
0.0.0.0 10.1.1.1
Routers not Seeing this Cache Engine
10.1.1.1
Routers Notified of but not Configured
-NONE-
Multicast Addresses Configured
-NONE-
Router Information for Service: Reverse-Proxy
Routers Seeing this Cache Engine
Router Id Sent To
0.0.0.0 10.1.1.1
Routers not Seeing this Cache Engine
10.1.1.1
Routers Notified of but not Configured
-NONE-
Multicast Addresses Configured
-NONE-
Posted: Tue Jun 5 11:57:14 PDT 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.