Table Of Contents
show hosts
show http
show http-authcache
show https
show icap
show icp
show inetd
show interface
show inventory
show ip access-list
show ip routes
show ldap
show logging
show mediafs
show memory
show multicast
show network-filesystem
show ntlm
show ntp
show pac-file-server
show pre-load
show processes
show programs
show proxy-auto-config
show proxy-protocols
show radius-server
show rtsp
show rule
show running-config
show services
show snmp
show ssh
show standby
show startup-config
show statistics access-lists 300
show statistics acquirer
show statistics authentication
show statistics bandwidth
show statistics bypass
show statistics cdnfs
show statistics cfs
show statistics cifs-server
show statistics content-distribution-network
2
show hosts
To view the hosts on your Content Engine, use the show hosts EXEC command.
show hosts
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Examples
The show hosts command lists the name servers and their corresponding IP addresses. It also lists the hostnames, their corresponding IP addresses, and their corresponding aliases (if applicable) in a host table summary.
Table 2-74 describes the fields shown in the show hosts display.
Table 2-74 show hosts Field Descriptions
Field
|
Description
|
Domain names
|
Domain names used by the WAE to resolve the IP address.
|
Name Server(s)
|
IP address of the DNS name server or servers.
|
Host Table
|
hostname
|
FQDN (hostname and domain) of the current device.
|
inet address
|
IP address of the current host device.
|
aliases
|
Name configured for the current device based on the host global configuration command.
|
show http
To display HTTP caching parameters, use the show http EXEC command.
show http {age-mult | all | anonymizer | append {host-header | proxy-auth-header | via-header |
www-auth-header | x-forwarded-for-header} | authenticate-strip-ntlm | authentication |
bandwidth | cache-authenticated {all | basic | ntlm} | cache-cookie | cache-on-abort |
cache-vary-user-agent | client-no-cache-request | cluster | custom-error-page [message |
configured] destination-port | dns-cache | fast-response | methods [supported |
unsupported] | monitor [url url] | object | persistent-connections | proxy | request-header |
reval-each- request | serve-ims | smart-range | strict-request-content-length-checking |
tcp-keepalive | ttl}
Syntax Description
age-mult
|
Displays HTTP/1.0 caching heuristic modifiers.
|
all
|
Displays all HTTP-related caching configurations.
|
anonymizer
|
Displays the HTTP anonymizer configuration.
|
append
|
Displays the configuration of HTTP headers appended by the Content Engine.
|
host-header
|
Displays the Host header configuration.
|
proxy-auth-header
|
Displays the Proxy-Authorization header configuration.
|
via-header
|
Displays the Via header configuration.
|
www-auth-header
|
Displays the WWW-Authorization header configuration.
|
x-forwarded-for-header
|
Displays the X-Forwarded-For header configuration.
|
authenticate-strip-ntlm
|
Displays the NT LAN Manager (NTLM) authentication header configuration.
|
authentication
|
Displays HTTP authentication parameters.
|
bandwidth
|
Displays HTTP bandwidth settings for pre-positioned HTTP traffic.
|
cache-authenticated
|
Displays the configuration for caching of authenticated web objects.
|
all
|
Displays the configuration for caching of all authenticated web objects.
|
basic
|
Displays the configuration for caching of basic authenticated web objects.
|
ntlm
|
Displays the configuration for caching of NTLM authenticated web objects.
|
cache-cookie
|
Displays the configuration for caching of web objects with associated cookies.
|
cache-on-abort
|
Displays the cache-on-abort configuration.
|
cache-vary-user-agent
|
Displays the configuration for caching of objects with Vary headers.
|
client-no-cache-request
|
Displays the configuration for managing of no-cache requests.
|
cluster
|
Displays the configuration of the cache cluster.
|
custom-error-page
|
Displays the information about custom error pages.
|
message
|
(Optional) Message; see Table 2-5.
|
configured
|
(Optional) Displays the errors for which custom error pages are configured.
|
destination-port
|
Displays the restrictions on HTTP destination ports.
|
dns-cache
|
Displays the DNS cache configuration and status.
|
fast-response
|
Displays the configuration of the fast HTTP client response.
|
methods
|
Displays supported and unsupported HTTP request methods.
|
supported
|
(Optional) Displays supported HTTP request methods. The supported methods include both default and configured HTTP request methods.
|
unsupported
|
(Optional) Displays HTTP request methods that are not supported but used in HTTP requests received by the Content Engine.
|
monitor
|
(Optional) Displays information about all the monitored URLs.
|
url
|
(Optional) Displays monitoring information for a specified URL.
|
url
|
URL for which monitoring information is displayed.
|
object
|
Displays the configuration of HTTP objects.
|
persistent-connections
|
Displays the configuration of persistent connections.
|
proxy
|
Displays the proxy-mode configuration.
|
request-header
|
Display the HTTP request header configuration.
|
reval-each-request
|
Displays the revalidation configuration for every request.
|
serve-ims
|
Displays the configuration of if-modified-since requests.
|
smart-range
|
Displays smart Range request configurations.
|
strict-request-content- length-checking
|
Displays the strict request content length checking configuration.
|
tcp-keepalive
|
Displays the TCP keepalive configuration.
|
ttl
|
Displays the Time To Live for objects in the cache.
|
Defaults
No default behavior or values
Command Modes
EXEC
Examples
The following example lists the configuration and status of HTTP:
ContentEngine# show http all
Basic authenticated objects are not cached.
NTLM authenticated objects are not cached.
HTTP heuristic age-multipliers: text 30% binary 60%
Serve-IMS without revalidation if...
Text object is less than 50% of max age
Binary object is less than 80% of max age
Objects with associated cookies are not cached
Client no-cache requests are retrieved from the origin server
Cache on abort feature is disabled
Objects will always continue to be cached on a client abort
Maximum threshold is disabled
Minimum threshold is disabled
Percent threshold is disabled
Maximum time to live in days: text 3 binary 7
Minimum time to live for all objects in minutes: 5
Objects are not revalidated on each request
Not servicing incoming proxy mode connections.
Not using outgoing proxy mode.
Monitor Interval for Outgoing Proxy Servers is 60 seconds
Timeout period for probing Outgoing Proxy Servers is 300000 microseconds
Use of Origin Server upon Proxy Failures is disabled.
Persistent connection is enabled and set to all
Persistent connection timeout is 600 seconds
WWW-Authenticate headers containing NTLM authentication are preserved
Append Via-header is disabled
Append x-forward header is disabled
No host configured to receive Proxy-Authorization header
No host configured to receive WWW-Authorization header
Maximum size of a cacheable object is unlimited
Requested Object URL validation is enabled
HTTP anonymizer is disabled
Healing client is disabled
Timeout for responses = 0 seconds
Max number of misses allowed before stop healing mode = 0
Port number for healing request/response = 14333
Http-port to forward http request to healing server = 80
Authentication Header : Based on URL syntax
Authentication Cache Timeout : 480 (minutes)
Authentication Cache Maximum entries: 8000
Strict request content length checking disabled
The show http cluster command displays the values defined by the http max-delay, misses, http-port, and heal-port options. The following example shows that the values are set to 0 and the healing client is disabled:
ContentEngine(config)# show http cluster
Healing client is disabled
Timeout for responses = 10 seconds
Max number of misses allowed before stop healing mode = 0
Port number for healing request/response = 14333
Http-port to forward http request to healing server = 80
The following example shows that the healing client is enabled:
ContentEngine(config)# show http cluster
Healing client is enabled
Timeout for responses = 10 seconds
Max number of misses allowed before stop healing mode = 999
Port number for healing request/response = 14333
Http-port to forward http request to healing server = 80
The following example shows the IP address and port numbers of the HTTP incoming and outgoing proxy modes:
ContentEngine# show http proxy
Servicing Proxy mode HTTP connections on port: 8080
Directing request to proxy server at 10.1.1.1 port 7777
The following example displays a list of supported and unsupported HTTP request methods. In the show http methods command output, request methods supported by default appear in parentheses.
ContentEngine# show http methods
Request headers supported for HTTP:
------------------------------------
(Default methods shown in-between braces)
(GET), (POST), (HEAD), (PUT), (TRACE)
(DELETE), (OPTIONS), (CONNECT), (PURGE), (NETHCMD)
(PROPFIND), (PROPPATCH), (MKCOL), (COPY), (DELETE)
(MOVE), (LOCK), (UNLOCK), (BIND), (BMOVE)
(BCOPY), (BDELETE), (BPROPFIND), (BPROPPATCH), (SEARCH)
(SUBSCRIBE), (UNSUBSCRIBE), (POLL), (SUBSCRIPTIONS), (ACL)
Unsupported Request Methods Hit :
------------------------------------
(Sorted in more recently used order)
The show http monitor EXEC command is available in the ACNS 5.2.3 software and later releases to enable you to display a list of monitored URLs, including the interval and acceptable delay setting for each monitored URL. The following example shows the output of the show http monitor EXEC command:
ContentEngine# show http monitor
Monitor URL: http://www.abc.com/
Monitor URL: http://www.abccorp.com/
Related Commands
clear statistics http
http
proxy-protocols
show statistics http
show http-authcache
To display the authentication cache configuration information, use the show http-authcache EXEC command.
show http-authcache
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Examples
The following example displays the authentication cache information:
ContentEngine# show http-authcache
Groups cache : size (2000), no-of-items (0), used-memory (0)
Total groups iterated (0)
Related Commands
clear statistics http-authcache
show statistics http-authcache
show https
To display HTTPS proxy status and port policies, use the show https EXEC command.
show https {all | cert [cert-name] | certgroup [certchain_name] | destination-port | key
[key_name] | proxy | server [name]}
Syntax Description
all
|
Displays all HTTPS configuration parameters.
|
cert
|
Displays the HTTPS certificate information.
|
cert-name
|
(Optional) Name of the certificate.
|
certgroup
|
Displays the HTTPS certificate chain information.
|
certchain-name
|
(Optional) Name of the certificate chain.
|
destination-port
|
Displays destination port restrictions.
|
key
|
Displays the HTTPS private key information.
|
key_name
|
(Optional) Name of the private key.
|
proxy
|
Displays the proxy-mode configuration.
|
server
|
Displays the HTTPS server caching configuration.
|
name
|
(Optional) Name of the HTTPS server.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
The ACNS software offers the capability to cache HTTPS information. The Content Engine can cache key and certificate information and store it securely. You can also configure your own HTTPS server, which can be located at a central location and which can then be accessed from remote sites, using the secure connection offered by the Content Engine.
Use the show https command command to display all HTTPS certificate and key information and HTTPS server configuration parameters.
Examples
The following example displays all HTTPS configuration parameters:
ContentEngine# show https all
Not servicing incoming proxy mode connections.
Not using outgoing proxy mode.
Monitor Interval for Outgoing Proxy Servers is 60 seconds
Timeout period for probing Outgoing Proxy Servers is 300000 microseconds
Use of Origin Server upon Proxy Failures is disabled.
Destination port restrictions:
HTTPS caching certificate information:
HTTPS caching certificate group information:
HTTPS caching private key information:
1. Private Key Name : key1
Display all https server caching information:
1: name name, host <not configured>, disabled
The following example displays the HTTPS proxy configuration details:
ContentEngine# show https proxy
Configured Proxy mode HTTPS connections on ports: 9090
Primary Proxy Server: 10.77.155.221 port 8088 Failed
Monitor Interval for Outgoing Proxy Servers is 20 seconds
Timeout period for probing Outgoing Proxy Servers is 3000 microseconds
Use of Origin Server upon Proxy Failures is enabled.
Related Commands
https destination-port
https proxy
https server
proxy-protocols
show statistics https requests
show icap
To display ICAP configuration details, use the show icap EXEC command.
show icap [service service_name | vector-point {reqmod-postcache | reqmod-precache |
respmod-precache}]
Syntax Description
service
|
(Optional) Displays the configurations for the specified service.
|
service_name
|
Name of the service.
|
vector-point
|
(Optional) Displays the service information at the specified vectoring point.
|
reqmod-postcache
|
Displays information about the requests modified by the ICAP server and cached by the Content Engine.
|
reqmod-precache
|
Displays information about the requests modified as they are sent from the Content Engine to the ICAP server on their way to the origin server.
|
respmod-precache
|
Displays information about responses modified before they are stored in the cache by the Content Engine.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
Use the show icap EXEC command to display the current ICAP configuration for the Content Engine. The command output shows the status of the enabled ICAP features, the service definitions, a list of vectoring points, and an ordered list of ICAP services.
To display the definition and status of a specific ICAP service that is configured on the Content Engine, use the show icap service service_name EXEC command.
To display an ordered list of configured ICAP services and their status, use the show icap vector-point vector-point-name EXEC command.
Examples
The following example displays the ICAP configuration for the Content Engine:
ICAP global configurations
==========================
ICAP bypass Streaming content: ENABLED
ICAP rescan cached objects on service update: ENABLED
ICAP service configurations
===========================
----------------------------------------------
Configurations for service test
----------------------------------------------
Load Balancing Scheme: Weighted-load
Error handling scheme: Send client error
Vectoring points registered:
reqmod-precachereqmod-postcacherespmod-precache
server URL: icap://10.1.1.1:1344/test-icap
----------------------------------------------
Configurations for service service
----------------------------------------------
Load Balancing Scheme: round-robin
Error handling scheme: Bypass
Vectoring points registered:
----------------------------------------------
Configurations for service servforicap
----------------------------------------------
Load Balancing Scheme: round-robin
Error handling scheme: Bypass
Vectoring points registered:
server URL: icap://1.2.3.4/servforicap
Related Commands
icap service
show statistics icap
show icp
To display the Internet Cache Protocol (ICP) client, root, or server information, use the show icp EXEC command.
show icp {client | root | server}
Syntax Description
client
|
Displays the ICP client detailed information.
|
root
|
Displays the ICP brief client/server information.
|
server
|
Displays the ICP server detailed information.
|
Defaults
No default behavior or values
Command Modes
EXEC
Examples
The following examples of show icp commands list the cache parameters of the client, root, and client/server root, respectively:
ContentEngine# show icp client
max wait for replies = 2 seconds
remove from wait list after 20 failures
Number of remote servers = 0 "
ContentEngine# show icp root
max wait for replies = 2 seconds
remove from wait list after 20 failures
Number of remote servers = 0
Number of remote clients = 0
ContentEngine# show icp server
HTTP proxy server for ICP on port 3128
Related Commands
icp client
icp server
show inetd
To display the status of TCP/IP services, use the show inetd EXEC command.
show inetd
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Examples
The following example displays the enabled or disabled status of TCP/IP services:
ContentEngine# show inetd
Inetd service configurations:
Related Commands
inetd
show interface
To display the hardware interface information, use the show interface EXEC command.
show interface {FastEthernet slot/port | FibreChannel slot/port | GigabitEthernet slot/port | ide
control_num | PortChannel port-num | scsi device_num | Standby group_num | usb}
Syntax Description
FastEthernet
|
Displays the Fast Ethernet interface device information.
|
slot/port
|
Slot and port number for the Fast Ethernet interface. The slot range is 0-3; the port range is 0-3. The slot number and port number are separated with a forward slash character (/).
|
FibreChannel
|
Displays the Fibre Channel interface device information.
|
slot/port
|
Slot and port number for the Fibre Channel interface. The slot range is 0-0; the port range is 0-0. The slot number and port number are separated with a forward slash character (/).
|
GigabitEthernet
|
Displays the Gigabit Ethernet interface device information (only on suitably equipped systems).
|
slot/port
|
Slot and port number for the Gigabit Ethernet interface. The slot range is 0-3; the port range is 0-3. The slot number and port number are separated with a forward slash character (/).
|
ide
|
Displays the Integrated Drive Electronics (IDE) interface device information.
|
control_num
|
IDE controller number (0-1).
|
PortChannel
|
Displays the port-channel interface device information.
|
port-num
|
Port number for the port-channel interface (1-2).
|
scsi
|
Displays the SCSI interface device information.
|
device_num
|
SCSI device number (0-7).
|
Standby
|
Displays the standby group information.
|
group_num
|
Standby group number (1-4).
|
usb
|
Displays the Universal Serial Bus (USB) interface device information.
|
Defaults
No default behavior or values
Command Modes
EXEC
Examples
Table 2-75 describes the fields shown in the show interface FastEthernet display.
Table 2-75 show interface FastEthernet Field Descriptions
Field
|
Description
|
Description
|
Description of the device, as configured by using the description option of the interface global configuration command.
|
Type
|
Type of interface. Always Ethernet.
|
Ethernet address
|
Layer-2 MAC address.
|
Internet address
|
Internet IP address configured for this interface.
|
Broadcast address
|
Broadcast address configured for this interface.
|
Netmask
|
Netmask configured for this interface.
|
Maximum Transfer Unit Size
|
Current configured MTU value.
|
Metric
|
Metric setting for the interface. The default is 1. The routing metric is used by the routing protocol to determine the most favorable route. Metrics are counted as additional hops to the destination network or host; the higher the metric value, the less favorable the route.
|
Packets Received
|
Total number of packets received by this interface.
|
Input Errors
|
Number of incoming errors on this interface.
|
Input Packets Dropped
|
Number of incoming packets that were dropped on this interface.
|
Input Packets Overruns
|
Number of incoming packet overrun errors.
|
Input Packets Frames
|
Number of incoming packet frame errors.
|
Packet Sent
|
Total number of packets sent from this interface.
|
Output Errors
|
Number of outgoing packet errors.
|
Output Packets Dropped
|
Number of outgoing packets that were dropped by this interface.
|
Output Packets Overruns
|
Number of outgoing packet overrun errors.
|
Output Packets Carrier
|
Number of outgoing packet carrier errors.
|
Output Queue Length
|
Output queue length in bytes.
|
Collisions
|
Number of packet collisions at this interface.
|
Interrupts
|
Number of packet interrupts at this interface.
|
Base address
|
Base address. hexidecimal value.
|
Flags
|
Interface status indicators. Values include Up, Broadcast, Running, and Multicast.
|
Mode
|
Speed setting, transmission mode, and transmission speed for this interface.
|
Table 2-76 describes the fields shown in the show interface PortChannel display.
Table 2-76 Field descriptions for the show interface PortChannel Command
Field
|
Description
|
Type
|
Type of interface. Always Ethernet.
|
Ethernet address
|
Layer-2 MAc address.
|
Maximum Transfer Unit Size
|
Current configured MTU value.
|
Metric
|
Metric setting for the interface. The default is 1. The routing metric is used by the routing protocol. Higher metrics have the effect of making a route less favorable; metrics are counted as addition hops to the destination network or host.
|
Packets Received
|
Total number of packets received by this interface.
|
Input Errors
|
Number of incoming errors on this interface.
|
Input Packets Dropped
|
Number of incoming packets that were dropped on this interface.
|
Input Packets Overruns
|
Number of incoming packet overrun errors.
|
Input Packets Frames
|
Number of incoming packet frame errors.
|
Packet Sent
|
Total number of packets sent from this interface.
|
Output Errors
|
Number of outgoing packet errors.
|
Output Packets Dropped
|
Number of outgoing packets that were dropped by this interface.
|
Output Packets Overruns
|
Number of outgoing packet overrun errors.
|
Output Packets Carrier
|
Number of outgoing packet carrier errors.
|
Output Queue Length
|
Output queue length in bytes.
|
Collisions
|
Number of packet collisions at this interface.
|
Flags
|
Interface status indicators. Values include Up, Broadcast, Running, and Multicast.
|
Table 2-77 describes the field shown in the show interface scsi display.
Table 2-77 Field Description for the show interface scsi Command
Field
|
Description
|
SCSI interface X
|
Information for SCSI device number X. Shows the make, device ID number, model number, and type of SCSI device.
|
Table 2-78 describes the fields shown in the show interface standby display.
Table 2-78 show interface standby Field Descriptions
Field
|
Description
|
Standby Group
|
Number that identifies the standby group.
|
Description
|
Description of the device, as configured by using the description option of the interface global configuration command.
|
IP address, netmask
|
IP address and netmask of the standby group.
|
Member interfaces
|
Member interfaces of the standby group. Shows which physical interfaces are part of the standby group. Shows the interface definition, such as GigibitEthernet 1/0.
|
Active interface
|
Interfaces that are currently active in the standby group.
|
Related Commands
interface
show running-config
show startup-config
show inventory
To display the system inventory information, use the show inventory EXEC command.
show inventory
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
The show inventory command allows you to view the unique device identifier information (UDI) for a Content Engine. Typically, Cisco Content Engines contain the following three identification items, which make up the UDI:
•
Product ID (PID)
•
Version ID (VID)
•
Serial number (SN)
This identity information is stored in the Content Engine nonvolatile memory. Each Content Engine has a unique device identifier (UDI). The UDI = PID + VID + SN.
The UDI is electronically accessed by the product operating system or network management application to enable identification of unique hardware devices. The data integrity of the UDI is vital to customers. The UDI that is programmed into the Content Engine's nonvolatile memory is equivalent to the UDI that is printed on the product label and on the carton label. This UDI is also equivalent to the UDI that can be viewed through any electronic means and in all customer-facing systems and tools. Currently, there is only CLI access to the UDI; there is no SNMP access to the UDI information.
On newer Content Engine models, you can use the show inventory EXEC command to display the Content Engine's UDI. On older Content Engine models, use the show tech-support EXEC command to display the Content Engine's UDI.
Examples
The following example shows the inventory information for one of the newer Content Engine models (CE-565):
ContentEngine# show inventory
PID: CE-565-K9 VID: 0 SN: serial_number
In the preceding example, serial number is the serial number of the Content Engine. The version ID is displayed as "0" because the version number is not available.
Table 2-79 describes the fields shown in the show inventory display.
Table 2-79 show inventory Field Descriptions
Field
|
Description
|
PID
|
Product identification (ID) number of the device.
|
VID
|
Version ID number of the device. Displays as 0 if the version number is not available.
|
SN
|
Serial number of the device.
|
The following example shows that you must use the show tech-support EXEC command to display the inventory information on an older Content Engine model:
Please look at 'sh tech-support' for information!
CE-507# show tech-support
Related Commands
show tech-support
show ip access-list
To display the access lists that are defined and applied to specific interfaces or applications, use the show ip access-list EXEC command.
show ip access-list [acl-name | acl-num]
Syntax Description
acl-name
|
(Optional) Information for a specific access list, using an alphanumeric identifier up to 30 characters, beginning with a letter.
|
acl-num
|
(Optional) Information for a specific access list, using a numeric identifier (0-99 for standard access lists and 100-199 for extended access lists).
|
Defaults
Displays information about all defined access lists.
Command Modes
EXEC
Usage Guidelines
Use the show ip access-list EXEC command to display the access lists that have been defined on the current system. Unless you identify a specific access list by name or number, the system displays information about all the defined access lists, including the following sections:
•
Available space for new lists and conditions
•
Defined access lists
•
References by interface and application
Examples
The following example shows sample output from the show ip access-list command:
ContentEngine# show ip access-list
492 access list conditions
Standard IP access list 1
1 permit 10.1.1.2
(implicit deny any: 2 matches)
Extended IP access list 100
1 permit tcp host 10.1.1.1 any
2 permit tcp host 10.1.1.2 any
3 permit tcp host 10.1.1.3 any
(implicit fragment permit: 0 matches)
(implicit deny ip any any: 0 matches)
Standard IP access list test
1 permit 1.1.1.1 (10 matches)
(implicit deny: 2 matches)
Interface access list references:
FastEthernet 0/0 inbound 100
Application access list references:
The following example shows sample output from the show ip access-list command for the access list named test:
ContentEngine# show ip access-list test
Standard IP access list test
1 permit 1.1.1.1 (10 matches)
(implicit deny: 2 matches)
Note
The system displays the number of packets that have matched a condition statement only if the number is greater than zero.
Related Commands
clear ip access-list counters
ip access-group
ip access-list
show ip routes
To display the IP routing table, use the show ip routes EXEC command.
show ip routes
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Examples
The show ip routes command displays the IP routing table.
Table 2-80 describes the fields shown in the show ip routes display.
Table 2-80 show ip routes Field Descriptions
Field
|
Description
|
Destination
|
Destination address IP route mask.
|
Gateway
|
IP address or IP alias of the gateway router.
|
Netmask
|
Subnet mask of the gateway router.
|
.
Related Commands
ip route
show ldap
To display the Lightweight Directory Access Protocol (LDAP) parameters, use the show ldap EXEC command.
show ldap
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Examples
Table 2-81 describes the fields shown in the show ldap display.
Table 2-81 show ldap Field Descriptions
Field
|
Description
|
LDAP Authentication
|
State of LDAP authentication (enabled or disabled).
|
Allow mode
|
Access to users when the LDAP server is unavailable.
|
Base DN
|
Base distinguished name.
|
Filter
|
LDAP filter for authentication group.
|
Retransmits
|
Number of retransmissions.
|
Timeout
|
Wait time in seconds for an LDAP server to reply.
|
UID Attribute
|
User ID attribute on the LDAP server.
|
Group Attribute
|
Authentication group attribute: dn = distinguished name, un = unique name, ou = organizational unit for native LDAP groups, and memberOf = member of Active Directory group.
|
organizationUnit
|
Group name obtained from the ou attribute of the user account.
|
Custom Attribute
|
Group name obtained from the custom attribute of the user account.
|
Active Directory
|
Group name obtained from the memberOf attribute of the user account.
Note An Active Directory database is a user database that resides on a Windows 2000 server that is running the Microsoft Active Directory program.
|
Static Groups
|
Status of whether the static group query for user membership has been enabled. A static group defines each member individually using the object class attribute of groupOfNames or groupOfUniqueNames.
|
Group Attribute
|
Group attribute that the LDAP server uses to search the direct or nested static group configurations.
|
Group Member
|
Group member attribute that the LDAP server uses to search the direct or nested static group configurations.
|
Nested Groups
|
Any static groups that are nested under the parent group, which the LDAP server searches for user account information.
|
Nested Level
|
Number of levels down the LDAP directory from the starting point of the search that the LDAP server searches.
|
Administrative DN
|
Administrator distinguished name for the LDAP database search. There is no default value for this field and none is specified if it is not configured.
|
Administrative Password
|
Password of administrator for the LDAP database search. There is no default value for this field and none is specified if it is not configured.
|
LDAP version
|
LDAP software release version.
|
LDAP port
|
TCP port for the LDAP authentication server.
|
Policy redirect feature
|
Status of whether the support for acceptable use policy redirection has been configured.
|
Policy redirect append request url
|
Status of whether the Content Engine is enabled to append the request URL (original destination URL) to the LDAP AUP redirect URL.
|
Policy redirection URL
|
URL to redirect to if the user still has accepted the usage policy.
|
Policy redirection LDAP attribute name
|
Name of the LDAP attribute that is to be queried for the version that the user has accepted.
|
Policy redirection LDAP attribute value
|
Value of the LDAP attribute that is to be queried for the version that the user has accepted.
|
Password Expiry feature
|
Status of whether support for expiry of authorization passwords has been configured.
|
Password Expiry redirection URL
|
URL to redirect to if the user password has expired.
|
Server
|
LDAP server IP address.
|
Status
|
Status of whether the server is the primary or secondary host.
|
Primary
|
Primary host.
|
Secondary
|
Secondary host.
|
Related Commands
ldap
show logging
To display the system message log configuration, use the show logging EXEC command.
show logging
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
In the ACNS 5.3 software release, proxy-mode native FTP support was added. Syslog messages for proxy-mode native FTP support were added in the ACNS 5.3 software release. The following is an example of one of these syslog message for proxy-mode native FTP support:
CE-FTP_PROXY-3-252009: Failed to configure FTP Proxy-mode listener on port
Explanation: Could not start proxy-mode listener for FTP control
connection for the specified port. The port is temporarily
in an un-bindable state, or is in use by some other
Action: Check whether the port has been configured for use by a
different application. If not, retry the ftp-native
incoming proxy command after 2 minutes. If this error
repeats frequently, contact Cisco TAC.
To view information about events that have occurred in all devices in your ACNS network, you can use the system message log in the Content Distribution Manager GUI. The Content Distribution Manager logs only severity level critical or higher messages from registered nodes. Also, the Content Distribution Manager logs certain other status messages that are considered important to the Centralized Management System (CMS). The messages displayed in the System Message Log for device, Content Engine, window are not related to the messages logged in the system log file on the sysfs partition on the Content Distribution Manager as /local1/syslog.txt.
The syslog.txt file on the Content Distribution Manager contains information about events that have occurred on the Content Distribution Manager and not on the registered nodes. The messages that ar written to the syslog.txt file depend on specific parameters of the system log file that you have set by using the logging global configuration command. For example, a critical error message logged on a registered node does not appear in the syslog.txt file on the Content Distribution Manager because the problem never occurred on the Content Distribution Manager but only on the registered node. However, this error message is displayed in the System Message Log for device, Content Engine, window.
Examples
The following example displays the syslog host configuration on a Content Engine:
ContentEngine# show logging
Syslog to host is disabled
Priority for host logging is set to: warning
Syslog to console is disabled
Priority for console logging is set to: warning
Syslog to disk is enabled
Priority for disk logging is set to: notice
Filename for disk logging is set to: /local1/syslog.txt
Syslog facility is set to *
Syslog disk file recycle size is set to 500000
Related Commands
clear logging
logging
show mediafs
To display the disk name, partition numbers, and size in kilobytes of all volumes with media file system (mediafs) information, use the show mediafs EXEC command.
show mediafs volumes
Syntax Description
volumes
|
Displays media file system volumes.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
The media file system caches RealProxy and WMT files.
Examples
The following example displays the media file system information:
ContentEngine# show mediafs volumes
mediafs 00: /disk06-00/X/media 4030064KB
mediafs 01: /disk07-00/X/media 17223532KB
Related Commands
mediafs-division
show memory
To display memory blocks and statistics, use the show memory EXEC command.
show memory
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Examples
Table 2-82 describes the fields shown in the show memory display.
Table 2-82 show memory Field Descriptions
Field
|
Description
|
Total physical memory
|
Total amount of physical memory in kilobytes (KB).
|
Total free memory
|
Total available memory (in kilobytes).
|
Total buffer memory
|
Total amount of memory (in kilobytes) in the memory buffer.
|
Total cached memory
|
Total amount of memory (in kilobytes) in the memory cache.
|
Total swap
|
Total amount of memory (in kilobytes) for swap purposes.
|
Total free swap
|
Total available memory (in kilobytes) for swap purposes.
|
show multicast
To display a multicast client configuration and license, use the show multicast EXEC command.
show multicast [license-agreement]
Syntax Description
license-agreement
|
(Optional) Displays the multicast client license agreement.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
The show multicast command output displays the current status of the multicast client. If the license-agreement option is included in the command string, the full text of the multicast license agreement is displayed.
The sender-delay option of the multicast command controls the length of time that the multicast sender must wait for its associated metadata to be propagated to multicast receivers. To display the sender delay, use the show running-config command and look for the multicast sender-delay line item. If the sender-delay line item is present, then the delay time value is displayed. Otherwise, the value is 960 seconds, which is the default value.
Examples
The following example displays the current status of the multicast client:
ContentEngine# show multicast
multicast client product model: Cisco CE507
multicast client end user license agreement accepted
multicast client license key not installed
multicast client evaluation enabled. Estimated 60 days left for evaluation.
Related Commands
multicast
show network-filesystem
To display the status of network-attached storage (NAS) devices or file servers, use the show network-filesystem EXEC command.
show network-filesystem {client {all | cifs | nfs | samba} | server {cifs | nfs | samba}}
Syntax Description
client
|
Displays the information about the Content Engine client, which is used for access to NAS devices.
|
all
|
Displays the information about all types of clients.
|
cifs
|
Displays the information about Common Internet File System (CIFS) clients.
|
nfs
|
Displays the information about Network File System (NFS) clients.
|
samba
|
Displays the information about CIFS file servers; this deprecated command is provided for compatibility with earlier versions of the ACNS software.
|
server
|
Displays the information about file servers.
|
cifs
|
Displays the information about CIFS file servers.
|
nfs
|
Displays the information about NFS file servers.
|
samba
|
Displays the information about CIFS file servers; this deprecated command is provided for compatibility with earlier versions of the ACNS software.
|
Defaults
No default behavior or values
Command Modes
EXEC
Examples
The show network-filesystem client cifs all EXEC command displays the status of all network file system clients.
Table 2-83 describes the fields shown in the show network-filesystem client cifs all display. When the NAS share is in the process of being attached, the output for the NAS share appears as described in this table.
Table 2-83 show network-filesystem client all Field Descriptions
Field
|
Description
|
Network file system status
|
CIFS and NFS clients are enabled.
|
Shows which clients are enabled or disabled.
|
CIFS: //7.1.1.7:7: FILESYSTEM
|
Path to the CIFS partition on the disk and the type of the file system being used, such as CDNFS, CFS, or MEDIAFS.
|
Current status
|
Connection status of the CIFS client.
|
Total volume size
|
Total size of the file system in megabytes.
|
Free volume space
|
Amount of unused disk space available in megabytes.
|
Used volume space
|
Amount of disk space being used (in megabytes) and the percentage of the total.
|
Volume space assigned to CE
|
Amount of disk space (in megabytes and gigabytes) being used for system use.
|
NFS: //7.1.1.3:/ce: FILESYSTEM
|
Path to the NFS partition on the disk and the type of the file system being used, such as CDNFS, CFS, or MEDIAFS.
|
Volume space assigned to CE
|
Amount of space that is being used in the disk for the respective file system.
|
Current status
|
Connection status of the NFS share. Values may be attaching or online.
|
NAS is NOT ready to use.
|
Statement shows that the NAS share is still in the process of attaching. When the NAS share is fully attached, the statement changes to "NAS is ready to use."
|
Latest record found is:
|
Shows the record of the last time the share was accessed.
|
This NAS share has been used by CE-7325 Mon date 09/25/2003.
|
Shows which device is using this NAS share.
|
The show network-filesystem server cifs EXEC command displays the CIFS server status.
Table 2-84 describes the fields shown in the show network-filesystem server cifs display.
Table 2-84 show network-filesystem server cifs Field Descriptions
Field
|
Description
|
Network file system status
|
Windows file sharing (CIFS) server is enabled.
|
Status of whether the device is acting as a CIFS server.
|
Authentication mode is ce-user (default)
|
About the authentication mode.
|
Maximum number of concurrent connections is 16 (default)
|
Maximum number of concurrent connections.
|
Total 1 shared web site(s): www.cifs1.com as [Testingthis]: protected content is shared
|
Shows whether the content is shared or not, the number of shared websites and their FQDNs, and whether the shared content is protected or not.
|
show ntlm
To display Microsoft Windows NT LAN Manager (NTLM) parameters, use the show ntlm EXEC command.
show ntlm
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Examples
Table 2-85 describes the fields shown in the show ntlm display.
Table 2-85 show ntlm Field Descriptions
Field
|
Description
|
NTLM Hosts
|
Hostname or IP address of each NTLM server that you want the Content Engine to use for HTTP request authentication.
|
scheme
|
Scheme (load balancing or failover) that is to be used among the configured NTLM or Global Catalog Servers.
|
State
|
Status of whether NTLM authentication is enabled on the Content Engine.
|
Basic Auth
|
Status of whether the Content Engine is configured to send a basic authentication response header along with an NTLM authentication header to the client browser.
|
Default domain
|
Default user domain name for NTLM authentication.
|
Connection Timeout
|
Number of seconds that the Content Engine should wait for a response from the NTLM server to which it is attempting to connect.
|
Connection Retries
|
Maximum number of times that the Content Engine is to attempt to connect to one of the configured NTLM servers.
|
Allow Domains
|
Status of whether the allowed domain list feature is enabled on the Content Engine. This capability allows you to limit the domains that can perform NTLM HTTP request authentication with the Content Engine.
|
Allow Domains List
|
Names of the domains that are allowed to perform NTLM HTTP request authentication with the Content Engine. A domain list can contain up to 32 domain names.
|
AD group search is enabled
|
Status of whether the Active Directory group search to obtain group information is enabled.
|
Enumeration User
|
Enumeration user parameters.
|
Username
|
Enumeration user username.
|
Password
|
Enumeration user password.
|
Domain
|
Enumeration user domain name.
|
LDAP Port
|
LDAP port for group information retrieval. The default is port 389. This option configures the LDAP search server port for all of the configured Active Directory domain controllers.
|
Global Catalog Servers
|
Global Catalog Server information.
|
Hostname or Ip-address
|
Hostname or IP address of the Global Catalog Servers for Active Directory searches.
|
Domain
|
Host domain name for the Global Catalog Server.
|
Scheme
|
Scheme (load balancing or failover) that is to be used among the Global Catalog Servers.
|
Port
|
Port for the Global Catalog Server.
|
User objectclass
|
Object class for the user object (the default is user). The values of the objectclass attribute determine the schema rules that the entry must obey.
|
Username attribute
|
Username attribute in the Active Directory (the default is sAMAccountName).
|
Groupname attribute
|
Group name attribute in the Active Directory (the default is cn).
|
Membership attribute
|
Membership attribute in the Active Directory (the default is memberOf).
|
AD LDAP referral chasing
|
Status of whether LDAP referral is enabled on the Content Engine.
|
AD LDAP referral chasing limit
|
Referral limit for NTLM nested group searches.
|
Related Commands
ntlm
show ntp
To display the Network Time Protocol (NTP) parameters, use the show ntp EXEC command.
show ntp status
Syntax Description
status
|
Displays the NTP status.
|
Defaults
No default behavior or values
Command Modes
EXEC
Examples
Table 2-86 describes the fields shown in the show ntp status display.
Table 2-86 show ntp status Field Descriptions
Field
|
Description
|
NTP
|
Status of whether NTP is enabled or disabled.
|
server list
|
NTP server IP and subnet addresses.
|
remote
|
Name (first 15 characters) of remote NTP server.
|
*
|
In the remote column, identifies the system peer to which the clock is synchronized.
|
+
|
In the remote column, identifies a valid or eligible peer for NTP synchronization.
|
space
|
In the remote column, indicates that the peer was rejected. (The peer could not be reached or excessive delay occurred in reaching the NTP server.)
|
x
|
In the remote column, indicates a false tick and is ignored by the NTP server.
|
-
|
In the remote column, indicates a reading outside the clock tolerance limits and is ignored by the NTP server.
|
refid
|
Clock reference ID to which the remote NTP server is synchronized.
|
st
|
Clock server stratum or layer. In this example, stratum 1 is the top layer.
|
t
|
Type of peer (local, unicast, multicast, or broadcast).
|
when
|
Status of when the last packet was received from the server in seconds.
|
poll
|
Time check or correlation polling interval in seconds.
|
reach
|
8-bit reachability register. If the server was reachable during the last polling interval, a 1 is recorded; otherwise, a 0 is recorded. Octal values 377 and above indicate that every polling attempt reached the server.
|
delay
|
Estimated delay (in milliseconds) between the requester and the server.
|
offset
|
Clock offset relative to the server.
|
jitter
|
Clock jitter.
|
Related Commands
clock set
clock timezone
ntp server
show pac-file-server
To display information regarding the dynamic proxy autoconfiguration (PAC) file server, use the show pac-file-server EXEC command.
show pac-file-server {file url client-ip-address | information}
Syntax Description
file
|
Displays the PAC file that is generated by the specified parameters if the PAC file server is enabled.
|
url
|
Full path of the origin URL (including the PAC filename) where the PAC file can be accessed.
|
client-ip-address
|
IP address that an end user would use to configure the browser to obtain the PAC file from a PAC file server.
|
information
|
Displays whether the PAC file server is enabled and if enabled, the URLs that it is serving.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
Use the show pac-file-server command to display the PAC file that would be generated by a request using the specified URL from the specified IP address. Select the specified URL from the output of the show pac-file-server information command.
Proxy Autoconfiguration File Server
The Cisco ACNS 5.3 software release and later releases support dynamic proxy autoconfiguration (PAC). This feature is a form of direct proxy routing that allows a browser to dynamically obtain proxy IP address and port configuration information from a special file called a PAC file template. PAC is supported by the Microsoft Internet Explorer and Netscape Communicator browsers. Browsers must be manually configured for automatic proxy configuration.
PAC can be configured through the Content Distribution Manager and requires at least one Content Engine that is enabled as a PAC file server. The PAC file server dynamically chooses the proxy Content Engine that is closest to the client requesting the content, based on instructions contained in the PAC file template.
Dynamic PAC routing supports the following features:
•
It supports multiple PAC files.
•
The user can specify the names of the PAC files instead of being limited to preset names.
•
The PAC file server dynamically adds a set of nearest proxies to a PAC file template based on coverage zone information and the source IP address of the requester.
•
The Content Distribution Manager acquires the PAC file templates and distributes them to Content Engines that are PAC file servers rather than the Content Engines acquiring the PAC file templates.
Note
This new feature is not an extension of the proxy-auto-config EXEC command feature supported in the ACNS 5.0 software, nor does it replace that feature. Both features are supported in the ACNS 5.3 software.
PAC File Templates
The system administrator creates a PAC file template on a workstation and places it where the Content Distribution Manager can access the URL. The administrator then registers the PAC file template URL in the Content Distribution Manager GUI and assigns a coverage zone file to it.
The template is a complete PAC file except that the administrator inserts predefined macros where the PAC file server is to generate and insert dynamic information. The nearest proxies are determined by the metrics contained in the coverage zone file.
The Content Distribution Manager acquires the template and distributes it to all PAC file servers. For each Content Engine that is a PAC file server, the administrator must also configure the ports used for PAC file requests. Typically, port 80 is used.
The port can be configured in the CLI using the http proxy incoming port global configuration command. (There is no default.) Alternatively, you can use the Content Distribution Manager to configure the incoming proxy ports in the HTTP Connection Settings window.
The administrator then gives the PAC file URLs, including the desired servers, to end users. Users must configure their browsers to use the URL. When the browser first comes up, it requests the URL. The PAC file server dynamically replaces any ACNS software macros with the current information from the local coverage zone, if present, and from the default coverage zone based on the source IP address of the requester. The completed PAC file is returned to the requesting client.
When end users are behind a NAT device and the network administrator wants to direct end users to different proxies based on their IP address, then there must also be a PAC file server behind the NAT device for those users to use. A PAC file server that is not behind the NAT would receive PAC requests for users behind the NAT with the source IP address of the NAT device rather than the source IP address of the end user.
Three macros are defined:
•
CE_NAME_n
•
CE_IPADDR_n
•
NEAREST_PROXIES_n
where n can be a value of 1 to 5.
For CE_NAME_n, the PAC file server substitutes the name of the nth closest proxy. For CE_IPADDR_n, the PAC file server substitutes the IP address of the nth closest proxy. If there is no nth closest proxy, the PAC file server substitutes the empty string "" in place of the macro.
For the NEAREST_PROXIES_n macro, the PAC file server substitutes the string PROXY <ip address>; for up to n closest proxies where <ip address> is the IP address of the proxy. If the template writer includes a port number with the macro, then this port number is appended to each proxy IP address.
For example, NEAREST_PROXIES_2:8080 might expand into a string such as PROXY 192.30.120.12:8080; PROXY 168.10.10.1:8080;. If n is larger than the number of available proxies, then the PAC file server substitutes fewer than n proxies. For example, NEAREST_PROXIES_2 might expand into PROXY 192.30.120.12; or even just quotation marks ("") when there are no nearest proxies.
Examples
The following example displays the PAC file server details:
ContentEngine# show pac-file-server information
PAC File Server enabled
PAC URLs served by this PAC File Server
----------------------------------------
http://itest-ce2.ce.des.unicorn.com/sample_1
http://itest-ce2.ce.des.unicorn.com/sample_2
http://itest-ce2.ce.des.unicorn.com/sample_3
itest-ce2#
The following example shows how to configure the URL where the PAC file can be accessed and the IP address that an end user would use to configure the browser to obtain the PAC file:
ContentEngine# show pac-file-server file http://itest-ce2.ce.des.unicorn.com/sample_1
10.0.0.0
function FindProxyForURL(url,host)
{
if ((dnsDomainIs(host, ".uhc.com"))
if (dnsDomainIs(host, ".digital.com") ||
dnsDomainIs(host, ".computershare.com") ||
dnsDomainIs(host, ".compaq.com") ||
dnsDomainIs(host, ".trizetto.com") ||
dnsDomainIs(host, ".forrester.com"))
return "PROXY itest-ce2.proxy.merck.com:8080; DIRECT";
return "DIRECT";
}
ContentEngine#
Related Commands
debug pac-file-server
show statistics pac-file-server
show pre-load
To display information about the preload configuration, use the show pre-load EXEC command.
show pre-load
Syntax Description
This command has no arguments or keywords.
Defaults
Maximum number of concurrent requests: 25
Depth level of URL download: 1
Start Time: 00:00
Command Modes
EXEC
Examples
Table 2-87 describes the fields shown in the show pre-load display.
Table 2-87 show pre-load Field Descriptions
Field
|
Description
|
Preloading is disabled
|
Status of whether preload is enabled or disabled.
|
Number of concurrent sessions
|
Maximum number of concurrent requests (1-100). The default is 25.
|
Depth level
|
Depth level of URL download (1-50). The default is 1.
|
URL List File
|
Pathname or the FTP or HTTP location where the preload URL list file resides.
|
Fetch Domains
|
Domains to be fetched.
|
Fetch Suffix
|
Suffixes to be fetched.
|
Fetch Directory
|
Directories to be fetched.
|
No-fetch Domain
|
Domains to be excluded by an object filter.
|
No-Fetch Suffix
|
Suffixes to be excluded by an object filter.
|
No-Fetch Directory
|
Directories to be excluded by an object filter.
|
Scheduling on all days
|
Preload in scheduling intervals of 1 day, 1 hour or less, or 1 week or less.
|
Start Time
|
Preload start time. The default is 00:00.
|
End Time
|
Preload end time. If no end time appears, the preload continues until completion.
|
Related Commands
pre-load
pre-load force
show pre-load statistics
show processes
To display CPU or memory processes, use the show processes EXEC command.
show processes [cpu | debug pid | memory | system [delay 1-60 | count 1-100]]
Syntax Description
cpu
|
(Optional) Displays the CPU utilization.
|
debug
|
(Optional) Prints the system call and signal traces for a specified process identifier (PID) to display system progress.
|
pid
|
Process identifier.
|
memory
|
(Optional) Displays memory allocation processes.
|
system
|
(Optional) Displays system load information in terms of updates.
|
delay
|
(Optional) Specifies the delay between updates, in seconds (1-60).
|
count
|
(Optional) Specifies the number of updates that are displayed (1-100).
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
Use the commands shown in this section to track and analyze system CPU utilization.
The show processes debug command displays the extensive internal system call information and a detailed account of each system call (and arguments) made by each process and the signals that it has received.
Use the show processes system command to display system updates. The delay option specifies the delay between updates, in seconds. The count option specifies the number of updates that are displayed. This command displays these items:
•
A list of all processes in wide format.
•
Two tables listing the processes that utilize CPU resources. The first table displays the list of processes in descending order of utilization of CPU resources based on a snapshot taken after the processes system (ps) output is displayed. The second table displays the same processes based on a snapshot taken 5 seconds after the first snapshot.
•
Virtual memory used by the corresponding processes in a series of five snapshots, each separated by 1 second.
Note
CPU utilization and system performance may be affected when you use these commands. We recommend that you avoid using these commands, especially the show processes debug command, unless it is absolutely necessary.
Examples
Table 2-88 describes the fields shown in the show processes displays.
Table 2-88 show processes Field Descriptions
Field
|
Description
|
CPU Usage
|
CPU utilization as a percentage for user, system overhead, and idle.
|
PID
|
Process identifier.
|
STATE
|
Current state of corresponding processes.
R = running S = sleeping in an interruptible wait D = sleeping in an uninterruptible wait or swapping Z = zombie T = traced or stopped on a signal
|
PRI
|
Priority of processes.
|
User T
|
User time utilization in seconds.
|
Sys T
|
System time utilization in seconds.
|
COMMAND
|
Process command.
|
Total
|
Total available memory in bytes.
|
Used
|
Memory currently used in bytes.
|
Free
|
Free memory available in bytes.
|
Shared
|
Shared memory currently used in bytes.
|
Buffers
|
Buffer memory currently used in bytes.
|
Cached
|
Cache memory currently used in bytes.
|
TTY
|
TTY to which the process is attached. For example, TTY may indicate which processes belong to network Telnet sessions.
|
%MEM
|
Percentage of memory used by corresponding processes.
|
VM Size
|
Virtual memory size (in bytes) allocated to the corresponding process.
|
RSS (pages)
|
Resident set size, which indicates the number of pages that the process has in real memory minus three (-3) for administrative purposes. These pages count toward text, data, and stack space but do not count demand-loaded or swapped-out pages.
|
Name
|
Filename of the executable in parentheses.
|
show programs
To display a list of programs on the Content Engine, use the show programs EXEC command.
show programs [cisco-streaming-engine [live] | program-id id | program-name name | tvout |
wmt [live | rebroadcast]]
Syntax Description
cisco-streaming-engine
|
(Optional) Displays the list of programs served by the Cisco Streaming Engine.
|
live
|
(Optional) Displays the list of live programs served by the Cisco Streaming Engine.
|
program-id
|
(Optional) Displays detailed program information for the specified program ID.
|
id
|
Unique number identifying the program.
|
program-name
|
(Optional) Displays detailed program information for the specified program name.
|
name
|
Name of the program.
|
tvout
|
(Optional) Displays the list of TV-out programs.
|
wmt
|
(Optional) Displays the list of programs served by WMT.
|
live
|
(Optional) Displays the list of live programs served by WMT.
|
rebroadcast
|
(Optional) Displays the list of rebroadcast programs served by WMT.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
Typically, users create programs using the Content Distribution Manager by defining programs in the manifest file or by using the Program API. The show programs command output displays the program type, the channel with which the program is associated, the current status of the program, and the next time that the program will start next and end.
A program in the ACNS software is defined as a scheduled event in which the content is presented to the end user. Attributes of the program include the start and end time of the program, whether the content is pre-positioned or live, the set of Content Engines assigned to the program, and the streaming server to be used for content delivery.
Program types determine the hardware or software component involved in delivering content to the user. Different program types that are shown in the output of the show programs command are as follows:
•
Cisco Streaming Engine live
•
Cisco Streaming Engine rebroadcast
•
WMT live
•
WMT rebroadcast
•
TV-out
The Content Distribution Manager GUI allows you to create a program, schedule it, and deliver it over your multicast-enabled ACNS network. Programs can consist of prerecorded video or live events. In the case of live events, the ACNS software interoperates with third-party encoders and IP/TV Broadcast Servers to transmit the live stream across the ACNS network.
When creating a program in the Content Distribution Manager GUI, the administrator specifies the following information:
•
Streaming server—How the program will be streamed or delivered to the end user
–
Cisco Streaming Engine—The event is played from a PC using the Apple QuickTime application or using the IP/TV Viewer application
–
WMT server—The event is played using a Windows Media Technologies player
–
TV-out device—The event is displayed over a television monitor that is directly connected to the Content Engine
–
Exported—The program is exported over HTTP to a set top box
•
Media source
–
Live stream transmitted from a third-party encoder or an IP/TV Broadcast Server
–
Pre-positioned content stored on Content Engines
•
Destination
–
A set of Content Engines or device groups
–
A channel (live or export)
•
Delivery method
–
Unicast or multicast live events
–
Multicast scheduled rebroadcasts
–
TV-out or export playlists
•
Schedule
–
Start time and duration
–
Looping forever (enabled or disabled)
–
Multiple playback times
–
Repeating playback times
•
Publishing URL—The URL used to view the program
Playing Hinted and Nonhinted IP/TV Programs over an ACNS Network
Note
Hinted files contain hint tracks, which store packetization information that tells the streaming server how to package the media data. The streaming server uses the packetization information in the hint tracks to stream the media data to the network.
The Cisco Streaming Engine supports only hinted files (MOV and hinted MP4 files) for streaming. If you are creating a file-based IP/TV program for streaming over an ACNS network, make sure that you use only hinted files such as those with .mov or .mp4 extensions.
However, you can pre-position IP/TV on-demand programs based on nonhinted files such as .mpg files on Content Engines when IP/TV is integrated with an ACNS network by using the TV-out feature.
Configuring Multicast IP Addresses for IP/TV Programs
If an IP/TV program that you want to deliver over an ACNS network uses live multicast mode, you must use the same multicast IP address for the audio, video, and SlideCast streams.
This requirement does not apply if the Content Engine used for live splitting is running the ACNS 5.1.5 software and later releases. However, this requirement still applies if the Content Engine is running the ACNS 5.1.1 software, even if you are running IP/TV 5.1.5 and later releases on IP/TV Program Manager.
Live Events
Live events are streamed from third-party encoders (such as the Windows Media encoder Version 9 and the QuickTime encoder) or from streaming servers (such as Windows Media Server). The live stream is acquired by the root Content Engine and transmitted to edge Content Engines using unicast. From the edge Content Engines, the live stream is transmitted to end users using either multicast or multicast and unicast live splitting. The live program is available to viewers only during its scheduled times.
Before setting up a live event in the Content Distribution Manager GUI, the administrator must complete the following tasks:
1.
Set up the live event on the encoder or streaming server. This task is done externally to the Content Distribution Manager GUI.
2.
In the Content Distribution Manager GUI, accept the streaming server's license agreement (WMT or RTSP) on the Content Engines designated to acquire and distribute the stream.
3.
Create a live channel (or designate an existing channel as a live channel), assign Content Engines to the live channel, and designate a root Content Engine to acquire the stream.
After you have completed the preceding tasks, you are ready to define the program and configure the program settings in the Content Distribution Manager GUI. The Content Distribution Manager allows you to define two types of live events based on the streaming server being used:
•
WMT live
•
Cisco Streaming Engine live
Configuration Requirements for Managed Live Events
If you have channels for live programs configured in your ACNS 5.3 network, make sure that there are no external proxy servers physically located between your ACNS 5.3 receiver Content Engines and your ACNS 5.3 root Content Engine that require proxy authentication. Also, make sure that proxy authentication is not enabled on any receiver Content Engines that might be in the logical, hierarchical path between the root Content Engine and the receiver Content Engine that is going to serve the live stream to the requesting clients. If a live stream encounters any device that requires proxy authentication, the stream will be dropped before it reaches its destination.
If your network is set up with intermediary devices that require proxy authentication, you can work around the problem by configuring rules to bypass authentication on these devices.
For example, to enable the formation of the unicast splitting tree and, in turn, enable live broadcasting from all receiver Content Engines, you can specify the following rule on all of the parent Content Engines in the channel:
ContentEngine(config)# rule pattern-list 1 downstream-CE-ipaddress
ContentEngine(config)# rule no-auth pattern-list 1
Live Stream Interruptions
During a WMT live broadcast, any interruption of the live stream that lasts 5 minutes or longer causes the multicast broadcast to stop for the duration of the currently scheduled period. If the live stream is interrupted for less than 5 minutes, the broadcast resumes.
Live stream interruptions can be caused by unexpected encoder failures or by an operational restart. If you have early trials scheduled prior to the live event, we recommend that you configure multiple schedules, one for each trial. We also recommend that you start the encoder prior to the scheduled time.
If the live stream stops for more than 5 minutes and resumes later while the program is still scheduled, you can modify the schedule or any other attribute of the program (such as the description) to trigger a restart of the multicast broadcast. Restarting might take up to 5 minutes under these circumstances. This setting does not apply to unicast delivery of a WMT live event or to Cisco Streaming Engine live programs.
Scheduled Rebroadcasts
In a scheduled rebroadcast, the pre-positioned content is scheduled to be streamed from edge Content Engines using multicast. To define a program for a rebroadcast event, the administrator must complete the following tasks:
1.
Create a content acquisition channel and pre-position the content.
2.
Assign media files to the program.
3.
Specify the multicast address and port or define a program address pool.
4.
Specify the days and times for the rebroadcast.
Note
For rebroadcast programs, the media can only be selected from one channel. The Content Engines and device groups assigned to the channel are selected automatically when you choose the media files for the program.
The Content Distribution Manager allows you to define a program as a WMT rebroadcast program or as a Cisco Streaming Engine rebroadcast.
TV-Out Programs
A TV-out program is a scheduled program that is based on a playlist. A playlist is list of media files and their associated attributes. When you define a TV-out program, you set up a schedule called a playtime. A playlist can have between one and ten different playtimes.
To define a program for TV-out, the administrator must complete the following tasks:
1.
Create a content acquisition channel and pre-position the content.
2.
Select a content channel to be associated with the program.
3.
Specify the days and times for the program to play.
Note
For TV-out programs, Content Engines are assigned directly to the program. The content can be acquired from one channel and distributed through a different channel. The program distribution channel does not have to be the same as the content acquisition channel or channels. To ensure a successful playback, however, the administrator must verify that the media files are pre-positioned on all Content Engines assigned to the program distribution channel.
Examples
Table 2-89 describes the fields shown in the show programs display.
Table 2-89 show programs Field Descriptions
Field
|
Description
|
ID
|
Unique number identifying the program.
|
Program-Name
|
Name of the program.
|
Type
|
Program type. Program types are as follows:
• Cisco Streaming Engine live
• Cisco Streaming Engine rebroadcast
• TV-out
• Windows Media live
• Windows Media rebroadcast
|
Channel
|
Name of the channel to which the program is assigned.
|
Status
|
Status of whether the program is currently playing.
|
Next-Start-Time
|
Date and time at which the program is scheduled to start the next time.
|
Next-End-Time
|
End date and time for the program.
|
Table 2-90 describes the fields shown in the show programs program-name display.
Table 2-90 show programs program-name Field Descriptions
Field
|
Description
|
Current Time
|
Current system clock time.
|
Program ID
|
Unique number identifying the program.
|
Program Name
|
Name of the program.
|
Channel ID
|
Channel number to which the program is assigned.
|
Channel Name
|
Name of the channel to which the program is assigned.
|
Type
|
Program type. Program types are as follows:
• Cisco Streaming Engine live
• Cisco Streaming Engine rebroadcast
• TV-out
• Windows Media live
• Windows Media rebroadcast
|
Forwarder List
|
List of forwarders on the path to the broadcast server. The first IP address in the list is that of the Content Engine and the last IP address in the list is that of the broadcast server.
|
Schedule
|
Playback schedule for the program.
|
Start Time (loc)
|
Start date and time for the program.
|
End Time (loc)
|
End date and time for the program.
|
Duration
|
Duration of the program or the looping time in a scheduled view.
|
Repeatdays
|
Playback repeats every so many days according to the interval specified (for example, every 10 minutes).
|
Repeat
|
Status of whether the program is configured as a one-time live event, to repeat every so many days, hours, or minutes, or to repeat at the same hour on the days that you have chosen.
|
Time spec
|
Time zone configured on the Content Engine.
|
Source
|
Reference to the source of the media file as follows:
• For the live content, this field contains information about how the streaming server correlates with the live feed.
• For the pre-positioned content, this field contains the portion of the URL that follows the origin server (the fully qualified domain name [FQDN]).
Note When the pre-positioned content is exported, this field contains the URL for the file that can be routed in the ACNS network without the protocol specification.
|
Multicast URL
|
URL used by the end user to request this program over the network.
|
Multicast Address
|
Multicast address to be used for the program.
|
Start Time (loc)
|
Program start time in the Content Engine local time.
|
Start Time
|
Program start time in Universal Coordinated Time (UTC), which is the same as Greenwich Mean Time (GMT).
|
End Time (loc)
|
Program end time in the Content Engine local time.
|
End Time
|
Program end time in UTC.
|
Current Status
|
Status of whether the program is currently playing.
|
Time left
|
Amount of time remaining for the program to end.
|
show proxy-auto-config
To display the state of the browser autoconfiguration feature, use the show proxy-auto-config EXEC command.
show proxy-auto-config
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
The ACNS 5.x software supports proxy automatic configuration files (.pac files). A browser obtains proxy IP address and port configuration information from the proxy automatic configuration file when the browser's autoconfiguration URL field is configured with the Content Engine IP address, incoming port number, file directory, and .pac filename.
Note
You must configure disks /local1 or /local2 as a sysfs volume before downloading the autoconfiguration file to either of these two disk locations.
The Microsoft Internet Explorer and Netscape browsers support the proxy autoconfiguration feature. The browser must be manually configured for automatic proxy configuration.
The following example demonstrates the URL syntax to enter in the proxy automatic configuration URL field of the browser:
http://ContentEngine-IPaddress:portnumber/theproxyfile.pac
Note
Use a port number specified by the proxy incoming settings for configuring proxy incoming ports. For instance, if port 8080 is specified, then use 8080 as your port number in the example shown.
Examples
The following example displays the state of the proxy autoconfiguration feature:
ContentEngine# show proxy-auto-config
Proxy auto-config is disabled.
Proxy auto-config file is NOT installed.
Related Commands
proxy-auto-config
show proxy-protocols
To display the current global outgoing proxy exclude status and criteria, use the show proxy-protocols EXEC command.
show proxy-protocols {all | outgoing-proxy | transparent}
Syntax Description
all
|
Displays all proxy protocol parameters.
|
outgoing-proxy
|
Displays global outgoing proxy exceptions.
|
transparent
|
Displays transparent mode protocol policies.
|
Defaults
No default behavior or values
Command Modes
EXEC
Examples
The following example displays the outgoing proxy exclude status:
ContentEngine# show proxy-protocols all
Transparent mode forwarding policies: default-server
Outgoing exclude domain name: cisco.com
Related Commands
proxy-protocols
show radius-server
To display RADIUS information, use the show radius-server EXEC command.
show radius-server
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Examples
Table 2-91 describes the fields shown in the show radius-server display.
Table 2-91 show radius-server Field Descriptions
Field
|
Description
|
Login Authentication for Console/Telnet Session
|
Status of whether RADIUS server is enabled for login authentication.
|
Configuration Authentication for Console/Telnet Session
|
Status of whether RADIUS server is enabled for authorization or configuration authentication.
|
Authentication scheme fail-over reason
|
Status of whether Content Engines fail over to the secondary method of administrative login authentication whenever the primary administrative login authentication method fails.
|
RADIUS Configuration
|
RADIUS authentication settings.
|
RADIUS Authentication
|
Status of whether RADIUS authentication is enabled on the Content Engine.
|
Key
|
Key used to encrypt and authenticate all communication between the RADIUS client (the Content Engine) and the RADIUS server.
|
Timeout
|
Number of seconds that the Content Engine waits for a response from the specified RADIUS authentication server before declaring a timeout.
|
Retransmit
|
Number of times that the Content Engine is to retransmit its connection to the RADIUS if the RADIUS timeout interval is exceeded.
|
Radius Redirect
|
Status of whether the RADIUS server redirects the response if an authentication request fails.
|
Reply-Message
|
Message sent to the user if redirection occurs.
|
URL(s) to authentication failure instructions expired
|
HTML page location or URL where the redirect message should be sent.
|
Servers
|
RADIUS servers that the Content Engine is to use for RADIUS authentication.
|
IP
|
Hostname or IP address of the RADIUS server.
|
Port
|
Port number on which the RADIUS server is listening.
|
Related Commands
radius-server
show rtsp
To display the Real-Time Streaming Protocol (RTSP) configurations, use the show rtsp EXEC command. If the license-agreement option is included in the command string, the full text of the RealProxy license agreement is displayed.
show rtsp [all | gateway | proxy media-real [all | bandwidth | license-agreement] | server
{cisco-streaming-engine [all | bandwidth] | real-subscriber [bandwidth |
license-agreement] | wmt [bandwidth]}]
Syntax Description
all
|
(Optional) Displays all RTSP configurations.
|
gateway
|
(Optional) Displays the RTSP gateway configuration.
|
proxy
|
(Optional) Displays RTSP-based proxy configurations.
|
media-real
|
Displays the RealProxy configuration.
|
license-agreement
|
(Optional) Displays the RealProxy end user license agreement (EULA).
|
server
|
(Optional) Displays the RTSP server configuration.
|
cisco-streaming-engine
|
Displays the Cisco Streaming Engine configuration.
|
all
|
(Optional) Displays all Cisco Streaming Engine-related configurations.
|
bandwidth
|
(Optional) Displays Cisco Streaming Engine bandwidth settings.
|
real-subscriber
|
Displays the RealSubscriber configuration.
|
bandwidth
|
(Optional) Displays RealSubscriber bandwidth settings.
|
license-agreement
|
(Optional) Displays the RealSubscriber end user license agreement (EULA).
|
wmt
|
Displays information about the WMT RTSP server that runs on the Content Engine.
|
bandwidth
|
(Optional) Displays WMT RTSP server bandwidth settings.
|
Defaults
No default behavior or values
Command Modes
EXEC
Examples
The following examples display the output of the show rtsp all, show rtsp gateway, and show rtsp proxy media-real EXEC commands. If the show rtsp license-agreement command is used, the full text of the RTSP license agreement appears.
CONTENTENGINE# show rtsp all
RTSP Gateway Configuration
--------------------------
RTSP Gateway ip-address 128.10.192.212
RTSP Gateway incoming port 554
RTSP Gateway incoming request rate limit is 40 requests/sec
RTSP Gateway initial setup delay is 10 sec
RTSP gateway is bypassed for cisco streaming engine
RTSP Gateway L4-switch not enabled
RTSP Gateway Transparent Interception (WCCP):
Real Subscriber Configurations
------------------------------
Real Subscriber version: ce590-9.0.2.855
Real Subscriber end user license agreement accepted
Real Subscriber evaluation not enabled
Real Subscriber golden license key installed
Real Subscriber bandwidth enforced is 76800 kbps
Cisco Streaming Engine Configurations
-------------------------------------
Cisco Streaming Engine version ce590-4.1.3
Cisco Streaming Engine enabled
Cisco Streaming Engine bandwidth enforced is 119000 kbps
WMT RTSP Server/Proxy Configuration
-----------------------------------
WMT version: ce590-001.000
WMT beta license key installed
WMT outgoing bandwidth limit enforced: 168000 Kbits/sec
WMT end user license agreement accepted
WMT disallowed client protocols: none
WMT outgoing bandwidth configured is 168000 Kbits/sec
WMT incoming bandwidth configured is 168000 Kbits/sec
WMT max sessions configured: 969
WMT max sessions platform limit: 969
WMT max sessions enforced: 969 sessions
WMT max outgoing bit rate allowed per stream: 1 Kbits/sec
WMT max incoming bit rate allowed per stream has no limit
WMT L4 switch is not enabled
WMT debug client ip not set
WMT debug server ip not set
WMT fast-start is enabled
WMT fast-start max. bandwidth per player is 3500 (Kbps)
WMT fast-cache is enabled
WMT fast-cache acceleration factor is 5
WMT Extended Transaction Log is not enabled
WMT Transaction Log format is Windows Media Services 4.1 logging
Real Proxy Configurations
-------------------------
Real Proxy version: ce590-9.0.2.794
Real Proxy evaluation is not enabled
Real Proxy beta license key installed
Real Proxy end user license agreement accepted
Real Proxy is configured to use 49% of MEDIAFS partition
Real Proxy incoming bandwidth enforced is 168000 kbps
Real Proxy outgoing bandwidth enforced is 168000 kbps
ContentEngine# show rtsp gateway
RTSP Gateway ip-address 10.107.193.30
RTSP Gateway incoming port 67
RTSP Gateway L4-switch not enabled
RTSP Gateway Transparent Interception (WCCP):
CONTENTENGINE# show rtsp proxy media-real
Real Proxy version: ce507-9.0.2.794
Real Proxy is not enabled
Real Proxy evaluation is not enabled
Real Proxy license key not installed
Real Proxy end user license agreement accepted
Real Proxy is configured to use 30% of MEDIAFS partition
Real Proxy incoming bandwidth enforced is 20 kbps
Real Proxy outgoing bandwidth enforced is 40 kbps
CONTENTENGINE# show rtsp server cisco-streaming-engine
Cisco Streaming Engine version ce507-4.1.3
Cisco Streaming Engine enabled
Cisco Streaming Engine bandwidth enforced is 67 kbps
In the ACNS 5.3 software, the wmt option was added to the show rtsp server command to enable you to display information about the WMT RTSP server that runs on the Content Engine. The following example shows a sample configuration for the WMT RTSP server that is running on the Content Engine:
Content Engine# show rtsp server wmt
WMT version: ce507-001.000
WMT license key is installed
WMT evaluation is not enabled
WMT end user license agreement accepted
WMT disallowed client protocols: none
WMT outgoing bandwidth configured is 1 Kbits/sec
WMT incoming bandwidth configured is 56000 Kbits/sec
WMT max sessions configured: 2500
WMT max sessions platform limit: 2500
WMT max sessions enforced: 2500 sessions
WMT max outgoing bit rate allowed per stream: 2 Kbits/sec
WMT max incoming bit rate allowed per stream: 3 Kbits/sec
WMT debug client ip not set
WMT debug server ip not set
WMT fast-start is enabled
WMT fast-start max. bandwidth per player is 65 (Kbps)
WMT fast-cache is enabled
WMT fast-cache acceleration factor is 5
WMT Extended Transaction Log is not enabled
WMT Transaction Log format is Windows Media Services 4.1 logging
Related Commands
rtsp proxy
wccp rtsp
show rule
To display rules configuration information, use the show rule EXEC command. For a more complete explanation of specific rules, see the "rule" section on page 2-407.
show rule {action {action-type | all} [protocol {http | https | rtsp}] | all | pattern-list {1-512
pattern-type | all}}
Syntax Description
action
|
Displays all the rules with the specified action.
|
action-type
|
Action type (see Table 2-92). See the "Understanding Actions and Patterns" section for explanations of actions and patterns.
|
all
|
Displays rules with all action types.
|
protocol
|
(Optional) Specifies the protocol to which actions apply.
|
http
|
Displays HTTP-related requests for this action.
|
https
|
Displays HTTPS-related requests for this action.
|
rtsp
|
Displays RTSP-related requests for this action.
|
all
|
Displays all the configured actions and pattern lists.
|
pattern-list
|
Displays the rules with the specified patterns.
|
1-512
|
Specifies the pattern number (1-512).
|
pattern-type
|
Pattern type (see Table 2-93).
|
all
|
Displays rules with all pattern lists.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
You can use the show rule action action-type command to display rules using a specific action. Table 2-92 shows the permitted action types and the effect of each action.
Table 2-92 Action Types
Action Type
|
Action Effect
|
allow
|
Permits requests.
|
append-username-header
|
Appends the username in the header to the request sent to the server.
|
block
|
Blocks the request.
|
cache-cookie
|
Caches the request containing cookies.
|
cache-non-cacheable
|
Caches the object, overriding HTTP response headers.
|
cache-only
|
Caches the object.
|
dscp client cache-hit
|
Sets the IP ToS or DSCP bits for the client-side connection to the configured value for cache hit responses to the client.
|
dscp client cache-miss
|
Sets the IP ToS or DSCP bits for the client-side connection to the configured value for cache miss responses to the client.
|
dscp server
|
Configures the IP ToS or DSCP field for requests to the origin server.
|
freshness-factor
|
Caches heuristic modifiers.
|
insert-no-cache
|
Inserts no-cache headers into the response.
|
no-auth
|
Does not authenticate.
|
no-cache
|
Does not cache the object.
|
no-persistent-connection
|
Does not use persistent connections to connect to clients or servers.
|
no-proxy
|
Does not use any upstream proxy.
|
no-url-filtering
|
Bypasses the URL filtering for certain HTTP and HTTPS requests. This feature is supported for local list URL filtering (good and good sites' lists), as well as Websense, SmartFilter, or N2H2 URL filtering.
|
redirect
|
Redirects the request to a rewritten URL.
|
redirect-url-for-cdn
|
Redirects the URL to an alternative URL for the ACNS network content.
|
refresh
|
Revalidates the object with the web server.
|
reset
|
Issues a TCP RST.
|
rewrite
|
Rewrites the original request as a specified URL and fetches the rewritten URL on a cache miss.
|
use-dns-server
|
Uses a specific DNS server.
|
use-icap-service
|
Uses the ICAP service.
|
use-proxy failover
|
Fails over to outgoing HTTP proxy servers.
|
use-server
|
Uses a specific server.
|
use-xforward-clt-ip
|
Uses the client IP address for filtering in an X-Forwarded-For header.
|
You can use the show rule pattern-list pattern-type command to display rules using a specific pattern type. Table 2-93 shows the permitted pattern types and describes each pattern type.
Table 2-93 Pattern Types
Pattern Type
|
Description
|
domain
|
Regular expression to match the domain name.
|
dst-ip
|
Destination IP address of the request.
|
dst-port
|
Destination port number of the request.
|
groupname
|
LDAP or NTLM group name of the user.
|
groupname-regex
|
Regular expression substring match with the LDAP or NTLM group name of the user.
|
header-field referer
|
Request header field pattern for the Referer request header.
|
header-field request-line
|
Request header field pattern for the request method line.
|
header-field user-agent
|
Request header field pattern for the User-agent request header.
|
mime-type1
|
Regular expression to match the MIME type.
|
src-ip
|
Source IP address of the request.
|
url-regex
|
Regular expression to be matched against the URL.
|
username
|
Username of the HTTP request.
|
Examples
The following example displays all rules with the configured action types and pattern lists:
ContentEngine# show rule all
Rules Template Configuration
----------------------------
rule block domain bar.com
rule block domain \.foo.com
rule rewrite url-regsub http://www.ietf.org/rfc/.* http://wwwin-eng.cisco.com/RFC/$1
rule no-cache dst-ip 172.31.120.0 255.255.192.0
rule no-cache url-regex \.*cgi-bin*
The following example displays all rules configured with the use-proxy failover action type:
ContentEngine# show rule action use-proxy failover
Rules Template Configuration
----------------------------
rule action use-proxy 10.77.155.221 80 failover pattern-list 1
rule action use-proxy 10.77.155.221 80 failover pattern-list 510
The following example displays statistics of all rules configured with the use-proxy failover action type:
ContentEngine# show statistics rule action use-proxy failover
Rules Template Statistics
-------------------------
Rule hit count = 0 Rule: rule action use-proxy failover 10.77.155.221 80 pattern-list 1
Rule hit count = 0 Rule: rule action use-proxy failover 10.77.155.221 80 pattern-list
510
Related Commands
clear statistics rule
rule
show statistics rule
show running-config
To display the current running configuration information on the terminal, use the show running-config EXEC command. This command replaces the write terminal command.
show running-config
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
Use this command with the show startup-config command to compare the information in running memory to the startup configuration used during bootup.
Examples
The following example displays the current running configuration information:
ContentEngine# show running-config
alarm overload-detect raise 10 clear 9
http authentication realm "Cache"
http append via-header custom "cust"
http avoid-multiple-auth-prompts
http proxy incoming 80 8888
http proxy outgoing host 10.77.155.221 8090 primary
http proxy outgoing host 10.77.155.221 8080
http proxy outgoing monitor 10
http proxy outgoing connection-timeout 2000
http proxy outgoing origin-server
http proxy outgoing preserve-407
tcp client-rw-timeout 360
tcp client-receive-buffer 28
http max-ttl days text 5 binary 8
http tcp-keepalive enable
http monitor url http://www.cisco.com
ftp-over-http reval-each-request directory-listing
clock timezone US/Pacific -8 0
https proxy incoming 1 2 3 4
https proxy outgoing host 10.77.155.221 8080 primary
https proxy outgoing host 10.2.3.4 2
https proxy outgoing host 10.2.3.41 4
https proxy outgoing host 10.2.3.42 5
https proxy outgoing host 10.2.3.43 3
https proxy outgoing host 10.2.3.45 6
https proxy outgoing host 10.2.3.47 7
https proxy outgoing host 10.2.3.48 8
https proxy outgoing monitor 20
https proxy outgoing connection-timeout 3000
https proxy outgoing origin-server
https destination-port allow all
description This is Ether Channel interface
ip access-group extended_ip_acl in
ip address 10.10.10.10 255.0.0.0
ip address 10.0.0.9 255.255.0.0
description This is an interface that acts as a backup
ip address 10.2.3.4 255.0.0.0
interface FastEthernet 0/0
description This is the primary interface
ip address 10.1.1.21 255.255.255.0
interface FastEthernet 0/1
ip default-gateway 10.1.1.50
primary-interface FastEthernet 0/0
wmt license-key installed
wmt accept-license-agreement
wmt transaction-logs format extended wms-90!
rtsp server real-subscriber accept-license-agreement
multicast accept-license-agreement
ip name-server 192.168.11.48
ip access-list standard ex
ip access-list standard std_acl
ip access-list extended ext_acl_2
ip access-list extended extended_ip_acl
permit tcp any eq 2 any eq exec
external-ip 10.107.192.148
logging console priority alert
logging disk priority alert
ntp server 10.107.192.168
bypass static any-client 1.2.3.4
bypass auth-traffic enable
bypass load time-interval 6
proxy-protocols outgoing-proxy exclude enable
icp client add-remote-server 10.2.3.4 sibling icp-port 3130 http-port 3128 restrict (8)
icp server remote-client 10.0.0.1 no-fetch
icp server remote-client 10.1.1.1 no-fetch
icp server remote-client 198.133.219.25 fetch
wccp router-list 1 10.1.1.1 172.19.226.63
wccp router-list 3 10.4.5.6
wccp router-list 5 10.2.3.4 2.3.4.5
wccp port-list 4 1 2 3 4 5 6 7
wccp port-list 5 90 91 1026 127 1068 1098 19 178
wccp web-cache mask dst-ip-mask 0xfe000000
wccp reverse-proxy mask dst-ip-mask 0xfe00
wccp ftp-native mask src-ip-mask 0xfc000000 dst-ip-mask 0x1000000
wccp custom-web-cache router-list-num 1 port 31
wccp dns router-list-num 5
wccp ftp-native router-list-num 1 password **** l2-redirect mask-assign
wccp https-cache accept-all
wccp shutdown max-wait 15
https server name protocol-version sslv2-only
dns pin forward host1 1.2.3.4
rule action no-auth pattern-list 9
rule action no-auth pattern-list 4
rule action no-auth pattern-list 5
rule action block pattern-list 1
rule action block pattern-list 10
rule action allow pattern-list 2
rule action allow pattern-list 5
rule action no-url-filtering pattern-list 5
rule action no-url-filtering pattern-list 6
rule action use-proxy 10.77.155.221 80 failover pattern-list 1
rule action use-proxy 10.77.155.221 80 failover pattern-list 510
rule action append-username-header pattern-list 3
rule action use-icap-service icapser pattern-list 25
rule pattern-list 1 dst-port 9090
rule pattern-list 1 domain acme.com
rule pattern-list 1 domain yahoo.com
rule pattern-list 1 domain \.foo.com
rule pattern-list 1 domain \.cisco.com
rule pattern-list 1 domain \.cisco.com,bar.com
rule pattern-list 2 username user,r
rule pattern-list 2 username user,r,rt
rule pattern-list 4 domain mydomain.net
rule pattern-list 5 domain mydomain.net
rule pattern-list 6 domain cisco.com
rule pattern-list 9 dst-ip 1.2.3.4 255.0.0.0
rule pattern-list 10 domain yahoo.com
rule pattern-list 72 domain yahoo.com
rule pattern-list 510 domain acme.com
icap apply rules-template
icap append-x-headers x-server-ip
icap rescan-cache ISTag-change
vector-point reqmod-precache
vector-point respmod-precache
load-balancing weighted-load
vector-point reqmod-precache
vector-point reqmod-postcache
vector-point respmod-precache
error-handling return-error
server icap://10.1.1.1:1344/test-icap
server icap://1.0.0.1/icapser
server icap://1.2.3.4/servforicap
websense-server service policy local activate
rtsp proxy media-real accept-license-agreement
rtsp ip-address 114.116.115.112
rtsp advanced bypass-gateway media-real
transaction-logs log-windows-domain
transaction-logs export enable
transaction-logs format apache
username admin password 1 .RQrsujYFEO0U
username admin privilege 15
username nkurahas password 1 meYjSh.Ip.RXA uid 2002
username nkurahas privilege 0
username sample1 password 1 OszWHEZOgfYcA uid 2003
username sample1 privilege 0
username sample2 password 1 Cs2klvDtNE5lA uid 2004
username sample2 privilege 0
username pdelay password 1 etLYMNNMAPKeI uid 2001
username pdelay privilege 0
username hari password 1 791lvYweJxoc2 uid 65535
username hari privilege 0
username hari cifs-password 1 2FEE38AC020EA782AAD3B435B51404EE
E7AA6786F8D97524A6F44C206C274FC9
username savenugo password 1 boHitrTDO6yvE uid 2005
username savenugo privilege 0
username hg password 1 EuXx0Jp9Y5bnM uid 2006
username fromcli password 1 OuQ4SisW2PQEk uid 2007
username fromcli privilege 0
username h password 1 MucRaMZMhbWsQ uid 2008
username use password 1 7uSBQDu55xg/E uid 2009
username pat password 1 w1RcmUw0WWEF2 uid 2010
username pat privilege 15
username u password 1 52YyGE9fNgIjU uid 2011
username pa password 1 y2psIwhLRb0NI uid 2012
snmp-server enable traps config
snmp-server enable traps content-engine disk-read
snmp-server enable traps content-engine disk-write
snmp-server enable traps content-engine disk-fail
snmp-server enable traps content-engine overload-bypass
snmp-server enable traps content-engine transaction-log
snmp-server enable traps alarm raise-critical
snmp-server enable traps alarm clear-critical
snmp-server enable traps alarm raise-major
snmp-server enable traps alarm clear-major
snmp-server enable traps alarm raise-minor
snmp-server enable traps alarm clear-minor
snmp-server enable traps entity
snmp-server enable traps snmp authentication
snmp-server enable traps snmp cold-start
snmp-server enable traps event
snmp-server mib persist event
snmp-server host 1.1.1.1 com
snmp-server host 1.2.3.4 informs v2c
snmp-server user user1 group1 auth sha ****
snmp-server user admin group2 remote 7
snmp-server user snmp_user1 group3 remote 56 auth md5 **** priv ****
snmp-server view view1 entityMIB included
snmp-server view agon system included
snmp-server view agon system.7 included
snmp-server community community1
snmp-server notify inform
snmp-server access-list 5
radius-server host 10.77.7.7 auth-port 1645
tacacs host 172.9.26.12 primary
ntlm server ad-group-search enum-user username user1
ntlm server ad-group-search enum-user password ****
ntlm server ad-group-search enum-user domain dom1
ntlm server ad-group-search gc-server host 172.16.30.45 domain gcdom
ntlm server ad-group-search ldap-search-port 506
ntlm server ad-group-search enable
authentication login local enable primary
authentication configuration local enable secondary
authentication configuration tacacs enable primary
authentication fail-over server-unreachable
aaa accounting commands 0 default start-stop tacacs
aaa accounting system default start-stop tacacs
access-lists 300 deny groupname Marketing
access-lists 300 permit groupname "Tech Pubs"
access-lists 300 permit groupname Manufacturing
acquirer proxy authentication outgoing 10.77.155.221 8080 admin password **** ntlm
my_domain basic-auth-disable
acquirer proxy authentication transparent u password ****
url-filter http websense server 1.2.3.4
url-filter http websense server local
url-filter http N2H2 server 172.16.22.10 port 4008 timeout 20
mediafs-division wmt-cache-space 30 real-cache-space 70
tftp-server dir /local1/tftpdir
tftp-server dir /local1/tftp
tftp-server gw proto http server 172.16.5.6 pri 1
tftp-server gw proto http server 172.16.7.10 pri 2
tftp-server access-list std_acl
cms rpc timeout incoming-wait 80
banner motd message "____________________________________________________________________
\n| ***WARNING***
|\n| YOU HAVE CONNECTED TO THE DOC CE
|\n| THIS CE IS USED FOR TESTING CONFIGS
|\n| FOR USER DOCS
|\n___________________________________________________
banner login message "This is login banner.\nUse your password to login\n"
network-filesystem server cifs share-web-site cisco.com share-auth-content
bandwidth real-server 10 start-time Monday 08:00 end-time Friday 18:00
bandwidth wmt incoming 20000 start-time Monday 13:00 end-time Monday 15:00
bandwidth cisco-streaming-engine 20000 start-time Friday 14:00 end-time Saturday 17:00
bandwidth http 2000 default
! End of ACNS configuration
Related Commands
configure
copy running-config
copy startup-config
show services
To display services-related information, use the show services EXEC command.
show services {ports [port-num] | summary}
Syntax Description
ports
|
Displays services by port number.
|
port-num
|
(Optional) Up to 8 port numbers (1-65535).
|
summary
|
Displays the services summary.
|
Defaults
No default behavior or values
Command Modes
EXEC
Examples
The following example displays the services information by the port number:
ContentDistributionManager# show services ports
Service information by port
---------------------------
550 Started on Mon Oct 14 12:13:20 2002
553 Started on Mon Oct 14 12:13:20 2002
554 Started on Mon Oct 14 12:13:20 2002
15256 Started on Mon Oct 14 12:13:20 2002
27999 Started on Mon Oct 14 12:13:20 2002
28000 Started on Mon Oct 14 12:13:20 2002
The following example displays a services information summary, showing the service and the associated port numbers:
ContentDistributionManager# show services summary
-----------------------------------------------------
CMS 15256 2000 2001 2002 2003 2004 2005
Real_Proxy 1090 8082 9002 555 28000 7879 6060 7071 30
Real_Server 7070 8081 9091 27999 7878 7802 1554 3030 40
temp_RPC_APACHE_PORT 8008
Cisco_Streaming_Engine 550 SNMP
show snmp
To check the status of SNMP communications, use the show snmp EXEC command.
show snmp {alarm-history | engine ID | event | group | stats | user}
Syntax Description
alarm-history
|
Displays SNMP alarm history information.
|
engineID
|
Displays the local SNMP engine identifier.
|
event
|
Displays events configured through the Event MIB.
|
group
|
Displays SNMP groups.
|
stats
|
Displays SNMP statistics.
|
user
|
Displays SNMP users.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
This command provides information on various SNMP variables and statistics on SNMP operations.
Examples
Table 2-94 describes the fields shown in the snmp alarm-history display.
Table 2-94 show snmp alarm-history Field Descriptions
Field
|
Description
|
Index
|
Serial number of the listed alarms.
|
Type
|
Status of whether the alarm has been Raised or Cleared.
|
Sev
|
Levels of alarm severity (Critical, Major, or Minor).
|
Alarm ID
|
Traps sent by an ACNS device contain numeric alarm IDs.
|
ModuleID
|
Traps sent by an ACNS device contain numeric module IDs. See Table 2-95 to map module names to module IDs.
|
Category
|
Traps sent by an ACNS device contain numeric category IDs. See Table 2-96 to map category names to category IDs.
|
Descr
|
Description of the ACNS software alarm and the application that generated the alarm.
|
Table 2-95 Mapping of Module Names to Module IDs
Module Name
|
Module ID
|
acquirer
|
4000
|
AD_DATABASE
|
8000
|
cms
|
3000
|
MULTICAST_DATA_SENDER
|
7000
|
NHM
|
1
|
NHM/NHM
|
2500
|
nodemgr
|
2000
|
standby
|
4000
|
sysmon
|
1000
|
UNICAST_DATA_RECEIVER
|
5000
|
UNICAST_DATA_SENDER
|
6000
|
Table 2-96 Mapping of Category Names to Category IDs
Category Name
|
Category ID
|
Communications
|
1
|
Service Quality
|
2
|
Processing Error
|
3
|
Equipment
|
4
|
Environment
|
5
|
Content
|
6
|
Table 2-97 describes the fields shown in the show snmp stats display.
Table 2-97 show snmp stats 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.
|
Table 2-98 describes the fields shown in the show snmp engineID display.
Table 2-98 show snmp engineID Field Descriptions
Field
|
Description
|
Local SNMP Engine ID
|
String that identifies the copy of SNMP on the local device.
|
Table 2-99 describes the fields shown in the show snmp event display. The show snmp event command displays information about the SNMP events that were set using the snmp trigger command:
Table 2-99 show snmp event Field Descriptions
Field
|
Description
|
Mgmt Triggers
|
Output for management triggers, which are numbered 1, 2, 3, and so on in the output.
|
(1): Owner:
|
Name of the person who configured the trigger. "CLI" is the default owner; the system has a default trigger configured.
|
(1):
|
Name for the trigger. This name is locally-unique and administratively assigned. For example, this field might contain the "isValid" trigger name. Numbering indicates that this is the first management trigger listed in the show output.
|
Comment:
|
Description of the trigger's function and use. For example: WAFS license file is not valid.
|
Sample:
|
Basis on which the test sample is being evaluated. For example: Abs (Absolute) or Delta.
|
Freq:
|
Frequency. Number of seconds to wait between trigger samplings. To encourage consistency in sampling, the interval is measured from the beginning of one check to the beginning of the next and the timer is restarted immediately when it expires, not when the check completes.
|
Test:
|
Type of trigger test to perform based on the SNMP trigger configured. The Test field may contain the following types of tests:
Absent—Absent existence of a test
Boolean—Boolean value test
Equal—Equality threshold test
Falling—Falling threshold test
Greater-than—Greater-than threshold test
Less-than—Less-than threshold test
On-change—Changed existence test
Present—Present present test
Rising—Rising threshold test
|
ObjectOwner:
|
Name of the object owner who created the trigger using the snmp trigger create global configuration command or by using an SNMP interface. "CLI" is the default owner.
|
Object:
|
String identifying the object.
|
Boolean Entry:
|
Value:
|
Object identifier of the MIB object to sample to see whether the trigger should fire.
|
Cmp:
|
Comparison. Type of boolean comparison to perform. The numbers 1-6 correspond to these Boolean comparisons:
unequal (1)
equal (2)
less (3)
lessOrEqual (4)
greater (5)
greaterOrEqual (6)
|
Start:
|
Starting value for which this instance will be triggered.
|
ObjOwn:
|
Object owner.
|
Obj:
|
Object.
|
EveOwn:
|
Event owner.
|
Eve:
|
Event. Type of SNMP event. For example: CLI_EVENT.
|
Delta Value Table:
|
Table containing trigger information for delta sampling.
|
(0):
|
Thresh:
|
Threshold value to check against if the trigger type is threshold.
|
Exis:
|
Type of existence test to perform. Values are 1 or 0.
|
Read:
|
Indicates whether the MIB instance has been queried or not.
|
OID:
|
Object ID (Same as MIB instance).
|
val:
|
Value ID.
|
(2):
|
MIB instance on which the trigger is configured. This is the second management trigger listed in the show output. The fields are repeated for each instance listed in this show command.
|
Table 2-100 describes the fields shown in the show snmp group display.
Table 2-100 show snmp group Field Descriptions
Field
|
Description
|
groupname
|
Name of the SNMP group, or collection of users who have a common access policy.
|
security_model
|
Security model used by the group (either v1, v2c, or v3).
|
readview
|
String identifying the read view of the group.
|
writeview
|
String identifying the write view of the group.
|
notifyview
|
string identifying the notify view of the group.
|
Table 2-101 describes the fields shown in the show snmp user display.
Table 2-101 show snmp user Field Descriptions
Field
|
Description
|
User name
|
String identifying the name of the SNMP user.
|
Engine ID
|
String identifying the name of the copy of SNMP on the device.
|
Group Name
|
Name of the SNMP group, or collection of users who have a common access policy.
|
Related Commands
snmp-server community
snmp-server contact
snmp-server enable traps
snmp-server group
snmp-server host
snmp-server location
snmp-server mib
snmp-server notify
snmp-server user
snmp-server view
show ssh
To display Secure Shell (SSH) status and configuration information, use the show ssh EXEC command.
show ssh
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Examples
Table 2-102 describes the fields shown in the show ssh display.
Table 2-102 show ssh Field Descriptions
Field
|
Description
|
SSH server supports SSH2 protocol (SSH1 compatible).
|
Protocol support statement.
|
SSH service is not enabled.
|
Status of whether the SSH service is enabled or not enabled.
|
Currently there are no active SSH sessions.
|
Number of active SSH sessions.
|
Number of successful SSH sessions since last reboot:
|
Number of successful SSH sessions since last reboot.
|
Number of failed SSH sessions since last reboot:
|
Number of failed SSH sessions since last reboot.
|
SSH key has not been generated or previous key has been removed.
|
Status of the SSH key.
|
SSH login grace time value is 300 seconds.
|
Time allowed for login.
|
Allow 3 password guess(es).
|
Number of password guesses allowed.
|
Related Commands
sshd
ssh-key-generate
show standby
To display standby interface information, use the show standby EXEC command.
show standby
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
To display information about a specific standby group configuration, enter the show interface standby standby group_num EXEC command.
Examples
Table 2-103 describes the fields shown in the show standby display.
Table 2-103 show standby Field Descriptions
Field
|
Description
|
Standby Group
|
Number that identifies the standby group.
|
Description
|
Description of the device, as configured by using the description option of the interface global configuration command.
|
IP address
|
IP address of the standby group.
|
netmask
|
Netmask of the standby group.
|
Member interfaces
|
Member interfaces of the standby group. Shows which physical interfaces are part of the standby group. Shows the interface definition, such as GigabitEthernet 1/0.
|
priority
|
Priority status of each interface.
|
Active interface
|
Interfaces that are currently active in the standby group.
|
Maximum errors allowed on the active interface
|
Maximum number of errors allowed on the active interface.
|
Related Commands
show interface
show running-config
show startup-config
standby
show startup-config
To display the startup configuration, use the show startup-config EXEC command.
show startup-config
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
Use this command to display the configuration used during an initial bootup, stored in nonvolatile random-access memory (NVRAM).
Examples
The following example displays the startup configuration details on the Content Engine:
ContentEngine# show startup-config
alarm overload-detect raise 10 clear 9
http authentication realm "Cache"
http append via-header custom "cust"
http avoid-multiple-auth-prompts
http proxy incoming 80 8888
http proxy outgoing host 10.77.155.221 8090 primary
http proxy outgoing host 10.77.155.221 8080
http proxy outgoing monitor 10
http proxy outgoing connection-timeout 2000
http proxy outgoing origin-server
http proxy outgoing preserve-407
tcp client-rw-timeout 360
tcp client-receive-buffer 28
http max-ttl days text 5 binary 8
http tcp-keepalive enable
http monitor url http://www.cisco.com
ftp-over-http reval-each-request directory-listing
clock timezone Etc/GMT 0 0
https proxy incoming 1 2 3 4
https proxy outgoing host 10.77.155.221 8080 primary
https proxy outgoing host 1.2.3.4 2
https proxy outgoing host 1.2.3.41 4
https proxy outgoing host 1.2.3.42 5
https proxy outgoing host 1.2.3.43 3
https proxy outgoing host 1.2.3.45 6
https proxy outgoing host 1.2.3.47 7
https proxy outgoing host 1.2.3.48 8
https proxy outgoing monitor 20
https proxy outgoing connection-timeout 3000
https proxy outgoing origin-server
https destination-port allow all
description This is Ether Channel interface
ip access-group extended_ip_acl in
ip address 10.10.10.10 255.0.0.0
ip address 120.0.0.9 255.255.0.0
description This is an interface that acts as a backup
ip address 1.2.3.4 255.0.0.0
interface FastEthernet 0/0
description This is the primary interface
ip address 10.1.1.21 255.255.255.0
interface FastEthernet 0/1
ip default-gateway 10.1.1.50
primary-interface FastEthernet 0/0
wmt license-key xxxyyyxxx
wmt accept-license-agreement
wmt transaction-logs format extended wms-90
rtsp server real-subscriber accept-license-agreement
multicast accept-license-agreement
ip name-server 171.69.11.48
ip access-list standard std_acl
ip access-list extended ext_acl_2
ip access-list extended extended_ip_acl
permit tcp any eq 2 any eq exec
external-ip 128.107.192.148
logging console priority alert
logging disk priority alert
ntp server 128.107.192.168
bypass static any-client 1.2.3.4
bypass auth-traffic enable
bypass load time-interval 6
proxy-protocols outgoing-proxy exclude enable
icp client add-remote-server 10.2.3.4 sibling icp-port 3130 http-port 3128 restrict (8)
icp server remote-client 10.0.0.1 no-fetch
icp server remote-client 10.1.1.1 no-fetch
wccp router-list 1 10.1.1.1 172.19.226.63
wccp router-list 3 1.4.5.6
wccp router-list 5 1.2.3.4 2.3.4.5
wccp port-list 4 1 2 3 4 5 6 7
wccp port-list 5 90 91 1026 127 1068 1098 19 178
wccp web-cache mask dst-ip-mask 0xfe000000
wccp reverse-proxy mask dst-ip-mask 0xfe00
wccp ftp-native mask src-ip-mask 0xfc000000 dst-ip-mask 0x1000000
wccp custom-web-cache router-list-num 1 port 31
wccp dns router-list-num 1
wccp ftp-native router-list-num 1 password pass l2-redirect mask-assign
wccp https-cache accept-all
wccp shutdown max-wait 15
https server name protocol-version sslv2-only
dns pin forward host1 1.2.3.4
rule action no-auth pattern-list 9
rule action block pattern-list 1
rule action block pattern-list 10
rule action allow pattern-list 2
rule action allow pattern-list 5
rule action no-url-filtering pattern-list 5
rule action no-url-filtering pattern-list 6
rule action use-proxy 10.77.155.221 80 failover pattern-list 1
rule action use-proxy 10.77.155.221 80 failover pattern-list 510
rule action append-username-header pattern-list 3
rule action use-icap-service icapser pattern-list 25
rule pattern-list 1 dst-port 9090
rule pattern-list 1 domain acme.com
rule pattern-list 1 domain yahoo.com
rule pattern-list 1 domain \.foo.com
rule pattern-list 1 domain \.cisco.com
rule pattern-list 1 domain \.cisco.com,bar.com
rule pattern-list 2 username user,r
rule pattern-list 2 username user,r,rt
rule pattern-list 6 domain cisco.com
rule pattern-list 9 dst-ip 1.2.3.4 255.0.0.0
rule pattern-list 10 domain yahoo.com
rule pattern-list 72 domain yahoo.com
rule pattern-list 510 domain acme.com
icap apply rules-template
icap append-x-headers x-server-ip
icap rescan-cache ISTag-change
vector-point reqmod-precache
vector-point respmod-precache
load-balancing weighted-load
vector-point reqmod-precache
vector-point reqmod-postcache
vector-point respmod-precache
error-handling return-error
server icap://10.1.1.1:1344/test-icap
server icap://1.0.0.1/icapser
server icap://1.2.3.4/servforicap
websense-server service policy local activate
websense-server service eim activate
rtsp proxy media-real accept-license-agreement
rtsp ip-address 114.116.115.112
rtsp advanced bypass-gateway media-real
transaction-logs log-windows-domain
transaction-logs export enable
transaction-logs format custom "ZXZX"
username admin password 1 .RQrsujYFEO0U
username admin privilege 15
username nkurahas password 1 meYjSh.Ip.RXA uid 2002
username nkurahas privilege 0
username sample1 password 1 OszWHEZOgfYcA uid 2003
username sample1 privilege 0
username sample2 password 1 Cs2klvDtNE5lA uid 2004
username sample2 privilege 0
username pdelay password 1 etLYMNNMAPKeI uid 2001
username pdelay privilege 0
username hari password 1 791lvYweJxoc2 uid 65535
username hari privilege 0
username hari cifs-password 1 2FEE38AC020EA782AAD3B435B51404EE
E7AA6786F8D97524A6F44C206C274FC9
username savenugo password 1 boHitrTDO6yvE uid 2005
username savenugo privilege 0
username hg password 1 EuXx0Jp9Y5bnM uid 2006
username fromcli password 1 OuQ4SisW2PQEk uid 2007
username fromcli privilege 0
username h password 1 MucRaMZMhbWsQ uid 2008
username use password 1 7uSBQDu55xg/E uid 2009
username pat password 1 w1RcmUw0WWEF2 uid 2010
username pat privilege 15
snmp-server enable traps config
snmp-server enable traps content-engine disk-read
snmp-server enable traps content-engine disk-write
snmp-server enable traps content-engine disk-fail
snmp-server enable traps content-engine overload-bypass
snmp-server enable traps content-engine transaction-log
snmp-server enable traps alarm raise-critical
snmp-server enable traps alarm clear-critical
snmp-server enable traps alarm raise-major
snmp-server enable traps alarm raise-minor
snmp-server enable traps entity
snmp-server enable traps snmp authentication
snmp-server enable traps snmp cold-start
snmp-server mib persist event
snmp-server host 1.1.1.1 com
snmp-server user user1 group1 auth sha admin
snmp-server user admin group2 remote 7
snmp-server user snmp_user1 group3 remote 56 auth md5 ad priv ad
snmp-server view view1 entityMIB included
snmp-server community community1
snmp-server notify inform
snmp-server access-list 5
radius-server key encrkey
radius-server host 10.77.7.7 auth-port 1645
tacacs host 172.9.26.12 primary
ntlm server ad-group-search enum-user username user1
ntlm server ad-group-search enum-user password pass
ntlm server ad-group-search enum-user domain dom1
ntlm server ad-group-search gc-server host 172.16.30.45 domain gcdom
ntlm server ad-group-search ldap-search-port 506
ntlm server ad-group-search enable
authentication login local enable primary
authentication configuration local enable secondary
authentication configuration tacacs enable primary
authentication fail-over server-unreachable
aaa accounting commands 0 default start-stop tacacs
aaa accounting system default start-stop tacacs
access-lists 300 deny groupname Marketing
access-lists 300 permit groupname "Tech Pubs"
access-lists 300 permit groupname Manufacturing
acquirer proxy authentication outgoing 10.77.155.221 8080 admin password default ntlm
my_domain basic-auth-disable
acquirer proxy authentication transparent u
url-filter http websense server 1.2.3.4
url-filter http websense server local
url-filter http N2H2 server 1.2.3.4 port 56 timeout 3
mediafs-division wmt-cache-space 30 real-cache-space 70
tftp-server dir /local1/tftpdir
tftp-server dir /local1/tftp
tftp-server gw proto http server 172.16.5.6 pri 1
tftp-server gw proto http server 172.16.7.10 pri 2
tftp-server access-list std_acl
cms rpc timeout incoming-wait 80
cms database maintenance regular schedule every-day at 00:00
cms database maintenance full schedule every-day at 00:00
disk error-handling threshold 100
disk error-handling reload
banner motd message "____________________________________________________________________
\n| ***WARNING***
|\n| YOU HAVE CONNECTED TO THE DOC CE
|\n| THIS CE IS USED FOR TESTING CONFIGS
|\n| FOR USER DOCS
|\n___________________________________________________
banner login message "This is login banner.\nUse your password to login\n"
network-filesystem server cifs share-web-site cisco.com share-auth-content
bandwidth real-server 10 start-time Monday 08:00 end-time Friday 18:00
bandwidth wmt incoming 20000 start-time Monday 13:00 end-time Monday 15:00
bandwidth cisco-streaming-engine 20000 start-time Friday 14:00 end-time Saturday 17:00
bandwidth http 2000 default
! End of ACNS configuration
Related Commands
configure
copy running-config
show running-config
show statistics access-lists 300
To display Content Engine access control list statistics, use the show statistics access-lists 300 EXEC command.
show statistics access-lists 300
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
The access control list statistics display the number of access requests, denials, and permissions recorded. Use the show statistics access-lists 300 command to display the number of group name accesses recorded.
Examples
Table 2-104 describes the fields shown in the show statistics access-lists 300 display.
Table 2-104 Field Descriptions for the show statistics access-lists 300 Command
Field
|
Description
|
Access Control Lists Statistics
|
Groupname and username-based List
|
Lists the group name-based access control lists.
|
Number of requests
|
Number of requests.
|
Number of deny responses
|
Number of deny responses.
|
Number of permit responses
|
Number of permit responses.
|
Related Commands
clear statistics
show statistics acquirer
To display Content Engine acquirer channel statistics, use the show statistics acquirer EXEC command.
show statistics acquirer [channel-id channel-num | channel-name channel-name | contents
{channel-id channel-num | channel-name channel-name} | errors {channel-id channel-num |
channel-name channel-name} | job-list {channel-id channel-num | channel-name
channel-name}]
Syntax Description
channel-id
|
(Optional) Displays the acquirer statistics for the specified channel number.
|
channel-num
|
Channel number.
|
channel-name
|
(Optional) Displays the acquirer statistics for the specified channel name.
|
channel-name
|
Channel name.
|
contents
|
(Optional) Displays the acquired contents of the specified channel.
|
channel-id
|
Displays the acquired contents of the specified channel number.
|
channel-name
|
Displays the acquired contents of the specified channel name.
|
errors
|
(Optional) Displays the acquisition error logs for the specified channel.
|
channel-id
|
Displays the acquisition error logs for the specified channel number.
|
channel-name
|
Displays the acquisition error logs for the specified channel name.
|
job-list
|
(Optional) Displays the job list statistics for the specified channel.
|
channel-id
|
Displays the job list statistics for the specified channel number.
|
channel-name
|
Displays the job list statistics for the specified channel name.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
The show statistics acquirer command displays acquirer statistics for all channels for which the Content Engine is the root Content Engine. The output of the command displays any manifest file parsing or fetch errors if any errors occur. It displays the total number of acquired objects, number of failed objects, and total disk space used by the acquired objects. When a channel ID or name is specified, acquirer statistics are displayed for that channel specified by ID or name.
The show statistics acquirer contents command displays all the acquired content, its size, and its last-modified time, specified by channel ID or name.
The show statistics acquirer errors command displays acquisition errors, if any, for the channel specified by ID or name. Manifest file parsing and fetch errors, as well as single item or crawler job errors, are displayed.
The show statistics acquirer job-list command displays the details of all the single items and crawler jobs for the channel specified by ID or name.
Examples
Table 2-105 describes the fields shown in the show statistics acquirer display.
Table 2-105 show statistics acquirer Field Descriptions
Field
|
Description
|
Statistics For Channel ID: channel-id
|
Channel-id
|
Channel identification number.
|
Channel-Name
|
Name of the channel.
|
Manifest
|
Fetch Errors
|
Number of manifest file fetch errors.
|
Parsing Errors
|
Number of manifest file parsing errors.
|
Acquisition
|
Total Number of Acquired Objects
|
Total number of acquired objects.
|
Total Size of Acquired Objects (Bytes)
|
Total size of acquired objects (in bytes).
|
Total Number of Failed Objects
|
Total number of failed objects.
|
Related Commands
acquirer
clear statistics
show acquirer
show statistics authentication
To display Content Engine authentication statistics, use the show statistics authentication EXEC command.
show statistics authentication
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
Authentication statistics displays the number of access requests, denials, and allowances recorded. Use the show statistics authentication command to display the number of authentication accesses recorded.
Examples
Table 2-106 describes the fields shown in the show statistics authentication display.
Table 2-106 Field Descriptions for the show statistics authentication Command
Field
|
Description
|
Authentication Statistics
|
Number of access requests
|
Number of access requests.
|
Number of access deny responses
|
Number of access deny responses.
|
Number of access allow responses
|
Number of access allow responses.
|
Related Commands
authentication
clear statistics
show authentication
show statistics authentication
show statistics bandwidth
To display Content Engine bandwidth statistics, use the show statistics bandwidth EXEC command.
show statistics bandwidth advanced [errors]
Syntax Description
advanced
|
Displays the WMT server bandwidth allocation statistics.
|
errors
|
(Optional) Display statistics about bandwidth allocation errors.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
The show statistics bandwidth advanced errors EXEC command displays statistics about bandwidth allocation errors. The command output shows the time the allocation error occurred, the client from which the request was received, and the amount of allocated bandwidth that was requested.
Examples
Table 2-107 describes the fields shown in the show statistics bandwidth advanced display.
Table 2-107 show statistics bandwidth advanced Field Descriptions
Field
|
Description
|
WMT Server Bandwidth Allocation Statistics
|
Description
|
Rule for which bandwidth statistics apply.
|
Subnet
|
Configured subnet to match.
|
Used Bw
|
Currently used bandwidth (in kilobits per second) for each specified rule in the advanced configuration file
|
Used Bw
|
Currently available bandwidth (in kilobits per second) for each specified rule in the configuration file
|
Related Commands
bandwidth (global configuration mode)
show statistics bypass
To display Content Engine bypass statistics, use the show statistics bypass EXEC command.
show statistics bypass [auth-traffic | load | summary]
Syntax Description
auth-traffic
|
(Optional) Displays authenticated traffic bypass statistics.
|
load
|
(Optional) Displays load bypass statistics.
|
summary
|
(Optional) Displays a summary of bypass statistics.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
To preserve cache transparency and avoid service disruption, the Content Engine can bypass authentication traffic and automatically generate a dynamic access list for the selected client/server pairs. When dynamic authentication bypass is enabled, use the show statistics bypass auth-traffic command option to display the bypass statistics.
If the Content Engine is overloaded with traffic, it can reroute the excess traffic with the overload bypass feature. When the bypass load command is enabled, the Content Engine refuses additional requests and forwards them to the origin servers. To display overload bypass statistics, use the show statistics bypass load command option.
To display a summary of the bypass statistics, use the show statistics bypass or show statistics bypass summary command option.
Examples
Table 2-108 describes the fields shown in the show statistics bypass display.
Table 2-108 show statistics bypass Field Descriptions
Field
|
Description
|
Total number of HTTP connections bypassed
|
Total number of HTTP connections bypassed.
|
Connections bypassed due to system overload
|
Number of connections bypassed due to system overload.
|
Connections bypassed due to authentication issues
|
Number of connections bypassed due to authentication issues.
|
Connections bypassed to facilitate error transparency
|
Number of connections bypassed to facilitate error transparency.
|
Connections bypassed due to static configuration
|
Number of connections bypassed due to static configuration.
|
Total number of entries in the bypass list
|
Total number of entries in the bypass list.
|
Number of Authentication bypass entries
|
Number of authentication bypass entries.
|
Number of Error bypass entries
|
Number of error bypass entries.
|
Number of Static Configuration entries
|
Number of static configuration entries.
|
Related Commands
bypass
clear statistics
show bypass
show statistics cdnfs
To display Content Engine ACNS network file system (cdnfs) statistics, use the show statistics cdnfs EXEC command.
show statistics cdnfs
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Examples
Table 2-109 describes the show statistics cdnfs command fields displayed in the command output.
Table 2-109 show statistics cdnfs Fields
Field
|
Description
|
size of physical file system
|
Physical disk size of the ACNS network file system.
|
space assigned for CDNFS purposes
|
Amount of physical disk space on the ACNS network file system that has been assigned to hold pre-positioned objects. The space can be less than the size of the file system; for example, if mediafs space has been assigned.
|
number of CDNFS entries
|
Number of cdnfs objects in the ACNS network file system.
Note One pre-positioned file internally uses two cdnfs entries. The count of cdnfs entries will be twice the number of actual files displayed to users.
|
space reserved for CDNFS entries
|
Amount of disk space reserved for existing pre-positioned objects. This space is reserved for cdnfs objects before the file is created and written to the file system.
|
available space for new entries
|
Amount of physical disk space available in the ACNS network file system for new pre-positioned objects.
|
ACNS 4.x legacy ECDN files (total)
|
Total quantity of disk space in the ACNS network file system being consumed by files left over from ACNS 4.x.
|
ACNS 4.x legacy ECDN files (unused)
|
Quantity of disk space in the ACNS network file system being consumed by unused files left over from ACNS 4.x (these files can be removed by the cdnfs delete-unused-ecdnfs-files EXEC command).
|
physical file system in use
|
Amount of physical disk space currently in use by the ACNS network file system.
|
physical file system space free
|
Amount of unused physical disk space in the ACNS network file system.
|
physical file system percentage in use
|
Percentage of physical disk space in use relative to the total disk space available.
|
Related Commands
cdnfs
clear statistics
show cdnfs
show disks details
show statistics cfs
To display Content Engine cache file system (cfs) statistics, use the show statistics cfs EXEC command.
show statistics cfs
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
Cache objects retrieved from the web are saved and manipulated with the cfs on a cfs partition of the hard disk. The cfs partition does not affect the sysfs, swfs, or mediafs partitions. To display the statistics of the hard disk cache file system, use the show statistics cfs command. Cache file system hard disk statistics include total disk space, disk space used, object read-write statistics, byte read-write statistics, and read-write error statistics.
Examples
Table 2-110 describes the fields shown in the show statistics cfs display.
Table 2-110 show statistics cfs Field Descriptions
Field
|
Description
|
CFS Statistics
|
Volume x
|
Cache file system (CFS) volume based on the disk configurations. Normally, one volume per disk maps to the CFS disk partition.
|
Total disk space
|
Total amount of disk space available in bytes.
|
Total disk space used
|
Total amount of disk space used so far for caching content.
|
Total disk objects read
|
Total number of cached segments read from the disk. Large URL objects could span several segments.
|
Total disk objects write
|
Total number of cached segments written to the disk. Large URL objects could span several segments.
|
Total bytes of disk read
|
Total number of bytes read from the disk.
|
Total bytes of disk write
|
Total number of bytes written to the disk.
|
Disk read errors
|
Number of disk read errors encountered.
|
Disk write errors
|
Number of disk write errors encountered.
|
Related Commands
cfs
clear statistics
show cfs
show statistics cifs-server
To display the CIFS server statistics, use the show statistics cifs-server EXEC command.
show statistics cifs-server
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
The number of bytes served by the Content Engine, or bandwidth usage, is defined as the number of outgoing bytes per second used by the CIFS server running on the Content Engine during the period allowed for that type of bandwidth. The number of bytes served value does not take into account the TCP/UDP or lower layer protocol overhead.
The total number of bytes output by the CIFS server (outgoing bytes) is defined as the number of bytes passing between the Content Engine on which an application server such as CIFS is running and the clients or children Content Engines (in case of a hierarchy of Content Engines).
Examples
Table 2-111 describes the fields shown in the show statistics cifs-server display.
Table 2-111 show statistics cifs-server Field Descriptions
Field
|
Description
|
CIFS Server Statistics
|
Total bytes served
|
Total number of bytes served.
|
Total files served
|
Total number files served.
|
Related Commands
network-filesystem server (global configuration mode)
clear statistics cifs-server
show statistics content-distribution-network
To display the status of a Content Engine or device group for an ACNS network, use the show statistics content-distribution-network EXEC command. This command is available on Content Distribution Manager devices only.
show statistics content-distribution-network device status device_id
Syntax Description
device
|
Displays the status of a Content Engine or device group for the ACNS network.
|
status
|
Displays the status of the Content Engine or device group.
|
device_id
|
Name or ID of the device or device group.
|
Defaults
No default behavior or values
Command Modes
EXEC
Usage Guidelines
Use the show statistics content-distribution-network EXEC command to display the identification details of a Content Engine or Content Engines in a device group for an ACNS network, and verify if a Content Engine is online.
Examples
Table 2-112 describes the fields shown in the Content Distribution Manager show statistics cifs-server display for a particular device that is registered with the Content Distribution Manager.
Table 2-112 show statistics content-distribution-network device status Field Descriptions
Field
|
Description
|
Device id
|
Name or ID of the device or device group.
|
name
|
Name of the device.
|
status
|
Status of the device or device group. Values are Online, Offline, or Pending.
|