Cisco TelePresence Video Communication Server Model Video Conferencing System Release Notes

Cisco TelePresence Video Communication

Server

X8.7.3

Release Note

First Published: November 2015

Last Updated: May 2016

Preface

Change History

Table 1 Release Note Change History

Date Change

May 2016 Cisco Unified IP Conference Phone 8831 is not supported over MRA, unlike the other phones in the IP Phone 8800 Series.

April 2016 Acano interoperability added. Updated resolved and open issues links. Listed minor changes in X8.7.3.

March

2016

Updated resolved and open issues links. Listed minor changes in X8.7.2.

February

2016

Updated resolved and open issues links. Listed minor changes in X8.7.1. Added

Hybrid Services upgrade prerequisite.

November

2015

Release notes for new version of Cisco VCS.

Reason

New information found

X8.7.3

maintenance release

X8.7.2

maintenance release

X8.7.1

maintenance release

X8.7 feature release

Cisco Systems, Inc.

www.cisco.com

1

Cisco TelePresence Video Communication Server Release Note

Preface

Supported Platforms

Table 2 Cisco VCS Software Versions Supported by Platform

Platform name

Cisco VCS appliance (1 st generation)

Serial Numbers

52A#####

Scope of software version support

All features in versions up to and including X8.6.1

Critical fixes only in X8.7.n*

Small VM (OVA)

Medium VM (OVA)

(Auto-generated)

(Auto-generated)

X8.1 onwards

X8.1 onwards

Large VM (OVA)

CE500

†

(Cisco VCS pre-installed on

UCS C220 M3L)

CE1000

†

(Cisco VCS pre-installed on

UCS C220 M3L)

(Auto-generated)

52C#####

52B#####

X8.1 onwards

X8.1.1 onwards

X8.1.1 onwards

CE1100 (Cisco VCS pre-installed on

UCS C220 M4L)

52D##### X8.6.1 onwards

* As of 12 th

September 2015, we are not obliged to release new software for this platform (see End-of-Life

Announcement ). X8.6.1 is the last version on which you will receive support for all the features included in the software. However, we may encourage you to upgrade to later releases to address critical issues (for example, security vulnerabilities). In this case, we will not support any of the newer features in those releases on these legacy platforms. Ask your Cisco representative about migrating to a newer platform.

† As of 26 th

February 2016, you cannot order the CE500 and CE1000 appliances from Cisco. See the End-of-sale announcement for other important dates in the lifecycle of these platforms.

Product Documentation

The following documents provide guidance on installation, initial configuration, and operation of the product:

■

■

■

■

■

Cisco VCS Installation Guides

Cisco TelePresence VCS Administrator Guide in Cisco TelePresence VCS Maintain and Operate Guides

Hybrid services knowledge base

Cisco TelePresence VCS Serviceability Guide in Cisco TelePresence VCS Maintain and Operate Guides

Cisco VCS and Microsoft Infrastructure Deployment Guide in Cisco TelePresence VCS Configuration Guides

2


Changes in X8.7.3

Changes in X8.7.3

X8.7.3 is a maintenance release. There are no new features, but the lists of

Open and Resolved Issues, page 7 , have

been updated.

■

■

The Cisco VCS now accepts SCTP (Stream Control Transmission Protocol).

The Cisco VCS TURN server has been enhanced to interoperate with the Acano Server (1.9), to enable

Microsoft RDP sharing.

Changes in X8.7.2



been updated.

■

CiscoSSL has been upgraded to version 5.4.3 in this version of Cisco VCS. This version of Cisco SSL rejects keys with fewer than 1024 bits when doing Diffie-Hellman (DH) key exchange.

Note:

This Cisco VCS upgrade prevents SSL interoperability with versions 9.x and earlier of Cisco Unified

Communications Manager and Cisco Unified Communications Manager IM and Presence Service, because those products generate 768 bit keys for D-H key exchange.

Suggested workaround: Upgrade Cisco Unified Communications Manager and Cisco Unified Communications

Manager IM and Presence Service to the latest version of 10.x or 11.x.

Changes in X8.7.1



been updated.

■

■

■

■

Two parameters have been added to the DNS zone configuration. These parameters enable a manual override of the DNS request, to enable routing outbound calls to the Cisco Collaboration Cloud without modifying the

SIP URI. The parameters are Modify DNS request (On or Off) and Domain to search for (accepts an FQDN).

This option is primarily intended for use with Cisco Spark Call Service. See www.cisco.com/go/hybridservices .

The 2 * 2.4 GHz CPU reservation requirement of the Medium virtual Cisco VCS has been relaxed to allow for slight variance in host clock speeds.

These natural variations were preventing some correctly specified UCS hardware configurations, including some BE6000 options, from meeting the CPU requirement.

See Cisco VCS Virtual Machine Installation Guide on the VCS installation guides page .

The IP interface selection options have changed. On System > Network interfaces > IP, the IP protocol switch now has the options IPv4 only, IPv6 only, or Both.

CiscoSSL has been upgraded to version 5.4.2 (based on OpenSSL v1.0.2e). This version does not allow

TLS connections to use the RC4 cipher.

New Features in X8.7

Table 3 Feature History by Release Number

Feature / change

Dial via Office-Reverse (DVO-R)

Lync Screen Sharing Through a Gateway Cluster

X8.7

Supported

Supported

3



Table 3 Feature History by Release Number (continued)

Feature / change

Mobile and Remote Access with Cisco IP Phone 78/8800 Series

Hybrid Services and Expressway/VCS Rebranding

Hosting on VMWare vSphere

®

6.0

Keyword Filter for Syslog Output

Changes and Minor Enhancements

X8.7

Supported

Supported

Supported

Supported

Supported

Dial via Office-Reverse through MRA

Your mobile workers need the same high quality, security and reliability that they experience when placing calls in the office. You can assure them of just that when you enable the Dial via Office-Reverse (DVO-R) feature and they are using Cisco Jabber on a dual-mode mobile device. DVO-R routes Cisco Jabber calls through the enterprise automatically.

DVO-R handles call signaling and voice media separately. All call signaling, including the signaling for Mobile and

Remote Access on Cisco VCS, traverses the IP connection between the client and Cisco Unified Communications

Manager. Voice media traverses the cellular interface and hairpins at the enterprise Public Switched Telephone

Network (PSTN) gateway.

Moving audio to the cellular interface ensures high-quality calls and securely maintained audio even when the IP connection is lost.

You can configure DVO-R so that, when a user makes a call, the return call from Cisco Unified Communications

Manager goes to either:

■

■

The user’s Mobile Identity (mobile number).

An Alternate Number for the user (such as a hotel room).

This feature is dependent on the following versions of related systems:

■

■

Cisco Unified Communications Manager 11.0(1) or later

Cisco Jabber 11.1 or later

You can read more about how this feature works in the Mobile and Remote Access through VCS Deployment Guide on the VCS Configuration Guides page .

Lync Screen Sharing Through a Gateway Cluster

Transcoding of Lync screen sharing was introduced in X8.6.

X8.7 extends this feature to work on a cluster of Gateway Cisco VCS peers, so that a greater number of screen sharing sessions can be simultaneously transcoded.

You must configure the Lync B2BUA and the related transcoding parameters on the primary peer. The number of transcoding sessions you enter is the per peer number.

The transcoding capacity of the cluster is approximately the number of sessions you choose multiplied by the number of peers, up to a maximum multiple of 4x.

For example, consider a cluster of four large VMs. If you set Maximum RDP transcode sessions to 20, then the cluster would provide up to 80 simultaneous screen shares.

To configure your Cisco Collaboration environment to interoperate with Microsoft Lync, see the Microsoft Lync and

Cisco VCS Deployment Guide on the VCS Configuration Guides page.

4



Mobile and Remote Access with Cisco IP Phone 78/8800 Series

Mobile and Remote Access is now officially supported with the Cisco IP Phone 78/8800 Series**, when the phones are running firmware version 11.0(1) or later. We recommend Cisco VCS X8.7 or later for use with these phones.

■

■

Cisco IP Phone 8800 Series

Cisco IP Phone 7800 Series

MRA is officially supported with the Cisco DX Series endpoints running firmware version 10.2.4(99) or later. This support was announced with Cisco VCS version X8.6.

■

■

■

Cisco DX650

Cisco DX80

Cisco DX70

When deploying DX Series or IP Phone 78/8800 Series endpoints to register with Cisco Unified Communications

Manager via Mobile and Remote Access, you need to be aware of the following:

■

■

■

■

Phone security profile:

If the phone security profile for any of these endpoints has TFTP Encrypted Config checked, you will not be able to use the endpoint via Mobile and Remote Access. This is because the

MRA solution does not support devices interacting with CAPF (Certificate Authority Proxy Function).

Trust list:

You cannot modify the root CA trust list on these endpoints. Make sure that the Cisco VCS

Expressway's server certificate is signed by one of the CAs that the endpoints trust, and that the CA is trusted by the Cisco VCS Control and the Cisco VCS Expressway.

Bandwidth restrictions:

The Maximum Session Bit Rate for Video Calls on the default region on Cisco

Unified Communications Manager is 384 kbps by default. The Default call bandwidth on Cisco VCS Control is also 384 kbps by default. These settings may be too low to deliver the expected video quality for the

DX Series.

Off-hook dialling:

The way KPML dialing works between these endpoints and Unified CM means that you need CUCM 10.5(2)SU2 or later to be able to do off-hook dialing via MRA. You can work around this dependency by using on-hook dialing.

** Except the Cisco Unified IP Conference Phone 8831. This IP phone uses a different firmware to the rest of the series.

Hybrid Services and Expressway/VCS Rebranding

We have changed some terminology in this release:

■

Expressway/VCS base

In previous versions of the Cisco Expressway Series and the Cisco TelePresence Video Communication

Server, the software was always branded as "VCS Control" before you activated it with a release key.

In X8.7, the product is now called "Expressway/VCS base" when it is in this pre-activation state, which shows that it can be activated as an Expressway or as a VCS.

These changes prepare us for a future release that will change the user experience of defining the purpose of your Cisco VCS.

5



■

Hybrid Services

Version X8.6.1 included support for a feature called "Cloud Extensions". That feature has been renamed to

"Hybrid Services" in the UI, documentation, and Cloud Collaboration Management.

Hybrid Services is a group name for a family of user services that are delivered in part by the Cisco

Collaboration Cloud and in part by your on-premises equipment.

The Expressway/VCS base does not need a release key to register for Hybrid Services. After you register the

Expressway/VCS base, it will be branded "Cisco Expressway base". You don't need to apply a release key for subsequent upgrades.

Note:

For these reasons, we are requiring new Hybrid Services customers to use version X8.7. If you are using X8.6.1

for Hybrid Services, we strongly recommend upgrading to X8.7.

Hosting on VMWare vSphere 6.0

Cisco VCS virtual machines can now run on VMware vSphere

® version 6.0. Please be aware that we have noticed a known issue in ESXi 6.0 during our testing. We recommend that you read http://kb.vmware.com/kb/2124669 before you upgrade.

You can install new Cisco VCS OVAs on the ESXi 6.0 host, or you can migrate existing VMs. If you migrate a virtual

Cisco VCS to a different host, you must shut it down before you move it.

See the Cisco VCS Virtual Machine Installation Guide on the Cisco VCS Install and Upgrade Guides page .

Note:

The virtual Cisco VCS now has virtual hardware version 8. This means that new installations of virtual Cisco

VCS require ESXi 5.0 or later, and will not run on ESX/ESXi 4.x or earlier.

Keyword Filter for Syslog Output

You can now use keywords to filter the logs that Cisco VCS sends to each remote syslog host. You can enter comma delimited words or phrases, and the syslog daemon will only forward log messages that match at least one of those keywords.

The keyword filter gives you more control over the types of messages that are published. You may only be interested in some types of messages, or you may not be allowed to send potentially sensitive information over the channel to the syslog server.

The user interface has also been improved as part of this change. In addition to the new keyword filter field, we've added more granular control over the message format and transport connection. Previously, these options were grouped into a "Mode" field and you could not configure them unless you chose the "Custom" mode.

Changes and Minor Enhancements

■

■

■

■

■

Multistream support is disabled in this release, pending a complete implementation in a future release.

A new CLI command allows you to set the cipher suites used when the Cisco VCS authenticates with the

AD domain for LDAP queries. The command is

xconfiguration Authentication ADS CipherSuite

.

A Hybrid Services menu item has been added to the Cisco VCS Expressway, to support Cisco VCS-based hybrid services that are currently in development. The new menu item (Applications > Hybrid Services

> Certificate management) has no explicit purpose for X8.7.

A new system metric has been added to monitor each CPU core independently.

New parameters have been added to the .ova file so you can configure the VM's network properties when deploying through vCenter.

See Cisco VCS Virtual Machine Installation Guide on the VCS installation guides page .

There is a delay when you deploy virtual machines with pre-configured network parameters. The deployment will take a few minutes longer than deploying the VM without pre-configured network parameters.

6


Open and Resolved Issues

■

The Cisco VCS deployment guide now warns against choosing a single NIC, static NAT deployment of the

Cisco VCS Expressway. The preferred option for deploying the Cisco VCS Expressway in the DMZ is to use both NICs.

See Cisco TelePresence VCS Basic Configuration (Control with Expressway) Deployment Guide on the VCS configuration guides page .

Open and Resolved Issues

Follow the links below to read the most recent information about the open and resolved issues in this release.

■

■

■

■

■

All open issues, sorted by date modified (recent first)

Issues resolved by X8.7.3



Issues resolved by X8.7

Notable Issues in this Version

CSCuy59366

: Upgrading Cisco VCS to X8.7.2 breaks SSL Handshake with CUCM or IM&P 9.x (also affects

Jabber Guest Server)

An upgrade of CiscoSSL in this version of Cisco VCS prevents it from accepting weak DH keys. If you have not yet applied this security improvement to your Cisco Unified Communications Manager or Cisco Unified Communications

Manager IM and Presence Service infrastructure, they may not be able to communicate securely with Cisco VCS.

This could prevent your MRA deployment from working as expected.

We strongly recommend that you upgrade Cisco Unified Communications Manager and Cisco Unified

Communications Manager IM and Presence Service to the latest version of 10.x or 11.x .

This issue also affects Jabber Guest Server versions before 10.6.9. We strongly recommend that you upgrade to the latest version of Jabber Guest Server.

CSCuw95309

: DTMF mid-call features not supported for Mobility-enabled Users

(This issue is present in Cisco Unified Communications Manager version 11.0)

For end users who have mobility enabled, DTMF-based mid-call features (for example, *81 - Hold, *83 - Resume) are not supported, regardless of the DTMF Signaling Method setting for the SIP trunk. This issue is present for all SIP trunks due to issues with SIP signaling and MTP allocation. There is no workaround for this issue.

Note

: DTMF for User Controlled Voicemail avoidance and for navigating IVRs at the far-end are both supported.

CSCuv47574

: SDP Decode Fails when Trying to Split IM&P and Video From Lync

This issue in X8.6 and X8.7 prevents a previously published Lync federation deployment from working as it did in

X8.5. If you are using the affected deployment, we recommend that you do not upgrade yet.

The affected deployment is documented in Appendix 1: Federation, of the X8.5 version of Microsoft Lync and Cisco

VCS Deployment Guide, on the Cisco VCS Configuration Guides page .

Limitations

Unsupported Features (General)

■

DTLS is not supported through the Cisco VCS Control/Cisco VCS Expressway. SRTP is used to secure calls instead; attempts to make DTLS calls will fail.

7


Limitations

■

■

SIP UPDATE method. Features that rely on the SIP UPDATE method ( RFC 3311 ) will not work as expected because the Cisco VCS does not support this method.

Audio calls may be licensed as video calls in some circumstances. Calls that are strictly audio-ONLY consume fewer licenses than video calls. However, when audio calls include non-audio channels, such as the iX channel that enables ActiveControl, they are treated as video calls for licensing purposes.

Unsupported Endpoint Features When Using Mobile and Remote Access

Note:

This list contains known limitations and is not exhaustive. The MRA deployment does not necessarily support pass through of line-side features provided by Cisco Unified Communications Manager. Absence of such items from this list does not imply that they are supported.

■

■

■

■

■

Calls to/from additional lines on IP phones and endpoints that support multiple lines; only the primary line is supported via Mobile and Remote Access.

Directory access mechanisms other than UDS.

Certificate provisioning to remote endpoints e.g. CAPF.

Features that rely on the SIP UPDATE method ( RFC 3311 ) will not work as expected because the Cisco VCS does not support this method. For example, CUCM and endpoints use UPDATE to implement blind transfer, which does not work correctly via MRA.

Peer-to-peer file transfer when using IM and Presence Service and Jabber is unsupported via MRA

■

■

■

■

■

■

—

Managed File Transfer (MFT) with IM and Presence Service 10.5.2 (and later) and Jabber 10.6 (and later) clients is supported via MRA

—

File transfer with WebEx Messenger Service and Cisco Jabber is supported via MRA

Jabber SDK, Jabber for Mac, and Jabber for Windows are not capable of deskphone control when they are connected over MRA, because the CTI-QBE protocol is not traversed by the Cisco VCS pair. When these

Jabber applications, or other CTI applications, can connect to CUCM CTIManager (on-premises or VPN) then they can deskphone control endpoints and clients that are connected over MRA.

Additional mobility features including GSM handoff and session persistency.

Hunt group/hunt pilot/hunt list.

Self-care portal.

Support for Jabber SDK.

Shared lines are not supported on endpoints connected over MRA.

Some shared line features may work but are not supported.

Unsupported Cisco VCS Features and Limitations When Using Mobile and Remote

Access

■

■

■

■

■

The Cisco VCS cannot be used for Jabber Guest when it is used for MRA.

The Cisco VCS Control used for Mobile and Remote Access cannot also be used for Microsoft Interoperability.

Microsoft Interoperability requires a dedicated Cisco VCS Control.

MRA is not supported in IPv6 only mode.

Secure XMPP traffic between Cisco VCS Control and IM&P servers (XMPP traffic is secure between Cisco

VCS Control and Cisco VCS Expressway, and between Cisco VCS Expressway and remote endpoint).

Endpoint management capability (SNMP, SSH/HTTP access).

8


Interoperability

■

■

■

■

■

■

Multi-domain and multi-customer support is limited as follows:

—

Prior to X8.5, each Cisco VCS deployment supported only one IM&P domain (even though IM and Presence

Service 10.0 or later supports Multiple Presence Domains).

—

—

As of X8.5, you can create multiple deployments on the Cisco VCS Control, but this feature is still limited to one domain per deployment.

As of X8.5.1, a deployment can have Multiple Presence Domains. This feature is in preview, and we currently recommend that you do not exceed 50 domains.

Mobile and remote access functionality is not within the FIPS boundary.

NTLM authentication via the HTTP proxy.

Maintenance mode; if the Cisco VCS Control or the Cisco VCS Expressway is placed into maintenance mode, any existing calls passing through that Cisco VCS will be dropped.

The Cisco VCS Expressway must not have TURN services enabled.

Deployments on Large VM servers are limited to 2500 proxied registrations to Unified CM (the same limit as

Cisco VCS appliances or equivalent VM).

Interoperability

The interoperability test results for this product are posted to http://www.cisco.com/go/tp-interop , where you can also find interoperability test results for other Cisco TelePresence products.

Upgrading to X8.7.3

Prerequisites and Software Dependencies

Hybrid Services

Your Management Connector must be up to date before you upgrade your Cisco VCS. You must authorize and accept any upgrades advertised by the Cisco Collaboration Cloud before attempting to upgrade.

Note:

X8.7.1 is now the minimum version required for Hybrid Services. If you are using Hybrid Services with X8.7, you must upgrade to X8.7.1 or later.

Existing TMS Agent (Legacy Mode) Provisioning Deployments

Cisco VCS X8.1 and later no longer supports TMS Agent (legacy mode) provisioning. Before you upgrade to X8 or

later, if you are using TMS Agent (legacy mode) for provisioning you must first migrate to Cisco TelePresence

Management Suite Provisioning Extension which requires TMS 13.2.x. See Cisco TMS Provisioning Extension

Deployment Guide for instructions about how to migrate.

Existing OCS Relay Deployments

Cisco VCS X8.1 and later no longer supports OCS Relay integration with Microsoft Lync 2010 / OCS 2007 R2. If you use OCS Relay you must migrate to using the Microsoft Interoperability B2BUA to route SIP calls between the Cisco

VCS and Microsoft infrastructure. See Cisco VCS and Microsoft Infrastructure Deployment Guide for information about this deployment.

Existing Non-AES Build Installations

As of version X8.1, the software uses AES encryption. Prior to this, a version that used weaker encryption was available. If you are upgrading to X8.1 or later (or another version that uses AES) from a version that used the weaker encryption, you must perform a factory reset. Proceed as follows to ensure you can upgrade in future:

9


Upgrading to X8.7.3

1.

Record all your software configuration details

2.

Upgrade the software with the AES-encryption version

All configuration will be lost

3.

Perform a factory reset

4.

Manually reconfigure the software

Upgrade Instructions

When maintenance mode is enabled on Cisco VCS, existing calls passing through it may be dropped. We recommend that you upgrade Cisco VCS components while the system is inactive.

If you are upgrading a Cisco VCS that uses clustering, device provisioning (Cisco TMSPE) or FindMe (with Cisco TMS managing Cisco VCS), you must follow the directions in Cisco VCS Cluster Creation and Maintenance Deployment

Guide.

Follow the procedure below for upgrading Cisco VCS to X8.7.3, only if all of the following apply:

■

■

■

■

The Cisco VCS is not part of a cluster

Device provisioning is not in use

Cisco TMS is not managing the Cisco VCS

Cisco VCS is currently running X5.1.1 or later

To upgrade a Cisco VCS:

1.

Backup the Cisco VCS (Maintenance > Backup and restore).

You should backup your system before upgrading. If you later need to downgrade to an earlier release you will have to restore a backup made against that previous release.

If your system was delivered with X6.1 pre-installed, you must make some configuration changes before using the backup process as described in the section below.

2.

Enable maintenance mode.

Log in to the Cisco VCS as admin (SSH or serial), and at a command prompt, type:

xConfiguration SystemUnit Maintenance Mode: On

Note that from X8.1 you can enable maintenance mode via the web interface (Maintenance > Maintenance

mode).

3.

Wait for all calls to clear and registrations to timeout.

—

If necessary, manually remove any calls that do not clear automatically (Status > Calls, click Select all and then click Disconnect).

—

If necessary, manually remove any registrations that do not clear automatically (Status > Registrations > By

device, click Select all and then click Unregister).

4.

Upgrade and restart the Cisco VCS (Maintenance > Upgrade).

Note that when upgrading to a new major release, for example from X7.n to X8.n you need to supply a valid release key as a part of the upgrade process.

The web browser interface may timeout during the restart process, after the progress bar has reached the end.

This may occur if the Cisco VCS carries out a disk file system check – which it does approximately once every

30 restarts.

The upgrade is now complete and all Cisco VCS configuration should be as expected.

Upgrade Cisco VCS Control and Cisco VCS Expressway systems connected over a traversal zone

We recommend that Cisco VCS Control (traversal client) and Cisco VCS Expressway (traversal server) systems that are connected over a traversal zone both run the same software version.

10


Using the Bug Search Tool

However, we do support a traversal zone link from one Cisco VCS system to another that is running the previous major release of Cisco VCS. This means that you do not have to simultaneously upgrade your Cisco VCS Control and

Cisco VCS Expressway systems.

Note that certain features introduced in recent software versions (such as Mobile and Remote Access) require both the Cisco VCS Control and Cisco VCS Expressway systems to be running the same software version.

Back up Cisco VCS units delivered with X6.1 pre-installed

If your system was delivered with X6.1 pre-installed, you must make some configuration changes before using the backup process. You do not need to follow these additional steps if you do not have X6.1 installed or your installation of X6.1 is the result of an upgrade from a previous release. To ensure that all of your data is backed up:

1.

Log in to the Cisco VCS as root user.

2.

Enter the following commands:

mkdir /tandberg/persistent/oti mkdir /tandberg/persistent/management

3.

Exit the root account.

Upgrade from older releases

■

■

■

We strongly recommend installing a new server certificate if you are upgrading from any version of Cisco VCS released prior to X8.1.1.

The certificate signing request storage location changed in X8.

When you generate a CSR in X7, the application puts csr.pem and privkey_csr.pem into

/tandberg/persistent/certs.

When you generate a CSR in X8, the application puts csr.pem and privkey.pem into

/tandberg/persistent/certs/generated_csr.

If you want to upgrade from X7 and have an unsubmitted CSR, then we recommend discarding the CSR before upgrade, and then regenerating the CSR after upgrade.

You cannot upgrade to X7.n or later from releases prior to X5.1.

You must first upgrade to X5.2 and then to X7.n or later. See the X5.2 release notes for details.

Using the Bug Search Tool

The Bug Search Tool contains information about open and resolved issues for this release and previous releases, including descriptions of the problems and available workarounds. The identifiers listed in these release notes will take you directly to a description of each issue.

To look for information about a specific problem mentioned in this document:

1.

Using a web browser, go to the Bug Search Tool .

2.

Sign in with a cisco.com username and password.

3.

Enter the bug identifier in the Search field and click Search.

To look for information when you do not know the identifier:

1.

Type the product name in the Search field and click Search.

2.

From the list of bugs that appears, use the Filter drop-down list to filter on either Keyword, Modified Date,

Severity, Status, or Technology.

Use Advanced Search on the Bug Search Tool home page to search on a specific software version.

The Bug Search Tool help pages have further information on using the Bug Search Tool.

11


Obtaining Documentation and Submitting a Service Request

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see

What's New in Cisco Product Documentation

.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's New in

Cisco Product Documentation RSS feed . The RSS feeds are a free service.

12


Cisco Legal Information

Cisco Legal Information

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO

CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE

BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.

USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE

INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS

REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR

CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of

California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved.

Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE

SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL

WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING,

USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR

INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA

ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN

ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version should be referred to for latest version.

Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices .

© 2016 Cisco Systems, Inc. All rights reserved.

Cisco Trademark

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)

13

No results