 Feedback
|
Table Of Contents
Release Notes for Cisco Videoscape Distribution Suite, Internet Streamer 3.3
Resolved Caveats in Release 3.3
Enhancement Features Added in Release 3.3
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Videoscape Distribution Suite, Internet Streamer 3.3
This Release note covers Cisco Videoscape Distribution Suite, Internet Streamer Release 3.3.
First Published: December 13, 2013
OL-29883-02
Contents
The following information is included in these release notes:
•
Resolved Caveats in Release 3.3
•
•
New Features in Release 3.3
Release 3.3 of Cisco Internet Streamer VDS introduces the following features:
•
The Cisco VDS-IS 3.3 Release introduces virtualization for SE, SR and CDSM modes of VDS-IS. This enables the SE, SR and CDSM to boot as a Virtual Machine in the UCS platform and in other server platforms.
•
The Cisco VDS-IS 3.3 Release enhances the content deletion feature present in the earlier releases. To simplify the earlier process of deletion new GUI and APIs are created for the following content deletion enhancements:
–
–
–
–
–
–
–
•
The Cisco VDS-IS 3.3 Release provides support for both VOD and Live profile of MPEG Dash.
–
–
–
–
•
A new type of snapshot transaction log is generated by WebEngine with following counters per DS per URL regex periodically:
–
–
–
–
The generation interval is configurable between the range of 1 minute to 10 minutes with a granularity of minutes per URL regex.
•
VDS-IS 3.3 enables Session Tracking in all SEs attached to a delivery service. Upon receiving requests from Client the HTTP/HTTPS transactions will be tracked in Session by WebEngine.
•
In earlier Releases for Generic Session Tracking none of the requests were rejected. In VDS-IS 3.3 Generic Session Tracking is enhanced to reject request with 403 when the request can not be tracked and the requested content is protected.
•
In VDS-IS 3.3, Generic Session Tracking and Logging feature is verified to be working fine with HTTPS. No behavior change is made for Generic Session Tracking and Logging feature.
•
In VDS-IS 3.3, it provides support for latest release of Quova (Nestar). Another geo location service, Maxmind GeoIP web service will also be supported. New failover mechanism will be added to the Quova latest release and Maxmind. Other changes include, more geo location information fields are checked for geo protection, IPv6 IP address support for both Quova and Maxmind servers.
Geo location information of an IP address is obtained from an external server. RESTful API is used to communicate with Quova (Nestar) latest release server and Maxmind server.
•
In Earlier Releases, IPv6 was supported for client facing interfaces by SEs and SRs. The IPv6 is supported by dual stack approach, so both IPv4 and IPv6 communication with clients are supported.
In VDS-IS 3.3, IPv6 support is extended to enable IPv6 communication with the following VDS-IS's external servers:
–
–
–
–
•
In VDS-IS 3.3, the OpenSSL library is upgraded to 1.0.1c. Crypto hardware acceleration capability and improvement in the HTTPS performance are a result of the 1.0.1c upgrade.
•
In Mutual Authentication (two-way authentication), the SSL client verifies the identity of the SSL server, and then the SSL server verifies the identity of the SSL-client. With this verification of client, SSL server can make sure that the client is authorized.
One-way HTTPS authentication only enables the SSL client verify the identity of the SSL server. This authentication for SSL server is currently supported.
Certificate Revocation List (CRL) is also supported. CRL is a list of certificates that have been revoked before their scheduled expiration date. It is maintained by a CA which also provides information about revoked certificates that were issued by that CA.
•
VDS-IS supports HTTPS streaming to client, VDS-IS 3.3 Release requires that the CDSM presents the list of all Cyphers supported by SE and the operator chooses to disable some of the Cyphers from the list.
For HTTPS streaming between OS and Content Acquirer, Content Acquirer can also provide a supported Cypher list to OS.
The Cypher list can be configured for individual Delivery Service or in system level. By default, all supported Cyphers are enabled. The configured Cypher list will be sent to SEs which is used by each SE to select Cypher during the SSL/TLS handshake with client/OS.
•
In Earlier Releases, a network interface can be assigned more than one IP address. But for portchannel interface it is limited, multiple IP address can only be assigned in the same subnet.
This feature enables access to a CDN from different subnet, more than one IP address is defined in different subnet on a portchannel.
•
In Earlier Releases, transaction log exporting was controlled at the global level. Enhancements have been made to control the exporting of transaction logs individually by GUI and CLI. All transaction logs are still dumped to the disk as before.
The FTP destination configuration and the achieving frequency are still controlled at the global level. The device group support and Splunk support follow the existing behavior.
•
In VDS-IS 3.3 Release, a new option is added for SR to provide a configurable option to use Web Engine's status as the whole streamer's status for redirection. That is, if web engine reaches it's threshold, SR will not direct the traffic to the same streamer.
•
In Earlier Releases, the Slowscan (which synchronizes the files from disks to ContentMgr) runs every 12 hours, this behavior is not configurable. It was found that the Slowscan was running unexpectedly at peak time. In VDS-IS 3.3 Release, an option is provided to schedule the Slowscan. The option is only available on SE.
•
In Earlier Releases, when logging into VDS-IS devices through SSH/telnet device mode is displayed as "Cisco Service Engine", "Cisco Service Router" or "Cisco Content Delivery System Manager". In VDS-IS 3.3 Release, it is changed to "Service Engine", "Service Router" and "Content Delivery System Manager" respectively.
According to different use cases, the "Server" Header of SE/SR response is either "Cisco-CDS" or from Origin Server, like "Apache/2.2.22 (Debian)" for example. In VDS-IS 3.3 Release, this is configurable, operators could choose to keep the same behavior as before or operators could configure an arbitrary string.
Server Header of SE/SR response is a per-delivery-service configuration.
•
VDS-IS 3.3 Release provides DSCP Marking for Flash Media Streaming use cases including VOD and Live. This is done through service rule file configuration. It allows for per session DSCP marking as well as some other flexible rules based on configurations.
Open Caveats in Release 3.3
Table 1 lists the issues open in the Cisco Internet Streamer CDS 3.3 Release.
Click on the bug ID to view the bug details. This information is displayed in the Bug Search.
Resolved Caveats in Release 3.3
Table 2 lists the issues resolved in the Cisco Internet Streamer CDS 3.3 Release.
Click on the bug ID to view the bug details. This information is displayed in the Bug Search.
Enhancement Features Added in Release 3.3
Table 3 lists the enhancements in the Cisco Internet Streamer CDS 3.3 Release.
Click on the bug ID to view the bug details. This information is displayed in the Bug Search.
Accessing Bug Search
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
Note
Step 3
Step 4
•
•
•
•
•
–
–
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.
–
–
–
Step 5
Step 6
a.
b.
c.
If you cannot export the spreadsheet, log into the Technical Support website at http://www.cisco.com/cisco/web/support/index.html or contact the Cisco Technical Assistance Center (TAC).
Downgrading from Release 3.3
For software downgrades from Release 3.3 on systems with primary and standby CDSMs, you need to do the following:
Step 1
If you are using the CLI, downgrade the primary CDSM first, followed by the standby CDSM.
Step 2
•
cms database downgrade script downgrade/Downgrade3_3_to3_2cms database downgrade script downgrade/Downgrade3_1_2_b20_to_3_1_2_b19cms database downgrade script downgrade/Downgrade3_1_1_to_3_1cms database downgrade script downgrade/Downgrade3_1_to_3_0cms database downgrade script downgrade/Downgrade3_0_to_2_6cms database downgradecms enableThen, consult the "Downgrading the Internet Streamer CDS Software" chapter in the Cisco Internet Streamer CDS 2.6 Software Upgrade Guide for downgrading from Release 2.6.x to Release 2.5.9 or 2.5.11.
•
cms database downgrade script downgrade/Downgrade3_3_to3_2cms database downgrade script downgrade/Downgrade3_1_2_b20_to_3_1_2_b19cms database downgrade script downgrade/Downgrade3_1_1_to_3_1cms database downgrade script downgrade/Downgrade3_1_to_3_0cms database downgrade script downgrade/Downgrade3_0_to_2_6cms database downgradecms enable
After downgrade from 3.2.1 to 2.6.1, If SE does not come up in operational status in SR, restart the Service router and the operational state will be updated.
•
cms database downgrade script downgrade/Downgrade3_3_to3_2cms database downgrade script downgrade/Downgrade3_1_2_b20_to_3_1_2_b19cms database downgrade script downgrade/Downgrade3_1_1_to_3_1cms database downgradecms enable•
cms database downgrade script downgrade/Downgrade3_3_to3_2cms database downgrade script downgrade/Downgrade3_1_2_b20_to_3_1_2_b19cms database downgradecms enable•
cms database downgrade script downgrade/Downgrade3_3_to3_2cms database downgradecms enableStep 3
Related Documentation
Refer to the following documents for additional information about Cisco Internet Streamer CDS 3.3:
•
•
•
•
•
•
•
•
•
•
http://www.cisco.com/en/US/docs/video/cds/cde/regulatory/compliance/CDE_RCSI.html
•
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C200M1/install/c200M1.html
•
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C210M1/install/C210M1.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
The Cisco UCS C-Series Rack Servers documentation is available on Cisco.com at:
http://www.cisco.com/en/US/products/ps10493/prod_installation_guides_list.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.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
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)
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.
© 2013 Cisco Systems, Inc. All rights reserved.
