Guest

Cisco Videoscape Distribution Suite for Internet Streaming

Release Notes for Cisco CDA Visual Quality Experience Application, Release 2.0

 Feedback

Table Of Contents

Release Notes for Cisco CDA Visual Quality Experience Application, Release 2.0

Contents

Introduction

System Requirements

Limitations and Restrictions

Open Caveats

Important Notes

Notices

OpenSSL/Open SSL Project

License Issues

GNU General Public License Information

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco CDA Visual Quality Experience Application, Release 2.0


Revised: March, 2008, OL-14479-01

Contents

This information is in the release notes:

"Introduction" section

"System Requirements" section

"Limitations and Restrictions" section

"Open Caveats" section

"Important Notes" section

"Notices" section

"Related Documentation" section

"Obtaining Documentation, Obtaining Support, and Security Guidelines" section

Introduction

Cisco CDA Visual Quality Experience Application (VQE), Release 2.0, is the first VQE release. Cisco VQE offers service providers a set of technologies and products associated with the delivery of IPTV video services. VQE is designed to improve the quality of IPTV services and subscribers' viewing experiences. VQE is part of a Cisco end-to-end solution that builds video awareness into the network infrastructure. For Release 2.0, VQE technology is intended for wireline operators who offer managed broadcast (multicast) IPTV services using xDSL.

Cisco Content Delivery Application (CDA) Visual Quality Experience Application, Release 2.0, includes these major software components:

VQE Server (VQE-S)—Software that runs on a Linux-based Cisco Content Delivery Engine 110 (CDE110) appliance located in the intelligent edge of the service-provider's network.

VQE Client (VQE-C)—Software embedded in the subscriber's CPE—typically a set-top box.

These release notes cover VQE Server software and two related software components: VQE Channel Provisioning Tool (VCPT) and VQE Client Channel Configuration Delivery Server.

For information on VQE Server, VQE Channel Provisioning Tool, and VQE Client Channel Configuration Delivery Server, see the Cisco CDA Visual Quality Experience Application User Guide, Release 2.0.

For information on VQE Client, see the documentation that is provided in the TAR file containing the VQE Client software.

System Requirements

VQE Server runs on one Content Delivery Engine 110 (CDE110) appliance. VQE Channel Provisioning Tool and VQE Client Channel Configuration Delivery Server run on a separate CDE110 appliance.

The Cisco CDE110 comes with the required software pre-installed—either VQE Server software or VQE Channel Provisioning Tool and VQE Client Channel Configuration Delivery Server software. In each case, the required Linux, Apache web server, and other software is also pre-installed.

To access the VQE-S Application Monitoring Tool (VQE-S AMT or AMT) or the VQE Channel Provisioning Tool, you need a web browser. For these tools, the following web browsers are supported:

Microsoft Internet Explorer version 6.0 or later

Mozilla Firefox version 2.0 or later

The minimum screen resolution required for VQE-S AMT and VCPT is 1024 x 768 pixels.

Limitations and Restrictions

Cisco CDA Visual Quality Experience Application, Release 2.0, technology is intended for wireline operators who offer managed broadcast (multicast) IPTV services using xDSL.

Open Caveats

This release contains the following open caveats:

CSCsj40019

Adding channels causes intermittent Error Repair loss.

When new channel lineups are sent to a VQE Server, temporary loss of Error Repair can occur for several seconds depending on the number of changes in the new channel lineup from the existing one on the VQE-S server.

Workaround: Update the channel lineups during a period of minimal viewing.

CSCsj88638

Changing system time on VQE-S affects Error Repair.

When system time is changed with the date command on a VQE-S server that is actively repairing errors, all error repairs will stop indefinitely, and packet loss will be seen on the VQE Client devices. This appears to be due to a problem with the Linux routing daemons no longer advertising routes for VQE-S.

Workaround: The workaround for this problem is to perform the following steps in the order specified after the system time is changed:


Step 1 Restart the VQE Server—kill the process_monitor process

Step 2 Stop watchquagga daemon—service watchquagga stop

Step 3 Stop zebra Linux daemon—service zebra stop

Step 4 Stop ospfd Linux daemon—service ospfd stop

Step 5 Restart zebra Linux daemon—service zebra start

Step 6 Restart ospfd Linux daemon—service ospfd start

Step 7 Restart watchquagga daemon—service watchquagga start



Note It is recommended that you issue the preceding commands through the system console so connectivity to the VQE system is not lost when the quagga services are stopped and restarted.


CSCsk11985

SNMPSA will not operate without the IMB driver.

On rare occasions after an ISO image installation, SNMPSA (SNMP subagent) may fail to start because an IMB driver is not installed correctly. The following messages are displayed when you run the vqes_init_setup script:

SNMPSA: IMB driver is not started, possibly due to kernel version mismatch.
SNMPSA: SNMPSA will not operate without the IMB driver

Workaround: Reboot the machine after seeing this error.

CSCsj70513

An "Invalid module format" error is thrown on ipmi/imb.ko.

The following errors are shown on the CDE110 system console and saved in first_boot_addon.log file during VQE-S installation first boot phase:

+ /usr/local/ism/driver/imbload start
insmod: error inserting '/usr/local/ism/driver/imb.ko': -1 Invalid module format
/bin/mknod: missing operand after `0'
Try `/bin/mknod --help' for more information.

The error always occurs during the first boot phase of initial VQE-S install. The VQE-S installation patches the Linux kernel during first boot phase, and installs the Intel IPMI driver for the new kernel. The IPMI driver tries to load before the new kernel is loaded and causes the error messages shown on console and in first_boot_addon.log.

Workaround: No work around is required. The system will function correctly since the patched kernel will be used once the installation is complete and system is reloaded.

CSCsk00570

The ospfd daemon fails to load if the log file /var/log/quagga/ospfd.log is larger than 2GB.

Quagga OSPFD will not load when its log file is larger than 2GB to avoid potential system performance issues. When the Quagga OSPFD log level is set to a too verbose level, such as informational or higher, and many OSPF messages are received by the server, the log file may grow to over 2GB within the logrotate checking interval. If ospfd is restarted when this condition occurs, it will fail to load. VQE-S is shipped with default logging level set to warning, and this problem should not occur in normal operational conditions.

Workaround: Manually remove the log file /var/log/quagga/ospfd/log and restart the ospfd service. We also recommend that the operator lower the logging level when this failure occurs.

CSCsj95844

The ifup command produces a core dump of the arping process.

The ifup command used to activate an Ethernet interface executes a system utility named arping to do duplicate address detection on the network. In certain cases, the arping utility may stop unexpectedly while running an interface up or interface down operation. A message indicating that the duplicate address detection check has failed is displayed. However, the interface up operation will continue to run and apply configuration changes as expected. A second message to the console will indicate that arping has segfaulted. A core dump file of the arping process will be found in /var/core.

This failure can occur whenever an interface is started using the /sbin/ifup command and the VQE-S application is running.

Workaround: Retry the interface up operation by first issuing the interface down command /sbin/ifdown ethX. Then issue the interface up command /sbin/ifup ethX again.

CSCsi67816

Manual startup or restart of tomcat5 service daemon fails.

The symptom is that the VQE-S Application Management Tool (AMT) does not work and simple restarts of the tomcat5 service fail to clear the problem. The tomcat 5 service is required for the VQE-S AMT to operate.

In some conditions, an attempt to restart the tomcat5 service fails and leaves tomcat5 in an inoperable state even though the process itself may appear to be running. The root cause of the problem is not known. However, the issue only seems to occur when the tomcat5 service has been started, or restarted, from within a Linux shell environment that has been reached with the su command rather than through a direct login.

Workaround: Perform the following:

1. Login to the VQE-S system directly as root. For example, use the following command:

ssh -l root vqes-system

2. Restart the tomcat5 service with the following command:

service tomcat5 restart

CSCsj53629

On initial CD/DVD installation, error messages are dispayed on the system console.

The following error messages come from the CD/DVD drive during initial installation:

hda: packet command error: status=0x51 { DriveReady SeekComplete Error }
hda: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
hda: packet command error: status=0x51 { DriveReady SeekComplete Error }

Workaround: No workaround is needed because these messages do not affect CD/DVD perfomance. Users can safely ignore them.

CSCsk12402

The SDP Parser does not perform syntax checks or checks for mandatory elements.

VQE-S may fail to perform syntax checks and checks for mandatory elements in the SDP data describing a channel. In cases where the syntax of the SDP data is incorrect, or where mandatory elements are missing from the SDP, the parser may incorrectly accept the channel description as valid and attempt to operate on it, with undefined results.

This condition would normally occur only in cases where the SDP description for a channel has been edited manually or has been constructed by a tool that does not correctly validate the constructed SDP before sending it to the VQE-S (or VQE-C). It should not occur in cases where the SDP has been constructed using the VQE Channel Provisioning Tool (VCPT).

Workaround: In cases where the SDP has been constructed by tools other than the VCPT or has been manually edited, it is suggested that the user perform an extra check to determine that the syntax of the constructed SDP is correct and that all required elements are present.

CSCsk19357

VQE-S may generate syslog error messages when no error has occurred.

VQE-S may generate a syslog error message when, in fact, no error has occurred and the system is behaving as expected. The syslog message contains the text CP channel handle not match DP's from upcall event:channel. For example:

<<%VQES-CP-4-ERA_GENERAL_WARN>> ERA warning: CP channel handle not match DP's from upcall 
event:channel Channel 229.1.5.47

When the VQE-S channel configuration file is modified (for example, one or more channels have been modified or deleted), one or more of the above syslog messages may be generated. If VQE-S channel configuration has recently been modified, these error messages are harmless and should be ignored.

Workaround: No workaround is needed. Ignore the message.

CSCsk19624

Cache Manager rejects a channel with too little bandwidth configured.

When a channel is configured with less than approximately 1500Kbps of aggregate bandwidth, the Cache Manager may fail to properly create the channel, causing the channel to remain inoperative. The channel will be shown with a "red" status in the "Channels" summary screen of the VQE-S Application Monitoring Tool and VQE-S will fail to perform error repair for that channel.

When this condition occurs, a message similar to the following will be seen in the vqes.log file:

<<%VQES_DP-3-DP_BAD_ARG>> A bad parameter was passed to the Cache Manager API (detail: 
channel descriptor: number of buffers value 28l is not in range [256l,75000l])

The bandwidth configured for a channel can be seen in the SDP description for the channel in the line:

b=AS:1000

In the preceding line, the data rate of the stream (in Kbps) appears after AS.

Workaround: Reconfigure the channel with a bandwidth of at least 1500Kbps. VQE-S will still perform error repair properly for the channel even if its actual rate is less than the configured rate.

Important Notes

When restarting VQE-S-related processes, it is recommended that you perform the restart through the CDE110 system console. If you restart VQE-S-related processes through one of the CDE110 Ethernet interfaces, be careful to configure routing properly in case one of the routing daemons needs to be restarted. If routing is not configured properly, the CDE110 can become unreachable.

Notices

The following notices pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

Copyright © 1998-2007 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].

GNU General Public License Information

Cisco CDA Visual Quality Experience Application (VQE), Release 2.0, includes Cisco-modified software derived from the following packages that are licensed under version 2 of the GNU General Public License (GPLv2):

irqbalance

quagga

syslogd

Cisco will make the source code of these modified packages available upon request, in accordance with the terms of the GPLv2 license. Interested parties may obtain the source code by making a written request to:

Cisco Legal Department
300 E. Tasman Drive,
San Jose, California 95134

Please include the product name, version number, date of purchase, and specifics regarding the code you are requesting.

Related Documentation

Refer to the following documents for additional information about Cisco VQE and the Cisco CDE110 appliance:

Cisco CDA Visual Quality Experience Application User Guide, Release 2.0 (OL-14115-01)

http://www.cisco.com/en/US/docs/video/cds/cda/vqe/2_0/user/guide/vqe_guide2_0.html

Cisco Content Delivery Engine 110 Hardware Installation Guide (OL-14114-01)

http://www.cisco.com/en/US/docs/video/cds/cde/cde110/installation/guide/cde110_install.html

Regulatory Compliance and Safety Information for the Cisco Content Delivery Engine 110 (78-18228-01)

http://www.cisco.com/en/US/docs/video/cds/cde/regulatory/compliance/cde110_rcsi.pdf

For information on VQE Client, see the documentation that is provided in the TAR file containing the VQE Client software.

The entire Content Delivery Systems documentation suite is available on Cisco.com at:

http://www.cisco.com/cisco/web/psa/default.html

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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