cc/td/doc/product/webscale/webcache/ce30
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Cisco Cache Software, Release 3.0.0 Commands

Cisco Cache Software, Release 3.0.0 Commands

This chapter contains an alphabetical listing of all commands of the Cisco Cache software, Release 3.0.0

autosense

To enable autosense on an interface, use the autosense interface configuration command. To disable this function, use the no form of this command.

autosense

no autosense

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Interface configuration

Usage Guidelines

Cisco router Ethernet interfaces do not negotiate duplex settings. If the Content Engine is connected to a router directly with a crossover cable, the Content 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 Content Engine to start autosensing.

Examples

Console(config-if)# autosense Console(config-if)# no autosense

bandwidth

To configure an interface bandwidth, use the bandwidth interface configuration command. To disable this function, use the no form of this command.

bandwidth mbits

no bandwidth

Syntax Description

mbits

Bandwidth size in megabits per second (Mbps) (10, 100, or 1000).

Defaults

10 Mbps

Command Modes

Interface configuration

Usage Guidelines

Use this command to set the bandwidth of an interface to 10, 100, or 1000 Mbps.

Examples

Console(config-if)# bandwidth 10 Console(config-if)# no bandwidth

bypass

To enable transparent error handling and dynamic authentication bypass, and to configure static bypass lists, use the bypass command. To disable the bypass feature, use the no form of the command.

bypass {auth-traffic enable | load {enable | in-interval seconds | out-interval seconds | time-interval minutes} | static {clientipaddress {clientipaddress | any-server} | any-client serveripaddress} | timer minutes}

no 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

auth-traffic

Authenticated traffic bypass configuration.

enable

Enables load bypass.

load

Loads bypass configuration.

in-interval

Time interval between buckets coming back.

out-interval

Time interval between bypassing buckets.

time-interval

Time that a bucket is bypassed.

seconds

Time in seconds (4-600).

minutes

Time in minutes (1-1440).

static

Adds a static entry to the bypass list.

any-server

Bypasses HTTP traffic from a specified client to any Web server.

any-client

Bypasses HTTP traffic from any client destined to a particular server.

clientipaddress

IP address of the Web client to be bypassed.

serveripaddress

IP address of the Web server to be bypassed.

timer

Sets timer for authentication bypass, in minutes.

Defaults

The default authentication bypass value is 10 minutes. The in-interval option default is 60 seconds. The out-interval option default is 4 seconds. The timer-interval option default is 10 minutes.

Command Modes

Global configuration

Usage Guidelines

Bypass features are available only with WCCP Version 2. The Content Engine can only bypass WCCP-redirected traffic, not proxy-style requests.

Authentication Bypass

Some Web sites, because of IP authentication, do not allow the Content Engine to connect directly on behalf of the client. In order to avoid a disruption of service, the Content 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 Bypass

If a Content Engine becomes overwhelmed with traffic, it can use the load bypass feature to reroute the overload traffic.

When the Content Engine is overloaded and load bypass is enabled, the Content Engine bypasses a bucket. If the load remains too high, another bucket is bypassed, and so on until the Content 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 Content 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 Content Engine begins to again service the bypassed traffic, it begins with a single bypassed bucket. If the load is serviceable, 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 Bypass

The bypass static command permits traffic from specified sources to bypass the Content 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.

Examples

    Console(config)# bypass static 10.1.17.1 172.10.7.52


    Console(config)# bypass static any-client 172.10.7.52


    Console(config)# bypass static 10.1.17.1 any-server

A static list of source and destination addresses helps to isolate instances of problem-causing clients and servers.

    console# show bypass list Client Server Entry type ------ ------ ---------- 10.1.17.1:0 172.10.7.52:0 static-config any-client:0 172.10.7.52:0 static-config 10.1.17.2:0 any-server:0 static-config
    Total number of HTTP connections bypassed = 0 Connections bypassed due to system overload = 0 Connections bypassed due to authentication issues = 0 Connections bypassed due to facilitate error transparency = 0 Connections bypassed due to static configuration = 0 Total number of entries in the bypass list = 3 Number of Authentication bypass entries = 0 Number of Error bypass entries = 0 Number of Static Configuration entries = 3

Related Commands

show bypass

cache

To synchronize the cache file system (cfs) contents from memory to disk, use the cache synchronize EXEC command.

cache {clear [force] | reset | synchronize}

To clear the disk of all cached content, use the cache clear EXEC command.

Syntax Description

clear

Clears the cache.

force

Forcefully deletes all cached objects.

reset

Resets the cache.

synchronize

Synchronizes the cache.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

The cache clear command removes all cached contents from the currently mounted cfs volumes. Objects being read or written are removed when they cease being "busy." The equivalent to this command is the clear cache or cfs clear command.


Caution   This command is irreversible, and all cached content will be erased.

The cache clear force deletes all objects, whether busy or not, and may generate broken GIF or HTML messages for objects that were being read from the disk when the command was executed. If an object is being written to the Content 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 Content Engine is operating, this command can be used to ensure all data is written to disk before you reset or turn off the Content Engine. Synchronization can also be done using the cfs sync command.

Examples

Console# cache clear force

Related Commands

clear cache

cfs clear

cd

To change directory, use the cd EXEC command.

cd directoryname

Syntax Description

directoryname

Name of the directory.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

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

Examples

Relative path:

Console# cd local1

Absolute path:

Console# cd /local1

Related Commands

dir

lls

ls

mkdir

pwd

rmdir

cfs

To manipulate the cache object file system of the Content Engine, use the cfs EXEC command.

cfs {clear diskname [force] | format diskname | mount diskname | reset diskname | sync
diskname | unmount diskname}

Syntax Description

clear

Deletes nonbusy objects from the specified cfs volume.

force

Forcibly deletes all objects from the specified cfs volume.

format

Erases and formats or creates a file system for caching.

mount

Mounts a cache file system.

reset

Resets (unmounts-formats-mounts) a cache file system.

sync

Synchronizes a cache file system.

unmount

Unmounts a cache file system.

diskname

Disk name (for example, disk00, disk01).

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Cache objects retrieved from the Web are saved and manipulated with the cache file system (cfs) on a cfs partition of the hard disk. This does not affect the sysfs partition, which saves user data, such as syslog output.

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 or HTML message to the client.

The cfs clear force command deletes all objects, busy or nonbusy, and may generate broken GIF or HTML messages for objects that were being read from the disk when the command was executed. If an object is being written to the Content 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 or HTML messages for objects that are being read from the disk (cache hits) when the command is executed. When a cfs volume is reset, all cfs data on that volume is lost.


Note   The cfs reset command can be invoked on unmounted volumes.

The cfs format command creates the cache file system internal "dbs" for the cfs partition of the disk if the volume is unmounted. It formats the cfs partition to prepare it for a cfs mount. The cfs mount command creates and maps data structures in memory to the cfs partition.


Caution   All cached content is erased with the format command.

The cfs unmount command frees the in-memory data structures that map to the physical (disk) cfs partition.

The cfs sync command synchronizes the cache file system contents from memory to disk. Although synchronization is performed at regular intervals while the Content Engine is running, this command can be used to ensure that all data is written to disk before you reset or turn off the Content Engine. Synchronization can also be done with the cache sync command.

Examples

Console# cfs sync disk05

Related Commands

show cfs

cache clear

clear cache

check

To check whether superuser accounts are password-protected, use the check EXEC command.

check superuser passwords

Syntax Description

superuser

Keyword.

passwords

Keyword.

Defaults

By default, superuser accounts are not password-protected.

Command Modes

EXEC

Usage Guidelines

This command displays whether or not the superuser account is password-protected. To configure a superuser password, from global configuration mode, use the user modify command. A superuser is defined as an administrator or user with full read and write privileges to the cache files and utilities.

Examples

Console# check superuser passwords ---------------------------------------------------------------------- All super-user accounts are password protected ----------------------------------------------------------------------

Related Commands

user modify

show user

clear

To clear the HTTP object cache, the hardware interface, statistics, transaction logs, or WCCP settings, use the clear EXEC command.

clear {bypass {counters | list} | cache [force] | dns-cache | interface serial number | logging | statistics {all | dns-cache | ftp | history | http {all | errors | ims | object | requests | response | savings} | https | icp {all | client | cluster | server}} | running | tcp | transaction-logs} | transaction-log}

Syntax Description

bypass

Selects bypass clear commands.

counters

Clears all bypass counters.

list

Clears all bypass lists.

cache

Clears the HTTP object cache.

force

Forcefully deletes all cached objects.

dns-cache

DNS clear commands.

interface serial

Clears serial interface.

number

Interface number (0-4294967295).

logging

Clears syslog messages saved in disk file.

statistics

Clears statistics.

all

Clears all statistics.

dns-cache

Clears DNS cache statistics.

ftp

Clears FTP caching statistics.

history

Clears the statistics history.

http

Clears HTTP statistics.

all

Clears all HTTP statistics.

errors

Clears HTTP errors statistics.

ims

Clears HTTP if-modified-since (IMS) statistics.

object

Clears HTTP object statistics.

requests

Clears HTTP requests statistics.

response

Clears HTTP response statistics.

savings

Clears HTTP savings statistics.

https

Clears HTTPS statistics.

icp

Selects ICP statistics.

all

Clears all ICP statistics.

client

Clears ICP client statistics.

cluster

Clears ICP cluster statistics.

server

Clears ICP server statistics.

running

Clears the running statistics.

tcp

Clears TCP statistics.

transaction-logs

Clears transaction-log export statistics.

transaction-log

Archives working transaction log file.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

The clear cache command removes all cached contents from the currently mounted cfs volumes. Objects being read or written are removed when they cease being "busy." The equivalent to this command is the cache clear or cfs clear command.


Caution   This command is irreversible and all cached content will be erased.

The clear cache force command deletes all objects, whether busy or not, and may generate broken GIF or HTML messages for objects that were being read from the disk when the command was executed. If an object is being written to the Content Engine disk when a clear cache force command is executed, the application stops caching that object but still delivers the object from the Web server to the client.

The clear interface command clears the statistics presented by the show interface command.

The clear statistics command clears all statistical counters from the parameters given. Use this command to monitor fresh statistical data for some or all features without losing cached objects or configurations.

The clear transaction-log command causes the transaction log to be archived immediately to the Content Engine hard disk. This command has the same effect as the transaction-log force archive command.

Examples

To purge all the entries in the bypass list, use the clear bypass list option.

console# clear bypass list

To force the working transaction log file to be archived, use the clear transaction-log option.

console# clear transaction-log

Related Commands

cache clear

cfs clear

show statistics

show interface

show wccp

clock

To set, clear, or save the battery-backed clock functions, use the clock EXEC command.

clock {read-calendar | set time day month year | update-calendar}

Syntax Description

read-calendar

Reads the calendar and update system clock.

set

Sets the time and date.

time

Current time in hh:mm:ss format (hh: 00-23; mm: 00-59; ss: 00-59).

day

Day of the month (1-31).

month

Month of the year (April, August, December, February, January, July, June, March, May, November, October, September).

year

Year (1993-2035).

update-calendar

Updates the calendar with the system clock.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

If you have an outside source on your network that provides time services (such as a Network Time Protocol [NTP] server), you do not need to set the system clock manually. When setting the clock, enter the local time. The Content Engine calculates Coordinated Universal Time (UTC) based on the time zone set by the clock timezone global configuration command.

Two clocks exist in the system: the software clock and the hardware clock. The software uses the software clock. The hardware clock is used only at bootup to initialize the software clock.

The set keyword sets the software clock.

Examples

Console# clock set 13:32:00 01 February 2000

Related Commands Related Commands

clock timezone

show clock detail

clock timezone

To set the time zone for display purposes, use the clock timezone global configuration command. To disable this function, use the no form of this command.

clock timezone {timezone hoursoff minutesoff}

no clock timezone {timezone hoursoff minutesoff}

Syntax Description

timezone

Name of time zone.

hoursoff

Hours offset from Coordinated Universal Time (UTC) (-23, +23).

minutesoff

Minutes offset from UTC (0-59).

Defaults

No default behavior or values

Command Modes

Global configuration

Usage Guidelines

To set and display the local and UTC current time of day without an NTP server, use the clock timezone command together with the clock set command.

The clock timezone parameter specify the difference between UTC and local time which is set with the clock set command. The UTC and local time are displayed with the show clock detail EXEC command.

Examples

The following example specifies the local time zone as Pacific Standard Time and offsets 8 hours behind UTC:

Console(config)# clock timezone PST -8 Console(config)# no clock timezone

Related Commands Related Commands

clock

show clock detail

configure

To enter global configuration mode, use the configure EXEC command. You must be in global configuration mode to enter global configuration commands.

configure

To exit global configuration mode, use the end, Ctrl-Z, or exit commands.

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to enter global configuration mode.

Examples

Console# configure Enter configuration commands, one per line. End with CNTL/Z. Console(config)#

Related Commands Related Commands

show running-config

show startup-config

end

exit

Ctrl-Z

copy

To copy configuration or image data from a source to a destination, use the copy EXEC command.

copy {disk {flash imagename | startup-config filename} | flash disk imagename | ftp flash {hostname | ipaddress} remotedir remotefilename | running-config {disk filename | startup-config | tftp {hostname | ipaddress} filename} | startup-config {disk filename | tftp {hostname | ipaddress} filename} | tech-support {disk filename | tftp {hostname | ipaddress} filename}} | tftp {disk {hostname | ipaddress} remotefilename localfilename | flash
{hostname | ipaddress} imagename}}

Syntax Description

disk

Copies image or configuration from disk.

flash

Copies image to Flash memory.

imagename

Specifies image filename. Use the complete path name.

startup-config

Copies configuration file from disk to startup configuration (NVRAM).

filename

Specifies name of existing configuration file.

flash disk

Copies image from Flash memory to disk.

imagename

Specifies the name of disk file to be created. Use the complete path name.

ftp flash

Copies image from FTP server to Flash memory.

hostname

Specifies host name of FTP server.

ipaddress

Specifies IP address of FTP server.

remotedir

Specifies the directory on the FTP server where the image file resides.

remotefilename

Specifies the name of the image file.

running-config

Copies current system configuration.

disk

Copies current system configuration to disk.

filename

Specifies name of file to be created on disk.

startup-config

Copies running configuration to startup configuration (NVRAM).

tftp

Copies running configuration to a file on a TFTP server.

hostname

Specifies host name of TFTP server.

ipaddress

Specifies IP address of TFTP server.

filename

Specifies name of configuration file to be created on TFTP server. Use the complete path name.

startup-config

Copies startup system configuration.

disk

Copies startup system to disk.

filename

Specifies name of file to be created on disk.

tftp

Copies startup configuration to a file on a TFTP server.

hostname

Specifies host name of TFTP server.

ipaddress

Specifies IP address of TFTP server.

filename

Specifies name of configuration file to be created on TFTP server. Use the complete path name.

tech-support

Copies system information for technical support.

disk

Copies system information to disk.

filename

Specifies name of file to be created on disk.

tftp

Copies system information to a TFTP server.

hostname

Specifies host name of TFTP server.

ipaddress

Specifies IP address of TFTP server.

filename

Specifies name of system information file to be created on TFTP server. Use the complete path name.

tftp

Copies image from a TFTP server.

disk

Copies a file from a TFTP server to disk.

hostname

Specifies host name of TFTP server.

ipaddress

Specifies IP address of TFTP server.

remotefilename

Specifies the name of the file on the TFTP server. Use the complete path name.

localfilename

Specifies the name of the file to be created on the disk.

flash

Copies an image file from a TFTP server to Flash memory.

hostname

Specifies host name of TFTP server.

ipaddress

Specifies IP address of TFTP server.

imagename

Specifies name of the image file on the TFTP server. Use the complete path name.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use the copy running-config startup-config command to save the configuration to NVRAM memory. This command is equivalent to the write command.

The copy flash disk imagename command will copy the image from Flash memory to the disk.

The copy disk flash imagename command will install 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.

The copy ftp flash command copies an image file from an FTP server to Flash memory.

Examples

The following example copies an image file from an FTP server to the Flash memory of the Content Engine. Once the image is copied to Flash, a reload command is entered to boot the new system.

Console# copy ftp flash 172.22.11.11 /public/software dmdsysimg.b36 Initiating FTP download. . . Downloaded 10685440 byte image file A new system image has been downloaded. You should write it to flash at this time. Write to flash [yes]: y Ok, writing new image to flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console# reload

Related Commands

reload

show running-config

show startup-config

write

cpfile

To copy one filename to another filename, use the cpfile EXEC command.

cpfile oldfilename newfilename

Syntax Description

oldfilename

Name of the old file from which to copy.

newfilename

Name of the new file to copy to.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to copy one filename to another. This command only copies sysfs files.

Examples

Console# cpfile ce500-194616.bin cd500-194618.bin

Related Commands Related Commands

copy

dir

lls

ls

mkfile

rmdir

rmname

debug

debug

Command Modes

EXEC

Usage Guidelines

It is recommended that the debug command be used only at the direction of Cisco Systems technical support personnel.

Related Commands Related Commands

no debug

show debugging

undebug

delfile

To remove a file, use the delfile EXEC command.

delfile filename

Syntax Description

filename

Name of the file to delete.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to remove a file from any directory. Note that some files are necessary for proper functionality and should not be removed.

Examples

Console# delfile /local1/tempfile

Related Commands RelatedCommands

cpfile

deltree

mkdir

mkfile

rmdir

deltree

To remove a directory recursively and all files that it contains, use the deltree EXEC command.

deltree directory

Syntax Description

directory

Name of the directory tree to delete.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to remove a directory and all files within the directory from the Content Engine (sysfs 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.

Examples

Console# deltree /local1/testdir

Related Commands Related Commands

delfile

dir

To view a long list of files in a directory, use the dir EXEC command.

dir [directory]

Syntax Description

directory

(Optional.) Name of the directory to list.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to view a detailed list of files contained within the working directory, including names, sizes, and time created. The equivalent command is lls.

Examples

Console# dir size time of last change name -------------- ------------------------- ----------- 3931934 Tue Sep 19 10:41:32 2000 errlog-cache-20000918-164015 431 Mon Sep 18 16:57:40 2000 ii.cfg 431 Mon Sep 18 17:27:46 2000 ii4.cfg 431 Mon Sep 18 16:54:50 2000 iii.cfg 1453 Tue Sep 19 10:34:03 2000 syslog.txt 1024 Tue Sep 19 10:41:31 2000 <DIR> testdir

Related Commands

ls

lls

disable

To turn off privileged EXEC commands, use the disable EXEC command.

disable

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

The disable command places you in EXEC mode. To turn privileged EXEC mode back on, use the enable command.

Examples

Console# disable

Related Commands Related Commans

enable

disk

To configure the Content Engine disks, use the disk EXEC command.

disk {erase-all-partitions disk name | manufacture disk name | partition disk name {cfs | sysfs} | prepare disk name}

Syntax Description

erase-all-partitions

Disk initialization procedure. Erases the partition on a disk.

manufacture

Reformats all partitions and volumes on a disk as cfs, and mounts the disk.

partition

Partitions the hard disk.

cfs

Cache file system.

sysfs

System file system.

prepare

Partitions and formats volumes on a hard disk.

disk name

Disk name (for example, disk00, disk01).

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

The disk partition option creates a single partition of the entire disk for the specified file system. Use the show disks command to obtain the name, SCSI ID, partition, and mounting status for each disk.


Caution   Partitioning a disk destroys all of its contents. After partitioning, the disk must be formatted as sysfs or cfs.

The disk prepare option automates the preparation of a disk. This command partitions, formats, and mounts a disk as a cfs volume.

The disk manufacture command initializes a disk for use by the Content Engine or the Storage Array, and must be run on each disk before that disk is used by the Content Engine for the first time. The specified disk is partitioned, formatted, and mounted as a cfs volume. The disk manufacture command needs to be executed only once for each disk.


Note   The disk manufacture command is executed on each internal Content Engine disk by Cisco Systems prior to shipping.

Cisco Storage Array Guidelines

Targets 2 through 13 are assigned to Storage Array disk drives. The leftmost hard disk inserted in a Storage Array bus is always target 2. Counting to the right, the next disk is target 3, the next disk is
target 4, and so on. There can be empty slots between targets on the same bus, but this is not recommended. In a two-host, split-bus configuration, each bus is counted independently.

For example, in a split-bus, six-disk, fully populated Storage Array, bus 0 disk drive targets are 2, 3, and 4, and bus 1 disk drive targets are 2, 3, and 4. If the first disk on bus 1 is removed (slot 5 is empty) and the Content Engine rebooted, bus 0 targets are still 2, 3, and 4, but bus 1 targets are 2 and 3. The empty disk slot is skipped, and the target count begins with the first detected disk on bus 1.

Once a disk drive has been partitioned and formatted, it can be used in any Storage Array slot, but moving a disk drive from one slot to another makes the data it contains unusable to the Content Engine. Power cycle the Content Engine if the following actions occur while the Storage Array is in operation:

Examples

In the following example, Console1 and Console2 are Content Engine 590 machines running software release 3.0.0. Refer to the Cisco Storage Array Installation and Configuration Guide for further information on configuring the Storage Array.


Note   The larger the storage capacity of the disk drive, the longer the duration of the disk manufacture routine.

In this example, six Storage Array disk drives are initialized in a single-host, joined-bus Storage Array configuration.

Console1#show disks disk00 (scsi host 0, channel 0, id 0) disk01 (scsi host 0, channel 0, id 1) disk02 (scsi host 0, channel 0, id 8) disk03 (scsi host 0, channel 0, id 9) disk04 (scsi host 0, channel 0, id 10) disk05 (scsi host 0, channel 0, id 11) disk06 (scsi host 0, channel 0, id 12) disk07 (scsi host 0, channel 0, id 13)

Console1# disk manufacture disk02 Console1# disk manufacture disk03 Console1# disk manufacture disk04 Console1# disk manufacture disk05 Console1# disk manufacture disk06 Console1# disk manufacture disk07

In the following example, Console1 is connected to the SCSI 0 connector of the Storage Array, and Console2 is connected to the SCSI 1 connector.

The disks of a fully populated six-disk Storage Array are initialized in a two-host, split-bus configuration.

Console1# disk manufacture disk02 Console1# disk manufacture disk03 Console1# disk manufacture disk04 Console2# disk manufacture disk02 Console2# disk manufacture disk03 Console2# disk manufacture disk04

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

Transaction logs must be written to a sysfs volume. The following example creates a sysfs partition on the first disk on the SCSI bus, formats the partition, and mounts the volume /local1:

Console# disk erase-all-partitions disk00 Console# disk partition disk00 sysfs Console# sysfs format disk00 Console# sysfs mount disk00 /local1

Related Commands

cfs

sysfs

disk

show disk-partitions

show disks

dns-cache

To configure the DNS cache, use the dns-cache global configuration command. To disable the DNS cache, use the no form of this command.

dns-cache size maxsize

no dns-cache size

Syntax Description

size

Sets the DNS cache size.

maxnumber

Specifies maximum number of cache records (4096-65536).

No default behavior or value

Command Modes

Global configuration

Usage Guidelines

Cache size refers to the maximum number of DNS cache entries. Domain name resolution requires that at least one DNS name server be configured with the ip name-server command. The DNS cache goes online when the ip name-server command is configured, and goes offline when the last IP name-server configuration is deleted with the no ip name-server ip-address command.

Examples

Console(config)# dns-cache size 20000 Console(config)# no dns-cache size

Related Commands Related Comands

ip name-server

clear dns-cache

dnslookup

show statistics dns-cache

dnslookup

Use the dnslookup EXEC command to resolve a host or domain name to an IP address.

dnslookup {host | domain-name}

Syntax Description

host

Name of host on network.

domain_name

Domain name.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# dnslookup myhost official hostname: myhost.cisco.com address: 172.41.69.11 Console#dnslookup cisco.com official hostname: cisco.com address: 198.133.219.25 Console#dnslookup 41.69.11 official hostname: 41.69.11 address: 41.69.0.11

enable

To turn on privileged EXEC commands, use the enable EXEC command.

enable

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

To return to privileged EXEC mode from user EXEC mode, use the enable command.

The disable command takes you from privileged EXEC mode back to user EXEC mode.

Examples

Console> enable Console#

Related Commands Related Commands

disable

end

To exit global configuration mode, use the end global configuration command.

end

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Global configuration

Usage Guidelines

Use the end command to exit global configuration mode after completing any changes to the running configuration. To save new configurations to NVRAM, use the write command.

The Ctrl-Z command also exits global configuration mode.

Examples

Console(config)# end Console#

Related Commands Related mands

exit

Ctrl-Z

error-handling

Use the error-handling command to set error-handling options.

error-handling {reset-connection | send-cache-error | transparent}

Syntax Description

reset-connection

Resets TCP connection without specifying any error.

send-cache-error

Sends Content Engine error.

transparent

Makes the Content Engine transparent to the client.

Defaults

No default behavior or values

Command Modes

Global configuration

Usage Guidelines

With the transparent option enabled, end users can receive browser-generated messages rather than a Content Engine-generated HTML page for errors that the Content Engine encounters while processing a client request or response. Thus, the Content Engine remains transparent (invisible) to the end user.

Transparent error reporting is implemented as follows:

To make the source of the error messages transparent to the user, the client/server pair is added to the bypass list and an HTTP redirect message is sent to the client, requesting the client to redirect the request to the same URL as before. The client, on receiving the redirect message, sends back the request once again. This time, the request is bypassed by the Content Engine because the client/server pair is on the bypass list. The request now goes to the server directly. Since the connection was not accepted by the Content Engine, any timeout error, failure to connect to the server, or mangled response from the server is handled by the browser. Currently all entries on the bypass list are kept for a configurable period of time (for example, 5 minutes).

When an internal failure in the Content Engine occurs while it is processing a request, a reset is sent back to the client and the connection is closed. This is because memory is needed to add the client/server pair to the bypass list. When a browser receives a connection reset, it pops up a "Connection Reset By Peer" alert box.

For all error conditions, the Content Engine sends back a reset and closes the connection. It does not send back any error pages. All errors seen by the clients are in the familiar browser error format.

The Content Engine sends back HTML error pages. When clients are using the Content Engine as an incoming proxy server, they will receive the HTML error pages generated by the clients.

Examples

console# error-handling transparent

exec-timeout

To configure the length of time that an inactive terminal session window will remain open, use the exec-timeout global configuration command. To disable the exec timeout, use the no form of this command.

exec-timeout timeout

no exec-timeout

Syntax Description

timeout

Timeout in minutes (0 to 44,640).

Defaults

The default is 150 minutes.

Command Modes

Global configuration

Syntax Description Usage Guidlines

Use this command to establish the length of time, in minutes, that an inactive terminal session window will remain open. The default is 150 minutes.

Examples

Console(config)# exec-timeout 100 Console(config)# no exec-timeout

exit

To exit any configuration mode or close an active terminal session and terminate an EXEC mode session, use the exit EXEC command.

exit

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC, global, and interface configuration

Usage Guidelines

Use the exit command in global configuration mode to return to EXEC mode. You can also press Ctrl-Z or use the end command from any configuration mode to return to EXEC mode.

Use the exit command in EXEC command mode to close an active terminal session and terminate the EXEC mode session.

Examples

Console# exit

Related Commands Relateands

end

ftp

Use the ftp global configuration command to configure FTP caching services on the Content Engine. Use the no form of the command to selectively disable options.

ftp {age-multiplier directory-listing dl_time file fo_time | max-ttl {days directory-listing dlmax_days file fmax_days | hours directory-listing dlmax_hours file fmax_hours | minutes directory-listing dlmax_ min file fmax_min | seconds directory-listing dlmax_ sec file fmax_sec} | min-ttl min_minutes | object max-size size | proxy {anonymous-pswd passwd | incoming port | outgoing host {hostname | ipaddress} port | reval-each-request {all | directory-listing | none} | serve-ims directory-listing age_percent file age_percent}

no ftp {age-multiplier directory-listing dl_time file fo_time | max-ttl {days directory-listing dlmax_days file fmax_days | hours directory-listing dlmax_hours file fmax_hours | minutes directory-listing dlmax_ min file fmax_min | seconds directory-listing dlmax_ sec file fmax_sec} | min-ttl min_minutes | object max-size size | proxy {anonymous-pswd passwd | incoming port | outgoing host {hostname | ipaddress} port | reval-each-request {all | directory-listing | none} | serve-ims directory-listing age_percent file age_percent}

Syntax Description

age-multiplier

FTP caching heuristic modifiers.

directory-listing

Heuristic modifier for directory listing objects.

dl_time

Expiration time of directory listing objects as a percentage of their age (0-100). The default is 30.

file

Heuristic modifier for file objects.

fo_time

Expiration time of file objects as a percentage of their age (0-100).
The default is 60.

max-ttl

Sets maximum Time To Live for objects in the cache.

days

Sets maximum Time To Live units in days.

directory-listing

Sets maximum Time To Live for directory listing objects in days.

dlmax_days

Specifies maximum Time To Live in days for directory listing objects (1-1825). The default is 7 days.

file

Sets maximum Time To Live for file objects in days.

fmax_days

Specifies the maximum Time To Live in days (1-1825). The default is 3 days.

hours

Sets maximum Time To Live units in hours.

directory-listing

Sets maximum Time To Live for directory listing objects in hours.

dlmax_hours

Specifies maximum Time To Live for directory listing objects in hours (1-43800). The default is 72 hours.

file

Sets maximum Time To Live for file objects in hours.

fmax_hours

Specifies the maximum Time To Live for file objects in hours (1-43800).
The default is 168 hours.

minutes

Sets maximum Time To Live units in minutes.

directory-listing

Sets maximum Time To Live for directory listing objects in minutes.

dlmax_ min

Specifies the maximum Time To Live for directory listing objects in minutes (1-2628000). The default is 4320 minutes.

file

Sets maximum Time To Live for file objects in minutes.

fmax_min

Specifies the maximum Time To Live for file objects in minutes (1-2628000). The default is 10080 minutes.

seconds

Sets maximum Time To Live units in seconds.

directory-listing

Sets maximum Time To Live for directory listing objects in seconds.

dlmax_ sec

Specifies the maximum Time To Live for directory listing objects in seconds (1-157680000). The default is 259200 seconds.

file

Sets maximum Time To Live for file objects in seconds.

fmax_sec

Specifies the maximum Time To Live for file objects in seconds (1-157680000). The default is 604800 seconds.

min-ttl

Sets minimum Time To Live for FTP objects in cache.

min_minutes

Specifies the minimum Time To Live in minutes for FTP objects in cache (0-86400).

object

Sets configuration of FTP objects.

max-size

Sets maximum size of a cachable object.

size

Specifies the maximum size of a cachable object in kilobytes (KB) (1-1048576).

proxy

Sets proxy configuration parameters.

anonymous-pswd

Sets anonymous password string (for example, wwwuser@cisco.com).

passwd

Specifies the anonymous password. The default is anonymous@hostname.

incoming

Sets the incoming port for proxy-mode requests.

port

Specifies up to eight ports to listen for requests (1-65535).

outgoing

Sets parameters to direct outgoing FTP requests to another proxy server.

host

Sets outgoing FTP proxy host parameters.

hostname

Specifies the host name of the outgoing FTP proxy.

ipaddress

Specifies the IP address of the outgoing FTP proxy.

port

Specifies the port of the outgoing FTP proxy (1-65535).

reval-each-request

Sets scope of revalidation for every request.

all

Revalidates all objects on every request.

directory-listing

Revalidates directory listing objects on every request.

none

Does not revalidate for each request.

serve-ims

Sets the handling of if-modified-since requests.

directory-listing

Modifies handling of if-modified-since requests for directory listing objects.

age_percent

Specifies the percentage of age to serve the object without revalidation (0-100). The default is 50.

file

Modifies handling of if-modified-since requests for file objects.

age_percent

Specifies percentage of age to serve the object without revalidation (0-100). The default is 80.

Defaults

Command Modes

Global configuration

Usage Guidelines

The Content Engine can handle ftp:// style FTP requests over HTTP transport in proxy mode.

When the Content Engine receives an FTP request from the Web client, it first looks in its cache. If the object is not in its cache, it fetches the object from an upstream FTP proxy server (if one is configured), or directly from the origin FTP server.

The Content Engine caches both the FTP file objects and directory listings. The content (directory listings and files) is stored in the cfs.

The FTP proxy supports passive and active mode for fetching files and directories. Passive mode is the default. The Content Engine automatically changes to active mode if passive mode is not supported by the FTP server.

The FTP proxy supports anonymous as well as authenticated FTP requests. Only base64 encoding is supported for authentication. The FTP proxy accepts all FTP URL schemes defined in RFC 1738. In the case of a URL in the form ftp://user@site/dir/file, the proxy sends back an authentication failure reply and the browser supplies a popup window for the user to enter login information.

The FTP proxy supports commonly used MIME types, attaches the corresponding header to the client, chooses the appropriate transfer type (binary or ASCII), and enables the browser to open the FTP file with the configured application. For unknown file types, the proxy uses binary transfer as the default and instructs the browser to save the download file instead of opening it. The FTP proxy returns a formatted directory listing to the client if the FTP server replies with a known format directory listing. The formatted directory listing has full information about the file or directory and provides the ability for users to choose the download transfer type.

The Content Engine caches FTP traffic only when the client uses the Content Engine as a proxy server for FTP requests. All FTP traffic that was sent directly from the Web client to an FTP server, if transparently intercepted by the Content Engine, is treated as non-HTTP traffic.

The FTP proxy supports up to eight incoming ports. It can share the ports with transparent-mode services and also with the other proxy-mode protocols supported by the Content Engine, such as HTTP and HTTPS. In proxy-mode, the Content Engine accepts and services the FTP requests only on the ports configured for FTP proxy. All the FTP requests on other proxy mode ports are rejected in accordance with the error-handling settings on the Content Engine.

The Content Engine can apply the rules template to FTP requests based on server name, domain name, server IP address and port, client IP address, and URL.

The Content Engine logs FTP transactions in the transaction log, in accordance with the Squid syntax. When URL tracking is enabled, the Content Engine logs FTP transaction information to the syslog. The syslog entries are prefixed with <ftp>.

Examples

This example configures an incoming FTP proxy on ports 8080, 8081, and 9090. Up to eight incoming proxy ports can be configured on the same command line.

Console(config)# ftp proxy incoming 8080 8081 9090

This example removes one FTP proxy port from the list entered in the previous example. Ports 8080 and 9090 remain FTP proxy ports.

Console(config)# no ftp proxy incoming 8081

This example disables all the FTP proxy ports.

Console(config)# no ftp proxy incoming

This example configures an upstream FTP proxy with the IP address 172.76.76.76 on port 8888.

Console(config)# ftp proxy outgoing host 172.76.76.76 8888

This example specifies an anonymous password string for the Content Engine to use when contacting FTP servers. The default password string is anonymous@hostname.

Console(config)# ftp proxy anonymous-pswd newstring@hostname

This example configures the maximum size in kilobytes of an FTP object that the Content Engine will cache. By default, the maximum size of a cachable object is not limited.

Console(config)# ftp object max-size 15000

This example forces the Content Engine to revalidate all objects for every FTP request.

Console(config)# ftp reval-each-request all

This example configures a maximum Time To Live of 3 days in cache for directory listing objects and file objects.

Console(config)# ftp max-ttl days directory-listing 3 file 3

Related Commands

show ftp

fullduplex

To configure an interface for full-duplex operation, use the fullduplex interface configuration command. To disable this function, use the no form of this command.

fullduplex

no fullduplex

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Interface configuration

Usage Guidelines

Use this command to configure an interface for full-duplex operation. Full duplex allows data to travel in both directions at the same time through an interface or a cable. 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.

Examples

Console(config-if)# fullduplex Console(config-if)# no fullduplex

Related Commands Related Commands

halfduplex

gui-server

To disable or specify the number of the Content Engine management graphical user interface (GUI) server port, use the gui-server global configuration command.

gui-server {enable | port port}

no gui-server {enable | port port}

Syntax Description

enable

Enables the graphical user interface.

port

Configures the graphical user interface server port.

port

Port number (1-65535). The default is 8001.

Defaults

The default port is 8001.

Command Modes

Global configuration

Examples

The following example enables the Content Engine management GUI on port 8002.

Console(config)# gui-server enable Console(config)# gui-server port 8002

Related Commands

show gui-server

halfduplex

To configure an interface for half-duplex operation, use the halfduplex interface configuration command. To disable this function, use the no form of this command.

halfduplex

no halfduplex

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Interface configuration

Usage Guidelines

Use this command to configure an interface for half-duplex operation. Full duplex allows data to travel in both directions at the same time through an interface or a cable. A half-duplex setting ensures that data only travels in one direction at any given time. Full duplex is obviously faster, but sometimes the interfaces cannot seem to handle it. If you encounter collisions or other network errors, you may want to configure an interface for half duplex rather than full duplex.

Examples

Console(config-if)# halfduplex Console(config-if)# no halfduplex

Related Commands Related Commands

fullduplex

help

To get online help for the command-line interface, use the help EXEC or global configuration command.

help

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC, global, and interface configuration

Usage Guidelines

You can get help at any point in a command by entering a question mark (?). If nothing matches, the help list will be empty, and you must back up until entering a ? shows the available options.

Two styles of help are provided:

Examples

Console# help

hostname

To configure the Content Engine's network name, use the hostname global configuration command. To reset the host name to the default setting, use the no form of this command.

hostname name

no hostname name

Syntax Description

name

New host name for the Content Engine; the name is case sensitive. The name may be from 1 to 22 alphanumeric characters.

Defaults

The default host name is the Content Engine model number (for example CE590 or CE7320).

Command Modes

Global configuration

Usage Guidelines

Use this command to configure the host name for the Content Engine. The host name is used for the command prompts and default configuration filenames.

Examples

The following example changes the host name to sandbox:

Console(config)# hostname sandbox sandbox(config)#

The following example removes the host name:

Console(config)# no hostname (config)#

http

To configure HTTP-related parameters, use the http global configuration command. To disable HTTP related-parameters, use the no form of this command.

http {age-multiplier {text texttime binary bintime} | anonymizer enable | append {via-header | x-forwarded-for-header} | authenticate-strip-ntlm | cache-authenticated | cache-cookies | cache-miss revalidate | cache-on-abort {enable | max-threshold maxthresh | min-threshold minthresh | percent percenthresh} | max-ttl {days text textdays binary bindays | hours text texthours binary binhours | minutes text textminutes binary binminutes | seconds text textseconds binary binseconds} | min-ttl minutes | object {max-size maxsize | url-validation enable} | persistent-connections {all | client-only | server-only | timeout seconds} | proxy {incoming port | outgoing host {hostname | ipaddress} port} | reval-each-request {all |
none | text}}

no http {age-multiplier {text texttime binary bintime} | anonymizer enable | append {via-header | x-forwarded-for-header} | authenticate-strip-ntlm | cache-authenticated | cache-cookies | cache-miss revalidate | cache-on-abort {enable | max maxthresh | min minthresh | percent percenthresh} | max-ttl {days text textdays binary bindays | hours text texthours binary binhours | minutes text textminutes binary binminutes | seconds text textseconds binary binseconds} | min-ttl minutes | object {max-size maxsize | url-validation enable} | persistent-connections {all | client-only | server-only} | proxy {incoming port | outgoing host {hostname | ipaddress} port} | reval-each-request {all | none | text}}

Syntax Description

age-multiplier

HTTP/1.0 caching heuristic modifiers.

text

Heuristic modifier for text object.

texttime

Expiration time of text objects as a percentage of their age (0-100).

binary

Heuristic modifier for binary object.

bintime

Expiration time of binary objects as a percentage of their age (0-100).

anonymizer enable

Sets HTTP anonymizer.

append

Configures HTTP headers to be appended by the Content Engine.

via-header

Includes "Via" header in responses and replies.

x-forwarded-for-header

Notifies Web server of client's IP address through "X-Forwarded-For" header.

authenticate-strip-ntlm

Strips NT LAN Manager (NTLM) authentication headers.

cache-authenticated

Caches and revalidates authenticated Web objects.

cache-cookies

Caches Web objects with associated cookies.

cache-miss

Configuration for the handling of "no-cache" requests.

revalidate

Revalidates the object with the origin before serving.

cache-on-abort

Sets cache-on-abort configuration options.

enable

Enables cache-on-abort feature.

max-threshold

Sets maximum threshold.

maxthresh

Value in kilobytes of maximum threshold (1-99999). Default is 256.

min-threshold

Sets minimum threshold.

minthresh

Value in kilobytes of minimum threshold (1-99999). Default is 32.

percent

Sets percent threshold.

percenthresh

Percentage value (1-99). Default is 80 percent.

max-ttl

Maximum Time To Live for objects in the cache.

text

Sets maximum Time To Live for text objects.

binary

Sets maximum Time To Live for binary objects.

days

Sets maximum Time To Live for units in days.

hours

Sets maximum Time To Live for units in hours.

minutes

Sets maximum Time To Live for units in minutes.

seconds

Sets maximum Time To Live for units in seconds.

hours

Maximum Time To Live for units in hours.

minutes

Maximum Time To Live for units in minutes.

seconds

Maximum Time To Live for units in seconds.

min-ttl

Sets minimum Time To Live for objects in the cache.

minutes

Minimum Time To Live in minutes (0-86400).

object

Sets URL validation and maximum size of HTTP objects.

max-size

Sets the maximum size of a cachable object.

maxsize

Specifies maximum size of a cachable object in kilobytes (1-204800).

url-validation enable

Enables each HTTP validation request.

persistent-connections

Sets persistent connections configuration options.

all

Makes client and server connection persistent.

client-only

Makes only a client connection persistent.

server-only

Makes only a server connection persistent.

timeout

Sets persistent connections timeout value.

seconds

Specifies persistent connections timeout in seconds (1-86400).

proxy

Configuration parameters for proxy mode.

incoming

Configuration for incoming proxy mode requests.

port

Port on which to listen for incoming HTTP proxy requests (1-65535). Default is port 8080.

outgoing

Configuration to direct outgoing request to another proxy server.

host

Uses outgoing HTTP proxy.

hostname

Host name of outgoing proxy.

ipaddress

IP address of outgoing proxy.

port

Port number of outgoing proxy (1-65535).

reval-each-request

Configuration of revalidation for every request.

all

Revalidates all objects on every request.

none

Does not revalidate objects for each request.

text

Revalidates text objects on every request.

Defaults

Command Modes

Global configuration

Usage Guidelines

Use these commands to configure specific parameters for caching HTTP objects.


Note   Text objects refer to HTML pages. Binary objects refer to all other Web objects (for example, GIFs or JPEGs).

If a cached object's HTTP header does not specify an expiration time, the age-multiplier and max-ttl options provide a means for the Content Engine to age cached objects. The Content 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  percent for text and 60 percent for binary objects. After the expiration date, the object is considered stale and subsequent requests result in a fresh retrieval by the Content Engine.

The max-ttl option 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 cache-cookies option enables the Content Engine to cache binary content served with HTTP set-cookies headers and no explicit expiration information.

The cache-authenticated option enables the Content Engine to cache authenticated content. If this command is enabled, the Content Engine will not serve authenticated objects without first revalidating the authentication header attached to the cached object.

The reval-each-request option enables the Content Engine to revalidate all objects requested from the cache, text objects only, or none at all.

The cache-miss revalidate option revalidates a cache-miss request forced by the client (Shift-reload).

Use the object max-size option to specify the maximum size in kilobytes of a cachable object. The default is no maximum size for a cachable object. The no form of the command resets the default value.

The proxy mode option enables the Content 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 option.

To configure the Content Engine to direct all HTTP miss traffic to a parent cache (without using ICP or WCCP), use the proxy outgoing hostname port option, in which 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 cache-on-abort option provides user-defined thresholds to determine whether or not the Content 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 Content Engine or counted in the hit-rate statistics. Client abort processing occurs when a client of the Content Engine aborts the download of a cachable 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 Content Engine always aborts downloading an object to the cache. If the Content Engine determines that there is another client currently requesting the same object, downloading is not aborted. The Content Engine only applies those thresholds that have been enabled.

The http proxy outgoing option can configure backup proxy servers for HTTP proxy failover. Failover to a proxy server occurs in the order the proxy servers were configured. Up to eight outgoing proxy servers can be configured for a single Content Engine.

Requests with a destination specified in the proxy-protocols outgoing-proxy exclude option bypass the Content Engine proxy as well as the failover proxies.

When an HTTP request intended for another proxy server is intercepted by the Content Engine in transparent mode, the Content Engine forwards the request to the intended proxy server if the proxy-protocols transparent original-proxy command was entered.

The proxy failover feature currently supports only HTTP, and not HTTPS or FTP.

The persistent-connections enable command enables persistent connections on the Content Engine.

The http object url-validation option has a dependency with the ip name-server CLI command. When the ip name-server option is not configured (for example, during transparent proxy), http object url-validation is dynamically turned off. When the ip name-server option is configured, http object url-validation is turned on automatically if and only if it was enabled.


Caution   URL validation is on by default. Cisco Systems strongly recommends that you keep URL validation enabled, because disabling URL validation might make the Content Engine vulnerable to corruption from the HTTP objects in the cache.

Examples

Console# show statistics http requests Statistics - Requests Total % of Requests --------------------------------------------------- Total Received Requests: 0 - Forced Reloads: 0 0.0 Client Errors: 0 0.0 Server Errors: 0 0.0 Sent to Outgoing Proxy: 0 0.0 Excluded from Outgoing Proxy: 0 0.0 ICP Client Hits: 0 0.0 ICP Server Hits: 0 0.0 HTTP 0.9 Requests: 0 0.0 HTTP 1.0 Requests: 0 0.0 HTTP 1.1 Requests: 0 0.0 HTTP Unknown Requests: 0 0.0 Non HTTP Requests: 0 0.0 Non HTTP Responses: 0 0.0 Chunkes HTTP Responses: 0 0.0 Http Miss Due To DNS: 0 0.0 Http Deletes Due To DNS: 0 0.0 Objects cached for min ttl: 0 0.0 Console# show statistics http usage Statistics - Usage Current Peak ----------------- CPU Usage: 0 % 2 % Disk Usage: Disk 0 0 % 0 % Disk 1 0 % 0 % HTTP Requests: active 0 0 idle client 0 0 idle server 0 0 Requests when all proxies were failed: 0 Console(config)# http age-multiplier text 30 bin 60 Console(config)# http reval-each-request text Console(config)# no http age-multiplier text 30 bin 60 Console(config)# no http reval-each-request text
    Console(config)# http cache-on-abort enable
    Console(config)# no http cache-on-abort
    Console(config)# http cache-on-abort min-threshold 16
    Console(config)# no http cache-on-abort min-threshold
The cache-on-abort max and percent thresholds are configured in the same way as the minimum threshold shown in the examples.

Related Commands

proxy-protocols

show http

show http proxy

show statistics http requests

https

Use the https global configuration command to configure the Content Engine for HTTPS proxy services.

https proxy {incoming port | outgoing {host hostname | address} port}

no https proxy {incoming port | outgoing {host hostname | address} port}

Syntax Description

proxy

Sets configuration parameters for proxy mode.

incoming

Sets configuration for incoming proxy-mode requests.

port

Port number on which to listen for HTTPS requests (1-65535).

outgoing

Sets configuration to direct outgoing requests to another proxy server.

host

Uses outgoing HTTPS proxy.

hostname

Host name of outgoing proxy.

address

IP address of outgoing proxy.

port

Port of outgoing proxy (1-65535).

Defaults

No default behavior or values

Command Modes

Global configuration

Usage Guidelines

HTTPS Proxy Features Related CLI Commands (Abbreviated Syntax)

Supports a single proxy on the specified port

https proxy incoming port_1-65535

Shares proxy port with transparent services

Configures a WCCP service and an HTTPS incoming proxy on the same port.
https proxy incoming port_1-65535
wccp custom-web-cache . . .

Configures outgoing HTTPS proxy server, uses global exclude option for HTTPS proxy

proxy-protocols outgoing-proxy exclude domain_name
https proxy outgoing host {hostname | ip_address} port_1-65535

Original versus default outgoing HTTPS proxy decision process

proxy-protocols transparent {default-server | original-proxy}

Handles in transparent mode an HTTPS request bound for another proxy host

proxy-protocols transparent {default-server | original-proxy}

The order in which the CLI commands are entered is not important.

Cisco Cache software Release 3.0.0 supports HTTPS in the following two scenarios:

In both cases the Content Engine creates a connection to the origin server (directly or through another proxy server) and allows the Web client and origin server to set up an SSL tunnel through the Content Engine.

HTTPS traffic is encrypted and cannot be interpreted by the Content Engine or any other device between the Web client and the origin server. HTTPS objects are not cached.

The Content Engine as an HTTPS proxy server supports up to eight ports. It can share the ports with transparent-mode services and with HTTP. In proxy mode, the Content Engine accepts and services the HTTPS requests on the ports specified with the https proxy incoming command. All HTTPS requests on other proxy-mode ports are rejected in accordance with the error-handling settings on the
Content Engine. In transparent mode, all HTTPS proxy-style requests intended for another HTTPS proxy server are accepted. The Content Engine acts on these transparently received requests in accordance with the proxy-protocols transparent command.

When the Content Engine is configured to use an HTTPS outgoing proxy with the https proxy outgoing host command, all incoming HTTPS requests are directed to this outgoing proxy. The proxy-protocols outgoing-proxy exclude command specifies a global proxy exclude domain effective for all proxy server protocols including HTTPS. The Content Engine applies the following logic when an outgoing proxy server is configured:

When a Content Engine intercepts a proxy request intended for another proxy server and there is no outgoing proxy configured for HTTPS, and the proxy-protocols transparent default-server command is invoked, the Content Engine addresses the request to the destination server directly and not to the client's intended proxy server.

Statistics Reporting

Only connection statistics are reported. Because requests and responses are sent through the secure tunnel, the Content Engine is not able to identify the number of requests sent, or the number of bytes per request. Thus, the request and transaction per second (TPS) statistics are not available for HTTPS.

Transaction Logging

The Content Engine logs HTTPS transactions in the transaction log in accordance with Squid syntax. One log entry is made for each HTTPS connection, though many transactions are performed per connection. The Content Engine is not aware of objects conveyed through the SSL tunnel, only the HTTPS server name.

Syslog and URL Tracking

When URL tracking is enabled, the Content Engine logs HTTPS transaction information to the syslog file. The syslog entries have the prefix <https>. For HTTPS there are no "misses" or "hits." Because the Content Engine ignores objects transferred through an SSL tunnel, there is only one URL tracking entry per HTTPS connection (similar to the transaction log).

Examples

In this example, the Content Engine is configured as an HTTPS proxy server, and accepts HTTPS requests on port 8081. Only a single port is supported the HTTPS protocol.

Console(config)# https proxy incoming 8081

In this example, the Content Engine is configured to forward HTTPS requests to an outgoing proxy server (10.1.1.1) on port 8880.

Console(config)# https proxy outgoing host 10.1.1.1 8880

In this example, a domain name is excluded from being forwarded to an outgoing proxy server.

Console(config)# proxy-protocols transparent default-server Console(config)# proxy-protocols outgoing-proxy exclude cruzio.com

Related Commands

proxy-protocols

http proxy

show proxy-protocols

show http proxy

icp

To configure the Internet Cache Protocol (ICP) client and server, use the icp global configuration command. To disable the ICP client and server, use the no form of this command.

icp {client {{add-remote-server {hostname | ipaddress} {parent | sibling} icp-port icpport http-port httpport [restrict domainnames]} | enable | exclude domainnames | max-fail retries | max-wait timeout | modify-remote-server {hostname | ipaddress} {http-port port | icp-port port | parent | restrict domainnames | sibling}} | server {enable | port icpport | remote-client {hostname | ipaddress} {fetch | no-fetch}}}

no icp {client {{add-remote-server {hostname | ipaddress} {parent | sibling} icp-port icpport http-port httpport [restrict domainnames]} | enable | exclude domainnames | max-fail retries | max-wait timeout | modify-remote-server {hostname | ipaddress} {http-port port | icp-port port | parent | restrict domainnames | sibling}} | server {enable | port icpport | remote-client {hostname | ipaddress} {fetch | no-fetch}}}

Syntax Description

client

Sets ICP client functionality.

add-remote-server

Adds an ICP client remote server.

hostname

Specifes host name of remote server.

ipaddress

Specifies IP address of remote server.

parent

ICP server acts like a parent.

sibling

ICP server acts like a sibling.

icp-port

ICP port.

icpport

Sends remote requests to this ICP port number (0-65535).

http-port

HTTP port.

httpport

Sends HTTP requests to this port number (0-65535).

restrict

Sets restricted list of domains.

domainnames

Specifes space-delimited restricted domain list

enable

Enables the ICP client.

exclude

Excludes ICP client local domains.

domainnames

Specifies space-delimited local domain list.

max-fail

Maximum number of retries allowed.

retries

Number of retries (0-100).

max-wait

Maximum wait for ICP responses before timeout occurs.

timeout

Timeout period for ICP responses in seconds (0-30).

modify-remote-server

Modifies the ICP client remote server parameters.

hostname

Specifes host name of remote server.

ipaddress

Specifies IP address of remote server.

http-port

HTTP port.

port

Sends HTTP requests to this port number (0-65535).

icp-port

ICP port.

port

Sends ICP requests to this port number (0-65535).

parent

ICP remote server acts like a parent.

restrict

Sets restricted list of domains.

domainnames

Specifies space-delimited local domain list.

sibling

ICP remote server acts like a sibling.

server

ICP server functionality.

enable

Enables the ICP server.

port

ICP server port that listens for ICP requests.

icpport

Sends ICP requests to this port number (0-65535).

remote-client

ICP server remote client.

hostname

Specifes host name of remote client.

ipaddress

Specifies IP address of remote client.

fetch

ICP remote client will fetch cache miss.

no-fetch

ICP remote client will not fetch cache miss.

Defaults

No default behavior or values

Command Modes

Global configuration

Usage Guidelines

Use these commands to establish and configure the ICP server and client functionality of the Content 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 Content Engines or ICP servers or clients within the ICP environment to ensure proper service. You can monitor the statistical data of the ICP service using the show statistics icp EXEC command.

Examples

The following example restricts ICP parent and sibling to specific domain sets:

Console(config)# icp client add-remote-server 1.1.1.1 parent icp-port 3130 http-port 3128 domain_x.com domain_y.com domain_z.com Console(config)# icp client add-remote-server 1.1.1.1 sibling icp-port 3130 http-port 3128 domain_a.com domain_b.com domain_c.com Console(config)# icp client enable Icp Client started

Related Commands Related Commands

show icp client

show icp server

show statistics icp

install

To install a new version of Content Engine software, use the install EXEC command.

install paxfilename

Syntax Description

paxfilename

Name of the .pax file you want to install.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Install and run the .pax file from the /local directory only. When the install command is executed, the .pax file is expanded. The expanded files overwrite the existing files in the Content Engine. The newly installed version takes effect after the system image is reloaded.

Examples

Console# install ce25.pax

Related Commands Related Commands

reload

interface

To configure a Fast Ethernet or Gigabit Ethernet interface, use the interface global configuration command. To disable selected options, restore default values, or enable a shutdown interface, use the no form of this command.

interface {FastEthernet slot/port [autosense | bandwidth linespeed | fullduplex | halfduplex |
ip address ipaddress netmask | shutdown ] | GigabitEthernet slot/port [autosense | bandwidth linespeed | fullduplex | halfduplex | ip address ipaddress netmask | shutdown]}

no interface {FastEthernet slot/port [autosense | bandwidth linespeed | fullduplex | halfduplex | ip address ipaddress netmask | shutdown ] | GigabitEthernet slot/port [autosense | bandwidth linespeed | fullduplex | halfduplex | ip address ipaddress netmask | shutdown]}

Syntax Description

FastEthernet

Selects a Fast Ethernet interface to configure.

GigabitEthernet

Selects a GigabitEthernet interface to configure.

slot/port

Specfies slot and port number for the selected interface. Slot is 0-3; port is 0-3. The slot number and port number are separated with a forward slash character (/).

autosense

Sets interface to autosense.

bandwidth

Sets bandwidth of specified interface.

linespeed

Specifies bandwidth of interface in megabits per second (Mbps) (10, 100, 1000).

fullduplex

Sets interface to full-duplex operation.

halfduplex

Sets interface to half-duplex operation.

ip address

Sets IP address and netmask.

ipaddress

Specifies IP address of the interface.

netmask

Specifies netmask of the interface.

shutdown

Shuts down the specified interface.

Defaults

No default behavior or values

Command Modes

Global configuration

Usage Guidelines

To display the interface identifiers (for example, Interface FastEthernet 0/1), use the
show running-config or show startup-config commands. The autosense, bandwidth, fullduplex,
halfduplex, ip, and shutdown commands are listed separately in this command reference.

Examples

The following example configures an attribute of an interface with a single CLI command:

Console(config)# interface FastEthernet 0/1 half-duplex

An interface can be configured in a sequence of CLI commands as follows:

Console(config)# interface FastEthernet 0/1 Console(config-if): ? Configure Interface commands: autosense Interface autosense bandwidth Interface bandwidth exit Exit from this submode full-duplex Interface fullduplex half-duplex Interface halfduplex ip Interface Internet Protocol Config commands no Negate a command or set its defaults shutdown Shutdown the specific interface Console(config-if)# half-duplex Console(config-if)# exit Console(config)#

The following example enables a shutdown interface:

Console(config)# no interface FastEthernet 0/1 shutdown

Related Commands Related Commands

show interface

show running-config

show startup-config

ip

To configure the Content Engine 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

no ip address [ip-address ip-subnet]

Syntax Description

address

Sets the IP address of an interface.

ip-address

IP address.

ip-subnet

IP subnet mask.

Defaults

No default behavior or values

Command Modes

Interface configuration

Usage Guidelines

Use this command to set or change the IP address and subnet mask of the Content Engine network interfaces. The Content Engine requires a reboot in order for the new IP address to take effect.

Examples

Console(config-if)# ip address 10.10.10.10 255.0.0.0 Console(config-if)# no ip address

ip

To change initial network device configuration settings, use the ip global configuration command. To delete or disable these settings, use the no form of this command.

ip {default-gateway ipaddress | domain-name domainname | name-server ipaddress | route destaddrs netmask gateway}

no ip{default-gateway ipaddress | domain-name domainname | name-server ipaddress | route destaddrs netmask gateway

Syntax Description

default-gateway

Specifies default gateway (if not routing IP).

ipaddress

IP address of default gateway.

domain-name

Specifies domain name.

domainname

Domain name.

name-server

Specifies address of name server.

ipaddress

IP address of name server.

route

Net route.

destaddrs

Destination route address.

netmask

Netmask.

gateway

Gateway address.

Defaults

No default behavior or values

Command Modes

Global configuration

Usage Guidelines

To define a default gateway, use the ip default-gateway global configuration command. To delete the IP default gateway, use the no form of this command.

The Content Engine uses the default gateway to route IP packets when there is no specific route found to the destination.

To define a default domain name, use the ip domain-name global configuration command. To remove the IP default domain name, use the no form of this command.

The Content 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 Content 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 Content Engine uses DNS servers. Use the ip name-server command to point the Content 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.

Examples

Console(config)# ip default-gateway 192.168.7.18 Console(config)# no ip default-gateway Console(config)# ip route 172.16.227.128 ffffff80 172.16.227.250 Console(config)# no ip route 172.16.227.128 ffffff80 172.16.227.250 Console(config)# ip domain-name cisco.com Console(config)# no ip domain-name Console(config)# ip name-server 10.11.12.13 Console(config)# no ip name-server 10.11.12.14

Related Commands

show ip routes

lls

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

lls [directory]

Syntax Description

directory

(Optional.) Name of the directory for which you want a long list of files.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

This command provides detailed information about files and subdirectories stored in the present working directory (including size, date, time of creation, sysfs name, and long name of the file). This information can also be viewed with the dir command.

Examples

Console# lls size time of last change name -------------- ------------------------- ----------- 0 Tue Mar 18 01:52:41 1980 dir 1959099 Tue Mar 18 01:52:41 1980 errlog-cache-19800317-171249 62 Mon Mar 17 17:12:33 1980 errlog-dataserver-19800317-17 1233 439190 Tue Mar 18 01:52:34 1980 errlog-webserver-19800317-171 243 26758 Tue Mar 18 01:47:25 1980 syslog.txt 0 Tue Mar 18 01:52:21 1980 testee 0 Tue Mar 18 01:52:10 1980 tester

Related Commands Related Cands

dir

ls

logging

To configure system logging, use the logging global configuration command. To disable logging functions, use the no form of this command.

logging {console {enable | priority loglevels} | disk {enable | filename filename | priority loglevels | recycle size}| facility facility | host {ip-address | priority loglevels}

no logging {console {enable | priority loglevels} | disk {enable | filename filename | priority loglevels | recycle size}| facility facility | host {ip-address | priority loglevels}

Syntax Description

console

Sets log to console.

enable

Enables log to a console.

priority

Sets which priority level messages to log.

Loglevels

Use one of these keywords:

  • alert

Immediate action needed. Priority 1.

  • critical

Immediate action needed. Priority 2

  • debug

Debugging messages. Priority 7.

  • emergency

System is unusable. Priority 0.

  • error

Error conditions. Priority 3.

  • information

Informational messages. Priority 6.

  • notice

Normal but significant conditions. Priority 5.

  • warning

Warning conditions. Priority 4.

disk

Sets log to disk file.

enable

Enables log to disk file.

filename

Sets log filename.

filename

Specifies name of the log file.

recycle

Overwrites syslog.txt when it surpasses the recycle size.

size

Size of syslog file in bytes (1 to 50,000,000).

facility

Sets facility parameter for syslog messages.

Facility

Use one of these keywords:

  • auth

Authorization system

  • daemon

System daemons.

  • httpd

HTTPD

  • kernel

Kernel.

  • local0

Local use.

  • local1

Local use.

  • local2

Local use.

  • local3

Local use.

  • local4

Local use.

  • local5

Local use.

  • local6

Local use.

  • local7

Local use.

  • mail

USENET news.

  • news

Mail system.

  • syslog

Syslog itself.

  • user

User process.

  • uucp

UUCP system.

host

Sets log to a host.

ip-address

Specifies host IP address.

Defaults

Logging: on

Priority of message for console: warning

Priority of message for file: debug

Log file: /local/var/log/syslog.txt

Log file recycle size: 5,000,000 bytes

Command Modes

Global configuration

Usage Guidelines

Use this command to set specific parameters of the system log file. System logging is always enabled internally. The system log file is located on the sysfs partition as /local1/syslog.txt. To configure the Content Engine to send varying levels of event messages to an external syslog host, use the logging host option. Logging can be configured to send various levels of messages to the console using the logging console priority option.

Examples

Console(config)# logging console priority warnings Console(config)# no logging console warnings

ls

To view a list of files or subdirectory names within a directory, use the ls EXEC command.

ls [directory]

Syntax Description

directory

(Optional.) Name of the directory for which you want a list of files.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

To list the filenames and subdirectories within a particular directory, use the ls directory command; to list the filenames and subdirectories of the current working directory, use the ls command. To view the present working directory, use the pwd command.

Examples

Console# ls /local etc tftpboot var lib ce60.pax 2125922304 bytes AVAILABLE ON VOLUME /c0t0d0s1

Related Commands

dir

lls

pwd

mkdir

To create a directory, use the mkdir EXEC command.

mkdir directory

Syntax Description

directory

Name of the directory to create.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to create a new directory or subdirectory in the Content Engine file system.

Examples

Console# mkdir /oldpaxfiles

Related Commands

dir

lls

ls

pwd

rmdir

mkfile

To create a new file, use the mkfile EXEC command.

mkfile filename

Syntax Description

filename

Name of the file you want to create.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to create a new file in any directory of the Content Engine.

Examples

Console# mkfile traceinfo

Related Commands

lls

ls

mkdir

no

To negate a command or set its defaults, use the no interface configuration command.

no {autosense | bandwidth | fullduplex | halfduplex | ip}

Syntax Description

autosense

Autosense capability on an interface.

bandwidth

Interface speed.

fullduplex

Full-duplex interface.

halfduplex

Half-duplex interface.

ip

Interface Internet Protocol (IP) configuration commands.

Defaults

No default behavior or values

Command Modes

Interface configuration

Usage Guidelines

Use this command to negate an interface configuration mode command or set its defaults. See the individual commands for syntax options and descriptions.

Examples

Console(config-if)# no autosense

no

To undo a global configuration command or set its defaults, use the no form of a command to undo the original command.

no command

Syntax Description

command

  • bypass

Configures bypass.

  • clock

Configures time-of-day clock.

  • dns-cache

Configures DNS cache.

  • error-handling

Customizes how Content Engine should handle errors.

  • exception

Exception handling.

  • exec-timeout

Configures exec timeout.

  • ftp

Configures FTP caching related parameters.

  • gui-server

Configures GUI server.

  • help

Configures assistance for command line interface.

  • hostname

Configures the system's network name.

  • http

Configures HTTP-related parameters.

  • https

Configures HTTPS-related parameters.

  • icp

Configures Internet Cache Protocol (ICP) parameters.

  • interface

Configures a Fast Ethernet or Gigabit Ethernet interface.

  • ip

Internet Protocol (IP) configuration commands.

  • logging

Configures system logging (syslog).

  • ntp

Configures Network Time Protocol (NTP).

  • proxy-protocols

Configures proxy protocols-related parameters.

  • snmp-server

Configures SNMP.

  • tcp

Configures TCP parameters.

  • terminal

Current terminal commands.

  • tftp-server

Configures TFTP server.

  • transaction-logs

Configures transaction logging.

  • user

Configures users.

  • wccp

Configures Web Cache Coordination Protocol.

Defaults

No default behavior or values

Command Modes

Global configuration

Usage Guidelines

Use the no command to disable functions or negate a command. If you need to negate a specific command, such as the default gateway IP address, you must include the specific string in your command, such as no ip default-gateway ip-address.

Examples

Console(config)# wccp version 2 Console(config)# no wccp version 2

ntp

To configure the Network Time Protocol (NTP) and to allow the system clock to be synchronized by a time server, use the ntp server global configuration command. To disable this function, use the no form of this command.

ntp server {hostname | ip-address}

no ntp server {hostname | ip-address}

Syntax Description

hostname

Host name of the time server providing the clock synchronization (maximum of 4).

ip-address

IP address of the time server providing the clock synchronization (maximum of 4).

Defaults

The default NTP version number is 3.

Command Modes

Global configuration

Usage Guidelines

Use this command to synchronize the Content Engine clock with the specified server. The server will not synchronize to this machine.

Examples

Console(config)# ntp server 172.16.22.44 Console(config)# no ntp server 172.16.22.44

Related Commands

clock

show clock

show ntp

ntpdate

To 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

hostname

NTP host name.

ip-address

NTP server IP address.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use NTP to find the current time of day and set the Content 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.

Examples

Console# ntpdate 10.11.23.40

Related Commands

clock save

clock set

show clocks

ping

To send echo packets for diagnosing basic network connectivity on networks, use the ping EXEC command.

ping {hostname | ip-address}

Syntax Description

hostname

Host name of system to ping.

ip-address

IP address of system to ping.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

To use this command with the hostname argument, be sure DNS functionality is configured on your Content Engine. To force the timeout of a nonresponsive host, or to eliminate a loop cycle, press Ctrl-C.

Examples

Console# ping mycacheengine

proxy-protocols

Use the proxy-protocols global configuration command to specify a domain name, host name, or IP address to be excluded from proxy forwarding.

proxy-protocols {outgoing-proxy exclude domain | transparent {default-server | original-proxy}}

no proxy-protocols {outgoing-proxy exclude domain | transparent {default-server | original-proxy}}

Syntax Description

outgoing-proxy exclude

Sets global outgoing proxy exclude criteria.

domain

Domain name, host name, or IP address to be excluded from proxy forwarding.

transparent

Sets transparent mode behavior for proxy requests.

default-server

Uses the Content Engine to go to the origin server or the outgoing proxy, if configured.

original-proxy

Uses the intended proxy server from the original request.

Defaults

No default behavior or values

Command Modes

Global configuration

Usage Guidelines

When you enter the proxy-protocols transparent default-server global configuration command, the Content Engine forwards intercepted HTTP and HTTPS proxy-style requests to the outgoing HTTP or HTTPS proxy server, if one is configured. If no outgoing proxy server is configured for the protocol, the request is serviced by the Content Engine and the origin server.

The proxy-protocols transparent original-proxy global configuration option specifies that requests sent by a Web client to another proxy server, but intercepted by the Content Engine in transparent mode, be directed back to the intended proxy server.

The proxy-protocols outgoing-proxy exclude global configuration option allows the administator to specify a single domain name, host name, or IP address to be globally excluded from proxy forwarding.

Examples

The following example configures the Content Engine to forward intercepted HTTPS proxy-style requests to an outgoing proxy server. The domain name cruzio.com is excluded from proxy forwarding. The show proxy-protocols command verifies the configuration.

Console(config)# https proxy outgoing host 172.16.10.10 266 Console(config)# proxy-protocols transparent default-server Console(config)# proxy-protocols outgoing-proxy exclude cruzio.com Console# show proxy-protocols all Transparent mode forwarding policies: default-server Outgoing exclude domain name: cruzio.com The following example configures the Content Engine to forward intercepted HTTP proxy-style requests to the intended proxy server. Console(config)# proxy-protocols transparent original-proxy

Related Commands

http proxy outgoing

https proxy outgoing

show proxy-protocols

pwd

To show the current directory, use the pwd EXEC command.

pwd

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to display the present working directory of the Content Engine.

Examples

Console# pwd

Related Commands

cd

dir

lls

ls

reload

To halt and perform a cold restart on your Content Engine, use the reload EXEC command.

reload

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

To reboot the Content 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.

Examples

Console# reload

Related Commands

cache synchronize

write

write erase

rename

To rename a file on your Content Engine, use the rename EXEC command.

rename sourcefile destinationfile

Syntax Description

sourcefile

Source file or path name of the file you want to rename.

destinationfile

Destination file or path name of the new file.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to rename any file within the Content Engine.

Examples

Console# rename ce25.pax ce6399.pax

Related Commands

cpfile

rmdir

To delete a directory, use the rmdir EXEC command.

rmdir directory

Syntax Description

directory

Name of the directory you want to delete.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to remove any directory from the Content Engine file system. The rmdir command only removes empty directories.

Examples

Console# rmdir /local/oldpaxfiles

Related Commands

lls

ls

mkdir

show arp

To display the Address Resolution Protocol (ARP) table, use the show arp EXEC command.

show arp

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show arp Protocol Address Flags Hardware Addr Type Interface Internet 172.16.55.1 Adj 00:D0:D3:39:6F:BC ARPA eth0

show bypass

To display bypass configuration information, use the show bypass EXEC command.

show bypass [list] [statistics {auth-traffic | load}] [summary]

Syntax Description

list

(Optional.) Displays bypass list entries.

statistics

(Optional.) Shows IP bypass statistics.

auth-traffic

Displays authenticated traffic bypass statistics.

load

Displays load bypass statistics.

summary

(Optional.) Displays a summary of bypass information.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

console# show bypass Total number of HTTP connections bypassed = 3 Connections bypassed due to system overload = 0 Connections bypassed due to authentication issues = 3 Connections bypassed to facilitate error transparency = 0 Connections bypassed due to static configuration = 0 Total number of entries in the bypass list = 2 Number of Authentication bypass entries = 0 Number of Error bypass entries = 0 Number of Static Configuration entries = 2 console# show bypass list Client Server Entry type ------ ------ ---------- 171.11.11.11:0 any-server:0 static-config any-client:0 171.23.23.23:0 static-config

Related Commands

bypass

show cfs

To view information about your cache file system, use the show cfs EXEC command.

show cfs {statistics | volumes}

Syntax Description

statistics

Displays the cache file system statistics.

volumes

Displays the cache file system volumes.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show cfs statistics CFS statistics -------------- Disk 0 Total disk space = 18119393280 Total disk space used = 941621248 Total disk objects read = 0 Total disk objects write = 0 Total bytes of disk read = 0 Total bytes of disk write = 0 Disk read errors = 0 Disk write errors = 0 isk 1 Total disk space = 18119393280 Total disk space used = 485490688 Total disk objects read = 0 Total disk objects write = 0 Total bytes of disk read = 0 Total bytes of disk write = 0 Disk read errors = 0 Disk write errors = 0 console# Console# show cfs volumes disk01 : mounted size: 18210037760 disk02 : mounted size: 18210037760 disk03 : mounted size: 18210037760 disk04 : mounted size: 18210037760

Related Commands

cfs

show disks

show disk-partitions

show statistics cfs

show clock

To display the system clock, use the show clock EXEC command.

show clock [detail]

Syntax Description

detail

(Optional.) Displays detailed information; indicates the clock source (NTP) and the current summer-time setting (if any).

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show clock Wed Apr 28 20:52:48 1999 GMT Console# show clock detail Tue Jun 1 14:48:18 1999 GMT Tue Jun 1 07:48:18 1999 LocalTime Epoch: 928248498 seconds UTC offset: -25200 seconds (-7 hr 0 min) timezone: PST summerzone: PDT summer offset: 0 minutes daylight: summer

Related Commands

clock clear

clock save

clock set

show debugging

To display the state of each debugging option, use the show debugging EXEC command.

show debugging

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Usage Guidelines

This command only displays the type of debugging enabled, not the specific subset of the command. For example, it shows that ICP debugging is enabled but does not define whether that debugging is monitoring ICP client or server packet transfer.

Command Modes

EXEC

Examples

Console# debug icp client Console# show debugging Debug icp (client) is on

Related Commands

debug

no debug

undebug

show disk-partitions

To view information about your disk partitions, use the show disk-partitions EXEC command.

show disk-partitions diskname

Syntax Description

diskname

The disk name (such as disk00 or disk01).

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to display partition information about a particular disk. The command show disks displays the names of the disks currently attached to the Content Engine.

Examples

Console# show disk-partitions disk00 Disk size in blocks: 17921835 Partition 1: CFS offset: 16 blocks, size 17921008 blocks

Related Commands

disk partition

disk prepare

show disks

show disks

To view information about your disks, use the show disks EXEC command.

show disks

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

The show disks command displays the names of the disks currently attached to the Content Engine. You can partition a disk using the disk partition command.

Examples

Console# show disks disk00 (scsi bus 0, unit 0, id 0) disk01 (scsi bus 0, unit 1, id 0)

Related Commands

disk partition

disk prepare

show disk-partitions

show dns-cache

To display DNS cache information, use the show dns-cache EXEC command.

show dns-cache

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show dns-cache DNS cache status : CONFIGURED and ONLINE Max cache size : 16384 Hash table size : 4093

show flash

To display the Flash memory version and usage information, use the show flash EXEC command.

show flash

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show flash Version:test_flash System flash directory: System image:86 sectors 120 sectors total, 15 sectors free.

show ftp

To display the configuration of the File Transfer Protocol (FTP) on the Content Engine, use the show ftp command.

show ftp

Syntax Description

The show ftp command has no keywords or options.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show ftp FTP heuristic age-multipliers: directory-listing 30% file 60% Maximum time to live in days : directory-listing 3 file 7 Minimum time to live in minutes: 60 No objects are revalidated on every request. Serve-IMS without revalidation if... Directory listing object is less than 50% of max age File object is less than 80% of max age Incoming Proxy-Mode: Servicing Proxy mode FTP connections on ports: 22 23 88 66 48 488 449 90 Outgoing Proxy-Mode: Not using outgoing proxy mode. Maximum size of a cachable object is unlimited. Console#

To show the FTP caching statistics:

Console# show statistics ftp ims If-Modified-Since statistics object Object statistics requests Request statistics savings Savings statistics errors error statistics

To clear the FTP caching statistics:

Console# clear statistics ftp

Related Commands

ftp

show statistics ftp

show gui-server

To display the current port assignment and operational status of the management graphical user interface (GUI) server, use the show gui-server command.

show gui-server

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

console# show gui-server GUI Server is enabled Listen on port 8001

Related Commands

gui-server

show hardware

To display system hardware status, use the show hardware EXEC command.

show hardware

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show hardware Cisco Content Engine Copyright (c) 1986-2000 by Cisco Systems, Inc. Cisco Content Engine Software Release 3.00 (build eft Sep 1 2000) Version:test_625 Compiled 20:44:11 Sep 1 2000 by (cisco) System was restarted on Thu Sep 28 20:56:09 2000. The system has been up for 23 hours, 59 minutes, 5 seconds. Core CPU is GenuineIntel Pentium III (Coppermine) (rev 8) running at 598MHz. 990 Mbytes of Physical memory. List of disk drives: disk00 (scsi host 0, channel 0, id 0) disk01 (scsi host 0, channel 0, id 1) disk02 (scsi host 0, channel 0, id 8) NOT available disk03 (scsi host 0, channel 0, id 9) NOT available disk04 (scsi host 0, channel 0, id 10) NOT available disk05 (scsi host 0, channel 0, id 11) NOT available disk06 (scsi host 0, channel 0, id 12) NOT available disk07 (scsi host 0, channel 0, id 13) NOT available

Related Commands

show version

show hosts

To view the hosts on your Content Engine, use the show hosts EXEC command.

show hosts

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show hosts Domain name = cisco.com Name Servers: ----------- 10.2.2.3 172.89.2.111 Host Table: hostname inet address aliases -------- ------------ ------- localhost 172.0.1.5 console 172.89.117.254

show http

To display the HTTP-related caching parameters, use the show http EXEC command.

show http {age-mult | all | anonymizer | append | authenticate-strip-ntlm | cache-authenticated | cache-cookie | cache-miss | cache-on-abort | object | persistent-connections | proxy | reval-each-request | ttl}

Syntax Description

age-mult

HTTP/1.0 caching heuristic modifiers.

all

All HTTP-related caching parameters.

anonymizer

Shows HTTP anonymizer settings.

append

Shows HTTP headers appended by Content Engine.

authenticate-strip-ntlm

Handling of requests with NT LAN Manager (NTLM) authentication headers.

cache-authenticated

Caching of authenticated Web objects.

cache-cookie

Caching of Web objects with associated cookies.

cache-miss

Handling of no-cache requests.

cache-on-abort

Configuration of cache-on-abort parameters.

object

Configuration of HTTP object.

persistent-connections

Persistent connections configuration.

proxy

Proxy-mode configuration.

reval-each-request

Configuration of revalidation for every request.

ttl

Time To Live for objects in the cache.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show http proxy Incoming Proxy-Mode: Servicing Proxy mode HTTP connections on port: 8080 Outgoing Proxy-Mode: Directing request to proxy server at 1.1.1.1 port 7777

show https

Use the show https command to display HTTPS proxy status and port policies.

show https proxy

Syntax Description

proxy

Proxy mode configuration.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

console# show https proxy Incoming HTTPS proxy: Servicing Proxy mode HTTPS connections on port 9090 Outgoing HTTPS proxy: Directing request to proxy server at 1.1.1.2 port 8888

Related Commands

proxy-protocols

show statistics https

show icp

To display the ICP client, root, or server information, use the show icp EXEC command.

show icp {client | root | server}

Syntax Description

client

Shows ICP client detailed information.

root

Shows ICP brief client/server information.

server

Shows ICP server detailed information.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show icp client ICP client is disabled max wait for replies = 2 seconds remove from wait list after 20 failures local_domain "" Number of remote servers = 0 "

Related Commands

icp client

icp server

show interface

To display hardware interface information, use the show interface EXEC command.

show interface {FastEthernet slot/port | GigabitEthernet slot/port | scsi number}

Syntax Description

FastEthernet

Selects Fast Ethernet interface.

slot/port

Specfies slot and port number for selected interface. Slot is 0-3; port is 0-3. The slot number and port number are separated with a forward slash character (/).

GigabitEthernet

Selects Gigabit Ethernet interface.

slot/port

Specfies slot and port number for selected interface. Slot is 0-3; port is 0-3. The slot number and port number are separated with a forward slash character (/).

scsi

Selects SCSI interface.

number

Specifies SCSI device number (0-20).

s

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show interface scsi 0 Max Transfer Size: 33554432 Sync: yes Wide: yes Console# # show interface FastEthernet 0/1 Type:Ethernet Ethernet address:01:64:FE:D0:99 Maximum Transfer Unit Size:1500 Metric:1 Packets Received:0 Input Errors:0 Input Packets Dropped:0 Input Packets Overruns:0 Input Packets Frames:0 Packet Sent:0 Output Errors:0 Output Packets Dropped:0 Output Packets Overruns:0 Output Packets Carrier:0 Output Queue Length:100 Collisions:0 Interrupts:10 Base address:0x6000

Related Commands

interface

show running-config

show ip routes

To display the IP routing table, use the show ip routes EXEC command.

show ip routes

Syntax Description

routes

Displays routing table.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

console# show ip routes Destination Gateway Netmask ---------------- ---------------- ---------------- 172.16.55.190 0.0.0.0 255.255.255.255 172.16.55.0 0.0.0.0 255.255.255.0 0.0.0.0 172.16.55.1 0.0.0.0

Related Commands

ip route

no ip route

show logging

To display the system message log configuration, use the show logging EXEC command.

show logging

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

console# show logging Syslog to host is disabled Priority for host logging is set to: warning Syslog to console is disabled Priority for console logging is set to: warning Syslog to disk is enabled Priority for disk logging is set to: notice Filename for disk logging is set to: /local1/syslog.txt Syslog facility is set to * Syslog disk file recycle size is set to 500000

show memory

To display memory blocks and statistics, use the show memory EXEC command.

show memory

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show memory Total physical memory : 1013008 KB Total free memory : 516352 KB Total memory shared : 0 KB Total buffer memory : 284 KB Total cached memory : 8044 KB

show ntp

To display the Network Time Protocol (NTP) parameters, use the show ntp EXEC command.

show ntp status

Syntax Description

status

NTP status.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show ntp status NTP subsystem ------------- servers:

Related Commands

ntp

clock set

clock timezone

show processes

To display CPU or memory processes, use the show processes EXEC command.

show processes [cpu | memory]

Syntax Description

cpu

(Optional.) CPU utilization.

memory

(Optional.) Memory allocation processes.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show processes cpu CPU Usage: cpu: 0.27% User, 0.70% System, 0.00% User(nice), 99.03% Idle cpu0: 0.27% User, 0.70% System, 0.00% User(nice), 99.03% Idle -------------------------------------------------------------------- PID STATE PRI User T SYS T COMMAND ----- ----- --- ------ ------ -------------------- 1 S 0 111 258 (init) 2 S 0 0 0 (kswapd) 3 S 0 0 0 (kflushd) 4 S 0 0 0 (kupdate) 128 S 0 0 0 (mingetty) 129 S 0 0 0 (mingetty) 130 S 0 0 0 (mingetty) 131 S 0 0 0 (mingetty) 132 S 0 0 0 (mingetty) 133 S 0 0 0 (mingetty) 134 S 0 1 126 (exec) 135 S 0 9 132 (start) 137 S 0 0 0 (inetd) 138 S 0 10 13 (dataserver) 144 S 0 0 0 (parser_server) 151 S 0 6 1 (parser_server) 247 S 0 0 1 (syslogd) 250 S 0 0 1 (wccp) 251 S 0 0 0 (overload) 252 S 0 0 8 (cache) 253 S 0 1 0 (webserver) 254 S 0 0 0 (snmpced) 260 S 0 0 0 (cache) 261 S 0 0 0 (cache) 347 S 0 0 0 (cache) 351 S 0 0 0 (cache) 392 S 0 0 0 (parser_server) 395 S 0 0 0 (in.telnetd) 396 S 0 3 8 (exec) 397 S 0 0 0 (parser_server) 408 R 0 0 0 (exec_show_proce) Console# show processes memory Total Used Free Shared Buffers Cached 1037320192 508776448 528543744 0 290816 8364032 PID State TTY %MEM VM Size RSS (pages) Name ------ ----- ------ ----- ---------- ----------- ---- 1 S 0 0.0 380928 53 (init) 2 S 0 0.0 0 0 (kswapd) 3 S 0 0.0 0 0 (kflushd) 4 S 0 0.0 0 0 (kupdate) 128 S 1025 0.0 1118208 102 (mingetty) 129 S 1026 0.0 1118208 102 (mingetty) 130 S 1027 0.0 1118208 102 (mingetty) 131 S 1028 0.0 1118208 102 (mingetty) 132 S 1029 0.0 1118208 102 (mingetty) 133 S 1030 0.0 1118208 102 (mingetty) 134 S 1088 0.0 1552384 164 (exec) 135 S 0 0.0 1413120 144 (start) 137 S 0 0.0 1179648 123 (inetd) 138 S 0 0.0 1585152 186 (dataserver) 144 S 0 0.3 4554752 864 (parser_server) 151 S 0 0.3 4554752 864 (parser_server) 247 S 0 0.0 1490944 166 (syslogd) 250 S 0 0.0 1847296 144 (wccp) 251 S 0 0.0 1462272 142 (overload) 252 S 0 40.3 422227968 102285 (cache) 253 S 0 0.3 4239360 767 (webserver) 254 S 0 0.0 1622016 208 (snmpced) 260 S 0 40.3 422227968 102285 (cache) 261 S 0 40.3 422227968 102285 (cache) 347 S 0 40.3 422227968 102285 (cache) 351 S 0 40.3 422227968 102285 (cache) 392 S 0 0.3 4554752 864 (parser_server) 395 S 0 0.0 1675264 176 (in.telnetd) 396 S 34816 0.0 1548288 163 (exec) 397 S 0 0.3 4554752 864 (parser_server) 409 R 34816 0.0 1589248 144 (exec_show_proce) Console# show processes CPU Usage: cpu: 0.27% User, 0.69% System, 0.00% User(nice), 99.04% Idle cpu0: 0.27% User, 0.69% System, 0.00% User(nice), 99.04% Idle -------------------------------------------------------------------- PID STATE PRI User T SYS T COMMAND ----- ----- --- ------ ------ -------------------- 1 S 0 111 258 (init) 2 S 0 0 0 (kswapd) 3 S 0 0 0 (kflushd) 4 S 0 0 0 (kupdate) 128 S 0 0 0 (mingetty) 129 S 0 0 0 (mingetty) 130 S 0 0 0 (mingetty) 131 S 0 0 0 (mingetty) 132 S 0 0 0 (mingetty) 133 S 0 0 0 (mingetty) 134 S 0 1 126 (exec) 135 S 0 9 132 (start) 137 S 0 0 0 (inetd) 138 S 0 10 13 (dataserver) 144 S 0 0 0 (parser_server) 151 S 0 6 1 (parser_server) 247 S 0 0 1 (syslogd) 250 S 0 0 1 (wccp) 251 S 0 0 0 (overload) 252 S 0 0 8 (cache) 253 S 0 1 0 (webserver) 254 S 0 0 0 (snmpced) 260 S 0 0 0 (cache) 261 S 0 0 0 (cache) 347 S 0 0 0 (cache) 351 S 0 0 0 (cache) 392 S 0 0 0 (parser_server) 395 S 0 0 0 (in.telnetd) 396 S 0 4 9 (exec) 397 S 0 0 0 (parser_server) 410 R 0 0 0 (exec_show_proce)

show proxy-protocols

Use the show proxy-protocols command to display current global outgoing proxy exclude status and criteria.

show {all | outgoing-proxy | transparent}

Syntax Description

all

All proxy protocols-related parameters.

outgoing-proxy

Global outgoing proxy exceptions.

transparent

Transparent-mode protocol policies.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

console# show proxy-protocols all Transparent mode forwarding policies: default-server Outgoing exclude domain name: cisco.com

Related Commands

proxy-protocols

show running-config

To display the current running configuration information on the terminal, use the show running-config EXEC command. This command replaces the write terminal command.

show running-config

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command in conjunction with the show startup-config command to compare the information in running memory to the startup configuration used during bootup.

Examples

Console# show running-config hostname csbu-lab-ce590 ! http proxy incoming 8080 ! ! ! ip domain-name cisco.com ! exec-timeout 60 ! ! ! interface ethernet 0 ip address 172.16.55.190 255.255.255.0 exit ! ! ip name-server 172.16.2.200 ! ip route 0.0.0.0 0.0.0.0 172.16.55.1 ! ! ! icp client add-remote-server 1.1.1.1 parent icp-port 2222 http-port 888 restrict wertw ! ! ! ! user modify username admin password 1 c4CaLFXa9epFg ! !

Related Commands

configure

copy running-config

copy startup-config

show snmp

To check the status of SNMP communications, use the show snmp EXEC command.

show snmp

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

This command provides counter information for SNMP operations.

Examples

Console# show snmp Contact: Mary Brown, system admin, mbrown@acme.com 555-1111 Location: Building 2, 1st floor, Lab 1 37 SNMP packets input 0 Bad SNMP version errors 4 Unknown community name 0 Illegal operation for community name supplied 0 Encoding errors 24 Number of requested variables 0 Number of altered variables 0 Get-request PDUs 28 Get-next PDUs 0 Set-request PDUs 78 SNMP packets output 0 Too big errors     2048 Maximum packet size 0 No such name errors 0 Bad values errors 0 General errors 24 Response PDUs 13 Trap PDUs

Table 2-1 describes the fields shown in the display.


Table 2-1: show snmp Field Descriptions
Field Description

SNMP packets input

Total number of SNMP packets input.

  Bad SNMP version errors

Number of packets with an invalid SNMP version.

  Unknown community name

Number of SNMP packets with an unknown community name.

  Illegal operation for   community name supplied

Number of packets requesting an operation not allowed for that community.

  Encoding errors

Number of SNMP packets that were improperly encoded.

  Number of requested variables

Number of variables requested by SNMP managers.

  Number of altered variables

Number of variables altered by SNMP managers.

  Get-request PDUs

Number of GET requests received.

  Get-next PDUs

Number of GET-NEXT requests received.

  Set-request PDUs

Number of SET requests received.

SNMP packets output

Total number of SNMP packets sent by the router.

  Too big errors

Number of SNMP packets that were larger than the maximum packet size.

  Maximum packet size

Maximum size of SNMP packets.

  No such name errors

Number of SNMP requests that specified a MIB object that does not exist.

  Bad values errors

Number of SNMP SET requests that specified an invalid value for a MIB object.

  General errors

Number of SNMP SET requests that failed because of some other error. (It was not a
No such name error, Bad values error, or any of the other specific errors.)

  Response PDUs

Number of responses sent in reply to requests.

  Trap PDUs

Number of SNMP traps sent.

show startup-config

To show the configuration, use the show startup-config EXEC command.

show startup-config

Syntax Description

This command has no keywords or arguments.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to display the configuration used during an initial bootup, stored in NVRAM.

Examples

Console# show startup-config hostname Console ! ! ! ! ip domain-name cisco.com ! ! ! ! interface FastEthernet 0/0 ip address 172.16.55.190 255.255.255.0 exit interface FastEthernet 0/1 shutdown exit ! ! ip name-server 172.16.2.200 ! ! ! ! ! ! ! ! ! username admin password 1 .9ENIWf7GjMm2 username admin privilege 15 ! !

Related Commands

configure

copy running-config

show running-config

show statistics

To display Content Engine statistics, use the show statistics EXEC command.

show statistics {bypass [auth-traffic | load | summary] | cfs | dns-cache | ftp | http {ims | object | performance | requests | savings | usage} | https | icmp | icp {client | server} | ip | netstat | snmp |tcp | transaction-logs | udp}

Syntax Description

bypass

Displays bypass statistics.

auth-traffic

Displays authenticated traffic bypass statistics.

summary

Displays a summary of bypass statistics.

cfs

Displays cache file system statistics.

dns-cache

Displays DNS cache statistics.

ftp

Displays FTP caching statistics.

http

Displays HTTP caching statistics.

ims

Displays HTTP if-modified-since statistics.

object

Displays HTTP object statistics.

performance

Displays HTTP performance statistics.

requests

Displays HTTP requests statistics.

savings

Displays HTTP savings statistics.

usage

Displays HTTP usage statistics.

https

Displays HTTPS statistics.

icmp

Displays ICMP statistics.

icp

Displays ICP caching statistics.

client

Displays ICP client statistics.

server

Displays ICP server statistics.

ip

Displays IP statistics.

netstat

Displays Internet socket connections.

snmp

Displays SNMP statistics

tcp

Displays TCP statistics.

transaction-logs

Displays transaction-log export statistics.

udp

Displays UDP statistics.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

To clear statistics without affecting configurations, use the clear statistics command. This will set all counters to zero.

Examples

Console# show statistics icmp ICMP statistics --------------- ICMP messages received = 3 ICMP messages receive failed = 0 Destination unreachable = 3 Timeout in transit = 0 Wrong parameters = 0 Source quenches = 0 Redirects = 0 Echo requests = 0 Echo replies = 0 Timestamp requests = 0 Timestamp replies = 0 Address mask requests = 0 Address mask replies = 0 ICMP messages sent = 3 ICMP messages send failed = 0 Destination unreachable = 3 Time exceeded = 0 Wrong parameters = 0 Source quenches = 0 Redirects = 0 Echo requests = 0 Echo replies = 0 Timestamp requests = 0 Timestamp replies = 0 Address mask requests = 0 Address mask replies = 0

Related Commands

clear statistics

show tcp

To display TCP configuration information, use the show tcp EXEC command.

show tcp

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show tcp ==TCP Configuration== TCP keepalive timeout 300 sec TCP keepalive probe count 4 TCP keepalive probe interval 75 sec TCP server R/W timeout 120 sec TCP client R/W timeout 120 sec TCP server send buffer 8 k TCP server receive buffer 32 k TCP client send buffer 32 k TCP client receive buffer 8 k TCP Listen Queue 200 TCP server max segment size 1432 TCP server satellite (RFC1323) disabled TCP client max segment size 1432 TCP client satellite (RFC1323) disabled

show tech-support

To view information necessary for Cisco's Technical Assistance Center (TAC) to assist you, use the show tech-support EXEC command.

show tech-support [page]

Syntax Description

page

(Optional.) Pages through output.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to view system information necessary for TAC to assist you with your Content Engine. We recommend that you log the output to a disk file.

Examples

Console# show tech-support ------------------ version and hardware -------------------- Cisco Content Engine Copyright (c) 1986-2000 by Cisco Systems, Inc. Cisco Content Engine Software Release 3.00 (build eft Sep 21 2000) Compiled 18:48:10 Sep 21 2000 by (cisco) System was restarted on Sat Mar 15 22:12:25 2000. The system has been up for 1 day, 5 hours, 13 minutes, 10 seconds. disk00 (scsi host 0, channel 0, id 0) disk01 (scsi host 0, channel 0, id 1) disk02 (scsi host 0, channel 0, id 8) NOT available disk03 (scsi host 0, channel 0, id 9) NOT available disk04 (scsi host 0, channel 0, id 10) NOT available disk05 (scsi host 0, channel 0, id 11) NOT available disk06 (scsi host 0, channel 0, id 12) NOT available disk07 (scsi host 0, channel 0, id 13) NOT available ------------------ running configuration ------------------- hostname Console ! ! ! ! ip domain-name cisco.com ! ! !

<snip>

show transaction-logging

To show the transaction log summaries or to show transaction log settings, use the show transaction-logging EXEC command.

show transaction-logging

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use the show transaction-logging command to display the current settings for the transaction logging feature.

Examples

Console# show transaction-logging Transaction log configuration: Logging is enabled. End user identity is hidden. (sanitized) File markers are disabled Archive interval: every-day at 12:00 Maximum size of archive file: 2000000 KB Exporting files to servers is enabled. Export interval: every-day every 1 hour

show user

To display user information for a particular user, use the show user EXEC command.

show user username name

Syntax Description

username

Displays username keyword.

name

Username.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show user username bwhidney Username : bwhidney Uid : 5013 Password : bSzyydQbSb Privilege : super user

Related Commands

show users

show users

To display all users, use the show users EXEC command.

show users

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show users UID USERNAME 0 admin 5013 bwhidney

Related Commands

show user

show version

To display version information of your Content Engine software, use the show version EXEC command.

show version

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show version Copyright (c) 1986-2000 by Cisco Systems, Inc. Cisco Content Engine Software Release 3.00 (build eft Sep 21 2000) Compiled 18:48:10 Sep 21 2000 by (cisco) System was restarted on Sat Mar 15 22:12:25 2000. The system has been up for 1 day, 5 hours, 26 minutes, 53 seconds.

show wccp

To display WCCP information, use the show wccp EXEC command.

show wccp {content-engines | flows {custom-web-cache | reverse-proxy | web-cache}[summary] | routers | services [detail] | slowstart {custom-web-cache | reverse-proxy | web-cache}| status}

Syntax Description

content-engines

Shows WCCP Content Engine information.

flows

Shows WCCP packet flow count by bucket.

custom-web-cache

Custom Web caching service.

reverse-proxy

Reverse proxy Web caching service.

web-cache

Standard Web caching service.

summary

Displays summary information.

routers

Shows WCCP router list.

services

Shows WCCP services configured.

detail

Shows detail of services.

slowstart

Shows WCCP slow start state for the selected service.

status

Shows which version of WCCP is enabled and running.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Console# show wccp routers Routers Seeing this Content 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 Content Engine Router Id Sent To 0.0.0.0 10.1.1.1 Routers not Seeing this Content Engine 10.1.1.1 Routers Notified of but not Configured -NONE- Multicast Addresses Configured -NONE-

shutdown

To shut down a specific hardware interface, use the shutdown interface configuration command. To restore an interface to operation, use the no form of this command.

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Interface configuration

Usage Guidelines

See the "interface" section for alternative syntax.

Examples

Console(config-if)# shutdown Console(config-if)# no autosense

snmp-server community

To enable the SNMP agent and set up the community access string to permit access to the SNMP agent, use the snmp-server community global configuration command. Use the no form of this command to disable the SNMP agent and to remove the previously configured community string.

snmp-server community string

no snmp-server community

Syntax Description

string

Community string that acts like a password and permits access to the SNMP agent.

Defaults

The SNMP agent is disabled and a community string is not configured.

When configured, an SNMP community string by default permits read-only access to all objects.

Command Modes

Global configuration

Examples

The following example enables the SNMP agent and assigns the community string comaccess to SNMP:

Console(config)# snmp-server community comaccess

The following example disables the SNMP agent and removes the previously defined community string.

Console(config)# no snmp-server community

Related Commands

show snmp

snmp-server contact

To set the system contact (sysContact) string, use the snmp-server contact global configuration command. Use the no form of this command to remove the system contact information.

snmp-server contact line

no snmp-server contact

Syntax Description

contact

Text for MIB object sysContact.

line

Identification of the contact person for this managed node.

Command Modes

Global configuration

Defaults

No system contact string is set.

Usage Guidelines

The system contact string is the value stored in the MIB-II system group sysContact object.

Examples

The following is an example of a system contact string:

Console(config)# snmp-server contact Dial System Operator at beeper # 27345 Console(config)# no snmp-server contact

Related Commands

snmp-server location

show snmp

snmp-server enable traps

To enable the Content Engine to send SNMP traps, use the snmp-server enable traps global configuration command. Use the no form of this command to disable all SNMP traps or only SNMP authentication traps.

snmp-server enable traps [snmp authentication]

no snmp-server enable traps [snmp authentication]

Syntax Description

snmp authentication

(Optional.) Enables sending the MIB-II SNMP authentication trap.

Defaults

This command is disabled by default. No traps are enabled.

Command Modes

Global configuration

Usage Guidelines

If you do not enter an snmp-server enable traps command, no traps are sent. In order to configure traps, you must enter the snmp-server enable traps command.

The snmp-server enable traps command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP traps. To send traps, you must configure at least one snmp-server host command.

For a host to receive a trap, both the snmp-server enable traps command and the snmp-server host command for that host must be enabled.

In addition, SNMP must be enabled with the snmp-server community command.

To disable the sending of the MIB-II SNMP authentication trap, you must enter the command
no snmp-server enable traps snmp authentication.

Examples

The following example enables the Content Engine 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

The following example disables all traps:

Console(config)# no snmp-server enable traps

Related Commands

snmp-server host

snmp-server community

snmp-server host

To specify the recipient of an SNMP trap operation, use the snmp-server host global configuration command. Use the no form of this command to remove the specified host.

snmp-server host {hostname | ip-address} communitystring

no snmp-server host {hostname | ip-address} communitystring

Syntax Description

hostname

Host name of SNMP trap host.

ip-address

IP address of SNMP trap host.

communitystring

Password-like community string sent with the trap operation.

Defaults

This command is disabled by default. No traps are sent.

The version of the SNMP protocol used to send the traps is SNMPv1.

Command Modes

Global configuration

Usage Guidelines

If you do not enter an snmp-server host command, no traps are sent. To configure the Content 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.

Examples

The following example sends the SNMP traps defined in RFC 1157 to the host specified by the IP address 172.16.2.160. The community string is comaccess.

Console(config)# snmp-server enable traps Console(config)# snmp-server host 172.16.2.160 comaccess

The following example removes the host 172.16.2.160 from the SNMP trap recipient list.

Console(config)# no snmp-server host 172.16.2.160

Related Commands

snmp-server enable traps

snmp-server community

snmp-server location

To set the SNMP system location string, use the snmp-server location global configuration command. Use the no form of this command to remove the location string.

snmp-server location line

no snmp-server location

Syntax Description

line

String that describes the physical location of this node.

Defaults

No system location string is set.

Command Modes

Global configuration

Usage Guidelines

The system location string is the value stored in the MIB-II system group system location object.

You can see the system location string with the show snmp EXEC command.

Examples

The following is an example of a system location string:

Console(config)# snmp-server location Building 3/Room 214

Related Commands

show snmp

snmp-server contact

sysfs

To maintain the system file system, use the sysfs command.

sysfs {check disk name | format disk name | mount {disk name {local1 | local2}} | repair disk name | sync | unmount {local1 | local2}}

Syntax Description

check

Checks a file system.

disk name

Disk name (for example, disk00 or disk01).

format

Erases and creates a file system on a disk device.

mount

Mounts a disk or volume file system.

repair

Checks and repairs a sysfs file system.

local1

Mounts to /local1.

local2

Mounts to /local2.

sync

Syncs all sysfs commands running on the system.

unmount

Unmounts a disk or volume file system.

local1

Unmounts sysfs mounted at /local1.

local2

Unmounts sysfs mounted at /local2.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

A sysfs formatted volume must be mounted when you use transaction logs.

A file system is automatically repaired when it is mounted.

Examples

The following example creates a sysfs partition on the first disk on the SCSI bus, formats the partition and mounts the volume /local1:

Console# disk erase-all-partitions disk00 Console# disk partition disk00 sysfs Console# sysfs format disk00 Console# sysfs mount disk00 /local1

tcp

To configure TCP parameters, use the tcp global configuration command. To disable TCP parameters, use the no form of this command.

tcp {client-mss maxsegsize | client-receive-buffer kbytes | client-rw-timeout seconds | client-satellite | client-send-buffer kbytes | keepalive-probe-cnt count | keepalive-probe-interval seconds | keepalive-timeout seconds | server-mss maxsegsize | server-receive-buffer kbytes | server-rw-timeout seconds | server-satellite | server-send-buffer kbytes | type-of-service enable}

no tcp {client-mss maxsegsize | client-receive-buffer kbytes | client-rw-timeout seconds | client-satellite | client-send-buffer kbytes | keepalive-probe-cnt count | keepalive-probe-interval seconds | keepalive-timeout seconds | server-mss maxsegsize | server-receive-buffer kbytes | server-rw-timeout seconds | server-satellite | server-send-buffer kbytes | type-of-service enable}

Syntax Description

client-mss

Sets client TCP maximum segment size.

maxsegsize

Maximum segment size in bytes (512-1460).

client-receive-buffer

Sets client connections receive buffer size.

kbytes

Receive buffer size in kilobytes (1-1024).

client-rw-timeout

Sets client connection's read/write timeout.

seconds

Timeout in seconds (1-3600).

client-satellite

Sets client TCP compliance to RFC 1323 standard.

client-send-buffer

Sets client connection's send buffer size.

kbytes

Send buffer size in kilobytes (8-1024).

keepalive-probe-cnt

Sets TCP keepalive probe counts.

count

Number of probe counts (1-10).

keepalive-probe-interval

Sets TCP keepalive probe interval.

seconds

Keepalive probe interval in seconds (1-300).

keepalive-timeout

Sets TCP keepalive timeout.

seconds

Keepalive timeout in seconds (1 to 3600).

server-mss

Sets server TCP max segment size.

maxsegsize

Maximum segment size in bytes (512-1460).

server-receive-buffer

Sets server connection's receive buffer size.

kbytes

Receive buffer size in kilobytes (1-1024).

server-rw-timeout

Sets server connection's read/write timeout.

seconds

Read/write timeout in seconds (1-3600).

server-satellite

Sets server TCP compliance to RFC 1323 standard.

server-send-buffer

Sets server connection's send buffer size.

kbytes

Send buffer size in kilobytes (1-1024).

type-of-service enable

Sets TCP type of service to match client's type of service.

Defaults

tcp server maximum segment size: 1,432 bytes

tcp client maximum segment size: 1,432 bytes

tcp server-receive-buffer: 8 kilobytes

tcp client-receive-buffer: 8 kilobytes

tcp server-rw-timeout: 120 seconds

tcp client-rw-timeout: 30 seconds

tcp server-send-buffer: 8 kilobytes

tcp client-send-buffer: 8 kilobytes

tcp keepalive-probe-cnt: 4

tcp keepalive-probe-interval: 75 seconds

tcp keepalive-timeout: 300 seconds

tcp server-satellite (RFC 1323): disabled

tcp client-satellite (RFC 1323): disabled

tcp type of service: disabled

Usage Guidelines

In nearly all environments, the default TCP setting is adequate.

Command Modes

Global configuration

Examples

Console(config)# tcp client-receive-buffer 100 Console(config)# no tcp client-receive-buffer

Related Commands

show tcp

terminal

To display the current console debug command output, use the terminal EXEC command.

terminal monitor

Syntax Description

monitor

Monitors debug command output on the console.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

This command allows a Telnet session to display the output of the debug commands that appear on the console. The monitoring continues until the Telnet session is terminated.

Examples

Console# terminal monitor

terminal length

To set the number of lines displayed in the console window, use the terminal global configuration command. To set the default value, use the no form of the command.

terminal length lines

no terminal length

Syntax Description

length

Sets the number of lines displayed on the terminal screen.

lines

Number of lines on the screen displayed before pausing (0 to 512). Enter 0 for no pausing.

Defaults

Default is 24 lines.

Command Modes

Global configuration

Usage Guidelines

When 0 is entered as the lines parameter, output to the screen does not pause. For all nonzero values of lines, the -More- prompt is displayed when the number of output lines matches the specified lines number. The -More- prompt is considered a line of output. To view the next screen, press the Spacebar. To view one line at a time, press the Enter key. To exit the show command output, press the Esc key or any other keystroke.

Examples

The following example sets the number of lines to display to 20:

Console(config)# terminal length 20

The following example sets the number of lines to the default of 24:

Console(config)# no terminal length

The following example configures the terminal for no pausing:

Console(config)# terminal length 0

Related Commands

All show commands.

transaction-log force

To force the immediate creation of a transaction log, use the transaction-log force EXEC command.

transaction-log force {archive | export}

Syntax Description

archive

Forces the archive of the working.log file.

export

Forces the archived files to be exported to an FTP server.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

The transaction-log force archive command causes the transaction log to be archived immediately to the Content Engine hard disk. This command has the same effect as the clear transaction-log command.

The transaction-log force export command causes the transaction log to be exported immediately to an FTP server designated by the transaction-logs export ftp-server command.

The force commands do not change the configured or default schedule for archive or export of transaction log files. If a scheduled archive or export job is in progress when a corresponding force command is entered, the force command runs when the job in progress completes. If a force command is in progress when an archive or export job is scheduled to run, the scheduled job runs when the force command is complete.

Examples

Console# transaction-log force archive Console# transaction-log force export

Related Commands

transaction-logs

clear statistics transaction-logs

clear transaction-log

show statistics transaction-logs

show transaction-logging

transaction-logs

To enable transaction logs, use the transaction-logs global configuration command. To disable transaction logs, use the no form of this command.

transaction-logs {archive {interval {every-day {at time | every hour} | every-hour {at minute | every interval}} | max-file-size filesize} | enable | export {enable | ftp-server {hostname | servipaddrs} login passw directory} | file-marker | sanitize}

no transaction-logs {archive {interval {every-day {at time | every hour} | every-hour {at
minute | every interval}} | max-file-size filesize} | enable | export {enable | ftp-server {hostname | servipaddrs} login passw directory} | file-marker | sanitize}

Syntax Description

archive

Configures archive parameters.

interval

Determines how frequently the archive file is to be saved.

every-day

Archives using frequencies of 1 day or less.

at time

Specifies the time of day at which to archive in hours and minutes (hh:mm).

every hour

Interval in hours (1, 2, 3, 4, 6, 8, 12, or 24). Interval aligns with midnight.

every-hour

Archives using frequencies of 1 hour or less.

at minute

Specifies the minute alignment for the hourly archive (0-59).

every interval

Interval in minutes (2, 5, 10, 15, 20, or 30).

max-file-size

Sets maximum archive file size.

filesize

Specifies maximum archive file size in kilobytes (1000-2000000).

enable

Enables transaction log feature.

export

Configures file export parameters.

enable

Enables the exporting of log files at the specified interval.

ftp-server

Sets FTP server to receive exported archived files.

hostname

Host name of target FTP server.

servipaddrs

IP address of target FTP server.

login

User login to target FTP server.

passw

User password to target FTP server.

directory

Target directory for exported files on FTP server.

file-marker

Adds statements to translog indicating the file beginning and end.

sanitize

Writes user IP addresses in log file as 0.0.0.0.

Defaults

The transaction log options (archive, export, file marker, and sanitize) are disabled by deafult. The default interval for archiving files is every day, every 1 hour. The default maximum archive size is 2,000,000 kilobytes. The default export time interval is 60 minutes.

Command Modes

Global configuration

Usage Guidelines

Transaction logs are saved to the system file system (sysfs). A sysfs volume must be mounted to receive transaction logs.

Enable transaction log recording with the transaction-logs enable command. When enabled, daemons create a working.log file in the /local1/logs/ sysfs volume.

After an interval specified by the transaction-logs archive interval command, the working.log file is copied as an archive file to the /local1/logs/ directory. The records of the working.log file are then deleted, and only transactions subsequent to the archiving event are recorded. The transaction log archive file-naming conventions are shown in Table 2-2. The Content Engine default archive interval is every day, every 1 hour.

Use the transaction-logs file-marker option to mark the beginning and end of archive files. By examining the file markers of an exported archive file, the administrator can determine if the FTP process transferred the entire file. The file markers are in the form of dummy transaction entries as follows:

Use the transaction-logs archive max-file-size command to specify the maximum size of an archive file. The working.log file is archived when it attains the maximum file size.

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.

The transaction log archive and export functions are configured with the following commands:

The following limitations apply:

Transaction Log Archive File-Naming Convention

The archive transaction log file is named as follows:

celog_10.1.118.5_20001228_235959.txt

Table 2-2 describes the name elements.


Table 2-2: Description of Archive Log Name Elements
Sample of Element Description

celog_10.1.118.5

IP address of the Content Engine creating the archive file.

20001228

Date archive file was created (yyyy/mm/dd).

235959

Time archive file was created (hh/mm/ss).

Exporting Transaction Logs to External FTP Servers

The transaction-logs export ftp-server option can support up to four FTP servers. To export transaction logs, you must first enable the feature and configure the FTP server parameters. The following information is required for each target FTP server:

The Content Engine translates the host name with a DNS lookup and then stores the IP address.

Use a fully qualified path or a relative path for the user login. The user must have write permission to the directory.

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 Server

When an FTP server returns a permanent error to the Content Engine, the archive transaction logs are no longer exported to that server. You must reenter the Content Engine transaction log export parameters to clear the error condition. The show statistics transaction-logs command displays the current state of transaction log export readiness.

A permanent error (Permanent Negative Completion Reply, RFC 959) occurs when the FTP command to the server cannot be accepted, and the action does 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 Content Engine failed to export archive files.

Console# show statistics transaction-logs Transaction Log Export Statistics: Server:172.16.10.5 Initial Attempts:3 Initial Successes:1 Initial Open Failures:0 Initial Put Failures:0 Retry Attempts:2 Retry Successes:2 Retry Open Failures:0 Retry Put Failures:0 Authentication Failures:1 Invalid Server Directory Failures:2

To restart the export of archive transaction logs, you must reenter the transaction-logs export ftp-server parameters.

Console(config)# transaction-logs export ftp-server 10.1.1.1 goodlogin pass /etc/webcache

Examples

In this example, an FTP server is configured.

Console(config)# transaction-logs export ftp-server 10.1.1.1 mylogin mypasswd /tmp/local/webcache Console(config)# transaction-logs export ftp-server myhostname mylogin mypasswd /tmp/local/webcache

To delete an FTP server, use the no form of the command.

Console(config)# no transaction-logs export ftp-server myhostname Console(config)# no transaction-logs export ftp-server 10.1.1.1

Use the no form of the command to disable the entire transaction log export feature while retaining the rest of the configuration.

Console(config)# no transaction-logs export enable
Note   The default is export disabled; the export interval is every 10 minutes. There are no defaults for the FTP server configuration.

To change a username, password, or directory, reenter the entire line.

Console(config)# transaction-logs export ftp-server 10.1.1.1 mynewname mynewpass /tmp/local/webcache

The show transaction-logging command displays information on exported log files.

Console# show transaction-logging Transaction log configuration: --------------------------------------- Logging is enabled. End user identity is visible. File markers are disabled. Archive interval: every-day at 10:35 Maximum size of archive file: 2000000 KB Exporting files to ftp servers is enabled. ftp-server username directory 1.1.1.1 user /ftpdirectory 2.2.2.2 myname /tmp/logfiles Working Log file - size : 103 age: 0
Note   For security reasons, passwords are never displayed.

The export option displays the status of logging attempts to export servers.

Console# show statistics transaction-logs Transaction Log Export Statistics: Server:172.16.10.5 Initial Attempts:3 Initial Successes:1 Initial Open Failures:0 Initial Put Failures:0 Retry Attempts:2 Retry Successes:2 Retry Open Failures:0 Retry Put Failures:0 Authentication Failures:1 Invalid Server Directory Failures:2

Configuring Intervals Between 1 Day and 1 Hour

The interval can be set for once an day with a specific timestamp. It can also be set for frequencies of hours; these frequencies align with midnight. For example, every 4 hours means archiving will occur at 0000, 0400, 0800, 1200, 1600 and the like. It is not possible to archive at 0030, 430, 830, and so forth.

Console(config)# transaction-logs archive interval every-day ? at Specify the time at which to archive each day every Specify the interval in hours. It will align with midnight Console(config)# transaction-logs archive interval every-day at ? <0-23>: Time of day at which to archive (hh:mm) Console(config)# transaction-logs archive interval every-day every ? <1-24> Interval in hours: {1, 2, 3, 4, 6, 8, 12 or 24}

Scheduling Intervals of 1 Hour or Less

The interval can be set for once an hour with a minute alignment. It can also be set for frequencies of less than an hour; these frequencies will align with the top of the hour. That is, every 5 minutes means archiving will occur at 1700, 1705, and 1710.

Console(config)# transaction-logs archive interval every-hour ? at Specify the time at which to archive each day every Specify interval in minutes. It will align with top of the hour Console(config)# transaction-logs archive interval every-hour at ? <0-59> Specify the minute alignment for the hourly archive Console(config)# transaction-logs archive interval every-hour every ? <2-30> Interval in minutes: {2, 5, 10, 15, 20, 30}

Related Commands Related Commands

clear transaction-log

show transaction-logging

show statistics transaction-logs

transaction-log force

type

To display a file, use the type EXEC command.

type filename

Syntax Description

filename

Name of file.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to display the contents of a file within any Content Engine file directory. This command may be used to monitor features such as transaction logging or system logging (syslog).

Examples

Console# type /local1/syslog.txt

Related Commands

cpfile

dir

lls

ls

mkfile

undebug

To disable debugging functions, use the undebug EXEC command. Also see the debug EXEC command.

Command Modes

EXEC

Usage Guidelines

It is recommended that debug commands be used only at the direction of Cisco Systems technical support personnel.

Related Commands

debug

no debug

show debug

user

To configure user accounts on your Content Engine, use the user global configuration command.

user {add | delete | modify}

user add username {password [ 0 | 1] password} [capability [admin-access]] [uid userid]

user delete {username username | uid userid}

user modify {uid number | username name}{add-capability admin-access | del-capability admin-access | password [0 | 1] password}

Syntax Description

add

Creates a new user account on the Content Engine.

delete

Removes the specified user account from Content Engine.

modify

Changes the user information.

username

Content Engine login name for the user.

password

Sets password. See password options.

0

(Optional.) Specifies that a clear-text password will follow (default).

1

(Optional.) Specifies that a type 1 encrypted password will follow.

password

Specifies password for the specified user.

capability

(Optional.) See capability options. Adds capability to a new user. Use with add keyword.

admin-access

Grants all possible access to the Content Engine.

uid

Assigns a user ID.

userid

Range of administrator-assigned user ID numbers (2001-2147483647).

username

Specifies a username.

name

Name of the user.

add-capability

Adds capability to an existing user. Use with modify keyword.

del-capability

Deletes capability of an existing user. Use with modify keyword.

Defaults

The default users are admin and anonymous.The default password option is 0.

Command Modes

Global configuration

Usage Guidelines

The user command creates, modifies, and deletes Content Engine user accounts. Up to 50 user accounts can be added to the Content Engine. Only administrator access capability permits a user to write to the Content 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 Content 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 Content 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.

Examples

Console(config)# user add dilbert Console(config)# user add bwhidney password 0 dzgchenpa Console(config)# user modify username bwhidney add-capability admin-access 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

Related Commands Related Commands

show users

wccp custom-web-cache

To enable the Content 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

router-list-num

Specifies router list number.

num

Router list number (1-8).

port

Specifies port number.

port

Port number range (1-65535).

hash-destination-ip

(Optional.) Load-balancing hash - destination IP (default).

hash-destination-port

(Optional.) Load-balancing hash - destination port.

hash-source-ip

(Optional.) Load-balancing hash - source IP.

hash-source-port

(Optional.) Load-balancing hash - source port.

password

(Optional.) Specifies authentication password.

passw

Password.

weight

(Optional.) Sets weight percentage for load balancing (0-100).

percentage

Percentage value (0-100).

Defaults

Command Modes

Global configuration

Usage Guidelines

The wccp custom-web-cache command can configure the Content 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 Content Engine when WCCP is not enabled or when 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 Content Engine cluster (for example, a Content Engine with a weight of 30 receives 30 percent of the total load). If the total of all weight parameters in the Content Engine cluster exceeds 100, the percentage load for each Content Engine is recalculated as the percentage that its weight parameter represents of the
combined total.

Examples

The following example shows the configuration for starting custom Web caching on interface 3 of a WCCP Version 2-enabled router:

router(config): ip wccp 98 [Output not shown] router(config-if): ip interface 3 router(config-if): ip web-cache 98 redirect out [Output not shown]

The following example shows the configuration on the Content Engine:

Console(config)# wccp custom-web-cache router-list-num 5 port 82 weight 30 password Allied hash-destination-ip hash-source-port Console(config)# no wccp custom-web-cache Console(config)# http proxy outgoing ans.allied.com 82 no-local-domain Console# 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 Commands

wccp web-cache

http proxy incoming

http proxy outgoing

wccp flow-redirect

To enable WCCP flow redirection, use the flow-redirect enable global configuration command. Use the no form of the command to disable flow redirection.

wccp flow-redirect enable

no wccp flow-redirect enable

Syntax Description

enable

Enables flow redirection.

Defaults

Enabled

Command Modes

Global configuration

Usage Guidelines

This command works with WCCP Version 2 only. The flow protection feature is designed to keep the TCP flow intact as well as to not overwhelm Content Engines when they come up or are reassigned new traffic. This feature also has a slow start mechanism whereby the Content Engines try to take a load appropriate for their capacity.

Examples

Console(config)# wccp flow-redirect enable

Related Commands

wccp slow-start enable

wccp home-router

To configure a WCCP Version 1 router IP address, use the wccp home-router global configuration command. To disable this function, use the no form of this command.

wccp home-router ip-address

no wccp home-router ip-address

Syntax Description

ip-address

Home router IP address.

Defaults

Disabled

Command Modes

Global configuration

Usage Guidelines

To use WCCP Version 1 with the Content Engine, you must also point the Content 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.

Examples

Console(config)# wccp home-router 172.16.65.243 Console(config)# no wccp home-router 172.16.65.243

Related Commands

show wccp routers

wccp version 1

wccp reverse-proxy

To enable WCCP Version 2 reverse proxy service, use the wccp reverse-proxy global configuration command. To disable this function, use the no form of this command.

wccp reverse-proxy router-list-num number [password key] [weight percentage]

no wccp reverse-proxy

Syntax Description

router-list-num

Router list number.

number

Router list number range (1-8).

password

(Optional.) WCCP services authentication password (key) set on router.

key

(Optional.) Password character string.

weight

(Optional.) Sets a load-balancing parameter.

percentage

Percentage of the load that the Content Engine shares with the other
Content Engines (1-100).

Defaults

Disabled.

Command Modes

Global configuration

Usage Guidelines

This command applies only to WCCP Version 2.

You must configure the wccp router-list command before you use this command. The routers in the list must have WCCP reverse proxy service enabled (service 99). See the Cisco Cache Software Configuration Guide, Release 3.x.x for information on configuring reverse proxy service on the router.

By default, the router does load balancing across the various Content 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, the client's browser IP address).

To enable the use of a password for a secure reverse proxy cache within a cluster, use the wccp reverse-proxy password key command to be sure to enable all other Content Engines and routers within the cluster with the same password.

The weight parameter represents a percentage of the total load redirected to the Content Engine in a cluster (for example, a Content Engine with a weight of 30 receives 30 percent of the total load). If the total of all weight parameters in a Content Engine cluster exceeds 100, the percentage load for each Content Engine is recalculated as the percentage that its weight parameter represents of the combined total.

Examples

Console(config)# wccp reverse-proxy router-list-num 8 password mysecret weight 100 Console(config)# no wccp reverse-proxy

Related Commands

show wccp content-engines

show wccp services

wccp router-list

wccp version 2

wccp router-list

To configure a router list for WCCP Version 2, use the wccp router-list global configuration command. To disable this function, use the no form of this command.

wccp router-list number ip-address

no wccp router-list number ip-address

Syntax Description

number

Router list number (1-32).

ip-address

IP address of router to add to list.

Defaults

Disabled

Command Modes

Global configuration

Usage Guidelines

Use this command to configure various router lists for use with WCCP Version 2 services. For example, you can specify one router list for WCCP Version 2 Web cache service and another list for reverse proxy at the same time without having to reconfigure groups of routers or caches. You can add up to 8 router lists and up to 32 IP addresses per list.

Examples

Console(config)# wccp router-list 7 172.31.68.98 Console(config)# no wccp router-list 7 172.31.68.98

Related Commands

wccp reverse-proxy

wccp web-cache

wccp version 2

wccp shutdown

To set the maximum time interval over which the Content Engine will perform a clean shutdown, use the wccp shutdown global configuration command. To disable the clean shutdown, use the no form of the command.

wccp shutdown max-wait seconds

no wccp shutdown max-wait

Syntax Description

max-wait

Sets the clean shutdown time interval.

seconds

Time in seconds (0-86400). The default is 120 seconds.

Defaults

120 seconds

Command Modes

Global configuration

Usage Guidelines

To prevent broken TCP connections, the Content Engine performs a clean shutdown of WCCP after a reload or wccp version command is issued. The Content Engine does not reboot until either all connections have been serviced or the configured max-wait interval has elapsed.

During a clean shutdown, the Content 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 Content Engine takes itself out of the cluster by having its buckets reassigned to other Content Engines by the lead Content Engine. TCP connections can still be broken if the Content Engine crashes or is rebooted without WCCP being cleanly shut down. The clean shutdown can be aborted while in progress.

Examples

Console(config)# wccp shutdown max-wait 4999

Related Commands

wccp version

wccp slow-start

wccp flow-redirect

wccp slow-start

To enable the slow start capability of the Cisco Cache software on the Content Engine, use the wccp slow-start enable global configuration command. To disable slow start capability, use the no form of this command.

wccp slow-start enable

no wccp slow-start enable

Syntax Description

enable

Enables WCCP slow start.

Defaults

Enabled

Command Modes

Global configuration

Usage Guidelines

Within a cluster of Content Engines, TCP connections are redirected to other Content Engines as units are added or removed. A Content 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 Content 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 Content Engines can be assigned their share of the buckets right away.

Examples

console# wccp slow-start enable console# no wccp slow-start enable

Related Commands

wccp flow-redirect

wccp version

To specify the version of WCCP that the Content Engine should use, enter the wccp version global configuration command. Use the no form of the command to disable the currently running version.

wccp version {1 | 2}

no wccp version {1 | 2}

Syntax Description

1

WCCP Version 1.

2

WCCP Version 2.

Defaults

No default behavior or values

Command Modes

Global configuration

Usage Guidelines

Both WCCP versions allow transparent caching of Web content. For a detailed description of both versions, see the Cisco Cache Software Configuration Guide, Release 3.x.x. It is not necessary to disable WCCP Version 1 before enabling WCCP Version 2, and vice-versa. Be sure the routers used in the WCCP environment are running a software version that supports the WCCP version configured on the Content Engine.

When operating with WCCP Version 2, the Content Engine performs a clean shutdown after a reload, wccp version 1, or no wccp version 2 command is executed. A clean shutdown prevents broken TCP connections.

Examples

Console(config)# no wccp version 1 Console(config)# wccp version 2

Related Commands

wccp home-router

wccp web-cache

To instruct the router to run the Web cache service with WCCP Version 2, use the wccp web-cache global configuration command. To disable this function, use the no form of this command.

wccp web-cache router-list-num number [password key] [weight percentage]

no wccp web-cache

Syntax Description

route-list-num

Specifies router list number.

number

Router list number (1-8).

password

(Optional.) Authentication password (key) set by the router.

key

Password string for the router.

weight

(Optional.) Sets weight percentage.

percentage

Weight of load that the Content Engine carries compared to that of other Content Engines (1-100).

Defaults

The default is no wccp web-cache.

Command Modes

Global configuration

Usage Guidelines

Use this command to enable Web cache service with WCCP Version 2. With Web cache service, the router balances the traffic load within a Content 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 the password key option and be sure to enable all other Content Engines and routers within the cluster with the same password.

The weight parameter represents a percentage of the total load redirected to the Content Engine (for example, a Content Engine with a weight of 30 receives 30 percent of the total load). If the total of all weight parameters in a Content Engine cluster exceeds 100, the percentage load for each Content Engine is recalculated as the percentage that its weight parameter represents of the combined total.

Examples

Console(config)# wccp web-cache router-list-num 1 Console(config)# no wccp web-cache

Related Commands

show wccp content-engines

show wccp routers

show wccp status

wccp version 2

whoami

To display the current user's name, use the whoami EXEC command.

whoami

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to display the current user's username.

Examples

Console# whoami admin

Related Commands

pwd

write

To write running configurations to memory or to a terminal session, use the write EXEC command.

write [erase | memory | terminal]

Syntax Description

erase

(Optional.) Erases startup configuration from NVRAM.

memory

(Optional.) Writes the configuration to NVRAM. This is the default.

terminal

(Optional.) Writes the configuration to a terminal session.

Defaults

The configuration is written to NVRAM by default.

Command Modes

EXEC

Usage Guidelines

Use this command to either save running configurations to NVRAM or 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 Content Engine.

Use the write terminal command to display the current running configuration in the terminal session window. The equivalent command is show running-config.

Examples

Console# write

Related Commands

copy running-config startup-config

show running-config


hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Jun 6 14:18:58 PDT 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.