Guest

Cisco Videoscape Distribution Suite Service Broker

Release Notes for Cisco VDS Service Broker 1.2

  • Viewing Options

  • PDF (300.3 KB)
  • Feedback
Release Notes for Cisco VDS Service Broker 1.2

Table Of Contents

Release Notes for Cisco VDS Service Broker 1.2

Contents

New Features in Release 1.2

Support sending CDN URL in HTTP body for clients that do not support HTTP location header

Support for HTTP URL query parameters in policy rules

Support for generic CDN URL generation based on user provided query parameters and input request values

Support for additional Velocix URL validation to check if the value present in token and query parameter are same

System Requirements

System Limits and Thresholds

Open Caveats in Release 1.2

Resolved Caveats in Release 1.2

Accessing Bug Tool kit

Installation Procedure

Upgrade Procedure

Downgrade Procedure

Related Documentation


Release Notes for Cisco VDS Service Broker 1.2


This release notes document covers Cisco VDS Service Broker Release 1.2.

First Published: July, 2013

OL-30213-01

Contents

The following information is included in these release notes:

New Features in Release 1.2

System Requirements

System Limits and Thresholds

Open Caveats in Release 1.2

Resolved Caveats in Release 1.2

Accessing Bug Tool kit

Installation Procedure

Upgrade Procedure

Downgrade Procedure

Related Documentation

New Features in Release 1.2

The following new features are introduced in the Cisco VDS Service Broker 1.2 Release:

Support sending CDN URL in HTTP body for clients that do not support HTTP location header

Support for HTTP URL query parameters in policy rules

Support for generic CDN URL generation based on user provided query parameters and input request values

Support for additional Velocix URL validation to check if the value present in token and query parameter are same

Support sending CDN URL in HTTP body for clients that do not support HTTP location header

The Service Broker currently responds with HTTP 302 redirect by sending the CDN URL in location header for HTTP requests. In this release, the service broker supports sending CDN URL in HTTP body for SDK players that do not support HTTP 302 redirect and expect the status code to be HTTP 200. The default behavior is sending CDN URL in location header for HTTP requests.

Support for HTTP URL query parameters in policy rules

The Service broker policy rules currently supports various rules like BFQDN, CPE type, Content type, URL, HTTP header, Query type, Onnet name, Offnet name, data, time and location parameters like country, state, city. In this release, the service broker supports rules based on a query parameter value in the URL.

Support for generic CDN URL generation based on user provided query parameters and input request values

The CDN adaptation policy page currently supports URL resign action to support URL signing based on CDN vendor and URL rewrite action to rewrite incoming URL to CDN specific URL based on regular expression. In this release, the service broker supports generic CDN URL generation.

Support for additional Velocix URL validation to check if the value present in token and query parameter are same

Service Broker currently supports validation for Velocix signed URL. To ensure that the URL is not changed by any external entity, in this release, the service broker will check if the value present in token and query parameter are the same.

System Requirements

VDS Service Broker system is a software-only product and supports VMWare virtualization on any UCS platform or third-party hardware.The Cisco UCS C220M3S is the recommended hardware to run VDSM and SB.

Local storage (disk) on UCS models is limited and is used for system image and local management functions (such as database, configuration files, error logs, and transaction logs).

All VDS Service Broker device modes (SB and VDSM), can run in a virtual machine. With virtual machine support, VDS Service Broker can run on any hardware supported by virtual machine. Also, it is possible to run multiple VDS Service Broker device modes on a single hardware platform. For example, it is possible to run the VDSM and the SB on the same hardware. The VDS Service Broker virtualization is only supported with VMware EXSi 5.1.0 or above hypervisor.


Note For performance information, see the release-specific performance bulletin.


System Limits and Thresholds

This release has the following limits and thresholds:

Service Monitor Limits and Thresholds

VDSM Limits and Thresholds

Service Monitor Limits and Thresholds

When the Service Monitor thresholds are exceeded, an alarm is raised on the respective device and an SNMP trap is sent to the VDSM. The default thresholds are as outlined below.

Following are the parameters that are monitored on each device (SB and VDSM) and the default threshold setting of each parameter:

CPU—80 percent

Memory—80 percent

Kernel memory—50 percent

Disk —80 percent

Augmentation alarms—80 percent

VDSM Limits and Thresholds

The VDSM has the following limits and thresholds:

RPC Connections

File Synchronization

VDSM Availability (primary and standby)

RPC Connections

A maximum of 40 RPC connections are supported among the managed devices (SB, standby VDSM, and primary VDSM).

File Synchronization

The primary VDSM checks for file updates and synchronization with the managed devices (SB and standby VDSM) every ten minutes.

VDSM Availability (primary and standby)

The SB checks for the availability of the primary and standby VDSM on a regular interval; however, if the VDSM does not respond, the SB uses an exponential-backoff call for retrying the connection.

The exponential backoff call means that if the VDSM does respond to the first attempt, the SB sleep for ten seconds before trying again. If the second attempt does not succeed, the wait time doubles (20 seconds), if that attempt does not succeed, the wait time doubles again (40 seconds). The wait time doubles every attempt (10, 20, 40, 80, and so on) until the maxWaitingTime of 320 seconds.

Open Caveats in Release 1.2

Table 1 lists the issues open in the Cisco VDS Service Broker 1.2 release.

Click on the bug ID to view the bug details. This information is displayed in the Bug Toolkit.

Table 1 Open Caveats in Cisco VDS Service Broker 1.2 Release 

Bug ID
Description

CSCui36244

Attribute changes from "Http Query Parameter" to "State" after "Submit"

CSCui34382

CLI showing extra CDN wen downgraded to lower version


Resolved Caveats in Release 1.2

Table 2 lists the issues resolved in the Cisco VDS Service Broker 1.2 release.

Click on the bug ID to view the bug details. This information is displayed in the Bug Toolkit.

Table 2 Resolved Caveats in Cisco VDS Service Broker 1.2 Release

Bug ID
Description

CSCuh71569

CDN Adaptation files are missing after downgrade from SB 1.1 to 1.0.1

CSCui21377

CDN Adaptation Policies - URL Rewrite Actions fields are too short


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 Go to http://tools.cisco.com/Support/BugToolKit.

Step 2 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 http://tools.cisco.com/RPF/register/register.do.


Step 3 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.

Step 4 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 Videoscape Distribution Suite Service Broker.

Software Version—[1.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.

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.

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.

Step 5 Click Search. The Bug Toolkit displays the list of bugs based on the specified search criteria.

Step 6 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 http://www.cisco.com/cisco/web/support/index.html or contact the Cisco Technical Assistance Center (TAC).

Installation Procedure

Refer to the Cisco VDS Service Broker 1.2 Software Installation Guide for UCS Platforms for the Installation procedure.

Upgrade Procedure

Use the copy command "copy http install" to execute the upgrade. The CLI format is

copy http install <http-server-ip-addr> <dir-name> <filename>

Downgrade Procedure

Before downgrade to 1.0 release, ensure that the BFQDN Policy Settings, CDN Adaptation Policy Settings and CDN Selection Policy Settings is set to Using File method via VDSM GUI method.

Related Documentation

Refer to the following documents for additional information about Cisco VDS Service Broker 1.2:

Cisco VDS Service Broker 1.2 Software Configuration Guide

http://www.cisco.com/en/US/docs/video/videoscape/distribution_suite/SB/1.2/ConfigurationGuide/vds_sb_1.2_config.html

Cisco VDS Service Broker 1.2 API Guide

http://www.cisco.com/en/US/docs/video/videoscape/distribution_suite/SB/1.2/APIGuide/vds_sb_1_2_api_guide.html

Cisco VDS Service Broker 1.2 Command Reference Guide

http://www.cisco.com/en/US/docs/video/videoscape/distribution_suite/SB/1.2/CLIGuide/VDS_SB_commandref.html

Cisco VDS Service Broker 1.2 Alarms and Error Messages Guide

http://www.cisco.com/en/US/docs/video/videoscape/distribution_suite/SB/1.2/AlarmsandError/message_guide.html

Cisco VDS Service Broker 1.2 Software Installation Guide for non-CDEs

http://www.cisco.com/en/US/docs/video/videoscape/distribution_suite/SB/1.2/InstallationGuide/VDS_SB_1_2Software_Install.html

Open Source Used in Cisco VDS Service Broker 1.1

http://www.cisco.com/en/US/docs/video/videoscape/distribution_suite/SB/1.1/Licensing/VDS-SB_1.1_Open_Src_Doc_OL-30015-01.pdf