Specifications

A-33
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Appendix A Troubleshooting
Streaming and Playout Issues
Listing of Streams
To monitor streams based on various criteria, go to the Stream Monitor page in the CDSM GUI by
clicking Monitor > System Level > Stream Monitor. For more information, see the “Stream Monitor”
section on page 5-16.
No Streaming
Some common causes for streaming problems are the following:
• Server is in the process of being offloaded.
• QAM device has no available bandwidth.
• Tuning failure because of one of the following:
– Error in the ARP table
– QAM device is down
– Network problem
• Backoffice is out of synchronization with the CDS ContentStore, resulting in content not being
found.
Following are some general methods for troubleshooting stream and playout issues:
• View the /arroyo/log/streamevent.log.<date> file for stream setup activity.
• Check for GOIDs in the /arroyo/log/c2k.log.<date> file.
• Check if the stream setup is using /home/isa/IntegrationTest/list_all_streams or
/home/isa/IntegrationTest/list_a_stream.
• View the /home/isa/Berkeley/dumpDB file and use the vi ctnobj.lst command to check that the
Vaults are synchronized.
• Check content integrity by looking at the objectStatus for damaged GOIDs.
Stream Not Playing
Cause 1: A piece of content is missing.
In this case, a user can typically stream part of the content, but at some point the stream stops
and this error is returned in the ANNOUNCE message. The content needs to be validated at the
CServer level.
Action 1: Set up a stream to play to a multicast address.
If this is successful, then there is a network issue, which is either a default gateway or
unreachable remote client. You can verify whether it is successful by looking at the
/home/stats/ifstats information.
Action 2: If ifstats information does not detect a problem, try streaming to another multicast IP address.
Repeat streaming to a multicast address with different content and, if possible, ingest known
good content. Check the protocoltiming.log.<date> for damaged GOIDs by using the following
command:
tail -f protocoltiming.log.<latest date> | grep Goids
Cause 2: There is a problem reaching the destination QAM device.