New Features in Release 1.1

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

•Support for creating BFQDN Policies via VDSM GUI

•Support for assigning BFQDN Policies to a BFQDN via VDSM GUI

•Support for creating CDN Adaptation Policies via VDSM GUI

•Support for assigning CDN Adaptation Policies to a CDN via VDSM GUI

•Support for creating CDN Selection Policies via VDSM GUI

•Support for assigning CDN Selection Policies via VDSM GUI

•Support for Cisco Location Server Web-Service Geo Location Server

•Neustar interface update for more resiliency

•WebServices API for configuration and management

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.

VDSM Limits and Thresholds

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.1

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

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

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—[Product Version].

•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:

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)

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.