Release Notes for Cisco TV CDS 3.2.2

Transcription

1 These release notes cover Cisco TV CDS Release Revised: March 2013 Contents The following information is in the release notes: Enhancements, page 2 Supported Environments, page 2 System Requirements, page 2 Open Caveats, page 3 Resolved Caveats, page 3 Upgrading to Cisco TV CDS Release 3.2.2, page 6 Related Documentation, page 9 Obtaining Documentation and Submitting a Service Request, page 10 Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA USA 2012 Cisco Systems, Inc. All rights reserved.

2 Enhancements Enhancements Table 1 lists the enhancements in the CDS-TV release. Click on the bug ID to view the bug details. This information is displayed in the Bug Toolkit. Table 1 Enhancements in CDS-TV Release Bug ID CSCth96606 CSCud02656 CSCud07575 CSCud40171 CSCud81758 Description 2.3.2FSI: UDP capture delayed to start for 5 min when ftp pulls exist Playlist: Add configuration switch to change the jump-ahead behavior Adding new field to completed ingest page for TVOD [Gehua] need to send out an ANNOUNCE message after 200 ok Master Vault fail over logic must include ARP checks before rolling VIP Supported Environments Release 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 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/460 Hardware Installation Guide. The Cisco TV CDS Release does not run on the CDE100, CDE200, CDE300, and CDE400 hardware models. Note If you are using Internet Explorer 8 to access the CDSM GUI, for the online help to display correctly, you need to turn on Compatibility View. To turn on Compatibility View in Internet Explorer 8, choose Tools > Compatibility View. Limitations and Restrictions This release contains the following limitations and restrictions: RTSP Redirect Server Limitations The TV CDS Redirect Server provides a central entry-point for stream requests, which are then redirected based on internal load balancing policies to other Setup servers in the CDS deployment for session processing. The load balancing policies require that the CDS server running the Redirect Server have access to the database of each potential Setup server. The policies use key pieces of information from the database, such as the RTSP server status, the server load, and the Setup IP address to management IP address mappings. If the Redirect Server does not have access to this data, it cannot properly redirect the setup request to the "best" Setup server. 2

3 Open Caveats 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 Table 2 lists the open issues in the CDS-TV release. Click on the bug ID to view the bug details. This information is displayed in the Bug Toolkit. Table 2 Open Caveats in CDS-TV Release Bug ID CSCub38015 CSCue09530 CSCud77332 CSCue69080 Description & Servers not creating core file when hung in kernel debug NPT Related Issues PLE SETUP fails with 777 when first item has non-zero npt start time Synopsis - It appears that the I04D06 version of the Data Warehouse spec Resolved Caveats Table 3 lists the issues resolved in the CDS-TV release. Click on the bug ID to view the bug details. This information is displayed in the Bug Toolkit. Table 3 Bug ID CSCue24181 CSCud03890 CSCud60764 CSCud84017 CSCue02259 CSCue69191 CSCue78940 CSCue79515 CSCue12411 CSCub62911 CSCue86304 CSCue89947 CSCuf03555 Resolved Caveats in CDS-TV Release Description ISA Services crash after upgrade A3 async message returned to wrong responseurl C2 Parsing Fails when Connection: Keep-Alive is in lower case VE_STOP with invalid segment Index and content NPT build 2.5.7b13 Timing issue between CPU's 2 and 3 on the Stream Server Synopsis - Cisco is not in compliance with the following Streaming Serve VMcore is not generated on systems with kernels Memory Leak in ContentStoreMaster Caches crash in IOX::ControlSlot::transmitDone BO send more than 600 request lead to backup and primary streamer crash After network flap, streamer almost lost capability to stream Track locate port reachability on a per-adapter level Ingest of bad content causing BUG: soft lockup on CPU 3

4 Resolved Caveats Table 3 Bug ID CSCua60678 CSCuc57659 CSCud00876 CSCud14149 CSCud44787 CSCud51267 CSCud90317 CSCue59645 CSCud84164 CSCtw88140 Resolved Caveats in CDS-TV Release (continued) Description VVIM GUI does not display Content Data information on System Snapshot Fiber port eth8 and eth9 can't work cv-account-add-homeid0 should be triggered from GUI to seed the db RTSP EventIS deployment generates no teardown in LivenessManager Streamer hit KDB after the reboot Wrong content played due to GOID mismatch in avsdb Cache Node uses "down" transfer port ATST - Black screen at VOD end Two consecutive LSC Pause requests transition state to LSC OPEN 2.5.7b13 SNMP Agent GUI configuration settings do not permit a " " ( space) Accessing Bug Tool kit This section explains how to use the Bug Toolkit to search for a specific bug or to search for all bugs in a release. Step 1 Step 2 Go to At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Toolkit page opens. Note If you do not have a Cisco.com username and password, you can register for them at Step 3 Step 4 To search for a specific bug, click the Search Bugs tab, enter the bug ID in the Search for Bug ID field, and click Go. To search for bugs in the current release, click the Search Bugs tab and specify the following criteria: Select Product Category Video. Select Products Cisco Content Delivery Engine Series. Software Version [3.2]. Search for Keyword(s) Separate search phrases with boolean expressions (AND, NOT, OR) to search within the bug title and details. Advanced Options You can either perform a search using the default search criteria or define custom criteria for an advanced search. To customize the advanced search, click Use custom settings for severity, status, and others and specify the following information: Severity Choose the severity level. Status Choose Terminated, Open, or Fixed. Choose Terminated to view terminated bugs. To filter terminated bugs, uncheck the Terminated check box and select the appropriate suboption (Closed, Junked, or Unreproducible) that appears below the Terminated check box. Select multiple options as required. 4

5 Resolved Caveats Step 5 Step 6 Step 7 Step 8 Choose Open to view all open bugs. To filter the open bugs, uncheck the Open check box and select the appropriate suboptions that appear below the Open check box. For example, if you want to view only new bugs in Prime Optical 9.5, choose only New. Choose Fixed to view fixed bugs. To filter fixed bugs, uncheck the Fixed check box and select the appropriate suboption (Resolved or Verified) that appears below the Fixed check box. Advanced Check the Show only bugs containing bug details check box to view only those bugs that contain detailed information, such as symptoms and workarounds. Modified Date Choose this option to filter bugs based on the date when the bugs were last modified. Results Displayed Per Page Specify the number of bugs to display per page. Click Search. The Bug Toolkit displays the list of bugs based on the specified search criteria. To export the results to a spreadsheet: a. In the Search Bugs tab, click Export All to Spreadsheet. b. Specify the filename and location at which to save the spreadsheet. c. Click Save. All bugs retrieved by the search are exported. Search for Keyword(s) Separate search phrases with boolean expressions (AND, NOT, OR) to search within the bug title and details. Advanced Options You can either perform a search using the default search criteria or define custom criteria for an advanced search. To customize the advanced search, click Use custom settings for severity, status, and others and specify the following information: Severity Choose the severity level. Status Choose Terminated, Open, or Fixed. Choose Terminated to view terminated bugs. To filter terminated bugs, uncheck the Terminated check box and select the appropriate suboption (Closed, Junked, or Unreproducible) that appears below the Terminated check box. Select multiple options as required. Choose Open to view all open bugs. To filter the open bugs, uncheck the Open check box and select the appropriate suboptions that appear below the Open check box. For example, if you want to view only new bugs in Prime Optical 9.5, choose only New. Choose Fixed to view fixed bugs. To filter fixed bugs, uncheck the Fixed check box and select the appropriate suboption (Resolved or Verified) that appears below the Fixed check box. Advanced Check the Show only bugs containing bug details check box to view only those bugs that contain detailed information, such as symptoms and workarounds. Modified Date Choose this option to filter bugs based on the date when the bugs were last modified. Results Displayed Per Page Specify the number of bugs to display per page. Click Search. The Bug Toolkit displays the list of bugs based on the specified search criteria. To export the results to a spreadsheet: a. In the Search Bugs tab, click Export All to Spreadsheet. b. Specify the filename and location at which to save the spreadsheet. c. Click Save. All bugs retrieved by the search are exported. If you cannot export the spreadsheet, log into the Technical Support website at or contact the Cisco Technical Assistance Center (TAC). 5

6 Upgrading to Release Upgrading to Release The supported upgrade paths are the following: Release to Release Release to Release Release to Release Release to Release Release to Release Release to Release Release to Release If the CDS is running an earlier software release, you must first upgrade to one of the supported releases before upgrading to Release For software upgrade procedures, see the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide. Upgrading to Cisco TV CDS Release 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.2 Installation, Upgrade, and Maintenance Guide. To upgrade a CDS device, do the following: Step 1 Step 2 Step 3 Step 4 Download the ISO image file (CDS-TV iso) and the cdsinstall script from the Cisco Software Download website. For more information on downloading the software files, see the Overview chapter in the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide. For the CDS servers, offload the device before upgrading the software. a. From the CDSM GUI, choose Maintain > Servers > Server Offload. The Server Offload page is displayed. b. From the Server IP drop-down list, select the IP address or nickname of the sever and click Display. c. From the New Server Status drop-down list, select Offline for a Streamer or Caching Node, select Offline (No Ingest & Fill) for a Vault. d. Click Submit. e. Ensure the CDS server has been offloaded by checking the protocol timing log. Log in to the CDS server as user root. For CDS servers, before installing the image file, stop the database with the following command: # db_shutdown Wait until the following command returns no output: # netstat -an grep 9999 and #pgrep avsdb Step 5 Copy the ISO image file and the cdsinstall script to the CDS server. # scp -p <user>@<remote_ip_address>:cds-tv iso / # scp -p <user>@<remote_ip_address>:cdsinstall / 6

7 Upgrading to Release Step 6 Run the cdsinstall script to upgrade the ISO image to Release # cd /root #./cdsinstall /CDS-TV iso Step 7 Step 8 Step 9 Step 10 For the CDSM or VVIM, when the script has completed, reboot the server. For the CDSM or VVIM, log in to the GUI as a user with Engineering access level and configure the settings on the CDSM Setup page. For CDS servers, make sure that the database is not running and reboot the server. # pgrep avsdb # mv /etc/rc.d/rc.local /etc/rc.d/rc.local.bak # reboot For CDS servers, after the CDS server has been came up from reboot, start DB, statsd, submit the interface setup page and start cserver # su - isa -c "arroyo start avsdb" >& /dev/null # /home/stats/statsd.bin -i <Server IP> -s <subnet mask> -d eth0 Wait till statsd connects to avsdb and both are operational Submit Server Interface Setup page for this CDS server from GUI Configure -> Server Level -> Interface Setup Start avslauncher to start setup and control ip ( incase if the CDS server is streamer) # /usr/bin/avslauncher >& /arroyo/log/avslauncher.out& Start cserver # /arroyo/test/run Start FSI application (incase if the CDS server is vault) # su - isa -c "arroyo start fsi ns nfs aim" >& /dev/null Move the rc.local file to the original location # mv /etc/rc.d/rc.local.bak /etc/rc.d/rc.local Step 11 For CDS servers, after the CDS server has been verified as reachable, return the server to online. a. Choose Maintain > Servers > Server Offload. The Server Offload page is displayed. b. From the Server IP dropdown list, select the IP address or nickname of the server and click Display. c. Choose Online and click Submit. d. Verify the CDS server is online by viewing the status on the Monitor > System Level > System Health page. 7

8 Upgrading to Release Downgrading from Release 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.2 Installation, Upgrade, and Maintenance Guide. To downgrade a CDS device, do the following: Step 1 Download the ISO image file (for example, CDS-TV iso) and the cdsinstall script (for example, cdsinstall-2.5.6) for Release 2.5.2, 2.5.3, 2.5.5, or from the Cisco software download website. For more information on downloading the software files, see the Overview chapter in the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide. Step 2 For CDS servers, offload the server (see Step 2 in Upgrading to Cisco TV CDS Release ). Step 3 Step 4 Log in to the CDS device as user root. For CDS servers, before installing the image file, stop the database with the following command: # db_shutdown Wait until the following command returns no output: # netstat -an grep 9999 and #pgrep avsdb Step 5 Step 6 Step 7 Step 8 Copy the ISO image file and the cdsinstall script to the /root directory and run the cdsinstall script to download the software. For example, the following commands are for downgrading to Release 2.5.6: # scp -p <user>@<remote_ip_address>:cds-tv iso / # scp -p <user>@<remote_ip_address>:cdsinstall / # cd /root #./cdsinstall /CDS-TV iso For the CDSM or VVIM, when the script has completed, reboot the server. For CDS servers, make sure that the database is not running and reboot the server. # pgrep avsdb # mv /etc/rc.d/rc.local /etc/rc.d/rc.local.bak # reboot For CDS servers, after the CDS server has been came up from reboot, start DB, statsd, submit the interface setup page and start cserver # su - isa -c "arroyo start avsdb" >& /dev/null # /home/stats/statsd.bin -i <Server IP> -s <subnet mask> -d eth0 Wait till statsd connects to avsdb and both are operational Submit Server Interface Setup page for this CDS server from GUI Configure -> Server Level -> Interface Setup Start avslauncher to start setup and control ip ( incase if the CDS server is streamer) # /usr/bin/avslauncher >& /arroyo/log/avslauncher.out& Start cserver # /arroyo/test/run 8

9 Related Documentation Start FSI application (incase if the CDS server is vault) # su - isa -c "arroyo start fsi ns nfs aim" >& /dev/null Move the rc.local to the original location # mv /etc/rc.d/rc.local.bak /etc/rc.d/rc.local Step 9 For CDS servers, after the CDS server has been verified as reachable, return the server to online. a. Choose Maintain > Servers > Server Offload. The Server Offload page is displayed. b. From the Server IP dropdown list, select the IP address or nickname of the server and click Display. c. From the New Server Status drop-down list, select Online and click Submit. d. Verify the CDS server is online by viewing the status on the Monitor > System Level > System Health page. (see Step 7 in Upgrading to Cisco TV CDS Release procedure). Related Documentation Refer to the following documents for additional information about the Cisco TV CDS 3.2: Cisco TV CDS 3.2 ISA Software Configuration Guide onfig.html Cisco TV CDS 3.2 RTSP Software Configuration Guide _config.html Cisco TV CDS 3.2 API Guide ml Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide pgrade_maint.html Cisco Content Delivery System 3.x Documentation Roadmap Cisco Content Delivery Engine 205/220/250/420/460 Hardware Installation Guide 420_hig.html Cisco Content Delivery Engine 110 Hardware Installation Guide Regulatory Compliance and Safety Information for Cisco Content Delivery Engines Open Source Used in TV CDS

10 Obtaining Documentation and Submitting a Service Request The entire CDS software documentation suite is available on Cisco.com at: The entire CDS hardware documentation suite is available on Cisco.com at: 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: 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: 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 Cisco Systems, Inc. All rights reserved. 10