-
Cisco Internet Streamer CDS 2.4 Command Reference
-
Index
-
Preface
-
Command-Line Interface Command Summary
-
Internet Streamer CDS Release 2.4 Software Commands - access-lists through line
-
Internet Streamer CDS Release 2.4 Software Commands - lls through show statistics cdnfs
-
Internet Streamer CDS Release 2.4 Software Commands - show statistics distribution through write
-
Acronyms
-
Standard Time Zones
-
Feedback
Table Of Contents
show statistics access-lists 300
show statistics authentication
lls
To view a long list of directory names, use the lls EXEC command.
lls [directory]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
This command provides detailed information about files and subdirectories stored in the present working directory (including size, date, time of creation, sysfs name, and long name of the file). This information can also be viewed with the dir command.
Examples
The following example shows how to view a long list of directory names:
ServiceEngine#llssize time of last change name-------------- ------------------------- -----------4096 Mon Jan 10 14:02:26 2005 <DIR> WebsenseEnterprise4096 Mon Jan 10 14:02:26 2005 <DIR> Websense_config_backup10203 Mon Feb 28 04:24:53 2005 WsInstallLog4096 Wed Feb 9 00:59:48 2005 <DIR> core_dir4096 Mon Jan 10 13:49:27 2005 <DIR> crash382 Tue Mar 1 03:32:13 2005 crka.log1604 Tue Feb 22 03:55:04 2005 dbupgrade.log4096 Mon Jan 10 14:02:31 2005 <DIR> downgrade4096 Mon Feb 28 04:17:32 2005 <DIR> errorlog53248 Tue Mar 1 03:01:53 2005 <DIR> logs16384 Mon Jan 10 13:49:26 2005 <DIR> lost+found438 Tue Jan 11 05:37:57 2005 new_file.xml8192 Tue Mar 1 00:00:00 2005 <DIR> preload_dir4096 Tue Mar 1 03:26:00 2005 <DIR> sa40960 Tue Mar 1 03:32:15 2005 <DIR> service_logs4096 Tue Feb 22 03:51:25 2005 <DIR> smartfilter384802 Mon Feb 28 03:46:00 2005 syslog.txt16296 Mon Feb 21 04:42:12 2005 test4096 Mon Jan 10 14:02:24 2005 <DIR> var4096 Sat Feb 12 07:15:23 2005 <DIR> wmt_vodRelated Commands
dir
lslogging
To configure system logging, use the logging global configuration command. To disable logging functions, use the no form of this command.
logging {console {enable | priority loglevel} | disk {enable | filename filename | priority loglevel | recycle size} | facility facility | host {hostname | ip-address} [port port_num | priority loglevel | rate-limit message_rate]}
no logging {console {enable | priority} | disk [enable | filename | priority | recycle] | facility | host {hostname | ip-address} [port port_num | priority loglevel | rate-limit message_rate]}
Syntax Description
Defaults
Logging: on
Priority of message for console: warning
Priority of message for log file: debug
Priority of message for a host: warning
Log file: /local1/syslog.txt
Log file recycle size: 10,000,000 bytes
Command Modes
Global configuration
Usage Guidelines
Use the logging command to set specific parameters of the system log file. System logging is always enabled internally on the SE. The system log file is located on the sysfs partition as /local1/syslog.txt. This file contains the output from many of the CDS components running on the SE, such as authentication entries, privilege levels, administrative details, and diagnostic output during the boot process.
To view information about events that have occurred in all devices in your CDS network, you can use the system message log feature. When a problem occurs in the CDS network, use the system message logs to diagnose and correct such problems.
The syslog.txt file on the CDSM contains information about events that have occurred on the CDSM and not on the registered nodes. The messages written to the syslog.txt file depend on specific parameters of the system log file that you have set 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 CDSM because the problem never occurred on the CDSM but occurred only on the registered node. However, such an error message will be displayed in the syslog.txt file on the registered node.
A disk failure syslog message is generated every time that a failed sector is accessed. Support for filtering multiple syslog messages for a single failed sector on an IDE disk was added. Support for filtering multiple syslog messages for a single failed section for SCSI disks and SATA disks exists.
To configure the SE to send varying levels of event messages to an external syslog host, use the logging host option. Logging can be configured to send various levels of messages to the console using the logging console priority option.
The no logging disk recycle size command sets the file size to the default value. Whenever the current log file size surpasses the recycle size, the log file is rotated. The log file cycles through at most five rotations, and they are saved as [log file name].[1-5] under the same directory as the original log. The rotated log file is the one configured using the logging disk filename command.
Configuring System Logging to Remote Syslog Hosts
Cisco Internet Streamer Release 2.4 software, supported logging to only a single remote syslog host, and the following two commands is used to configure a single remote syslog host for an SE:
ServiceEngine(config)#logging host hostnameServiceEngine(config)#logging priority priorityYou can configure an SE to send varying levels of messages to up to four remote syslog hosts. To accommodate this, logging host priority priority global configuration command (shown above) is deprecated, and the logging host hostname global configuration command is extended as follows:
ServiceEngine(config)#[no]logging host hostname [priority priority-code | port port |rate-limit limit]where the following is true:
•
hostname is the hostname or IP address of the remote syslog host. Specify up to four remote syslog hosts. To specify more than one syslog host, use multiple command lines; specify one host per command.
•
Note
•
•
Mapping syslog Priority Levels to RealProxy Error Codes
The RealProxy system generates error messages and writes them to the RealProxy log file. These error messages are captured by the caching application and passed to the system log file. A one-to-one mapping exists between the RealProxy error codes and the syslog priority levels.
Examples
The following example shows that the SE is configured to send messages that have a priority code of "error" (level 3) to the console:
ServiceEngine(config)#logging console priority warningsThe following example shows that the SE is configured to disable sending of messages that have a priority code of "error" (level 3) to the console:
ServiceEngine(config)#no logging console warningsThe following example shows that the SE is configured to send messages that have a priority code of "error" (level 3) to the remote syslog host that has an IP address of 172.31.2.160:
ServiceEngine(config)#logging host 172.31.2.160 priority errorRelated Commands
clear logging
debug
show loggingls
To view a list of files or subdirectory names within a directory, use the ls EXEC command.
ls [directory]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
To list the filenames and subdirectories within a particular directory, use the ls directory command; to list the filenames and subdirectories of the current working directory, use the ls command. To view the present working directory, use the pwd command.
Examples
The following example displays a list of files within the current working directory:
ServiceEngine#ls/local1The following example displays a list of files within the /local1 directory:
ServiceEngine#ls /local1core_dircrasherrorloglogslost+foundservice_logssmartfiltersyslog.txtRelated Commands
dir
lls
pwdmkdir
To create a directory, use the mkdir EXEC command.
mkdir directory
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
Use this command to create a new directory or subdirectory in the SE file system.
Examples
The following example shows how to create a new directory under local1:
ServiceEngine#mkdir /local1/mydirRelated Commands
dir
lls
ls
pwd
rmdirmkfile
To create a new file, use the mkfile EXEC command.
mkfile filename
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
Use this command to create a new file in any directory of the SE.
Examples
The following example shows how to create a new file:
ServiceEngine#mkfile traceinfoRelated Commands
lls
ls
mkdirmovie-streamer
To enable and configure the Movie Streamer server, use the movie-streamer global configuration command. To disable the Movie Streamer, use the no form of this command.
movie-streamer accelerate vod enable
movie-streamer advanced {client {idle-timeout num | rtp-timeout} | origin server idle-interval num}
movie-streamer broadcast port-list num port num
movie-streamer cache {age-multiplier num | enable | max-ttl {days num | hours num | minutes num | seconds num} | reval-each-request}
movie-streamer enable
movie-streamer max-concurrent-sessions num
movie-streamer proxy outgoing rtsp host ip address port num
movie-streamer transport-src-address ip address
no movie streamer {accelerate vod enable | advanced {client {idle-timeout num | rtp-timeout} | origin server idle-interval num} | broadcast port-list num port num | cache {age-multiplier num | enable | max-ttl {days num | hours num | minutes num | seconds num} | reval-each-request} | enable | max-concurrent-sessions num | proxy outgoing rtsp host ip address port num | transport-src-address ip address}
Syntax Description
Defaults
days: 1 day
hours: 72 hours
minutes: 4320 minutes
seconds: 259200 seconds
Command Modes
Global configuration
Usage Guidelines
The movie-streamer accelerate vod enable command enables kernel streaming acceleration for VOD.
The movie-streamer advanced client command sets the RTSP or RTP timeout value.
The movie-streamer advanced origin-server command sets the origin-server idle-interval value, which can determine the origin-server RTP timeout value.
The Idle Timeout field and the movie-streamer advanced client idle-timeout command (as well as the movie-streamer advanced client rtp-timeout command), are only intended for performance testing when using certain testing tools that do not have full support of the RTCP receiver report. Setting these timeouts to high values causes inefficient tear-down of client connections when the streaming sessions have ended.
For typical deployments, it is preferable to leave these parameters set to their defaults. The default is 60.
The movie-streamer advanced client idle-timeout command has a range from 0 to 300, whereas the Idle Timeout field has a range from 30-180. This is by design.
Examples
The following example shows how to set the original server interval:
ServiceEngine(config)#movie-streamer advanced origin-server idle-interval 5The following example shows how to set the broadcast port list:
ServiceEngine(config)#movie-streamer broadcast port-list 1 5000 5002The following example shows how to set the expiration time as a percentage of the age:
ServiceEngine(config)#movie-streamer cache age-multiplier 50The following example shows how to set the content cache maximum TTL:
ServiceEngine(config)#movie-streamer cache max-ttl days 100The following example shows how to set the maximum concurrent sessions:
ServiceEngine(config)#movie-streamer max-concurrent-sessions 7000The following example shows how to set the outgoing proxy:
ServiceEngine(config)#movie-streamer proxy outgoing rtsp host 10.74.61.98 554The following example shows how to set the source IP of the transport header while behind NAT:
ServiceEngine(config)#movie-streamer transport-src-address 10.74.61.99The following example shows how to set the client timeout:
ServiceEngine(config)#movie-streamer advanced client idle-timeout 150The following example shows how to set the RPT time out:
ServiceEngine(config)#movie-streamer advanced client rtp-timeout 150Set original server interval is 5 secondServiceEngine(config)#movie-streamer advanced origin-server idle-interval 5Set broadcast port listSPCDN-QA-35(config)#movie-streamer broadcast port-list 1 5000 5002Set Expiration time as a percentage of their age's 50%SPCDN-QA-35(config)#movie-streamer cache age-multiplier 50Set cache content max ttl is 100 daysSPCDN-QA-35(config)#movie-streamer cache max-ttl days 100Set max con-current sessions is 7000SPCDN-QA-35(config)#movie-streamer max-concurrent-sessions 7000Set out going proxySPCDN-QA-35(config)#movie-streamer proxy outgoing rtsp host 10.74.61.98 554Set the source Ip of transport header while behind NATSPCDN-QA-35(config)#movie-streamer transport-src-address 10.74.61.99Related Commands
show movie-streamer
show statistics movie-streamermtu
To set the interface maximum transmission unit (MTU) packet size, use the mtu interface configuration
command. Use the no form of this command to reset the MTU packet size.
mtu mtusize
no mtu mtusize
Syntax Description
Command Default
The default MTU packet size for an Ethernet interface is 1500 bytes.
Command Modes
Interface configuration
Usage Guidelines
The MTU is the largest size of IP datagram that can be transferred using a specific data link connection. Use the mtu command to set the maximum packet size in bytes.
Examples
The following example sets the MTU packet size as 1500 bytes:
ServiceEngine(config-if)#mtu 1500The following example resets the MTU packet size:
ServiceEngine(config-if)#no mtu 1500Related Commands
show interface
show running-config
show startup-configno (global configuration)
To undo a global configuration command or set its defaults, use the no form of a global configuration command.
no command
Note
Syntax Description
command
Specifies the command type; see the "" section for valid values.
Defaults
No default behavior or values.
Command Modes
Global configuration
Usage Guidelines
Valid values for command are as follows:
Use the no command to disable functions or negate a command. If you need to negate a specific command, such as the default gateway IP address, you must include the specific string in your command, such as no ip default-gateway ip-address.
no (interface configuration)
To negate a Gigabit Ethernet or port-channel interface configuration command or set its defaults, use the no interface configuration command.
no interface {GigabitEthernet slot/port | PortChannel {1 | 2} | Standby group num}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Related Commands
interface
show interface
show running-config
show startup-configntp
To configure the Network Time Protocol (NTP) server and to allow the system clock to be synchronized by a time server, use the ntp global configuration command. To disable this function, use the no form of this command.
ntp server {ip-address | hostname} [ip-addresses | hostnames]
no ntp server {ip-address | hostname} [ip-addresses | hostnames]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Usage Guidelines
Use this command to synchronize the SE, SR or CDSM clock with the specified NTP server. The ntp server command enables NTP servers for timekeeping purposes and is the only way to synchronize the system clock with a time server.
When you synchronize the CDSM clock with an NTP server, there is a possibility of all devices registered with the CDSM being shown as offline and then reverted to online status. This situation can occur when synchronization with the NTP server sets the CDSM clock forward in time by an interval greater than at least two polling intervals or when the software clock on the CDSM is changed by a similar value using the clock EXEC command. The CDSM determines the status of devices in the CDS network depending on when it was last contacted by the devices for a getUpdate request. If you set the CDSM clock ahead in time, you have added that amount of time to the period since the CDSM received the last getUpdate request. However, it is only a transient effect. Once the devices contact the CDSM for their next getUpdate request after the clock setting change, the CDSM GUI reports the status of all devices correctly.
Examples
The following example configures the IP address of the time server providing the clock synchronization:
ServiceEngine(config)#ntp 172.16.22.44The following example resets the time server providing the clock synchronization:
ServiceEngine(config)#no ntp 172.16.22.44Related Commands
clock
show clock
show ntp statusntpdate
To set the software clock (time and date) using a Network Time Protocol (NTP) server, use the ntpdate EXEC command.
ntpdate {hostname | ip-address}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
Use NTP to find the current time of day and set the SE current time to match. The ntpdate command synchronizes the software clock with the hardware clock.
Examples
The following example sets the software clock of the SE using an NTP server:
ServiceEngine#ntpdate 10.11.23.40Related Commands
clock set
show clockping
To send echo packets for diagnosing basic network connectivity on networks, use the ping EXEC command.
ping {hostname | ip-address}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
To use this command with the hostname argument, be sure that DNS functionality is configured on your SE. To force the timeout of a nonresponsive host or to eliminate a loop cycle, press Ctrl-C.
Following are sample results of the ping command:
•
•
•
•
Examples
The following example shows how to test the basic network connectivity with a host:
ServiceEngine#ping 172.19.131.189PING 172.19.131.189 (172.19.131.189) from 10.1.1.21 : 56(84) bytes ofdata.64 bytes from 172.19.131.189: icmp_seq=0 ttl=249 time=613 usec64 bytes from 172.19.131.189: icmp_seq=1 ttl=249 time=485 usec64 bytes from 172.19.131.189: icmp_seq=2 ttl=249 time=494 usec64 bytes from 172.19.131.189: icmp_seq=3 ttl=249 time=510 usec64 bytes from 172.19.131.189: icmp_seq=4 ttl=249 time=493 usec--- 172.19.131.189 ping statistics ---5 packets transmitted, 5 packets received, 0% packet lossround-trip min/avg/max/mdev = 0.485/0.519/0.613/0.047 msServiceEngine#ping6
To ping the IPv6 address, use the ping6 EXEC command.
ping6 line ip-address
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
The following example shows how to ping the IPv6 address:
ServiceEngine(config)#pingv5 fec0::100/64Related Commands
ping
port-channel
To configure the port-channel load-balancing options, use the port-channel global configuration command. To disable load-balancing options, use the no form of this command.
port-channel load-balance {dst-ip | dst-mac | round-robin}
no port-channel load-balance
Syntax Description
Defaults
Round-robin is the default load-balancing method.
Command Modes
Global configuration
Usage Guidelines
The port-channel load-balance command configures one of three load-balancing algorithms and provides flexibility in choosing interfaces when an Ethernet frame is sent. The round-robin option allows evenly balanced usage of identical network interfaces in a channel group. Because this command takes effect globally, if two channel groups are configured, they must use the same load-balancing option.
Because the Internet Streamer CDS software normally initiates IP packets or Ethernet frames, it does not support hashing based on the source IP address and source MAC address. Cisco Internet Streamer Release 2.4 software adds the round-robin option, which is the default load-balancing algorithm, to evenly distribute traffic among several identical network interfaces.
Examples
The following example shows how to configure the round-robin load-balancing method on an SE:
ServiceEngine(config)#port-channel load-balance round-robinRelated Commands
interface
primary-interface
To configure the primary interface for the CDS network, use the primary-interface global configuration command. Use the no form of the command to remove the configured primary interface.
primary-interface {GigabitEthernet 1-2/port | PortChannel 1-2 | Standby group_num}
no primary-interface {GigabitEthernet 1-2/port | PortChannel 1-2 | Standby group_num}
Syntax Description
Defaults
The default primary interface is the first operational interface on which a link beat is detected. Interfaces with lower-number IDs are polled first (for example, GigabitEthernet 0/0 is checked before 1/0). Primary interface configuration is required for the proper functioning of the Centralized Management System (CMS). After devices are registered to the CDSM, the CDSM uses the configured primary interface to communicated with the registered devices.
You cannot enable the CDS network without specifying the primary interface. Also, you must have chosen the primary interface before you enable the CMS. The primary interface can be changed without disabling the CDS network. The primary interface specifies the default route for an interface. To change the primary interface, choose a different interface as the primary interface.
In Cisco Internet Streamer Release 2.4 software and later releases, you can select a standby interface as the primary interface (you can enter the primary-interface Standby group_num command) to specify a standby group as the primary interface on an SE.
Command Modes
Global configuration
Usage Guidelines
The primary-interface global configuration command allows the administrator to specify the primary interface for the CDS network.
The primary interface can be changed without disabling the CDS network. To change the primary interface, re-enter the command string and specify a different interface.
Note
Examples
The following example shows how to specify the GigabitEthernet slot 1 port 0 as the primary interface on an SE:
ServiceEngine(config)#primary-interface GigabitEthernet 1/0The following example shows how to specify the GigabitEthernet slot 2 port 0 as the primary interface on an SE:
ServiceEngine(config)#primary-interface GigabitEthernet 2/0pwd
To view the present working directory, use the pwd EXEC command.
pwd
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
Use this command to display the present working directory of the SE.
Examples
The following example shows how to view the present working directory:
ServiceEngine#pwd/local1Related Commands
cd
dir
lls
lsqos
To globally enable QoS functionality on the switch, use the qos command. To globally disable QoS functionality, use the no form of this command.
qos {device-policy-service {config-file url | enable} | dsvc num name name fqdn icap ip address num list request-type {all num num name redirect-url {no-redirect list num | url list num}| http-download num num name{no-redirect list num | url list num} | wmt-streaming num num name redirect-url {no-redirect list num | url list num}}
no qos {device-policy-service {config-file url | enable} | dsvc num name name fqdn icap ip address num list request-type {all num num name redirect-url {no-redirect list num | url list num}| http-download num num name{no-redirect list num | url list num} | wmt-streaming num num name redirect-url {no-redirect list num | url list num}}
Syntax Description
Defaults
QoS functionality is disabled.
Command Modes
Global configuration
Usage Guidelines
If QoS functionality is globally enabled, it is enabled on all interfaces, except on the interfaces where QoS has been disabled. If QoS functionality is globally disabled, all traffic is passed in QoS pass-through mode.
Examples
This example shows how to enable QoS functionality globally on the switch:
ServiceEngine(config)#qos device-policy-service enableRelated CommandsPlease ensure you have purchased License for this advanced feature
Related CommandsSwitch(config)#
show qos
show statistics qosradius-server
To configure RADIUS authentication parameters, use the radius-server global configuration command. To disable RADIUS authentication parameters, use the no form of this command.
radius-server {enable | host {hostname | hostipaddr} [auth-port port] | key keyword | redirect {enable | message reply location url} | retransmit retries | timeout seconds}
no radius-server {enable | host {hostname | hostipaddr} | key | redirect {enable | message reply location url} | retransmit | timeout}
Syntax Description
Defaults
auth-port port: UDP port 1645
retransmit retries: 2
timeout seconds: 5
Command Modes
Global configuration
Usage Guidelines
RADIUS is a client/server authentication and authorization access protocol used by an CDS network device to authenticate users attempting to connect to a network device. The CDS network device functions as a client, passing user information to one or more RADIUS servers. The CDS network device permits or denies network access to a user based on the response that it receives from one or more RADIUS servers. RADIUS uses the User Datagram Protocol (UDP) for transport between the RADIUS client and server.
You can configure a RADIUS key on the client and server. If you configure a key on the client, it must be the same as the one configured on the RADIUS servers. The RADIUS clients and servers use the key to encrypt all RADIUS packets transmitted. If you do not configure a RADIUS key, packets are not encrypted. The key itself is never transmitted over the network.
Note
RADIUS authentication usually occurs in these instances:
•
•
RADIUS authentication is disabled by default. You can enable RADIUS authentication and other authentication methods at the same time. You can also specify which method to use first.
To configure RADIUS parameters, use the radius-server command in global configuration mode. To disable RADIUS authentication parameters, use the no form of this command.
The redirect option of the radius-server command redirects an authentication response to a different authentication server if an authentication request using the RADIUS server fails.
Note
To exclude domains from RADIUS authentication, use the rule no-auth domain command. RADIUS authentication takes place only if the site requested does not match the specified pattern.
Enabling and Disabling Administrative Login Authentication and Authorization Through RADIUS
When configuring an SE to use RADIUS to authenticate and authorize administrative login requests, follow these guidelines:
•
•
•
•
Tip
To use the SE CLI to enable RADIUS authentication and authorization on an SE, enable RADIUS authentication for normal login mode by entering the authentication login radius global configuration command as follows:
ServiceEngine(config)#authentication login radius enable[primary][secondary]Use the authentication configuration radius global configuration command to enable RADIUS authorization as follows:
ServiceEngine(config)#authentication configuration radius enable [primary][secondary]
Note
Configuring RADIUS Authentication of HTTP Requests
To configure RADIUS authentication for HTTP requests on an SE, configure the RADIUS server settings on the SE and enable RADIUS authentication for HTTP requests on the SE using the radius-server global configuration command.
Examples
The following example enables the RADIUS client, specifies a RADIUS server, specifies the RADIUS key, accepts retransmit defaults, and excludes the domain name, mydomain.net, from RADIUS authentication. You can verify the configuration with the show radius-server and show rule all commands.
ServiceEngine(config)#radius-server enableServiceEngine(config)#radius-server host 172.16.90.121ServiceEngine(config)#radius-server key myradiuskeyServiceEngine(config)#rule action no-auth pattern-list 2ServiceEngine(config)#rule pattern-list 2 domain mydomain.netServiceEngine#show radius-serverLogin Authentication for Console/Telnet/Ftp/SSH Session: enabledConfiguration Authentication for Console/Telnet/Ftp/SSH Session: enabled (secondary)Radius Configuration:---------------------Radius Authentication is onTimeout = 5Retransmit = 2Key = ****Radius Redirect is offThere is no URL to authentication failure instructionsServers-------IP 172.16.90.121 Port = 1645ServiceEngine#show rule allRules Template Configuration----------------------------Rule Processing Enabledrule no-auth domain mydomain.netThe following example disables RADIUS authentication on the SE:
ServiceEngine(config)#no radius-server enableThe following example shows how to force the SE to try RADIUS authentication first:
ServiceEngine(config)#authentication login radius enable primaryRelated Commands
debug authentication user
rule
show radiusrcp
To enable the Remote Copy Program (RCP), use the rcp global configuration command. To disable RCP, use the no form of this command.
rcp enable
no rcp enable
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Examples
The following example shows how to enable RCP:
ServiceEngine(config)#rcp enableRelated Commands
show rcp
rea
To initiate the remote execution agent, use the rea EXEC command.
rea {start | stop}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
The following example shows the remote execution agent services being started.
ServiceEngine(config)#rea startRelated Commands
show rea
reload
To halt and perform a cold restart on the SE, use the reload EXEC command.
reload [force]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
To reboot the SE, use the reload command. If the current running configuration is different from the startup configuration and if the configuration changes are not saved to flash memory, you are prompted to save the current running configuration parameters to the startup configuration.
To save any file system contents to disk from memory before a restart, use the cache synchronize command.
Examples
The following example reloads the SE after you have saved the configuration changes.
ServiceEngine#reloadSystem configuration has been modified. Save?[yes]:yesProceed with reload?[confirm]yesShutting down all services, will timeout in 15 minutes.reload in progress .....The following example forces a reboot on the SE:
ServiceEngine#reload forceRelated Commands
cache synchronize
write
write eraserename
To rename a file on the SE, use the rename EXEC command.
rename oldfilename newfilename
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
Use this command to rename any sysfs file without making a copy of the file.
Examples
The following example renames a file named errlog.txt as old_errlog.txt:
ServiceEngine#rename errlog.txt old_errlog.txtRelated Commands
cpfile
restore
To restore the device to its manufactured default status, removing the user data from the disk and flash memory, use the restore EXEC command. This command erases all existing content on the device.
restore factory-default [preserve basic-config]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
Use this command to restore data on disk and in flash memory to the factory default, while preserving particular time-stamp evaluation data. You need to enter this command from the root directory, or else the following error message is displayed:
ServiceEngine#restore factory-defaultNeed to cd to / before issuing this commandCommand aborted.SERVICEENGINE#Be sure to back up the CDSM database and copy the backup file to a safe location that is separate from that of the CDSM, or change over from the primary to a standby CDSM before you use the restore factory-default command on your primary CDSM. The primary CDSM operation must be halted before proceeding with backup and restore commands.
Caution
By removing the CDSM database, all configuration records for the entire CDS network are deleted. If you do not have a valid backup file or a standby CDSM, you must use the cms deregister force command and reregister every SE and SR after you have reconfigured the CDSM, because all previously configured data is lost.
If you used your standby CDSM to store the database while you reconfigured the primary, you can simply register the former primary as a new standby CDSM.
If you created a backup file while you configured the primary CDSM, you can copy the backup file to this newly reconfigured CDSM and use the cms database restore command.
Caution
Cisco Internet Streamer CDS software consists of three basic components:
•
•
•
All of these components must be correctly installed for Cisco Internet Streamer CDS software to work properly.
Examples
The following two examples show the results of using the restore factory-default and restore factory-default preserve basic-config commands. Because configuration parameters and data are lost, prompts are given before initiating the restore operation to ensure that you want to proceed.
Note
CDSM# restore factory-defaultThis command will wipe out all of data on the disksand wipe out CDS CLI configurations you have ever made.If the box is in evaluation period of certain product,the evaluation process will not be affected though.It is highly recommended that you stop all active servicesbefore this command is run.Are you sure you want to go ahead?[yes/no]CDSM# restore factory-default preserve basic-configThis command will wipe out all of data on the disksand all of CDS CLI configurations except basic networkconfigurations for keeping the device online.The to-be-preserved configurations are network interfaces,default gateway, domain name, name server and hostname.If the box is in evaluation period of certain product,the evaluation process will not be affected.It is highly recommended that you stop all active servicesbefore this command is run.Are you sure you want to go ahead?[yes/no]
Note
The following example shows that entering the show disk command after the restore command verifies that the restore command has removed data from the partitioned file systems (sysfs and cdnfs):
ServiceEngine#show diskSYSFS 0.0GB 0.0%CDNFS 0.0GB 0.0%FREE 29.9GB 100.0%Because flash memory configurations were removed after the restore command was used, the show startup-config command does not return any flash memory data. The show running-config command returns the default running configurations.
The show wmt commands continue to display the same license evaluation periods as before the restore factory-default command was invoked, because the evaluation period is not affected by this restore command. For example, if there were 21 days remaining in the evaluation period before the restore factory-default command was used, there would continue to be 21 days remaining in the evaluation period.
Related Commands
cms database backup
cms database restore
show disks
show rtsp server real-subscriber
show running-config
show startup-config
show wmtrmdir
To delete a directory, use the rmdir EXEC command.
rmdir directory
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
Use this command to remove any directory from the SE file system. The rmdir command removes only empty directories.
Examples
The following example removes the oldfiles directory under /local1:
ServiceEngine#rmdir /local1/oldfilesRelated Commands
lls
ls
mkdirrtsp
To configure the Real-Time Streaming Protocol (RTSP)-related parameters, use the rtsp global configuration command. To disable individual options, use the no form of this command.
rtsp {advanced ip address {bypass-gateway movie-streamer | max-initial-setup-delay time_delay | max-request-rate num}| ip-address ip address}
no rtsp {advanced ip address {bypass-gateway movie-streamer | max-initial-setup-delay time_delay | max-request-rate num}| ip-address ip address}
Syntax Description
Defaults
max-initial-setup-delay time_delay: 10 seconds
max-request-rate num: 40 requests
Command Modes
Global configuration
Usage Guidelines
RTSP is a standard Internet streaming control protocol (RFC 2326). It is an application-level protocol that controls the delivery of data with real-time properties, such as video and audio. Apple QuickTime, Real Networks, and the Cisco Streaming Engine use RTSP as the streaming control protocol.
Live Streaming with the Cisco Streaming Engine
The Internet Streamer CDS software supports live streaming content with many kinds of network topologies and deployment scenarios. This feature allows the integration of streaming content from Cisco IP/TV Servers and QuickTime live broadcast servers with the CDS network. Support for broadcast of playlists is included (except for SEs at the network edge), allowing you to convert one or more disk files into a playlist and to send them out through simulated live streaming.
An RTSP source is a fully qualified RTSP URL that references an external streaming server, such as a parent SE, which provides the corresponding RTSP request point.
RTSP Gateway
The RTSP gateway is a process that runs on the SE. The RTSP gateway accepts an RTSP request and performs the initial RTSP handshake with RTSP-based clients (for example, Windows Media 9 players) on behalf of the back-end RTSP servers (for example, the WMT RTSP server) that are running on the SE.
For every RTSP request, the RTSP gateway examines the following properties of the request:
•
•
•
•
After the successful completion of uniformity checks, the RTSP gateway tunnels the request to the appropriate back-end RTSP server that is running on the SE. The RTSP gateway can tunnel the request to RealProxy, RealSubscriber, or the Cisco Streaming Engine on the SE, depending on the requested media type, the back-end RTSP servers that are currently enabled on the SE, and the media player that is requesting the content.
After the RTSP gateway tunnels the request to a particular back-end RTSP server that is running on the SE and the back-end server and the client negotiate the UDP ports, the RTSP gateway continues with RTSP message passing (SETUP). When the RTSP client issues a PLAY request, the streaming server starts streaming the data to the client over UDP.
Based on the properties of the incoming request, including user agent, final destination, and media file type, the RTSP gateway performs the following tasks with SEs:
•
•
•
If the SE is registered with a CDSM, the RTSP gateway also redirects the incoming requests to other content distributors (for example, RealSubscriber or Cisco Streaming Engine) that are configured on the SE.
Network Address Translation (NAT) is designed for IP address simplification and conservation because it enables private IP internetworks that use nonregistered IP addresses to connect to the Internet. NAT operates on a router, usually connecting two networks together, and translates the private addresses in the internal network into legal addresses before packets are forwarded onto another network. As part of this functionality, NAT can be configured to advertise only one external address for the entire network. This configuration provides additional security, effectively hiding the entire internal network from the world behind that address. NAT has the dual functionality of security and address conservation and is typically implemented in remote access environments.
Note
Default RTSP Gateway Settings
The RTSP gateway is automatically enabled on the SE and cannot be disabled with a command. Table 2-12 lists the default settings for the RTSP gateway.
By default, the RTSP gateway is always enabled on an SE and cannot be disabled by entering a CLI command. As Table 2-12 shows, the RTSP gateway has a set of default settings. You only need to change these default settings under the following conditions:
•
•
Note
Examples
The following example shows how to set up the Movie Streamer RTSP bypass gateway:
ServiceEngine(config)#rtsp advanced bypass-gateway movie-streamerThe following example shows how to establish the maximum initial setup delay:
ServiceEngine(config)#rtsp advanced max-initial-setup-delay 15The following example shows how to establish the maximum request rate:
ServiceEngine(config)#rtsp advanced max-request-rate 50The following example shows how to assign the RTSP IP address:
ServiceEngine(config)#rtsp ip-address 10.74.61.1Related Commands
show rtsp
rule
To set the rules by which the SE filters HTTP, HTTPS, and RTSP traffic, use the rule global configuration command. To disable individual options, use the no form of this command.
The general rule command is as follows:
rule {action action-type pattern-list list_num [protocol {all | protocol-type}] | enable | pattern-list list_num pattern-type}
The specific rule commands are as follows:
rule action allow pattern-list list_num [protocol {all | http | rtmp | rtsp}]
rule action block pattern-list list_num [protocol {all | http | rtmp | rtsp}]
rule action generate-url-signature {include-client-src-ip | key-id-owner 1-32 {key-id-number 1-16} {pattern-list 1-512} [protocol {all | http}]}
rule action no-cache pattern-list list_num [protocol {all | http | rtmp | rtsp}]
rule action redirect url pattern-list list_num [protocol {all | http | rtmp | rtsp}]
rule action refresh pattern-list list_num [protocol {all | http }]
rule action replace pattern-list list_num [protocol {all | http | rtmp | rtsp}]
rule action rewrite pattern-list list_num [protocol {all | http | rtmp | rtsp}]
rule action use-icap-service service-name pattern-list list_num [protocol {all | http}]
rule action validate-url-signature {error-redirect-url url | exclude {all error-redirect-url url pattern-list num [protocol {all | http | rtmp | rtsp}] | client-ip error-redirect-url url pattern-list num [protocol {all | http | rtmp | rtsp}] | expiry-time error-redirect-url url pattern-list num [protocol {all | http | rtmp | rtsp}]}}
rule enable
rule pattern-list list-num domain dn_regexp
rule pattern-list list-num group-type {and | or}
rule pattern-list list-num header-field {referer ref_regexp | request-line req_regexp | user-agent ua_regexp}
rule pattern-list list-num src-ip s_ipaddress s_subnet
rule pattern-list list-num url-regex url_regexp
rule pattern-list list-num url-regsub url_regexp url_sub
no rule action {allow pattern-list list_num [protocol {all | http | https | rtsp}] | block pattern-list list_num [protocol {all | http | https | rtsp}] | generate-url-signature {include-client-src-ip | key-id-owner 1-32 {key-id-number 1-16} {pattern-list 1-512} [protocol {all | http}]} | no-cache pattern-list list_num [protocol {all | http | https}] | redirect url pattern-list list_num [protocol {all | http | https | rtsp}] | refresh pattern-list list_num [protocol {all | http | https}] | replace pattern-list list_num [protocol {all | http | https | rtsp}] | rewrite pattern-list list_num [protocol {all | http | https | rtsp}] | use-icap-service service-name pattern-list list_num [protocol {all | http | https}] | validate-url-signature pattern-list error-redirect-url url | exclude {all error-redirect-url url pattern-list num [protocol {all | http | rtmp | rtsp}] | client-ip error-redirect-url url pattern-list num [protocol {all | http | rtmp | rtsp}] | expiry-time error-redirect-url url pattern-list num [protocol {all | http | rtmp | rtsp}]}
no rule enable
no rule pattern-list list-num {domain dn_regexp | group-type {and | or} | header-field {referer ref_regexp | src-ip s_ipaddress s_subnet | url-regex url_regexp | url-regsub url_regexp url_sub}}
Syntax Description
Defaults
The default is rule processing disabled.
The group-type pattern is OR by default.
Command Modes
Global configuration
Usage Guidelines
The Rules Template allows you to specify a set of rules, each clearly identified by an action and a pattern. The Rules Template allows you to configure an SE to use specific rules to filter HTTP, HTTPS, and RTSP traffic. A common use of this feature is to configure an SE to block the spread of Internet worms and viruses within an organization by checking whether a requested web page matches the pattern of a known Internet worm and if so then automatically blocking the request.
If you have enabled rules processing on an SE (enabled the Rules Template feature on the SE and configured rules for the SE), the SE checks each incoming client request to determine if a rule pattern matches the requested content. If a rule pattern matches the given request, the SE uses the specified action (policy) to handle this incoming traffic.
The SE can match incoming requests against the following:
•
•
•
•
•
•
•
–
–
–
You can apply the policies defined in the Rules Template to HTTP (including FTP over HTTP) and HTTPS and to RTSP for streaming media objects. Policies that can be applied include the following:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
Supported Rule Actions per Protocol
For RTSP, the redirect and the redirect_url_for_cdn rule actions are supported for RTSP requests from RealMedia players. These two rule actions are not supported for RTSP requests from Windows Media Players. For example, Windows Media Services 9 (WMS 9) supports theblock, rewrite, and allow rule actions for RTSP requests, but does not support the redirect and redirect_url_for cdn rule actions for RTSP requests.
Supported Action and Pattern Combinations
Not all actions support all patterns for request matching because some patterns do not make sense for some actions.
Understanding Actions and Patterns
A rule is specified by an action and a pattern list. An action is performed on a request if this request matches the pattern list specified in the rule pattern-list command.
An action is something that the SE performs when processing a request; for instance, an action could be blocking the request, using an alternative proxy, and so forth.
A pattern list defines the limits of a request; for instance, a pattern list may specify that the source IP address falls in the subnet range 172.16.*.*.
Rules can be dynamically added, displayed, or deleted from the SE. The rules are preserved across reboots because they are written into persistent storage, such as NVRAM, using the appropriate CLI commands, the SE GUI, or the CDSM GUI. Only the system resources limit the number of rules that the SE can support. Because rules consume resources, the more rules that you define can greatly impact how the SE performs.
Note
Actions
The Rules Template supports the following types of actions:
•
This rule action can be used in combination with block actions to allow selective types of requests. Allow does not carry any meaning as a standalone action.
•
•
•
•
•
•
•
•
Actions can be applied to specific protocols or to a set of protocols. If no protocol is configured, then the specified action will be taken for all the traffic that goes through the SE.
Patterns
The Rules Template supports the following pattern types:
•
Note
•
•
•
•
Request header field patterns referer, request-line, and user-agent are supported for the actions block, redirect, and rewrite. The referer pattern is matched against the Referer header in the request, the request-line pattern is matched against the first line of the request, and the user-agent pattern is matched against the User-Agent header in the request.
•
If an empty string is given as a replacement pattern, the Referer header is stripped. Stripping of the Referer header occurs in the user-agent pattern.
Multiple patterns can be entered on the same pattern list. If any of them matches the incoming request, the corresponding action is taken.
Multiple patterns for the same pattern list must be entered on different lines.
Rules Template Processing Considerations
Actions and patterns have a predefined order of execution. A group of rules with the same action is always executed either before or after another group of rules with a different action. The block, rewrite, and redirect rule actions support the following additional patterns: request-line, referer, and user-agent regular expressions. The request-line regular expression matches the first line of the request. The user-agent regular expression matches the User-Agent header value of the request. The referer regular expression matches the Referer header value of the request. The order is not affected by the order in which the rules are entered using CLI commands.
Allow and block carry the same precedence. The order of execution depends on the order of configuration between allow and block actions. Other actions always take precedence over allow.
Among rules of the same action, a predefined execution order exists among the rule patterns, which means that within a group of rules of the same action, one group of rules with the same pattern is always executed either before or after another group of rules with a different pattern.
Among all rules of the same action and of the same rules pattern, the rules are evaluated in a Last-Entered-First-Examined fashion (the reverse of the order in which the rules were entered). This order is not affected by the order in which the rules are entered using CLI commands.
Most actions do not have any parameters.
Service Rules for URLs
There are three cases for service rules:
1.
2.
3.
For example, if all URL requests that match HTML are blocked, implicitly, all requests that match other URL requests are allowed.
If all URL requests that match WMV are allowed, implicitly, all request that match other URL requests are blocked.
If both of the above rules are configured, then HTML URL requests are blocked, and all other URL requests are allowed.
Examples
The following example shows that the SE is configured to replace the internal.domain.com string in a request to the server named dummy:
ServiceEngine(config)#rule action rewrite header-field referer internal.domain.com dummyThe following example shows that if an empty string is given as a replacement pattern, then the referer header is stripped. This rule states that all requests, which have a referer header that indicates a corporate internal server in ABCBigCorp, strip the referer field so that the outside web server does not see the name of the corporate internal server.
ServiceEngine(config)#rule action rewrite header-field referer internal.abcbigcorp.com ""The following example shows that the rule pattern-list command is configured to add a pattern to an existing pattern list to perform an action to be defined on destination IP address 172.16.25.25 using the dst-ip pattern:
ServiceEngine#show rule pattern-list 10 allRules Template Configuration----------------------------Rule Processing EnabledPattern-Lists :rule pattern-list 11 dst-ip 172.16.25.25 255.255.255.0rule pattern-list 11 domain foo.comThe following example shows that the rule action block command is configured and associated with an existing pattern list:
ServiceEngine(config)#rule action block pattern-list 10 protocol allServiceEngine#show rule action blockRules Template Configuration----------------------------Rule Processing EnabledActions :rule action block pattern-list 10 protocol all
The following example shows that the rule action block command is configured and associated with an existing pattern list, which lists as its pattern the domain yahoo.com:
ServiceEngine(config)#rule pattern-list 10 domain yahoo.comServiceEngine#show rule pattern-list 10 allRules Template Configuration----------------------------Rule Processing EnabledPattern-Lists :rule pattern-list 10 domain yahoo.comServiceEngine(config)#rule action block pattern-list 10 protocol allIn this example, the request (using HTTP) to yahoo.com was denied three times.
The following example shows that the rule action block command (action) blocks all patterns specified with the rule pattern-list 12 command:
ServiceEngine(config)#rule pattern-list 12 domain \.foo.comServiceEngine(config)#rule action block pattern-list 12ServiceEngine(config)#The following example prevents caching of requests that match a URL request that contains the *cgi-bin* string:
ServiceEngine(config)#rule pattern-list 13 url-regex \.*cgi-bin.*ServiceEngine(config)#rule action no-cache pattern-list 13ServiceEngine(config)#The actions that are to be taken by the rules are configured through the rule action commands. Patterns that are to be matched to a particular pattern that you specify are configured through rule pattern-list commands.
The following example shows how patterns use AND by configuring patterns with the same pattern list number and applying that pattern list to an action:
ServiceEngine(config)#rule action block pattern-list 1ServiceEngine(config)#rule pattern-list 1 url-regex yahooServiceEngine(config)#rule pattern-list 1 dst-port 80Other options of the rule command work similarly to the preceding examples.
The following example redirects a request for old-domain-name that has been changed to new-domain-name:
Cache(config)#rule action redirect http://old-domain-name/ pattern-list 1 protocol httpCache(config)#rule pattern-list 1 url-regsub http://old-domain-name/ http://new-domain-name/The following example redirects requests from an IETF site to a site that is locally mirrored:
Cache(config)#rule action redirect http://www.ietf.org/rfc/(.*) pattern-list 2 protocol httpThe following example shows that if the request URL is http://www.ietf.org/rfc/rfc1111.txt, the SE rewrites the URL as http://wwwin-eng.cisco.com/RFC/RFC/rfc1111.txt and sends a 302 Temporary Redirect response with the rewritten URL in the Location header to the client. The browser automatically initiates a request to the rewritten URL.
Cache(config)#rule pattern-list 2 url-regsub http://www.ietf.org/rfc/(.*) http://wwwin-eng.cisco.com/RFC/RFC/\1The following example redirects all requests for linux.org to a local server in India that is closer to where the SE is located:
Cache(config)#rule action redirect http://linux.org/(.*) pattern-list 3 protocol httpThe following example shows that two URLs are to be matched if the pattern is url-regsub. If the URLs that are given in the action configuration are invalid, a warning is displayed during the configuration of this rule. The action URL is taken when the header field patterns are configured.
Cache(config)#rule pattern-list 3 url-regsub http://linux.org/(.*) http://linux.org.in/\1The following example bypasses requests with cisco.com as the domain from URL filtering:
ServiceEngine(config)#rule action no-url-filtering pattern-list 6 protocol allServiceEngine(config)#rule pattern-list 6 domain cisco.comRelated Commands
clear
show rulescript
To execute a script provided by Cisco or check the script for errors, use the script EXEC command.
script {check | execute} file_name
Syntax Description
check
Checks the validity of the script.
execute
Executes the script. The script file must be a sysfs file in the current directory.
file_name
Name of the script file.
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
The script EXEC command opens the script utility, which allows you to execute Cisco-supplied scripts or check errors in those scripts. The script utility can read standard terminal input from the user if the script you run requires inputs from the user.
Note
Examples
The following example checks for errors in the script file foo.script:
ServiceEngine#script check foo.scriptScript file foo.script is valid.service-router
To configure service routing, use the service-router global configuration command. To disable last-resort routing, use the no form of this command.
On the SE:
service-router {keepalive-interval num | service-monitor {number-of-samples {all num | cpu num | disk num | fms num | kmemory num | memory num | wmt num | nic num} | sample-period {all num | cpu num | disk num | fms num | kmemory num | memory num | movie-streamer num | nic num | wmt num} | threshold {all num | cpu num | disk num | failcntdisk num | fms num | kmemory num | memory num | nic num | wmt num} | type {all | cpu | disk | failcntdisk | fms | kmemory | memory | nic | wmt}}}
no service-router
On the SR:
service-router {access-policy enable | content-based-routing {enable | redundant} | dns-ttl num | lastresort {domain name {allow all | alternate name} | error-domain name error-file} | location-based-routing { enable | geo-location-server {primary ip address num | secondary ip address num}} | proximity-based-routing {enable | proximity-cache timeout num | proximity-server ip address num} | redirect-mode { ip-redirect} | service-monitor {number-of-samples {all num | cpu num | disk num | kmemory num | memory num}} | sample-period {cpu num | disk num | failcntdisk num| kmemory num | memory num} | threshold {all num | cpu num | disk num | kmemory num | memory num} | type {all | cpu | disk | kmemory | memory}}
no service-router
Syntax Description
Defaults
keepalive-interval: 2 seconds
redundant copies: 1 copy
dns-ttl: 60 seconds
proximity cache timeout: 1800 seconds
sample-period: 1 second
nic sample-period: 3 seconds
number of samples: 2 samples
Command Modes
Global configuration
Usage Guidelines
To configure last-resort routing, use the service-router global configuration command, where domain is the service routing domain name, and alternate is where to route requests.
Last-resort routing is applicable when load-based routing is enabled and all SEs have exceeded their thresholds or all SEs in the domain are offline. The SR can redirect requests to a configurable alternate domain when all SEs serving a client network region are overloaded.
Note
Crossdomain Support
When a client requests the content from a portal and the content then makes a request to a different remote domain (or origin server), the request cannot be served unless the origin server or the remote domain has a crossdomain.xml that grants access to the original portal to continue with the streaming.
For example, a client request for abc.com/streaming.html (which has the content), makes a request for cds-origin.com/vod/sample.flv (which is a different domain), then the client must request a crossdomain.xml. The crossdomain.xml allows access to abc.com and can then stream sample.flv. If the cds-origin.com does not have crossdomain.xml, then the request is denied.
Note
Instead of directly going to cds-origin.com, the request first comes to the service router. So when the request for crossdomain.xml comes to the service router, it is served to the client. This xml grants access to the portal for the file requested. So the client then sends the request for the file which is served.
Note
FLVPlaybackComponent does not currently crossdomain requests for video files. The crossdomain request is issued only when a query string is present. In such cases, the video gets downloaded but does not play.
The number of the HTTP Requests (normal) in Request Received ("show statistics service-router summary") should increase.
Examples
The following example shows how to configure the keepalive interval:
ServiceRouter(config)#service-router keepalive-interval 2The following example shows how to configure the service monitor type:
ServiceRouter(config)#service-router service-monitor type allCrossdomain Support
The following example shows how to enable crossdomain support:
ServiceEngine(config)#service-router access-policy enableThe following example shows how to disable crossdomain support:
ServiceEngine(config)#no service-router access-policy enableRelated Commands
show service-router
setup
To configure basic configuration settings (general settings, device network settings, and disk configuration) on the SE and a set of commonly used caching services, use the setup EXEC command. You can also use the setup EXEC command to complete basic configuration after upgrading.
setup
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
The following example shows the part of the output when you enter the setup EXEC command on an SE running the Internet Streamer CDS software:
ServiceEngine#setupHere is the current profile of this deviceCDN device : YesDo you want to change this (y/n) [n]:Press the ESC key at any time to quit this sessionshow access-lists
To display the access control list (ACL) configuration, use the show access-lists 300 EXEC command.
show access-lists 300
Syntax Description
None
Command Default
No default behavior or values.
Command Modes
EXEC
Examples
Table 2-13 describes the fields shown in the show access-lists 300 display.
Related Commands
access-lists
show acquirer
To display the acquirer information and progress of content acquisition for a specified channel number or name, use the show acquirer EXEC command.
show acquirer [delivery-service {delivery-service-id delivery-service-id | delivery-service-name delivery-service-name} | progress {delivery-service-id delivery-service-id | delivery-service-name delivery-service-name} | proxy authentication]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
The show acquirer progress command displays information for all channels for which the SE is the root SE. It displays the number of acquired objects in relation to the total number of objects for both a single item or crawler jobs. When an acquisition is in progress, it displays the number of data bytes currently being downloaded in relation to the total size of the object and its URL. The show acquirer progress command also displays information about the authentication that allows the acquirer to access content through a transparent or nontransparent proxy server.
The show acquirer proxy authentication command displays the proxy authentication configuration for the acquirer if you have enabled content acquisition through a proxy server and proxy authentication is configured. Use the acquirer proxy authentication outgoing global configuration command to configure authentication when you enable content acquisition through a proxy server. You must first configure the proxy host and the port using the http proxy outgoing host global configuration command.
When you enable content acquisition through a proxy server, you can provide the proxy configuration and proxy authentication information in the manifest file. If the proxy and proxy authentication are configured in the manifest file, the show acquirer proxy authentication command does not display any proxy details.
Examples
The show acquirer progress EXEC command displays the progress of the acquirer for a specified channel. If a specific channel is not mentioned, the display shows the progress for all the channels for which the SE is the root.
Table 2-14 describes the fields shown in the show acquirer progress display.
The following example shows the output from the show acquirer proxy authentication command when there are no proxies configured using the acquirer proxy authentication global configuration command:
ServiceEngine#show acquirer proxy authenticationNo proxy authentication information configuredThe following example shows the output from the show acquirer proxy authentication command after configuring the proxy using the acquirer proxy authentication global configuration command:
ServiceEngine#show acquirer proxy authenticationacquirer proxy authentication outgoing 172.28.225.29 8080 admin password **** My-Domain basic-auth-disableacquirer proxy authentication transparent admin password **** My-Domain basic-auth-disableRelated Commands
acquirer (global configuration)
http
show statistics acquirershow alarms
To display information on various types of alarms, their status, and history, use the show alarms EXEC command.
show alarms [critical [detail [support]] | detail [support] | history [[start_num [end_num [detail [support]] | detail [support]]] | critical [start_num [end_num [detail [support]] | detail [support]]] | detail [support] | major [start_num [end_num [detail [support]] | detail [support]]] | minor [start_num [end_num [detail [support]]] | detail [support]]] | major [detail [support]] | minor [detail [support]] | status]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
The Node Health Manager enables CDS applications to raise alarms to draw attention to error or significant conditions. The Node Health Manager, which is the data repository for such alarms, aggregates the health and alarm information for the applications, services (for example, the cache service), and resources (for example, disk drives) that are being monitored on the SE. For example, the Node Health Manager gives you a mechanism to determine if a monitored application (for example, the HTTP proxy caching service) is alive on the SE. These alarms are referred to as Internet Streamer CDS software alarms.
The Internet Streamer CDS software uses SNMP to report error conditions by generating SNMP traps. In the Internet Streamer CDS software, the following SE applications can generate an Internet Streamer CDS software alarm:
•
•
•
The three levels of alarms in the Internet Streamer CDS software are as follows:
•
•
•
You can configure alarms using the snmp-server enable traps alarm global configuration command.
Use the show alarms critical EXEC command to display the current critical alarms being generated by the Internet Streamer CDS software applications. Use the show alarms critical detail EXEC command to display additional details for each of the critical alarms being generated. Use the show alarms critical detail support EXEC command to display an explanation about the condition that triggered the alarm and how you can find out the cause of the problem. Similarly, you can use the show alarms major and show alarms minor EXEC commands to display the details of major and minor alarms.
Use the show alarms history EXEC command to display a history of alarms that have been raised and cleared by the Internet Streamer CDS software on the SE. The Internet Streamer CDS software retains the last 100 alarm raise and clear events only.
Use the show alarm status EXEC command to display the status of current alarms and the SE's alarm overload status and alarm overload configuration.
Examples
Table 2-15 describes the fields shown in the show alarms history display.
Table 2-16 describes the fields shown in the show alarms status display.
Related Commands
alarm overload-detect
snmp-server enable trapsshow arp
To display the Address Resolution Protocol (ARP) table, use the show arp EXEC command.
show arp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
The show arp command displays the Internet-to-Ethernet address translation tables of the Address Resolution Protocol. Without flags, the current ARP entry for the hostname is displayed.
Table 2-17 describes the fields shown in the show arp display.
show authentication
To display the authentication configuration, use the show authentication EXEC command.
show authentication user
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Related Commands
authentication
authentication
clear
show statistics authenticationshow authsvr
To display the status of the Authorization server, use the show authsvr EXEC command.
show authsvr [unknown-server]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
The following example shows the status of the Authorization server:
ServiceEngine#show authsvrAuthserver is EnabledRelated Commands
authsvr
show bandwidth
To display the bandwidth allocated to a particular device, use the show bandwidth EXEC command.
show bandwidth [flash-media-streaming | movie-streamer | wmt]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
Table 2-18 describes the fields shown in the show bandwidth display.
Related Commands
bandwidth (global configuration)
show banner
To display information on various types of banners, use the show banner EXEC command.
show banner
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
Table 2-19 describes the fields shown in the show banner display.
Related Commands
banner
show bitrate
To display the bit rate allocated to a particular device, use the show bitrate EXEC command.
show bitrate [movie-streamer | wmt]
Syntax Description
movie-streamer
(Optional) Displays the Movie Streamer bit rate settings.
wmt
(Optional) Displays Windows Media Technology (WMT) bit rate settings.
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
Table 2-20 describes the fields shown in the show bitrate display.
Related Commands
bitrate
show cache
To display a list of cached contents, use the show cache EXEC command.
show cache [content num]
Syntax Description
content
Displays a list of cached contents in order of decreasing priority.
num
Specifies number of cached contents to be displayed (1-1000).
Defaults
Number of cached contents is 100.
Command Modes
EXEC
Usage Guidelines
The show cache command allows users to check the cached content in an SE. Users can also view the priority, size, and URL information through this command.
Examples
The following example shows the cached contents:
ServiceEngine#show cache content 1000Max-cached-entries is set as 1000Number of cal cached assets: 12------------------------------------------------Priority Size URL------------------------------------------------1.09887e+00 16 rtsp://72.163.255.118/c.wmv1.04340e+00 416 rtsp://72.163.255.118/c.wmv.Ui4HeLMPgB5lLH_+bo2d.03.bmp6.71782e-01 957 rtsp://72.163.255.118/c.wmv.hdr5.74964e-01 16 rtsp://72.163.255.118/4.wmv5.60340e-01 664997 rtsp://72.163.255.118/c.wmv.Ui4HeLMPgB5lLH_+bo2d.033.15230e-01 665107 http://72.163.255.118/c.wmv2.39938e-01 5409 rtsp://72.163.255.118/4.wmv.hdr2.02040e-01 35256 rtsp://72.163.255.118/4.wmv.rPgfTr1Lo0dT6FJWaxDs.03.bmp1.59027e-01 873664 http://72.163.255.118/4.flv1.45368e-01 3603032 http://72.163.255.118/b.wmv1.23161e-01 70517409 rtsp://72.163.255.118/4.wmv.rPgfTr1Lo0dT6FJWaxDs.037.88076e-02 29180088 http://72.163.255.118/4.wmvRelated Commands
cache
show capability
To display the capabilities of the Cap-X profile ID, use the show capability EXEC command.
show capability profile ID profile ID
Syntax Description
profile ID
Displays information for the Cap-X profile.
profile ID
Profile ID number. The range is 1-65535.
Defaults
No default behavior or values.
Command Modes
EXEC
Related Commands
capability
show cdnfs
To display CDS network file system (cdnfs) information, use the show cdnfs EXEC command.
show {cdnfs volumes | usage}
Syntax Description
volumes
Displays CDS network file system volumes.
usage
Displays Content Delivery Network (CDN) current usage.
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
Table 2-21 describes the fields shown in the show cdnfs volumes display.
Table 2-21 show cdnfs volumes Field Descriptions
cdnfs 00-04
CDS network file system and disk number.
nnnnnnKB
Size of the volume in kilobytes.
Related Commands
cdnfs
disk (EXEC)
show disks
show statistics cdnfsshow clock
To display the system clock, use the show clock EXEC command.
show clock [detail | standard-timezones {all | details timezone | regions | zones region-name}]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
The CDS has several predefined standard time zones. Some of these time zones have built-in summertime information while others do not. For example, if you are in an eastern region of the United States (US), you must use the US/Eastern time zone that includes summertime information and will adjust the clock automatically every April and October. There are about 1500 standard time zone names.
The clock summertime command is disabled when a standard time zone is configured. You can only configure summertime if the time zone is not a standard time zone (if the time zone is a customized zone).
In addition, CLI commands exist to enable you to display a list of all the standard time zones. The show clock standard-timezones all EXEC command enables you to browse through all standard time zones and choose from these predefined time zones. You can choose a customized name that does not conflict with the predefined names of the standard time zones. Most predefined names of the standard time zones have two components, a region name and a zone name. You can list time zones by several criteria, such as regions and zones.
Examples
Table 2-22 describes the field in the show clock display.
Table 2-22 show clock Field Description
Local time
Day of the week, month, date, time (hh:mm:ss), and year in local time relative to the UTC offset.
Table 2-23 describes the fields shown in the show clock detail display.
The following example shows an excerpt of the output from the show clock standard-timezones all EXEC command. As the following example shows, all of the standard time zones (approximately 1500 time zones) are listed. Each time zone is listed on a separate line.
ServiceEngine #show clock standard-timezones allAfrica/AbidjanAfrica/AccraAfrica/Addis_AbabaAfrica/AlgiersAfrica/AsmeraAfrica/BamakoAfrica/BanguiAfrica/BanjulAfrica/BissauAfrica/BlantyreAfrica/BrazzavilleAfrica/BujumburaAfrica/CasablancaAfrica/CeutaAfrica/ConakryAfrica/DakarAfrica/Dar_es_SalaamAfrica/Djibouti..
ServiceEngine(config)#The following example shows an excerpt of the output from the show clock standard-timezones region EXEC command. As the example shows, all first level time zone names or directories are listed. All 1500 time zones are organized into directories by region.
ServiceEngine #show clock standard-timezones regionsAfrica/America/Antarctica/Arctic/Asia/Atlantic/Australia/Brazil/CET...The following example shows an excerpt of the output from the show clock standard-timezones zones EXEC command. As the following example shows, this command lists the name of every time zone that is within the specified region (for example, the US region).
ServiceEngine #show clock standard-timezones zones USAlaskaAleutianArizonaCentralEast-IndianaEasternHawaiiIndiana-StarkeMichiganMountainPacificSamoaThe following example shows an excerpt of the output from the show clock standard-timezones details EXEC command. This command shows details about the specified time zone (for example, the US/Eastern time zone). The command output also includes the standard offset from the Greenwich mean time (GMT).
ServiceEngine #show clock standard-timezones details US/EasternUS/Eastern is standard timezone.Getting offset information (may take a while) ...Standard offset from GMT is -300 minutes (-5 hour(s)).It has built-in summertime.Summer offset from GMT is -240 minutes. (-4 hour(s)).Related Commands
clock (EXEC)
clock (global configuration
show cms
To display the Centralized Management System (CMS) embedded database content and maintenance status and other information, use the show cms EXEC command.
show cms {database {content {dump filename | text | xml} | maintenance [detail]} | info | processes}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
Table 2-24 describes the fields shown in the CDSM show cms info display.
Table 2-25 describes the fields shown in the SE show cms info display.
The following example writes the database content to a file in text format:
CDSM# show cms database content textDatabase content can be found in /local1/cms-db-12-12-2002-17:06:08:070.txt.The following example writes the database content to a file in XML format:
CDSM# show cms database content xmlDatabase content can be found in /local1/cms-db-12-12-2002-17:07:11:629.xml.The following example shows the output of the show cms database maintenance detail on an SE:
ServiceEngine#show cms database maintenance detailDatabase maintenance is not running.Regular database maintenance is enabled.Regular database maintenance schedule is set on Sun, Mon, Tue, Wed, Thu, Fri, Sat at 02:00Full database maintenance is enabled.Full database maintenance schedule is set on Sun, Mon, Tue, Wed, Thu, Fri, Sat at 04:00Disk usage for STATE partition: Total: 1523564K, Available: 1443940K, Use: 6%DATABASE VACUUMING DETAILS AND ERRORS-------------------------------------Database Vacuuming never performed or it did not complete due to error.Latest Vacuuming status :No ErrorLast Vacuum Error : No ErrorLast Reindex Time : Thu Jul 15 02:02:49 2004Latest Reindexing status :No ErrorLast Reindex Error: No ErrorServiceEngine#Related Commands
cms (EXC)
cms (global configuration)show content
To display all content entries in the CDS, use the show content EXEC command.
show content {all [background | brief] | url url [brief]}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
This command allows users to check the cached or pre-positioned content in an SE. Through this command, users can view content attributes such as status and file size.
Examples
The following example displays the RTSP URL in the CDS:
ServiceEngine#show content url rtsp://www.cht.com/CHT_2M.wmvCAL content object attributes:URL: rtsp://www.cht.com/CHT_2M.wmvStatus is 2 (Servable)File size is 16 BytesPlayable by WMTAuthorization is Not RequiredContent is CACHED with priority 0.574964The following example displays all content entries in the CDS:
ServiceEngine#show content all name backgroundCommand running in background...ServiceEngine#USER INFO: Your 'show content all' command finishedshow debugging
To display the state of each debugging option, use the show debugging EXEC command.
show debugging
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
This command displays only the type of debugging enabled, not the specific subset of the command.
Examples
In the following example, the debug icp client command coupled with the show debugging command shows that Internet Cache Protocol (ICP) debugging is enabled:
ServiceEngine#debug icp clientServiceEngine#show debuggingDebug icp (client) is onRelated Commands
debug
undebugshow device-mode
To display the configured or current mode of a device, use the show device-mode EXEC command.
show device-mode {configured | current}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
If the configured and current device modes differ, a reload is required for the configured device mode to take effect.
Examples
The configured device mode field in the show device-mode configured display shows the device mode that has been configured, but has not yet taken effect. The current device mode field in the the show device-mode current display shows the current mode in which the CDS device is operating.
The following example shows how to use the show device-mode command to show the device mode when you change the device from an SE to an SR using the device mode command:
Acmehost# show device-mode currentCurrent device mode: service-engineAcmehost# show device-mode configuredConfigured device mode: service-engineAcmehost(config)#device mode service-routerThe new configuration will take effect after a reloadAcmehost(config)#exitAcmehost# show device-mode currentCurrent device mode: service-engineNote: The configured and current device modes differ,a reload is required for the configured device mode totake effect.Acmehost# show device-mode configuredConfigured device mode: service-routerNote: The configured and current device modes differ,a reload is required for the configured device mode totake effect.Acmehost# write memoryAcmehost# reload force...reload...Acmehost# show running-configdevice mode service-router!hostname Acmehost..Acmehost# show device-mode configuredConfigured device mode: service-routerAcmehost# show device-mode currentCurrent device mode: service-routerRelated Commands
device
show direct-server-return
To display the Direct Server return information, use the show direct-server-return EXEC command.
show direct-server-return
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
The following example displays the Direct Server return information:
ServiceEngine#show direct-server-returndirect-server-return vip 11.11.11.11Related Commands
direct-server-return
show disks
To view information about your disks, use the show disks EXEC command.
show disks [current | details | raid-state | SMART-info [details]]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
The show disks command displays the names of the disks currently attached to the SE.
Proactively Monitoring Disk Health with SMART
The ability to proactively monitor the health of disks with Self Monitoring, Analysis, and Reporting Technology (SMART) was added. SMART provides you with hard drive diagnostic information and information about impending disk failures.
SMART is supported by most disk vendors and is a standard method used to determine the health of a disk. SMART has several read-only attributes (for example, the power-on hours attribute, the load and unload count attribute) that provide the CDS software with information regarding the operating and environmental conditions that may indicate an impending disk failure.
To display more detailed information, enter the show disks SMART-info details EXEC command. The output from the show disks SMART-info and the show disks SMART-info details commands will differ based on the disk vendor and the type of drive technology (Integrated Drive Electronics [IDE], Small Computer Systems Interface [SCSI], and Serial Advanced Technology Attachment [SATA] disk drives).
Even though SMART attributes are vendor dependent, there is a common way of interpreting most SMART attributes. Each SMART attribute has a normalized current value and a threshold value. When the current value exceeds the threshold value, the disk is considered as failed. The CDS software monitors the SMART attributes and reports any impending failure through syslog messages, SNMP traps, and alarms.
The output from the show tech-support EXEC command also includes SMART information.
Filter Out Multiple Syslog Messages for a Single Failed Sector on SCSI, IDE, and SATA Disk Drives
Many disk failure messages were generated when a single disk sector failed, which caused an unnecessary alarm. Changes for suppressing multiple syslog messages on a single sector failure have been implemented for IDE disk drives. This fix has also been extended to SCSI and SATA disk drives.
Examples
Table 2-26 describes the fields shown in the show disks details display.
SMART support is vendor dependent; each disk vendor has a different set of supported SMART attributes. The following example shows the output from the show disks SMART-info EXEC command that was entered on two different SEs (Service Engine A and Service Engine B). These two SEs contain hard disks that were manufactured by different vendors.
ServiceEngine#show disks SMART-info=== disk00 ===smartctl version 5.38 [i686-spcdn-linux-gnu] Copyright (C) 2002-8 Bruce AllenHome page is http://smartmontools.sourceforge.net/=== START OF INFORMATION SECTION ===Device Model: ST3500320NSSerial Number: 5QM19RKRFirmware Version: SN04User Capacity: 500,107,862,016 bytesDevice is: Not in smartctl database [for details use: -P showall]ATA Version is: 6ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2Local Time is: Thu May 21 14:09:19 2009 UTCSMART support is: Available - device has SMART capability.SMART support is: Enabled=== START OF READ SMART DATA SECTION ===SMART overall-health self-assessment test result: PASSEDRUNNING: /usr/sbin/smartctl /dev/sda -H -i=== disk01 ===smartctl version 5.38 [i686-spcdn-linux-gnu] Copyright (C) 2002-8 Bruce AllenHome page is http://smartmontools.sourceforge.net/=== START OF INFORMATION SECTION ===Device Model: ST3500320NSSerial Number: 5QM19B0BFirmware Version: SN04User Capacity: 500,107,862,016 bytesDevice is: Not in smartctl database [for details use: -P showall]ATA Version is: 6ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2Local Time is: Thu May 21 14:09:19 2009 UTCSMART support is: Available - device has SMART capability.SMART support is: Enabled=== START OF READ SMART DATA SECTION ===SMART overall-health self-assessment test result: PASSEDRUNNING: /usr/sbin/smartctl /dev/sdb -H -i=== disk02 ===smartctl version 5.38 [i686-spcdn-linux-gnu] Copyright (C) 2002-8 Bruce AllenHome page is http://smartmontools.sourceforge.net/=== START OF INFORMATION SECTION ===Device Model: ST3500320NSSerial Number: 5QM19SK9Firmware Version: SN04User Capacity: 500,107,862,016 bytesDevice is: Not in smartctl database [for details use: -P showall]ATA Version is: 6ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2Local Time is: Thu May 21 14:09:19 2009 UTCSMART support is: Available - device has SMART capability.SMART support is: Enabled=== START OF READ SMART DATA SECTION ===SMART overall-health self-assessment test result: PASSEDRUNNING: /usr/sbin/smartctl /dev/sdc -H -iTable 2-27 describes some typical fields in the show disks SMART-info display.
Related Commands
disk (EXEC)
show distribution
To display the distribution information for a specified delivery service and to probe a remote SE for the liveness of its associated delivery service, use the show distribution EXEC command.
show distribution [delivery-services {delivery-service-id delivery-service-num | delivery-service-name delivery-service-name}]
show distribution [forwarder-list {delivery-service-id delivery-service-num | delivery-service-name delivery-service-name} | detail]
show distribution [location {forwarder-load-weight | live-load-weight | location-leader-preference} {delivery-service-id delivery-service-num | delivery-service-name delivery-service-name}]
show distribution [object-status object-url]
show distribution [processes]
show distribution [remote ip-address {metadata-sender delivery-service-id delivery-service-num [start-generation-id gen-id end-generation-id gen-id] | unicast-sender delivery-service-id delivery-service-num {cdn-url cdn_url | probe | relative-cdn-url cdn_url}}]
show distribution [remote traceroute {forwarder-next-hop delivery-service-id delivery-service-num {max-hop maxhop_num | trace-till-good | trace-till-root} | unicast-sender delivery-service-id delivery-service-num {cdn-url cdn-url | probe | relative-cdn-url cdn-url} {max-hop maxhop_num | trace-till-good | trace-till-root}}]
Syntax Description
delivery-services
(Optional) Displays information about the specified delivery service.
delivery-service-id
(Optional) Specifies the delivery service ID.
delivery-service-num
Delivery service number (64-bit number).
delivery-service-name
(Optional) Specifies the delivery service name.
delivery-service-name
Delivery service name.
forwarder-list
(Optional) Displays the forwarder lists for all delivery services subscribed to by the SE.
detail
(Optional) Displays detailed forwarder lists for all delivery services subscribed to by the SE.
location
(Optional) Displays delivery service routing-related parameters for the SEs in the location (specified by the delivery service ID).
forwarder-load-
weightDisplays the forwarder load weight value of the SEs in the location (specified by the delivery service ID). For more information, see the "Forwarder Probability" section.
live-load-weight
Displays the live load weight value of the SEs in the location (specified by the delivery service ID). For more information, see the "Live Splitting Probability" section.
location-leader-
preferenceDisplays the location leader preference value of the SEs in the location (specified by the delivery service ID). For more information, see the "Location Leader Preference" section.
object-status
(Optional) Displays information on the status of a pre-positioned object.
object-url
URL of the pre-positioned object.
processes
(Optional) Displays information on distribution processes.
remote
(Optional) Displays delivery service information about a remote SE.
ip-address
IP address of the remote SE.
metadata-sender
Displays the metadata from a remote SE.
start-generation-id
(Optional) Specifies the beginning database value of the current version of the multicast cloud.
gen_id
Beginning database value.
end-generation-id
Specifies the ending database value of the current version of the multicast cloud.
gen_id
Ending database value.
unicast-sender
Displays the unicast data from a remote SE.
cdn-url
Checks the object on a remote SE using the specified URL.
cdn_url
CDS network URL used to check the object on a remote SE.
probe
Probes the remote unicast sender.
relative-cdn-url
Checks the object on a remote SE using the specified URL.
traceroute
Displays the traceroute for the delivery service routing status.
forwarder-next-hop
Displays the next forwarder in the path for the SE.
Note
delivery-service-id
Specifies the delivery service ID with which the unicast sender is associated.
delivery-service-num
Delivery service number of the delivery service with which the unicast sender is associated.
max-hop
Displays the maximum number of hops needed to reach the unicast sender.
maxhop_num
Maximum number of hops (1-1024).
trace-till-good
Allows the device to trace the route of an object until the object is found.
trace-till-root
Allows the device to trace the route of an object until the device reaches the root SE.
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
Use the show distribution remote ip-address metadata-sender delivery-service-id delivery-service-num [start-generation-id gen_id end-generation-id gen_id] command option to retrieve the metadata from a remote SE assigned to a specified delivery service ID. The start and end generation IDs specify the beginning and ending database values representing the current version of the multicast cloud stored in the local database.
Note
The show distribution remote ip-address unicast-sender delivery-service-id delivery-service-num relative-cdn-url cdn-url command shows the status of the relative CDS network URL of an object at a remote SE assigned to a specified delivery service ID. A relative CDS network URL is one that lacks the prefix of the protocol and hostname. For example, the relative CDS network URL for http://www.mycompany.com/abc.def.html is abc.def.html.
Use the show distribution remote ip-address unicast-sender delivery-service-id delivery-service-num probe command to probe a remote SE for the liveness of the delivery service to which it is assigned.
The show distribution object-status object-url command can be used to display the properties of a pre-positioned object.
You can view the location leader preference and forwarder weight for the SE using the show distribution command. However, you can configure the location leader preference and forwarder weight only using the CDSM GUI for each SE. Default values are assumed if you do not manually configure them.
The show distribution location forwarder-load-weight command displays the probability of SEs assigned to the delivery service within the location being selected as a forwarder. The show distribution location location-leader-preference command displays the location leader preference value of SEs that are assigned to the delivery service within the location.
Use the show distribution delivery-services command to view the forwarder for the SEs. If a receiver SE is unable to find its forwarder SE, one of the following reasons is displayed in the Status/Reason column of the output of the show distribution delivery-services command:
•
•
•
Forwarder Probability
When an SE (location leader) selects its forwarder from an upstream location, it uses the forwarderLoad-weight value configured for each SE in its upstream location. The weight value of each SE corresponds to the probability of the SE being selected as the forwarder.
Each SE generates a unique random number. When an SE needs to select an inter-location forwarder, it views all the SEs in one remote location as a collection, with the size corresponding to their weight. It uses the generated random number to select an SE as a forwarder. SEs with a higher weight are more likely to be selected as forwarders.
Note
The load on the forwarder is the replication load per delivery service on the SE because all SEs subscribed to the delivery service will select a forwarder to balance the load. However, as the number of SEs assigned to different delivery services might differ, a forwarder might receive requests for content from SEs in other delivery services, which increases the load. Therefore, it is possible that the total load (of replicating content) on the forwarder does not reflect the weight but depends on the number of SEs assigned to a delivery service.
For each SE, you can specify the probability of each SE acting as a forwarder to SEs from downstream locations using the CDSM GUI. You can also specify whether certain SEs should never serve as a forwarder to downstream SEs. The specification is delivery service independent.
If you choose not to configure settings using the Location Leader and Forwarder Settings for SE window, the delivery service routing algorithm uses the random number method to generate one permutation of the SE ID ordered list.
Location Leader Preference
For intra-location (list of SEs in an SE's own location) forwarder selection, the delivery service routing algorithm first creates an ordered list of the SEs based on their location leader-preference in a descending order. Next, the delivery service routing algorithm will select the first SE in the ordered list as the location leader.
When multiple SEs have the same location leader-preference, the delivery service routing algorithm guarantees that all the SEs assigned to each delivery service in the location still generate the same ordered list, which avoids routing loops. A routing loop is a deadlock situation in which the forwarder selection among multiple SEs within the loop prevents the SEs from receiving the content from upstream locations. For example, SE1 uses SE2 as the forwarder and SE2 uses SE1 as the forwarder for the same delivery service.
However, for two different delivery services, the ordered list could be different (when multiple SEs have the same location leader probability value) even if the subscribed SEs are the same. When multiple SEs have the highest location leader-preference, although each SE has an equal chance of acting as the location leader (for different delivery services), only one SE always acts as the location leader for one particular delivery service. If you configure all the SEs in your network to have the same location leader-preference value, then each SE has an equal chance of acting as a location leader. When each SE has an equal probability of being selected as the location leader for any particular delivery service, only one particular SE is always selected as the location leader.
Note
In a location, you can specify the probability for each SE acting as the location leader. The specification is delivery service independent.
The following limitations are associated with specifying a location leader preference:
•
•
•
Live Splitting Probability
Similar to the delivery service routing application used for content replication that assigns weight and priority to SEs to tune location leader and forwarder selections, you can specify a configuration parameter liveSplit-load-weight for each SE. This parameter represents the relative probability that an SE is likely to receive live stream splitting traffic as compared to other SEs. The specification is delivery service independent. If you do not configure liveSplit-load-weight, the algorithm should work as it currently does.
A weighted load balancing scheme splits the live stream load on the SEs according to the liveSplit-load-weight value because SEs of different types have an equal probability of being selected as the splitting SE on the location path.
The liveSplit-load-weight is used when the delivery service routing generates the ordered list of SEs for each location. The SEs are ordered in a way that the higher the weight, the greater probability that the SEs are being ordered at the beginning of the list.
The weight represents a relative value. The liveSplit-load-weight assigned to one SE is compared against the weights of other SEs in the same location.
The weight is a probabilistic value. For one particular URL, all SEs generate the same ordered list for a location.
It is possible that an SE with a lower weight is being ordered at the beginning while an SE with a higher weight is being ordered at the end of the list. The weighted load balancing is useful only when there are multiple live stream URLs.
The liveSplit-load-weight parameter applies both within the home location and upstream locations. This setting is different from the distribution settings where locationLeader-priority controls how you choose SEs from the home location, while forwarderLoad-weight controls how you choose SEs from upstream locations.
Examples
The following examples show various ways of using the show distribution remote commands.
The following example shows the status of the object at a remote SE with the IP address 172.16.2.160 and delivery service ID 631. The URL of the content object specified in the command must not be the complete source URL. Instead, it must be the relative CDS network URL of the object.
ServiceEngine#show distribution remote 172.16.2.160 unicast-sender delivery-service-id 631 relative-cdn-url 101files/100.txtForwarder-Name : AD-SE08Forwarder-ID : 140Forwarder IP : 2.43.10.70Forwarder Location : default-locationRelative CDN URL : 101files/100.txtActual Size : 58Size Transferred : 58Resource-ID : roVe2aMzp+YhmbhGUfMPpQContent-ID : 7LC5xOlMp4YvkBJlHaQucQLast Modified Time : 10:52:38 Jan 04 2005The following example retrieves the metadata from a remote SE with the IP address 172.16.2.160 assigned to delivery service ID 4999:
ServiceEngine#show distribution remote 172.16.2.160 metadata-sender delivery-service-id 4999Getting meta data for delivery service(4999) from genid -1 to 2Connecting to 2.43.10.101Remote SE replied with the following headers:Action : Processing metadata recordsLatest Gen id is : 2Have more records to process : NoIs metadata still in full reload: Noadd-size: 2, del-size: 0Add Logs: 1 to 2add #1: UBsSUMwbTdJzzpqDvxSdYg.., basic_auth/public.htmladd #2: NJyVL9CZwpnyCfw+Is26yw.., index.txtThe following example probes the remote SE with the IP address 172.16.2.160 for the liveness of its assigned delivery service ID 153:
ServiceEngine#show distribution remote 172.16.2.160 unicast-sender delivery-service-id 153 probeProbe SuccessfulThe following example shows the beginning database value of the current version of the multicast cloud at a remote SE with the IP address 10.43.10.101 and delivery service ID 4999:
ServiceEngine# show distribution remote 10.43.10.101 metadata-sender delivery-service-id 4999 start-generation-id 0 end-generation-id 5Getting meta data for delivery service(4999) from genid -1 to 5Connecting to 10.43.10.101Remote SE replied with the following headers:Action : Processing metadata recordsLatest Gen id is : 2Have more records to process : NoIs metadata still in full reload: Noadd-size: 2, del-size: 0Add Logs: 1 to 2add #1: UBsSUMwbTdJzzpqDvxSdYg.., basic_auth/public.htmladd #2: NJyVL9CZwpnyCfw+Is26yw.., index.txt
Note
The following example shows the list of forwarders in the path toward the root SE:
ServiceEngine#show distribution remote traceroute forwarder-next-hop delivery-service-id 4999 trace-till-rootHop NextHop_SEId NextHop_SEName NextHop_SEIp GenID Status/Reason--- ------------ -------------- ------------ ----- -------------1 5884 AD-SE07 192.168.1.69 1 REGULAR2 6035 AD-SE13 2.43.10.101 1 LOC-LEAD3 5683 AD-SE12 2.43.10.100 1 LOC-LEAD4 6026 gnadaraj-507 2.43.27.2 1 LOC-LEAD5 5638 devi-507 2.43.27.36 1 LOC-LEAD (Reached RootSE)The following example shows output from the show distribution object-status command:
ServiceEngine#show distribution object-status http://www.cisco.com/index.txt========== Website Information ==========Name : cisco-crawlOrigin Server FQDN : www.cisco.comRequest Routed FQDN : N/AContent UNS Reference # : 1========== delivery services Information ==========*** delivery service 4999 (name = headercheck) ***Object Replication------------------Replication : DoneFile State : Ready for distributionMulticast for delivery service : Not EnabledReplication Lock : Received by Unicast-Receiver/AcquirerReference Count : 1Total Size : 2208640Transfered Size : 2208640MD5 of MD5 : zwhJagyCmRAE4UmTwc0EtA..Source Url : http://liqq-linux.cisco.com/index.txtSource Last Modified Time : Sun Jul 11 03:23:33 2004Object Properties-----------------Redirect To Origin : YesRequires Authentation : NoAlternative URL :Serve Start Time : N/AServe End Time : N/APlay servers : HTTP HTTPSContent Metadata : NoneContent uns_id : yhzR3VZ96MDz5FVHwmGD+A..Content gen-id : 5638:1108022220:1========== CDNFS Information ==========Internal File Name : /disk00-04/d/http-liqq-linux.cisco.com-azk2lrqzsytweswexham5w/32/326cf0278da48aac82d796cb1 19b1caa.0.data.txtActual File Size : 2208640 bytesMD5 of MD5 (Re-calculated): zwhJagyCmRAE4UmTwc0EtA..Content metadata : NoneMetadata match with : delivery service 4999Number of Source-urls : 1Source-url to CDN-object mapping:Source-url : http://liqq-linux.cisco.com/index.txtUsed by CDN object : ---- Yes ----Internal File Name : /disk00-04/d/http-liqq-linux.cisco.com-azk2lrqzsytweswexham5w/32/326cf0278da48aac82d796cb1 19b1caa.0.data.txtActual File Size : 2208640 bytes========== CDNFS lookup output ==========CDNFS File Attributes:Status 3 (Ready)File Size 2208640 BytesStart Time nullEnd Time nullAllowed Playback via HTTP HTTPSLast-modified Time Sun Jul 11 03:23:33 2004cdn_uns_id yhzR3VZ96MDz5FVHwmGD+A..last-modified Sun, 11 Jul 2004 03:23:33 GMTInternal path to data file: /disk00-04/d/http-liqq-linux.cisco.com-azk2lrqzsytweswexham5w/32/326cf0278da48aac82d796cb1 19b1caa.0.data.txtThe show distribution delivery-services output and the show distribution forwarder-list output display additional delivery service routing information. The newly added Status/Reason field displays whether the SE is a location leader and the reason for not having a forwarder SE.
The following example shows the delivery service distribution information:
ServiceEngine#show distribution delivery-servicesDelivery Service Name ID Priority Root Forwarder Status/Reason------------ -- -------- ---- --------- ------------- ----------00-AD 527 500 No Rack89-SE-11 REGULAR N/A01-AD 586 500 Yes N/A N/A N/A00-Live 588 500 Yes N/A LIVE N/ALOC-LEAD: This SE is the location leader for this delivery serviceREGULAR: This SE is not the location leader for this delivery serviceLLMT: This SE cannot find forwarder because this SE has limit onthe forwarder lookup levelFAIL: This SE cannot find forwarder because there is failed SE alongthe path within specified forwarder lookup levelNGWT: This SE cannot find forwarder because there is SE with negativeforwarder-load-weight along the path within the specifiedforwarder lookup levelLIVE: The specified delivery service is live delivery service, forwarder not applicable*: MetaData forwarder and Unicast forwarder are differentThe following example provides delivery service distribution information for delivery service ID 527:
ServiceEngine#show distribution delivery-services delivery-service-id 527Delivery service Configuration---------------------Delivery service ID : 527Delivery service Name : 00-ADWebsite Name : Test1Website Origin FQDN : www.test.comDelivery service Priority : 500Configured Distribution Type : Multicast onlyRoot SE Information-------------------ID of Configured Root SE : 462Name of Configured Root SE : Rack89-SE-11IP of Configured Root SE : 2.43.27.38ID of Effective Root SE : 462Current root-ce-uid : 1110247321This SE's Role : Not a Root SEThis SE in Full Reload : NoRoot SE Failover/Fallback Information---------------------------------------Root SE Failover/Fallback Interval : 120 MinsMetadata Information--------------------Metadata-Forwarder ID : 462Metadata-Forwarder Name : Rack89-SE-11Metadata-Forwarder Primary IP : 2.43.27.38Metadata-Forwarder NAT IP/Port : N/AAddress to Poll Metadata-Forwarder : Primary IPMetadata-Forwarder Status : REGULARLast gen-id Switch : NeverCurrent low-water-marker : 1Current max-gen-id : 0Current max-del-gen-id : 0Last poll : 13 Secs agoNext poll : 107 Secs from nowIdle poll interval : 120 SecsPoll interval multiplier : 1Unicast Information-------------------Ucast-Forwarder ID : 462Ucast-Forwarder Name : Rack89-SE-11Ucast-Forwarder Primary IP : 2.43.27.38Ucast-Forwarder NAT IP/Port : N/AAddress to Poll Ucast-Forwarder : Primary IPUcast-Forwarder Status : REGULARMulticast Information---------------------QoS Configuration-----------------MetaData QoS (system config) : 16 (Effective)Progress Information--------------------Number of jobs completed : 0Has incomplete jobs : NoLOC-LEAD: This SE is the location leader for this delivery serviceREGULAR: This SE is not the location leader for this delivery serviceLLMT: This SE cannot find forwarder because this SE has limit onthe forwarder lookup levelFAIL: This SE cannot find forwarder because there is failed SE alongthe path within specified forwarder lookup levelNGWT: This SE cannot find forwarder because there is SE with negativeforwarder-load-weight along the path within the specifiedforwarder lookup levelLIVE: The specified delivery service is live delivery service, forwarder not applicable*: MetaData forwarder and Unicast forwarder are different
Note
Related Commands
show statistics distribution
show flash
To display the flash memory version and usage information, use the show flash EXEC command.
show flash
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
If a new software image has been installed and is waiting to be run after a reboot, the show flash command displays this information and the version of Internet Streamer CDS software that will run on the device after reload.
Examples
The following example displays the flash information:
ServiceEngine#show flashCDS software version (disk-based code): CDS-2.4.0-b328System image on flash:Version: 2.4.0.328System flash directory:System image: 274 sectorsBootloader, rescue image, and other reserved areas: 59 sectors512 sectors total, 179 sectors free.Table 2-28 describes the fields shown in the show flash display.
show flash-media-streaming
To display the Flash Media Streaming information, use the show flash-media-streaming EXEC command.
On the SE:
show flash-media-streaming [license | logging name | mtrack | stream-status {dvrcast [all name] | live [all name]}]
On the SR:
show flash-media-streaming
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
When you execute the show flash-media-streaming stream-status live command and the Forwarder is a Content Origin server running Linux, the show command does not show statistics for the Content Origin server.
Examples
The following example displays the Flash media streaming information:
ServiceEngine#show flash-media-streamingFlash Media Streaming is disabled.Max. Allowed concurrent sessions are 200.Flash Media Streaming Monitoring is enabled.Admin list allow: 1.1.1.1Total number of wholesale licenses is 0.Bandwidth Details:Non wholesale bandwidth (Perpetual) is 200000 kbps.Configured max bandwidth is 10000 kbps.Total wholesale bandwidth (Term Based) is 0 kbps.Allowed bandwidth is 10000 kbps.Related Commands
flash-media-streaming
show statistics flash-media-streamingshow ftp
To display the caching configuration of the File Transfer Protocol (FTP), use the show ftp EXEC command.
show ftp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
This example lists the caching configuration of FTP:
ServiceEngine#show ftpFTP heuristic age-multipliers: directory-listing 30% file 60%Maximum Time To Live in days : directory-listing 3 file 7Minimum Time To Live in minutes: 60No objects are revalidated on every request.Serve-IMS without revalidation if...Directory listing object is less than 50% of max ageFile object is less than 80% of max ageIncoming Proxy-Mode:Servicing Proxy mode FTP connections on ports: 22 23 88 66 48 488 449 90Outgoing Proxy-Mode:Not using outgoing proxy mode.Maximum size of a cacheable object is unlimited.show hardware
To display the system hardware status, use the show hardware EXEC command.
show hardware
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC configuration mode.
Usage Guidelines
In Internet Streamer CDS Release 2.4, the output of the show hardware EXEC command displays the version of the TV-out hardware that the SE is equipped with. In the following excerpt of the sample output from the show hardware command, this particular information is highlighted in bold. Rev 3 in the command output indicates that the TV-out hardware uses the newer Revision 3 MPEG decoder PCI part. The Vela II Revision D and Revision E cards use the Revision 3 part.
ServiceEngine#show hardware...Total 1 CPU.1024 Mbytes of Physical memory.1 CD ROM drive (CD-224E)1 AV card (Vela II)2 GigabitEthernet interfaces1 Console interface2 USB interfaces [Not supported in this version of software]The following PCI cards were found:PCI-Slot-1 MPEG-Decoder-AV [1105:8476 (Sigma Designs, Inc.) (rev 3)]PCI-Slot-2 SCSIManufactured As: Pre-FCS 565 [867383Z]...The output of the show hardware EXEC command notifies you if the SE is running a version of the CDS software that does not support the TV-out hardware contained in the SE. In the following example, you are notified that the SE has a Vela II audio-video (AV) card that is not supported by the version of the CDS software that is running on the SE. In the following excerpt of the sample output from the show hardware command, this particular information is highlighted in bold:
ServiceEngine #show hardwareCPU 0 is GenuineIntel Intel(R) Celeron(R) CPU 1.70GHz (rev 1) running at 1699MHz.Total 1 CPU.1024 Mbytes of Physical memory.1 CD ROM drive (CD-224E)1 AV card (Vela II)[***Revision not supported in this version of software***]2 GigabitEthernet interfaces1 Console interface2 USB interfaces [Not supported in this version of software]The following PCI cards were found:...Examples
Table 2-29 describes the fields shown in the show hardware display.
Related Commands
show version
show hosts
To view the hosts on your SE, 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-30 describes the fields shown in the show hosts display.
show http
To display HTTP caching parameters, use the show http EXEC command.
show http {age-mult | all | cache-cookie | cache-fill-range | cache-on-abort | object | proxy | reval-each-request | ttl}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
The following example lists the configuration and status of HTTP:
ServiceEngine#show http allBasic 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 ageBinary object is less than 80% of max ageObjects with associated cookies are not cachedClient no-cache requests are retrieved from the origin serverCache on abort feature is disabledObjects will always continue to be cached on a client abortMaximum threshold is disabledMinimum threshold is disabledPercent threshold is disabledMaximum time to live in days: text 3 binary 7Minimum time to live for all objects in minutes: 5Objects are not revalidated on each requestIncoming Proxy-Mode:Not servicing incoming proxy mode connections.Outgoing Proxy-Mode:Not using outgoing proxy mode.Monitor Interval for Outgoing Proxy Servers is 60 secondsTimeout period for probing Outgoing Proxy Servers is 300000 microsecondsUse of Origin Server upon Proxy Failures is disabled.Persistent connection is enabled and set to allPersistent connection timeout is 600 secondsWWW-Authenticate headers containingNo host configured to receive Proxy-Authorization headerNo host configured to receive WWW-Authorization headerMaximum size of a cacheable object is unlimitedRequested Object URL validation is enabledHealing client is disabledTimeout for responses = 0 secondsMax number of misses allowed before stop healing mode = 0Port number for healing request/response = 14333Http-port to forward http request to healing server = 80The following example shows the IP address and port numbers of the HTTP incoming and outgoing proxy modes:
ServiceEngine#show http proxyIncoming Proxy-Mode:Servicing Proxy mode HTTP connections on port: 8080Outgoing Proxy-Mode:Directing request to proxy server at 10.1.1.1 port 7777Related Commands
http
show statistics httpshow icap
To display Internet Content Adaptation Protocol (ICAP) configuration details, use the show icap EXEC command.
show icap [service service_name]
Syntax Description
service
(Optional) Displays the configurations for the specified service.
service_name
Name of the service.
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 SE. 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 SE, use the show icap service service_name EXEC command.
Examples
The following example displays the ICAP configuration for the SE:
ServiceEngine#show icapICAP global configurations==========================ICAP apply: RULESICAP logging: DEFAULTICAP bypass Streaming content: ENABLEDICAP rescan cached objects on service update: ENABLEDICAP service configurations===========================----------------------------------------------Configurations for service test----------------------------------------------Enabled Status: ENABLEDLoad Balancing Scheme: Weighted-loadError handling scheme: Send client errorVectoring points registered:reqmod-precachereqmod-postcacherespmod-precacheServers configured:server URL: icap://10.1.1.1:1344/test-icap----------------------------------------------Configurations for service service----------------------------------------------Enabled Status: DISABLEDLoad Balancing Scheme: round-robinError handling scheme: BypassVectoring points registered:NoneServers configured:None----------------------------------------------Configurations for service servforicap----------------------------------------------Enabled Status: ENABLEDLoad Balancing Scheme: round-robinError handling scheme: BypassVectoring points registered:NoneServers configured:server URL: icap://1.2.3.4/servforicapRelated Commands
icap service
show interface
To display the hardware interface information, use the show interface EXEC command.
show interface {GigabitEthernet slot/port | PortChannel {1 | 2} | standby group num}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
Table 2-31 describes the fields shown in the show interface GigabitEthernet display.
Table 2-32 describes the fields shown in the show interface PortChannel display.
Table 2-33 describes the fields shown in the show interface standby display.
Related Commands
interface
show running-config
show startup-configshow 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 an SE. Typically, Cisco SEs contain the following three identification items, which make up the UDI:
•
•
•
This identity information is stored in the SE nonvolatile memory. Each SE has a unique device identifier (UDI). The UDI shows PID, VID and 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 SE'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 SE models, you can use the show inventory EXEC command to display the SE's UDI. On older SE models, use the show tech-support EXEC command to display the SE's UDI.
Examples
The following example shows the inventory information for one of the newer SE models (SE-565):
ServiceEngine#show inventoryPID: SE-565-K9 VID: 0 SN: serial_numberIn the preceding example, serial number is the serial number of the SE. The version ID is displayed as "0" because the version number is not available.
Table 2-34 describes the fields shown in the show inventory display.
The following example shows that you must use the show tech-support EXEC command to display the inventory information on an older SE model:
ServiceEngine# show inventoryPlease look at 'sh tech-support' for information!ServiceEngine# show tech-supportRelated 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
Defaults
Displays information about all defined access lists.
Command Modes
EXEC configuration mode.
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:
ServiceEngine#show ip access-listSpace available:47 access lists492 access list conditionsStandard IP access list 1 1 permit 10.1.1.22 deny 10.1.2.1(implicit deny any: 2 matches)total invocations: 2Extended IP access list 1001 permit tcp host 10.1.1.1 any2 permit tcp host 10.1.1.2 any3 permit tcp host 10.1.1.3 any(implicit fragment permit: 0 matches)(implicit deny ip any any: 0 matches)total invocations: 0Standard IP access list test1 permit 1.1.1.1 (10 matches)2 permit 1.1.1.33 permit 1.1.1.2(implicit deny: 2 matches)total invocations: 12Interface access list references:GigabitEthernet 0/0 inbound 100Application access list references:tftp_server standard 1UDP ports: 69The following example shows sample output from the show ip access-list command for the access list named test:
ServiceEngine#show ip access-list testStandard IP access list test1 permit 1.1.1.1 (10 matches)2 permit 1.1.1.33 permit 1.1.1.2(implicit deny: 2 matches)total invocations: 12
Note
Related Commands
clear
ip access-listshow 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 configuration mode.
Examples
The show ip routes command displays the IP routing table.
Table 2-35 describes the fields shown in the show ip routes display.
.
Related Commands
ip
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-36 describes the fields shown in the show ldap display.
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
The following is an example of a syslog message for proxy-mode native FTP support:
SE-FTP_PROXY-3-252009: Failed to configure FTP Proxy-mode listener on port'[port]'.Explanation: Could not start proxy-mode listener for FTP controlconnection for the specified port. The port is temporarilyin an un-bindable state, or is in use by some otherapplication.Action: Check whether the port has been configured for use by adifferent application. If not, retry theincoming proxy command after 2 minutes. If this errorrepeats frequently, contact Cisco TAC.To view information about events that have occurred in all devices in your CDS network, you can use the system message log in the CDSM GUI. The CDSM logs only severity level critical or higher messages from registered nodes. Also, the CDSM 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, SE, are not related to the messages logged in the system log file on the sysfs partition on the CDSM as /local1/syslog.txt.
The syslog.txt file on the CDSM contains information about events that have occurred on the CDSM and not on the registered nodes. The messages that are 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 CDSM because the problem never occurred on the CDSM but only on the registered node. However, this error message is displayed in the system message log for device, SE
Examples
The following example displays the syslog host configuration on an SE:
ServiceEngine#show loggingSyslog to host is disabledPriority for host logging is set to: warningSyslog to console is disabledPriority for console logging is set to: warningSyslog to disk is enabledPriority for disk logging is set to: noticeFilename for disk logging is set to: /local1/syslog.txtSyslog facility is set to *Syslog disk file recycle size is set to 500000Related Commands
clear
loggingshow movie-streamer
To display the Movie Streamer configuration, use the show movie-streamer EXEC command.
show movie-streamer [bandwidth | cache | proxy]
Syntax Description
bandwidth
(Optional) Displays Movie Streamer bandwidth configuration.
cache
(Optional) Displays Movie Streamer cache configuration.
proxy
(Optional) Displays Movie Streamer proxy configuration.
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
The following example shows the Movie Streamer configuration:
ServiceEngine#show movie-streamerMovie Streamer version cde200-5.0.3Movie Streamer is not enabled------ Movie Streamer General Configurations ------Movie Streamer max sessions configured: 8000Movie Streamer transport source ip address is not configuredMovie Streamer accelerate for VOD is enabledMovie Streamer client idle timeout is 300 secondsMovie Streamer origin-server idle interval is 10 secondsMovie Streamer client rtp timeout is 180 secondsMovie Streamer outgoing bitrate per streamer has no limitMovie Streamer incoming bitrate per streamer has no limit------ Movie Streamer Bandwidth Configurations ----Movie Streamer Outgoing bandwidth enforced is 2000000 kbpsMovie Streamer Incoming bandwidth enforced is 2000000 kbps------ Movie Streamer Cache Configurations --------Movie Streamer cache is enabledMovie Streamer cache age-multiplier: 30%Movie Streamer cache max-ttl: 1 (days)Movie Streamer cache revalidate for each request is enabled------ Movie Streamer Proxy Configurations --------Movie Streamer proxy has not been configured.------ Movie Streamer Broadcast List --------------Related Commands
movie-streamer
show statistics movie-streamershow ntp
To display the Network Time Protocol (NTP) parameters, use the show ntp EXEC command.
show ntp status
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
Table 2-37 describes the fields shown in the show ntp status display.
Related Commands
clock
ntpshow 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
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:
•
•
•
Note
Examples
Table 2-38 describes the fields shown in the show processes displays.
show programs
To display a list of programs on the SE, use the show programs EXEC command.
show programs [ movie-streamer [cli | live | rebroadcast] | program-id id | program-name name]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
Typically, users create programs using the CDSM 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 and end.
A program in the Internet Streamer CDS 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 SEs 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 CDSM GUI allows you to create a program, schedule it, and deliver it over your multicast-enabled CDS network. Programs can consist of prerecorded video or live events. In the case of live events, the Internet Streamer CDS software interoperates with third-party encoders and IP/TV Broadcast Servers to transmit the live stream across the CDS network.
When creating a program in the CDSM GUI, the administrator specifies the following information:
•
–
–
•
–
–
•
–
–
•
–
–
–
•
–
–
–
–
•
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 SE and transmitted to edge SEs using unicast. From the edge SEs, 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 CDSM GUI, the administrator must complete the following tasks:
1.
2.
3.
After you have completed the preceding tasks, you are ready to define the program and configure the program settings in the CDSM GUI. The CDSM 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 Internet Streamer CDS Release 2.4 network, make sure that there are no external proxy servers physically located between your Internet Streamer SEs and your root SE that require proxy authentication. Also, make sure that proxy authentication is not enabled on any receiver SEs that might be in the logical, hierarchical path between the root SE and the receiver SE 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 SEs, you can specify the following rule on all of the parent SEs in the channel:
ServiceEngine(config)# rule pattern-list 1 downstream-SE-ipaddressServiceEngine(config)# rule no-auth pattern-list 1Live 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 five 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 Movie Streamer live programs.
Scheduled Rebroadcasts
In a scheduled rebroadcast, the pre-positioned content is scheduled to be streamed from edge SEs using multicast. To define a program for a rebroadcast event, the administrator must complete the following tasks:
1.
2.
3.
4.
Note
The CDSM allows you to define a program as a Movie Streamer rebroadcast.
Fast Encoder Failover
In Internet Streamer CDS, release 2.4, the show programs command was enhanced to support encoder failover. Issues with the previous release were as follows:
•
•
•
With this release, the output of the command looks like the following:
ServiceEngine#show programs program-name live2Current Time : May 18 2009 @ 10:10:33 IST (1242621633)Program ID : 1341Program Name : live2Delivery Service ID : 1340Delivery Service Name : live2Type : WMT Managed Scheduled LiveForwarder List : 3.1.2.11 <- 172.22.28.104Schedules :Schedule #1:Start Time (loc) : May 18 2009 @ 10:11:00 IST (1242621660)End Time (loc) : May 18 2009 @ 10:12:00 IST (1242621720)Duration : 60 secsRepeat : N/ARepeatdays : N/ATime spec : localSource :Server : http://172.22.28.104:1881Destination :Unicast Access URL: rtsp://kinswmt.spcdn.net/live2Multicast URL : http://kinswmt.spcdn.net/live2.nsc.asxMulticast Address : 224.2.2.58:94Start Time (loc) : May 18 2009 @ 10:11:00 IST (1242621660)Start Time : May 18 2009 @ 04:41:00 GMT (1242601860)End Time (loc) : May 18 2009 @ 10:12:00 IST (1242621720)End Time : May 18 2009 @ 04:42:00 GMT (1242601920)Current Status : ScheduledTime left : N/AServiceEngine#show clockLocal time: Mon May 18 10:10:47 IST 2009RT-612-2#sh programs program-name live2Current Time : May 18 2009 @ 10:11:05 IST (1242621665)Program ID : 1341Program Name : live2Delivery Service ID : 1340Delivery Service Name : live2Type : WMT Managed Scheduled LiveForwarder List : 3.1.2.11 <- 172.22.28.104Schedules :Schedule #1:Start Time (loc) : May 18 2009 @ 10:11:00 IST (1242621660)End Time (loc) : May 18 2009 @ 10:12:00 IST (1242621720)Duration : 60 secsRepeat : N/ARepeatdays : N/ATime spec : localSource :Server : http://172.22.28.104:1881Destination :Unicast Access URL: rtsp://kinswmt.spcdn.net/live2Multicast URL : http://kinswmt.spcdn.net/live2.nsc.asxMulticast Address : 224.2.2.58:94Start Time (loc) : May 18 2009 @ 10:11:00 IST (1242621660)Start Time : May 18 2009 @ 04:41:00 GMT (1242601860)End Time (loc) : May 18 2009 @ 10:12:00 IST (1242621720)End Time : May 18 2009 @ 04:42:00 GMT (1242601920)Current Status : PlayingTime left : 55 secsServiceEngine#show clockLocal time: Mon May 18 10:11:10 IST 2009RT-612-2#sh programs program-name live2Current Time : May 18 2009 @ 10:12:10 IST (1242621730)Program ID : 1341Program Name : live2Delivery Service ID : 1340Delivery Service Name : live2Type : WMT Managed Scheduled LiveForwarder List : 3.1.2.11 <- 172.22.28.104Schedules :Schedule #1:Start Time (loc) : May 18 2009 @ 10:11:00 IST (1242621660)End Time (loc) : May 18 2009 @ 10:12:00 IST (1242621720)Duration : 60 secsRepeat : N/ARepeatdays : N/ATime spec : localSource :Server : http://172.22.28.104:1881Destination :Unicast Access URL: rtsp://kinswmt.spcdn.net/live2Multicast URL : http://kinswmt.spcdn.net/live2.nsc.asxMulticast Address : 224.2.2.58:94Start Time (loc) : End of Program ReachedStart Time : End of Program ReachedEnd Time (loc) : End of Program ReachedEnd Time : End of Program ReachedCurrent Status : StoppedTime left : N/AServiceEngine#show clockLocal time: Mon May 18 10:12:14 IST 2009Now the show programs command output contains the forwarder list with the backup source, and the root SE and non-root SE output is consistent. Also, if the user executes the show statistics wmt streamstat command from the root SE, the output shows which server is currently serving.
The source URL displays in the source section and the CLI and CDSM are consistent. Because the non-content acquirer cannot get the information on which source is serving, the output contains tips, such as "Please check which source is serving in content acquirer."
The CDSM parses the backup SDP file and puts the results into the database. The item video_file_back_up saves the backup source server's IP address and port in the play_media table.
Examples
Table 2-39 describes the fields shown in the show programs program-name and program-id display.
show qos
To display Quality of Service (QoS) information, use the show qos EXEC command.
show qos
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
This example shows the output that might be displayed if you do not enter any keywords:
ServiceRouter# show qosCamiant policy service config file is not configuredCamiant policy service is runningRelated Commands
qos
show statistics qosshow 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-40 describes the fields shown in the show radius-server display.
Related Commands
radius-server
show rea
To display the remote execution agent (REA) information use the show rea EXEC command.
show rea info
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
The following example displays the REA information:
ServiceEngine#show rea inforea agent is runningRelated Commands
rea
show rcp
To display Remote Copy Program (RCP) information, use the show rcp EXEC command.
show rcp
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
This example shows how to display RCP information:
ServiceEngine#show rcprcp service configurations:rcp enableRelated Commands
rcp
show rtsp
To display the Real-Time Streaming Protocol (RTSP) configurations, use the show rtsp EXEC command.
show rtsp [gateway]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Examples
The following example display the output of the show rtsp gateway EXEC command.
ServiceEngine#show rtsp gatewayRTSP Gateway ip-address 10.107.193.30RTSP Gateway incoming port 67RTSP Gateway L4-switch not enabledRTSP Gateway Transparent Interception:Not configured.Related Commands
rtsp
show rule
To display rules configuration information, use the show rule EXEC command.
show rule action all [protocol {http | rtmp | rtsp}]
show rule action allow [protocol {http | rtmp | rtsp}]
show rule action block [protocol {http | rtmp | rtsp}]
show rule action generate-url-signature [protocol {http | rtmp | rtsp}]
show rule action no-cache [protocol {http | rtmp | rtsp}]
show rule action [protocol {http | rtmp | rtsp}]
show rule action redirect [protocol {http | rtmp | rtsp}]
show rule action refresh [protocol {http | rtmp | rtsp}]
show rule action rewrite [protocol {http | rtmp | rtsp}]
show rule action use-icap-service [protocol {http | rtmp | rtsp}]
show rule action validate-url-signature [protocol {http | rtmp | rtsp}]
show rule all
show rule pattern-list {1-512 pattern-type | all}
Syntax Description
all
Displays rules with all action types.
http
Displays HTTP-related requests for this action.
rtmp
Displays RTMP-related requests for this action.
rtsp
Displays RTSP-related requests for this action.
protocol
(Optional) Specifies the protocol to which actions apply.
allow
Allows the request.
block
Blocks the request.
generate-url-signature
Generates a signed URL.
no-cache
Does not cache the object.
redirect
Redirects the request to the rewritten URL.
refresh
Revalidates the object with the web server.
rewrite
Rewrites the URL and fetch.
use-icap-service
Sets ICAP service.
validate-url-signature
Validates a signed URL.
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-41).
all
Displays rules with all pattern lists.
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
You can use the show rule pattern-list pattern-type command to display rules using a specific pattern type. For a more complete explanation of specific rules, see the "rule" section.Table 2-41 shows the permitted pattern types and describes each pattern type.
Examples
The following example displays all rules with the configured action types and pattern lists:
ServiceEngine#show rule allRules Template Configuration----------------------------Rule Processing Enabledrule block domain bar.comrule block domain \.foo.comrule rewrite url-regsub http://www.ietf.org/rfc/.* http://wwwin-eng.cisco.com/RFC/$1rule no-cache dst-ip 172.31.120.0 255.255.192.0rule no-cache url-regex \.*cgi-bin*Related Commands
clear
ruleshow running-config
To display the current running configuration information on the terminal, use the show running-config EXEC 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.
Note
Examples
The following example displays the current running configuration information:
ServiceEngine#show running-configV2-CDE200-3#show running-config! CDS version 2.3.9!device mode service-engine!!hostname V2-CDE200-3!!primary-interface PortChannel 1!!interface PortChannel 1ip address 3.1.14.72 255.255.255.0exitinterface PortChannel 2ip address 4.0.8.13 255.255.255.0exit!interface GigabitEthernet 1/0channel-group 2exitinterface GigabitEthernet 2/0channel-group 2exitinterface GigabitEthernet 3/0channel-group 1exitinterface GigabitEthernet 4/0channel-group 1exitinterface GigabitEthernet 5/0channel-group 1exitinterface GigabitEthernet 6/0channel-group 1exit!!ip default-gateway 3.1.14.1!!offline-operation enable!!rule action block pattern-list 3rule action redirect http://www.baidu.com pattern-list 2rule pattern-list 1 url-regex http://chunliu.com/b.wmvrule pattern-list 2 header-field request-line b.wmvrule pattern-list 3 header-field request-line c.wmv!icap service camiantserver icap://trythis/servernameexit!!transaction-logs enabletransaction-logs archive interval 120!username admin password 1 bVmDmMMmZAPjYusername admin privilege 15!!authentication login local enable primaryauthentication configuration local enable primary!access-lists 300 deny groupname Disneyaccess-lists 300 permit groupname anyaccess-lists enable!!telnet enable!!cdsm ip 4.0.8.10cms enable!!service-router service-monitor threshold wmt 50service-router service-monitor number-of-samples wmt 5service-router service-monitor sample-period wmt 15qos device-policy-service enable!!cache content max-cached-entries 1000! End of CDS configurationV2-CDE200-3#Related Commands
configure
copyshow service-router
To display the service router configuration, use the show service-router EXEC command.
On the SE or on the CDSM:
show service-router {keepalive-interval | service-monitor}
On the SR:
show service-router {access-policy | content-based-routing | dns-ttl | forwarding [content-origin content-origin] | lastresort [domain name] | load {all | sename sename} | location-based-routing | proximity-based-routing | routes [content-origin content-origin] | service-monitor | services {all | sename sename} | summary [content-origin content-origin]}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Usage Guidelines
This command allows users to check the service router-releated configuration. Through this command, users can view the configured features of an SR, such as location-based routing and content-based routing.
Examples
The following example displays the service router information on the SE:
ServiceEngine#show service-router service-monitorMonitor types configured:-------------------------CPU,MEM,KMEM,WMT,FMS,WEB,MS,DISK,NICThreshold values configured:---------------------------CPU : 80%MEM : 80%KMEM : 50%WMT : 50%FMS : 90%MS : 90%WEB : 90%NIC : 90%DISK : 80%DISKFAILCNT : 7Sample periods configured:--------------------------CPU : 1 (secs)MEM : 1 (secs)KMEM : 1 (secs)WMT : 15 (secs)FMS : 1 (secs)NIC : 3 (secs)DISK : 1 (secs)Sample counts configured to use in calculating average:-------------------------------------------------------CPU : 2MEM : 2KMEM : 2WMT : 5FMS : 2NIC : 2DISK : 2Device Status-------------CPUCurrent load : 0%Average load : 0%Threshold : Not reachedDISKCurrent load : 0%Average load : 0%Threshold : Not reachedStatus : OperationalMEMAverage Used Memory : 4%Threshold : Not reachedKMEMAverage Kernel Memory : 1%Threshold : Not reachedNICAverage BW In : 0%Average BW Out : 0%Threshold : Not reachedAverage Device load : 0%Services Status---------------Critical Service(s) : RunningWEBEnabled : YesThreshold : Not reachedStopped : NoWMTEnabled : YesCurrent Stream Count : 0Threshold : Not reachedStopped : NoMSEnabled : NoFMSEnabled : NoThe following example displays the service router information on the CDSM:
CDSM#show service-router service-monitorMonitor types configured:-------------------------CPU,MEM,KMEM,DISKThreshold values configured:---------------------------CPU : 80%MEM : 80%KMEM : 50%DISK : 80%DISKFAILCNT : 1Sample periods configured:--------------------------CPU : 1 (secs)MEM : 1 (secs)KMEM : 1 (secs)DISK : 1 (secs)Sample counts configured to use in calculating average:-------------------------------------------------------CPU : 2MEM : 2KMEM : 2DISK : 2Device Status-------------CPUCurrent load : 0%Average load : 0%Threshold : Not reachedDISKCurrent load : 0%Average load : 0%Threshold : Not reachedStatus : OperationalMEMAverage Used Memory : 13%Threshold : Not reachedKMEMAverage Kernel Memory : 1%Threshold : Not reachedAverage Device load : 0%Related Commands
service-router
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 eight 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:
CDSM# show services portsService information by port---------------------------550 Started on Mon Oct 14 12:13:20 2002Runs 1 serviceCisco_Streaming_Engine553 Started on Mon Oct 14 12:13:20 2002Runs 1 serviceRTSP_Gateway554 Started on Mon Oct 14 12:13:20 2002Runs 1 serviceRTSP_Gateway...15256 Started on Mon Oct 14 12:13:20 2002Runs 1 serviceCMS27999 Started on Mon Oct 14 12:13:20 2002Runs 1 serviceReal_Server28000 Started on Mon Oct 14 12:13:20 2002Runs 1 serviceReal_ProxyThe following example displays a services information summary, showing the service and the associated port numbers:
CDSM# show services summaryService Ports-----------------------------------------------------CMS 15256 2000 2001 2002 2003 2004 2005GUI 8001Wmt 1755 1756 1757 1799icp 3128emdb 5432CertMgr 6001MgmtAgent 5252Real_Proxy 1090 8082 9002 555 28000 7879 6060 7071 3031Cdsm_UI_http 8443Real_Server 7070 8081 9091 27999 7878 7802 1554 3030 4040 5050RTSP_Gateway 554 553RPC_APACHE_PORT 6550temp_RPC_APACHE_PORT 8008Cisco_Streaming_Engine 550 SNMPshow snmp
To check the status of Simple Network Management Protocol (SNMP) communications, use the show snmp EXEC command.
show snmp {alarm-history | engineID | group | stats | user}
Syntax Description
alarm-history
Displays SNMP alarm history information.
engineID
Displays the local SNMP engine identifier.
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-42 describes the fields shown in the snmp alarm-history display.
Table 2-42 show snmp alarm-history Field Descriptions
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 a CDS device contain numeric alarm IDs.
ModuleID
Traps sent by a CDS device contain numeric module IDs. See Table 2-43 to map module names to module IDs.
Category
Traps sent by an CDS device contain numeric category IDs. See Table 2-44 to map category names to category IDs.
Descr
Description of the Internet Streamer CDS software alarm and the application that generated the alarm.
Table 2-43 describes themapping of module names to module ids.
Table 2-44 describes themapping of category names to category ids.
Table 2-44 Mapping of Category Names to Category IDs
Communications
1
Service Quality
2
Processing Error
3
Equipment
4
Environment
5
Content
6
Table 2-45 describes the fields shown in the show snmp stats display.
Table 2-46 describes the fields shown in the show snmp engineID display.
Table 2-46 show snmp engineID Field Descriptions
Local SNMP Engine ID
String that identifies the copy of SNMP on the local device.
Table 2-47 describes the fields shown in the show snmp group display.
Table 2-48 describes the fields shown in the show snmp user display.
Related Commands
snmp-server community
snmp-server contact
snmp-server enable traps
snmp-server group
snmp-server host
snmp-server location
snmp-server notify inform
snmp-server user
snmp-server viewshow 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
Usage Guidelines
To display SSH status, enter the show ssh EXEC command.
Related Commands
sshd
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 standby interface information, enter the show standby EXEC command.
Examples
Table 2-49 describes the fields shown in the show standby display.
Related Commands
show interface
show running-config
show startup-configshow 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 SE:
ServiceEngine#show startup-config! CDS version 2.3.9!device mode service-engine!!hostname V2-CDE200-3!!!primary-interface PortChannel 1!!interface PortChannel 1ip address 3.1.14.72 255.255.255.0exitinterface PortChannel 2ip address 4.0.8.13 255.255.255.0exit!interface GigabitEthernet 1/0channel-group 2exitinterface GigabitEthernet 2/0channel-group 2exitinterface GigabitEthernet 3/0channel-group 1exitinterface GigabitEthernet 4/0channel-group 1exitinterface GigabitEthernet 5/0channel-group 1exitinterface GigabitEthernet 6/0channel-group 1exit!!ip default-gateway 3.1.14.1!!offline-operation enable!!!rule action block pattern-list 3rule action redirect http://www.baidu.com pattern-list 2rule pattern-list 1 url-regex http://chunliu.com/b.wmvrule pattern-list 2 header-field request-line b.wmvrule pattern-list 3 header-field request-line c.wmv!icap service camiantserver icap://trythis/servernameexit!!!transaction-logs enabletransaction-logs archive interval 120!username admin password 1 bVmDmMMmZAPjYusername admin privilege 15!!authentication login local enable primaryauthentication configuration local enable primary!access-lists 300 deny groupname Disneyaccess-lists 300 permit groupname anyaccess-lists enable!!telnet enable!!!cdsm ip 4.0.8.10cms enable!!!service-router service-monitor threshold wmt 50service-router service-monitor number-of-samples wmt 5service-router service-monitor sample-period wmt 15qos device-policy-service enable!!cache content max-cached-entries 1000! End of CDS configurationRelated Commands
configure
copy
show running-configshow statistics access-lists 300
To display SE 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-50 describes the fields shown in the show statistics access-lists 300 display.
Related Commands
clear
show statistics acquirer
To display SE acquirer channel statistics, use the show statistics acquirer EXEC command.
show statistics acquirer [contents {delivery-service-id delivery-service-id | delivery-service-name delivery-service-name} | delivery-service-id delivery-service-id | delivery-service-name delivery-service-name | errors {delivery-service-id delivery-service-id | delivery-service-name delivery-service-name} | job-list {delivery-service-id delivery-service-id | delivery-service-name delivery-service-name}]
Syntax Description
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 SE is the root SE. 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-51 describes the fields shown in the show statistics acquirer display.
Related Commands
acquirer (EXEC)
clear statistics
show acquirershow statistics authentication
To display SE 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 display the number of access requests, denials, and allowances recorded. Use the show statistics authentication command to display the number of authentication accesses recorded.
Examples
The fields shown in the show statistics authentication display include the following
•
•
•
Related Commands
authentication
clear statistics
show authentication
show statistics authenticationshow statistics cdnfs
To display SE CDS 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-52 describes the show statistics cdnfs command fields displayed in the command output.
Related Commands
cdnfs
clear
show cdnfs
show disks
