- 9361crf
- Preface
- Command Line Interface Command Summary
- Cisco ACNS Software Commands - aaa accounting to clear
- Cisco ACNS Software Commands - clock to hostname
- Cisco ACNS Software Commands - http to ldap
- Cisco ACNS Software Commands - less to rtsp (global config)
- Cisco ACNS Software Commands - rtsp to show hardware
- Cisco ACNS Software Commands - show hosts to show statistics content-distribution-network
- Cisco ACNS Software Commands - show statistics content-routing to show statistics tvout
- Cisco ACNS Software Commands - show statistics udp to tacacs
- Cisco ACNS Software Commands - tcp to wccp router-list
- Cisco ACNS Software Commands - wccp rtsp to write
- Appendix A: Acronyms
- Appendix B: Standard Time Zones
Cisco ACNS Software Command Reference, Release 5.5
- Updated:
- February 9, 2018
Chapter: Cisco ACNS Software Commands - show hosts to show statistics content-distribution-network
- 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
show hosts
To view the hosts on your Content Engine, use the show hosts EXEC command.
Syntax Description
Defaults
Command Modes
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.
|
|
|
|---|---|
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
Displays the configuration of HTTP headers appended by the Content Engine. |
|
Displays the NT LAN Manager (NTLM) authentication header configuration. |
|
Displays HTTP bandwidth settings for pre-positioned HTTP traffic. |
|
Displays the configuration for caching of authenticated web objects. |
|
Displays the configuration for caching of all authenticated web objects. |
|
Displays the configuration for caching of basic authenticated web objects. |
|
Displays the configuration for caching of NTLM authenticated web objects. |
|
Displays the configuration for caching of web objects with associated cookies. |
|
Displays the configuration for caching of objects with Vary headers. |
|
Displays the configuration for managing of no-cache requests. |
|
(Optional) Message; see Table 2-5 . |
|
(Optional) Displays the errors for which custom error pages are configured. |
|
Displays the configuration of the fast HTTP client response. |
|
(Optional) Displays supported HTTP request methods. The supported methods include both default and configured HTTP request methods. |
|
(Optional) Displays HTTP request methods that are not supported but used in HTTP requests received by the Content Engine. |
|
(Optional) Displays information about all the monitored URLs. |
|
(Optional) Displays monitoring information for a specified URL. |
|
Displays the strict request content length checking configuration. |
|
Defaults
Command Modes
Examples
The following example lists the configuration and status of HTTP:
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:
The following example shows that the healing client is enabled:
The following example shows the IP address and port numbers of the HTTP incoming and outgoing proxy modes:
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.
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:
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.
Syntax Description
Defaults
Command Modes
Examples
The following example displays the authentication cache information:
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
Defaults
Command Modes
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:
The following example displays the HTTPS proxy configuration details:
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
Defaults
Command Modes
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:
Related Commands
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
Defaults
Command Modes
Examples
The following examples of show icp commands list the cache parameters of the client, root, and client/server root, respectively:
Related Commands
show inetd
To display the status of TCP/IP services, use the show inetd EXEC command.
Syntax Description
Defaults
Command Modes
Examples
The following example displays the enabled or disabled status of TCP/IP services:
Related Commands
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
Defaults
Command Modes
Examples
Table 2-75 describes the fields shown in the show interface FastEthernet display.
Table 2-76 describes the fields shown in the show interface PortChannel display.
Table 2-77 describes the field shown in the show interface scsi display.
|
|
|
|---|---|
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.
Related Commands
show inventory
To display the system inventory information, use the show inventory EXEC command.
Syntax Description
Defaults
Command Modes
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:
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):
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.
|
|
|
|---|---|
Version ID number of the device. Displays as 0 if the version number is not available. |
|
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:
Related Commands
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
Defaults
Command Modes
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:
Examples
The following example shows sample output from the show ip access-list command:
1 permit 10.1.1.2
The following example shows sample output from the show ip access-list command for the access list named test:
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.
Syntax Description
Defaults
Command Modes
Examples
The show ip routes command displays the IP routing table.
Table 2-80 describes the fields shown in the show ip routes display.
|
|
|
|---|---|
Related Commands
show ldap
To display the Lightweight Directory Access Protocol (LDAP) parameters, use the show ldap EXEC command.
Syntax Description
Defaults
Command Modes
Examples
Table 2-81 describes the fields shown in the show ldap display.
Related Commands
show logging
To display the system message log configuration, use the show logging EXEC command.
Syntax Description
Defaults
Command Modes
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
'[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
application.
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:
Related Commands
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.
Syntax Description
Defaults
Command Modes
Usage Guidelines
Examples
The following example displays the media file system information:
Related Commands
show memory
To display memory blocks and statistics, use the show memory EXEC command.
Syntax Description
Defaults
Command Modes
Examples
Table 2-82 describes the fields shown in the show memory display.
|
|
|
|---|---|
show multicast
To display a multicast client configuration and license, use the show multicast EXEC command.
show multicast [ license-agreement ]
Syntax Description
Defaults
Command Modes
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:
Related Commands
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
Defaults
Command Modes
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.
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.
show ntlm
To display Microsoft Windows NT LAN Manager (NTLM) parameters, use the show ntlm EXEC command.
Syntax Description
Defaults
Command Modes
Examples
Table 2-85 describes the fields shown in the show ntlm display.
Related Commands
show ntp
To display the Network Time Protocol (NTP) parameters, use the show ntp EXEC command.
Syntax Description
Defaults
Command Modes
Examples
Table 2-86 describes the fields shown in the show ntp status display.
Related Commands
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
Defaults
Command Modes
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.
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.
where n can be a value of 1 to 5.
For CE_NAME_n, the PAC file server substitutes the name of the n th closest proxy. For CE_IPADDR_n, the PAC file server substitutes the IP address of the n th closest proxy. If there is no n th 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:
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:
{
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
show pre-load
To display information about the preload configuration, use the show pre-load EXEC command.
Syntax Description
Defaults
Maximum number of concurrent requests: 25
Command Modes
Examples
Table 2-87 describes the fields shown in the show pre-load display.
Related Commands
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
Defaults
Command Modes
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.
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
Defaults
Command Modes
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:
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:
– 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
– Live stream transmitted from a third-party encoder or an IP/TV Broadcast Server
– Pre-positioned content stored on Content Engines
– A set of Content Engines or device groups
– Unicast or multicast live events
– Multicast scheduled rebroadcasts
– Looping forever (enabled or disabled)
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 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:
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:
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.
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.
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.
|
|
|
|---|---|
Date and time at which the program is scheduled to start the next time. |
|
Table 2-90 describes the fields shown in the show programs program-name display.
show proxy-auto-config
To display the state of the browser autoconfiguration feature, use the show proxy-auto-config EXEC command.
Syntax Description
Defaults
Command Modes
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:
Related Commands
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
Defaults
Command Modes
Examples
The following example displays the outgoing proxy exclude status:
Related Commands
show radius-server
To display RADIUS information, use the show radius-server EXEC command.
Syntax Description
Defaults
Command Modes
Examples
Table 2-91 describes the fields shown in the show radius-server display.
Related Commands
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
Defaults
Command Modes
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.
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 is enabled
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 level: 0
WMT L4 switch is 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 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
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.
show rule { action { action-type | all } [ protocol { http | https | rtsp }] | all | pattern-list { 1-512 pattern-type | all }}
Syntax Description
Action type (see Table 2-92 ). See the “Understanding Actions and Patterns” section for explanations of actions and patterns. |
|
Defaults
Command Modes
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.
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.
|
|
|
|---|---|
Regular expression substring match with the LDAP or NTLM group name of the user. |
|
Request header field pattern for the Referer request header. |
|
Request header field pattern for the User-agent request header. |
|
mime-type1 |
|
|
1.mime-type is an option for the freshness-factor, no-cache, and selective-cache actions only. |
Examples
The following example displays all rules with the configured action types and pattern lists:
The following example displays all rules configured with the use-proxy failover action type:
The following example displays statistics of all rules configured with the use-proxy failover action type:
Related Commands
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.
Syntax Description
Defaults
Command Modes
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:
Related Commands
show services
To display services-related information, use the show services EXEC command.
show services { ports [ port-num ] | summary }
Syntax Description
Defaults
Command Modes
Examples
The following example displays the services information by the port number:
The following example displays a services information summary, showing the service and the associated port numbers:
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
Defaults
Command Modes
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.
|
|
|
|---|---|
Traps sent by an ACNS device contain numeric module IDs. See Table 2-95 to map module names to module IDs. |
|
Traps sent by an ACNS device contain numeric category IDs. See Table 2-96 to map category names to category IDs. |
|
Description of the ACNS software alarm and the application that generated the alarm. |
|
|
|
|---|---|
|
|
|
|---|---|
Table 2-97 describes the fields shown in the show snmp stats display.
Table 2-98 describes the fields shown in the show snmp engineID display.
|
|
|
|---|---|
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-100 describes the fields shown in the show snmp group display.
|
|
|
|---|---|
Name of the SNMP group, or collection of users who have a common access policy. |
|
Table 2-101 describes the fields shown in the show snmp user display.
|
|
|
|---|---|
String identifying the name of the copy of SNMP on the device. |
|
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.
Syntax Description
Defaults
Command Modes
Examples
Table 2-102 describes the fields shown in the show ssh display.
|
|
|
|---|---|
Status of whether the SSH service is enabled or not enabled. |
|
SSH key has not been generated or previous key has been removed. |
|
Related Commands
show standby
To display standby interface information, use the show standby EXEC command.
Syntax Description
Defaults
Command Modes
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.
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.
Syntax Description
Defaults
Command Modes
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:
Related Commands
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
Defaults
Command Modes
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.
|
|
|
|---|---|
Related Commands
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
Defaults
Command Modes
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.
|
|
|
|---|---|
Related Commands
show statistics authentication
To display Content Engine authentication statistics, use the show statistics authentication EXEC command.
show statistics authentication
Syntax Description
Defaults
Command Modes
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.
|
|
|
|---|---|
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
(Optional) Display statistics about bandwidth allocation errors. |
Defaults
Command Modes
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.
Related Commands
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
(Optional) Displays authenticated traffic bypass statistics. |
|
Defaults
Command Modes
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.
|
|
|
|---|---|
Number of connections bypassed due to authentication issues. |
|
Number of connections bypassed to facilitate error transparency. |
|
Related Commands
show statistics cdnfs
To display Content Engine ACNS network file system (cdnfs) statistics, use the show statistics cdnfs EXEC command.
Syntax Description
Defaults
Command Modes
Examples
Table 2-109 describes the show statistics cdnfs command fields displayed in the command output.
Related Commands
show statistics cfs
To display Content Engine cache file system (cfs) statistics, use the show statistics cfs EXEC command.
Syntax Description
Defaults
Command Modes
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.
Related Commands
show statistics cifs-server
To display the CIFS server statistics, use the show statistics cifs-server EXEC command.
Syntax Description
Defaults
Command Modes
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.
|
|
|
|---|---|
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
Displays the status of a Content Engine or device group for the ACNS network. |
|
Defaults
Command Modes
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.
|
|
|
|---|---|
Status of the device or device group. Values are Online, Offline, or Pending. |
Feedback