Cisco Cisco Internet Streamer Application Release Notes

CSCte42043

Symptom:

Windows Media request fails in particular scenario.

Condition:

When a badly formed URL request is sent for Windows Media content.

Workaround:

None. Do not use badly formed URLs in client requests.

CSCtf67983

Symptom:

Content with a bad MD-5 sum does not get removed and reingested on one of the SEs.  It replicated 
fine to all other SEs, except the one SE where the content was not removed. 

Condition:

In Release 2.4.3, an SE gets a bad copy of content and the MD-5 sum fails. The bad copy is not 
removed, so MD-5 sum is repeated in acquisition and distribution logs.

Workaround:

Delete the asset from the SE, wait for the replication to run again without errors, reingest the 
content, then have the replication run again.

The following caveats have been resolved since Cisco Internet Streamer CDS Release 2.5.3 Not all the 
resolved issues are mentioned here. The following list highlights the resolved caveats associated with 
customer deployment scenarios.

CSCtd16093

Symptom:

CDS-IS software does not currently support the lowering of SMART alarms. Should an event which 
triggers a SMART alarm clear, the SMART alarm will remain raised until the CDS-IS system has 
been reloaded. 

For a CDS-IS system, the typical SMART alarm pertains to drive failure prediction, and will be 
raised whenever a hard drive predicts its own imminent failure. The nature of this type of alarm is 
persistent. Once the prediction is made, it will not be cleared. Once more, because CDS-IS only 
supports replacing failed drives across reboot, the consequence of not lowering the alarm will go 
largely unnoticed.