Cisco VDS-IS Release 4.1.2 introduces the following features:
Support of CDE280
New Content Delivery Engine - CDE280 is supported by this release. This latest generation of CDEs provides high-performance, highly reliable Adaptive Bit Rate (ABR) video streaming that meets cable and IPTV operators’ needs, as video traffic continues to grow rapidly.
The following six modes of CDE280 are introduced and supported by this release:
– CDE280-2H1 : 1 x 600G SAS HDD
– CDE280-2H13 : 24 x 600G SAS HDD
– CDE280-2H26 : 24 x 1200G SAS HDD
– CDE280-2S5 : 24 x 240G SSD
– CDE280-2S10 : 24 x 480G SSD
– CDE280-2S21 : 24 x 960G SSD
Note CDE280 is expected to be orderable by the end of June, 2015. For more information about CDE280 refer to Cisco Content Delivery Engine Hardware Installation guide or contact your sales team. Alternatively, you can send an email to email@example.com or contact the Cisco support organization.
CDE-280 SSD / HDD replacement
Starting from Release 4.3.1 introduces new drive model support for CDE280 drives, as the old drive models are reaching end of support.The new drive models are of the same size of the old drive models. For more information on new disk models, see Table 7.
New Features in Release 4.1.1
Cisco VDS-IS Release 4.1.1 introduces the following features:
HTTP Header Manipulation
Release 4.1.1 introduces HTTP Header manipulation that allows you to modify headers on the SE. You can define when to manipulate the headers (that is, the conditions or defined different stage) and how to manipulate the headers(that is, the actions).
A Service Engine (SE) supports receive request, send request,receive response, and the send response stages. This feature can be configured per Delivery Service using the rule file.
The conditions can be checked by the existence of specific headers, by URL regex, or by combinations of them using logical expressions. Actions can be combination of add, append, set and remove.
Release 4.1.1 optimises the DNS lookup result to cache in each WebEngine blocking thread for configurable time period. If the cached record is not expired, the Web Engine will use it for the following request.
Release 4.1.1 allows the configuration of the cookie refresh threshold time. The Session cookie for Generic Session Tracking is refreshed after the cookie refresh threshold time is reached. The threshold value is currently is 50%.
Generic Session Tracking Manifest URI failover in cookie
Release 4.1.1 introduces a Manifest URI to ensure that when a request is failover by one SE to another SE, the manifest URI in the cookie will be retrieved and logged correctly in the WebEngine ABR per session log. A value of 1 means enabled. A value of 0 (zero) means disabled. The default is disabled.
Per Content Provider Allocation of Delivered Session or Bandwidth
Release 4.1.1 provides the ability to set the session and bandwidth quotas per Delivery Service Group in the VDS-IS. Associating a Delivery Service Group with a content provider (tenant) in the CDSM, provides the ability to manage multiple tenants with different session and bandwidth requirements in the CDSM.
The per-Delivery Service Group session quota ensures that one Delivery Service is assigned to only one Delivery Service Group. One Delivery Service Group can contain multiple Delivery Services. The per-Delivery Service Group bandwidth quota limits the maximum bandwidth used to deliver content to clients.
– To view the list of Delivery Service Groups using the CDSM, choose Services > Service Definition > Delivery Service Group.
– To assign a Delivery Service to a Delivery Service Group using CDSM, choose Service > Service Definition > Delivery Service Group > Assign Delivery Services.
– To assign a Delivery Service Group to a Delivery Service using CDSM, choose Service > Service Definition > Delivery Services > Assign Delivery Service Group.
Quova IPv6 Support
Release 4.1.1 supports IPv6 client address geo location lookup through Quova server. The client geo location information is used in location based routing and authorization.
VLAN Tagging on the Delivery Interface or port
In Release 4.1.1, the stream interface supports network package with VLAN Tagging. The VLAN Tagging per interface or LACP group must support a standard VLAN ID range of 1-4094.
Precision increase of the DownloadTime value in the WebEngine Ingest Transaction Log
In VDS-IS 4.1.1 release, the type of DownloadTime(Seconds) value in the WebEngine Ingest Transaction Logs is changed from integer to 3 digit float.
The following is an example of the ingest transaction log:
FMS Rollover enhancement, which stops one of the three amscore processes when the overall traffic is low. This is one protection for the potential memory leak of the amscore processes. There is no impact on the FMS services
FMS Thread Implementation, thread pool implementation for the auth and file plugins, which enables asynchronous process of FMS events. This helps improve the FMS cache miss performance. There is no impact to the existing FMS services
Operator could update CDN Splunk UF forwarder configs as: 1. for two configs which are global for all monitor types - Throttling, max Queue Size; 2. For each monitor log type - ignoreOlderThan, sourcetype and index names
Release 4.1 supports upgrading from Release 3.1.3, 3.2.1, 3.3.1 and 4.0.0.
Note Starting with Release 3.3.1, VDS-IS uses a new regular expression library RE2-20131024, which improves the performance, but lacks support for some advanced regex syntax, for example, back-reference.
When upgrading from Release 3.1.3 or 3.2.1, if you were using any unsupported regex syntax in service rules, you need to update them. The examples in configuration guides of previous releases still work in Release 4.1.
Note When upgrading a CDE250 Service Engine from a release earlier than 3.3.1-b100, including 3.3.1-b100, you need to upgrade the LSI SAS adapter firmware and BIOS during the upgrading process. For more information on upgrading the LSI SAS firmware and BIOS, see the Upgrading LSI SAS Adapter Firmware and BIOS on the CDE250.
We strongly recommend that you upgrade your VDS-IS network devices in the following order:
1. Multicast sender Service Engines
2. Multicast receiver Service Engines
3. Edge Service Engines
4. Middle-tier Service Engines
5. Content Acquirers
6. Service Routers
7. Standby CDSMs (Upgrade before primary when using the GUI only.)
8. Primary CDSM
For more information on the upgrade procedure, see the Cisco Videoscape Distribution Suite, Internet Streamer 4.1 Software Configuration Guide.
After the upgrade procedure starts, do not make any configuration changes until all the devices have been upgraded.
Downgrading from Release 4.1
Release 4.1 supports downgrading to Release 3.1.3, 3.2.1, 3.3.1 and 4.0.0.
Note When downgrading a Service Engine to 3.x or earlier release, you must execute the content-mgr rollback command before installing the image. This command evicts the cached file count to be below 20,000,000 and the cached directory count to be below 950,000. The content-mgr rollback command prevents the cached content from being lost.
Note When downgrading a CDE250 Service Engine to a release earlier than 3.3.1-b100, including 3.3.1-b100, you need to do the downgrade path as below 4.1 -> 3.3.1-b116 -> 3.2.1 or 3.1.3 or 3.3.1 build earlier than 101.
You also need to execute the smpt2sas firmware flash-to-v6 command after installing the 3.3.1-b116 image and before rebooting the device. This command downgrades the LSI SAS adapter firmware and BIOS and reboots the device. If the device fails to reboot in long time (20 minutes), we recommend that you power cycle the device manually. To execute the smpt2sas firmware flash-to-v6 command, you must install the image using the CLI instead of GUI.
The downgrade steps are as below:
Downgrade from 4.1 to 3.3.1-b116 and then reload.
Downgrade from 3.3.1-b116 to target version(3.2.1 or 3.1.3 or 3.3.1 build earlier than 101) using CLI and do not reload.
Downgrade the LSI SAS adapter firmware and BIOS then reboots the device.
For software downgrades from Release 4.1, follow these steps:
Step 1 If you are using the CDSM GUI, downgrade the standby CDSM first, followed by the primary CDSM.
If you are using the CLI, downgrade the primary CDSM first, followed by the standby CDSM.
Step 2 After downgrading the primary and standby CDSMs, using the CLI, log in to each CDSM and enter the following commands:
Step 3 Downgrade the software on the service routers, followed by the service engines.
Upgrading LSI SAS Adapter Firmware and BIOS on the CDE250
To resolve the non-responding SSD issue (refer to bug CSCuo76567) on CDE250 devices, it's required to upgrade firmware and BIOS for the LSI SAS adapter on CDE250 devices, which is supported starting with Release 3.3.1-b101.
This is only applicable for service engines.
When upgrading from a release earlier than 3.3.1-b100, including 3.3.1-b100 to Release 3.3.1-b101 or later releases, follow these steps to upgrade the firmware and BIOS:
Step 1 Check the LSI SAS firmware version and BIOS version:
streamer# smpt2sas firmware show
LSI Corporation SAS2 Flash Utility
Version 19.00.00.00 (2014.03.17)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved
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: 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.