![]() |
Cisco Cache Engine User Guide, Version 2.1.0
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Appendix A: Command Reference
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Table of ContentsCommand ReferenceEXEC Mode
Global Configuration Mode Interface Configuration Mode Check Command Syntax System Help Save Configuration Changes General Commands (or EXEC Commands) cache
Global Configuration Commandscd cfs check clear clock configure copy cpfile debug del deltree dir disable disk dnslookup dosfs enable exit help install lls ls mkdir mkfile no debug ntpdate ping pwd reload rename rmdir show tclsh terminal type undebug whoami write bypass
Interface Configuration Commandsclock timezone cron dns-cache end error-handling exception exec-timeout exit group help hostname http icp inetd interface ip logging no ntp radius snmp-server community snmp-server contact snmp-server enable traps snmp-server host snmp-server location tcp terminal length transaction-logs trusted-host url-filter user wccp custom-web-cache wccp flow-redirect wccp home-router wccp reverse-proxy wccp router-list wccp shutdown wccp slow-start wccp version wccp web-cache Show Commands (EXEC Commands) show arp
show bypass show cfs show clock show cron show debugging show disk-partitions show disks show dns-cache show dosfs show events show file-descriptors show flash show group show groups show hardware show hosts show http show icp show inetd show interface show ip routes show logging show memory show ntp show processes show radius-server show running-config show snmp show stacktrace show startup-config show statistics show tcp show tech-support show tftp-server show transaction-logging show trusted-hosts show url-filter show user show users show version show wccp Command ReferenceThis appendix provides a summary of the commands used to configure your 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:
EXEC ModeTo 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 Global Configuration ModeTo 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. Interface Configuration ModeTo 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)# Check Command SyntaxThe 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 System HelpYou 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 Save Configuration ChangesTo 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 General Commands (or EXEC Commands)The general (or EXEC) Cache Engine commands are entered in the EXEC mode. This section describes the following EXEC commands.
cacheTo 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. Syntax Description
Usage GuidelinesThe 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.
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. ExampleConsole# cache clear force Related Commandsclear cache cfs clear cdTo change directory, use the cd EXEC command. cd{directoryname}Syntax Description
Usage GuidelinesUse 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 "/". ExampleRelative path: Console# cd etc Absolute path: Console# cd /local/etc Related Commandsdir lls ls mkdir pwd rmdir cfsTo 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}Syntax Description
Usage GuidelinesCache 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.
The cfs format command creates the cache file system internal "dbs" for the cfs partition of the disk if the volume is unmounted. It formats the cfs partition to prepare it for a cfs mount. The cfs mount command creates and maps data structures in memory to the cfs partition.
The cfs unmount command frees the in-memory data structures that 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. ExampleConsole# cfs sync c0t0d0s3 Related Commandsshow cfs cache clear clear cache checkTo check whether superuser accounts are password-protected, use the check EXEC command. check superuser passwordsSyntax Description
DefaultBy default, superuser accounts are not password-protected. Usage GuidelinesThis 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. ExampleConsole# check superuser passwords ---------------------------------------------------------------------- All super-user accounts are password protected ---------------------------------------------------------------------- Related Commandsuser modify show user clearTo 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| statistics {all | dns-cache | history | http {all | errors | ims | object | requests | response | savings} | transaction-logs} Syntax Description
Usage GuidelinesThe 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.
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 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. ExampleConsole# clear cache Related Commandscache clear cfs clear show statistics show interface show wccp clockTo set, clear, or save the battery-backed clock functions, use the clock EXEC command. clock {clear | save | set hh:mm:ss day month year}Syntax Description
Usage GuidelinesIf 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. ExampleConsole# clock set 13:32:00 01 February 2000 Related Commandsclock timezone show clock detail configureTo 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. Syntax DescriptionThis command has no arguments or keywords. Usage GuidelinesUse this command to enter global configuration mode. ExamplesConsole# configure Enter configuration commands, one per line. End with CNTL/Z. Console(config)# Related Commandsshow running-config show startup-config end exit Ctrl-Z copyTo 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}| startup-config {disk filename | tftp} | tech-support {disk filename | tftp} | tftp {disk | flash}} Syntax Description
Usage GuidelinesUse 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. ExampleConsole# copy disk flash /local/bin Related Commandswrite show running-config show startup-config cpfileTo copy one filename to another filename, use the cpfile EXEC command. cpfile oldfilename newfilenameSyntax Description
Usage GuidelinesUse this command to copy one filename to another. This command only copies dosfs files. ExampleConsole# cpfile ce500-194616.bin cd500-194618.bin Related Commandscopy dir lls ls mkfile rmdir rmname debugTo 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| 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} 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} Syntax Description
Subcommands
Usage GuidelinesUse 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. ExampleConsole# debug http cache trace Console# no debug http cache trace Related Commandsno debug show debug undebug delTo remove a file, use the del EXEC command. del filename Syntax Description
Usage GuidelinesUse this command to remove a file from any directory. Note that some files are necessary for proper functionality and should not be removed. ExampleConsole# del /local/tempfile Related Commandscpfile deltree mkdir mkfile rmdir deltreeTo remove a directory recursively and all files that it contains, use the deltree EXEC command. deltree directorySyntax Description
Usage GuidelinesUse 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. ExampleConsole# deltree /local Related Commandsdel dirTo view a long list of files in a directory, use the dir EXEC command. dir [directory]Syntax Description
Usage GuidelinesUse 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. ExampleConsole# 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 Related Commandslls ls disableTo turn off privileged EXEC commands, use the disable EXEC command. disableSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesThe disable command places you in EXEC mode. To turn privileged EXEC mode back on, use the enable command. ExampleConsole# disable Related Commandsenable diskTo configure the Cache Engine disks, use the disk EXEC command. disk {erase-all-partitions devname | manufacture devname | partition devname | prepare devname}Syntax Description
Usage GuidelinesDisk 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.
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.
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). ExampleTo create only a DOS partition on the first disk, enter the following commands: Console# disk erase-all-partitions Console# disk partition boot Related Commandsshow disk-partitions show disks dnslookupUse the dnslookup EXEC command to resolve a host or domain name to an IP address. dnslookup {host | domain-name} Syntax Description
Usage GuidlinesExamplesConsole# 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
dosfsTo 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}Syntax Description
Usage GuidelinesUse 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. ExampleConsole# dosfs format /local Related Commandsshow dosfs volumes cd copy cpfile del deltree dir ls mkdir mkfile enableTo turn on privileged commands, use the enable EXEC command. enableSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesTo 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. ExampleConsole> enable Console# Related Commandsdisable exitTo exit any configuration mode or close an active terminal session and terminate an EXEC mode session, use the exit EXEC command. exitSyntax DescriptionThis command has no arguments or keywords. Command ModeEXEC and global configuration Usage GuidelinesUse 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. ExampleConsole# exit Related Commandsend helpTo get online help for the command-line interface, use the help EXEC or global configuration command. helpSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesYou 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:
ExampleConsole# help installTo install a new version of Cache Engine software, use the install EXEC command. install paxfilenameSyntax Description
Usage GuidelinesInstall 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. ExampleConsole# install ce25.pax Related Commandsreload llsTo view a long list of directory names, use the lls EXEC command. lls [directory]Syntax Description
Usage GuidelinesThis 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. ExampleConsole# 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 Related Commandsdir ls lsTo view a list of files or subdirectory names within a directory, use the ls EXEC command. ls [directory]Syntax Description
Usage GuidelinesTo list the filenames and subdirectories within a particular directory, use the ExampleConsole# ls /local etc tftpboot var lib ce25.pax 2125922304 bytes AVAILABLE ON VOLUME /c0t0d0s1 Related Commandsdir lls pwd mkdirTo create a directory, use the mkdir EXEC command. mkdir directorySyntax Description
Usage GuidelinesUse this command to create a new directory or subdirectory in the Cache Engine file system. ExampleConsole# mkdir /oldpaxfiles Related Commandsdir lls ls pwd rmdir mkfileTo create a new file, use the mkfile EXEC command. mkfile filenameSyntax Description
Usage GuidelinesUse this command to create a new file in any directory of the Cache Engine. ExampleConsole# mkfile traceinfo Related Commandslls ls mkdir no debugTo 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}Syntax DescriptionSee the syntax description for the debug command. Usage GuidelinesUse 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. ExampleConsole# no debug http all error Related Commandsdebug no debug show debug undebug ntpdateTo set the software clock (time and date) using a Network Time Protocol (NTP) server, use the ntpdate EXEC command. ntpdate {hostname | ip-address}Syntax Description
Usage GuidelinesUse 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. ExampleConsole# ntpdate 10.11.23.40 Related Commandsclock clear clock save clock set show clock pingTo send echo packets for diagnosing basic network connectivity on networks, use the ping (packet internet groper) EXEC command. ping {hostname | ip-address}Syntax Description
Usage GuidelinesTo 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. ExampleConsole# ping mycacheengine pwdTo show the current directory, use the pwd EXEC command. pwdSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesUse this command to display the present working directory of the Cache Engine. ExampleConsole# pwd Related Commandscd dir lls ls reloadTo halt and perform a cold restart on your Cache Engine, use the reload EXEC command. reloadSyntax DescriptionThis command has no arguments or keywords. Usage Guidelines
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. ExampleConsole# reload Related Commandscache sync write write erase renameTo rename a file on your Cache Engine, use the rename EXEC command. rename sourcefile destinationfileSyntax Description
Usage GuidelinesUse this command to rename any file within the Cache Engine. ExampleConsole# rename ce25.pax ce6399.pax Related Commandscpfile rmdirTo delete a directory, use the rmdir EXEC command. rmdir directorySyntax Description
Usage GuidelinesUse this command to remove any directory from the Cache Engine file system. The rmdir command only removes empty directories. ExampleConsole# rmdir /local/oldpaxfiles Related Commandslls ls mkdir showUse 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. tclshThe tclsh command is for Cisco Systems internal use only. terminalTo display the current terminal commands, use the terminal EXEC command. terminal monitorSyntax Description
Usage GuidelinesThis 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. ExampleConsole# terminal monitor Console is always monitored typeTo display a file, use the type EXEC command. type filenameSyntax Description
Usage GuidelinesUse 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. ExampleConsole# type badurl.lst Related Commandscpfile dir lls ls mkfile undebugTo 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}Syntax DescriptionSee the syntax description for the debug command. Usage GuidelinesUse 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. ExampleConsole# undebug icp all Related Commandsdebug no debug show debug whoamiTo display the current user's name, use the whoami EXEC command. whoamiSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesUse this command to display the current user's username and user identification number. ExampleConsole# whoami admin Related Commandspwd writeTo write running configurations to memory or to a terminal session, use the write EXEC command. write [erase | memory | terminal]Syntax Description
DefaultThe configuration is written to NVRAM by default. Usage GuidelinesUse 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. ExampleConsole# write Related Commandscopy running-config startup-config show running-config Global Configuration CommandsThe global configuration Cache Engine commands are entered in the global configuration mode. The section describes the following global configuration commands.
bypassTo 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}Syntax Description
Usage GuidelinesBypass features are available only with WCCP Version 2. The Cache Engine can only bypass WCCP-redirected traffic, not proxy-style requests. Authentication BypassSome 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). Load BypassIf 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. Static BypassThe 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. Example
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 Related Commandsshow bypass clock timezoneTo 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]no clock timezone Syntax Description
Usage GuidelinesTo 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. ExampleThe 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 Related Commandsclock show clock detail cronTo 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}no cron {del-tab entryid | file tabfile | save-tab | tab-entry tabentry} Syntax Description
Usage GuidelinesThe 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
ExampleConsole(config)# cron sav-tab Console(config)# no cron sav-tab Related Commandsshow cron dns-cacheTo 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 maxsizeno dns-cache size Syntax Description
Usage GuidelinesCache 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 ExamplesConsole(config)# dns-cache enable Console(config)# dns-cache size 512 Console(config)# no dns-cache enable Console(config)# no dns-cache size Related Commandsip name-server clear dns-cache show dns-cache dnslookup show statistics dns-cache endTo exit global configuration mode, use the end global configuration command. endSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesUse 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. ExampleConsole(config)# end Console# Related Commandsexit Ctrl-Z error-handlingUse the error-handling command to set error-handling options. error-handling {reset-connection | send-cache-error | transparent}Syntax Description
Usage GuidelinesWith 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:
Exampleconsole# error-handling transparent exceptionThe exception debug command is for Cisco Systems internal purposes only. exec-timeoutTo 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 timeoutno exec-timeout Syntax Description
Usage GuidelinesUse this command to establish the length of time, in minutes, that an inactive terminal session window will remain open. The default is 150 minutes. ExampleConsole(config)# exec-timeout 100 Console(config)# no exec-timeout exitTo exit any configuration mode or close an active terminal session and terminate EXEC mode session, use the exit EXEC command. exitSyntax DescriptionThis command has no arguments or keywords. Command ModeEXEC and global configuration Usage GuidelinesUse 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. ExampleConsole# exit Related Commandsend Ctrl-Z groupTo 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}}Syntax Description
Usage GuidelinesUse 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. ExampleConsole(config)# group add pubs Related Commandsshow group show groups show user show users user users helpTo get online help for the command-line interface, use the help EXEC or global configuration command. helpSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesYou 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:
ExampleConsole(config)# help hostnameTo 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 nameno hostname Syntax Description
DefaultThe default host name is the Cache Engine model number (CE505, CE550, or CE570). Usage GuidelinesUse this command to configure the host name for the Cache Engine. The host name is used for the command prompts and default configuration filenames. ExampleThe following example changes the host name to sandbox: Console(config)# hostname sandbox sandbox(config)# Console(config)# no hostname CE550(config)# httpTo 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}no 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} Syntax Description
Usage GuidelinesUse these commands to configure specific parameters for caching HTTP objects.
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
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 syntax172.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. ExampleConsole(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
Related Commandshow http icpTo 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}}no 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}} Syntax Description
Usage GuidelinesUse 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. ExampleConsole(config)# icp client enable Icp Client started Console(config)# no icp client enable Icp Client disabled Related Commandsshow icp client show icp server show statistics icp inetdTo 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}no inetd {enable service} Syntax Descriptions
Default
Usage GuidelinesUse 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 ExampleConsole(config)# inetd enable ftp 5 Console(config)# no netd enable ftp Related Commandsshow inetd interfaceTo 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 numberno interface ethernet number Syntax Description
Usage GuidelinesUse 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. ExampleConsole(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 Related Commandsshow interface ipip {default-gateway ipaddress | domain-name domainname | name-server ipaddress | route destaddrs netmask gateway}Syntax Description
Usage GuidelinesTo 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 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. ExampleConsole(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 Related Commandsshow ip route loggingTo 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}no logging {hostname | ip-address | console loglevels | disk filename loglevels | event-export events loglevels facility | facility facility | on | recycle size | trap loglevels} Syntax Description
DefaultsThese are the defaults when no other options are configured by the user:
Usage GuidelinesUse 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. ExampleConsole(config)# logging console warnings Console(config)# no logging console warnings noTo undo a global configuration command or set its defaults, use the no form of a command to undo the original command no commandSyntax Description
Usage GuidelinesUse 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. ExampleConsole(config)# wccp version 2 Console(config)# no wccp version 2 ntpTo 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}no ntp server {hostname | ip-address} Syntax Description
DefaultThe default NTP version number is 3. Usage GuidelinesUse this command to synchronize the Cache Engine clock with the specified server. The server will not synchronize to this machine. ExampleConsole(config)# ntp server 172.16.22.44 Console(config)# no ntp server 172.16.22.44 Related Commandsclock show clock show ntp radiusTo 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}no radius {auth-timeout value | exclude {enable | list domainlist} | host {hostname | hostipaddr} [auth-port port] | key keyword | retransmit retries | timeout seconds} Syntax Description
Usage GuidelinesRADIUS 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. Selective RADIUS AuthenticationUsers 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. ExampleConsole(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.
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:
Console(config)# no radius exclude list cisco.com
Console(config)# no radius exclude enable
snmp-server communityTo 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 stringno snmp-server community Syntax Description
DefaultBy default, an SNMP community string permits read-only access to all objects. Usage GuidelinesExamplesThe 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 Related Commandsshow snmp snmp-server contactTo 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 lineno snmp-server contact Syntax Description
DefaultNo system contact string is set. Usage GuidelinesThe system contact string is the value stored in the MIB-II system group sysContact object. ExampleThe following is an example of a system contact string: Console# snmp-server contact Dial System Operator at beeper # 27345 Console# no snmp-server contact Related Commandssnmp-server location show snmp snmp-server enable trapsTo 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 trapsno snmp-server enable traps Syntax DescriptionThis command has no arguments or keywords. DefaultThis command is disabled by default. No traps are enabled. Usage GuidelinesIf 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. ExampleThe 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 Related Commandssnmp-server host snmp-server community snmp-server hostTo 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} communitystringno snmp-server host {hostname | ip-address} communitystring Syntax Description
DefaultThis command is disabled by default. No traps are sent. The version of the SNMP protocol used to send the traps is SNMPv1. Usage GuidelinesIf 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. ExampleThe 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 Related Commandssnmp-server enable traps snmp-server community snmp-server locationTo 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 lineno snmp-server location Syntax Description
DefaultNo system location string is set. Usage GuidelinesThe 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. ExampleThe following is an example of a system location string: Console(config)# snmp-server location Building 3/Room 214 Related Commandsshow snmp snmp-server contact tcpTo 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}no 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} Syntax Description
Default
Usage GuidelinesIn nearly all environments, the default TCP setting is adequate. If you modify the listen-queue settings, reboot the Cache Engine to effect the changes. ExampleConsole(config)# tcp client-receive-buffer 100 Console(config)# no tcp client-receive-buffer 100 Related Commandsshow tcp terminal lengthTo 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 linesno terminal length lines Syntax Description
Usage GuidelinesThis 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. ExampleConsole(config)# terminal length 0 Console(config)# no terminal length 0 Related CommandsAll show commands. transaction-logsTo 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} | sanitizeno transaction-logs Syntax Description
Usage GuidelinesEnable 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. Transaction Log Archive File-Naming ConventionThe archive transaction log file is named as follows: celog_10.1.118.5_19991228_235959.txt Table A-1 describes the name elements. Table A-1: Description of Archive Log Name Elements
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. Exporting Transaction Logs to External FTP ServersThe 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. Restarting Export After Receiving a Permanent Error from the External FTP ServerWhen 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. 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:
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. Example
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
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
Related Commandsshow transaction-logs trusted-hostTo 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}no trusted-host {domain-lookup} Syntax Description
DefaultNo trusted hosts is the default. Usage GuidelinesTo 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. ExampleConsole(config)# trusted-host domain-lookup Console(config)# trusted-host 172.31.90.33 Console(config)# no trusted-host domain-lookup Related Commandsshow trusted-hosts url-filterTo 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]}}no url-filter {bad-sites-block [custom-message] | good-sites-allow [custom-message] | websense {allowmode enable | server {hostname | ipaddrs} [port port] [timeout seconds]}} Syntax Description
Usage GuidelinesThe Cache Engine can control client access to web sites as follows:
Only one form of URL filtering can be active at a time. URL Filtering with URL ListsThe 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). Custom Blocking MessagesWhen 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
To disable the custom-message option without disabling URL filtering,enter the URL filtering command without the custom-message option URL Filtering with the Websense Enterprise ServerThe 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.
ExampleTo 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 Related Commandsshow url-filter show url-filter statistics websense userTo configure user accounts on your Cache Engine, use the user global configuration command. user {add | delete | modify}user add username [password [ 0 | 1] password] [capability [admin-access | ftp-access | http-access | telnet-access]] [uid userid] user delete {username username | uid userid} user modify {uid number | username name}{[add-capability [admin-access | ftp-access | http-access | telnet-access]] | [del-capability [admin-access | ftp-access | http-access | telnet-access]] | [password [ 0 | 1] password]} Syntax Description
DefaultThe default users are admin and anonymous. Usage GuidelinesThe 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. ExampleConsole(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
Related Commandsshow user show users wccp custom-web-cacheTo 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]]no 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]] Syntax Description
Usage GuidelinesThe 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. ExampleStarting 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 Related Commandswccp web-cache http proxy incoming http proxy outgoing wccp flow-redirectTo 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 Syntax Explanation
Usage GuidelinesThis 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. Examplesconsole# wccp flow-redirect enable Related Commandswccp slow-start enable wccp home-routerTo 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-addressno wccp home-router ip-address Syntax Description
DefaultDisabled. Usage GuidelinesTo 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. ExampleConsole(config)# wccp home-router 172.16.65.243 Console(config)# no wccp home-router 172.16.65.243 Related Commandsshow wccp routes wccp version 1 wccp reverse-proxyTo 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]no wccp reverse-proxy Syntax Description
DefaultDisabled. Usage GuidelinesThis 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. ExampleConsole(config)# wccp reverse-proxy router-list-num 8 password key weight 100 Console(config)# no wccp reverse-proxy Related Commandsshow wccp cache-engines show wccp services wccp router-list wccp version 2 wccp router-listTo 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-addressno wccp router-list number ip-address Syntax Description
DefaultDisabled. Usage GuidelinesUse 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. ExampleConsole(config)# wccp router-list 7 172.31.68.98 Console(config)# no wccp router-list 7 172.31.68.98 Related Commandswccp reverse-proxy wccp web-cache wccp version 2 wccp shutdownTo 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 secondsSyntax Description
Usage GuidelinesTo 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. Exampleconsole(config)# wccp shutdown max-wait 4999 Related Commandswccp versionwccp slow-start wccp flow-redirect wccp slow-startTo 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 enableno wccp slow-start enable Syntax Description
DefaultThe default is slow start enabled. Usage GuidelinesWithin 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. Exampleconsole# wccp slow-start enable console# no wccp slow-start enable Related Commandswccp flow-redirect wccp shutdown wccp versionTo specify the version of WCCP that the Cache Engine should use, enter the no wccp version {1 | 2} Syntax Description
DefaultVersion 1. Usage GuidelinesBoth 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 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 ExampleConsole(config)# no wccp version 1 Console(config)# wccp version 2 Related Commandswccp home-router wccp shutdown wccp web-cacheTo 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]no wccp web-cache Syntax Description
Usage GuidelinesUse 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. ExampleConsole(config)# wccp web-cache router-list-num 1 Console(config)# no wccp web-cache Related Commandsshow wccp cache-engines show wccp routers show wccp status wccp version 2 Interface Configuration CommandsThe 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.
autosenseTo enable autosense on an interface, use the autosense interface configuration command. To disable this function, use the no form of this command. autosenseno autosense Syntax DescriptionThis command has no arguments or keywords. Usage GuidelinesCisco 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. ExampleConsole(config-if)# autosense Console(config-if)# no autosense bandwidthTo configure an interface bandwidth, use the bandwidth interface configuration command. To disable this function, use the no form of this command. bandwidth mbitsno bandwidth Syntax Description
Usage GuidelinesUse this command to set the bandwidth of an interface to either 10 or 100 megabits. ExampleConsole(config-if)# bandwidth 10 Console(config-if)# no bandwidth exitTo exit the interface configuration mode, use the exit interface configuration command. exitSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesUse this command to return to the global configuration mode from the interface configuration mode. ExampleConsole(config-if)# exit Console(config)# fullduplexTo configure an interface for full-duplex operation, use the fullduplex interface configuration command. To disable this function, use the no form of this command. fullduplexno fullduplex Syntax DescriptionThis command has no arguments or keywords. Usage GuidelinesUse 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. ExampleConsole(config-if)# fullduplex Console(config-if)# no fullduplex Related Commandshalfduplex halfduplexTo configure an interface for half-duplex operation, use the halfduplex interface configuration command. To disable this function, use the no form of this command. halfduplexno halfduplex Syntax DescriptionThis command has no arguments or keywords. Usage GuidelinesUse 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 ExampleConsole(config-if)# halfduplex Console(config-if)# no halfduplex Related Commandsfullduplex ipTo 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}no ip {address [ip-address ip-subnet] | broadcast-address} Syntax Description
Usage GuidelinesUse 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. ExampleConsole(config-if)# ip address 10.10.10.10 255.0.0.0 Console(config-if)# no ip broadcast-address noTo negate a command or set its defaults, use the no interface configuration command. no {autosense | bandwidth | fullduplex | halfduplex | ip}Syntax Description
Usage GuidelinesUse this command to negate an interface configuration mode command or set its defaults. See the interface configuration command descriptions for syntax options and descriptions. ExampleConsole(config-if)# no autosense Show Commands (EXEC Commands)The show Cache Engine commands are entered in the EXEC mode. The following show commands are described in the following pages:
show arpTo display the Address Resolution Protocol (ARP) table, use the show arp EXEC command. show arpSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# 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# show bypassTo display bypass configuration information, use the show bypass EXEC command. show bypass [list] [statistics {auth-traffic | load}] [summary]Syntax Description
Exampleconsole# 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
show cfsTo view information about your cache file system, use the show cfs EXEC command. show cfs {statistics | volumes}Syntax Description
ExampleConsole# 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
Related Commandscfs show disks show dosfs show clockTo display the system clock, use the show clock EXEC command. show clock [detail]Syntax Description
ExampleConsole# 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 Related Commandsclock clear clock save clock set show cronTo display cron information, use theshow cron EXEC command. show cronSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# 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
show debuggingTo display the state of each debugging option, use the show debugging EXEC command. show debuggingSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesThis 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. ExampleConsole# debug icp client trace Console# show debugging icp debugging is on Related Commandsdebug no debug undebug show disk-partitionsTo view information about your disk partitions, use the show disk-partitions EXEC command. show disk-partitions devnameSyntax Description
Usage GuidelinesUse 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. ExampleConsole# show disk-partitions devname Related Commandsdisk partition disk prepare show disks show disksTo view information about your disks, use the show disks EXEC command. show disksSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesThe 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. ExampleConsole# show disks /c0t0d0 (scsi bus 0, unit 0, lun 0) /c0t1d0 (scsi bus 0, unit 1, lun 0) Related Commandsdisk partition disk prepare show disk-partitions show dns-cacheTo display DNS cache information, use the show dns-cache EXEC command. show dns-cacheSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# show dns-cache DNS cache status : CONFIGURED and ONLINE Max cache size : 16384 Hash table size : 4093 show dosfsTo view DOS file system information, use the show dosfs EXEC command. show dosfs {config volname | label devicename | volumes}Syntax Description
ExampleConsole# show dosfs volumes /c0t0d0s1: mounted /c0t1d0s1: not mounted /local: mounted Related Commandsdosfs cfs show cfs show eventsTo display a number of system events by category, use the show events EXEC command. show events number {all | critical | notice | warning}Syntax Description
Usage GuidelinesUse this command to show the chosen number of events by category. ExampleConsole# 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# show file-descriptorsTo display information about the Cache Engine's file descriptors, use the Syntax DescriptionThis command has no arguments or keywords. ExampleConsole# 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 show flashTo display the Flash memory content, such as file code names, version numbers, and sizes, use the show flash EXEC command. show flashSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# show flash System flash directory: File Length Name/status 1 1198448 system image [655360 read only, 1460592 bytes used, 5944976 available, 8388608 total] show groupTo 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}}Syntax Description
ExampleConsole# show group gid 1004 GroupName: LocalUsers Gid: 1004 Number of Users in Group: 10 show groupsTo display all groups configured on the Cache Engine, use the show groups EXEC command. show groupsSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# show groups
There are 4 groups(s)
GID GROUPNAME
0 root
1000 everyone
1001 nogroup
1004 LocalUsers
show hardwareTo display system hardware status, use the show hardware EXEC command. show hardwareSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# 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. Related Commandsshow version show hostsTo view the hosts on your Cache Engine, use the show hosts EXEC command. show hostsSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# 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 show httpTo 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}Syntax Description
ExampleConsole# 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
show icpTo display the ICP client, root, or server information, use the show icp EXEC command. show icp {client | root | server}Syntax Description
ExampleConsole# 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 Related Commandsicp client icp server show inetdTo display TCP/IP services that include echo, discard, chargen, FTP, RCP, Telnet, and TFTP, use the show inetd EXEC command. show inetdSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# 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 Related Commandsinetd show interfaceTo display hardware interfaces, use the show interface EXEC command. show interface {ethernet number | scsi number}Syntax Description
ExampleConsole# 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)
Related Commandset interface show ip routesTo display the IP routing table, use the show ip routes EXEC command. show ip routesSyntax Description
Exampleconsole# 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 ---------------------------------------------------------------------------- Related Commandsip route no ip route show loggingTo display the system message log configuration, use the show logging EXEC command. show loggingSyntax DescriptionThis command has no arguments or keywords. Exampleconsole# 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
show memoryTo display memory blocks and statistics, use the show memory EXEC command. show memory [free]Syntax Description
ExampleConsole# 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 show ntpTo display the Network Time Protocol (NTP) parameters, use the show ntp EXEC command. show ntp statusSyntax Description
ExampleConsole# show ntp status NTP subsystem ------------- servers: Related Commandsntp clock set clock timezone show processesTo display CPU or memory processes, use the show processes EXEC command. show processes [cpu | memory]Syntax Description
ExampleConsole# 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--
show radius-serverTo show RADIUS information, use the show radius EXEC command. show radius-serverSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# 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
show running-configTo display the current running configuration information on the terminal, use the show running-config EXEC command. This command replaces the Syntax DescriptionThis command has no arguments or keywords. Usage GuidelinesUse this command in conjunction with the show startup-config command to compare the information in running memory to the startup configuration used during bootup. ExampleConsole# 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 Related Commandsconfigure copy running-config copy startup-config show snmpTo check the status of SNMP communications, use the show snmp EXEC command. show snmpSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesThis command provides counter information for SNMP operations. ExampleConsole# 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. Table A-2: show snmp Field Descriptions
Related Commandssnmp-server chassis-id show stacktraceTo get stack trace information from your Cache Engine, use the show stacktrace EXEC command. show stacktrace {task-ID | exception}Syntax Description
ExampleConsole# show stacktrace exception show startup-configTo show the configuration, use the show startup-config EXEC command. show startup-configSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesUse this command to display the configuration used during an initial bootup, stored in NVRAM. ExampleConsole# 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 Related Commandsconfigure copy running-config show running-config show statisticsTo 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}Syntax Description
Usage GuidelinesTo clear statistics without affecting configurations, use the clear statistics command. This will set all counters to zero. ExampleConsole# 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
Related Commandsclear statistics show tcpTo display TCP configuration information, use the show tcp EXEC command. show tcpSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# 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 show tech-supportTo view information necessary for Cisco's Technical Assistance Center (TAC) to assist you, use the show tech-support EXEC command. show tech-support [page]Syntax Description
Usage GuidelinesUse 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. ExampleConsole# 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--- show tftp-serverUse this command to display configured TFTP directories. show tftp-serverSyntax DescriptionThis command has no arguments or keywords. Usage GuidelinesExampleconsole#show tftp-server
== TFTPD Directory List ==
/local/public
show transaction-loggingTo show the transaction log summaries or to show transaction log settings, use the show transaction-logging EXEC command. show transaction-logging [entries number]Syntax Description
Usage GuidelinesUse 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. ExampleConsole# 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
show trusted-hostsTo display the name of the Cache Engine trusted hosts, use the Syntax DescriptionThis command has no arguments or keywords. ExampleConsole# show trusted-hosts Trusted Host checking: ON 111.333.123.2/C_Medici 333.222.111.1/Procrustes show url-filterTo display URL filter information, use the show url-filter EXEC command. show url-filter [statistics websense]Syntax Description
ExampleConsole# show url-filter
Websense URL Filtering Lookup enabled
Websense Server = 171.22.11.22
Server Port = 3333
Server Timeout = 5
Allowmode is not enabled.
show userTo display user information for a particular user, use the show user EXEC command. show user {uid number | username name}Syntax Description
Exampleconsole#show user username bwhidney Username : bwhidney Uid : 5013 Number of Groups : 1 Primary Group : everyone (1000) Password : bSzyydQbSb Comment : HomeDir : /local Capability : admin-access Related Commandsshow groups show users show usersTo display all users, use the show users EXEC command. show usersSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# show users
There are 2 user(s)
UID USERNAME
0 admin
5013 bwhidney
Related Commandsshow groups show user show versionTo display the current software on your Cache Engine, use the show version EXEC command. show versionSyntax DescriptionThis command has no arguments or keywords. ExampleConsole# 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" show wccpTo display WCCP information, use the show wccp EXEC command. show wccp {cache-engines | router | status}Syntax Description
ExampleConsole# 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-
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||