Table Of Contents

show statistics content-routing

show statistics distribution

show statistics dns-cache

show statistics ftp-native

show statistics ftp-over-http

show statistics http

show statistics http-authcache

show statistics https

show statistics icap

show statistics icmp

show statistics icp

show statistics ip

show statistics ldap

show statistics mediafs

show statistics netstat

show statistics ntlm

show statistics pac-file-server

show statistics pre-load

show statistics radius

show statistics replication

show statistics rtsp

show statistics rule

show statistics services

show statistics snmp

show statistics tacacs

show statistics tcp

show statistics transaction-logs

show statistics tvout

2

show statistics content-routing

To display simplified hybrid content routing statistics, use the show statistics content-routing EXEC command. This command is available only on the Content Router.

show statistics content-routing {all | ce [ce-name] | dns | history | summary | website [fqdn]}

Syntax Description

all	Displays all content routing statistics.
ce	Displays the content routing statistics of the specified Content Engine.
ce-name	(Optional) Name of the Content Engine.
dns	Displays DNS statistics.
history	Displays the content routing statistical history.
summary	Displays the content routing statistical summary.
website	Displays the content routing statistics of the specified website.
fqdn	(Optional) Fully qualified domain name of the website.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use this command to display the request routing activity of the Content Router.

When the ACNS network contains many Content Engines, the ce option generates excessive output of statistical data unless a specific Content Engine is named. When the ACNS network has many content-routed websites, the website option generates excessive output of statistical data unless a specific website is named. The same holds true for the all option.

The clear statistics content-routing command clears all statistics displayed here.

Examples

Table 2-113 describes the fields shown in the show statistics content-routing summary display.

Table 2-113 show statistics content-routing summary Field Descriptions

Field	Description
Requests Received	Total number of content requests received by simplified hybrid routing.
HTTP Requests (normal)	Number of normal HTTP requests received. Normal HTTP requests do not use Advanced Stream Redirector (ASX).
HTTP Requests (ASX)	Number of HTTP requests received in which the URL ends in .asx.
RTSP Requests	Number of RTSP requests received.
HTTP Requests (API)	Number of content routing API requests received.
Requests Redirected	Total number of content requests received by simplified hybrid routing that were redirected.
HTTP 302 Redirects	Number of HTTP 302 redirects issued in response to normal (non-ASX) HTTP requests.
ASX Redirects	Number of ASX redirects issued in response to HTTP ASX requests.
RTSP Redirects	Number of RTSP redirects issued in response to RTSP requests.
Requests Not Redirected	Total number of content requests received by simplified hybrid routing that were not redirected.
No CE Covering Client	Number of requests not redirected because the requesting client was not in the coverage zone of any Content Engine that serves the requested website's content.
Unknown Website	Number of requests not redirected because the requested website is not known to the Content Router.
Route Table Locked	Number of requests not redirected because the route table used by simplified hybrid routing was locked at the time of the request. Locking occurs briefly when the route table must be rebuilt because of a configuration change.
"Stale CE" Requests	Number of Content Engine alias requests received for failed Content Engines. When a Content Router redirects content requests, it generates URLs containing Content Engine alias domain names. An example of a Content Engine alias is sanjose3.ce.cdn.acme.com, where cdn.acme.com is the FQDN of a content-routed website and sanjose3 is the name of a Content Engine to which a client's content request has been redirected. If the target Content Engine fails before the client issues a request to it, the redirect is considered to be stale. (This condition is most likely to happen if the client bookmarks the redirect URL and uses it in the future.) Through the DNS resolution mechanism, stale Content Engine requests are sent to the Content Router, which reroutes the request to another Content Engine that is running.

Table 2-114 describes the fields shown in the show statistics content-routing history display.

Table 2-114 show statistics content-routing history Field Descriptions

Field	Description
Type	First line—History statistics for HTTP and RTSP requests handled by simplified hybrid routing. Second line—History statistics for redirects issued by simplified hybrid routing.
Minimum	Smallest number of requests or redirects in any 1-minute interval over the last hour of operation.
Maximum	Largest number of requests or redirects in any 1-minute interval over the last hour of operation.
Average	Average number of requests or redirects per minute over the last hour of operation.
Last	Number of requests or redirects that occurred in the last whole minute of operation.

Table 2-115 describes the fields shown in the show statistics content-routing dns display.

Table 2-115 show statistics content-routing dns Field Descriptions 

Field	Description
Total DNS queries	Total number of end system DNS queries received.
Web site FQDNs	Number of DNS queries for the FQDNs of content-routed websites. The Content Router resolves a website FQDN by returning its own IP address.
Content Engine aliases	Number of DNS queries for Content Engine alias domain names. These domain names appear in redirect URLs generated by the Content Router. A sample Content Engine alias is sanjose3.ce.cdn.acme.com, where cdn.acme.com is the FQDN of a content-routed website and sanjose3 is the name of a Content Engine to which a client's content request has been redirected. The Content Router resolves a Content Engine alias by returning the IP address of the Content Engine.
Aliases for Down CEs	Number of DNS queries for Content Engine alias domain names, when the Content Engine has failed. The Content Router considers a Content Engine to have failed when keepalive messages are no longer received from the Content Engine. The Content Router resolves these queries by returning its own IP address, forcing a subsequent redirect to a Content Engine that is running.
Unknown domains	Number of DNS queries for domains unknown to the Content Router. The Content Router responds to these queries with an NXDOMAIN reply.
PTR queries	Number of reverse mapping pointer (PTR) DNS queries that match the Content Router's IP address. Given an IP address, this record maps it to the Content Router's hostname.
Failed	Number of DNS queries that resulted in a SERVFAIL response.
Dropped	Number of DNS queries that were dropped.
Content engine keepalives	Number of keepalive messages received from Content Engines. These messages are included in the DNS statistics because they are sent as specially formatted DNS queries and are processed by the Content Router's DNS subsystem. Keepalive messages are not included in the DNS query statistics above.
From unknown source	Number of keepalive messages received from Content Engines that are unknown to the Content Router. A continually increasing value for this statistic indicates a possible misconfiguration of the Content Router.

Table 2-116 describes the fields shown in the show statistics content-routing website display.

Table 2-116 show statistics content-routing website Field Descriptions 

Field	Description
HTTP Requests (normal)	Number of normal (non-ASX) HTTP requests received for this website.
HTTP Requests (ASX)	Number of HTTP requests received for this website in which the URL ends in .asx.
RTSP Requests	Number of RTSP requests received for this website.
HTTP 302 Redirects	Number of HTTP 302 redirects issued for this website in response to normal (non-ASX) HTTP requests.
ASX Redirects	Number of ASX redirects issued for this website in response to HTTP ASX requests.
RTSP Redirects	Number of RTSP redirects issued for this website in response to RTSP requests.

Table 2-117 describes the fields shown in the show statistics content-routing ce display.

Table 2-117 show statistics content-routing ce Field Descriptions 

Field	Description
IP Address	IP address of the Content Engine. The Content Router learns this address from the Content Engine's keepalive messages.
Aliveness	Either up or down. The Content Router considers a Content Engine to be up if the Content Router is receiving keepalive messages from the Content Engine. The Content Router will not route requests to a Content Engine that is down.
HTTP 302 Redirects	Number of HTTP 302 redirects to this Content Engine. These redirects are issued in response to normal (non-ASX) HTTP requests.
ASX Redirects	Number of ASX redirects to this Content Engine. These redirects are issued in response to HTTP ASX requests.
RTSP Redirects	Number of RTSP redirects to this Content Engine. These redirects are issued in response to RTSP requests.
Number of Keepalives	Number of successive keepalive messages received from the Content Engine since the last down to up transition.

Related Commands

clear statistics content-routing
show content-routing

show statistics distribution

To display the statistics of the content distribution components, use the show statistics distribution EXEC command.

show statistics distribution {all | errors {channel-id channel-num | channel-name name} | mcast-data-receiver [detail] | mcast-data-sender [channel-id channel-num | channel-name name detail] | metadata-receiver | metadata-sender | unicast-data-receiver [channel-id channel_num [pending-queue jobs | suspended-queue jobs | waiting-queue [first | last] [jobs]] | channel-name [pending-queue jobs | suspended-queue jobs | waiting-queue [first | last] [max_jobs]] | hot-forwarders [forwarder_id | forwarder_name] {idle-queue | priority-queue} channels | idle-forwarders max_idle_forwarders] | unicast-data-sender}

Syntax Description

all	Displays the content distribution statistics for all distribution components.
errors	Displays the distribution error records for the specified channel.
channel-id	(Optional) Displays statistics about the specified channel ID.
channel-num	Channel number (0-4294967295).
channel-name	Displays statistics about the specified channel name.
name	Channel name.
mcast-data-receiver	Displays the content distribution statistics of the multicast data receiver.
detail	(Optional) Displays detailed statistics.
mcast-data-sender	Displays the content distribution statistics of the multicast data sender.
metadata-receiver	Displays the content distribution statistics of the metadata receiver.
metadata-sender	Displays the content distribution statistics of the metadata sender.
unicast-data-receiver	Displays the content distribution statistics of the unicast data receiver.
pending-queue	(Optional) Displays the queue that contains jobs ready to be run.
jobs	Maximum number of jobs to be displayed. The default is 5.
suspended-queue	(Optional) Displays the queue that contains jobs suspended because of multicast.
waiting-queue	(Optional) Displays the queue that contains jobs waiting to be run.
first	(Optional) Displays the first jobs in the waiting queue.
last	(Optional) Displays the last jobs in the waiting queue.
max_jobs	(Optional) Maximum number of jobs to be displayed (for the first or last options). The default is 5.
hot-forwarders	(Optional) Displays the content distribution statistics of hot forwarders.
forwarder_id	(Optional) Identifier for the hot forwarder Content Engine.
forwarder_name	(Optional) Name of the hot forwarder Content Engine.
idle-queue	Displays the channels from which the forwarder Content Engine is not selecting jobs at present.
priority-queue	Displays the channels from which the forwarder Content Engine is selecting jobs at present.
channels	Maximum number of channels to be displayed. The default is 3.
idle-forwarders	(Optional) Displays the content distribution statistics of idle forwarders.
max_idle_forwarders	Maximum number of idle forwarder Content Engines to be displayed. The default is 3.
unicast-data-sender	Displays the content distribution statistics of the unicast data sender.

Defaults

pending-queue jobs: 5

waiting-queue first max_jobs: 5

waiting-queue last max_jobs: 5

idle-queue channels: 3

priority-queue channels: 3

idle-forwarders max_idle_forwarders: 3

Command Modes

EXEC

Usage Guidelines

The ACNS 5.2 software and later releases support new multicast file transfer features that enhance the reliability and performance of multicast file distribution. In earlier ACNS software releases (ACNS 5.0 software and ACNS 5.1 software), the file transfer session depended on a window of time to resend the missing packets. The sender had to transmit the packets within this window of time for each retransmission request (NACK) from receiver Content Engines. If a multicast receiver joined the session too late and missed blocks of data that were outside the transmission window, the sender would not resend the missing blocks. The receiver could not receive the entire file, and the transmission failed. The receiver had to wait until a subsequent carousel pass to recover the missed files. The receiver could only receive the entire file or nothing. A slow receiver often failed to receive a large file if the receiving rate lagged behind the sending rate.

The multicast file transfer enhancements in the ACNS 5.2 software and later releases resolve these issues by eliminating the window of time for file transmissions. This feature is called checkpoint. Checkpoint allows the sender to divide the transferring file into blocks and to retransmit any and all blocks until the transfer session ends. At any time during the transfer session, a receiver can request retransmission of any block that it has missed. Also, receiver Content Engines can receive the blocks of a transfer in any order. Data transmission can occur over a longer period, and receivers can recover missed data blocks to successfully complete the transfer in most situations. File transfers are much more resistant to loss of data.

This feature also solves the problem of a multicast receiver joining a transfer session late. Even if a receiver goes offline and restarts during a transfer, it can recover missing data without requesting retransmission of the blocks that it has already received.

---

Note Because of these enhancements, receivers using the ACNS 5.2 software and later releases cannot interact with senders using the ACNS 5.0 or 5.1 software. The ACNS 5.2 multicast receiver will ignore files sent from an ACNS 5.0 or 5.1 multicast sender. However, an ACNS 5.2 multicast sender can interoperate with ACNS 5.0 or 5.1 multicast receivers because the software detects the lower software version and disables checkpoint. We recommend that you upgrade your multicast sender to the ACNS 5.2 software and later releases first and then upgrade your receivers to the ACNS 5.2 software and later releases.

---

Examples

Except for the lines "Files Ready to Schedule," "Files Not Ready to Schedule," "Next File Ready in," "Current Files Scheduled," "Total Files Sent," and "Total File Transmissions," which are unaffected by the clear statistics command, the show statistics distribution mcast-data-sender command output displays multicast sender statistical information that has accumulated since the last reboot or since the clear statistics distribution multicast-data-receiver or multicast-data-sender commands were entered.

Table 2-118 describes the fields shown in the show statistics distribution mcast-data-sender display.

Table 2-118 show statistics distribution mcast-data-sender Field Descriptions 

Field	Description
File Transfer Information
Total Files Sent	Total number of files sent through the multicast at least once.
Total File Transmissions	Number of carousel passes that the sender Content Engine has completed including retransmission of missing files for on-demand carousels.
Total Bytes Transferred	Total number of bytes of content (excluding overhead byte count) sent through the multicast and the amount of time taken for multicast.
Scheduling Information
Files Ready to Schedule	Number of files that are to be multicast after their latest delay period. Delay periods are determined by either the multicast sender-delay command value, or in the case of multiple carousels, from the carousel delay period in the multicast cloud. If ready, the multicast sender application attempts to schedule these files immediately.
Files Not Ready to Schedule	Number of files that are to be multicast but continue to be delayed by their latest delay period. After these files successfully pass their delay period, they move into the "Files Ready to Schedule" state.
Next File Ready in	Displays one of three states: •No unsent multicast files exist—The "Files Ready to Schedule" and "Files Not Ready to Schedule" lines are both 0, as shown in the example preceding the table. •The "Files Ready to Schedule" line is a nonzero value—In this state, "Now" is displayed on the "Next File Ready in" line. •The "Files Ready to Schedule" line is 0 while the "Files Not Ready to Schedule" line is nonzero—In this state, the amount of time until the earliest of these files will become "Ready to Schedule" is displayed in the format: numberofdaysd numberofhoursh numberofminutesm numberofsecondss as follows: 1d 2h 12m 4s 1h 48m 0s 1h 12s 12m 3s 12s
Current Files Scheduled	Current number of files scheduled.
Current Bytes Scheduled	Current number of bytes of content scheduled to be sent.
Max Files that can be Scheduled Simultaneously	Maximum number of files that can be scheduled by the multicast sender at any one time.
Multicast Sender Failover/Fallback [on Primary Sender] Information
Total Number of Heartbeat Received	Number of keepalive packets that have been periodically received by the primary sender from the backup sender to detect whether the backup sender is active.
Total Number of Failed heartbeat	Number of keepalive packets that have been dropped during transmission from the backup sender to the primary sender.
Last failed Heartbeat Time	Amount of time that has elapsed since the primary sender did not hear a heartbeat from the backup sender for the status probe requests that it sent to the backup sender.
Total Number of Init Probes Sent	Number of RPC initialization status probe requests that have been sent to the multicast receiver.
Total Number of Failed Init Probes	Number of RPC initialization status probe requests for which the multicast receiver failed to respond.
Last Failed Init Probe Time	Amount of time that has elapsed since the last initialization status probe request was sent to the multicast receiver.
Last Time Init State was Entered	Amount of time that has elapsed since the multicast sender was in initialization state.
Last Time Active State was Entered	Amount of time that has elapsed since the multicast sender was in the active state.
Last Time Failover/Fallback Statistics was Cleared	Amount of time that has elapsed since the clear statistics distribution multicast-data-receiver command was used.
File-Level Nacks Information received from Multicast Receivers
Nack processed OK	Number of NACK messages received by the multicast sender in response to which the sender retransmits missing data packets.
Nack Invalid	Number of NACK messages that are declared as invalid by the multicast sender. This situation might occur when NACK messages unicast by the receiver are corrupted during their passage through the network elements forwarding NACKs PGM-hop-by-PGM-hop to the source.
Nack too Busy to Handle	Number of NACK messages in response to which missing content could not be sent because many receiver Content Engines generated more traffic than the sender could handle.
On-demand Mcast Triggered	Number of carousel passes that have been completed in response to NACK messages that trigger a resend of the content.
On-demand Mcast Not Triggered (reach max carousel)	Number of carousel passes that have not triggered a resend of the content because the maximum number of carousel passes configured on the multicast sender has been used up. Note When the maximum number of carousel passes is reached for a file on the current active sender, you can configure file distribution to fall back to unicast.
Send Errors	This section is displayed in the output of the show statistics distribution mcast-data-sender command only if any error has occurred during multicasting of the content.
File Submission Failures	Number of files that failed during submission. Note If the error counts continue to increase, it is important to monitor the failures at the sender error log (/local/local1/errorlog/dist-mcast-sender-errorlog.current).
Catalog Record Access Failures	Failure that occurs if a channel or a content object is deleted after the file is scheduled but before it is sent. An error condition is displayed if database problems occur.
Insertion Failures	Internal multicast file sender errors.
Unrecognized Transfers	Internal file transfer errors resulting from database or internal data structure problems.
UNS File Access Failures	During multicast file transfer, the sender accesses the unified name space (UNS) to open and read the file being distributed. If the sender gets errors from UNS, it aborts the job transfer session and increases this error count.
Resource Record Access Failures	Errors displayed if the content is deleted. Such errors are likely to be reported as a "Catalog Record Access Failure."
Outdated Transfer requests	Indications that the content has changed (the newer content has arrived) between the time that the content was scheduled to be sent and the time that it was actually sent.
Stale Objects Abort	During multicast file transfer, the sender checks to determine if the file being transferred is out of date. This scenario can occur if the root Content Engine detects that the content on the original server has changed and then refreshes the content. If the sender gets the new metadata, but the content file is out of date, it stops the file transfer and increases this error count. The sender resends the file when it gets the new file from its forwarder.

Except for the Files Being Received line, which is unaffected by the clear statistics command, the show statistics distribution mcast-data-receiver output displays multicast data receiver statistical information that has accumulated since the last reboot or since the clear statistics distribution multicast-data-sender or multicast-data-receiver command was entered.

Table 2-119 describes the fields shown in the show statistics distribution mcast-data-receiver display.

Table 2-119 mcast-data-receiver Field Descriptions 

Field	Description
Files Being Received	Current file count based on reading the database.
Total Files Received	Total number of files received from the multicast since the last reboot or clear statistics command.
Total Bytes Received	Total number of bytes of content (excluding overhead byte count) received from the multicast.
Multicast Nack Statistics
Last successful nack	Amount of time that has elasped since the NACK message was sent in response to which the multicast sender resent the content.
Next scheduled nack	Amount of time that has to elapse before the next NACK message is generated by the receiver Content Engine.
Length of last rpc-nack payload	Number of bytes of the NACK message that was last sent to the multicast sender.
Number of last rpc-nack channels	Number of channels of missing files contained in the last NACK message unicast to the sender.
Number of rpc-nack files	Number of NACK messages that have been triggered in response to missing PGM packets.
Receive Errors	Section that is displayed in the output of the show statistics distribution mcast-data-receiver command only if any error has occurred while receiving the multicast content.
Unknown Files Received	Errors indicating that new files were received but cannot be found in the internal data structure at processing time.
File Update Error	Error displayed when a database update is attempted after a new file is received.
Advertisement Rejected - DB Access Failed	Error displayed when an internal file transfer is attempted and the entry cannot be found in an internal data structure. Note Before actually sending a file, the multicast sender advertises that a file is on its way. The receiver must accept the file, or it is not sent to the receiver.
Advertisement Rejected - DB update Failed	Failures in the attempt to update a database (DB) record for the file.
Advertisement Rejected - Unknown Channel	Error counts of a multicast channel that is not accepted by the Content Engine, according to the local database.
Advertisement Rejected - Unknown Meta Data	Error counts of metadata not yet received for this file.
Advertisement Rejected - DB URL Access Failed	Error counts from attempting to read the URL of the file from the database.
Advertisement Rejected - DB UNS Access Failed	Error counts from attempting to read the unified name space (UNS) record for the URL.
Advertisement Rejected - DB Insert Failed	Error counts from attempting to add a record in a data structure.
Symbolic Link Creation Failed	Error counts from attempting to create a symbolic link to receive a file.
Symbolic Link Removal Failed	Error counts from attempting to delete an unnecessary symbolic link after receiving a file.
Content Size Mismatch	Error counts from a mismatch between the size of the file received and the size in its associated metadata.
Md5 Error	Error counts from the mismatch between the received file's Message Digest 5 (MD5) checksum and its metadata checksum.
Total Number of DB Resource Lock Failed	Error counts because the resource record cannot be locked.

Except for the Files Being Received and Last Time Received PGM Advertisement lines, which are unaffected by the clear statistics command, the show statistics distribution mcast-data-receiver detail displays detailed statistics for the multicast receiver that have accumulated since the last reboot or since the clear statistics distribution multicast-data-sender or multicast-data-receiver command was entered:

Table 2-119 describes the fields shown in the show statistics distribution mcast-data-receiver detail display.

Table 2-120 show statistics distribution mcast-data-receiver detail Field Descriptions 

Field	Description
Files Being Received	Current file count based on reading the database.
Total Files Received	Total number of files received from the multicast since the last reboot or clear statistics command.
Total Bytes Received	Total number of bytes of content (excluding overhead byte count) received from the multicast.
Last Time Received PGM Advertisement	Amount of time that has elapsed since the multicast sender's last advertisement of a file. A multicast receiver rejects the multicast sender's advertisement of a file if the proper content metadata has not yet arrived.
Multicast Nack Statistics
Last successful nack	Amount of time that has elasped since the NACK message was sent in response to which the multicast sender resent the content.
Next scheduled nack	Amount of time that has to elapse before the next NACK message is generated by the receiver Content Engine.
Length of last rpc-nack payload	Number of bytes of the NACK message that was last sent to the multicast sender.
Number of last rpc-nack channels	Number of channels of missing files contained in the last NACK message unicast to the sender.
Number of rpc-nack files	Number of NACK messages that have been triggered in response to missing PGM packets.

Table 2-121 describes the fields shown in the show statistics distribution unicast-data-receiver display.

Table 2-121 show statistics distribution unicast-data-receiver Field Descriptions 

Field	Description
Channel ID	Numerical identifier for the channel.
Channel name	Name for the channel.
Current unicast forwarder ID	Numerical identifier for the current unicast forwarder.
Current unicast forwarder name	Name for the current unicast forwarder.
Use hot forwarder	Status of the forwarder Content Engine. Values are Yes or No. Yes means that the forwarder is active, and the job for this channel can be started immediately. No means that the forwarder is currently inactive and may become active some time later depending on the failure reason. For example, any new forwarder must wait at least 1 minute before starting active jobs.
Current running job	Shows statistics for jobs that are currently running.
relative-cdn-url	Relative URL for the current job.
channel-id	Numerical identifier for the channel for this job.
fwdr ip address	IP address of the current unicast forwarder for this job.
bytes written/total	Total number of bytes written for this job.
last write time	Number of seconds since the last write time for this job
Cumulative bps	Number of cumulative bits per second.
Last successful job was done at	Time of completion of the last successful job.
#Consecutive failures	Number of consecutive failures.
#Jobs in pending queue(P_Q)	Number of jobs pending.
#Jobs in suspended queue(S_Q)	Number of jobs suspended.
#Jobs in waiting queue(W_Q)	Number of jobs waiting.
#Bytes of jobs in P_Q and W_Q	Total number of bytes for jobs that are pending and waiting.
#Bytes of jobs in S_Q	Number of bytes for jobs that are suspended.
#Bytes of running jobs	Number of bytes for jobs that are currently running.

Related Commands

clear statistics
show distribution

show statistics dns-cache

To display Content Engine DNS caching statistics, use the show statistics dns-cache EXEC command.

show statistics dns-cache

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

To display a summary of DNS caching statistics, use the show statistics dns-cache command. DNS caching statistics include lookup responses for the resolution of DNS names to addresses, hostname hash statistics, IP address hash statistics, and a long record of other related DNS caching transactions.

Examples

Table 2-122 describes the fields shown in the show statistics dns-cache display.

Table 2-122 show statistics dns-cache Field Descriptions  

Field	Description
Max cache size	Maximum number of DNS cache entries (also referred to as the DNS cache size).
DNS Cache Statistics
Total DNS lookups	Total number of DNS lookups performed by the DNS service module of the caching application running on the Content Engine.
Adds	Number of hostname entries added to the DNS cache.
Deletes	Number of hostname entries deleted from the DNS cache.
Drains	Number of DNS cache entries that have been discarded due to the LRU expiration mechanism of removing old unused entries.
Total Record	Total number of entries contained in the DNS cache service lookup tables.
Hits	Number of cache hits because the requested content (web object) is in the Content Engine cache.
Misses	Number of cache misses because the requested content (web object) is not in the Content Engine cache.
TTL Expired	Number of times that an entry in the cache was found to have an expired TTL value. This entry would then result in a cache miss and that entry being removed from the cache.
ReqLazy Validity Calls	HTTP caching application on the Content Engine that does not need to know the IP address of an origin server immediately but needs to know if the IP address in the client's request matches the origin server's DNS name in the Hostname: header field of an HTTP request. The HTTP cache uses this information to validate that the origin server, which serves the object, matches the IP address used. The HTTP caching application does not prevent clients from accessing servers that have hostnames that do not match the IP address of the given Hostname: header, but it does not cache an HTTP response that does not match. This mechanism prevents hackers from clogging the HTTP cache with undesirable or spoofed objects. Because the HTTP caching application does not need to wait for the DNS lookup to occur immediately, it can continue to retrieve the object from the origin server and send it back to the requesting client while lazily waiting for the validation of hostnames to IP addresses to complete. This value is the count of the number of lazy lookups that have been issued. These types of lookups occur only if the cache is serving a transparently intercepted HTTP request, such as a WCCP redirected request.
ReqLazy Valid	Number of valid lazy hostname to IP address lookups performed. A valid lookup is one that is not negatively cached as being a nonexistent hostname for a correct hostname.
ReqLazy Invalid	Number of invalid lazy resolution of hostnames to IP addresses performed. An invalid lookup is one that is negatively cached as being a nonexistent hostname for a correct hostname. The value of this field is similar to the Bad Hostname Recs field value; however, it is specific only to lazy lookups.
Total Accesses	Total number of times that DNS lookups are performed by the DNS service module for domain name resolution. The value of this field is the same as the value of the Total DNS Lookups field.
Outstanding Queries	Current number of pending queries that are awaiting a response from an upstream DNS server.
Max Outstanding Queries	Maximum number of pending queries that are awaiting a response from an upstream DNS server.
Lazy Accesses	Number of lazy validation requests that had to be passed to an upstream DNS server to be resolved.
Lazy Mismatches	Number of lazy mismatches during the resolution of hostnames to IP addresses. A high value for this field may, but not always, be an indication that a hacker is attempting to populate the HTTP cache with spoofed objects.
Lazy Matches	Number of lazy matches during the resolution of hostnames to IP addresses.
Lazy Cache Hits	Number of lazy cache hits that occurred because the specific entry for the validation of a particular hostname to an IP address was already available in the DNS cache.
Lazy Cache Misses	Number of lazy cache misses that occurred because the specific entry for the validation of a particular hostname to an IP address did not reside in the DNS cache.
Bad Hostname Recs	Number of lookups performed by the DNS name server for a nonexistent hostname.
Bad Hostname Cache Hits	Number of cache hits that occurred when a DNS name server performs a lookup for a nonexistent hostname. The DNS cache holds the information for a short period of time. This method allows the DNS cache to catch any subsequent requests for a bad hostname and quickly respond that the hostname does not exist. The value of this field displays the number of cache hits for such bad hostnames. This type of cache is also called the negative cache because it is a small cache of negative responses.
Bytes Sent	Number of bytes sent to upstream DNS servers (byte count refers to the body of a DNS query only and does not include any IP header byte count overheads).
Bytes Received	Number of bytes received from upstream DNS servers (byte count refers to the body of DNS responses only and does not include any IP header byte count overheads).
I/O Errors	Number of times that a read operation on the network socket resulted in an unexpected error. A high count for this field can indicate a possible network problem.
DNS response not matching lookup	Number of times that a DNS server responded with a response ID that did not match a pending DNS request. It is normal for this value to be nonzero because the DNS caching service module often issues multiple DNS requests if a server response time is high or may issue requests to more than one upstream DNS server. Multiple DNS servers may respond to the request but the first response satisfies the request, while subsequent responses are not needed.
Server down time	Number of times that the DNS cache service marks any upstream DNS server as being down or nonresponsive. A large value for this field indicates either network problems or slow or faulty upstream DNS servers.
Hostname Hash Statistics
total number of members	Number of entries available in the hostname to IP address lookup hash table.
total number of lkups	Number of DNS lookup resolution requests of hostnames to IP addresses received by the DNS cache name server.
number of lkup hits	Number of cache hits on the resolution records of hostnames to IP addresses stored by the DNS cache.
cumu lkups hit cmps	Number of cache hits that occurred when multiple requests are received by the DNS name server for the resolution of a hostname to an IP address. If there is a request already pending for that lookup with an upstream DNS server, then this additional request is piggybacked on to the pending request. While the first request is the result of a cache miss, the piggybacked requests are all cache hits that have accumulated behind the first request or response.
number of lkup misses	Number of cache misses on the resolution records of hostnames to IP addresses stored by the DNS cache.
cumu lkups miss cmps	Number of requests that occurred when multiple requests are received by the DNS name server for resolution of a hostname to an IP address, and if there is a request already pending for that lookup with an upstream DNS server, then this additional request is piggybacked on to the pending request. If the pending request results in a failed lookup response (nonexistent entry for the hostname to the IP address translation), then the accumulated piggybacked requests are also treated as cache misses.
IP Address Hash Statistics
total number of members	Number of entries available in the IP address to hostname lookup hash table.
total number of lkups	Number of DNS lookup resolution requests of IP addresses to hostnames received by the DNS cache name server.
number of lkup hits	Number of cache hits on the resolution records of IP addresses to hostnames stored by the DNS cache.
cumu lkups hit cmps	Number of requests that occurred when multiple requests are received by the DNS name server for the resolution of an IP address to a hostname. If there is a request already pending for that lookup with an upstream DNS server, then this additional request is piggybacked on to the pending request. While the first request is the result of a cache miss, the piggybacked requests are all cache hits that have accumulated behind the first request or response.
number of lkup misses	Number of cache misses on the resolution records of IP addresses to hostnames stored by the DNS cache.
cumu lkups miss cmps	Number of requests that occurred when multiple requests are received by the DNS name server for resolution of an IP address to a hostname. If there is a request already pending for that lookup with an upstream DNS server, then this additional request is piggybacked on to the pending request. If the pending request results in a failed lookup response (nonexistent entry for the hostname to the IP address translation), then the accumulated piggybacked requests are also treated as cache misses.

Related Commands

clear statistics dns-cache
http dns-cache
show http dns-cache

show statistics ftp-native

To display Content Engine FTP native statistics, use the show statistics ftp-native EXEC command.

show statistics ftp-native

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use the show statistics ftp-native EXEC command to display statistics for the FTP native requests that the Content Engine has handled. The command output shows the number of FTP native GET requests received by the Content Engine, the number of FTP native hits and misses for GET requests, and the number of FTP native PUT requests that have been received by this Content Engine.

Examples

Table 2-123 describes the fields shown in the show statistics ftp-native display.

Table 2-123 show statistics ftp-native Field Descriptions 

Field	Description
FTP-Native GET requests received	Number of FTP-native GET requests received.
FTP-Native Hits for GET requests
Number of hits	Number of FTP-native hits for GET requests.
Percentage	Percentage of hits to total GET requests received.
Bytes	Number of bytes received.
FTP-Native Misses for GET requests
Number of misses	Number of FTP-native misses for GET requests.
Percentage	Percentage of misses to total GET requests received.
Bytes	Number of bytes missed.
FTP-Native PUT requests received	Number of FTP-native PUT requests received.

Related Commands

clear statistics ftp-native
ftp-native
show ftp-native

show statistics ftp-over-http

To display Content Engine FTP-over-HTTP statistics, use the show statistics ftp-over-http EXEC command.

show statistics ftp-over-http

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

Use the show statistics ftp-over-http EXEC command to display statistics for the FTP-over-HTTP requests that the Content Engine has handled. The command output shows the number of FTP-over-HTTP requests received by the Content Engine, the number of FTP-over-HTTP hits and misses, and the number of FTP-over-HTTP requests that the Content Engine has forwarded to the origin FTP server or to the specified outgoing proxy server. The command output also shows the number of FTP-over-HTTP errors.

Examples

Table 2-124 describes the fields shown in the show statistics ftp-over-http display.

Table 2-124 show statistics ftp-over-http Field Descriptions 

Field	Description
FTP-over-HTTP requests received	Number of FTP-over-HTTP requests received.
FTP-over-HTTP Hits
Number of hits	Number of FTP-over-HTTP hits for HTTP requests.
Percentage	Percentage of hits to total HTTP requests received.
Bytes	Number of bytes received.
FTP-over-HTTP Misses
Number of misses	Number of FTP-over-HTTP misses for HTTP requests.
Percentage	Percentage of misses to total HTTP requests received.
Bytes	Number of bytes missed.
Requests sent to Outgoing Proxy	Number of requests sent to the outgoing proxy.
Requests sent to origin ftp server	Number of requests sent to the origin FTP server.
FTP-over-HTTP error count	Number of FTP-over-HTTP errors.

Related Commands

clear statistics ftp-over-http
ftp-over-http
show ftp-over-http

show statistics http

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

show statistics http {cluster | ims | miss-reason | monitor [url url] | object | performance | proxy outgoing | requests | savings | usage}

Syntax Description

cluster	Displays HTTP healing mode statistics.
ims	Displays HTTP if-modified-since statistics.
miss-reason	Displays HTTP cache-miss statistics and reasons for cache-misses.
monitor	Displays statistics for all the monitored URLs.
url	(Optional) Displays monitoring statistics for a specified URL.
url	URL for which monitoring statistics are displayed.
object	Displays HTTP object statistics.
performance	Displays HTTP performance statistics.
proxy outgoing	Displays outgoing proxy monitor statistics.
requests	Displays HTTP request statistics.
savings	Displays HTTP saving statistics.
usage	Displays HTTP usage statistics.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-125 describes the fields shown in the show statistics http requests displays.

Table 2-125 show statistics http requests Field Descriptions 

Field	Description
Total Received Requests	Total number of requests received by the Content Engine.
Forced Reloads	Number of times that the HTTP requests received from clients required a noncached response to be served directly by the origin server. You can perform this action by pressing Ctrl-F5 in the Microsoft Internet Explorer browser and by pressing the Shift key while clicking the Reload button in the Netscape, Mozilla, and Firefox browsers.
Client Errors	Number of client error requests or authentication failures handled by the Content Engine.
Server Errors	Number of origin server errors or authentication failures handled by the Content Engine.
URL Blocked (Reset)	Number of client requests to URLs specified in the HTTP good sites' list file that reset the TCP client connection without specifying any error.
URL Blocked	Number of client requests to URLs specified in the HTTP good sites' list file that resulted in a Content Engine-generated error page being sent to the client.
Sent to Outgoing Proxy	Number of requests sent to the outgoing proxy servers configured on the Content Engine. These outgoing proxy servers can be other Content Engines or standard proxy servers that can be contacted to process HTTP cache misses without using ICP or WCCP.
Failures from Outgoing Proxy	Number of requests that failed to be served by the outgoing proxy servers. If the primary outgoing proxy server fails to respond to the HTTP request, the server is noted as failed and the requests are redirected to the next outgoing proxy server until one of the proxies services the request. A failover occurs in the order that the proxy servers were configured. If all of the configured proxy servers fail, the Content Engine can optionally redirect HTTP requests to the origin server specified in the HTTP header if you have used the http proxy outgoing origin-server global configuration command. If the origin-server option is not enabled, the client receives an error message.
Excluded from Outgoing Proxy	Number of requests with a destination specified in the proxy-protocols outgoing-proxy exclude global configuration command that bypass the primary outgoing proxy server and the failover proxy servers.
ICP Client Hits	Number of requests that resulted in the web object being served by the ICP clients from their cache.
ICP Server Hits	Number of requests that generated ICP queries resulting in the requested web object being served from the cache of the ICP servers. These requests allow the Content Engine to probe the hierarchy of Content Engines by multicasting an ICP message to the ICP parent and sibling clients in the hierarchy.
If-Range Hits	Number of requests with the If-Range request header field contained in the message sent from a web client to the Content Engine that are served from the Content Engine cache. If a client has a partial copy of an entity in its cache and wants to have an up-to-date copy of the entire entity in its cache, it could use the Range request header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.) If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server provides the specified subrange of the entity using a 206 (Partial content) response. If the entity tag does not match, then the server returns the entire entity using a 200 (OK) response.
HTTP 0.9 Requests	Number of requests made using the HTTP 0.9 version. HTTP/0.9 cannot manage caches because document transfers are not optimized. HTTP/0.9, which is the first version of HTTP, has only the GET method. Everything is performed with this method, including sending data to the server (the requested URI looks like the following: http://www.foo.bar/url?var1=foo; the string that follows the first question mark means that the variable called var1 is set to foo).
HTTP 1.0 Requests	Number of requests made using the HTTP 1.0 version. HTTP/1.0 provided a simple caching mechanism. An origin server may mark a response, using the Expires header, with a time until which the cache could return the response without violating semantic transparency. A cache may check the current validity of a response using a conditional request. It may include an If-Modified-Since header in a request for the resource, specifying the value in the cached response's Last-Modified header. The server may then either respond with a 304 (Not Modified) status code, implying that the cache entry is valid, or it may send a normal 200 (OK) response to replace the cache entry. HTTP/1.0 also included a mechanism, the Pragma: no-cache header, for the client to indicate that a request should not be satisfied from a cache.
HTTP 1.1 Requests	Number of requests made using the HTTP 1.1 version. HTTP/1.1 includes a number of new conditional request-headers, in addition to If-Modified-Since. The most basic is If-None-Match, which allows a client to present one or more entity tags from its cache entries for a resource. If none of these matches the resource's current entity tag value, the server returns a normal response; otherwise, it may return a 304 (Not Modified) response with an ETag header that indicates which cache entry is currently valid. This mechanism allows the server to cycle through a set of possible responses, while the If-Modified-Since mechanism only generates a cache hit if the most recent response is valid. HTTP/1.1 also adds new conditional headers called If-Unmodified-Since and If-Match, which create other forms of preconditions on requests.
HTTP Unknown Requests	Number of requests with an unknown request method that could not be resolved by the Content Engine. The HTTP protocol anomaly is an unknown HTTP request. Known requests are OPTION, GET, HEAD, POST, PUT, DELETE, TRACE, and CONNECT.
Non HTTP Requests	Number of requests received by the Content Engine using other protocols, such as RTSP or HTTPS.
Non HTTP Responses	Number of responses sent by the Content Engine using other protocols, such as RTSP or HTTPS.
Chunked HTTP Responses	Number of responses sent to web clients that contained chunked transfer-encoded (CTE) objects (the http cache-chunk-encoded enable global configuration command). HTTP 1.0 clients do not support CTE. If an object is stored in a CTE format, then the Content Engine must refetch the object from the source HTTP server if the HTTP client is not HTTP 1.1 compliant.
Http Miss Due To DNS	Number of HTTP requests that resulted in a cache miss (web object not available in the cache) because of DNS lookup failures. Domain name resolution requires that at least one DNS name server be configured on the Content Engine.
Http Deletes Due To DNS	Number of requests for which web objects were deleted from the cache. The response received from the remote server is cached for a maximum or minimum time frame after which it expires and is deleted from the cache. You can configure the DNS caching name service to use an expired response if it is in its cache, while initiating a new lookup to renew the cached object. This configuration is particularly useful when the upstream DNS is slow or unresponsive. The expired response continues to be used until the entry is updated by a new response or is purged from the cache using the Least Recently Used (LRU) algorithm.
Objects cached for min ttl	Number of requests received for objects cached with a minimum TTL setting (the http min-ttl global configuration command).
On-Demand Requests	Number of requests for the on-demand content. The on-demand content is acquired and cached by the Content Engine and then delivered by the Content Engine in response to a client request. When the first client request is made for a piece of content, the Content Engine pulls the data from the origin web server and serves it to the client. The content is also stored (or cached) on the Content Engine. Subsequent requests for the same content are served to the client directly from the Content Engine cache.
CDN Content Hits	Number of requests that resulted in a cache hit (the web object was available in the cache) for all Content Engines in the ACNS network.
CDN Content Misses	Number of requests that resulted in a cache miss (the web object was not available in the cache) for all Content Engines in the ACNS network.
CDN Object Expired	Number of requests received by all Content Engines in the ACNS network for the expired content. An object is considered stale or expired if the age of the cached object has exceeded its freshness lifetime. The age of a cached object is the time that the object has been stored in the Content Engine's cache without the Content Engine contacting the origin server to check if the object is still fresh.
Content Routing Redirects	Number of client requests for the content redirected by the Content Router to the closest Content Engine in the ACNS network containing that content.

The following example displays the statistics regarding the savings because the Content Engine serviced HTTP requests from its local HTTP cache (cache hits) instead of retrieving the content from the origin web server. You can use this command to see whether or not the cache is caching the request correctly.

ContentEngine# show statistics http savings

                         Statistics - Savings

                        Requests                          Bytes

         -----------------------------------------------------------

  Total:               525980242                    79047534484

   Hits:                 1966223                    19865155481

   Miss:               524014019                    59182379003

Savings:                     0.4 %                         25.1 %

ContentEngine# show statistics http usage

     Statistics - Usage

               Current      Peak

               -----------------

  CPU Usage:       0 %      66 %

 Disk Usage:

  Disk 0           0 %      24 %

  Disk 1           0 %      25 %

  Disk 2           0 %       4 %

HTTP Requests:

  active           6      1085

  idle client     39      8123

  idle server     10       908

Server Responses Sent = 0

The show statistics http miss-reason command displays cache miss statistics and the reasons why objects are not being cached by the Content Engine. Once you know the reason for a miss or a no-store, you can try to correct it.

Table 2-126 describes the fields in the output from the show statistics http miss-reason command.

Table 2-126 show statistics http miss-reason Field Descriptions 

Field	Description
Statistics - No hit reasons
not_in_cache	Requested file not available in the cache.
dmbuf_low	Size of the Content Engine's data buffers is small.
none_get_method	HTTP request method that is in an incoming request from a client is a method other than POST, HEAD, PUT. This method is added using the http add-method command.
ftp_not_anonymous	FTP requests sent from authenticated web clients.
http_not_anonymous	HTTP requests sent from authenticated web clients.
suspicious_url	HTTP request URL that contains the question mark (?) followed by data, cgi-bin, or aw-cgi.
ie_5_ims	If-Modified-Since request header field sent in the message from the client browser using Internet Explorer Version 5.
has_if_match	If-Match request header field sent in the message from a web client. A client that has one or more entities previously obtained from the resource verifies that one of those entities is current by including a list of its associated entity tags in the If-Match header field.
has_invalid_if_range	Invalid If-Range request header field contained in the message sent from a web client to the Content Engine. If a client has a partial copy of an entity in its cache and wants to have an up-to-date copy of the entire entity in its cache, it could use the Range request header with a conditional GET (using either or both of If-Unmodified-Since and If-Match). However, if the condition fails because the entity has been modified, the client has to make a second request to obtain the entire current entity body. The If-Range header allows a client to prevent the second request.
has_if_unmodified_since	If-Unmodified-Since request header field contained in the message sent from the client browser. If the requested resource has not been modified since the time specified in this field, the Content Engine performs the requested operation as if the If-Unmodified-Since header is not present.
has_invalid_range	Invalid Range request header field contained in the message sent from the client. If a client has a partial copy of an entity in its cache and wants to have an updated copy of the entire entity in its cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match).
has_more_than_supported_ range	Byte range that is sent in the message from the client is not within the set of supported values. Byte range specifications in HTTP apply to the sequence of bytes in the entity body (not necessarily the same as the message body). A byte range operation may specify a single range of bytes or a set of ranges within a single entity.
has_pragma_no_cache	Pragma: no-cache request header that is contained in the message sent from HTTP/1.0 clients. HTTP/1.1 caches treat Pragma: no-cache as if the client had sent Cache-Control: no-cache.
has_authorization	Authorization header contained in the message sent from the client. The Authorization field value consists of credentials containing the authentication information of the user agent for the realm of the resource being requested.
has_cache_control_no_ cache	Cache-control: no-cache request header contained in the message sent from the client. When the no-cache directive is present in a request message, the Content Engine forwards the request to the origin server even if it has a cached copy of the request.
is_https	HTTPS-over-HTTP tunneled request sent from the client. The Content Engine can accept native HTTPS traffic from the client and tunnel such requests to the origin HTTPS server.
invalid_ims	If-Modified-Since request header contained in the message from the client is invalid. If the IMS date is not in a valid format, as specified in HTTP 1.0 and HTTP 1.1 RFCs, the IMS date is considered as invalid.
cert_check_fail	Number of requests for which DNS resolution of hostnames to IP addresses failed. This failure might have occurred if you had not specified the IP address of the DNS server that the Content Engine should use for domain name resolution and/or disabled the DNS caching on the Content Engine. Note The value of this field is not related to PKI certificates.
second_validation	Another validation that is pending on the object requested from the Content Engine because the first domain name resolution failed.
invalid_ims_reply	Invalid If-Modified-Since response header contained in the reply from the origin server. The IMS response is considered invalid if it is neither 200 (OK) nor 304 (Not Modified [Conditional Get]).
ims_200_reply	If-Modified-Since request header that resulted in a 200 (OK) response from the origin server. If the request would normally result in anything other than a 200 (OK) status, or if the passed If-Modified-Since date is invalid, the response is the same as for a normal GET.
xfs_open_error	Number of file system errors that have occurred.
has_unknown_length_ transfer_pending	Transfer-length of the message body, in decimal number of octets, that is not known and the response that is pending to be served for a previous request.
object_in_cache_older_than_clients	Time specified in the If-Modified-Since header contained in the message sent from the client is later than the time specified for the object stored in the cache.
object_in_cache_expired_ cannot_verified	Object that is stored in the cache is stale and cannot be served by the cache. The object must be revalidated with the origin server.
different_protocol	Web access protocol that is used by the clients to request web objects is not supported by the Content Engine. Note Support for HTTP, FTP, TFTP, HTTPS and the IETF standard RTP/RTSP protocols is included as part of the ACNS software product. Support for the WMT and RealProxy product features each need a separate license.
other_error	Miscellaneous errors with status codes such as 500 Internal Server Error (Lotus Notes Error) or 503 Service Unavailable.
Statistics - Validate reasons
reval_all	Freshness check that is revalidated by the Content Engine for the content stored in the local cache before serving the content to a client browser, although there is no requirement for a freshness check.
reval_text	Freshness check that is forced by the Content Engine for all text objects stored in the cache, although there is no requirement for a freshness check.
max_age	Age of the cached object that has exceeded its freshness lifetime. Note The age of a cached object is the time that the object has been stored in the Content Engine's cache without the Content Engine explicitly contacting the origin server to check if the object is still fresh.
min_fresh	Minimum Time To Live that was exceeded for an object has expired. This field applies to requests that contain a Cache-control header with a min-fresh directive that queries the object with the specific min-fresh value. If the freshness of the object in the cache is less than the min-fresh directive value, the object is validated with the origin server.
max_stale	Maximum Time To Live that was exceeded for an object requested from the cache that may not have expired already.
response_say_so	Previous response that requires that the Content Engine validate the freshness of requested content in its cache by sending an IMS request to the origin web server.
object_expired	Response that the object is stale and that subsequent content requests require a fresh retrieval from the origin server by the Content Engine. The Content Engine also sends an IMS request to the origin web server when the maximum Time To Live (TTL) has expired.
reval_no_cache_req	Request with the Pragma: no-cache header that is received by the Content Engine and that the Content Engine must revalidate for the content freshness of the HTTP objects in its cache.
rule_refresh	Refresh rule action configured on the Content Engine, forcing a revalidation of the object with the web server.
Statistics - No store reasons
dmbuf_low	Size of the Content Engine's data buffers is small.
none_get_method	HTTP request method in an incoming request from a client is other than POST, HEAD, PUT. This HTTP method is added using the http add-method command.
ftp_not_anonymous	FTP requests sent from authenticated web clients.
http_not_anonymous	HTTP requests sent from authenticated web clients.
suspicious_url	HTTP request URL that contains the question mark (?) followed by data, cgi-bin, or aw-cgi.
has_range	Range request header contained in the HTTP response. HTTP retrieval requests using conditional or unconditional GET methods may request one or more subranges of the entity, instead of the entire entity, using the Range request header, which applies to the entity returned as the result of the request:
has_authorization	Authorization header contained in the HTTP response obtained from the origin server.
has_cache_control_no_store	Cache-control:no-store request header contained in the message sent from the origin server. The purpose of the no-store directive is to prevent the inadvertent release or retention of sensitive information (for example, on backup tapes). If sent in a response, the Content Engine cache must not store any part of either this response or the request that elicited it.
invalid_ims	If-Modified-Since request header contained in the response from the origin server is invalid. If the IMS date is not in a valid format, as specified in RFC 2616, the IMS date is considered as invalid.
cert_check_fail	Number of requests for which DNS resolution of hostnames to IP addresses failed. This failure might have occurred if you had not specified the IP address of the DNS server that the Content Engine should use for domain name resolution and/or disabled DNS caching on the Content Engine.
second_validation	Domain name resolution that failed and another validation that is pending on the object requested from the Content Engine.
invalid_ims_reply	Invalid If-Modified-Since response header contained in the reply from the origin server. The IMS response is considered invalid if it is neither 200 (OK) nor 304 (Not Modified [Conditional Get]).
url_too_long	Length of the request URL that exceeds 255 characters.
http_0_9_reply	Object being requested from the Content Engine's cache and sent to the client that is HTTP 0.9 compliant.
header_too_long	HTTP request header fields that are longer than 8 KB.
http_unknown_verion_reply	HTTP response that is returned to the client contained an unknown version.
http_none_cachable_reply_status	HTTP response that indicates that objects served to the client must not be cached as authenticated objects. The HTTP reply status codes except 200, 301, and 305 fall into this category.
http_unknow_reply_status	Status code of the HTTP reply sent to the client is unknown. The HTTP response status line consists of an HTTP status code.
has_cookie	Set-Cookie header that is part of an HTTP response sent by the Content Engine while returning the object to the client. Note Cookies are a general mechanism that server-side connections (such as CGI scripts) use to both store and retrieve information on the client side of the connection.
object_too_big	Maximum size of the object stored in the cache is exceeded. An object with a size above the configurable upper limit is not stored by the Content Engine.
has_pragma_no_cache	Pragma: no-cache header contained in the HTTP response returned to the client. Note HTTP/1.1 caches treat Pragma: no-cache as if the client had sent Cache-Control: no-cache.
cache_control_no_cache	Cache-Control: no-cache general-header field contained in the HTTP response returned to the client. If the no-cache directive does not specify a field name, then the Content Engine must not use the response to satisfy a subsequent request without successful revalidation with the origin server. This setting allows an origin server to prevent caching even by caches that have been configured to return stale responses to client requests.
cache_control_no_store	Cache-Control: no-store general-header field contained in the HTTP response returned to the client. The purpose of the no-store directive is to prevent the inadvertent release or retention of sensitive information (for example, on backup tapes). If sent in a response, the cache does not store any part of either this response or the request that elicited it.
cache_control_private	Cache-Control: private general-header field contained in the HTTP response returned to the client. All or part of the response message is intended for a single user and must not be cached by a shared cache. This setting allows an origin server to state that the specified parts of the response are intended for only one user and are not a valid response for requests by other users.
has_multipart	Response to a request for multiple nonoverlapping ranges that is transmitted as a multipart message. Note When an HTTP 206 (Partial Content) response message includes the content of multiple ranges (a response to a request for multiple nonoverlapping ranges), these ranges are transmitted as a multipart message body. The media type for this purpose is called multipart or byte ranges.
invalid_expire	Invalid Expires header contained in the response sent to the client. The Expires entity-header field contains the date/time after which the response is considered stale. A stale cache entry may not normally be returned by the Content Engine unless it is first validated with the origin server.
invalid_last_modified	Invalid Last-Modified header contained in the response sent to the client. The Last-Modified entity-header field indicates the date and time at which the origin server that believes the variant was last modified.
invalid_date	Date header that is contained in the response sent to the client is invalid if the format does not match the date format specified in the RFC. The Date general-header field represents the date and time at which the message was originated, having the same semantics as orig-date in RFC 822. The field value is an HTTP-date. Note HTTP/1.0 and HTTP/1.1 applications allow three different formats for the representation of date and time stamps: •Sun, 06 Nov 1994 08:49:37 GMT; RFC 822, updated by RFC 1123 •Sunday, 06-Nov-94 08:49:37 GMT; RFC 850, obsoleted by RFC 1036 •Sun Nov 6 08:49:37 1994; ANSI C's asctime() format The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by RFC 1123 [6] (an update to RFC 822 [7]). The second format is in common use but is based on the obsolete RFC 850 [10] date format and lacks a four-digit year. HTTP/1.0 clients and servers that parse the date value should accept all three formats; they must never generate the third (asctime) format.
content_length_0	Content-Length header field that indicates the size of the entity body is zero. Any Content-Length less than zero is an invalid value.
has_vary	Vary header contained in the response sent to the client. A Vary field value consisting of a list of field-names signals that the representation selected for the response is based on a selection algorithm that considers only the listed request-header field values in selecting the most appropriate representation. Note The Content Engine assumes that the same selection will be made for future requests with the same values for the listed field names for the duration of time for which the response is fresh.
transfer_encoding	Transfer-Encoding general-header field contained in the HTTP response. This header indicates what (if any) type of transformation has been applied to the message body in order to safely transfer it between the sender and the recipient. This transformation differs from the content coding in that the transfer coding is a property of the message, not of the entity.
three_to_two_way	Writing objects to the cache failed during a three-way handshake when establishing adjacencies on point-to-point media. If the client and server connections are still alive, the data transfer reverts to a two-way handshake.
xfs_open_error	Number of file system errors that have occurred.
has_unknown_length_ transfer_pending	Response of unknown content length that is still pending for the previous object requested.
other_error	Miscellaneous errors with status codes such as 500 Internal Server Error (Lotus Notes Error) or 503 Service Unavailable.
weird_server_pipe_though	Origin server that replied with a 200 (OK) response to the client but the Content-Length or Transfer-Encoding header field was not present in the response. However, the Connection: keep-alive header was present in the response.
incorrect_content_length	Content-Length header that indicates the transfer length of the message body is incorrect for the actual length of the object returned to the client.
rule_no_store	Rule action configured on the Content Engine indicates that the requested content should not be stored in the local cache.

The show statistics http monitor EXEC command is available in the ACNS software 5.2.3 and later releases to enable you to display statistics for the monitored URLs.

Table 2-127 describes the fields shown in the show statistics http monitor display.

Table 2-127 show statistics http monitor Field Descriptions

Field	Description
Monitor URL	URL that allows the Content Engine to monitor the performance.
Total requests	Number of the requests serviced for the monitored URL.
Failed requests	Requests that did not succeed (for example, the request failed to resolve the domain name of that URL).
Requests above acceptable delay	Requests that took longer than the specified acceptable delay (the maximum number of seconds specified by the acceptable-delay setting).
Minimum response time	Minimum amount of time taken to process a request for the monitored URL.
Maximum response time	Maximum amount of time taken to process a request for the monitored URL.

Related Commands

clear statistics ftp
ftp
show ftp

show statistics http-authcache

To display Content Engine HTTP authentication cache statistics, use the show statistics http-authcache EXEC command.

show statistics http-authcache

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Syntax Description

To display authentication cache statistics for a Content Engine, use the show statistics http-authcache EXEC command.

Examples

Table 2-128 describes the fields shown in the show statistics http-authcache display.

Table 2-128 show statistics http-authcache Field Descriptions 

Field	Description
Authentication Cache Statistics
Adds	Total number of entries added to the HTTP authentication cache on the Content Engine.
Dels Total	Total number of entries deleted from the authentication cache. The value of this field is equal to the sum of the Dels Timeout, Dels TTL, and Dels Other fields.
Dels Timeout	Number of entries deleted from the authentication cache because of the inactivity timer (the http authentication cache timeout command option).
Dels TTL	Number of entries deleted from the authentication cache because of the absolute TTL timeout (the http authentication cache ttl command option).
Dels Other	Number of entries deleted from the authentication cache for all other reasons (for example, entries that were deleted because the clear users request-authenticated EXEC command was entered).
Hits	Number of times that the requested content (web object) was served from the authentication cache.
Misses	Number of times that the requested content (web object) could not be served from the authentication cache because it was not available.
Current Entries Used	Number of entries maintained in the authentication cache on the Content Engine. The maximum number of entries that is maintained in the authentication cache is 32,000.
No Avail Entry	Number of entries available in the authentication cache.
Avg.Cache Search	Average amount of time required to find an entry in the authentication cache on the Content Engine.
Max Cache Search Miss	Maximum amount of time spent to find an entry in the authentication cache that resulted in a cache miss.
Max Cache Search Hit	Maximum amount of time spent to find an entry in the authentication cache that resulted in a cache hit.
Dup Add Attempts	Number of attempts made to add a duplicate entry to the authentication cache on the Content Engine.
Number of Compares	Number of times that the Content Engine compares the requested web object against the objects stored in the authentication cache.
Userid Passwd Too Long	Number of failures that occurred when an attempt was made to add an entry to the authentication cache because of the length of the username and password strings.
Started Xacts	Number of transactions in progress between the Content Engine and clients.
Completed Xacts	Number of completed transactions. A transaction denotes a completed request (whether successful or failed) for a web resource by a client.
Unknown Node Type	Number of entries with an unknown node type retained in the HTTP authentication cache.
Groups Cache Statistics
Requests	Number of requests made by clients for authenticated objects maintained in the authentication group cache.
Hits	Number of times that the requested content (web object) was served from the authentication group cache.
Misses	Number of times that the requested content (web object) could not be served from the authentication group cache because it was not available.
Overflows	Number of times that the size of the authentication group cache configured on the Content Engine was exceeded.
Deletes	Number of entries deleted from the authentication group cache for reasons, such as the absolute TTL timeout.
Total Size	Maximum size of the authentication group cache in KB. This size is limited by the physical resources available on the Content Engine.
Number of items	Number of entries retained in the authentication group cache on the Content Engine. This number is limited by the physical resources available on the Content Engine.
Memory used	Size of the memory occupied by the entries in the authentication group cache.
Bad message size	Incorrect authentication message size.
Key not found	Number of times that an entry failed to be added to the authentication group cache because of problems with the authentication key.
Bad AC Entry	Number of incorrect entries maintained in the HTTP authentication group cache.
Received auths	Number of authenticated web objects received by the Content Engine from the origin server.
Good Auths	Number of requests that resulted in the authentication cache returning a success message to the authentication module running on the Content Engine.
Bad Auths	Number of requests that resulted in the authentication cache returning a failure message to the authentication module running on the Content Engine.
No Pending xact	Number of transactions pending between the Content Engine and clients.
AM Prot errors	Number of socket read errors that occurred in the authentication module.
Bad Node type	Number of entries with an unknown node type retained in the HTTP authentication cache.
Request went allowmode	Number of requests for authenticated objects that were served when allow mode was enabled on the Content Engine. When allowmode is enabled, the Content Engine allows all HTTP traffic to continue through it (it proceeds with normal traffic processing) even if it fails to receive responses from the URL filtering server.

Related Commands

clear statistics http-authcache
show http-authcache

show statistics https

To display Content Engine Hypertext Transfer Protocol Secure (HTTPS) statistics, use the show statistics https EXEC command.

show statistics https [error | requests]

Syntax Description

error	(Optional) Displays HTTP error statistics.
requests	(Optional) Displays nontunneled HTTPS request statistics.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-129 describes the fields shown in the show statistics https display.

Table 2-129 show statistics https Field Descriptions 

Field	Description
HTTPS Statistics
Total connections	Total number of HTTPS connections.
Connection errors	Total number of HTTPS connection errors.
Total bytes	Total number of bytes through this connection.
Bytes received from client	Number of bytes received from the client.
Bytes sent to client	Number of bytes sent to the client.
% of Total	Percentage of the total for each counter.

Related Commands

clear statistics https
https
https server
show https

show statistics icap

To display ICAP-related statistics for the Content Engine, use the show statistics icap EXEC command.

show statistics icap

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-130 describes the fields shown in the show statistics icap display.

Table 2-130 show statistics icap Field Descriptions 

Field	Description
ICAP-client statistics (http proxy)	Statistics of the client of the ICAP process running on the Content Engine. The client of the ICAP process refers to the caching application that contacts the ICAP process which in turn communicates with the ICAP server. The server of the ICAP process refers to the ICAP server.
Total requests for V1 via RPC	Total number of client requests processed at the vectoring point V1.
Time per ICAP request (last 1k reqs)	Time taken to process each ICAP request. This field displays the time taken per request for the last 1000 requests.
ICAP daemon connection error	Number of errors that occurred when the caching application on the Content Engine attempted to connect to the ICAP daemon on the Content Engine.
Bad packets from ICAP daemon	Number of responses received by the Content Engine from the ICAP daemon that were not correct.
Error parsing HTTP req hdr from ICAP	Number of HTTP response headers received from the ICAP daemon that were incorrect. The ICAP daemon is the outgoing proxy server of the Content Engine.
ICAP daemon internal error	Number of internal errors that occurred on an ICAP daemon.
Total requests via outgoing proxy	Total number of requests sent from the caching application to the ICAP process through the outgoing proxy configured on the Content Engine.
ICAP daemon overloaded	Number of times that the ICAP process running on the Content Engine was overloaded.
Other errors	Number of all other errors that occurred when an ICAP request is processed.
ICAP Daemon statistics	Statistics recorded on the ICAP daemon running on the Content Engine.
Total requests served	Total number of requests that were served by the ICAP daemon running on the Content Engine.
Total bytes to ICAP-Client	Total number of bytes sent to the ICAP client running on the Content Engine.
Average latency in milliseconds	Average delay in serving ICAP requests to ICAP clients in milliseconds.
ICAP Service statistics	Statistics for each ICAP service configured on the Content Engine.
Service	Name of the configured ICAP service.
Service Errors	Number of error messages returned by the ICAP service in response to client requests. These errors are also entered in the transaction log to show the status of the action performed by the ICAP service.
Service Bypasses	Number of requests that bypassed this ICAP service. The value of this field is incremented when you have configured this service to be bypassed when an error occurs with this service.
Server	Hostname or IP address of the ICAP server. Displays the statistics associated with the ICAP server. More than one ICAP service may be associated with an ICAP service.
Total Reqmods (0), Total Respmods (0)	Total number of requests processed at the reqmod-precache, reqmod-postcache, or respmod-precache vector points.
Modifications (Reqmod - 0), (Respmod - 0)	Total number of requests for which the request header or request body was modified after processing at the reqmod-precache, reqmod-postcache, or respmod-precache vector points.
No Modifications (Reqmod - 0), (Respmod - 0)	Total number of requests for which the request header or request body was not modified after processing at the reqmod-precache, reqmod-postcache, or respmod-precache vector points.
Error Responses (Reqmod - 0), (Respmod - 0)	Total number of requests for which error responses were returned to the client after processing at the reqmod-precache, reqmod-postcache, or respmod-precache vector points.
Server Errors	Number of errors that occurred at the ICAP server.
Server Bypasses	Number of times the ICAP server was bypassed during request processing.
Options Req Success	Number of keepalive requests made by the Content Engine to the ICAP server that succeeded. The ICAP OPTIONS method is used by the ICAP client to retrieve configuration information from the ICAP server. In this method, the ICAP client sends a request addressed to a specific ICAP resource and receives a response with options that are specific to the service named by the URL. All OPTIONS requests may also return options that are global to the server (apply to all services). The OPTIONS method consists of a request line, such as the following example: OPTIONS icap://icap.server.net/sample-service ICAP/1.0 User-Agent: ICAP-client-XYZ/1.001 In the following example, an ICAP Client sends an OPTIONS Request to an ICAP Service named icap.server.net/sample-service to receive configuration information for the service provided. OPTIONS icap://icap.server.net/sample-service ICAP/1.0 Host: icap.server.net User-Agent: BazookaDotCom-ICAP-Client-Library/2.3
Options Req Failed	Number of keepalive requests made by the Content Engine to the ICAP server that failed.
Max Conn Available	Maximum number of connections that can be made to the ICAP server.
Used Connections	Number of connections currently established with the ICAP server.
Total Bytes sent	Total number of bytes sent to the ICAP server.
Total Bytes received	Total number of bytes received from the ICAP server.
Total BPS sent	Total number of bytes sent per second to the ICAP server.
Total BPS received	Total number of bytes received per second from the ICAP server.
Server State	Current state of the connections made to the ICAP server. This field displays Not Available, CONNECTED, or DISCONNECTED.

Related Commands

icap

show statistics icmp

To display Content Engine Internet Control Message Protocol (ICMP) statistics, use the show statistics icmp EXEC command.

show statistics icmp

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

ICMP messages are sent in several situations, such as when a datagram cannot reach its destination, when the gateway does not have the buffering capacity to forward a datagram, and when the gateway can direct the host to send traffic on a shorter route. The purpose of these control messages is to provide feedback about problems in the communication environment, not to make IP reliable. There is still no guarantee that a datagram will be delivered or a control message will be returned. Some datagrams may still be undelivered without any report of their loss.

The ICMP messages typically report errors in the processing of datagrams. To avoid the infinite regress of messages about messages, no ICMP messages are sent about ICMP messages. Also, ICMP messages are only sent about errors in handling fragment zero of fragmented datagrams.

ICMP messages are sent using the basic IP header. The first octet of the data portion of the datagram is a ICMP type field; the value of this field determines the format of the remaining data.

Many of the type fields contain more specific information about the error condition identified by a code value. ICMP messages have two types of codes:

•Query

•Error

Queries contain no additional information because they ask for information and will show a value of 0 in the code field. ICMP uses the queries as shown in Table 2-131.

Table 2-131 Queries 

Query	Type Field Value
Echo Reply	0
Echo Request	8
Router Advertisement	9
Router Solicitation	10
Time-stamp Request	13
Time-stamp Reply	14
Information Request (obsolete)	15
Information Reply (obsolete)	16
Address Mask Request	17
Address Mask Reply	18

Error messages give specific information and have varying values that further describe conditions. Error messages always include a copy of the offending IP header and up to 8 bytes of the data that caused the host or gateway to send the error message. The source host uses this information to identify and fix the problem reported by the ICMP error message. ICMP uses the error messages as shown in Table 2-132.

Table 2-132 Errors

Error	Type Field Value
Destination Unreachable	3
Source Quench	4
Redirect	5
Time Exceeded	11
Parameter Problems	12

Examples

Table 2-133 describes the fields shown in the show statistics icmp display.

Table 2-133 show statistics icmp Field Descriptions  

Field	Description
ICMP messages received	Total number of ICMP messages received by the Content Engine.
ICMP messages receive failed	Total number of ICMP messages that were not received by the Content Engine.
Destination unreachable	Number of destination-unreachable ICMP packets received by the Content Engine. A destination-unreachable message (Type 1) is generated in response to a packet that cannot be delivered to its destination address for reasons other than congestion. The reasons for the nondelivery of a packet is described by the code field value. Destination-unreachable packets use the code field values to further describe the function of the ICMP message being sent.
Timeout in transit	Number of ICMP time-exceeded packets received by the Content Engine. The time-exceeded message occurs when a router receives a datagram with a TTL of 0 or 1. IP uses the TTL field to prevent infinite routing loops. A router cannot forward a datagram that has a TTL of 0 or 1. Instead, it trashes the datagram and sends a time-exceeded message. Two different time-exceeded error codes can occur as follows: •0 = Time-To-Live Equals 0 During Transit •1 = Time-To-Live Equals 0 During Reassembly A router cannot forward a datagram with a TTL of 0 or 1 both during transit or reassembly. The TTL timer is measured in seconds and originally was used before the existence of routers to guarantee that a datagram did not live on the Internet forever. Each gateway processing a datagram reduces this value by at least one if it takes longer to process and forward the datagram. When this value expires, the gateway trashes the datagram and sends a message back to the sender notifying the host of the situation.
Wrong parameters	Number of ICMP packets with parameter problems received by the Content Engine. An IP datagram that has been received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 12 denote a parameter problem on a datagram. ICMP parameter-problem datagrams are issued when a router has had to drop a malformed datagram. This condition is a normal and necessary type of network traffic; however, large numbers of this datagram type on the network can indicate network difficulties or hostile actions. A host or gateway can send this message when no other ICMP message covering the problem can be used to alert the sending host.
Source quenches	Number of ICMP source-quench packets received by the Content Engine. A receiving host generates a source-quench message when it cannot process datagrams at the speed requested due to a lack of memory or internal resources. This message serves as a simple flow control mechanism that a receiving host can use to alert a sender to slow down its data transmission. When the source host receives this message, it must pass this information on to the upper-layer process, such as TCP, which then must control the flow of the application's data stream. A router generates this message when, in the process of forwarding datagrams, it has run low on buffers and cannot queue the datagram for delivery.
Redirects	Number of ICMP redirect packets received by the Content Engine. A router sends a redirect error to the sender of an IP datagram when the sender should have sent the datagram to a different router or directly to an end host (if the end host is local). The message assists the sending host to direct a misdirected datagram to a gateway or host. This alert does not guarantee proper delivery; the sending host has to correct the problem if possible. Only gateways generate redirect messages to inform source hosts of misguided datagrams. A gateway receiving a misdirected frame does not trash the offending datagram if it can forward it.
Echo requests	Number of echo ICMP packets received by the Content Engine. An echo request is an IP datagram that has been received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 8. The ICMP echo request is issued by the source to determine if the destination is alive. When the destination receives the request, it replies with an ICMP echo reply. This request and reply pair is most commonly implemented using the ping utility. Many network management tools use this utility or some derivative of it, and this condition is common as a part of network traffic. Note You should be suspicious when a large number of these packets are found on the network.
Echo replies	Number of echo-reply ICMP packets received by the Content Engine. An echo reply is the message that is generated in response to an echo request message. An echo reply is an IP datagram that has been received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 0. This condition is common as a part of network traffic. Note You should be suspicious when a large number of these packets are found on the network.
Timestamp requests	Number of ICMP time-stamp request packets received by the Content Engine. An ICMP time-stamp request is an IP datagram that has been received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 13. The ICMP time-stamp request and reply pair can be used to synchronize system clocks on the network. The requesting system issues the time-stamp request bound for a destination, and the destination system responds with a time-stamp reply message. This condition is normal as a part of network traffic but is uncommon on most networks. Note You should be suspicious when a large number of these packets are found on the network.
Timestamp replies	Number of ICMP time-stamp reply packets received by the Content Engine. Time-stamp request and reply messages work in tandem. You have the option of using time stamps. When used, a time-stamp request permits a system to query another for the current time. It expects a recommended value returned to be the number of milliseconds since midnight, UTC. This message provides millisecond resolution. The two systems compare the three time stamps and use a round-trip time to adjust the sender's or receiver's time if necessary. Most systems set the transmit and receive time as the same value.
Address mask requests	Number of ICMP address mask requests packets received by the Content Engine. An ICMP address mask request is an IP datagram that has been received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 17. ICMP address mask requests could be used to perform reconnaissance sweeps of networks. The ICMP address mask request and reply pair can be used to determine the subnet mask used on the network. When the requesting system issues the address mask request bound for a destination, the destination system responds with an address mask reply message. This condition can be a part of normal network traffic but is uncommon on most networks. Note You should be suspicious when a large number of these packets are found on the network.
Address mask replies	Number of ICMP address mask replies packets received by the Content Engine. An address mask ICMP reply is an IP datagram that has been received with the protocol field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 18. No known exploits incorporate this option. The ICMP address mask request and reply pair can be used to determine the subnet mask used on the network. When the requesting system issues the address mask request bound for a destination, the destination system responds with an address mask reply message. This condition can be a part of normal network traffic but is uncommon on most networks. Note You should be suspicious when a large number of these packets are found on the network.
ICMP messages sent	Total number of ICMP messages sent by the Content Engine.
ICMP messages send failed	Total number of ICMP messages that failed to be sent by the Content Engine.
Destination unreachable	Number of destination-unreachable ICMP packets sent by the Content Engine.
Timeout in transit	Number of ICMP time-exceeded packets sent by the Content Engine.
Wrong parameters	Number of ICMP packets with parameter problems sent by the Content Engine.
Source quenches	Number of ICMP source-quench packets sent by the Content Engine.
Redirects	Number of ICMP redirect packets sent by the Content Engine.
Echo requests	Number of echo ICMP packets sent by the Content Engine.
Echo replies	Number of echo-reply ICMP packets sent by the Content Engine.
Timestamp requests	Number of ICMP time-stamp request packets sent by the Content Engine.
Timestamp replies	Number of ICMP time-stamp reply packets sent by the Content Engine.
Address mask requests	Number of ICMP address mask requests sent by the Content Engine.
Address mask replies	Number of ICMP address mask replies sent by the Content Engine.

Related Commands

clear statistics icmp

show statistics icp

To display Content Engine Internet Cache Protocol (ICP) statistics, use the show statistics icp EXEC command.

show statistics icp {client | server}

Syntax Description

client	Displays ICP client caching statistics.
server	Displays ICP server caching statistics.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-134 describes the fields shown in the show statistics icp display.

Table 2-134 show statistics icp client Field Descriptions  

Field	Description
ICP remote server	Hostname or IP address of the configured ICP server.
Requests Sent	Number of ICP queries sent to ICP server Content Engines in a caching hierarchy.
Requests Timeout	Number of ICP queries that occurred in the time that the parent ICP client Content Engine waits before retrieving the requested data directly from the Internet was exceeded.
Replies Received	Number of responses received for the ICP queries sent to ICP server Content Engines.
Replies Hit	Number of ICP queries that resulted in a cache hit (the requested object was available in the cache of the ICP clients).
Replies Miss	Number of ICP queries that resulted in a cache miss (the requested object was not available in the cache of the ICP clients).
Replies Denied	Number of replies for an ICP query that was denied access to the requested content.
Replies Miss No fetch	Number of ICP queries that resulted in a cache miss because the ICP remote client was configured to not fetch a cache miss.
Replies Error	Number of erroneous replies received from the ICP server Content Engines.
Replies None	Number of ICP queries for which no reply was received from the ICP server Content Engines.
Total Icp client Requests	Total number of ICP requests sent to the ICP server.
Total Icp client Hits	Total number of ICP requests that resulted in a cache hit from the ICP server.

Table 2-135 describes the fields shown in the show statistics icp server display.

Table 2-135 show statistics icp-server Field Descriptions  

Field	Description
ICP remote client	Hostname or IP address of the configured ICP server.
Requests Received	Number of ICP queries received by ICP server Content Engines from IP remote clients in a caching hierarchy.
Requests URL Error	Number of ICP queries received by ICP server Content Engines that contained a URL error.
Replies Sent	Number of responses sent to the ICP remote clients for the ICP queries received by the ICP server Content Engines.
Replies Hit s	Number of ICP queries that resulted in a cache hit (the requested object was available in the cache of the ICP servers).
Replies Miss	Number of ICP queries that resulted in a cache miss (the requested object was not available in the cache of ICP servers).
Replies Miss No fetch	Number of ICP queries that resulted in a cache miss because the ICP remote client was configured to not fetch a cache miss.
Total Icp server Requests	Total number of ICP requests received by the ICP server.
Total Icp server Hits	Total number of ICP requests that resulted in a cache hit from the ICP server.
Total Icp server Denied	Number of ICP queries for which the ICP server denied access to the requested content.

Related Commands

clear statistics icp
icp
show icp

show statistics ip

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

show statistics ip

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-136 describes the fields shown in the show statistics ip display.

Table 2-136 show statistics ip Field Descriptions  

Field	Description
Total packets in	Total number of input datagrams received from interfaces, including those received in error.
with invalid header	Number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, Time To Live exceeded, errors discovered in processing their IP options, and so on.
with invalid address	Number of input datagrams discarded because the IP address in the IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (for example, 0.0.0.0) and addresses of unsupported classes (for example, Class E). For entities that are not IP routers and do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
forwarded	Number of input datagrams for which this entity was not the final IP destination, but the Content Engine attempted to find a route to forward them to that final destination. In entities that do not act as IP routers, this counter will include only those packets that were source-routed through this entity, and the source-route option processing was successful.
unknown protocol	Number of locally addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
discarded	Number of input IP datagrams that were discarded even though the datagrams encountered no problems to prevent their continued processing. This counter does not include any datagrams discarded while awaiting reassembly.
delivered	Total number of input datagrams successfully delivered to IP user protocols (including ICMP).
Total packets out	Total number of IP datagrams that local IP user protocols (including ICMP) supplied to IP in requests for transmission. This counter does not include any datagrams counted in the forwarded field.
dropped	Number of output IP datagrams that were discarded even though the datagrams encountered no problems that would prevent their transmission to their destination. This counter would include datagrams counted in the forwarded field if any such packets met this (discretionary) discard criterion.
dropped (no route)	Number of IP datagrams that were discarded because the Content Engine found no route to transmit them to their destination. This counter includes any packets counted in the forwarded field that meet this no-route criterion including any datagrams that a host cannot route because all of its default routers are down.
Fragments dropped after timeout	Number of received fragments at this entity that are dropped after being held for the maximum number of seconds while awaiting reassembly at this entity.
Reassemblies required	Number of IP fragments received that needed to be reassembled at this entity.
Packets reassembled	Number of IP datagrams successfully reassembled.
Packets reassemble failed	Number of failures detected by the IP reassembly algorithm (because of reasons such as timed out and errors.) This counter is not necessarily a count of discarded IP fragments because some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.
Fragments received	Number of IP datagrams that have been successfully fragmented at this entity.
Fragments failed	Number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be fragmented for reasons such as the Don't Fragment flag was set.
Fragments created	Number of IP datagram fragments that have been generated as a result of fragmentation at this entity.

Related Commands

clear statistics ip
ip
show ip routes

show statistics ldap

To display Content Engine LDAP (Lightweight Directory Access Protocol) statistics, use the show statistics ldap EXEC command.

show statistics ldap

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-137 describes the fields shown in the show statistics ldap display.

Table 2-137 Field Descriptions for the show statistics ldap Command

Field	Description
LDAP Statistics
Authentication
Number of access requests	Number of access requests.
Number of access deny responses	Number of access deny responses.
Number of access allow responses	Number of access allow responses.
Authorization
Number of authorization requests	Number of authorization requests.
Number of authorization failure responses	Number of authorization failure responses.
Number of authorization success responses	Number of authorization success responses.
Accounting
Number of accounting requests	Number of accounting requests.
Number of accounting failure responses	Number of accounting failure responses.
Number of accounting success responses	Number of accounting success responses.

Related Commands

clear statistics ldap
ldap
show ldap

show statistics mediafs

To view media file system (mediafs) statistics, use the show statistics mediafs EXEC command.

show statistics mediafs

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-138 describes the fields shown in the show statistics mediafs display.

Table 2-138 show statistics mediafs  

Field	Description
size of physical file system	Physical disk size of the mediafs file system.
space assigned for MEDIAFS purposes	Amount of physical disk space on the mediafs storage partition that has been assigned to hold objects from streaming proxy servers, such as WMT and RealProxy.
Space used by Real Proxy	Amount of physical disk space on the mediafs file system that has been assigned to hold objects from RealProxy servers. This storage partition is used to store any RTSP streaming media content that is cached on the Content Engine.
Space used by WMT Proxy	Amount of physical disk space on the mediafs storage partition that has been assigned to hold objects from Windows Media servers. This storage partition is used to store any WMT streaming media content that is cached on the Content Engine.
physical file system in use	Amount of physical disk space currently in use by the mediafs storage partition.
physical file system space free	Amount of unused physical disk space in the mediafs storage partition.
physical file system percentage in use	Percentage of physical disk space in use relative to the total disk space available.

Related Commands

disk config
show disks details

show statistics netstat

To display Content Engine Internet socket connection statistics, use the show statistics netstat EXEC command.

show statistics netstat

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-139 describes the fields shown in the show statistics netstat display.

Table 2-139 show statistics netstat Field Descriptions 

Field	Description
Active Internet connections (w/o servers)	The following output prints the list of all open Internet connections to and from this WAE.
Proto	Layer 4 protocol used on the Internet connection, such as, TCP, UDP, and so forth.
Recv-Q	Amount of data buffered by the Layer 4 protocol stack in the receive direction on a connection.
Send-Q	Amount of data buffered by the Layer 4 precool stack in the send direction on a connection.
Local Address	IP address and Layer 4 port used at the WAE end point of a connection.
Foreign Address	IP address and Layer 4 port used at the remote end point of a connection.
State	Layer 4 state of a connection. TCP states include the following: ESTABLISHED, TIME-WAIT, LAST-ACK, CLOSED, CLOSED-WAIT, SYN-SENT, SYN-RCVD, SYN-SENT, SYN-ACK-SENT, and LISTEN.

show statistics ntlm

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

show statistics ntlm

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-140 describes the fields shown in the show statistics ntlm display.

Table 2-140 Field Descriptions for the show statistics ntlm Command

Field	Description
NTLM Statistics
Authentication
Number of access requests	Number of access requests.
Number of access deny responses	Number of access deny responses.
Number of access allow responses	Number of access allow responses.
Authorization
Number of authorization requests	Number of authorization requests.
Number of authorization failure responses	Number of authorization failure responses.
Number of authorization success responses	Number of authorization success responses.

Related Commands

clear statistics ntlm
ntlm
show ntlm

show statistics pac-file-server

To display how many files the PAC file server has served, use the show statistics pac-file-server EXEC command.

show statistics pac-file-server

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

The following example displays the number of files served by the PAC file server:

ContentEngine# show statistics pac-file-server  
PAC File Server Statistics  
--------------------------  
 
PAC Files Served: 999

Related Commands

clear statistics pac-file-server
debug pac-file-server
show pac-file-server

show statistics pre-load

To display Content Engine preload statistics, use the show statistics pre-load EXEC command.

show statistics pre-load

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-141 describes the fields shown in the show statistics pre-load display.

Table 2-141 show statistics pre-load Field Descriptions 

Field	Description
Statistics of last Preloading operation
Preloading was initiated by force	Preloading initiation status.
Preloading started at	Date and time that the preloading started.
Preloading ended at	Date and time that the preloading ended.
List of preloaded URLs are in	Path to the local directory and folder that contains the list of preloaded files.
Preload errlog is	Path to the local directory that contains the preload error logs.
Number of invalid entries in URL list file	Number of invalid entries in URL list file.
Total number of preloaded objects	Total number of preloaded objects.
Total number of preloaded bytes	Total number of preloaded bytes.

Related Commands

clear statistics pre-load
pre-load
show pre-load

show statistics radius

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

show statistics radius

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-142 describes the fields in the show statistics radius display.

Table 2-142 show statistics radius Field Descriptions

Field	Description
RADIUS Statistics
Authentication
Number of access requests	Number of access requests.
Number of access deny responses	Number of access deny responses.
Number of access allow responses	Number of access allow responses.
Authorization
Number of authorization requests	Number of authorization requests.
Number of authorization failure responses	Number of authorization failure responses.
Number of authorization success responses	Number of authorization success responses.
Accounting
Number of accounting requests	Number of accounting requests.
Number of accounting failure responses	Number of accounting failure responses.
Number of accounting success responses	Number of accounting success responses.

Related Commands

clear statistics radius
radius-server
show radius-server

show statistics replication

To display channel replication status and related statistical data on the Content Distribution Manager, use the following show statistics replication EXEC command.

show statistics replication {channels [selected-channel site-name channel-name] | content-engines selected-channel site-name channel-name [content-engine ce-name] [refetch] | content-items content-name selected-channel site-name channel-name {all-content-engines [refetch] | content-engine ce-name [fully-replicated [refetch] | not-fully-replicated [refetch] | refetch [fully-replicated | not-fully-replicated]]} | item url}

To display channel replication status and related statistical data on the Content Engine, use the following show statistics replication EXEC command.

show statistics replication {channels [selected-channel site-name channel-name] | content-items content-name selected-channel site-name channel-name [fully-replicated | not-fully-replicated]}

Syntax Description

channels	Displays the replication status of the specified channels.
selected-channel	(Optional) Specifies a channel website and name.
site-name	Name of the website.
channel-name	Name of the channel.
content-engines	Displays the replication status of the specified Content Engines.
content-engine	(Optional) Specifies a Content Engine.
ce-name	Name of the Content Engine.
refetch	(Optional) Initiates a request to fetch the status again (Content Distribution Manager only).
content-items	Displays the replication status of the specified content items.
content-name	Content item name or pattern including an asterisk (*) and question mark (?). Use an asterisk to select all content items.
all-content-engines	Displays the replication status of the specified content items for all Content Engines in a channel.
fully-replicated	(Optional) Selects only those content items that are fully replicated.
not-fully-replicated	(Optional) Selects only those content items that are not fully replicated.
item	Displays the detailed replication status of a content item across all Content Engines in a channel.
url	URL of the content item.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

The show statistics replication commands that display the channel replication status on the Content Distribution Manager have been modified in the ACNS software, Release 5.2 and later releases to show the progressive file count status during acquisition and replication.

From the Content Distribution Manager, use the show statistics replication channels command to display the overall replication summary for all channels with details about the number of Content Engines in various states, the root Content Engine acquirer status for the channel, and the distribution status for the channel.

Use the show statistics replication channels selected-channel site-name channel-name command to display the replication status for all the Content Engines assigned to a particular channel.

Use the show statistics replication content-engines selected-channel channel content-engine ce-name command to display the replication status for the selected channel in the selected Content Engine.

From the Content Engine, use the show statistics replication channels command to display the replication status of all channels to which the Content Engine has been assigned.

Use the show statistics replication channels selected-channel site-name channel-name command to display details about a specific channel to which the Content Engine is assigned.

Examples

Table 2-143 describes the fields shown in the show statistics replication displays.

Table 2-143 show statistics replication Field Descriptions

Field	Description
Channel	Channel name.
State	Overall state of the channel. Values are Complete or Failed.
User Selected Root CE	Name of the root Content Engine that has been selected for channel.
Current Root CE	Name of the currently acting root Content Engine for the channel.
Receiver CEs Completed	Total number of Content Engines that have completed content replication for the channel.
Receiver CEs In Progress	Total number of Content Engines for which content replication is in progress for the channel.
Receiver CEs Failed	Total number of Content Engines that have some error condition and are treated as failed.
Receiver CEs Not Responding	Total number of Content Engines not responding to the replication status queries from the Content Distribution Manager.
Device	Name and ID of the device.
Website	Name of the website used for the channel.
Type	Role of the device, such as Root or Receiver.
State	State of the Content Engine replication. For receiver Content Engines, states are Failed, Replicating, or Completed. For the root Content Engine, states are Acquiring Content, Rechecking Content, or Completed.
Status	Replication status. Values are Red for failure and Green for success.
Completed	Number of content items completed.
To Do	Number of content items pending for the channel.
Failed	Number of failed content items.
Total	Total number of content items.
Last Report Time	Time that this status was obtained.
Disk Quota Used	Total disk quota used for the channel.
Manifest Last Modified	Time at which the manifest file was last modified.
Manifest Last Check	Time at which the manifest file was last checked for freshness.
Manifest State	State of the manifest. Values are Complete or Error with details of the error displayed.

show statistics rtsp

To display Real-Time Streaming Protocol (RTSP) statistics, use the show rtsp EXEC command.

show statistics rtsp {proxy media-real {requests | savings}} | server cisco-streaming-engine {all | bw-usage | performance | requests}

Syntax Description

proxy	Displays RTSP proxy statistics.
media-real	Displays RealProxy statistics.
requests	Displays RealProxy request statistics.
savings	Displays RealProxy savings statistics.
server	Displays RTSP server statistics.
cisco-streaming-engine	Displays Cisco Streaming Engine statistics.
all	Displays all Cisco Streaming Engine statistics.
bw-usage	Displays Cisco Streaming Engine bandwidth usage statistics.
performance	Displays Cisco Streaming Engine server performance statistics.
requests	Displays Cisco Streaming Engine request statistics.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

The show statistics rtsp proxy media-real requests EXEC command displays RealMedia caching statistics for the RTSP requests that the Content Engine has serviced.

Table 2-144 describes the fields shown in the show statistics rtsp proxy media-real requests display.

Table 2-144 show statistics rtsp proxy media-real requests Field Descriptions 

Field	Description
Media Cache Statistics - Requests
Total Received Requests	Total number of requests served.
Demand Cache Hit	Total number of cache hits.
Demand Cache Miss	Total number of cache misses
Demand Pass-Through	Total number demand pass-through connections.
Live Split	Total number of live-split connections.
Live Pass-Through	Total number of live pass-through connections.

Table 2-145 describes the fields shown in the show statistics rtsp proxy media-real savings display.

Table 2-145 show statistics rtsp proxy media-real savings Field Descriptions 

Field	Description
Media Cache Statistics - Savings
Total	Total number of requests served.
Hits	Total number of cache hits.
Miss	Total number of cache misses
Bytes	Number of bytes bytes delivered.
Savings	Savings incurred by caching because the content was served from the local cache rather than being retrieved multiple times from the origin streaming server.

Table 2-146 describes the fields shown in the show statistics rtsp server cisco-streaming-engine all display.

Table 2-146 show statistics rtsp server cisco-streaming-engine all Field Descriptions 

Field	Description
Cisco Stream Server Request Statistics
Current RTSP sessions	Total number of RTSP sessions.
Current RTP connections	Total number of current RTP connections.
Total RTP connections	Total number of RTP connections.
Cisco Stream Server Bandwidth Usage Statistics
Current RTP bandwidth	Total number of bits per second for this session.
Average RTP bandwidth	Average number of bits per second for the connection.
Total Bytes output by server	Total number of bytes output by the server.
Total Packets output by server	Total number of packets output by the server.
Cisco Stream Server Performance Statistics
CPU Usage	Percentage of CPU capacity used for this session.
Uptime	Number of seconds that the connection has been up.

Related Commands

clear statistics rtsp
rtsp
show rtsp

show statistics rule

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

show statistics rule {all | http {action [action-type]} | pattern-list {all | listnum} | rtsp}

Syntax Description

all	Displays statistics of all the rules.
http	Displays statistics of all the rules that apply to HTTP, HTTPS, and WMT-HTTP requests.
action	Displays statistics of all the rules with the same action.
action-type	(Optional) Action type (see Table 2-92 on page 2-556): see the "Understanding Actions and Patterns" section for explanations of actions and patterns.
pattern-list	Displays statistics of the rule pattern lists.
all	Displays statistics of all the pattern lists.
listnum	Displays statistics of the configured patterns in the specified pattern list. Pattern list numbers range from 1 to 512.
rtsp	Displays statistics for the configured RTSP rules (rules configured for RTSP requests from RealMedia players [the RTSP rules] and rules configured for RTSP requests from Windows Media 9 players [the WMT-RTSP rules]).

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-147 describes the fields shown in the show statistics rule all display.

Table 2-147 show statistics rule all Field Descriptions 

Field	Description
Rules Template Statistics
Rule hit count	Number of matches to the rule.
Rule	Rule that is configured in the Rules Template to which the statistic applies.

Related Commands

clear statistics rule
rule
show rule

show statistics services

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

show statistics services

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-148 describes the fields shown in the show statistics services display.

Table 2-148 show statistics services Field Descriptions

Field	Description
Port Statistics	Service-related statistics for each port on the WAAS device.
Port	Port number.
Total Connections	Number of total connections.

show services ports
show services summary

show statistics snmp

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

show statistics snmp

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-149 describes the fields shown in the show statistics snmp display.

Table 2-149 show statistics 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.

Related Commands

show snmp
snmp-server

show statistics tacacs

To display Content Engine TACACS+ authentication and authorization statistics, use the show statistics tacacs EXEC command.

show statistics tacacs

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-150 describes the fields shown in the show statistics tacacs display for the Content Engine.

Table 2-150 Field Descriptions for the show statistics tacacs Command

Field	Description
TACACS+ Statistics
Authentication
Number of access requests	Number of access requests.
Number of access deny responses	Number of access deny responses.
Number of access allow responses	Number of access allow responses.
Authorization
Number of authorization requests	Number of authorization requests.
Number of authorization failure responses	Number of authorization failure responses.
Number of authorization success responses	Number of authorization success responses.
Accounting
Number of accounting requests	Number of accounting requests.
Number of accounting failure responses	Number of accounting failure responses.
Number of accounting success responses	Number of accounting success responses.

Related Commands

clear statistics tacacs
show tacacs
tacacs

show statistics tcp

To display Content Engine Transmission Control Protocol (TCP) statistics, use the show statistics tcp EXEC command.

show statistics tcp

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Examples

Table 2-151 describes the fields shown in the show statistics tcp display.

Table 2-151 show statistics tcp Field Descriptions 

Field	Description
Server connection openings	Number of connections opened from the Content Engine to the server.
Client connection openings	Number of connections opened from the client to the Content Engine.
Failed connection attempts	Number of incoming SYN connections rejected due to rate limiting or resource shortage.
Connections established	Number of incoming connections that have been set up.
Connections resets received	Number of resets (RSTs) received by the Content Engine.
Connection resets sent	Number of resets (RSTs) sent by the Content Engine.
Segments received	Number of TCP segments received from the client and the server. The value of this field is almost equal to the sum of the values of the Server segments received and the Client segments received fields.
Segments sent	Number of TCP segments sent by the client and the server. The value of this field is almost equal to the sum of the values of the Server segments sent and the Client segments sent fields.
Bad segments received	Number of incoming segments dropped due to checksum or being outside the TCP window.
Segments retransmitted	Number of TCP segments retransmitted by the client and the server. The value of this field is almost equal to the sum of the values of the Server segments retransmitted and the Client segments retransmitted fields.
Retransmit timer expirations	Number of times that the TCP retransmit timer expires. The TCP sender uses a timer to measure the time that has elapsed between sending a data segment and receiving the corresponding ACK from the receiving side of the TCP transmission. When this retransmit timer expires, the sender (according to the RFC standards for TCP congestion control) must reduce its sending rate.
Server segments received	Number of TCP segments received by the Content Engine from the server.
Server segments sent	Number of TCP segments sent by the Content Engine to the server.
Server segments retransmitted	Number of TCP segments retransmitted by the Content Engine from the server.
Client segments received	Number of TCP segments received by the Content Engine from the client.
Client segments sent	Number of TCP segments sent by the Content Engine to the server.
Client segments retransmitted	Number of TCP segments retransmitted by the Content Engine to the client.
Sync cookies sent	Number of synchronized (SYN) cookies sent by the Content Engine. TCP requires unacknowledged data to be retransmitted. The server is supposed to retransmit the SYN.ACK packet before giving up and dropping the connection. When SYN.ACK arrives at the client but the ACK gets lost, there is a disparity about the establishment state between the client and server. Typically, this problem can be solved by the server's retransmission. But in the case of a SYN cookie, there is no state kept on the server and retransmission is impossible.
Sync cookies received	Number of synchronized (SYN) cookies sent by the Content Engine. The entire process of establishing the connection is performed by the ACK packet sent by the client, making the connection process independent of the preceding SYN and SYN.ACK packets. This type of connection establishment opens the possibility of ACK flooding, in the hope that the client will have the correct value to establish a connection. This method also allows you to bypass firewalls that normally only filter packets with SYN bit set.
Sync cookies failed	Number of synchronized (SYN) cookies rejected by the Content Engine. The syncookies feature attempts to protect a socket from a SYN flood attack. This feature is a violation of TCP and conflicts with other areas of TCP such as TCP extensions. It can cause problems for clients and relays. We do not recommend that you use this feature as a tuning mechanism for heavily loaded servers to help with overloaded or misconfigured conditions.
Embryonic connection resets	Number of TCP connections that have been reset before the Content Engine accepted the connection.
Prune message called	Number of calls that the Content Engine makes to the function that tries to reduce the number of received but not acknowledged packets.
Packets pruned from receive queue	Number of packets that the TCP drops from the receive queue (usually due to low memory).
Out-of-order-queue pruned	Number of times that the packet was dropped from the out-of-order queue.
Out-of-window Icmp messages	Number of ICMP packets that were outside the TCP window and dropped.
Lock dropped Icmp messages	Number of ICMP packets that hit a locked (busy) socket and were dropped.
Arp filter	Number of ARPs not sent because they were meant for the Content Engine.
Time-wait sockets	Number of current sockets in the TIME-WAIT state. The TIME-WAIT state removes old duplicates for fast or long connections. The clock-driven ISN selection is unable to prevent the overlap of the old and new sequence spaces. The TIME-WAIT delay allows enough time for all old duplicate segments to die in the Internet before the connection is reopened.
Time-wait sockets recycled	Number of TIME-WAIT sockets that were recycled (the address or port was reused before the waiting period was over). In TCP, the TIME-WAIT state is used for two purposes: •Full-duplex connection close •Protection against old duplicate segments
Time-wait sockets killed	Number of TIME-WAIT sockets that were terminated to reclaim memory.
PAWS passive	Number of passive connections that were made with Protection Against Wrapped Sequence (PAWS) numbers enabled. PAWS operates within a single TCP connection using a state that is saved in the connection control block.
PAWS active	Number of active connections that were made with PAWS enabled. PAWS uses the same TCP time stamps as the round-trip time measurement mechanism and assumes that every received TCP segment (including the data and ACK segments) contains a time-stamp SEG.TSval that has values that are monotone and nondecreasing in time. A segment can be discarded as an old duplicate if it is received with a time-stamp SEG.TSval less than some time stamp recently received on this connection.
PAWS established	Number of current connections that were made with PAWS enabled.
Delayed acks sent	Number of delayed ACK counters sent by the Content Engine.
Delayed acks blocked by socket lock	Number of delayed ACK counters that were blocked because the socket was in use.
Delayed acks lost	Number of delayed ACK counters lost during transmission.
Listen queue overflows	Number of times that the three-way TCP handshake was completed, but enough space was not available in the listen queue.
Connections dropped by listen queue	Number of TCP connections dropped due to a resource shortage.
TCP packets queued to prequeue	Number of TCP packets queued to the prequeue.
TCP packets directly copied from backlog	Number of TCP delivered packets to the client from the backlog queue. Packets are queued in the backlog when the TCP receive routine runs and notices that the socket was locked.
TCP packets directly copied from prequeue	Number of TCP delivered packets to the client from the prequeue.
TCP prequeue dropped packets	Number of TCP packets dropped from the prequeue. The prequeue is where the TCP receive routine runs. It notes that the current running process as the TCP target process and queues it directly for copy after the TCP software interrupt is completed.
TCP header predicted packets	Number of incoming packets that successfully matched the TCP header prediction.
Packets header predicted and queued to user	Number of TCP packets copied directly to the user space.
TCP pure ack packets	Number of acknowledgment (ACK) packets that contain no data.
TCP header predicted acks	Number of incoming ACKs that successfully matched the TCP header prediction.
TCP Reno recoveries	Number of times that the TCP fast recovery algorithm recovered a packet loss. TCP Reno induces packet losses to estimate the available bandwidth in the network. When there are no packet losses, TCP Reno continues to increase its window size by one during each round trip. When it experiences a packet loss, it reduces its window size to one half of the current window size. This feature is called additive increase and multiplicative decrease. TCP Reno, however, does not fairly allocate bandwidth because TCP is not a synchronized rate-based control scheme, which is necessary for the convergence.
TCP SACK recoveries	Number of times that the Content Engine recovered from a selective acknowledgment (SACK) packet loss. If the data receiver has received a SACK-Permitted option on the SYN for this connection, the data receiver may choose to generate SACK options. If the data receiver generates SACK options under any circumstance, it should generate them under all permitted circumstances. If the data receiver has not received a SACK-Permitted option for a given connection, it must not send SACK options on that connection.
TCP SACK reneging	Number of times that the Content Engine refused to accept packets that have not been acknowledged to the data sender, even if the data has already been reported in a SACK option. Such discarding of SACKed packets is discouraged but may be used if the receiver runs out of buffer space. The data receiver may choose not to keep data that it has reported in a SACK option. Because the data receiver may later discard data reported in a SACK option, the sender must not discard data before it is acknowledged by the Acknowledgment Number field in the TCP header.
TCP FACK reorders	Number of forward acknowledgment packets (FACKs) that were out of sequence order. The FACK algorithm makes it possible to treat congestion control during recovery in the same manner as during other parts of the TCP state space. The FACK algorithm is based on first principles of congestion control and is designed to be used with the proposed TCP SACK option. By decoupling congestion control from other algorithms, such as data recovery, it attains more precise control over the data flow in the network. FACK takes advantage of the SACK option; it takes into account which segments have been SACKed. It also uses the receipt of a SACK that leaves at least 3*MSS bytes unacknowledged as a trigger for Fast Retransmit.
TCP SACK reorders	Number of selective acknowledgment (SACK) packets that were out of sequence order.
TCP Reno reorders	Number of TCP Renos that were out of sequence order.
TCP TimeStamp reorders	Number of segments received with out-of-order time stamps.
TCP full undos	Number of times that the congestion window (cwnd) was fully recovered.
TCP partial undos	Number of times that the congestion window (cwnd) was partially recovered.
TCP DSACK undos	Number of times that the duplicate selective acknowledgment packets were recovered.
TCP loss undos	Number of times that the congestion window (cwnd) recovered from a packet loss.
TCP losses	Number of times that data was lost and the size of the congestion window (cwnd) decreased.
TCP lost retransmit	Number of times that a retransmitted packet was lost.
TCP Reno failures	Number of times that the congestion window (cwnd) failed because the TCP fast recovery algorithm failed to recover from a packet loss. The congestion avoidance mechanism, which is adopted by TCP Reno, causes the window size to vary. This situation causes a change in the round-trip delay of the packets, larger delay jitter, and an inefficient use of the available bandwidth due to many retransmissions of the same packets after the packet drops occur. The rate at which each connection updates its window size depends on the round-trip delay of the connection. The connections with shorter delays can update their window sizes faster than other connections with longer delays.
TCP SACK failures	Number of times that the congestion window (cwnd) shrunk because the Content Engine failed to recover from a selective acknowledgment (SACK) packet loss. The selective acknowledgment extension uses two TCP options. The first is an enabling option, SACK-permitted, which may be sent in a SYN segment to indicate that the SACK option can be used once the connection is established. The other is the SACK option, which may be sent over an established connection once permission has been given by the SACK-permitted option.
TCP loss failures	Number of times that the TCP timeout occurred and data recovery failed.
TCP fast retransmissions	Number of TCP fast retransmission counters. TCP may generate an immediate acknowledgment (a duplicate ACK) when an out-of-order segment is received. The duplicate ACK lets the other end know that a segment was received out of order and tells it what sequence number is expected. Because TCP does not know whether a duplicate ACK is caused by a lost segment or just a reordering of segments, it waits for a small number of duplicate ACKs to be received. If there is just a reordering of the segments, there will be only one or two duplicate ACKs before the reordered segment is processed, which will then generate a new ACK. If three or more duplicate ACKs are received in a row, it is a strong indication that a segment has been lost. TCP then retransmits what appears to be the missing segment without waiting for a retransmission timer to expire.
TCP forward retransmissions	Number of TCP forward retransmission counters. This field applies only to SACK-negotiated connections; this field is the counter for FACK segments. The value of this field is for segments that were retransmitted even though there is no indication that they were actually lost. Retransmission is stopped when either one of the following occurs: •The maximum time to wait for a remote response is reached. This timeout occurs when the total time of all retransmission intervals exceeds the maximum time to wait for a remote response. •The number of retransmissions configured in maximum retransmissions per packet is reached.
TCP slowstart retransmissions	Number of TCP slow-start retransmission counters. The slow-start algorithm begins by sending packets at a rate that is determined by the congestion window. The algorithm continues to increase the sending rate until it reaches the limit set by the slow-start threshold (ssthresh) variable. (Initially, the value of the ssthresh variable is adjusted to the receiver's maximum window size [RMSS]. However, when congestion occurs, the ssthresh variable is set to half the current value of the cwnd variable, marking the point of the onset of network congestion for future reference.)
TCP Timeouts	Number of times that a TCP timeout occurred.
TCP Reno recovery fail	Number of times that the TCP fast recovery algorithm failed to recover from a packet loss. In TCP Reno, the maximum number of recoverable packet losses in a congestion window without timeout is limited to one or two packets. No more than six losses can be recovered with a maximum window size of 128 packets. This failure of recovery is because TCP Reno cuts the congestion window by half for each recovered loss.
TCP Sack recovery fail	Number of times that the Content Engine failed to recover from a SACK packet loss. When receiving an ACK containing a SACK option, the data sender should record the selective acknowledgment for future reference. The data sender is assumed to have a retransmission queue that contains the segments that have been transmitted but not yet acknowledged in sequence number order. If the data sender performs repacketization before retransmission, the block boundaries in a SACK option that it receives may not fall within the boundaries of segments in the retransmission queue.
TCP scheduler failed	Number of times that the TCP scheduler failed.
TCP receiver collapsed	Number of times that the data in an out-of-order queue collapsed.
TCP DSACK old packets sent	Number of duplicate selective acknowledgments (D-SACKs) sent by the Content Engine. The use of D-SACK does not require a separate negotiation between a TCP sender and receiver that have already negotiated SACK. The absence of a separate negotiation for D-SACK means that the TCP receiver could send D-SACK blocks when the TCP sender does not understand this extension to SACK. In this case, the TCP sender discards any D-SACK blocks and processes the other SACK blocks in the SACK option field as it normally would.
TCP DSACK out-of-order packets sent	Number of out-of-order D-SACK packets sent by the Content Engine. A D-SACK block is used only to report a duplicate contiguous sequence of data received by the receiver in the most recent packet. Each duplicate contiguous sequence of data received is reported in at most one D-SACK block. (The receiver sends two identical D-SACK blocks in subsequent packets only if the receiver receives two duplicate segments.) If the D-SACK block reports a duplicate contiguous sequence from a (possibly larger) block of data in the receiver's data queue above the cumulative acknowledgement, then the second SACK block in that SACK option should specify that (possibly larger) block of data.
TCP DSACK packets received	Number of D-SACK packets received by the Content Engine. TCP senders receiving D-SACK blocks should be aware that a segment reported as a duplicate segment could possibly have been from a prior cycle through the sequence number space. This awareness of the TCP senders is independent of the use of PAWS by the TCP data receiver.
TCP DSACK out-of-order packets received	Number of out-of-order D-SACK packets received by the Content Engine. Following a lost data packet, the receiver receives an out-of-order data segment, which triggers the SACK option as specified in RFC 2018. Because of several lost ACK packets, the sender then retransmits a data packet. The receiver receives the duplicate packet and reports it in the first D-SACK block.
TCP connections abort on sync	Number of times that a valid SYN segment was sent in the TCP window and the connection was reset.
TCP connections abort on data	Number of times that the connection closed after reading the data.
TCP connections abort on close	Number of times that the connection aborted with pending data.
TCP connections abort on memory	Number of times that memory was not available for graceful closing of the connection resulting in the connection being aborted immediately.
TCP connections abort on timeout	Number of times that the connection timed out.
TCP connections abort on linger	Number of times that the linger timeout expired resulting in the data being discarded and closing of the connection.
TCP connections abort failed	Number of times that the TCP connection ran out of memory, transmits failed, or peer RST could not be sent.
TCP memory pressures	Number of times that the TCP subsystem encounters memory constraints.

Related Commands

clear statistics tcp
show tcp
tcp

show statistics transaction-logs

To display Content Engine transaction log export statistics, use the show statistics transaction-logs EXEC command.

show statistics transaction-logs

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

To display the transaction logs export statistics, you must first configure the FTP server.

Examples

Table 2-152 describes the fields shown in the show statistics transaction-logs display.

Table 2-152 show statistics transaction-logs Field Descriptions 

Field	Description
Initial Attempts	Initial attempts made to contact the external server at the configured export intervals.
Initial Successes	Number of times that an initial attempt made to contact the external server succeeded.
Initial Open Failures	Number of times that the Content Engine failed to open a connection to the FTP export server.
Initial Put Failures	Number of times that the Content Engine failed to transfer a file to the FTP export server.
Retry Attempts	Number of retries made to contact the external server at the configured export intervals.
Retry Successes	Number of times that a retry made to contact the external server succeeded.
Retry Open Failures	Number of times that the Content Engine failed to open a connection to the FTP export server on a retry.
Retry Put Failures	Number of times that the Content Engine failed to transfer a file to the FTP export server on a retry.
Authentication Failures	Number of times that the Content Engine failed to authenticate with the FTP export server. This situation might occur if the Content Engine is misconfigured with the wrong password for the FTP server or the password on the FTP server has been changed since the Content Engine was configured.

Related Commands

clear statistics transaction-logs
show transaction-logging
transaction-logs

show statistics tvout

To display Content Engine TV-out statistics, use the show statistics tvout EXEC command.

show statistics tvout {all | bytes | files | usage}

Syntax Description

all	Displays all TV-out statistics.
bytes	Displays bytes-played statistics.
files	Displays files-played statistics.
usage	Displays current usage statistics.

Defaults

No default behavior or values

Command Modes

EXEC

Usage Guidelines

The show statistics tvout command displays the real-time playback status and history of the TV-out service through the local Content Engine.

Examples

Table 2-153 describes the fields shown in the show tvout bytes display.

Table 2-153 show statistics tvout bytes Field Descriptions 

Field	Description
TV-out Bytes
Bytes played (overall)	Total number of bytes played.
Bytes played (current playlist)	Number of bytes played from the current playlist.
Bytes played (current file)	Number of bytes played from the current file.

Table 2-154, Part 1 describes the fields shown in the show tvout files display for the Content Engine.

Table 2-154, Part 1 show statistics tvout files Field Descriptions 

Field	Description
TV-out Files
Files played (overall)	Total number of bytes played.
Files played (current playlist)	Number of bytes played from the current playlist.
Files skipped (overall)	Total number of files skipped.
Files skipped (current playlist)	Number of files skipped from the current playlist.

Related Commands

clear statistics tvout
show tvout
tvout