Downloads |
 Feedback
|
Table Of Contents
Release Notes for Cisco TV CDS 3.0.2
Upgrading from Release 2.5.2, 2.5.3, 2.5.5, 2.5.6, or 3.0.1 to Release 3.0.2
Downgrading from Release 3.0.2
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco TV CDS 3.0.2
These release notes cover Cisco TV CDS Release 3.0.2.
Revised: July 2012 OL-27184-01Contents
The following information is in the release notes:
•
Obtaining Documentation and Submitting a Service Request
Enhancements
The following enhancements have been added in Release 3.0.2:
•
•
The /etc/hosts file can be updated any time and the Streamer can be made aware of the changes in the /etc/hosts file by entering the following command:
echo 1 > /proc/calypso/tunables/read_etc_hosts•
–
–
As an example, the replication members of the VVIM/CDSM would be the following:
–
–
and the replication members of the Vault master would be the following:
–
–
The VVIM/CDSM replicates the records only to the Vault master, and the Vault master replicates the same records to the other Vaults.
When running the cdsconfig script on the VVIM/CDSM, there is a prompt to add the replication members. In the replication member list, a new role called "vmaster" is introduced for the Vault master. After the "vmaster" role is selected as a replication member for the controller (CDSM/VVIM), the Vault master replication feature is enabled and no other Vaults can be added as replication members for the CDSM/VVIM in the .arroyorc file. If the "vault" role is initially selected as a replication member for the controller, before adding the "vmaster," then the "vmaster" role is not available.
•
–
–
–
To adjust the amount of I-Frame video data initially scheduled for cache-fill when dynamic trick-file generation starts, enter the following command:
/proc/calypso/tunables/dtPrefetchIFramesFrom3rdPartyInitTimeInEonsTo adjust the maximum amount of I-Frame video data scheduled for cache-fill for a dynamic trick-file generation, enter the following command:
proc/calypso/tunables/dtPrefetchIFramesFrom3rdPartyMaxTimeInEonsTo adjust the interval with which the Streamer increases the amount of scheduled I-Frame video data, enter the following command:
proc/calypso/tunables/dtPrefetchIFramesFrom3rdPartyIncreaseTimeInEonsTo reduce the scheduled time when I-Frame data is needed to compensate for a delay in third-party cache-fill delivery, enter the following command:
proc/calypso/tunables/dtPrefetchIFramesFrom3rdPartyDelayAdjustTimeInEons–
–
–
–
•
echo 1 > /proc/calypso/tunables/streamPFramesDuringPause•
•
1.
2.
3.
To disable Fade Frame Support, select Disabled.
4.
The following line is written to Statsd with either a setting of enabled (0) or disabled (1):
/proc/calypso/tunables/disable_fade_frameSupported Environments
Release 3.0.2 of the Cisco TV CDS supports both the ISA and RTSP environments. Some RTSP environment features are only applicable to certain RTSP Deployment Types.
System Requirements
The Cisco TV CDS Release 3.0.2 runs on the CDE110, CDE220, CDE250, and CDE420. See the Cisco Content Delivery Engine110 Hardware Installation Guide, and the Cisco Content Delivery Engine 205/220/250/420 Hardware Installation Guide.
The Cisco TV CDS Release 3.0.2 does not run on the CDE100, CDE200, CDE300, and CDE400 hardware models.
Note
Limitations and Restrictions
This release contains the following limitations and restrictions:
•
In the case of multiple Stream Groups, with the Redirect Server configured to run on Streamers within one of the Stream Groups, it is required that the database replication partners for the Streamers contain all of the Streamers from all Stream Groups, which basically constitutes a full-mesh database replication approach among all of the Streamers
If a full-mesh database replication for the Streamers is not desired, the Redirect Server can operate on the Vaults, which already have the necessary database replication partners defined to support required data.
Open Caveats
This release contains the following open caveats:
CServer
•
Symptom:
In extreme conditions of initializing services, when the system is starting, the system fails.
Conditions:
When a Streamer is being booted, a very rare race condition may occur causing a null pointer to be created thus causing an exception and the server to fail.
Workaround:
Reboot the Streamer.
•
Symptom:
In the CDSM (or VVIM) GUI, on the Server Setup page (Configure > Server > Server Setup), when specifying an interface for the FTP Out Interface field under the FTP Out Setting section, the configuration setting does not take affect and the specified interface is not used for FTP out operations.
Conditions:
Using the CDSM (or VVIM) GUI, specify an FTP out interface and submit the Server Setup page. The setupfile on the server will be updated to reflect this configuration, as in following example:
ftpout if eth0 max utilization mbps 0 max sessions 0Workaround:
The IP address of the interface to be used in FTP out operations can be specified on the ftp command line.
Configuration
•
Symptom:
Not all packages are found in the drop-down list on the Monitor > System Level > Package Monitor page.
Conditions:
When the number of packages in the system reaches a level greater than 70,000.
Workaround:
If the number of packages in the system grows much beyond 70,000, then the drop-down list may not be able to display them all. The solution is to delete packages that are no longer needed. The maximum number of packages that will display in the drop-down list is variable, and is dependent on the system that is accessing the web page.
FSI
•
Symptom:
For a duplicated live future request, the state field in response XML body is empty instead of having the correct state of the scheduled live recording.
Conditions:
The client sends a request to schedule a live content with the same assetID, providerID, captureStart and captureEnd as an already scheduled future recording on the same channel.
Workaround:
None.
Monitoring
•
Symptom:
Occasionally, the Monitor > Server Level > NIC Monitor > Graph Ports page display does not match exactly the received Mbps and transmit Mbps reported by way of the ifstat for some CDS servers.
Conditions:
This appears almost randomly, and may be a temporary condition because of congested traffic between the CDS server and the CDSM.
Workaround:
There is no workaround at this time and this condition is rarely seen.
RTSP
•
Symptom:
RTSP Setup failed and error thrown as ""RTSP/1.0 771 Server Setup Failed - Asset Not Found"
Conditions:
1.
2.
3.
Workaround:
None.
•
Symptom:
Streamers take about 13 seconds to respond to a Session Setup request.
Conditions:
During load test on Streamers running Release 2.3.3 or Release 2.5.2 with RTSP-BNI Backoffice, responses to Session Setup requests takes between 13 and15 seconds.
Workaround:
None.
•
Symptom:
RTSP Session contents are not deleted properly in AVSDB.
Conditions:
When content streaming is very high, the database transmits and the transmits in the Thread Pools are high, which results in updates to the database in a mixed asynchronous and synchronous manner. This results in the orphans sessions in the database.
Workaround:
Stop AVSDB on all Streamers in that Stream Group and enter the following command on each CDS server:
rm rtsp_session.db rtsp_annex.dbStart AVSDB on Streamers in that Stream Group.
Statsd
•
Symptom:
When any of the Fail Ingest Settings parameters are updated from the CDSM/VVIM page (Configure > System Level > Ingest Tuning), the values are not updated in the /proc file tunables on the Vaults.
Conditions:
Fail Ingest Tuning is enabled from the CDSM/VVIM Setup page, and individual parameters are changed on the Ingest Tuning page.
Workaround:
Update the tunables directly on the Vault by echoing the appropriate values into the tunables, for example:
echo 1 > /proc/calypso/tunables/bRateErrorFailsIngestComplete list of tunables is as follows:
PSI Errors: bPSIErrorFailsIngest (1 = Enabled, 0 = Disabled)Bit Rate Errors: bRateErrorFailsIngest (1 = Enabled, 0 = Disabled)Error Count Method: bEveryNMinutes (1 = Per Minute, 0 = Per Sample)Number Of Minutes: nEveryNMinutes (minutes)Discontinuity Rate: nDiscErrorsFailIngestNumber Of Picture Gaps: nPicGapsFailIngestContinuity Counter Errors: nCCErrorsFailIngestNumber Of Sync Loss Errors: nSyncLossesFailIngestPicture Gap Duration: nPicGapsinHSFailIngest (hectoseconds)Sync Loss Duration: nSyncLossesinHSFFailIngest (hectoseconds)
Note
Resolved Caveats
This section contains he resolved caveats in Cisco TV CDS Release 3.0.2. Not all resolved issues are mentioned here. The following list highlights resolved caveats associated with customer deployment scenarios.
CServer
•
Symptom:
When upgrading a CDE220-2S3-C or CDE220-2S3-F with 300 GB SSD s and changing the part number to either CDE220-2S4-C or CDE220-2S4-F in a CDS running Release 2.5.6, the disk count and layout in the CDSM GUI does not show correctly, some pages show "Part Number Not Recognized" error messages, and the setupfile does not contain the correct disk information.
Conditions:
Occurs in Release 2.5.6 When upgrading a CDE220-2S3-C or CDE220-2S3-F with 300 GB SSDs and changing the part number to either CDE220-2S4-C or CDE220-2S4-F.
•
Symptom:
The CDS server enters a KDB state and displays the following error:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000818IP: [<ffffffffa036a4c8>] CM::Object::fillSegment+0x468/0x19c0 [avs_cserver]Conditions:
Specific conditions are required to reproduce this defect. The system must have a heavy load of disk traffic - nearly 100% of capacity - and it must have a heavy load on the network or the remote vaults containing the desired content. When the system tries to initially read the desired content and fails, it retries reading both a local copy and filling a remote copy. Under certain circumstances when the remote read and the local read fail at precisely the right (wrong) time the data read object leaves the cache data object (ObjectSegment) in an invalid state that allows the null pointer dereference.
•
Symptom:
The Streamer Backup server goes into kernel debugger (KDB) mode while becoming primary. The trace event log shows an infinite loop while trying to handle a stream that had been assigned to play on the backup Streamer and is in the playing state. However, the stream play no longer exists for the stream and the backup server gets into an infinite loop trying to cancel a non-existent play stream.
Conditions:
The conditions that caused this are not yet fully understood; there was not enough history in the trace event log for this stream. The backup control is out of sync with the primary control Streamer.
ISA
•
Symptom:
The ContentStore(Master) restarts because of ORB threads go into deadlock. The monitoring script (run_isa) restarts this application because it does not respond for 15-20 seconds.
Conditions:
Heavy load of db calls, and provisioning requests are served by leader thread. If Leader thread from the thread pool gets blocked on the provision call, then worker threads do not process any incoming requests rather just wait for leader thread to signal them. This causes unnecessary deadlock.
•
Symptom:
Content which was successfully ingested or cloned to regional Vaults gets deleted if it does not have any market reference and a market sends a provision request for it.
Conditions:
A content exists on the regional Vaults but has no market reference and a provision request is received for it from the market.
Statsd
•
Symptom:
In DCS setup with no Caching Nodes and local Vaults, the Streamer RemoteServers file contains both local and regional Vaults. However, local and regional Vault files do not contain Streamers.
Conditions:
DCS setup with no Caching Nodes and local Vaults.
Vault
•
Symptom:
The CDS server kernel debugger displays the following error:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000818IP: [<ffffffffa036a4c8>] CM::Object::fillSegment+0x468/0x19c0 [avs_cserver]Conditions:
The system must have a heavy load of disk traffic (nearly 100% of capacity) and a heavy load on the network or the remote vaults containing the content. When the system tries to initially read the content and fails, it retries reading both a local copy and filling a remote copy. When the remote read and the local read fail at precisely the right (wrong) time, the data read object leaves the cache data object (ObjectSegment) in an invalid state that allows the null pointer dereference.
Upgrading to Release 3.0.2
The supported upgrade paths are the following:
•
•
•
•
•
If the CDS is running an earlier software release, you must first upgrade to one of the supported releases before upgrading to Release 3.0.2.
For software upgrade procedures, see the Cisco TV CDS 3.0 Installation, Upgrade, and Maintenance Guide.
Upgrading from Release 2.5.2, 2.5.3, 2.5.5, 2.5.6, or 3.0.1 to Release 3.0.2
For the upgrade sequence of the CDS devices in your system (CDSM/VVIM and CDS servers [Vault, Streamer, Caching Node, ISV]), see the "Overview" chapter in the Cisco TV CDS 3.0 Installation, Upgrade, and Maintenance Guide.
To upgrade a CDS device, do the following:
Step 1
Step 2
a.
b.
c.
d.
Step 3
Step 4
# db_shutdownWait until the following command returns no output:
# netstat -an | grep 9999 and #pgrep avsdbStep 5
# scp -p <user>@<remote_ip_address>:CDS-TV-3.0.2.iso /# scp -p <user>@<remote_ip_address>:cdsinstall-3.0.2 /Step 6
# cd /root# ./cdsinstall-3.0.2 /CDS-TV-3.0.2.isoStep 7
Step 8
Step 9
# pgrep avsdb# rebootStep 10
a.
b.
c.
d.
Downgrading from Release 3.0.2
For the downgrade sequence of the CDS devices in your system (CDSM/VVIM and CDS servers [Vault, Streamer, Caching Node, ISV]), see the "Overview" chapter in the Cisco TV CDS 3.0 Installation, Upgrade, and Maintenance Guide.
To downgrade a CDS device, do the following:
Step 1
Step 2
Step 3
Step 4
# db_shutdownWait until the following command returns no output:
# netstat -an | grep 9999 and #pgrep avsdbStep 5
# scp -p <user>@<remote_ip_address>:CDS-TV-2.5.6.iso /# scp -p <user>@<remote_ip_address>:cdsinstall-2.5.6 /# cd /root# ./cdsinstall-2.5.6 /CDS-TV-2.5.6.isoStep 6
Step 7
# pgrep avsdb# rebootStep 8
a.
b.
c.
d.
Related Documentation
Refer to the following documents for additional information about the Cisco TV CDS 3.0:
•
•
•
http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_0/developer_guide/tv_cds_3_0_apiguide.html
•
http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_0/installation_guide/tv_cds_3_0_maint_guide.html
•
http://www.cisco.com/en/US/docs/video/cds/overview/CDS_Roadmap3.x.html
•
•
http://www.cisco.com/en/US/docs/video/cds/cde/cde110/installation/guide/cde110_install.html
•
http://www.cisco.com/en/US/docs/video/cds/cde/regulatory/compliance/CDE_RCSI.html
•
http://www.cisco.com/en/US/products/ps7127/products_licensing_information_listing.html
The entire CDS software documentation suite is available on Cisco.com at:
http://www.cisco.com/en/US/products/ps7127/tsd_products_support_series_home.html
The entire CDS hardware documentation suite is available on Cisco.com at:
http://www.cisco.com/en/US/products/ps7126/tsd_products_support_series_home.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
This product contains watermarking technology that is licensed from Verimatrix, Inc., and such functionality should not be used or distributed further by you without any additional license(s) required from Verimatrix, Inc.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2012 Cisco Systems, Inc. All rights reserved.
