-
Cisco Internet Streamer CDS 3.3 Command Reference
-
Preface
-
Command-Line Interface Command Surmmary
-
Cisco Internet Streamer CDS 3.3 Software Commands, aaa through line
-
Cisco Internet Streamer CDS 3.3 Software Commands, lls through show statistics content-mgr
-
Cisco Internet Streamer CDS 3.3 Software Commands, show statistic distribution through write
-
Acronyms
-
Standard Tme Zones
-
Index
-
Feedback
Table Of Contents
multicast (Global Configuration)
multicast (EXEC Configuration)
show ip ospf retransmission-list
show ip rib recursive-next-hop
show ip rib unresolved-next-hop
show statistics access-lists 300
lls
To view a long list of directory names, use the lls user command in user EXEC configuration mode.
lls [directory]
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
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
location community
To configure the community values that are associated with a Proximity Engine, use the location community command in BGP configuration (config-bgp) mode. To remove community values that are associated with a Proximity Engine, use the no form of this command.
location community community_string [target community_string | weight num]
no location community community_string [target community_string | weight num]
Syntax Description
Command Defaults
By default, no community values are associated with the Proximity Engine.
Command Modes
BGP configuration (config-bgp) mode.
Usage Guidelines
Use the location community command to configure community string values. The configuration includes all community values that represent location. When community values are configured, the Proximity Engine creates and maintains a sorted table of communities within BGP.
The maximum number of location communities allowed for each SE is 128.
The community_string can be in one of the following forms:
•
Community number, such as 100:3535 or 200:4566
•
Use the show ip bgp summary and show ip bgp community commands to display the community values that are configured for a Proximity Engine.
In order for the proximity function to work, one of the following is required:
•
•
Note
Previously location-specific communities must be manually configured using the location community command. The location community weight command includes the weight that must be assigned to the location community. Also in this release, the order the community strings are displayed in the running-config was changed. In the old releases, community strings were displayed in the order of lengths of the strings, but now they are displayed in alphabetical order.
Location community ranges overlaps are not allowed. Specific location communities are always allowed. Thus if location community 5:1-5:10 is already configured, then 5:2-5:3 is not allowed, 5:2-5:7 is also not allowed. 5:5 is allowed:
ServiceRouter(config-bgp)# location community 5:1-5:10 weight 2ServiceRouter(config-bgp)# location community 5:2-5:3%BGP: Invalid or overlapping location community.ServiceRouter(config-bgp)# location community 5:2-5:7%BGP: Invalid or overlapping location community.ServiceRouter(config-bgp) #location community 5:5ServiceRouter(config-bgp)#For the proximity calculation, the most specific match's weight is taken. If there is no such match, then the weight of the range is taken. In the example above, a PTA with location-community 5:5, has weight 1 if both PSA and PTA location-community match, and a PTA with location community 5:1 has weight 2, if PSA And PTA location-community also match.
Examples
The following example shows how use the location community command to configure community values for a Proximity Engine.
ServiceRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# location community 100:3535ServiceRouter(config-bgp)# location community 100:50-100:100The following example shows how to configure the location community weight of 2:
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# location community 5:1-5:10 weight 2The following example associates a source/PSA with a location-community community 1:1 with a target/PTA with a location community 2:2 and the weight of this association is 2. Also, the source and/or target community might be a range:
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# location community 1:1 target 2:2 weight 2The following example associates the source community 1:1 with all target communities in the range 2:0-2:10 with preference weight 2:
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# location community 1:1 target 2:0-2:10 weight 2The following example associates all source communities in the range 1:0-1:10 with target community 2:2 with preference weight 2:
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# location community 1:0-1:10 target 2:2 weight 2The following example associates all source communities in the range 1:0-1:10 with all target communities in the range 2:0-2:10 with preference weight 2. It can also be seen that a PSA with community 1:1 and a PTA with community 2:2 would satisfy all four commands above since 1:1 falls in the range 1:0-1:10 and 2:2 falls in the range 2:0-2:10. In such scenario, where multiple commands satisfy the matching criteria, the weight is based on the preference level of the commands. The preference level of the four commands above is descending in the following order:
1.
2.
3.
4.
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# location community 1:0-1:10 target 2:0-2:10 weight 2Related Commands
proximity algorithm bgp location-community
Specifies that the community-based proximity algorithm be used.
log-adjacency-changes
To configure the router to send a syslog message when an IS-IS neighbor goes up or down, use the log-adjacency-changes router configuration command. To turn off this function, use the no form of this command.
log-adjacency-changes
no log-adjacency-changes
Syntax Description
This command has no arguments or keywords.
Command Defaults
Sending syslog messages when an IS-IS neighbor goes up or down is enabled.
Command Modes
BGP (config-bgp), IS-IS (config-isis) and OSPF configuration (config-ospf) modes.
Usage Guidelines
This command allows you to know about IS-IS neighbors going up or down without turning on the debug IS-IS adjacency command. The log-adjacency-changes command provides a higher level view of changes in the peer relationship with less output. This command is enabled by default but messages are sent only when up or down (full or down) events are reported.
Examples
The following example shows how to configure the router to send a syslog message when an IS-IS neighbor's state changes:
ServiceRouter(config)# router isis ServiceRouter(config-isis)# log-adjacency-changesServiceRouter(config-isis)#Related Commands
logging
To configure system logging, use the logging command in Global configuration mode. 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 loglevel} | disk {enable | filename filename | priority loglevel | recycle size} | facility facility | host {hostname | ip_address} [port port_num | priority loglevel | rate-limit message_rate]}
Syntax Description
Command 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
Command Modes
Global configuration (config) mode.
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 is 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 command. Logging can be configured to send various levels of messages to the console using the logging console priority command.
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
Users can log to only a single remote syslog host Use one of the following two commands 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:
•
•
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
log-neighbor-changes
To enable logging of BGP neighbor resets, use the log-neighbor-changes BGP configuration command. To disable the logging of BGP neighbor changes, use the no form of this command.
log-neighbor-changes
no log-neighbor-changes
Syntax Description
This command has no arguments or keywords.
Command Defaults
If the log-neighbor-changes command is not issued, neighbor status change messages are not tracked. One exception is a reset, which is always available as output of the show ip bgp neighbors command.
Command Modes
BGP configuration (config-bgp) mode.
Usage Guidelines
The log-neighbor-changes command enables logging of BGP neighbor status changes (up or down) and resets for troubleshooting network connectivity problems and measuring network stability. Unexpected neighbor resets might indicate high error rates or high packet loss in the network and should be investigated.
Using the log-neighbor-changes command to enable status change message logging does not cause a substantial performance impact, unlike, for example, enabling per BGP update debugging.
In order for the proximity function to work, one of the following is required:
•
•
Note
Log neighbor changes help keep track of the adjacency changes. Once you enable the log-neighbor-changes command, you can monitor BGP logs to see changes and troubleshoot issues by using the type-tail errorlog/bgp_log.current command.
Examples
The following example logs neighbor changes for BGP:
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# log-neighbor-changesServiceRouter(config-bgp)#ls
To view a list of files or subdirectory names within a directory, use the ls command in EXEC configuration mode.
ls [directory]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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 shows how to display a list of files within the current working directory:
ServiceEngine# ls/local1The following example shows how to display a list of files within the /local1 directory:
ServiceEngine# ls /local1core_dircrasherrorloglogslost+foundservice_logssmartfiltersyslog.txtRelated Commands
lsp-mtu
To set the maximum transmission unit (MTU) size of IS-IS LSPs, use the lsp-mtu IS-IS configuration command. To set the MTU to it's default value, use the no form of this command.
lsp-mtu size
no lsp-mtu size
Syntax Description
Command Defaults
The default size is 1497 bytes.
Command Modes
IS-IS configuration (config-isis) mode.
Usage Guidelines
The LSP MTU size describes the amount of information that can be recorded in a single LSP. The lsp-mtu command is used to configure the maximum number of bytes allowed in an LSP. If this command is not configured, IS-IS uses the default size of 1500 bytes while sending LSPs for Gigabit Ethernet. Use the no lsp-mtu command to configure the maximum number of bytes allowed in an LSP at the default value of 1497 bytes.
Examples
The following example shows how to configure the MTU size to be 1400 bytes.
ServiceRouter(config)# router isisServiceRouter(config-isis)# lsp-mtu 1400ServiceRouter(config-isis)# endServiceRouter#Related Commands
mkdir
To create a directory, use the mkdir command in EXEC configuration mode.
mkdir directory
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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
mkfile
To create a new file, use the mkfile command in EXEC configuration mode.
mkfile filename
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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
model
To change the CDE250 platform model number after a remanufacturing or rescue process, use the model command in EXEC configuration mode.
model {cde250-2S10 | cde250-2S6 | cde250-2S8 | cde250-2S9}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Use the model command to change the CDE250 model type. Table 2-10 shows the internal and external drives for the CDE250 models.
Examples
The following example shows how to change the CDE250 to model 2S9:
ServiceEngine# model CDE250-2S6This platform is already a CDE250-2S6.ServiceEngine#movie-streamer
To enable and configure the Movie Streamer server, use the movie-streamer command in Global configuration mode. To disable the Movie Streamer, use the no form of this command.
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}
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
Command Defaults
days: 1
hours: 72
minutes: 4320
seconds: 259200Command Modes
Global configuration (config) mode.
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 to 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 150The following example shows how to set the original server interval to 5 second:
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 their age's 50%:
ServiceEngine(config)# movie-streamer cache age-multiplier 50The following example shows how to set the cache content max ttl to 100 days:
ServiceEngine(config)# movie-streamer cache max-ttl days 100The following example shows how to set the max concurrent sessions to 7000:
ServiceEngine(config)# movie-streamer max-concurrent-sessions 7000The following example shows how to set the out going proxy:
ServiceEngine(config)# movie-streamer proxy outgoing rtsp host 10.74.61.98 554The following example shows how to set the source the IP of the transport header while behind NAT:
ServiceEngine(config)# movie-streamer transport-src-address 10.74.61.99Related Commands
show movie-streamer
Displays the Movie Streamer configuration.
show statistics movie-streamer
Displays statistics for the Movie Streamer.
mtu
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 mtu_size
no mtu mtu_size
Syntax Description
Command Defaults
The default MTU packet size for an Ethernet interface is 1500 bytes.
Command Modes
Interface configuration (config-if) mode.
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 shows how to set the MTU packet size as 1500 bytes:
ServiceEngine(config-if)# mtu 1500The following example shows how to reset the MTU packet size:
ServiceEngine(config-if)# no mtu 1500Related Commands
multicast (Global Configuration)
To configure multicast options, use the multicast command in Global configuration mode. To disable individual options, use the no form of this command.
multicast {client {receiver enable | sender enable} | fixed-carousel enable | max-concurrent-jobs number_jobs | priority-weight num | sender-delay delay}
no multicast {client {receiver enable | sender enable} | fixed-carousel enable | max-concurrent-jobs number_jobs | priority-weight num | sender-delay delay}
Note
Syntax Description
Defaults
Sender Delay: 960 seconds.
Maximum Concurrent Jobs: 5
Priority Weight: 50%
Command Modes
Global configuration mode.
Usage Guidelines
Note
In the CDS, content is replicated through a channel distribution architecture. Content in channels can be transmitted by unicast pull, or if multicasting is enabled, by multicast push. Multicasting allows efficient distribution of content to multiple SEs and is useful when many end users are interested in the same content. The Internet Streamer CDS software supports Pragmatic General Multicast (PGM)-based multicast replication using either satellite or multicast-enabled terrestrial infrastructures.
Multicast delivery enables the distribution of streaming media by allowing different receiving devices on the IP multicast to receive a single stream of media content from the SE simultaneously. This method can save significant network bandwidth consumption, because a single stream is sent to many devices, rather than sending a single stream to a single device every time that this stream is requested.
This multicast delivery feature is enabled by setting up a multicast address on the SE to which different devices, configured to receive content from the same channel, can subscribe. The delivering device sends content to the multicast address set up at the SE, from which it becomes available to all subscribed receiving devices.
To take advantage of multicasting, all devices, including SEs, routers, and clients, must be multicast enabled. For this reason, multicasting is mostly used in local networks where routers can be configured for multicasting. Multicast delivery over the Internet can only be accomplished when all the devices that participate in the multicast have been enabled for multicasting.
For multicast content replication, SEs are grouped into multicast clouds. A multicast cloud consists of one sender SE, an optional backup sender SE, and at least one receiver SE in a hub and spoke topology. All the SEs in one multicast cloud share a unique advertisement address that allows them to communicate multicast session information. The multicast cloud is then associated with one or more multicast-enabled channels.
In pull-based unicast content distribution, a unicast receiver pulls file data out of the proper forwarder (or root SE) when a client requests the content. In multicast content distribution, the sender SE in a multicast cloud proactively pushes content into the cloud according to a preconfigured schedule.
The receiver SEs listen on the advertisement IP address for information on the content to be replicated from the sender and decide whether to accept an advertisement and whether to receive the content.
The content metadata (machine-readable information that describes the characteristics of the content) must be distributed to a receiver first before the content can be replicated. The content metadata helps to define what content to retrieve, how the content will be retrieved, how recently the content has been updated, how the content is to be pre-positioned (for example, the expiration time), and so forth. The metadata is always distributed using unicast. The content, however, can be replicated using either multicast or unicast. A multicast receiver rejects the multicast sender's advertisement of a file if the proper content metadata has not arrived. During the content distribution process, both the content and its associated information describing the content, called the metadata, are distributed. A multicast receiver does not accept any multicast content unless it has already received the associated metadata for that particular content.
Use the multicast fixed-carousel enable command to enable fixed-carousel sending. Carousel sending, which refers to the multicast retransmission of content, allows receivers who join a multicast group after a distribution has ended or who miss some content to receive the content without requiring a unicast transmission. By default, the SE uses intelligent carousel sending, which means that the retransmission is guided by feedback from the content receivers. Late-joining receivers or receivers that missed some content send a negative acknowledgement (NACK) to the sender for any files that were not received.
Fixed-carousel sending causes the content to be sent without depending on any receiver feedback. When this feature is enabled, the SE continuously retransmits the content after waiting for the time specified by the sender-delay option. You can use the fixed-carousel option when sending the content to receivers, which do not send NACKs to the sender. This configuration is allowed only for the primary sender and is not supported for an SE configured as a backup sender. Use the no multicast fixed-carousel enable command to disable fixed-carousel sending and to restore the default configuration.
Use the multicast max-concurrent-jobs command option to set the maximum number of objects that can be scheduled concurrently for multicast distribution. When networks are reliable or the size of files being multicast is small, we recommend that you set the maximum number of concurrent objects to 50. However, when networks are unreliable or the size of files being multicast is large, a smaller number of concurrent objects (for example, five) is recommended. The default maximum number of jobs is five.
The priority-weight option allows you to change the percentage of multicast bandwidth that is used for priority-based scheduling. By default, 50 percent of the bandwidth is allocated for a priority-based queue and 50 percent is allocated for a time-based, first in, first out (FIFO) queue. The time-based queue allows the system to process lower-priority traffic in a timely way even when it frequently receives large, high-priority requests.
Multicast Sender Delay
The multicast sender delay interval is the amount of time before each multicast transmission begins. A period of delay before the actual multicast transmission begins is required to allow the content metadata time to propagate to the receiver SE. The metadata contains the content file and configuration information that is necessary for the successful transmission of content files. The sender delay parameter is used to configure an extra delay before a multicast transmission can begin.
When configuring the sender delay interval, you must take into account that the content metadata must first propagate to the receiver before the multicast transmission can begin. During a multicast session, a receiver SE sends out periodic requests for files that it has not received. The sender retransmits files only as requested by the receiver SE. A multicast receiver will reject a multicast sender's advertisement of a file if the associated content metadata has not arrived. The sender delay option allows you to configure enough time for the metadata to propagate to the receiver, and avoid having the receiver reject the multicast sender's advertisement of a file.
To configure the sender delay interval, use the multicast sender-delay global configuration command on a sender SE. The sender-delay option controls the length of time that the multicast sender must wait for its associated metadata to propagate to the multicast receivers. The default delay time value is 960 seconds, the minimum is 480 seconds, and the maximum is 7200 seconds. You can configure the duration of the delay based on your expectation or best guess of the amount of time required for the metadata to be propagated. The system takes this user-configured sender delay value and delays the multicast transmission for a period defined by the sender delay.
Note
Examples
The following example shows how to enable the multicast client for the receiver on an SE:
ServiceEngine(config)# multicast client receiver enableRelated Commands
multicast (EXEC Configuration)
To generate multicast packets and test connectivity through multicast routers, use the multicast command in EXEC configuration mode.
multicast connectivity-test {cloud-id cloud_id [duration duration_num [message-length | mullticast-address multicast_addr | output-style {detail | error} | port port_num] | packet-count packet_num] | cloud-name name [duration duration [message-length | multicast-address multicast_addr | output-style {detail | error} | port port_num] | packet-count packet_num] | receive multicast_ip_addr interface interface_ip_addr | send multicast_ip_addr ttl interface interface_ip_addr | streamer receiver_ip_addr {receiver_ip_addr | multicast-address multicast_addr [duration duration [FEC-size size | max-transfer-rate rate | message-length | output-style {detail | error} | port port_num] | packet-count packet_num | time-to-live ttl]}}
Syntax Description
Command Defaults
Duration: 180 seconds
Packet Count: 100
FEC Size: 8
Maximum Transfer Rate: 128 kbps
Port: 7000
Time-to-live: 255
Message Length: 1024
Output Style: Detail Report
Command Modes
EXEC configuration mode.
Usage Guidelines
Note
You can use the multicast connectivity-test command to test multicast connectivity within the CDS network. The multicast connectivity-test command options run pgmrategen (the PGM packet generation application) and pgmratemon (the PGM packet receiver application) in the background to test multicast connectivity. These applications use the PGM protocol, which allows a receiver to report lost data and to request retransmission from the sender. With PGM, the sender multicasts sequenced data packets, and the receivers reply with unicast negative acknowledgments (NACKs) when data packets are missing from the expected sequence. Network elements forward the NACKs to the multicast sender and confirm each hop by multicasting a NACK confirmation on the interface on which the NACK was received.
Multicast Forward Error Correction
Forward error correction (FEC) is a type of data encoding that protects transmissions against errors, without requiring retransmission. The FEC number denotes the number of packets that will be encoded into one FEC transmission group. A higher FEC number means that the transmission group size is larger. The multicast may be more error-resistant, but there will also be more computational overhead on the multicast sender and receivers. No bandwidth overhead is related to FEC.
The FEC default value is 8. If the multicast sender device is a high-end SE model, you can set this number higher to improve multicast reliability when your network connectivity has a high uniform loss rate. However, we do not recommend that you set this number beyond 64, because it may place too much of a load on all the receiver SEs.
You can also set proactive FEC using the PGM configuration file (a text file accessible from the SE CLI in the /local1/multicast-expert-config/ directory). Proactive FEC is the number of extra packets that the multicast sender proactively sends out for every FEC number of data packets. The proactive FEC default value is 0. You can set the proactive FEC number higher for better multicast reliability. For example, you can set 2 proactive packets for every 16 FEC packets at the expense of 12.5 percent traffic overhead (2 divided by 16).
Proactive FEC is an additional reliability measure above and beyond that of normal FEC. Although normal FEC does not incur bandwidth overhead, proactive FEC does use bandwidth overhead. Proactive FEC primarily protects the multicast from uniform losses. For example, if the network has a uniform loss rate of 15 percent, then a proactive FEC of 2 extra packets for every 16 FEC packets (a 12.5 percent bandwidth overhead) cuts the effective loss rate down to 2.5 percent. Most network losses are not completely uniform. Still, during bursts, proactive FEC undercuts the effective burst loss rate. For example, if the burst loss rate is 20 percent while the average loss rate is 2 percent, with proactive FEC at 12.5 percent, the receiver SEs experience a burst loss rate of 7.5 percent and an average loss rate near 0 percent.
Testing Multicast Connectivity in CDS Networks
The multicast connectivity-test command options allow you to test multicast connectivity in the CDS networks. You can specify a maximum of 20 multicast receiver SEs using this option. Use the cloud-id or cloud-name options to test multicast connectivity to receiver SEs grouped into multicast clouds in the CDS network. There is no limit to the number of SEs you can have in a multicast cloud.
The cloud-id or cloud-name options initiate the following sequence of events:
1.
2.
3.
–
–
4.
If you interrupt the test by pressing Ctrl-C, the multicast sender sends a notification to all receiver SEs to stop listening and displays the information obtained so far.
5.
Note
6.
7.
Using the cloud-id or cloud-name Option
You can use the cloud-id or cloud-name options to test multicast connectivity in large networks where a number of SEs are grouped under multicast clouds.
Note
Use the multicast connectivity-test cloud-name command to test the multicast connectivity to the receiver SEs in the multicast cloud mcloud1.
The multicast address is not specified in this example. The Internet Streamer CDS software uses the advertisement IP address specified in the multicast cloud configuration as the multicast address. Because no values were specified for the options, the Internet Streamer CDS software uses the default values for all the optional parameters.
multicast connectivity-test send Command
To test the multicast connectivity to the receiver SEs listening to a specific multicast address, use the multicast connectivity-test send command. This command runs the pgmrategen application, which continuously sends PGM packets to the specified multicast IP address. After you enter this command, the system displays the percentage of packets that have been multicast and stops sending packets when the packets sent reaches 100 percent. Press Ctrl-C to interrupt the PGM application and return to the EXEC prompt.
To determine the number of network elements through which the packet can pass before reaching the receiver, specify the Time To Live (TTL), which can vary between 1 and 255.
multicast connectivity-test receive Command
To receive PGM packets, use the multicast connectivity-test receive command. Entering this command runs the pgmratemon application, which listens for the PGM multicast data transmitted from a PGM sender on the specified multicast IP address. When a packet is received, the pgrmratemon application lists the packet size and bandwidth.
To test the multicast connectivity between two SEs, use the same multicast IP address for both send and receive. The pgmratemon application terminates by itself after a default period of 3 minutes and returns to the EXEC prompt. You can press Ctrl-C to terminate the pgmratemon application and return to the EXEC prompt.
Examples
The following example shows the output of the multicast connectivity-test command for a multicast IP address of 239.1.1.1 and receiver SE IP addresses 10.43.27.2 and 10.43.27.4:
ServiceEngine# multicast connectivity-test 10.43.27.2 10.43.27.4 multicast-address 239.1.1.1Connecting to Receiver : 10.43.27.2Starting PGM Receiver on the SE 10.43.27.2Connecting to Receiver : 10.43.27.4Starting PGM Receiver on the SE 10.43.27.4Packet Generation thread has started. It will start sending packets after PGMReceivers have been startedTime Elapsed : 180 secondsPGM Sender has finished sending packets. Awaiting Receiver responseWill wait for 60 seconds...Configuration-------------Multicast Address : 239.1.1.1Port : 7000Max Rate to send PGM Packets : 128 kbpsTime to live for multicast packets : 255Forwarder Error Correction Size : 8Detailed Report----------------Receiver IP : 10.43.27.2Duration : 180 secondsNo of Packets received : 1134Packet Length : 1024 BytesMinimum BW : 5.714 KBpsMaximum BW : 7 KBpsAverage BW : 6.291 KBpsNAK Count : 0Receiver IP : 10.43.27.4Duration : 180 secondsNo of Packets received : 1134Packet Length : 1024 BytesMinimum BW : 5.691 KBpsMaximum BW : 7 KBpsAverage BW : 6.298 KBpsNAK Count : 0Summary Report--------------Total number of receivers : 2No: of receivers which received Packets : 2No: of receivers which did not receive Packets : 0No: of RPC calls failures : 0No: of Other Errors obtained from Receivers : 0The following example shows all the optional parameters and default values:
ServiceEngine# multicast connectivity-test 10.77.155.171 10.77.155.175 10.77.155.179 multicast-address 239.10.1.11 duration 180 FEC-size 8 max-transfer-rate 128 message-length 1024 output-style detail port 7000 time-to-live 255The following example shows the multicast connectivity-test cloud-name command with all the optional parameters and default values:
ServiceEngine# multicast connectivity-test cloud-name mcloud1 duration 180 message-length 1024 output-style detail port 7000The following example shows the output of the multicast connectivity-test cloud-name command for the multicast cloud Mcloud1. Because the multicast address was not specified, the Internet Streamer CDS software uses the advertisement IP address 239.1.1.1, specified in the multicast cloud configuration, as the multicast IP address. PGM packets are sent to the two receiver SEs (IP addresses 10.43.27.2 and 10.43.27.4) that make up the multicast cloud Mcloud1.
ServiceEngine# multicast connectivity-test cloud-name Mcloud1Connecting to Receiver : 10.43.27.2Starting PGM Receiver on the SE 10.43.27.2Connecting to Receiver : 10.43.27.4Starting PGM Receiver on the SE 10.43.27.4Packet Generation thread has started. It will start sending packets after PGMReceivers have been startedTime Elapsed : 180 secondsPGM Sender has finished sending packets. Awaiting Receiver responseWill wait for 60 seconds...Configuration-------------Multicast Address : 239.1.1.1Port : 7000Max Rate to send PGM Packets : 10000 kbpsTime to live for multicast packets : 255Forwarder Error Correction Size : 16Detailed Report----------------Receiver IP : 10.43.27.4Duration : 180 secondsNo of Packets received : 1139Packet Length : 1024 BytesMinimum BW : 4.903 KBpsMaximum BW : 7 KBpsAverage BW : 6.296 KBpsNAK Count : 0Receiver IP : 10.43.27.2Duration : 180 secondsNo of Packets received : 1139Packet Length : 1024 BytesMinimum BW : 5.641 KBpsMaximum BW : 7 KBpsAverage BW : 6.319 KBpsNAK Count : 0Summary Report--------------Total number of receivers : 2No: of receivers which received Packets : 2No: of receivers which did not receive Packets : 0No: of RPC calls failures : 0No: of Other Errors obtained from Receivers : 0The following example shows the output of the multicast connectivity-test send command for a multicast IP address of 239.1.1.1 and TTL of 255:
ServiceEngine# multicast connectivity-test send 239.1.1.1 255Starting pgmrategen ....pgmrategen is already running. Exiting previous instanceSending 1024 messages of 1024 bytes (1024 Kbytes)PGM rate is 1024 KbpsProgress: 99%Total time 159.924 seconds, 6.40302 KBps, 52.4536 KbpsThe following example shows the output of the multicast connectivity-test receive command:
ServiceEngine# multicast connectivity-test receive 239.1.1.1Starting pgmratemon ....This SE is not configured as Multicast receiver in any cloudConfiguring this SE as Satellite mode receiverPress ^C to abort or wait for 3 mins to exit....Multicasting PGM multicast data to SmartPGM receivers on multicast address 239.1Sending 1024 messages of 1024 bytes (1024 Kbytes)PGM rate is 1024 KbpsProgress: 99%Total time 8.39756 seconds, 121.94 KBps, 998.934 KbpsExiting....Stopping pgmratemonServiceEngine#Related Commands
multicast (Global configuration)
Configure multicast options.
show multicast
Displays whether or not the multicast sender and receiver are enabled.
neighbor
To configure BGP neighbors, use the neighbor BGP configuration command. To return to the default, use the no form of this command.
neighbor ip_address {ebgp-multihop TTL | password word | remote-as as_number | timers keepalive_timer hold_timer}
no ip_address {ebgp-multihop TTL | password word | remote-as as_number | timers keepalive_timer hold_timer}
Syntax Description
Command Defaults
•
•
•
Command Modes
BGP configuration (config-bgp) mode.
Usage Guidelines
Use the neighbor ebgp-multihop BGP configuration command to set the TTL value for the EBGP multihop scenarios.
Specifying a neighbor with an autonomous system number that matches the autonomous system number specified in the router bgp Global configuration command identifies the neighbor as internal to the local autonomous system. Otherwise, the neighbor is considered as external.
Use the neighbor remote-as command to add a neighbor to the BGP, or multi protocol BGP table, before setting the TTL value for the neighbor.
By default, neighbors that are defined using the neighbor remote-as command in router configuration mode exchange only unicast address prefixes.
Use the neighbor remote-as command before setting the TTL value.
In order for the proximity function to work, one of the following is required:
•
•
Note
Examples
The following example shows that a router at the address 192.168.86.3 is a neighbor in autonomous system number 23, and has a ebgp-multihop TTL value of 3:
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# neighbor 192.168.86.3 remote-as 23ServiceRouter(config-bgp)# neighbor 192.168.86.3 ebgp-multihop 3ServiceRouter(config-bgp)#The following example shows how to specify that a router at the address 192.168.86.3 is a neighbor in autonomous system number 23:
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# neighbor 192.168.86.3 remote-as 23ServiceRouter(config-bgp)#The following example shows that a router at the address 192.168.86.3 is a neighbor in autonomous system number 23, and its keepalive timer interval and hold timer interval are set to be 100 seconds and 200 seconds, respectively.
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# neighbor 192.168.86.3 remote-as 23ServiceRouter(config-bgp)# neighbor 192.168.86.3 timers 100 200ServiceRouter(config-bgp)#To confirm that timers are updated correctly, use the show ip bgp neighbors command. The following example output shows that the keepalive interval has been changed to 100 seconds and the hold timer has been changed to 200 seconds:
ServiceRouter> show ip bgp neighborsBGP neighbor is 192.168.86.3, remote AS 23, ibgp link, Peer index 1BGP version 4, remote router ID 192.168.86.3BGP state = Established, up for 1d05hPeer is directly attached, interface GigabitEthernet 2/0Last read 0.868226, hold time = 200, keepalive interval is 100 secondsLast written 00:00:09, keepalive timer expiry due 00:01:30Received 78444 messages, 0 notifications, 0 bytes in queueSent 1788 messages, 0 notifications, 0 bytes in queueConnections established 1; dropped 0Last reset by us never, due to process restartLast reset by peer never, due to process restartNeighbor capabilities:Dynamic capability: advertised (mp, refresh, gr)Dynamic capability (old): advertisedRoute refresh capability (new): advertised receivedRoute refresh capability (old): advertised receivedAddress family IPv4 Unicast: advertised receivedFor address family: IPv4 UnicastBGP table version 1, neighbor version 8107498518 accepted paths consume 613296 bytes of memory0 sent pathsLocal host: 192.168.86.47, Local port: 58920Foreign host: 192.168.86.3, Foreign port: 179fd = 35ServiceRouter>Related Commands
net
To configure an IS-IS network entity title (NET) for a Connectionless Network Service (CLNS) routing process, use the net IS-IS configuration command. To remove a NET, use the no form of this command.
net network_entity_title
no net network_entity_title
Syntax Description
network_entity_title
NET that specifies the area address and the system ID for a CLNS routing process. Either an address or a name may be specified.
Command Defaults
No NET is configured and the CLNS process does not start without a NET.
Command Modes
IS-IS configuration (config-isis) mode.
Usage Guidelines
Under most circumstances, one and only one NET must be configured.
A NET is a network service access point (NSAP) where the last byte is always zero. On a Proximity Engine running IS-IS, a NET can be 8 to 20 bytes. The last byte is always the n-selector and must be zero.
The six bytes directly in front of the n-selector are the system ID. The system ID length is a fixed size and cannot be changed. The system ID must be unique throughout each area (Level 1) and throughout the backbone (Level 2).
All bytes in front of the system ID are the area ID.
Even when IS-IS is used to perform IP routing only (that is, no CLNS routing enabled), a NET must still be configured to define the router system ID and area ID.
•
•
Examples
The following example shows how to use the net command to configure a router with system ID 0001.0c11.1111.00 and area ID 47.0004.004d.0001:
ServiceRouter(config)# router isisServiceRouter(config-isis)# net 47.0004.004d.0001.0001.0c11.1111.00ServiceRouter(config-isis)#Related Commands
netmon
To display the transmit and receive activity on an interface, use the netmon command in EXEC configuration mode.
netmon line
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The netmon utility displays the transmit and receive activity on each interface in megabits per second (Mbps), bytes per second (Bps), and packets per second (pps).
Examples
The following example shows how to display the netmon list of options:
ServiceEngine# netmon -hUsage: netmon [<loop-time-in-seconds>] [<iterations>](runs forever if iterations not specified)Related Commands
netstatr
To display the rate of change of netstat statistics, use the netstatr command in EXEC configuration mode.
netstatr line
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The netstatr utility displays the rate of change, per second, of netstat statistics for a given period of time. The average rate per second is displayed, regardless of the sample period. To view the list of options, enter netstatr -h.
Examples
The following example shows how to display the netstart list of options:
ServiceEngine# netstatr -hUsage: netstatr [-v] [<loop-time-in-seconds>] [<iterations>]-v verbose mode(default is 3 sec loop time, run forever)Related Commands
network area
To define the interfaces on which OSPF runs and the area ID for those interfaces, use the network area router configuration command. To disable OSPF routing for interfaces defined with the address wildcard-mask pair, use the no form of this command.
network ip_address wildcard_mask area area_id
no network ip_address wildcard_mask area area_id
Syntax Description
Note
Command Defaults
OSPF routing for interfaces is disabled by default.
Command Modes
OSPF configuration (config-ospf) mode.
Usage Guidelines
The ip_address and wildcard_mask arguments together allow you to define one or multiple interfaces to be associated with a specific OSPF area using a single command. Using the wildcard_mask argument allows you to define one or multiple interfaces to be associated with a specific OSPF area using a single command. If you intend to associate areas with IP subnets, you can specify a subnet address as the value of the area_id argument.
For OSPF to operate on the interface, the primary address of the interface must be covered by the network area command. If the network area command covers only the secondary address, it does not enable OSPF over that interface.
The Proximity Engine sequentially evaluates the ip_address wildcard_mask pair for each interface as follows:
1. The wildcard_mask is logically ORed with the interface IP address.
2. The wildcard_mask is logically ORed with the ip_address argument in the network command.
3. The software compares the two resulting values. If they match, OSPF is enabled on the associated interface and this interface is attached to the OSPF area specified.
There is no limit to the number of network area commands that can be used on the router.
Note
When a more specific OSPF network range is removed, interfaces belonging to that network range are retained and remain active if, and only if, a less specific network range exists.
For example, consider the following configuration:
router ospfnetwork 205.188.129.16 0.0.0.3 area 20network 205.188.129.40 0.0.0.3 area 20network 205.188.129.44 0.0.0.3 area 20network 205.188.129.96 0.0.0.3 area 20network 205.188.129.96 0.0.127.255 area 20Enter the following:
no network 205.188.129.40 0.0.0.3 area 20Interfaces falling into the network range 205.188.129.40/0.0.0.3 still remains active because the superset, 205.188.128.0/0.0.127.255, exists for area 20. A more specific network statement causes interfaces belonging to that range to be removed from a different area only if a less specific network statement (superset) exists.
Consider a configuration such as the following:
router ospf 1network 205.188.128.0 0.0.127.255 area 20If the following network statement is entered:
network 205.188.129.96 0.0.0.3 area 40the interfaces belonging to range 205.188.129.96/0.0.0.3 are removed from area 20 and moved to area 40. Network statements with identical ranges but different area IDs are considered as area changes. For example, the following network statements cause interfaces belonging to network range 205.188.129.40/0.0.0.3 to move from area 20 to area 40:
network 205.188.129.40 0.0.0.3 area 20 network 205.188.129.40 0.0.0.3 area 40Examples
The following example shows how to initialize OSPF routing process. Area 0 enables OSPF.
ServiceRouter(config)# router ospfServiceRouter(config-ospf)# network 192.168.78.0 0.0.0.255 area 0ServiceRouter(config-ospf)#Related Commands
no (Global configuration)
To undo a command in Global configuration mode or set its defaults, use the no form of a command in Global configuration mode.
no command
Note
Syntax Description
Command Defaults
None
Command Modes
Global configuration (config) mode.
Usage Guidelines
Valid values for command are as follows:
aaa
Configures AAA1 .
access-lists
Configures access control list entries.
acquirer
Configures acquisition parameters.
asset
Configures the asset tag name string.
authentication
Configures the authentication.
bandwidth
Configures bandwidth controls.
banner
Defines a login banner.
bitrate
Configures the bit rate.
cdsm
Configures the CDSM settings.
clock
Configures the time-of-day clock.
cms
Configures the CMS2 .
device
Configures the device mode.
direct-server-return
Configures direct-server-return.
disk
Configures disk-related settings.
dns
Configures the SE DNS cache.
exec-timeout
Configures the EXEC timeout.
external-ip
Configures up to eight external (NAT) IP addresses.
ftp
Configures FTP caching-related parameters.
help
Configures the assistance for the command-line interface.
hostname
Configures the system's network name.
http
Configures HTTP-related parameters.
icap
Configures the ICAP feature for the HTTP protocol.
interface
Configures a Gigabit Ethernet interface.
ip
Configures IP parameters.
ip access-list
Configures IP access lists.
kernel
Enables access to the kernel debugger.
ldap
Configures LDAP3 parameters.
logging
Configures the syslog4 .
network-filesystem
Configures the network file system server and client.
ntp
Configures the NTP5 .
offline-operation
Configures the offline service operation.
pace
Configures the Movie Streamer 7H90C0CHand WMT pacing bandwidth and bit rate.
port-channel
Configures port channel global options.
primary-interface
Configures a primary interface.
radius-server
Configures RADIUS server authentication.
rtsp
Configures RTSP6 -related parameters.
rule
Configures the Rules Template.
snmp-server
Configures the SNMP server.
sshd
Configures the SSH7 service.
tcp
Configures global TCP parameters.
telnet enable
Configures Telnet services.
transaction-logs
Configures the transaction logging.
username
Establishes username authentication.
wmt
Configures WMT8 parameters.
1 AAA = authentication, authorization, and accounting
2 CMS = Centralized Management System
3 LDAP = Lightweight Directory Access Protocol
4 syslog = system logging
5 NTP = Network Time Protocol
6 RTSP = Real-time Streaming Protocol
7 SSH = Secure Shell
8 WMT = Windows Media Technologies7H90C0CH
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 command in interface configuration mode or set its defaults, use the no command in interface configuration mode.
no interface {GigabitEthernet slot/port | PortChannel {1 | 2 | 3 | 4}[ ip | address [ip-address | netmask | secondary ] ] | Standby group_num}
Syntax Description
Command Defaults
None
Command Modes
Interface configuration (config-if) mode.
Related Commands
ntp
To configure the Network Time Protocol (NTP) server and to allow the system clock to be synchronized by a time server, use the ntp command in Global configuration mode. 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
Command Defaults
None
Command Modes
Global configuration (config) mode.
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 command in EXEC configuration mode. 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 shows how to configure the IP address of the time server providing the clock synchronization:
ServiceEngine(config)# ntp 172.16.22.44The following example shows how to reset the time server providing the clock synchronization:
ServiceEngine(config)# no ntp 172.16.22.44Related Commands
clock
Sets or clears clock functions or updates the calendar.
show clock
Displays the system clock.
show ntp status
Displays the Network Time Protocol parameters.
ntpdate
To set the software clock (time and date) using a Network Time Protocol (NTP) server, use the ntpdate command in EXEC configuration mode.
ntpdate {hostname | ip_address}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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 shows how to set the software clock of the SE using an NTP server:
ServiceEngine# ntpdate 10.11.23.40Related Commands
ping
To send echo packets for diagnosing basic network connectivity on networks, use the ping command in EXEC configuration mode.
On the CDSM and SE:
ping {hostname | ip_address}
On the SR:
ping {hostname | ip_address | srp {hostname | ip_address}}
Syntax Description
hostname
Hostname of system to ping.
ip_address
IP address of system to ping.
srp
Pings the Service Routing Protocol.
Command Defaults
None
Command Modes
EXEC configuration mode.
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#ping srp
To ping the Service Routing Protocol ring, use the ping command in EXEC configuration mode.
ping srp
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
In an ipv4 or ipv6 environment, the ping command uses the ipv4 or ipv6 address. The ping srp command uses The DHT key (64 bits hex-id).
In the example below, the node that owns the DHT key (node SR-205-5) responds to this ping. The TTL is 64, and the response time is 0.330585 ms.
Examples
The following example shows how to test the basic network connectivity with a host:
ServiceRouter# ping srp6aab6568d794a77bc20633b0cb3aef14d906e4aef00a3fa2a93973524337e40cPing response from SR-205-5:9000, ttl=64, time=0.330585 msid=6aab6568d794a77bc20633b0cb3aef14d906e4aef00a3fa2a93973524337e40cPing response from SR-205-5:9000, ttl=64, time=0.282069 msid=6aab6568d794a77bc20633b0cb3aef14d906e4aef00a3fa2a93973524337e40cPing response from SR-205-5:9000, ttl=64, time=0.278821 msid=6aab6568d794a77bc20633b0cb3aef14d906e4aef00a3fa2a93973524337e40cPing response from SR-205-5:9000, ttl=64, time=0.279144 msid=6aab6568d794a77bc20633b0cb3aef14d906e4aef00a3fa2a93973524337e40cPing response from SR-205-5:9000, ttl=64, time=0.283236 msid=6aab6568d794a77bc20633b0cb3aef14d906e4aef00a3fa2a93973524337e40cServiceRouter#Related Commands
ping6
To ping the IPv6 address, use the ping6 command in EXEC configuration mode.
ping6 line ip_address
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following example shows how to ping the IPv6 address:
ServiceEngine# ping6 fec0::100/64Related Commands
port-channel
To configure the port channel load balancing, use the port-channel command in Global configuration mode. To disable load balancing, use the no form of this command.
port-channel load-balance {dst-ip | dst-mac | dst-port | round-robin | src-dst-mac | src-dst-port | src-port}
no port-channel load-balance
Syntax Description
Command Defaults
Round-robin is the default load balancing method.
Command Modes
Global configuration (config) mode.
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 keyword 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.
The other balancing options give you the flexibility to choose specific interfaces (by IP address, MAC address, port) when sending an Ethernet frame. The source and destination options, while calculating the outgoing interface, take into account both the source and destination (MAC address or port).
Because the Internet Streamer CDS software normally starts IP packets or Ethernet frames, it does not support hashing based on the source IP address and source MAC address. The round-robin keyword is the default load balancing algorithm to evenly distribute traffic among several identical network interfaces.
To remove a port channel, use the no port-channel interface PortChannel command.
Note
Note
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
primary-interface
To configure the primary interface for the CDS network, use the primary-interface command in Global configuration mode. 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
Command 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.
Note
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 (config) mode.
Usage Guidelines
The primary-interface command in Global configuration mode 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 Gigabit Ethernet 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 Gigabit Ethernet slot 2 port 0 as the primary interface on an SE:
ServiceEngine(config)# primary-interface GigabitEthernet 2/0proximity algorithm bgp
To enable a Border Gateway Protocol (BGP) proximity algorithm option for the Proximity Engine, use the proximity algorithm bgp command in Global configuration mode. To disable a BGP proximity algorithm option, use the no form of the command.
proximity algorithm bgp {best-path | location-community [strict] | redirect}
no proximity algorithm bgp {best-path | location-community [strict] | redirect}
Syntax Description
Command Defaults
By default, the BGP algorithms are turned off.
Command Modes
Global configuration (config) mode.
Usage Guidelines
When BGP is configured as the routing protocol, the proximity algorithm bgp command enables a BGP proximity option for the Proximity Engine. The Proximity algorithm bgp commands are not effective unless BGP is configured first.
Best-Path
When the BGP routing protocol is configured the Proximity Engine learns routes from other AS, and therefore can rank proximity target addressees (PTAs) that originate in an external AS using not only the basic BGP proximity (which ranks the PTAs based on their next-hop), but also based on the AS path length of the PTAs. This capability is enabled by the proximity algorithm bgp best-path command. A PTA that has a longer AS path length is less preferred. It should be noted that the Proximity Engines takes into account the AS path length of the PTAs only if the proximity source address (PSA) is originated in the same AS as the Proximity Engine, since the AS path length learnt by the Proximity Engine is with reference to its own AS. If the PSA originates in an external AS, it is recommended that the proximity algorithm bgp redirect be enabled to redirect the request to a Proximity Engine in the same AS as the PSA if such a Proximity Engine exists.
Location Community
When the proximity algorithm bgp location-community command is enabled, additional location information is included in the proximity calculation to influence application-level traffic optimization in the network. Many service providers are already using BGP community values to identify prefixes originated from a given POP. Taking advantage of the community information can greatly improve the scalability and flexibility of the proximity calculation algorithm.
BGP community-based proximity is used when community-based proximity option is enabled and the PSA has a BGP community string that is configured in the location community command. PTAs that have the same BGP community string as the PSA are ranked as more preferred than PTAs that do not have the same BGP community string as the PSA. For the remaining PTAs that have different community strings, they are ranked by either IGP or BGP proximity.
Community-based proximity requires the use of the location community command to configure the Proximity Engine community values. Each Proximity Engine must be configured with the community numbers that are used within the network to locate the prefix origination point.
When community values are configured, the Proximity Engine creates and maintains a sorted table of communities within BGP. Currently, location community configurations must be manually configured on each Proximity Engine.
Redirect
If the PSA, where the proximity request is initiated, is learned from another AS, the current Proximity Engine does not have the best knowledge to handle the proximity request. If the proximity redirect option is enabled, the Proximity Engine sends back a Redirect response to the Service Router. The Redirect response contains the list of Proximity Engines that reside in the same AS as the PSA. The Service Router then sends the proximity request to one of these Proximity Engines.
Configuring Proximity Algorithm BGP
Perform the following steps to configure Proximity Algorithm BGP:
Step 1
ServiceRouter(config)# proximity engine enableServiceRouter(config)# proximity algorithm bgp best-pathStep 2
ServiceRouter(config)# router bgp 1ServiceRouter(config)# neighbor 26.0.0.6 remote-as 1Step 3
Result Analysis
When PSA is 3.1.5.0 and PTA is 33.1.5.0, the returned proximity cost is 2164260884.
ServiceRouter# show ip rib route3.1.5.0/24, 1 ucast next-hops, 0 mcast next-hops, attached*via 3.1.5.3, GigabitEthernet 1/0, [0/0], 00:01:59, direct26.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops, attached*via 26.0.0.2, GigabitEthernet 2/0, [0/0], 00:01:59, direct33.1.5.0/24, 1 ucast next-hops, 0 mcast next-hops*via 26.0.0.6, GigabitEthernet 2/0, [200/0], 00:00:29, bgp-1, internal, tag 2extended route information: AS Hops 1, BGP PxEer AS 162.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops*via 26.0.0.6, GigabitEthernet 2/0, [115/20], 00:01:27, isis-p1, L1The AS Path length can be calculated from the show ip route command:
AS Path length for PTA 33.1.5.0 - 1
The 31st community bit set to 1 since no location community match, AS Path length is 1(set the 24th bit to 1), the IGP cost is 20.
2147483648+ 16777216 + 20 = 2164260884
The proximity calculation rendered using the following formula:
rating(PSA,PTA)= 2^31Cc comm_match(PSA,PTA) +2^24CBPAS_path_len(PTA)+ IGP_rating(PSA,PTA)
•
•
•
•
Examples
Proximity Algorithm Redirect
The following example shows how to use the proximity redirect option:
ServiceRouter(config)# proximity algorithm bgp redirectFirst, each Proximity Engine must form a DHT ring.
ProximityEngine1(config)# router srpProximityEngine1(config-srp)# domain 100ProximityEngine2(config)# router srpProximityEngine2(config-srp)# domain 100ProximityEngine1(config-srp)# bootstrap 3.4.0.7Configure both the Proximity Servers on the Service Router and enable proximity-based-routing:
ServiceRouter(config)# service-router proximity-based-routing proximity-server 3.4.0.7ServiceRouter(config)# service-router proximity-based-routing proximity-server 3.1.14.17ServiceRouter(config)# service-router proximity-based-routing enableNext, enable BGP on both the Proximity Engines such that both are in different AS:
ProximityEngine1(config)# router bgp 1ProximityEngine1(config-bgp)# neighbor 3.4.0.12 remote-as 1ProximityEngine2(config)# router bgp 2ProximityEngine2(config-bgp)# neighbor 3.1.14.12 remote-as 2For Proximity Redirect to work efficiently, it is recommended that there are at least two Proximity Servers, one each in a different autonomous system.
In the above example each Proximity Engine is connected with routers and routers advertise the routes to the respective Proximity Engines and the neighbor IP addresses are the corresponding neighbor router's directly connected interfaces:
ProximityEngine1# sh ip bgp allBGP routing table information for address family IPv4 UnicastBGP table version is 5, local router ID is 3.4.0.7Status: s-suppressed, x-deleted, S-stale, d-dampened, h-history, *-valid, >-bestPath type: i-internal, e-external, c-confed, l-local, a-aggregate, r-redistOrigin codes: I - IGP, E - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*>i3.1.14.0/24 3.4.0.12 0 100 0 2 I*>i3.4.0.0/16 3.4.0.12 0 100 0 IBGP routing table information for address family IPv4 MulticastProximityEngine2# sh ip bgp allBGP routing table information for address family IPv4 UnicastBGP table version is 5, local router ID is 3.4.0.8Status: s-suppressed, x-deleted, S-stale, d-dampened, h-history, *-valid, >-bestPath type: i-internal, e-external, c-confed, l-local, a-aggregate, r-redistOrigin codes: I - IGP, E - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*>i3.1.14.0/24 3.1.14.12 0 100 0 I*>i3.4.0.0/16 3.1.14.12 0 100 0 1 IBGP routing table information for address family IPv4 MulticastNext, it needs to be checked if the DHT Ring is formed appropriately:
ServiceRouter# show srp neighborCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - Intransitive, R - Replicate Set, D - delay, ND - New DelayH - hold time, U - up timeNumber of neighbors in the database: 1RPL c152b683f000c6be3ff82214e4d8084d52a44dee85b29d67c49e60fbaf3e4737via U6-CDE205-2 [3.1.14.17] 9000, D=0.223891 ms, ND=0.230440 msH=00:00:07, U=00:00:15ProximityEngine2# show srp neighborCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - Intransitive, R - Replicate Set, D - delay, ND - New DelayH - hold time, U - up timeNumber of neighbors in the database: 1RPL 97d35b9f3cb020799d9cbfec2adcca50e9644f2613f041648734459d29f88a0dvia U6-CDE205-1 [3.4.0.7] 9000, D=0.229732 ms, ND=0.223568 msH=00:00:08, U=00:00:22Where 3.4.0.7 is ProximityEngine1's interface and 3.1.14.17 is ProximityEngine2's interface and is stored in each other tables.
When a request arrives from the client machine, whose client IP belongs to the 3.4.0.0/16 network (which happens to be from AS-1), say for example, 3.4.0.10, the SR looks up in the configured Proximity Servers and selects the Proximity Server with the lowest IP address, which in this case happens to be 3.1.14.17.
The SR would send the SOAP request with the PSA 3.4.0.10 to ProximityEngine2 (3.1.14.17).
ProximityEngine2, would lookup the URIB table to find out if there is another Proximity Engine from the same AS. Since, in this case, there is ProximityEngine1 in AS-1 from where the request has emanated, it returns a Redirect message with ProximityEngine1's IP address as the request end-point.
The SR redirects the SOAP request to the ProximityEngine1.
ProximityEngine1 would look up its URIB table and return the cost for the available PTAs.
The Service Router, upon receiving the cost from the ProximityEngine1, would choose the PTA with lowest cost and give the SE redirection to the client.
The client would now contact the SE and play the content.
Community-Based Proximity Algorithm Example
The following example shows how to use the proximity algorithm bgp command to enable the community-based proximity algorithm:
ServiceRouter(config)# proximity algorithm bgp location-communityServiceRouter(config)# exitServiceRouter# show ip proximity algorithmProximity algorithm: bgp communityThe following example shows how to configure community values. In this example, the first location community command configures the community value 100:10 and the second command configures community values from 100:100 to 100:200:
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# location community 100:10ServiceRouter(config-bgp)# location community 100:100-100:200The following example shows how to enable the proximity redirect option:
ServiceRouter(config)# proximity algorithm bgp redirectFirst, each Proximity Engine must form a DHT ring:
ServiceRouter(config)# router srpServiceRouter(config-srp)# domain 100ServiceRouter(config-srp)# bootstrap 192.168.10.1Each Proximity Engine must advertise its interface address to the BGP cloud by configuring IGP for OSPF and IS-IS or configuring BGP with the neighbor.
The following example is for OSPF:
ServiceRouter(config)# router ospfServiceRouter(config-ospf)# network 192.168.10.0 255.255.255.0 area 0The following example is for configuring BGP:
ServiceRouter(config)# router bgpServiceRouter(config-bgp)# neighbor 192.168.82.1 remote-as 23The following examples shows how to configure the BGP AS path length-based proximity. This example is for the same AS configuration:
ServiceRouter(config)# proximity algorithm bgp best-pathServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)# neighbor 192.168.82.1 remote-as 23The following example is for a different AS configuration:
ServiceRouter(config)# proximity algorithm bgp best-pathServiceRouter(config)# router bgp 10ServiceRouter(config-bgp)# neighbor 192.168.82.1 remote-as 23Proximity Algorith BGP Best-Path Example
The following example shows how to turn on the BGP Best-Path algorithm:
ProximityEngine(config)# proximity algorithm bgp best-pathProximityEngine# show ip bgp 3.1.14.0BGP routing table entry for 3.1.14.0/24, version 4Paths: (1 available, best #1)Flags: on xmit-list, is in urib, is best urib routePath type: internal, path is valid, is best pathAS-Path: 2 , path sourced external to AS3.4.0.12 (metric 0) from 3.4.0.12 (3.4.0.12)Origin IGP, MED 0, localpref 100, weight 0Community: 1:1Not advertised to any peerThe following is a sample of the service-router logs with respect to the cost returned by the Proximity Engine:
02/08/2010 07:34:42.290(Local)(5792)TRCE:SRNetProxClient.cpp:86->TargetHostname => U6-WAE612-2IpAddress => 3.4.0.14Rating => 214748364802/08/2010 07:34:42.290(Local)(5792)TRCE:SRNetProxClient.cpp:86->TargetHostname => U6-WAE612-1IpAddress => 3.1.14.7Rating => 2164260864In the previous example, since the PTA 3.1.14.7 has a higher cost, the PTA 3.4.0.17 gets a higher preference owing to the lower cost.
The following example shows how to verify proper connectivity between the two Proximity Engines:
ProximityEngine1# show srp neighborCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - Intransitive, R - Replicate Set, D - delay, ND - New DelayH - hold time, U - up timeNumber of neighbors in the database: 1RPL c152b683f000c6be3ff82214e4d8084d52a44dee85b29d67c49e60fbaf3e4737via U6-CDE205-2 [3.1.14.17] 9000, D=0.395056 ms, ND=0.378471 msH=00:00:09, U=00:38:37ProximityEngine1# show srp databasec9bc3e170457a6a08d8a218a15a00d8feb73e4295d06f7e014b6f66fee01c9e4: 793Enter the same commands to check the SRP connection on the other Proximity engine:
ServiceRouter# show srp neighborCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - Intransitive, R - Replicate Set, D - delay, ND - New DelayH - hold time, U - up timeNumber of neighbors in the database: 1RPL 97d35b9f3cb020799d9cbfec2adcca50e9644f2613f041648734459d29f88a0dvia U6-CDE205-1 [3.4.0.7] 9000, D=0.495889 ms, ND=0.470399 msH=00:00:07, U=00:40:57ProximityEngine2# show srp databasec9bc3e170457a6a08d8a218a15a00d8feb73e4295d06f7e014b6f66fee01c9e4: 793Related Commands
show ip proximity algorithm
Displays the proximity algorithm options currently in use by this Proximity Engine.
proximity engine enable
To enable the Proximity Engine, use the proximity engine enable command in Global configuration mode. To disable the Proximity Engine, use the no form of this command.
proximity engine enable
no proximity engine enable
Syntax Description
This command has no arguments or keywords.
Command Modes
Global configuration (config) mode.
Usage Guidelines
The Proximity Engine is a device mode which needs to be enabled on the Service Router in order to enable dynamic routing protocols OSPF/IS-IS/BGP. You can turn on the Proximity Engine functionality using the proximity engine enable command. Only after enabling the Proximity Engine, all the routing functionality is enabled and related commands are unlocked. Once the Proximity Engine is enabled, you can turn on either OSPF or IS-IS for IGP and/or BGP. But in the Proximity Engine device, we do not make use of the OSPF process-id, which we generally do on the router.
When disabling the Proximity Engine after issuing the no proximity engine enable command, you are asked to confirm this action because all Proximity Engine configurations are lost when you enter this command.
Examples
The following example shows how to enable the Proximity Engine:
ServiceRouter# configure terminalServiceRouter(config)# proximity engine enableThe following example shows how to disable the Proximity Engine:
ServiceRouter# configure terminalServiceRouter(config)# no proximity engine enableAll Proximity Engine configuration will be lost! Proceed? [ no ] yesServiceRouter(config)#The following example shows how to enable OSPF:
ServiceRouter# configServiceRouter (config)# proximity engine enableStarting Proximity Engine ....Proximity Engine Started.ServiceRouter (config)# router ospfServiceRouter (config-ospf)# network 15.0.0.0 ?A.B.C.D IP wildcard maskServiceRouter (config-ospf)# network 15.0.0.0 0.255.255.255 ?area Configure area propertiesServiceRouter (config-ospf)# network 15.0.0.0 0.255.255.255 area 0 ServiceRouter# ServiceRouter (config-ospf)#
Note
Enter the following commands on the router:
Router (config)# router ospf 1Router (config-ospf)# network 15.0.0.0 0.255.255.255 area 0Router (config-ospf)#<Turned on OSPF debugging on Router>*Jun 29 01:14:08.642: OSPF: Interface GigabitEthernet0/0 going Up *Jun 29 01:14:09.142: OSPF: Build router LSA for area 0, router ID 2.2.2.2, seq 0x80000001, process 1 *Jun 29... Output omitted<2.2.2.2 is the Router-id of the Router>Verify adjacency on the Proximity Engine by entering the following commands:
ServiceRouter# show ip ospf routeOSPF Process ID p1 context default, Routing Table(D) denotes route is directly attached (R) denotes route is inRIB15.0.0.0/8 (intra)(D) area 0via 15.0.0.1/GigabitEthernet 2/0*, cost 65535, adv router 3.1.5.2ServiceRouter# show ip ospf databaseOSPF Router with ID (3.1.5.2) (Process ID p1 context default)Router Link States (Area 0)Link ID ADV Router Age Seq# Checksum LinkCount2.2.2.2 2.2.2.2 140 0x80000002 0xb04d 13.1.5.2 3.1.5.2 140 0x80000002 0x100d 1Network Link States (Area 0)Link ID ADV Router Age Seq# Checksum15.0.0.1 3.1.5.2 140 0x80000001 0x2408The following example shows how to enable BGP:
ServiceRouter# configServiceRouter(config)# proximity algorithm bgp location-community!ServiceRouter(config)# router bgp 1ServiceRouter(config-bgp)# neighbor 5.45.1.101 remote-as 1 <-- configures a BGP peer in Autonomous System (AS) 1. This peer advertises BGP routes to the PxE.ServiceRouter(config-bgp)# location community 1:1 <-- configures 1:1 as a location-community used by BGP location-community proximity algorithm.ServiceRouter(config-bgp)# exitThe following example shows how to enable IS-IS:
ServiceRouter# configServiceRouter(config)# router isisServiceRouter(config-isis)# net 49.0000.0000.0205.0002.00 <-- Configures the Network Entity Title (NET).ServiceRouter(config-isis)# interface GigabitEthernet 1/0 <-- PxE interface actively running IS-IS.ServiceRouter(config-isis)# ip router isisServiceRouter(config-isis)# exitServiceRouter(config-isis)# interface GigabitEthernet 2/0 <-- PxE interface actively running IS-IS.ServiceRouter(config-isis)# ip router isisServiceRouter(config-isis)# exitThe following example shows how to enable SRP:
ServiceRouter# configServiceRouter(config)# router srpServiceRouter(config-srp)# bootstrap 172.20.168.89 <-- A boot-strap-node is an existing member of the DHT ring.ServiceRouter(config-srp)# domain 1 <-- All SRP nodes have the same domain number to be in a DHT ringServiceRouter(config-srp)# exitRelated Commands
service-router proximity-based-routing
Configures proximity-based routing on the Service Router.
pwd
To view the present working directory, use the pwd command in EXEC configuration mode.
pwd
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
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
radius-server
To configure RADIUS authentication parameters, use the radius-server command in Global configuration mode. To disable RADIUS authentication parameters, use the no form of this command.
radius-server {enable | host {hostname | host_ipaddr} [auth-port port] | key keyword | redirect {enable | message reply location url} | retransmit retries | timeout seconds}
no radius-server {enable | host {hostname | host_ipaddr} | key | redirect {enable | message reply location url} | retransmit | timeout}
Syntax Description
Command Defaults
auth-port port: UDP port 1645
retransmit retries: 2
timeout seconds: 5
Command Modes
Global configuration (config) mode.
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 sent. If you do not configure a RADIUS key, packets are not encrypted. The key itself is never sent 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 keyword 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 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 on an SE, enable RADIUS authentication for normal login mode by entering the authentication login radius command in Global configuration mode as follows:
ServiceEngine(config)#authentication login radius enable [primary] [secondary]Use the authentication configuration radius command in Global configuration mode 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 command in Global configuration mode.
Examples
The following example shows how to enable the RADIUS client, specify a RADIUS server, specify the RADIUS key, accept 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
rcp
To enable the Remote Copy Program (RCP), use the rcp command in Global configuration mode. To disable RCP, use the no form of this command.
rcp enable
no rcp enable
Syntax Description
Command Defaults
None
Command Modes
Global configuration (config) mode.
Examples
The following example shows how to enable RCP:
ServiceEngine(config)#rcp enableRelated Commands
reload
To halt and perform a cold restart on the SE, use the reload command in EXEC configuration mode.
reload [force]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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 shows how to reload 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
Saves any file system contents to disk from memory before a restart.
write
Saves startup configurations.
write erase
Erases the startup configuration from NVRAM.
rename
To rename a file on the SE, use the rename command in EXEC configuration mode.
rename old_filename new_filename
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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
restore
To restore the device to its manufactured default status, removing the user data from the disk and flash memory, use the restore command in EXEC configuration mode. This command erases all existing content on the device.
restore factory-default [preserve basic-config]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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 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 disks command after the restore command verifies that the restore command has removed data from the partitioned file systems (sysfs and cdnfs):
ServiceEngine# show disksSYSFS 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 command continues 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
rmdir
To delete a directory, use the rmdir command in EXEC configuration mode.
rmdir directory
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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 shows how to remove the oldfiles directory under /local1:
ServiceEngine# rmdir /local1/oldfilesRelated Commands
router bgp
To configure a BGP routing process, use the router bgp command in Global configuration mode. To remove a BGP routing process, use the no form of this command.
router bgp as_number
no router bgp as_number
Syntax Description
as_number
Number of an Autonomous System (AS) that identifies the router to other BGP routers, and tags the routing information that is passed along.
Command Defaults
No BGP routing process is configured.
Command Modes
Global configuration (config) mode.
Usage Guidelines
This command is used to set up a distributed routing core that automatically guarantees the loop-free exchange of routing information between autonomous systems.
Enable the Proximity Engine by entering the proximity engine enable command before executing this command.
For the proximity function to work, one of the following is required:
•
•
Note
Examples
The following example shows how to configure a BGP process for autonomous system 23:
ServiceRouter(config)# router bgp 23ServiceRouter(config-bgp)#Related Commands
router isis
To enable the IS-IS routing protocol and to specify an IS-IS process, use the router isis command in Global configuration mode. To disable IS-IS routing, use the no form of this command.
router isis
no router isis
Syntax Description
This command has no arguments or keywords.
Command Defaults
IS-IS routing is disabled.
Command Modes
Global configuration (config) mode.
Usage Guidelines
This command is used to enable routing for an area. An appropriate network entity title (NET) must be configured to specify the area address and the system ID of the router. Routing must be enabled on one or more interfaces before adjacencies can be established and dynamic routing is made possible.
Enable the Proximity Engine by entering the proximity engine enable command before executing this command.
Note
%Cannot configure both IS-IS and OSPF together. Please remove 'router ospf' first. (Error number: 1137)
If you want to configure IS-IS and you already have OSPF running, you must enter the no router ospf command first before entering the router isis command.
Examples
The following example shows how to configure IS-IS for IP routing. In this example, system ID is set to 0001.0c11.1111.00 and area is set to ID 47.0004.004d.0001. IS-IS is configured to form adjacencies on Ethernet interface 0 and serial interface 0. The IP prefix assigned to Ethernet interface 0 is advertised to other IS-IS routers.
ServiceRouter# show node-typePROXIMITY_ENGINEServiceRouter# config tServiceRouter(config)# router isisServiceRouter(config-isis)# net 47.0004.004d.0001.0001.0c11.1111.00ServiceRouter(config-isis)# interface GigabitEthernet 1/0ServiceRouter(config-isis-if)# ip router isisServiceRouter(config-isis-if)# endServiceRouter#Related Commands
router ospf
To enable the Open Shortest Path First (OSPF) routing process, use the router ospf command in Global configuration mode. To terminate the OSPF process, use the no form of this command.
router ospf
no router ospf
Syntax Description
This command has no arguments or keywords.
Command Defaults
This command is disabled by default.
Command Modes
Global configuration (config) mode.
Usage Guidelines
For Proximity Engine, the fixed process ID "p1" is used internally. This allows only one instance of the OSPF process, but it supports multiple areas. Routing must be enabled on one or more interfaces before adjacencies can be established and before dynamic routing is possible.
Enable the Proximity Engine by entering the proximity engine enable command before executing this command.
Note
%Cannot configure both IS-IS and OSPF together. Please remove 'router ospf' first. (Error number: 1137)
If you want to configure OSPF and you already have IS-IS running, you must enter the no router isis command first before entering the router ospf command.
Examples
The following example shows how to configure an OSPF routing process:
ServiceRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.ServiceRouter(config)# router ospfServiceRouter(config-ospf)# endServiceRouter#Related Commands
router srp
To enter SRP configuration mode, use the router srp command in Global configuration mode. To negate the SRP daemon and remove all SRP running configuration, use the no form of this command.
router srp
no router srp
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
Global configuration (config) mode.
Usage Guidelines
This command is used to enter SRP configuration mode, where a system administrator can configure different parameters of the SRP.
Enable the Proximity Engine by entering the proximity engine enable command before executing this command.
For SRP to run properly, it is necessary to configure the NTP server on the SR. Configure NTP as follows:
ServiceRouter(config)# ntp server 171.68.10.150ServiceRouter(config)# endServiceRouter# sh ntp status ntp enabled server list: 2.8.1.2 171.68.10.150remote refid st t when poll reach delay offset jitter==============================================================================2.8.1.2 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00*ntp-sj1.cisco.c ntp02-syd.cisco 2 u 63m 137m 177 1.625 -1.806 0.881ServiceRouter#Examples
The following example shows the use of router srp:
ServiceRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.ServiceRouter(config)# router srpServiceRouter(config-srp)#Related Commands
bootstrap-node
Configures a bootstrap node IP address.
domain
Sets the domain ID for an SRP.
flooding
Configures the flooding threshold.
rtsp
To configure the Real-Time Streaming Protocol (RTSP)-related parameters, use the rtsp command in Global configuration mode. 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
Command Defaults
max-initial-setup-delay time_delay: 10
max-request-rate num: 40 requests
Command Modes
Global configuration (config) mode.
Usage Guidelines
Real-Time Streaming Protocol (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 3-11 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 3-11 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
rule
To set the rules by which the SE filters HTTP, HTTPS, and RTSP traffic, use the rule command in Global configuration mode. To disable individual options, use the no form of this command.
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 key_id {key-id-number key_id_number} {pattern-list patterm_list_num} [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}] | enable | 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}}}
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 key_id {key-id-number key_id_number} {pattern-list patterm_list_num} [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}] | enable | 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
Command Defaults
The default is rule processing disabled.
The group-type pattern is OR by default.
Command Modes
Global configuration (config) mode.
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:
•
•
•
•
•
•
•
–
–
–
Note
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 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 the block, rewrite, and allow rule actions for RTSP requests, but does not support the redirect rule actions for RTSP requests.
WMT supports all the rule action types—allow, block, no-cache, redirect, refresh, replace, rewrite, validate-url-signature, and generate-url-signature. RTMP and Movie Streamer only support allow, block, and validate-url-signature.
Note
This command removes the trailing "protocol all" when it displays in the running-config. All service rule-related commands have this functionality. Also, the rule action allow pattern-list 1 ? command does not have a help message indicating "protocol all" is the default value if it is omitted.
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 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 is taken for all the traffic that goes through the SE.
Execution Order of Rule Actions
The order in which the rule actions are executed is different between the Web Engine and the other protocol engines (Windows Media Streaming, Movie Streamer, and Flash Media Streaming).
Note
Note
Note
Web Engine Rule Action Order
The order in which the rule actions are executed for the Web Engine is as follows:
1.
Note
2.
3.
4.
5.
6.
7.
8.
All Other Protocol Engine Rule Action Order
The order in which the rule actions are executed for the other protocol engines is the order in which they were configured, except for the validate-url-signature action. If the rule pattern associated with the validate-url-signature action is matched, regardless of the configuration order the rules, the validate-url-signature action is performed before any other action.
1.
2.
Note
3.
4.
Patterns
The Rules Template supports the following pattern types:
•
Note
•
–
rule pattern-list 22 group-type and
rule pattern-list 22 url-regsub 10 airforce
rule pattern-list 22 url-regsub wma wmv
rule pattern-list 23 url-regsub 10 airforce
rule pattern-list 23 url-regsub wma wmv
–
rule pattern-list 22 group-type and
rule pattern-list 22 url-regsub 10 airforce
rule pattern-list 23 url-regsub wma wmv
–
rule pattern-list 22 group-type or
rule pattern-list 22 url-regsub 10 airforce
rule pattern-list 22 url-regsub wma wmv
rule pattern-list 23 url-regsub 10 airforce
rule pattern-list 23 url-regsub wma wmv
–
rule pattern-list 22 group-type or
rule pattern-list 22 url-regsub 10 airforce
rule pattern-list 23 url-regsub wma wmv
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:
•
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 starts 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.comThe following example covers both uppercase and lowercase expressions of MP4 files:
ServiceEngine(config)# rule pattern-list 2 url-regex http://(.*.)cdsis.com/(.*.)[mM] [pP]4(.*)Related Commands
clear
Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.
show rule
Displays rules configuration information.
script
To execute a script provided by Cisco or check the script for errors, use the script command in EXEC configuration mode.
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.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The script command in EXEC configuration mode opens the script utility, which allows you to execute scripts supplied by Cisco 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 shows how to check for errors in the script file foo.script:
ServiceEngine# script check foo.scriptScript file foo.script is valid.service
To specify the type of service, use the service command in EXEC configuration mode.
On the CDSM:
service csm restart
On the SE:
service {acquisition restart | csm restart | distribution restart | flash-media-streaming restart | ms restart | rtspg restart | web-engine restart | wmt restart}
On the SR:
service {cms restart | service-router restart}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following example shows how to start acquisition service:
ServiceEngine# service acquisition restartThe service acquirer has been restarted successfully!ServiceEngine#service-router
To configure service routing, use the service-router command in Global configuration mode. To disable last-resort routing, use the no form of this command.
On the SE:
service-router {keepalive-interval num | service-monitor {augmentation-alarm enable | license-universal enable | 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 {augmentation num | burstcnt num | cpu num | disk num | faildisk num | fms num | kmemory num | memory num | movie-streamer num |nic num | wmt num} | transaction-log enable | type {all | cpu | disk | fms | kmemory | memory| movie-streamer | nic | wmt}}}
no service-router {keepalive-interval num | service-monitor {augmentation-alarm enable | license-universal enable | 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 {augmentation num | burstcnt num | cpu num | disk num | faildisk num | fms num | kmemory num | memory num | movie-streamer num |nic num | wmt num} | transaction-log enable | type {all | cpu | disk | fms | kmemory | memory | movie-streamer | nic | wmt}}}
On the SR:
service-router service-monitor {augmentation-alarm enable | number-of-samples {all num | cpu num | disk num | kmemory num | memory num} | sample-period {all num | cpu num | disk num | kmemory num | memory num} | threshold {augmentation num | cpu num | disk num | faildisk num | kmemory num | memory num} | type {all | cpu | disk | kmemory | memory}}
no service-router service-monitor {augmentation-alarm enable | number-of-samples {all num | cpu num | disk num | kmemory num | memory num} | sample-period {all num | cpu num | disk num | kmemory num | memory num} | threshold {augmentation num | cpu num | disk num | faildisk num | kmemory num | memory num} | type {all | cpu | disk | kmemory | memory}}
On the CDSM:
service-router {access-policy enable | content-based-routing {enable | redundant num} | lastresort {domain name {allow all | alternate name port_num} | error-domain name error-file port_num | translator ip_address port_num} | location-based-routing {enable | location-cache timeout num} | proximity-based-routing {enable | proximity-cache timeout num | proximity-server ip_address password password} | redirect-burst-control {enable | rate num} | redirect-mode {dns-redirect {all | domain domain} | ip-redirect} | service-monitor {augmentation-alarm enable | number-of-samples {all num | cpu num | disk num | kmemory num | memory num}} | subscribe domain domain | threshold {augmentation num | cpu num | disk num | kmemory num | memory num | transaction-log enable}}
no service-router {access-policy enable | content-based-routing {enable | redundant num} | lastresort {domain name {allow all | alternate name port_num} | error-domain name error-file port_num | translator ip_address port_num} | location-based-routing {enable | location-cache timeout num} | proximity-based-routing {enable | proximity-cache timeout num | proximity-server ip_address password password} | redirect-burst-control {enable | rate num} | redirect-mode {dns-redirect {all | domain domain} | ip-redirect} | service-monitor {augmentation-alarm enable | number-of-samples {all num | cpu num | disk num | kmemory num | memory num}} | subscribe domain domain | threshold {augmentation num | cpu num | disk num | kmemory num | memory num | transaction-log enable}}
Syntax Description
keepalive-interval
Specifies the SR keepalive interval in seconds.
keepalive_interval _num
Number of seconds. The range is from 1 to 120.
service-monitor
Configures Service Monitor related parameters.
augmentation-alarm
Alarm for checking the device level loads.
enable
Enables the augmentation alarm.
license-universal
Universal license feature to clear all alarms for Protocol Engines.
enable
Enables the universal license feature.
number-of-samples
Counts the latest sampled values to be used when calculating average.
all
Sets to all monitor types.
num
Count of latest sampled values to be used when calculating average. The range is from 1 to 120.
cpu
Enables the monitor CPU load.
disk
Sets the disk monitor type.
fms
Sets the FMS1 monitor type.
kmemory
Sets the monitor kernel memory type.
memory
Sets the monitor memory type.
movie-streamer
Monitors the Movie Streamer stream count.
wmt
Sets the WMT2 monitor type.
nic
Sets the Network Interface Card monitor type.
sample-period
Configures the time interval, in seconds, between two consecutive samples.
num
Time interval between two consecutive samples, in seconds. The range is from 1 to 60.
threshold
Configures threshold values.
augmentation
Applies the Augmentation alarm threshold as a percentage of the device parameter threshold.
num
Configures the Augmentation threshold values in percentage (1 to 100).
burstcnt
Configures the Protocol Engine Burst License Control monitor type.
num
Protocol Engine Burst License Control threshold value.
faildisk
Sets the disk failure monitor type.
num
Configures the Disk Failure Count threshold percentage (1-100). The default is 75 percent.
movie-streamer
Sets the Movie Streamer monitor type.
type
Configures the type to be monitored.
access-policy
Configures the service-router access-policy.
enable
Enables the access-policy.
enable
Enables the CDN Selector.
content-based-routing
Configures content based routing.
enable
Enables content based routing.
redundant
Specifies the number of redundant copies of the content.
num
Number of redundant copies of the content. The range is from 1 to 4.
lastresort
Configures the lastresort domain.
domain
Configures the domain.
name
Domain name.
allow
Allows the client to be routed through an alternate domain or origin server.
all
Allows all requests.
alternate
Configures an alternate domain.
name
Alternate domain name.
error-domain
Configures error domain.
name
Error domain name.
translator
Configures the external translator IP address.
ip_address
External translator IP address.
port
(Optional) Specifies the port number.
port_num
Port number (1-65535).
error-file
Configures error file name.
port_num
Error file name.
location-based-routing
Configures location-based routing.
enable
Enables location-based routing.
location-cache
Configures the location cache.
timeout
Configures the location cache timeout.
num
Location cache timeout in seconds (1 to 864000).
proximity-based-routing
Configures proximity-based routing.
enable
Enables proximity-based routing.
proximity-cache
Configures proximity cache.
timeout
Configures proximity cache timeout.
num
Proximity cache timeout, in seconds. The range is from 1 to 86400.
proximity-server
Configures proximity server IP address and port.
ip_address
IP address of proximity server.
redirect-burst-control
Configures the redirect burst control.
enable
Enables redirect burst control.
rate
Configures the redirect burst control rate (requests per second).
num
Redirect burst control rate. The range is from 1 to 100000.
redirect-mode
Enables the redirect mode. The redirect mode is disabled by default.
dns-redirect
Sets the redirect mode to DNS-based redirection.
Note
all
Enables the DNS-based redirection for all domains.
domain
Enables the DNS-based redirection for a specific domain.
domain
Name of the domain.
ip-redirect
Sets the redirect mode to IP-based redirection.
service-monitor
Configures service monitor parameters.
number-of-samples
Counts the latest sampled values to be used when calculating average.
all
Allows all monitor types.
num
Count of latest sampled values to be used when calculating average. The range is from 1 to 120.
cpu
Sets the CPU monitor type.
disk
Sets the disk monitor type.
kmemory
Sets the monitor kernel memory.
memory
Sets the monitor memory.
faildisk
Sets the disk failure monitor type.
sample-period
Configures the time interval between two consecutive samples.
subscribe
Configures the domains to which the service router should be subscribed.
domain
Configures the domain.
domain
Specifies the domain name.
threshold
Configures threshold values.
transaction-log
Configures Transaction logging for the Service Monitor.
enable
Enables transaction logging for the Service Monitor.
type
Configures the type to be monitored.
1 FMS = Flash Media Server
2 WMT = Windows Media Technology
Command Defaults
keepalive-interval: 2
redundant copies: 1
dns-ttl: 60
burstcnt: 1
location cache timeout: 691200 seconds (8 days)
content-based-routing: disabled
proximity cache timeout: 1800
sample-period: 1
nic sample-period: 3
number of samples: 2
faildisk: 75 percent
augmentation-alarm: disabled
transaction-logs: disabled
port number: 80
Command Modes
Global configuration (config) mode.
Usage Guidelines
To configure last-resort routing, use the service-router command in Global configuration mode, 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
Augmentation Alarms
Augmentation alarms on the Service Monitor are soft alarms that send alerts before the threshold is reached. These alarms are applicable to all devices—Service Engines, Service Routers and CDSMs. Augmentation thresholds apply to device and Protocol Engine parameters.
Note
As the show disk details command output reports, if disks have both SYSTEM and CDNFS partitions, they are treated as only system disks, which means they are not included in the accounting of the CDNFS disk calculation.
Location-Based Routing
The Geo-Location servers were introduced with the location-based routing method. Once you enable location-based routing, you must specify the Geo-Location servers.
The Authorization Service uses an XML file to allow or deny client requests based on the client's IP address or geographic location. The country, state, and city names in the Authorization XML file must match what is used by the Geo-Location server and the names are case sensitive.
Cross Domain 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.
Last-Resort Routing
Last-resort routing is not supported when dns-based-redirect is enabled.
Configuring the license-universal Command
Universal license is like a regular license but with higher BW and it applies to all PEs. When the user buys a universal license and configures this command, alarm data for all PEs is cleared. Thereafter monitoring of the PEs continues as usual for any future alarms. If universal license was already configured upon box reload (through saved configuration in the show run command), the existing licenses on the PEs is cleared and the PEs are monitored as usual for any future alarms.
The following information is cleared when you execute the service-router service-monitor license-universal enable command:
•
Note
•
•
Burst Streaming License Control
Previously, the license limit was set to 500 Mbps and each protocol engine had a maximum number of sessions allowed. The base license limit is set to 200 sessions and 200 Mbps bandwidth.
When the number of sessions or current bandwidth usage exceeds the configured license limit on the Service Engine, the protocol engine raises an alarm and sends a threshold exceeded notification to the Service Router. Any new requests for that protocol engine are not routed to that Service Engine.
Note
Configure Burst Count
The protocol engines can trigger multiple minor alarms for session and bandwidth exceeded threshold conditions. If multiple minor alarms are triggered for a protocol engine in a single day (24-hour interval), they are recorded as a single alarm.
The burst count, which indicates the number of days after which a major alarm is raised, is configurable. On the Service Engine, use the service-router service-monitor threshold burstcnt command to configure the burst count. The default setting is one (1), which means all the minor alarms that occur in a single day (24-hour interval) are counted as one single alarm. If the service-router service-monitor threshold burstcnt command is set to two, all minor alarms that occur in two days (48-hour interval) are counted as a single alarm.
Configure Universal License
A universal license is similar to a regular license, except it has a higher bandwidth and applies to all protocol engines (except Web Engine). When a universal license is purchased and configured, the alarm data for all protocol engines are cleared. Thereafter, the monitoring of the protocol engines continues as usual for any future alarms.
On the Service Engine, use the service-router service-monitor license-universal enable command to enable the universal license. The service-router service-monitor license-universal command is disabled by default.
Disk Failure Count Threshold
When the number of failed disks exceeds this threshold, no further requests are sent to this device and an alarm is raised. The Disk Failure Count Threshold is only for the CDNFS disks. Disk threshold configuration is the overall percentage of CDNFS disk failures after which an alarm is raised.
Note
Domain Subscription
The service-router subscribe domain command allows us to specify domains to which the service router should be subscribed. By default the service-router takes all the domains specified in the CDSM. Even if you configure only one domain subscription through this command, the SR takes the list of domains subscribed through the CLI to be the complete list.
URL Translator
Use the service-router lastresort domain domain translator ipaddress command to configure the IP address of the third party URL translator. If a translator configuration is not present for any domain, it falls back to the alternate domain configuration. A maximum of one translator can be configured per content origin.
Service Router Transaction Log Fields
Table 3-12 describes the fields for the Service Router transaction log.
Service Monitor Transaction Logs
Service Monitor transaction logs provide an additional tool for analyzing the health history of a device and the protocol engines.
The device and service health information are periodically logged on the device in transaction log files. Transaction logs provide a useful mechanism to monitor and debug the system. The transaction log fields include both device and protocol engine information applicable to Service Engines and Service Routers that are useful for capacity monitoring. Additionally, when a device or protocol engine threshold is exceeded, detailed information is sent to a file (threshold_exceeded.log) to capture the processes that triggered the threshold alarm.
The Service Monitor transaction log filename has the following format: service_monitor_<ipaddr>_yyyymmdd_hhmmss_<>, where:
•
•
For example, service_monitor_192.168.1.52_20110630_230001_00336 is the filename for the log file on the device with the IP address of 192.168.1.52 and a time stamp of June 30, 2011 at 3:36 AM.
The Service Monitor transaction log file is located in the /local1/logs/service_monitor directory.
An entry to the Service Monitor transaction log is made every two seconds.
Note
•
•
•
•
•
Table 3-13 describes the fields for the Service Monitor transaction log on an SE.
Table 3-14 describes the fields for the Service Monitor transaction log on a SR.
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 allAugmentation Alarms
The augmentation alarms threshold is a percentage, that applies to the CPU, memory, kernel memory, disk, disk fail count, NIC, and protocol engine usages. By default it is set to 80 percent.
As an example of an augmentation alarm, if the threshold configured for CPU usage is 80 percent, and the augmentation threshold is set to 80 percent, then the augmentation alarm for CPU usage is raised when the CPU usage crosses 64 percent.
If "A" represents the Service Monitor threshold configured, and "B" represents the augmentation threshold configured, then the threshold for raising an augmentation alarm = (A * B) / 100 percent.
The threshold value range is 1-100. The following command shows how to set the augmentation alarms threshold to 70 percent:
ServiceRouter(config)# service router service-monitor threshold augmentation 70The following command shows how to reset the augmentation alarm threshold to the default:
ServiceRouter(config)# no service router service-monitor threshold augmentation 70The show service-router service monitor command displays the augmentation alarm threshold configuration.
The show alarms command displays the alarms output.
The show alarms history detail command displays the history details.
The show alarms detail command displays the alarms details.
The show alarms detail support command displays the support information.
Cross Domain 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 enableThe following example shows how to configure Proximity Engine cache on an SR:
ServiceRouter(config)# proximity engine enableStarting Proximity Engine....Proximity Engine Started.ServiceRouter(config)# service-router proximity-based-routing proximity-server 127.0.0.1ServiceRouter(config)# service-router proximity-based-routing proximity-cache timeout 600ServiceRouter(config)# service-router proximity-based-routing enablePlease ensure you have purchased License for this advanced featureServiceRouter(config)# endThe following example shows how to enable DNS-based redirection with the cdsfms.com domain as the domain used to redirect all client requests to:
ServiceRouter(config)# service-router redirect-mode dns-redirect domain cdsfms.comThe following example shows how to display information about the redirect mode by entering the show service-router redirect-mode command:
ServiceRouter# show service-router redirect-modeip-redirect is enableddns-redirect domain fms.cds.comdns-redirect domain cds.comdns-redirect domain abc.comdns-redirect domain cdsfms.comThe following example shows how to subscribe the SR to a domain named test3.com:
ServiceRouter(config)# service-router subscribe domain test3.comServiceRouter(config)#The following example shows how to configure the failed disk threshold to 40 percent:
ServiceEngine(config)# service-router service-monitor threshold faildisk 40U2-205-2(config)#endU2-205-2#show running-config | include thresholdservice-router service-monitor threshold faildisk 40ServiceEngine#To display the statistics, use the show statistics service-router summary command and the show statistics se sename command. The new output for the DNS-Based Redirection feature is highlighted in boldface type in the examples below. In addition to these two show commands, there is also the show statistics service-router dns command, which displays the same output as before:
ServiceRouter# show statistics service-router summary----- SR Summary Statistics -----Requests Received : 2HTTP Requests (normal) : 0HTTP Requests (ASX) : 0RTSP Requests : 0RTMP Requests : 0DNS Requests : 2Requests Served : 0HTTP Requests Served : 0Requests Redirected : 1HTTP 302 Redirects : 0ASX Redirects : 0RTSP redirects : 0RTMP redirects : 0DNS redirects : 1Requests Overflowed : 1HTTP 302 Redirects : 0ASX Redirects : 0RTSP redirects : 0RTMP redirects : 0DNS redirects : 1Requests Not Redirected : 0No SE Covering Client : 0Unknown Content Origin : 0Route Table Locked : 0"Stale SE" Requests : 0ServiceRouter# show statistics service-router se temp2----- Statistics Of SE: temp2 -----IP Address : 2.225.2.59Aliveness : upHTTP 302 Redirects : 0ASX Redirects : 0RTSP Redirects : 0RTMP Redirects : 0DNS Redirects : 1Number Of Keepalives : 85261The following example shows how to enable the Service Monitor transaction logging:
ServiceEngine(config)# transaction-logs enableServiceEngine(config)# service-router service-monitor transaction-log enableThe following example shows how to configure the URL translator:
ServiceRouter(config)# service-router last-resort domain cds.com translator 171.XX.XX.XXXServiceRouter(config)# service-router last-resort domain cdsis.com translator 171.XX.XX.XXX port 8080ServiceRouter#The following example shows how to verify the current last resort configuration details:
ServiceRouter# show service-router last-resortDomain cds.com translator 171.XX.XX.XXXDomain cdsis.com translator 171.XX.XX.XXX port 8080Related Commands
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 command in EXEC configuration mode. You can also use the setup command in EXEC configuration mode to complete basic configuration after upgrading.
setup
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following example shows the part of the output when you enter the setup command in EXEC configuration mode 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 aaa
To display the accounting, authentication, and authorization configuration, use the show aaa command in EXEC configuration mode.
show aaa {commands [accounting | authorization] | enable [authentication] | exec [accounting | authorization] | login [authentication] | system [accounting | authorization]}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-15 describes the fields shown in the show aaa commands command display.
Table 3-16 describes the fields shown in the show aaa enable command display.
Table 3-17 describes the fields shown in the show aaa exec command display.
Table 3-18 describes the fields shown in the show aaa login command display.
Table 3-19 describes the fields shown in the show aaa system command display.
Table 3-19 show aaa system Field Descriptions
System events Accounting
Tacacs+
Accounting through Tacacs+ for system event is enabled or disabled.
Related Commands
show access-lists 300
To display the access control list (ACL) configuration, use the show access-lists 300 command in EXEC configuration mode.
show access-lists 300
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-20 describes the fields shown in the show access-lists 300 display.
Related Commands
show acquirer
To display the acquirer information and progress of content acquisition for a specified channel number or name, use the show acquirer command in EXEC configuration mode.
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
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The show acquirer progress command displays information for all channels for which the SE is the Content Acquirer. 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 command in Global configuration mode 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 command in Global configuration mode.
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.
The show acquirer progress command in EXEC configuration mode 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 3-21 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 command in Global configuration mode:
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 command in Global configuration mode:
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
show alarms
To display information on various types of alarms, their status, and history, use the show alarms command in EXEC configuration mode.
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
Command Defaults
None
Command Modes
EXEC configuration mode.
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 command in Global configuration mode.
Use the show alarms critical command in EXEC configuration mode to display the current critical alarms being generated by the Internet Streamer CDS software applications. Use the show alarms critical detail command in EXEC configuration mode to display additional details for each of the critical alarms being generated. Use the show alarms critical detail support command in EXEC configuration mode 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 command in EXEC configuration modes to display the details of major and minor alarms.
Use the show alarms history command in EXEC configuration mode 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 command in EXEC configuration mode to display the status of current alarms and the SE's alarm overload status and alarm overload configuration.
Note
Brstcnt Threshold Alarm
When the number of sessions or current bandwidth usage exceeds the configured license limit on the Service Engine, the protocol engine raises an alarm and sends a threshold exceeded notification to the Service Router. Any new requests for that protocol engine are not routed to that Service Engine.
Note
Table 3-22 describes the fields shown in the show alarms history display.
Table 3-23 describes the fields shown in the show alarms status display.
Related Commands
alarm
Configure alarms.
snmp-server enable traps
Enables the SE to send SNMP traps.
show arp
To display the Address Resolution Protocol (ARP) table, use the show arp command in EXEC configuration mode.
show arp
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The show arp command displays the Internet-to-Ethernet address translation tables of the ARP. Without flags, the current ARP entry for the hostname is displayed.
Table 3-24 describes the fields shown in the show arp display.
show authentication
To display the authentication configuration, use the show authentication command in EXEC configuration mode.
show authentication user
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Related Commands
show authsvr
To display the status of the Authorization server, use the show authsvr command in EXEC configuration mode.
show authsvr [unknown-server | location-server]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following example shows how to display the status of the Authorization server:
ServiceEngine# show authsvrAuthserver is EnabledThe following example shows the status of the Location server:
ServiceEngine# show authsvr location-serverPrimary geo location server 4.0.1.3 7000Secondary geo location server 171.71.50.140 7000Related Commands
show bandwidth
To display the bandwidth allocated to a particular device, use the show bandwidth command in EXEC configuration mode.
show bandwidth [flash-media-streaming | movie-streamer | wmt]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-25 describes the fields shown in the show bandwidth display.
Table 3-25 show bandwidth Field Descriptions
Module
Types of application servers for which bandwidth allocation is displayed:
•
•
•
•
•
Bandwidth Kbps
Maximum amount of bandwidth that you want allowed in kbps1 for a particular period of time. Incoming and outgoing bandwidth enforced is 8000000 kbps.
Start Time
Time of the day for the bandwidth rate setting to begin, using a 24-hour clock in local time on the SE (hh:mm).
End Time
Time of the day for the bandwidth rate setting to end, using a 24-hour clock in local time on the SE (hh:mm).
Default Bandwidth Kbps
Amount of default bandwidth (in kbps). The default bandwidth is the amount of bandwidth associated with each content service type when there is no scheduled bandwidth.
Max Bandwidth Kbps
Maximum bandwidth (in kbps) permitted by the system license. This bandwidth specifies the upper limit of allowable bandwidth.
1 kbps = kilobits per second
Related Commands
bandwidth (Global configuration)
Sets an allowable bandwidth usage limit and its duration for Cisco Streaming Engine WMT streaming media.
show banner
To display information on various types of banners, use the show banner command in EXEC configuration mode.
show banner
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-26 describes the fields shown in the show banner display.
Related Commands
show bitrate
To display the bit rate allocated to a particular device, use the show bitrate command in EXEC configuration mode.
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.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-27 describes the fields shown in the show bitrate display.
Related Commands
bitrate
Configures the maximum pacing bit rate for large files for the Movie Streamer and separately configures WMT bit-rate settings.
show cache
To display a list of cached contents, use the show cache command in EXEC configuration mode.
show cache { content num | deletion [ status [ all [ | [ begin line | count [ begin line | exclude line | include line ] | exclude line | include line ] ] | transaction-id transaction-id ] | transactions [ | [ begin line | count [ begin line | exclude line | include line ] | exclude line | include line ] ] | list path | | [ begin line | count [ begin line | exclude line | include line ] | exclude line | include line ] }
Syntax Description
Command Defaults
Number of cached contents is 100.
Command Modes
EXEC configuration mode.
Usage Guidelines
The show cache command allows users to check the cached content in an SE.
Use the show cache content command to display cache contents, such as priority, size, and URL, and to verify that content has been cached under the correct storage URL. The show cache content command also displays the eviction protection information. For relative contents such as WMT and MS, it only displays the parent URL information.
Note
Note
Examples
The following example shows how to display the cached contents:
ServiceEngine# show cache content 1000Max-cached-entries is set as 20000000Number of cal cached assets: 3913Eviction protection is disabled.Cache eviction-preferred-size configured is large------------------------------------------------Size URL------------------------------------------------200000 http://7.6.200.3/B480-Sep18-TEST1/62/file-0-7372200000 http://7.6.200.3/B480-Sep18-TEST1/62/file-0-6461200000 http://7.6.200.3/B480-Sep18-TEST1/99/file-0-9701200000 http://7.6.200.3/B480-Sep18-TEST1/99/file-0-4429200000 http://7.6.200.3/B480-Sep18-TEST1/99/file-0-8867200000 http://7.6.200.3/B480-Sep18-TEST1/67/file-0-3360200000 http://7.6.200.3/B480-Sep18-TEST1/927/file-0-4481200000 http://7.6.200.3/B480-Sep18-TEST1/927/file-0-5002200000 http://7.6.200.3/B480-Sep18-TEST1/44/file-0-4454200000 http://7.6.200.3/B480-Sep18-TEST1/105/file-0-4643200000 http://7.6.200.3/B480-Sep18-TEST1/291/file-0-544<Output truncated>Related Commands
show cache-router
To Display cache-router information for various Protocol Engines, use the show cache-route command in EXEC configuration mode.
show cache-router {routes {dss-engine url | fms-engine url | web-engine url | wmt-engine url | upstream-status}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
This command can only be run on an SE to see the route taken by the appropriate Protocol Engine through the CDN (from the current SE where this command is executed) to retrieve the asset for a given URL.
The sh cache-router routes command route calculation is agnostic of whether or not the URL is valid.
When a new SE is added to a delivery service, the get_cache_route does not vie the path, the command dumps the cached output and does not perform a liveness query. You must first enter the show cache router upstream status command and then the commands in the following example:
Examples
The following examples show the cache route information:
ServiceEngine# sh cache-router routes web-engine http://7.25.0.7/index.htmlThe route: [ 7.25.0.15/7.25.0.13/ ] will be used to cache the asset for URL=http://7.25.0.7/index.htmlServiceEngine# sh cache-router routes web-engine http://7.25.0.7/index.htmlThe route: [ 7.25.0.13/ ] will be used to cache the asset for URL=http://7.25.0.7/index.htmlServiceEngine# sh cache-router routes web-engine http://7.25.0.7/index.htmlThe route: [ (null) ] will be used to cache the asset for URL=http://7.25.0.7/index.htmlServiceEngine# sh cache-router routes web-engine http://ccp-ccp-images.gslb.bdn.lab.xcal.tv/image1The route: [ 69.241.50.154/69.252.83.150/69.241.118.14/ ] will be used to cache the asset for URL=http://ccp-ccp-images.gslb.bdn.lab.xcal.tv/image1.show capability
To display the capabilities of the Cap-X profile ID, use the show capability command in EXEC configuration mode.
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 from 1 to 65535.
Command Defaults
None
Command Modes
EXEC configuration mode.
Related Commands
show cdn-select
To display the status of the CDN Selector, use the show cdn-select command in EXEC configuration mode.
show cdn-select
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Related Commands
show cdnfs
To display CDS network file system (CDNFS) information, use the show cdnfs command in EXEC configuration mode.
show cdnfs {usage | volumes}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
If there are any clear cache all commands in progress, the show cdnfs usage command displays the progress. If any disks are marked for not creation, then the disk is listed here and the reason is provided.
Table 3-28 describes the fields shown in the show cdnfs volumes display.
Table 3-28 show cdnfs volumes Field Descriptions
cdnfs 00-04
CDS network file system and disk number.
nnnnnnKB
Size of the volume in kilobytes.
Table 3-29 describes the fields shown in the show cdnfs usage display.
Examples
The following example shows how to display the CDNFS usage on an SE:
ServiceEngine# show cdnfs usageTotal number of CDNFS entries : 13437532Total space : 5037.9 GBTotal bytes available : 2425.6 GBTotal cache size : 2521.4 GBTotal cached entries : 13436995Cache-content mgr status : CacheableUnits: 1KB = 1024B; 1MB = 1024KB; 1GB = 1024MBThe following example shows how to display the CDNFS volumes:
ServiceEngine# show cdnfs volumescdnfs 00: /disk00-06 444200480KBcdnfs 01: /disk01-06 444200480KBcdnfs 02: /disk03-01 488246296KBcdnfs 03: /disk04-01 488247316KBcdnfs 04: /disk05-01 488246296KBcdnfs 05: /disk06-01 488244924KBcdnfs 06: /disk07-01 488244924KBcdnfs 07: /disk09-01 488244924KBcdnfs 08: /disk10-01 488244924KBcdnfs 09: /disk11-01 488246296KBcdnfs 10: /disk08-01 488377368KBRelated Commands
show clock
To display the system clock, use the show clock command in EXEC configuration mode.
show clock [detail | standard-timezones {all | details timezone | regions | zones region_name}]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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 adjusts 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 command in EXEC configuration mode 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.
Table 3-30 describes the field in the show clock display.
Table 3-30 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 3-31 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 command in EXEC configuration mode. As the following example shows all 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 command in EXEC configuration mode. 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 command in EXEC configuration mode. 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 command in EXEC configuration mode. 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)
Sets or clears clock functions or updates the calendar.
clock (Global configuration
Sets the summer daylight saving time and time zone for display purposes.
show cms
To display the Centralized Management System (CMS)-embedded database content and maintenance status and other information, use the show cms command in EXEC configuration mode.
show cms {database {content {dump filename | text | xml} | maintenance [detail]} | info | processes}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-32 describes the fields shown in the CDSM show cms info display.
Table 3-33 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 (EXEC)
Configures the CMS-embedded database parameters.
cms (global)
Schedules maintenance and enables the CMS on a given node.
show content
To display all content entries in the CDS, use the show content command in EXEC configuration mode.
show content {all [brief | foreground] | diskpath [brief | detail] | last-folder-url [brief] | url url [brief | detail]}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
This command allows users to check the cached or prepositioned content in an SE. Through this command, users can view content attributes such as status and file size.
Note
The show content all command scans through the entire disk and transfers the information to the file specified by the user. This command runs in the background unless the foreground option is specified.
The show content url command displays cached content and Web Engine metadata attributes, and it helps debug header validation issues. It also displays additional information including start, end time, UNS, and relative content information. If the input URL is parent, then it shows the child disk path. The Authorization field is only applicable for preposition content and this field is moved to the show content url detail output.
When executing the show content url command with live URL, it displays as preposition content. This is because the object stored on CDNFS is either cache content or preposition content.
Examples
The following command shows how to display cached content and Web Engine attributes for a URL:
ServiceEngine# show content url http://172.XX.XX.XXX/diff.new detailCAL content object attributes:URL: http://we-os.cds.com/vod/pinball.wmvStatus is 3 (Servable)Content is CompleteFile size is 0 BytesPlayable by WebEngine WMTLinked to[rtsp://http-we-os.cds.com-s6kmyz359zgyulqfiavhgw/vod/pinball.wmv]Content is PREPOSITIONEDStart Time : Not presentEnd Time : Not presentInternal path to data file[/disk00-06/p/we-os.cds.com/1d/a1/1da1394af838bbcb45af78fd5681abeb/pinball.wmv]Protocol Engine Metadata:Authorization is Not Requireduns_attr_symlink :http-we-os.cds.com-s6kmyz359zgyulqfiavhgw/vod/pinball.wmvUNS_NV_CALC_N_CACHED : PREPOSITIONEDcdn_uns_id : Rm+7u02g2S8PsuaCfnOKAQ..content-type : video/x-ms-wmvetag : "9601c7-cc3d0-11016c00"file_duration : 25ignore_query_string : 1last-modified : Wed, 06 Oct 2010 22:12:00 GMTserver : Apache/2.2.3 (Red Hat)The following example shows how to display 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 shows how to display all content entries in the CDS:
ServiceEngine# show content all name backgroundCommand running in background...ServiceEngine# USER INFO: Your 'show content all' command finishedThe following example shows how to display cached content objects with the original diskpath.
ServiceEngine# show content diskpath /disk02-01/c/171.71.51.234/66/66/6666cd76f96956469e7be39d750cc7d9/1mbs.wmv.hdrCAL content object attributes:URL: rtsp://171.XX.XX.XXX/1mbs.wmv.hdrStatus is 3 (Servable)Content is IncompleteFile size is 4096 BytesPlayable by WMTAuthorization is Not RequiredContent is CACHED with priority 0.303707The following example shows how to display all the contents matching to that last-folder-url with the brief option:
ServiceEngine# show content last-folder-url http://172.XX.XX.XXX/vod/types briefProtocol will be ignored with last-folder-url.-----------------------------------------------------------------Type URL Size(K) Status-----------------------------------------------------------------C http://172.XX.XX.XXX/vod/types/sample_s 81 Servableorenson.movC http://172.XX.XX.XXX/vod/types/sample_1 912 Servable00kbit.mp4C http://172.XX.XX.XXX/vod/types/brodeo.m 3745 Servablep3The following example shows how to display all the contents matching to that last-folder-url without the brief option:
ServiceEngine# show content last-folder-url http://172.XX.XX.XXX/vod/typesProtocol will be ignored with last-folder-url.CAL content object attributes:URL: http://172.XX.XX.XXX/vod/types/sample_sorenson.movStatus is 3 (Servable)Content is CompleteFile size is 82395 BytesPlayable by WebEngineContent is CACHEDCAL content object attributes:URL: http://172.XX.XX.XXX/vod/types/sample_100kbit.mp4Status is 3 (Servable)Content is CompleteFile size is 933456 BytesPlayable by WebEngineContent is CACHEDCAL content object attributes:URL: http://172.XX.XX.XXX/vod/types/brodeo.mp3Status is 3 (Servable)Content is CompleteFile size is 3834862 BytesPlayable by WebEngineContent is CACHEDshow content-mgr
To display all content management information in the CDS, use the show content-mgr command in EXEC configuration mode.
show content-mgr {content {all {all-disk-volumes output-file filename | disk-volume output-file filename| cache {all-disk-volumes output-file filename | disk-volume output-file filename | prepos {all-disk-volumes output-file filename | disk-volume output-file filename} | disk-info | eviction-list size num {all-disk-volumes output-file filename | disk-volume output-file filename | eviction-protection output-file filename | health-info}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The show content-mgr content all command dumps all the contents to the specified output file. This process goes through the entire Content Manager data structure to collect file information, and then writes it into the file specified by the user. When the Content Manager begins to dump the records, it states the number of records it prepares to write and how many are actually written in the ~/errorlog/ content_manager.current file.
The following example shows a dump with no object being deleted:
03/18/2011 23:32:34.945(Local)(9633)LOG :ContentMgr.cpp:968-> Scheduled prepositioned entries[1] for dump03/18/2011 23:32:34.945(Local)(9633)LOG :CMgrDumpStore.cpp:75-> Starting dump, entries[1]03/18/2011 23:32:34.946(Local)(9633)LOG :CMgrDumpStore.cpp:97-> Dump finished.The following example shows a dump with objects being deleted:
14:03/18/2011 23:36:20.195(Local)(9633)LOG :ContentMgr.cpp:951-> Scheduled cached entries[81931] for dump14:03/18/2011 23:36:20.195(Local)(9633)LOG :CMgrDumpStore.cpp:75-> Starting dump, entries[81931]14:03/18/2011 23:36:23.764(Local)(9633)LOG :CMgrDumpStore.cpp:97-> Dump finished. Entries removed during dump[41931]. These will not show up in the output file.The show content-mgr disk-info command prints disk and asset information for the Content Manager monitors.
Examples
The following example shows how to display all the Content Manager disk information in an output file:
ServiceEngine# show content-mgr content all all-disk-volumes output-file dumps#type-tail dumps#ContentType Priority URL DiskPathcached-content 6 http://5.3.3.10/a_1/file_10005542/disk00-06/c/5.3.3.10/5f/37/5f37c0748805ddf6e58a63853b3677af/file_10005542.httpprepos-content 0 http://172.22.67.108/vod/FootballHD.flv/disk08-01/p/172.22.67.108/1d/a1/1da1394af838bbcb45af78fd5681abeb/FootballHD.flvprepos-content 0://172.22.67.108/manifest-Channel_5683.xml-FNtiIA2L9GVRqiFKzK-h3w/disk04-01/p/172.22.67.108/66/66/6666cd76f96956469e7be39d750cc7d9/_7279f4d49c9963f509d8ad2cd772fdf6prepos-content 0://http-172.22.67.108-89xld465l9xq3fuq2dgi5w/vod/abc.html/disk06-01/p/http-172.22.67.108-89xld465l9xq3fuq2dgi5w/1d/a1/1da1394af838bbcb45af78fd5681abeb/abc.htmlThe following example shows how to display the Content Manager disk information:
ServiceEngine# show content-mgr disk-infoMount point : /disk00-01Bucket Number Assigned to Disk : 0File system : CDNFSTotal space : 423.6 GBFree space : 415.1 GBDisk Eviction low watermark : 381.3 GBDisk Eviction high watermark : 394.0 GBWritable : YesUsable : YesPreposition Asset Count : 0Cache Asset Count : 0Preposition Asset Size : 0 BCache Asset Size : 0 BThe following example shows how to display the Content Manager health information:
ServiceEngine# show content-mgr health-infoDeletion Task Count : 0Deletion Store Sizedisk00-06 : 0 Bdisk01-06 : 0 Bdisk02-01 : 0 BProtection Table Size : 0 BSnapshot In Progress : NoEviction In Progress : NoSlow scan In Progress : NoSanity In Progress : NoClear Cache All In Progress : NoDump In Progress : NoPriority Queue Asset Count : 0HitCount Decay Half Life (days): 14Disk Bucket Alarm Threshold(%): 30------------------------ Printing All Asset Info ------------------------Mount Point : disk00-06Preposition Asset Count : 4Cache Asset Count : 0Preposition Asset Size : 104 BCache Asset Size : 0 BMount Point : disk01-06Preposition Asset Count : 8Cache Asset Count : 0Preposition Asset Size : 312 BCache Asset Size : 0 BMount Point : disk02-01Preposition Asset Count : 2Cache Asset Count : 0Preposition Asset Size : 52 BCache Asset Size : 0 BMemory pool statistics : [ Used][ Free][ Max Used]Cached File Nodes : [ 0][ 0][ 0]Cached Child Nodes : [ 0][ 0][ 0]Cached Dir Nodes : [ 1][ 818][ 1]Prepos File Nodes : [ 14][ 220738][ 15]Prepos Child Nodes : [ 48][ 262096][ 49]Prepos Dir Nodes : [ 35][ 784][ 35]------------------------ Printing Process Status ------------------------CPU Usage Percent : 0.00Threads Count : 33Virtual Memory Size : 189.6 MBResident Memory Size : 33.4 MB------------------------ Printing Delivery Services ------------------------Delivery Service Id : 1450Origin FQDN : 172.22.67.227Routing Domain Name : vodplay1.comDelivery Service Id : 1272Origin FQDN : 1.2.3.5Routing Domain Name : livewmtplay.comDelivery Service Id : 1262Origin FQDN : 171.71.51.234Routing Domain Name : wmtplay.comDelivery Service Id : 1260Origin FQDN : 172.22.67.108Routing Domain Name : vodplay.comRelated Commands
show content-origin
To display information about the Network-attached Storage (NAS) mount, use the show content-origin command in user EXEC configuration mode.
show content-origin request-fqdn domain
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
Table 3-33 describes the fields shown in the show content-origin display.
The following syslog messages are displayed if the NAS mount fails:
Cds Origin Manager writes syslog messages when NAS mount fails. Below are some sample syslog messages:Apr 28 04:25:26 nas-se CdsOriginMgr: %SE-CdsOriginMgr-3-802100: Failed to mount NFS vod/0 for NAS share 14.1.2.12:/ifs/dataExamples
The following example shows how to display the content origin information:
ServiceEngine# show content-originFQDN: www.cisco.comProtocol: CIFSSharePoint: 171.XX.XX.X:/wmrootMountPoint: WMSStatus: SuccessProtocol: NFSSharePoint: 171.XX.XX.XXX:/usr/local/apache2/htdocs/WMTMountPoint: WMTStatus: FailedMaxRetry: 10RetryCount: 17Protocol: NFSSharePoint: 171.XX.XX.XXX:/usr/local/apache2/htdocs/ZeriMountPoint: ZERIStatus: FailedMaxRetry: 10RetryCount: 17ServiceEngine#Related Commands
show debugging
To display the state of each debugging option, use the show debugging user command in user EXEC configuration mode.
show debugging [ip {bgp | ospf | proximity | rib} | isis | srp | svc {desci | registry}]
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
The show debugging ip bgp command is used to display the debugging flags that have been set for BGP.
The show debugging ip ospf command is used to display debug options for OSPF processes that are enabled.
The show debugging ip rib command is used to display debug options for rib processes that are enabled.
The show debugging isis command is used to display debug options for IS-IS processes that are enabled.
The show debugging srp command is used to displays the debug flags that are turned on for the SRP.
Examples
The following is sample output from the show debugging ip bgp command:
ServiceRouter# debug ip bgp keepalivesServiceRouter# show debugging ip bgpBGP keepalives debug is onServiceRouter# debug ip bgp allServiceRouter# show debugging ip bgpBGP events debug is onBGP internal debug is onBGP RIB debug is onBGP BRIB debug is onBGP updates debug is onBGP keepalives debug is onBGP packets debug is onBGP IO debug is onBGP list debug is onBGP dampening debug is onServiceRouter#The following is sample output from the show debugging ip ospf command:
ServiceRouter# show debugging ip ospfAll OSPF debug is onAdjacency events debug is onOSPF LSDB changes debug is onOSPF LSDB timers debug is onOSPF related events debug is onLSA flooding debug is onServiceRouter#The following is sample output from the show debugging isis command.
ServiceRouter# show debugging isisSRP error debug is onSRP api debug is onSRP multicast debug is onSRP session debug is onSRP srhp packet debug is onSRP replica debug is onSRP packet asiii debug is onSRP function debug is onSRP replay is onServiceRouter#The following example shows the use of show srp debug command:
ServiceRouter# show debugging srpSRP packet debug is onSRP error debug is onSRP database debug is onSRP api debug is onSRP host debug is onSRP multicast packet debug is onSRP session debug is onSRP srhp packet debug is onSRP replica debug is onSRP sync debug is onSRP configuration debug is onSRP ippc debug is onSRP packet ascii debug is onSRP function debug is onServiceRouter#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
Monitors and records caching application functions.
undebug
Disables debugging functions.
show debugging srp
To display the debug flags that are turned on for SRP, use the show debugging srp command in privileged EXEC mode.
show debugging srp
Syntax Description
This command has no arguments or keywords.
Command Default
None
Command Modes
Privileged EXEC configuration mode.
Examples
The following example shows the use of show debugging srp:
ServiceRouter# show debugging srpSRP packet debug is onSRP error debug is onSRP database debug is onSRP api debug is onSRP host debug is onSRP multicast packet debug is onSRP session debug is onSRP srhp packet debug is onSRP replica debug is onSRP sync debug is onSRP configuration debug is onSRP ippc debug is onSRP packet ascii debug is onSRP function debug is onServiceRouter#show device-mode
To display the configured or current mode of a device, use the show device-mode command in EXEC configuration mode.
show device-mode {configured | current}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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 show device-mode current command 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
show direct-server-return
To display the Direct Server return information, use the show direct-server-return command in EXEC configuration mode.
show direct-server-return
Syntax Description
This command has no keywords or arguments.
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following example shows how to display the Direct Server return information:
ServiceEngine# show direct-server-returndirect-server-return vip 11.11.11.11Related Commands
show disks
To view information about your disks, use the show disks command in EXEC configuration mode.
show disks [current | details | error-handling [details] | raid-state | SMART-info [details]]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The show disks command displays the names of the disks currently attached to the SE.
Table 3-35 describes the fields shown in the show disks details display.
The show disks error-handling command displays the current level of disk and sector-related errors.
Table 3-36 describes the fields shown in the show disks error-handling details display.
I/O e
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 about the operating and environmental conditions that may indicate an impending disk failure.
To display more detailed information, enter the show disks SMART-info details command in EXEC configuration mode. The output from the show disks SMART-info and the show disks SMART-info details commands 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 command in EXEC configuration mode also includes SMART information.
Table 3-37 describes some typical fields in the show disks SMART-info display.
Examples
The following example displays output for two disks experiencing sector errors:
ServiceEngine# show disks error-handlingDisk errors since last boot:disk05 total bad sectors = 1, total errors = 2disk10 total bad sectors = 3, total errors = 9If the details option is given, then each bad sector's Logical Block Address (LBA) displays along with its corresponding I/O error count:
ServiceEngine# show disks error-handling detailsDisk errors since last boot:disk05 total bad sectors = 1, total errors = 2# diskname Sector (LBA) I/O errors:disk05 3000005 2disk10 total bad sectors = 3, total errors = 9# diskname Sector (LBA) I/O errors:disk10 16000 3disk10 170001 4disk10 180001 2Total errors (since system boot) across all disks = 11
Note
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 command in EXEC configuration mode 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 -iThe following example shows the output from the show dis raid-state command, which shows all the disk partitions on a CDE:
ServiceEngine# #show disks raid-stateSYSTEM : RAID-1Status: NormalPartitions: disk00/05 disk02/05SYSTEM: RAID-1Status: NormalPartitions: disk00/01 disk02/01SYSTEM: RAID-1Status: NormalPartitions: disk00/02 disk02/02SYSTEM: RAID-1Status: NormalPartitions: disk00/04 disk02/04Related Commands
disk (EXEC)
Configures disks and allocates disk space for devices using CDS software.
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 command in EXEC configuration mode.
show distribution [delivery-services {delivery-service-id delivery_service_num | delivery-service-name delivery_service_name} | forwarder-list {delivery-service-id delivery_service_num | delivery-service-name delivery_service_name} | location {forwarder-load-weight | live-load-weight | location-leader-preference} {delivery-service-id delivery_service_num | delivery-service-name delivery_service_name} | mcast-data-receiver {channels | cloud detail} | mcast-data-sender {channels | cloud detail} | object-status object_url | processes | remote ip_address {metadata-sender {delivery-service-id delivery_service_num [start-generation-id gen_id end-generation-id gen_id] | {delivery-service-name delivery_service_name [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}} | delivery-service-name delivery_service_name {cdn-url cdn_url | probe | relative-cdn-url cdn_url}} | 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.
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.
mcast-data-receiver
Display Multicast Data Receiver information.
channels
(Optional) Displays the list of channels assigned.
cloud
(Optional) Displays the cloud configuration.
detail
(Optional) Displays detailed cloud configuration.
mcast-data-sender
Displays Multicast Data Sender information.
object-status
(Optional) Displays information on the status of a prepositioned object.
object_url
URL of the prepositioned 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. The range is from 1 to 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 Content Acquirer.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Note
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 prepositioned 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:
•
•
•
Use the show distribution mcast-data-sender and show distribution mcast-data-receiver commands to see a list of assigned channels and cloud configuration for the Multicast data senders and receivers that were added to the Multicast cloud using the multicast 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 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 selects 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 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 Content Acquirer:
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 following example shows the mcast-data-sender information:
SE-5#show distribution mcast-data-senderMulticast enabledCurrently a Primary Multicast Sender for Cloud : shekharMC [412]Primary Sender Details-----------------------Multicast Sender State : PRIMARY_ACTIVE(1)Current Send State : OK to SendCurrent MOUT BW (kbps) : 100000Fixed Carousel : DisabledMulticast Checkpoint Transfer : EnabledCurrent Default Per Delivery service data rate(kbps) :100000The 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 Origin server failover information for delivery service ID 373:
ServiceEngine# show distribution delivery-service delivery-service-name deliveryDelivery Service Configuration---------------------Delivery Service ID : 239Delivery Service Name : deliveryContent Origin Name : 3M-Prepos-TestContent Origin fqdn : www.threemprepos.comContent Origin Origin FQDN : 72.0.110.38Delivery Service Priority : 750Configured Distribution Type : Multicast/UnicastContent Acquirer Information-------------------ID of Configured Content Acquirer : 283Name of Configured Content Acquirer : SE-3IP of Configured Content Acquirer : 8.8.8.103ID of Effective Content Acquirer : 283Current content-Acquirer-uid : 1381954721This SE's Role : Not a Content AcquirerThis SE in Full Reload : NoContent Acquirer Failover/Fallback Information---------------------------------------Content Acquirer Failover/Fallback Interval: 20 MinsOrigin Server Failover Information--------------------Origin Server Failover Status : OffMetadata Information--------------------Metadata-Forwarder ID : 283Metadata-Forwarder Name : SE-3Metadata-Forwarder Primary IP : 8.8.8.103Metadata-Forwarder NAT IP/Port : N/AAddress to Poll Metadata-Forwarder : Primary IPMetadata-Forwarder Status : LOC-LEADLast gen-id Switch : 350469 Secs agoCurrent low-water-marker : 1Current max-gen-id : 4202Current max-del-gen-id : 0Last poll : 92 Secs agoNext poll : 28 Secs from nowIdle poll interval : 120 SecsPoll interval multiplier : 1Unicast Information-------------------Ucast-Forwarder ID : 283Ucast-Forwarder Name : SE-3Ucast-Forwarder Primary IP : 8.8.8.103Ucast-Forwarder NAT IP/Port : N/AAddress to Poll Ucast-Forwarder : Primary IPUcast-Forwarder Status : LOC-LEADDelivery service level unicast option for this SEUcast Receiver of this SE : Enabled for this delivery serviceUcast Sender of this SE : Enabled for this delivery serviceMulticast Information---------------------Multicast Cloud InformationMcast Receiving : NoMcast Sending : YesDelivery service level multicast option for this SEMcast Receiver of this SE : Enabled for this delivery serviceMcast Sender of this SE : Enabled for this delivery serviceMcast sender data rate : 10000 KbpsFec value of this delivery service : 16Carousel value of this delivery service : 4QoS Configuration-----------------MetaData QoS (effective system config) : 0 (Not Enabled)Multiccast QoS : 56 [0X 38]Progress Information--------------------Number of jobs completed : 1056Has 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
The following example provides delivery service distribution information for delivery service ID 527:
ServiceEngine# show distribution delivery-services delivery-service-id 239Delivery Service Configuration---------------------Delivery Service ID : 239Delivery Service Name : deliveryContent Origin Name : 3M-Prepos-TestContent Origin fqdn : www.threemprepos.comContent Origin Origin FQDN : 72.0.110.38Delivery Service Priority : 750Configured Distribution Type : Multicast/UnicastContent Acquirer Information-------------------ID of Configured Content Acquirer : 283Name of Configured Content Acquirer : SE-3IP of Configured Content Acquirer : 8.8.8.103ID of Effective Content Acquirer : 283Current content-Acquirer-uid : 1381954721This SE's Role : Not a Content AcquirerThis SE in Full Reload : NoContent Acquirer Failover/Fallback Information---------------------------------------Content Acquirer Failover/Fallback Interval: 20 MinsOrigin Server Failover Information--------------------Origin Server Failover Status : OffMetadata Information--------------------Metadata-Forwarder ID : 283Metadata-Forwarder Name : SE-3Metadata-Forwarder Primary IP : 8.8.8.103Metadata-Forwarder NAT IP/Port : N/AAddress to Poll Metadata-Forwarder : Primary IPMetadata-Forwarder Status : LOC-LEADLast gen-id Switch : 350374 Secs agoCurrent low-water-marker : 1Current max-gen-id : 4202Current max-del-gen-id : 0Last poll : 117 Secs agoNext poll : 3 Secs from nowIdle poll interval : 120 SecsPoll interval multiplier : 1Unicast Information-------------------Ucast-Forwarder ID : 283Ucast-Forwarder Name : SE-3Ucast-Forwarder Primary IP : 8.8.8.103Ucast-Forwarder NAT IP/Port : N/AAddress to Poll Ucast-Forwarder : Primary IPUcast-Forwarder Status : LOC-LEADDelivery service level unicast option for this SEUcast Receiver of this SE : Enabled for this delivery serviceUcast Sender of this SE : Enabled for this delivery serviceMulticast Information---------------------Multicast Cloud InformationMcast Receiving : NoMcast Sending : YesDelivery service level multicast option for this SEMcast Receiver of this SE : Enabled for this delivery serviceMcast Sender of this SE : Enabled for this delivery serviceMcast sender data rate : 10000 KbpsFec value of this delivery service : 16Carousel value of this delivery service : 4QoS Configuration-----------------MetaData QoS (effective system config) : 0 (Not Enabled)Multiccast QoS : 56 [0X 38]Progress Information--------------------Number of jobs completed : 1056Has 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
The following example provides the forwarder list information for delivery service ID 6290:
ServiceEngine# show distribution forwarder-list delivery-service-id 6290 detail************************** delivery service 6290 ***************************Topology Information:Delivery Service : ( 6290) akot1Content Origin : ( 6289) akoHome SE : ( 6162) W14-CDE205-1Home Location : ( 6189) W14-CDE205-1-locationContent Acquirer : ( 6181) W14-612-1Root Location : ( 6182) W14-612-1-location======================= Forwarder Result Start ========================Latest information for unicast Meta-Data receptionand for unicast Data reception.USABLE Forwarder:SE ID : ( 6181) W14-612-1SE Location : ( 6182) W14-612-1-locationSE IP address : 114.0.92.11 SE Fowarder Level : 2SE attributes : resides in root locationis the Content Acquirer for the Delivery ServiceSE state : USABLEapplies until Thu Jul 8 05:42:43 2010Result Status :Am Location Leader : YesPOLLABLE Forwarder:None.----------------------------------------------------------------------Location Path:List of locations from Home-Location to Root-LocationNumber of locations : 3( 6189) W14-CDE205-1-location( 6068) L1( 6182) W14-612-1-location------------------------------------------------------------------List of Delivery-Service-subscribed locations from Home-Location to Root-LocationNumber of locations : 3( 6189) W14-CDE205-1-location( 6068) L1( 6182) W14-612-1-location----------------------------------------------------------------------Forwarder Lists:Location W14-CDE205-1-location(6189) REACHABLE.Showing Forwarder list forLocation : ( 6189) W14-CDE205-1-locationNumber of forwarders in location : 1----------------------------------------Configured Forwarder SE List:<EMPTY>Non-configured Forwarder SE List:<EMPTY>------------------------------------------------------------------Location L1(6068) REACHABLE.Showing Forwarder list forLocation : ( 6068) L1Number of forwarders in location : 0----------------------------------------Configured Forwarder SE List:<EMPTY>Non-configured Forwarder SE List:<EMPTY>------------------------------------------------------------------Location W14-612-1-location(6182) REACHABLE.Showing Forwarder list forLocation : ( 6182) W14-612-1-locationNumber of forwarders in location : 1----------------------------------------Configured Forwarder SE List:SE ID ( 6181) W14-612-1 IP 114.0.92.11 state USABLE (Content Origin)Non-configured Forwarder SE List:<EMPTY>Related Commands
show flash
To display the flash memory version and usage information, use the show flash command in EXEC configuration mode.
show flash
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
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 runs on the device after reload.
Note
Examples
The following example shows how to display 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 3-38 describes the fields shown in the show flash display.
Related Commands
show flash-media-streaming
To display the Flash Media Streaming information, use the show flash-media-streaming command in EXEC configuration mode.
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
Note
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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 shows how to display 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.ServiceEngine#Related Commands
flash-media-streaming
Enables and configures Flash Media Streaming.
show statistics flash-media-streaming
Displays the statistics for Flash Media Streaming.
show ftp
To display the caching configuration of the File Transfer Protocol (FTP), use the show ftp command in EXEC configuration mode.
show ftp
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following example shows how to display the 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 command in EXEC configuration mode.
show hardware [all | core | cpuinfo | dmi [all | baseboard | bios | cache | chassis | connector | memory | processor | slot | system] | mapping {disk [all | diskname] | interface [all | GigabitEthernet slot/port_num | TenGigabitEthernet slot/port_num]} | meminfo | pci [details | drivers | ids | tree]]
Syntax Description
all
(Optional) Displays all hardware class information.
core
(Optional) Displays core hardware information.
cpuinfo
(Optional) Displays CPU information.
dmi
(Optional) Displays DMI1 .
all
(Optional) Displays all DMI information.
baseboard
(Optional) Displays motherboard information.
bios
(Optional) Displays BIOS information.
cache
(Optional) Displays processor cache information.
chassis
(Optional) Displays chassis information.
connector
(Optional) Displays connector information.
memory
(Optional) Displays physical memory information.
processor
(Optional) Displays processor information.
slot
(Optional) Displays PCI slot information.
system
(Optional) Displays system information.
mapping
(Optional) Shows mapping between Cisco and Linux hardware names.
disk
Maps Cisco disk name to Linux device name.
diskname
Name of the disk (disk00).
interface
Maps Cisco interface name to Linux device name.
all
Displays all interface information.
GigabitEthernet
Selects a 1G ethernet interface.
slot/port_num
Slot and port number for the selected interface. The slot range is from 1 to 14; the port range is from 0 to 0. The slot number and port number are separated with a forward slash character (/).
TenGigabitEthernet
Selects a 10G ethernet interface.
meminfo
(Optional) Displays RAM information.
pci
(Optional) Displays PCI information.
details
(Optional) Show output with PCI addresses and names.
drivers
(Optional) Identify driver names and availability.
ids
(Optional) Show PCI vendor and device codes.
tree
(Optional) Show a tree-like diagram containing all buses, bridges and devices.
1 Desktop Management Interface
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The output of the show hardware command in EXEC configuration mode displays all core or Desktop Management Interface (DMI) information. The DMI output can also be filtered by optional keywords.
Table 3-39 describes the fields shown in the show hardware display.
Examples
The following example shows how to display the core hardware information:
ServiceEngine# show hardware coreContent Delivery System Software (CDS)Copyright (c) 1999-2011 by Cisco Systems, Inc.Content Delivery System Software Release 2.6.0 (buildb460 Aug 28 2011)Version: cde220-2g2-DEVELOPMENT[vcn-build1:/auto/vcn-u1/cdsis_release_builds/cdsis_2.6.0-b460/spcdn]Compiled 05:55:01 Aug 28 2011 by ipvbuildCompile Time Options: KQ SSSystem was restarted on Mon Aug 29 11:56:58 2011.The system has been up for 1 day, 5 hours, 5 minutes, 2 seconds.CPU 0 is GenuineIntel Intel(R) Xeon(R) CPUL5410 @ 2.33GHz (rev 23) running at 2333MHz.CPU 1 is GenuineIntel Intel(R) Xeon(R) CPUL5410 @ 2.33GHz (rev 23) running at 2333MHz.CPU 2 is GenuineIntel Intel(R) Xeon(R) CPUL5410 @ 2.33GHz (rev 23) running at 2333MHz.CPU 3 is GenuineIntel Intel(R) Xeon(R) CPUL5410 @ 2.33GHz (rev 23) running at 2333MHz.CPU 4 is GenuineIntel Intel(R) Xeon(R) CPUL5410 @ 2.33GHz (rev 23) running at 2333MHz.CPU 5 is GenuineIntel Intel(R) Xeon(R) CPUL5410 @ 2.33GHz (rev 23) running at 2333MHz.CPU 6 is GenuineIntel Intel(R) Xeon(R) CPUL5410 @ 2.33GHz (rev 23) running at 2333MHz.CPU 7 is GenuineIntel Intel(R) Xeon(R) CPUL5410 @ 2.33GHz (rev 23) running at 2333MHz.Total 8 CPUs.16000 Mbytes of Physical memory.10 GigabitEthernet interfaces1 Console interface2 USB interfaces [Not supported in this version ofsoftware]Cookie info:Base PID: CDE220-2G2 VID: 00SerialNumber: 99999999999Model Type:SerialNumber (raw): 57 57 57 57 57 57 57 57 5757 57TestDate: 12-19-2002ExtModel: CDE220-2G2ModelNum (raw): 55 0 0 0 1HWVersion: 1PartNumber: 53 54 55 56 57BoardRevision: 1ChipRev: 1VendID: 0CookieVer: 2Chksum: 0xfb9eList of all disk drives:disk00: Normal (h02 c00 i00 l00 - mptsas) 476940MB(465.8GB)disk00/01: SYSTEM 5120MB( 5.0GB)mounted internallydisk00/02: SYSTEM 3072MB( 3.0GB)mounted internallydisk00/04: SYSTEM 2048MB( 2.0GB)mounted internallydisk00/05: SYSFS 32768MB( 32.0GB)mounted at /local1disk00/06: CDNFS 433917MB(423.7GB)mounted internallydisk01: Normal (h02 c00 i01 l00 - mptsas) 476940MB(465.8GB)disk01/01: SYSTEM 5120MB( 5.0GB)mounted internallydisk01/02: SYSTEM 3072MB( 3.0GB)mounted internallydisk01/04: SYSTEM 2048MB( 2.0GB)mounted internallydisk01/05: SYSFS 32768MB( 32.0GB)mounted at /local1<Output truncated>The following example shows how to display the DMI information:
ServiceEngine# show hardware dmi--------------------- DMI Information -------------# dmidecode 2.9SMBIOS 2.5 present.70 structures occupying 2793 bytes.Table at 0xCFF66000.Handle 0x0000, DMI type 0, 24 bytesBIOS InformationVendor: Phoenix Technologies LTDVersion: 1.2aRelease Date: 04/09/2009Address: 0xE3DD0Runtime Size: 115248 bytesROM Size: 2048 kBCharacteristics:PCI is supportedPNP is supportedBIOS is upgradeableBIOS shadowing is allowedESCD support is availableBoot from CD is supportedServiceEngine#Related Commands
show hosts
To view the hosts on your SE, use the show hosts command in EXEC configuration mode.
show hosts
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
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 3-40 describes the fields shown in the show hosts display.
Table 3-40 show hosts Field Descriptions
Domain names
Domain names used by the device to resolve the IP address.
Name Server(s)
IP address of the DNS1 name server or servers.
hostname
FQDN2 (that is, hostname and domain) of the current device.
inet address
IP address of the current host device.
aliases
Name configured for the current device based on the host command in Global configuration mode.
1 DNS = Domain Name Server
2 FQDN = fully qualified domain name
show interface
To display the hardware interface information, use the show interface command in EXEC configuration mode.
show interface {all | GigabitEthernet slot/port | PortChannel {1 [lacp] | 2 | 3 | 4} | standby group_num | TenGigabitEthernet slot/port}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-41 describes the fields shown in the show interface GigabitEthernet display.
Table 3-42 describes the fields shown in the show interface PortChannel display.
Table 3-43 describes the fields shown in the show interface standby display.
Table 3-44 describes the fields shown in the show interface TenGigabitEthernet display.
Related Commands
show inventory
To display the system inventory information, use the show inventory command in EXEC configuration mode.
show inventory
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
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 that 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 command in EXEC configuration mode to display the SE's UDI. On older SE models, use the show tech-support command in EXEC configuration mode 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 3-45 describes the fields shown in the show inventory display.
The following example shows that you must use the show tech-support command in EXEC configuration mode 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
Displays system information necessary for Cisco Technical Support to assist you with your SE.
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 command in EXEC configuration mode.
show ip access-list [acl_name | acl_num]
Syntax Description
Command Defaults
Displays information about all defined access lists.
Command Modes
EXEC configuration mode.
Usage Guidelines
Use the show ip access-list command in EXEC configuration mode 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
show ip bgp
To display the contents of a particular host in the BGP routing table, use the show ip bgp user command in user EXEC configuration mode.
show ip bgp {ip_address | prefix/prefix_length}
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
To display information about an entry in the BGP routing table (for example, 42.1.1.0/24), use the show ip bgp 42.1.1.0/24 command. To locate information by IP address (for example, 42.1.1.1), use the show ip bgp 42.1.1.1 command.
ServiceRouter# show ip bgp 42.1.1.0/24BGP routing table entry for 42.1.1.0/24, version 12Paths: (1 available, best # 1)Flags: on xmit-list, is in urib, is best urib routePath type: internal, path is valid, is best pathAS-Path: NONE, path sourced internal to AS192.168.86.3 (metric 0) from 192.168.86.3 (192.168.86.3)Origin incomplete, MED 0, localpref 100, weight 0Not advertised to any peerServiceRouter# show ip bgp 42.1.1.1BGP routing table entry for 42.1.1.0/24, version 12Paths: (1 available, best # 1)Flags: on xmit-list, is in urib, is best urib routePath type: internal, path is valid, is best pathAS-Path: NONE, path sourced internal to AS192.168.86.3 (metric 0) from 192.168.86.3 (192.168.86.3)Origin incomplete, MED 0, localpref 100, weight 0Not advertised to any peerServiceRouter#
The following sample output shows the display when the advertised community and the configured location community matches:
ServiceRouter# sh ip bgp 1.1.1.1BGP routing table entry for 1.1.1.1/32, version 4Paths: (1 available, best # 1)Flags: on xmit-list, is in urib, is best urib routePath type: internal, path is valid, is best pathAS-Path: NONE, path sourced internal to AS48.0.0.8 (metric 0) from 48.0.0.8 (1.1.1.1)Origin IGP, MED 0, localpref 100, weight 0Community: 1:1(location specific)The following sample output shows the display when the community is not advertised to any peer:
ServiceRouter# sh ip bgp 33.1.5.0BGP routing table entry for 33.1.5.0/24, version 4Paths: (1 available, best #1)Flags: on xmit-list, is in urib, is best urib routePath type: internal, path is valid, is best pathAS-Path: 2 , path sourced external to AS62.0.0.2 (metric 20) from 26.0.0.6 (10.1.1.1)Origin IGP, MED 0, localpref 100, weight 0Community: 5:5(location specific)Related Commands
clear ip bgp
Clears entries in the BGP route table.
router bgp
Configures a BGP routing process.
show ip bgp all
To display the contents of the BGP routing table, use the show ip bgp user command in user EXEC configuration mode.
show ip bgp {ip_address | prefix/prefix_length | all}
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following example is sample output from the show ip bgp command. The output shows the contents of the BGP routing table:
ServiceRouter# show ip bgp allBGP table version is 810399, local router ID is 172.20.168.47Status: s-suppressed, x-deleted, S-stale, d-dampened, h-history,*-valid, >-bestPath type: i-internal, e-external, c-confed, l-local, a-aggregate, r-redistOrigin codes: I - IGP, E - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*>i5.5.5.5/32 192.168.86.3 20 100 0 ?*>i12.1.1.1/32 192.168.86.3 20 100 0 ?*>i13.1.1.1/32 192.168.86.3 20 100 0 ?*>i14.1.1.1/32 192.168.86.3 20 100 0 ?*>i22.22.22.22/32 192.168.86.3 20 100 0 ?*>i40.1.1.0/24 192.168.86.3 0 100 0 ?*>i41.1.1.0/24 192.168.86.3 0 100 0 ?*>i42.1.1.0/24 192.168.86.3 0 100 0 ?*>i43.1.1.0/24 192.168.86.3 0 100 0 ?*>i45.1.1.0/24 192.168.86.3 0 100 0 ?-- More --Related Commands
clear ip bgp all
Clears all BGP neighbors.
router bgp
Configures a BGP routing process.
show ip bgp community
To display BGP routes that match a specified BGP community string, use the show ip bgp community user EXEC command.
show ip bgp community community_string
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
The show ip bgp community command is used to display BGP route information for a specified community string. To determine whether a community string exists in the BGP table, use the show ip bgp summary command. This command requires a Proximity Engine license.
The show ip bgp community command displays the origin AS and community values. Since the community list may be long, the output is limited to 80 columns. Other community unrelated fields longer display in this command; use the show ip bgp all command to display these fields.
Examples
In the following example, show ip bgp summary output can be used to determine that a community string 100:50 exists in the BGP table. The show ip bgp community command displays BGP route information for the community string 100:50. In this example, no route information is present for the community string 100:50:
ServiceRouter# show ip bgp summaryBGP router identifier 1.100.8.92, local AS number 23BGP table version is 2, IPv4 Unicast config peers 2, capable peers 00 network entries and 0 paths using 0 bytes of memoryBGP attribute entries [ 0/0 ] , BGP AS path entries [ 0/0 ]BGP community entries [ 0/0 ] , BGP clusterlist entries [ 0/0 ]BGP Location Communities: 100:50-100:100Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd192.168.82.1 4 23 0 0 0 0 0 4d10h Idle192.168.82.10 4 100 0 0 0 0 0 4d10h IdleServiceRouter# show ip bgp community 100:50BGP table version is 2, local router ID is 1.100.8.92Status: s-suppressed, x-deleted, S-stale, d-dampened, h-history, *-valid, >-bestPath type: i-internal, e-external, c-confed, l-local, a-aggregate, r-redistOrigin codes: I - IGP, E - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight PathServiceRouter#The following example shows the output for the show ip bgp community command:
ServiceRouter# show ip bgp communitysh ip bgp communityBGP table version is 32, local router ID is 1.100.9.206Status: s-suppressed, x-deleted, S-stale, d-dampened, h-history, *-valid, >-bestPath type: i-internal, e-external, c-confed, l-local, a-aggregate, r-redistCommunity: @ - source, # - targetNetwork Next Hop Origin AS Community List*>e2.4.1.0/24 192.168.82.2 33*>e3.1.4.0/24 192.168.82.2 23 @23:999*>e5.5.5.5/32 192.168.82.2 23 @23:999*>e12.1.1.0/24 192.168.82.1 23*>e12.1.1.1/32 192.168.82.2 23 @23:100 @#44:100*>e13.1.1.0/24 192.168.82.1 23*>e13.1.1.1/32 192.168.82.2 23 @#44:100*>e14.1.1.1/32 192.168.82.2 23 @#44:100*>e40.1.1.0/24 192.168.82.2 23 @23:999*>e41.1.1.0/24 192.168.82.2 23 @23:999*>e42.1.1.0/24 192.168.82.2 33*>e43.1.1.0/24 192.168.82.2 33*>e44.1.1.0/24 192.168.82.2 33*>e45.1.1.0/24 192.168.82.2 33*>e46.1.1.0/24 192.168.82.2 33*>e50.1.1.0/24 192.168.82.2 23 @23:999*>e51.1.1.0/24 192.168.82.2 23 @23:999*>e52.1.1.0/24 192.168.82.2 33*>e53.1.1.0/24 192.168.82.2 33*>e54.1.1.0/24 192.168.82.2 33*>e55.1.1.0/24 192.168.82.2 33*>e62.1.1.1/32 192.168.82.2 23 @23:999*>e62.62.62.0/24 192.168.82.2 23 @23:999*>e108.0.32.0/24 192.168.82.2 33*>e171.70.0.0/16 192.168.82.2 33*>e171.71.0.0/16 192.168.82.2 33*>e172.20.0.0/16 192.168.82.2 33*>e192.168.81.0/24 192.168.82.2 23*>e203.0.0.205/32 192.168.82.2 23 @23:999ServiceRouter#Related Commands
location community
BGP location-specific community configuration.
router bgp
Configures a BGP routing process.
show ip bgp ipv4 unicast
To display information relating to all IPv4 unicast routes in the BGP routing table, use the show ip bgp ipv4 unicast user command in user EXEC configuration mode.
show ip bgp ipv4 unicast
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
The show ip bgp ipv4 unicast command is used to display information relating to all IPv4 unicast routes in the BGP routing table. To see any route in the output of this command, BGP needs to connect successfully to at least one neighbor and receive route information from this neighbor. This command requires a Proximity Engine license.
Examples
The following is sample output from the show ip bgp ipv4 unicast command:
ServiceRouter# show ip bgp ipv4 unicastBGP table version is 810674, local router ID is 172.20.168.47Status: s-suppressed, x-deleted, S-stale, d-dampened, h-history, *-valid, >-bestPath type: i-internal, e-external, c-confed, l-local, a-aggregate, r-redistOrigin codes: I - IGP, E - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*>i5.5.5.5/32 192.168.86.3 20 100 0 ?*>i12.1.1.1/32 192.168.86.3 20 100 0 ?*>i13.1.1.1/32 192.168.86.3 20 100 0 ?*>i14.1.1.1/32 192.168.86.3 20 100 0 ?*>i22.22.22.22/32 192.168.86.3 20 100 0 ?*>i40.1.1.0/24 192.168.86.3 0 100 0 ?*>i41.1.1.0/24 192.168.86.3 0 100 0 ?*>i42.1.1.0/24 192.168.86.3 0 100 0 ?*>i43.1.1.0/24 192.168.86.3 0 100 0 ?*>i44.1.1.0/24 192.168.86.3 0 100 0 ?*>i45.1.1.0/24 192.168.86.3 0 100 0 ?*>i50.1.1.0/24 192.168.86.3 0 100 0 ?*>i51.1.1.0/24 192.168.86.3 0 100 0 ?-- More --Related Commands
clear ip bgp all
Clears all BGP neighbors.
router bgp
Configures a BGP routing process.
show ip bgp memory
To display memory usage information of the running BGP daemon, use the show ip bgp memory user command in user EXEC configuration mode.
show ip bgp memory
Syntax Description
This command has no keywords or arguments.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following example is sample output from the show ip bgp memory command:
ServiceRouter# show ip bgp memoryShared memory information for /topos_shm_bgp,Current-Size HWM Maximum-Size1727064 1727088 209715200BGP memory usage statsPrivate memoryTotal mallocs/frees/failed : 31/9/0Memory allocated : 4258692 bytesHWM allocated : 4262700 bytesShared memoryTotal mallocs/frees/failed : 19/3/0Memory requested/allocated : 1534799/1727064 bytesHWM requested/allocated : 1534819/1727088 bytesServiceRouter#Related Commands
show ip bgp neighbors
To display information about the TCP and BGP connections to neighbors, use the show ip bgp neighbors user command in user EXEC configuration mode.
show ip bgp neighbors [ip_address]
Syntax Description
Command Defaults
The output of this command displays information for all neighbors for IPv4 address family sessions only.
Command Modes
User EXEC configuration mode.
Usage Guidelines
The show ip bgp neighbors command is used to display BGP and TCP connection information for neighbor sessions. For BGP, this includes detailed neighbor attribute, capability, path, and prefix information. For TCP, this includes statistics related to BGP neighbor session establishment and maintenance.
This command requires a Proximity Engine license.
Examples
The following example is sample output from the show ip bgp neighbors command. The example shows the 192.168.86.3 neighbor. This neighbor is an internal BGP (iBGP) peer. This neighbor supports the route refresh and graceful restart capabilities.
ServiceRouter# show ip bgp neighborsBGP neighbor is 48.0.0.8, remote AS 2, ebgp link, Peer index 1BGP version 4, remote router ID 48.0.0.8BGP state = Established, up for 00:00:04Peer is directly attached, interface GigabitEthernet 2/0Last read 0.027030, hold time = 180, keepalive interval is 60 secondsLast written 00:00:01, keepalive timer expiry due 00:00:58Received 14265 messages, 0 notifications, 0 bytes in queueSent 5 messages, 0 notifications, 0 bytes in queueConnections established 1; dropped 0Last reset by us never, due to process restartLast reset by peer never, due to process restartNeighbor capabilities:Dynamic capability: advertised (mp, refresh, gr)Dynamic capability (old): advertisedAddress family IPv4 Unicast: advertisedCapabilities parameter not sent by neighborExchanging IPv4 Unicast NLRI by defaultFor address family: IPv4 UnicastBGP table version 1, neighbor version 101573142640 accepted paths consume 5135040 bytes of memory0 sent pathsLocal host: 48.0.0.4, Local port: 179Foreign host: 48.0.0.8, Foreign port: 2867fd = 42ServiceRouter#To display information for all BGP neighbors, use the show ip bgp neighbors command. In this example, the Proximity Engine has two BGP peers, 192.168.86.3 and 192.168.86.87.
ServiceRouter# show ip bgp neighborsBGP neighbor is 192.168.86.3, remote AS 23, ibgp link, Peer index 1BGP version 4, remote router ID 192.168.86.3BGP state = Established, up for 1d05hPeer is directly attached, interface GigabitEthernet 2/0Last read 0.868226, hold time = 180, keepalive interval is 60 secondsLast written 00:00:09, keepalive timer expiry due 00:00:50Received 78444 messages, 0 notifications, 0 bytes in queueSent 1788 messages, 0 notifications, 0 bytes in queueConnections established 1; dropped 0Last reset by us never, due to process restartLast reset by peer never, due to process restartNeighbor capabilities:Dynamic capability: advertised (mp, refresh, gr)Dynamic capability (old): advertisedRoute refresh capability (new): advertised receivedRoute refresh capability (old): advertised receivedAddress family IPv4 Unicast: advertised receivedFor address family: IPv4 UnicastBGP table version 1, neighbor version 8107498518 accepted paths consume 613296 bytes of memory0 sent pathsLocal host: 192.168.86.47, Local port: 58920Foreign host: 192.168.86.3, Foreign port: 179fd = 35BGP neighbor is 192.168.86.87, remote AS 23, ibgp link, Peer index 2BGP version 4, remote router ID 0.0.0.0BGP state = Idle, down for 00:00:10Last read never, hold time = 180, keepalive interval is 60 secondsLast written never, keepalive timer not runningReceived 0 messages, 0 notifications, 0 bytes in queueSent 0 messages, 0 notifications, 0 bytes in queueConnections established 0; dropped 0Last reset by us never, due to process restartLast reset by peer never, due to process restartFor address family: IPv4 UnicastBGP table version 1, neighbor version 00 accepted paths consume 0 bytes of memory0 sent pathsNo established BGP session with peerRelated Commands
clear ip bgp all
Clears all BGP neighbors.
router bgp
Configures a BGP routing process.
show ip bgp nexthop-database
To display the next-hop database information in the BGP routing table, use the show ip bgp nexthop-database user command in user EXEC configuration mode.
show ip bgp nexthop-database
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
The show ip bgp nexthop-database command is used to display the BGP next-hop information, including IGP cost, IGP route type, IGP preference, interface to reach this next-hop, time of last next-hop resolution, and reachability. This command requires a Proximity Engine license.
Examples
The following example is sample output from the show ip bgp nexthop-database command:
ServiceRouter# show ip bgp nexthop-databaseNexthop: 192.168.86.3, Refcount: 4021, IGP cost: 0IGP Route type: 0, IGP preference: 0Attached nexthop: 192.168.86.3, Interface: GigabitEthernet 2/0Nexthop is attached not-local reachableNexthop last resolved: 1d05h, using 192.168.86.0/24Metric next advertise: NeverServiceRouter#Related Commands
router bgp
Configures a BGP routing process.
show ip bgp all
Displays BGP route table information.
show ip bgp summary
To display the status of all BGP connections, use the show ip bgp summary user command in user EXEC configuration mode.
show ip bgp summary
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
The show ip bgp summary command is used to display BGP path, prefix, and attribute information for all connections to BGP neighbors.
A path is a route to a given destination. By default, BGP only installs a single path for each destination. If multipath routes are configured, BGP installs a path for each multipath route, and only one multipath route is marked as the best path. A prefix is an IP address and network mask. It can represent an entire network, a subset of a network, or a single host route.
BGP attribute and cache entries are displayed individually and in combinations that affect the best path selection process. The fields for this output are displayed when the related BGP feature is configured or when the BGP attribute is received. Memory usage is displayed in bytes.
This command requires a Proximity Engine license.
Examples
The following example is sample output from the show ip bgp summary command:
ServiceRouter# show ip bgp summaryBGP router identifier 1.100.8.40, local AS number 65204BGP table version is 567, IPv4 Unicast config peers 1, capable peers 180 network entries and 80 paths using 16960 bytes of memoryBGP attribute entries [ 10/1600 ] , BGP AS path entries [ 10/174 ]BGP community entries [ 10/160 ] , BGP clusterlist entries [ 0/0 ]location community 100:1535 200:4566 123:3000-123:4000 350:2530 300:500-300:1000Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd192.168.52.10 4 65204 4363 4289 567 0 0 00:00:59 80ServiceRouter#Related Commands
router bgp
Configures a BGP routing process.
show ip bgp all
Displays BGP route table information.
show ip interface
To display the IP interface state and address/mask for all interfaces, use the show ip interface command in user EXEC configuration mode.
show ip interface
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command is used to display a Summary of the IP interface status and configuration.
Examples
The following example is sample output from the show ip bgp summary command:
ServiceRouter# show ip interface briefInterface IP Address Interface StatusPortChannel 1 3.1.14.71 protocol-up/link-up/admin-upPortChannel 2 4.0.8.12 protocol-up/link-up/admin-upServiceRouter#show ip ospf
To display general information about OSPF routing processes, use the show ip ospf command in privileged EXEC configuration mode.
show ip ospf
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show ip ospf command:
ServiceRouter# show ip ospfOSPF information:Routing Process p1 with ID 172.20.168.41 context defaultStateful High Availability enabledSupports only single TOS(TOS0) routesSupports opaque LSAReference Bandwidth is 40000 MbpsInitial Inter-SPF schedule delay 200.000 msecs,backoff factor 2, capped at 1000.000 msecs,minimum Inter-SPF delay reset after 5000.000 msecsMinimum hold time for Router LSA throttle 5000.000 msMinimum hold time for Network LSA throttle 5000.000 msMinimum LSA arrival 1000.000 msecMaximum paths to destination 8Originating router LSA with maximum metricCondition: AlwaysNumber of external LSAs 22, checksum sum 0xdc4baNumber of opaque AS LSA 0, checksum sum 0Number of areas is 1, 1 normal, 0 stub, 0 nssaNumber of active areas is 1, 1 normal, 0 stub, 0 nssaArea BACKBONE(0)Area has existed for 00:00:02Interfaces in this area: 1 Active interfaces: 1No authentication availableSPF calculation has run 2 timesLast SPF ran for 0.000054sRouter LSA throttle timer due in 00:00:02Area ranges areNumber of LSAs: 498, checksum sum 0xf5eb6bServiceRouter#Table 3-46 describes the significant fields included in the display above.
Related Commands
show ip ospf border-routers
To display general information about OSPF border routers, use the show ip ospf border-routers command in privileged EXEC configuration mode.
show ip ospf border-routers
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show ip ospf command:
ServiceRouter# show ip ospf border-routersOSPF Process ID p1 context default, Internal Routing TableCodes: i - Intra-area route, I - Inter-area routeintra 192.168.0.86 [65535], ASBR, Area 0, SPF 3via 192.168.86.3, GigabitEthernet 2/0Related Commands
show ip ospf database
To display lists of information related to the OSPF database for a specific router, use the show ip ospf database user command in EXEC configuration mode. The various forms of this command deliver information about different OSPF link-state advertisements (LSAs).
show ip ospf database [adv-router [ip_address]] [detail] | [asbr-summary] [link_state_id] [detail] | [database-summary] | [detail] | [external] [link_state_id] [detail] | [network] [link_state_id] [detail] | [nssa-external] [link_state_id] [detail] | [router] [link_state_id] [detail] | [self-originate] [detail] | [summary] [link_state_id] [detail]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show ip ospf database command when no arguments or keywords are used:
ServiceRouter# show ip ospf databaseOSPF Router with ID (172.20.168.88) (Process ID p1 context default)Router Link States (Area 0)Link ID ADV Router Age Seq# Checksum Link Count172.20.168.88 172.20.168.88 1686 0x80000006 0x4531 1192.168.0.4 192.168.0.4 1284 0x8000000a 0x80cf 1Network Link States (Area 0)Link ID ADV Router Age Seq# Checksum192.168.20.2 192.168.0.4 1284 0x80000003 0x49d2ServiceRouter#Table 3-47 describes the significant fields included in the display above.
The following is sample output from the show ip ospf database command with the
asbr-summary keyword:ServiceRouter# show ip ospf database asbr-summaryOSPF Router with ID (172.20.168.41) (Process ID p1 context default)Summary ASBR Link States (Area 0)Link ID ADV Router Age Seq# Checksum193.0.50.3 193.0.50.3 1281 0x800007a8 0x86d4193.0.150.3 193.0.150.3 1281 0x800007ac 0x6f1fSummary ASBR Link States (Area 10)Link ID ADV Router Age Seq# Checksum193.0.50.3 172.20.168.41 345 0x8000002a 0x0a95193.0.150.3 172.20.168.41 345 0x8000002a 0xb981ServiceRouter#Table 3-48 describes the significant fields included in the display above.
The following is sample output from the show ip ospf database command with the external keyword:
ServiceRouter# show ip ospf database externalOSPF Router with ID (172.20.168.41) (Process ID p1 context default)Type-5 AS External Link StatesLink ID ADV Router Age Seq# Checksum Tag30.0.0.0 193.0.50.3 1580 0x800007ab 0x7e24 030.0.0.0 193.0.150.3 1580 0x800007ae 0xb981 030.0.1.0 193.0.50.3 1580 0x800007ab 0x732e 030.0.1.0 193.0.150.3 1580 0x800007ae 0xae8b 030.0.2.0 193.0.50.3 1580 0x800007ab 0x6838 030.0.2.0 193.0.150.3 1580 0x800007ae 0xa395 030.0.3.0 193.0.50.3 1580 0x800007ab 0x5d42 030.0.3.0 193.0.150.3 1580 0x800007ae 0x989f 0ServiceRouter#Table 3-49 describes the significant fields included in the display above.
The following is sample output from the show ip ospf database command with the network keyword:
ServiceRouter# show ip ospf database networkOSPF Router with ID (172.20.168.41) (Process ID p1 context default)Network Link States (Area 0)Link ID ADV Router Age Seq# Checksum192.168.78.4 100.73.1.4 312 0x80000135 0xeaeb192.168.82.4 100.73.1.4 1311 0x8000009b 0xbc01193.0.50.2 193.0.50.3 57 0x800007ad 0x7cec193.0.61.2 193.0.61.3 57 0x80000fe4 0x0d5e193.0.72.2 193.0.72.3 57 0x80000fe4 0x3906193.0.83.2 193.0.83.3 57 0x800007a9 0xf362193.0.84.2 193.0.83.3 57 0x800007a9 0xc9a1ServiceRouter#Table 3-50 describes the significant fields included in the display above.
The following is sample output from the show ip ospf database command with the router keyword:
ServiceRouter# show ip ospf database routerOSPF Router with ID (172.20.168.41) (Process ID p1 context default)Router Link States (Area 0)Link ID ADV Router Age Seq# Checksum Link Count1.1.78.8 1.1.78.8 525 0x800007af 0x801b 21.1.78.9 1.1.78.9 525 0x800007ab 0x7ce8 2100.73.1.4 100.73.1.4 780 0x800003bd 0x2dd9 2172.20.168.41 172.20.168.41 1388 0x80000030 0x67fa 1172.20.168.83 172.20.168.83 1179 0x80000039 0xfddd 1192.168.82.1 192.168.82.1 1299 0x8000006f 0x06fe 2Router Link States (Area 10)Link ID ADV Router Age Seq# Checksum Link Count172.20.168.41 172.20.168.41 628 0x8000002c 0xf99d 1ServiceRouter#Table 3-51 describes the significant fields included in the display above.
The following is sample output from the show ip ospf database command with the summary keyword:
ServiceRouter# show ip ospf database summaryOSPF Router with ID (172.20.168.41) (Process ID p1 context default)Summary Network Link States (Area 0)Link ID ADV Router Age Seq# Checksum20.0.0.0 193.0.50.3 1325 0x800007ac 0xa49620.0.0.0 193.0.150.3 1326 0x800007af 0xdff320.0.1.0 193.0.50.3 1325 0x800007ac 0x99a020.0.1.0 193.0.150.3 1326 0x800007af 0xd4fd20.0.2.0 193.0.50.3 1325 0x800007ac 0x8eaa20.0.2.0 193.0.150.3 1326 0x800007af 0xc908Summary Network Link States (Area 10)Link ID ADV Router Age Seq# Checksum192.168.78.0 172.20.168.41 370 0x8000002b 0xc127ServiceRouter#Table 3-52 describes the significant fields included in the display above.
The following is sample output from the show ip ospf database command with the database-summary keyword:
ServiceRouter# show ip ospf database database-summaryOSPF Router with ID (172.20.168.41) (Process ID p1 context default)Area 0 database summaryLSA Type CountOpaque Link 0Router 156Network 296Summary Network 41Summary ASBR 2Type-7 AS External 0Opaque Area 0Subtotal 495Area 10 database summaryLSA Type CountOpaque Link 0Router 1Network 0Summary Network 1Summary ASBR 2Type-7 AS External 0Opaque Area 0Subtotal 4Process p1 database summaryLSA Type CountOpaque Link 0Router 157Network 296Summary Network 42Summary ASBR 4Type-7 AS External 0Opaque Area 0Type-5 AS External 20Opaque AS 0Total 519ServiceRouter#Table 3-53 describes the significant fields included in the display above.
Related Commands
show ip ospf interface
To display OSPF-related interface information, use the show ip ospf interface command in user EXEC configuration mode.
show ip ospf interface
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following example shows how to display sample output from the show ip ospf interface command.
ServiceRouter# show ip ospf interfaceInterface: GigabitEthernet 1/0 is up, line protocol is upIP address 192.168.78.41/24, Process ID p1 context default, area 0State BDR, Network type BROADCAST, cost 1Index 1, Transmit delay 1 sec, Router Priority 1Designated Router ID: 100.73.1.4, address: 192.168.78.4Backup Designated Router ID: 172.20.168.41, address: 192.168.78.414 Neighbors, flooding to 2, adjacent with 2Timer intervals: Hello 10, Dead 40, Wait 40, Retransmit 5Hello timer due in 00:00:01No authenticationNumber of link LSAs: 0, checksum sum 0GigabitEthernet 1/0 is up, line protocol is upIP address 172.20.168.41/24, Process ID p1 context default, area 10State DR, Network type BROADCAST, cost 1Index 2, Transmit delay 1 sec, Router Priority 1Designated Router ID: 172.20.168.41, address: 172.20.168.41No backup designated router on this network0 Neighbors, flooding to 0, adjacent with 0Timer intervals: Hello 10, Dead 40, Wait 40, Retransmit 5Hello timer due in 00:00:07No authenticationNumber of link LSAs: 0, checksum sum 0ServiceRouter#Table 3-54 describes the significant fields included in the display above.
Related Commands
show ip ospf memory
To display memory usage of the OSPF process, use the show ip ospf memory command in user EXEC configuration mode.
show ip ospf memory
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following example shows how to display sample output from the show ip ospf memory command.
ServiceRouter# show ip ospf memoryOSPF memory usage statistics:Shared memory information for /topos_shm_ospf,Current-Size HWM Maximum-Size48 1088240 4194304OSPF Process ID p1, Memory statisticsByte usage: needed 0, overhead 0, using 0 bytesAllocations: current 0, created 0, failed 0, free 0Bitfields: current 0, created 0, failed 0, free 0, using 0 bytesSlabs: current 0, created 0, failed 0, free 0, using 8 bytesIndex failure: Interface 0, Neighbor 0CurBytes Current HWM Malloc Free Description728 1 1 1 0 area119712 516 520 526 10 lsdb entry320 2 2 2 0 ASBR route984 1 1 1 0 ospf interface16 1 1 1 0 backup safety memory48136 515 520 9465 8950 lsa60 1 2 2 1 lsa0 0 197 517 517 lsa0 0 2 2 2 redist work1048576 1 1 1 0 backup memory4192 1 1 1 0 ospf subrouter2920 1 1 1 0 ager wheel10100 11 11 13 2 pak buffer80 1 1 1 0 ospf table48 1 1 1 0 ager wheel holder2784 3 3 3 0 neighbor24 1 1 1 0 network configuration entry
Related Commands
show ip ospf neighbor
To display OSPF neighbor information, use the show ip ospf neighbor command in user EXEC configuration mode.
show ip ospf neighbor [neighbor_id | detail | summary]
Syntax Description
neighbor_id
(Optional) Neighbor ID or Router ID.
detail
(Optional) Displays details of neighbors.
summary
(Optional) Displays a summary of neighbors.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show ip ospf neighbor command. It shows a single line of summary information for each neighbor:
ServiceRouter# show ip ospf neighborsOSPF Process ID p1 context defaultTotal number of neighbors: 2Neighbor ID Pri State Up Time Address Interface100.73.1.4 1 FULL/DR 1d00h 192.168.78.4 GigabitEthernet 1/0172.20.168.83 1 FULL/DROTHER 14:42:44 192.168.78.83 GigabitEthernet 1/0ServiceRouter#The following is sample output showing summary information about the neighbor that matches the specified neighbor ID:
ServiceRouter# show ip ospf neighbors 100.73.1.4OSPF Process ID p1 context defaultTotal number of neighbors: 4Neighbor ID Pri State Up Time Address Interface100.73.1.4 1 FULL/DR 1d00h 192.168.78.4 GigabitEthernet 1/0ServiceRouter#The following is sample output from the show ip ospf neighbor detail command:
ServiceRouter# show ip ospf neighbors detailNeighbor 100.73.1.4, interface address 192.168.78.4Process ID p1 context default, in area 0 via interface GigabitEthernet 1/0State is FULL, 6 state changes, last change 1d00hNeighbor priority is 1DR is 192.168.78.4 BDR is 192.168.78.41Hello options 0x12, dbd options 0x52Last non-hello packet received 0.301737Dead timer due in 00:00:40Neighbor 172.20.168.83, interface address 192.168.78.83Process ID p1 context default, in area 0 via interface GigabitEthernet 1/0State is FULL, 4 state changes, last change 14:47:09Neighbor priority is 1DR is 192.168.78.4 BDR is 192.168.78.41Hello options 0x2, dbd options 0x42Last non-hello packet received 00:00:08Dead timer due in 00:00:34ServiceRouter#The following is sample output from the show ip ospf neighbor summary command:
ServiceRouter# show ip ospf neighbors summaryOSPF Process ID p1 context default, Neighbor SummaryInterface Down Attempt Init TwoWay ExStart Exchange Loading Full TotalTotal 0 0 0 0 0 0 0 2 2GigabitEthernet 1/0 0 0 0 0 0 0 0 2 2ServiceRouter#Table 3-55 describes the significant fields included in the display above.
Related Commands
show ip ospf request-list
To display a list of all link-state advertisements (LSAs) requested by a router, use the show ip ospf request-list command in EXEC configuration mode.
show ip ospf request-list neighbor interface
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The output is useful in debugging OSPF routing operations. This command requires a Proximity Engine license.
Examples
The following example shows how to display sample output from the show ip ospf request-list command, with neighbor router ID set to 100.73.1.4, and interface set to `GigabitEthernet 1/0':
ServiceRouter# show ip ospf request-list 100.73.1.4 GigabitEthernet 1/0OSPF Process ID p1 context defaultNeighbor 100.73.1.4, interface GigabitEthernet 1/0, address 192.168.78.41 LSAs on request-listType LSID Adv Rtr Seq No Checksum Age1 192.168.1.12 192.168.1.12 0x8000020D 0x6572 5ServiceRouter#Related Commands
show ip ospf retransmission-list
To display a list of all link-state advertisements (LSAs) waiting to be re-sent, use the show ip ospf retransmission-list command in EXEC configuration mode.
show ip ospf retransmission-list neighbor interface
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
The output of this command is useful in debugging OSPF routing operations. This command requires a Proximity Engine license.
Examples
The following example shows how to display sample output from the show ip ospf retransmission-list command, with neighbor router ID set to `100.73.1.4', and interface set to `GigabitEthernet 1/0':
ServiceRouter# show ip ospf retransmission-list 100.73.1.4 GigabitEthernet 1/0OSPF Process ID p1 context defaultNeighbor 100.73.1.4, interface GigabitEthernet 1/0, address 192.168.78.4Link state retransmission due in 00:00:04Type LSID Adv Rtr Seq No Checksum Age1 172.20.168.41 172.20.168.41 0x80000044 0x3f0f 0ServiceRouter#Related Commands
show ip ospf route
To display the OSPF RSPF route for OSPF routes, use the show ip ospf route command in EXEC configuration mode.
show ip ospf route [all | router_id]
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show ip ospf route command:
ServiceRouter# show ip ospf routeOSPF Process ID p1 context default, Routing Table(D) denotes route is directly attached (R) denotes route is in RIB20.0.0.0/24 (inter) area 0via 192.168.78.8/GigabitEthernet 1/0, cost 65645via 192.168.78.9/GigabitEthernet 1/0, cost 6564520.0.1.0/24 (inter) area 0via 192.168.78.8/GigabitEthernet 1/0, cost 65645via 192.168.78.9/GigabitEthernet 1/0, cost 6564520.0.2.0/24 (inter) area 0via 192.168.78.8/GigabitEthernet 1/0, cost 65645via 192.168.78.9/GigabitEthernet 1/0, cost 6564520.0.3.0/24 (inter) area 0via 192.168.78.8/GigabitEthernet 1/0, cost 65645via 192.168.78.9/GigabitEthernet 1/0, cost 6564520.0.4.0/24 (inter) area 0via 192.168.78.8/GigabitEthernet 1/0, cost 65645via 192.168.78.9/GigabitEthernet 1/0, cost 6564520.0.5.0/24 (inter) area 0via 192.168.78.8/GigabitEthernet 1/0, cost 65645via 192.168.78.9/GigabitEthernet 1/0, cost 6564520.0.6.0/24 (inter) area 0via 192.168.78.8/GigabitEthernet 1/0, cost 65645via 192.168.78.9/GigabitEthernet 1/0, cost 65645192.168.78.0/24 (intra)(D) area 0via 192.168.78.41/GigabitEthernet 1/0*, cost 65535192.168.79.0/24 (intra) area 0via 192.168.78.4/GigabitEthernet 1/0, cost 65537192.168.82.0/24 (intra) area 0via 192.168.78.4/GigabitEthernet 1/0, cost 65536Related Commands
show ip ospf rspf route
To display OSPF reverse shortest path first (RSPF) from a specific router(s), use the show ip ospf rspf route command in EXEC configuration mode.
show ip ospf rspf route [router_id]
Syntax Description
Command Defaults
If no router ID is specified, displays OSPF RSPF information for all router IDs.
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command shows cached RSPF routing information because of previous proximity request. This command requires a Proximity Engine license.
Examples
The following is sample output from the show ip ospf rspf route command:
ServiceRouter# show ip ospf rspf routeAdvertising Router SPF Version Cache Hit Age172.20.168.41 2292 1 00:00:04ServiceRouter#Table 3-56 describes the significant fields included in the display above
.
The following example shows the spf cost of each route from router 172.20.168.41:
ServiceRouter# show ip ospf rspf route 172.20.168.41OSPF Process ID p1 context default, Routing Table(D) denotes route is directly attached (R) denotes route is in RIB192.168.78.0/24 area 0, spf cost 0192.168.79.0/24 area 0, spf cost 3192.168.82.0/24 area 0, spf cost 1193.0.50.0/24 area 0, spf cost 10193.0.51.0/24 area 0, spf cost 30193.0.52.0/24 area 0, spf cost 30193.0.53.0/24 area 0, spf cost 30193.0.54.0/24 area 0, spf cost 30193.0.55.0/24 area 0, spf cost 30193.0.56.0/24 area 0, spf cost 30193.0.57.0/24 area 0, spf cost 30193.0.58.0/24 area 0, spf cost 30193.0.59.0/24 area 0, spf cost 30193.0.60.0/24 area 0, spf cost 30ServiceRouter#Related Commands
show ip ospf traffic
To display OSPF traffic statistics, use the show ip ospf traffic command in user EXEC configuration mode.
show ip ospf traffic
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show ip ospf traffic command:
ServiceRouter# show ip ospf trafficPacket Counter:OSPF Process ID p1 context default, Packet Counters (cleared 00:04:33 ago)Total: 324 in, 160 outLSU transmissions: first 1, rxmit 0, for req 0Flooding packets output throttled (IP/tokens): 0 (0/0)Ignored LSAs: 0, LSAs dropped during SPF: 0LSAs dropped during graceful restart: 0Errors: drops in 0, drops out 0, errors in 0,errors out 0, hellos in 0, dbds in 0,lsreq in 0, lsu in 0, lsacks in 0,unknown in 0, unknown out 0, no ospf 0,bad version 0, bad crc 0, dup rid 0,dup src 0, invalid src 0, invalid dst 0,no nbr 0, passive 0, wrong area 0,pkt length 0, nbr changed rid/ip addr 0bad auth 0hellos dbds lsreqs lsus acksIn: 84 0 0 118 122Out: 31 101 0 1 27ServiceRouter#Table 3-57 describes the significant fields included in the display above.
Related Commands
show ip proximity algorithm
To display the proximity algorithm options currently in use by this Proximity Engine, use the show ip proximity algorithm command in user EXEC configuration mode.
show ip proximity algorithm
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
When BGP is configured as the routing protocol, the output from show ip proximity algorithm has information on the following:
•
•
•
These threes options are enabled with the proximity algorithm bgp command. For information on these options, see the proximity algorithm bgp command.
Examples
The following example shows sample output from the show ip proximity algorithm command.
ServiceRouter> show ip proximity algorithmProximity algorithm: bgp communityServiceRouter#Related Commands
proximity algorithm bgp
Enables a BGP proximity algorithm option for the Proximity Engine.
proximity engine enable
Enables the Proximity Engine.
show ip proximity servers
To display the interface addresses and hostnames of the Proximity Servers currently in use by this Proximity Engine, use the show ip proximity servers command in user EXEC configuration mode.
show ip proximity servers
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command shows other proximity servers and their interface addresses for use in redirection. The DHT ring must be enabled between these proximity servers using the router srp command for the DHT ring to be formed. These servers are used for redirection only if the proximity algorithm bgp redirect command is enabled.
Examples
The following example shows sample output from the show ip proximity servers command.
ServiceRouter# show ip proximity serversProximity servers:Hostname: Hostname not foundIP0: 3.1.4.14IP1: 192.168.82.10Hostname: Hostname not foundIP0: 3.1.4.12IP1: 192.168.82.199Hostname: SN-CDSMIP0: 192.168.86.77IP1: 1.100.8.190ServiceRouter#Related Commands
show ip rib clients
To display details of all the routing protocol instances that are clients of the RIB, use the show ip rib clients command in user EXEC configuration mode.
show ip rib clients
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command is used to display detailed information about all routing protocol instances that have registered with RIB.
Examples
The following example shows sample output from the show ip rib clients command. The output shows three routing protocol instances that have registered with RIB, along with the results of various counters in RIB.
ServiceRouter# show ip rib clientsDisplaying information for all clients:CLIENT: directepid: 352 MTS SAP: -1 MRU cache hits/misses: 3/1Routing Instances:route context "default" table "default"Messages received:Register : 1 Add-one-route : 3 Denotify-request : 1Messages sent:CLIENT: isis-abcepid: 19498 MTS SAP: 1666 MRU cache hits/misses: 1137375/1Routing Instances:route context "default" table "default"Messages received:Register : 1 Add-route : 52647 Delete-route : 48872Notify-request : 1Messages sent:Add-route-ack : 52647 Delete-route-ack : 48872CLIENT: isis-abc-teepid: 19498 MTS SAP: 1666 MRU cache hits/misses: 0/0Messages received:Register : 1Messages sent:Related Commands
show ip rib memory
To display the memory usage information of the RIB, use the show ip rib memory command in user EXEC configuration mode.
show ip rib memory
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command is used to display detailed information about the memory usage of the RIB (for example, shared memory information and memory used by routes).
Examples
The following example shows sample output from the show ip rib memory command:
ServiceRouter# show ip rib memoryShared memory information for /topos_shm_urib,Current-Size HWM Maximum-Size3897168 3897168 131072000allocated:7 alloc errs:0URIB slab block statistics:alloc fail cumm alloc cumm freed high-waterurib routes 0 5 0 5urib nibs 0 1 0 1urib rte nibs 0 330 325 5urib tib nibs 0 1 0 1urib next hops 0 330 325 5urib chlst elms 0 5 0 5urib nhlfes 0 0 0 0crib nodes 0 0 0 0crib routes 0 0 0 0crib uroutes 0 0 0 0crib next hops 0 0 0 0URIB slab statistics:allocated cumm alloc cumm freed high-waterurib routes 8538 8538 0 8538urib nibs 2 2 0 2urib rte nibs 8515 550792 542277 8538urib tib nibs 2 2 0 2urib next hops 8515 550792 542277 8538urib chlst elms 8538 8538 0 8538urib nhlfes 0 0 0 0crib nodes 0 0 0 0crib routes 0 0 0 0crib uroutes 0 0 0 0crib next hops 0 0 0 0Related Commands
show ip rib recursive-next-hop
To display IP recursive next-hop information from the RIB, use the show ip rib recursive-next-hop command in user EXEC configuration mode.
show ip rib ip recursive-next-hop [ip_addr]
Syntax Description
Command Defaults
In no ip_addr argument is specified, show ip rib recursive-next-hop displays information for all recursive next-hops for this Proximity Engine.
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command is used to display IP recursive next-hop information from the RIB.
Examples
The following example shows sample output from the show ip rib recursive-next-hop command.
ServiceRouter# show ip rib recursive-next-hopIP Recursive Next-Hop Table192.168.79.3/32, uptime: 3d22h, bgp-301192.168.82.1/32, uptime: 3d22h, bgp-301ServiceRouter> show ip rib recursive-next-hop 192.168.82.1IP Recursive Next-Hop Table192.168.82.1/32, uptime: 3d22h, bgp-301ServiceRouter#In the output, bgp-301 is the number of the BGP Autonomous System containing the recursive next hop.
Related Commands
show ip rib route
To display IP RIB route information, use the show ip rib route command in user EXEC configuration mode.
show ip rib route [ip_address | bgp | direct | isis | ospf | static | summary]
Syntax Description
Command Defaults
In no ip_address argument is specified, show ip rib route displays information for all routes for this Proximity Engine.
Command Modes
User EXEC configuration mode.
Examples
The following example shows sample output from the show ip rib route command:
ServiceRouter# show ip rib routeIP Urib Route Table:'*' denotes best ucast next-hop '**' denotes best mcast next-hop' [ x/y ] ' denotes [ preference/metric ]1.1.1.1/32, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 115/20 ] , 04:34:54, isis-p1, L2 2.2.2.2/32, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 115/30 ] , 04:34:54, isis-p1, L2 2.8.1.0/24, 1 ucast next-hops, 0 mcast next-hops, attached*via 2.8.1.8, GigabitEthernet 1/0, [ 0/0 ] , 04:35:13, direct 12.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 115/20 ] , 04:34:54, isis-p1, L2 20.0.0.0/16, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 200/0 ] , 04:34:53, bgp-209, internal, tag 209extended route information: AS Hops 0, BGP peer AS 209 101.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 200/0 ] , 04:35:03, bgp-209, internal, tag 65209extended route information: AS Hops 1, BGP peer AS 209 102.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 200/0 ] , 04:34:53, bgp-209, internal, tag 65209extended route information: AS Hops 1, BGP peer AS 209 103.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 200/0 ] , 04:34:53, bgp-209, internal, tag 65209extended route information: AS Hops 1, BGP peer AS 209 201.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 200/0 ] , 04:35:03, bgp-209, internal, tag 209extended route information: AS Hops 0, BGP peer AS 209 202.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 200/0 ] , 04:34:53, bgp-209, internal, tag 209extended route information: AS Hops 0, BGP peer AS 209 203.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops, attached*via 203.0.0.205, GigabitEthernet 2/0, [ 0/0 ] , 04:35:13, direct 204.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 115/30 ] , 04:34:54, isis-p1, L2 205.0.0.0/8, 1 ucast next-hops, 0 mcast next-hops*via 203.0.0.1, GigabitEthernet 2/0, [ 115/20 ] , 04:34:54, isis-p1, L2ServiceRouter#The following example shows how to display the static route configuration in URIB:
ServiceRouter# show ip rib route staticIP Urib Route Table:'*' denotes best ucast next-hop '**' denotes best mcast next-hop'[x/y]' denotes [preference/metric]10.1.1.0/24, 1 ucast next-hops, 0 mcast next-hops*via GigabitEthernet 2/0, [1/0], 00:26:07, static10.1.2.0/24, 1 ucast next-hops, 0 mcast next-hops*via GigabitEthernet 2/0, [1/0], 00:26:07, static10.1.3.0/24, 1 ucast next-hops, 0 mcast next-hops*via GigabitEthernet 2/0, [1/0], 00:26:07, static10.1.4.0/24, 1 ucast next-hops, 0 mcast next-hops*via GigabitEthernet 2/0, [1/0], 00:26:07, staticRelated Commands
show ip rib unresolved-next-hop
To display unresolved next-hop information from the RIB, use the show ip rib unresolved-next-hop command in user EXEC configuration mode.
show ip rib unresolved-next-hop [ip_address]
Syntax Description
Command Defaults
In no ip_address argument is specified, show ip rib recursive-next-hop displays information for all unresolved next-hops for this Proximity Engine.
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command is used to display unresolved next-hop information from the RIB. It is normal to have zero unresolved next-hops. When incoming packets contain a next-hop address that cannot be resolved (that is, cannot be found during the route lookup), the count of unresolved next-hops increases.
Examples
The following example shows sample output from the show ip rib unresolved-next-hop command.
ServiceRouter# show ip rib unresolved-next-hopInformation about unresolved next-hops for context "default"Proximity EngineNumber of unresolved nexthops: 0ServiceRouter#Related Commands
show ip routes
To display the IP routing table, use the show ip routes command in EXEC configuration mode.
show ip routes
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The show ip routes command displays the policy routing tables. The main routing table is always displayed first, and if any policy routing tables have been instantiated, they are also displayed after the main table.
Examples
The show ip routes command displays the IP routing table that shows actual routes in the system.
Table 3-58 describes the fields shown in the show ip routes display.
.
The following example shows sample output from the show ip routes command:
ServiceRouter# sh ip routesDestination Gateway Netmask---------------- ---------------- ----------------202.0.0.22 203.0.0.1 255.255.255.25520.0.40.1 2.8.1.204 255.255.255.25512.0.0.2 203.0.0.1 255.255.255.25520.0.60.1 2.8.1.206 255.255.255.25513.0.0.3 203.0.0.1 255.255.255.2552.2.2.2 203.0.0.1 255.255.255.255204.0.0.2 203.0.0.1 255.255.255.25520.0.50.1 2.8.1.205 255.255.255.25513.0.0.1 203.0.0.1 255.255.255.25512.0.0.1 203.0.0.1 255.255.255.25520.0.10.1 2.8.1.201 255.255.255.25520.0.70.1 2.8.1.207 255.255.255.255201.0.0.12 203.0.0.1 255.255.255.25520.0.30.1 2.8.1.203 255.255.255.25520.0.20.1 2.8.1.202 255.255.255.25520.0.80.1 2.8.1.208 255.255.255.2552.8.1.0 0.0.0.0 255.255.255.020.0.0.0 2.8.1.201 255.0.0.0172.0.0.0 2.8.1.1 255.0.0.010.0.0.0 2.8.1.1 255.0.0.0203.0.0.0 0.0.0.0 255.0.0.00.0.0.0 2.8.1.1 0.0.0.0Related Commands
show ip static route
To display IP static route information, use the show ip static route command in user EXEC configuration mode.
show ip static route
Syntax Description
This command has no keywords or arguments.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Examples
The following example shows sample output from the show ip rib route command:
ServiceRouter# show ip static routeIPv4 Unicast Static Routes:10.1.1.0/24, configured nh: 0.0.0.0/32real nh: 0.0.0.0, iod: 8 [1/0]10.1.2.0/24, configured nh: 0.0.0.0/32real nh: 0.0.0.0, iod: 8 [1/0]10.1.3.0/24, configured nh: 0.0.0.0/32real nh: 0.0.0.0, iod: 8 [1/0]10.1.4.0/24, configured nh: 0.0.0.0/32real nh: 0.0.0.0, iod: 8 [1/0]10.1.5.0/24, configured nh: 0.0.0.0/32real nh: 0.0.0.0, iod: 8 [1/0]10.1.6.0/24, configured nh: 0.0.0.0/32real nh: 0.0.0.0, iod: 8 [1/0]Related CommandsI
ip rib route
Configures unicast static routes for the Proximity Engine.
show ip rib route
Displays IP RIB route information.
show ipv6
To display IPv6 information, use the show ipv6 command in user EXEC configuration mode.
show ipv6
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Examples
The following example shows sample output from the show ipv6 access-list command:
ServiceRouter# show ipv6 access-listSpace available:48 access lists498 access list conditionsStandard IPv6 access list 11 deny fec0:0:3:5::1/128(implicit deny any: 0 matches)total invocations: 0Extended IPv6 access list test1 permit icmpv6 any any echo(implicit fragment permit: 0 matches)(implicit deny ip any any: 0 matches)total invocations: 0Interface access list references:None ConfiguredApplication access list references:No applications registered.The following example shows sample output from the show ipv6 routes command:
ServiceRouter# show ipv6 routesDestination Next Hop---------------------------------------- ------------------------------------Destination Next3ffe:1200:4260:f::/64 ::fe80::/64 ::fec0:0:3:3::/64 ::ff00::/8 ::::/0 fec0:0:3:3::1::/0 fe80::218:74ff:fe17:a8c0ServiceRouter#
Note
Related CommandsI
clear ipv6
Clears IPv6 ACL counters.
ipv6
Specifies the default gateway's IPv6 address.
traceroute6
Traces the route to a remote IPv6-enabled host.
show isis adjacency
To display IS-IS adjacencies, use the show isis adjacency command in user EXEC configuration mode.
show isis adjacency [detail]
Syntax Description
Command Modes
User EXEC configuration mode.
Command Defaults
By default, this command displays a summarized report on IS-IS adjacency.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show isis adjacency command with and without the parameter keyword detail:
ServiceRouter# show isis adjacency detailIS-IS adjacency database:System ID SNPA Level State Hold Time Interface0200.c0a8.5401 0000.a1e8.e019 1 UP 00:00:32 GigabitEthernet 3/0Up/Down transitions: 3, Last transition: 18:45:08 agoCircuit Type: 1-2IPv4 Address: 192.168.84.1IPv6 Address: 0::Circuit ID: 7301-7-core.01, Priority: 647301-7-core 001d.a1e9.c41b 1 UP 00:00:08 GigabitEthernet 3/0Up/Down transitions: 1, Last transition: 18:45:52 agoCircuit Type: 1-2IPv4 Address: 192.168.84.7IPv6 Address: 0::Circuit ID: 7301-7-core.01, Priority: 647301-7-core 001d.a1e9.c41b 2 UP 00:00:07 GigabitEthernet 3/0Up/Down transitions: 1, Last transition: 18:37:20 agoCircuit Type: 1-2IPv4 Address: 192.168.84.7IPv6 Address: 0::Circuit ID: 7301-7-core.01, Priority: 64ServiceRouter#ServiceRouter# show isis adjacencyIS-IS adjacency database:System ID SNPA Level State Hold Time Interface0200.c0a8.5401 0000.a1e8.e019 1 UP 00:00:29 GigabitEthernet 3/07301-7-core 001d.a1e9.c41b 1 UP 00:00:08 GigabitEthernet 3/07301-7-core 001d.a1e9.c41b 2 UP 00:00:10 GigabitEthernet 3/0Related Commands
show isis clns route
To display one or all the destinations to which the router knows how to route CLNS packets, use the show isis clns route command in user EXEC configuration mode.
show isis clns route nsap
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
The show isis clns route command shows the IS-IS Level 2 routing table and static and Intermediate System-to-Intermediate System Interior Gateway Routing Protocol (ISO-IGRP) learned prefix routes. This table stores IS-IS area addresses and prefix routes. This command requires a Proximity Engine license.
Examples
The following is sample output from the show clns route command when the nsap argument is not used:
ServiceRouter# show isis clns routeIS-IS Level-1 IS routing table7301-5-Core.00, Instance 0x00000145*via 7301-7-core, GigabitEthernet 3/0, metric 207301-7-core.00, Instance 0x00000145*via 7301-7-core, GigabitEthernet 3/0, metric 107301-7-core.02, Instance 0x00000145*via 7301-7-core, GigabitEthernet 3/0, metric 200200.c0a8.5401.00, Instance 0x00000145*via 0200.c0a8.5401, GigabitEthernet 3/0, metric 100200.cf00.0002.00, Instance 0x00000145*via 0200.c0a8.5401, GigabitEthernet 3/0, metric 200200.cf00.0002.01, Instance 0x00000145*via 0200.c0a8.5401, GigabitEthernet 3/0, metric 200200.cf00.2802.00, Instance 0x00000145*via 0200.c0a8.5401, GigabitEthernet 3/0, metric 300200.cf00.2802.01, Instance 0x00000145*via 0200.c0a8.5401, GigabitEthernet 3/0, metric 300200.cf00.5002.00, Instance 0x00000145*via 0200.c0a8.5401, GigabitEthernet 3/0, metric 400200.cf00.5002.01, Instance 0x00000145-- More --Related Commands
show isis database
To display the IS-IS link-state database, use the show isis database command in user EXEC configuration mode.
show isis database [ [LSP_ID] [detail] | advertise | private | summary]
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
Each option for this command can be entered in an arbitrary string within the same command entry. For example, the following are both valid command specifications and provide the same output: show isis database detail l2 and show isis database l2 detail. This command requires a Proximity Engine license.
Examples
The following is sample output from the show isis database command when it is issued with no keywords or arguments:
ServiceRouter# show isis database summaryIS-IS LSP database:IS-IS Level-1 Link State DatabaseLSP : 3IS-IS Level-2 Link State DatabaseLSP : 3ServiceRouter#The following is sample output from the show isis database command when it is issued with the private keyword:
ServiceRouter# show isis database privateIS-IS LSP database:IS-IS Level-1 Link State DatabaseLSPID Seq Number Checksum Lifetime A/P/O/TDD10-CDE205-2.00-00 * 0x00000004 0x7D13 992 0/0/1/3Instance : 0x00000004Digest Offset : 0Area Address : 49.0000NLPID : 0xCCRouter ID : 3.1.5.3IP Address : 3.1.5.3Hostname : DD10-CDE205-2 Length : 13Extended IS : DD10-CDE205-2.01 Metric : 10Extended IP : 3.1.5.0/24 Metric : 10 (U)Extended IP : 26.0.0.0/8 Metric : 10 (U)DD10-CDE205-2.01-00 * 0x00000001 0x8ABC 992 0/0/0/3Instance : 0x00000001Digest Offset : 0Extended IS : DD10-7301-6.00 Metric : 0Extended IS : DD10-CDE205-2.00 Metric : 0DD10-7301-6.00-00 0x00000003 0x206E 988 0/0/0/3Instance : 0x00000000Digest Offset : 0Area Address : 49.0000NLPID : 0xCCHostname : DD10-7301-6 Length : 11IP Address : 62.0.0.6IP Internal : 26.0.0.0/8 Metric : 10 (I,U)IP Internal : 62.0.0.0/8 Metric : 10 (I,U)IS Neighbor : DD10-CDE205-2.01 Metric : 10 (I)IS-IS Level-2 Link State DatabaseLSPID Seq Number Checksum Lifetime A/P/O/TDD10-CDE205-2.00-00 * 0x00000004 0x7D13 994 0/0/1/3Instance : 0x00000004Digest Offset : 0Area Address : 49.0000NLPID : 0xCCRouter ID : 3.1.5.3IP Address : 3.1.5.3Hostname : DD10-CDE205-2 Length : 13Extended IS : DD10-CDE205-2.01 Metric : 10Extended IP : 3.1.5.0/24 Metric : 10 (U)Extended IP : 26.0.0.0/8 Metric : 10 (U)DD10-CDE205-2.01-00 * 0x00000001 0x8ABC 994 0/0/0/3Instance : 0x00000001Digest Offset : 0Extended IS : DD10-7301-6.00 Metric : 0Extended IS : DD10-CDE205-2.00 Metric : 0DD10-7301-6.00-00 0x00000003 0x2668 990 0/0/0/3Instance : 0x00000000Digest Offset : 0Area Address : 49.0000NLPID : 0xCCHostname : DD10-7301-6 Length : 11IP Address : 62.0.0.6IS Neighbor : DD10-CDE205-2.01 Metric : 10 (I)IP Internal : 26.0.0.0/8 Metric : 10 (I,U)IP Internal : 62.0.0.0/8 Metric : 10 (I,U)ServiceRouter#The following is sample output from the show isis database command when it is issued with an LSP_ID specified:
ServiceRouter# sh isis database DD10-CDE205-2.00-00IS-IS LSP database:IS-IS Level-1 Link State DatabaseLSPID Seq Number Checksum Lifetime A/P/O/TDD10-CDE205-2.00-00 * 0x00000004 0x7D13 968 0/0/1/3IS-IS Level-2 Link State DatabaseLSPID Seq Number Checksum Lifetime A/P/O/TDD10-CDE205-2.00-00 * 0x00000004 0x7D13 970 0/0/1/3ServiceRouter#The following is sample output from the show isis database command when it is issued with the advertise keyword:
ServiceRouter# show isis database advertiseIS-IS LSP database:IS-IS Level-1 Link State DatabaseLSPID Seq Number Checksum Lifetime A/P/O/TDD10-CDE205-2.00-00 * 0x00000004 0x7D13 1016 0/0/1/3Max: 1446 Used: 104 Free: 1342Type: 1, Max: 42, Used: 42, Free: 0Type: 129, Max: 1, Used: 1, Free: 0Type: 134, Max: 4, Used: 4, Free: 0Router ID: 3.1.5.3Type: 22, Max: 255, Used: 11, Free: 244Extended IS NBR: DD10-CDE205-2.01 (UP)Type: 135, Max: 255, Used: 14, Free: 241Extended IP Prefix: 3.1.5.0/24 Metric: 10Extended IP Prefix: 26.0.0.0/8 Metric: 10Type: 137, Max: 255, Used: 13, Free: 242Hostname: DD10-CDE205-2 Length: 13DD10-CDE205-2.01-00 * 0x00000001 0x8ABC 1016 0/0/0/3Max: 1446 Used: 24 Free: 1422Type: 22, Max: 255, Used: 22, Free: 233Extended IS NBR: DD10-7301-6.00 (UP)Extended IS NBR: DD10-CDE205-2.00 (UP)DD10-7301-6.00-00 0x00000003 0x206E 1012 0/0/0/3Max: 0 Used: 0 Free: 0IS-IS Level-2 Link State DatabaseLSPID Seq Number Checksum Lifetime A/P/O/TDD10-CDE205-2.00-00 * 0x00000004 0x7D13 1018 0/0/1/3Max: 1446 Used: 104 Free: 1342Type: 1, Max: 42, Used: 42, Free: 0Type: 129, Max: 1, Used: 1, Free: 0Type: 134, Max: 4, Used: 4, Free: 0Router ID: 3.1.5.3Type: 22, Max: 255, Used: 11, Free: 244Extended IS NBR: DD10-CDE205-2.01 (UP)Type: 135, Max: 255, Used: 14, Free: 241Extended IP Prefix: 3.1.5.0/24 Metric: 10Extended IP Prefix: 26.0.0.0/8 Metric: 10Type: 137, Max: 255, Used: 13, Free: 242Hostname: DD10-CDE205-2 Length: 13DD10-CDE205-2.01-00 * 0x00000001 0x8ABC 1018 0/0/0/3Max: 1446 Used: 24 Free: 1422Type: 22, Max: 255, Used: 22, Free: 233Extended IS NBR: DD10-7301-6.00 (UP)Extended IS NBR: DD10-CDE205-2.00 (UP)DD10-7301-6.00-00 0x00000003 0x2668 1014 0/0/0/3Max: 0 Used: 0 Free: 0ServiceRouter#The following is sample output from the show isis database command when it is issued with the detail keyword:
Note
ServiceRouter# show isis database detailIS-IS LSP database:IS-IS Level-1 Link State DatabaseLSPID Seq Number Checksum Lifetime A/P/O/TDD10-CDE205-2.00-00 * 0x00000004 0x7D13 1007 0/0/1/3Area Address : 49.0000NLPID : 0xCCRouter ID : 3.1.5.3IP Address : 3.1.5.3Hostname : DD10-CDE205-2 Length : 13Extended IS : DD10-CDE205-2.01 Metric : 10Extended IP : 3.1.5.0/24 Metric : 10 (U)Extended IP : 26.0.0.0/8 Metric : 10 (U)DD10-CDE205-2.01-00 * 0x00000001 0x8ABC 1007 0/0/0/3Extended IS : DD10-7301-6.00 Metric : 0Extended IS : DD10-CDE205-2.00 Metric : 0DD10-7301-6.00-00 0x00000003 0x206E 1002 0/0/0/3Area Address : 49.0000NLPID : 0xCCHostname : DD10-7301-6 Length : 11IP Address : 62.0.0.6IP Internal : 26.0.0.0/8 Metric : 10 (I,U)IP Internal : 62.0.0.0/8 Metric : 10 (I,U)IS Neighbor : DD10-CDE205-2.01 Metric : 10 (I)IS-IS Level-2 Link State DatabaseLSPID Seq Number Checksum Lifetime A/P/O/TDD10-CDE205-2.00-00 * 0x00000004 0x7D13 1008 0/0/1/3Area Address : 49.0000NLPID : 0xCCRouter ID : 3.1.5.3IP Address : 3.1.5.3Hostname : DD10-CDE205-2 Length : 13Extended IS : DD10-CDE205-2.01 Metric : 10Extended IP : 3.1.5.0/24 Metric : 10 (U)Extended IP : 26.0.0.0/8 Metric : 10 (U)DD10-CDE205-2.01-00 * 0x00000001 0x8ABC 1008 0/0/0/3Extended IS : DD10-7301-6.00 Metric : 0Extended IS : DD10-CDE205-2.00 Metric : 0DD10-7301-6.00-00 0x00000003 0x2668 1004 0/0/0/3Area Address : 49.0000NLPID : 0xCCHostname : DD10-7301-6 Length : 11IP Address : 62.0.0.6IS Neighbor : DD10-CDE205-2.01 Metric : 10 (I)IP Internal : 26.0.0.0/8 Metric : 10 (I,U)IP Internal : 62.0.0.0/8 Metric : 10 (I,U)ServiceRouter#Related Commands
show isis hostname-table
To display the router-name-to-system-ID mapping table entries for an IS-IS router, use the show isis hostname-table command in user EXEC configuration mode.
show isis hostname-table
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
In the IS-IS routing domain, the system ID is used to represent each router. The system ID is part of the network entity title (NET) that is configured for each IS-IS router. For example, a router with a configured NET of 49.0001.0023.0003.000a.00 has a system ID of 0023.0003.000a. Router-name-to-system-ID mapping is difficult for network administrators to remember during maintenance and troubleshooting on the routers. Entering the show isis hostname-table command displays the entries in the router-name-to-system-ID mapping table. This command requires a Proximity Engine license.
Examples
Entering the show isis hostname-table command displays the dynamic host mapping table, which displays the router-name-to-system-ID mapping table entries. The * symbol next to the System ID signifies that this is the router-name-to-system-ID mapping information for the local router.
ServiceRouter# show isis hostname-tableIS-IS dynamic hostname table:Level System ID Dynamic hostname1 0200.c0a8.0a05 7301-5-Core1 0200.c0a8.0a07 7301-7-core1 1111.1111.1111* sn-sj832 1234.1234.1234 sn-sj862 1234.1242.1234 7301-2-IS-ISServiceRouter#Related Commands
show isis interface
To display information about the IS-IS interfaces, use the show isis interface command in user EXEC configuration mode.
show isis interface interface_name
Syntax Description
Command Defaults
Displays all IS-IS interfaces.
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show isis interface command with interface name set to be GigabitEthernet 1/0 and without an interface name, respectively:
ServiceRouter# show isis interface GigabitEthernet 1/0GigabitEthernet 1/0, Interface status: protocol-down/link-down/admin-downIP address: 0.0.0.0, IP subnet: 0.0.0.0/0IPv6 routing is disabledIS-IS interface operation state : Down/ReadyIndex: 0x0002, Local Circuit ID: 0x02, Circuit Type: 1-2Passive level: level-1-2LSP interval: 33 msLevel Metric CSNP Next CSNP Hello Multi Next IIH1 10 10 Never 10 3 Never2 10 10 Never 10 3 NeverLevel Adjs Ups Pri Circuit ID Since1 0 0 64 0000.0000.0000.02 never2 0 0 64 0000.0000.0000.02 neverServiceRouter#ServiceRouter# show isis interfaceGigabitEthernet 1/0, Interface status: protocol-up/link-up/admin-upIP address: 172.20.168.83, IP subnet: 172.20.168.0/24IPv6 routing is disabledIndex: 0x0001, Local Circuit ID: 0x01, Circuit Type: 1-2Passive level: level-1-2LSP interval: 33 msLevel Metric CSNP Next CSNP Hello Multi Next IIH1 10 10 Never 10 3 Never2 10 10 Never 10 3 NeverLevel Adjs Ups Pri Circuit ID Since1 0 0 64 sn-sj83.01 never2 0 0 64 sn-sj83.01 neverGigabitEthernet 1/0, Interface status: protocol-down/link-down/admin-downIP address: 0.0.0.0, IP subnet: 0.0.0.0/0IPv6 routing is disabledIS-IS interface operation state : Down/ReadyIndex: 0x0002, Local Circuit ID: 0x02, Circuit Type: 1-2Passive level: level-1-2LSP interval: 33 msLevel Metric CSNP Next CSNP Hello Multi Next IIH1 10 10 Never 10 3 Never2 10 10 Never 10 3 NeverLevel Adjs Ups Pri Circuit ID Since1 0 0 64 0000.0000.0000.02 never2 0 0 64 0000.0000.0000.02 neverGigabitEthernet 2/0, Interface status: protocol-down/link-down/admin-downIP address: 0.0.0.0, IP subnet: 0.0.0.0/0IPv6 routing is disabledIS-IS interface operation state : Down/ReadyIndex: 0x0003, Local Circuit ID: 0x03, Circuit Type: 1-2Passive level: level-1-2LSP interval: 33 msLevel Metric CSNP Next CSNP Hello Multi Next IIH1 10 10 Never 10 3 Never2 10 10 Never 10 3 NeverLevel Adjs Ups Pri Circuit ID Since1 0 0 64 0000.0000.0000.03 never2 0 0 64 0000.0000.0000.03 neverGigabitEthernet 3/0, Interface status: protocol-up/link-up/admin-upIP address: 192.168.84.83, IP subnet: 192.168.84.0/24IPv6 routing is disabledIndex: 0x0004, Local Circuit ID: 0x04, Circuit Type: 1-2LSP interval: 33 msLevel Metric CSNP Next CSNP Hello Multi Next IIH1 10 10 Never 10 3 00:00:082 10 10 Never 10 3 00:00:05Level Adjs Ups Pri Circuit ID Since1 2 2 64 7301-7-core.01 18:55:472 1 1 64 7301-7-core.01 18:47:15GigabitEthernet 4/0, Interface status: protocol-up/link-up/admin-upIP address: 192.168.78.83, IP subnet: 192.168.78.0/24IPv6 routing is disabledIndex: 0x0005, Local Circuit ID: 0x05, Circuit Type: 1-2Passive level: level-1-2LSP interval: 33 msLevel Metric CSNP Next CSNP Hello Multi Next IIH1 10 10 Never 10 3 Never2 10 10 Never 10 3 NeverLevel Adjs Ups Pri Circuit ID Since1 0 0 64 sn-sj83.05 never2 0 0 64 sn-sj83.05 neverGigabitEthernet 5/0, Interface status: protocol-down/link-down/admin-downIP address: 0.0.0.0, IP subnet: 0.0.0.0/0IPv6 routing is disabledIS-IS interface operation state : Down/ReadyIndex: 0x0006, Local Circuit ID: 0x06, Circuit Type: 1-2Passive level: level-1-2LSP interval: 33 msLevel Metric CSNP Next CSNP Hello Multi Next IIH1 10 10 Never 10 3 Never2 10 10 Never 10 3 NeverLevel Adjs Ups Pri Circuit ID Since1 0 0 64 0000.0000.0000.06 never2 0 0 64 0000.0000.0000.06 neverGigabitEthernet 6/0, Interface status: protocol-down/link-down/admin-downIP address: 0.0.0.0, IP subnet: 0.0.0.0/0IPv6 routing is disabledIS-IS interface operation state : Down/ReadyIndex: 0x0007, Local Circuit ID: 0x07, Circuit Type: 1-2Passive level: level-1-2LSP interval: 33 msLevel Metric CSNP Next CSNP Hello Multi Next IIH1 10 10 Never 10 3 Never2 10 10 Never 10 3 NeverLevel Adjs Ups Pri Circuit ID Since1 0 0 64 0000.0000.0000.07 never2 0 0 64 0000.0000.0000.07 never
GigabitEthernet 7/0, Interface status: protocol-down/link-down/admin-downIP address: 0.0.0.0, IP subnet: 0.0.0.0/0IPv6 routing is disabledIS-IS interface operation state : Down/ReadyIndex: 0x0008, Local Circuit ID: 0x08, Circuit Type: 1-2Passive level: level-1-2LSP interval: 33 msLevel Metric CSNP Next CSNP Hello Multi Next IIH1 10 10 Never 10 3 Never2 10 10 Never 10 3 NeverLevel Adjs Ups Pri Circuit ID Since1 0 0 64 0000.0000.0000.08 never2 0 0 64 0000.0000.0000.08 neverServiceRouter#Related Commands
show isis ip route
To display the Intermediate IS-IS RSPF route for IS-IS learned routes, use the show isis ip route command in user EXEC configuration mode.
show isis ip route [IP | detail | summary]
Syntax Description
Command Defaults
Displays all IS-IS route information.
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show isis route command with various parameters:
ServiceRouter# show isis ip route detailIS-IS IPv4 routing table5.5.5.5/32, L2*via 192.168.84.7, GigabitEthernet 3/0, metric 20, L2 (I,U)Instance 0x0000D831LSPID 1234.1242.1234.00-0012.1.1.1/32, L2*via 192.168.84.7, GigabitEthernet 3/0, metric 20, L2 (I,U)Instance 0x0000D831LSPID 1234.1242.1234.00-0013.1.1.1/32, L2*via 192.168.84.7, GigabitEthernet 3/0, metric 20, L2 (I,U)Instance 0x0000D831LSPID 1234.1242.1234.00-0014.1.1.1/32, L2*via 192.168.84.7, GigabitEthernet 3/0, metric 20, L2 (I,U)Instance 0x0000D831LSPID 1234.1242.1234.00-0022.22.22.22/32, L2*via 192.168.84.7, GigabitEthernet 3/0, metric 20, L2 (I,U)Instance 0x0000D831LSPID 1234.1242.1234.00-0040.1.1.0/24, L2*via 192.168.84.7, GigabitEthernet 3/0, metric 20, L2 (I,U)-- More --ServiceRouter# show isis ip route summaryIS-IS IPv4 routing tableTotal number of best routes : 8517Total number of paths : 12523Total number of best paths : 8517Total number of backup paths : 4006Best routes per levelL1 total : 4006direct : 3normal : 4003L2 total : 4511normal : 4511Best paths per levelL1 total : 4006direct : 3normal : 4003L2 total : 4511normal : 4511Backup paths per levelL2 total : 4006direct : 3normal : 4003Number of best routes per mask-length/24 : 8511 /32 : 6ServiceRouter#ServiceRouter# show isis ip route 40.1.1.0IS-IS IPv4 routing table40.1.1.0/24, L2*via 192.168.84.7, GigabitEthernet 3/0, metric 20, L2 (I,U)ServiceRouter#ServiceRouter# show isis ip route 40.1.1.0 detailIS-IS IPv4 routing table40.1.1.0/24, L2*via 192.168.84.7, GigabitEthernet 3/0, metric 20, L2 (I,U)Instance 0x0000D880LSPID 1234.1242.1234.00-00ServiceRouter#Related Commands
show isis ip rspf route
To display the Intermediate IS-IS RSPF route for IS-IS learned routes, use the show isis ip rspf command in user EXEC configuration mode.
show isis ip rspf route [LSP_ID]
Syntax Description
Command Defaults
If no LSP ID is specified, displays IS-IS RSPF information for all LSP IDs.
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command is used to display the IS-IS RSPF routing information. Output is only displayed for this command when a new proximity request has been received. To clear IS-IS RSPF routing information, use the clear isis ip rspf route command. This command requires a Proximity Engine license.
Examples
The following is sample output from the show isis rspf route command:
ServiceRouter# show isis ip rspf routeLSP ID SPF Time Cache Hit Level Age Max range0200.c0a8.0a01.00-00 01:45:41 0 1 01:43:23 10ServiceRouter#ServiceRouter# show isis ip rspf route 0200.c0a8.0a07.00-00IS-IS IPv4 routing table172.20.168.0/24, L1metric 20, L1192.168.78.0/24, L1metric 20, L1192.168.79.0/24, L1metric 20, L1192.168.84.0/24, L1metric 10, L1192.168.89.0/24, L1metric 10, L1192.168.90.0/24, L1metric 10, L1207.0.0.0/24, L1metric 20, L1207.0.1.0/24, L1metric 30, L1-- More --ServiceRouter#Related Commands
show isis memory
To display memory usage information for an IS-IS instance, use the show isis memory command in user EXEC configuration mode.
show isis memory
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show isis memory command:
ServiceRouter# show isis memoryShared memory information for /topos-shm-isis-abc,Current-Size HWM Maximum-Size2005392 2005392 4194304IS-IS memory usage:Type Size Count HWM Slab Overhead TotalInterface 2632 9 9 16 18600 42288Adjacency 184 35 35 64 5512 11952LSP DB 320 665 665 704 13136 225936LSP TLV 48 10 10 64 2768 3248LSP Retx 72 0 0 0 128 128Next Hop 24 13130 21970 22528 226736 541856RT HIX 32 0 0 0 128 128SPF Adj 104 3 3 64 6520 6832SPF RT 28 20553 20557 21504 27764 603248Redist RT 44 3 3 1024 45100 45232RI 72 6 6 1024 73472 73904SPF RT 40 0 1 0 128 128Redist RT 56 0 0 0 128 128RI 56 0 0 0 128 128Total: 420248 1555136ServiceRouter#Related Commands
show isis process
To display summary information about an IS-IS instance, use the show isis process command in user EXEC configuration mode.
show isis process
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show isis process command:
ServiceRouter# show isis processIS-IS process : abcSystem ID : 1111.1111.1111 IS-Type : L1-L2SAP : 1666 Queue Handle : 1666Metric-style : advertise(narrow, wide), accept(narrow, wide)Area address(es) :49.0005Process is up and runningVRF ID: 1Stale routes during non-graceful controlled restartInterfaces supported by IS-IS :GigabitEthernet 0/0GigabitEthernet 1/0GigabitEthernet 2/0GigabitEthernet 3/0GigabitEthernet 4/0GigabitEthernet 5/0GigabitEthernet 6/0GigabitEthernet 7/0Address family IPv4 unicast :Number of interface : 8Distance : 115Address family IPv6 unicast :Number of interface : 0Distance : 115Related Commands
show isis rrm
To display IS-IS Received Routing Message (RRM) information, use the show isis rrm command in user EXEC configuration mode.
show isis rrm interface_name
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show isis rrm command that shows rrm information for all interfaces:
ServiceRouter# show isis rrm GigabitEthernet 1/0IS-IS RRM information for interface GigabitEthernet 1/0:No retransmission on non-P2P interfaceServiceRouter# show isis rrm GigabitEthernet 1/0IS-IS RRM information for interface GigabitEthernet 1/0:No retransmission on non-P2P interfaceServiceRouter#ServiceRouter# show isis rrm GigabitEthernet 2/0IS-IS RRM information for interface GigabitEthernet 2/0:No retransmission on non-P2P interfaceServiceRouter# show isis rrm GigabitEthernet 3/0IS-IS RRM information for interface GigabitEthernet 3/0:No retransmission on non-P2P interfaceServiceRouter#Related Commands
show isis spf-log
To display how often and why the router has run a full shortest path first (SPF) calculation, use the show isis spf-log command in user EXEC configuration mode.
show isis spf-log [detail]
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from show isis spf-log and show isis spf-log detail commands, respectively:
ServiceRouter# show isis spf-logIS-IS SPF information:Total number of SPF calculations: 55836Log entry (current/max): 20/20Ago Level Reason Count Total00:02:49 2 Updated LSP 7301-5-Core.00-0f 1 0.01151000:02:49 2 Updated LSP 7301-5-Core.00-10 1 0.01195600:02:49 2 Updated LSP 7301-5-Core.00-11 1 0.01146900:02:49 2 Updated LSP 7301-5-Core.00-12 1 0.01150300:02:49 2 Updated LSP 7301-5-Core.00-13 1 0.01147300:02:49 2 Updated LSP 7301-5-Core.00-14 1 0.01152200:02:49 2 Updated LSP 7301-5-Core.00-15 1 0.01151400:02:49 2 Updated LSP 7301-5-Core.00-16 1 0.01151600:02:49 2 Updated LSP 7301-5-Core.00-17 1 0.01149900:02:49 2 Updated LSP 7301-5-Core.00-18 1 0.01153000:02:49 2 Updated LSP 7301-5-Core.00-19 1 0.01147600:02:49 2 Updated LSP 7301-5-Core.00-1a 1 0.01156000:02:49 2 Updated LSP 7301-5-Core.00-1b 1 0.01151000:02:49 2 Updated LSP 7301-5-Core.00-1c 1 0.01171000:02:49 2 Updated LSP 7301-5-Core.00-1d 1 0.01151400:02:49 2 Updated LSP 7301-5-Core.00-1e 1 0.01151200:02:49 2 Updated LSP 7301-5-Core.00-1f 1 0.01193400:02:49 2 Updated LSP 7301-5-Core.00-20 1 0.01152500:02:49 2 Updated LSP 7301-5-Core.00-21 1 0.01223200:02:49 2 Purged LSP 7301-5-Core.01-00 1 0.011647ServiceRouter#ServiceRouter# show isis spf-log detailIS-IS SPF information:Total number of SPF calculations: 55836Log entry (current/max): 20/20Log entry: 01, Ago: 00:03:59, Date: Tue Jan 06 17:34:05 1970Level Instance Init SPF IS Update URIB Update Total2 0x0000D8C4 0.000019 0.008100 0.000133 0.003255 0.011510Level Node Count Changed Reason2 8 1 0 Updated LSP 7301-5-Core.00-0fLog entry: 02, Ago: 00:03:59, Date: Tue Jan 06 17:34:05 1970Level Instance Init SPF IS Update URIB Update Total2 0x0000D8C5 0.000016 0.008552 0.000129 0.003256 0.011956Level Node Count Changed Reason2 8 1 0 Updated LSP 7301-5-Core.00-10Log entry: 03, Ago: 00:03:58, Date: Tue Jan 06 17:34:05 1970Level Instance Init SPF IS Update URIB Update Total2 0x0000D8C6 0.000016 0.008079 0.000127 0.003243 0.011469Level Node Count Changed Reason2 8 1 0 Updated LSP 7301-5-Core.00-11Log entry: 04, Ago: 00:03:58, Date: Tue Jan 06 17:34:05 1970Level Instance Init SPF IS Update URIB Update Total2 0x0000D8C7 0.000015 0.008097 0.000129 0.003258 0.011503Level Node Count Changed Reason2 8 1 0 Updated LSP 7301-5-Core.00-12Log entry: 05, Ago: 00:03:58, Date: Tue Jan 06 17:34:05 1970Level Instance Init SPF IS Update URIB Update Total2 0x0000D8C8 0.000017 0.008088 0.000129 0.003236 0.011473Level Node Count Changed Reason2 8 1 0 Updated LSP 7301-5-Core.00-13Log entry: 06, Ago: 00:03:58, Date: Tue Jan 06 17:34:05 1970Level Instance Init SPF IS Update URIB Update Total2 0x0000D8C9 0.000019 0.008113 0.000130 0.003257 0.011522Level Node Count Changed Reason2 8 1 0 Updated LSP 7301-5-Core.00-14ServiceRouter#Related Commands
show isis srm
To display Send Routing Message (SRM) information for an IS-IS, use the show isis srm command in privileged EXEC configuration mode.
show isis srm interface_name
Syntax Description
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following example shows how to display sample output from the show isis srm command. It shows the srm information on interface GigabitEthernet 1/0:
ServiceRouter# show isis srm GigabitEthernet 1/0IS-IS SRP information for interface GigabitEthernet 1/0:IS-IS Level-1 Link State DatabaseInterface is not eligible for flooding LSPInterface is not on stopped SRM listLSP interval: 33ms, Next LSP: NeverLSPID Seq Number Checksum Lifetime A/P/O/TIS-IS Level-2 Link State DatabaseIS-IS Level-1 Link State DatabaseInterface is not eligible for flooding LSPInterface is not on stopped SRM listLSP interval: 33ms, Next LSP: NeverLSPID Seq Number Checksum Lifetime A/P/O/TServiceRouter#Related Commands
show isis ssn
To display Send Sequence Number (SSN) information for an IS-IS, use the show isis ssn command in user EXEC configuration mode.
show isis ssn interface_name
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show isis ssn command that shows the ssn information on interface GigabitEthernet 1/0.
ServiceRouter# show isis ssn GigabitEthernet 1/0IS-IS SSN information for interface GigabitEthernet 1/0:IS-IS Level-1 Link State DatabaseInterface is not eligible for sending PSNPNext PSNP: NeverLSPID Seq Number Checksum Lifetime A/P/O/TIS-IS Level-2 Link State DatabaseInterface is not eligible for sending PSNPNext PSNP: NeverLSPID Seq Number Checksum Lifetime A/P/O/TServiceRouter#Related Commands
show key chain
To display the key chains in the system, use the show key chain command in user EXEC configuration mode.
show key chain [decrypt | name]
Syntax Description
Command Defaults
None
Command Modes
User EXEC configuration mode.
Usage Guidelines
This command requires a Proximity Engine license.
Examples
The following is sample output from the show key chain command:
ServiceRouter# show key chainshow key chainKey-Chain lspKey 1 -- text <encrypted-string>accept lifetime (00:00:00 Jan 01 1970) - (always valid) [valid now]send lifetime (00:00:00 Jan 01 1970) - (always valid) [valid now]ServiceRouter#Related Commands
show lacp
To display LACP information, use the show lacp command in EXEC configuration mode.
show lacp {counters| internal}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
You must first turn on LACP by entering the lacp command in Interface configuration mode before you can display the LACP statistics.
In the show lacp counters command, the LACP control packet is sent or received every 30 seconds. If one of the interfaces within the port channel goes down, then the counter value does not further increment for that interface.
Examples
The following example shows how to display the LACP statistics:
ServiceEngine# show lacp countersInterface PortChannel 1 (4 physical interface(s)):Protocol: noneInterface PortChannel 2 (4 physical interface(s)):lacpdu marker marker responsePort send receive send receive send receive error-----------------------------------------------------GigabitEthernet 7/0 16 16 0 0 0 0 0GigabitEthernet 8/0 16 15 0 0 0 0 0GigabitEthernet 9/0 16 15 0 0 0 0 0GigabitEthernet 10/0 17 15 0 0 0 0 0Interface PortChannel 3 (0 physical interface(s)):Protocol: noneInterface PortChannel 4 (0 physical interface(s)):Protocol: noneThe following example shows how to display the link status for the port channel:
ServiceEngine# show lacp internalInterface PortChannel 1 (4 physical interface(s)):Protocol: LACPMode: src-dst-portPort Admin-State Link-State LACP-State Aggregate id-----------------------------------------------------------------------------GigabitEthernet 3/0 up up bndl 21GigabitEthernet 4/0 up up bndl 21GigabitEthernet 5/0 up up bndl 21GigabitEthernet 6/0 up up bndl 21ServiceEngine# show interface portChannel 1 lacpInterface PortChannel 1 (4 physical interface(s)):Protocol: LACPMode: src-dst-portPort Admin-State Link-State LACP-State Aggregate id-----------------------------------------------------------------------------GigabitEthernet 3/0 up up bndl 21GigabitEthernet 4/0 up up bndl 21GigabitEthernet 5/0 up up bndl 21GigabitEthernet 6/0 up up bndl 21Related Commands
lacp
Turns on Link Aggregation Control Protocol (LACP).
show interface portchannel 1 lacp
Displays the link status for the port channel.
show logging
To display the system message log configuration, use the show logging command in EXEC configuration mode.
show logging
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
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 the SE device.
Examples
The following example shows how to display 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
Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.
logging
Configures system logging.
show movie-streamer
To display the Movie Streamer configuration, use the show movie-streamer command in EXEC configuration mode.
show movie-streamer [bandwidth | cache | proxy]
Note
Syntax Description
bandwidth
(Optional) Displays Movie Streamer bandwidth configuration.
cache
(Optional) Displays Movie Streamer cache configuration.
proxy
(Optional) Displays Movie Streamer proxy configuration.
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following example shows the Movie Streamer configuration:
ServiceEngine# show movie-streamerMovie Streamer version cde220-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
Enables and configures the Movie Streamer server.
show statistics movie-streamer
Displays statistics for the Movie Streamer.
show multicast
To display whether or not the multicast sender and receiver are enabled, use the show multicast command in EXEC configuration mode.
show multicast
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
This command is only available on Cisco Internet Streamer CDS Release 3.1.1.
Examples
The following example shows how to display the multicast:
ServiceEngine# show multicastmulticast sender not enabledmulticast receiver enabledRelated Commands
multicast (Global configuration)
Configures multicast options.
multicast (EXEC configuration)
Generate multicast packets and tests connectivity through multicast routers.
show ntp
To display the Network Time Protocol (NTP) parameters, use the show ntp command in EXEC configuration mode.
show ntp status
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-59 describes the fields shown in the show ntp status display.
Related Commands
clock
Sets or clears clock functions or updates the calendar.
ntp
Configures the NTP server and allows the system clock to be synchronized by a time server.
show processes
To display CPU or memory processes, use the show processes command in EXEC configuration mode.
show processes [cpu | debug pid | memory | system [delay delay_num | count count_num]]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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
Table 3-60 describes the fields shown in the show processes displays.
show programs
To display a list of programs on the SE, use the show programs command in EXEC configuration mode.
show programs [movie-streamer [cli | live | rebroadcast] | program-id id | program-name name]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
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 the program starts and ends.
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 prepositioned 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 Content Acquirer 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 network, make sure that there are no external proxy servers physically located between your Internet Streamer SEs and your Content Acquirer 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 Content Acquirer 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 is 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 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 before the live event, we recommend that you configure multiple schedules, one for each trial. We also recommend that you start the encoder before 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 prepositioned 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
The show programs command supports encoder failover. The output of the command looks like the following:
Note
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/APriming Status :Primed : NoCurrent Status : N/ARestarts : 0ServiceEngine# 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 Content Acquirer and non-Content Acquirer output is consistent. Also, if the user executes the show statistics wmt streamstat command from the Content Acquirer, 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.
Note
Table 3-61 describes the fields shown in the show programs program-name and program-id display.
show radius-server
To display RADIUS information, use the show radius-server command in EXEC configuration mode.
show radius-server
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-62 describes the fields shown in the show radius-server display.
Related Commands
show rcp
To display Remote Copy Program (RCP) information, use the show rcp command in EXEC configuration mode.
show rcp
Syntax Description
This command has no keywords or arguments.
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following example shows how to display RCP information:
ServiceEngine# show rcprcp service configurations:rcp enableRelated Commands
show rtsp
To display the Real-Time Streaming Protocol (RTSP) configurations, use the show rtsp command in EXEC configuration mode.
show rtsp [gateway]
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following example display the output of the show rtsp gateway command in EXEC configuration mode:
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
show rule
To display rules configuration information, use the show rule command in EXEC configuration mode.
show rule {action {all [protocol {http | rtmp | rtsp}] | allow [protocol {http | rtmp | rtsp}] | block [protocol {http | rtmp | rtsp}] | generate-url-signature [protocol {http | rtmp | rtsp}] | no-cache [protocol {http | rtmp | rtsp}] | redirect [protocol {http | rtmp | rtsp}] | refresh [protocol {http | rtmp | rtsp}] | rewrite [protocol {http | rtmp | rtsp}] | validate-url-signature [protocol {http | rtmp | rtsp}]} | all | hit {word} | pattern-list {pattern_num pattern_type | all}}
Syntax Description
action
Displays all the rules with the same action types.
all
Displays all the action rules.
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.
validate-url-signature
Validates a signed URL.
all
Displays all the configured actions and pattern lists.
hit
Display the rule hit and its action for a request URL.
word
A quoted string containing the request URL.
pattern-list
Displays the rules with the specified patterns.
pattern_num
Pattern number. The range is from 1 to 512.
pattern_type
Pattern type (see Table 3-63).
all
Displays rules with all pattern lists.
Command Defaults
None
Command Modes
EXEC configuration mode.
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 3-63 shows the permitted pattern types and describes each pattern type.
Note
Examples
The following example shows how to display 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
show running-config
To display the current running configuration information on the terminal, use the show running-config command in EXEC configuration mode.
show running-config
Syntax Description
This command has no keywords or arguments.
Command Defaults
None
Command Modes
EXEC configuration mode.
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 shows how to display the current running configuration information:
ServiceEngine# show running-config! CDS version 2.6.0!device mode service-engine!!hostname EE8-2G2-5!!authsvr location-server primary 4.0.1.3 7000!!clock timezone PDT -7 0!!ip domain-name telstra.com!exec-timeout 0!!!!!interface PortChannel 1ip address 188.0.82.8 255.255.255.0exitinterface PortChannel 2ip address 188.87.0.5 255.255.0.0exit!interface GigabitEthernet 1/0channel-group 1exitinterface GigabitEthernet 2/0channel-group 1exitinterface GigabitEthernet 3/0channel-group 2exitinterface GigabitEthernet 4/0channel-group 2exitinterface GigabitEthernet 5/0channel-group 2exitinterface GigabitEthernet 6/0channel-group 2exitinterface GigabitEthernet 7/0channel-group 2exitinterface GigabitEthernet 8/0channel-group 2exitinterface GigabitEthernet 9/0channel-group 2exitinterface GigabitEthernet 10/0channel-group 2exit!streaming-interface PortChannel 2!!ip default-gateway 188.0.82.1ip default-gateway 188.87.0.1!!port-channel load-balance round-robinprimary-interface PortChannel 2!transaction-logs enabletransaction-logs archive max-file-size 2000000transaction-logs archive max-file-number 50transaction-logs archive interval 300transaction-logs export enabletransaction-logs export interval 5transaction-logs export sftp-server 188.0.84.5 root **** /var/ftp/pub/uploadtransaction-logs format custom "%J"!!!!!ip name-server 188.0.84.7!ip route 10.74.61.0 255.255.255.0 188.87.0.1ip route 171.70.77.0 255.255.255.0 188.87.0.1ip route 188.85.0.3 255.255.255.255 188.87.0.1ip route 188.0.86.3 255.255.255.255 188.0.82.1ip route 188.85.0.4 255.255.255.255 188.87.0.1ip route 225.1.1.12 255.255.255.255 188.87.0.1ip route 239.1.1.12 255.255.255.255 188.87.0.1ip route 239.1.1.14 255.255.255.255 188.87.0.1ip route 224.0.0.22 255.255.255.255 188.87.0.1!!!ntp server 171.68.10.150ntp server 171.68.10.80!!!!!!!!!!rule enable!!!!!movie-streamer enablemovie-streamer max-concurrent-sessions 10000movie-streamer advanced client idle-timeout 0movie-streamer advanced client rtp-timeout 0bitrate movie-streamer outgoing 6000000bitrate movie-streamer incoming 6000000!rtsp advanced max-request-rate 1000wmt max-concurrent-sessions 14000wmt cache min-ttl 1wmt cache max-ttl days 3wmt advanced client idle-timeout 300wmt advanced server inactivity-timeout 300wmt transaction-logs format extended wms-90!username admin password 1 $5$bVz2jc/k$QYvCAKrBmq3YqM5IklvuGrXQACMelfONdq3/siTpqV8username admin privilege 15!snmp-server enable traps configsnmp-server enable traps service-engine disk-failsnmp-server enable traps alarm raise-criticalsnmp-server enable traps alarm clear-criticalsnmp-server enable traps alarm raise-majorsnmp-server enable traps alarm clear-majorsnmp-server enable traps alarm raise-minorsnmp-server enable traps alarm clear-minorsnmp-server enable traps entitysnmp-server enable traps snmp cold-startsnmp-server host 188.0.84.6 telstra v2csnmp-server group telstra v2c read telstra notify telstrasnmp-server community telstra!!!tacacs key ****tacacs password asciitacacs host 188.0.84.5 primary!!aaa authentication login local secondaryaaa authentication login tacacs+ primaryaaa authorization exec local secondaryaaa authorization exec tacacs+ primary!ftp enable!telnet enable!!!!!!!cdsm ip 188.0.86.3cms enable!cms database maintenance regular schedule every-day at 04:00cms database maintenance full schedule Sun at 04:00!kernel kdbdisk error-handling reload!banner enable!bandwidth wmt outgoing 6000000 defaultbandwidth wmt outgoing 6000000 max-bandwidthbandwidth wmt incoming 6000000 defaultbandwidth wmt incoming 6000000 max-bandwidthbandwidth movie-streamer outgoing 6000000 defaultbandwidth movie-streamer outgoing 6000000 max-bandwidthbandwidth movie-streamer incoming 6000000 defaultbandwidth movie-streamer incoming 6000000 max-bandwidth!url-signature key-id-owner 1 key-id-number 1 key ****url-signature key-id-owner 2 key-id-number 2 key ****!!!!!!!!contentmgr disk-bucket-fail-threshold 1!! End of CDS configurationServiceEngine#Related Commands
configure
Enters Global configuration mode.
copy
Copies the configuration or image data from a source to a destination.
show service-router
To display the Service Router configuration, use the show service-router command in EXEC configuration mode.
On the SE:
show service-router {keepalive-interval | service-monitor}
On the SR:
show service-router {access-policy | content-based-routing | forwarding [content-origin content_origin] | lastresort [domain name] | load {all | sename sename} | location-based-routing | memory | proximity-based-routing {cache ip ip_address} | redirect-burst-control | redirect-mode | routes [content-origin content_origin ip-address ip_address] | service-monitor | services {all | sename se_name} | subscribe domain | summary [content-origin content_origin]}
On the CDSM:
show service-router service-monitor
Syntax Description
access-policy
Configures the service-router access-policy.
content-based-routing
Displays the content-based routing configuration.
forwarding
Displays the content origin forwarding tables.
content-origin
(Optional) Displays information for one content origin.
content_origin
Content origin FQDN1 .
lastresort
Displays the domain and alternate domain configured.
domain
(Optional) Displays information for one domain.
name
Domain name.
load
Displays the load and threshold reached status.
all
Displays for all SEs.
sename
Displays for one SE.
se_name
SE name.
location-based-
routingDisplays the location-based routing configurations.
memory
Displays details on malloc-related memory usage for the SR process.
proximity-based-
routingDisplays the proximity-based routing configurations.
cache
(Optional) Displays proximity-based routing cache information.
ip
Displays one IP address or subnet.
ip_address
Client IP address or subnet of the proximity cache information to be displayed.
redirect-burst-control
Displays the redirect burst control configurations.
redirect-mode
Displays the redirect-mode configurations.
routes
Displays the content origin routing tables.
service-monitor
Displays the service monitor configuration.
services
Displays the services status.
subscribe
Displays the subscribe list.
domain
Displays the domain names.
summary
Displays the content origin routing table summary statistics.
keepalive-interval
Displays the keepalive interval.
1 FQDN = fully qualified domain name
Command Defaults
content-based-routing: disabled
Command Modes
EXEC configuration mode.
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.
The show service-router content-based-routing command displays the content aware routing configuration for every content-origin. This command displays whether the universal content based routing is enabled or disabled, the content redundant copy number, and whether the content based routing has been disabled for any particular domain.
Note
The memory usage is calculated in the show service-router service-monitor command as follows:
Total used memory = total memory - (total free memory + total buffer memory + total cache memory) + total pinned memory. The percentage of total used memory = (total used memory)/total memory.
The total memory, total free memory, total buffer memory, and total cache memory are obtained from /proc/meminfo. The total pinned memory is obtained from /proc/ukse/ukse_prefetch_details.
The show service-router content-origin <content-origin> ip-address <client-ip> command is only used to check which SE the request is routed to based on the network entries and metrics configured in the coverage zone file. It does not take into account the service status of the SEs because there is no protocol or filename in the input. Also, it does not take into account matches from location based routing and proximity based routing.
The show service-router content-origin <content-origin> output shows an SE as overloaded only if the device load has exceeded thresholds. The SE does not show as overloaded because there might be other Protocol Engines in the SE that are still able to serve requests.
Examples
The following example shows how to display SR routing statistics:
ServiceRouter# show statistics service-router all | begin "SR Routing Statistics"----- SR Routing Statistics -----Network Redirects : 0Proximity Redirects : 2Geo Location Redirects : 0Zero Network Redirects : 0Last Resort Redirects : 0----- SR Proximity Routing Statistics -----Cache Hits : 1Cache Misses : 1Errors : 0The following example shows how to display the content aware routing configuration for every content-origin:
ServiceRouter# show service-router content-based-routingContent based routing is enabled globallyContent redundant copy 1Content based routing is disabled for vod.cds.comContent based routing is disabled for kse.memContent based routing is disabled for kse.vod.cds.comThe following example shows how to display the proximity routing information on an SR:
ServiceRouter# sh service-router proximity-based-routingProximity based routing is enabledProximity cache timeout 600 secondsservice-router proximity-based-routing proximity-server 127.0.0.1The following example shows how to display the proximity routing cache information on an SR:
ServiceRouter# show service-router proximity-based-routing cache ip 171.XX.XXX.XXX----- Proximity cache information for 171.XX.XXX.XXX -----Cached proximity information on Fri Jul 30 05:19:50 2010SE Name: XX-CDE220-FiberRating : 3758096385SE Name: XX-CDE250-CE-2Rating : 3758096385SE Name: XXXX-SRRating : 3758096385SE Name: XXX-CDE220-1Rating : 3758096385SE Name: XXX-CDE250-2Rating : 3758096385SE Name: XX-CDE420-1Rating : 3758096385SE Name: XXX-CDE420-1Rating : 3758096385The following example shows how to display 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 : 90%FMS : 90%MS : 90%NIC : 90%BURST COUNT : 1DISK : 80%DISKFAILCNT : 1Sample periods configured:--------------------------CPU : 1 (secs)MEM : 1 (secs)KMEM : 1 (secs)WMT : 1 (secs)FMS : 1 (secs)NIC : 3 (secs)DISK : 1 (secs)Sample counts configured to use in calculating average:-------------------------------------------------------CPU : 2MEM : 2KMEM : 2WMT : 2FMS : 2NIC : 2DISK : 2Device Status-------------CPUCurrent load : 35%Average load : 35%Threshold : Not reachedDISKCurrent load : 20%Average load : 20%Threshold : Not reachedStatus : OperationalMEMAverage Used Memory : 10%Threshold : Not reachedKMEMAverage Kernel Memory : 1%Threshold : Not reachedNICInterface : PortChannel 1/0Average BW In : 9%Average BW Out : 9%Threshold : Not reachedAverage Device load : 35%Services Status---------------Critical Service(s) : RunningWEBEnabled : YesThreshold : Not reachedStopped : NoWMTEnabled : YesCurrent Stream Count : 0Threshold : Not reachedStopped : NoMSEnabled : NoFMSEnabled : NoThe following example shows how to display the Service Router information on the CDSM:
CDSM# show service-router service-monitorAlarm types configured:-------------------------AUGMENTATION ALARM : DisabledMonitor types configured:-------------------------CPU,MEM,KMEM,DISKThreshold values configured:---------------------------CPU : 80%MEM : 80%KMEM : 50%DISK : 80%DISKFAILCNT : 75%AUGMENTATION: 80%Sample 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 : 1%Average load : 1%Threshold : Not reachedDISKCurrent load : 1%Average load : 0%Load Threshold : Not reachedDisk Fail Cnt Threshold : Not reachedMEMAverage Used Memory : 6%Threshold : Not reachedKMEMAverage Kernel Memory : 0%Threshold : Not reachedAverage Device load : 1%CDSM#The following example shows how to display the domains to which the SR is subscribed:
ServiceRouter# show service-router subscribe domainDomains subscribed:test1.comtest5.comtest4.comtest3.comRelated Commands
service-router
Configures service routing.
clear service-router
Clears the proximity-based routing proximity cache.
show services
To display services-related information, use the show services command in EXEC configuration mode.
show services {ports [port_num] | summary}
Syntax Description
ports
Displays services by port number.
port_num
(Optional) Displays up to eight port numbers. The port number range is from 1 to 65535.
summary
Displays the services summary.
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following example shows how to display 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 shows how to display 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 command in EXEC configuration mode.
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.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
This command provides information on various SNMP variables and statistics on SNMP operations.
Table 3-64 describes the fields shown in the snmp alarm-history display.
Table 3-64 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 3-65 to map module names to module IDs.
Category
Traps sent by an CDS device contain numeric category IDs. See Table 3-66 to map category names to category IDs.
Descr
Description of the Internet Streamer CDS software alarm and the application that generated the alarm.
Table 3-65 describes the mapping of module names to module IDs.
Table 3-66 describes the mapping of category names to category IDs.
Table 3-66 Mapping of Category Names to Category IDs
Communications
1
Service Quality
2
Processing Error
3
Equipment
4
Environment
5
Content
6
Table 3-67 describes the fields shown in the show snmp stats display.
Table 3-68 describes the fields shown in the show snmp engineID display.
Table 3-68 show snmp engineID Field Descriptions
Local SNMP Engine ID
String that identifies the copy of SNMP on the local device.
Table 3-69 describes the fields shown in the show snmp group display.
Table 3-70 describes the fields shown in the show snmp user display.
Related Commands
snmp-server community
Configures the community access string to permit access to the SNMP1 .
snmp-server contact
Sets the system server contact (sysContact) string.
snmp-server enable traps
Enables the SE to send SNMP traps.
snmp-server group
Defines a user security model group.
snmp-server host
Specifies the recipient of a host SNMP trap operation.
snmp-server location
Sets the SNMP system location string.
snmp-server notify inform
Configures the SNMP notify inform request.
snmp-server user
Defines a user who can access the SNMP server.
snmp-server view
Defines a SNMP V2 MIB view.
1 SNMP = Simple Network Management Protocol
show srp database
To display the descriptor-related information saved in the descriptor database, use the show srp database command in privileged EXEC configuration mode.
show srp database [key | active | brief | content | expired | group | statistics | maincontent target_string | record key target_string | service | size low high | subid key target_string | update start end]
Syntax Description
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command displays information saved in the descriptor database and filters the data based on the argument that is specified. Without specifying any key or argument, it displays a summary of the descriptor database, which contains the DHT key and size for each descriptor and the total number of active descriptors in the database.
By providing the DHT key in hexadecimal format or various filtering arguments, show srp database filters through the descriptor database or a particular descriptor to obtain the desired information. Keys with less than 64 hexadecimal characters are appended with zeroes.
In filtering arguments that have a target string, the specified string is case sensitive.
Examples
The following examples show the output show srp database displays with and without a DHT key and the optional filtering arguments that specify how to query the database to obtain desired information. All the examples are based on querying the same descriptor database.
The following example is sample output from the show srp database command when it is issued with no keywords or arguments.
ServiceRouter# show srp databaseDHT KEY : SIZE0a1405495f14dfc1d6fd10b93d957903456166d3b7b883b9047fb89cbecb5157: 10541230000000000000000000000000000000000000000000000000000000000000: DELETED15136e3cfb5c3de3c4258d5c16c1bbabc5ddb538b51b32bdc1ebbd9bcb75b6d7: 8382340000000000000000000000000000000000000000000000000000000000000: 1683392b8bfe67c12c326aa346bdff1e83ac6286e397ce0013f8c4a33fc4dc5abda: 1065352a5e7e0e3dd9b78ab18fdb4408191f8418439b3ffef79f9b0698b8a73c16bc: 85339da9f8b45b6a186fdfdb6eec44ab71e7510c1de7b1b049df7c971696cb398a0: 10744e346a0c197a6e1e69650badd1687557dc4d9b80789407a9b452eda761f1056e: 10564f9400b0372d934d5819f3e88f4ad5be2177e96b79ee34aca49722e2db9ff300: 11027770000000000000000000000000000000000000000000000000000000000000: 1297890000000000000000000000000000000000000000000000000000000000000: 1098880000000000000000000000000000000000000000000000000000000000000: 1678d3e7478a3685decd322f891ea5a09a6b264097ab166d5b7bedd5ad9715f1401: 10489990000000000000000000000000000000000000000000000000000000000000: 183a6c4ef5b73c5b5621567946e7691b3d1123f9a3cf8b28ce29a075bfa41cb21ad: 1068c1898f9a8b69c3912f0fe8fecac30818fab24385fa8a1d37a8ffd193cf3eeebc: 324c53126d4113799d7f300c6accf526423756efa5e007fc3cc16fe45a9c8c06ee3: 881ca1329d38687cdd5f8ab7aabe4333ee7883a6a28f7e8b03e11d58bb3f4c39988: 1057cbb037edbe196fbf8d0f5bfa6e629ff1242483f5f5450719748189cf9d7b1fa4: 1086e50dc5cca2b736d00c41506b754c7bd331ab38826a4df396f6343a81e5631832: 843e8ca53dbcf748505194a10c9b6fa1549f309345f19b4d4df920be79d5e986471: 1083f47ec4f84068b9fda926f4767d2219f4faeabbbb0738312f70917504a0c8c9b9: 863Total 21 active item(s) in the databaseServiceRouter#The preceding example shows that there are 22 entries in the database, of which 21 are active ones. If a descriptor is active (has not been deleted), then its size is displayed. Otherwise, DELETED is displayed in the SIZE field of the descriptor. If the descriptor database is empty, the following output is displayed:
ServiceRouter# show srp databaseDHT KEY : SIZETotal 0 active item(s) in the databaseServiceRouter#The following is sample output from the show srp database key command where the DHT key is 234:
ServiceRouter# show srp database 234Getting database entry for234Entity key:2340000000000000000000000000000000000000000000000000000000000000Entity rec type: 101 Entity total length: 168Entity type: 5783093e Entity flags: 0--------------- Element 0 (main)-----------------Element ID: mainElement total len 45 ID len: 0Delete Time: 47af31d505d8fb77Flags 8Last Update: Sun Feb 10 17:18:34 2008 (47af31ea077ac2e7)Expiration : Tue Mar 11 17:18:34 2008 (47d6beea077a0000)Element data len: 5Element data:test--------------- Element 1 (comp)-----------------Element ID: "123"(313233)Element total len 51 ID len: 3Last Update: Sun Feb 10 17:24:40 2008 (47af335826c5288f)Expiration : Sun Feb 10 17:29:40 2008 (47af348426c50000)Element data len: 8Element data:testingServiceRouter#In the preceding example, the output is detailed information saved for the descriptor 234:
•
•
•
•
•
–
–
The following is sample output from show srp database key command where the DHT key is 123. In this example, the entity specified by the key has been deleted.:
ServiceRouter# show srp database 123Getting database entry for123Entity key:1230000000000000000000000000000000000000000000000000000000000000Entity was DELETED on (47b1fabdd076fba7) Tue Feb 12 19:59:57 2008ServiceRouter#The following is abbreviated sample output from the show srp database command when it is issued with the optional argument brief:
ServiceRouter# show srp database briefKey: 0a1405495f14dfc1d6fd10b93d957903456166d3b7b883b9047fb89cbecb5157Type: Regular Entity Type: Service Size: 1054Body: <Service xmlns="urn:topos:descriptor:xmlKey: 0a1405495f14dfc1d6fd10b93d957903456166d3b7b883b9047fb89cbecb5157Type: Regular Entity Type: Service Size: 1054Body: <Service xmlns="urn:topos:descriptor:xml... Output omittedKey: 7770000000000000000000000000000000000000000000000000000000000000Type: Mcast Cmd Entity Type: Group Size: 129Body: ....................test.Key: 7890000000000000000000000000000000000000000000000000000000000000Type: Regular Entity Type: Group Size: 109Body: test.Key: 8880000000000000000000000000000000000000000000000000000000000000Type: Regular Entity Type: Unknown(0) Size: 167Body: test... Output omittedTotal 21 active item(s) in the databaseServiceRouter#In the preceding example, show srp database brief displays brief information for each descriptor in the database, including DHT key, Type, Entity Type, Size, and Body (the initial part of the Element Data in Element 0 of the descriptor). The Body contains different information, depending on the type of the descriptor displayed.
•
•
The following is sample output from the show srp database command when it is issued with the filtering argument content. There are no content-type descriptors in the database:
ServiceRouter# show srp database contentTotal 0 content type descriptor(s) in the databaseServiceRouter#The following is sample output from the show srp database command when it is issued with the filtering argument service. There are 16 service-type descriptors in the database:
ServiceRouter# show srp database service0a1405495f14dfc1d6fd10b93d957903456166d3b7b883b9047fb89cbecb5157: Size: 105415136e3cfb5c3de3c4258d5c16c1bbabc5ddb538b51b32bdc1ebbd9bcb75b6d7: Size: 8382340000000000000000000000000000000000000000000000000000000000000: Size: 1683392b8bfe67c12c326aa346bdff1e83ac6286e397ce0013f8c4a33fc4dc5abda: Size: 1065352a5e7e0e3dd9b78ab18fdb4408191f8418439b3ffef79f9b0698b8a73c16bc: Size: 85339da9f8b45b6a186fdfdb6eec44ab71e7510c1de7b1b049df7c971696cb398a0: Size: 10744e346a0c197a6e1e69650badd1687557dc4d9b80789407a9b452eda761f1056e: Size: 10564f9400b0372d934d5819f3e88f4ad5be2177e96b79ee34aca49722e2db9ff300: Size: 11028d3e7478a3685decd322f891ea5a09a6b264097ab166d5b7bedd5ad9715f1401: Size: 1048a6c4ef5b73c5b5621567946e7691b3d1123f9a3cf8b28ce29a075bfa41cb21ad: Size: 1068c53126d4113799d7f300c6accf526423756efa5e007fc3cc16fe45a9c8c06ee3: Size: 881ca1329d38687cdd5f8ab7aabe4333ee7883a6a28f7e8b03e11d58bb3f4c39988: Size: 1057cbb037edbe196fbf8d0f5bfa6e629ff1242483f5f5450719748189cf9d7b1fa4: Size: 1086e50dc5cca2b736d00c41506b754c7bd331ab38826a4df396f6343a81e5631832: Size: 843e8ca53dbcf748505194a10c9b6fa1549f309345f19b4d4df920be79d5e986471: Size: 1083f47ec4f84068b9fda926f4767d2219f4faeabbbb0738312f70917504a0c8c9b9: Size: 863Total 16 service type descriptor(s) in the databaseServiceRouter#The following is sample output from the show srp database command when it is issued with the filtering argument group. There are three group-type descriptors in the database:
ServiceRouter# show srp database group7770000000000000000000000000000000000000000000000000000000000000: Size: 3939990000000000000000000000000000000000000000000000000000000000000: Size: 307c1898f9a8b69c3912f0fe8fecac30818fab24385fa8a1d37a8ffd193cf3eeebc: Size: 124Total 3 group type descriptor(s) in the databaseServiceRouter#The following is sample output from the show srp database command when it is issued with the option statistics. The output indicates how many descriptors (including deleted ones) exist in the descriptor database:
ServiceRouter# show srp database statisticsTotal number of descriptors = 22ServiceRouter#The following is sample output from the show srp database command when it is issued with the filtering argument maincontent and the target string service. The sample output indicates that there are 15 descriptors in the database whose main content (that is, the Element Data field of Element 0) contains the target string service:
ServiceRouter# show srp database maincontent service0a1405495f14dfc1d6fd10b93d957903456166d3b7b883b9047fb89cbecb5157: Type: 101Rec Type: 5783093e Size: 105415136e3cfb5c3de3c4258d5c16c1bbabc5ddb538b51b32bdc1ebbd9bcb75b6d7: Type: 101Rec Type: 5783093e Size: 8383392b8bfe67c12c326aa346bdff1e83ac6286e397ce0013f8c4a33fc4dc5abda: Type: 101Rec Type: 5783093e Size: 1065352a5e7e0e3dd9b78ab18fdb4408191f8418439b3ffef79f9b0698b8a73c16bc: Type: 101Rec Type: 5783093e Size: 85339da9f8b45b6a186fdfdb6eec44ab71e7510c1de7b1b049df7c971696cb398a0: Type: 101Rec Type: 5783093e Size: 10744e346a0c197a6e1e69650badd1687557dc4d9b80789407a9b452eda761f1056e: Type: 101Rec Type: 5783093e Size: 10564f9400b0372d934d5819f3e88f4ad5be2177e96b79ee34aca49722e2db9ff300: Type: 101Rec Type: 5783093e Size: 11028d3e7478a3685decd322f891ea5a09a6b264097ab166d5b7bedd5ad9715f1401: Type: 101Rec Type: 5783093e Size: 1048a6c4ef5b73c5b5621567946e7691b3d1123f9a3cf8b28ce29a075bfa41cb21ad: Type: 101Rec Type: 5783093e Size: 1068c53126d4113799d7f300c6accf526423756efa5e007fc3cc16fe45a9c8c06ee3: Type: 101Rec Type: 5783093e Size: 881ca1329d38687cdd5f8ab7aabe4333ee7883a6a28f7e8b03e11d58bb3f4c39988: Type: 101Rec Type: 5783093e Size: 1057cbb037edbe196fbf8d0f5bfa6e629ff1242483f5f5450719748189cf9d7b1fa4: Type: 101Rec Type: 5783093e Size: 1086e50dc5cca2b736d00c41506b754c7bd331ab38826a4df396f6343a81e5631832: Type: 101Rec Type: 5783093e Size: 843e8ca53dbcf748505194a10c9b6fa1549f309345f19b4d4df920be79d5e986471: Type: 101Rec Type: 5783093e Size: 1083f47ec4f84068b9fda926f4767d2219f4faeabbbb0738312f70917504a0c8c9b9: Type: 101Rec Type: 5783093e Size: 863Total 15 item(s) in the database whose main content contains'service'ServiceRouter#The following is sample output from the show srp database command when it is issued with the filtering argument record to search in a descriptor specified by the key 999 to locate records containing the target string test. The examples are in the following order:
•
•
•
ServiceRouter# show srp database record 999 testEntity key:9990000000000000000000000000000000000000000000000000000000000000Entity rec type: 101 Entity total length: 183Entity type: 22222222 Entity flags: 0--------------- Element 1 (comp)-------4----------Element ID: "123"(313233)Element total len 47 ID len: 3Last Update: Tue Feb 12 02:07:38 2008 (47b0ff6ae5e0497b)Expiration : Thu Mar 13 02:07:38 2008 (47d88c6ae5e00000)Element data len: 4Element data:testServiceRouter# show srp database record 123 testEntity key:1230000000000000000000000000000000000000000000000000000000000000Entity was DELETED on (47b1fabdd076fba7) Tue Feb 12 19:59:57 2008ServiceRouter# show srp database record 777 testEntity key:7770000000000000000000000000000000000000000000000000000000000000Entity rec type: 102 Entity total length: 129Entity type: 22222222 Entity flags: 0There is no resource record containing testServiceRouter#The following is sample output from the show srp database command when it is issued with the filtering argument size to select descriptors whose size is in the given range. This example shows that, for the active descriptors, there are five descriptors whose size is larger than 100 bytes and smaller than 300 bytes:
ServiceRouter# show srp database size 100 3002340000000000000000000000000000000000000000000000000000000000000: Type: 101Rec Type: 5783093e Size: 1687770000000000000000000000000000000000000000000000000000000000000: Type: 102Rec Type: 22222222 Size: 1297890000000000000000000000000000000000000000000000000000000000000: Type: 101Rec Type: 22222222 Size: 1098880000000000000000000000000000000000000000000000000000000000000: Type: 101Rec Type: 0 Size: 1679990000000000000000000000000000000000000000000000000000000000000: Type: 101Rec Type: 22222222 Size: 183Total 5 item(s) in the database whose size is between 100 and 300ServiceRouter#The following example is sample output from the show srp database command when it is issued with the filtering argument subid to search for elements in a given descriptor whose Element ID contains the given target string. In this example, the search is in the descriptor whose key is 999 and for elements whose sub ID (Element ID) is 123. The output indicates one element, Element 1, with the specified Element ID 123.
ServiceRouter# show srp database subid 999 123Entity key:9990000000000000000000000000000000000000000000000000000000000000Entity rec type: 101 Entity total length: 183Entity type: 22222222 Entity flags: 0--------------- Element 1 (comp)-----------------Element ID: "123"(313233)Element total len 47 ID len: 3Last Update: Tue Feb 12 02:07:38 2008 (47b0ff6ae5e0497b)Expiration : Thu Mar 13 02:07:38 2008 (47d88c6ae5e00000)Element data len: 4Element data:testServiceRouter#The following example is sample output from the show srp database command when it is issued with the filtering argument update to select descriptors that have been updated in the specified time range. The command uses the Last Update field of Element 0 to determine when the descriptor has been updated. The sample output indicates that four descriptors have been updated in the specific time range.
ServiceRouter# show srp database update Feb_11_02:07:38_2008 Feb_12_02:07:38_20097770000000000000000000000000000000000000000000000000000000000000: Type: 102Rec Type: 22222222 Size: 1298880000000000000000000000000000000000000000000000000000000000000: Type: 101Rec Type: 0 Size: 1679990000000000000000000000000000000000000000000000000000000000000: Type: 101Rec Type: 22222222 Size: 183c1898f9a8b69c3912f0fe8fecac30818fab24385fa8a1d37a8ffd193cf3eeebc: Type: 102Rec Type: 22222222 Size: 324Total 4 active item(s) in the database updated in the specified time durationServiceRouter#Related Commands
show srp leafset
To display SRP leafset information, use the show srp leafset command in privileged EXEC configuration mode.
show srp leafset
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command displays leafset information for the current Proximity Engine (the local node). The current Proximity Engine must be part of a properly configured DHT network for leafset information about network members to be displayed.
Examples
The following example shows the output from show srp leafset when the current Proximity Engine is a standalone node and not a member of a DHT network:
ServiceRouter# show srp leafsetCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - Intransitive, W - wrappedLeafset count: total 5, left 2, right 2T d2fc632c53c9ff1de8683e265386b09502791aedd65f28025fe7f64ad8cab2d9via sn-sj87 [ 172.20.168.87 ] :9000ServiceRouter#Table 3-71 describes the codes that show srp leafset uses in its output.
The following example shows the output from show srp leafset command when the current Proximity Engine is a member of a DHT network consisting of seven nodes: the local node in the middle, three nodes on the left, and three nodes on the right.
ServiceRouter# show srp leafsetCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - Intransitive, W - wrappedLeafset count: total 7, left 3, right 3WPL 0e33b4fc00ea5e32b7323c2a712cc226fe4990430df6ac9a05d2a87ab67c9faevia sn-sj43 [ 172.20.168.43, 192.168.20.10, 192.168.86.10 ] :9000,1.772254 ms, 00:00:08PL b5ca21563f5b938e46e2cb8f33a148ae00a1f6666f2a5eb735b7ed90c012c882via sn-sj82 [ 172.20.168.82, 192.168.82.82, 192.168.86.82 ] :9000,0.392633 ms, 00:00:08PL c89908f53cc3ab6bc6065fd545341e9868cab7dcf852eaa346dd470011fcff1dvia sn-sj89 [ 172.20.168.89 ] :9000, 0.352768 ms, 00:00:08T e966a1daec3ef3f1a81fec0e46338ae66eb7d154341e3a20fef0c5d2e8a0aabfvia sn-sj87 [ 172.20.168.87 ] :9000PL 0e33b4fc00ea5e32b7323c2a712cc226fe4990430df6ac9a05d2a87ab67c9faevia sn-sj43 [ 172.20.168.43, 192.168.20.10, 192.168.86.10 ] :9000,1.772254 ms, 00:00:08WPL b5ca21563f5b938e46e2cb8f33a148ae00a1f6666f2a5eb735b7ed90c012c882via sn-sj82 [ 172.20.168.82, 192.168.82.82, 192.168.86.82 ] :9000,0.392633 ms, 00:00:08WPL c89908f53cc3ab6bc6065fd545341e9868cab7dcf852eaa346dd470011fcff1dvia sn-sj89 [ 172.20.168.89 ] :9000, 0.352768 ms, 00:00:08ServiceRouter#Related Commands
bootstrap-node
Configures a bootstrap node IP address.
domain
Sets the domain ID for the SRP.
show srp memory
To display SRP memory usage information, use the show srp memory command in privileged EXEC configuration mode.
show srp memory
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command displays SRP memory usage information.
Examples
The following example shows the output from show srp memory command:
ServiceRouter# show srp memorySRP memory usage:Type Size Count HWM Slab Overhead TotalPacket 65536 2 0 0 0 131072Operation 192 92 0 0 0 18566Sync 120 0 0 0 0 0Pending 104 0 0 0 0 0Mcast Pend 40 0 0 0 0 0Proximity 104 0 0 0 0 0To IPPC 208 0 0 0 0 0Neighbor 384 2 2 128 48560 49328Neighbor EP 134 0 0 0 128 128Timer CTX 16 16 16 64 944 1200Packet Addr 32 0 2 0 128 128Subscriber 240 2 2 64 15056 15536Seq Req 88 0 0 0 128 128WorkQ 32 0 0 0 128 128Total: 65072 216214ServiceRouter#Related Commands
show srp multicast database
To display multicast database information for an SRP process, use the show srp multicast database command in privileged EXEC configuration mode.
show srp multicast database [group_id | brief | statistics]
Syntax Description
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command is used to display information saved in the multicast database. Without specifying any key or argument, show srp multicast database displays a summary of the multicast database. The summary contains the DHT key and size for each descriptor and the total number of active group descriptors in the database. By providing the DHT key in hexadecimal format or various filtering arguments, you can filter through the multicast database or a particular group descriptor to obtain desired information.
Examples
The following example is sample output from the show srp multicast database command when it is issued with no keywords or arguments:
ServiceRouter# show srp multicast databaseDHT KEY : SIZE1230000000000000000000000000000000000000000000000000000000000000: 10034444000000000000000000000000000000000000000000000000000000000000: 5227770000000000000000000000000000000000000000000000000000000000000: 5239990000000000000000000000000000000000000000000000000000000000000: 307c1898f9a8b69c3912f0fe8fecac30818fab24385fa8a1d37a8ffd193cf3eeebc: 124Total 5 active item(s) in the databaseServiceRouter#The preceding example shows that there are five active entries in the database. If a descriptor is active (has not been deleted), its size is displayed. If a descriptor has been deleted, DELETED is displayed in the SIZE field of the descriptor. If the descriptor database is empty, the following output is displayed:
ServiceRouter# show srp multicast databaseDHT KEY : SIZETotal 0 active item(s) in the databaseServiceRouter#The following is sample output from the show srp multicast database command when it is issued with the optional argument group_id. In this example, the DHT key for group_id is 4444:
ServiceRouter# show srp multicast database 4444Getting database entry for4444Entity key:4444000000000000000000000000000000000000000000000000000000000000Entity rec type: 103 Entity total length: 522Entity type: 22222222 Entity flags: 0--------------- Element 0 (main)-----------------Element ID: mainElement total len 65 ID len: 0Delete Time: 0000000000000000Flags 0Last Update: Tue Feb 12 21:47:20 2008 (47b213e8ec98be67)Expiration : Thu Mar 13 21:47:20 2008 (47d9a0e8ec980000)Element data len: 25Element data:Content Acquirerquence number: 0Data: test--------------- Element 1 (mcast)-----------------Element ID: "....U.......(# .."(95160500550106090000000028230000)Element total len 123 ID len: 16Last Update: Tue Feb 12 21:48:14 2008 (47b2141e24526623)Expiration : Thu Mar 13 21:48:14 2008 (47d9a11e24520000)Element data len: 67Element data:Content Acquirerquence number: 1Sender ID: d2fc632c53c9ff1de8683e265386b09502791aedd65f28025fe7f64ad8cab2d9Data: hello1--------------- Element 2 (mcast)-----------------Element ID: "....r@......(# .."(9916050072401b1f0000000028230000)Element total len 123 ID len: 16Last Update: Tue Feb 12 21:48:18 2008 (47b214227ce17ea3)Expiration : Thu Mar 13 21:48:18 2008 (47d9a1227ce10000)Element data len: 67Element data:Content Acquirerquence number: 2Sender ID: d2fc632c53c9ff1de8683e265386b09502791aedd65f28025fe7f64ad8cab2d9Data: hello2--------------- Element 3 (mcast)-----------------Element ID: "............(# .."(b0160500ae9e151c0000000028230000)Element total len 123 ID len: 16Last Update: Tue Feb 12 21:48:41 2008 (47b21439709c703b)Expiration : Thu Mar 13 21:48:41 2008 (47d9a139709c0000)Element data len: 67Element data:Content Acquirerquence number: 3Sender ID: d2fc632c53c9ff1de8683e265386b09502791aedd65f28025fe7f64ad8cab2d9Data: hello3ServiceRouter#In the preceding example, the output is detailed information saved for the multicast group 4444 including the following:
•
•
•
•
•
–
–
Related Commands
clear srp group messages
Deletes all locally stored messages sent to a multicast group in the service routing layer.
show srp neighbor
To display SRP neighbor information, use the show srp neighbor command in privileged EXEC configuration mode.
show srp neighbor [detail | down]
Syntax Description
detail
Displays detailed information for each neighbor.
down
Displays the information of down neighbor entries.
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command displays SRP neighbor information. The current Proximity Engine must be part of a properly configured DHT network for neighbor information about current network members to be displayed.
If the keyword down is specified, show srp neighbor displays down neighbors. These are Proximity Engines that are members of a DHT network the local Proximity Engine previously belonged to.
Examples
In the following example, assume a standalone Proximity Engine sn-sj87, and a two-node network consisting of Proximity Engine sn-sj81 and Proximity Engine sn-sj85. The show srp neighbor command is run from sn-sj87 before it is connected to the two-node network:
ServiceRouter# show srp neighborCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - Intransitive, D - delay, H - hold timeNumber of neighbors in the database: 0In the preceding example, sn-sj87 does not have any neighbor in the database.
In the following example, after sn-sj87 is added to the network, show srp neighbor is issued again. From the following output, we can see that sn-sj87 has two neighbors, sn-sj81 and sn-sj85:
ServiceRouter# show srp neighborCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - Intransitive, D - delay, H - hold timeNumber of neighbors in the database: 2PL 8886822171add71887d54107c266d814b605eaa0d5cc9b54b9160a137f4355d1via sn-sj81 [ 172.20.168.81 ] :9000, D=0.339605 ms,H=00:00:07PL 9f752f56f347ca8fcc40a4e09b645f9b4c9b71c73401083f4c04920b30215b0avia sn-sj85 [ 172.20.168.85, 192.168.20.85, 192.168.86.85 ] :9000,D=0.379999 ms, H=00:00:09To see details of these two neighbors, issue the show srp neighbor detail command:
ServiceRouter# show srp neighbor detailCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - IntransitiveD - delay, H - hold time, U - up timeS_SEQ - send seq no., R_SEQ - receive seq. no.S_SID - send session id, R_SID - receive session id,R_Q - Receive Queue, T_Q - Transmit Queue.Number of neighbors in the database: 2PL 8886822171add71887d54107c266d814b605eaa0d5cc9b54b9160a137f4355d1via sn-sj81 [ 172.20.168.81 ] :9000, D=0.302328 ms,H=00:00:08, U=02:15:53, S_SEQ=1, R_SEQ=0, S_SID=148214958, R_SID=0PL 9f752f56f347ca8fcc40a4e09b645f9b4c9b71c73401083f4c04920b30215b0avia sn-sj85 [ 172.20.168.85, 192.168.20.85, 192.168.86.85 ] :9000,D=0.379999 ms, H=00:00:10, U=01:45:42, S_SEQ=0, R_SEQ=0,S_SID=2134859630, R_SID=0The following example illustrates the usage of show srp neighbor down. Assume that a four-node network consists of Proximity Engines sn-sj43, sn-sj88, sn-sj44, and sn-sj87. From sn-sj87, the show srp neighbor down command can be used to confirm this, as shown by the following output:
ServiceRouter# show srp neighborCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - Intransitive, D - delay, H - hold timeNumber of neighbors in the database: 3PLI 0e33b4fc00ea5e32b7323c2a712cc226fe4990430df6ac9a05d2a87ab67c9faevia sn-sj43 [ 192.168.86.43 ] :9000, D=0.439602 ms,H=00:00:03PL 2a2db308fd3dc172940a7902a4db7c16c98c3a32e1b048005bce1e832b6d056fvia sn-sj88 [ 192.168.86.88 ] :9000, D=0.405537 ms,H=0.553618PL 9a28755bba0228c7ac3d1be20d21a7a57c532eed9d5ffc5e1da2a9841e2e77a8via sn-sj44 [ 192.168.86.44 ] :9000, D=0.398474 ms,H=00:00:01ServiceRouter# show srp neighbor downNumber of down neighbors in the database: 0Next down neighbor write offset: 0For the next example, assume that the domain ID for the local node (sn-sj87) is reconfigured so that it is detached from the network. The following output from show srp neighbor down now shows that all three neighbors are down:
ServiceRouter# show srp neighbor downNumber of down neighbors in the database: 3Next down neighbor write offset: 39a28755bba0228c7ac3d1be20d21a7a57c532eed9d5ffc5e1da2a9841e2e77a8via sn-sj44 [ 192.168.86.44 ] :9000, 0.000 ms, no-timer0e33b4fc00ea5e32b7323c2a712cc226fe4990430df6ac9a05d2a87ab67c9faevia sn-sj43 [ 192.168.86.43 ] :9000, 0.000 ms, no-timer2a2db308fd3dc172940a7902a4db7c16c98c3a32e1b048005bce1e832b6d056fvia sn-sj88 [ 192.168.86.88 ] :9000, 0.000 ms, no-timerRelated Commands
bootstrap-node
Configures a bootstrap node IP address.
domain
Sets the domain ID for an SRP.
show srp process
To display the basic configurations for SRP, use the show srp process command in privileged EXEC configuration mode.
show srp process
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command displays SRP process information.
Examples
The following example shows sample output from show srp process when it is run from Proximity Engine sn-sj87.
ServiceRouter# show srp processProcess:Domain: 0Node Id: d2fc632c53c9ff1de8683e265386b09502791aedd65f28025fe7f64ad8cab2d9Host name: sn-sj87Port: 9000Interfaces running SRP:*GigabitEthernet 1/0Bootstrap host name: 172.20.168.85, address: 172.20.168.85, port: 9000Database Mirroring: Disabled# of storages requested for mirroring: 2# of storages used for mirroring : 1ServiceRouter#Related Commands
show srp replica-set
To display the replica set information for a Proximity Engine, use the show srp replica-set command in privileged EXEC configuration mode.
show srp replica-set
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command displays SRP replica set information.
To use this command to show a replica set, a network needs to be formed by properly configuring a bootstrap node and domain ID.
Examples
The following examples show sample output from show srp replica-set. For the first example, assume a standalone Proximity Engine sn-sj87 and a two-node network consisting of Proximity Engine sn-sj81 and Proximity Engine sn-sj85. The show srp replica-set command is issued from sn-sj87 before it is connected to the two-node network:
ServiceRouter# show srp replica-setCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - intransitive, R - Replicate Set, A - activekey(part) address type state--------------------------------------------------308fe23f... EE7-CDE205-8:9000 PL Active5c71ac1e... EE7-CDE205-10:9000 PL Activefeb5784c...-> SN-CDSM:9000 local NoneServiceRouter#Related Commands
show srp leafset
Displays SRP leafset information,
show srp neighbor
Displays SRP neighbor information
show srp route
To display route information for a Proximity Engine to its neighbor nodes on the same DHT network, use the show srp route command in privileged EXEC configuration mode.
show srp route [backup | statistics]
Syntax Description
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command displays route information for a Proximity Engine to its neighbor nodes on the same DHT network.
To use this command to show route entries, a network needs to be formed by properly configuring a bootstrap node and domain ID.
Examples
The following examples show sample output from show srp route. For the first example, assume a standalone Proximity Engine sn-sj87 and a two-node network consisting of Proximity Engine sn-sj81 and Proximity Engine sn-sj85. The show srp route command is issued from sn-sj87 before it is connected to the two-node network. The output shows no srp route information, as is expected for a standalone Proximity Engine:
ServiceRouter# show srp routeCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - IntransitiveFor the following example, assume that Proximity Engine sn-sj87 has joined the two-node network consisting of Proximity Engine sn-sj81 and Proximity Engine sn-sj85. The output shows that sn-sj87 has route information to its two neighbors, sn-sj81 and sn-sj85.
ServiceRouter# show srp routeCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - IntransitivePL 8/4 via 8886822171add71887d54107c266d814b605eaa0d5cc9b54b9160a137f4355d1sn-sj81 [ 172.20.168.81 ] :9000, 0.301080 ms, 00:00:09PL 9/4 via 9f752f56f347ca8fcc40a4e09b645f9b4c9b71c73401083f4c04920b30215b0asn-sj85 [ 172.20.168.85, 192.168.20.85, 192.168.86.85 ] :9000, 0.382097 ms,00:00:08The show srp route command shows only primary routing table entries. In the SRP routing table, there are backup routes as well. To display the backup routes as well as the primary routes, use the command show srp route backup command:
ServiceRouter# show srp route backupCodes: T - local node, L - leafset, P - primary, S - secondary, B - backupI - IntransitivePL 8/4 via 8886822171add71887d54107c266d814b605eaa0d5cc9b54b9160a137f4355d1sn-sj81 [ 172.20.168.81 ] :9000, 0.301080 ms, 00:00:07PL 9/4 via 9f752f56f347ca8fcc40a4e09b645f9b4c9b71c73401083f4c04920b30215b0asn-sj85 [ 172.20.168.85, 192.168.20.85, 192.168.86.85 ] :9000, 0.382097 ms,00:00:10ServiceRouter#Because there is no backup route in this small three-node network, show srp route backup displays the same results as show srp route. This can be confirmed by issuing the show srp route statistics command as shown in the following example. From the following output, we can confirm that are total two routes in the routing table, one appearing in cell 8 row 0 (which is the route via sn-sj81) and the other appearing in cell 9 row 0 (which is the route via sn-sj85).
ServiceRouter# show srp route statisticsTotal routes: 2Entries that share my prefix: 0Last nonempty row: 0ServiceRouter#Related Commands
show srp leafset
Displays SRP leafset information.
show srp neighbor
Displays SRP neighbor information.
show statistics srp
Displays SRP statistics information.
show srp subscribers
To display SRP multicast group subscriber information, use the show srp subscribers command in privileged EXEC configuration mode.
show srp subscribers
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
Privileged EXEC configuration mode.
Usage Guidelines
This command is used to check what multicast groups the Proximity Engine is currently subscribed to. If the Proximity Engine is not subscribed to any groups, there is no output.
Examples
In the following example, assume a standalone Proximity Engine sn-sj87:
1.
2.
3.
ServiceRouter# show srp subscribersc1898f9a8b69c3912f0fe8fecac30818fab24385fa8a1d37a8ffd193cf3eeebcRoot node: d2fc632c53c9ff1de8683e265386b09502791aedd65f28025fe7f64ad8cab2d9Subscriber: 0x6891a0ServiceRouter# show srp subscribers9990000000000000000000000000000000000000000000000000000000000000Root node: 8886822171add71887d54107c266d814b605eaa0d5cc9b54b9160a137f4355d1Subscriber: 0x6891a0c1898f9a8b69c3912f0fe8fecac30818fab24385fa8a1d37a8ffd193cf3eeebcRoot node: d2fc632c53c9ff1de8683e265386b09502791aedd65f28025fe7f64ad8cab2d9ServiceRouter#show ssh
To display Secure Shell (SSH) status and configuration information, use the show ssh command in EXEC configuration mode.
show ssh
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Related Commands
show standby
To display standby interface information, use the show standby command in EXEC configuration mode.
show standby
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-72 describes the fields shown in the show standby display.
Related Commands
show startup-config
To display the startup configuration, use the show startup-config command in EXEC configuration mode.
show startup-config
Syntax Description
This command has no keywords or arguments.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Use this command to display the configuration used during an initial bootup, stored in non-volatile random-access memory (NVRAM).
Examples
The following example shows how to display the startup configuration details on the SE:
ServiceEngine# show startup-config! CDS version 2.3.9!device mode service-engine!!hostname V2-CDE220-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
show statistics aaa
To display SE access control list statistics, use the show statistics access-lists 300 command in EXEC configuration mode.
show statistics aaa
Syntax Description
This command has no keywords or arguments.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-73 describes the fields shown in the show statistics aaa display.
Related Commands
aaa
Specifies accounting, authentication and authorization methods.
show aaa
Displays the accounting, authentication and authorization configuration.
show statistics access-lists 300
To display SE access control list statistics, use the show statistics access-lists 300 command in EXEC configuration mode.
show statistics access-lists 300
Syntax Description
This command has no keywords or arguments.
Command Defaults
None
Command Modes
EXEC configuration mode.
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.
Table 3-74 describes the fields shown in the show statistics access-lists 300 display.
Related Commands
clear
Clears the HTTP object cache, the hardware interface, statistics, archive working transaction logs, and other settings.
show statistics acquirer
To display SE acquirer channel statistics, use the show statistics acquirer command in EXEC configuration mode.
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
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The show statistics acquirer command displays acquirer statistics for all channels for which the SE is the Content Acquirer. 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.
Table 3-75 describes the fields shown in the show statistics acquirer display.
Table 3-76 describes the fields shown in the show statistics acquirer contents delivery-service-name display.
Examples
The following example shows how to display the acquirer statistics for the Delivery Service name settur-ds:
ServiceEngine# show statistics acquirer contents deliver-service-name settur-dsQuerying Database.......Contents Acquired for the Delivery Service Name :settur-ds---------------------------------------Acquired Contents:----------------------Modification Time : Fri Aug 1 06:08:26 2008Size : 128899758 BytesUrl : http://172.XX.XX.XX/300kbs.wmvModification Time : Wed May 21 08:58:17 2008Size : 174569021 BytesUrl : http://172.XX.XX.XX/1mbps.movModification Time : Wed May 11 09:19:17 2011Size : 425468369 BytesUrl : http://172.XX.XX.XX/flash_1mbps.mp4Modification Time : Mon Jun 20 10:15:37 2011Size : 22952732 BytesUrl : http://172.XX.XX.XX/sample.mpegRelated Commands
show statistics admission
To display admission control statistics, use the show statistics admission command in EXEC configuration mode.
show statistics admission
Syntax Description
This command has no keywords or arguments.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-77 describes the fields shown in the show statistics admission display.
show statistics authsvr
To view the Authentication Server statistics, use the show statistics authsvr command in EXEC configuration mode.
show statistics authsvr {delivery-service-id num {detail | geo | ip | rules} | global}
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
The output of the show statistics authsvr command displays Rules statistics based on the rules configured through the XML. If Rule_Allow is configured, then the statistics for Rule_Allow must be incremented whether or not any other rule is configured. If the Rule_Allow or Rule_Block is not configured but Rule_UrlRewrite is configured, then the statistics of Rule_UrlRewrite are incremented. Similarly, if the Rule_Block is configured along with Rule_UrlRewrite, then the statistics of Rule_Block and Rule_UrlRewrite are incremented.
When Unknown Server Requests is enabled, a request for an unknown server increments both the Allowed counter and the Unknown Server Allowed counter. When Unknown Server Request is disabled, a request for an unknown server increments both the Blocked counter and the Unknown Server Blocked counter.
The show statistics authsvr delivery-service-id command displays statistics for each delivery service and for each rule in the delivery service. All the statistics are based on the Authsvr Rules configured in the XML file for a particular delivery service.
Table 3-78 describes the fields shown in the show statistics authsvr delivery-service-id detail display.
Table 3-79 describes the fields shown in the show statistics authsvr global display.
Examples
The following shows how to display the Authentication Server delivery service ID detail statistics:
ServiceEngine# show statistics authsvr delivery-service-id 1 detailIP Statistics ---------------- Allow : 200 Block : 10Geo Statistics ------------------- Allow : 23 Block : 10Rules Statistics ---------------------- Rule_Allow : 134 Rule_Block : 23 Rule_ForcedReValidate : 12 Rule_NoCache : 16 Rule_SwfFileValidate : 5 Rule_UrlRedirect : 7 Rule_UrlResolve : 10 Rule_UrlRewrite : 3ServiceEngine#The following shows how to display the Authentication Server global statistics:
ServiceEngine# show statistics authsvr globalAuthserver Statistics---------------------Allowed : 4329108Blocked : 0Unknown Server Allowed : 10Unknown Server Blocked : 0Errors : 0ServiceEngine#Related Commands
authsvr
Enables and configures the Authorization server.
show authsvr
Displays the status of the Authorization server.
show statistics cdn-select
To view the CDN Selector statistics, use the show statistics cdn-select command in EXEC configuration mode.
show statistics cdn-select summary
Syntax Description
Command Defaults
None
Command Modes
EXEC configuration mode.
Examples
The following is sample CDN Selector statistics:
ServiceRouter# show statistics cdn-select summary----- CDN Selector Summary Statistics -----Requests Received : 0Requests Redirected (3rd party) : 0Requests Routed (CDS-IS) : 0Requests Not Redirected : 0CDN Errors : 0ServiceRouter#Related Commands
show statistics cdnfs
To display SE CDS network file system (cdnfs) statistics, use the show statistics cdnfs command in EXEC configuration mode.
show statistics cdnfs
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-80 describes the show statistics cdnfs command fields displayed in the command output.
Related Commands
show statistics content-mgr
To display Content Manager statistics, use the show statistics content-mgr command in EXEC configuration mode.
show statistics content-mgr
Syntax Description
This command has no arguments or keywords.
Command Defaults
None
Command Modes
EXEC configuration mode.
Usage Guidelines
Table 3-81 describes the show statistics content-mgr command fields displayed in the command output.
Related Commands-
