Specifications

A-2
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Appendix A Troubleshooting
Troubleshooting the Distribution Hierarchy
– Is there a delivery service created for the requested domain and a serving Service Engine
assigned to this delivery service? See the “Creating Delivery Service” section on page 5-4.
– Is the serving Service Engine alive? Use the show statistics service-routing se command to
show the status of a Service Engine. See the “Using show and clear Commands” section on
page 7-9.
• Content prefetched on a Service Engine
– Is a Manifest file assigned to the delivery service associated with the serving Service Engine?
See the “Working with Manifest Files” section on page B-2.
– Is the Manifest file accessible from the CDSM? See the “Identifying Content Using a Manifest
File” section on page 5-22.
– Is there any syntax error in the Manifest file? See the “Manifest File Structure and Syntax”
section on page B-17.
– Is the requested content specified in the Manifest file? See the “Specifying a Single Content
Item” section on page B-2.
– If the requested content is streaming media, is the protocol engine enabled? See the
“Application Control” section on page 4-28.
Troubleshooting the Distribution Hierarchy
Because distribution-related problems are design-dependent, your initial strategy is to discover whether
or not the correct Service Engine is sending content in the correct distribution path.
• To determine which Service Engines are in the distribution path of a particular Service Engine, use
the show distribution remote traceroute EXEC command, as shown in the following example:
ce1# show distribution remote traceroute ?
forwarder-next-hop next forwarder along the path
unicast-sender check status for unicast sender
ce1# show distribution remote traceroute forwarder-next-hop ?
delivery-service-id Delivery-service-id of a Delivery Service
ce1# show distribution remote traceroute forwarder-next-hop delivery-service-id 133 ?
max-hop Trace route till specified number of hops is reached
trace-till-good traceroute till probe is good or the object is found
trace-till-root traceroute till the acquirer
ce1# show distribution remote traceroute forwarder-next-hop delivery-service-id 133
trace-till-root
Hop NextHop_SEId NextHop_SEName NextHop_SEIp GenID Status/Reason
--- ------------ -------------- ------------ ----- -------------
1 1100 ce3 10.255.0.43 1 LOC-LEAD
1 1100 ce3 128.107.193.183 1 LOC-LEAD (Reached RootCE)
• To verify that the Service Engine is reachable and that it is in the distribution hierarchy, use the show
distribution remote traceroute EXEC command, as shown in the following example:
se1# show distribution remote traceroute unicast-sender delivery-service-id 133 ?
cdn-url check the object on remote SE using cdn-url
probe probe the remote unicast sender
relative-cdn-url check the object on remote SE using relative-cdn-url