Cisco Internet Streamer CDS 3.2 Command Reference
Cisco Internet Streamer CDS Release 3.2 Software Commands, show statistics distribution through write
Downloads: This chapterpdf (PDF - 935.0KB) The complete bookPDF (PDF - 3.88MB) | Feedback

show statistics distribution

Table Of Contents

show statistics distribution

show statistics flash-media-streaming

show statistics icmp

show statistics ip

show statistics isis

show statistics movie-streamer

show statistics netstat

show statistics radius

show statistics replication

show statistics service-router

show statistics services

show statistics snmp

show statistics srp

show statistics tacacs

show statistics tcp

show statistics transaction-logs

show statistics udp

show statistics web-engine

show statistics wmt

show tacacs

show tech-support

show telnet

show transaction-logging

show url-signature

show user

show users

show version

show web-engine

show wmt

shutdown (interface configuration)

shutdown (EXEC)

snmp-server community

snmp-server contact

snmp-server enable traps

snmp-server group

snmp-server host

snmp-server location

snmp-server notify inform

snmp-server user

snmp-server view

splunk-uf-monitor

ss

sshd

streaming-interface

sysreport

tacacs

tcpdump

tcpmon

tcp timestamp

telnet

telnet enable

terminal

test-url

top

traceroute

traceroute srp

traceroute6

transaction-log force

transaction-logs

type

type-tail

undebug

url-signature

username

web-engine (EXEC)

web-engine (Global configuration)

whoami

wmt

write


show statistics distribution

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

show statistics distribution {all | errors {delivery-service-id delivery_service_id | delivery-service-name delivery_service_name} | mcast-data-receiver detail | mcast-data-sender [delivery-service-id delivery_service_id | delivery-service-name delivery_service_name | detail | feedback duration {days num detail | hours num detail | minutes num detail}] | metadata-receiver | metadata-sender | unicast-data-receiver [delivery-service-id delivery_service_id | delivery-service-name delivery_service_name | hot-forwarders [forwarder_id | forwarder_name] | 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.

delivery-service-id

Displays statistics about the specified delivery service ID.

delivery_service_id

Delivery service number.

delivery-service-name

Displays statistics about the specified delivery service name.

delivery_service_name

Delivery service name.

mcast-data-receiver

Distribution statistics for Multicast Data Receiver.

detail

(Optional) Detailed statistics.

mcast-data-sender

Distribution statistics for Multicast Data Sender.

feedback

(Optional) Distribution feedback statistics.

duration

(Optional) Feedback statistics for the particular duration.

days

Number of days. The range is from 1 to 365.

num

Days.

hours

Number of hours. The range is from 1 to 24.

num

Hours.

minutes

Number of minutes. The range is from 1 to 60.

num

Minutes.

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.

delivery-service-id

(Optional) Displays statistics about the specified delivery service ID.

delivery_service_id

(Optional) Delivery service number.

delivery-service-name

(Optional) Displays statistics about the specified delivery service name.

delivery_service_name

(Optional) Delivery service name.

hot-forwarders

(Optional) Displays the content distribution statistics of hot forwarders.

forwarder_id

(Optional) Identifier for the hot forwarder SE.

forwarder_name

(Optional) Name of the hot forwarder SE.

idle-forwarders

(Optional) Displays the content distribution statistics of idle forwarders.

max_idle_forwarders

(Optional) Maximum number of idle forwarder SEs to be displayed.

unicast-data-sender

(Optional) Displays the content distribution statistics of the unicast data sender.


Command Defaults

The idle-forwarders max_idle_forwarders default is 3.

Command Modes

EXEC configuration mode.

Usage Guidelines


Note This command is only available on Cisco Internet Streamer CDS Release 3.1.1.


The customer creates a multicast cloud and specifies which SEs are multicast senders, and which are multicast receivers within the cloud. Use the show statistics distribution mcast-data-sender or show statistics distribution mcast-data-receiver to view multicast statistics.

Table 0-1 describes the fields shown in the show statistics distribution unicast-data-receiver display.

Table 0-1 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 SE. 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 one 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.


Note

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

distribution

Reschedules and refreshes content redistribution for a specified delivery service ID or name

show distribution

Displays the distribution information for a specified delivery service.


This command is only available on Cisco Internet Streamer CDS Release 3.1.1.

Related Commands

show statistics flash-media-streaming

To display the statistics for Flash Media Streaming, use the show statistics flash-media-streaming command in EXEC configuration mode.

show statistics flash-media-streaming [connections | dvrcast | errors | flvcache | livestats | performance | proxy | rules | server | swf | vod]

Syntax Description

connections

(Optional) Displays Flash Media Streaming connections statistics.

dvrcast

(Optional) Displays Flash Media Streaming dvrcast application statistics.


Note The dvrcast keyword is only available on the 2.4.3 and earlier releases.


errors

(Optional) Displays Flash Media Streaming errors statistics.

flvcache

(Optional) Displays Flash Media Streaming FLV1 cache statistics.

livestats

(Optional) Displays Flash Media Streaming live application statistics.

performance

(Optional) Displays Flash Media Streaming performance statistics.

proxy

(Optional) Displays Flash Media Streaming proxy application statistics.

rules

(Optional) Displays Flash Media Streaming rules statistics.

server

(Optional) Displays Flash Media Streaming server level statistics.

swf

(Optional) Displays Flash Media Streaming SWF2 verification statistics.

vod

(Optional) Displays Flash Media Streaming vod application statistics.

1 Flash Video

2 Shockwave Flash


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

The show statistics flash-media-streaming rules command indicates how many requests rules were allowed, denied, if URL signing was performed, if URL signing failed with different error cases, and if the auth server accepted or rejected the request. Since the auth server rules framework performs all these actions, the values of the rules statistics are calculated by observing auth server replies and return codes.

Examples

The following example shows how to display the statistics for Flash Media Streaming:

ServiceEngine# show statistics flash-media-streaming 
Flash Media Streaming Statistics
Statistics have not been cleared since last Flash Media Streaming starts
 
   
Connections
-----------
Current Connections 
Total                :                    0
VOD                  :                    0
LIVE                 :                    0
DVRCast              :                    0
Proxy                :                    0
Max Concurrent       :                    0
Total Connections 
Total                :                    0
VOD                  :                    0
LIVE                 :                    0
DVRCast              :                    0
Proxy                :                    0
 
   
VOD Streaming
-----
Current Connections  :                    0
Total Connections    :                    0
DownStream Bytes     :                    0
UpStream Bytes       :                    0
DownStream BW        :                    0 Kbps
Preposition Hit      :                    0
External Hit         :                    0
Cache Hit            :                    0
Cache Miss           :                    0
Proxy Case           :                    0
Cache Hit Percentage :                 0.00
Local Disk Reads     :                    0
HTTP Based Reads     :                    0
Bytes From Local Disk:                    0
Bytes Through HTTP   :                    0
Ignore Query String  :                    0
Query String Bypassed:	0
 
   
Live Streaming
-----
Current Connections          :                    0
Total Connections            :                    0
UpStream BW                  :                    0 Kbps
DownStream BW                :                    0 Kbps
UpStream Bytes               :                    0
DownStream Bytes             :                    0
Downstream CDS-IS total conn.:                    0
Ignore Query String          :                    0
Query String Bypassed:	0
 
   
DVRCast Streaming
-----
Current Connections  :                    0
Total Connections    :                    0
UpStream BW          :                    0 Kbps
DownStream BW        :                    0 Kbps
UpStream Bytes       :                    0
DownStream Bytes     :                    0
Ignore Query String  :                    0
Query String Bypassed:	0
 
   
Proxy Streaming 
-----
Current Connections  :                    0
Total Connections    :                    0
UpStream BW          :                    0 Kbps
DownStream BW        :                    0 Kbps
UpStream Bytes       :                    0
DownStream Bytes     :                    0
 
   
Rules
-----------
Action Allow                :                    0
Action Block                :                    0
Validate url Sign           :                    0
URL Signing errors:
         Invalid Client     :                    0
         Invalid Signature  :                    0
         No signing         :                    0
         Expired URL        :                    0
Auth server validation:
         Auth Server Allow  :                    0
         Auth Server Deny   :                    0
 
   
SWF Verification :
 ---------------------
Requests 
         Performed             :                    0
         Failed                :                    0
         Successful            :                    0
         Bypassed              :                    0
         Memory Hash Hit       :                    0
         Memory Hash Calculated:                    0
         Local SWF Hit         :                    0
         Preposition SWF       :                    0
         SWF External Hit      :                    0
         SWF Cache Hit         :                    0
         SWF Cache Miss        :                    0
         SWF Proxy             :                    0
Errors
         SWF Fetch Error       :                    0
         Local SWF Read Error  :                    0
         Cached SWF Read Error :                    0
         SWF File not found    :                    0
         SWF Incorrect Depth   :                    0
         SWF Hash Match Fail   :                    0
         SWF Hash Partial      :                    0
         Edge SWF Cache Miss   :                    0
         SWF Response Timeout  :                    0
         SWF Client Unsupported:                    0
         SWF Wrong Version     :                    0
 
   
Error
-----
Disk Error 
         File Open Error            :                    0
         File Read Error            :                    0
         File GetAttributes Error   :                    0
         File Close Error           :                    0
 
   
 HTTP Error 
         Invalid Error              :                    0
         Server Error               :                    0
         Media Not Found            :                    0
         Media Unauthorize          :                    0
         Invalid Request            :                    0
         Bad Gateway                :                    0
         Service Unavailable        :                    0
         Gateway Timeout            :                    0
         Request Failed             :                    0
         Invalid Response           :                    0
         Too many Redirect          :                    0
         Invalid Redirect           :                    0
         Invalid Cache Type         :                    0
 
   
Server
-----------
Total UpStream BW      :                    0 Kbps
Total DownStream BW    :                    0 Kbps
Total UpStream Bytes   :                    0
Total DownStream Bytes :                    0
Total Server Bytes     :                    0
 
   
Performance
-----------
Server Up Time       :                    3 S
Mem Usage            :                    4 %
Max Mem Usage        :                    4 %
Total Messages Dropped:                    0 
 
   
Num of Active VOD Instances     :                    0
Num of Active Live Instances    :                    0
Num of Active DVRCast Instances :                    0
 
   
Flash Video Cache Statistics
-----------
Hits                 :                    0 
Misses               :                    0 
Released             :                    0 
Bytes in cache       :                    0 
Bytes in use         :                    0 
Disk Usage           :                 4096
ServiceEngine# 
 
   

Table 0-2 describes the fields shown in the show statistics flash-media-streaming display.

Table 0-2 show statistics flash-media-streaming Field Descriptions 

Field
Description

Connections

Current Connections

Total

Total number of current active connections to Flash Media Streaming.

VOD

Total number of current active connections to VOD applications to Flash Media Streaming.

Live

Total number of current active connections to Live applications to Flash Media Streaming.

DVRCast

Total number of current active connections to DVRCast applications to Flash Media Streaming.

Proxy

Total number of current active connections to non-VOD, Live or DVR applications to Flash Media Streaming.

Max Current

Max concurrent connections to Flash Media Streaming since it has started.

Total Connections

Total

Total number of connections to Flash Media Streaming since it has started.

VOD

Total number of connections to VOD applications to Flash Media Streaming since it has started.

LIVE

Total number of connections to Live applications to Flash Media Streaming since it has started.

DVRCast

Total number of connections to DVRCast applications to Flash Media Streaming since it has started.

Proxy

Total number of connections to non-VOD, Live or DVR applications to Flash Media Streaming since it has started.

VOD Streaming

Current Connections

Total number of current active connections to VOD applications to Flash Media Streaming.

Total Connections

Total number of connections to VOD applications to Flash Media Streaming since it has started.

DownStream Bytes

Total bytes transferred from server to client by VOD applications of Flash Media Streaming since it has started.

UpStream Bytes

Total bytes transferred from client to server by VOD applications of Flash Media Streaming since it has started.

DownStream BW

Current Bandwidth from server to client by VOD applications of Flash Media Streaming in Kbps.

Preposition Hit

Total requests for prepositioned content by VOD applications of Flash Media Streaming since it has started.

External Hit

Displays NAS Origin Hit count.

Cache Hit

Total requests for cache hit content by VOD applications of Flash Media Streaming since it has started.

Cache Miss

Total cache miss requests by VOD applications of Flash Media Streaming since it has started.

Proxy Case

Total requests for non cached and non prepositioned content by VOD applications of Flash Media Streaming since it has started.

Cache Hit Percentage

Percentage of cache hit requests to total requests.

Local Disk Reads

Number of read calls to local disk by VOD applications.

HTTP Based Reads

Number of read calls to HTTP sockets by VOD applications.

Bytes from Local Disk

Total bytes read through HTTP by VOD applications.

Bytes through HTTP

Total bytes read from local disk by VOD applications.

Live Streaming

Current Connections

Total number of current active connections to Live applications to Flash Media Streaming.

Total Connections

Total number of connections to Live applications to Flash Media Streaming since it has started.

UpStream BW

Current bandwidth from client to server by Live applications of Flash Media Streaming in Kbps.

DownStream BW

Current bandwidth from server to client by Live applications of Flash Media Streaming in Kbps.

UpStream Bytes

Total bytes transferred from client to server by Live applications of Flash Media Streaming since it has started.

DownStream Bytes

Total bytes transferred from server to client by Live applications of Flash Media Streaming since it has started.

Downstream CDS-IS Total Connections

Total live connections from CDS-IS devices that are on a lower level in a tree hierarchy.

DVRCast Streaming

Current Connections

Total number of current active connections to DVRCast applications to Flash Media Streaming.

Total Connections

Total number of connections to DVRCast applications to Flash Media Streaming since it has started.

UpStream BW

Current bandwidth from client to server by DVRCast applications of Flash Media Streaming in Kbps.

DownStream BW

Current bandwidth from server to client by DVRCast applications of Flash Media Streaming in Kbps.

UpStream Bytes

Total bytes transferred from client to server by DVRCast applications of Flash Media Streaming since it has started.

DownStream Bytes

Total bytes transferred from server to client by DVRCast applications of Flash Media Streaming since it has started.

Proxy Streaming

Current Connections

Total number of current active connections non-VOD, Live or DVR applications to Flash Media Streaming.

Total Connections

Total number of connections non-VOD, Live or DVR applications to Flash Media Streaming since it has started.

UpStream BW

Current bandwidth from client to server by non-VOD, Live or DVR applications of Flash Media Streaming in Kbps.

DownStream BW

Current bandwidth from server to client by non-VOD, Live or DVR applications of Flash Media Streaming in Kbps.

UpStream Bytes

Total bytes transferred from client to server by non-VOD, Live or DVR applications of Flash Media Streaming since it has started.

DownStream Bytes

Total bytes transferred from server to client by non-VOD, Live or DVR applications of Flash Media Streaming since it has started.

Rules

Action Allow

Total number of requests allowed by configured rules.

Action Block

Total number of requests blocked by configured rules.

Validate URL Sign

Total number of requests for which URL sign validation was performed.

URL Signing errors

Invalid Client

Total requests where URL signing failed as request was from an invalid client IP address.

Invalid Signature

Total requests where URL signing failed as request had an invalid signature.

No signing

Total requests where URL signing failed as request was sent without URL signature.

Expired URL

Total requests where URL signing failed as the signature had expired its lifetime.

Auth server validation

Auth Server Allow

Total number of requests allowed by the authorization server process.

Auth Server Deny

Total number of requests denied by the authorization server process.

SWF Verification

Requests

Performed

Total number of requests for which SWF verification was performed.

Failed

Total number of requests for which SWF verification failed.

Successful

Total number of requests for which SWF verification was successful.

Bypassed

Total number of requests for which SWF verification was not performed or bypassed.

Memory Hash Hit

Total number of requests for which SWF signature was already present in internal memory of Flash Media Streaming.

Memory Hash Calculated

Total number of requests for which SWF signature was newly calculated by Flash Media Streaming.

Local SWF Hit

Total number of requests where SWF file was present on /local1 partition of SE.

Preposition SWF

Total number of requests where SWF file was prepositioned on SE.

SWF External Hit

Total number of requests where SWF file was present on a NAS partition.

SWF Cache Hit

Total number of requests where SWF file was cached on local disk.

SWF Cache Miss

Total number of requests where SWF file was dynamically cached on local disk.

SWF Proxy

Total number of requests where SWF file was not prepositioned or cached on disk.

Errors

SWF Fetch Error

SWF Fetch Error: Error in fetching SWF file from web engine.

Local SWF Read Error

Error reading SWF file from /local1 partition.

Cached SWF Read Error

Error reading cached SWF file.

SWF File not found

SWF file not found on disk.

SWF Incorrect Depth

SWF File could not hash to the requested depth.

SWF Match Fail

Hash produced does not match the client's hash.

SWF Hash Partial

Partial file SWF Hash Match.

Edge SWF Cache Miss

Edge SWF Hash Cache missed.

SWF Response Timeout

SWF Hash Response Timeout.

SWF Client Unsupported

Client cannot support SWF Hashing.

SWF Wrong Version

Hash is the wrong SWF Verification version.

Error

Disk Error

File Open Error

Total errors when trying to open a file by Flash Media Streaming.

File Read Error

Total errors when trying to read a file by Flash Media Streaming.

File GetAttributes Error

Total errors when trying to get file attributes by Flash Media Streaming.

File Close Error

Total errors when trying to close a file by Flash Media Streaming.

HTTP Error

Invalid Error

Invalid HTTP error code received by Flash Media Streaming.

Server Error

HTTP error code 500 received by Flash Media Streaming.

Media Not Found

HTTP error code 404 received by Flash Media Streaming.

Media Unauthorize

Unauthorized access, HTTP error code 401-407, except 404, received by Flash Media Streaming.

Invalid Request

HTTP error code 400 received by Flash Media Streaming.

Bad Gateway

HTTP error code 502 received by Flash Media Streaming.

Service Unavailable

HTTP error code 503 received by Flash Media Streaming.

Gateway Timeout

HTTP error code 504 received by Flash Media Streaming.

Request Failed

Null reply received by Flash Media Streaming.

Invalid Response

HTTP error code 0 received by Flash Media Streaming.

Too many Redirect

More than allowed number of HTTP redirects received by Flash Media Streaming.

Invalid Redirect

Invalid redirect URL received by Flash Media Streaming.

Invalid Cache Type

Invalid cache type received from web engine by Flash Media Streaming.

Server

Total UpStream BW

Total instantaneous BW from client to server for Flash Media Streaming.

Total DownStream BW

Total instantaneous BW from server to client for Flash Media Streaming.

Total UpStream Bytes

Total bytes transferred from client to server for Flash Media Streaming.

Total DownStream Bytes

Total bytes transferred from server to client for Flash Media Streaming.

Total Server Bytes

Total bytes served by Flash Media Streaming.

Performance

Server Up Time

Time since the Flash Media Streaming has been running.

Mem Usage

Current memory usage of Flash Media Streaming.

Max Mem Usage

Maximum memory usage of Flash Media Streaming.

Total Messages Dropped

Total messages dropped by Flash Media Streaming.

Num of Active VOD Instances

Total active VOD instances.

Num of Active Live Instances

Total active Live instances.

Num of Active DVRCast Instances

Total active DVRCast instances.

Flash Video Cache Statistics

Hits

Total hits on Flash video cache.

Misses

Total misses on Flash video cache.

Released

Total number of segments released by Flash video cache since Flash Media Streaming has started.

Bytes in cache

Current number of bytes in cache.

Bytes in use

Current number of bytes in cache being used.

Disk Usage

Size of flash video cache on disk.


Related Commands

Command
Description

flash-media-streaming

Enables and configures Flash Media Streaming.

show flash-media-streaming

Displays the Flash Media Streaming information.


show statistics icmp

To display SE Internet Control Message Protocol (ICMP) statistics, use the show statistics icmp command in EXEC configuration mode.

show statistics icmp

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

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 is delivered or a control message is 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 on 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 show a value of 0 in the code field. ICMP uses the queries as shown in Table 0-3.

Table 0-3 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 0-4.

Table 0-4 Errors

Error
Type Field Value

Destination Unreachable

3

Source Quench

4

Redirect

5

Time Exceeded

11

Parameter Problems

12


Table 0-5 describes the fields shown in the show statistics icmp display.

Table 0-5 show statistics icmp Field Descriptions  

Field
Description

ICMP messages received

Total number of ICMP messages received by the SE.

ICMP messages receive failed

Total number of ICMP messages that were not received by the SE.

Destination unreachable

Number of destination-unreachable ICMP packets received by the SE. 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 reason 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 SE. 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 SE. 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 SE. A receiving host generates a source-quench message when it cannot process datagrams at the speed requested because of 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 SE. 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 SE. 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 SE. 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 SE. 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 SE. 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 request packets received by the SE. 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 reply packets received by the SE. 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 SE.

ICMP messages send failed

Total number of ICMP messages that failed to be sent by the SE.

Destination unreachable

Number of destination-unreachable ICMP packets sent by the SE.

Timeout in transit

Number of ICMP time-exceeded packets sent by the SE.

Wrong parameters

Number of ICMP packets with parameter problems sent by the SE.

Source quenches

Number of ICMP source-quench packets sent by the SE.

Redirects

Number of ICMP redirect packets sent by the SE.

Echo requests

Number of echo ICMP packets sent by the SE.

Echo replies

Number of echo-reply ICMP packets sent by the SE.

Timestamp requests

Number of ICMP time stamp request packets sent by the SE.

Timestamp replies

Number of ICMP time stamp reply packets sent by the SE.

Address mask requests

Number of ICMP address mask requests sent by the SE.

Address mask replies

Number of ICMP address mask replies sent by the SE.


Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.


show statistics ip

To display the IP statistics, use the show statistics ip command in user EXEC configuration mode.

On the SE and CDSM:

show statistics ip

On the SR:

show statistics ip {ospf | proximity {rib | server}}

Syntax Description

ospf

Displays the different OSPF counters.

proximity

Displays the proximity statistics.

rib

Displays the RIB proximity statistics.

server

Displays the proximity server statistics.


Command Defaults

None

Command Modes

User EXEC configuration mode.

Usage Guidelines

The show statistics ip OSPF command is used to display OSPF counters.

The show statistics ip proximity command is used to display proximity statistics that are tracked in the RIB.

Examples

The following is sample output from the show statistics ip ospf command:

ServiceRouter# show statistics ip ospf
 
   
Generic counters:
 OSPF Process ID p1, Event statistics (cleared 06:57:01 ago)
  Router ID changes: 0
  DR elections: 0
  Older LSAs received: 0
  Neighbor state changes: 0
  Neighbor dead postponed: 0
  Neighbor dead interval expirations: 0
  Neighbor bad lsreqs: 0
  Neighbor sequence number mismatches: 0
  SPF computations:  2926 full, 0 summary, 0 external
 
   
         LSA Type Generated Refreshed   Flushed  Aged out
           Router         0        14         0         2
          Network         0         0         0         0
      Summary Net         0         0         0         0
     Summary ASBR         0         0         0         0
      AS External         0         0         0         0
      Opaque Link         0         0         0         0
      Opaque Area         0         0         0         0
        Opaque AS         0         0         0         0
 
   
  Following counters can not be reset:
 
   
  LSA deletions: 0 pending, 2 hwm, 531 deleted, 0 revived, 12 runs
  Hello queue: 0/200, hwm 2, drops 0
  Flood queue: 0/100, hwm 8, drops 0
  LSDB additions failed: 0
 
   
         Buffers:    in use       hwm permanent     alloc      free
       128 bytes          0         4         4     19430     19430
       512 bytes          0         4         4     37061     37061
      1520 bytes          0         3         2      1205      1205
      4500 bytes          0         2         1     20535     20535
            huge          0         0         0         0         0
 
   
ServiceRouter# 
 
   

The following is sample output from the show statistics ip proximity command.

ServiceRouter> show statistics ip proximity 
 
   
Total number of proximity requests received from applications: 9736
Total number of proximity replies sent to applications:        9736
 
   
Proximity msg exchanges between urib and other routing protocols:
                               Sent_Prox_Req     Received_Prox_Resp
isis                                  0                  0
 
   
ospf                               6677               6677
 
   
Local proximity requests from applications: 3055
 
   
Invalid proximity requests from applications: 0
 
   
PSA/PTL non-rankable proximity requests from applications: 4
Failed proximity requests to routing protocols: 0
Failed PSA lookups: 4
Failed PTL lookups: 52493
 
   
ServiceRouter>
 
   

Table 0-6 describes the fields shown in the show statistics ip display.

Table 0-6 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 because of 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 SE attempted to find a route to forward them to that final destination. In entities that do not act as IP routers, this counter includes 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 SE found no route to send 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 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 because of fragmentation at this entity.


Related Commands

Command
Description

clear statistics ip

Clears IP statistics counters.

ip

Configures the IP.

show ip routes

Displays the IP routing table.


show statistics isis

To display IS-IS traffic counters, use the show statistics isis command in user EXEC configuration mode.

show statistics isis [GigabitEthernet slot/port_num | PortChannel num]

Syntax Description

GigabitEthernet

(Optional) Selects a Gigabit Ethernet interface.

slot/port_num

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

PortChannel

(Optional) Selects the Ethernet Channel of interfaces.

num

Ethernet Channel interface number. The range is from 1 to 4.


Defaults

Not specifying an interface name displays IS-IS traffic statistics for all the IS-IS instances.
IS-IS traffic statistics are displayed for all interfaces.

Command Modes

User EXEC configuration mode.

Usage Guidelines

The show statistics isis command displays IS-IS traffic counters for the specified interface or all traffic counters if no interface is specified.

Examples

The following is sample output from the show statistics isis command that shows all traffic counters for all IS-IS instances:

ServiceRouter# show statistics isis
 
   
IS-IS statistics:
PDU        Received        Sent  RcvAuthErr OtherRcvErr
LAN-IIH       60182       15965           0           0
P2P-IIH           0           0           0           0
CSNP          73498           0           0           0
PSNP              0          28           0           0
 
   
PDU        Received     Flooded  RcvAuthErr OtherRcvErr  ReTransmit
LSP          117526        2922           0           0           0
 
   
DIS elections:    24        
SPF calculations: 55836     
LSPs sourced:     3         
LSPs refreshed:   273       
LSPs purged:      3183      
 
   
ServiceRouter# 
 
   

The following is sample output from the show statistics isis command that shows all traffic counters for a specific interface:

ServiceRouter# show statistics isis GigabitEthernet 1/0
 
   
IS-IS statistics for GigabitEthernet 1/0:
PDU        Received        Sent  RcvAuthErr OtherRcvErr
LAN-IIH           0           0           0           0
P2P-IIH           0           0           0           0
CSNP              0           0           0           0
PSNP              0           0           0           0
 
   
PDU        Received     Flooded  RcvAuthErr OtherRcvErr  ReTransmit
LSP               0           0           0           0           0
 
   
DIS elections:    2         
 
   
ServiceRouter# 
 
   

show statistics movie-streamer

To display statistics for the Movie Streamer, use the show statistics movie-streamer command in EXEC configuration mode.

show statistics movie-streamer {all | bw-usage | error | performance | requests | rule}

Syntax Description

all

Displays all statistics.

bw-usage

Displays bandwidth usage statistics.

error

Displays error statistics.

performance

Displays server performance.

requests

Displays request statistics.

rule

Displays rule statistics.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

Execution Order of Rule Actions

The order in which the rule actions are implemented for Windows Media Streaming and Movie Streamer is the order in which they were configured, except for the validate-url-signature action. If the rule pattern associated with the validate-url-signature action is matched, regardless of the configuration order of the rules, the validate-url-signature action is performed before any other action.

1. validate-url-signature

2. block or allow


Note NOTE: The allow and block actions carry the same precedence. The order of implementation depends on the order of configuration between allow and block actions. Other actions always take precedence over allow.


3. redirect (before cache lookup)

4. rewrite (before cache lookup)


Note Windows Media Streaming supports all rule actions. Movie Streamer supports the following rule actions: allow, block, redirect, rewrite, and validate-url-signature.

For the Web Engine and Flash Media Streaming, the Service Rule file must be used if service rules are to be configured. See the Cisco Internet Streamer CDS 3.2 Software Configuration Guide.


Examples

The following example shows all the Movie Streamer statistics:

ServiceEngine# show statistics movie-streamer all
 
   
Movie Streamer Request Statistics
Total
---------------------------------------------------
Current RTSP Sessions: 3400
Total RTSP Sessions: 283299
Current RTP Connections: 2739
Total RTP Connections: 282885
 
   
CDN Related Statistics
--------
Preposition Hits: 0
Cache Hits: 0
Cache Miss: 0
Live Requests: 283299
 
   
Cache Revalidation Statistics
--------
Fresh Content Requests: 0
Revalidated Requests: 0
 
   
Movie Streamer Bandwidth Usage Statistics
Total
---------------------------------------------------
Current Incoming Bandwidth: 0 bps
Current Outgoing Bandwidth: 3921755 bps
Current Total Bandwidth: 3921755 bps
 
   
Average Incoming Bandwidth: 475217 bps
Average Outgoing Bandwidth: 13038460 bps
Average Total Bandwidth: 13513677 bps
 
   
 
   
By Type of Connection
--------
Unicast Incoming Bandwidth: 0 bps
Multicast Incoming Bandwidth: 0 bps
Unicast Outgoing Bandwidth: 3816953 bps
Multicast Outgoing Bandwidth: 0 bps
 
   
By Type of Content
--------
Live Incoming Bandwidth: 0 bps
VOD Incoming Bandwidth: 0 bps
Live Outgoing Bandwidth: 3816953 bps
VOD Outgoing Bandwidth: 0 bps
 
   
Overall Traffic
--------
Incoming Bytes: 709316834819 Bytes
Outgoing Bytes: 62627648126402 Bytes
Total Bytes: 63336964961221 Bytes
 
   
Incoming Packets: 652577871
Outgoing Packets: 191008363529
Total Packets: 191660941400
 
   
Movie Streamer Error Statistics
Total 
Server Error
--------
Internal Error: 0
Not Implemented: 0
Server Unavailable: 0
Gateway Timeout: 0
Others: 0
 
   
Client Error
--------
Bad Request: 0
File Not Found: 6
Session Not Found: 0
Method Not Allowed: 0
Not Enough Bandwidth: 0
Client Forbidden: 0
Others: 0
 
   
Movie Streamer Performance Statistics
Total
---------------------------------------------------
CPU Usage: 0.166702 %
Uptime: 254328 sec
Statistics was last cleared on Monday, 18-May-2009 20:04:42 UTC. 
 
   

The following example shows the Movie Streamer rule statistics:

ServiceEngine# show statistics movie-streamer rule
RTSP Rule Template Statistics
================
URL Rewrite: 0
URL Block: 0
Allow: 0
Redirect: 0
Validate URL Signature:         0

Related Commands

Command
Description

movie-streamer

Enables and configures the Movie Streamer server.

show movie-streamer

Displays the Movie Streamer configuration.


show statistics netstat

To display SE Internet socket connection statistics, use the show statistics netstat command in EXEC configuration mode.

show statistics netstat

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

Table 0-7 describes the fields shown in the show statistics netstat display.

Table 0-7 show statistics netstat Field Descriptions 

Field
Description

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 protocol stack in the send direction on a connection.

Local Address

IP address and Layer 4 port used at the device 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 radius

To display SE RADIUS authentication statistics, use the show statistics radius command in EXEC configuration mode.

show statistics radius

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

The fields in the show statistics radius display are as follows:

Number of access requests

Number of access deny responses

Number of access allow responses

Number of authorization requests

Number of authorization failure responses

Number of authorization success responses

Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

radius-server

Configures the RADIUS authentication.

show radius-server

Displays the RADIUS server information.


show statistics replication

To display delivery service replication status and related statistical data, use the following show statistics replication command in EXEC configuration mode.

On the CDSM:

show statistics replication {content-items content_name selected-delivery-service content_origin_name delivery_service_name {all-service-engines [refetch] | service-engine service_engine_name [fully-replicated | not-fully-replicated | refetch} | delivery-service [selected-delivery-service content_origin_name delivery_service_name| item url selected-delivery-service content_origin_name delivery_service_name | service-engines selected-delivery-service content_origin_name delivery_service_name [refetch | service-engine service_engine_name]}

On the SE:

show statistics replication {content-items content_name selected-delivery-service content_origin_name delivery_service_name [fully-replicated | not-fully-replicated] | delivery-service [selected-delivery-service content_origin_name delivery_service_name}

Syntax Description

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.

selected-delivery-service

Selects a delivery service.

content_origin_name

Content origin name.

delivery_service_name

Delivery service name.

all-service-engines

For all service engines in a delivery service.

refetch

Initiates a request to re-fetch the status.

fully-replicated

Content items that are fully replicated.

not-fully-replicated

Content items that are not fully replicated.

delivery-service

Displays replication status of the delivery service.

item

Displays the detailed replication status of a content item across all SEs in a delivery service.

url

URL of the content item.

service-engines

Displays the replication status of the specified SEs.

service-engine

Displays the replication status of the specified service engine.

service_engine_name

Service engine name.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

The show statistics replication delivery-service command displays the delivery service replication status on the CDSM and the SE.

Table 0-8 describes the fields shown in the show statistics replication delivery-service display.

Table 0-8 show statistics replication delivery-service Field Descriptions 

Field
Description

Delivery Service

Delivery service name.

State

Overall state of the delivery service. Values are Complete or Failed.

Status

Replication status. Values are Red for failure and Green for success.

User Selected Content Acquirer

Name of the Content Acquirer that has been selected for delivery service.

Current Content Acquirer

Name of the currently acting Content Acquirer for the delivery service.

Receiver SEs Completed

Total number of SEs that have completed content replication for the delivery service.

Receiver SEs In Progress

Total number of SEs for which content replication is in progress for the delivery service.

Receiver SEs Failed

Total number of SEs that have some error condition and are treated as failed.

Receiver SEs Not Responding

Total number of SEs not responding to the replication status queries from the CDSM.

Device

Name and ID of the device.

Content Origin

Origin of content.

Type

Role of the device, such as Root or Receiver.

State

State of the SE replication. For receiver SEs, states are Failed, Replicating, or Completed. For the Content Acquirer, states are Acquiring Content, Rechecking Content, or Completed.

Completed

Number of content items completed.

To Do

Number of content items pending for the delivery service.

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 delivery service.

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.


The show statistics replication content-items command displays the progressive file count status during acquisition and replication.

Table 0-9 describes the fields shown in the show statistics replication content-items display.

Table 0-9 show statistics replication content-items Field Descriptions 

Field
Description

Content URL

URL of the replicated content.

Status

Indicates if the content was complete.

Size

Size of the file.

Modification Time

Displays the UTC time the content was replicated.


Examples

The following example shows how to display the statistics for the replication delivery service on a CDSM:

CDSM# show statistics replication delivery-service selected-delivery-service XXXX-iptv 
XXXX-ds1
Delivery Service: XXXX-ds1
State: Completed
Status: Green
User Selected Content Acquirer: XX-nas-se01
Current Content Acquirer: XX-nas-se01
Receiver SEs Completed: 0
Receiver SEs In Progress: 0
Receiver SEs Failed: 0
Receiver SEs Not Responding: 0
 
   
Displaying Device Acquisition Replication Status
Device: XX-nas-se01 (SE ID: 111)
Delivery Service: XXXX-ds1 (Delivery Service ID: 222)
Content Origin: XXXX-iptv
Type: Acquirer
State: Completed
Status: Green
Completed: 579
To Do: 0
Failed: 0
Total: 579
Last Report Time: Tue Aug 30 20:05:03 GMT 2011
Disk Quota Used: 270.715 GB
Manifest Last Modified: Tue Aug 30 19:33:32 GMT 2011
Manifest Last Check: Tue Aug 30 20:04:47 GMT 2011
Manifest State: Completed
 
   

The following example shows how to display the statistics for the replication delivery service on an SE:

ServiceEngine# show statistics replication delivery-service selected-delivery-service 
XXXX-iptv XXXX-ds1
Displaying Device Acquisition Replication Status
Device: XX-nas-se01 (SE ID: 111)
Delivery Service: XXXX-ds1 (Delivery Service ID: 222)
Content Origin: XXXX-iptv
Type: Acquirer
State: Completed
Status: Green
Completed: 579
To Do: 0
Failed: 0
Total: 579
Last Report Time: Tue Aug 30 20:13:24 GMT 2011
Disk Quota Used: 270.715 GB
Manifest Last Modified: Tue Aug 30 19:33:32 GMT 2011
Manifest Last Check: Tue Aug 30 20:12:57 GMT 2011
Manifest State: Completed
 
   

The following example shows how to display the statistics for replication content items on an SE:

ServiceEngine# show statistics replication content-items * selected-delivery-service 
jerry-iptv dtnas-ds1
Gathering replication status may take some time.... (enter ctrl-c to stop)
 
   
There are 579 content items for Delivery Service: 'XXXX-ds1', Content Origin: 'XXXX-iptv' 
(Delivery Service ID 111) that match the request.
 
   
Content URL: http://14.6.0.2/isilon_prepos/largefile/nastest_4
Status: Complete
Size: 478.318 MB
Modification Time: 00:44:04 03-25-2011
 
   
 
   
Content URL: http://14.6.0.2/isilon_prepos/largefile/nastest_70
Status: Complete
Size: 478.318 MB
Modification Time: 00:47:15 03-25-2011
 
   
 
   
Content URL: http://14.6.0.2/isilon_prepos/largefile/nastest_583
Status: Complete
Size: 478.318 MB
Modification Time: 00:56:19 03-25-2011
 
   
 
   
Content URL: http://14.6.0.2/isilon_prepos/largefile/nastest_464
Status: Complete
Size: 478.318 MB
Modification Time: 01:04:21 03-25-2011
 
   
<Output truncated>

show statistics service-router

To display Service Router statistics, use the show statistics service-router command in EXEC configuration mode.

show statistics service-router {all | content-origin content_name | dns | history | keepalive | routing {geo-location | proximity} | se se_name | summary}

Syntax Description

all

Displays all statistics.

content-origin

Displays content origin specific statistics.

content_name

Content origin name to show.

dns

Displays DNS statistics.

history

Displays statistics history.

keepalive

Displays keepalive statistics.

routing

Displays routing statistics.

geo-location

Displays routing geo location-related statistics.

proximity

Displays routing proximity-related statistics.

se

Displays Service Engine specific statistics.

se_name

Service Engine name to show.

summary

Displays summary statistics.


Command Defaults

None

Command Modes

EXEC configuration mode.

Examples

The following example shows how to display the content origin-specific statistics on the number of requests and redirects:

ServiceRouter# show statistics service-router content-origin 
 
   
----- SR Statistics Of Content Origin -----
domain: sr.ABC.com (Origin Server: ABC.com)
HTTP Requests (normal) :                     0
HTTP Requests (ASX)    :                     0
HTTP Requests (API)    :                     0
RTSP Requests          :                     0
RTMP Requests          :                     0
HTTP 302 Redirects     :                     0
ASX Redirects          :                     0
HTTP API Redirects     :                     0
RTSP Redirects         :                     0
RTMP Redirects         :                     0
Overflow Redirects     :                     0
 
   
----- SR Statistics Of Content Origin -----
domain: cdsfms.com (Origin Server: 171.71.50.185, Alternate Domain: 171.71.50.18
5)
HTTP Requests (normal) :                     0
HTTP Requests (ASX)    :                     0
HTTP Requests (API)    :                     0
RTSP Requests          :                     0
RTMP Requests          :                     0
HTTP 302 Redirects     :                     0
ASX Redirects          :                     0
HTTP API Redirects     :                     0
RTSP Redirects         :                     0
RTMP Redirects         :                     0
Overflow Redirects     :                     0
 
   
----- SR Statistics Of Content Origin -----
domain: chunliu.com (Origin Server: 72.163.255.111)
HTTP Requests (normal) :                     0
HTTP Requests (ASX)    :                     0
HTTP Requests (API)    :                     0
RTSP Requests          :                     0
RTMP Requests          :                     0
HTTP 302 Redirects     :                     0
ASX Redirects          :                     0
HTTP API Redirects     :                     0
RTSP Redirects         :                     0
RTMP Redirects         :                     0
Overflow Redirects     :                     0
 
   
----- SR Statistics Of Content Origin -----
domain: install3.com (Origin Server: 10.74.115.24)
HTTP Requests (normal) :                     0
HTTP Requests (ASX)    :                     0
HTTP Requests (API)    :                     0
RTSP Requests          :                     0
RTMP Requests          :                     0
HTTP 302 Redirects     :                     0
ASX Redirects          :                     0
HTTP API Redirects     :                     0
RTSP Redirects         :                     0
RTMP Redirects         :                     0
Overflow Redirects     :                     0
V2-CDE220-2#
 
   

The following example shows how to display the DNS statistics, including the number of DNS queries for each type (Content Origin FQDN, Service Engine aliases), and the response sent (aliases for down Service Engines, unknown domains, failed, dropped).

:

ServiceRouter# show statistics service-router dns 
 
   
----- SR DNS Statistics -----
Total DNS queries             :                  0
    Content Origin FQDNs      :                  0
    Service Engine aliases    :                  0
    Aliases for Down SEs      :                  0
    Unknown domains           :                  0
    PTR queries               :                  0
    Failed                    :                  0
    Dropped                   :                  0
 
   
ServiceRouter#
 
   

The following example shows how to display the statistics history on the number of redirect requests (maximum, minimum, average, last [in the past hour or minute]):

ServiceRouter# show statistics service-router history 
 
   
----- SR Statistics History -----
Type         Minimum   Maximum   Average      Last (in past hour/per minute)
---------- --------- --------- --------- --------- 
REQUESTS           0         0         0         0
REDIRECTS          0         0         0         0
 
   

The following example shows how to display keepalive statistics on the number of keepalives received from Service Engines, unknown source, and number of keepalives dropped:

ServiceRouter# show statistics service-router keepalive
 
   
----- SR Keepalive Statistics -----
    Dropped                   :                  0
    Service Engine keepalives :                  0
    From unknown source       :                  0
 
   
ServiceRouter#
 
   

The following example shows how to display statistics to show which routing method is used in redirection to SEs:

ServiceRouter# show statistics service-router routing
 
   
----- SR Routing Statistics -----
    Network Redirects         :                  0
    Proximity Redirects       :                  0
    Geo Location Redirects    :                  4
    Zero Network Redirects    :                  0
    Last Resort Redirects     :                  1
 
   
ServiceRouter#
 
   

The following example shows how to display geo location-related statistics showing the number of cache hits, cache misses and errors.

 
   
ServiceRouter# show statistics service-router routing geo-location
 
   
----- SR Geo Location Routing Statistics -----
    Cache Hits                :                  3
    Cache Misses              :                  2
    Errors                    :                  1
 
   
ServiceRouter#
 
   

The following example shows how to display proximity-related statistics showing the number of cache hits, cache misses and errors.

 
   
ServiceRouter# show statistics service-router routing proximity
 
   
----- SR Proximity Routing Statistics -----
    Cache Hits                :                  2
    Cache Misses              :                  3
    Errors                    :                  2
 
   
ServiceRouter#
 
   

The following example shows how to display Service Engine statistics including liveness of the SE, number of redirects to that particular SE, and the total number of keepalives received from that SE.

ServiceRouter# show statistics service-router se             
 
   
----- Statistics Of SE: V2-CDE220-1 -----
Aliveness               : down
HTTP 302 Redirects      :                  0
ASX Redirects           :                  0
HTTP API Redirects      :                  0
RTSP Redirects          :                  0
RTMP Redirects          :                  0
DNS Redirects           :                  0
Number Of Keepalives    :                  0
 
   
----- Statistics Of SE: V2-CDE220-3 -----
Aliveness               : down
HTTP 302 Redirects      :                  0
ASX Redirects           :                  0
HTTP API Redirects      :                  0
RTSP Redirects          :                  0
RTMP Redirects          :                  0
DNS Redirects           :                  0
Number Of Keepalives    :                  0
V2-CDE220-2#
 
   

The following example shows how to display summary statistics including the number of requests received, requests redirected, requests served, and requests not redirected:

ServiceRouter# show statistics service-router summary
 
   
----- SR Summary Statistics -----
Requests Received          :                  1
  HTTP Requests (normal)   :                  0
  HTTP Requests (ASX)      :                  0
  HTTP Requests (API)      :                  0
  RTSP Requests            :                  1
  RTMP Requests            :                  0
  DNS Requests             :                  0
 
   
Requests Served            :                  0
  HTTP Requests Served     :                  0
 
   
Requests Redirected        :                  1
  HTTP 302 Redirects       :                  0
  ASX Redirects            :                  0
  HTTP API Redirects       :                  0
  RTSP redirects           :                  1
  RTMP redirects           :                  0
  DNS redirects            :                  0
 
   
Requests Overflowed        :                  0
  HTTP 302 Redirects       :                  0
  ASX Redirects            :                  0
  HTTP API Redirects       :                  0
  RTSP redirects           :                  0
  RTMP redirects           :                  0
  DNS redirects            :                  0
 
   
Requests Not Redirected    :                  0
  No SE Covering Client    :                  0
  Unknown Content Origin   :                  0
  Invalid Requests         :                  0
  Session limit exceeded   :                  0
  Bandwidth limit exceeded :                  0
 
   
  "Stale SE" Requests      :                  0

Related Commands

Command
Description

service-router

Configures service routing.

show service-router

Displays the Service Router configuration.


show statistics services

To display SE services statistics, use the show statistics services command in EXEC configuration mode.

show statistics services

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

Table 0-10 describes the fields shown in the show statistics services display.

Table 0-10 show statistics services Field Descriptions

Field
Description

Port Statistics

Service-related statistics for each port on the WAAS1 device.

Port

Port number.

Total Connections

Number of total connections.

1 WAAS = Wide Area Application Service


Related Commands

Command
Description

show services

Displays the services-related information.


show statistics snmp

To display SE Simple Network Management Protocol (SNMP) statistics, use the show statistics snmp command in EXEC configuration mode.

show statistics snmp

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

Table 0-11 describes the fields shown in the show statistics snmp display.

Table 0-11 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

Command
Description

show snmp

Displays the SNMP parameters.

snmp-server community

Configures the community access string to permit access to the SNMP.

snmp-server contact

Sets the system server contact string.

snmp-server enable

Enables the SE to send SNMP traps.

snmp-server group

Defines a user security model group.

snmp-server host

Specifies the hosts to receive SNMP traps.

snmp-server location

Sets the SNMP system location string.

snmp-server notify inform

Configures the SNMP notify inform request.

snmp-server user

Defines a user who can access the SNMP engine.


show statistics srp

To display SRP statistics information, use the show statistics srp command in Privileged EXEC configuration mode.

show statistics srp

Syntax Description

This command has no arguments or keywords.

Defaults

None

Command Modes

Privileged EXEC configuration mode.

Usage Guidelines

This command displays SRP statistics information.

Examples

The following example shows sample output from the show statistics srp command.

ServiceRouter# show statistics srp
			Sent     Received    Neighbors
Join request                    504          493            0
Join response                   493          492            0
LS exchange request            7447         7317            0
LS exchange response           7317         7447            0
Route exchange request         3469         3743            8
Route exchange response        3742         3469            9
Ping request                  39570        39405            1
Ping response                 39405        39530            0
Lookup request                 4610         2920            0
Lookup response                2920         4582            0
Ping traceroute request           0            0            0
Ping traceroute response          0            0            0
Request Retry                     0
Pkt at wrong interface            0
Malform packet                    0
Mismatched domain ID              1
 
   
ServiceRouter# 
 
   

In the show statistics srp output, the "Pkt at wrong interface" statistic for received packets indicates that packets have arrived at an interface that is not configured as a network-facing interface. For Pkt at wrong interface, the Sent and Neighbors values are always 0.

Related Commands

Command
Description

show srp leafset

Displays SRP leafset information.

show srp neighbor

Displays SRP neighbor information.

show srp route

Displays route information for a Proximity Engine to its neighbor nodes on the same DHT ring.


show statistics tacacs

To display Service Engine TACACS+ authentication and authorization statistics, use the show statistics tacacs command in user EXEC configuration mode.

show statistics tacacs

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

User EXEC configuration mode.

Usage Guidelines

The fields shown in the show statistics tacacs display for the service engine are as follows:

Number of access requests

Number of access deny responses

Number of access allow responses

Number of authorization requests

Number of authorization failure responses

Number of authorization success responses

Number of accounting requests

Number of accounting failure responses

Number of accounting success responses

Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

show tacacs

Displays TACACS+ authentication protocol configuration information.

tacacs

Configures TACACS+ server parameters.


show statistics tcp

To display SE Transmission Control Protocol (TCP) statistics, use the show statistics tcp command in EXEC configuration mode.

show statistics tcp

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

Table 0-12 describes the fields shown in the show statistics tcp display.

Table 0-12 show statistics tcp Field Descriptions 

Field
Description

Server connection openings

Number of connections opened from the SE to the server.

Client connection openings

Number of connections opened from the client to the SE.

Failed connection attempts

Number of incoming SYN connections rejected because of rate limiting or resource shortage.

Connections established

Number of incoming connections that have been set up.

Connections resets received

Number of RSTs1 received by the SE.

Connection resets sent

Number of RSTs sent by the SE.

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 because of 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 SE from the server.

Server segments sent

Number of TCP segments sent by the SE to the server.

Server segments retransmitted

Number of TCP segments retransmitted by the SE from the server.

Client segments received

Number of TCP segments received by the SE from the client.

Client segments sent

Number of TCP segments sent by the SE to the server.

Client segments retransmitted

Number of TCP segments retransmitted by the SE to the client.

Sync cookies sent

Number of SYN2 cookies sent by the SE. 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 SYN cookies received by the SE. 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 has 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 SYN cookies rejected by the SE. The SYN cookies 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 SE accepted the connection.

Prune message called

Number of calls that the SE 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 because of 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 ARPs3 not sent because they were meant for the SE.

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 as 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 PAWS4 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 SE.

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 because of 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 packets delivered 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 packets delivered to the client from the prequeue.

TCP prequeue dropped packets

Number of TCP packets dropped from the prequeue. The prequeue is where the TCP receives 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 ACK5 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 SE recovered from a 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 SE 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 SACK 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 FACK6 packets 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 SACK7 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 D-SACK8 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 because of 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 cwnd9 shrunk because the SE failed to recover from a 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 is only one or two duplicate ACKs before the reordered segment is processed, which then generates 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:

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.

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 SE 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 sent 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 D-SACKs sent by the SE. 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 SE. 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 SE. 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 SE. 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 TCP Reset (RST) could not be sent.

TCP memory pressures

Number of times that the TCP subsystem encounters memory constraints.

1 RST = reset

2 SYN = synchronized

3 ARP = Address Resolution Protocol

4 PAWS = Protection Against Wrapped Sequence

5 ACK = acknowledgment

6 FACK = Forward Acknowledgment

7 SACK = Selective Acknowledgment

8 D-SACK = Duplicate Selective Acknowledgment

9 cwnd = congestion window


Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.


show statistics transaction-logs

To display SE transaction log export statistics, use the show statistics transaction-logs command in EXEC configuration mode.

show statistics transaction-logs

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

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

Table 0-13 describes the fields shown in the show statistics transaction-logs display.

Table 0-13 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 SE failed to open a connection to the FTP export server.

Initial Put Failures

Number of times that the SE 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 SE failed to open a connection to the FTP export server on a retry.

Retry Put Failures

Number of times that the SE failed to transfer a file to the FTP export server on a retry.

Authentication Failures

Number of times that the SE failed to authenticate with the FTP export server. This situation might occur if the SE is misconfigured with the wrong password for the FTP server or the password on the FTP server has been changed since the SE was configured.

Invalid Server Directory Failures

Number of times the SE failed to direct traffic to the correct server directory.


Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

show transaction-logging

Displays the transaction log configuration settings and a list of archived transaction log files.

transaction-log force

Forces the archive or export of the transaction log.


show statistics udp

To display SE User Datagram Protocol (UDP) statistics, use the show statistics udp command in EXEC configuration mode.

show statistics udp

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

Table 0-14 describes the fields shown in the show statistics udp display.

Table 0-14 show statistics udp Field Descriptions 

Field
Description

Packets received

Total number of UDP packets received.

Packets to unknown port received

Number of packets to unknown ports received.

Packet receive error

Number of packet receive errors.

Packet sent

Number of UDP packets sent.


show statistics web-engine

To display the Web Engine statistics, use the show statistics web-engine command in EXEC configuration mode.

show statistics web-engine [abr {generic-tracking-app [file | session | summary] | hls-media-app [detail | fragment-file | manifest-file | session | summary] | smoothhd-media-app [detail | fragment-file | manifest-file | meta-file | session | summary] | zeri-media-app [detail | fragment-file | manifest-file | meta-file | summary]} | detail | error summary | key-client | performance | usage]

Syntax Description

abr

(Optional) Adaptive Bit-Rate streaming statistics.

generic-tracking-app

(Optional) Displays Generic-Tracking-App statistics.

hls-media-app

(Optional) Displays Hls-Media-App statistics.

detail

(Optional) Displays Hls-Media-App Detail Statistics.

fragment-file

(Optional) Displays Hls-Media-App Fragment-File Statistics.

manifest-file

(Optional) Displays Hls-Media-App Manifest-File Statistics.

meta-file

(Optional) Displays Hls-Media-App Meta-File Statistics.

session

(Optional) Displays Session Statistics.

summary

(Optional) Displays Hls-Media-App Summary.

smoothhd-media-app

Displays SmoothHD-Media-App statistics.

detail

Displays the SmoothHD-Media-App Detail Statistics.

fragment-file

Displays the SmoothHD-Media-App Fragment-File Statistics.

manifest-file

Displays the SmoothHD-Media-App Manifest-File Statistics.

meta-file

Displays the SmoothHD-Media-App Meta-File Statistics.

summary

Displays the SmoothHD-Media-App Summary.

zeri-media-app

Displays the Zeri-Media-App statistics.

detail

Displays the Zeri-Media-App Detail Statistics.

fragment-file

Displays the Zeri-Media-App Fragment-File Statistics.

manifest-file

Displays the Zeri-Media-App Manifest-File Statistics.

meta-file

Displays the Zeri-Media-App Meta-File Statistics.

summary

Displays the Zeri-Media-App Summary.

detail

(Optional) Displays detail statistics.

error

(Optional) Displays error statistics.

summary

Displays statistics based on 4xx/5xx response codes.

key-client

(Optional) Displays key client statistics.

performance

(Optional) Displays performance statistics.

usage

(Optional) Displays usage statistics.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

The Web Engine must be running to see the statistics. The Web Engine is running by default.


Note A client request to an edge SE triggers a liveness query to the upstream SEs and Content Acquirer. Even after the client connection is closed, the liveness query continues for up to ten minutes. This is to keep the SEs ready with liveness states for subsequent client requests.



Note The show statistics web-engine detail command output also displays Web Engine memory usage. This can increase to greater than 2 GB and can stay above 2 GB even after traffic subsides. This is expected behavior and does not indicate a memory leak.


Table 0-15 describes the fields shown in the show statistics web-engine display.

Table 0-15 show statistics web-engine Field Descriptions 

Field
Description

HTTP Request Info Statistics

Num Lookups

Number of CAL lookups done.

Preposition Hit

Number of preposition hit requests. This statistic is only incremented at the end of the session life.

External Hit

Displays NAS Origin Hit count.

Cache Hit

Number of requests that resulted in a cache hit. This statistic is only incremented at the end of the session life.

Cache Miss

Number of requests that resulted in a cache miss (the web object was not available in the cache).

Partial Cache Hit

Number of cacheable requests that were partial cache hits. This statistic is only incremented at the end of the session life.

Cache Bypass

Whenever the Web Engine receives either a large file range request or a request type that it cannot cache. This statistics counter increases and the request file is not cached. This statistic is only incremented at the end of the session life.

Live Miss

Session miss for MP3 Live streaming over HTTP.

Live Hit

Session hit for MP3 Live streaming over HTTP.

ASX Meta Response

Incremented when a Windows Media Live Request(.asx) request is processed by the Web Engine.

HTTP Request Type Statistics

Get Requests

Total Get requests.

Post Requests

Total Post requests.

Head Requests

Total Head requests.

Range Requests Received

Range requests from clients.

Range Requests Sent

Requests sent to OS liveness query.

Revalidation Requests Received

Revalidation requests from clients. This counter is incremented only when an If-Modified-since (IMS) request is received by the Streamer.

Revalidation Requests Sent

Revalidation requests to OS liveness query.

Liveness Query

Liveness query received from the downstream SE. Liveness queries are sent even when there are no client requests and liveness updates are sent every ten minutes, so it is not mandatory to have client request in order to generate a liveness query.

Streaming Redirected Requests

The number of request handed over to WMT.

Local Requests

Requests from other Protocol Engines.

Play Live Requests

WMT Live requests.

Total Outgoing Requests

Total number of unique request that web-engine sent to the upstream.

Origin Server Redirected Requests

Cumulative sum of requests coming to all delivery services on the SE for which this feature is enabled. This number is cleared when the Web Engine is restarted or the clear statistics all command is executed.

HTTP Authorization Statistics

Authorization Allow

Number of authorization requests being allowed.

Authorization No Cache

Number of authorization requests being applied with the No-cache rule.

Authorization Force Revalidate

Number of authorization requests being applied with the Force revalidate rule.

Authorization Deny

Number of authorization requests being denied.

Authorization Rewrite

Number of authorization requests being applied with the rewrite rule.

Authorization GenerateSign

Number of authorization requests being applied with the generate sign rule.

Authorization Redirect

Number of authorization requests being redirected.

Authorization Resolve

Number of authorization requests being applied with the URL-Resolve rule.

WMT (HTTP) Rule Statistics

Allow

Number of WMT (HTTP) rules being allowed.

Block

Number of WMT (HTTP) rules being blocked.

URL Redirect

Number of URL redirect statistics.

URL Rewrite

Number of URL rewrite statistics.

Validate URL Signature

Total number of requests for which URL sign validation was performed.

No Cache

Number of WMT (HTTP) rules being applied with no cache.

HTTP Error Statistics

Client Errors

Number of 4xx errors.

Server Errors

Number of 5xx errors.

Bad Requests

Number of HTTP request corruptions.

Error Response Hit

Number of error response cache hits.

Error Response Miss

Number of error response cache misses. With error response caching enabled, the error responses like 404 and 503 could be cached.

HTTP Performance Statistics

Total Bytes In

Total bytes in. This statistic is only incremented at the end of the session life.

Total Bytes Out

Total bytes out. This statistic is only incremented at the end of the session life.

Total Requests

Total requests since last web-engine statistics cleared time.

Average Request Per Second

Average requests per second.

Note To get an accurate request per second reading in a given time period, clear the Web Engine statistics first and then generate the shows statistics web-engine command.

Average Bytes Per Second

Average number of bytes per second since the last web-engine statistics were cleared.

Web-Engine Detail Statistics

Active HTTPSession

HTTPSession is unique to the end user connection. This value counts the HTTP request targeted to port 80, regardless of which Protocol Engine handles the request. The sample rate and Real-Time value are calculated at the time the command is executed.

Active DataSource

Sources used to fetch the data. Disk for cache hit; OS for cache miss.

Active HTTPDataFeed

Active connections to the Origin Server or upstream SE's to fetch Data.

Active HTTPData
SourceFinder

The number of active DataSourceFinder present. DataSourceFinder is responsible for creating the datasource.

Active HTTPTransact-
ion

On a given session, this is the number of active pipeline transactions the Web Engine is currently processing.

Pending HTTPTransact-
ion

On a given session, this is the number of pending pipeline transactions the Web Engine has yet to process.

Active ServerXact

HTTP Request currently under process.

Total HTTPConnection

Total outgoing HTTP connection to upstream.

Active HTTPConnection

HTTP connection currently serving request.

Idle Proxy HTTPConnection

Intra-SE connection in the idle queue.

Idle Origin HTTPConnection

Non-Intra-SE/Origin Server connection in the idle queue.

Memory Hit

Number of requested files available in /tmpfs. This statistic is only incremented at the end of the session life.

Cut-Thru Counter

Number of cached files deleted without moving to disk.

Memory Usage

Memory usage of the Web Engine process.

WebEngine Trickle Status

This flag is set when the Web Engine has exceeded thresholds but cannot restart because of outstanding sessions. When the transactions on HTTPSessions complete, it looks at this trickle flag and terminates the connection instead of processing the next request on the connection.

This flag is reset to 0 when memory usage is low because the number of sessions has decreased. If the number of sessions goes to 0 and memory usage is still high, the Trickle flag is set and the web-engine restarts.

Outstanding Content Create Requests

Allocates a disk and a file path for a given URL. The protocol engine uses this location to store the downloaded content. The number of outstanding creates reflect the number of such requests to the CAL module that have been submitted but were not completed.

Outstanding Content Lookup Requests

Translates the URL from an end client into a disk path in the case of a cache hit (based on a previous create). In the case of cache miss, it would give the route from where the content can be found. The counter number of outstanding lookups reflects the number of pending requests.

Outstanding Content Delete Requests

Deletes a file created by CAL. The number of outstanding deletes reflects the number of pending delete requests.

Outstanding Content Update Requests

Updates the Content metadata CAL. The number of outstanding updates reflect the number of pending update requests submitted to CAL.

Outstanding Content Popularity Update Requests

Updates the Content Popularity metadata CAL. The number of outstanding updates reflect the number of pending update requests submitted to CAL.



Note The "Total Bytes Out" statistic counts the header length but the "Total Bytes In" statistic does not.


Examples

The following example shows how to display the detailed Web Engine statistics:

ServiceEngine# show statistics web-engine abr generic-tracking-app file
 
   
Generic Session File Statistics
-----------------------
Preposition Hit								:                    0
Alien Hit								:                    0
Cache Hit								:                    0
Cache Miss								:                    0
Partial Cache Hi								:                    0
Cache Bypass								:                    0
 
   
ServiceEngine# show statistics web-engine abr generic-session-app session
 
   
Session Statistics
-----------------------
Active Generic sessions														:                    0
Sessions Created														:                    0
Sessions Created-Internal SessID														:                    0
Sessions Recreated With Received Cookie														:                    0
Sessions Deleted-Inactive														:                    0
Requests Failed to Track Internal Error														:                    0
Requests Failed to Track Client IP Invalid														:                    0
Requests Failed to Track SessID Collision														:                    0
Requests Failed to Track														:                    0
Requests Failed to Track Session in Deletion														:                    0
Start Notifications sent														:                    0
Start Notification send failed														:                    0
Stop Notifications sent														:                    0
Stop Notification send failed														:                    0
Notification message send aborted due to DNS failure														:                    0
Requests Internal SessId With Cookie Disabled														:                    0
 
   
ServiceEngine# show statistics web-engine abr generic-tracking-app summary
 
   
Generic Session Summary Statistics
-----------------------
Preposition Hit								:                    0
External Hit								:                    0
Cache Hit								:                    0
Cache Miss								:                    0
 
   
ServiceEngine# show statistics web-engine detail
 
   
HTTP Request Info Statistics
-----------------------
Num Lookups                    :                     4212308 
Preposition Hit                :                           0 
External Hit                   :                           0 
Cache Hit                      :                       30109 
Cache Miss                     :                     4043651 
Partial Cache Hit              :                           0 
Cache Bypass                   :                           0 
Live Miss                      :                           0 
Live Hit                       :                           0 
ASX Meta Response              :                           0 
 
   
HTTP Request Type Statistics
-----------------------
Get Requests                   :                     4215164 
Post Requests                  :                           0 
Head Requests                  :                           0 
Range Requests Received        :                          10 
Range Requests Sent            :                           0 
Revalidation Requests Received :                       26921 
Revalidation Requests Sent     :                     1003660 
Liveness Query                 :                        6832 
WMT(http) Redirected Requests  :                           0 
Local Requests                 :                           0 
Play Live Requests             :                           0 
Total Outgoing Requests        :                     4073031 
 
   
HTTP Authorization Statistics
----------------------
Authorization Allow            :                     4212638 
Authorization No Cache         :                           0 
Authorization Force Revalidate :                           0 
Authorization Deny             :                           0 
Authorization Rewrite          :                           0 
Authorization GenerateSign     :                           0 
Authorization Redirect         :                           0 
Authorization Resolve          :                           0 
 
   
WMT(http) Rule Statistics
----------------------
Allow                          :                           0 
Block                          :                           0 
Url Redirect                   :                           0 
Url Rewrite                    :                           0 
Validate Url Signature         :                           0 
No Cache                       :                           0 
 
   
HTTP Error Statistics
----------------------
Client Errors                  :                           0 
Server Errors                  :                      877658 
Bad Requests                   :                           0 
Error Response Miss            :                           0 
Error Response Hit             :                           0 
 
   
HTTP Performance Statistics
----------------------
Total Bytes In                 :                621029676477 
Total Bytes Out                :                594801670055 
Total Requests                 :                     4215255 
Average Requests Per Second    :                       60.61 
Average Bytes Per Second       :                  8552759.45 
 
   
Web-Engine Detail Statistics
----------------------
Active HTTPSession             :                          29 
Active DataSource              :                         161 
Active HTTPDataFeed            :                           0 
Active HTTPDataSourceFinder    :                           0 
Active HTTPTransaction         :                           1 
Pending HTTPTransaction        :                           0 
Active ServerXact              :                           0 
Total HTTPConnection           :                          12 
Active HTTPConnection          :                           0 
Idle Proxy HTTPConnection      :                           0 
Idle Origin HTTPConnection     :                          12 
Memory Hit                     :                         377 
Cut-Thru Counter               :                     7390705 
Memory Usage                   :                  2297475072 
WebEngine Trickle Status       :                           0 
Outstanding Content Create Requests:                       0 
Outstanding Content Lookup Requests:                       0 
Outstanding Content Delete Requests:                       0 
Outstanding Content Update Requests:                       0 
Outstanding Content Popularity Update Requests:                    0 
Statistics was last cleared on Wednesday, 24-Aug-2011 22:18:08 PDT.
ServiceEngine#
 
   
The following example shows how to display the statistics for theHLD-Media-App:
ServiceEngine# show statistics web-engine abr hls-media-app 
 
   
Media Manifest File Statistics
-----------------------
Preposition Hit                                       :                    0 
Alien Hit                                             :                    0 
Cache Hit                                             :                    0 
Cache Miss                                            :                    0 
Partial Cache Hit                                     :                    0 
Cache Bypass                                          :                    0 
 
   
Media Fragment File Statistics
-----------------------
Preposition Hit                                       :                    0 
Alien Hit                                             :                    0 
Cache Hit                                             :                    0 
Cache Miss                                            :                    0 
Partial Cache Hit                                     :                    0 
Cache Bypass                                          :                    0 
 
   
Media Detail Statistics
----------------------
Active Assets                                         :                    0 
Active Manifest Files                                 :                    0 
Active Media Files                                    :                    0 
Request Sent To Default App                           :                    0 
 
   
Session Statistics
----------------------
Active Media sessions                                 :                    0 
Sessions Created                                      :                    0 
Sessions Created-Internal SessID                      :                    0 
Sessions Recreated With Received Cookie               :                    0 
Sessions Deleted-Inactive                             :                    0 
Sessions Deleted-Internal Error                       :                    0 
Sessions Deleted-Expired Request                      :                    0 
Sessions Deleted-Session ID Error                     :                    0 
Requests Rejected-Client IP Invalid                   :                    0 
Requests Rejected-SessID Collision                    :                    0 
Requests Rejected-Failed to Track                     :                    0 
Inline Key Requests                                   :                    0 
Start Notifications sent                              :                    0 
Start Notification send failed                        :                    0 
Stop Notifications sent                               :                    0 
Stop Notification send failed                         :                    0 
Notification message send aborted due to DNS failure  :                    0 
ServiceEngine#
 
   
The following example shows how to display the detailed statistics for the Zeri-Media-App:
ServiceEngine# show statistics web-engine abr zeri-media-app detail  
 
   
Media Detail Statistics
-----------------------
Active DataSource              :                           0 
Request Sent To Default App    :                           0 
ServiceEngine#
 
   
The following example shows how to display the summary for the Smooth-Media-App:
ServiceEngine# show statistics web-engine abr smoothhd-media-app summary
 
   
Media Summary Statistics
-----------------------
Preposition Hit                :                           0 
External Hit                   :                           0 
Cache Hit                      :                           0 
Cache Miss                     :                           0 
ServiceEngine#

Related Commands

Command
Description

show web-engine

Displays the Web Engine information.

web-engine (EXEC)

Configures the Web Engine module.

web-engine (Global configuration)

Configures the Web Engine caching parameters.


show statistics wmt

To display the SE Windows Media Technologies (WMT) statistics, use the show statistics wmt command in EXEC configuration mode.

show statistics wmt {all | bytes {incoming | outgoing} | cache | errors | multicast | requests | rule | savings | streamstat [incoming | live | outgoing | stream-id stream_id] | usage}

Syntax Description

all

Displays all WMT statistics.

bytes

Displays unicast byte statistics.

incoming

(Optional) Displays unicast incoming byte statistics.

outgoing

(Optional) Displays unicast outgoing byte statistics.

cache

Displays cache validation statistics.

errors

Displays error statistics.

multicast

Displays multicast statistics.

requests

Displays unicast request statistics.

rule

Displays the Rule Template statistics.

savings

Displays savings statistics.

streamstat

Displays Windows Media streaming connections.

incoming

(Optional) Displays statistics of all incoming WMT streams from the SE.

live

(Optional) Displays aggregated live stream statistics.

outgoing

(Optional) Displays statistics of all outgoing WMT streams from the SE.

stream-id

(Optional) Displays statistics of the WMT streams that have the specified stream ID. The range is from 1 to 999999.

stream_id

WMT stream ID to display.

usage

Displays current usage statistics.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

The output of the show statistics wmt command includes information about WMT RTSP requests. For example, the output from the show statistics wmt command was changed as follows:

RTSP-related information was added to the show statistics wmt all command output.

Information about RTSPT and RTSPU was added in the transport protocol portion of the show statistics wmt bytes command output.

RTSPT and RTSPU errors were added to the show statistics wmt errors command output.

The show statistics wmt requests command output includes the RTSPT and RTSPU protocols and Fast Start and Fast Cache data.

The live option was added to the show statistics wmt streamstat command to enable you to display aggregated live statistics. Also, the incoming, outgoing, and stream-id options were added to the show statistics wmt streamstat command to display statistics of all incoming WMT streams, outgoing WMT streams, and streams with the specified ID.

Configuring the HTTP Allow and Block Rule

For the MMS over HTTP request rule, even though the request is served by WMT, it doesn't increment the statistics. The user needs the statistics for all WMT requests. Now the user can execute the show statistics http rule command as the rules daemon check is done from the HTTP side, and the request is redirected to WMT.

Table 0-16 describes the fields shown in the show statistics wmt all display.

Table 0-16 show statistics wmt all Field Descriptions 

Field
Description

Unicast Requests Statistics

Total unicast requests received

Total number of unicast requests received.

Display shows the number of requests in each category and calculates the percentage of the total for each category.

Streaming Requests served

Number of streaming requests received.

Multicast nsc file Request

Number of multicast NSC file requests received.

Note This field continuously increments for a single request if there are two SE locations in the same subnet. This is not valid and causes both SEs to send data to the same multicast address.

Authenticate Requests

Number of authenticated requests received.

Requests error

Number of request errors received.

By Type of Content

Live content

Number of live content requests received.

On-Demand Content

Number of on-demand content requests received.

By Transport Protocol

HTTP

Number of HTTP requests received.

RTSPT

Number of RTSPT requests received.

Unicast Savings Statistics

Total bytes saved

Total number of bytes saved.

By Source of Content

Local

Number of local bytes saved.

Remote HTTP

Number of remote HTTP bytes saved.

Remote RTSP

Number of remote RTSP bytes saved.

Multicast

Number of multicast bytes saved.

CDN-Related WMT Requests

CDN Content Hits

Number of CDN content request hits.

CDN Content Misses

Number of CDN content request misses.

CDN Content Live

Number of CDN live content requests.

CDN Content Errors

Number of CDN content request errors.

Fast Streaming-related WMT Requests

Normal Speed

Number of normal-speed Fast Streaming-related WMT requests.

Fast Start Only

Number of Fast Start WMT requests.

Fast Cache Only

Number of Fast Cache WMT requests.

Fast Start and Fast Cache

Number of Fast Start and Fast Cache WMT requests.

Authenticated Requests

By Type of Authentication

Negotiate

Number of negotiated authentication authenticated requests.

NTLM

 

Digest

Number of digest authentication authenticated requests.

Basic

Number of basic authentication authenticated requests.

Unicast Bytes Statistics

Total unicast incoming bytes

Total number of bytes incoming as unicast streams.

By Type of Content

Live content

Number of bytes incoming as unicast streams for live content.

On-Demand Content

Number of bytes incoming as unicast streams for on-demand content.

By Transport Protocol

HTTP

Number of bytes incoming as unicast streams using the HTTP transport protocol.

RTSPT

Number of bytes incoming as unicast streams using the RTSPT transport protocol.

Total unicast outgoing bytes

Total number of bytes outgoing as unicast streams.

Unicast Savings Statistics

Total bytes saved

Total number of bytes saved.

By prepositioned content

Number of bytes saved for prepositioned content.

By live-splitting

Number of bytes saved for live-splitting content.

By cache-hit

Number of bytes saved for cached content.

Live Splitting

Incoming bytes

Number of bytes incoming as live-split streams.

Outgoing bytes

Number of bytes outgoing as live-split streams.

Bytes saved

Number of bytes saved.

Caching

Bytes cache incoming

Number of bytes incoming for the cache.

Bytes cache outgoing

Number of bytes outgoing from the cache.

Bytes cache total

Total number of bytes cached.

Bytes cache-bypassed

Number of bytes that bypassed the cache.

Cacheable requests

Number of cacheable requests.

Req cache-miss

Number of cacheable requests that were cache misses.

Req cache-hit

Number of cacheable requests that were cache hits.

Req cache-partial-hit

Number of cacheable requests that were partial cache hits.

Req cache-total

Total number of requests that were cached.

Objects not cached

Number of objects that were not cached.

Cache bypassed

Number of objects that were not cached because they bypassed the cache.

Exceed max-size

Number of objects that were not cached because they exceeded the maximum cacheable size limit.

Usage Summary

Concurrent Unicast Client Sessions

Total number of concurrent unicast client sessions.

Current

Number of concurrent unicast client sessions currently running.

Max

Maximum number of concurrent unicast client sessions recorded.

Concurrent Remote Server Sessions

Total number of concurrent remote server sessions.

Concurrent Active Multicast Sessions

Total number of concurrent active multicast sessions.

Concurrent Unicast Bandwidth (Kbps)

Total amount of bandwidth being used (in kilobits per second) for concurrent unicast sessions.

Concurrent Bandwidth to Remote Servers (Kbps)

Total amount of bandwidth being used (in kilobits per second) for concurrent remote server sessions.

Concurrent Multicast Out Bandwidth (Kbps)

Total amount of bandwidth being used (in kilobits per second) for concurrent multicast out sessions.

Error Statistics

Total request errors

Total number of request errors.

Errors generated by this box

Number of request errors generated by this device.

Errors generated by remote servers

Number of request errors generated by remote servers.

Other Statistics

Authentication Retries from Clients

Number of authentication retries from clients.

WMT Rule Template Statistics

URL Rewrite

Number of URL rewrites.

URL Redirect

Number of URL redirects.

URL Block

Number of blocked URLs.

No-Cache

Number of no-cache matches.

Allow

Number of allow matches.

Multicast Statistics

Total Multicast Incoming Bytes

Total number of bytes incoming as multicast-out streams.

Total Multicast Outgoing Bytes

Total number of bytes outgoing as multicast-out streams.

Total Multicast Logging Requests

Total number of multicast logging requests.

Aggregate Multicast Out Bandwidth (Kbps)

Aggregated amount of bandwidth being used (in kilobits per second) for multicast out sessions.

Current

Number of concurrent multicast out sessions currently running.

Max

Maximum number of multicast out sessions recorded.

Number of Concurrent Active Multicast Sessions

Number of concurrent active multicast sessions.

Cache Validation Statistics

 

Fresh Content Requests

 

Object Not Found

 

Revalidate Requests

 

Revalidate Reasons

 

Object Expired

 

Min TTL Expired

 

Max TTL Expired

 

MBR Content

 

Others

 

Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

show wmt

Displays WMT bandwidth and proxy mode configuration.

wmt

Configures the WMT.


show tacacs

To display TACACS+ authentication protocol configuration information, use the show tacacs command in EXEC configuration mode.

show tacacs

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

The show tacacs command displays the TACACS+ configuration for the Service Engine.

Table 0-17 describes the fields shown in the show tacacs display.

Table 0-17 show tacacs Field Descriptions 

Field
Description

Login Authentication for Console/Telnet Session

Status of whether TACACS+ server is enabled for login authentication.

Configuration Authentication for Console/Telnet Session

Status of whether TACACS+ server is enabled for authorization or configuration authentication.

Authentication scheme fail-over reason

Status of whether Service Engines fails over to the secondary method of administrative login authentication whenever the primary administrative login authentication method is used.

TACACS+ Configuration

TACACS+ server parameters.

TACACS+ Authentication

Status of whether TACACS+ authentication is enabled on the Service Engine.

Key

Secret key that the Service Engine uses to communicate with the TACACS+ server. The maximum number of characters in the TACACS+ key should not exceed 99 printable ASCII characters (except tabs).

Timeout

Number of seconds that the Service Engine waits for a response from the specified TACACS+ Authentication Server before declaring a timeout.

Retransmit

Number of times that the Service Engine is to retransmit its connection to the TACACS+ server if the TACACS+ timeout interval is exceeded.

Password type

Mechanism for password authentication. By default, the PAP1 is the mechanism for password authentication.

Server

Hostname or IP address of the TACACS+ server.

Status

Status of whether server is the primary or secondary host.

1 PAP = Password Authentication Protocol


Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

show statistics tacacs

Displays the SE TACACS+ authentication and authorization statistics.

tacacs

Configures TACACS+ server parameters.


show tech-support

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

show tech-support [list-files directory_name [recursive] | page | service {acquisition-distribution [authentication | cms | flash-media-streaming | icap | kernel | movie-streamer | rules | web-engine | wmt] | authentication [acquisition-distribution | cms | flash-media-streaming | icap | kernel | movie-streamer | rules | web-engine | wmt] | cms [acquisition-distribution | authentication | flash-media-streaming | icap | kernel | movie-streamer | rules | web-engine | wmt] | flash-media-streaming [acquisition-distribution | authentication | cms | icap | kernel | movie-streamer | rules | web-engine | wmt] | icap [acquisition-distribution | authentication | cms | flash-media-streaming | kernel | movie-streamer | rules | web-engine | wmt] | kernel [acquisition-distribution | authentication | cms | flash-media-streaming | icap | movie-streamer | rules | web-engine | wmt] | movie-streamer [acquisition-distribution | authentication | cms | flash-media-streaming | icap | kernel | rules | web-engine | wmt] | rules [acquisition-distribution | authentication | cms | flash-media-streaming | icap | kernel | movie-streamer | web-engine | wmt] | web-engine [acquisition-distribution | authentication | cms | flash-media-streaming | icap | kernel | movie-streamer | rules | wmt] | wmt [acquisition-distribution | authentication | cms | flash-media-streaming | icap | kernel | movie-streamer | rules | web-engine]}

Syntax Description

list-files

(Optional) Displays the list of files under a directory.

directory_name

Directory name (use absolute path, such as /local1/logs).

page

(Optional) Specifies the pages through the output.

service

(Optional) Displays technical support information specific to a service.

authentication

Displays technical support information related to HTTP authentication.

acquisition-distribution

Displays technical support information related to acquisition and distribution.

cms

Displays technical support information related to CMS.

flash-media-streaming

Displays technical support information related to Flash Media Streaming.

http

Displays technical support information related to HTTP.

icap

Displays technical support information related to ICAP.

kernel

Displays technical support information related to the kernel.

movie-streamer

Displays technical support information related to the Movie Streamer.

rules

Displays technical support information related to rules.

wmt

Displays technical support information related to WMT.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

Use this command to view system information necessary for TAC to assist you with your SE. We recommend that you log the output to a disk file. Use the streaming option to view information specific to the streaming feature.

The following types of information are available when using the streaming option with the show tech-support command.

General Information

You can access the following general information when you enter the show tech-support command:

Version and hardware (show version)

Running configuration (show running-config)

Processes (show processes)

Process memory (show processes memory)

System memory

File system information

Interface information

Media file system statistics

Application and kernel core dump information

Netstat

Information Common to WMT and RTSP

Information that is common to both WMT and RTSP is as follows:

CPU or memory processes (show programs)

WMT streaming connections (show statistics wmt streamstat)

Bandwidth allocation (show bandwidth)

Bit rate allocation (show bitrate)

Acquirer information (show acquirer)

Rules (show rule all)

Distribution channel details

Information Specific to WMT

Information that is specific to WMT is as follows:

WMT bandwidth and proxy mode configuration (show wmt)

WMT statistics (show statistics wmt)

Information Specific to RTSP

Information that is specific to RTSP is as follows:

RTSP configuration (show rtsp)

Examples

The following example shows the types of information available about the CDS software. Because the show tech-support command output is comprehensive and can be extensive, only excerpts are shown in the following example:

ServiceEngine# show tech-support
 
   
CPU Usage:
   cpu: 0.39% User,  0.42% System,  0.33% User(nice),  98.86% Idle
  cpu0: 0.39% User,  0.42% System,  0.33% User(nice),  98.86% Idle
--------------------------------------------------------------------
 PID  STATE PRI User T  SYS T        COMMAND      
----- ----- --- ------ ------ --------------------
    1    S   0   4386   1706 (init)
    2    S   0      0      0 (keventd)
    3    S  19      0      0 (ksoftirqd_CPU0)
    4    S   0      0      0 (kswapd)
    5    S   0      0      0 (bdflush)
    6    S   0      0      0 (kupdated)
    7    S   0      0      0 (scsi_eh_0)
   45    S   0   4733   4114 (nodemgr)
   46    S   0      0      0 (syslogd)
   47    R   0     83     65 (dataserver)
  920    S   0      0      0 (login)
 1207    S   0      0      0 (parser_server)
 1208    S   0      0      0 (eval_timer_mana)
 1211    S   0     46      1 (parser_server)
 1443    S   0      0      0 (overload)
 1444    S   0      0      0 (standby)
 1445    S   0     13     29 (cache)
 1446    S   0      0      0 (proxy_poll)
 1447    S   0      0      0 (snmpced)
 1448    S   0      0      0 (http_authmod)
 1458    S   0      0      0 (http_authmod)
 1465    S   0      0      0 (http_authmod)
 1466    S   0      0      0 (http_authmod)
 1467    S   0      0      0 (http_authmod)
 1537    S   0      0      0 (cache)
 1538    S   0      0      0 (unified_log)
 1540    S   0      0      1 (webserver)
 1541    S   0      2      2  (mcm)
 1542    S   0      0      0 (cache)
 1543    S   0      0      0 (cache)
 1550    S   0      0      0 (cache)
 1551    S   0      0      0 (cache)
 1556    S   0      0      0 (cache)
 1567    S   0      0      0  (mcm)
 1568    S   0      0      0  (mcm)
 1629    S   0  18982   4140 (crond)
 1936    S   0   1669    611 (bootnet)
 1937    S  10      0      0 (tracknet)
 1938    S  10  33545   5556 (checkup)
 1983    S   0      0      0 (srcpd)
 2023    S   0      1      0 (admin-shell)
 2024    S   0      0      0 (parser_server)
 2150    S   0      0      0 (rsvpd)
 2152    S   0      0      0 (rtspd)
 2153    S   0   1635   1067 (httpsd)
 2164    S   0      0      0 (librarian)
 2167    S   0   1667   2105 (libaux)
 2170    S   0      0      0 (mapper)
 2178    S   0     32     37 (cache)
 2179    S   0      0      0 (router)
 2180    S   0      0      0 (fill)
 2183    S   0      0      0 (remotereq)
 2185    S -20      0      0 (videosvr)
 2188    S   0      9      4 (contentsvr)
 2189    S   0      0      0 (routeraux)
 2190    S   0      0      1 (dfcontrolsvr)
 2226    S   0      0      0 (smbd)
 2228    S   0      0      0 (nmbd)
 2973    Z   0      0      0 (cache)
 8446    S   0      0      0 (httpsd)
 8447    S   0      0      0 (gcache)
18173    S   0      0      0 (in.telnetd)
18174    S   0      0      0 (login)
18175    S   0      2      2 (admin-shell)
18176    S   0      0      0 (parser_server)
19426    S   0      0      0 (httpsd)
19427    S   0      0      0 (httpsd)
19456    Z   0      0      0 (cache)
19503    Z   0     30      3 (crond)
19515    S   0      0      0 (more)
19516    S   0      6     18 (exec_show_tech-)
19553    R   0      0      0 (exec_show_proce)
 
   
------------------ process memory --------------------
 
   
     Total       Used       Free     Shared    Buffers     Cached
1050943488  564785152  486158336          0    5222400  475176960
 
   
 
   
 
   
 
   
   PID State    TTY  %MEM    VM Size RSS (pages) Name
------ ----- ------ ----- ---------- ----------- ----
     1     S      0  0.0    1146880         119 (init)
     2     S      0  0.0          0           0 (keventd)
     3     S      0  0.0          0           0 (ksoftirqd_CPU0)
     4     S      0  0.0          0           0 (kswapd)
     5     S      0  0.0          0           0 (bdflush)
     6     S      0  0.0          0           0 (kupdated)
     7     S      0  0.0          0           0 (scsi_eh_0)
    45     S      0  0.0    1208320         143 (nodemgr)
    46     S      0  0.0    1630208         194 (syslogd)
    47     R      0  0.0    1974272         238 (dataserver)
   920     S   1088  0.0    1728512         236 (login)
  1207     S      0  0.3    4980736         847 (parser_server)
  1208     S      0  0.0    1933312         151 (eval_timer_mana)
  1211     S      0  0.3    4980736         847 (parser_server)
  1443     S      0  0.0    1548288         154 (overload)
  1444     S      0  0.0    1724416         161 (standby)
  1445     S      0  5.9   65646592       15266 (cache)
  1446     S      0  0.0    1957888         173 (proxy_poll)
  1447     S      0  0.1    2097152         290 (snmpced)
  1448     S      0  0.0    1757184         205 (http_authmod)
  1458     S      0  0.0    1757184         205 (http_authmod)
  1465     S      0  0.0    1757184         205 (http_authmod)
  1466     S      0  0.0    1757184         205 (http_authmod)
  1467     S      0  0.0    1757184         205 (http_authmod)
  1537     S      0  5.9   65646592       15266 (cache)
  1538     S      0  0.0    1789952         169 (unified_log)
  1540     S      0  0.4   10817536        1164 (webserver)
  1541     S      0  0.0    2150400         251 (mcm)
  1542     S      0  5.9   65646592       15266 (cache)
  1543     S      0  5.9   65646592       15266 (cache)
  1550     S      0  5.9   65646592       15266 (cache)
  1551     S      0  5.9   65646592       15266 (cache)
  1556     S      0  5.9   65646592       15266 (cache)
  1567     S      0  0.0    2150400         251 (mcm)
  1568     S      0  0.0    2150400         251 (mcm)
  1629     S      0  0.0    1187840         137 (crond)
  1936     S      0  0.6    7532544        1605 (bootnet)
  1937     S      0  0.2    3215360         545 (tracknet)
  1938     S      0  0.2    3637248         654 (checkup)
  1983     S      0  0.3    4374528         838 (srcpd)
  2023     S   1088  0.0    2146304         182 (admin-shell)
  2024     S      0  0.3    4980736         847 (parser_server)
  2150     S      0  0.0    1679360         188 (rsvpd)
  2152     S      0  0.3    6217728         881 (rtspd)
  2153     S      0  0.1    2527232         329 (httpsd)
  2164     S      0  0.3    6533120         990 (librarian)
  2167     S      0  0.4    7110656        1144 (libaux)
  2170     S      0  0.3    5955584         863 (mapper)
  2178     S      0  0.3    6135808         927 (cache)
  2179     S      0  0.3    6287360         948 (router)
  2180     S      0  0.3    5955584         926 (fill)
  2183     S      0  0.3    5832704         852 (remotereq)
  2185     S      0  0.3    8269824         873 (videosvr)
  2188     S      0  0.4    7651328        1196 (contentsvr)
  2189     S      0  0.3    6103040         953 (routeraux)
  2190     S      0  0.4   10272768        1075 (dfcontrolsvr)
  2226     S      0  0.1    3559424         504 (smbd)
  2228     S      0  0.0    2084864         247 (nmbd)
  2973     Z      0  0.0          0           0 (cache)
  8446     S      0  0.1    2506752         327 (httpsd)
  8447     S      0  0.0    1421312         116 (gcache)
 18173     S      0  0.0    1220608         132 (in.telnetd)
 18174     S  34816  0.0    1736704         238 (login)
 18175     S  34816  0.0    2162688         184 (admin-shell)
 18176     S      0  0.3    4980736         847 (parser_server)
 19426     S      0  0.1    2551808         350 (httpsd)
 19427     S      0  0.1    2576384         354 (httpsd)
 19456     Z      0  0.0          0           0 (cache)
 19503     Z      0  0.0          0           0 (crond)
 19515     S  34816  0.0    1163264         109 (more)
 19516     S  34816  0.0    1941504         168 (exec_show_tech-)
 19554     R  34816  0.1    2277376         266 (exec_show_proce)
 
   
------------------ system memory --------------------
 
   
Total physical memory    :    1026312 KB
Total free memory        :     474692 KB
Total memory shared      :          0 KB
Total buffer memory      :       5100 KB
Total cached memory      :     464040 KB
 
   
------------------ interfaces --------------------
 
   
Interface type: GigabitEthernet Slot: 0  Port: 0
Type:Ethernet
Ethernet address:00:05:32:02:DD:74
Internet address:172.16.5.234
Netmask:255.255.255.0
Maximum Transfer Unit Size:1500
Metric:1
Packets Received: 513241
Input Errors: 0
Input Packets Dropped: 0
Input Packets Overruns: 0
Input Packets Frames: 0
Packet Sent: 153970
Output Errors: 0
Output Packets Dropped: 0
Output Packets Overruns: 0
Output Packets Carrier: 0
Output Queue Length:100
Collisions: 0
Interrupts:9
MULTICASTMode:autoselect, 100baseTX
 
   

show telnet

To display the Telnet services configuration, use the show telnet command in EXEC configuration mode.

show telnet

Syntax Description

This command has no arguments or keywords.

Command Defaults

Enabled.

Command Modes

EXEC configuration mode.

Examples

The following example shows how to display the Telnet service details:

ServiceEngine# show telnet
telnet service is enabled

Related Commands

Command
Description

exec-timeout

Configures the length of time that an inactive Telnet or SSH session remains open.

telnet enable

Enables the Telnet services.


show transaction-logging

To display the transaction log configuration settings and a list of archived transaction log files, use the show transaction-logging command in EXEC configuration mode.

show transaction-logging

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

To display information about the current configuration of transaction logging on an SE, use the show transaction-logging command. Transaction log file information is displayed for HTTP and WMT caching proxy transactions and TFTP and ICAP transactions.

Examples

The following example shows how to display information about the current configuration of transaction logging on an SE:

ServiceEngine# show transaction-logging
Transaction log configuration:
---------------------------------------
Logging is enabled.
Archive interval: 1800 seconds
Maximum size of archive file: 2000000 KB
Maximum number of archive files: 50 files
Log File format is apache.
Windows domain is not logged with the authenticated username
 
   
Exporting files to ftp servers is enabled.
File compression is disabled.
Export interval: 30 minutes
 
   
server               type  username        directory
10.77.153.110        ftp   root            /var/ftp/test
 
   
 
   
 
   
WMT MMS Caching Proxy/Server Transaction Log File Info
  Working Log file - size : 556
                     age: 483497
  Archive Log file - mms_export_3.1.18.8_20090522_074807        size: 556
 
   
WMT MMS Caching Proxy/Server Transaction Log File Info (WMS-90 format)
  Working Log file - size : 665
                     age: 483497
  Archive Log file - mms_export_wms_90_3.1.18.8_20090522_074807 size: 665
 
   
WMT MMS Caching Proxy/Server Transaction Log File Info (Ext. WMS-90 format)
  Working Log file - size : 702
                     age: 483497
  Archive Log file - mms_export_e_wms_90_3.1.18.8_20090522_074807       size: 70
2
 
   
WMT MMS Caching Proxy/Server Transaction Log File Info (Ext. WMS-41 format)
  Working Log file - size : 584
                     age: 483497
  Archive Log file - mms_export_e_wms_41_3.1.18.8_20090522_074807       size: 58
4
 
   
A&D Transaction Log File Info
  Working Log file - size : 138
                     age: 483497
  Archive Log file - acqdist_3.1.18.8_20090522_074807   size: 138
Movie Streamer Transaction Log File Info
  Working Log file - size : 488
                     age: 482196
  Archive Log file - movie-streamer_3.1.18.8_20090522_062602    size: 648
  Archive Log file - movie-streamer_3.1.18.8_20090522_064309    size: 805
  Archive Log file - movie-streamer_3.1.18.8_20090522_065857    size: 645
  Archive Log file - movie-streamer_3.1.18.8_20090522_070038    size: 648
  Archive Log file - movie-streamer_3.1.18.8_20090522_074807    size: 645
  Archive Log file - movie-streamer_3.1.18.8_20090522_080016    size: 648
  Archive Log file - movie-streamer_3.1.18.8_20090523_030829    size: 645
ICAP Transaction Log File Info
  Working Log file - size : 61
                     age: 483496
  Archive Log file - icap_3.1.18.8_20090522_074807      size: 61
 
   
Web Engine Transaction Log File Info - Apache format
  Working Log file - size : 86
                     age: 483497
  Archive Log file - we_accesslog_apache_3.1.18.8_20090522_074807       size: 82
 
   
Web Engine Transaction Log File Info - CLF format
  Working Log file - size : 3
                     age: 483497
  Archive Log file - we_accesslog_clf_3.1.18.8_20090522_074807  size: 3
 
   
Web Engine Transaction Log File Info - Extended Squid format
  Working Log file - size : 102
                     age: 483497
  Archive Log file - we_accesslog_extsqu_3.1.18.8_20090522_074807       size: 10
2
 
   
Cached Content Log File Info
  Working Log file - size : 41
                     age: 483496
  Archive Log file - cache_content_3.1.18.8_20090522_074807     size: 41
 
   
Flash Media Streaming Access Transaction Log File Info
  Working Log file - size : 36
                     age: 482196
  Archive Log file - fms_access_3.1.18.8_20090522_062602        size: 650
  Archive Log file - fms_access_3.1.18.8_20090522_064309        size: 509
  Archive Log file - fms_access_3.1.18.8_20090522_065857        size: 650
  Archive Log file - fms_access_3.1.18.8_20090522_074807        size: 509
  Archive Log file - fms_access_3.1.18.8_20090522_080016        size: 509
  Archive Log file - fms_access_3.1.18.8_20090523_030830        size: 650
 
   
Flash Media Streaming Authorization Transaction Log File Info
  Working Log file - size : 43
                     age: 482196
  Archive Log file - fms_auth_3.1.18.8_20090522_062602  size: 4826
  Archive Log file - fms_auth_3.1.18.8_20090522_063036  size: 281
  Archive Log file - fms_auth_3.1.18.8_20090522_064309  size: 596
  Archive Log file - fms_auth_3.1.18.8_20090522_065857  size: 4789
  Archive Log file - fms_auth_3.1.18.8_20090522_070038  size: 277
  Archive Log file - fms_auth_3.1.18.8_20090522_074807  size: 596
  Archive Log file - fms_auth_3.1.18.8_20090523_030830  size: 4790
 
   
Authserver Transaction Log File Info
  Working Log file - size : 108
                     age: 483496
  Archive Log file - authsvr_3.1.18.8_20090522_065857   size: 108
ServiceEngine# 
 
   

The following example shows how to display information about the current configuration of transaction logging on an SR:

ServiceRouter# show transaction-logging
Transaction log configuration:
---------------------------------------
Logging is enabled.
Archive interval: 120 seconds
Maximum size of archive file: 2000000 KB
Maximum number of archive files: 50 files
 
   
Exporting files to ftp servers is enabled.
File compression is disabled.
Export interval: 1 minute
 
   
server               type  username        directory
10.74.115.12         sftp  xinwwang        /workspace/xinwwang/test
10.74.124.156        sftp  root            /root/test
10.74.124.157        sftp  root            /root/test
171.71.50.162        sftp  root            /test
 
   
 
   
 
   
Service Router Log File Info
  Working Log file - size : 96
                     age: 169813
  Archive Log file - service_router_3.1.14.70_20090421_222006   size: 256
  Archive Log file - service_router_3.1.14.70_20090422_020038   size: 223
  Archive Log file - service_router_3.1.14.70_20090422_210022   size: 351
  Archive Log file - service_router_3.1.14.70_20090423_020006   size: 1248
  Archive Log file - service_router_3.1.14.70_20090423_210021   size: 456
  Archive Log file - service_router_3.1.14.70_20090521_000218   size: 402
  Archive Log file - service_router_3.1.14.70_20090521_014815   size: 243
  Archive Log file - service_router_3.1.14.70_20090521_015020   size: 225
  Archive Log file - service_router_3.1.14.70_20090521_015227   size: 243
  Archive Log file - service_router_3.1.14.70_20090521_015417   size: 272
  Archive Log file - service_router_3.1.14.70_20090521_015601   size: 390
  Archive Log file - service_router_3.1.14.70_20090521_015816   size: 243
  Archive Log file - service_router_3.1.14.70_20090521_020033   size: 243
  Archive Log file - service_router_3.1.14.70_20090521_020249   size: 143
  Archive Log file - service_router_3.1.14.70_20090521_032633   size: 168
  Archive Log file - service_router_3.1.14.70_20090526_025027   size: 143
  Archive Log file - service_router_3.1.14.70_20090526_030002   size: 176
  Archive Log file - service_router_3.1.14.70_20090526_030226   size: 250
  Archive Log file - service_router_3.1.14.70_20090526_052206   size: 250
  Archive Log file - service_router_3.1.14.70_20090526_052413   size: 143
  Archive Log file - service_router_3.1.14.70_20090526_200213   size: 168
  Archive Log file - service_router_3.1.14.70_20090526_200413   size: 481
  Archive Log file - service_router_3.1.14.70_20090526_200645   size: 173
  Archive Log file - service_router_3.1.14.70_20090526_201010   size: 250

Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

show statistics transaction-logs

Displays the SE transaction log export statistics.

transaction-log force

Forces the archive or export of the transaction log.


show url-signature

To display the URL signature information, use the show url-signature command in EXEC configuration mode.

show url-signature

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

EXEC configuration mode.

Examples

The following example shows how to display the URL signature information:

ServiceEngine# show url-signature 
key-id-owner key-id-number key
-------------------------------
 
   

show user

To display the user identification number and username information for a particular user, use the show command in EXEC configuration mode.

show user {uid num | username name}

Syntax Description

uid

Displays the user's identification number.

num

Identification number. The range is from 0 to 65535.

username

Displays the name of user.

name

Name of the user.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

Table 0-18 describes the fields shown in the show user display.

Table 0-18 show user Field Descriptions

Field
Description

Uid

User ID number.

Username

Username.

Password

Login password. This field does not display the actual password.

Privilege

Privilege level of the user.

Configured in

Database in which the login authentication is configured.


Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

show users

Displays the specified users.

username

Establishes the username authentication.


show users

To display users, use the show users command in EXEC configuration mode.

show users administrative

Syntax Description

administrative

Lists users with administrative privileges.


Command Defaults

None

Command Modes

EXEC configuration mode.

Examples

The following example shows how to display the list of users with administrative privileges:

ServiceEngine# show users administrative
           UID USERNAME
           0 admin 
 
   

Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

show user

Displays the user identification number and username information for a particular user.

username

Establishes the username authentication.


show version

To display version information about the software, use the show version command in EXEC configuration mode.

show version pending

Syntax Description

pending

Displays the version for pending upgraded image.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

Table 0-19 describes the fields shown in the show version display.

Table 0-19 show version Field Descriptions 

Field
Description

Version

CDS software version.

Compiled hour:minute:second month day year by cnbuild

Compile information for the software build.

System was restarted on day of week month day hour:minute:second year

Date and time that the system was last restarted.

The system has been up for X hours, X minutes, X seconds

Length of time the system has been running since the last reboot.



Note If you update the CDS software on an SE, the new version displays in the show version pending command output, but it says, "Pending version will take effect after reload." You must reboot the device for the software update to take affect.


Examples

The follow example shows how to display the software version:

ServiceEngine# show version 
Content Delivery System Software (CDS)
Copyright (c) 1999-2011 by Cisco Systems, Inc.
Content Delivery System Software Release 3.0.0 (build b460 Aug 28 2011)
Version: cde220-2g2-DEVELOPMENT[vcn-build1:/auto/vcn-u1/cdsis_release_builds/cds
is_3.0.0-b460/spcdn]
 
   
Compiled 05:55:01 Aug 28 2011 by ipvbuild
Compile Time Options: KQ SS
 
   
System was restarted on Mon Aug 29 11:56:58 2011.
The system has been up for 1 day, 23 hours, 32 minutes, 15 seconds.
ServiceEngine#
 
   

The following example shows how to display the pending software version:

ServiceEngine# show version pending
Pending version is CDS 3.0.0-b360, built on 05:17:52 Jun 19 2011 by ipvbuild
It will take effect after reload
ServiceEngine#

Related Commands

Command
Description

show flash

Displays the flash memory version and usage information.


show web-engine

To display the Web Engine information, use the show web-engine command in EXEC configuration mode.

show web-engine {all | delivery-service-configuration | health}

Syntax Description

all

Displays all Web Engine-related caching configuration.

delivery-service-configuration

Displays the Delivery Service configuration information.

health

Displays the Web-engine health information.


Command Defaults

None

Command Modes

EXEC configuration mode.

Examples

The following example shows how to display the Web Engine information:

ServiceEngine# show web-engine all 
HTTP heuristic age-multipliers: 30%
 
   
Maximum time to live in days: 61
 
   
Minimum time to live in minutes: 60
 
   
Web-Engine Revalidation Disabled.
 
   
Web-Engine Cache Range Fill Enabled.
 
   
ServiceEngine#
 
   

The following example shows how to display the Web Engine health information:

ServiceEngine# show web-engine health 
 
   
WebEngine - Virtual memory Usage 
----------------------------------
Total memory usage                      :           1133268992 bytes [UnderLimit
]
Platform Virtual memory limit           :           3435973836 bytes
Glibc Caching Turn-Off Threshold        :           2061584301 bytes
Glibc memory Caching                    :                   ON
 
   
WebEngine - Alarm Status
-------------------------
memory_exceeded                         :                  OFF
max_session_exceeded                    :                  OFF
 
   

The following example shows how to display the Web Engine Delivery Service configuration:

ServiceEngine#
 
   
ServiceEngine# show web-engine delivery-service-configuration
 
   
Delivery Service Configuration
------------------------------------
Delivery Service Id 	: 355 
Delivery Service Rfqdn                      	: www.samreval.com 
Delivery Service Ofqdn                                      : 7.7.7.7 
Delivery Service Type                                       : Vod 
Delivery Service BitRate                                    : 5000 
Delivery Service Max tmpfs File Size                        : 2097152 
Delivery Service OutgoingCookie                             :  
Delivery Service Dscp                                       : 0 
Delivery Service Enable Download                            : Enabled 
Delivery Service Enable Streaming Extensions                :  
Delivery Service URL Hash Level for Cache Routing           : 0 
Delivery Service Enable Error Caching                       : Disabled 
Delivery Service Cacheable Error Responses                  :  
Delivery Service Content Flow Trace                         : Disabled 
Delivery Service Filter Trace Flow                          : Disabled 
Delivery Service Disable Small File Caching on Disk         : Disabled 
Delivery Service Response Read Timeout 	:15 sec
ServiceEngine#

Related Commands

Command
Description

web-engine (EXEC)

Configures the Web Engine module.

web-engine (Global configuration)

Configures the Web Engine caching parameters.

show statistics web-engine

Displays the Web Engine statistics.


show wmt

To display Windows Media Technologies (WMT) bandwidth and proxy mode configuration, use the show wmt command in EXEC configuration mode.

show wmt [bandwidth [incoming bypass-list] | detail | diagnostics {header-info {stream-file word | nsc-file .nsc_filename} | network-trace filename} http allow extension | proxy]

Syntax Description

bandwidth

(Optional) Displays WMT bandwidth settings.

incoming

(Optional) Displays WMT incoming bandwidth settings.

bypass-list

Displays the WMT incoming bandwidth bypass list.

broadcast

(Optional) Displays the WMT broadcast configuration.

detail

(Optional) Displays the detailed WMT configuration.

diagnostics

(Optional) Displays a set of WMT diagnostics tools.

header-info

Displays the file header information.

stream-file

Displays the headers of a Windows Media file.

word

An .asf, .wma, .wmv URL, or local file.

nsc-file

Displays the .nsc file headers.

.nsc_filename

Name of a local or remote WMT station.

network-trace

Displays WMT diagnostics information.

filename

Name of a local tcpdump file.

http

(Optional) Displays HTTP configurations.

allow

Displays the HTTP filename extensions allowed to be served using WMT.

extension

(Optional) Displays the list of HTTP filename extensions to be served using WMT.

proxy

(Optional) Displays proxy mode configuration.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

You can access the following three WMT diagnostic tools through the SE CLI:

asfhead—Examine the headers of a Windows Media file (for example, an .asf, .wmv, or .wma file). To access the asfhead tool, enter the show wmt diagnostics header-info stream-file word command.

nschead—Examine the .nsc file headers. To access the nschead tool, enter the show wmt diagnostics header-info nsc-file .ncs-filename command.

mmsdig—Use this text-based tool to decode the Multimedia Messaging Service (MMS) protocol (a binary protocol) that is captured in tcpdump traces (or any standard network trace output). To access this tool, enter the show wmt diagnostics network trace word command.

The mmsdig tool does not currently support decoding for RTSP, RTP, and RTCP.

Examples

The following example shows sample output of the show wmt diagnostics header-info stream-file command. In this example, this command is used to display the headers of a .wmv file named 256.wmv.

ServiceEngine#  show wmt diagnostics header-info stream-file 256.wmv
Start dumping ASF header objects...
 
Obj: ASF_Header_Object (size 30)
        Header Len: 5342
        Header Num Of Objs: 8
Obj: ASF_File_Properties_Object (size 104)
        file_size: 429275084
        creation_time: 128208475755620000
        packet_count: 53656
        play_duration: 36050290000
        send_duration: 35992950000
        preroll: 5000
        flags: 2
        min_pktsize: 8000
        max_pktsize: 8000
        min_bitrate: 1003200
Obj: ASF_Stream_Properties_Object (size 114)
        time_offset: 0
        stream_type: ASF_Audio_Media
        ecc_type: ASF_Audio_Spread
        type_data_len: 28
        ecc_data_len: 8
        flags: 0x0001 (stream # : 1)
        ASF type specific data: --------
        id_tag: 161             num_channels: 2
        sample_per_sec: 48000   bytes_per_sec: 15875
        block_align: 2032       bits_per_sample: 16
        codec_data(size: 10):
        0x00 0x88 0x00 0x00 0x0f 0x00 0xf0 0x07
        0x00 0x00
        ASF Ecc data: --------
        span: 1
        packet_len: 2032        chunk_len: 2032
        silence_data (1 bytes): 0x00
Obj: ASF_Stream_Properties_Object (size 133)
        time_offset: 0
        stream_type: ASF_Video_Media
        ecc_type: ASF_No_Error_Correction
        type_data_len: 55
        ecc_data_len: 0
        flags: 0x0002 (stream # : 2)
        ASF type specific data: --------
        image_width: 320        image_height: 240
        flags: 2                data_size: 44
        width: 320              height: 240
        bits_per_pixel: 24      compression_id: 861293911
        data_size: 44           image_size: 0
        h_pixels_per_meter: 0   v_pixels_per_meter: 0
        color_count: 0          important_color_count: 0
        codec_data (4 bytes):   0x4e 0xd9 0x1a 0x01
Obj: ASF_Extended_Content_Description_Object (size 208)
Obj: ASF_Content_Description_Object (size 42)
        title:
        author:
        copyright:
        description:
        rating:
Obj: ASF_Stream_Bitrate_Properties_Object (size 38)
        bitrate record count: 2
        # 0: flags = 0x0001, bitrate = 129550
        # 1: flags = 0x0002, bitrate = 873650
Obj: ASF_Codec_List_Object (size 252)
        codec_list_entry count: 2
        entry # 0:
        name = Windows Media Audio 9.1
        description = 127 kbps, 48 kHz, stereo Low Delay 1-pass CBR
        0x61 0x01
        entry # 1:
        name = Windows Media Video 9
        description =
        0x57 0x4d 0x56 0x33
Obj: ASF_Header_Extension_Object (size 4421)
Obj: ASF_Language_List_Object (size 39)
Obj: ASF_Extended_Stream_Properties_Object (size 88)
Obj: ASF_Extended_Stream_Properties_Object (size 110)
Obj: ASF_Compatibility_Object (size 26)
Obj: ASF_Metadata_Object (size 224)
Obj: ASF_Padding_Object (size 3850)
Obj: ASF_GUID_Invalid/Unknown_Object (size 38)
        0x20 0xde 0xaa 0xd9 0x17 0x7c 0x9c 0x4f
        0xbc 0x28 0x85 0x55 0xdd 0x98 0xe2 0xa2
Obj: ASF_Data_Object (size 50)
        data_size: 429248050
        packet_count: 53656
 
   

The following example shows an excerpt of sample output from the show wmt diagnostics header-info nsc-file command. In this example, this command is used to display the headers of the .nsc file named live1.nsc:

ServiceEngine#  show wmt diagnostics header-info nsc-file live1.nsc
Press Ctrl-C to abort, if no information is shown within 30 secs.
 
   
========Dumping NSC file - live1.nsc========
 
        [ Address ] 
        Name=(null)
        NSC Format Version=3.0
        Multicast Adapter=(null)
        IP Address=224.2.2.3
        IP Port=96
        Time To Live=15
        Default Ecc=10
        Log URL=http://kinslive.spcdn.net/live1.nsclog
        Unicast URL=rtsp://kinslive.spcdn.net/live1
        Allow Splitting=1
        Allow Caching=1
        Cache Expiration Time=86400
        [ Formats ] 
        Format1= [ Binary data skipped ] , len = 5316, key = 1111
 
--------Now trying to dump ASF header(0)--------
 
Obj: ASF_Header_Object (size 30)
        Header Len: 5266
        Header Num Of Objs: 8
Obj: ASF_File_Properties_Object (size 104)
        file_size: 5268
        creation_time: 128880472543590000
        packet_count: 4294967295
        play_duration: 0
        send_duration: 0
        preroll: 5000
        flags: 9
        min_pktsize: 8000
        max_pktsize: 8000
        min_bitrate: 1003200
Obj: ASF_Stream_Properties_Object (size 114)
        time_offset: 0
        stream_type: ASF_Audio_Media
        ecc_type: ASF_Audio_Spread
        type_data_len: 28
        ecc_data_len: 8
        flags: 0x0001 (stream # : 1)
        ASF type specific data: --------
        id_tag: 161             num_channels: 2
        sample_per_sec: 48000   bytes_per_sec: 15875
        block_align: 2032       bits_per_sample: 16
        codec_data(size: 10):
        0x00 0x88 0x00 0x00 0x0f 0x00 0xf0 0x07
        0x00 0x00
        ASF Ecc data: --------
        span: 1
        packet_len: 2032        chunk_len: 2032
        silence_data (1 bytes): 0x00
Obj: ASF_Stream_Properties_Object (size 133)
        time_offset: 0
        stream_type: ASF_Video_Media
        ecc_type: ASF_No_Error_Correction
        type_data_len: 55
        ecc_data_len: 0
        flags: 0x0002 (stream # : 2)
        ASF type specific data: --------
        image_width: 320        image_height: 240
        flags: 2                data_size: 44
        width: 320              height: 240
        bits_per_pixel: 24      compression_id: 861293911
        data_size: 44           image_size: 0
        h_pixels_per_meter: 0   v_pixels_per_meter: 0
        color_count: 0          important_color_count: 0
        codec_data (4 bytes):   0x4e 0xd9 0x1a 0x01
Obj: ASF_Stream_Bitrate_Properties_Object (size 38)
        bitrate record count: 2
        # 0: flags = 0x0001, bitrate = 129550
        # 1: flags = 0x0002, bitrate = 873650
Obj: ASF_Extended_Content_Description_Object (size 164)
Obj: ASF_Codec_List_Object (size 252)
        codec_list_entry count: 2
        entry # 0:
        name = Windows Media Audio 9.1
        description = 127 kbps, 48 kHz, stereo Low Delay 1-pass CBR
        0x61 0x01
        entry # 1:
        name = Windows Media Video 9
        description =
        0x57 0x4d 0x56 0x33
Obj: ASF_Error_Correction_Object (size 48)
        ecc type: ASF_Error_Correction_Default
        data_len: 4
        ecc span: 10
Obj: ASF_Header_Extension_Object (size 4383)
Obj: ASF_Language_List_Object (size 39)
Obj: ASF_Extended_Stream_Properties_Object (size 88)
Obj: ASF_Extended_Stream_Properties_Object (size 110)
Obj: ASF_Compatibility_Object (size 26)
Obj: ASF_Metadata_Object (size 224)
Obj: ASF_Padding_Object (size 3850)
Obj: ASF_Data_Object (size 50)
        data_size: 50
        packet_count: 0
 
   

Some of the fields are common between the command output from the show wmt diagnostics header-info stream-file and show wmt diagnostics header-info nsc-file commands.

The following example shows the WMT server configurations, the WMT HTTP configurations, and the WMT proxy configurations for the SE. The output of the show wmt and show wmt detail commands is identical.

ServiceEngine# show wmt
--------- WMT Server Configurations -----------------
WMT is enabled
WMT disallowed client protocols: http
WMT bandwidth platform limit: 2000000 Kbits/sec
WMT outgoing bandwidth configured is 2000000 Kbits/sec
WMT incoming bandwidth configured is 2000000 Kbits/sec
WMT max sessions configured: 400 
WMT max sessions platform limit: 14000 
WMT max sessions enforced: 400 sessions
WMT max outgoing bit rate allowed per stream has no limit
WMT max incoming bit rate allowed per stream has no limit
WMT cache is enabled
WMT cache max-obj-size: 10000 MB
WMT cache revalidate for each request is enabled
WMT cache age-multiplier: 100%
WMT cache min-ttl: 75 minutes
WMT cache max-ttl: 7 days
WMT debug client ip not set
WMT debug server ip not set
WMT accelerate live-split is enabled
WMT accelerate proxy-cache is enabled
WMT accelerate VOD is enabled
WMT fast-start is enabled
WMT fast-start max. bandwidth per player is 65535 (Kbps)
WMT fast-cache is enabled
WMT fast-cache acceleration factor is 65535
WMT maximum data packet MTU (TCP) enforced is 1472 bytes
WMT maximum data packet MTU (UDP) is 16000 bytes
WMT client idle timeout is 300 seconds
WMT forward logs is enabled
WMT server inactivity-timeout is 65535
WMT Transaction Log format is Windows Media Services 9.0 logging and SE specific
 information
RTSP Gateway incoming port 554 
 
   
--------- WMT HTTP Configurations -------------------
WMT http extensions allowed: 
asf none nsc wma wmv nsclog 
 
   
--------- WMT Proxy Configurations ------------------
Outgoing Proxy-Mode:
--------------------
MMS-over-HTTP Proxy-Mode:
  is not configured.
RTSP Proxy-Mode:
  is configured: 2.2.23.19:86
ServiceEngine# 
 
   

The following example shows how to display the WMT bandwidth settings configured on an SE:

ServiceEngine# show wmt bandwidth
Outgoing bandwidth configured 2000000 kbps
Incoming bandwidth configured 2000000 kbps
Incoming bandwidth configured 50000 kbps

Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

show statistics wmt

Displays the SE WMT statistics.

wmt

Configures the WMT.


shutdown (interface configuration)

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

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Command Defaults

None

Command Modes

Interface configuration (config-if) mode.

Usage Guidelines

See the "interface" section for alternative mechanism.

Examples

The following example shows how to shut down an interface configured on an SE:

ServiceEngine(config-if)# shutdown
 
   

Related Commands

Command
Description

interface

Configures a Gigabit Ethernet or port channel interface.

show interface

Displays the hardware interface information.

show running-config

Displays the current operating configuration.

show startup-config

Displays the startup configuration.


shutdown (EXEC)

To shut down the Service Engine (SE), Service Router (SR), or Content Delivery System Manager (CDSM), use the shutdown command in EXEC configuration mode.

shutdown [poweroff]

Syntax Description

poweroff

(Optional) Turns off the power after closing all applications and the operating system.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

A controlled shutdown refers to the process of properly shutting down an SE without turning off the power on the device. With a controlled shutdown, all the application activities and the operating system are properly stopped on an SE but the power is still on. Controlled shutdowns of an SE can help you minimize the downtime when the SE is being serviced.

The shutdown command enables you to shut down and optionally power off an SE:

Shutdown means that all application activities (applications and operating system) are stopped, but the power is still on. This shutdown is similar to the Linux halt command.

Shutdown poweroff means that the SE is powered down by the Internet Streamer CDS software after being shut down. This operation is also referred to as a software poweroff. The implementation of the shutdown poweroff feature uses the Advanced Configuration and Power Interface (ACPI) power management interface.


Caution If you do not perform a controlled shutdown, the SE file system can be corrupted. It also takes longer to reboot the SE if the SE is not properly shut down.


Note You cannot power on SEs again through software after a software poweroff operation. You must press the power button once on these SEs to bring these SEs back online.


The shutdown command facilitates a proper shutdown for SEs, SRs, or CDSMs. Where the shutdown command is supported on all content networking hardware models, the shutdown poweroff command is supported only on those models that support ACPI.

The shutdown command closes all applications and stops all system activities but keeps the power on. The fans continue to run and the power LED is on, indicating that the device is still powered on. When you enter the shutdown command, you are prompted to save your configuration changes, if any. The device console displays a menu after the shutdown process is completed. You need to log in to the SE using a console to display the following menu:

ServiceEngine# shutdown
System configuration has been modified. Save? [ yes ] :yes
Device can not be powered on again through software after shutdown.
Proceed with shutdown? [ confirm ] yes
Shutting down all services, will timeout in 15 minutes.
shutdown in progress ..Halt requested by CLI@ttyS0.
..........
Shutdown success
 
   
Cisco Service Engine Console
 
   
Username: admin
Password:
 
   
================= SHUTDOWN SHELL =================
   System has been shut down.
 
   
   You can either
      Power down system by pressing and holding power button
   or
   1. Reload system through software
   2. Power down system through software
   Please select [ 1-2 ] :
 
   

The shutdown poweroff command closes all applications and the operating system, stops all system activities, and turns off the power. The fans stop running and the power LED starts flashing, indicating that the device has been powered off.


Note If you use the shutdown or shutdown poweroff commands, the device does not perform a file system check when you power on and boot the device the next time.


Table 0-20 describes the shutdown and shutdown power-off operations for SEs.

Table 0-20 Shutting Down Content Engines Through CLI Commands 

Activity
All Content Engine Models
Content Engines with Power Management Capability

User performs a
shutdown operation on
the SE

ServiceEngine#  shutdown
ServiceEngine#  shutdown 
poweroff 

User intervention to
bring SE
back online

To bring an SE that has an on/off switch on the back online after a shutdown operation, flip the on/off switch twice.

To bring an SE that has a power button (instead of an on/off switch on the back) back online after a shutdown operation, first press and hold the power button for several seconds to power off these models, and then press the power button once again.

After a shutdown poweroff, press the power button once to bring the SE back online.

File system check

Is not performed after you turn the power on again and reboot the SE.

Is not performed after you turn the power on again and reboot the SE.


You can enter the shutdown command from a console session or from a remote session (Telnet or SSH Version 1 or SSH Version 2) to perform a shutdown on an SE.

To perform a shutdown on an SE, enter the shutdown command as follows:

ServiceEngine#  shutdown
 
   

When you are asked if you want to save the system configuration, enter yes as follows:

System configuration has been modified. Save? [ yes ] :yes
 
   

When you are asked if you want to proceed with the shutdown, press Enter to proceed with the shutdown operation as follows:

Device can not be powered on again through software after shutdown.
Proceed with shutdown? [ confirm ] 
 
   

The following message appears, reporting that all services are being shut down on this SE:

Shutting down all services, will timeout in 15 minutes.
shutdown in progress ..System halted.

 
   

After the system is shut down (the system has halted), an Internet Streamer CDS software shutdown shell displays the current state of the system (for example, System has been shut down) on the console. You are asked whether you want to perform a software power off (the Power down system by software option), or if you want to reload the system through the software.

================= SHUTDOWN SHELL =================
System has been shut down.

Table 0-21 show statistics wmt all Field Descriptions 

Field
Description

Unicast Requests Statistics

Total unicast requests received

Total number of unicast requests received.

Display shows the number of requests in each category and calculates the percentage of the total for each category.

Streaming Requests served

Number of streaming requests received.

Multicast nsc file Request

Number of multicast NSC file requests received.

Authenticate Requests

Number of authenticated requests received.

Requests error

Number of request errors received.

By Type of Content

Live content

Number of live content requests received.

On-Demand Content

Number of on-demand content requests received.

By Transport Protocol

HTTP

Number of HTTP requests received.

RTSPT

Number of RTSPT requests received.

RTSPU

Number of RTSPU requests received.

Unicast Savings Statistics

Total bytes saved

Total number of bytes saved.

By Source of Content

Local

Number of local bytes saved.

Remote HTTP

Number of remote HTTP bytes saved.

Remote RTSP

Number of remote RTSP bytes saved.

Multicast

Number of multicast bytes saved.

CDN-Related WMT Requests

CDN Content Hits

Number of CDN content request hits.

CDN Content Misses

Number of CDN content request misses.

CDN Content Live

Number of CDN live content requests.

CDN Content Errors

Number of CDN content request errors.

Fast Streaming-related WMT Requests

Normal Speed

Number of normal-speed Fast Streaming-related WMT requests.

Fast Start Only

Number of Fast Start WMT requests.

Fast Cache Only

Number of Fast Cache WMT requests.

Fast Start and Fast Cache

Number of Fast Start and Fast Cache WMT requests.

Authenticated Requests

By Type of Authentication

Negotiate

Number of negotiated authentication authenticated requests.

Digest

Number of digest authentication authenticated requests.

Basic

Number of basic authentication authenticated requests.

Unicast Bytes Statistics

Total unicast incoming bytes

Total number of bytes incoming as unicast streams.

By Type of Content

Live content

Number of bytes incoming as unicast streams for live content.

On-Demand Content

Number of bytes incoming as unicast streams for on-demand content.

By Transport Protocol

HTTP

Number of bytes incoming as unicast streams using the HTTP transport protocol.

RTSPT

Number of bytes incoming as unicast streams using the RTSPT transport protocol.

Total unicast outgoing bytes

Total number of bytes outgoing as unicast streams.

Unicast Savings Statistics

Total bytes saved

Total number of bytes saved.

By prepositioned content

Number of bytes saved for prepositioned content.

By live-splitting

Number of bytes saved for live-splitting content.

By cache-hit

Number of bytes saved for cached content.

Live Splitting

Incoming bytes

Number of bytes incoming as live-split streams.

Outgoing bytes

Number of bytes outgoing as live-split streams.

Bytes saved

Number of bytes saved.

Caching

Bytes cache incoming

Number of bytes incoming for the cache.

Bytes cache outgoing

Number of bytes outgoing from the cache.

Bytes cache total

Total number of bytes cached.

Bytes cache-bypassed

Number of bytes that bypassed the cache.

Cacheable requests

Number of cacheable requests.

Req cache-miss

Number of cacheable requests that were cache misses.

Req cache-hit

Number of cacheable requests that were cache hits.

Req cache-partial-hit

Number of cacheable requests that were partial cache hits.

Req cache-total

Total number of requests that were cached.

Objects not cached

Number of objects that were not cached.

Cache bypassed

Number of objects that were not cached because they bypassed the cache.

Exceed max-size

Number of objects that were not cached because they exceeded the maximum cacheable size limit.

Usage Summary

Concurrent Unicast Client Sessions

Total number of concurrent unicast client sessions.

Current

Number of concurrent unicast client sessions currently running.

Max

Maximum number of concurrent unicast client sessions recorded.

Concurrent Remote Server Sessions

Total number of concurrent remote server sessions.

Concurrent Active Multicast Sessions

Total number of concurrent active multicast sessions.

Concurrent Unicast Bandwidth (Kbps)

Total amount of bandwidth being used (in kilobits per second) for concurrent unicast sessions.

Concurrent Bandwidth to Remote Servers (Kbps)

Total amount of bandwidth being used (in kilobits per second) for concurrent remote server sessions.

Concurrent Multicast Out Bandwidth (Kbps)

Total amount of bandwidth being used (in kilobits per second) for concurrent multicast out sessions.

Error Statistics

Total request errors

Total number of request errors.

Errors generated by this box

Number of request errors generated by this device.

Errors generated by remote servers

Number of request errors generated by remote servers.

Other Statistics

Authentication Retries from Clients

Number of authentication retries from clients.

WMT Rule Template Statistics

URL Rewrite

Number of URL rewrites.

URL Redirect

Number of URL redirects.

URL Block

Number of blocked URLs.

No-Cache

Number of no-cache matches.

Allow

Number of allow matches.

Multicast Statistics

Total Multicast Outgoing Bytes

Total number of bytes outgoing as multicast-out streams.

Total Multicast Logging Requests

Total number of multicast logging requests.

Aggregate Multicast Out Bandwidth (Kbps)

Aggregated amount of bandwidth being used (in kilobits per second) for multicast out sessions.

Current

Number of concurrent multicast out sessions currently running.

Max

Maximum number of multicast out sessions recorded.

Number of Concurrent Active Multicast Sessions

Number of concurrent active multicast sessions.

You can either
   Power down system by pressing and holding power button
or
1. Reload system through software
2. Power down system through software
 
   

To power down the SE, press and hold the power button on the SE, or use one of the following methods to perform a shutdown poweroff:

From the console command line, enter 2 when prompted as follows:

================= SHUTDOWN SHELL =================
System has been shut down.
You can either
   Power down system by pressing and holding power button
or
1. Reload system through software
2. Power down system through software
 
   

From the SE CLI, enter the shutdown poweroff command as follows:

ServiceEngine#  shutdown poweroff 

When you are asked if you want to save the system configuration, enter yes as follows:

System configuration has been modified. Save? [ yes ] :yes
 
   

When you are asked to confirm your decision, press Enter.

Device can not be powered on again through software after poweroff.
Proceed with poweroff? [ confirm ] 
Shutting down all services, will timeout in 15 minutes.
poweroff in progress ..Power down.

Examples

The following example shows that the shutdown command is used to close all applications and stop all system activities:

ServiceEngine1# shutdown
System configuration has been modified. Save? [ yes ] :yes
Device can not be powered on again through software after shutdown.
Proceed with shutdown? [ confirm ] 
Shutting down all services, will timeout in 15 minutes.
shutdown in progress ..System halted.
 
   

The following example shows that the shutdown poweroff command is used to close all applications, stop all system activities, and then turn off power to the SE:

ServiceEngine2# shutdown poweroff
System configuration has been modified. Save? [ yes ] :yes
Device can not be powered on again through software after poweroff.
Proceed with poweroff? [ confirm ] 
Shutting down all services, will timeout in 15 minutes.
poweroff in progress ..Power down.
 
   

snmp-server community

To configure the community access string to permit access to the Simple Network Management Protocol (SNMP), use the snmp-server community command in Global configuration mode. To remove the specified community string, use the no form of this command.

snmp-server community community_string [group group_name | rw]

no snmp-server community community_string [group group_name | rw]

Syntax Description

community_string

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

group

(Optional) Specifies the group to which this community name belongs.

group_name

(Optional) Name of the group.

rw

(Optional) Specifies read-write access with this community string.


Command Defaults

An SNMP community string permits read-only access to all MIB objects.

A community string is assigned to the Secure Domain Router (SDR) owner.

Command Modes

Global configuration (config) mode.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. Use the snmp-server community command to configure the community access string to permit access to SNMP. To remove the specified community string, use the no form of this command.


Note In a non-owner SDR, a community name provides access only to the object instances that belong to that SDR, regardless of the access privilege assigned to the community name. Access to the owner SDR and system-wide access privileges are available only from the owner SDR.


Examples

The following example shows how to add the community comaccess:

ServiceEngine(config)# snmp-server community comaccess rw
 
   

The following example shows how to remove the community comaccess:

ServiceEngine(config)# no snmp-server community comaccess

Related Commands

Command
Description

snmp-server view

Defines a Version 2 SNMP (SNMPv2) MIB view.


snmp-server contact

To set the system server contact (sysContact) string, use the snmp-server contact command in Global configuration mode. To remove the system contact information, use the no form of this command.

snmp-server contact line

no snmp-server contact

Syntax Description

line

Identification of the contact person for this managed node.


Command Defaults

No system contact string is set.

Command Modes

Global configuration (config) mode.

Usage Guidelines

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

Examples

The following example shows how to configure a system contact string:

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

The following example shows how to reset the system contact string:

ServiceEngine(config)# no snmp-server contact

Related Commands

Command
Description

show snmp

Displays the SNMP parameters.

snmp-server community

Configures the community access string to permit access to the SNMP.

snmp-server enable traps

Enables the SE to send SNMP traps.

snmp-server group

Defines a user security model group.

snmp-server host

Specifies the hosts to receive SNMP traps.

snmp-server location

Sets the SNMP system location string.

snmp-server notify inform

Configures the SNMP notify inform request.

snmp-server user

Defines a user who can access the SNMP engine.

snmp-server view

Defines a SNMPv2 MIB view.


snmp-server enable traps

To enable the SE to send SNMP traps, use the snmp-server enable traps command in Global configuration mode. To disable all SNMP traps or only SNMP authentication traps, use the no form of this command.

snmp-server enable traps [alarm [clear-critical | clear-major | clear-minor | raise-critical | raise-major | raise-minor] | config | entity | event | service-engine [disk-fail | disk-read | disk-write | transaction-log] | snmp [authentication | cold-start]]

no snmp-server enable traps [alarm [clear-critical | clear-major | clear-minor | raise-critical | raise-major | raise-minor] | config | entity | event | service-engine [disk-fail | disk-read | disk-write | transaction-log] | snmp [authentication | cold-start]]

Syntax Description

alarm

(Optional) Enables SE alarm traps.

clear-critical

(Optional) Enables the clear-critical alarm trap.

clear-major

(Optional) Enables the clear-major alarm trap.

clear-minor

(Optional) Enables the clear-minor alarm trap.

raise-critical

(Optional) Enables the raise-critical alarm trap.

raise-major

(Optional) Enables the raise-major alarm trap.

raise-minor

(Optional) Enables the raise-minor alarm trap.

config

(Optional) Enables CiscoConfigManEvent traps.

entity

(Optional) Enables SNMP entity traps.

event

(Optional) Enables Event MIB traps.

service-engine

(Optional) Enables SNMP SE traps.

disk-fail

(Optional) Enables the disk failure error trap.

disk-read

(Optional) Enables the disk read error trap.

disk-write

(Optional) Enables the disk write error trap.

transaction-log

(Optional) Enables the transaction log write error trap.

snmp

(Optional) Enables SNMP-specific traps.

authentication

(Optional) Enables the authentication trap.

cold-start

(Optional) Enables the cold-start trap.


Command Defaults

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

Command Modes

Global configuration (config) mode.

Usage Guidelines

You can configure an SE to generate an SNMP trap for a specific alarm condition. You can configure the generation of SNMP alarm traps on SEs based on the following:

Severity of the alarm (critical, major, or minor)

Action (the alarm is raised or cleared)

Cisco Internet Streamer CDS software supports six generic alarm traps. These six generic alarm traps provide SNMP and Node Health Manager integration. Each trap can be enabled or disabled through the SE CLI.


Note Some SNMP traps are different between v1 and v2 and v3 when configure the trap.


SNMP notifications can be sent as traps or inform requests. The snmp-server enable traps command enables both traps and inform requests for the specified notification types.

To configure traps, enter the snmp-server enable traps command. If you do not enter the snmp-server enable traps command, no traps are sent.

If you do not enter an snmp-server enable traps command, no notifications controlled by this command are sent. To configure the SE to send these SNMP notifications, enter at least one snmp-server enable traps command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled. To enable multiple types of notifications, enter a separate snmp-server enable traps command for each notification type and notification option.

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

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

In addition, enable SNMP with the snmp-server community command.

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

Examples

The following example shows how to enable the SE to send all traps to the host 172.31.2.160 using the community string public:

ServiceEngine(config)# snmp-server enable traps
ServiceEngine(config)# snmp-server host 172.31.2.160 public
 
   

The following example disables all traps:

ServiceEngine(config)# no snmp-server enable traps

Related Commands

Command
Description

show snmp

Displays the SNMP parameters.

snmp-server community

Configures the community access string to permit access to the SNMP.

snmp-server contact

Sets the system server contact string.

snmp-server group

Defines a user security model group.

snmp-server host

Specifies the hosts to receive SNMP traps.

snmp-server location

Sets the SNMP system location string.

snmp-server notify inform

Configures the SNMP notify inform request.

snmp-server user

Defines a user who can access the SNMP engine.

snmp-server view

Defines a SNMPv2 MIB view.


snmp-server group

To define a user security model group, use the snmp-server group command in Global configuration mode. To remove the specified group, use the no form of this command.

snmp-server group name {v1 [notify name] [read name] [write name] | v2c [notify name] [read name] [write name] | v3 {auth [notify name] [read name] [write name] | noauth [notify name] [read name] [write name] | priv [notify name] [read name] [write name]}}

no snmp-server group name {v1 [notify name] [read name] [write name] | v2c [notify name] [read name] [write name] | v3 {auth [notify name] [read name] [write name] | noauth [notify name] [read name] [write name] | priv [notify name] [read name] [write name]}}

Syntax Description

name

Name of the SNMP group. Supports up to a maximum of 64 characters.

v1

Specifies the group using the Version 1 Security Model.

notify

(Optional) Specifies a notify view for the group that enables you to specify a notify, inform, or trap.

name

Notify view name. Supports up to a maximum of 64 characters.

read

(Optional) Specifies a read view for the group that enables you only to view the contents of the agent.

name

Read view name. Supports up to a maximum of 64 characters.

write

(Optional) Specifies a write view for the group that enables you to enter data and configure the contents of the agent.

name

Write view name. Supports up to a maximum of 64 characters.

v2c

Specifies the group using the Version 2c Security Model.

v3

Specifies the group using the User Security Model (SNMPv3).

auth

Specifies the group using the AuthNoPriv Security Level.

noauth

Specifies the group using the noAuthNoPriv Security Level.

priv

Specifies the group using the AuthPriv Security Level.


Command Defaults

The default is that no user security model group is defined.

Command Modes

Global configuration (config) mode.

Usage Guidelines

The maximum number of SNMP groups that can be created is 10.

Select one of three SNMP security model groups: Version 1 (v1) Security Model, Version 2c (v2c) Security Model, or the User Security Model (v3 or SNMPv3). Optionally, you then specify a notify, read, or write view for the group for the particular security model chosen. The v3 option allows you to specify the group using one of three security levels: auth (AuthNoPriv Security Level), noauth (noAuthNoPriv Security Level), or priv (AuthPriv Security Level).


Note Each community is associated with a group. Each group has a view and users are assigned to a group. If the group does not have a view associated with it, then users associated that group cannot access any MIB entry.


The Cisco Internet Streamer CDS software supports the following versions of SNMP:

Version 1 (SNMPv1)—This version is the initial implementation of SNMP. See RFC 1157 for a full description of its functionality.

Version 2 (SNMPv2c)—This version is the second release of SNMP, described in RFC 1902. It provides additions to data types, counter size, and protocol operations.

Version 3 (SNMPv3)—This version is the most recent SNMP version, defined in RFC 2271 through RFC 2275.

SNMP Security Models and Security Levels

SNMPv1 and SNMPv2c do not have any security (authentication or privacy) mechanisms to keep SNMP packet traffic on the wire confidential. As a result, packets on the wire can be detected and SNMP community strings can be compromised.

To solve the security shortcomings of SNMPv1 and SNMPv2c, SNMPv3 provides secure access to SEs by authenticating and encrypting packets over the network. The SNMP agent supports SNMPv3, SNMPv1, and SNMPv2c.

Using SNMPv3, users can securely collect management information from their SNMP agents. Also, confidential information, such as SNMP set packets that change an SE's configuration, can be encrypted to prevent their contents from being exposed on the wire. Also, the group-based administrative model allows different users to access the same SNMP agent with varying access privileges.

Examples

The following example shows how to configure the SNMP group name, security model, and notify view on the SE:

ServiceEngine(config)# snmp-server group acme v1 notify mymib
 
   

Related Commands

Command
Description

show snmp

Displays the SNMP parameters.

snmp-server community

Configures the community access string to permit access to the SNMP.

snmp-server contact

Sets the system server contact string.

snmp-server enable traps

Enables the SE to send SNMP traps.

snmp-server host

Specifies the hosts to receive SNMP traps.

snmp-server location

Sets the SNMP system location string.

snmp-server notify inform

Configures the SNMP notify inform request.

snmp-server user

Defines a user who can access the SNMP engine.

snmp-server view

Defines a SNMPv2 MIB view.


snmp-server host

To specify the recipient of a host SNMP trap operation, use the snmp-server host command in Global configuration mode. To remove the specified host, use the no form of this command.

snmp-server host {hostname | ip_address} communitystring [v2c [retry number] [timeout seconds]   | [v3 {auth [retry number] [timeout seconds] | noauth [retry number] [timeout seconds] | priv [retry number] [timeout seconds]}]

no snmp-server host {hostname | ip_address} [v2c [retry number] [timeout seconds]   | [v3 {auth [retry number] [timeout seconds] | noauth [retry number] [timeout seconds] | priv [retry number] [timeout seconds]} | communitystring]

Syntax Description

hostname

Hostname of the SNMP trap host that is sent in the SNMP trap messages from the SE.

ip_address

IP address of the SNMP trap host that is sent in the SNMP trap messages from the SE.

communitystring

Password-like community string sent in the SNMP trap messages from the SE. You can enter a maximum of 64 characters.

v2c

(Optional) Specifies the Version 2c Security Model.

retry

(Optional) Sets the count for the number of retries for the inform request. (The default is 2 tries.)

number

Number of retries for the inform request. The range is from 1 to 10.

timeout

(Optional) Sets the timeout for the inform request The default is 15 seconds.

seconds

Timeout value, in seconds. The range is from 1 to 1000.

v3

(Optional) Specifies the User Security Model (SNMPv3).

auth

Sends notification using the AuthNoPriv Security Level.

noauth

Sends notification using the noAuthNoPriv Security Level.

priv

Sends notification using the AuthPriv Security Level.


Command Defaults

This command is disabled by default. No traps are sent. The version of the SNMP protocol used to send the traps is SNMP Version 1.

retry number: 2

timeout seconds: 15

Command Modes

Global configuration (config) mode.

Usage Guidelines

SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver does not send acknowledgments when it receives traps. The sender cannot determine if the traps were received. However, an SNMP entity that receives an inform request acknowledges the message with an SNMP response protocol data unit (PDU). If the sender never receives the response, the inform request can be sent again. Informs are more likely to reach their intended destination.

However, informs consume more resources in the agent and in the network. Unlike a trap, which is discarded as soon as it is sent, an inform request must be held in the memory until a response is received or the request times out. Also, traps are sent only once, while an inform may be retried several times. The retries increase traffic and contribute to a higher overhead on the network.


Note When entering the snmp-server host command, a valid host name must be provided or you receive an error.


If you do not enter an snmp-server host command, no notifications are sent. To configure the SE to send SNMP notifications, enter at least one snmp-server host command. To enable multiple hosts, enter a separate snmp-server host command for each host. You can specify multiple notification types in the command for each host.

When multiple snmp-server host commands are given for the same host and kind of security model, each succeeding command overwrites the previous command. Only the last snmp-server host command is in effect. For example, if you enter an snmp-server host v2c command for a host and then enter another snmp-server host v3 command for the same host, the second command replaces the first.

The maximum number of SNMP hosts that can be created by entering the snmp-server host commands is eight.

When multiple snmp-server host commands are given for the same host, the community string in the last command is used.

The snmp-server host command is used with the snmp-server enable traps command. Use the snmp-server enable traps command to specify which SNMP notifications are sent globally. For a host to receive most notifications, at least one snmp-server enable traps command and the snmp-server host command for that host must be enabled.


Note You must enable SNMP with the snmp-server community command.


Examples

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

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

The following example shows how to remove the host 172.16.2.160 from the SNMP trap recipient list:

ServiceEngine(config)# no snmp-server host 172.16.2.160
 
   

Related Commands

Command
Description

show snmp

Displays the SNMP parameters.

snmp-server community

Configures the community access string to permit access to the SNMP.

snmp-server contact

Sets the system server contact string.

snmp-server enable traps

Enables the SE to send SNMP traps.

snmp-server group

Defines a user security model group.

snmp-server location

Sets the SNMP system location string

snmp-server notify inform

Configures the SNMP notify inform request.

snmp-server user

Defines a user who can access the SNMP engine.

snmp-server view

Defines a SNMPv2 MIB view.


snmp-server location

To set the SNMP system location string, use the snmp-server location command in Global configuration mode. To remove the location string, use the no form of this command.

snmp-server location line

no snmp-server location

Syntax Description

line

String that describes the physical location of this node.


Command Defaults

No system location string is set.

Command Modes

Global configuration (config) mode.

Usage Guidelines

The system location string is the value stored in the MIB-II system group system location object. You can see the system location string with the show snmp command.

Examples

The following example shows how to configure a system location string:

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

Related Commands

Command
Description

show snmp

Displays the SNMP parameters.

snmp-server community

Configures the community access string to permit access to the SNMP.

snmp-server contact

Sets the system server contact string.

snmp-server enable traps

Enables the SE to send SNMP traps.

snmp-server group

Defines a user security model group.

snmp-server host

Specifies the hosts to receive SNMP traps.

snmp-server notify inform

Configures the SNMP notify inform request.

snmp-server user

Defines a user who can access the SNMP engine.

snmp-server view

Defines a SNMPv2 MIB view.


snmp-server notify inform

To configure the SNMP notify inform request, use the snmp-server notify inform command in Global configuration mode. To return the setting to the default value, use the no form of this command.

snmp-server notify inform

no snmp-server notify inform

Syntax Description

This command has no arguments or keywords.

Command Defaults

If you do not enter the snmp-server notify inform command, the default is an SNMP trap request.

Command Modes

Global configuration (config) mode.

Usage Guidelines

The snmp-server host command specifies which hosts receive informs. The snmp-server enable traps command globally enables the production mechanism for the specified notifications (traps and informs).

For a host to receive an inform, enable the inform globally by entering the snmp-server notify inform command.

The SNMP inform requests feature allows SEs to send inform requests to SNMP managers. SEs can send notifications to SNMP managers when particular events occur. For example, an agent SE might send a message to a manager when the agent SE experiences an error condition.

SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver does not send any acknowledgment when it receives a trap. The sender cannot determine if the trap was received. However, an SNMP manager that receives an inform request acknowledges the message with an SNMP response protocol data unit (PDU). If the manager does not receive an inform request, it does not send a response. If the sender never receives a response, the inform request can be sent again. Informs are more likely to reach their intended destination.

Because they are more reliable, informs consume more resources in the SE and in the network. Unlike a trap, which is discarded as soon as it is sent, an inform request must be held in the memory until a response is received or the request times out. Also, traps are sent only once, while an inform may be retried several times. The retries increase traffic and contribute to a higher overhead on the network. Traps and inform requests provide a trade-off between reliability and resources.


Tip If it is important that the SNMP manager receives every notification, then you should use inform requests in your network. If you are concerned about traffic on your network or about the memory in the SE and you do not need to receive every notification, then you should use traps in your network.


Examples

The following example shows how to configure the SNMP notify inform request on the SE:

ServiceEngine(config)# snmp-server notify inform
 
   

Related Commands

Command
Description

show snmp

Displays the SNMP parameters.

snmp-server community

Configures the community access string to permit access to the SNMP.

snmp-server contact

Sets the system server contact string.

snmp-server enable traps

Enables the SE to send SNMP traps.

snmp-server group

Defines a user security model group.

snmp-server host

Specifies the hosts to receive SNMP traps.

snmp-server location

Sets the SNMP system location string.

snmp-server user

Defines a user who can access the SNMP engine.

snmp-server view

Defines a SNMPv2 MIB view.


snmp-server user

To define a user who can access the SNMP server, use the snmp-server user command in Global configuration mode. To remove access, use the no form of this command.

snmp-server user name group [auth {md5 password [priv password] | sha password [priv password]} | remote octet_string [auth {md5 password [priv password] | sha password [priv password]}]]

no snmp-server user name group [auth {md5 password | sha password} [priv password] | remote octetstring [auth {md5 password | sha password} [priv password]]]

Syntax Description

name

Name of the SNMP user. Use letters, numbers, dashes, and underscores, but no blanks. This is the name of the user on the SNMP host who wants to communicate with the SNMP agent on the SE. You can enter a maximum of 64 characters.

group

Name of the group to which the SNMP user belongs. You can enter a maximum of 64 characters.

auth

(Optional) Configures user authentication parameters.

md5

Configures the Hashed-Based Message Authentication Code Message Digest 5 (HMAC MD5) authentication algorithm.

password

HMAC MD5 user authentication password.

priv

(Optional) Configures authentication parameters for the packet.

password

HMAC MD5 user private password. You can enter a maximum of 256 characters.

sha

Configures the HMAC Secure Hash Algorithm (SHA) authentication algorithm.

password

HMAC SHA authentication password. You can enter a maximum of 256 characters.

remote

(Optional) Specifies the engine identity of the remote SNMP entity to which the user belongs.

octet_string

Globally unique identifier for a remote SNMP entity (for example, the SNMP network management station) for at least one of the SNMP users.


Command Defaults

None

Command Modes

Global configuration (config) mode.

Usage Guidelines

The maximum number of SNMP users that can be created is 10. Follow these guidelines when defining SNMP users for SEs:

If SNMPv3 is going to be used for SNMP requests, define at least one SNMPv3 user account on the SE for the SE to be accessed through SNMP.

Group defined with the SNMPv1 or SNMPv2c security model should not be associated with SNMP users; they should only be associated with the community strings.


Tip To send an SNMPv3 inform message, you must configure at least one SNMPv3 user with a remote SNMP ID option on the SE. The SNMP ID is entered in octet string form. For example, if the IP address of a remote SNMP entity is 192.147.142.129, then the octet string would be 00:00:63:00:00:00:a1:c0:93:8e:81.


Examples

The following example shows that an SNMPv3 user account is created on the SE. The SNMPv3 user is named acme and belongs to the group named admin. Because this SNMP user account has been set up with no authentication password, the SNMP agent on the SE does not perform authentication on SNMP requests from this user.

ServiceEngine(config)#  snmp-server user acme admin
 
   

Related Commands

Command
Description

show snmp

Displays the SNMP parameters.

snmp-server community

Configures the community access string to permit access to the SNMP.

snmp-server contact

Sets the system server contact string.

snmp-server enable traps

Enables the SE to send SNMP traps.

snmp-server group

Defines a user security model group.

snmp-server host

Specifies the hosts to receive SNMP traps.

snmp-server location

Sets the SNMP system location string.

snmp-server notify inform

Configures the SNMP notify inform request.

snmp-server view

Defines a SNMPv2 MIB view.


snmp-server view

To define a SNMP Version 2 (SNMPv2) MIB view, use the snmp-server view command in Global configuration mode. To undefine the MIB view, use the no form of this command.

snmp-server view view_name MIB_family {excluded | included}

no snmp-server view view_name MIB_family {excluded | included}

Syntax Description

view_name

Name of this family of view subtrees. You can enter a maximum of 64 characters.

MIB_family

An object identifier that identifies a subtree of the MIB. You can enter a maximum of 64 characters.

excluded

Excludes the MIB family from the view.

included

Includes the MIB family from the view.


Command Defaults

None

Command Modes

Global configuration (config) mode.

Usage Guidelines

An SNMP view is a mapping between SNMP objects and the access rights available for those objects. An object can have different access rights in each view. Access rights indicate whether the object is accessible by either a community string or a user. The snmp-server view command is used with the snmp-server group to limit the read-write access of MIB trees based on the group. Because the group can be associated with the SNMP community string or users, using the snmp-server view command extends the limit to users and community strings. If the view is not configured, read-write access to the community string applies to the MIB tree and all users (SNMPv3).

The maximum number of views that can be created is 10. You can configure the SNMP view settings only if you have previously configured the SNMP server settings.

To remove a view record, use the no snmp-server view command.

You can enter the snmp-server view command multiple times for the same view record. Later lines take precedence when an object identifier is included in two or more lines.


Note When configuring an SNMP View with Excluded, the specified MIB that is excluded is not accessible for the community associated with the group that has that view.


Examples

The following example shows how to configure the view name, family name, and view type:

ServiceEngine(config)# snmp-server view contentview ciscoServiceEngineMIB included
 
   

The following example creates a view that includes all objects in the MIB-II system group and all objects in the Cisco enterprise MIB:

ServiceEngine(config)# snmp-server view phred system included
ServiceEngine(config)# snmp-server view phred cisco included
 
   

The following example shows how to create a view that includes all objects in the MIB-II system group except for sysServices (System 7) in the MIB-II interfaces group:

ServiceEngine(config)# snmp-server view agon system included
ServiceEngine(config)# snmp-server view agon system.7 excluded

Related Commands

Command
Description

show snmp

Displays the SNMP parameters.

snmp-server community

Configures the community access string to permit access to the SNMP.

snmp-server contact

Sets the system server contact string.

snmp-server enable traps

Enables the SE to send SNMP traps.

snmp-server group

Defines a user security model group.

snmp-server host

Specifies the hosts to receive SNMP traps.

snmp-server location

Sets the SNMP system location string.

snmp-server notify inform

Configures the SNMP notify inform request.

snmp-server user

Defines a user who can access the SNMP engine.


splunk-uf-monitor

To configure Splunk Universal Forwarder monitoring, use the splunk-uf-monitor command in Global configuration mode.

On the SE:

splunk-uf-monitor {enable | host hostname or ipaddress [port port number] | type {all | abr-session | flash-media-streaming | movie-streamer | snapshot-counter | web-engine | wmt}}

no splunk-uf-monitor {enable | host hostname or ipaddress [port port number] | type {all | abr-session | flash-media-streaming | movie-streamer | snapshot-counter | web-engine | wmt}}

On the SR:

splunk-uf-monitor {enable | host hostname or ipaddress [port port number] | type {all | snapshot-counter | service-router}}

no splunk-uf-monitor {enable | host hostname or ipaddress [port port number] | type {all | snapshot-counter | service-router}}

Syntax Description

enable

Enables the Splunk Universal Forwarder.

host

Uploads to the host (maximum of three hosts).

hostname or ipaddress

Host name or IP address of the host.

port

Port to use when connected to a host (default is 9998).

port number

Port number of the host.

type

Configures the log type to be monitored.

all

Monitors all log types.

abr-session

Monitors the ABR session log.

flash-media-streaming

Monitors the Flash Media Streaming log.

movie-streamer

Monitors the Movie Streamer log.

snapshot-counter

Monitors the snapshot-count log.

service-router

Monitors the Service Router log.

web-engine

Monitors the Web Engine log.

wmt

Monitors the WMT log.


Command Defaults

Port: 9998

Command Modes

Global configuration (config) mode.

Usage Guidelines

The splunk-uf-monitor enable command enables and disables the Splunk Universal Forwarder monitoring on the SE and SR.

The splunk-uf-monitor host hostname or ipaddress [port port number] command configures the Splunk Universal Forwarder host IP address and port number, the port number is optional when it's default port number is 9998 on the SE and SR.

The splunk-uf-monitor type {all | abr-session | flash-media-streaming | movie-streamer | snapshot-counter | web-engine | wmt} command configures the transaction logs to be monitored by Splunk Universal Forwarder on an SE.

The splunk-uf-monitor type {all | snapshot-counter | service-route} command configures the transaction logs to be monitored by the Splunk Universal Forwarder on an SR.

Examples

The following example shows how to enable the Splunk Universal Forwarder and configures the forwarder to monitor all transaction log types:

ServiceEngine(config)# splunk-uf-monitor enable
ServiceEngine(config)#
 
   
ServiceEngine(config)# splunk-uf-monitor type all
ServiceEngine(config)#
 
   

The following example shows how to configure the Splunk Universal Forwarder host IP address and port number:

ServiceEngine(config)# splunk-uf-monitor host X.X.X.X port 9998
ServiceEngine(config)#

Related Commands

Command
Description
transaction-logs
Configure and enable transaction logs.

ss

To dump socket statistics, use the ss command in EXEC configuration mode.

ss line

Syntax Description

line

ss connection information, -h to get help.


Command Defaults

None

Command Modes

EXEC configuration.

Usage Guidelines

The ss utility is used to dump socket statistics. It shows information similar to the netstat command and displays more TCP information than other tools.

When specifying the options and filters, you can use the short form of the option (a single dash followed by a character) or the long form of the option (two dashes followed by the whole word). To view the list of options and filters, enter ss -h (or ss --help) and the list of options and filters are displayed along with descriptions.

ServiceEngine# ss -h
Usage: ss [OPTIONS]
       ss [OPTIONS] [FILTER]
   -h, --help           this message
   -V, --version        output version information
   -n, --numeric        does not resolve service names
   -r, --resolve       resolve host names
   -a, --all            display all sockets
   -l, --listening      display listening sockets
   -o, --options       show timer information
   -e, --extended      show detailed socket information
   -m, --memory        show socket memory usage
   -p, --processes      show process using socket
   -i, --info           show internal TCP information
   -s, --summary        show socket usage summary
 
   
   -4, --ipv4          display only IP version 4 sockets
   -6, --ipv6          display only IP version 6 sockets
   -0, --packet display PACKET sockets
   -t, --tcp            display only TCP sockets
   -u, --udp            display only UDP sockets
   -d, --dccp           display only DCCP sockets
   -w, --raw            display only RAW sockets
   -x, --unix           display only Unix domain sockets
   -7, --filter display when tcp rqueue threshold meet
   -8, --filter display when tcp wqueue threshold meet
   -9, --filter display when tcp retransmit threshold meet
   -W, --filter display only window scale disable
   -B, --background display output in new format
   -L, --no_loop_back   display without loopback interface
   -S, --basic_output  display basic information
   -f, --family=FAMILY display sockets of type FAMILY
 
   
   -A, --query=QUERY
       QUERY := {all | inet | tcp | udp | raw | unix | packet | netlink}[,QUERY]
 
   
   -F, --filter=FILE   read filter information from FILE
       FILTER := [state TCP-STATE] [EXPRESSION]
 
   

With the -A query option, you list the identifiers (all, inet, tcp, udp, and so on) of the socket tables you want displayed, separated by commas.

With the -F filter option, you can filter by TCP state, or using a boolean expression you can filter by IP addresses and ports.

The default output does not resolve host addresses (IP addresses) and does resolve service names (usually stored in local files). To resolve host addresses, use the -r option. To suppress resolution of service names, use the -n option.

Examples

The following command shows how to display all TCP sockets:

ServiceEngine# ss -t -a 
 
   

The following command shows how to display all UDP sockets:

ServiceEngine# ss -u -a 
 
   

The following command shows how to display all established SSH connections and display the timer information:

ServiceEngine# ss -o state established '( dport = :ssh or sport = :ssh )' 
 
   

The following command shows how to display all established HTTP connections and display the timer information:

ServiceEngine# ss -o state established '( dport = :http or sport = :http )' 

Related Commands

Command
Description

gulp

Captures lossless gigabit packets and writes them to disk.

netmon

Displays the transmit and receive activity on an interface.

netstatr

Displays the rate of change of netstat statistics.

tcpmon

Searches all TCP connections.


sshd

To enable the Secure Shell (SSH) daemon, use the sshd command in Global configuration mode. To disable SSH, use the no form of this command.

sshd {enable | timeout seconds | version {1 | 2}}

no sshd {enable | password-guesses | timeout | version {1 | 2}}

Syntax Description

enable

Enables the SSH feature.

timeout

Configures the number of seconds for which an SSH session is active during the negotiation (authentication) phase between the client and the server before it times out.

Note If you have established an SSH connection to the SE but have not entered the username when prompted at the login prompt, the connection is terminated by the SE even after successful login if the grace period expires.

seconds

SSH login grace time value, in seconds. The range is from 1 to 99999. The default is 300.

version

Configures the SSH version to be supported on the SE.

1

Specifies that SSH Version 1 is supported on the SE.

2

Specifies that SSH Version 2 is supported on the SE.


Command Defaults

timeout seconds: 300

version: Both SSH Version 1 and 2 are enabled.

Command Modes

Global configuration (config) mode.

Usage Guidelines

SSH enables login access to the SE through a secure and encrypted channel. SSH consists of a server and a client program. Like Telnet, you can use the client program to remotely log on to a machine that is running the SSH server, but unlike Telnet, messages transported between the client and the server are encrypted. The functionality of SSH includes user authentication, message encryption, and message authentication.

When you enable the SSH server, the Secure File Transfer Protocol (SFTP) server is also enabled. The SFTP is a file transfer program that provides a secure and authenticated method for transferring files between CDS devices and other workstations or clients.


Note SFTP is the standard file transfer protocol introduced in SSH Version 2. The SFTP client functionality is provided as part of the SSH component. If you use SSH Version 1 on the SE, SFTP support is not available.


The sshd version command in Global configuration mode allows you to enable support for either SSH Version 1 or SSH Version 2. When you enable SSH using the sshd enable command in Global configuration mode, the Internet Streamer CDS software enables support for both SSH Version 1 and SSH Version 2 on the SE. If you want the SE to support only one version of SSH (for example SSH Version 2), disable the other version (in this example, SSH Version 1) by using the no sshd version 1 command.

When support for both SSH Version 1 and SSH Version 2 are enabled in the SE, the show running-config command output does not display any sshd configuration. If you have disabled the support for one version of SSH, the show running-config command output contains the following line:

no sshd version version_number

Note You cannot disable both SSH versions in an SE. Use the no sshd enable command in Global configuration mode to disable SSH on the SE.


Examples

The following example shows how to enable the SSH daemon and configure the number of allowable password guesses and timeout for the SE:

ServiceEngine(config)# sshd enable
ServiceEngine(config)# sshd password-guesses 4
ServiceEngine(config)# sshd timeout 20
 
   

The following example disables the support for SSH Version 1 in the SE:

ServiceEngine(config)# no sshd version 1

Related Commands

Command
Description

show ssh

Displays the SSH status and configuration.


streaming-interface

To configure the streaming interface, use the streaming-interface command in Global configuration mode. To remove a streaming interface, use the no form of this command.

streaming-interface {GigabitEthernet num | PortChannel num | Standby num}

Syntax Description

GigabitEthernet

Selects a Gigabit Ethernet interface as streaming interface.

num

Gigabit Ethernet slot (the range is 1 to 14) and port (the range is 0 to 0).

PortChannel

Selects a port channel interface as streaming interface.

num

Port channel port.

Standby

Selects a standby group as streaming interface.

num

Standby group number.


Defaults

None

Command Modes

Global configuration (config) mode.

Usage Guidelines

When upgrading from a previous software release, the primary interface is converted to a streaming interface by the upgrade process. When configuring new delivery traffic interfaces, either because of a new installation or because of removing existing configuration, use the streaming-interface command.

Examples

The following example shows how to configure port channel 1 as the streaming interface:

ServiceEngine# streaming-interface portChannel 1
 
   
ServiceEngine# 

sysreport

To save the sysreport to a user-specified file, use the sysreport privilege command in EXEC configuration mode.

sysreport {acquisition-distribution [date-range start_date end_date | filename] | authentication [date-range start_date end_date | filename] | cms [date-range start_date end_date | filename] | dns | flash-media-streaming | ftp | http | icap | movie-streamer | rules | wmt}

Syntax Description

acquisition-distribution

Generates sysreport information related to acquisition and distribution.

date-range

Specifies the date range of system report.

start_date

Specifies start date of system report following the yyyy/mm/dd format assuming local time zone.

end_date

The end date of system report following the yyyy/mm/dd format assuming local time zone.

filename

Filename (xxx.tar.gz) for system report.

authentication

Generates sysreport information related to http authentication.

cms

Generates sysreport information related to Centralized Management System (CMS).

dns

Generates sysreport information related to Domain Name Server (DNS).

flash-media-streaming

Generates sysreport information related to Flash Media Streaming.

ftp

Generates sysreport information related to FTP.

http

Generates sysreport information related to HTTP.

icap

Generates sysreport information related to ICAP

movie-streamer

Generates sysreport information related to Movie Streamer.

rules

Generates sysreport information related to rules.

wmt

Generates sysreport information related to WMT.


Command Defaults

None

Command Modes

Privilege EXEC configuration mode.

Examples

The following example saves the sysreport for WMT to a user-specified file:

ServiceEngine# sysreport wmt date-range 2009/05/07 2009/05/11 xxx.tar.gz 
The sysreport has been saved onto file xxx.tar.gz in local1

tacacs

To configure TACACS+ server parameters, use the tacacs command in Global configuration mode. To disable individual options, use the no form of this command.

tacacs {host {hostname | ip_address} [primary] | key keyword | password ascii  | retransmit retries | timeout seconds}

no tacacs {host {hostname | ip_address} [primary] | key | password ascii | retransmit | timeout}

Syntax Description

host

Sets a server address.

hostname

Hostname of the TACACS+ server.

ip_address

IP address of the TACACS+ server.

primary

(Optional) Sets the server as the primary server.

key

Sets the security word.

keyword

Keyword. An empty string is the default.

password ascii

Specifies ASCII as the TACACS+ password type.

retransmit

Sets the number of times that requests are retransmitted to a server.

retries

Number of retry attempts allowed. The range is from 1 to 3. The default is 2.

timeout

Sets the number of seconds to wait before a request to a server is timed out.

seconds

Timeout, in seconds. The range is from 1 to 20. The default is 5.


Command Defaults

keyword: none (empty string)

timeout seconds: 5

retransmit retries: 2

password ascii: PAP

Command Modes

Global configuration (config) mode.

Usage Guidelines

Using the tacacs command, configure the TACACS+ key, the number of retransmits, the server hostname or IP address, and the timeout.

Execute the following two commands to enable user authentication with a TACACS+ server:

ServiceEngine(config)# authentication login tacacs enable
ServiceEngine(config)# authentication configuration tacacs enable
 
   

HTTP request authentication is independent of user authentication options and must be disabled with the following separate commands:

ServiceEngine(config)# no authentication login tacacs enable
ServiceEngine(config)# no authentication configuration tacacs enable
 
   

The Users GUI page or the username command in Global configuration provide a way to add, delete, or modify usernames, passwords, and access privileges in the local database. The TACACS+ remote database can also be used to maintain login and configuration privileges for administrative users. The tacacs host command or the TACACS+ Service Engine GUI page allows you to configure the network parameters required to access the remote database.

One primary and two backup TACACS+ servers can be configured; authentication is attempted on the primary server first and then on the others in the order in which they were configured. The primary server is the first server configured unless another server is explicitly specified as primary with the tacacs host hostname primary command.

Use the tacacs key command to specify the TACACS+ key that is used to encrypt the packets sent to the server. This key must be the same as the one specified on the server daemon. The maximum number of characters in the key should not exceed 99 printable ASCII characters (except tabs). An empty key string is the default. All leading spaces are ignored; spaces within and at the end of the key string are not ignored. Double quotes are not required even if there are spaces in the key, unless the quotes themselves are part of the key.

The tacacs timeout is the number of seconds that the Service Engine waits before declaring a timeout on a request to a particular TACACS+ server. The range is from 1 to 20 seconds with 5 seconds as the default. The number of times that the Service Engine repeats a retry-timeout cycle before trying the next TACACS+ server is specified by the tacacs retransmit command. The default is two retry attempts.

Three unsuccessful login attempts are permitted. TACACS+ logins may appear to take more time than local logins depending on the number of TACACS+ servers and the configured timeout and retry values.

Use the tacacs password ascii command to specify the TACACS+ password type as ASCII. The default password type is Password Authentication Protocol (PAP). In earlier releases, the password type was not configurable. When users needed to log in to a Service Engine, a TACACS+ client sent the password information in PAP format to a TACACS+ server. However, TACACS+ servers that were configured for router management required the passwords to be in ASCII cleartext format instead of PAP format to authenticate users logging in to the Service Engine. The password type to authenticate user information to ASCII was configurable from the CLI.


Note When the no tacacs password ascii command is used to disable the ASCII password type, the password type is once again reset to PAP.


The TACACS+ client can send different requests to the server for user authentication. The client can send a TACACS+ request with the PAP password type. In this scenario, the authentication packet includes both the username and the user's password. The server must have an appropriately configured user's account.

Alternatively, the client can send a TACACS+ request with the ASCII password type as another option. In this scenario, the authentication packet includes the username only and waits for the server response. Once the server confirms that the user's account exists, the client sends another Continue request with the user's password. The Authentication Server must have an appropriately configured user's account to support either type of password.

Examples

The following example shows how to configure the key used in encrypting packets:

ServiceEngine(config)# tacacs key human789
 
   

The following example shows how to configure the host named spearhead as the primary TACACS+ server:

ServiceEngine(config)# tacacs host spearhead primary
 
   

The following example shows how to set the timeout interval for the TACACS+ server:

ServiceEngine(config)# tacacs timeout 10
 
   

The following example shows how to set the number of times that authentication requests are retried (retransmitted) after a timeout:

ServiceEngine(config)# tacacs retransmit 5
 
   

The following example shows the password type to be PAP by default:

ServiceEngine# show tacacs 
    Login Authentication for Console/Telnet Session: enabled (secondary)
    Configuration Authentication for Console/Telnet Session: enabled (secondary)
 
   
    TACACS+ Configuration:
    ---------------------
    TACACS+ Authentication is off
    Key        = *****
    Timeout    = 5
    Retransmit = 2
    Password type: pap
 
   
    Server                         Status
    ----------------------------   ------
    10.107.192.148                primary
    10.107.192.168                
    10.77.140.77                   
ServiceEngine# 
 
   

However, you can configure the password type to be ASCII using the tacacs password ascii command. You can then verify the changes using the show tacacs command as follows:

ServiceEngine(config)# tacacs password ascii 
ServiceEngine(config)# exit
ServiceEngine# show tacacs 
    Login Authentication for Console/Telnet Session: enabled (secondary)
    Configuration Authentication for Console/Telnet Session: enabled (secondary)
 
   
    TACACS+ Configuration:
    ---------------------
    TACACS+ Authentication is off
    Key        = *****
    Timeout    = 5
    Retransmit = 2
    Password type: ascii
 
   
    Server                         Status
    ----------------------------   ------
    10.107.192.148                primary
    10.107.192.168                
    10.77.140.77 

Related Commands

Command
Description

show authentication

Displays the authentication configuration.

show statistics tacacs

Displays the Service Engine TACACS+ authentication and authorization statistics.

show tacacs

Displays TACACS+ authentication protocol configuration information.


tcpdump

To dump the network traffic, use the tcpdump command in EXEC configuration mode.

tcpdump [LINE]

Syntax Description

LINE

(Optional) Dump options.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

Use the tcpdump command to gather a sniffer trace on the SE, SR, or CDSM for troubleshooting when asked to gather the data by the Cisco Technical Support. This utility is very similar to the Linux or UNIX tcpdump command.

The tcpdump command allows an administrator (must be an admin user) to capture packets from the Ethernet. On the SE 500 series, the interface names are GigabitEthernet 1/0 and GigabitEthernet 2/0. On all CDS platforms, we recommend that you specify a path/filename in the local1 directory.

You can do a straight packet header dump to the screen by entering the tcpdump command. Press Ctrl-C to stop the dump.

The tcpdump command has the following options:

-w <filename>—Writes the raw packet capture output to a file.

-s <count>—Captures the first <count> bytes of each packet.

-i <interface>—Allows you to specify a specific interface to use for capturing the packets.

-c <count>—Limits the capture to <count> packets.

The following example captures the first 1500 bytes of the next 10,000 packets from interface Ethernet 0 and puts the output in a file named dump.pcap in the local1 directory on the SE:

ServiceEngine# tcpdump -w /local1/dump.pcap -i GigabitEthernet 1/0 -s 1500 -c 10000

When you specify the -s option, it sets the packet snap length. The default value captures only 64 bytes, and this default setting saves only packet headers into the capture file. For troubleshooting of redirected packets or higher level traffic (HTTP, authentication, and so on), copy the complete packets.

After the TCP dump has been collected, you need to move the file from the SE to a PC so that the file can be viewed by a sniffer decoder.

 
   
ftp <ip address of the SE>
 
   
!--- Log in using the admin username and password.     
 
   
 
   
     cd local1
     bin
     hash
     get <name of the file>      
 
   
 
   
!--- Using the above example, it would be dump.pcap.
 
   
     bye
 
   

We recommend that you use Ethereal as the software application for reading the TCP dump. With Ethereal, you can decode packets that are encapsulated into a GRE tunnel. See the Ethereal website for further information.


Note In most cases, redirected packets captured by the tcpdump facility with the CDS CLI differ from the data received on the interface. The destination IP address and TCP port number are modified to reflect the device IP address and the port number 8999.


Examples

The following example shows how to dump the TCP network traffic:

ServiceEngine# tcpdump
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on GigabitEthernet 1/0, link-type EN10MB (Ethernet), capture size 68 bytes
12:45:43.017677 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 
3342832089:3342832201(112) ack 1248615673 win 15232
12:45:43.018950 IP 172.19.226.63 > ServiceEngine.cisco.com: icmp 36: 172.19.226.63 udp 
port 2048 unreachable
12:45:43.019327 IP ServiceEngine.cisco.com.10015 > dns-sj2.cisco.com.domain:  49828+ [  | 
domain ] 
12:45:43.021158 IP dns-sj2.cisco.com.domain > ServiceEngine.cisco.com.10015:  49828 
NXDomain* [  | domain ] 
12:45:43.021942 IP ServiceEngine.cisco.com.10015 > dns-sj2.cisco.com.domain:  49829+ [  | 
domain ] 
12:45:43.023799 IP dns-sj2.cisco.com.domain > ServiceEngine.cisco.com.10015:  49829 
NXDomain* [  | domain ] 
12:45:43.024240 IP ServiceEngine.cisco.com.10015 > dns-sj2.cisco.com.domain:  49830+ [  | 
domain ] 
12:45:43.026164 IP dns-sj2.cisco.com.domain > ServiceEngine.cisco.com.10015:  49830* [  | 
domain ] 
12:45:42.702891 802.1d config TOP_CHANGE 8000.00:03:9f:f1:10:63.8042 root 
8000.00:01:43:9a:c8:63 pathcost 26 age 3 max 20 hello 2 fdelay 15 
12:45:42.831404 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 112 win 64351
12:45:42.831490 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: . 112:1444(1332) ack 1 
win 15232
12:45:42.831504 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 1444:1568(124) ack 1 
win 15232
12:45:42.831741 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 1568:1696(128) ack 1 
win 15232
12:45:43.046176 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 1568 win 65535
12:45:43.046248 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 1696:2128(432) ack 1 
win 15232
12:45:43.046469 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 2128:2256(128) ack 1 
win 15232
12:45:43.046616 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 2256:2400(144) ack 1 
win 15232
12:45:43.107700 802.1d config TOP_CHANGE 8000.00:03:9f:f1:10:63.8042 root 
8000.00:01:43:9a:c8:63 pathcost 26 age 3 max 20 hello 2 fdelay 15 
12:45:43.199710 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 1696 win 65407
12:45:43.199784 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 2400:2864(464) ack 1 
win 15232
12:45:43.199998 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 2864:2992(128) ack 1 
win 15232
12:45:43.259968 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 2400 win 64703
12:45:43.260064 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 2992:3280(288) ack 1 
win 15232
12:45:43.260335 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 3280:3408(128) ack 1 
win 15232
12:45:43.260482 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 3408:3552(144) ack 1 
win 15232
12:45:43.260621 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 3552:3696(144) ack 1 
win 15232
12:45:43.413320 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 2992 win 65535
12:45:43.413389 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 3696:3984(288) ack 1 
win 15232
12:45:43.413597 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 3984:4112(128) ack 1 
win 15232
12:45:43.413741 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 4112:4256(144) ack 1 
win 15232
12:45:43.473601 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 3552 win 64975
12:45:43.473659 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 4256:4544(288) ack 1 
win 15232
12:45:43.473853 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 4544:4672(128) ack 1 
win 15232
12:45:43.473994 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 4672:4816(144) ack 1 
win 15232
12:45:43.474132 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 4816:4960(144) ack 1 
win 15232
12:45:43.484117 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: P 1:81(80) ack 3696 
win 64831
12:45:43.484167 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 4960:5248(288) ack 
81 win 15232
12:45:43.484424 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 5248:5392(144) ack 
81 win 15232
12:45:43.627125 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 4112 win 64415
12:45:43.627204 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 5392:5680(288) ack 
81 win 15232
12:45:43.627439 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 5680:5808(128) ack 
81 win 15232
12:45:43.627586 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 5808:5952(144) ack 
81 win 15232
12:45:43.688261 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 4544 win 65535
12:45:43.688316 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 5952:6240(288) ack 
81 win 15232
12:45:43.688495 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 6240:6368(128) ack 
81 win 15232
12:45:43.688638 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 6368:6512(144) ack 
81 win 15232
12:45:43.689012 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 4960 win 65119
12:45:43.689046 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 6512:6800(288) ack 
81 win 15232
12:45:43.689170 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 6800:6928(128) ack 
81 win 15232
12:45:43.689309 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 6928:7072(144) ack 
81 win 15232
12:45:43.689447 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 7072:7216(144) ack 
81 win 15232
12:45:43.698391 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 5392 win 64687
12:45:43.698437 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 7216:7504(288) ack 
81 win 15232
12:45:43.698599 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 7504:7632(128) ack 
81 win 15232
12:45:43.698740 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 7632:7776(144) ack 
81 win 15232
12:45:43.840558 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 5808 win 64271
12:45:43.840622 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 7776:8064(288) ack 
81 win 15232
12:45:43.840819 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 8064:8192(128) ack 
81 win 15232
12:45:43.840962 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 8192:8336(144) ack 
81 win 15232
12:45:43.901868 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 6368 win 65535
12:45:43.901938 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 8336:8624(288) ack 
81 win 15232
12:45:43.901887 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 6928 win 64975
12:45:43.901910 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 7216 win 64687
12:45:43.902137 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 8624:8752(128) ack 
81 win 15232
12:45:43.902281 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 8752:8896(144) ack 
81 win 15232
12:45:43.902414 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 8896:9024(128) ack 
81 win 15232
12:45:43.902547 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 9024:9152(128) ack 
81 win 15232
12:45:43.902687 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 9152:9296(144) ack 
81 win 15232
12:45:43.902826 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 9296:9440(144) ack 
81 win 15232
12:45:43.902965 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 9440:9584(144) ack 
81 win 15232
12:45:43.903104 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 9584:9728(144) ack 
81 win 15232
12:45:43.922413 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 7632 win 64271
12:45:43.922459 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 9728:10304(576) ack 
81 win 15232
12:45:43.922622 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 10304:10432(128) ack 
81 win 15232
12:45:43.922764 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 10432:10576(144) ack 
81 win 15232
12:45:44.053872 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 8192 win 65535
12:45:44.053972 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 10576:10864(288) ack 
81 win 15232
12:45:44.054308 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 10864:11104(240) ack 
81 win 15232
12:45:44.054453 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 11104:11248(144) ack 
81 win 15232
12:45:44.054596 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 11248:11392(144) ack 
81 win 15232
12:45:44.111702 802.1d config TOP_CHANGE 8000.00:03:9f:f1:10:63.8042 root 
8000.00:01:43:9a:c8:63 pathcost 26 age 3 max 20 hello 2 fdelay 15 
12:45:44.114626 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 8752 win 64975
12:45:44.114712 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 11392:11712(320) ack 
81 win 15232
12:45:44.115219 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 11712:11952(240) ack 
81 win 15232
12:45:44.115381 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 11952:12096(144) ack 
81 win 15232
12:45:44.115426 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 9152 win 64575
12:45:44.115617 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 12096:12336(240) ack 
81 win 15232
12:45:44.115760 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 12336:12480(144) ack 
81 win 15232
12:45:44.115904 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 12480:12624(144) ack 
81 win 15232
12:45:44.116045 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 12624:12768(144) ack 
81 win 15232
12:45:44.116094 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 9440 win 64287
12:45:44.116114 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 9728 win 65535
12:45:44.116332 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 12768:13088(320) ack 
81 win 15232
12:45:44.116473 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 13088:13232(144) ack 
81 win 15232
12:45:44.116614 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 13232:13376(144) ack 
81 win 15232
12:45:44.116755 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 13376:13520(144) ack 
81 win 15232
12:45:44.116895 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 13520:13664(144) ack 
81 win 15232
12:45:44.135947 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: . ack 10432 win 64831
12:45:44.135996 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 13664:13808(144) ack 
81 win 15232
12:45:44.136223 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 13808:14048(240) ack 
81 win 15232
12:45:44.136366 IP ServiceEngine.cisco.com.ssh > 10.77.140.97.4314: P 14048:14192(144) ack 
81 win 15232
12:45:44.144104 IP 10.77.140.97.4314 > ServiceEngine.cisco.com.ssh: P 81:161(80) ack 10576 
win 64687
 
   
102 packets captured
105 packets received by filter
0 packets dropped by kernel
 
   

The following example shows how to dump the TCP network traffic and redirect it to a file named test:

ServiceEngine# tcpdump port 8080 -w test
tcpdump: listening on GigabitEthernet 1/0, link-type EN10MB (Ethernet), capture size 68 
bytes
216 packets captured
216 packets received by filter
0 packets dropped by kernel
 
   

tcpmon

To search all TCP connections, use the tcpmon command in EXEC configuration mode.

tcpmon line

Syntax Description

line

Shows TCP connection information, -h to get help.


Command Defaults

None

Command Modes

EXEC configuration.

Usage Guidelines

The tcpmon utility is a script that constantly calls the ss utility at specified intervals. The tcpmon utility searches all TCP connections every 30 seconds and displays information about any socket that meets the search criteria. To view the list of options, enter tcpmon -h.

ServiceEngine# tcpmon -h
 
   
Usage: Tcpmon [-N] [-R <Recv-Q-Threshold> | -S <Send-Q-threshold> | -T 
<Retransmit-threshold>]
              [<loop-time-in-seconds>] [<iterations>]
       (runs every 30 sec forever by default)
 
   

Output Example

The following example shows the output for the tcpmon utility:

State   Recv-Q   Send-Q   Local Address:Port    Peer Address:Port  Rtt/var   Swnd  Retrans
ESTAB     0      257744      10.3.5.2:80         10.3.5.137:32963   530/15    13      0
ESTAB     0      861560      10.3.5.2:80         10.3.5.137:32849   545/24     4      0
ESTAB     0      234576      10.3.5.2:80         10.3.5.122:32979   547/22.2   6      0
ESTAB     0      254848      10.3.5.2:80         10.3.5.103:32909   531/14.8  10      0
ESTAB     0      231680      10.3.5.2:80         10.3.5.135:32925   532/11.5   9      0
ESTAB     0      224440      10.3.5.2:80         10.3.5.133:33057   550/32     7      0
ESTAB     0      267880      10.3.5.2:80         10.3.5.135:32985   530/18.2   7      0
ESTAB     0      291048      10.3.5.2:80         10.3.5.113:32909   539/12.2   6      0
ESTAB     0      249056      10.3.5.2:80         10.3.5.103:32903   520/23.2   8      0
ESTAB     0      218648      10.3.5.2:80         10.3.5.132:33069   522/14.5  16      0
ESTAB     0      702280      10.3.5.2:80         10.3.5.100:32829   539/24.5   5      0
ESTAB     0      412680      10.3.5.2:80         10.3.5.110:32992   546/22.8   7      0
ESTAB     0      254848      10.3.5.2:80         10.3.5.115:33136   552/37.2   5      0
 
   

Table 0-22 describes the tcpmon output fields.

Table 0-22 tcpmon Output Fields

Field
Description

State

One of the following TCP connection states: ESTAB, SYN-SENT, SYN-RECV, FIN-WAIT-1, FIN-WAIT-2, TIME-WAIT, CLOSE-WAIT, LAST-ACK, LISTEN, and CLOSING.

Recv-Q

Number of bytes in the receiving queue.

Send-Q

Number of bytes in the sending queue.

Local Address: Port

Source address and port.

Peer Address: Port

Destination address and port.

Rtt/var

Average round-trip time (in seconds) and the deviation.

Send

Current sending rate (in Mbps).

Retrans

Number of retransmit timeouts.


Examples

The following command sets the polling cycle to 30 seconds and the receive-queue threshold to 100:

ServiceEngine# tcpmon -R 100 30
 
   

The following command sets the polling cycle to 30 seconds and displays only the sockets with window scaling disabled:

ServiceEngine# tcpmon -N 30

Related Commands

Command
Description

gulp

Captures lossless gigabit packets and writes them to disk.

netmon

Displays the transmit and receive activity on an interface.

netstatr

Displays the rate of change of netstat statistics.

ss

Dumps socket statistics.


tcp timestamp

To enable and disable the TCP timestamp, use the tcp timestamp command in Global configuration mode. To disable the TCP timestamp, use the no form of this command.

tcp timestamp

no tcp timestamp

Syntax Description

This command has no arguments or keywords.

Command Defaults

TCP timestamp is enabled by default.

Command Modes

Global configuration (config) mode.

Examples

The following example shows how to disable the TCP timestamp:

ServiceEngine# no tcp timestamp
ServiceEngine#

telnet

To log in to a network device using the Telnet client, use the telnet command in EXEC configuration mode.

telnet {hostname | ip_address} [port_num]

Syntax Description

hostname

Hostname of the network device.

ip_address

IP address of the network device.

port_num

(Optional) Port number. The range is from 1 to 65535. Default port number is 23.


Command Defaults

The default port number is 23.

Command Modes

EXEC configuration mode.

Usage Guidelines

Some UNIX shell functions, such as escape and the suspend command, are not available in the Telnet client. In addition, multiple Telnet sessions are also not supported.

The Telnet client allows you to specify a destination port. By entering the telnet command, you can test websites by attempting to open a Telnet session to the website from the SE CLI.

Examples

The following example shows how to open a Telnet session to a network device using the hostname:

ServiceEngine# telnet cisco-ce
 
   

The following example shows how to open a Telnet session to a network device using the IP address:

ServiceEngine# telnet 172.16.155.224
 
   

The following example shows how to open a Telnet session to a network device on port 8443 using the hostname:

ServiceEngine# telnet cisco-ce 8443
 
   

The following example shows how to open a Telnet session to a network device on port 80 using the hostname:

ServiceEngine# telnet www.yahoo.com 80
 
   

telnet enable

To enable Telnet, use the telnet enable command in Global configuration mode. To disable Telnet, use the no form of this command.

telnet enable

no telnet enable

Syntax Description

This command has no arguments or keywords.

Command Defaults

Enabled

Command Modes

Global configuration (config) mode.

Usage Guidelines

Use this Terminal Emulation protocol for a remote terminal connection. The telnet enable command allows users to log in to other devices using a Telnet session.

Examples

The following example shows how to enable Telnet on the SE:

ServiceEngine(config)# telnet enable

Related Commands

Command
Description

show telnet

Displays the Telnet services configuration.


terminal

To set the number of lines displayed in the console window, or to display the current console debug command output, use the terminal command in EXEC configuration mode.

terminal {length length | monitor [disable]}

Syntax Description

length

Sets the length of the display on the terminal.

length

Length of the display on the terminal (the range is 0 to 512). Setting the length to 0 means that there is no pausing.

monitor

Copies the debug output to the current terminal.

disable

(Optional) Disables monitoring at this specified terminal.


Command Defaults

The default length is 24 lines.

Command Modes

EXEC configuration mode.

Usage Guidelines

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

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

Examples

The following example shows how to set the number of lines to display to 20:

ServiceEngine# terminal length 20
 
   

The following example shows how to configure the terminal for no pausing:

ServiceEngine# terminal length 0

Related Commands

All show commands.

test-url

To test the accessibility of a URL using FTP, HTTP, or HTTPS, use the test-url command in EXEC configuration mode.

test-url {ftp url [use-ftp-proxy proxy_url] | http url [custom-header header [head-only] [use-http-proxy proxy_url] | head-only [custom-header header] [use-http-proxy proxy_url] | use-http-proxy proxy_url [custom-header header] [head-only]]}

Syntax Description

ftp

Specifies the FTP URL to be tested.

url

FTP URL to be tested. Use one of the following formats to specify the FTP URL:

ftp://domainname/path

ftp://user:password@domainname/path

use-ftp-proxy

(Optional) Specifies the FTP proxy that is used to test the URL.

proxy_url

FTP proxy URL. Use one of the following formats to specify the proxy URL:

proxy IP Address:proxy Port

proxy Username:proxy Password@proxy IP Address:proxy Port

http

Specifies the HTTP URL to be tested.

url

HTTP URL to be tested. Use one of the following formats to specify the HTTP URL:

http://domainname/path

http://user:password@domainname/path

custom-header

(Optional) Specifies the custom header information to be sent to the server.

header

Custom header information to be sent to the server. Use the format header:line to specify the custom header.

head-only

(Optional) Specifies that only the HTTP header information must be retrieved.

use-http-proxy

(Optional) Specifies the HTTP proxy that is used to test the URL.

proxy_url

HTTP proxy URL. Use one of the following formats to specify the HTTP proxy URL:

http://proxyIp:proxyPort

http://proxyUser:proxypasswd@proxyIp:proxyPort

head-only

(Optional) Specifies that only the HTTPS header information must be retrieved.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

The HTTP CLI client allows you to test connectivity and debug caching issues. The test-url command allows you to test whether a URL is accessible over the FTP, HTTP, and HTTPS protocols. When you test the connectivity using the test-url command, the SE sends a request using the protocol that you have specified to the server and fetches the requested contents. The actual content is dumped into the path /dev/null, and the server response with the header information is displayed to the user.

You can use the test-url ftp command to test the following for the specified URL:

Connectivity to the URL

Connectivity to the URL through the FTP proxy (using the use-ftp-proxy option)

Authentication

FTP proxy authentication

You can use the test-url http command to test the following for the specified URL:

Test the connectivity to the URL

Test the connectivity to the URL through the HTTP proxy (using the use-http-proxy option)

Authentication

HTTP proxy authentication

Header information only for the specified page (using the head-only option) or additional header information (using the custom-header option)

Examples

The following example tests the accessibility to the URL http://192.168.171.22 using HTTP:

ServiceEngine# test-url http http://ce1.server.com
--02:27:20-- http://ce1.server.com/
           => `/dev/null'
Len - 22 , Restval - 0 , contlen - 0 , Res - 134728056Resolving ce1.server.com..
 
   
done.
Connecting to ce1.server.com [ 192.168.171.22 ] :80... connected.
HTTP request sent, awaiting response...
 1 HTTP/1.1 200 OK
 2 Date: Mon, 26 Jul 2004 08:41:34 GMT
 3 Server: Apache/1.2b8
 4 Last-Modified: Fri, 25 Apr 2003 12:23:04 GMT
 5 ETag: "1aee29-663-3ea928a8"
 6 Content-Length: 1635
 7 Content-Type: text/html
 8 Via: 1.1 Content Delivery System Software 5.2
 9 Connection: Keep-Alive
 (1635 to go)
 0% [                                    ] 0             --.--K/s    ETA --:--L
en - 0   ELen - 1635     Keepalive - 1
100% [ ====================================> ] 1,635          1.56M/s    ETA 00:00
 
   
02:27:20 (1.56 MB/s) - `/dev/null' saved [ 1635/1635 ] 
 
   

The following example tests the accessibility to the URL http://192.168.171.22 through the HTTP proxy 10.107.192.148:

ServiceEngine# test-url http http://192.168.171.22 use-http-proxy 10.107.192.148:8090
--15:22:51--  http://10.77.155.246/
           => `/dev/null'
Len - 1393 , Restval - 0 , contlen - 0 , Res - 134728344Connecting to 
10.107.192.148:8090... connected.
Proxy request sent, awaiting response...
 1 HTTP/1.1 401 Authorization Required
 2 Date: Mon, 27 Sep 2004 15:29:18 GMT
 3 Server: Apache/1.3.27 (Unix) tomcat/1.0
 4 WWW-Authenticate: Basic realm="IP/TV Restricted Zone"
 5 Content-Type: text/html; charset=iso-8859-1
 6 Via: 1.1 Content Delivery System Software 5.2.1
 7 Connection: Close
Len - 0 , Restval - 0 , contlen - -1 , Res - -1Connecting to 10.107.192.148:8090... 
connected.
Proxy request sent, awaiting response...
 1 HTTP/1.1 401 Authorization Required
 2 Date: Mon, 27 Sep 2004 15:29:19 GMT
 3 Server: Apache/1.3.27 (Unix) tomcat/1.0
 4 WWW-Authenticate: Basic realm="IP/TV Restricted Zone"
 5 Content-Type: text/html; charset=iso-8859-1
 6 Via: 1.1 Content Delivery System Software 5.2.1
 7 Connection: Keep-Alive
 (1635 to go)
 0% [                                    ] 0             --.--K/s    ETA --:--L
en - 0   ELen - 1635     Keepalive - 1
100% [ ====================================> ] 1,635          1.56M/s    ETA 00:00
 
   
02:27:20 (1.56 MB/s) - `/dev/null' saved [ 1635/1635 ] 
 
   

The following example tests the accessibility to the URL ftp://ssivakum:ssivakum@10.77.157.148 using FTP:

ServiceEngine# test-url ftp ftp://ssivakum:ssivakum@10.77.157.148/antinat-0.90.tar
Mar 30 14:33:44 nramaraj-ce admin-shell: %SE-PARSER-6-350232: CLI_LOG shell_parser_log: 
test-url ftp ftp://ssivakum:ssivakum@10.77.157.148/antinat-0.90.tar
--14:33:44--  ftp://ssivakum:*password*@10.77.157.148/antinat-0.90.tar
           => `/dev/null'
Connecting to 10.77.157.148:21... connected.
Logging in as ssivakum ...
220 (vsFTPd 1.1.3)
--> USER ssivakum
 
   
331 Please specify the password.
--> PASS Turtle Power!
230 Login successful. Have fun.
--> SYST
 
   
215 UNIX Type: L8
--> PWD
 
   
257 "/home/ssivakum"
--> TYPE I
 
   
200 Switching to Binary mode.
==> CWD not needed.
--> PORT 10,1,1,52,82,16
 
   
200 PORT command successful. Consider using PASV.
--> RETR antinat-0.90.tar
 
   
150 Opening BINARY mode data connection for antinat-0.90.tar (1771520 bytes).
Length: 1,771,520 (unauthoritative)
 
   
 0% [                                                                                     
] 0             --.--K/s    ETA --:--Len - 0   ELen - 1771520          Keepalive - 0
100% [ 
=====================================================================================> ] 
1,771,520    241.22K/s    ETA 00:00
 
   
226 File send OK.
14:33:53 (241.22 KB/s) - `/dev/null' saved [ 1771520 ] 
 
   
ServiceEngine# 

Related Commands

Command
Description

acquirer (EXEC)

Starts or stops content acquisition on a specified acquirer delivery service.


top

To see a dynamic real-time view of a running CDS, use the top command in EXEC configuration mode.

top {line}

Syntax Description

line

Specifies top options, enter -h to get Help. Press q to quit from the output.


Command Defaults

No default behavior values

Command Modes

EXEC configuration mode.

Usage Guidelines

The memory usage reported in the output of the top command could fluctuate between 1x to 2x of SR's initial memory usage when the SR configuration changes. This fluctuation is between 'init memory with URT on' and 'init memory with URT off', when changing the URT configuration. Therefore, there is a 1.5GB limit so the SR has enough space to go as high as 3GB memory for TPS.

Considerations:

1. Make sure the SR initial memory usage is less than 1.5GB.

2. The memory usage after a configuration change causes the number reported by the top command to be higher, but that is acceptable.

3. If changing the URT, make sure the memory usage URT is turned off at less than 1.5GB; otherwise, there may be a problem.

Examples

The following example shows sample output from the top command on an SE:

ServiceEngine# top
top - 01:08:45 up 8 days, 23:39, 3 users, load average: 1244.22, 1246.32, 1243.66
Tasks: 1789 total,  4 running, 1785 sleeping,  0 stopped,  0 zombie
Cpu(s): 0.0%us, 13.2%sy, 18.1%ni, 57.8%id, 1.1%wa, 0.7%hi, 9.2%si, 0.0%st
Mem: 32825728k total, 32671416k used,  154312k free,  137164k buffers
Swap:       0k total,        0k used,        0k free, 21289468k cached
 
   

traceroute

To trace the route to a remote host, use the traceroute command in EXEC configuration mode.

On the CDSM and SE:

traceroute {hostname | ip_address}

On the SR:

traceroute {hostname | ip_address | srp name}

Syntax Description

hostname

Name of the remote host.

ip_address

IP address of the remote host.

srp

Specifies Traceroute Service Routing Protocol.

name

Name of the DHT key.


Command Defaults

No default behavior values

Command Modes

EXEC configuration mode.

Usage Guidelines

Traceroute is a widely available utility on most operating systems. Similar to ping, traceroute is a valuable tool for determining connectivity in a network. Ping allows the user to find out if there is a connection between the two end systems. Traceroute does this as well, but additionally lists the intermediate routers between the two systems. Users can see the routes that packets can take from one system to another. Use the traceroute command to find the route to a remote host when either the hostname or the IP address is known.

The traceroute command uses the TTL field in the IP header to cause routers and servers to generate specific return messages. Traceroute starts by sending a UDP datagram to the destination host with the TTL field set to 1. If a router finds a TTL value of 1 or 0, it drops the datagram and sends back an ICMP time-exceeded message to the sender. The traceroute facility determines the address of the first hop by examining the source address field of the ICMP time-exceeded message.

To identify the next hop, traceroute sends a UDP packet with a TTL value of 2. The first router decrements the TTL field by 1 and sends the datagram to the next router. The second router sees a TTL value of 1, discards the datagram, and returns the time-exceeded message to the source. This process continues until the TTL is incremented to a value large enough for the datagram to reach the destination host (or until the maximum TTL is reached).

To determine when a datagram has reached its destination, traceroute sets the UDP destination port in the datagram to a very large value that the destination host is unlikely to be using. When a host receives a datagram with an unrecognized port number, it sends an ICMP "port unreachable" error to the source. This message indicates to the traceroute facility that it has reached the destination.

Examples

The following example shows how to trace the route to a remote host from the SE:

ServiceEngine# traceroute 10.77.157.43
traceroute to 10.77.157.43 (10.77.157.43), 30 hops max, 38 byte packets
 1  10.1.1.50 (10.1.1.50)  2.024 ms  2.086 ms  2.219 ms
 2  sblab2-rtr.cisco.com (192.168.10.1)  3.718 ms 172.19.231.249 (172.19.231.249)  0.653 
ms  0.606 ms
 3  sjc22-00lab-gw1.cisco.com (172.24.115.65)  0.666 ms  0.624 ms  0.597 ms
 4  sjc20-lab-gw2.cisco.com (172.24.115.109)  0.709 ms  0.695 ms  0.616 ms
 5  sjc20-sbb5-gw2.cisco.com (128.107.180.97)  0.910 ms  0.702 ms  0.674 ms
 6  sjc20-rbb-gw5.cisco.com (128.107.180.9)  0.762 ms  0.702 ms  0.664 ms
 7  sjc12-rbb-gw4.cisco.com (128.107.180.2)  0.731 ms  0.731 ms  0.686 ms
 8  sjc5-gb3-f1-0.cisco.com (10.112.2.158)  1.229 ms  1.186 ms  0.753 ms
 9  capnet-hkidc-sjc5-oc3.cisco.com (10.112.2.238)  146.784 ms  147.016 ms  147.051 ms
10  hkidc-capnet-gw1-g3-1.cisco.com (10.112.1.250)  147.163 ms  147.319 ms  148.050 ms
11  hkidc-gb3-g0-1.cisco.com (10.112.1.233)  148.137 ms  148.332 ms  148.361 ms
12  capnet-singapore-hkidc-oc3.cisco.com (10.112.2.233)  178.137 ms  178.273 ms  178.005 
ms
13  singapore-capnet2-fa4-0.cisco.com (10.112.2.217)  179.236 ms  179.606 ms  178.714 ms
14  singapore-gb1-fa2-0.cisco.com (10.112.2.226)  179.499 ms  179.914 ms  179.873 ms
15  capnet-chennai-singapore-ds3.cisco.com (10.112.2.246)  211.858 ms  212.167 ms  212.854 
ms
16  hclodc1-rbb-gw2-g3-8.cisco.com (10.112.1.213)  213.639 ms  212.580 ms  211.211 ms
17  10.77.130.18 (10.77.130.18)  212.248 ms  212.478 ms  212.545 ms
18  codc-tbd.cisco.com (10.77.130.34)  212.315 ms  213.088 ms  213.063 ms
19  10.77.130.38 (10.77.130.38)  212.955 ms  214.353 ms  218.169 ms
20  10.77.157.9 (10.77.157.9)  217.217 ms  213.424 ms  222.023 ms
21  10.77.157.43 (10.77.157.43)  212.750 ms  217.260 ms  214.610 ms
 
   

The following example shows how the traceroute command fails to trace the route to a remote host from the SE:

ServiceEngine# traceroute 10.0.0.1    
traceroute to 10.0.0.1 (10.0.0.1), 30 hops max, 38 byte packets
 1  10.1.1.50 (10.1.1.50)  2.022 ms  1.970 ms  2.156 ms
 2  sblab2-rtr.cisco.com (192.168.10.1)  3.955 ms 172.19.231.249 (172.19.231.249)  0.654 
ms  0.607 ms
 3  sjc22-00lab-gw1.cisco.com (172.24.115.65)  0.704 ms  0.625 ms  0.596 ms
 4  sjc20-lab-gw1.cisco.com (172.24.115.105)  0.736 ms  0.686 ms  0.615 ms
 5  sjc20-sbb5-gw1.cisco.com (128.107.180.85)  0.703 ms  0.696 ms  0.646 ms
 6  sjc20-rbb-gw5.cisco.com (128.107.180.22)  0.736 ms  0.782 ms  0.750 ms
 7  sjce-rbb-gw1.cisco.com (171.69.7.249)  1.291 ms  1.314 ms  1.218 ms
 8  sjce-corp-gw1.cisco.com (171.69.7.170)  1.477 ms  1.257 ms  1.221 ms
 9  * * *
10  * * *
.
.
.
29  * * *
30  * * *
 
   

Table 0-23 describes the fields in the traceroute command output.

Table 0-23 traceroute Command Output Fields 

Field
Description

30 hops max, 38 byte packets

Maximum TTL value and the size of the ICMP datagrams being sent.

2.022 ms 1.970 ms 2.156 ms

Total time (in milliseconds) for each ICMP datagram to reach the router or host plus the time it took for the ICMP time-exceeded message to return to the host.

An exclamation point following any of these values (for example, 20 ms) indicates that the port-unreachable message returned by the destination had a TTL of 0 or 1. Typically, this situation occurs when the destination uses the TTL value from the arriving datagram as the TTL in its ICMP reply. The reply does not arrive at the source until the destination receives a traceroute datagram with a TTL equal to the number of hops between the source and destination.

*

An asterisk (*) indicates that the timeout period (default of 5 seconds) expired before an ICMP time-exceeded message was received for the datagram.


Related Commands

Command
Description

ping

Sends echo packets for diagnosing basic network connectivity on networks.


traceroute srp

To trace the Service Routing Protocol ring, use the traceroute srp command in EXEC configuration mode.

traceroute srp name

Syntax Description

name

Name of the DHT key.


Command Defaults

No default behavior values

Command Modes

EXEC configuration mode.

Usage Guidelines

The output from the traceroute srp command tells how to reach the owner node of the DHT key by looking up the SRP route table. Along the path each node responds if there is more than one node.

In following example, only the node SN-CDSM responds to the command, and it took 0.373206 ms for it to respond.

Examples

The following example shows how to trace the route to a remote host from the SR:

ServiceRouter# traceroute srp
feb5784c704bb8eddba9c2aaa831a2806cb606d2f9205bc1d3edfe770cbaa1dc
1 SN-CDSM:9000, 0.373206 ms
  id=feb5784c704bb8eddba9c2aaa831a2806cb606d2f9205bc1d3edfe770cbaa1dc
 
   

Related Commands

Command
Description

ping srp

Pings the Service Routing Protocol ring.


traceroute6

To trace the route to a remote IPv6-enabled host, use the traceroute6 command in EXEC configuration mode.

traceroute6 ip_address

Syntax Description

ip_address

Remote IPv6-enabled host or IP address.


Command Defaults

No default behavior values

Command Modes

EXEC configuration mode.

Examples

The following example shows how to trace the route to a remote IPv6-enabled host from the SE:

ServiceEngine# traceroute6 <IP address>
 
   

Related Commands

Command
Description

ipv6

Specifies the IPv6 address of the default gateway.


transaction-log force

To force the archive or export of the transaction log, use the transaction-log force command in EXEC configuration mode.

transaction-log force {archive | export}

Syntax Description

archive

Forces the archive of the working.log file.

export

Forces the archived files to be exported to the server.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

The transaction-log force archive command causes the transaction log working.log file to be archived to the SE hard disk following the next transaction. This command has the same effect as the clear transaction-log command.

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

The transaction-log force command does not change the configured or default schedule for archive or export of transaction log files. If the archive interval is configured, in seconds, or the export interval is configured in minutes, the forced archive or export interval period is restarted after the forced operation.

If a scheduled archive or export job is in progress when a corresponding transaction-log force command is entered, the command has no effect. If a transaction-log force command is in progress when an archive or export job is scheduled to run, the forced operation is completed and the archive or export is rescheduled for the next configured interval.

Examples

The following example shows how to archive the transaction log file to the SE hard disk:

ServiceEngine# transaction-log force archive
 
   

The following example shows that the SE is configured to export its transaction logs to two FTP servers:

ServiceEngine(config)#  transaction-logs export ftp-server 10.1.1.1 mylogin mypasswd 
/ftpdirectory 
ServiceEngine(config)#  transaction-logs export ftp-server myhostname mylogin mypasswd 
/ftpdirectory
 
   

The following example shows how to export the transaction log file from the SE hard disk to an FTP server designated by the transaction-logs export ftp-server command:

ServiceEngine# transaction-log force export
 
   
 
   
 
   

Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

show statistics transaction-logs

Displays the SE transaction log export statistics.

show transaction-logging

Displays the transaction log configuration settings and a list of archived transaction log files.

transaction-logs

Configures and enables the transaction logging parameters.


transaction-logs

To configure and enable transaction logs, use the transaction-logs command in Global configuration mode. To disable transaction logs, use the no form of this command.

transaction-logs {archive {interval {seconds | every-day {at hour:minute | every hours} | every-hour {at minute | every minutes} | every-week [on weekdays at hour:minute]} | max-file-number file_number | max-file-size file_size} | ds-snapshot-counter enable | enable | export {compress | enable | ftp-server {hostname | serv_ip_addrs} login passw directory | interval {minutes | every-day {at hour:minute | every hours} | every-hour {at minute | every minutes} | every-week [on weekdays at hour:minute] | sftp-server {hostname | serv_ip_addrs} login passw directory | format {apache | custom string | extended-squid} | log-windows-domain}

no transaction-logs {archive {interval {seconds | every-day {at hour:minute | every hours} | every-hour {at minute | every minutes} | every-week [on weekdays at hour:minute]} | max-file-number file_number | max-file-size file_size} | ds-snapshot-counter enable | enable | export {compress | enable | ftp-server {hostname | serv_ip_addrs} login passw directory | interval {minutes | every-day {at hour:minute | every hours} | every-hour {at minute | every minutes} | every-week [on weekdays at hour:minute] | sftp-server {hostname | serv_ip_addrs} login passw directory | format {apache | custom string | extended-squid} | log-windows-domain}

Syntax Description

archive

Configures archive parameters.

interval

Determines how frequently the archive file is to be saved.

seconds

Frequency of archiving, in seconds. The range is from120 to 604800.

every-day

Archives using intervals of 1 day or less.

at

Specifies the local time at which to archive each day.

hour:minute

Time of day at which to archive in local time (hh:mm).

every

Specifies the interval in hours. Interval aligns with midnight.

hours

Number of hours for daily file archive.

1—Hourly
12—Every 12 hours
2—Every 2 hours
24—Every 24 hours
3—Every 3 hours
4—Every 4 hours
6—Every 6 hours
8—Every 8 hours

every-hour

Specifies the archives using intervals of 1 hour or less.

at

Sets the time to archive at each hour.

minute

Minute alignment for the hourly archive. The range is from 0 to 59.

every

Specifies the interval in minutes for hourly archive that aligns with the top of the hour.

minutes

Number of minutes for hourly archive.

10—Every 10 minutes
15—Every 15 minutes
2—Every 2 minutes
20—Every 20 minutes
30—Every 30 minutes
5—Every 5 minutes

every-week

Archives using intervals of 1 or more times a week.

on

(Optional) Sets the day of the week on which to archive.

weekdays

Weekdays on which to archive. One or more weekdays can be specified.

Fri—Every Friday
Mon—Every Monday
Sat—Every Saturday
Sun—Every Sunday
Thu—Every Thursday
Tue—Every Tuesday
Wed—Every Wednesday

at

(Optional) Sets the local time at which to archive each day.

hour:minute

Time of day at which to archive in local time (hh:mm).

max-file-number

Sets the maximum number of the archived log file.

file_number

Maximum number of the archived log file. The range is from 1 to 10000.

max-file-size

Sets the maximum archive file size.

filesize

Maximum archive file size in kilobytes. The range is from 1000 to 2000000.

ds-snapsot-counter enable

Enables the per delivery service snapshot counter.

enable

Enables the transaction log.

export

Configures file export parameters.

compress

Compresses the archived files in the gzip format before exporting.

enable

Enables the exporting of log files at the specified interval.

ftp-server

Sets the FTP server to receive exported archived files.

hostname

Hostname of the target FTP server.

serv_ip_addrs

IP address of the target FTP server.

login

User login to target FTP server.

passw

User password to target FTP server.

directory

Target directory path for exported files on FTP server.

interval

Determines how frequently the file is to be exported.

minutes

Number of minutes in the interval at which to export a file. The range is from 1 to 10080.

every-day

Specifies the exports using intervals of 1 day or less.

at

Specifies the local time at which to export each day.

hour:minute

Time of day at which to export in local time (hh:mm).

every

Specifies the interval in hours for the daily export.

hours

Number of hours for the daily export.

1—Hourly
12—Every 12 hours
2— Every 2 hours
24—Every 24 hours
3— Every 3 hours
4—Every 4 hours
6—Every 6 hours
8—Every 8 hours

every-hour

Specifies the exports using intervals of 1 hour or less.

at

Specifies the time at which to export each hour.

minute

Minute alignment for the hourly export. The range is from 0 to 59.

every

Specifies the interval in minutes that align with the top of the hour.

minutes

Number of minutes for the hourly export.

10—Every 10 minutes
15—Every 15 minutes
2—Every 2 minutes
20—Every 20 minutes
30—Every 30 minutes
5—Every 5 minutes

every-week

Specifies the exports using intervals of 1 of more times a week.

on

(Optional) Specifies the days of the week for the export.

weekdays

Weekdays on which to export. One or more weekdays can be specified.

Fri—Every Friday
Mon—Every Monday
Sat—Every Saturday
Sun—Every Sunday
Thu—Every Thursday
Tue—Every Tuesday
Wed—Every Wednesday

at

(Optional) Specifies the time of day at which to perform the weekly export.

hour:minute

Time of day at which to export in the local time (hh:mm).

sftp-server

Sets the SFTP1 server to receive exported archived files.

hostname

Hostname of the target SFTP server.

serv_ip_addrs

IP address of the target SFTP server.

login

User login to the target SFTP server (less than 40 characters).

passw

User password to the target SFTP server (less than 40 characters).

directory

Target directory path for exported files on the SFTP server.

format

Sets the format to use for the HTTP transaction log entries in the working.log file.

apache

Configures the HTTP transaction logs output to the Apache CLF2 .

custom

Configures the HTTP transaction logs output to the custom log format.

string

Quoted log format string containing the custom log format.

extended-squid

Configures the HTTP transaction logs output to the Extended Squid log format.

log-windows-domain

Logs the Windows domain with an authenticated username if available in HTTP transaction log entries.

enable

Enables the remote transaction logging.

entry-type

Specifies the type of transaction log entry.

all

Sets the SE to send all transaction log messages to the remote syslog server.

request-auth-failures

Sets the SE to log to the remote syslog server only those transactions that the SE failed to authenticate with the Authentication Server.

Note Only those authentication failures that are associated with an end user who is attempting to contact the Authentication Server are logged. The transactions in pending state (that have contacted the Authentication Server, but waiting for a response from the Authentication Server) are not logged.

facility

Configures a unique facility to create a separate log on the remote syslog host for real-time transaction log entries.

parameter

Specifies one of the following facilities:

auth—Authorization system
daemon—System daemons
kern—Kernel
local0—Local use
local1—Local use
local2—Local use
local3—Local use
local4—Local use
local5—Local use
local6—Local use
local7—Local use
mail—Mail system
news—USENET news
syslog—Syslog itself
user—User process
uucp—UUCP system

host

Configures the remote syslog server.

hostname

Hostname of the remote syslog server.

ip-address

IP address of the remote syslog server.

port

Configures the port to use when sending transaction log messages to the syslog server.

port-num

Port number to use when sending transaction log messages to the syslog server. The default is 514.

rate-limit

Configures the rate at which the transaction logger is allowed to send messages to the remote syslog server.

rate

Rate (number of messages per second) at which the transaction logger is allowed to send messages to the remote syslog server.

1 SFTP = Secure File Transfer Protocol

2 CLF = common log format


Command Defaults

archive: disabled

enable: disabled

export compress: disabled

export: disabled

file-marker: disabled

archive interval: every day, every one hour

archive max-file-size: 2,000,000 KB

export interval: every day, every one hour

format: apache

logging port port_num: 514

Command Modes

Global configuration (config) mode.

Usage Guidelines

SEs can record all errors and access activities. Each content service module on the SE provides logs of the requests that were serviced. These logs are referred to as transaction logs.

Typical fields in the transaction log are the date and time when a request was made, the URL that was requested, whether it was a cache hit or a cache miss, the type of request, the number of bytes transferred, and the source IP address. Transaction logs are used for problem identification and solving, load monitoring, billing, statistical analysis, security problems, and cost analysis and provisioning.

The translog module on the SE handles transaction logging and supports the Apache CLF, Extended Squid format, and the World Wide Web Consortium (W3C) customizable logging format.


Note For RTSP, when you choose the Repeat option from the Play menu in the Windows Media player to play media files continuously in a loop, an extra entry is logged in the transaction logs for each playback of the file. This situation occurs mostly with the WMT RTSPU protocol because of the behavior of the player.


Enable transaction log recording with the transaction-logs enable command. The transactions that are logged include HTTP and FTP. In addition, Extensible Markup Language (XML) logging for MMS-over-HTTP and MMS-over-RTSP (RTSP over Windows Media Services 9) is also supported.

When enabled, daemons create a working.log file in /local1/logs/ on the sysfs volume for HTTP and FTP transactions and a separate working.log file in /local1/logs/export for Windows Media transactions. The posted XML log file from the Windows Media Player to the SE (Windows Media server) can be parsed and saved to the normal WMT transaction logs that are stored on the SE.

The working.log file is a link to the actual log file with the timestamp embedded in its filename. When you configure the transaction-logs archive interval command, the first transaction that arrives after the interval elapses is logged to the working.log file as usual, and then actual log file is archived and a new log file is created. Only transactions subsequent to the archiving event are recorded in the new log file. The working.log file is then updated to point to the newly created log file. The transaction log archive file naming conventions are shown in Table 4-29. The SE default archive interval is once an hour every day.


Note The time stamp in the transaction log filename is in UTC and is irrespective of the time zone configured on the SE. The time stamp in the transaction log filename is the time when the file was created. The logs entries in the transaction logs are in the time zone configured on the SE.


Use the transaction-logs ds-snapshot-counter enable command to enable or disable snapshot counter transaction logs. This command is available for both SE and SR. On SE, the snapshot counter transaction log records per delivery service Storage Usage. On the SR, the snapshot counter transaction log records per delivery service Session and Bandwidth Usage.

Use the transaction-logs archive max-file-size command to specify the maximum size of an archive file. The working.log file is archived when it attains the maximum file size if this size is reached before the configured archive interval time.

Use the transaction-logs file-marker option to mark the beginning and end of the HTTP, HTTPS, and FTP proxy logs. By examining the file markers of an exported archive file, you can determine whether the FTP process transferred the entire file. The file markers are in the form of dummy transaction entries that are written in the configured log format.

The following example shows the start and end dummy transactions in the default native Squid log format.

970599034.130 0 0.0.0.0 TCP_MISS/000 0 NONE TRANSLOG_FILE_START - NONE/- -

970599440.130 0 0.0.0.0 TCP_MISS/000 0 NONE TRANSLOG_FILE_END - NONE/- -

Use the format option to format the HTTP, HTTPS, and FTP proxy log files for custom format, native Squid or Extended Squid formats, or Apache CLF.

The transaction-logs format custom command allows you to use a log format string to log additional fields that are not included in the predefined native Squid or Extended Squid formats or the Apache CLF. The log format string is a string that contains the tokens listed in Table 0-24 and mimics the Apache log format string. The log format string can contain literal characters that are copied into the log file. Two backslashes (\\) can be used to represent a literal backslash, and a backslash followed by a single quotation mark (\') can be used to represent a literal single quotation mark. A literal double quotation mark cannot be represented as part of the log format string. The control characters \t and \n can be used to represent a tab and a new line character, respectively.

Table 0-24 lists the acceptable format tokens for the log format string. The ellipsis (...) portion of the format tokens shown in this table represent an optional condition. This portion of the format token can be left blank, as in %a. If an optional condition is included in the format token and the condition is met, then what is shown in the Value column of Table 0-24 is included in the transaction log output. If an optional condition is included in the format token but the condition is not met, the resulting transaction log output is replaced with a hyphen (-). The form of the condition is a list of HTTP status codes, which may or may not be preceded by an exclamation point (!). The exclamation point is used to negate all the status codes that follow it, which means that the value associated with the format token is logged if none of the status codes listed after the exclamation point (!) match the HTTP status code of the request. If any of the status codes listed after the exclamation point (!) match the HTTP status code of the request, then a hyphen (-) is logged.

For example, %400,501 { User-Agent } i logs the User-Agent header value on 400 errors and 501 errors (Bad Request, Not Implemented) only, and %!200,304,302 { Referer } i logs the Referer header value on all requests that did not return a normal status.

The custom format currently supports the following request headers:

User-Agent

Referer

Host

Cookie

The output of each of the following Request, Referer, and User-Agent format tokens specified in the custom log format string is always enclosed in double quotation marks in the transaction log entry:

%r

% { Referer } i

% { User-Agent } i

The % { Cookie } i format token is generated without the surrounding double quotation marks, because the Cookie value can contain double quotes. The Cookie value can contain multiple attribute-value pairs that are separated by spaces. We recommend that when you use the Cookie format token in a custom format string, you should position it as the last field in the format string so that it can be easily parsed by the transaction log reporting tools. By using the format token string \'% { Cookie } i\' the Cookie header can be surrounded by single quotes (').


Note Each transaction log includes a header line that provides the Cisco Internet Streamer CDS software version and a summary line as the last line in the transaction log, which includes a summary of all the requests that appear in the transaction log.


The following command can generate the well-known Apache Combined Log Format:

transaction-log format custom " [ % { %d } t/% { %b } t/% { %Y } t:% { %H } t:% { %M } t:% { %S } t % { %z } t ] %r %s %b % { Referer } i % { User-Agent } i"

The following transaction log entry example in the Apache Combined Format is configured using the preceding custom format string:

 [ 11/Jan/2003:02:12:44 -0800 ] "GET http://www.cisco.com/swa/i/site_tour_link.gif 
HTTP/1.1" 200 3436 "http://www.cisco.com/" "Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 
5.0)"

Table 0-24 Custom Format Log Format String Values 

Format Token
Value

%a

IP address of the requesting client.

%A

IP address of the SE.

%b

Bytes sent, excluding HTTP headers.

%c

Log Entry Generation Time.

%C

Records AuthLOOKupTime|CALLOOKuptime|CacheRouterTime|OSDownload Time in microseconds.

%D

Time consumed to serve the request in microseconds.

%g

Storage URL when URL Resolve rule action is configured in Service Rule file.

%G

Source URL when URL Resolve rule action is configured in Service Rule file.

%h

Remote host (IP address of the requesting client is logged).

%H

Request protocol.

%I

Bytes received from the client.

%J

Gives the average RTT (Round trip time) for that transaction.

%K

Gives the congestion window flickers for the transaction.

%L

Prints the asset size, irrespective of the bytes transferred.

%m

Request method.

%M

MIME type of the requested asset.

%N

The network interface and bytes transferred in that interface.

%O

Bytes sent to client, including the headers.

%p

The client who set up the transport session for the request.

%q

Query string (which is preceded by a question mark (?) if a query string exists; otherwise, it is an empty string).

%r

First line of the request. The space in the first line of the request is replaced with a vertical bar (|) delimiter (for example, Get|/index.html|HTTP/1.1)

%R

Request description (Squid description codes).

%s

Status. The translog code always returns the HTTP response code for the request.

%t

Time in common log time format (or standard English format).

%T

Time consumed to serve the request in seconds (a floating point number with 3 decimal places).

%u

URL path requested, including query strings.

%U

URL path requested, not including query strings.

%V

Value of the host request header field reported if the host appeared in the request. If the host did not appear in the host request header, the IP address of the server specified in the URL is reported.

%X

Connection status when the response is completed. The %X field has the following possible values:

X-Connection aborted before the response completed.

+ -Connection may be kept alive after the response is sent.

- -Connection is closed after the response is sent.

%Z

Print the request received time stamp in milliseconds; otherwise, the request received time stamp is in seconds.

%{Header-
Field}i

Any request header. Replace the Header-Field with the actual header field you want to log; for example, %{Cache-Control}i.

Note All client request headers are only logged on the edge SE.


Sanitizing Transaction Logs

Use the sanitized option to disguise the IP address of clients in the transaction log file. The default is that transaction logs are not sanitized. A sanitized transaction log disguises the network identity of a client by changing the IP address in the transaction logs to 0.0.0.0.

The no form of this command disables the sanitize feature. The transaction-logs sanitize command does not affect the client IP (%a) value associated with a custom log format string that is configured with the CLI (configured with the transaction-logs format custom string command in Global configuration mode in which the string is the quoted log format string that contains the custom log format). To hide the identity of the client IP in the custom log format, either hard code 0.0.0.0 in the custom log format string or exclude the %a token, which represents the client IP, from the format string.

Exporting Transaction Log Files

To facilitate the postprocessing of cache log files, you could export transaction logs to an external host.

This feature allows log files to be exported automatically by FTP to an external host at configurable intervals. The username and password used for FTP are configurable. The directory to which the log files are uploaded is also configurable.

The log files automatically have the following naming convention:

Module name

Host IP address

Date

Time

File generation number

For example, the filename for a Web Engine access log would be the following:

we_accesslog_apache_192.0.2.22_20091207_065624_00001
 
   

where we_accesslog_apache is the module name, 192.0.2.22 is the IP address of the device, 20091207 is the date of the log file (December 7, 2009), and 065624_00001 is the file generation number. The file generation number ranges from 00001 to 99999.


Note WMT logs have no .txt extension in the filename.


Exporting and Archiving Intervals

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

The transaction-logs archive interval command in Global configuration mode allows the administrator to specify when the working.log file is archived.

The transaction-logs export interval command in Global configuration mode allows the administrator to specify when the archived transaction logs are exported.

The following limitations apply:

When the interval is scheduled in units of hours, the value must divide evenly into 24. For example, the interval can be every 4 hours, but not every 5 hours.

When the interval is scheduled in units of minutes, the value must divide evenly into 60.

Only the more common choices of minutes are supported. For example, the interval can be 5 minutes or 10 minutes, but not 6 minutes.

Selection of interval alignment is limited. If an interval is configured for every 4 hours, it aligns with midnight. It cannot align with 12:30 or with 7 a.m.

Feature does not support different intervals within a 24-hour period. For example, it does not support an interval that is hourly during regular business hours and then every 4 hours during the night.

Transaction Log Archive Filenaming Convention

The archive transaction log file is named as follows for HTTP and WMT caching:

celog_10.1.118.5_20001228_235959.txt
 
   
mms_export_10.1.118.5_20001228_235959
 
   

If the export compress feature is enabled when the file is exported, then the file extension is .gz after the file is compressed for the export operation, as shown in the following example:

celog_10.1.118.5_20001228_235959.txt.gz
 
   
mms_export_10.1.118.5_20001228_235959.gz
 
   

Table 0-25 describes the name elements.

Table 0-25 Archive Log Name Element Descriptions 

Sample of Element
Description

acqdist_

Acquisition and distribution archive log file.

cseaccess

Cisco Streaming Engine archive file.

tftp_server_

TFTP server archive file.

webengine_apache

Web Engine Apache transaction logging format log file.

webengine_clf

Web Engine custom transaction logging format log file.

webengine_extsquid

WebEngine extended-squid transaction logging format log file.

fms_access

Flash Media Streaming transaction log file.

fms_authorization

Flash Media Streaming transaction log for authorization and diagnostic logs.

fms_wsl

Flash Media Streaming transaction log for wholesale licensing.

movie-streamer

Movie Streamer transaction log file.

cache_content

Content Access Layer transaction log file.

authsvr

CDS Authorization Server transaction log file.

mms_export_

Standard Windows Media Services 4.1 caching proxy server archive file.

mms_export_e_wms_41_

Extended Windows Media Services 4.1 caching proxy server archive file.

mms_export_wms_90_

Standard Windows Media Services 9.0 caching proxy server archive file.

mms_export_e_wms_90_

Extended Windows Media Services 9.0 caching proxy server archive file.

10.1.118.5_

IP address of the SE creating the archive file.

20001228_

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

235959

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


Table 0-26 lists the directory names and the corresponding examples of the archive filenames.

Table 0-26 Archive Filename Examples and Directories 

Directory
Archive Filename

logs/acqdist

acqdist_10.1.94.4_20050315_001545

logs/cisco-streaming-engine

cseaccess10.1.94.4__050315000.log

logs/tftp_server

tftp_server_10.1.94.4_20050315_001545

logs/webengine_apache

we_accesslog_apache_114.0.92.27_20110322_213143_00001

logs/webengine_clf

we_accesslog_clf_114.0.92.27_20110322_213143_00004

logs/webengine_extsquid

we_accesslog_extsqu_114.0.92.27_20110322_213143_00072

logs/fms_access

fms_access_10.1.94.4_20110323_210446_00001

logs/fms_authorization

fms_auth_10.1.94.4_20110323_210446_00001

logs/fms_wsl

fms_wsl_10.1.94.4_20110323_210446_00001

logs/movie-streamer

movie-streamer_10.1.94.4_20110323_210446_00001

logs/cache_content

cache_content_10.1.94.4_20110323_210446_00001

logs/authsvr

authsvr_10.1.94.4_20110323_210446_00001

logs/export

mms_export_18.0.101.116_20110318_121111_00120

logs/export/extended-wms-41

mms_export_e_wms_41_18.0.101.116_20110318_012847_00001

logs/wms-90

mms_export_wms_90_18.0.101.116_20110318_012847_00001

logs/export/extended-wms-90

mms_export_e_wms_90_18.0.101.116_20110318_012847_00001


Compressing Archive Files

The transaction-logs export compress option compresses an archive into a gzip file format before exporting it. Compressing the archive file uses less disk space on both the SE and the FTP export server. The compressed file uses less bandwidth when transferred. The archive filename of the compressed file has the extension .gz.

Exporting Transaction Logs to External FTP Servers

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

FTP server IP address or the hostname

The SE translates the hostname with a DNS lookup and then stores the IP address in the configuration.

FTP user login and user password

Path of the directory where transferred files are written

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

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

Exporting Transaction Logs to External SFTP Servers

Use the transaction-logs export sftp-server option to export transaction logs. First enable the feature and configure the Secure File Transfer Protocol (SFTP) server parameters. The following information is required for each target SFTP server:

SFTP server IP address or the hostname

The SE translates the hostname with a DNS lookup and then stores the IP address in the configuration.

SFTP user login and user password

Path of the directory where transferred files are written

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

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

Receiving a Permanent Error from the External FTP Server

A permanent error (Permanent Negative Completion Reply, RFC 959) occurs when the FTP command to the server cannot be accepted, and the action does not take place. Permanent errors can be caused by invalid user logins, invalid user passwords, and attempts to access directories with insufficient permissions.

When an FTP server returns a permanent error to the SE, the export is retried at 10-minute intervals or sooner if the configured export interval is sooner. If the error is a result of a misconfiguration of the transaction-logs export ftp server command, then re-enter the SE parameters to clear the error condition. The show statistics transaction-logs command displays the status of logging attempts to export servers.

The show statistics transaction-logs command shows that the SE failed to export archive files.

The transaction-logs format command has three options: extended-squid, apache, and custom.

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

Configuring Intervals Between 1 Hour and 1 Day

The archive or export interval can be set for once a day with a specific time stamp. It can also be set for hour frequencies that align with midnight. For example, every 4 hours means archiving occurs at 0000, 0400, 0800, 1200, and 1600. It is not possible to archive at half-hour intervals such as 0030, 0430, or 0830. The following intervals are acceptable: 1, 2, 3, 4, 6, 8, 12, and 24.

Configuring Intervals of 1 Hour or Less

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

Configuring Export Interval on Specific Days

The export interval can be set for specific days of the week at a specific time. One or more days can be specified. The default time is midnight.

Archived logs are automatically deleted when free disk space is low. It is important to select an export interval that exports files frequently enough so that files are not automatically removed before export.

Monitoring HTTP Request Authentication Failures in Real Time

HTTP transaction log messages are sent to a remote syslog server so that you can monitor the remote syslog server for HTTP request authentication failures in real time. This real-time transaction log allows you to monitor transaction logs in real time for particular errors such as HTTP request authentication errors. The existing transaction logging to the local file system remains unchanged.


Note Because system logging (syslog) occurs through UDP, the message transport to the remote syslog host is not reliable.


Summary Line

The transaction logs include a summary line as the last line in the transaction log, which includes a summary of all the requests that appear in the transaction log.

Examples

The following example shows how to configure an FTP server:

ServiceEngine(config)# transaction-logs export ftp-server 10.1.1.1 mylogin mypasswd 
/ftpdirectory 
 
   
ServiceEngine(config)# transaction-logs export ftp-server myhostname mylogin mypasswd 
/ftpdirectory
 
   

The following example shows how to delete an FTP server:

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

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

ServiceEngine(config)# no transaction-logs export enable
 
   

The following example shows how to change a username, password, or directory:

ServiceEngine(config)# transaction-logs export ftp-server 10.1.1.1 mynewname mynewpass 
/newftpdirectory 

Note For security reasons, passwords are never displayed.


The following example shows how to restart the export of archive transaction logs:

ServiceEngine(config)# transaction-logs export ftp-server 172.16.10.5 goodlogin pass 
/ftpdirectory
 
   

The following example shows how to delete an SFTP server from the current configuration:

ServiceEngine(config)# no transaction-logs export sftp-server sftphostname
 
   

The following examples show how to configure the archiving intervals:

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

The following example shows that the SE has failed to export archive files:

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

The following example shows how to correct a misconfiguration:

ServiceEngine(config)# transaction-logs export ftp-server 10.1.1.1 goodlogin pass 
/ftpdirectory
 
   

The working.log file and archived log files are listed for HTTP and WMT.

The following example shows how to export transaction logs to an SFTP server:

ServiceEngine(config)# transaction-logs export sftp-server 10.1.1.100 mylogin mypasswd 
/mydir
 
   

The following example shows how to archive every 4 hours and align with the midnight local time (0000, 0400, 0800, 1200, 1600, and 2000):

ServiceEngine(config)# transaction-logs archive interval every-day every 4
 
   

The following example shows how to export once a day at midnight local time:

ServiceEngine(config)# transaction-logs export interval every-day every 24
 
   

The following example shows how to configure export intervals:

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

Related Commands

Command
Description

clear

Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.

show statistics transaction-logs

Displays the SE transaction log export statistics.

show transaction-logging

Displays the transaction log configuration settings and a list of archived transaction log files.

transaction-log force

Forces the archive or export of the transaction log.


type

To display the contents of a file, use the type command in EXEC configuration mode.

type filename

Syntax Description

filename

Name of file.


Command Defaults

None

Command Modes

EXEC configuration mode.

Usage Guidelines

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

Examples

The following example shows how to display the syslog file on the SE:

ServiceEngine# type /local1/syslog.txt
 
   
Jan 10 22:02:46 (none) populate_ds: %SE-CLI-5-170050: Cisco Internet Streamer CDS Software 
starts booting
Jan 10 22:02:47 (none) create_etc_hosts.sh: %SE-CLI-5-170051: HOSTPLUSDOMAIN: NO-HOSTNAME
Jan 10 22:02:47 NO-HOSTNAME : %SE-CLI-5-170053: Recreated etc_hosts (1, 0) 
Jan 10 22:02:48 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330082: [ CLI_VER_NTP ] requests stop 
service ntpd 
Jan 10 22:02:49 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330082: [ ver_tvout ] requests stop 
service tvoutsvr 
Jan 10 22:02:50 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330084: [ ver_rtspg ] requests restart 
service rtspg 
Jan 10 22:02:50 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330082: [ ver_iptv ] requests stop 
service sbss 
Jan 10 22:02:51 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330080: [ ver_telnetd ] requests start 
service telnetd 
Jan 10 22:02:52 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330082: [ ver_wmt ] requests stop 
service wmt_mms 
Jan 10 22:02:53 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330082: [ ver_wmt ] requests stop 
service wmt_logd 
Jan 10 22:02:55 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330082: [ Unknown ] requests stop 
service mcast_sender 
Jan 10 22:02:55 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330082: [ Unknown ] requests stop 
service mcast_receiver 
Jan 10 22:02:56 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330024: Service 'populate_ds' exited 
normally with code 0 
Jan 10 22:02:56 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330040: Start service 'parser_server' 
using: '/ruby/bin/parser_server' with pid: 1753 
Jan 10 22:02:56 NO-HOSTNAME Nodemgr: %SE-NODEMGR-5-330040: Start service 
'syslog_bootup_msgs' using: '/ruby/bin/syslog_bootup_msgs' with pid: 
1754 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4>Linux version 2.4.16 
(cnbuild@builder2.cisco.com) (gcc version 3.0.4) # 1 
SMP Fri Jan 7 19:26:58 PST 2005 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <6>setup.c: handling 
flash window at [ 15MB..16MB) 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <6>BIOS-provided 
physical RAM map: 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4> BIOS-e820: 
0000000000000000 - 000000000009ec00 (usable) 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4> BIOS-e820: 
000000000009ec00 - 00000000000a0000 (reserved) 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4> BIOS-e820: 
00000000000e0800 - 0000000000100000 (reserved) 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4> BIOS-e820: 
0000000000100000 - 0000000000f00000 (usable) 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4> BIOS-e820: 
0000000000f00000 - 0000000001000000 (reserved) 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4> BIOS-e820: 
0000000001000000 - 0000000010000000 (usable) 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4> BIOS-e820: 
00000000fff00000 - 0000000100000000 (reserved) 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <6>setup.c: reserved 
bootmem for INITRD_START = 0x6000000, INITRD_SIZE = 117
09348 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4>On node 0 totalpages: 
65536 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4>zone(0): 4096 pages. 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4>zone(1): 61440 pages. 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4>zone(2): 0 pages. 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4>Local APIC disabled 
by BIOS -- reenabling. 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4>Found and enabled 
local APIC! 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <4>Kernel command line: 
root=/dev/ram ramdisk_size=100000 ramdisk_start=0x60
00000 console=ttyS0,9600n8 
Jan 10 22:02:56 NO-HOSTNAME syslog_bootup_msgs: %SE-SYS-5-900001: <6>Initializing CPU# 0 
--More--

Related Commands

Command
Description

cpfile

Copies a file.

dir

Displays the files in a directory in a long-list format.

lls

Displays a long list of directory names.

ls

Lists the files and subdirectories in a directory.

mkfile

Makes a file (for testing).


type-tail

To view a specified number of lines of the end of a log file or to view the end of the file continuously as new lines are added to the file, use the type-tail command in EXEC configuration mode.

type-tail filename [line | follow]

Syntax Description

filename

File to be examined.

line

(Optional) The number of lines from the end of the file to be displayed (the range is 1 to 65535).

follow

(Optional) Displays the end of the file continuously as new lines are added to the file.


Command Defaults

The default is ten lines shown.

Command Modes

EXEC configuration mode.

Usage Guidelines

This command allows you to monitor a log file by letting you view the end of the file. You can specify the number of lines at the end of the file that you want to view, or you can follow the last line of the file as it continues to log new information. To stop the last line from continuously scrolling, press Ctrl-C.

Examples

The following example shows the list of log files in the /local1 directory:

stream-ServiceEngine# ls /local1
WS441
Websense
WebsenseEnterprise
Websense_config_backup
WsInstallLog
badfile.txt
codecoverage
core.stunnel.5.3.0.b100.cnbuild.5381
core_dir
crash
crka.log
cse_live
cse_vod
dbdowngrade.log
dbupgrade.log
downgrade
errorlog
http_authmod.unstrip
index.html
logs
lost+found
netscape-401-proxy
netscape-401-proxy1
netscape-dump
newwebsense
oldWsInstallLog
preload_dir
proxy-basic1
proxy1
proxy2
proxy3
proxy4
proxy5
proxy6
proxy7
proxy8
proxyreply
proxyreply-407
real_vod
ruby.bin.cli_fix
ruby.bin.no_ws_fix
ruby.bin.ws_edir_fix
sa
service_logs
smartfilter
smfnaveen
superwebsense
syslog.txt
syslog.txt.1
syslog.txt.2
temp
two.txt
url.txt
urllist.txt
var
vpd.properties
websense.pre-200
webtarball44
webtarball520
wmt_vod
ws_upgrade.log
 
   

The following example shows how to display the last ten lines of the syslog.txt file. In this example, the number of lines to display is not specified; however, ten lines is the default.

stream-ServiceEngine# type-tail /local1/syslog.txt
Oct  8 21:49:15 stream-ce syslog:(26830)TRCE:input_serv.c:83-> select_with
return 0, ready = 0
Oct  8 21:49:15 stream-ce syslog:(26832)TRCE:al_master.c:246-> select_with
return 0, ready = 0
Oct  8 21:49:15 stream-ce syslog:(26832)TRCE:in_mms.c:1747-> tv = NULL
Oct  8 21:49:17 stream-ce syslog:(26830)TRCE:input_serv.c:83-> select_with
return 0, ready = 0
Oct  8 21:49:17 stream-ce syslog:(26832)TRCE:al_master.c:246-> select_with
return 0, ready = 0
Oct  8 21:49:17 stream-ce syslog:(26832)TRCE:in_mms.c:1747-> tv = NULL
Oct  8 21:49:19 stream-ce syslog:(26830)TRCE:input_serv.c:83-> select_with
return 0, ready = 0
Oct  8 21:49:19 stream-ce syslog:(26832)TRCE:al_master.c:246-> select_with
return 0, ready = 0
Oct  8 21:49:19 stream-ce syslog:(26832)TRCE:in_mms.c:1747-> tv = NULL
Oct  8 21:49:21 stream-ce syslog:(26830)TRCE:input_serv.c:83-> select_with
return 0, ready = 0
 
   

The following example shows how to display the last 20 lines of the syslog.text file:

stream-ServiceEngine# type-tail /local1/syslog.txt 20
Oct  8 21:49:11 stream-ce syslog:(26832)TRCE:al_master.c:246-> select_with
return 0, ready = 0
Oct  8 21:49:11 stream-ce syslog:(26832)TRCE:in_mms.c:1747-> tv = NULL
Oct  8 21:49:13 stream-ce syslog:(26830)TRCE:input_serv.c:83-> select_with
return 0, ready = 0
Oct  8 21:49:13 stream-ce syslog:(26832)TRCE:al_master.c:246-> select_with
return 0, ready = 0
Oct  8 21:49:13 stream-ce syslog:(26832)TRCE:in_mms.c:1747-> tv = NULL
Oct  8 21:49:15 stream-ce syslog:(26830)TRCE:input_serv.c:83-> select_with
return 0, ready = 0
Oct  8 21:49:15 stream-ce syslog:(26832)TRCE:al_master.c:246-> select_with
return 0, ready = 0
Oct  8 21:49:15 stream-ce syslog:(26832)TRCE:in_mms.c:1747-> tv = NULL
Oct  8 21:49:17 stream-ce syslog:(26830)TRCE:input_serv.c:83-> select_with
return 0, ready = 0
Oct  8 21:49:17 stream-ce syslog:(26832)TRCE:al_master.c:246-> select_with
return 0, ready = 0
Oct  8 21:49:17 stream-ce syslog:(26832)TRCE:in_mms.c:1747-> tv = NULL
Oct  8 21:49:19 stream-ce syslog:(26830)TRCE:input_serv.c:83-> select_with
return 0, ready = 0
Oct  8 21:49:19 stream-ce syslog:(26832)TRCE:al_master.c:246-> select_with
return 0, ready = 0
Oct  8 21:49:19 stream-ce syslog:(26832)TRCE:in_mms.c:1747-> tv = NULL
Oct  8 21:49:21 stream-ce syslog:(26830)TRCE:input_serv.c:83-> select_with
return 0, ready = 0
Oct  8 21:49:21 stream-ce syslog:(26832)TRCE:al_master.c:246-> select_with
return 0, ready = 0
Oct  8 21:49:21 stream-ce syslog:(26832)TRCE:in_mms.c:1747-> tv = NULL
Oct  8 21:49:23 stream-ce syslog:(26830)TRCE:input_serv.c:83-> select_with
return 0, ready = 0
Oct  8 21:49:23 stream-ce syslog:(26832)TRCE:al_master.c:246-> select_with
return 0, ready = 0
Oct  8 21:49:23 stream-ce syslog:(26832)TRCE:in_mms.c:1747-> tv = NULL
 
   

The following example follows the file as it grows:

stream-ServiceEngine# type-tail /local1/syslog.txt ?
  <1-65535>  The numbers of lines from end
  follow     Follow the file as it grows