|
|
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:
To execute a command, type the command at the EXEC system prompt and press the Return key.
There are 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 Delete or Backspace 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, the letters sho can be entered for the show command.
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 leave 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 wish 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 only exits 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 (cfs) contents from memory to disk, use the cache sync EXEC command.
cache {clear [force] | reset | sync}To clear the disk of all cached content, use the cache clear EXEC command.
clear | Clears the cache. |
force | Forcefully deletes all cached objects. |
reset | Resets the cache. |
sync | Synchronizes the cache. |
The cache clear command removes all cached contents from the currently mounted cfs volumes. Objects being read or written are removed when they cease being "busy." The equivalent to this command is the clear cache or cfs clear command.
 |
Caution This command is irreversible, and all cached content will be erased. |
The cache clear force deletes all objects, whether busy or not, and may generate broken GIF/HTML messages for objects that were being read from the disk when the command was executed. If an object is being written to the Cache Engine disk when a cache clear force command is executed, the application stops caching that object but still delivers the object from the web server to the client.
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 operating, this command can be used to ensure all data is written to disk before you reset or turn off the Cache Engine. Synchronization can also be done using the cfs sync command.
Console# cache clear force
clear cache
cfs clear
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
To manipulate the cache object file system of the Cache Engine, use the cfs EXEC command.
cfs {clear volname [force] | format volname | mount volname | reset volname | sync volname | unmount volname}
clear | Deletes nonbusy objects from the specified cfs volume. |
force | Forcibly deletes all objects from the specified cfs volume. |
format | Erases and formats or creates a file system for caching. |
mount | Mounts a cache file system. |
reset | Resets (unmounts-formats-mounts) a cache file system. |
sync | Synchronizes a cache file system. |
unmount | Unmounts a cache file system. |
volname | Volume name (for example, c0t0d0s3). |
Cache objects retrieved from the web are saved and manipulated with the cache file system (cfs) on a cfs partition of the hard disk. This does not affect the dosfs partition, which saves user data, such as syslog.
The cfs commands are used to manage the cache object file system.
The cfs clear command deletes nonbusy objects from the specified cfs volume. A nonbusy object is an object that is not being accessed (read or written). The cfs clear command (without force) deletes all possible objects without generating a broken GIF/HTML message to the client.
The cfs clear force command deletes all objects, busy or nonbusy, and may generate broken GIF/HTML messages for objects that were being read from the disk when the command was executed. If an object is being written to the Cache Engine disk when a cfs clear force command is executed, the application stops caching that object but still delivers the object from the web server to the client.
The cfs reset command unmounts, formats, and mounts a specified volume. Unmounting a volume can result in broken GIF/HTML messages for objects that are being read from the disk (cache hits) when the command is executed. When a cfs volume is reset, all cfs data on that volume is lost.
 |
Note The cfs reset command can be invoked on unmounted volumes. |
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.
|
Caution All cached content is erased with the format command. |
The cfs unmount command frees the in-memory data structures that map 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 used to ensure that all data is written to disk before you reset or turn off the Cache Engine. Synchronization can also be done with the cache sync command.
Console# cfs sync c0t0d0s3
show cfs
cache clear
clear cache
To check whether superuser accounts are password-protected, use the check EXEC command.
check superuser passwords
superuser | Keyword. |
passwords | Keyword. |
By default, superuser accounts are not password-protected.
This command displays 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, transaction logs, or WCCP settings, use the clear EXEC command.
clear {cache [force] | dns-cache | interface serial number | logging
cache | Clears the HTTP object cache. |
force | Forcefully deletes all cached objects. |
dns-cache | DNS clear commands. |
interface | Clears the hardware interface. |
serial | Serial device. |
number | Serial interface number (for example, 0). |
logging | Clears syslog messages saved in disk file. |
statistics | Clears statistics. |
all | Clears all statistics. |
dns-cache | Clears DNS cache statistics. |
history | Clears the statistics history. |
http | Clears HTTP statistics. |
all | Clears all HTTP statistics. |
errors | Clears HTTP error statistics. |
ims | Clears HTTP IMS statistics. |
object | Clears HTTP object statistics. |
requests | Clears HTTP requests statistics. |
response | Clears HTTP response statistics. |
savings | Clears HTTP savings statistics. |
transaction-logs | Clears transaction-log export statistics. |
The clear cache command removes all cached contents from the currently mounted cfs volumes. Objects being read or written are removed when they cease being "busy." The equivalent to this command is the cache clear or cfs clear command.
|
Caution This command is irreversible and all cached content will be erased. |
The clear cache force command deletes all objects, whether busy or not, and may generate broken GIF/HTML messages for objects that were being read from the disk when the command was executed. If an object is being written to the Cache Engine disk when a clear cache force command is executed, the application stops caching that object but still delivers the object from the web server to the client.
The clear interface command clears the statistics presented by the
show interfaces 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.
Console# clear cache
cache clear
cfs clear
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 Universal Coordinated 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, 2000). |
If you have an outside source on your network that provides time services (such as a Network Time Protocol [NTP] server), you do not need to set the system clock manually. When setting the clock, enter the local time. The Cache Engine calculates UTC based on the time zone set by the clock timezone global configuration mode.
Two clocks exist in the system: the software clock and the hardware clock. The software uses the software clock. The hardware clock is used only at bootup to initialize the software clock.
The set keyword sets the software clock.
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 bootup is the NTP time or an obviously invalid time.
Console# clock set 13:32:00 01 February 2000
clock timezone
show clock detail
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, Ctrl-Z, or exit commands.
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 | startup-config filename} | flash {disk imagename} | running-config {disk filename | startup-config | tftp}
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 the configuration to NVRAM memory. This command is equivalent to the write command.
The copy flash disk imagename command will copy the image from Flash memory to the disk.
The copy disk flash imagename command will copy the image from the disk to Flash memory.
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 newfilename
oldfilename | 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 | http httpsubcommands debugsubcommands
all | Enables all debugging. |
cron | Cron. |
http | HTTP debug commands. |
icp | Internet Cache Protocol debug commands. |
inetd | INETD daemon. |
logging | LOG debug commands. |
ntp | Sets the debug level. |
radius | Remote Authentication Dial-in User Service (RADIUS) debug commands. |
rcpd | RCPD. |
snmp | SNMP debug commands. |
stats | Statistics debug commands. |
tftp-server | TFTP server. |
translog | Transaction log debug commands. |
url-filtering | URL filtering debug commands. |
wccp | WCCP information. |
packets | WCCP packet-related information. |
wi | Web interface debug commands. |
debuglevel | NTP debug level (0 to 100). |
debugsubcommands | |
all | Enables error, procedure, and trace debug |
error | Error debug. |
packet | Debugs URL filtering packets (appears only with |
proc | Procedure debug. |
trace | Trace debug. |
httpsubcommands | |
all | Enables debug for all HTTP subcommands. |
cache | HTTP cache debug. |
header | HTTP header debug. |
hit | HTTP hit debug. |
miss | HTTP miss debug. |
proxy | HTTP proxy debug. |
server | HTTP server debug. |
icpsubcommands |
|
all | Enables debug for all ICP subcommands. |
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. |
ICP print module debug. | |
server | ICP server module debug. |
utils | ICP utils module debug. |
loggingsubcommands | |
all | Logging all debug. |
events | Logging events debug. |
url-track | Logging URL-tracking debug. |
radiussubcommands | |
all | Error, procedure, trace. |
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 if-modified-since (IMS) module debug. |
log | SNMP log module debug. |
main | SNMP main module debug. |
parse | SNMP parse module debug. |
perf | SNMP performance module debug. |
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. |
archive | Transaction log archive. |
command | Transaction log command debugging. |
daemon | Transaction log daemon debugging. |
export | Transaction log FTP-export functionality. |
file-manager | Transaction log file manager debugging. |
logging | Transaction log entry generation. |
off | Disables transaction log subcommand. |
on | Enables transaction log subcommand. |
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. |
cache-on-abort | Web interface cache-on-abort module debug. |
clustering | Web interface clustering module debug. |
custom-web-cache | Web interface custom web cache 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 reverse proxy 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.
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 files that it contains, use the deltree EXEC command.
deltree directory
directory | Name of the directory tree to delete. |
Use this command to remove a directory and all files within the directory from the Cache Engine (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
4 DIR(S), 1 FILE(S) 11192642 bytes
2125889536 bytes AVAILABLE ON VOLUME /c0t0d0s1
lls
ls
To turn off privileged EXEC commands, use the disable EXEC 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 disks, use the disk EXEC command.
disk {erase-all-partitions devname | manufacture devname | partition devname | prepare devname}
erase-all-partitions | Disk initialization procedure. Erases all partitions |
manufacture | Reformats all partitions and volumes on a disk. |
partition | Partitions the hard disk. |
prepare | Partitions and formats volumes on a hard disk. |
devname | Device name. |
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 automates the preparation of a disk. This command partitions the disk and then formats and mounts all the partitions.
The disk manufacture command initializes a disk for use by the Cache Engine, and must be run on each disk before that disk is used by the Cache Engine for the first time. The disk manufacture command needs to be executed only once for each disk.
|
Note The disk manufacture command is executed on each internal Cache Engine disk by Cisco Systems prior to shipping. |
The disk manufacture command erases the master boot record (sector 0) of the disk and sets up the disk to have partitions for the various file systems (that is, dosfs, cfs, bfs). It also formats and mounts the appropriate file system on the volumes.
The disk erase-all-partitions command unmounts all the currently mounted file systems on the specified device (disk) and erases all the partitions from the master boot record (sector 0).
To create only a DOS partition on the first disk, enter the following commands:
Console# disk erase-all-partitions
Console# disk partition boot
show disk-partitions
show disks
Use the dnslookup EXEC command to resolve a host or domain name to an IP address.
dnslookup {host | domain-name}
host | Name of host on network. |
domain_name | Domain name. |
Console# dnslookup myhost
official hostname: myhost.cisco.com
address: 172.41.69.11
Console#dnslookup cisco.com
official hostname: cisco.com
address: 198.133.219.25
Console#dnslookup 41.69.11
official hostname: 41.69.11
address: 41.69.0.11
To configure the DOS file system, use the dosfs EXEC command.
dosfs {check volname [force | verbose [force]] | format volname | label volname vol-label | mount volname {rdonly | rdwr} | repair {automatic | interactive} volname [force | verbose [force]] | sync syncdevice | unmount volname}
check | Checks DOS file system. |
volname | Volume name. |
force | (Optional.) Forces a check or repair. |
format | Erases and formats a file system on a disk device. |
label | Sets a device volume label. |
vol-label | Label of volume. |
mount | Mounts a disk or volume file system. |
rdonly | (Optional.) Mounts volume as read-only. |
rdwr | (Optional.) Mounts volume as read-write. |
repair | Checks and repairs a uvfat/DOS file system. |
automatic | Automatic (not interactive) repair. |
interactive | Starts a user-interactive repair. |
verbose | (Optional.) Prints extra messages to screen. |
sync | Synchronizes a disk device. |
syncdevice | Absolute device name. |
unmount | Unmounts a disk or volume file system. |
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.
The dosfs format command formats the dosfs partition to prepare it for a dosfs mount.
The dosfs mount command creates and maps data structures that map to the physical dosf partition on the disk.
The dosfs unmount command frees the in-memory data structures that map to the physical dosfs partition on the disk.
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 paxfilename
paxfilename Name of the .pax file you want to install.
Install and run the .pax file from the /local directory only. When the install command is executed, the .pax file is expanded. The expanded files overwrite the existing files in the Cache Engine. The newly installed version takes effect after the system image is 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 directory
directory Name of the directory 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 filename
filename 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 | http httpsubcommands debugsubcommands | icp icpsubcommands debugsubcommands | inetd | logging loggingsubcommands | ntp debuglevel | radius radiussubcommands debugsubcommands | rcpd | snmp snmpsubcommands debugsubcommands | stats statssubcommands | tftp-server | translog translogsubcommands {off | on} | url-filtering url-filteringsubcommands | wccp packets | 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 off 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 a Network Time Protocol (NTP) server, use the ntpdate EXEC command.
ntpdate {hostname | ip-address}
hostname NTP host name. ip-address NTP server IP address.
Use NTP 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 you issue 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 sourcefile destinationfile
sourcefile Source file or path name of the file you want to rename. destinationfile Destination file or path name of the new file.
Use this command to rename any file within the Cache Engine.
Console# rename ce25.pax ce6399.pax
cpfile
To delete a directory, use the rmdir EXEC command.
rmdir directory
directory Name of the directory you want to delete.
Use this command to remove any directory from the Cache Engine file system. The rmdir command only removes empty directories.
Console# rmdir /local/oldpaxfiles
lls
ls
mkdir
Use the show command to display configuration, status, and statistics. See the "Show Commands (EXEC Commands)" section for a complete description of the show EXEC command.
The tclsh command is for Cisco Systems internal use only.
To display the current terminal commands, use the terminal EXEC command.
terminal monitor
monitor 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 filename
filename 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 or 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 | http httpsubcommands debugsubcommands | icp icpsubcommands debugsubcommands | inetd | logging loggingsubcommands | ntp debuglevel | radius radiussubcommands debugsubcommands | rcpd | snmp snmpsubcommands debugsubcommands | stats statssubcommands | tftp-server | translog translogsubcommands {off | on} | url-filtering url-filteringsubcommands | wccp packets | 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. 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.
The configuration is written to NVRAM by default.
Use this command to either save running configurations to NVRAM or to erase memory configurations. Following a write erase command, no configuration is held in memory, and a prompt for configuration specifics occurs after you reboot the 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 enable transparent error handling and dynamic authentication bypass, and to configure static bypass lists, use the bypass command. To disable the bypass feature, use the no form of the command.
bypass {auth-traffic enable | load {enable | in-interval seconds | out-interval seconds | time-interval minutes} | static {clientipaddress {clientipaddress | any-server} | any-client serveripaddress} | timer minutes}
auth-traffic | Authenticated traffic bypass configuration. |
load | Load bypass configuration. |
enable | Enable load bypass. |
in-interval | Time interval between buckets coming back. |
out-interval | Time interval between bypassing buckets. |
time-interval | Time that a bucket is bypassed. |
seconds | Time in seconds (4-600). |
minutes | Time in minutes (1-1440). |
static | Adds a static entry to the bypass list. |
any-server | Bypasses HTTP traffic from a specified client to any webserver. |
any-client | Bypasses HTTP traffic from any client destined to a particular server. |
clientipaddress | IP address of the web client to be bypassed. |
serveripaddress | IP address of the web server to be bypassed. |
timer | Sets timer for authentication bypass, in minutes. |
Bypass features are available only with WCCP Version 2. The Cache Engine can only bypass WCCP-redirected traffic, not proxy-style requests.
Some web sites, because of IP authentication, do not allow the Cache Engine to connect directly on behalf of the client. In order to avoid a disruption of service, the Cache Engine can use authentication bypass to generate a dynamic access list for these client-server pairs. Authentication bypass triggers are also propagated upstream and downstream in the case of hierarchical caching. When a client/server pair goes into authentication bypass, it is bypassed for a configurable amount of time, set by the timer option (10 minutes by default).
If a Cache Engine becomes overwhelmed with traffic, it can use the load bypass feature to reroute the overload traffic.
When the Cache Engine is overloaded and load bypass is enabled, the Cache Engine bypasses a bucket. If the load remains too high, another bucket is bypassed, and so on until the Cache Engine can handle the load. The time interval between one bucket being bypassed and the next, is set by the out-interval option. The default is 4 seconds.
When the first bucket bypass occurs, a time interval must elapse before the Cache Engine begins to again service the bypassed buckets. The duration of this interval is set by the time-interval option. The default is 10 minutes.
When the Cache Engine begins to again service the bypassed traffic, it begins with a single bypassed bucket. If the load is servicable, it picks up another bypassed bucket and so on. The time interval between picking up one bucket and the next is set by the in-interval option. The default is 60 seconds.
The bypass static command permits traffic from specified sources to bypass the Cache Engine. The type of traffic sources are as follows:
Wildcards in either the source or the destination field are not supported.
To clear all static configuration lists, use the no form of the command.
cache-engine(config)# bypass static 10.1.17.1 172.10.7.52
cache-engine(config)# bypass static any-client 172.10.7.52
cache-engine(config)# bypass static 10.1.17.1 any-server
A static list of source and destination addresses helps to isolate instances of problem-causing clients and servers.
console# show bypass list
Total number of entries in the bypass list = 5
Client IP Server IP Reason
10.1.17.1 15.1.10.6 Error Handling
10.1.24.1 128.10.2.4 Auth Traffic
10.1.24.2 128.10.2.4 Static Config
10.2.4.5 any-server Static Config
any-client 178.10.45.6 Static Config
cache-engine# show bypass summary
Cache Engine will bypass authenticated HTTP traffic.
Cache Engine will bypass HTTP traffic if it is overloaded.
Total number of entries in the bypass list = 5
Total number of HTTP connections bypassed = 20
show bypass
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 | Hours offset from Coordinated Universal Time (UTC). |
minutes | (Optional.) Minutes offset from UTC. |
To set and display the local and UTC current time of day without an NTP server, use the clock timezone command together with the clock set command.
The clock timezone parameter specify the difference between UTC and local time which is set with the clock set command. The UTC and local time are displayed with the show clock detail EXEC command.
The following example specifies the local time zone as Pacific Standard Time and offsets 8 hours behind UTC:
Console(config)# clock timezone PST -8
Console(config)# no clock timezone
clock
show clock detail
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 size maxsize
size Sets the DNS cache size. maxsize Maximum number of cache records (4096-65536).
Cache size refers to the maximum number of DNS entries to be stored at one time. Domain name resolution requires that at least one DNS name server be configured with the ip name-server command. The DNS cache goes online when the
ip name-server command is configured, and goes offline when the last IP name-server configuration is deleted with the no ip name-server ip-address command.
Console(config)# dns-cache enable
Console(config)# dns-cache size 512
Console(config)# no dns-cache enable
Console(config)# no dns-cache size
ip name-server
clear dns-cache
show dns-cache
dnslookup
show statistics dns-cache
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. To save new configurations to NVRAM, use the write command.
The Ctrl-Z command also exits global configuration mode.
Console(config)# end
Console#
exit
Ctrl-Z
Use the error-handling command to set error-handling options.
error-handling {reset-connection | send-cache-error | transparent}
reset-connection | Resets TCP connection without specifying any error. |
send-cache-error | Sends Cache Engine error. |
transparent | Makes the Cache Engine transparent to the client. |
With the transparent option enabled, end users can receive browser-generated messages rather than a Cache Engine-generated HTML page for errors that the Cache Engine encounters while processing a client request or response. Thus, the Cache Engine remains transparent (invisible) to the end user.
Transparent error reporting is implemented as follows:
console# error-handling transparent
The exception debug command is for Cisco Systems internal purposes only.
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 timeout
timeout 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. The default is 150 minutes.
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 newgroupname | delete {gid group-id | groupname groupname} | modify {gid group-id newgroupname | groupname groupname newgroupname}}
add Adds a group name. delete Deletes a group name or ID. modify Modifies a group name or group ID. gid Deletes or modifies a group by the group ID. newgroupname 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
show group
show groups
show user
show users
user
users
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 name
name 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 the Cache Engine model number (CE505, CE550, or CE570).
Use this command to configure the host name for the Cache Engine. The host name is used for the command 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} | append {via-header | x-forwarded-for-header} | authenticate-strip-ntlm | cache-authenticated | cache-cookies | cache-miss {retrieve | revalidate} | cache-on-abort {enable | max maxthresh | min minthresh | percent percenthresh} | cluster max-delay delayseconds misses totalmisses | max-ttl {days text textdays binary bindays | hours text texthours binary binhours | minutes text textminutes binary binminutes | seconds text textseconds binary binseconds} | object {max-size maxsize | url-validation enable} | persistent-connections {enable | timeout secs max-idle connections} | proxy {incoming port | outgoing {exclude {enable | list domain} | host {hostname | ip-address} port} | reval-each-request {all | none | text} | serve-ims text textpercentage binary binpercentage}
age-multiplier | HTTP/1.0 caching heuristic modifiers. |
text | Heuristic modifier for text object. |
texttime | Expiration time of text objects as a percentage of their age (0-100). |
binary | Heuristic modifier for binary object. |
bintime | Expiration time of binary objects as a percentage of their age (0-100). |
append | Configures HTTP headers to be included by |
via-header | Includes "Via" header in responses and replies. |
x-forwarded-for-header | Notifies web server of client's IP address through "X-Forwarded-For" header. |
authenticate-strip-ntlm | Strips NT LAN Manager (NTLM) |
cache-authenticated | Caches and revalidates authenticated web objects. |
cache-cookies | Caches web objects with associated cookies. |
cache-miss | Configuration for the handling of "no-cache" requests. |
retrieve | Retrieves the object from the point of origin. |
revalidate | Revalidates the object with the origin before serving. |
cache-on-abort | Sets cache-on-abort configuration options. |
enable | Enables cache-on-abort feature. |
max | Sets maximum threshold. |
maxthresh | Value in kilobytes of maximum threshold (1-99999). Default is 256. |
min | Sets minimum threshold. |
minthresh | Value in kilobytes of minimum threshold (1-99999). Default is 32. |
percent | Sets percent threshold. |
percenthresh | Percentage value (1-99). Default is 80 percent. |
cluster | Sets cache cluster configuration options. |
max-delay | Maximum delay to wait for a response. |
delayseconds | Maximum delay in seconds (0-10). |
misses | Duration of healing mode (misses). |
totalmisses | Total number of misses before healing is disabled (0-999). |
max-ttl | Maximum time to live for objects in the cache. |
text | Sets maximum time to live for text objects. |
binary | Sets maximum time to live for binary objects. |
days | Sets maximum time to live for units in days. |
hours | Sets maximum time to live for units in hours. |
minutes | Sets maximum time to live for units in minutes. |
seconds | Sets maximum time to live for units in seconds. |
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. |
object | Sets URL validation and maximum size of |
max-size | Sets the maximum size of a cacheable object. |
maxsize | Maximum size of a cacheable object in kilobytes (1-1048576). |
url-validation enable | Enables each HTTP validation request. |
persistent-connections | Persistent connections configuration options. |
enable | Enables persistent connections. |
timeout secs | Persistent connections timeout in seconds (1-86400). |
max-idle | Sets maximum number of idle persistent connections. |
connections | Maximum number of idle persistent connections (1-4096). |
proxy | Configuration parameters for proxy mode. |
incoming | Configuration for incoming proxy-mode requests. |
port | Port on which to listen for incoming HTTP proxy requests (1-65535). Default is port 8080. |
outgoing | Configuration to direct outgoing request to another proxy server. |
exclude | Excludes local domains. |
enable | Enables exclusion of local domains for |
list | Lists local domains to exclude. |
domain | Local domain name. |
host | Specifies hostname of outgoing proxy. |
hostname | Host name of outgoing proxy. |
ip-address | IP address of outgoing proxy. |
port | Port number of outgoing proxy (1-65535). |
reval-each-request | Configuration of revalidation for every request. |
all | Revalidates all objects on every request. |
none | Does not revalidate for each request. |
text | Revalidates text objects on every request. |
serve-ims | Configuration for the handling of if-modified-since (IMS) requests for text objects. |
text | Modifies handling of if-modified-since requests for text objects. |
binary | Modifies handling of if-modified-since requests for binary objects. |
textpercentage | Percentage of age to serve the text object without revalidation (0-100). |
binpercentage | Percentage of age to serve the binary object without revalidation (0-100). |
Use these commands to configure specific parameters for caching HTTP objects.
|
Note Text objects refer to HTML pages. Binary objects refer to all other web objects (for example, GIFs or JPEGs). |
If a cached object's HTTP header does not specify an expiration time, the age-multiplier and max-ttl commands provide a means for the Cache Engine to age cached objects. The Cache Engine's algorithm to calculate an object's cache expiration date is as follows:
Expiration date = (Today's date - Object's last modified date) * Freshness factor
The freshness factor is computed from the text and binary percentage parameters of the age-multiplier command. Valid age-multiplier values are 0 to 100 percent of the object's age. Default values are 30% for text and 60% for binary objects. After the expiration date, the object is considered stale and subsequent requests result in a fresh retrieval by the Cache Engine.
The max-ttl command sets the upper limit on estimated expiration dates. An explicit expiration date in the HTTP header 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 than 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 this command is enabled, the Cache Engine will not serve authenticated objects without first revalidating the authentication header attached to the cached object.
The reval-each-request command enables the Cache Engine to revalidate all objects requested from the cache, text objects only, or none at all.
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.
Use the object max-size command to specify the maximum size in kilobytes of a cacheable object. The default is no maximum size for a cacheable object. The no form of the command resets the default value.
The cluster command modifies the healing mode parameters. A cluster refers to a group of two or more Cache Engines 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 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 configure the Cache Engine to direct all HTTP miss traffic to a parent cache (without using ICP or WCCP), 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.
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 timeout option. To set the number of seconds that the Cache Engine should allow an idle persistent connection to remain open, use the max-idle option.
The http object url-validation command has a dependency with the
ip name-server CLI command. When the ip name-server command is not configured (for example, during transparent proxy), http object url-validation is dynamically turned off. When the ip name-server command is configured,
http object url-validation is turned on automatically if and only if it
was enabled.
|
Caution URL validation is on by default. Cisco Systems strongly recommends that you keep URL validation enabled, because disabling URL validation might make the Cache Engine vulnerable to corruption from the HTTP objects in the cache. |
Use the exclude list option in the http proxy outgoing global configuration command to specify domains for which the Cache Engine will not use an upstream proxy.
Only one domain can be specified per command line. To specify multiple domains for proxy exclusion, iteratively execute the command for each domain. In the following example, cisco.com and the address 10.9.8.7 are proxy-excluded.
console(config)# http proxy outgoing exclude list cisco.com
console(config)# http proxy outgoing exclude list 10.9.8.7
The maximum number of no-proxy domains is 64. The Cache Engine will not use an upstream proxy for any domain that ends with a listed domain name. For example, if you specify cisco.com, the configured outgoing proxy server will be bypassed each time the Cache Engine tries to retrieve a web page from videos.cisco.com, or personals.cisco.com.
For IP addresses, enter the full IP address or use the asterisk "*" as a wildcard for IP address fields as follows:
172.16.1.*
172.16.*.*
172.*.*.*
The syntax—172.16.*.*— indicates that all requests to the domain host of 172.16.xxx.xxx will be excluded. Wildcard syntax does not support "0" or "?".
The following forms of wildcard specification are not supported:
172.*.10.2
172.31.1*.8
The cache-on-abort option provides user-defined thresholds to determine whether or not the Cache Engine will complete the download of an object when the client has aborted the request. When the download of an object aborts before it is completed, the object is not stored on the Cache Engine or counted in the hit-rate statistics. Client abort processing occurs when a client of the Cache Engine aborts the download of a cacheable object before the download is complete. Typically a client aborts a download by clicking the Stop icon on the browser, or by closing the browser during a download.
If the cache-on-abort option is enabled and all cache-on-abort thresholds are disabled, then the Cache Engine always aborts downloading an object to the cache. If the Cache Engine determines that there is another client currently requesting the same object, downloading is not aborted. The Cache Engine only applies those thresholds that have been enabled.
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
console(config)# http cache-on-abort enable
console(config)# no http cache-on-abort
console(config)# http cache-on-abort min 16
console(config)# no http cache-on-abort min
show http
To configure the Internet Cache 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 {parent | sibling} icp-port icpport http-port httpport | enable | exclude line max-fail retries | max-wait timeout | modify-remote-server hostname {http-port port | icp-port port | parent | restrict line | sibling} | server {enable | port port | remote-client hostname {fetch | no-fetch}}
client | ICP client functionality. |
add-remote-server | Adds an ICP client remote server. |
hostname | Host name or IP address. |
parent | ICP server acts like a parent. |
sibling | ICP server acts like a sibling. |
icp-port | ICP port. |
icpport | Sends remote requests to this ICP port number (0-65,535). |
http-port | HTTP port. |
httpport | Sends HTTP requests to this port number (0-65,535). |
enable | Enables the ICP client. |
exclude | ICP client local domain. |
line | Space-delimited local domain list. |
max-fail | Maximum number of retries allowed. |
retries | Number of retries (0-100). |
max-wait | Maximum wait for ICP responses before timeout occurs. |
timeout | Timeout period for ICP responses in seconds (0-30). |
modify-remote-server | Modifies the ICP client remote server parameters. |
hostname | Host name or IP address. |
http-port | HTTP port. |
port | Sends HTTP requests to this port number (0-65,535). |
icp-port | ICP port. |
port | Sends ICP requests to this port number (0-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 that listens for ICP requests. |
port | Sends ICP requests to this port number (0-65,535). |
remote-client | ICP server remote client. |
hostname | Host name or IP address. |
fetch | ICP remote client will fetch cache miss. |
no-fetch | ICP remote client will not fetch cache 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 or clients within the ICP environment to ensure proper service. You can 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}
enable Enables TCP/IP service. service Name of the service to be enabled: echo, discard, chargen, TFP, RCP, Telnet, and TFTP. tasks Maximum number of concurrent tasks.
echo | Disabled. |
discard | Disabled. |
chargen | Disabled. |
ftp | Five sessions. |
rcp | Five sessions. |
tftp | Five sessions. |
telnet | Three 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 number
ethernet The Ethernet IEEE 802.3 interface to configure. number 0 or 1. The Ethernet interface number.
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 manually setting the speed or duplex mode.
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
default-gateway | Specifies default gateway (if not routing IP). |
ipaddress | IP address of default gateway. |
domain-name | Specifies domain name. |
domainname | Domain name. |
name-server | Specifies address of name server. |
ipaddress | IP address of name server. |
route | Net route. |
destaddrs | Destination route address. |
netmask | Netmask. |
gateway | Gateway address. |
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.
The Cache Engine uses the default gateway to route IP packets when there is no specific route found to the destination.
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.
The Cache Engine appends the configured domain name to any IP host name that does not contain a domain name. The appended name is resolved by the DNS server and then added to the host table. The Cache Engine must have at least one domain name server specified for the host name resolution to work correctly. Use the ip name-server hostname command to specify domain name servers.
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.
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 can configure up to eight servers.
To configure static IP routing, use the ip route global configuration command. To disable an IP routing, use the no form of this command.
Use the ip route command to add a specific static route for a network host. Any IP packet designated to the specified host uses the configured route.
Console(config)# ip default-gateway 192.168.7.18
Console(config)# no ip default-gateway
Console(config)# ip route 172.16.227.128 ffffff80 172.16.227.250
Console(config)# no ip route 172.16.227.128 ffffff80 172.16.227.250
Console(config)# ip domain-name cisco.com
Console(config)# no ip domain-name
Console(config)# ip name-server 10.11.12.13
Console(config)# no ip name-server 10.11.12.14
show ip route
To configure system logging, use the logging global configuration command. To disable logging functions, use the no form of this command.
logging {hostname | ip-address | console loglevels | disk filename loglevels | event-export events loglevels facility | facility facility | on | recycle size | trap loglevels}
hostname | Syslog server host name. |
ip-address | IP address. |
console | Sets console logging level. |
loglevels | Use one of these keywords: |
| Immediate action needed. |
| Immediate action needed. |
| Debugging messages. |
| System is unusable. |
| Error conditions. |
| Informational messages. |
| Normal but significant conditions. |
| Warning conditions. |
disk | Stores log in a file. |
filename | Name of the log file. |
event-export | Syslog event export configuration. |
events | Use one of these keywords: |
| Exports critical events. |
| Exports notice events. |
| Tracks URLs to syslog. |
| Exports warning events. |
facility | Use one of these keywords: |
| Cron. |
| System daemons. |
| Kernel. |
| Line printer system. |
| Local use. |
| Local use. |
| Local use. |
| Local use. |
| Local use. |
| Local use. |
| Local use. |
| Local use. |
USENET news. | |
| Mail system. |
| Authorization system. |
| Syslog itself. |
| User process. |
| UUCP system. |
facility | Facility parameter for syslog messages. |
on | Enables logging to all destinations. |
recycle | Overwrites syslog.txt when it surpasses the |
size | Size of syslog file in bytes (1 to 50,000,000). |
trap | Sets syslog server logging level. |
These are the defaults when no other options are configured by the user:
Logging | On |
Priority of message for console | Warning |
Priority of message for file | Debugging |
Log file | /local/var/log/syslog.txt |
Log file recycle size | 5,000,000 bytes |
Use this command to set specific parameters of the system log file. System logging is always enabled internally. The system log file is located on the dosfs partition as /local/var/log/syslog.txt. To configure the Cache Engine to send varying levels of event messages to an external syslog host, use the logging hostname command. Logging can be configured to send various levels of messages to the console using the logging console loglevels 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 command
command 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 configuration. 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.
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 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 Remote Authentication Dial-in User Services (RADIUS) parameters, use the radius global configuration command.To disable RADIUS authentication parameters, use the no form of this command.
radius {auth-timeout value | exclude {enable | list domainlist} | host {hostname | hostipaddr} [auth-port port] | key keyword | retransmit retries | timeout seconds}
auth-timeout | Configures RADIUS authentication timeout. |
value | Auth Timeout value in minutes (1-1440). Default is 20. |
exclude | Excludes local domains (selective authentication). |
enable | Enables selective authentication feature. |
list | Specifies domains to be excluded from RADIUS authentication. |
domainlist | Domain name or IP address. |
host | Specifies a RADIUS server. |
hostname | Host name of RADIUS server. |
hostipaddr | IP address of RADIUS server. |
auth-port | Specifies UDP port for RADIUS authentication server. |
port | Port number (1-65535). |
key | Encryption key shared with the RADIUS servers. |
keyword | Text of shared key (15 characters maximum). |
retransmit | Specifies the number of transmission attempts to an active server. |
retries | Number of transmission attempts for a transaction (1-100). Default is 3. |
timeout | Time to wait for a RADIUS server to reply. |
seconds | Wait time in seconds (1-1000). Default is 5 seconds. |
RADIUS authentication clients reside on Cisco Cache Engines. When enabled, these clients send authentication requests to a central RADIUS server, which contains all user authentication and network service access information. Selective RADIUS authentication allows users to access intranet servers without requiring authentication, and can limit RADIUS authentication to those users that access external web servers.
Users can specify an exclusion list of IP addresses or domain names (in the form mydomain.com) for which the Cache Engine will not perform RADIUS authentication. The maximum number of excluded domains is 64. The selective RADIUS authentication feature can be disabled without deleting the domains.
Console(config)# radius server 172.16.90.121 70 password enable
Console(config)# no radius server 172.16.90.121 70 password enable
Console# show radius
Radius Authentication is on
Timeout = 5 seconds
AuthTimeout = 20 minutes
Retransmit = 3
Key = ****
Servers
-------
IP 1.1.1.1, Port = 1645 State: ENABLED
Selective Authentication is off.
Console(config)# radius exclude enable
Console# show radius
Radius Authentication is on
Timeout = 5 seconds
AuthTimeout = 20 minutes
Retransmit = 3
Key = ****
Servers
-------
IP 1.1.1.1, Port = 1645 State: ENABLED
Selective Authentication is on.
Local domains to be excluded from Radius Authentication: None.
CE(config)# radius exclude list cisco.com
CE(config)# radius exclude list 171.69.236.202
CE# show radius
Radius Authentication is on
Timeout = 5 seconds
AuthTimeout = 20 minutes
Retransmit = 3
Key = Vash
Servers
-------
IP 1.1.1.1, Port = 1645 State: ENABLED
Selective Authentication is on.
Local domains to be excluded from Radius Authentication:
cisco.com
176.63.236.202
Console(config)# no radius exclude list cisco.com
Console(config)# no radius exclude 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 string
string | 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 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 SNMP without removing a previously defined community string:
Console(config)# no snmp-server
show snmp
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 line
contact | Text for MIB object sysContact. |
line | Identification of the contact person for this managed node. |
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 traps, 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.31.2.160 using the community string public:
Console(config)# snmp-server enable traps
Console(config)# snmp-server host 172.31.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} communitystring
hostname | Host name of SNMP trap host. |
ip-address | IP address of SNMP trap host. |
communitystring | 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 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.16.2.160. The community string is comaccess.
Console(config)# snmp-server enable traps
Console(config)# snmp-server host 172.16.2.160 comaccess
Console(config)# no snmp-server host 172.16.2.160
snmp-server enable traps
snmp-server community
To set the SNMP 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 line
line | 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 maxsegsize | 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-mss maxsegsize | server-receive-buffer kbytes | server-rw-timeout seconds | server-satellite | server-send-buffer kbytes}
client-mss | Sets client TCP maximum segment size. |
maxsegsize | Maximum segment size in bytes (512-1460). |
client-receive-buffer | Sets client receive buffer size. |
kbytes | Receive buffer size in kilobytes (1-1024). |
client-rw-timeout | Sets client connection's read/write timeout. |
seconds | Timeout in seconds (1-3600). |
client-satellite | Client TCP compliance to RFC 1323 standard. |
client-send-buffer | Client connection's send buffer size. |
kbytes | Send buffer size in kilobytes (8-1024). |
cwnd-base | Sets TCP CWnd base factor. |
factor | Factor value (1-16). |
init-ssthresh | Sets TCP initial smooth threshold. |
value | Threshold value (2920-1073741824). |
keepalive-probe-cnt | Sets TCP keepalive probe counts. |
count | Number of probe counts (1-10). |
keepalive-probe-interval | TCP keepalive probe interval. |
seconds | Keepalive probe interval in seconds (1-300). |
keepalive-timeout | TCP keepalive timeout. |
seconds | Keepalive timeout in seconds (1 to 3600). |
listen-queue | Maximum size of TCP listen queue. |
length | Listen queue length in kilobytes (1-1000). |
server-receive-buffer | Server connection receive buffer size. |
kbytes | Receive buffer size in kilobytes (1-1024). |
server-rw-timeout | Server connection read/write timeout. |
seconds | Read/write timeout in seconds (1-3600). |
server-satellite | Server TCP compliance to RFC 1323 standard. |
server-send-buffer | Server connection send buffer size. |
kbytes | Buffer size in kilobytes (1-1024). |
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 is adequate. If you modify the listen-queue settings, reboot the Cache Engine to effect the changes.
Console(config)# tcp client-receive-buffer 100
Console(config)# no tcp client-receive-buffer 100
show tcp
To set the number of lines displayed in the console window, use the terminal global configuration command. To disable this function, use the no form of the command.
terminal length lines
length | Sets the number of lines displayed by the terminal screen. |
lines | Number of lines on the screen (0 to 512). Default is 24 lines. Enter 0 for no 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 Spacebar. 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 {archive {files maxnumfiles | interval seconds} | enable | export {enable | ftp-server {hostname | servipaddrs} login passw directory} | interval minutes} | sanitize
archive | Configures archive parameters. |
files | Saves archive log files to disk. |
maxnumfiles | Maximum number of archive files to save on disk (1-10). The default is 1. |
interval | Determines how frequently the archive file is to be saved. |
seconds | Time interval in seconds. The default is 86400 seconds (120-86400). |
enable | Enables transaction log feature. |
export | Configures file export parameters. |
enable | Enables the saving of log files according to interval. |
ftp-server | Sets FTP server to receive exported archived files. |
hostname | Host name of target FTP server. |
servipaddrs | IP address of target FTP server. |
login | User login to target FTP server. |
passw | User password to target FTP server. |
directory | Target directory for exported files on FTP server. |
interval | Files are transferred to FTP server after this interval. |
minutes | Export time interval in minutes (1-10,080). The default is 60 minutes. |
sanitize | Writes user IP addresses in log file as 0.0.0.0. |
Enable transaction log recording with the transaction-logs enable command. When enabled, daemons create a working.log file in the /local/var/log/translog/ dosfs directory.
After an interval specified by the transaction-logs archive interval command, the working.log file is renamed and copied as an archive file to the dosfs directory with the path /local/var/log/translog/archive/data. A new working.log file is then created and the process repeats. The Cache Engine default archive interval is 86,400 seconds, or one day.
Use the transaction-logs archive files command to specify how many archive files to store on disk. When the maximum number of files has been created, the next archive file overwrites the oldest stored file.
The transaction-logs export interval sets the interval in minutes after which the Cache Engine will FTP the archive file to a remote server. The export interval can be configured to be smaller than the archive interval to improve recovery time if the remote FTP server is unavailable after the archive interval.
If the transaction-logs export interval is configured to a larger value than the archive interval, the administrator must ensure that there are enough archive files.
The archive transaction log file is named as follows:
celog_10.1.118.5_19991228_235959.txt
Table A-1 describes the name elements.
celog_10.1.118.5 | IP address of the Cache Server creating the archive file. |
19991228 | Date archive file was created (yyyy/mm/dd). |
235959 | Time archive file was created (hh/mm/ss). |
10340 | Size of archive file in kilobytes. |
The transaction logs export feature does not create the legacy archive files named archive.log. Legacy archive files must be manually deleted or copied from the Cache Engine hard disk.
The transaction-logs export ftp-server option can support up to four FTP servers. To export transaction logs, you must first enable the feature and configure the export interval. The following information is required for each target server:
Use the no form of the transaction-logs export enable command to disable the entire transaction-logs feature while retaining the rest of the configuration.
When an FTP server returns a permanent error to the Cache Engine, the archive transaction logs are no longer exported to that server. You must reenter the Cache Engine transaction log export parameters to clear the error condition.
The show statistics transaction-logs command displays the current state of transaction log export readiness.
A permanent error (Permanent Negative Completion Reply, RFC 959) occurs when the FTP command to the server cannot be accepted, and the action did not take place. Permanent errors can be caused by invalid user logins, invalid user passwords, and attempts to access directories with insufficient permissions.
In the following example, an invalid user login parameter was included in the transaction-logs export ftp-server command. The show statistics transaction-logs command shows that the Cache Engine failed to export archive files.
console# show statistics transaction-logs
Server:176.79.23.12
Export stopped due to permanent error received from FTP.
Attempts:1
Successes:0
Open Failures:0
Put Failures:0
Other Transport Errors:
Authentication Failures:1
Permanent Directory Failures:0
Permanent Put Failures:0
Previous Permanent Ftp Errors:0
To restart the export of archive transaction logs, the transaction-logs export ftp-server parameters must be reentered:
console(config)# transaction-logs export ftp-server 10.1.1.1 goodlogin
pass /etc/webcache
Use the sanitized option to disguise the IP address and usernames of clients in the transaction log file. The default is not sanitized. A sanitized transaction log disguises the network identity of a client by changing the IP address in the transaction logs to 0.0.0.0. The no form disables the sanitize feature.
console(config)# transaction-logs export ftp-server 10.1.1.1
mylogin mypasswd /tmp/local/webcache
console(config)# transaction-logs export ftp-server myhostname
mylogin mypasswd /tmp/local/webcache
console(config)# no transaction-logs export ftp-server myhostname
console(config)# no transaction-logs export ftp-server 10.1.1.1
console(config)# no transaction-logs export enable
|
Note The default is export disabled; the interval default is 1 hour. There are no defaults for the FTP server configuration. |
console(config)# transaction-logs export ftp-server 10.1.1.1
mynewname mynewpass /tmp/local/webcache
console# show transaction-logging
Transaction Logs:
Logging is enabled
End user identity is visible.
Current Archive Interval: 86400 sec.
Maximum Number of Archived Files: 6
Exporting files to servers is enabled.
Current export retry interval: 100 minutes.
Working Log file - size: 8650
age: 4885
Archive Log file:
celog_10.1.118.5_19991228_235959.txt - size: 10340
File export feature is enabled
ftp-server username directory
1.1.1.1 mynewname /tmp/local/webcache
2.2.2.2 erasmus /tmp/translogfiles
|
Note For security reasons, passwords are never displayed. |
console# show statistics transaction-logs
Transaction Logs:
Logging is enabled.
End user identity is visible.
Current Archive Interval: 120 seconds.
Maximum Number of Archived Files: 10
Exporting files to servers is enabled.
Export retry interval:1 minutes.
Working Log file - size:0
age:45
No Archive Log file found
ftp-server username directory
152.59.21.110 zpajanos ~zp/201/translog/logfiles
152.59.33.33 zpajanos ~zp/outputfiles
1.1.1.1 my my
show transaction-logs
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 of trusted host. ip-address IP address of trusted host. 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. You must first enable this feature with the trusted-host domain-lookup command.
Console(config)# trusted-host domain-lookup
Console(config)# trusted-host 172.31.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 [custom-message] | good-sites-allow [custom-message] | websense {allowmode enable | server {hostname | ipaddrs} [port port] [timeout seconds]}}
bad-sites-block Blocks access to sites listed in badurl.lst file. custom-message Displays customized URL blocking message from block.html file. good-sites-allow Allows access only to sites listed in goodurl.lst file. websense Uses Websense Enterprise server to govern URL access. allowmode (Optional.) Allows HTTP traffic if Websense server does not respond. enable (Optional.) Enables allowmode. server Configures Websense server host name or IP address. hostname Host name of Websense server. ipaddrs IP address of Websense server. port (Optional.) Sets the Websense server port number. port (Optional.) Port on which to send the Websense requests (1-65535). Default is 15868. timeout (Optional.) Specifies the time to wait for a response from the Websense server. seconds (Optional.) Timeout value in seconds (1-120). Default is 20 seconds.
The Cache Engine can control client access to web sites as follows:
Only one form of URL filtering can be active at a time.
The url-filter bad-sites-block command causes the Cache Engine to block a client request for a URL if the URL is listed in an administrator-created plain text file named badurl.lst copied to the /local/etc dosfs directory of the Cache Engine.
The url-filter good-sites-allow command causes the Cache Engine to fulfill a client request only if the requested URL is listed in an administrator-created plain text file named goodurl.lst copied to the /local/etc dosfs directory of the Cache Engine.
The list of URLs in the goodurl.lst and badurl.lst text files must be written in the form www.domain.com and delimited with carriage returns.
Use the no form of the command to disable blocking or Websense permission requests (for example, no url-filter bad-sites-block).
When the Cache Engine blocks a URL, it returns a blocking message to the client. A customized message can be returned by including the custom-message option (for example, url-filter good-sites-allow custom-message).
The custom message must be an administrator-created HTML page named block.html copied to the /local/etc dosfs directory. Copy all embedded graphics associated with the custom message HTML page to the /local/lib/gui/pub directory and reference the image from the custom message HTML page with a fully qualified path name. If the custom-message option is enabled but the block.html file is not in the /local/etc directory, the Cache Engine returns a "file not found" message to the client upon blocking.
The following is an example of the block.html file:
<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>
 |
Tips You can cut and paste sample files from the .PDF or HTML versions of this user guide. |
To disable the custom-message option without disabling URL filtering,enter the URL filtering command without the custom-message option
(for example, url-filter good-sites-allow).
The Cache Engine can use a Websense Enterprise server as a filtering engine and enforce the filtering policy configured on the Websense server. Refer to the Websense documentation for further information on Websense filtering policies.
To enable Websense URL filtering on the Cache Engine, specify the Websense server IP address or hostname. The timeout option sets the maximum amount of time that the Cache Engine will wait for a Websense response. The timeout default is 20 seconds. The port option specifies the port number on which the server will intercept requests from the Cache Engine (the default port is 15868). Use the no url-filter websense server command to disable Websense URL filtering.
The url-filter websense allowmode enable command permits the Cache Engine to fulfill the client request after a Websense server timeout. Use the no form of the command to disable Websense allowmode.
The Websense Server returns its own blocking message.
|
Note To use Websense URL filtering with a cluster of Cache Engines, make sure to configure url-filter websense server on each Cache Engine in the cluster to ensure that all traffic is filtered. |
To block listed URLs and return a custom message, enter:
console# url-filter bad-sites-block custom-message
To turn off the customized URL blocking message but still block listed URLs, enter:
console# url-filter bad-sites-allow
To disable URL blocking, use the no form of this command.
Console(config)# no url-filter bad-sites-block
Console(config)# no url-filter good-sites-allow
To configure a Cache Engine to use Websense URL filtering with a 4-second timeout, enter:
console# url-filter websense server 172.16.11.22 timeout 4
show url-filter
show url-filter statistics websense
To configure user accounts on your Cache Engine, use the user global configuration command.
user {add | delete | modify}
add Creates a new user account on the Cache Engine. delete Removes the specified user account from Cache Engine. modify Changes the user information. username Cache Engine login name for the user. password See password options. capability (Optional.) See capability options. add-capability (Optional.) See capability options. uid Assigns a user ID. userid Range of administrator-assigned user ID numbers (2001-2147483647). capability (Optional.) Adds capability to a new user. Use with add keyword. add-capability (Optional.) Adds capability to an existing user. Use with modify keyword. See capability options. del-capability (Optional.) Deletes capability of an existing user. Use with modify keyword. See capability options.
Capability Options | |
admin-access | Grants all possible access to the Cache Engine. |
ftp-access | Grants FTP access to the Cache Engine. FTP access includes HTTP access. |
http-access | Grants HTTP access to the Cache Engine. |
telnet-access | Grants Telnet access to the Cache Engine. Telnet access includes FTP and HTTP access. |
Password Options | |
password | Sets a password for the specified user. |
0 | Specifies that a clear-text password will follow (default). |
1 | Specifies that a type 1 encrypted password will follow. |
password | Password for the specified user. For no password, omit this option. Password must be a string of 4 to 128 characters in length. Passwords of one to three characters are rejected. |
The default users are admin and anonymous.
The user command creates, modifies, and deletes Cache Engine user accounts. Up to 50 user accounts can be added to the Cache Engine. Only administrator access capability permits a user to write to the Cache Engine. The admin user account is included by default.
The user identification number (UID) 0 is reserved for the user "admin" and cannot be assigned to another user. The user ID numbers 2001 to 2147483647 can be assigned manually by the administrator. The Cache Engine assigns a UID number from 1 through 2000 if a UID is not assigned by the administrator.
In summary, ID numbers 1 to 2000 are assigned by the Cache Engine; 2001 to 2147483647 can be assigned by the administrator. User accounts with ID numbers 1 to 2147483647 can be modified or deleted, and the show users command displays ID numbers 0 through 2147483647.
Console(config)# user add dilbert
Operation successful
Console(config)# user add bwhidney password 0 dzgchenpa capability ftp
Operation successful
Console(config)# user modify user bwhidney add admin-access
Operation successful
Console(config)# show users
There are 4 user(s)
UID USERNAME
0 admin
1002 anonymous
5013 bwhidney
5014 dilbert
Console(config)# user delete uid 5014
Operation successful
show user
show users
To enable the Cache Engine to accept redirected HTTP traffic on a port other than 80, use the wccp custom-web-cache command. To disable custom web caching, use the no form of the command.
wccp custom-web-cache router-list-num num port port [[hash-destination-ip] [hash-destination-port] [hash-source-ip] [hash-source-port] [password passw] [weight percentage]]
router-list-num Router list number. num Router list number (1-8). port Specifies port number. port Port number range (1-65535). hash-destination-ip (Optional.) Load-balancing hash - destination IP (default). hash-destination-port (Optional.) Load-balancing hash - destination port. hash-source-ip (Optional.) Load-balancing hash - source IP. hash-source-port (Optional.) Load-balancing hash - source port. password (Optional.) Specifies authentication password. passw Password. weight (Optional.) Sets weight percentage for load balancing (0-100). percentage Percentage value (0-100).
The wccp custom-web-cache command can configure the Cache Engine to automatically establish WCCP Version 2 redirection services with a Cisco router on a user-specified port number and then perform transparent web caching for all HTTP requests over that port while port 80 transparent web caching continues without interruption. For custom web caching, service 98 must be enabled on the routers. WCCP Version 1 does not support custom web caching.
Transparent caching on ports other than port 80 can be performed by the Cache Engine in environments where WCCP is not enabled or where client browsers have previously been configured to use a legacy proxy server. See the http proxy global configuration command for further information.
The weight parameter represents a percentage of load redirected to the Cache Engine cluster (for example, a Cache Engine with a weight of 30 receives 30 percent of the total load). If the total of all weight parameters in the Cache Engine cluster exceeds 100, the percentage load for each Cache Engine is recalculated as the percentage that its weight parameter represents of the combined total.
Starting custom-web-caching on interface 3 of a WCCP Version 2 enabled router:
router(config): ip wccp 98
[Output not shown]
router(config-if): ip interface 3
router(config-if): ip web-cache 98 redirect out
[Output not shown]
On the Cache Engine:
cache_engine(config)# wccp custom-web-cache router-list-num 5 port 82
weight 30 password Allied hash-destination-ip hash-source-port
cache_engine(config)# no wccp custom-web-cache
cache_engine(config)# http proxy outgoing ans.allied.com 82
no-local-domain
cache_engine# sh running-config
Building configuration...
Current configuration:
!
....
!
http proxy outgoing 192.168.200.68 82 no-local-domain
!
wccp router-list 5 10.1.1.1
wccp custom-web-cache router-list 5 port 82 weight 30 password Allied
hash-destination-ip hash-source-port
wccp home-router 10.1.1.2
wccp version 2
!
end
wccp web-cache
http proxy incoming
http proxy outgoing
To enable WCCP flow redirection, use the flow-redirect enable global configuration command. Use the no form of the command to disable flow redirection.
wccp flow-redirect enable
no wccp flow-redirect enable
enable | Enables flow redirection. |
This command works with WCCP Version 2 only. The flow protection feature is designed to keep the TCP flow intact as well as to not overwhelm Cache Engines when they come up or are reassigned new traffic. This feature also has a slow start mechanism whereby the Cache Engines try to take a load appropriate for their capacity.
console# wccp flow-redirect enable
wccp slow-start 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-address
ip-address | Home router 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 172.16.65.243
Console(config)# no wccp home-router 172.16.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 range (1-8). |
password | (Optional.) WCCP services authentication password (key) set on router. |
key | (Optional.) Password character string. |
weight | (Optional.) Sets a load-balancing parameter. |
percentage | Percentage of the load that the Cache Engine shares with the other Cache Engines (1-100). |
Disabled.
This command applies only to WCCP Version 2.
You must configure the wccp router list command before you use this command. The routers in the list must have WCCP reverse proxy service enabled (service 99). See "Web Cache Communication Protocol Version 2."
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 Cache Engines and routers within the cluster with the same password.
The weight parameter represents a percentage of the total load redirected to the Cache Engine in a cluster (for example, a Cache Engine with a weight of 30 receives 30 percent of the total load). If the total of all weight parameters in a Cache Engine cluster exceeds 100, the percentage load for each Cache Engine is recalculated as the percentage that its weight parameter represents of the combined total.
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-address
number | Router list number (1-8). |
ip-address | IP address of router to add to list. |
Disabled.
Use this command to configure various router lists for use with WCCP Version 2 services. For example, you can specify one router list for WCCP Version 2 web-cache service and another list for reverse-proxy at the same time without having to reconfigure groups of routers or caches. You can add up to eight router lists and up to six IP addresses per list.
Console(config)# wccp router-list 7 172.31.68.98
Console(config)# no wccp router-list 7 172.31.68.98
wccp reverse-proxy
wccp web-cache
wccp version 2
To set the maximum time interval over which the Cache Engine will perform a clean shutdown, use the wccp shutdown global configuration command.
wccp shutdown max-wait seconds
max-wait | Sets the clean shutdown time interval. |
seconds | Time in seconds (0-86400). The default is 120 seconds. |
To prevent broken TCP connections, the Cache Engine performs a clean shutdown of WCCP after a reload or wccp version command is issued. The Cache Engine does not reboot until either all connections have been serviced or the configured max-wait interval has elapsed.
During a clean shutdown, the Cache Engine continues to service the flows it is handling but starts to bypass new flows. When the number of flows goes down to zero, the Cache Engine takes itself out of the cluster by having its buckets reassigned to other Cache Engines by the lead Cache Engine. TCP connections can still be broken if the Cache Engine crashes or is rebooted without WCCP being cleanly shut down. The clean shutdown can be aborted while in progress.
console(config)# wccp shutdown max-wait 4999
To enable the Cache Engine slow start capability, use the wccp slow-start enable global configuration command. To disable slow start capability, use the no form of this command.
wccp slow-start enable
enable | Enable WCCP slow start. |
The default is slow start enabled.
Within a cluster of Cache Engines, TCP connections are redirected to other Cache Engines as units are added or removed. A Cache Engine can be overloaded if it is too quickly reassigned new traffic or introduced abruptly into a fat pipe.
WCCP slow start performs the following tasks to prevent a Cache Engine from being overwhelmed when it comes online or is reassigned new traffic:
Slow start is applicable only in the following cases:
In all other cases slow start is not necessary and all the Cache Engines can be assigned their share of the buckets right away.
console# wccp slow-start enable
console# no wccp slow-start enable
wccp flow-redirect
wccp shutdown
To specify the version of WCCP that the Cache Engine should use, enter the
wccp version global configuration command. Use the no form of the command to disable the currently running version.
1 | WCCP Version 1. |
2 | WCCP Version 2. |
Version 1.
Both WCCP versions allow transparent caching of web content. For a detailed description of both versions, see "Web Cache Communication Protocol Version 1" and "Web Cache Communication Protocol Version 2". It is necessary to disable WCCP Version 1 before enabling
WCCP Version 2, and vice-versa. Be sure the routers used in the WCCP environment are running a software version that supports the WCCP version configured on the Cache Engine.
To prevent broken TCP connections, the Cache Engine performs a clean shutdown of WCCP after a reload or wccp version command is executed. See the
wccp shutdown global configuration command for an explanation of
clean shutdown.
Console(config)# no wccp version 1
Console(config)# wccp version 2
wccp home-router
wccp shutdown
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 router-list-num number [password key] [weight percentage]
route-list-num | Specifies router list number. |
number | Router list number (1-8). |
password | (Optional.) Authentication password (key) set by |
key | Password string for the router. |
weight | (Optional.) Sets weight percentage. |
percentage | Weight of load that the Cache Engine carries as compared to other Cache Engines (1-100). |
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 Engine 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 Cache Engines and routers within the cluster with the same password.
The weight parameter represents a percentage of the total load redirected to the Cache Engine (for example, a Cache Engine with a weight of 30 receives 30 percent of the total load). If the total of all weight parameters in a Cache Engine cluster exceeds 100, the percentage load for each Cache Engine is recalculated as the percentage that its weight parameter represents of the combined total.
Console(config)# wccp web-cache router-list-num 1
Console(config)# no wccp web-cache
show wccp cache-engines
show wccp routers
show wccp status
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)#
This section describes the following interface configuration commands.
To enable autosense on an 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.
Cisco router Ethernet interfaces do not negotiate duplex settings. If the Cache Engine is connected to a router directly with a crossover cable, the Cache Engine Ethernet interface has to be manually set to match the router interface settings. Disable autosense before configuring an Ethernet interface. When autosense is on, manual configurations are overridden. You must reboot the Cache Engine to start autosensing.
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 mbits
mbits | 10 10 megabits per second. |
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 configuration 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 for full-duplex operation, 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 operation. 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 this mode. If you encounter excessive collisions or network errors, you may want to configure the interface for half duplex rather than full duplex.
Console(config-if)# fullduplex
Console(config-if)# no fullduplex
halfduplex
To configure an interface for half-duplex operation, 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 operation. 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. If you encounter collisions or other network errors, 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 10.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 Autosense capability on an interface. bandwidth Interface speed. fullduplex Full-duplex interface. halfduplex Half-duplex interface. ip Interface Internet Protocol (IP) configuration commands.
Use this command to negate an 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 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 bypass configuration information, use the show bypass EXEC command.
show bypass [list] [statistics {auth-traffic | load}] [summary]
list | (Optional.) Displays bypass list entries. |
statistics | (Optional.) Shows IP bypass statistics. |
auth-traffic | Displays authenticated traffic bypass statistics. |
load | Displays load bypass statistics. |
summary | (Optional.) Displays a summary of bypass information. |
console# show bypass
Total number of HTTP connections bypassed = 3
Connections bypassed due to system overload = 0
Connections bypassed due to authentication issues = 3
Connections bypassed to facilitate error transparency = 0
Connections bypassed due to static configuration = 0
Total number of entries in the bypass list = 2
Number of Authentication bypass entries = 0
Number of Error bypass entries = 0
Number of Static Configuration entries = 2
console# show bypass list
Client Server Entry type
------ ------ ----------
171.11.11.11:0 any-server:0 static-config
any-client:0 171.23.23.23:0 static-config
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
Data Bytes Max 6815947 KB
Data Bytes Used 39 KB ( 0% full)
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
Volume Clears 0
Mount time Thu Mar 2 09:23:46 2000
Filesystem Statistics for volume /c0t1d0s3 Status: mounted
Data Bytes Max 6815947 KB
Data Bytes Used 9 KB ( 0% full)
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
Volume Clears 0
Mount time Thu Mar 2 09:23:47 2000
console#
Console# show cfs volumes
/c0t0d0s3: mounted
/c0t1d0s3: mounted
cfs
show disks
show dosfs
To display the system clock, use the show clock EXEC command.
show clock [detail]
detail (Optional.) Displays 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 save
clock set
To display 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 only displays the type of debugging enabled, not the specific subset of the command. For example, it shows that ICP debugging is enabled but does not define whether 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 devname
devname 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 show disks command 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 status : CONFIGURED and ONLINE
Max cache size : 16384
Hash table size : 4093
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 the 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 Mar 2000 00:00:10 GMT
Notice: Waiting for Web traffic on port 80
Thu, 01 Mar 2000 00:00:09 GMT
Notice: Waiting for Web Proxy traffic on port 8080
Thu, 01 Mar 2000 00:00:10 GMT
Notice: Waiting for admin traffic on port 8001
Thu, 01 Mar 2000 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.
This 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 1198448 system image
[655360 read only, 1460592 bytes used, 5944976 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 the group (0 to 2147483647). groupname Group name. name Group name. users Number of users in the 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-2000 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:
-----------
10.2.2.3
172.89.2.111
Host Table:
hostname inet address aliases
-------- ------------ -------
localhost 172.0.1.5
console 172.89.117.254
To display the HTTP-related caching parameters, use the show http EXEC command.
show http {age-mult | all | append | authenticate-strip-ntlm | cache-authenticated | cache-cookies | cache-miss | cache-on-abort | cluster | max-ttl | object | persistent-connections | proxy | reval-each-request | serve-ims}
age-mult HTTP/1.0 caching heuristic modifiers. all All HTTP-related caching parameters. append Shows HTTP headers appended by Cache Engine. authenticate-strip-ntlm Handling of requests with NT LAN Manager (NTLM) authentication headers. cache-authenticated Caching of authenticated web objects. cache-cookies Caching of web objects with associated cookies. cache-miss Handling of no-cache requests. cache-on-abort Configuration of cache-on-abort parameters. cluster Cluster healing configuration. max-ttl Maximum time to live for objects in the cache. object Configuration of HTTP object. 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 HTTP connections on port 8080.
Outgoing Proxy-Mode:
Directing request to proxy server at 10.10.10.10 port 8080.
Outgoing proxy exclude list is enabled
Outgoing proxy exclude list:
cisco.com
cruzio.com
Excluding only the domain names on the list is disabled
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 "google.com,cruzio.com"
Number of remote servers = 0
icp client
icp server
To display TCP/IP services that include echo, discard, chargen, 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
Console# show interface ethernet 0
fei (unit number 0):
Flags: (0x8063) UP BROADCAST MULTICAST ARP RUNNING
Type: ETHERNET_CSMACD
Internet address: 172.73.211.222
Broadcast address: 172.73.227.225
Netmask 0xffff0000 Subnetmask 0xffffff80
Ethernet address is 00:50:0f:0d:23:06
Maximum Transfer Unit size: 1500
Address Length: 6
Header Length: 14
Metric: 0
Baudrate: 0
Packets Received: 800
Input Errors: 0
Packets Sent: 567
Output Errors: 0
Collisions: 0
Bytes Received: 52754
Bytes Sent: 46678
Multicast Packets Received: 217
Multicast Packets Sent: 0
Received Packets Dropped: 0
Packets with Unknown Protocol: 0
Last Input/Output (ticks): 92746
Line speed: 100Mbit per sec. Duplex: full (AutoSensed)
Hardware statistical counters:
Current Total
------- -----
Tx good frames: 60 570
Tx MAXCOL errors: 0 0
Tx LATECOL errors: 0 0
Tx underrun errors: 0 0
Tx lost CRS errors: 0 0
Tx deferred: 0 0
Tx single collisions: 0 0
Tx multiple collisions: 0 0
Tx total collisions: 0 0
Rx good frames: 135 1725
Rx CRC errors: 0 0
Rx alignment errors: 0 0
Rx resource errors: 0 0
Rx overrun errors: 0 0
Rx collision detect errors: 0 0
Rx short frame errors: 0 0
(current values are polled and cleared for each display)
set interface
To display the IP routing table, use the show ip routes EXEC command.
show ip routes
routes Displays routing table.
console# show ip routes
Destination Mask TOS Gateway Flags RefCnt Use IntFace Proto
----------------------------------------------------------------------------
0.0.0.0 0.0.0.0 0 172.79.27.12 3 2 983 fei0 1
125.0.0.1 0.0.0.0 0 127.0.0.1 5 0 0 lo 0 0
172.79.22.12 255.255.255.1 172.79.27.200 101 0 0 fei0 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
Syslog logging: enabled
Console logging: level warning
Trap logging: disabled
Disk logging: level debug
Logging to /local/var/log/syslog.txt, recycle size 5000000
Event export:
Critical events are exported to syslog
To display memory blocks and statistics, use the show memory EXEC command.
show memory [free]
free (Optional.) Shows free blocks of memory.
Console# show memory free
SUMMARY:
status bytes blocks avg block max block
------ --------- -------- ---------- ----------
current
free 4374032 12 364502 4359952
alloc 125199608 514 243579 -
cumulative
alloc 125341720 1336 93818 -
Page Freelist Summary:
status pagesz pages avg contig pages max contig pages
------ ------ ------- ---------------- ----------------
free 4096 15346 3069 15300
To display the Network Time Protocol (NTP) parameters, use the show ntp EXEC command.
show ntp status
status NTP status.
Console# show ntp status
NTP subsystem
-------------
servers:
ntp
clock set
clock timezone
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 radius-serverThis command has no arguments or keywords.
Console# show radius-server
Radius Configuration:
---------------------
Radius Authentication is off
This could be because there are no servers or key is NULL
Timeout = 5 seconds
AuthTimeout = 20 minutes
Retransmit = 3
Key =
Servers
-------
Selective Authentication is on.
Local domains to be excluded from Radius Authentication: None
To display the current running configuration information on the terminal, use the show running-config EXEC command. This command replaces the
write terminal command.
This 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 bootup.
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 britta uid 2001
!
!
!
hostname waltraud_cache
!
interface ethernet 0
ip address 172.16.0.0 255.255.255.008
ip broadcast-address 172.16.10.0
exit
!
!
interface ethernet 1
exit
ip domain-name cisco.com
ip route 0.0.0.0 0.0.0.0 172.16.0.3
cron file /local/etc/crontab
!
bypass static 171.11.11.11 any-server
bypass static any-client 172.16.0.5
http cache-cookies
http max-ttl days text 4 binary 3
http cache-authenticated
http proxy outgoing exclude enable
http proxy outgoing exclude list cisco.com
http proxy outgoing exclude list cruzio.com
http proxy outgoing host 10.2.2.2 8080
http proxy incoming 8080
icp client exclude google.com,cruzio.com
url-filter websense server 172.16.12.0 port 3333 timeout 5
no url-filter websense allowmode
wccp router-list 1 10.1.1.1
wccp web-cache router-list-num 1
wccp reverse-proxy router-list-num 1
wccp custom-web-cache router-list-num 1 port 1 hash-destination-ip
weight 33
wccp home-router 10.1.1.1
wccp version 1
!
radius-server exclude enable
transaction-logs archive files 5
transaction-logs archive interval 600
transaction-logs enable
transaction-logs export interval 3600
transaction-logs export enable
!
exec-timeout 60
!
end
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-2 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 No such name error, Bad values 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 toFFFFFFFF). exception Stack trace on previous exception.
Console# show stacktrace exception
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 bootup, stored in NVRAM.
Console# show startup-config
Configuration Size 1538 bytes
!
!
logging event-export critical-events warning user
!
group add admin gid 0
group add everyone gid 1000
group add LocalUsers gid 1004
!
user add admin uid 0 password 1 "ceSzbyeb" capability admin-access
user add bwhidney uid 5013 password 1 "bSzyydQbSb" capability
admin-access
!
!
!
hostname console
!
interface ethernet 0
ip address 172.31.77.70 255.255.255.77
ip broadcast-address 172.31.77.255
exit
!
!
interface ethernet 1
interface ethernet 1
exit
!
ip default-gateway 172.31.77.0
ip name-server 10.7.7.7
ip name-server 10.8.2.72
ip domain-name cisco.com
ip route 0.0.0.0 0.0.0.0 172.31.77.55
cron file /local/etc/crontab
!
bypass static 172.30.77.70 any-server
bypass static any-client 172.16.77.70
http cache-cookies
http max-ttl days text 4 binary 3
http cache-authenticated
http proxy outgoing exclude enable
http proxy outgoing exclude list cisco.com
http proxy outgoing exclude list cruzio.com
http proxy outgoing host 172.31.33.70 8080
http proxy incoming 8080
icp client exclude google.com,cruzio.com
url-filter websense server 172.22.77.70 port 3333 timeout 5
no url-filter websense allowmode
wccp router-list 1 10.1.1.1
wccp web-cache router-list-num 1
wccp reverse-proxy router-list-num 1
wccp custom-web-cache router-list-num 1 port 1 hash-destination-ip
weight 33
wccp home-router 10.1.1.1
wccp version 1
!
radius-server exclude enable
transaction-logs archive files 5
transaction-logs archive interval 600
transaction-logs enable
transaction-logs export interval 3600
transaction-logs export enable
!
exec-timeout 60
!
end
configure
copy running-config
show running-config
To display Cache Engine statistics, use the show statistics EXEC command.
show statistics {bypass [auth-traffic | load | summary] | cfs | dns-cache | http {ims | object | performance | savings | usage} | icmp | icp {client | cluster | server} | ip | mbuf | netstat | radius-server | routing | tcp | transaction-logs | udp | url-filter websense}
bypass Displays bypass statistics. auth-traffic Displays authenticated traffic bypass statistics. load Displays load bypass statistics. summary Displays a summary of bypass statistics. cfs Displays cache file system statistics. dns-cache Displays DNS cache statistics. http Displays HTTP caching statistics. ims Displays HTTP if-modified-since statistics. object Displays HTTP object statistics. performance Displays HTTP performance statistics. requests Displays HTTP requests statistics. savings Displays HTTP savings statistics. usage Displays HTTP usage statistics. icmp Displays ICMP statistics. icp Displays ICP caching statistics. client Displays ICP client statistics. cluster Displays ICP cluster statistics. server Displays ICP server statistics. ip Displays IP statistics. mbuf Displays mbuf statistics. netstat Displays Internet socket connections. radius-server Displays RADIUS statistics. routing Displays routing statistics. tcp Displays TCP statistics. transaction-logs Displays transaction-log export statistics. udp Displays UDP statistics. url-filter Displays URL filter statistics. websense Displays Websense URL filtering statistics.
To clear statistics without affecting configurations, use the clear statistics command. This will set all counters to zero.
Console# 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 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
TCP server max segment size 1432
TCP server satellite (RFC1323) disabled
TCP client max segment size 1432
TCP client satellite (RFC1323) disabled
TCP retransmit drop threshold 1
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.) Pages through output.
Use this command to view system information necessary for TAC to assist you with your Cache Engine. This is a long display. You can manage the output using the terminal length command.
Console# show tech-support
---------------------show hardware---------------------
Cisco Cache Engine
Copyright (c) 1986-1999 by Cisco Systems, Inc.
Software Release: CE ver 2.09 (Build: #17 03/02/00)
Compiled: 06:19:45 Mar 2 2000 by morlee
Image text-base 0x108000, data_base 0x392064
System restarted by Reload
The system has been up for 3 hours, 12 minutes, 23 seconds.
System booted from "flash"
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.
---More---
Use this command to display configured TFTP directories.
show tftp-serverThis command has no arguments or keywords.
console#show tftp-server
== TFTPD Directory List ==
/local/public
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 Number of most recent entries to display (1-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 transaction-logging entries command to work.
Console# show transaction-logging
Transaction Logs:
Logging is enabled.
End user identity is visible.
Current Archive Interval: 600 seconds.
Maximum Number of Archived Files: 5
Exporting files to servers is enabled.
Export retry interval: 3600 minutes.
Working Log file - size: 0
age: 555
Archive Log file - celog_171.69.227.250_20000302_182550.txt size: 0
To display the name of the Cache Engine trusted hosts, use the
show trusted-hosts EXEC command.
This command has no arguments or keywords.
Console# show trusted-hosts
Trusted Host checking: ON
111.333.123.2/C_Medici
333.222.111.1/Procrustes
To display URL filter information, use the show url-filter EXEC command.
show url-filter [statistics websense]
statistics websense | Displays Websense URL filtering statistics. |
Console# show url-filter
Websense URL Filtering Lookup enabled
Websense Server = 171.22.11.22
Server Port = 3333
Server Timeout = 5
Allowmode is not enabled.
To display user information for a particular user, use the show user EXEC command.
show user {uid number | username name}
uid User ID keyword. number User ID number (0-2147483647). username Displays information for user. name Username.
console#show user username bwhidney
Username : bwhidney
Uid : 5013
Number of Groups : 1
Primary Group : everyone (1000)
Password : bSzyydQbSb
Comment :
HomeDir : /local
Capability : admin-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
5013 bwhidney
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
Copyright (c) 1986-1999 by Cisco Systems, Inc.
Software Release: CE ver 2.09 (Build: #17 03/02/00)
Compiled: 06:19:45 Mar 2 2000 by morlee
Image text-base 0x108000, data_base 0x392064
System restarted by Reload
The system has been up for 3 hours, 36 minutes, 34 seconds.
System booted from "flash"
To display WCCP information, use the show wccp EXEC command.
show wccp {cache-engines | router | status}
cache-engines Shows WCCP Cache Engine information. routers Shows WCCP router list. status Shows WCCP running status.
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 19:10:28 PDT 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.