Cisco 3.7 Visual Quality Experience Application User Guide
Quảng cáo
Quảng cáo
Cisco CDA Visual Quality Experience
Application User Guide Release 3.7
July 31 2013
Cisco Systems, Inc.
www.cisco.com
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.
Text Part Number: OL-30119-01
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.
Cisco CDA Visual Quality Experience Application User Guide, Release 3.7
©2007–2013 Cisco Systems, Inc. All rights reserved.
Text Part Number: OL-30119-01
OL-30119-01
C O N T E N T S
Preface
XIII
XIII
XIII
XIV
XV
XVI
Obtaining Documentation and Submitting a Service Request
XVII
Introduction to Cisco CDA
Visual Quality Experience Application
1-1
1-1
1-2
1-4
1-4
1-5
1-7
1-7
Lookaside Mode and the Cisco CDE
1-8
1-8
1-9
1-10
Support for All NAT Mapping Types
1-10
1-11
VQE-C Forward Error Correction
1-12
VQE-C IPTV Packet Loss Monitoring
1-13
VQE-C Software Development Kit and Documentation
1-13
VQE Deployment Options and Requirements
1-14
VQE Reference Architecture Model
1-14
Cisco End-to-End IPTV Solution Model
1-14
1-14
1-15
1-17
VCDS Delivery of the Channel Configuration File
1-17
VCDS Delivery of the Per-Client Network Configuration File
1-18
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
III
Contents
IV
VQE-C System Configuration Provisioning Server Role
1-20
1-20
1-20
1-21
VQE-S RTCP Exporter for Video-Quality Monitoring
1-23
1-24
1-26
1-27
Initial VQE Configuration
2-1
Web Browser, Screen Resolution, and Other Requirements
2-2
2-3
Configuring Terminal Emulation Software
2-3
Security Restrictions for Logins and Root Privileges
2-4
2-4
2-4
2-5
Using the Cisco VQE Configuration Tool for SSL Certificates
2-6
Creating Your Own Certificate Authority
2-6
Generating and Deploying Your Own SSL Certificates
2-7
Generating a Certificate-Signing Request
2-7
Signing the Certificate-Signing Request
2-8
Installing the Certificates, Private Key, and Keystore
2-9
Deploying Commercial SSL Certificates
2-10
Commercial CA: Installing the Certificates, Private Key, and Keystore
2-10
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
2-11
Bond Interfaces on a VQE-S and VQE-Tools Server
2-12
Types of Routes on a VQE-Tools Server
2-13
2-13
2-14
2-14
Using Dedicated or Shared Interfaces for VQE-S Ingest Traffic and for VQE-S Services Traffic
2-15
Routing Configuration for Dedicated Interfaces and Shared Interfaces
2-16
2-17
Interface for a Management Network
2-18
Load Balancing and Redundancy with Multiple VQE-S
2-19
Configuring LACP Bonding on a VQE-S and VQE Tools Server
2-20
2-20
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
OL-30119-01
Contents
2-20
Configuring VLAN Support on a VQE-S and VQE-Tools Server
2-22
Using the VQE Configuration Tool
2-23
2-24
2-32
VQE Configuration Tool Root Menu
2-36
On the VQE-S Host: Verifying the Status of the VQE and System Services
2-39
On the VQE Tools Host: Verifying the Status of the VQE and System Services
2-41
Configuring the VQE-S RTCP Exporter
2-42
Configuring VQE-S RTCP Exporter via manually editing the VCDB File
2-43
Configuring VQE-S RTCP Exporter via VQE Configuration Tool
2-44
Configuring the Other Parameters for the VQE-S Host
2-46
Configuring the Edge Router for VQE-S
2-46
For Bond Interfaces: Guidance for Configuring Bond Interface on the Attached Router
2-47
For OSPF Routing: Guidance for Configuring the Attached Router
2-48
2-48
2-49
2-49
For Static Routes: Guidance for Configuring the Feedback Targets on the Attached Router
2-50
Using the VQE Channel Provisioning Tool
3-1
3-2
Working with VCPT Configuration Files
3-3
Performing Configuration-File Operations
3-4
3-4
3-5
Sending or Pushing Channel Information to Servers
3-5
3-5
3-6
Sending Channel Information to a Subset of Servers
3-7
3-7
3-8
Viewing or Updating Channel Information
3-12
3-13
3-13
Defining VQE-Ss, VCDSs, or Remote Servers
3-14
3-16
Viewing or Updating Server Information
3-17
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
V
Contents
3-18
3-18
Defining Channel Associations for a Server
3-19
Copying Channel Associations from Another Server
3-19
Setting-up a SSH Certificate on a Remote Server
3-19
Using the VQE-S AMT
4-1
Logging into and Navigating in the VQE-S AMT
4-2
Monitoring the Health of the VQE-S Processes
4-4
Viewing Channel Configuration and Status
4-7
4-8
4-10
4-14
4-15
Monitoring Unicast Retransmission and RCC
4-16
Viewing Error Repair and RCC Configuration
4-16
Viewing Error Repair and RCC Statistics
4-17
4-21
4-22
Viewing Error Repair and RCC Capacity Statistics
4-23
4-26
4-28
4-30
4-31
4-32
4-33
4-33
Using the VCDS AMT
5-1
Logging into and Navigating in VCDS AMT
5-2
Monitoring the Health of the VCDS Process and VQE Tools Server
5-3
Viewing VCDS Configuration and Statistics
5-4
5-5
5-7
5-7
5-9
VI
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
OL-30119-01
Contents
Troubleshooting VQE Software Components
6-1
6-1
6-2
VQE Server and VQE Tools Logging and Log Files
6-2
VQE-S AMT, VCDS AMT, and VCPT Logging and Log Files
6-3
VQE Files, Directories, and Permissions
6-3
6-5
Replacing a Lost or Corrupt VQE File
6-5
VQE-S and VQE Tools Server Troubleshooting
6-7
Monitoring Received Multicast Streams
6-8
Repeated Message on CDE Hosting VQE-S or VQE Tools
6-9
Performing a Date and Time Change with NTP
6-9
Performing a Date and Time Change with the Linux
date
Command 6-10
VQE-S AMT, VCDS AMT, or VCPT Unavailable
6-10
Channels Are Not Displayed in VQE-S AMT
6-11
VQE-S AMT Channels Status Summary Has No Graphs
6-12
6-12
Channel-Provisioning Server Cannot Send Channel Information to VQE-S:
Trusted Provisioning Client Problem
6-13
Channel-Provisioning Server Cannot Send Channel Information to VQE-S: SSL Certificates Problems
6-13
Unable to Connect Error When VCPT Tries to Send Channel Information
6-14
Internal Server Error When VCPT Tries to Send Channel Information to VQE-S
6-15
6-15
6-16
Channel is not configured on the VQE-S
6-16
Channel is not active on the VQE-S
6-16
RCC is disabled on the channel
6-17
No connectivity between the VQE-C and the FBT on the VQE-S
6-18
No connectivity between the VQE-C and the VQE-S
6-18
RCC refused by the VQE-S control or data planes
6-18
RCC refused by the VQE-S—invalid e-factor
6-19
RCC refused by the VQE-S—insufficient bandwidth
6-19
MPEG Parser is unable to locate the burst start point
6-20
VQE-S MPEG Parser is unable to locate the ECM PID
6-21
Burst start point not found within the backfill range
6-21
No burst start point found—stream is invalid
6-22
6-23
6-24
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
VII
Contents
Problem with priming information sent from the VQE-S
6-24
First packets from repair burst not received within expected time period
6-25
6-25
6-25
6-28
6-29
Gathering Information for a Service Request
6-30
Stopping, Starting, and Restarting VQE-S
6-30
Stopping, Starting, and Restarting VCDS
6-31
Resetting the Root Password on the VQE-S or VQE Tools Server
6-31
Configuring VQE Server and VQE Tools
7-1
Managing /etc Configuration Files Using the VQE CMS
7-2
Managing /etc Configuration Files with the VQE CMS
7-2
Using the VQE Configuration Tool
7-3
Starting the Configuration Tool and Using the Root Menu
7-3
Using the Configuration Tool Menus
7-4
Entering Data for Configuration Parameters
7-6
Entering Data for Parameters That Can Have Only One Definition
7-6
Entering Data for Parameters That Can Have Multiple Definitions
7-7
Entering New Values for Parameters That Have a Currently Defined Value
7-8
Reverting to the Default VCDB Values
7-10
7-11
7-13
Manually Editing the VCDB File
7-14
7-14
7-15
7-15
Understanding the vcdb.conf.sample File
7-15
Using the VQE Configuration Tool Command-Line Options
7-18
VQE, System and Network Parameters
A-1
SNMP MIBs
B-1
B-1
B-1
B-2
B-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
VIII OL-30119-01
OL-30119-01
Contents
B-2
B-3
B-4
B-5
B-5
B-5
B-8
B-9
VQE System Messages
C-1
C-1
C-3
C-3
VQE System Messages Reference Information
C-4
Manual Initial VQE System Configuration
D-1
Setting Up a Cisco CDE That Hosts VQE-S
D-2
Prerequisites for a Cisco CDE That Hosts the VQE-S
D-3
Connecting Cables for the VQE-S
D-3
Setting Up SSL Certificates for the VQE-S
D-3
Configuring the Linux Operating System for the VQE-S
D-3
D-5
Configuring a Static Route for a Management Network (VQE-S Host)
D-6
Configuring Static Routes for VQE-S Traffic or VQE-S Services Traffic (VQE-S Host)
D-8
Enabling OSPF Routing for VQE-S Traffic or VQE-S Services Traffic
D-10
Configuring Interfaces for VQE-S Traffic (Ingest and Services) and VQE-S Services Traffic
D-15
Configuring Dedicated Interfaces for VQE-S Ingest Traffic and for VQE-S Services Traffic
D-16
Configuring Shared Interfaces for All VQE-S Traffic
D-17
Synchronizing the Time and Configuring Network Time Protocol
D-19
VQE STUN Server Is Enabled By Default
D-20
D-20
Ensuring That Only Trusted HTTPS Clients Can Communicate Using HTTPS
D-21
Configuring Remote Syslog Servers
D-22
Starting VQE-S System Services and Verifying Status
D-22
Starting the VQE-S Processes and Verifying Status
D-27
Restarting the System and Verifying System and VQE-S Status
D-28
Setting Up a Cisco CDE That Hosts VQE Tools
D-30
Prerequisites for a Cisco CDE That Hosts VQE Tools
D-31
D-31
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
IX
Contents
Setting Up SSL Certificates for VCPT
D-31
Configuring the Linux Operating System for VQE Tools
D-31
Configuring a Static Route for a Management Network (VQE Tools Host)
D-34
Synchronizing the Time and Configuring Network Time Protocol
D-36
D-37
Ensuring That Only Trusted HTTPS Clients Can Communicate Using HTTPS
D-38
Configuring Remote Syslog Servers
D-39
Starting VQE Tools System Services and Verifying Status
D-39
Starting the VCDS Service and Verifying VCDS, VCDS AMT and VCPT Status
D-43
Restarting the System and Verifying System, VCPT, VCDS AMT, and VCDS Status
D-44
Configuring DHCP and DNS Servers for VCDS
E-1
Using the vcds_send_file Command
F-1
VQE CDI and VQE-C Network-based Per-Client Configuration
F-1
F-2
Changing the Boot Sequence to Start from the CD/DVD Drive
G-1
VQE Server Performance and Scaling Limits
H-1
Ingress and Egress Bandwidth Limits
H-1
Scaling and Performance Summary
H-2
H-4
VCPT Configuration Files
I-1
I-1
VCPT Configuration File Data Rules
I-2
VCPT Configuration in XML Format
I-8
I-8
XML Data Elements and Attributes
I-16
I-17
VCPT Configuration in CSV Format
I-21
I-24
I-25
Using IPMI on Cisco CDE 250
J-1
J-1
Configuring IPMI on Cisco CDE-250
J-1
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
X OL-30119-01
Configuring Active Directory Settings for IPMI
J-2
J-3
Remote Server Health Monitoring
J-4
Viewing System Sensor Information
J-4
J-5
Remote Control of Cisco CDE 250 via IPMI
J-5
J-5
J-6
J-6
J-6
J-7
J-7
Contents
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
XI
Contents
XII
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Preface
This preface describes the objectives and organization of this document and explains how to find additional information on related products and services. This preface contains the following sections:
•
•
•
•
•
•
Document Revision History, page XIII
Document Organization, page XIV
Related Documentation, page XV
Document Conventions, page XVI
Obtaining Documentation and Submitting a Service Request, page XVII
Objectives
This document describes Cisco CDA Visual Quality Experience (VQE) Application, Release 3.7, and explains how to set up and use the VQE software.
Document Revision History
records technical changes to this document. The table shows the document revision number for the change, the date of the change, and a brief summary of the change.
Table 1 Document Revision History
Revision
OL-30119-01
OL-14115-13
OL-14115-12
OL-14115-11
OL-14115-10
OL-14115-09
OL-14115-08
OL-14115-07
Date
July 2013
August 2012
June 2012
April 2012
October 2010
June 2010
February 2010
August 2009
Change Summary
Document for Cisco VQE Release 3.7
Document for Cisco VQE Release 3.6.3
Document for Cisco VQE Release 3.6.2
Document for Cisco VQE Release 3.6
Document for Cisco VQE Release 3.5.5
RCC Troubleshooting section added
Document for Cisco VQE Release 3.5
Document for Cisco VQE Release 3.4
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
XIII
Table 1 Document Revision History
Revision Date Change
OL-14115-06
OL-14115-05
April 2009
January 2009
Document for Cisco VQE Release 3.3
Document for Cisco VQE Release 3.2
OL-14115-04
OL-14115-03
OL-14115-02
OL-14115-01
October 2008
August 2008
December 2007
August 2007
Document for Cisco VQE Release 3.1
Document for Cisco VQE Release 3.0
Document for Cisco VQE Release 2.1
Document for Cisco VQE Release 2.0
For information on the content and enhancements of each Cisco VQE Release, see the relevant VQE
Release notes.
Document Organization
This publication is organized as follows:
Chapter Title Description
Chapter 1
Chapter 2
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Provides an introduction to the VQE Application.
Explains how to use the vqe_cfgtool command to perform the initial configuration tasks for the Cisco CDE that hosts the VQE-S
1
and the CDE that hosts the VQE Tools.
Describes how to use the Cisco VCPT
2
.
Describes how to use the Cisco VQE-S AMT
3
.
Describes how to use the Cisco VCDS AMT.
Describes how to identify and remedy problems related to the Cisco VQE
Server, the VQE-S AMT, and the VCPT. The chapter also explains how to stop, start, and restart the VQE-S and VCDS
4
services.
Chapter 7
Describes these VQE Configuration Management System software components: the VQE Configuration Tool, the Configuration Engine, and the
VCDB Parser. The chapter also provides information on using the
Configuration Tool, manually editing the VCDB file, and using the
vqe_cfgtool command.
Provides descriptions of the VQE-S Configuration Database parameters. Appendix A
Appendix B
Gives information about the VQE-specific and standard Linux MIBs on the
Cisco CDE that hosts the VQE-S and on the CDE that hosts VQE Tools.
Provides information on the Cisco VQE system messages. Appendix C
Appendix D
Explains how to perform manual initial configuration on the CDE that hosts
VQE-S and on the CDE that hosts VQE Tools.
XIV
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter
Appendix F
Title
Appendix E
Appendix G
Changing the Boot Sequence to Start from the CD/DVD
Description
Provides information on configuring the DHCP
5
and DNS
6
servers so that they work correctly with the VCDS or another RTSP server.
Gives overview information on the network-based per-client configuration of the VQE-C
7
. Also, explains how to use the vcds_send_file command to send the client database file and group attribute file to one or more VCDSs.
Explains how to change the BIOS setting on the Cisco CDE server so that the server boots first from the CD/DVD Combo drive.
Appendix H
VQE Server Performance and Scaling Limits
Appendix I
Appendix J
Summarizes performance information of the Cisco VQE-Ss, and provides information on how to access the VQE-S capacity statistics.
Describes the VCPT import and export configuration file formats, and provides examples of both formats.
Gives supplementary information on IPMI GUI
1.
VQE-S = VQE Server
2.
VCPT = VQE Channel Provisioning Tool
3.
AMT = Application Monitoring Tool.
4.
VCDS = VQE Client Configuration Delivery Server.
5.
DHCP = Dynamic Host Configuration Protocol.
6.
DNS = Domain Name System.
7.
VQE-C = VQE Client.
Related Documentation
The following is a list of documents and Cisco.com URLs for the Cisco CDE and the Cisco CDA Visual
Quality Experience Application, Release 3.7:
• Release Notes for Cisco CDA Visual Quality Experience Application, Release 3.7
•
• http://www.cisco.com/en/US/docs/video/cds/cda/vqe/3_7/release/notes/vqe_notes3_7.html
Cisco CDA Visual Quality Experience Application User Guide, Release 3.7 (this document) http://www.cisco.com/en/US/docs/video/cds/cda/vqe/3_7/user/guide/vqe_guide3_7.html
Cisco CDA Visual Quality Experience Client System Command Reference Guide
•
•
•
• http://www.cisco.com/en/US/docs/video/cds/cda/vqe/vqec/CLI_Guide/Book.html
Cisco CDA Visual Quality Experience Client System Configuration Guide http://www.cisco.com/en/US/docs/video/cds/cda/vqe/vqec/configuration/guide/vqec_cnfg.html
Cisco Content Delivery Engine 205/220/250/420 Hardware Installation Guide http://www.cisco.com/en/US/docs/video/cds/cde/cde205_220_420/installation/guide/cde205_220_
420_hig.html
Cisco Content Delivery Engine 110 Hardware Installation Guide 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 http://www.cisco.com/en/US/docs/video/cds/cde/regulatory/compliance/cde110_rcsi.pdf
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
XV
• Regulatory Compliance and Safety Information for the Cisco Content Delivery Engines http://www.cisco.com/en/US/docs/video/cds/cde/regulatory/compliance/CDE_RCSI.html
Open Source Used in Visual Quality Experience 3.7
• http://www.cisco.com/en/US/products/ps7127/products_licensing_information_listing.html
The VQE Client (VQE-C) documentation is included in the VQE-C software TAR file. If you are a registered Cisco.com user, the file can be downloaded from the following location: http://www.cisco.com/kobayashi/sw-center/content-delivery/cda.shtml
Table 2 lists the VQE Client documentation that is provided.
Table 2 VQE Client Documentation
VQE-C Document Description
VQE-C System Integration Reference
Cisco CDA Visual Quality Experience Client
System Configuration Guide *
VQE-C CLI Command Reference
Provides information on the VQE-C components, architecture, integration, and APIs. Also includes a
VQE-C quick-start guide.
Explains certain factors to consider when configuring and deploying VQE-C. Also provides reference information on the VQE-C configuration file parameters.
Provides reference information on the VQE-C command-line interface.
* This guide is available only on Cisco.com. See the URL in the list preceding
Document Conventions
This guide uses the following conventions for command syntax descriptions and textual emphasis:
Convention Description
boldface font
italic font
[ ]
{x | y | z}
Commands and keywords are in boldface.
Arguments for which you supply values are in italics.
Elements in square brackets are optional.
Alternative, mutually exclusive, keywords are grouped in braces and separated by vertical bars.
[x | y | z] string
Optional alternative keywords are grouped in brackets and separated by vertical bars.
A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.
screen
font italic screen font
Terminal sessions and information the system displays are in screen
font.
boldface screen
font Information you must enter is in boldface screen
font.
Arguments for which you supply values are in italic screen font.
XVI
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Convention
^
< >
[ ]
!, #
Description
The symbol ^ represents the key labeled Control—for example, the key combination ^D in a screen display means hold down the Control key while you press the D key.
Nonprinting characters, such as passwords, are in angle brackets in contexts where italics are not available.
Default responses to system prompts are in square brackets.
An exclamation point ( ! ) or a pound sign ( # ) at the beginning of a line of code indicates a comment line.
Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this publication.
Tip Means the following information might help you solve a problem.
Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.
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 the following URL: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
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.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
XVII
XVIII
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
C H A P T E R
1
Introduction to Cisco CDA
Visual Quality Experience Application
This chapter provides information on Cisco CDA Visual Quality Experience (VQE) Application and contains the following major topics:
•
•
•
•
•
•
VQE Deployment Options and Requirements, page 1-14
VCPT and Channel Information, page 1-15
•
•
•
•
•
•
VQE-S RTCP Exporter for Video-Quality Monitoring, page 1-23
Content Delivery Engine 110, page 1-26
Content Delivery Engine 250, page 1-27
VQE Overview
This VQE overview has the following sections:
•
•
VQE Major Software Components, page 1-4
•
•
•
•
•
VQE Hybrid Error Repair, page 1-4
VQE Web Browser-based Tools, page 1-7
Lookaside Mode and the Cisco CDE, page 1-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-1 OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE Overview
Introduction to VQE
Cisco CDA Visual Quality Experience (VQE) Application offers service providers a set of technologies and products associated with the delivery of Internet Protocol television (IPTV) video services. VQE is designed to improve the quality of IPTV services and viewing experiences of the subscriber. VQE is part of a Cisco end-to-end solution that builds video awareness into the network infrastructure. For Cisco
VQE Release 3.7, VQE technology is intended for wireline operators who offer managed broadcast
(multicast) IPTV services using xDSL.
IPTV subscribers expect high video quality. Because many subscribers are migrating from existing analog or digital cable services, their quality expectation has already been set. To attract subscribers,
IPTV providers must meet or exceed the video experience of existing services. VQE technology and products provide that capability.
Video is less tolerant of network factors such as jitter, delay, and especially packet loss because a single
IP packet carries up to seven MPEG transport frames. Therefore, IP networks require additional functionality to deliver the video quality expected by subscribers. The accepted industry benchmark for quality is to deliver a maximum of one video artifact or perceived distortion during the viewing of a one-hour movie. This level of quality translates into a network-layer requirement of a loss of fewer than
7.8E-7 video packets. Most xDSL networks are not optimized to deliver such low levels of packet loss.
The second issue that affects IPTV video quality is channel change time (CCT). Consumers have become used to the current CCT—which is less than 2 seconds—offered by digital cable and digital satellite services. Several factors can contribute to longer IPTV channel change times, including Internet Group
Management Protocol (IGMP) delays, MPEG decoding delays, and I-frame acquisition time.
Non-optimized IPTV channel change times can take several seconds. Channel change times as long as
5 seconds have been observed.
VQE addresses the issue of video quality from both a network infrastructure and a video technology perspective. VQE provides the linkage to optimize video delivery over next-generation carrier networks.
Based on industry standards, including Real-Time Transport Protocol (RTP) and RTP Control
Protocol (RTCP), Cisco VQE provides these mechanisms to help in delivering entertainment-grade services to subscribers:
• Unicast Retransmission—Optimized, selective retransmission of dropped IPTV packets caused by noisy DSL lines or errors in the home network caused by poor quality wiring. The set-top box (STB) receiver, the VQE Client (VQE-C), sends non-acknowledgement (NACK) packets to the VQE-S to request retransmission of the lost packets.
•
•
Forward Error Correction (FEC)—Extra information is sent along with the video data at the application layer. The additional information is used by the VQE-C on the STB to detect and correct lost packets.
Rapid Channel Change (RCC)—When the subscriber requests a channel change, the VQE-C on the
STB sends the VQE-S a request for the IPTV packets of the new channel. The VQE-S sends the
VQE-C an optimized unicast burst of IPTV packets and other channel information for the new channel from the cached video data of the VQE-S. This greatly reduces the time needed to display the new channel.
• IPTV Packet Loss Monitoring—Facilities such as VQE-S RTCP Exporter help operators measure, baseline, and pinpoint problem areas of the video infrastructure, including transmission lines and home networks.
The two error-repair options, Unicast Retransmission and Forward Error Correction (FEC), can be used separately or together for Hybrid Error Repair (see
“VQE Hybrid Error Repair” section on page 4 ). Each
repair mechanism has its own advantages and limitations. Whether Unicast Retransmission or FEC or both are used, the subscriber does not detect the error repair and no video artifact results.
1-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE Overview
Figure 1-1 shows the location of the major network and VQE components in the service-provider
network and in the customer premises equipment (CPE) of the subscriber.
Figure 1-1
SHE
VQE Major Components
VHO VSO/CO CO Customer premises
VQE Server on CDE250
VQE Client on Cisco STB
IPTV (RTP) multicast streams
Encoders
Unicast transmissions to VQE Clients
Metro network
N-PE router PE-AGG router
DSLAM
VQE Client on third-party STB
VQE operates on errors in this part of network
If FEC is used for error repair, an SMPTE 2022-compatible FEC stream generator, such as the Cisco
Digital Content Manager (DCM), is required. The FEC stream generator, shown in
, is often located in the headend and sends application-layer FEC packets. RTP encapsulation is a prerequisite for
FEC.
The FEC stream generator, which is connected to the real-time encoders, subscribes to video channels from the headend and encodes FEC for each channel. It is responsible for originating FEC packets associated with individual channels and with primary multicast streams. For each FEC-enabled channel, a primary media stream and two encoded FEC streams are sent over multicast addresses (see
).
Figure 1-2 FEC Stream Generator
Primary media stream
FEC stream generator
FEC 1 stream
FEC 2 stream
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-3
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE Overview
VQE Major Software Components
The two major VQE software components that implement Unicast Retransmission, FEC, RCC, and IPTV
Packet Loss Monitoring are:
• VQE-C—Software embedded in the CPE of the subscriber—typically a STB. The VQE-C provides the CPE interface to the VQE Server (VQE-S) to support Unicast Retransmission, RCC, and IPTV
Packet Loss Monitoring statistics. The VQE-C receives the primary media data packets and, if FEC is enabled, one or two streams with FEC packets. When the VQE-C software detects packet loss on a channel that is configured for FEC and Unicast Retransmission, the following occurs:
–
–
If there are packet losses in the primary media stream, the VQE-C first tries to repair the lost packets using the FEC streams.
If some packet losses cannot be corrected by FEC, the VQE-C requests a Unicast
Retransmission of the missing packets from the VQE-S.
• VQE-S—Software that runs on a Linux-based Cisco Content Delivery Engine (CDE) appliance located in the intelligent edge of the service provider’s network. For Unicast Retransmission and
RCC, the VQE-S caches primary video packets from an encoder or other headend device.
– For Unicast Retransmission, working with the VQE-C, the VQE-S monitors the subscriber’s reception of video packets and uses its cached video data to service Unicast Retransmission requests from the VQE-C on the STB.
– For RCC, when the subscriber requests a channel change, the VQE-C on the STB sends a request for a new channel to the VQE-S. To service the RCC request, the VQE-S sends the
VQE-C a unicast burst of video packets from its cached video data for the channel and also sends some MPEG priming information to facilitate immediate decoding.
With both Unicast Retransmission and FEC, the missing packets are resequenced by the STB without interruption.
The VQE-C is available with certain Cisco STBs running Scientific-Atlanta IPTV Layer (SAIL) 1.x and
2.x. Please contact your Cisco sales representative for further information. The VQE-C can also be integrated into a STB from third-party vendors. The VQE-C code and Software Development Kit (SDK) is available to third-party vendors through an open-source program.
VQE Hybrid Error Repair
VQE Hybrid Error Repair occurs when Unicast Retransmission and FEC are used together. The devices used for Hybrid Error Repair are shown in
Figure 1-3 , which for simplicity omits some of the network
elements. Hybrid Error Repair allows the service provider to customize VQE error repair to match the error characteristics of a given access network.
1-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
Figure 1-3 Hybrid Error Repair
VQE Overview
VQE Server on CDE110
Encoder
FEC stream generator
Primary media stream
Unicast
Retransmission
VQE Client on STB
Headend FEC streams
PE-AGG Router
In an IPTV system, video data is very sensitive to packet losses because of the interdependence of the encoded data. One packet loss could cause quality degradation of several successive frames in a group of pictures (GOP). Selective retransmission and FEC are two methods to protect channels from packet losses.
With selective retransmission (Unicast Retransmission), RTCP NACK compound packets are sent to the
VQE-S to request retransmission of the lost packets whenever the receiver (VQE-C) detects dropped packets. Selective retransmission is very efficient in terms of bandwidth utilization in a unicast scenario, but may flood the network with control packets when errors are highly correlated in nature. Starting with
Cisco VQE Release 3.7, it is possible to configure the VQE-C on a per-channel basis to send RTCP
NACK compound packets without Receive Reports (RRs) to reduce the bandwidth consumed by RTCP
NACK compound packets on the access link.
The application-layer FEC method of error repair is usually used for controlling errors in a one-way communication system. The FEC stream generator (for example, the Cisco DCM) sends FEC information along with the primary media stream. The VQE-C uses the FEC data to detect and correct the lost packets. No feedback to the VQE-S is needed. FEC is optimized for non-bursty, correlated errors.
Unicast Retransmission is better for bursty, uncorrelated errors.
In addition to providing a flexible solution for error repair, VQE Hybrid Error Repair is also able to correct more lost-packet errors than when FEC is used alone. If the VQE-C tries but is unable to retrieve lost packets using FEC, it can request that the VQE-S selectively retransmit the dropped packets.
The VQE Hybrid Error Repair solution provides the flexibility to customize an error-repair scheme that best suits the network error characteristics and available access-link bandwidth.
VQE RCC
Channel change time is defined as the time from when a subscriber initiates a channel change to the time the video for the new channel is displayed. The RCC functionality built into the VQE-S and the VQE-C reduces channel change time from several seconds to approximately one second.
There are several factors that contribute to channel change time:
•
•
Multicast latency for leaving the old channel (IGMP leave latency).
Time it takes for the STB to receive the information it needs to begin demultiplexing, decoding, decrypting, and displaying the video stream. This time includes how long it takes to receive the following:
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-5
VQE Overview
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
– Program Association Tables (PAT), Program Map Tables (PMT), and Entitlement Control
Messages (ECM) if decryption is required.
–
–
Program Clock Reference (PCR) and sequence header information (for example, frame rate).
Random access point (such as I-frame) acquisition delay.
–
–
Network buffer delays, including delays caused by error-mitigation techniques (Unicast
Retransmission or FEC).
MPEG decoder buffer delay.
• Multicast latency for joining the new channel (IGMP join latency).
Not all of the above factors need to be addressed by RCC functionality. For example, many Digital
Subscriber Line Access Multiplexers (DSLAMs) can provide fast leave for IGMP, which addresses the multicast leave latency factor.
The goal of RCC is to reduce or eliminate the main sources of channel change delay. With RCC, the resulting channel change delay should be similar to or better than the delay observed in a typical digital broadcast.
For RCC, the VQE-S caches multicast IPTV packets corresponding to each channel (see
Each cache holds a few GOPs of video data as well as PAT, PMT, ECM, PCR, and sequence information.
When the subscriber requests a channel change, the VQE-C on the STB requests the IPTV packets for the new channel from its target the VQE-S, using a specific RTCP message. After it has sent the RTCP message, the VQE Client issues an IGMP join for the new channel at an optimum point in time.
Figure 1-4 VQE Server Caches Multicast IPTV Packets for RCC
VQE Server on CDE110
CH-n cache
CH-3 cache
CH-2 cache
CH-1 cache
RCC unicast burst
VQE Client on STB
IPTV multicast streams
PE-AGG router DSLAM
Upon receipt of the request, the VQE-S locates the appropriate channel cache, identifies the location of the IPTV packet carrying the beginning of a recent I-frame, and sends a short unicast burst of packets starting with the I-frame to the requesting VQE Client.
Before sending the unicast burst, the VQE-S originates an RTCP message to the requesting VQE Client
priming it with video parameters such as PAT, PMT, and ECM.
1-6
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE Overview
Because the incoming burst from the VQE-S contains an I-frame, the STB decoder can immediately start processing the MPEG information. This greatly reduces the time a subscriber waits before the image is rendered on the TV screen. Other VQE optimizations for RCC, such as Fast Decoder Buffer Fill, shorten channel change time by reducing MPEG decoder buffer delay.
After a short period of time, multicast packets for the new channel start to arrive at the STB. The VQE-C monitors RTP sequence numbers from both unicast and multicast streams. It is likely that the VQE-C sees a few packets with duplicate RTP sequence numbers before the unicast stream ends. During this period, the VQE-C only forwards one copy of the RTP packet to the MPEG demultiplexing stage.
The VQE-C is responsible for managing the seamless transition between unicast and multicast IPTV packets. The RCC unicast burst continues for up to the full duration of the IGMP join or until it is explicitly stopped by a message sent from the VQE-C to the VQE-S.
RTP and RTCP
VQE relies on RTP and RTCP. RTP is used to carry video packets over multicast streams from the video headend to the VQE-Cs on the STBs. It is also used to transport specific video packets between the
VQE-S and a VQE-C. RTCP is a signaling protocol used between VQE devices. RTP is the transport baseline for application-layer FEC, Unicast Retransmission, and RCC.
RTP encapsulation is typically the responsibility of real-time encoders and specialized video products, such as a Cisco DCM. These devices often reside in the video headend office (VHO) or super headend (SHE). RTP sequence numbers are assigned to IPTV packets and are unique within a given multicast group or channel.
A growing number of real-time encoders support native RTP and SMPTE 2022 FEC. For those that support UDP only or RTP encapsulation, the Cisco DCM product is recommended. For FEC support, the
DCM requires the GbE I/O Board with a FEC daughter card, and DCM software version 5 or higher.
VQE Web Browser-based Tools
VQE also provides three web browser-based tools: VQE Channel Provisioning Tool (VCPT), VQE-S
Application Monitoring Tool (AMT), and VQE Client Configuration Delivery Server (VCDS) AMT.
•
•
VCPT is an optional channel-provisioning utility to aid with the channel lineup configuration required by both the VQE-S and the VQE-C. The channel information is in Session Description
Protocol (SDP) format. The VCPT sends the channel information to the VQE-Ss and VCDSs. The
VCDS servers provide the channel lineup or network configuration to the VQE-Cs on the STBs.
VQE-S AMT is a browser-based GUI that displays configuration, status, and statistics on the VQE-S processes, the channel lineup, Unicast Retransmission, RCC, Ethernet interfaces, and VQE-S RTCP
Exporter. The VQE-S AMT also allows you to configure debugging and logging facilities.
• VCDS AMT is a browser-based GUI that displays configuration, status, and statistics on the VCDS and VQE Tools server. The VCDS AMT also allows you to configure debugging and logging facilities.
The VQE-S and the VCPT are bundled software and hardware solutions. The VQE-S and the VCPT run on separate Cisco CDE appliances. A typical network might consist of multiple CDEs hosting the
VQE-S and one or two CDEs hosting the VCPT, the VCDS AMT, and the VCDS.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-7
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE Benefits
Lookaside Mode and the Cisco CDE
The VQE-S software functions in lookaside mode where the VQE-S is not directly in the video data path.
Lookaside mode has these advantages:
• If the Cisco CDE appliance or the VQE-S software should fail, there is no loss of IPTV service to the customer.
•
•
Because no multicast forwarding is provided by the VQE-S, more IPTV customers can be serviced by each VQE-S instance.
Number of Cisco CDE appliances hosting the VQE-S can be easily scaled up as subscriber count and the demand for VQE services increase.
The Cisco CDE is a standalone, carrier-hardened appliance running the Linux operating system. The
Cisco CDE is NEBS-compliant and suitable for central office lights-out locations. The Cisco CDE comes with the required software preinstalled: VQE-S or VCPT, Linux, Apache web server, and other software.
VQE Benefits
Cisco VQE Release 3.7 provides the following benefits to the service provider:
• Supports Hybrid Error Repair allowing use of Unicast Retransmission or FEC or both
•
•
Addresses noise issues associated with lossy DSL lines and home network wiring
Reduces or eliminates the need for outside plant optimization, such as pair swapping, joint renewals, and drop-cable reruns
•
•
•
•
Increases addressable market consumer base because Hybrid Error Repair technology enables video service over noisier transmission lines, thus extending available footprint
Reduces or eliminates the need to fragment video service into consumers that can and cannot receive service based on line quality attributes
Supports RCC to effectively reduce or eliminate the main sources of channel change delay
Employs much of the same infrastructure and the same technology (RTCP) for Unicast
Retransmission and RCC—thereby reducing service-provider training time
•
•
•
•
Reduces or eliminates quality-related service-center calls
Establishes a video quality baseline for all consumers with granularity per STB
Provides an end-to-end view of network characteristics from an IPTV delivery perspective
Uses open, standards-based protocols
Cisco VQE also provides the subscriber with an enhanced video experience with higher and consistent visual and audio quality. Subscribers with noisier transmission lines or longer loop lengths can take advantage of the video offerings, bundles, and unique content of the service provider.
1-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE-S
VQE-S
The VQE-S software is hosted on a Cisco CDE appliance running a standard Linux operating system.
The Cisco CDE comes with the required software preinstalled: VQE-S, VQE-S AMT, Linux, Apache web server, and other software.
The VQE-S is responsible for the following functions:
•
•
•
•
•
•
Creating a channel configuration database using the channel configuration information sent by the
VCPT
Maintaining per-channel and per-component state information
Handling Unicast Retransmission by caching RTP data streams for channels and sending repair packets to the requesting VQE-Cs on the STBs
Handling RCC by caching RTP data streams as well as PAT, PMT, ECM, PCR, and sequence information and sending RCC unicast bursts to requesting VQE-Cs when a channel change occurs
Load balancing VQE-S services across the Cisco CDE Ethernet or bond interfaces
Providing detailed statistics on IPTV delivery down to the STB VQE-C level
• Monitoring the health of VQE-S application processes
Like a regular IP host, the VQE-S joins multicast groups using Internet Group Management
Protocol (IGMP). The VQE-S maintains a dedicated buffer for each channel. The VQE-S receives the multicast stream for each channel from upstream, caching a few seconds of the most recently received program content from each. The VQE-S can use the same cache of video to service both Unicast
Retransmission requests and RCC requests.
For Unicast Retransmission, when a VQE-C requests retransmission of missing packets, the VQE-S locates them in its cache and, if found, delivers them to the STB through an associated RTP retransmission stream. See
in
Appendix H, “VQE Server Performance and
for information on the VQE-S inbound repair request limits.
Several factors affect how many errors a single VQE-S can repair for a single VQE-C. These factors include the distribution of errors, the bandwidth of the channel, and the size of the jitter buffer in the
STB. The VQE-S software includes global and per-client policers to provide sensible rate limits for the traffic associated with Unicast Retransmission.
For RCC, the VQE-S uses much the same infrastructure as Unicast Retransmission with some major additions. The VQE-S can use the same cache of video data for both Unicast Retransmission and RCC.
Instead of requesting repair of a specific packet, the VQE-C sends the VQE-S an RTCP message requesting a unicast burst of IPTV packets for a new channel.
In addition, the VQE-S uses its MPEG Parser component to choose the start point of the RCC burst for the new channel. To properly form the RCC burst, the MPEG Parser examines the video data for several pieces of crucial information, caches the information, and provides it to other VQE-S components upon receipt of an RCC request. Before play-out can begin, the VQE-C must receive this information (for example, PAT, PMT, and PCR) to properly display the video. This additional data is sent out of band of the RCC burst and is used to prime the MPEG decoder on the client side.
The VQE-S separates the bandwidth resources that are dedicated to Unicast Retransmission and RCC.
A VQE-S configuration parameter (vqe.vqes.reserved_er_bw) controls the bandwidth resources that are dedicated to Unicast Retransmission. The parameter allows the amount of resources dedicated to Unicast
Retransmission to be reduced so that the resources are available for RCC instead. The VQE-S provides capacity statistics to indicate when Unicast Retransmission and RCC capacity limits have been exceeded. For more information on the VQE-S capacity statistics, see the
“VQE-S Capacity Statistics” section on page H-4
of
Appendix H, “VQE Server Performance and Scaling Limits”
.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-9
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE-S High Availability
The VQE-S supports setting Differentiated Services Code Point (DSCP) values on IPTV-related packets so that specific levels of service can be assigned to RTCP and RTP packets. For RTP traffic, the service provider can configure separate DSCP values for Unicast Retransmission and RCC. DSCP values are set using the VQE Configuration Tool.
For VQE-S performance information, see
Appendix H, “VQE Server Performance and Scaling Limits”
.
VQE-S High Availability
The VQE-S provides several high-availability mechanisms for resiliency and redundancy:
• VQE-S processes (Control Plane, Data Plane, Multicast Load Balancer, and STUN Server) are constantly monitored by the VQE monitoring process—Process Monitor. If a VQE-S process fails, the Process Monitor automatically attempts to restart it.
•
•
If the Process Monitor itself fails, the Linux initialization process detects this failure and restarts the
VQE-S service (Process Monitor).
If a Cisco CDE running a VQE-S fails and there is a redundant, backup CDE running a VQE-S that is configured to receive the same multicast streams, the backup VQE-S takes over servicing the streams.
• Use of anycast IP addresses and equal-cost multi-path routing allows multiple VQE-Ss in a single facility to be load balanced between servers and to provide failover protection in case of a server failure. For more information, see the
“Load Balancing and Redundancy with Multiple VQE-S” section on page 2-19 .
For Multicast Load Balancing, when a multicast stream used for caching on the VQE-S host starts or stops, the VQE-S determines the best Cisco CDE Ethernet interface on which to join or leave the multicast group. The VQE-S software distributes the joins across available interfaces to avoid oversubscription. The VQE-S also monitors the status of these interfaces, moving the streams to other interfaces in case of interface failure.
The VQE-S uses Linux system and network services for system initialization, network access, interface status monitoring, and multicast stream reception.
Support for All NAT Mapping Types
VQE supports all Network Address Translation (NAT) mapping types, including address and port-dependent mapping (symmetric NAT). Symmetric NAT is the most restrictive form of NAT behavior.
Deployments where a CPE device is behind a NAT device require a NAT transversal mechanism, such as a Simple Traversal of UDP (User Data Protocol) through NATs (STUN) Server. The STUN Server is included with the VQE-S software, and a STUN Client is included with the VQE-C. When the VQE-C tunes to a new channel, it sends STUN binding requests to the STUN Server on the VQE-S host. The
VQE-C sends the requests to the feedback target IP address of the channel and RTP and RTCP retransmission ports as configured on the VQE-S. The VQE-C uses the STUN Server responses to determine whether it is behind a NAT device and what type of NAT device it is.
The VQE-C is optimized to handle a variety of NAT configurations. For example, if the VQE-C determines from the initial STUN responses that it is not behind a NAT device, it turns off NAT mode so that the VQE-C does not send further STUN messages.
1-10
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE-C
The STUN Server that is included with the VQE-S can be turned on or off using a configurable option in the VQE-S configuration file. Unless it is certain that no STBs being serviced by VQE-S are behind a NAT device, we recommend that you enable the STUN Server. For information on enabling the STUN
Server, see the
“VQE STUN Server Is Enabled By Default” section on page D-20
.
VQE-C
The VQE-C software runs on customer premises equipment (CPE), such as a STB. The VQE-C supports
Unicast Retransmission, FEC, RCC, and video-quality statistics by providing the following:
•
•
•
•
CPE interface to the VQE-S for Unicast Retransmission and RCC
FEC functionality to receive and decode FEC packets for error repair
RTP packet reordering
RTP data plane jitter buffer and de-jittering
• IPTV Packet Loss Monitoring
For Unicast Retransmission, if an error in video transmission occurs, the VQE-C software detects the packet loss and requests a retransmission by sending a RTCP NACK compound packet to the VQE-S while holding the video sequence in queue. The VQE-S automatically repairs the error by transmitting the missing packet, which is resequenced by the STB without interruption. The entire error-repair cycle is imperceptible to the viewer. The RTCP NACK compound packet consists of an RR (Receiver Report) message, an SDES (source description) message, a PUBPORTS (publish ports) message, if applicable, and a generic RTP feedback (RTPFB) NACK message. Starting with Cisco VQE Release 3.5.5, the RR packets may be omitted to reduce the bandwidth utilized by the RTCP NACK compound packets on the access link.
For RCC, when a subscriber selects a new channel, the VQE-C sends to the VQE-S a special RTCP packet requesting a unicast burst of the IPTV packets for the new channel. As soon as the unicast IPTV packets arrive, the VQE-C software is responsible for sending the packets to the decoder. When the multicast IPTV packets for the new channel begin to arrive, the VQE-C manages the seamless transition between unicast packets from the VQE-S and multicast packets from the headend encoder.
The VQE-Cs can get channel configuration information and per-client network configuration from a
VCDS or from a centralized network management/configuration server that supports the DESCRIBE request of the RTSP protocol. For information on the interactions between a VQE-C and a VCDS, see the
“VCDS” section on page 17 section.
Each VQE-C can communicate client-specific information to a VQE-S so that some VQE-S services can be optimized for the particular client. Two examples of this capability are as follows:
• Maximum Receive Bandwidth—Each VQE-C can communicate a maximum receive bandwidth on the STB to the VQE-S so that VQE-S can precisely set the excess bandwidth available for Unicast
Retransmission and RCC. This information is specified with VQE-C system parameters and is used to determine the rate at which VQE-S sends packets to this VQE-C.
• Decoder Buffer Burst Shaping—Each VQE-C can communicate the size of the STB decoder hardware buffer using the VQE-C system parameter max_fastfill. This size is used for RCC and allows a STB with limited memory to perform RCC. Using the buffer size provided by the VQE-C, the VQE-S modifies the shape of the RCC burst to take advantage of fast decoder fill capabilities.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-11
VQE-C
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
The VQE-C supports setting Differentiated Services Code Point (DSCP) values on IPTV-related packets it sends so that specific levels of service can be assigned to packets. DSCP values can be configured with the rtcp_dscp_value parameter in the VQE-C system configuration file. The setting of rtcp_dscp_value applies to both the RTCP messages and the STUN messages. For information on VQE-C system parameters, see Cisco CDA Visual Quality Experience Client System Configuration Guide.
Starting with Cisco VQE Release 3.5.5, the VQE-C provides a data path for packets from UDP
MPEG2-TS streams and RTPv2 streams that are not configured in the VQE-C channel line up. No VQE services (that is, Error Repair and RCC) are provided for these streams. For UDP streams, the VQE-C acts as a pass-through device. For RTP streams not configured in the channel line up, the VQE-C provides reordering of packets.
The VQE-C supports the monitoring and reporting of a subset of TR-135 statistics. The technical report
TR-135—Data Model for a TR-069 Enabled STB defines a hierarchical model of statistics that may be collected by remote management stations for the purposes of monitoring and troubleshooting STB services. The VQE-C is in an ideal position to support the collection of the subset of these statistics that correspond to the IPTV and VoD streams that the VQE-C buffers. For more information on configuring the VQE-C to collect TR-135 statistics, see VQE-C System Integration Guide. For information on
TR-135 data model statistics, the TR-135 data model can be found at this url: http://www.broadband-forum.org/technical/download/TR-135.pdf
The VQE-C supports statistics counters that can be utilized to implement SNMP MIB views. The VQE-C provides APIs to export tuner and channel cumulative MIB-compatible counters. For more information on creation of SNMP MIB Views of VQE-C counters, see VQE-C System Integration Guide.
The VQE-C is available in two deployment models:
•
•
VQE-C is integrated into selected Cisco STBs.
VQE-C code is offered through an open-source program for integration with STBs from third-party vendors.
For information on VQE-C deployment models, see
“VQE Deployment Options and Requirements” section on page 14 .
VQE-C Forward Error Correction
The VQE-C supports both one-dimension FEC (one FEC stream) and two-dimension FEC streams (two
FEC streams). The Cisco DCM or other SMPTE 2022 compliant FEC stream generator sends one primary media stream and one or two FEC streams over different UDP ports to VQE-C. The VQE-C receives and processes these FEC streams to provide packet-level error repair.
Before receiving the FEC packets, the VQE-C must learn some basic information about the FEC session, such as the IP address and port numbers of FEC streams. This information is obtained through the channel configuration file that is sent to the VQE-C from the channel provisioning server, such as VCDS.
The FEC streams are configured on a per-channel basis.
When a VQE-C detects packet loss on a channel that is configured for FEC and Unicast Retransmission, the following occurs:
•
•
VQE-C first tries to repair the lost packets using the FEC streams.
If some packet losses cannot be corrected by FEC, the VQE-C requests a Unicast Retransmission of the missing packets from the VQE-S.
The use of one-dimension (1-D) or two-dimension (2-D) FEC is configured when the channel is defined.
1-D FEC uses one FEC stream, and 2-D FEC uses two FEC streams. While 2-D FEC can correct more packet losses than 1-D FEC, 2-D FEC sometimes requires more intensive processing of both FEC
1-12
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE-C streams to maximize the number of packets recovered. FEC bandwidth overheads may be too high in some deployments for full FEC-based error repair deployment. FEC can be turned on or off on a per-channel basis through the VQE-C channel configuration file.
The VQE-C supports several extensions to the SMPTE 2022 standard. The VQE-C autodetects L
(column) and D (row) values, and allows any combination of L and D sizes where L*D <= 256. This is an extension of the SMPTE 2022 limit of L*D <= 100. The VQE-C also allows any payload value to identify FEC packets where the standard says the value must be equal to 96.
The VQE-C supports SMPTE 2022 Annex A and Annex B stream orderings. For detailed information on 1-D and 2-D FEC, see SMPTE standard Forward Error Correction for Real-Time Video/Audio
Transport Over IP Networks (SMPTE 2022-1-2007). The standard is available for purchase at this URL: http://www.smpte.org/standards
VQE-C IPTV Packet Loss Monitoring
When used with VQE-S RTCP Exporter, the VQE-C software also provides the instrumentation for
IPTV Packet Loss Monitoring and valuable last hop analysis. The VQE-C generates RTP packet-level statistics for packet loss, jitter, delay, and other quality measurements. The VQE-C provides statistics on both Unicast Retransmission and FEC. For the RTCP reports, the VQE-C sends RTCP compound packets to their target VQE-S. Each compound packet contains an RTCP receiver report as well as other information.
For more information on IPTV Packet Loss Monitoring, see the
Video-Quality Monitoring” section on page 23
.
VQE-C Software Development Kit and Documentation
The VQE-C consists of a software development kit (SDK), which can be used for VQE-C integration into STBs from third-party vendors. The VQE-C code and SDK is available to third-party vendors through an open-source program. The VQE-C code resembles a standard Linux software component.
The VQE-C source code is currently supported for the Linux operating system. For information on support for other operating systems, contact your Cisco account representative.
The VQE-C library provides a set of high-level APIs designed to support easy integration into an existing
STB software base. The programmatic interface provides a socket replacement interface, which is used to get packets from a repaired VQE-S server-enhanced video stream. The VQE-C also provides APIs for updating its channel configuration data and acquiring statistics on error repairs.
The integrator configures the VQE-C through system configuration file parameters. The parameters allow customizing of many elements of the VQE-C system (for example, number of concurrent streams and client policing). The configuration of a VQE-C must be coordinated with the configuration of the
VQE-S. Certain features are operational only when they are enabled on both the VQE-C and the VQE-S.
The VQE-C command-line interface (CLI), based on the open source library libcli
( http://sourceforge.net/projects/libcli ), is designed primarily for testing and debugging the VQE-C software on the STB. The scope of the CLI is limited to the VQE-C software only. The CLI is accessible by Telnet.
The VQE-C SDK and documentation can be downloaded from Cisco.com. See the “Related
Documentation” section on page -XV for a list of the VQE-C documentation that is available.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-13
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE Deployment Options and Requirements
VQE Deployment Options and Requirements
The two basic deployment options for VQE are as follows:
• VQE reference architecture model—For existing IPTV deployments or new IPTV deployments that do not use Cisco STBs
• Cisco end-to-end IPTV solution model—For new IPTV opportunities
With both deployment options, the VQE-S is deployed on a Cisco CDE appliance running Linux.
VQE Reference Architecture Model
The VQE reference architecture model is designed for existing IPTV deployments or new IPTV deployments that do not use Cisco STBs. Cisco offers the VQE-C as open-source software. The VQE-C is implemented so that service providers and CPE device vendors can integrate the VQE-C software with third-party STBs. Appropriate development-level documentation is available along with the VQE-C code.
With this model, the service provider uses the VCPT to define channels and servers and to create channel lineups for different subscriber regions. The VCPT sends the channel information to the VQE-Ss, and to the VCDSs or a remote server from which each VQE-C gets its channel information. The channel information is in the Session Description Protocol (SDP) format required by the VQE-S and the VCDS.
Cisco End-to-End IPTV Solution Model
The Cisco end-to-end IPTV solution model is designed for new or greenfield IPTV opportunities. VQE technology is included as an integral part of the Cisco end-to-end video solution.
In this model, the VQE-C is integrated with selected Cisco STBs. The main difference between the Cisco end-to-end IPTV solution and the VQE reference architecture models lies with the integration responsibility of the VQE-C.
•
•
For the Cisco end-to-end IPTV solution model, Cisco is responsible for the integration and testing of the VQE-C.
For the VQE reference architecture model, the third-party vendor is responsible for the integration and testing of the VQE-C.
For the Cisco end-to-end IPTV solution, contact your Cisco representative for details of the STB models and software versions supported.
VQE Deployment Requirements
To deploy VQE, the following prerequisites must be met:
•
•
RTP support—Video streams from the headend must be encapsulated in RTP. Service providers can deploy products such as the Cisco Digital Content Manager (DCM) to provide RTP encapsulation capabilities at the video headend.
VQE-C and CPE integration— VQE-C must be integrated with the software of the CPE device
(STB).
1-14
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VCPT and Channel Information
•
•
•
•
•
TV channel information—VQE-C and the VQE-S require details of network-level TV channel lineup information. This includes per-channel IP multicast addresses, port numbers, and some other parameters. The information must be presented to the VQE-C and the VQE-S components in Session
Description Protocol (SDP) format. The VCPT is designed specifically for this purpose.
If forward error correction is used, an SMPTE 2022 compatible device, such as an encoder or
Cisco DCM, is required to send FEC streams to the VQE-C.
VQE-S network connectivity—VQE-S requires a connection to the edge router for the purposes of joining and receiving Internet Group Management Protocol (IGMP) multicast groups (channels).
A direct, Layer 3 connection between the VQE-S and the edge router is preferred.
VQE-C network connectivity—VQE-C requires an IP unicast path to and from its designated
VQE-S. The path is used for RTP Control Protocol (RTCP) signaling between the VQE-C and the
VQE-S, and for sending RTP data packets from the VQE-S to the VQE-C.
All versions of IGMP are supported by the VQE-S and the VQE-C.
VCPT and Channel Information
The VCPT is responsible for the creation, maintenance, and distribution of the channel information containing channel-lineup data. The VCPT includes a browser-based GUI that allows the service provider to provision the following:
•
•
Channel definitions—Information on the channels that is serviced by VQE
Server definitions—Information on each VQE-S, VCDS, and Remote Server that receives the channel information
• Channel lineups—Associations between channels, the VQE-Ss, and the VCDSs
details include information that is used for VQE error repair—both Unicast Retransmission and
FEC—and for RCC. The option to enable reduced-size RTCP messages is available in Cisco VQE
Release 3.5.5 and later releases.
Figure 1-5 VCPT Channel Definition
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-15
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VCPT and Channel Information
The VCPT GUI has a clone capability to simplify and expedite channel information. When the service provider uses the VCPT to define the set of the VQE-Ss that receive the channel information, the VQE-Ss can be grouped based on channel lineups. Using separate VCPT configuration files makes it possible to manage multiple deployments. For example, one VCPT configuration file might be for the channel lineup in one metro region, and another VCPT configuration file might be for the channel lineup in another metro region.
The VCPT GUI has the capability to import a configuration from a file. The file must be in either XML or CSV format, and must comply with the data rules and definitions specified in
file.
The VCPT channel-provisioning process creates a persistent local database, which is stored on the Cisco
CDE appliance. When the Cisco CDE or VCPT is restarted, channel data and server grouping information is read from the local database.
When the user completes channel, server, and channel-lineup configuration and starts the VCPT send operation, the VCPT sends the channel information in Session Description Protocol (SDP) format to the set of VQE-Ss, to the VCDS, or to a Remote Server.
The VCPT sends or pushes the channel information to all VQE-Ss that are defined in the current VCPT configuration file. The channel information is sent to the VQE-Ss over secure HTTPS. The VCPT contains a secure HTTPS client, and each VQE-S has an embedded web server running. Each VQE-S
stores it own local copy of the channel information. Figure 1-6
shows the interactions between the VCPT and the VQE-Ss. For information on the VQE-Ss, see the
.
Figure 1-6 VCPT: Sending Channel Information to VQE Servers
VCPT
Browser-based GUI
VQE Servers on CDE110s
HTTPS
VCPT on CDE110
HTTPS SDP “push”
The VCPT is also responsible for sending channel information to each VCDS. The VCDS is a software component installed on each VQE Tools server, the Cisco CDE that also hosts the VCPT. When the service-provider operator initiates the VCPT send operation, the VCPT pushes the channel information to one or more VCDSs. The VCPT sends the channel information in SDP format through HTTPS similar to the way it is sent to the VQE-Ss.
shows the interactions between the VCPT and the VCDSs. Each VQE Tools server includes both the VCPT and the VCDS. The VCPT can also send channel information to the VCDS on the same
CDE on which the VCPT resides. This interaction within a single VQE Tools server (CDE) is not shown in
1-16
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
Figure 1-7 VCPT: Sending Channel Information to VCDSs
VCPT
Browser-based GUI
VCDS’s on CDE110s
HTTPS
VCPT on CDE110
VCDS
HTTPS SDP “push”
An alterative VQE-C Configuration Delivery Server to the VCDS can be used to deploy network and channel information to the access network. The service-provider may have a multicast-based STB file delivery solution already be in place. The VCPT can send channel information to a remote server, once the service-provider defines the remote server in the VCPT by providing the following information:
• Management IP address of the remote server.
•
•
Transfer port number to use.
Full path and filename of the configuration file on the remote server.
• Name of the person with the authority to access this path.
The remote server is treated as another server role, with channels being associated with the remote server. The VCPT pushes a channel configuration to the remote server using the password-less secure copy protocol (SCP). From the remote server, you can distribute network and channel configuration data to STBs by integrating your deployment with customized middleware from a third-party vendor.
VCDS
The VCDS is a software component on the VQE Tools server that can be used to deliver the channel configuration file to the VQE-Cs on the STBs, and per-client network configuration files to the VQE-Cs on the STBs. This VCDS function is explained in the following section:
•
•
VCDS Delivery of the Channel Configuration File, page 1-17
VCDS Delivery of the Per-Client Network Configuration File, page 1-18
VCDS Delivery of the Channel Configuration File
When the VCDS receives information on the channel lineup from the VCPT, the VCDS creates a channel configuration file and stores it on the local disk. Each VQE-C running in a CPE device, such as a STB, uses a Real Time Streaming Protocol (RTSP) pull operation to receive the channel configuration file from the VCDS. The VCDS is a simplified RTSP server that supports the VQE-C RTSP pull operation.
The VQE-C learns the name of the VCDS through a Domain Name System (DNS) server using a SRV lookup.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-17
VCDS
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
After the VQE-C learns the VCDS name, it sends out an RTSP DESCRIBE request asking for the change status of the channel configuration. If there is new information on channels, the VQE-C asks the VCDS to send the channel configuration file. In response, the VCDS sends the channel configuration file for
the entire channel set in SDP format. Figure 1-8
shows the interaction between a VCDS and the VQE-Cs on the subscriber STBs.
For information on the interactions between the VCDS and the other components in the channel delivery infrastructure, see
Appendix E, “Configuring DHCP and DNS Servers for VCDS.”
Figure 1-8
VCDS on CDE110
VQE-C on STB: Receiving Channel Information File from VCDS
RTSP
SDP “pull”
Set-top boxes
The VQE-C requests the channel configuration file from the VCDS when the STB is started and the
VQE-C is initialized. After the initialization, the VQE-C can receive an updated channel configuration file by the following mechanisms:
• Periodic polls—VQE-C periodically polls the VCDS to determine whether a new channel configuration file is available. If a new version of the channel configuration file is detected during a poll, the VQE-C requests the updated channel configuration file.
• Triggered polls—When the STB attempts to tune to a channel that is not present in the VQE-C channel lineup, the VQE-C attempts to retrieve a new channel configuration file from the VCDS. As it does in a periodic-poll update, the VQE-C first determines whether an updated version of the file is available. If so, the VQE-C requests the updated channel configuration file.
With both periodic polls and triggered polls, the VQE-C uses the new channel configuration file to update the channel lineup that is in use and writes the channel configuration to the file specified in the
VQE-C channel-lineup system configuration.
VCDS Delivery of the Per-Client Network Configuration File
The VCDS can provide customized per-client network configuration to the VQE-C on the STB after the
VQE-C has been initialized. The VQE-C network configuration might, for example, specify whether
RCC or Forward Error Correction is enabled on the VQE-C, or specify some configuration parameters for the VQE-C.
Updates to the VQE-C network configuration occur because of periodic polls. The VQE-C polls the
VCDS to check whether the VQE-C network configuration file has been updated. If a new network configuration file is detected during a poll, the VQE-C requests the file from VCDS and overwrites the network configuration file it has stored in flash memory. The new network configuration does not apply until the next STB reboot.
1-18
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VCDS
The three major components involved in the delivery of per-client network configuration are the VQE-C system configuration provisioning server, the VCDS, and the VQE-C on the STB.
shows the interactions between these components. A simplified description of these interactions is as follows:
•
•
VQE-C system configuration provisioning server sends or pushes the client database file and group attribute file to the VCDSs.
In response to a request from the VQE-C on the STB, the VCDS sends the updated per-client network configuration file to the VQE-C.
• VQE-C receives the updated network configuration file, merges the attributes into its running configuration, and initializes the system using the merged running configuration on the next reboot.
Figure 1-9 Major Components for Delivering the Per-Client Network Configuration File
VCDS’s on CDE110s
VQE Clients on STBs
VQE-C System
Configuration
Provisioning Server
HTTPS
RTSP
Network configuration “pull”
The following sections provide information on the role of the major components used to deliver the per-client network configuration file for VQE-C system configuration:
•
VQE-C System Configuration Provisioning Server Role, page 1-20
•
•
For information on the interactions between the VCDS and the other components in the VQE configuration delivery infrastructure, see
Appendix E, “Configuring DHCP and DNS Servers for
An alternative to VCDS and CDI may be required for deploying configuration to the access network if the service provider already has a solution in place for multicasting network and channel configuration files to the access network or if the service provider wishes to unicast per-subscriber configuration changes to STBs.
The delivery of the network and channel configuration files may be handled externally to the VQE-C on the STB. The VQE-C provides a set of APIs to receive per-client network configuration data, channel configuration data, and per-subscriber configuration data (that is, an override configuration) from an external client. Deploying network, channel and override configurations to the VQE-C without using
VCDS and CDI requires integrating the Cisco’s VQE solution with customized middleware from a third-party vendor.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-19
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VCDS
VQE-C System Configuration Provisioning Server Role
The VQE-C system configuration provisioning server sends or pushes the client database file and group attribute file to one or more VCDSs using HTTPS. The service provider can provide a VQE-C system configuration provisioning server that meets the specific requirements of the deployment.
As an alternative to a VQE-C system configuration provisioning server, the VQE Tools software includes the vcds_send_file command that can be used to send the client database file and group attribute file to a VCDS. For information on this command, see
Appendix F, “Using the vcds_send_file Command.”
The VQE-C system configuration provisioning server has a different role than the channel-provisioning server (for example VCPT or ISDS). The VQE-C system configuration provisioning server delivers the following files to the VCDSs:
• Client database file—In this file, each STB VQE-C has a unique identity (for example, MAC address) that is associated with a group identifier (group ID) for the specific network configuration that should be applied to the VQE-C system. Each VQE-C is associated with one group ID. The client database file can be a complete set or superset of all STBs or a subset which adds to or modifies a previous set that exists on the VCDS.
• Group attribute file—In this file, different sets of per-client network configurations are defined.
Each set of attributes is identified by a group ID.
The client database file and the group attribute file are XML-based and follow a schema specified by a specification defined by Cisco. On a VQE Tools server, the XML schema and examples of the two files are included with the software. See
Appendix F, “Using the vcds_send_file Command” for the locations
of the files on a VQE Tools server.
For information on getting specifications for the client database file, group attribute file, and the VQE-C system configuration provisioning server, contact your Cisco account representative.
VCDS Role
When the VQE-C system configuration provisioning server sends or pushes the client database file and the group attribute file to one or more VCDSs, each VCDS does the following:
• Accepts a push of the client database file and the group attribute file from the VQE-C system configuration provisioning server
•
•
•
Parses the files for validity
Updates its local copies of the client database file and group attribute file
Services VQE-C requests for an updated per-client network configuration file
VQE-C Role
To obtain and process the per-client network configuration file, the VQE-C on the STB performs the following tasks:
•
•
By a periodic poll, determines whether an updated network configuration file is available
Retrieves the updated network configuration file from the VCDS
•
•
•
Writes the updated network configuration file to local flash memory
Derives a running configuration in memory by merging its existing network configuration file using the attributes in the updated network configuration file
On the next STB reboot, initializes the VQE-C network configuration using the merged running configuration
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-20 OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE-S AMT
For more information on VQE-C’s use of a per-client network configuration file, see Cisco CDA Visual
Quality Experience Client System Configuration Guide.
VQE-S AMT
The VQE-S AMT is a browser-based GUI that allows the service-provider operator to do the following:
•
•
•
•
•
Monitor the health of the VQE-S processes
View channel configuration details, status, and statistics
Monitor statistics for Unicast Retransmission and RCC
Monitor statistics for STUN Server usage
View configuration details, status, and statistics for:
– Multicast Load Balancer
•
– VQE-S RTCP Exporter
Change VQE-S logging levels and debugging options
The next paragraphs provide a few examples of VQE-S AMT functionality.
When you log in to VQE-S AMT, the initial window (see
) shows the health of VQE-S processes and other status information.
Figure 1-10 Monitoring VQE-S Processes
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-21
VQE-S AMT
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
With VQE-S AMT, you can view the channel lineup that was sent from the VCPT.
partial example of the channel lineup with usage statistics that VQE-S AMT displays.
Figure 1-11 Viewing Channel Lineups with Usage Statistics
In
, the channel-lineup summary data indicates when the lineup was last updated (for example, with the VCPT) and provides totals for all channels and active channels as well as aggregated bandwidth and total receivers:
Last update: 2008-07-08T14:44:14, Total Channels: 250, Active Channels: 240
Aggregated Bandwidth: 1215000 (kbits/sec), Total Receivers: 1040
In the channel-lineup summary data, the rightmost column, Member Receiver Population, is the number of VQE-Cs that are currently receiving this multicast stream.
The VQE-S AMT uses the Unicast Retransmission and RCC counters kept by the VQE-S to display a variety of data. For Unicast Retransmissions, the counters include non-acknowledgement (NACK) messages received from VQE-Cs, RTP packets requested and sent, error repair rates, and requests exceeding Unicast Retransmission capacity limits. For RCC, the counters include the number of RCCs requested, accepted, and refused, as well as the number of requests exceeding RCC capacity limits.
The Cisco VQE-S AMT provides limited configuration capabilities. The items that can be configured with the VQE-S AMT include parameters for the following:
• Logging priority level for the VQE-S processes
• Debugging options for the VQE-S-related functions, including RTP/RTCP packets, events, and errors
These configuration changes are temporary in nature, and only remain in effect until the VQE-S restarts.
In addition, the VQE-S AMT allows you to reset a subset of VQE-S counters to zero and subsequently, to restore these counters to their true values.
The VQE-S channel lineup is stored locally on the Cisco CDE appliance. If the VQE-S is restarted, the channel lineup is read from the local repository. The VQE-S counters for statistics that the VQE-S AMT displays are reset to zero when the VQE-S is restarted.
The VQE-S AMT is a web application that uses the application server and web server that are preinstalled on the Cisco CDE where the VQE-S runs. The VQE-S AMT has an XML-RPC client that communicates with multiple internal applications, such as VQE-S processes, to send and receive application management data.
1-22
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
VQE-S RTCP Exporter for Video-Quality Monitoring
VQE-S RTCP Exporter for Video-Quality Monitoring
The VQE-S provides a variety of data for monitoring IPTV packet delivery and for isolating faults. The
VQE-S receives RTCP reports from the VQE-Cs on the CPE devices and from reports generated by the
VQE-S itself. In those reports, the VQE-Cs provide statistics for RTP packet loss, jitter, delay, UDP packet loss, and other quality measurements. The VQE-Cs also provide statistics on Unicast
Retransmission.
For the RTCP reports, each VQE-C periodically sends RTCP compound packets to its target VQE-S.
Each compound packet contains an RR, an SDES, PUBPORTs, if present, and a generic RTP feedback
NACK, if present. The VQE-C sends additional RTCP reports every time a Unicast Retransmission request is made. Starting with Cisco VQE Release 3.5.5, the service provider may omit RRs from the
RTCP NACK compound packet for each channel using the VCPT. In addition to the RTCP compound packet, each VQE-C may transmit pre- and post-repair RTCP XR reports to its target VQE-S if the option to enable XR reports is enabled for each channel using the VCPT.
The service provider can use VQE-S RTCP Exporter to export the RTCP compound packets and the XR reports to a video-quality monitoring (VQM) application. Starting with Cisco VQE Release 3.5.5, the service provider can exclude RTCP NACK compound packets from being exported to the VQM application by setting the VCDB parameter vqe.vqes.exporter_filter_nack to TRUE. The VQM application collects the exported data in a database for use in video-quality analysis.
Starting with Cisco VQE Release 3.7, VQE-S RTCP Exporter supports exporting of VQE reports to maximum of two VQMs at a time.The video-quality monitoring application is outside the scope of the
VQE solution. The VQE documentation set includes detailed information on the data collected and the formats used in the RTCP reports.
The VQE-S RTCP Exporter is responsible for sending the RTCP compound packets to an external device, which typically hosts the video-quality monitoring application. The compound packets are sent over a TCP socket to a configurable location. The monitoring application is identified by IP address or
Internet domain name and a TCP port number.
The data in the RTCP compound packets are very useful for determining the quality of video service and for isolating faults. The data help the service provider to measure, baseline, and pinpoint problem areas of the video infrastructure, including transmission lines and home networks. The granularity of the data is per STB. The data could be stored in a database and searched for answers to questions of interest, such as whether packet loss and jitter events have occurred in the network and, if so, where and when the events have occurred.
On the VQE-S, RTCP Extended Reports and the Extended Report (XR) packet type are supported. The following XR report block types are supported:
• Loss RLE (run-length encoded)
•
•
•
•
Statistics Summary
Post-Repair Loss RLE
Multicast Acquisition
Diagnostic Counters (available in Cisco VQE Release 3.5.5 and later releases)
Extended Reports provide information that supplements the statistics contained in the report blocks used by the RTCP sender and receiver reports. For example, the Loss RLE report block type provides much more detailed reporting on individual packets and loss events than is provided in standard RTCP reports.
The VCPT allows the service provider to specify whether or not RTCP Extended Reports are used for each channel.
The following documents, which are available from http://www.faqs.org/faqs/ , provide more information on RTCP reports:
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-23
VCDS AMT
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
• RTCP reports are described in RFC 3550.
• RTCP Extended Reports are described in RFC 3611.
The Post-Repair Loss RLE report block type contains information on individual packet receipt and loss events, after packet recovery techniques (Unicast Retransmission or FEC or both) have been applied. For more information, see Post-Repair Loss RLE Report Block Type for RTCP XR at: http://tools.ietf.org/html/draft-begen-avt-post-repair-rtcp-xr-01
The Multicast Acquisition report block type is also capable of supporting information on the total channel change time, the expected RCC presentation timestamp and the actual RCC presentation timestamp. The availability of this timing information is dependent on the specific VQE-C platform integration. For more information, see Multicast Acquisition Report Block Type for RTCP XR at: http://tools.ietf.org/id/draft-begen-avt-rapid-sync-rtcp-xr-01.txt
Starting with Cisco VQE Release 3.5.5, the Diagnostic Counters XR report block type contains information on cumulative overruns and underruns, post-repair loss events, late packet drops, and output queue drops per channel.
VCDS AMT
The VCDS AMT is a browser-based GUI that allows the service-provider operator to do the following:
•
•
Monitor the health of the VCDS process and the VQE Tools Server
View configuration details and statistics for the VCDS
• Configure VCDS logging levels and debugging options
The next paragraphs provide a few examples of the VCDS AMT functionality.
When you log into VCDS AMT, the initial window (see
) shows the health of the VCDS process, the VQE Tools server, and other status information.
Figure 1-12 VCDS Status Information
The VCDS AMT displays status and configuration on the VCDS configuration, and on the VQE-C
channel configuration, the client database, and the group attribute files (see Figure 1-13
).
1-24
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
Figure 1-13 VCDS Configuration Window
PSTN
VCDS AMT
US1
Cisco Unified
MeetingPlace
Application Server
US2
Cisco Unified
MeetingPlac
Application S
OL-30119-01
Cisco IOS
Voice Gateway
The VCDS AMT displays configuration and status information for the channel configuration, the client database, and the group attribute files. For the channel configuration file, the VCDS AMT indicates whether the file contents are valid. It displays the full pathname of the file, the number of channels contained in the channel lineup and the timestamp of the last modification to the file. For the client database file, the VCDS AMT indicates whether the file contents are valid. It displays the full pathname of the file, the number of CNames (VQE-C unique identifier) in the file and the timestamp of the last modification to the file. For the group attribute file, the VCDS AMT indicates whether the file contents are valid. It displays the full pathname of the file, the number of attribute groups in the file and the timestamp of the last modification to the file.
The VCDS AMT provides limited configuration capabilities. The items that can be configured with the
VCDS AMT include parameters for the following:
•
•
Logging priority level for VCDS processes
Debugging options for VCDS-related functions
The VCDS AMT is a web application that uses the application server and web server that are preinstalled on the Cisco CDE where the VCDS runs. The VCDS AMT has an XML-RPC client that communicates with multiple internal applications, such as VCDS processes, to send and receive application management data.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-25
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
Content Delivery Engine 110
Content Delivery Engine 110
The VQE-S can run on one Cisco Content Delivery Engine 110 (CDE110). If the VCPT and the VCDS are used, another Cisco CDE110 hosts these two facilities. The Cisco CDE110, show in
comes with the Red Hat Enterprise Linux Release 5.1 operating system and either the VQE-S or the
VCPT and the VCDS software preinstalled.
Figure 1-14 Content Delivery Engine 110
Cisco
CDE110
Note The descriptions of hardware given in the following paragraphs are for the latest CDE110 models
(CDE111-2-146TXA-K9 and CDE111-2-146TXD-K9). For complete information on all CDE110 models, see the Cisco Content Delivery Engine 110 Hardware Installation Guide.
The Cisco CDE110 appliance is a NEBS-3 and ETSI-compliant carrier-grade rack server. It is powered by two 64-bit Quad-Core Intel Xeon L5410 processors with 12 MB of shared Layer 2 cache. For maximized bandwidth, it contains 8 GB of dual-channel Fully Buffered DIMM (FB-DIMM) memory at
667 MHz. For storage, the Cisco CDE110 has one 36-GB simple-swap, serial attached SCSI (SAS) hard disk drive. The optical drive is a CD/DVD RW combination drive.
The Cisco CDE110 has six 10/100/1000 Mb Ethernet ports and a serial port for the system console.
Earlier CDE110 models have four 10/100/1000 Mb Ethernet ports. The Ethernet ports can be load-balanced for incoming multicast IPTV streams and for outgoing Unicast Retransmission and RCC streams to the VQE-Cs.
Note The VQE-S supports Gigabit Ethernet (that is, 1000 Mb Ethernet) interfaces only.
1-26
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
Content Delivery Engine 250
The Cisco CDE110 has a 1-RU form factor and is available with redundant AC or DC hot-swappable power supplies. The Cisco CDE110 Telco Alarm Management features provide visual, audible (optional), and SNMP event indications of faults, consistent with the rigid requirements of the telecom central office environment.
Content Delivery Engine 250
The VQE-S can run on one Cisco Content Delivery Engine 250 (CDE250). If the VCPT and the VCDS are used, another Cisco CDE 250 hosts these two facilities. The Cisco CDE250, show in
comes with the Red Hat Enterprise Linux Release 5.1 operating system and either the VQE-S or the
VCPT and the VCDS software preinstalled.
Figure 1-15 Content Delivery Engine 250
OL-30119-01
Note The descriptions of hardware given in the following paragraphs are for the latest CDE250 model
(CDE250-K9, CB-48-XVR-2WPL-SB-1F200). For complete information on all CDE250 models, see the Cisco Content Delivery Engine 205/220/250/420 Hardware Installation Guide.
The Cisco CDE250 appliance is a NEBS-3 and ETSI-compliant carrier-grade rack server. It is powered by two Quad Core Intel Xeon (Westmere) CPUs @ 2.4GHz with 48 MB of shared Layer 2 cache. For maximized bandwidth, it contains two Dual (10GE) Ports, Copper or Fiber by removable SFP Module and one Quad (4GE) Copper Port. For storage, the Cisco CDE250 has one 200GB Solid State Drive
(SSD) hard disk drive. The optical drive is a CD/DVD RW combination drive.
The Cisco CDE250 has six 10/100/1000 Mb Ethernet ports and a serial port for the system console.
Earlier CDE250 models have four 10/100/1000 Mb Ethernet ports. The Ethernet ports can be load-balanced for incoming multicast IPTV streams and for outgoing Unicast Retransmission and RCC streams to the VQE-Cs.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
1-27
Content Delivery Engine 250
Chapter 1 Introduction to Cisco CDA Visual Quality Experience Application
Note The VQE-S supports Gigabit Ethernet (that is, 1000 Mb Ethernet) interfaces only.
The Cisco CDE250 has a 2-RU form factor and is available with redundant AC or DC hot-swappable power supplies. The Cisco CDE250 Telco Alarm Management features provide visual, audible (optional), and SNMP event indications of faults, consistent with the rigid requirements of the telecom central office environment.
1-28
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Initial VQE Configuration
C H A P T E R
2
OL-30119-01
This chapter explains the initial configuration tasks needed to get the two categories of Cisco CDE servers running with the Cisco VQE software:
• VQE server (VQE-S)—CDE hosting VQE-S
• VQE Tools server—CDE hosting the VQE Channel Provisioning Tool (VCPT) and the VQE Client
Configuration Delivery Server (VCDS)
In a VQE deployment, use of the VQE Tools server with the VCPT and the VCDS is optional.
For information on installing or upgrading VQE software, see Release Notes for Cisco CDA Visual
Quality Experience Application 3.7.
Note We recommend that you use the VQE Configuration Tool rather than try to do the initial configuration manually because the tool simplifies your work and is known to produce correct results.
For information on the manual initial VQE configuration tasks, see
Appendix D, “Manual Initial VQE
Read the following sections for information on CDE configuration configuring a CDE:
•
Web Browser, Screen Resolution, and Other Requirements, page 2-2
•
•
•
•
•
•
•
•
•
•
•
•
•
Configuring Terminal Emulation Software, page 2-3
Security Restrictions for Logins and Root Privileges, page 2-4
Setting Up SSL Certificates, page 2-5
Configuring the Edge Router for VQE-S, page 2-46
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview, page 2-11
Using the VQE Configuration Tool, page 2-23
On the VQE-S Host: Verifying the Status of the VQE and System Services, page 2-39
Configuring the VQE-S RTCP Exporter, page 2-42
Configuring the Other Parameters for the VQE-S Host, page 2-46
On the VQE Tools Host: Verifying the Status of the VQE and System Services, page 2-41
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-1
Chapter 2 Initial VQE Configuration
Web Browser, Screen Resolution, and Other Requirements
Note The configuration instructions in this chapter are intended for new installations of Cisco VQE Software,
Release 3.7, where the Cisco CDE has the Cisco VQE Software, Release 3.7 preinstalled.
For information on upgrading a Cisco CDE, see Release Notes for Cisco CDA Visual Quality Experience
Application, Release 3.7.
This chapter assumes that the Cisco CDE hardware has been installed as described in Cisco Content
Delivery Engine 110 Hardware Installation Guide and the Cisco Content Delivery Engine
205/220/250/420 Hardware Installation Guide, including connecting cables and connecting power.
Web Browser, Screen Resolution, and Other Requirements
To access the VQE-S AMT, the VCDS AMT, or the VCPT, 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 the VQE-S AMT, the VCDS AMT, and the VCPT is
1024 x 768 pixels.
For the VQE-S AMT, Adobe Flash Player must be installed on the computer that hosts the browser accessing the VQE-S AMT. Adobe Flash Player is required to display the Channels Status Summary graph of active, inoperative, and inactive channels in the AMT VQE-S Status window. Adobe Flash
Player is free and can be found at this URL: http://get.adobe.com/flashplayer/
2-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
System Port Numbers
System Port Numbers
presents the TCP ports used by the VQE-S, and displays the user of each port.
Table 2-1 VQE-S System Ports
8009
8050
8051
8052
8053
8054
Port Number
21
22
161
162
443
444
8005
Menu Description
FTP
SSH
1
SNMP
2
SNMP traps
HTTPS
3
HTTPS push
Apache tomcat
Apache tomcat
VQE process monitor
VQE-S CP
4
XML-RPC
5
MLB
6
RPC
VCDS
STUN Server RPC
1.
SSH = Secure Shell.
2.
SNMP = Simple Network Management Protocol.
3.
HTTP = Hypertext Transfer Protocol Secure.
4.
CP = control plane.
5.
XML-RPC = XML remote procedure call.
6. MLB = multicast load balancer.
Ports 8005, 8009, 8050, 8051, 8052, 8053, and 8054 are not open for external use. All other ports listed in
Table 2-1 are only accessible from a management interface. For information on management
interfaces, see the
“Interface for a Management Network” section on page 2-18
.
Configuring Terminal Emulation Software
The RJ-45 serial ports on the Cisco CDE front and back panels can be used for administrative access to the CDE through a terminal server. Terminal emulation software must be configured as follows:
• Bits per second—9600
•
•
•
•
Data bits—8
Parity—none
Stop bits—1
Hardware flow control—ON
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-3
Chapter 2 Initial VQE Configuration
Security Restrictions for Logins and Root Privileges
Security Restrictions for Logins and Root Privileges
For security reasons, the following restrictions apply to VQE:
• SSH is used to log in to the CDE that hosts the VQE-S and VQE Tools server. However, a root user cannot use SSH to log in to a CDE, VQE-S AMT, VCDS AMT, or VCPT. The vqe username should be used instead. The vqe username is a precreated Linux user ID, and has its password set during the CDE initial system configuration.
• Only users in the wheel group can use the su or sudo commands. By default, the vqe username is in the wheel group.
If you want to add user accounts to the wheel group so that additional users can use su and sudo, log in as root and issue the following command:
[root@system]# usermod -G wheel username
In the preceding command syntax, username specifies the user who is added to the wheel group.
Prerequisites
Before you start the initial VQE software configuration, the following items should be accomplished for the CDE that hosts the VQE-S and the CDE that hosts the VQE Tools:
•
Connect cables to the CDE—See the “Connecting Cables to the CDE” section on page 2-4
.
• Determine how you will set up Secure Sockets Layer (SSL) certificates—For information on the alternatives available to you, see the
“Setting Up SSL Certificates” section on page 2-5
.
Connecting Cables to the CDE
The following cable connections are used on the Cisco CDE that hosts the VQE-S and on the CDE that hosts the VQE Tools:
• Depending on whether the host is for the VQE-S or the VQE Tools, do one of the following:
Note Earlier models of the CDE have four Ethernet ports. The latest models of the CDE include the Intel
PRO/1000 PT Dual Port Server Adapter that provides two additional Ethernet ports.
–
–
On a VQE-S, use Category 5 UTP (Unshielded Twisted Pair) cables to connect up to six
Ethernet interfaces on the back of the Cisco CDE to Ethernet interfaces on the edge router that is providing multicast streams for each IPTV channel. Use Gigabit Ethernet (1000 Mb Ethernet) interfaces only. For optimal VQE-S performance, all Ethernet interfaces on the Cisco CDE should have a direct Layer 3 connection to the edge router. For OSPF routing on the VQE-S, the
Ethernet interfaces used for VQE-S traffic must have a direct Layer 3 connection to the edge router.
On a VQE Tools server, use Category 5 UTP cable to connect at least one of the Ethernet interfaces on the back of the CDE to the same network that the CDEs that host the VQE-S are on. It is recommended that you use Gigabit Ethernet interfaces. If you use additional Ethernet interfaces for link redundancy, connect Category 5 UTP cables for those interfaces also.
2-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Setting Up SSL Certificates
•
•
If a terminal server is used, the RJ-45 cable from the terminal server is connected to an RJ-45 serial port on the front or back of the Cisco CDE. Only one serial port can be used because it is one shared serial port.
If a PC is directly connected to the CDE serial port, the cable from the PC is connected to an RJ-45 serial port on the front or back of the Cisco CDE. Only one serial port (front or back) can be used because it is one shared serial port. The PC end of the cable connected to the CDE serial port varies depending on the type of ports supported by the PC.
Note The serial port is used for the system console. A system console is typically used rather than a monitor, keyboard, and mouse directly attached to the Cisco CDE.
• If a monitor, keyboard, and mouse are used, the cables for the devices are connected to the appropriate connectors on the Cisco CDE.
For the location of connectors on the Cisco CDE front and back panels, see Cisco Content Delivery
Engine 110 Hardware Installation Guide and the Cisco Content Delivery Engine 205/220/250/420
Hardware Installation Guide.
Setting Up SSL Certificates
SSL is used on the CDEs hosting the VQE-S and the VQE Tools server to create secure communication channels using Triple Data Encryption Standard (3DES) between web browsers and the VQE-S
Application Monitoring Tool (AMT), the VCDS AMT, and the VCPT. SSL is also used by the VCPT when providing channel information to the VQE-S and the VCDS.
The HTTP server on the VQE-S and the VQE Tools server is not usable until the SSL certificates and other required SSL files are created and deployed. The VQE-S AMT, the VCDS AMT, and the VCPT require SSL certificates from a certificate authority (CA) to be created and deployed. The CA can be you or someone in your company, or a commercial CA, such as VeriSign. The procedures to create and deploy certificates are explained in the following sections:
•
Using the Cisco VQE Configuration Tool for SSL Certificates, page 2-6
•
•
•
Creating Your Own Certificate Authority, page 2-6
Generating and Deploying Your Own SSL Certificates, page 2-7
Deploying Commercial SSL Certificates, page 2-10
You perform the procedures for deploying CA certificates on the VQE-S hosts and the VQE Tools hosts.
As an alternative if you are setting up the certificates manually, you can create the needed files on one host and copy them to the other hosts.
The Open Source toolkit from the OpenSSL Project collaborative is used to generate, sign, and install your own CA certificates and to generate the Certificate-Signing Request for commercial certificates.
The Open Source toolkit is installed on the VQE-S and the VQE Tools hosts. For more information on the Open Source toolkit and for documentation on toolkit commands, go to the following URL: http://www.openssl.org
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-5
Chapter 2 Initial VQE Configuration
Setting Up SSL Certificates
Using the Cisco VQE Configuration Tool for SSL Certificates
To manually create and deploy SSL certificates, follow the directions provided in these sections:
– For overview information of the SSL tasks, see the
“Setting Up SSL Certificates” section on page 5 .
–
–
For deploying your own SSL certificates, see the
“Creating Your Own Certificate Authority” section on page 6
and the
“Generating and Deploying Your Own SSL Certificates” section on page 7 .
Creating Your Own Certificate Authority
Note This task is not needed if you are using certificates that are signed by a commercial CA.
This task to create your own certificate authority (CA) is only performed once for all instances of the
VQE-S and the VCPT. The CA that you create can be used to sign server certificates on all CDE servers hosting the VQE-S or the VQE Tools.
To create a CA certificate, perform the following steps:
Step 1 Log in using a valid Linux username and password.
Note When generating an encrypted RSA private key, a pass phrase requirement can be added by including the -des3 option. The pass phrase is needed every time this CA signs a certificate request.
Step 2
Step 3
To generate an encrypted RSA private key, issue the following command:
$ openssl genrsa -out ca.key 4096
The openssl genrsa command saves the ca.key file in your current working directory.
The generated key is a 4096-bit RSA key, which is encrypted using Triple-DES and stored in PEM format so that it is readable as ASCII text.
To generate the CA certificate, issue the following command:
$ openssl req -new -x509 -days 3650 -key ca.key -out ca.crt
Note The –days option specifies the number of days to certify the certificate for. Set this value so that it meets the requirements of your deployment. The value 3650 (specified in the preceding command) may be too many or too few days for some deployments.
The command prompts for the following X.509 attributes of the certificate. It is recommended that you provide valid input for X.509 information. Use a period (.) to indicate blank input.
• Country Name—Country where your company resides. Use the two-letter country code without punctuation for country (for example, US or FR).
2-6
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Setting Up SSL Certificates
•
•
•
State or Province—State or province where your company resides. Spell out the state completely
(for example, California). Do not abbreviate the state or province name.
Locality or City—City or town where your company resides (for example, Berkeley).
Company—Your company’s name (for example, XYZ Corporation). If your company or department name has an &, @, or any other symbol that requires using the Shift key in its name, you must spell out the symbol or omit it to enroll.
•
•
Organizational Unit—Organization within the company. This field is optional but can be used to help identify certificates registered to an organization. The Organizational Unit (OU) field is the name of the department or organization unit making the request. To skip the OU field, press Enter.
Common Name—Common Name is the host plus the domain name (for example, www.company.com or company.com).
The openssl req command saves the ca.crt file in your current working directory.
Generating and Deploying Your Own SSL Certificates
When you act as your own certificate authority, you can sign multiple Certificate-Signing Requests for the VQE-S hosts and the VCPT hosts. Generating and deploying your own SSL certificates involves three tasks:
1.
2.
Generate a Certificate-Signing Request.
Sign the Certificate-Signing Request.
3.
Install the certificates, private key, and keystore.
These tasks are explained in the following three sections. We recommend that these tasks be repeated for each CDE host so that there is a unique set of files generated for each host. You can create the needed sets of files on one host and copy them to the other hosts.
Generating a Certificate-Signing Request
To generate a Certificate-Signing Request, perform the following steps:
Note When generating a private key, a pass phrase requirement can be added by including the -des3 option.
However, adding a pass phrase requirement is not recommended as it requires human intervention. On every service or system restart someone must manually enter the pass phrase.
Step 1 To generate a server private key, enter the following command:
$ openssl genrsa -out server.key 1024
The openssl genrsa command saves the server.key file in your current working directory.
Note We recommend that access to the Cisco CDE host be restricted so that only authorized server administrators can access or read the private key file.
Step 2 To generate a Certificate-Signing Request, enter the following command:
$ openssl req -new -key server.key -out server.csr
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 2-7
Chapter 2 Initial VQE Configuration
Setting Up SSL Certificates
The command prompts for the same X.509 attributes that were specified when you created your CA certificate in the
“Creating Your Own Certificate Authority” section on page 6
. It is recommended that you provide valid input for X.509 information. Use a period (.) to indicate blank input.
Note The Common Name (CN) of the CA and the server certificates should not match or else a naming collision occurs and you get errors when the certificates are used.
The openssl req command saves the server.csr file in your current working directory.
The command creates a public/private key pair. The private key (server.key) is stored locally on the server machine and is used for decryption. The public portion, in the form of a Certificate-Signing
Request (server.csr), is used for certificate enrollment with the CA.
Tip If you are creating Certificate-Signing Requests for multiple VQE-S or VCPT hosts and want to reuse most of the X.509 attributes, you can save the information to a file (openssl.cnf) and pass the information to the openssl req command by specifying -config openssl.cnf on the command line.
Signing the Certificate-Signing Request
The Certificate-Signing Request can be signed by commercial CA entities, such as VeriSign, or by your own CA, as described in the
“Creating Your Own Certificate Authority” section on page 6 .
Note If you use a self-created (non-commercial) CA, signing the Certificate-Signing Request must be done on the same CDE server where the CA was created.
We recommend that the system time of each CDE be synchronized with Network Time Protocol (NTP).
The system time when the signing of the Certificate-Signing Request occurs must be later than the system time when the CA was created.
To sign the Certificate-Signing Request with the self-created certificate authority, enter the following command:
$ openssl x509 -req -days 3650 -in server.csr -CA ca.crt -CAkey ca.key -set_serial 01 -out server.crt
Note The –days option specifies the number of days to make the certificate valid for. The start date is set to the current time and the end date is set to the value specified in the -days option. Set this value so that it meets the requirements of your deployment. The value 3650 (specified in the preceding command)
may be too many or too few days for some deployments.
The openssl x509 command saves server.crt in your current working directory.
In the example above, the serial number of the signed server certificate is set to 01. Each time you execute this command, you must change the serial number, especially if you sign another certificate before a previously-signed certificate is expired.
2-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Setting Up SSL Certificates
Installing the Certificates, Private Key, and Keystore
The certificate needs to be in a certain format and reside in a designated directory to be used by the
VQE-S-related or the VCPT-related software.
To install the server and CA certificates, the private key and the keystore, perform the following steps:
Step 1 To create a stacked PEM file, concatenate the contents of the server certificate file (server.crt) and all
CA certificate files (ca.crt) in the CA chain to a file named stackedChain.pem. The safest way to create the stackedChain.pem file is to use the Linux cat command. For example:
$ cat server.crt ca.crt > stackedChain.pem
Note Using a text editor and a cut-and-paste operation to concatenate the server and CA certificates can produce unusable results because the text editor may add extraneous characters.
The stackedChain.pem file content must be in this order:
-----BEGIN CERTIFICATE-----
<SSL Server Cert Contents>
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
<CA Cert Contents>
-----END CERTIFICATE-----
The following example shows the stackedChain.pem file:
-----BEGIN CERTIFICATE-----
MIIDvjCCAaYCAQEwDQYJKoZIhvcNAQEFBQAwZTELMAkGA1UEBhMCVVMxDTALBgNV
... Omitted contents ...
/kzgDk5wO1CbTwuxPIY1piy0Os1Q5EWk3VVAmv4tNMT9bANeKDUiVyYyOi1NIiHA
36w=
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIGGDCCBACgAwIBAgIJAPtvlrCRokk4MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNV
... Omitted contents ...
KV+sxNECGE40iWIvd1dXDA1O34qhAwkVD6/bxw==
-----END CERTIFICATE-----
Note If you are creating stackedChain.pem files for multiple VQE-S or VCPT hosts, the server.crt file should be different for each host.
Step 2
Step 3
For a VCPT only, to create a trust-store file for the SSL Java client, enter the following command:
$ keytool -import -keystore trustedca - alias rootca -file ca.crt
The CA certificate (ca.crt) specified in the -file argument is the CA certificate that you created in the
“Creating Your Own Certificate Authority” section on page 6
.
The keytool command creates a new keystore with the CA certificate. The resulting file is named
trustedca.
Do one of the following:
• On a VQE-S host, copy the following files to the directory /etc/opt/certs:
– server.key
– stackedChain.pem
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-9
Chapter 2 Initial VQE Configuration
Setting Up SSL Certificates
• On a VCPT host, copy the following files to the directory /etc/opt/certs:
–
– server.key stackedChain.pem
– trustedca
Deploying Commercial SSL Certificates
As an alternative to acting as your own certificate authority (CA), commercial certificate authorities, such as VeriSign, can issue and sign Secure Sockets Layer (SSL) certificates.
Deploying a commercial certificate involves the following steps:
1.
Generate a Certificate-Signing Request. See the
“Generating a Certificate-Signing Request” section on page 7
.
2.
3.
Submit the Certificate-Signing Request to the commercial CA for signing.
Install the certificates, private key, and keystore. See the
“Commercial CA: Installing the
Certificates, Private Key, and Keystore” section on page 10
that follows.
Commercial CA: Installing the Certificates, Private Key, and Keystore
When you get the signed certificates back from the commercial CA, you need to install them and the private key and keystore.
To install the certificates, private key, and keystore, follow these steps:
Step 1 To create a stacked PEM file, concatenate the contents of the server certificate file (server.crt) and all
CA certificate files (ca.crt) in the CA chain to a file named stackedChain.pem. The safest way to create the stackedChain.pem file is to use the Linux cat command. For example:
$ cat server.crt ca.crt > stackedChain.pem
Note Using a text editor and a cut-and-paste operation to concatenate the server and CA certificates can produce unusable results because the text editor may add extraneous characters.
The stackedChain.pem file content must be in this order:
-----BEGIN CERTIFICATE-----
<SSL Server Cert Contents>
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
<CA Cert Contents>
-----END CERTIFICATE-----
The following example shows the stackedChain.pem file:
-----BEGIN CERTIFICATE-----
MIIDvjCCAaYCAQEwDQYJKoZIhvcNAQEFBQAwZTELMAkGA1UEBhMCVVMxDTALBgNV
... Omitted contents ...
/kzgDk5wO1CbTwuxPIY1piy0Os1Q5EWk3VVAmv4tNMT9bANeKDUiVyYyOi1NIiHA
36w=
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
2-10
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
MIIGGDCCBACgAwIBAgIJAPtvlrCRokk4MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNV
... Omitted contents ...
KV+sxNECGE40iWIvd1dXDA1O34qhAwkVD6/bxw==
-----END CERTIFICATE-----
Note If you are creating stackedChain.pem files for multiple VQE-S or VCPT hosts, the server.crt file should be different for each host.
Step 2
Step 3
For the VCPT only, to create a trust-store file for the SSL Java client, enter the following command:
$ keytool -import -keystore trustedca -alias rootca -file ca.crt
The CA certificate (ca.crt) specified in the
-file
argument is the commercial CA certificate that you get from the vendor.
The keytool command creates a new keystore with the CA certificate. The resulting file is named trustedca.
Do one of the following:
• On a VQE-S host, copy the following files to the directory /etc/opt/certs:
•
– server.key
– stackedChain.pem
On a VCPT host, copy the following files to the directory /etc/opt/certs:
–
–
– server.key stackedChain.pem trustedca
VQE-S and VQE-Tools Server: Routing and Interface
Configuration Overview
For a VQE-S, configuring static routes, both static and dynamic routes, and Open Shortest Path First
(OSPF) routing is supported. This section provides overview information on how you can configure static routes and OSPF routing on a VQE-S. It introduces the concept of bond interfaces, which may be used for static and OSPF routing. It includes these topics:
•
•
•
•
•
Bond Interfaces on a VQE-S and VQE-Tools Server, page 2-12
Types of Routes on a VQE-Tools Server, page 2-13
Types of Routes on a VQE-S, page 2-13
Static Routes on a VQE-S, page 2-14
•
OSPF Routing on a VQE-S, page 2-14
•
•
Routing Configuration for Dedicated Interfaces and Shared Interfaces, page 2-16
Interface for a Management Network, page 2-18
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-11
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
•
Load Balancing and Redundancy with Multiple VQE-S, page 2-19
•
Configuring LACP Bonding on a VQE-S and VQE Tools Server, page 2-20
At initial system startup, the VQE Configuration Tool can be used to configure static routes and OSPF routing. After initial system startup, the VQE Configuration Tool can be used to modify the routing implementation.
Bond Interfaces on a VQE-S and VQE-Tools Server
Starting with Cisco VQE Release 3.7, support for bond interfaces is extended to VQE-Tools Server.
One or more bond interfaces may be configured on a CDE that hosts the VQE-S and VQE-Tools Server.
Two or more physical, Ethernet interfaces, may be combined into a single, logical bond interface, which has the combined capacity of the underlying Ethernet interfaces. For example, a bond interface that combines three 1 Gbps Ethernet interfaces has a capacity of 3 Gbps. All Ethernet interfaces that are members of a bond interface are active. In Linux, a bond interface is referred to as a master interface.
On Cisco routers, the terms EtherChannel and port-channel group are used to refer to a bond interface.
A bond interface must be configured on both the VQE-S/VQE-Tools Server and on the attached Edge router.
The use of a bond interface has the following benefits:
• Complexity of interface and routing configuration is reduced. An IP address and prefix length is assigned to the bond interface only. None of the underlying physical, Ethernet interfaces have an IP address and prefix length assigned.
• Feedback Target (FTB) routes are advertised on the bond interface and not on each of the underlying, physical interfaces, thereby reducing the number of Equal Cost Multi-Path (ECMP) advertisements per VQE-S.
Bond interfaces may be used for the following interfaces:
•
•
Bond interfaces may be used to support VQE-S traffic (ingest and services) in configurations where shared interfaces to the access and distribution networks are configured.
Bond interfaces may be used to support VQE-S ingest traffic in configurations where dedicated interfaces to the distribution network are configured.
•
•
Bond interfaces may be used to support VQE-S services traffic in configurations where dedicated interfaces to the access network are configured.
Bond interfaces may be used to support management traffic on a VQE-S. Management traffic may use a designated interface or may share interfaces used by other traffic types, including VQE-S traffic (ingest and services), VQE-S ingest traffic, or VQE-S services traffic. On a VQE-S, a combination of bond interfaces and Ethernet interfaces can be used for management traffic.
All members of a bond interface must have the same capacity. Ethernet interfaces that are members of a bond interface should not be assigned an IP address and prefix length nor should they be specified as an interface for VQE-S traffic (ingest and services), VQE-S ingest traffic, VQE-S services traffic, or VQE-S management traffic. The IP address and prefix length, and the interface role are assigned to the parent bond interface. An Ethernet interface may be a member of a one bond interface only.
Note For VQE-S traffic (ingest and services), VQE-S ingest traffic, VQE-S services traffic, multiple bond interfaces should not be used and a combination of bond interfaces and Ethernet interfaces can not be used because load balancing can not work effectively if there is no guarantee that each interface in the link has the same capacity.
2-12
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
Note The user cannot assign roles to bonds for VQE-Tools
Types of Routes on a VQE-Tools Server
On the VQE Tools server, the following routes are used:
•
•
Management route—Route on the VQE Tools server through an edge router to the management network.
External access—Proper route configuration is needed to provide external access to the VQE Tools server. This access allows VCDS to send channel and configuration information to the VQE-Cs on the STBs and for VCPT to send channel information to each VQE-S.
The VQE Tools server uses one or more static routes to the management network. The static route to the management network can also be used to provide the external access. The VQE Configuration Tool can be used to configure one or more static routes.
Types of Routes on a VQE-S
On the VQE-S, three types of routes are used:
•
•
Management routes—Static route on the VQE-S through a directly attached edge router to the management network.
Access routes—Routes on the VQE-S through a directly attached edge router to the access network, where the VQE Clients (VQE-Cs) on the set-top boxes (STBs) live.
• Feedback target routes—Routes on a directly attached edge router to the VQE-S that advertise reachability of the VQE-S feedback targets (FBTs) into the access network, where the STBs reside.
Each FBT is associated with a channel. VQE-Cs on the STBs send requests for Unicast
Retransmission and RCC services to the feedback target addresses. The VQE-S configures each channel FBT address as a host address on the VQE-S loopback interface.
The VQE-S also joins the multicast RTP streams from the distribution network. This interaction is between the VQE-S and the edge router. It takes place through the use of IGMP joins and does not involve routing with the local routing daemon on the VQE-S. This interaction is, in general, outside the scope of this discussion.
shows the types of routes used on a VQE-S.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-13
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
Figure 2-1 Routes Used on a VQE-S
Distribution network
Headend Management network
Feedback Target addresses /32 lo
VQE-S server eth1 to eth X
Edge router
To access network
STBs
Static Routes on a VQE-S
In Cisco VQE Release 3.1, OSPF routing was introduced on the VQE-S. Before this, the access routes and feedback target routes on a VQE-S were configured using static routes. Though static routes can still be chosen as the routing type, the use of static routes for the access routes and feedback target routes has some limitations.
For the access routes, use of static routes requires that the VQE-S be configured for the static routes to the access network. In contrast, with OSPF routing, the edge router advertises a default route to the access network through a routing protocol, allowing load balancing across the VQE-S interfaces and not requiring an extra configuration step.
For the feedback target routes, the use of static routes on the edge router means that repair services on the VQE-S for all feedback targets are assumed to always be available as long as the VQE-S interfaces are up. In some cases, although the interfaces are up, the VQE-S may not be able to handle requests for one or more feedback targets. The VQE-S itself can not add or withdraw the routes as services become available or unavailable for particular feedback targets. Another limitation of the use of static routes for feedback targets is that it requires the customer to take the extra step of configuring the edge router for feedback target addresses. In the worst case, this approach can require that each feedback target have a separate static route configured on the router if the feedback target addresses are not summarizable.
IP Address, Prefix Length, and Gateway Address” section on page 26
.
For information on static route configuration on the edge router, see the
OSPF Routing on a VQE-S
Starting with Release 3.1, Cisco VQE supports a dynamic routing feature, which uses OSPF routing to the access network from the VQE-S. The use of OSPF routing eliminates the limitations of static routing, see the
“Static Routes on a VQE-S” section on page 14 . Specifically, OSPF routing can be used on the
VQE-S for the following:
• To learn routes to the access network out the VQE-S interfaces to the edge router
2-14
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
• To advertise feedback target routes to the edge router and access network
Note If a bond interface is configured to support VQE-S traffic (ingest and services) or VQE-S services traffic and if OSPF routing is enabled, the corresponding edge router must support the configuration of
EtherChannels (that is, bond interfaces). Otherwise, the bond interface between the VQE-S and the edge router does not operate.
With dynamic routing, the feedback target routes can be advertised based on the actual capabilities of the VQE-S to process requests for services sent to those targets by adding and removing feedback target routes as needed.
On the VQE-S, the Quagga routing package provides the OSPF routing capability. The VQE
Configuration Tool simplify the OSPF configuration on the VQE-S. After you enter values for OSPF configuration parameters, such as the OSPF area and router ID, these tools perform the configuration tasks for you. For information on configuring OSPF parameters for a VQE-S, see the
Configuration (VQE-S Host Only)” section on page 28
.
For information on OSPF configuration on the edge router, see the
“For OSPF Routing: Guidance for
Configuring the Attached Router” section on page 48
.
Using Dedicated or Shared Interfaces for VQE-S Ingest Traffic and for VQE-S
Services Traffic
Some VQE deployments require that the CDE Ethernet interfaces or bond interfaces used for VQE-S ingest traffic (incoming multicast streams from the video sources) be separate from the interfaces used for VQE-S services traffic (Unicast Retransmission and RCC to the VQE-Cs on the STB). Dedicated
Ethernet interfaces or dedicated bond interfaces allow the video distribution network to be separate from the access network.
The service provider can choose one of the following approaches when configuring the CDE Ethernet or bond interfaces:
•
•
Dedicated Interfaces—If a VQE deployment requires that the interfaces used for VQE-S ingest traffic from upstream video sources be separate from the interfaces used for VQE-S services traffic to the downstream VQE-Cs on the STBs, the CDE Ethernet or bond interfaces must be configured as follows:
–
–
Either one or more Ethernet interfaces or one or more bond interfaces are configured as dedicated interfaces for VQE-S ingest traffic.
Either one or more Ethernet interfaces or one or more bond interfaces are configured as dedicated interfaces for VQE-S services traffic.
The VQE Configuration Tool allow you to configure dedicated CDE Ethernet interfaces or bond interfaces for VQE-S ingest traffic and for VQE-S services traffic.
Shared Interfaces—If a VQE deployment does not require that the Ethernet interfaces or bond interfaces used for VQE-S ingest traffic be separate from the interfaces used for VQE-S services traffic, a single set of CDE Ethernet interfaces are configured or one or more bond interfaces are configured as VQE-S traffic interfaces that handle both types of traffic. This combined traffic interface was the only configuration available before Cisco VQE Release 3.3.1. The VQE
Configuration Tool allow you to configure these shared VQE-S traffic interfaces.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-15
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
Note For VQE-S traffic (ingest and services), VQE-S ingest traffic, VQE-S services traffic, multiple bond interfaces should not be used because load balancing cannot work effectively if there is no guarantee that each interface in the link has the same capacity.
and shared interfaces.
Where To Find Information on Parameters for Dedicated and Shared Interfaces Table 2-2
Configuration Parameter For Where To Find Information
Dedicated Interfaces
Dedicated interfaces for VQE-S ingest traffic
Dedicated interfaces for VQE-S services traffic
“Interfaces for VQE-S Ingest Traffic (VQE-S Host Only)” section on page 2-29
“Interfaces for VQE-S Services Traffic (VQE-S Host Only)” section on page 2-30
Shared Interfaces
VQE-S traffic interfaces that handle VQE-S ingest traffic and VQE-S services traffic
“Interfaces for VQE-S Traffic (Ingest and Services) (VQE-S Host
Routing Configuration for Dedicated Interfaces and Shared Interfaces
When a VQE deployment uses shared VQE-S traffic interfaces that handle both VQE-S ingest traffic and
VQE-S services traffic, configuration of the CDE interfaces is as follows:
• One or more interfaces for VQE-S traffic use a static default route, or OSPF routing, or both.
• One or more interfaces for VQE-S management traffic use static routing to the management network.
When a VQE deployment uses separate dedicated interfaces for VQE-S ingest traffic and for VQE-S services traffic, configuration of the CDE interfaces is as follows:
• One or more interfaces for VQE-S services traffic use either a static default route, or OSPF routing, or both.
•
•
One or more interfaces for VQE-S ingest traffic use static routing to the distribution network where the video sources reside.
One or more interfaces for VQE-S management traffic use static routing to the management network.
For information on the configuration parameters that are used for static routes, see the
Configuration: IP Address, Prefix Length, and Gateway Address” section on page 26 .
For information on the configuration parameters that are used for OSPF routing, see the
Configuration (VQE-S Host Only)” section on page 28 .
2-16
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
Configuring Static Routes
When a VQE deployment uses dedicated interfaces for VQE-S ingest traffic, the ingest interfaces use static routing to the distribution network where the video sources reside. To configure one or more static routes to the video distribution network, use the VCDB parameter network.route.static_route. Using the
VQE Configuration Tool and their VCDB parameters, you specify the following for each ingest interface:
• Subnet IP address and prefix length for the distribution network.
•
•
Gateway (network hop) IP address of the router interface that is directly attached to a CDE Ethernet interface that is used for ingest traffic.
Optionally, an outbound interface on the VQE-S or VQE Tools server for the static route. To specify an outbound interface, append the interface name to the Gateway IP address, and separate both with a colon.
Caution Configuring an outbound interface is not generally necessary nor is it recommended.
In following example from the VQE configuration Tool, two statics routes are configured. Ethernet interfaces eth1 and eth2 are configured as ingest interfaces. The IP address and prefix length of the distribution network is 192.0.0.0/8. The gateway IP address for the router interface directly attached to eth1 is 10.2.9.1. The gateway IP address for the router interface directly attached to eth2 is 10.2.10.1.
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s):
P) Go to Parent Menu
R) Go to Root Menu
Enter your choice: 1
Add new static routes by entering destination subnet IP/Prefix and gateway IP pairs when prompted.
To configure a default route, enter 0.0.0.0/0 as the destination subnet IP/Prefix.
To specify a specific gateway interface (optional), add it to the end of the gateway IP, separated by ":" (e.g. "5.6.7.8:eth3).
To complete the configuration, press <Enter> at the prompt without entering data.
Enter the destination subnet in IP/Prefix format (e.g., 1.0.0.0/8): 192.0.0.0/8
Enter the gateway IP address: 10.2.9.1
Enter the destination subnet in IP/Prefix format (e.g., 1.0.0.0/8): 192.0.0.0/8
Enter the gateway IP address: 10.2.10.1
As the example shows, two static routes to the distribution network are configured; 192.0.0.0/8 via
10.2.9.1 (nexthop), and 192.0.0.0/8 via 10.2.10.1 (nexthop).
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s):
1.1) 192.0.0.0/8 via 10.2.9.1
1.2) 192.0.0.0/8 via 10.2.10.1
P) Go to Parent Menu
R) Go to Root Menu
Enter your choice:
Each static route has its own submenu. This allows an additional static route to be added without having to delete and recreate existing static routes. It also means that a single static route can be deleted or edited without effecting the other static routes.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-17
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
As the example below shows, static route 192.0.0.0/8 via 10.2.10.1 can be deleted without having to delete static route 192.0.0.0/8 via 10.2.9.1. To restore the default value of a specific route, enter the number of the sub-menu for that specific value followed by the letter “d” and press Enter. For example:
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s):
1.1) 192.0.0.0/8 via 10.2.9.1
1.2) 192.0.0.0/8 via 10.2.10.1
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default, enter
its number choice followed by the letter ‘d’ (e.g. 3d).
Default values are displayed inside square brackets [].
Enter your choice: 1.2d
In this example, when the Static Route(s) menu is displayed, the menu shows that the static route
192.0.0.0/8 via 10.2.10.1 has been deleted.
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s):
1.1) 192.0.0.0/8 via 10.2.9.1
P) Go to Parent Menu
R) Go to Root Menu
Interface for a Management Network
Management traffic is blocked from non-management interfaces. The service provider must designate at least one CDE Ethernet interface or one bond interface as a management interface. Bond interfaces are configurable on the VQE-S hosts only. Multiple Ethernet or bond interfaces may be designated as management interfaces. The default value is all Ethernet interfaces on the VQE-S or VQE Tools server, regardless of their operational status.
Note You must use the VQE Configuration Tool to limit the interfaces where management traffic is allowed or remove any Ethernet interfaces that are members of a bond interface and include the bond interface name.
VQE-S and VQE Tools Server. It also displays the standard type of management traffic associated with each of the ports.
Note If ports other than those listed in
are used for management traffic on non-management interfaces, management traffic on the non-standard protocol ports is not blocked.
Table 2-3 Standard Management Protocol Ports Blocked on Non-Management Interfaces
Port Number
22
443
Standard Management Traffic Type
SSH
1
HTTPS 2
2-18
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
Table 2-3 Standard Management Protocol Ports Blocked on Non-Management Interfaces
Port Number
444
161 and 162
21
Standard Management Traffic Type
HTTPS Push
SNMP
3
FTP
1.
SSH = Secure Shell.
2.
HTTPS = Hypertext Transfer Protocol Secure.
3.
SNMP = Simple Network Management Protocol.
VQE-S traffic (ingest and services), VQE-S ingest traffic or VQE-S services traffic may share the management interfaces. If your deployment requires that VQE-S traffic (ingest and services), VQE-S ingest traffic, or VQE-S services traffic be excluded from the CDE Ethernet interfaces or bond interfaces used for management traffic, do not include those CDE Ethernet interfaces or bond interfaces in the following VQE Configuration Tool parameters:
•
•
Interfaces for VQE-S Ingest Traffic
Interfaces for VQE-S Services Traffic
• Interfaces for VQE-S Traffic (ingest and services)
To set up one or more static routes to the management network, use the Static Route(s) parameter in the
VQE Configuration Tool.
Load Balancing and Redundancy with Multiple VQE-S
When more than one VQE-S provides Unicast Retransmission and RCC or both services for a set of channels, the VQE-Ss and edge router can load balance the requests from the VQE-Cs on the STBs and provide failover protection if a VQE-S fails.
In the VCPT channel definition, each channel is associated with a unique feedback target (FBT) IP address. The VQE-Cs on the STBs use the FBT addresses to request Unicast Retransmission and RCC services for a particular channel. The FBT address is a unique IP anycast address that the VQE-S configures on its host Cisco CDE based on the channel information that is sent to it by VCPT or another channel-provisioning server. An anycast address is a unicast address that is assigned to multiple interfaces. With the appropriate routing topology, packets addressed to an anycast address are delivered to a single interface (in this case, the nearest interface of the VQE-S that is identified by the address).
The use of anycast IP addresses and Equal Cost Multipath (ECMP) routing allows multiple VQE-Ss in a single facility to balance the load among themselves and to provide failover protection in case of a server failure. As an example,
shows a redundant pair of VQE-Ss, each providing Unicast
Retransmission and RCC services for the same set of three channels. On both VQE-Ss, each channel is defined to have the same anycast IP address: A for channel 1, B for channel 2, and C for channel 3.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-19
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
Figure 2-2
FBT addresses for channels channel 1: A channel 2: B channel 3: C
Redundant VQE-Ss for Service Failover and Load Balancing lo
VQE-S server eth1 to eth4
On the STB VQE Clients, channel to FBT mapping: channel 1 A channel 2 B channel 3 C
To access network
STBs channel 1: A channel 2: B channel 3: C lo
VQE-S server eth1 to eth4
Edge router
When OSPF routing is configured on the VQE-S, the FBT routes are advertised from the VQE-S to the edge router. In this example, both VQE-Ss advertise FBT routes for a particular channel. If the services for that channel become unavailable on one VQE-S, that VQE-S withdraws the route. This allows the other VQE-S to take over services for that channel. If one VQE-S fails, the second VQE-S services the requests directed to the three feedback target addresses.
With OSPF routing and ECMP on the edge router, the router uses multi-interface load splitting on different interfaces with equal cost paths. ECMP provides load balancing of output traffic on the edge router interfaces that are attached to the VQE-S traffic interfaces on the CDE server. If three Ethernet interfaces on each of the two VQE-Ss were configured for VQE-S traffic, the edge router would load balance STB requests for VQE-S services over the six available Ethernet interfaces.
Configuring LACP Bonding on a VQE-S and VQE Tools Server
You can enable 803.ad LACP protocol for all bonds on the VQE-S and VQE-Tools Server. This is a global configuration for all bonds. To enable LACP bonding, use network.bond1 on the VQE-S and
VQE-Tools Server:
The following two parameters support LACP bonding:
•
• network.bond.mode
This can be set to either “lacp” or “balance-xor” (default).
network.bond.lacp_rate
This parameter can be either slow or fast. It is slow by default.
Restrictions
A service role (ingest, service, management) may only have a single VLAN assigned to it. For example, you may only assign one sub-interface of a given interface/bond to a given role.
LACP and LACP Rate are global configuration knobs. If LACP or LACP Rate are enabled, this applies to all bonds.
User Interface
The following example shows how to create a VLAN interface and enable LACP:
2-20
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
VQE Configuration Tool <Network Parameters> Menu:
1) Routing Parameters
2) Interface Parameters
3) Bond Parameters
4) VLAN Parameters
R) Go to Root Menu
Enter your choice: 3
VQE Configuration Tool <Bond Parameters> Menu:
1) Bond1 IP/Mask and members: []
2) Bond2 IP/Mask and members: []
3) Bond3 IP/Mask and members: []
4) Bond4 IP/Mask and members: []
5) Bond5 IP/Mask and members: []
6) Enable 802.3ad LACP for Bonds: [false]
7) Enable fast LACP rate: [false]
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default value, enter its number choice
followed by the letter 'd' (e.g. 3d). Default values are displayed inside
square brackets [].
Enter your choice: 6
If you choose to enable LACP, all bonds will run in this mode instead of balance-xor.
Enable 802.3ad LACP: y/[n] y
VQE Configuration Tool <Bond Parameters> Menu:
1) Bond1 IP/Mask and members: []
2) Bond2 IP/Mask and members: []
3) Bond3 IP/Mask and members: []
4) Bond4 IP/Mask and members: []
5) Bond5 IP/Mask and members: []
6) Enable 802.3ad LACP for Bonds: true
7) Enable fast LACP rate: [false]
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default value, enter its number choice
followed by the letter 'd' (e.g. 3d). Default values are displayed inside
square brackets [].
Enter your choice: 7
Enable fast rate for LACP: y/[n] y
VQE Configuration Tool <Bond Parameters> Menu:
1) Bond1 IP/Mask and members: []
2) Bond2 IP/Mask and members: []
3) Bond3 IP/Mask and members: []
4) Bond4 IP/Mask and members: []
5) Bond5 IP/Mask and members: []
6) Enable 802.3ad LACP for Bonds: true
7) Enable fast LACP rate: true
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default value, enter its number choice
followed by the letter 'd' (e.g. 3d). Default values are displayed inside
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 2-21
Chapter 2 Initial VQE Configuration
VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview
square brackets [].
Enter your choice:
Configuring VLAN Support on a VQE-S and VQE-Tools Server
You can configure 802.1q VLAN sub-interfaces on all Ethernet and bond interfaces.
The following example shows how to configure VLAN support:
VQE Configuration Tool <Network Parameters> Menu:
1) Routing Parameters
2) Interface Parameters
3) Bond Parameters
4) VLAN Parameters
R) Go to Root Menu
Enter your choice: 4
VQE Configuration Tool <802.1q Sub-Interface Parameters> Menu:
1) Eth0 SubInterface VLAN tag IP/Mask:
2) Eth1 SubInterface VLAN tag IP/Mask:
3) Eth2 SubInterface VLAN tag IP/Mask:
4) Eth3 SubInterface VLAN tag IP/Mask:
5) Eth4 SubInterface VLAN tag IP/Mask:
6) Eth5 SubInterface VLAN tag IP/Mask:
7) Eth6 SubInterface VLAN tag IP/Mask:
8) Eth7 SubInterface VLAN tag IP/Mask:
9) Eth8 SubInterface VLAN tag IP/Mask:
10) Eth9 SubInterface VLAN tag IP/Mask:
11) Bond1 SubInterface VLAN tag IP/Mask:
12) Bond2 SubInterface VLAN tag IP/Mask:
13) Bond3 SubInterface VLAN tag IP/Mask:
14) Bond4 SubInterface VLAN tag IP/Mask:
15) Bond5 SubInterface VLAN tag IP/Mask:
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default value, enter its number choice
followed by the letter 'd' (e.g. 3d). Default values are displayed inside
square brackets [].
Enter your choice: 1
Configure VLAN (802.1q) interfaces for eth0.
Enter subinterface VLAN tag: 100
Enter the IP/Prefix for eth0.100 (e.g. 1.2.3.4/8): 1.2.3.4/24
Enter subinterface VLAN tag: 200
Enter the IP/Prefix for eth0.200 (e.g. 1.2.3.4/8): 4.3.2.1/24
Enter subinterface VLAN tag:
VQE Configuration Tool <802.1q Sub-Interface Parameters> Menu:
1) Eth0 SubInterface VLAN tag IP/Mask:
1.1) 100 1.2.3.4/24
1.2) 200 4.3.2.1/24
2) Eth1 SubInterface VLAN tag IP/Mask:
3) Eth2 SubInterface VLAN tag IP/Mask:
4) Eth3 SubInterface VLAN tag IP/Mask:
5) Eth4 SubInterface VLAN tag IP/Mask:
2-22
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
6) Eth5 SubInterface VLAN tag IP/Mask:
7) Eth6 SubInterface VLAN tag IP/Mask:
8) Eth7 SubInterface VLAN tag IP/Mask:
9) Eth8 SubInterface VLAN tag IP/Mask:
10) Eth9 SubInterface VLAN tag IP/Mask:
11) Bond1 SubInterface VLAN tag IP/Mask:
12) Bond2 SubInterface VLAN tag IP/Mask:
13) Bond3 SubInterface VLAN tag IP/Mask:
14) Bond4 SubInterface VLAN tag IP/Mask:
15) Bond5 SubInterface VLAN tag IP/Mask:
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default value, enter its number choice
followed by the letter 'd' (e.g. 3d). Default values are displayed inside
square brackets [].
Enter your choice:
V
Using the VQE Configuration Tool
The CDE server has the VQE software preinstalled. The tool is available on the CDE that hosts VQE-S and on the CDE that hosts VQE Tools. We recommend that you use the VQE Configuration Tool rather than try to do the initial configuration manually because the tool simplifies your work and is known to produce correct results.
Before using the VQE Configuration Tool, do the following to understand how the tool works and what information you need to collect before powering on the VQE-S or VCPT server:
• Read the
“VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview” section on page 2-11 .
•
•
•
•
Read the
Read the
“Configuration Parameters” section on page 2-24 .
Complete the
“Preconfiguration Worksheets” section on page 2-32
.
Read the
“VQE Configuration Tool Root Menu” section on page 2-36
.
When it is started, the VQE Configuration Tool displays the following choices:
Please choose one of the following:
1) I have all the information needed and want to proceed.
2) I do not have all the information and want to shutdown the system.
3) Skip configuration wizard and directly enter the system.
If you select choice 1, the VQE Configuration Tool prompts you for configuration values.
If you select choice 2, the system is shutdown. The next time the system is started the VQE Configuration
Tool is launched.
After you finish entering configuration values, the VQE Configuration Tool displays the Root Menu. The
Root Menu allows you to view the values that you have specified and to change values that are not correct.
After using the VQE Configuration Tool, perform the verification tasks in the following sections:
•
“On the VQE-S Host: Verifying the Status of the VQE and System Services” section on page 39
•
“On the VQE Tools Host: Verifying the Status of the VQE and System Services” section on page 41
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-23
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Configuration Parameters
This section provides information on the configuration parameters present in the VQE Configuration
Tool. Before using the VQE Configuration Tool, read the descriptions of the configuration parameters in this section.
Tip For many configuration parameters, you need to gather some information before booting the CDE for the first time and using the VQE Configuration Tool. The worksheets in the
Worksheets” section on page 32
may be helpful in organizing the information.
In the explanations that follow, these conventions are used for the configuration parameters:
•
•
For the parameters that are for a VQE-S host only, VQE -S Host Only appears in parentheses after the item name.
For optional parameters, Optional appears in parentheses after the item name.
Note To not enter data for an optional item, press Enter without entering any data at the VQE Configuration
Tool prompt.
Passwords for root and vqe User IDs
The password for root is set when the CDE boots normally for the first time (when you log in as root) and before the VQE Configuration Tool executes.
The vqe username is a predefined Linux user ID that the system administrator can use to log in to VQE-S
AMT, VCDS AMT, and VCPT.
The root and vqe user passwords have the following requirements: A valid password should be a mix of uppercase and lowercase letters, digits, and other characters. You can use an eight-character long password with characters from at least three of these four classes, or a seven-character long password containing characters from all the classes. An uppercase letter that begins the password and a digit that ends it do not count toward the number of character classes used.
The password can be a passphrase. A passphrase should be at least three words with a combined total length of 12 to 40 characters.
Creating Linux users and maintaining password settings is the responsibility of the Cisco CDE system administrator. The default password settings for root, vqe, and Linux users are located in the
/etc/pam.d/system-auth-ac file on the VQE-S and the VQE Tools server. For information on changing passwords for Linux and vqe users, see the Linux passwd man page at http://linux.die.net/man/1/passwd .
For information on resetting the root password, see the
“Resetting the Root Password on the VQE-S or
VQE Tools Server” section on page 6-31 . For more information on configuring password settings such
as length, complexity, and ageing, for root, vqe, and Linux users, see the pam_passwdqc man page at http://linux.die.net/man/8/pam_passwdqc .
Hostname for the CDE
The hostname is used in multiple Linux configuration files. Allowed range is 3 to 200 characters.
Domain Name System (DNS) IP Addresses and a Search Domain
The IP addresses of one or more DNS servers and an optional search domain. Allowed range for the search domain is 3 to 200 characters.
2-24
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
System Timezone
The timezone and current system time that are used for this CDE. The VQE Configuration Tool prompts for the needed information.
NTP Server IP Addresses
The IP addresses of one or more external Network Time Protocol (NTP) servers.
Note We recommend that the system time of each CDE be synchronized with NTP. Problems (for example, with Session Description Protocol [SDP] updates) can occur if the server time is not synchronized with
NTP.
Current System Time
The current system time that are used for this CDE. The VQE Configuration Tool prompts for the needed information.
Ethernet Interface Configuration: IP Address and Prefix Length
For one or more of the Ethernet ports on the Cisco CDE, you specify an IP address and prefix length (for example, 1.2.3.4/32). The IP address and prefix length are not specified for any CDE Ethernet interface that is a member of a bond interface. The Ethernet ports are named eth1 to eth6 as shown in
Note Earlier models of the CDE have four Ethernet ports (eth1 to e th4). These models did not have the Intel PRO/1000 PT Dual Port Server Adapter that provides the eth5 and eth6 ports.
•
•
•
On a VQE-S host, up to six Ethernet interfaces are typically configured and used for incoming multicast streams, outgoing Unicast Retransmissions, and other VQE-S traffic.
On a VQE Tools host, at least one Ethernet interface is typically configured and used for VCPT and
VCDS traffic.
On the VQE-S host, at least one Ethernet or bond interface must be used for the management interface. On the VQE Tools host, at least one Ethernet interface must be used for the management interface. If an Ethernet interface is used, this interface should be included in the set for which you provide IP addresses and prefix lengths.
Figure 2-3 Ethernet Port Numbering for Software Configuration eth3 eth2 eth6 eth5
3
4
2
1 eth4 eth1
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-25
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Bond Interface Configuration: IP Address and Prefix Length
On the VQE-S/VQE-Tool Server, you specify an IP address and prefix length (for example, 1.2.3.4/32) for one or more bond interfaces using the network.bondx.addr parameter where, depending on CDE model, bondx is bond1, bond2, or bond3. For each bond interface, you assign Ethernet interfaces to the bond interface using the network.bondx.member parameter where, depending on CDE model, bondx is bond1, bond2, or bond3. The Ethernet interfaces must not be members of an existing bond interface and do not have an IP address and prefix length assigned. On a VQE-S host, up to three bond interfaces may be configured and used for the Ethernet interfaces handling incoming multicast streams, outgoing
VQE-S services, and management traffic. The number of bonds on a VQE-Tools Server is hardware dependent.
In the following example from the VQE Configuration Tool, the IP address and prefix length of bond1 is 11.2.15.2/24 and the Ethernet interfaces assigned to bond1 are eth3 and eth4.
VQE Configuration Tool <Interface Parameters> Menu:
1) Eth1 Interface IP/Mask: 10.2.9.2/24
2) Eth2 Interface IP/Mask: 10.2.10.2/24
3) Eth3 Interface IP/Mask: [bond1]
4) Eth4 Interface IP/Mask: [bond1]
5) Eth5 Interface IP/Mask: []
6) Eth6 Interface IP/Mask: []
7) Bond1 IP/Mask and members: [11.2.15.2/24 eth3,eth4]
8) Bond2 IP/Mask and members: []
9) Bond3 IP/Mask and members: []
10) Management Interface(s): eth1,eth2
P) Go to Parent Menu
R) Go to Root Menu
Enter your choice:
Note Starting with Cisco VQE Release 3.7, bond interfaces are supported on the VQE Tools server.
For more information on the restrictions that apply to the use of bond interfaces, see
“Bond Interfaces on a VQE-S and VQE-Tools Server” section on page 12 .
Static Route Configuration: IP Address, Prefix Length, and Gateway Address
If your deployment makes use of static routes to the management, distribution, or access network, the
VQE Configuration Tool can configure static routes. Specify the following:
• Subnet IP address and prefix length for the target network. The following example shows the allowed format for the subnet IP address and prefix length:
10.1.0.0/16
Note On the VQE-S, when creating a default route, specify 0.0.0.0/0 as the subnet IP address and prefix length for the target network.
•
•
Gateway (next hop) IP address of the interface on the router that is directly attached to the VQE-S
CDE interface that is used for the target network. The interface on the VQE-S and the attached edge router may be an Ethernet interface or a bond interface. The interface on the VQE Tools server is always an Ethernet interface.
Optionally, an outbound interface on the VQE-S or VQE Tools server for the static route. To specify an outbound interface, append the interface name to the Gateway IP address, and separate both with a colon.
2-26
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Caution Specifying an outbound interface is not generally needed, nor is it recommended.
As an example of gateway (next hop) IP address, if Ethernet interface eth4 were used for the target network, specify the IP address of the router interface that is directly attached to eth4.
On the VQE Tools server, proper route configuration is needed for external access to the VQE Tools server. You can use the static route created by this parameter to configure this access.
Note If you configure a static route for a management network, the Multicast Load Balancer (MLB) monitors the status of this route. If the MLB detects that the underlying interface is administratively down, the
MLB attempts to recreate the route after the interface is brought back up.
On the VQE-S, multipath static routes can be configured for VQE-S traffic (ingest and services) or
VQE-S services traffic. The VQE-S uses Equal Cost Multipath (ECMP) to load-balance its output traffic across CDE Ethernet interfaces or the physical Ethernet interfaces of a bond interface that are directly attached to the gateway router interfaces that are specified. If a default route (static route) is configured for each Ethernet interface that is available to VQE-S for Unicast Retransmissions, RCC, and other
VQE-S traffic, ECMP load balances output traffic across all the CDE interfaces directly attached to the gateway router interfaces. Similarly, if a default route is configured for a bond interface, ECMP load balances output traffic across all the CDE physical interfaces assigned to the bond interface.
For more information on ECMP configuration, see the
“Configuring Static Routes for VQE-S Traffic or
VQE-S Services Traffic (VQE-S Host)” section on page D-8
.
SSL Certificate Options
Secure Sockets Layer (SSL) certificates must be created and deployed for VQE-S AMT, VCDS AMT, or VCPT to be accessed using HTTPS. The VQE Configuration Tool gives you three options for creating and deploying the certificates. For information on the three options and using the tool for creating and deploying SSL certificates, see the
“Using the Cisco VQE Configuration Tool for SSL Certificates” section on page 6 .
Trusted Provisioning Clients
The use of this VCDB parameter, system.iptables.trusted_provisioner, varies depending on the VQE-S type:
• For a VQE-S host, if your IPTV deployment uses VCPT or another channel-provisioning server to send channel information to the VQE-S, specify the IP addresses of the trusted channel-provisioning servers. If VCPT is the channel-provisioning server, the IP addresses of all Ethernet interfaces (that have been assigned IP addresses) on the VCPT host must be configured as trusted HTTPS clients on the VQE-S host.
•
•
For a VQE Tools host where a VCDS receives channel information from VCPT, all Ethernet
interfaces (that have been assigned IP addresses) on the VCPT host sending the channel information must be specified as addresses in Trusted Provisioning Clients. This requirement applies even when the VCDS is in the same VQE Tools server as the VCPT.
For a VQE Tools host, if a VQE-C system configuration provisioning server or the vcds_send_file command sends a network configuration file to the VCDS, you specify, on the VQE Tools host, the
IP address of the trusted VQE-C system configuration provisioning server or vcds_send_file. If
vcds_send_file is used, all Ethernet interfaces (that have been assigned IP addresses) on the
vcds_send_file host have to be specified as trusted provisioning clients. This requirement applies even when the VCDS is in the same VQE Tools server as the vcds_send_file command.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-27
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
2-28
Note If the needed IP addresses of the trusted provisioning servers are not configured on the VQE-S and VQE
Tools servers, the servers reject attempts by the provisioning server or vcds_send_file to send the channel or network configuration information.
This parameter is for enhanced communications security beyond HTTPS. The VQE-S or VQE Tools server is configured so that only trusted HTTPS clients (as specified in the Trusted Provisioning Client parameter) can send information to, respectively, the VQE-S or VQE Tools server using HTTPS.
Remote Syslog Hosts
On both the VQE-S and the VQE Tools server, VQE system messages are written to the file
/var/log/vqe/vqe.log by default. In addition to logging system messages locally, you can send system messages by means of UDP to remote servers for centralized logging. This VCDB parameter, system.syslog.remote_server, is used to specify the IP addresses of the remote servers.
SNMP Read-Only Community String, Location, Contact, and Trap-Listener IP Addresses or Hostnames
If your deployment uses SNMP, specify the following:
• Read-only community string—Password for read-only access to the VQE-S or VQE Tools server.
•
•
•
Location information—Physical location of the VQE-S or VQE Tools server.
Contact information—Username of a contact person who has management information for the CDE server.
Trap listeners—IP addresses or fully qualified hostnames of the management hosts that receives the
SNMP messages.
For more information on SNMP for the CDE, see
Sending SNMP Traps
When SNMP is configured, the VQE-S and the VQE Tools server provide the capability to convert system messages to SNMP traps (syslog traps). To generate syslog traps, configure the following parameters:
• VCDB parameter system.snmp.syslog_trap_enable (Enable Syslog Traps menu)—Disabled by default.
• VCDB parameter system.snmp.syslog_trap_priority (Syslog Trap Priority menu)—When the generation of syslog traps is enabled, syslog messages with a severity level less than or equal to this value are sent as traps. The default value is 2 (critical). Valid values are 0 to 7. For a definition of each severity level, see
.
The VQE-S provides the capability of sending a channel up trap when a channel becomes active and a channel down trap when a channel becomes inactive. Use the VCDB parameter system.snmp.channel_trap_enable (Enable Channel Up/Down traps menu) to enable or disable the generation of channel traps.
For information on configuring SNMP, see the
“SNMP Read-Only Community String, Location,
Contact, and Trap-Listener IP Addresses or Hostnames” section on page 28 .
For more information on SNMP for the CDE, see
OSPF Configuration (VQE-S Host Only)
on the OSPF parameters, see the following Quagga documentation: http://www.quagga.net/docs/quagga.pdf
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Table 2-4 OSPF Parameters
Parameter
Enable OSPF
Area Type
Area ID
Router ID
Enable MD5
MD5 Key
MD5 Key ID
Hello Interval
Dead Interval
Description
Specifies whether OSPF routing is enabled for VQE-S traffic (where shared interfaces to the access network are configured) or for VQE-S services traffic
(where dedicated interfaces to the access network are configured).
Type for the OSPF area that the VQE-S traffic interfaces and feedback target host addresses reside in. You can choose from either normal or nssa (Not So Stubby
Area). If no value is specified, the default value is normal.
Integer ID value for the OSPF area that the VQE-S Ethernet interfaces and feedback target addresses reside in. If no value is specified, the default value is 0. Allowed range is 0 to 4,294,967,295.
IP address used as the router ID to uniquely identify the VQE-S in the OSPF network. The router ID must not be the same as the IP address of one of the CDE
Ethernet interfaces because the router ID is added as an internal address to the loopback interface.
Specifies whether MD5
1
authentication is enabled on the Ethernet interfaces used for VQE-S traffic. When MD5 authentication is enabled, specifying an MD5 key and MD5 key ID are required.
If MD5 authentication is enabled, specifies a key (a string) that is configured for all
Ethernet interfaces used for VQE-S traffic. When MD5 authentication is enabled, an MD5 key and MD5 key ID are required. Allowed length for the string is 1 to 16 characters.
If MD5 authentication is enabled, specifies an MD5 key ID (an integer) that is used for all Ethernet interfaces used for VQE-S traffic. When MD5 authentication is enabled, an MD5 key and MD5 key ID are required. Allowed range of integer values is 1 to 255.
Interval (in seconds) at which OSPF Hello packets are sent. This value must be the same for all interfaces running OSPF in the network. The hello interval is set for all
VQE-S interfaces running OSPF. If no value is specified, the default value is 10.
Allowed range is 1 to 65,535.
OSPF dead interval (in seconds). The dead interval is the maximum amount of time allowed to receive a Hello packet from a neighbor before that neighbor is declared down. This value must be the same for all interfaces running OSPF in the network.
The dead interval is set for all VQE-S interfaces running OSPF. If no value is specified, the default value is 40. Allowed range is 1 to 65,535.
1.
MD5 = message digest 5.
For information about routing on the VQE-S host, see the
“VQE-S and VQE-Tools Server: Routing and
Interface Configuration Overview” section on page 11 .
Interfaces for VQE-S Ingest Traffic (VQE-S Host Only)
If you choose to select dedicated interfaces for VQE-S ingest traffic, specify one or more CDE Ethernet interfaces or one or more bond interfaces that are used for ingest of multicast streams. Ethernet interfaces must not be members of an existing bond interface. Depending on CDE model, allowed choices of
Ethernet interfaces are eth1 to eth6. Allowed bond interfaces are bond1 to bond3.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-29
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Note For VQE-S ingest traffic, multiple bond interfaces should not be used because load balancing cannot work effectively if there is no guarantee that each interface in the link has the same capacity.
When you choose to select dedicated interfaces for VQE-S ingest traffic and separate dedicated interfaces for VQE-S services traffic (see the next parameter), the following rules apply:
• At least one interface must be specified in the Interfaces for VQE-S Ingest Traffic parameter (this parameter).
•
•
•
•
At least one VQE-S services interface must be specified in the Interfaces for VQE-S Services Traffic parameter.
Interfaces for VQE-S Ingest Traffic must not be specified in the Interfaces for VQE-S Services
Traffic parameter.
Interfaces for VQE-S Traffic (ingest and services) parameter (in VCDB, vqe.vqes.vqe_interfaces) must not be specified.
If a dedicated interface is used for management traffic, it must not be specified in Interfaces for
VQE-S Ingest Traffic parameter, in the Interfaces for VQE-S Services Traffic parameter, or in the
Interfaces for VQE-S Traffic (ingest and services) parameter.
Interfaces for VQE-S Services Traffic (VQE-S Host Only)
If you choose to select a dedicated interface for VQE-S ingest traffic (the preceding parameter), you also must specify one or more CDE Ethernet interfaces or one or more bond interfaces that is used for VQE-S services—Unicast Retransmission and RCC traffic to downstream VQE-Cs on STBs. Ethernet interfaces must not be members of an existing bond interface. Depending on CDE model, allowed choices of
Ethernet interfaces are eth1 to eth6. Allowed bond interfaces are bond1 to bond3.
Note For VQE-S services traffic, multiple bond interfaces should not be used because load balancing cannot work effectively if there is no guarantee that each interface in the link has the same capacity.
For the rules that apply when you choose to select a dedicated interface for VQE-S ingest traffic and interfaces for VQE-S services traffic, see the preceding
“Interfaces for VQE-S Ingest Traffic (VQE-S
Host Only)” section on page 29 .
Interfaces for VQE-S Traffic (Ingest and Services) (VQE-S Host Only)
If you choose not to select dedicated interfaces for VQE-S ingest and services traffic, you specify the
CDE Ethernet interfaces or one or more bond interfaces that are available for all VQE-S Traffic (ingest and services). Ethernet interfaces must not be members of an existing bond interface. The shared interfaces are used for ingest of multicast streams from upstream video sources and for VQE-S services
(Unicast Retransmission and RCC traffic to downstream VQE-Cs on STBs). Ethernet and bond interfaces are different depending on the CDE model, refer to
for allowed choices for each model.
Note For VQE-S Traffic (ingest and services), multiple bond interfaces should not be used because load balancing cannot work effectively if there is no guarantee that each interface in the link has the same capacity.
2-30
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Note If a dedicated interface is used for a management network, that interface must not be included as one of the interfaces that are available for VQE-S traffic (ingest and services).
Interfaces for Management Traffic
At least one CDE Ethernet interface or one bond interface must be specified as the management interface. Ethernet interface must not be members of an existing bond interface. VQE-S traffic (ingest and services), VQE-S ingest traffic or VQE-S services traffic may share the management interfaces.
Management traffic is blocked from non-management interfaces.
For the rules that apply when you specify management interfaces, see the
Network” section on page 2-18 .
VQE Configuration Tool Root Menu
After you finish specifying values for the configuration items, the VQE Configuration Tool displays the following menu:
VQE Configuration Tool Root Menu:
1) System Parameters
2) Network Parameters
3) VQE-S Parameters
S) Save and Exit
A) Save/Apply and Exit
E) Exit without saving
Enter your choice:
For information on this menu, see the
“VQE Configuration Tool Root Menu” section on page 2-36
.
When you have completed the configuration items, you choose S) Save/Apply and reboot system. The
VQE Configuration Tool saves your configuration in the VCDB file, applies the VCDB values to the configuration files under /etc, and reboots the CDE system. Each time the VQE-S or VQE Tools host reboots, the services listed in
and
are started.
Table 2-5 VQE-S and System Services for CDE That Hosts VQE-S
Service vqes sshd httpd tomcat5 snmpd
Description
VQE-S service (process_monitor process) starts and monitors the other VQE-S processes—Control Plane, Data Plane, Multicast Load Balancer, and STUN
Server.
The Secure Shell daemon.
HyperText Transfer Protocol daemon (the Apache web server).
The Apache Tomcat application server.
(Optional) SNMP daemon. vqes_snmpsa syslog_snmpsa ntpd check_daemons
(Optional) VQE-S SNMP subagent
(Optional) Syslog SNMP subagent.
(Optional) NTP daemon.
Script that monitors httpd and tomcat processes and attempts to restart them if they fail. The script runs once a minute as a cron job owned by root.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-31
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Table 2-5 VQE-S and System Services for CDE That Hosts VQE-S (continued)
Service Description
If OSPF is selected as the routing type watchquagga Quagga watchdog process. If the ospfd or zebra daemon crashes or hangs, watchquagga restarts it automatically.
Table 2-6
Service sshd httpd tomcat5 snmpd snmpsa vcds_snmpsa syslog_snmpsa ntpd check_daemons
VCDS and System Services for CDE That Hosts VQE Tools
Description
Secure Shell daemon.
HyperText Transfer Protocol daemon (the Apache web server).
Apache Tomcat application server.
(Optional) SNMP daemon.
(Optional) Intel SNMP subagent.
(Optional) VCDS SNMP subagent.
(Optional) Syslog SNMP subagent.
(Optional) NTP daemon.
Script that monitors httpd and tomcat processes and attempts to restart them if they fail. The script runs once a minute as a cron job owned by root.
Note On the VQE Tools host, VCPT is a web application and has no dedicated processes associated with it.
The processes needed for the VCPT web application to work (for example, the web server) are started automatically when the Cisco CDE is started.
Preconfiguration Worksheets
Before using the VQE Configuration Tool, complete the preconfiguration worksheets in
VQE-S host and
for a VQE Tools host before the first normal boot. The use of a VQE Tools server and VCPT is optional.
For information on the configuration items in
and
, see the
Parameters” section on page 24
.
Table 2-7 VQE-S CDE: Preconfiguration Worksheet
Value for Your Deployment Configuration Item
Password for root
Password for the vqe username (a predefined Linux user ID)
2-32
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Table 2-7 VQE-S CDE: Preconfiguration Worksheet (continued)
Configuration Item
Hostname of the CDE for VQE-S
Domain Name System (DNS) IP addresses and a search domain
Value for Your Deployment
DNS IP address:
DNS IP address:
Search domain:
System timezone
External NTP server IP addresses
CDE110 Ethernet interface configurations
(IP address and prefix lengths) eth1: eth2: eth3:
CDE250 Ethernet interface configurations
(IP address and prefix lengths) eth4: eth5: eth6: eth0: eth1: eth2: eth3: eth4: eth5:
CDE110 Bond interface configurations (IP address, subnet mask and members eth6: eth7: eth8: eth9: bond1: bond2:
CDE250 Bond interface configurations (IP address, subnet mask and members bond3: bond1: bond2:
For static routes, destination subnet IP address and prefix length, and gateway
(next hop) IP address
SSL certificate option bond3: bond4: bond5:
Destination Subnet IP address and prefix length:
Gateway (next hop) IP address:
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-33
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Table 2-7 VQE-S CDE: Preconfiguration Worksheet (continued)
Value for Your Deployment Configuration Item
Trusted provisioning clients IP addresses
Remote syslog hosts IP addresses
SNMP read-only community string
Location for SNMP
Contact for SNMP
SNMP trap-listener IP addresses or hostnames
Are Syslog traps enabled?
Syslog trap priority
Are channel up/down traps enabled?
If OSPF routing is enabled, the OSPF parameters required by your networking implementation can be configured. community string: location: contact:
IP addresses or hostnames:
Yes or No:
Yes or No: area type: area ID: router ID:
Enable MD5 authentication?
MD5 key:
MD5 key ID:
Hello interval:
Dead interval:
Ethernet interface names or bond interface name that is used for VQE-S ingest traffic
Ethernet interface names or bond interface name that is used for VQE-S services traffic
Ethernet interface names or bond interface name that is used for VQE-S traffic (ingest and services)
One or more Ethernet interface names, or one or more bond interface names, or both that is used for management traffic
Table 2-8 VQE Tools CDE: Preconfiguration Worksheet
Value for Your Deployment Configuration Item
Password for root
Password for the vqe username (a predefined Linux user ID)
Hostname of the CDE for VCPT
2-34
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Table 2-8 VQE Tools CDE: Preconfiguration Worksheet (continued)
Configuration Item
Domain Name System (DNS) IP addresses and a search domain
Value for Your Deployment
DNS IP address:
DNS IP address:
Search domain:
System timezone
External NTP server IP addresses
CDE110 Ethernet interface configurations
(IP address and mask)
CDE250 Ethernet interface configurations
(IP address and mask) eth1: eth2: eth3: eth4: eth5: eth6: eth0: eth1: eth2: eth3: eth4: eth5: eth6: eth7: eth8: eth9:
Destination Subnet IP address and prefix length:
Gateway (next hop) IP address:
For static routes, destination subnet IP address and prefix length, and gateway
(next hop) IP address
SSL certificate option
Ethernet interface names that are used for management traffic
Trusted provisioning clients IP addresses
Remote syslog hosts IP addresses
SNMP read-only community string
Location for SNMP
Contact for SNMP
SNMP trap-listener IP addresses or hostnames
Are Syslog traps enabled?
Syslog trap priority community string: location: contact:
IP addresses or hostnames:
Yes or No:
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-35
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
VQE Configuration Tool Root Menu
After you have used the VQE Configuration Tool to specify values for the configuration items, the tool displays the Root Menu. The Root Menu allows you to view the values that you have specified and to change values that are not correct. The Root Menu on a VQE-S is as follows:
VQE Configuration Tool Root Menu:
1) System Parameters
2) Network Parameters
3) VQE-S Parameters
S) Save and Exit
A) Save/Apply and Exit
E) Exit without saving
Enter your choice:
This Root Menu and its behavior are similar to the standard VQE Configuration Tool Root Menu and behavior. The two differences are that the numbered choices 3 and 4 are only present in the VQE
Configuration Tool, and the Save/Apply choice in the VQE Configuration Tool includes a reboot of the system.
Note For information on how to use the VQE Configuration Tool Root Menu and the other menu choices, see the
“Using the VQE Configuration Tool” section on page 7-3 . The information in the “Using the VQE
Configuration Tool” section is applicable to the Root Menu and other menu choices presented at the end of the VQE Configuration Tool.
The Root Menu choices allow you to do the following:
•
•
View and change the parameter or password values that you have set (choices 1, 2, 3)
Save the parameter values to the VQE Configuration Database (VCDB), and apply the values to the
VQE-S or VQE Tools server (choice A)
To view and change parameter values, you can select choices 1, 2, and 3as many times as you wish.
Note When you are finished specifying parameter values, you must select choice S) Save/Apply and reboot system to save the parameter values to the VQE Configuration Database (VCDB), and apply the values to the VQE-S or VQE Tools server.
for your choice.
2-36
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Table 2-9
2) CDE110 Network
Parameters > Interface
Parameters
Root Menu Choices
Root Menu Choice
1) System Parameters
1) System Parameters >
SNMP Parameters
Menu Description
Allows you to view the current system parameter values that you have set, and to change or set the system parameters values:
1) Hostname
2) DNS Server(s)
3) DNS Search Domain
4) Timezone
5) NTP Server(s)
6) Trusted Provisioning Client(s)
7) Remote Syslog Host(s)
8) SNMP Parameters
R) Go to Root Menu
1) SNMP RO Community String
2) SNMP System Location
3) SNMP System Contact
4) SNMP Trap Listener(s)
5) Enable Syslog Traps
6) Syslog Trap Priority
7) Enable Channel Up/Down Traps
P) Go to Parent Menu
R) Go to Root Menu
Allows you to view the current interface parameter values that you have set, and to change or set the interface parameters values:
1) Eth1 Interface IP/Mask
2) Eth2 Interface IP/Mask
3) Eth3 Interface IP/Mask
4) Eth4 Interface IP/Mask
5) Eth5 Interface IP/Mask
6) Eth6 Interface IP/Mask
7) Bond1 IP/Mask and members
8) Bond2 IP/Mask and members
9) Bond3 IP/Mask and members
10) Management Interface(s)
P) Go to Parent Menu
R) Go to Root Menu
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-37
Chapter 2 Initial VQE Configuration
Using the VQE Configuration Tool
Table 2-9 Root Menu Choices (continued)
Root Menu Choice
2) CDE250 Network
Parameters > Interface
Parameters
Menu Description
Allows you to view the current interface parameter values that you have set, and to change or set the interface parameters values:
1) Eth0 Interface IP/Mask
2) Eth1 Interface IP/Mask
3) Eth2 Interface IP/Mask
4) Eth3 Interface IP/Mask
5) Eth4 Interface IP/Mask
6) Eth5 Interface IP/Mask
7) Eth6 Interface IP/Mask
8) Eth7 Interface IP/Mask
9) Eth8 Interface IP/Mask
10) Eth9 Interface IP/Mask
11) Bond1 IP/Mask and members
12) Bond2 IP/Mask and members
13) Bond3 IP/Mask and members
14) Bond4 IP/Mask and members
15) Bond5 IP/Mask and members
16) Management Interface(s)
2) Network Parameters >
Routing Parameters > Static
Routing Parameters
3) VQE-S Parameters
Allows you to view the current static routing parameter values that you have set, and change or set the static routing parameter value:
1) Static Route(s)
Allows you to view the current VQE-S parameter values that you have set, and to change or set the VQE-S parameters values:
1) Log Priority *
2) Excess Bandwidth Fraction *
3) Traffic (Ingest+Service) Interface(s)
4) Ingest Interface(s)
5) Service Interface(s)
S) Save and Exit
A) Save/Apply and Exit
E) Exit without saving
6) RTCP Exporter Parameters)
R) Go to Root Menu
* The VQE Configuration Tool does not allow you to set the values of these parameters in the set of parameters that were previously displayed.
You can supply values at this point if you want or accept the defaults. For more information on these values, see the vcdb.conf.sample file and
Appendix A, “VQE, System and Network Parameters.”
Saves the changes you have made to the VCDB parameters and exits
Configuration Tool. Any new parameter values are not applied to the configuration files under /etc.
Saves the changes you have made to the VCDB parameters, applies any new parameter values to the configuration files under /etc, restarts services (as needed), and exits Configuration Tool..
Exits Configuration Tool. Any changes you have made to the VCDB parameters are not saved.
2-38
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
On the VQE-S Host: Verifying the Status of the VQE and System Services
On the VQE-S Host: Verifying the Status of the VQE and System
Services
After the VQE Configuration Tool finishes and the CDE that hosts VQE-S reboots, it is recommended that you perform some quick checks to ensure that VQE and system services are running.
To verify the status of VQE services on the VQE-S host, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
If needed, log in as root.
To verify that the SSH service is running, enter the following command:
[root@system]# service sshd status sshd (pid 21165 21110 20595 20569 2777) is running...
To verify that the HTTP service is running, enter the following command:
[root@system]# service httpd status httpd (pid 9665 9664 9663 9661 9660 9658 9657 9656 3978) is running...
To verify that the Tomcat 5 service is running, enter the following command:
[root@system]# service tomcat5 status
Tomcat is running...
If you configured SNMP, to verify that the SNMP service is running, enter the following command:
[root@system]# service snmpd status snmpd (pid 2754) is running...
If you configured SNMP, to verify that the Intel SNMP subagent service is running, enter the following command:
[root@system]# service snmpsa status
The SNMP subagent is running.
OL-30119-01
Note This step does not apply to the CDE250.
Step 7
Step 8
Step 9
If you configured SNMP, to verify that the VQE-S subagent service is running, enter the following command:
[root@system]# service vqes_snmpsa status vqes_subagent (pid 28603) is running...
If you configured SNMP, to verify that the Syslog subagent service is running, enter the following command:
[root@system]# service syslog_snmpsa status syslog_subagent (pid 28472) is running...
If you enabled OSPF routing, to verify that the three OSPF-related services are running, enter the following commands:
[root@system]# service watchquagga status
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-39
Chapter 2 Initial VQE Configuration
On the VQE-S Host: Verifying the Status of the VQE and System Services watchquagga (pid 2513) is running...
[root@system]# service ospfd status ospfd (pid 7104) is running...
[root@system]# service zebra status zebra (pid 7072) is running...
Step 10 To verify that the VQE-S service is running, enter the following command:
[root@system]# service vqes status process_monitor (pid 21853) is running...
Step 11 To check that the VQE-S processes are running, enter the following commands:
[root@system]# ps -ef | grep vqe root 710 1 0 Mar24 pts/7 00:00:00 /opt/vqes/bin/process_monitor vqes 723 710 0 Mar24 pts/7 00:00:00 stun_server --ss-uid 499 --ss-gid 499
--xmlrpc-port 8054 --log-level 6 root 782 710 99 Mar24 pts/7 29-21:09:08 vqes_dp --group vqes --max-channels 500
--max-outstanding-rpcs 500 --max-pkts 150000 --log-level 6 --rtp-inactivity-tmo 300
--max-core-bw 850000000 --reserved-core-rcv-bw 100000000 --reserved-core-er-bw 120000000
--max-rai-gap 15 vqes 855 710 0 Mar24 pts/7 00:00:00 vqes_cp --cp-uid 499 --cp-gid 499
--xmlrpc-port 8051 --cfg /etc/opt/vqes/vqe_channels.cfg --er-cache-time 3000
--rtp-hold-time 100 --max-channels 500 --max-outstanding-rpcs 500 --max-queued-rpcs 1000
--max-reserved-rpcs 32000 --max-clients 32000 --er-pkt-tb-rate 50000 --er-pkt-tb-depth 100
--er-blp-tb-rate 10000 --er-blp-tb-depth 100 --client-er-policing
--client-er-tb-rate-ratio 5 --client-er-tb-depth 10000 --log-level 6 --rcc-mode conservative --igmp-join-variability 100 --max-client-bw 0 --max-idr-penalty 0
--rap-interval 2000 --excess-bw-fraction 20 --excess-bw-fraction-high-def 12
--high-def-min-bw 6000000 --buff-size-preroll-max 1500 --rcc-burst-delay-to-send 10
--rtp-dscp 0 --rtp-rcc-dscp -1 --rtcp-dscp 24 --overlap-loss 0 --intf-output-allocation 90
--max-rpr-stream-burst-msecs 30 --max-rpr-stream-burst-pkts 2 --unity-e-factor-interval 5
--min-client-excess-bw-fraction 0 --max-client-excess-bw-fraction 500
[root@system]# ps -ef | grep mlb root 2989 2965 0 09:17 pts/0 00:00:03 mlb --interface eth2,eth3,eth4
--xmlrpc-port 8052 --unicast-reservation 20 --poll-interval 1 --ssm --log-level 6
Step 12
In the preceding output, the VQE-S processes to check for are as follows:
•
•
•
• process_monitor—Process Monitor stun_server—STUN Server vqes_dp—Data Plane vqes_cp—Control Plane
• mlb—Multicast Load Balancer
If you configured an IP address for an external NTP server, to verify that the NTP service is running, enter the following command:
[root@system]# service ntpd status ntpd (pid 2790) is running...
2-40
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
On the VQE Tools Host: Verifying the Status of the VQE and System Services
Step 13 To use the VQE-S AMT from a web browser, enter as the URL the IP address of the Cisco CDE that hosts VQE-S: https://ip_address_of_VQES_host
Step 14
Log in using the vqe username and password. (Any valid Linux username and password can be used to log in to the VQE-S AMT).
If you click System in the left pane, the VQE-S AMT displays information on the VQE-S processes and channels.
Figure 4-2 shows an example. Because at this point no channel information has been sent to
the VQE-S, no channels are displayed.
Do one of the following:
• If the preceding checks indicate that all is well, you are ready to start using VQE-S and VQE-S
AMT. For information, see
Chapter 4, “Using the VQE-S AMT.”
• If one of the preceding checks fails, inspect the configuration of the item that failed and make any needed adjustments. You can get more information on VQE-S host configuration in
“Manual Initial VQE System Configuration.”
On the VQE Tools Host: Verifying the Status of the VQE and
System Services
After the VQE Configuration Tool finishes and the CDE that hosts VQE Tools reboots, it is recommended that you perform some quick checks to ensure that VQE and system services are running.
To verify the status of VQE services on the VQE Tools host, perform the following steps:
OL-30119-01
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
If needed, log in as root.
To verify that the SSH service is running, enter the following command:
[root@system]# service sshd status sshd (pid 21165 21110 20595 20569 2777) is running...
To verify that the HTTP service is running, enter the following command:
[root@system]# service httpd status httpd (pid 9665 9664 9663 9661 9660 9658 9657 9656 3978) is running...
To verify that the Tomcat 5 service is running, enter the following command:
[root@system]# service tomcat5 status
Tomcat is running...
If you configured SNMP, to verify that the SNMP service is running, enter the following command:
[root@system]# service snmpd status snmpd (pid 2754) is running...
If you configured SNMP, to verify that the Intel SNMP subagent service is running, enter the following command:
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-41
Chapter 2 Initial VQE Configuration
Configuring the VQE-S RTCP Exporter
Step 7
Step 8
[root@system]# service snmpsa status
The SNMP subagent is running.
If you configured SNMP, to verify that the VCDS subagent service is running, enter the following command:
[root@system]# service vcds_snmpsa status vqes_subagent (pid 28603) is running...
If you configured SNMP, to verify that the Syslog subagent service is running, enter the following command:
[root@system]# service syslog_snmpsa status
Step 9 syslog_subagent (pid 28472) is running...
If you configured an IP address for an external NTP server, to verify that the NTP service is running, enter the following command:
[root@system]# service ntpd status ntpd (pid 2790) is running...
Step 10 To verify that VCPT is accessible from a web browser, enter as the URL the IP address of the Cisco CDE that hosts VQE Tools: https://ip_address_of_VQE_tools_host
Step 11
Log in with a Linux username and password.
If you are able to log in successfully, VCPT is running correctly.
To use the VCDS AMT from a web browser, enter as the URL the IP address of the Cisco CDE that hosts
VQE Tools: https://ip_address_of_VQE_tools_host/vcds-amt
Step 12
Log in using the VQE username and password. (Any valid Linux username and password can be used to log in to the VCDS AMT.)
If you click System in the left pane, the VCDS Status window displays information on the VCDS processes.
Do one of the following:
• If the preceding checks indicate that all is well, you are ready to start using VCPT. For information, see
Chapter 3, “Using the VQE Channel Provisioning Tool.”
• If one of the preceding checks fails, inspect the configuration of the item that failed and make any needed adjustments. You can get more information on VCPT host configuration in
“Manual Initial VQE System Configuration.”
Configuring the VQE-S RTCP Exporter
VQE-S RTCP Exporter is the VQE-S software component responsible for sending the RTCP reports to an external device that hosts the video-quality monitoring (VQM) application. Use of RTCP Exporter is optional.
2-42
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Configuring the VQE-S RTCP Exporter
Starting with Cisco VQE 3.7 Release, VQE-S supports exporting RTCP reports to one or at most two
VQMs at a time.Also, in this release VQE-S RTCP Exporter can be configured either by vqe_cfgtool or by manually editing vcdb.conf file.
To monitor the RTCP Exporter, use the VQE-S AMT. This tool displays RTCP Exporter configuration details and status as well as counters of exported packets. The VQE-S AMT can also be used to enable or disable RTCP Exporter debugging.
To troubleshoot the RTCP Exporter, examine the Exporter syslog messages, which are sent to the VQE-S log file (/var/log/vqe/vqe.log). If more detailed troubleshooting is needed, enable RTCP Exporter debugging using VQE-S AMT and examine the debug messages, which are also sent to the VQE-S log file.
Starting with Cisco VQE 3.7 release, RTCP exporter can be configured/enabled via the following two methods:
• Manual editing of VCDB file
• Using VQE Configuration tool
Configuring VQE-S RTCP Exporter via manually editing the VCDB File
To configure and enable the RTCP Exporter on the Cisco CDE that hosts VQE-S, follow these steps:
Table 2-10
Step 1
Step 2
Step 3
If needed, log in as root. You must have root privileges to modify the vcdb.conf file and use the VQE
Configuration Tool by executing the following command:
[root@system]# vqe_cfgtool
Edit the /etc/opt/vqes/vcdb.conf file, and specify values for the parameters listed in
, to the file.
For information on manually editing the vcdb.conf file, see the
“Manually Editing the VCDB File” section on page 7-14 .
Save the vcdb.conf file.
RTCP Exporter Parameters
Parameter vqe.vqes.vqm_host="IP_addr_or_domain_name" vqe.vqes.vqm_port="vqm_port_no"
Value Required
IP address or fully qualified Internet domain name of the host on which the VQM application resides. There is no default value.
Note Though this parameter is still supported, Cisco recommends that the user use the new parameter vqe.vqes.vqm_host_port to configure the VQM host IP address and port.
TCP port number on which the VQM application listens for video quality data from RTCP Exporter. Allowed range is 1024 to 65535.
There is no default value.
Note Though this parameter is still supported, Cisco recommends that the user use the new parameter vqe.vqes.vqm_host_port to configure the VQM host IP address and port.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-43
Chapter 2 Initial VQE Configuration
Configuring the VQE-S RTCP Exporter
Table 2-10 RTCP Exporter Parameters (continued) vqe.vqes.vqm_host_port=”IP_addr_or_domain_nam e:vqm_port_no”
The IP address or fully qualified Internet domain name of the host on which the VQM application resides and the TCP port number on which the VQM application listens for video quality data from RTCP
Exporter are specified together as a single variable vqe.vqes.exporter_enable="true_or_false" vqe.vqes.exporter_filter_nack="true_or_false"
Note This parameter is available in the VCDB starting with Cisco
VQE Release 3.7.
Either true or false. The value true enables RTCP exports, and false disables RTCP exports. The default value is false.
Either true or false. The value true excludes RTCP NACK compound packets from being exported to the VQM application, and false includes RTCP NACK compound packets in the RTCP data being exported.
This parameter is available in the VCDB starting with Cisco VQE
Release 3.5.5.
Step 4
RTCP Exporter remains disabled unless both VQM Host IP Address and Port are configured and are valid.
By default, the vcdb.conf file contains no RTCP Exporter parameters and RTCP Exporter is disabled.
To apply the RTCP Exporter parameter values to the /etc configuration files and restart the VQE-S, enter the following command:
[root@system]# vqe_cfgtool -apply
For more information on the vqe_cfgtool command and the -apply option, see the
Configuration Tool Command-Line Options” section on page 7-18
.
Note The vqe_cfgtool command with -apply asks you if you want to restart VQE-S. When RTCP Exporter parameters are added or modified, this restart is required for the new or changed parameter values to take effect.
Configuring VQE-S RTCP Exporter via VQE Configuration Tool
You can also configure VQE-S RTCP Exporter via VQE Configuration Tool.
The following example shows how to configure VQE-S RTCP Exporter:
VQE Configuration Tool <VQE-S Parameters> Menu:
1) Log Priority: 6
2) Excess Bandwidth Fraction: [20]%
3) Traffic (Ingest+Service) Interface(s): eth2,eth3,eth4,eth5,eth6
4) Ingest Interface(s): []
5) Service Interface(s): []
6) RTCP Exporter Parameters:
R) Go to Root Menu
To reset a parameter to its factory default value, enter its number choice followed by the letter 'd' (e.g. 3d). Default values are displayed inside
2-44
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Configuring the VQE-S RTCP Exporter square brackets [].
Enter your choice:6
VQE Configuration Tool <RTCP Exporter Parameters> Menu:
1) Enable Exporter: [false]
2) Enable NACK Filter: [false]
3) VQM Parameters:
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default value, enter its number choice followed by the letter 'd' (e.g. 3d). Default values are displayed inside square brackets [].
Enter your choice: 1
Enable Exporter?: y/[n] y
VQE Configuration Tool <RTCP Exporter Parameters> Menu:
1) Enable Exporter: true
2) Enable NACK Filter: [false]
3) VQM Parameters:
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default value, enter its number choice followed by the letter 'd' (e.g. 3d). Default values are displayed inside square brackets [].
Enter your choice: 2
Enable NACK Filter?: y/[n] y
VQE Configuration Tool <RTCP Exporter Parameters> Menu:
1) Enable Exporter: true
2) Enable NACK Filter: true
3) VQM Parameters:
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default value, enter its number choice followed by the letter 'd' (e.g. 3d). Default values are displayed inside square brackets [].
Enter your choice: 3
Configure the VQM host(s) for RTCP Exporter reports. VQM parameter must be added as a colon separated field "host:port", where host is the IP address or host name of the VQM, and "port" is the port number. For multiple VQMs, enter one VQM parameter per line. Maximum number of VQMs supported is 2.
To complete the configuration, press <Enter> at the prompt without entering data. Usage example: 127.0.0.1:3000
Enter VQM information as "host:port":123.0.0.98:4000
Enter VQM information as "host:port":134.98.78.67:6000
VQE Configuration Tool <RTCP Exporter Parameters> Menu:
1) Enable Exporter: true
2) Enable NACK Filter: true
3) VQM Parameters:
3.1) 123.0.0.98:4000
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 2-45
Chapter 2 Initial VQE Configuration
Configuring the Other Parameters for the VQE-S Host
3.2) 134.98.78.67:6000
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default value, enter its number choice followed by the letter 'd' (e.g. 3d). Default values are displayed inside square brackets [].
Enter your choice: r
VQE Configuration Tool Root Menu:
1) System Parameters
2) Network Parameters
3) VQE-S Parameters
S) Save and Exit
A) Save/Apply and Exit
E) Exit without saving
Enter your choice:A vcdb.conf is successfully updated.
Applying this configuration will cause the following service interruptions:
Restart of VQE services (process_monitor) for configuration change.
Do you want to proceed and apply these changes?: y/[n] y
Configuring the Other Parameters for the VQE-S Host
The set of parameters for the VQE-S host includes many parameters that are not configurable with the
VQE Configuration Tool. Many additional parameters are used, for example, to make adjustments to the
VQE-S software facilities that perform Unicast Retransmission and RCC.
Read the following to get information on these additional parameters:
•
•
•
Chapter 7, “Configuring VQE Server and VQE Tools” describes the tools and procedures used to
configure all parameters for a VQE-S or VQE Tools system.
Appendix A, “VQE, System and Network Parameters”
describes the VQE-S, system, and network parameters.
File /etc/vqes/vcdb.conf.sample provides additional information on the VQE-S, system, and network parameters.
Configuring the Edge Router for VQE-S
This section provides some guidance on configuring the edge router that is directly attached to the
VQE-S host. Depending on whether OSPF routing or static routes are used on the VQE-S host, refer to one of the following sections:
•
For Bond Interfaces: Guidance for Configuring Bond Interface on the Attached Router, page 2-47
•
•
For OSPF Routing: Guidance for Configuring the Attached Router, page 2-48
For Static Routes: Guidance for Configuring the Feedback Targets on the Attached Router, page 2-50
2-46
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Configuring the Edge Router for VQE-S
For Bond Interfaces: Guidance for Configuring Bond Interface on the Attached
Router
This section provides guidance on manually configuring bond interfaces (EtherChannels) on the edge router that is directly attached to the VQE-S. This section assumes that the attached router is a Cisco
7600 running Cisco IOS software. A bond interface is referred to by the terms EtherChannel and
port-channel group on a Cisco 7600 router. A port-channel is used to group up to four Ethernet interfaces. It aggregates the bandwidth of the underlying Ethernet interfaces. All Ethernet interfaces must have the same speed.
To configure a port-channel on the Cisco 7600 router, do the following:
Step 1
Step 2
Step 3
Step 4
Create a port-channel group.
interface port-channel channel-number
The channel-number is the number assigned to this port-channel interface. As each channel can consist of up to four Ethernet interfaces, the valid range is 1 to 4.
Assign an IP Address and subnet mask to the port-channel group.
ip address ip-address mask
Assign Ethernet interfaces to the port-channel group.
interface fastethernet number
Enable the EtherChannel by specifying the port-channel number and setting the mode to ‘on’.
channel-group number mode ON
The EtherChannel has been statically configured without running dynamic protocols, such as Link
Aggregation Control Protocol (LACP) or Port Aggregation Protocol (PAgP).
In the following example, the port-channel 1 is assigned an IP address and network mask. Next, the
Ethernet port 1 and Ethernet port 2 on module 8 are assigned to port-channel 1. Finally, the EtherChannel is enabled.
7600# configure terminal
7600(config)# interface port-channel 1
7600(config-if)# ip address 1.1.1.10 255.255.255.0
7600(config-if)# exit
7600(config)# interface GigabitEthernet 8/1
7600(config-if)# channel-group 1 mode on
7600(config-if)# exit
7600(config)# interface GigabitEthernet 8/2
7600(config-if)# channel-group 1 mode on
7600(config-if)#
To display EtherChannel information, use the following command:
show etherchannel [channel-group] {port-channel | brief | detail | summary | port | load-balance |
protocol}
The following example displays a summary of information for etherchannel 2.
7600# show etherchannel 2 brief
Group: 2
----------
Group state = L2
Ports: 4 Maxports = 8
Port-channels: 1 Max Port-channels = 1
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-47
Chapter 2 Initial VQE Configuration
Configuring the Edge Router for VQE-S
Protocol: - (Mode ON)
7600#
For more information on the commands used to configure EtherChannels on a Cisco 7600 router, see the
Cisco 7600 Series Router Cisco IOS Command Reference Guide.
For OSPF Routing: Guidance for Configuring the Attached Router
If OSPF routing is enabled for VQE-S traffic or VQE-S services traffic, the following sections provide guidance on configuring the edge router that is directly attached to VQE-S:
•
•
VQE-S in a Separate OSPF Area, page 2-48
•
For detailed information on OSPF and the Cisco IOS commands used to configure the routing protocol, see the OSPF resources at: http://www.cisco.com/en/US/tech/tk365/tk480/tsd_technology_support_sub-protocol_home.html
Note In the following sections, Cisco IOS commands are used for some of the configuration examples.
However, there is no requirement that a Cisco router be used as the edge router.
VQE-S in a Separate OSPF Area
The VQE-S can be configured to be in a separate OSPF area by specifying the VCDB parameter network.ospf.area to be a non-zero value. With the VQE Configuration Tool, this separate area with the
VQE-S can be defined as a normal area or a Not So Stubby Area.
Figure 2-4 shows the VQE-S in a
separate OSPF area: area 1.
Figure 2-4 VQE-S in a Separate OSPF Area
Separate OSPF area: area 1 Access backbone: area 0
Feedback target addresses /32
To access network
VQE-S server Edge router
When the VQE-S is configured in a separate OSPF area, these guidelines for configuring the directly attached edge router apply:
• Configure the edge router interfaces attached to the VQE-S in the same OSPF area as the VQE-S host.
• To keep the routing table on the VQE-S small in size, configure the separate area (in
, area
1) to be a Not So Stubby Area (NSSA). The VQE-S must also be configured so that its OSPF area type is a NSSA by specifying the VCDB parameter network.ospf.area_type to have the value “nssa”.
2-48
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 2 Initial VQE Configuration
Configuring the Edge Router for VQE-S
With a NSSA, the edge router generates a default route to the access network and advertises the default route in the NSSA (in
Figure 2-4 , area 1). This default-route mechanism reduces the size of the VQE-S
routing table.
To configure the NSSA and to configure the edge router to advertise the default route in the NSSA, issue the following Cisco IOS commands on the edge router:
router ospf process-id
area area-id nssa no-summary
When no-summary is specified with area nssa, the edge router advertises the default route in the NSSA but does not inject summary routes into the area.
VQE-S in Area 0
When the VQE-S is configured within OSPF area 0 (that is, when the network.ospf.area VCDB parameter value is zero, the default), these guidelines for configuring the directly attached edge router apply:
•
•
Configure the edge router interfaces to the VQE-S host to be within OSPF area 0.
With this configuration, the VQE-S host routing table may be very large depending on the size of the network visible in area 0. If this is a concern, one suggestion is to configure the VQE-S host interfaces to be in a separate OSPF area, see the
“VQE-S in a Separate OSPF Area” section on page 48
.
General Guidelines
The following are general edge router configuration guidelines:
•
•
•
Feedback target routes—Feedback target (FBT) routes that are advertised from the VQE-S to the edge router should not be summarized by the edge router if multiple VQE-Ss exist in the network and high availability of VQE-S services is desired. The reason for this is that each FBT route advertises VQE-S services for a particular channel, and if the services for that channel become unavailable on a VQE-S, that VQE-S withdraws the route. This allows another VQE-S in the network to take over services for that channel. However, if the FBT routes are summarized by the edge router, the FBT routes cannot be added and withdrawn individually. Thus, redundancy is lost because a VQE-S may still get service requests for a channel that is not available.
Fast convergence—If fast convergence in the case of link failure or other causes in the network is a concern, set the VCDB parameter network.ospf.hello_interval on the VQE-S to the lowest possible setting, which is one second. Also, set the same hello interval value for each VQE-S interface on the edge router. This allows a link failure to be detected as quickly as possible between the VQE-S and the edge router. A general rule of thumb when changing the default hello interval is to set the dead interval to be four times the hello interval. Therefore, the VCDB parameter network.ospf.dead_interval should be set to four seconds, and a corresponding change must be made on the edge router for each VQE-S traffic interface. For each interface, the Cisco IOS commands on the edge router are as follows:
interface name
ip ospf hello-interval 1
ip ospf dead-interval 4
Interface authentication—If MD5 authentication is desired between OSPF peers, all VQE-S traffic interfaces must have the same key value and key ID when the VCDB parameters network.ospf.md5_key and network.ospf.md5_keyid are set. Therefore, the same MD5 key value and MD5 key ID must be configured on the edge router for all traffic interfaces to the VQE-S.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
2-49
Chapter 2 Initial VQE Configuration
Configuring the Edge Router for VQE-S
•
•
•
•
VQE-S redundancy—All VQE-Ss in the network must be configured to use the same routing type: either all must be static or all must be ospf. This is required for anycast ECMP across multiple
VQE-Ss to work properly.
Forwarding table—Size of the forwarding table on the edge router may be restricted, which limits the number of VQE-Ss that can participate in anycast ECMP properly. On a Cisco 7600 router, the size of the forwarding table can be increased to allow more VQE-Ss and more traffic interfaces per
VQE-S using the following commands:
router ospf process-id
maximum-paths maximum-paths
Directly connected VQE-S—VQE-S must be directly connected to the edge router on all VQE-S traffic or VQE-S services interfaces. Specifically, OSPF virtual links are not allowed.
For information on configuring the edge router to generate and advertise a default route into a Not
So Stubby Area, see the
“VQE-S in a Separate OSPF Area” section on page 48 .
For Static Routes: Guidance for Configuring the Feedback Targets on the
Attached Router
When channels are configured with a channel-provisioning tool such as VCPT, it is required that you specify a unique feedback target (FBT) address for each channel. If static routes are used for VQE-S traffic (ingest and services) or VQE-S services traffic, the router that is directly attached to the VQE-S host must have a static route configured for the FBT address so that the router can reach the target. If the
FBT addresses are allocated within a contiguous address range, this configuration piece can be done with a single aggregated route.
For example, if the FBT addresses for the channels are assigned to be 8.86.1.1, 8.86.1.2, 8.86.1.3, ...,
8.86.1.250, then the single static route 8.86.1.0/24 configured on the directly attached router allows any of these FBT addresses to be reached. The commands on the router for the FBT addresses would be as follows: configure terminal ip route 8.86.1.0 255.255.255.0 10.2.9.2 ip route 8.86.1.0 255.255.255.0 10.2.10.2 ip route 8.86.1.0 255.255.255.0 10.2.11.2 ip route 8.86.1.0 255.255.255.0 10.2.12.2
For the preceding configuration example, the IP addresses 10.2.9.2, 10.2.10.2, 10.2.11.2, and 10.2.12.2 have been assigned to the Ethernet interfaces on the VQE-S host. See
interfaces are used for VQE-S traffic, including Unicast Retransmission and RCC traffic.
2-50
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
C H A P T E R
3
Using the VQE Channel Provisioning Tool
This chapter describes how to use Cisco VQE Channel Provisioning Tool (VCPT).
tasks you perform with the VCPT. When you use VCPT for the first time, the required tasks are performed in the order shown in the table.
VCPT Tasks Table 3-1
VCPT Task
1.
2.
3.
Log in to VCPT
Create a new VCPT configuration file
Provision VQE channels
4.
Create VQE Servers (VQE-S), VQE Client
Configuration Delivery Servers (VCDSs), or Remote
Servers
5.
6.
Specify channel associations for the VQE-Ss, VCDSs, or Remote Servers
Send the channel information file to the VQE-Ss,
VCDSs, or Remote Servers
Section Where Described
Working with VCPT Configuration Files, page 3-3
Provisioning VQE Channels, page 3-7
Defining VQE-Ss, VCDSs, or Remote Servers, page 3-14
Defining Channel Associations, page 3-18
Working with VCPT Configuration Files, page 3-3
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-1
Chapter 3 Using the VQE Channel Provisioning Tool
Logging into VCPT
Logging into VCPT
Before logging into the VCPT, you need a valid UNIX username and password on the Cisco CDE hosting the VCPT. The username does not have to belong to any special group. Creation of the username is the responsibility of the Cisco CDE system administrator.
The VCPT supports two web browsers: Microsoft Internet Explorer version 6.0 or later, and Mozilla
Firefox version 2.0 or later. The VCPT uses secure HTTPS. The minimum screen resolution required for
VCPT is 1024 x 768 pixels.
To log in to a VCPT, follow these steps:
Step 1
Step 2
Step 3
Point your web browser to the Cisco CDE that hosts the VCPT using an IP address or fully qualified domain name: https://ip_address
or https://fully_qualified_domain_name
The VQE login dialog box is displayed.
Enter a UNIX username and password.
Click OK.
If the username and password are valid, the VCPT main window is displayed.
If you log in to the VCPT when another person is using the same VCPT, the message shown in
is displayed and your access to the VCPT is a read-only view. To get read-write access, wait and try to open a VCPT session at a later time when no one else is using the tool.
Figure 3-1 Read-only View Message
With certain versions of Microsoft Internet Explorer 6, if you close a read-write session and try to open it again immediately, you get a read-only view. In this case, wait a minute and open another session to get read-write access.
When you are finished using the VCPT, click the Logout button on the right side of the banner so that another user can get read-write access to the tool.
VCPT sessions are timed out after 25 minutes of inactivity. If VCPT detects a network failure or server failure, the session is timed out after one minute.
3-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 3 Using the VQE Channel Provisioning Tool
Working with VCPT Configuration Files
Working with VCPT Configuration Files
The VCPT channel, server, and association provisioning information is stored in a persistent local database on the Cisco CDE server. When the Cisco CDE or the VCPT is restarted, channel, server, and association data are read from the local database. The VCPT configuration file can be saved at any time and should be saved frequently to store your work.
Caution If a VCPT session times out because of inactivity or because of a server or network failure, unsaved data is lost. Therefore, you should save the VCPT configuration file frequently.
File management tasks for the VCPT are the responsibility of the VCPT user. The directories that the
VCPT uses for its data files are as follows:
•
•
VCPT configuration files are stored in the /etc/opt/vcpt/data directory.
SDP-formatted files that the VCPT creates for each valid VCPT configuration are stored in the
/etc/opt/vcpt/data/sdp directory.
If the /etc/opt/vcpt/data or /etc/opt/vcpt/data/sdp directory is deleted accidentally and does not exist at startup, VCPT fails to initialize. The missing directory must be recreated. For information on the remedy procedure, see the
“VCPT Fails to Initialize” section on page 6-12
.
Caution The VCPT configuration files must be backed up in a safe location that is not on the local Cisco CDE disk. If a server or software failure occurs, the latest VCPT configuration file must be retrievable from the backup location.
When the user completes channel and server configuration, and initiates the VCPT send operation, the
VCPT sends the channel information in Session Description Protocol (SDP) format to the set of VQE-Ss and VCDSs. As an alternative to the VCDS, the channel information may be sent in SDP format to one or more user-specified remote servers using a password-less secure copy (SCP) mechanism.
Figure 3-2 shows the buttons that you use for working with VCPT configuration files and for sending
channel information.
Figure 3-2 VCPT Configuration File Operations
OL-30119-01
The following sections explain the configuration file and channel information operations:
•
Performing Configuration-File Operations, page 3-4
•
•
Sending or Pushing Channel Information to Servers, page 3-5
Sending Channel Information to a Subset of Servers, page 3-7
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-3
Chapter 3 Using the VQE Channel Provisioning Tool
Working with VCPT Configuration Files
Performing Configuration-File Operations
The VCPT configuration file buttons used for non-push operations are:
• New Config—Clears the current configuration (if any) so that you can start a new one. The new configuration is not saved until you click Store, specify a file name, and click OK.
•
•
Import—Clears the current configuration (if any), and imports a configuration from a file that you specify that is located on the VQE Tools server. The configuration file is in either XML (Extensible
Markup Language) or CSV (text-based, comma-separated values) format.
Open Configuration—Allows you to choose an existing configuration file from the pull-down menu and open it. If needed, you should save the current configuration file before opening another one because any unsaved data in the current configuration file is lost.
•
•
•
Store—Saves the current configuration file on the Cisco CDE that hosts VCPT.
Store As—Saves the current file under a new file name that you specify.
Export—Exports the current configuration to a file in the format you specify. The format is either
XML or CSV.
Delete—Deletes the current configuration file and clears the configuration. •
When the current VCPT configuration is changed but the changes have not been saved, an asterisk is displayed beside the configuration filename (for example, bellini.xml*).
Names for VCPT Configuration Files
The name for a VCPT configuration file can be up to 60 characters long and use lowercase a to z, uppercase A to Z, numeric characters 0 to 9, and the underscore (_), hyphen (-), and period (.) characters.
No spaces are allowed in the name.
Importing a Configuration
To create a VQE channel configuration in the VCPT without manually entering the data, you can import the required information from an external file. The file can be located in any directory on the VQE Tools server as long as the file has the correct permissions. However, the file must be in a valid format. For information on VCPT configuration file formats, see
Appendix I, “VCPT Configuration Files.”
To import a configuration, do the following:
Step 1
Step 2
Click Import.
The Import dialog box, shown in
Figure 3-3 Import dialog
3-4
Step 3 Enter the full path name and extension (xml or csv) of the configuration file, and click OK.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 3 Using the VQE Channel Provisioning Tool
Working with VCPT Configuration Files
The VCPT clears the current configuration (if any) and displays the contents of the imported file. If the file is in XML format, the VCPT validates the file against the XML schema, vcpt_doc.xsd, prior to importing.
Exporting a Configuration
A VQE channel configuration can be exported to an external file you specify. The file can be in any directory on the VQE Tools server as long as the file has the correct permissions. Currently only two formats are supported by the VCPT; XML and CSV format. For information on the VCPT configuration file formats, see
Appendix I, “VCPT Configuration Files.”
To export a VCPT configuration, do the following:
Step 1 Click Export.
The Export dialog box, shown in
, is displayed.
Figure 3-4 Export dialog
Step 2 Enter a full path, file name and file extension (xml or csv), and click OK.
The VCPT exports the VCPT configuration to this file.
Sending or Pushing Channel Information to Servers
The VCPT buttons used to send or push channel information to VQE-Ss , VCDSs, or remote servers are the Send and Force Update buttons.
Send Button
Use the Send button to send channel information in the current configuration file to the VQE-Ss,
VCDSs, or remote servers that have been defined.
Note Use the Send button for “normal” configuration file changes where the changes modify the base file that was most recently pushed to the servers.
Note Using the Send button causes temporary disruption to Unicast Retransmission services for modified channels while the VQE-S cache used for packet retransmission on the modified channels is flushed.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-5
Chapter 3 Using the VQE Channel Provisioning Tool
Working with VCPT Configuration Files
The channel information to send is based on the channel associations that have been defined for the
VQE-Ss, VCDSs, or remote servers. When channel information is sent to a set of servers, VCPT saves the current configuration file. The send operation does not succeed if any channel has misconfiguration issues. When channel information is sent to servers, the VCPT displays the following:
• Status line next to the configuration file name is updated (for example,
Last update was sent to
1 out of 2 servers at: 5/11/2007 14:47:20
).
•
•
Status message is displayed: either “Send Complete” or, if the send operation fails, the message text
.
On the Servers tab, the Status of Last Send column is updated with information on the send operation. For a description of the status values that can appear in this column, see the
Updating Server Information” section on page 17
.
You can get more details on a send failure by examining the VCPT log file, which is located in
/usr/share/tomcat5/logs/vcpt.log.
Figure 3-5 Status Message for Failed Send Operation
Force Update Button
Note Using the Force Update button causes temporary disruption to Unicast Retransmission and Rapid
Channel Change (RCC) services for all channels while the VQE-S cache used for packet retransmission is flushed.
For the following types of configuration file changes, use the Force Update button to send the channel information to the VQE-Ss and VCDSs.
• Configuration file changes where you are reverting to an old version of the configuration file (older that the most recently pushed configuration file)
•
•
Configuration file changes where the changes modify some file other than the base file that was most recently pushed to the servers
Configuration file changes when you are not certain whether the file used was the base file that was most recently pushed to the servers
If configuration information is sent to the servers and the changes to channel information are not present on the servers after the send, you can use the Force Update button to force the channel information changes to be accomplished on the servers.
3-6
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 3 Using the VQE Channel Provisioning Tool
Provisioning VQE Channels
Sending Channel Information to a Subset of Servers
To send a channel information file to a subset of servers, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Open an existing VCPT configuration file that has the needed server, channel, and association information.
Click Save As to save the VCPT configuration file using a new file name.
On the Servers tab, adjust the servers list by deleting the VQE-Ss, VCDSs, and remote servers that are not wanted.
Click Store to save the VCPT configuration file.
Click Send to send the channel information file to the adjusted list of VQE-Ss, VCDSs, and remote servers.
Provisioning VQE Channels
In the Cisco VCPT, use the Channels tab to add a new channel, clone an existing channel, delete an existing channel, and get detailed information on an existing channel. The number of channels supported by single VQE-S is determined by the ingest capacity of the CDE server. For VQE-S performance information, see
Appendix H, “VQE Server Performance and Scaling Limits”
When you click the Channels tab, VCPT displays summary information on all channels that have been created. An incomplete channel is displayed in red. The Reduced Size RTCP Reports Enabled column show in
Figure 3-6 is available starting with Cisco VQE Release 3.5.5.
Figure 3-6 Channels Summary
OL-30119-01
From the Channels tab, you can do the following:
•
•
•
Click Incomplete Channels or Valid Channels to display only the corresponding subsets of channels.
Click a column heading to reorder the channels in the list. For example, clicking Feedback Target orders the entries by feedback target: the combination of IP address and RTCP port number.
Double-click any item in a channel’s row to display the full details for the channel in a new window.
You can update the channel information.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-7
Chapter 3 Using the VQE Channel Provisioning Tool
Provisioning VQE Channels
•
•
Click Add to display a dialog box so that you can create a new channel.
Click a channel to select it and then use one of the following buttons:
– Details—Displays a dialog box with detailed information on an existing channel and allows you to update the information.
–
–
Clone—Displays a dialog box with appropriate cloned information from an existing channel so that you can use the information to create a new channel.
Delete—Deletes an existing channel.
On the Channels summary, the Error Repair Options column indicates the types of repair that have been configured for the channel.
Table 3-2 shows the Error Repair Options column.
Table 3-2 Error Repair Options
Option
None
Description
No Error Repair.
Unicast Retransmission Only VQE-S provides selective retransmission of dropped IPTV packets to repair errors.
1-D FEC Only VQE-C provides 1-dimension FEC.
2-D FEC Only
1-D FEC Hybrid
2-D FEC Hybrid
VQE-C provides 2-dimension FEC.
Unicast retransmission and 1-dimension FEC are provided.
Unicast retransmission and 2-dimension FEC are provided.
The sections that follow provide more information on the tasks that can be performed from the Channels tab.
Adding a Channel
In the VCPT channel definition, each channel is associated with a unique feedback target (FBT) IP address. The feedback target address is a unique IP anycast address that VQE-S configures on its host
Cisco CDE based on the channel information that is sent to it by the VCPT. An anycast address is a unicast address that is assigned to multiple interfaces. With the appropriate routing topology, packets addressed to an anycast address are delivered to a single interface (in this case, the nearest VQE-S’s CDE interface that is identified by the address). The use of anycast addresses to identify feedback targets is useful for VQE-S redundancy.
Note When channels are configured with VCPT, it is required that you specify a unique feedback target (FBT) address for each channel. The router that is directly attached to the VQE-S host must have a static route configured for the FBT address so that the router can reach the target.
For information on configuring the FBT IP addresses on the router that is attached to the CDE hosting
3-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 3 Using the VQE Channel Provisioning Tool
To add a channel, follow these steps:
Step 1 On the Channels tab, click Add.
The New Channel dialog box, shown in
Figure 3-7 New Channel Dialog Box
Provisioning VQE Channels
Step 2 Fill in the information for the new channel.
has information on the fields that you need to complete.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-9
Chapter 3 Using the VQE Channel Provisioning Tool
Provisioning VQE Channels
Table 3-3 VQE Channel Details
VCPT Field
Channel Name
Description
String having 1 to 40 alphanumeric characters.
Feedback Target IP Unique anycast IP address on the VQE-Ss that provide services for this channel. Using the Feedback Target IP address that is sent to it by the VCPT in the channel information, the VQE-S automatically configures the specified address on one of its Cisco CDE interfaces.
Channel Features
Enable RTCP RTCP must be enabled to use Error Repair (Unicast Retransmission),
RCC, Video-Quality Monitoring (RTCP Exporter and RTCP Extended
Reports), or to have VQE-S display video-monitoring statistics.
Enable Error Repair
Enable Rapid Channel Change Check to enable RCC.
Enable Extended RTCP
Reports
Check to enable RTCP Extended Reports.
Enable Reduced Size RTCP
If Enable RTCP is not checked, the Enable Error Repair, Enable RCC, and Enable RTCP Extended Reports check boxes are grayed out.
Check to enable Error Repair (Unicast Retransmission). You also need to complete the Unicast Retransmission Stream fields.
Enable FEC 1 Stream
Enable FEC 2 Stream
Check to enable sending RTCP NACK compound packets to the
VQE-S without Receiver Reports (RRs).
Check to enable 1-dimension FEC. You also need to complete the
FEC 1 Stream fields.
Check to enable 2-dimension FEC. You also need to complete the
FEC 2 Stream fields.
Original Stream
Multicast IP
RTP Port
Multicast IP address for the original source stream of the channel. The first octet must be within the range of a valid multicast address. The multicast address must be unique for each channel.
RTP port number of the original source stream of the channel.
RTCP Port
Source IP
The RTCP port number of the original source stream of the channel.
By default, RTCP Port is the (RTP/UDP) port number plus one.
IP address of the original source stream of the channel.
Bit Rate
Note A channel may be defined with a Source IP address of 0.0.0.0 for the Original Stream. When the channel Source IP address is 0.0.0.0 for the Original Stream, the SDP entry for this channel does not include the source-filter line in the original stream section that would be used to perform a Source
Specific Multicast (SSM) join. In this case, the VQE-S and
VQE-C does not perform a SSM join.
Bit rate of the original source stream of the channel in kilobits per second. This parameter defines how many packets the VQE-S accepts and sends for this multicast stream.
Note The specified bit rate should be equal to the primary stream bandwidth but should not include bandwidth used for FEC.
3-10
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 3 Using the VQE Channel Provisioning Tool
OL-30119-01
Provisioning VQE Channels
Table 3-3 VQE Channel Details (continued)
VCPT Field Description
Unicast Retransmission Stream
Source IP IP address of the Unicast Retransmission stream. The IP address must be the same as is defined for Feedback Target IP.
RTP Port
RTCP Port RTCP port number of the unicast retransmission stream. By default,
RTCP Port is a valid port number.
FEC 1 Stream and FEC 2 Stream
Source IP
RTP port number of the unicast retransmission stream. By default,
RTP Port is a valid port number.
IP address of the source stream of the channel. By default, this is the
IP address of the Source IP specified for the Original Stream.
Multicast IP
RTP Port
Note A channel may be defined with a Source IP address of 0.0.0.0 for the FEC Stream. When the channel Source IP address is
0.0.0.0 for the FEC Stream, the SDP entry for this channel does not include the source-filter line in the FEC section that would be used to perform a SSM
1
join. In this case, the VQE-S and VQE-C does not perform a SSM join.
IP address of the multicast stream of the channel. By default, this is the IP address of the Multicast IP specified for the Original Stream.
RTP port number of the FEC stream. The port number specified cannot be the same as the port number used for the RTP or RTCP port for the Original Stream.
1.
SSM = source specific multicast.
Rules When Adding a Channel. The following rules apply when adding a channel:
• Feedback Target IP address must be unique for each channel.
•
•
•
For the Original Stream, the Multicast IP address must be unique for each channel. That is, the address cannot be used by another channel as its Original Stream Multicast IP address.
For the Original Stream, the Source IP address must not be equal to the Feedback Target IP address.
•
•
•
•
FEC 1 Stream and FEC 2 Stream RTP port numbers cannot be the same as the port numbers used for the Original Stream RTP or RTCP ports.
In any given stream, the RTP port number must not be equal to the RTCP port number.
Configuring a FEC 1 Stream or a FEC 2 Stream provides 1-dimension FEC for the channel.
Configuring a FEC 1 Stream and a FEC 2 Stream provides 2-dimension FEC for the channel.
•
If you enter invalid data, the field name is displayed in red. You must correct the invalid data before creating or updating the channel.
If you enter incomplete data, you can create or update the channel, but it is marked incomplete.
• Channel configuration file with an incomplete channel definition cannot be sent to VQE-Ss, remote servers, or VCDSs.
Port Usage Recommendations. When the STUN Server is enabled on a VQE-S (the default and recommended mode), one set of four unique port numbers can be used for all channels for the following:
• Original Source RTP Port
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-11
Chapter 3 Using the VQE Channel Provisioning Tool
Provisioning VQE Channels
•
•
•
Original Source RTCP Port
Unicast Retransmission Stream RTP Port
Unicast Retransmission Stream RTCP Port
Note If the STUN Server is not enabled, each channel must be configured with unique port numbers for the each of the preceding items. The STUN server is not enabled only when no set-top boxes (STBs) being serviced by VQE-S are behind NAT devices.
Step 3 When you have specified all required values, click Create to create the new channel, or click Cancel to exit the dialog box without creating the new channel.
Viewing or Updating Channel Information
To view or update channel information, follow these steps:
Step 1
Step 2
On the Channels tab, click the channel you want to view or update.
Click Details.
The Details dialog box, shown in
Figure 3-8 , is displayed. The Reduced Size RTCP Reports Enabled
column show in
Figure 3-8 is available starting with Cisco VQE Release 3.5.5.
Figure 3-8 Details Dialog Box
Step 3
Step 4
If needed, change or add channel information.
Do one of the following:
• Click Update to update the channel information.
• Click Cancel to close the dialog box without updating the channel information.
3-12
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 3 Using the VQE Channel Provisioning Tool
Provisioning VQE Channels
Cloning a Channel
To clone a channel, follow these steps:
Step 1
Step 2
Step 3
Step 4
On the Channels tab, click the channel you want to clone.
Click Clone.
The Clone dialog box is displayed. Only appropriate information from the existing channel is cloned.
Verify that the cloned values are what you require. Where needed, change the values and add channel information.
Do one of the following:
• Click Create to create the new channel.
• Click Cancel to close the dialog box without creating the new channel.
Deleting a Channel
To delete a channel, follow these steps:
Step 1
Step 2
Step 3
Step 4
On the Channels tab, click the channel you want to delete.
Click Delete.
A dialog box asking if you want to delete the channel is displayed.
Do one of the following:
• Click Delete to delete the channel.
• Click Cancel to close the dialog box without deleting the channel.
If you clicked Delete, a confirmation dialog box is displayed. Click OK.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-13
Chapter 3 Using the VQE Channel Provisioning Tool
Defining VQE-Ss, VCDSs, or Remote Servers
Defining VQE-Ss, VCDSs, or Remote Servers
The Cisco VCPT requires that you provide information on each VQE-S, each VCDS, and each remote server that receives channel configuration information from the VCPT.
If you choose to send channel information to a remote server, you must install a SSH public key in .ssh directory of the authorized user on the remote server. For more information on generating the SSH public key, see the
“Setting-up a SSH Certificate on a Remote Server” section on page 19 .
Note The system integrator must ensure that the generated public key is stored in the authorized_keys file in
.ssh directory of the authorized user for channel configuration files to be transferred successfully to the remote server.
In the VCPT, use the Servers tab to add a new server, delete an existing server, and get information on an existing server. When you click the Servers tab, the VCPT displays summary information, shown in
, on all servers that have been created.
Figure 3-9 Servers Summary
From the Servers tab, you can do the following:
• Click a column heading to reorder the servers in the list. For example, clicking Status of Last Send orders the servers by their channel configuration file status.
•
•
•
Double-click any item in a row representing a server to display the full details for the server in a new window. You can update the server information.
Click Add to display a dialog box so that you can create a new server.
Click a channel to select it and then use one of the following buttons:
–
–
Details—Displays a dialog box with detailed information on an existing server and allows you to update the information.
Delete—Deletes an existing server.
On the Servers tab, the following columns provide useful information on the servers.
• Number of Channels Currently Associated column shows how many channels are currently associated with a server in the current configuration—whether or not that configuration has been saved. If the current channel information in VCPT has not been sent to the server, the Number of
Channels Currently Associated can be different from the number shown as “Received” in the Status of Last Send Column.
3-14
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 3 Using the VQE Channel Provisioning Tool
Defining VQE-Ss, VCDSs, or Remote Servers
• Status of Last Send column provides information on the last attempt by VCPT to send channel configuration information to the server.
Table 3-4 lists the possible messages. The result is either
Success or Failed plus some additional information. The following examples explain some of the additional information that can be provided in the Status of Last Send column:
Success - Received 4 channels: 0 channels deleted; 1 channels restarted; and 0 new channels created
The preceding Success status indicates the send operation succeeded: A VQE-S received four channel definitions; zero channels were deleted; one channel definition was modified and the channel was restarted; zero new channels were created.
Failed - 0 out of 4 channels failed to validate; 1 channels having the old version; and 0 channels having the same version but contents being changed
The preceding Failed status indicates the send operation failed: all channel definitions have valid
SDP format; one channel definition is an older version of the channel; zero channels have the same version (when compared to the VQE-S or the current version of the VCPT server) but with a changed channel definition.
Note The “channels having the same version but contents being changed” error condition is present only when the SDP definition for the channels has been incorrectly coded by manual modifications or by a channel-provisioning tool other than VCPT.
Table 3-4 Status of Last Send Messages
Message Explanation
Success - additional_information Send operation succeeded. The additional_information provides details on the send operation.
Failed - additional_information Send operation failed. The additional_information provides details on the reasons for the failure.
Failed - Network Error
Failed - Connection refused
VCPT did not receive any error message back from the VQE-S, the VCDS, or the remote server.
See the
“Channel-Provisioning Server Cannot Send Channel
Information to VQE-S: Trusted Provisioning Client Problem” section on page 6-13 .
Failed - Unable to find valid certification path to requested target
See the
“Channel-Provisioning Server Cannot Send Channel
Information to VQE-S: SSL Certificates Problems” section on page 6-13
.
Failed - Unable to connect with
Server
Failed - Security Exception
Failed - Invalid EMS Address
Failed - VCPT Server Error
Failed - Channel config file is not writable
See the
“Unable to Connect Error When VCPT Tries to Send
Channel Information” section on page 6-14
Exception occurred while VCPT was authenticating the server
SSL certificate.
Incorrect server URL format
Generic internal VCPT coding error has occurred. This may be because of a coding bug or because VCPT failed to read a file.
Channel configuration file could not be written to disk on the
VQE-S, the VCDS or the remote server host.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-15
Chapter 3 Using the VQE Channel Provisioning Tool
Defining VQE-Ss, VCDSs, or Remote Servers
Table 3-4 Status of Last Send Messages (continued)
Message Explanation
Failed - File failed to open VQE-S, the VCDS or the remote server could not open the channel configuration file.
Tomcat application server has failed on the VCPT host. Failed - Tomcat Service
Unavailable
Failed - Unable to store the SDP data on VCPT Server
SDP data could not be generated or saved on the VCPT host.
Failed - VCPT:AMT IO Exception:
Connection Refused
VCPT was not able to deliver the channel configuration information. One possible cause of the failure is that VQE services were not running on the server to which the information was sent.
• Status of Last Send Time column shows the date and time of the last successful send operation for this server, or shows “None.” None indicates one of the following:
–
–
Server is new and channel information has never been successfully sent to it
VCPT configuration file that is currently open is from a previous version of VQE
The sections that follow provide more information on the tasks that can be performed from the Servers tab.
Adding a Server
To add a server, follow these steps:
Step 1 On the Servers tab, click Add.
The New Server dialog box, shown in
, is displayed.
Figure 3-10 New Server Dialog Box
3-16
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 3 Using the VQE Channel Provisioning Tool
Defining VQE-Ss, VCDSs, or Remote Servers
Step 2 Fill in the information for the new server. For descriptions of the fields that you need to fill in, see
.
Table 3-5 VQE-S and VCDS Information
VCPT Field Description
Server Details
Server Name
Management IP
String having 1 to 40 alphanumeric characters.
One of the following:
• IP address of an Ethernet interface on the Cisco CDE server
Role
• IP address of an Ethernet interface on the remote server.
One of the following:
• VQE-S
Transfer Port
• VCDS
• SCP (Secure Copy Protocol)—If chosen, VCPT pushes configuration data to a specified remote server using password-less SCP.
SCP port number on the remote server.
If role type is not SCP, the Transfer Port field is grayed out.
Username
Remote Path and Filename
Username of the person who has the authority to access the path on the remote server specified in the Remote Path and Filename field. If role type is not SCP, the Username field is grayed out.
Absolute path to the channel configuration file on the remote server and it’s filename. If role type is not SCP, the Remote Path and
Filename field is grayed out.
Server Wide Channel Configuration
Maximum Receivers Total number of VQE Clients (VQE-Cs) that are expected to tune in this channel. This value is used by the VQE-S to calculate how often the VQE-S sends an RTCP report to the video source for this channel.
RTCP Interval Defines how often VQE-Cs send an RTCP report. By default, RTCP
Interval is 5 seconds.
Step 3 Do one of the following:
•
•
Click Create to create the new server.
Click Cancel to close the dialog box without creating the new server.
Viewing or Updating Server Information
To view or update server information, follow these steps:
Step 1
Step 2
On the Servers tab, click the server you want to view or update.
Click Details.
The Details dialog box is displayed.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-17
Chapter 3 Using the VQE Channel Provisioning Tool
Defining Channel Associations
Step 3
Step 4
If needed, change the server information.
Do one of the following:
• Click Update to update the server information.
• Click Cancel to close the dialog box without changing server information.
Deleting a Server
To delete a server, follow these steps:
Step 1
Step 2
Step 3
Step 4
On the Servers tab, click the server you want to delete.
Click Delete.
A dialog box asking if you want to delete the server is displayed.
Do one of the following:
• Click Delete to delete the server.
• Click Cancel to close the server dialog box without deleting the server.
If you clicked Delete, a confirmation dialog box is displayed. Click OK.
Defining Channel Associations
After VQE channels and the VQE-Ss, VCDSs, and Remote Servers have been defined, you associate a set of channels with the servers. When the channel information file is sent to the VQE-Ss, VCDSs or
Remote Servers, only the channels associated with the server are included in the file.
In the VCPT, use the Association tab, shown in
Figure 3-11 , to associate servers with channels or copy
an existing channel association.
Figure 3-11 Association Tab
3-18
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 3 Using the VQE Channel Provisioning Tool
Defining Channel Associations
The following sections explain how to associate channels with servers:
•
•
Defining Channel Associations for a Server, page 3-19
Copying Channel Associations from Another Server, page 3-19
Defining Channel Associations for a Server
To define channel associations for a server, follow these steps:
Step 1
Step 2
From the Select Server pull-down menu, select the server for which you want to define channel associations.
The VCPT displays the IP address and role for the server.
Select one or more channels to associate or disassociate with the server by using the arrow buttons. For example:
• The > button moves a single available channel or group of available channels to the Selected group.
• The >> button moves all available channels to the Selected group.
The associations for the channel are updated.
Copying Channel Associations from Another Server
To copy channel associations for a server, follow these steps:
Step 1
Step 2
Step 3
From the Select Server pull-down menu, select the server for which you want to define channel associations.
The VCPT displays the IP address and role for the server.
From the Copy Association from Server pull-down menu, select the server whose channel associations you want to copy.
Click OK.
The associations for the channel are updated.
Setting-up a SSH Certificate on a Remote Server
If you choose to export channel configuration data to a remote provisioning server, a secure shell (SSH) certificate should be generated on the VQE Tools server and it’s public key deployed on the remote server to allow VCPT to securely send encrypted channel configuration files to the remote server. The
scpkey command is available on the VQE Tools server to assist in generating the SSH public key file.
The command also uses a secure copy mechanism to deliver the public key of SSH certificate to the remote server. The system integrator must supply a password for the authorized user when generating the certificates so that VCPT can later send data to the remote server without being prompted to supply a password.
On the VQE Tools server, the scpkey executable is located at /opt/vqes/bin/scpkey. To have the operating system find the scpkey executable, you must set the PATH environment variable to include the location of the /opt/vqes/bin directory, or use the full path to scpkey when executing the command.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-19
Chapter 3 Using the VQE Channel Provisioning Tool
Defining Channel Associations
Note You must log in as root to execute the scpkey command.
To generate a SSH public key, follow these steps:
Step 1
Step 2
From the command prompt, issue the following command:
[root@system ~]# scpkey
Welcome to the SCP key generation and transfer utility.
Checking for existing SCP key data...
Generating new keys via Linux ssh-keygen tool...
spawn ssh-keygen -t dsa
Generating public/private dsa key pair
Enter file in which to save the key (/root/.ssh/id_dsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_dsa.
Your public key has been saved in /root/.ssh/id_dsa.pub.
The key fingerprint is: f9:2c:89:5a:bf:22:1c:20:b8:08:05:3c:fc:d1:a9:9f root@system
SCP key generation successfully completed.
The scpkey command creates a new SSH public key. The key file is named id_dsa.pub and is located in
/root/.ssh/.
The scpkey command prompts you to automatically transfer the file to the remote server or to exit the command and manually copy the public key to the remote server at a later time. If you wish to automatically transfer the SSH public key file to the remote server, do the following: a.
When prompted to transfer the file to the remote server using the secure copy protocol, enter ‘y’ at the prompt below.
Do you wish to SCP transfer the key file to a remote system (y/n)? y
Gathering info for SCP transfer...
b.
Enter the IP address of the remote server at the prompt below.
Enter IP address of remote system: 10.22.21.101 c.
Enter the username of the person who is authorized to access the channel configuration files on the remote server at the prompt below:
Enter remote system username: dmurp d.
Enter a password for the authorized person at the prompt below:
Enter remote system username password: e.
By default, the SSH public key file is copied to the .ssh/authorized_keys file relative to the authorized users home directory on the remote server. Press Enter to select the default path or enter the absolute path of the SSH key file on the remote server.
By default, key file will be copied to .ssh/authorized_keys file relative to remote users home directory, however you may specify a different fully qualified path/filename here if desired.
Enter optional remote path/file (<ENTER> for default file):
3-20
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 3 Using the VQE Channel Provisioning Tool
Defining Channel Associations
Step 3
Transferring file, no further user input required...
spawn scp /root/.ssh/id_dsa.pub [email protected]:.ssh/authorized_keys
If you wish to manually transfer the SSH public key file to the remote server, copy the file named id_dsa.pub located in /root/.ssh/ on the VQE Tools server to the .ssh/authorized_keys file relative to the authorized users home directory on the remote server.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
3-21
Defining Channel Associations
Chapter 3 Using the VQE Channel Provisioning Tool
3-22
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
C H A P T E R
4
Using the VQE-S AMT
This chapter describes how to use Cisco VQE Server (VQE-S) Application Monitoring Tool (AMT). The tasks that you can perform with the VQE-S AMT are listed in
.
VQE-S AMT Tasks Table 4-1
VQE-S AMT Task
Log in to the VQE-S AMT
Monitor the health of the VQE-S processes
View channel configuration details, status, and statistics
Monitor statistics for Unicast Retransmission and RCC
1
View configuration details, status, and statistics for CDE
Ethernet interfaces
View configuration details, status, and statistics for the
VQE-S RTCP
2
Exporter
View STUN Server statistics
Reset VQE-S counters
Restore VQE-S counters
Change VQE-S logging levels
Change VQE-S debugging levels
1.
RCC = rapid channel change.
2.
RTCP = Real-Time Transport Control Protocol
Section Where Described
Logging into and Navigating in the VQE-S AMT, page 4-2
Monitoring the Health of the VQE-S Processes, page 4-4
Viewing Channel Configuration and Status, page 4-7
Monitoring Unicast Retransmission and RCC, page 4-16
Monitoring Interfaces, page 4-26
Monitoring RTCP Exporter, page 4-28
Monitoring the STUN Server, page 4-30
Resetting VQE-S Counters, page 4-31
Restoring VQE-S Counters, page 4-32
Change VQE-S Logging, page 4-33
Change VQE-S Debugging, page 4-33
Note The VQE-S AMT supports configuration capabilities for logging levels and debugging options.
However, the configured values do not persist when the VQE-S AMT is restarted.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-1 OL-30119-01
Chapter 4 Using the VQE-S AMT
Logging into and Navigating in the VQE-S AMT
Logging into and Navigating in the VQE-S AMT
Before logging into the VQE-S AMT, you need a valid Linux username and password on the
Cisco CDE hosting the VQE-S AMT. The username does not have to belong to any special group.
Creation of the username is the responsibility of the Cisco CDE system administrator.
The VQE-S AMT supports two web browsers: Microsoft Internet Explorer version 6.0 or later, and
Mozilla Firefox version 2.0 or later. The minimum screen resolution required for the VQE-S AMT is
1024 x 768 pixels.
The VQE-S AMT uses secure HTTPS. Access by multiple simultaneous browsers is supported.
To display the Channels Status Summary graph of active, inoperative, and inactive channels in the AMT
VQE-S Status window, Adobe Flash Player must be installed on the computer that hosts the browser accessing the VQE-S AMT. Adobe Flash Player is free and can be found at this URL: http://get.adobe.com/flashplayer/
To login to the VQE-S AMT, follow these steps:
Step 1
Step 2
Step 3
Point your web browser to the Cisco CDE that hosts the VQE-S AMT using an IP address or fully qualified domain name: https://ip_address
or https://fully_qualified_domain_name
The VQE-S AMT login dialog box is displayed.
Enter a Linux username and password.
Click OK.
If the username and password are valid, the AMT VQE-S Status window is displayed.
4-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Logging into and Navigating in the VQE-S AMT
Figure 4-1 shows the VQE-S AMT navigation controls and buttons.
Figure 4-1
Navigation Tree
VQE-S AMT Navigation
Navigation Tabs
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-3
Chapter 4 Using the VQE-S AMT
Monitoring the Health of the VQE-S Processes
The VQE-S AMT (see
Figure 4-1 ) provides these controls and buttons for navigating and displaying
VQE data:
• Navigation tree—Use the collapsible and expandable tree to display the VQE-S AMT items that can be viewed or configured. The navigation tree can be hidden by clicking the < arrow in its right border.
– Parent node in the tree (such as Channels) usually provides summary data.
•
•
•
•
•
– Child node in the tree (such as an individual channel name) provides data on the specific child node.
Navigation Tabs—Click the tabs to display VQE data for viewing or VQE parameters for configuring in the main window. Some, but not all, VQE items have Configuration and Statistics tabs that display the relevant data or parameters.
Advanced—Click to get additional, detailed information on the current VQE-S AMT items. The advanced data is intended for Cisco Technical Support and are not described in this document.
Refresh—Click to update the displayed data. The VQE-S AMT statistical data are not automatically updated when the VQE-S real-time counters are incremented. The last refresh date-and-time information to the right of the Refresh button indicates when the last update of displayed data occurred.
Reset—Click to globally reset counter values displayed on the VQE-S AMT to zero. The results of this action are visible to all AMT users, even those in separate AMT browser sessions. Only a subset of counters can have their display value reset. Resetting the display of counter values is provided for debugging purposes. For example, resetting a counter after you have fixed an issue could allow you to easily see that an error counter no longer occurs. The last reset date-and-time information to the right of the Reset button indicates when the last manual reset of counters occurred, and displays
never if a reset has not occurred.
Restore—Click to globally restore counters to their true value since the last start of the VQE-S service.
Monitoring the Health of the VQE-S Processes
When you click the System node in the navigation tree and the VQE-S Status tab, the VQE-S AMT displays the VQE-S Status window (see
). The Application Health Monitor and a Channel
Status Summary are displayed in the VQE-S Status window.
4-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Figure 4-2 VQE-S Status Window
Monitoring the Health of the VQE-S Processes
OL-30119-01
In the Application Health Monitor, a green icon with a check mark indicates that the VQE-S system is running and is healthy. A red icon with an X indicates one or more problems with the VQE-S processes.
Using the Application Health Monitor, you can view the following status information:
•
•
System Up Time—Time that Cisco CDE hosting the VQE-S has been running.
Platform—Cisco CDE hardware platform that is hosting this VQE-S. Platform can be one of the following:
•
–
–
Cisco CDE110 (models CDE110-1-036TXA-K9 and CDE110-1-036TXD-K9)
Cisco CDE111 (models CDE111-2-146TXA-K9 CDE111-2-146TXD-K9)
– UNKNOWN if the hardware platform cannot be determined.
Status Message—Current status of the VQE-S software or information on problems (for example, the message “Config File Parsing Failed”).
•
•
VQE-S Version—Current version of the VQE-S software.
Process Table—Information on these VQE-S processes:
–
–
Multicast Load Balancer
STUN Server
–
–
Data Plane
Control Plane.
In the Process Table, Failure Count is the number of times the process has failed and been restarted by the VQE-S Process Monitor. The VQE-S Process Monitor is responsible for starting and monitoring the preceding processes.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-5
Chapter 4 Using the VQE-S AMT
Monitoring the Health of the VQE-S Processes
The Channels Status Summary section provides the number of and a graph for active, inoperative, and inactive channels.
In addition to the VQE-S Status tab, you can get information on the VQE-S system on the eight other tabs.
lists the information that is available from each tab accessible from the System node.
Table 4-2 System Information
System Node Tab
VQE-S Status
Hardware
System Info
Network
Information Provided
Application Health Monitor and Channel Status Summary.
Processor and memory on the Cisco CDE that hosts the VQE-S.
Each CDE has two physical processors and four virtual processors.
Hostname, operating system version, date and time, Network Time
Protocol servers, Domain Name System servers, and iptables information (trusted channel-provisioning servers).
Output from the ifconfig and ip addr show lo commands.
• Configuration information displayed by ifconfig is for the four CDE
Ethernet interfaces and the CDE loopback addresses.
System Status
• Loopback addresses displayed by ip addr show lo are the feedback target addresses for the configured channels.
Detailed information on host uptime, currently running processes, and file system disk space.
OSPF Status Output from several commands that show OSPF information, including status, neighbors, interfaces, database, and routes.
SNMP SNMP
1
information on the VQE-S host taken from the snmpd.conf file.
Logs Most recent 300 lines from the following VQE-related log files are displayed:
•
•
VQE-S log (/var/log/vqe/vqe.log)
System messages log (/var/log/messages)
•
•
•
HTTPD error log (/var/log/httpd/error_log)
SSL error log (/var/log/httpd/ssl_error_log)
Tomcat log (/usr/share/tomcat5/logs/catalina.out)
1.
SNMP = simple network management protocol.
2.
IGMP = internet group management protocol.
4-6
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Viewing Channel Configuration and Status
Viewing Channel Configuration and Status
When you click the Channels node in the navigation tree, the VQE-S AMT displays the Channel
Lineups window (see
).
Figure 4-3 Channel Lineups Window
OL-30119-01
Using the Channel Lineups window, you can do the following:
• Click a column heading to reorder the channels in the list. For example, clicking Feedback Target orders the entries by feedback target: the combination of an IP address and RTCP port number.
•
•
Double-click any item in a channel’s row to display the full details for the channel in a new window.
Click the Re-Activate button to cause the VQE-S to create all channels that are not currently created in the VQE-S software.
with the VCPT) and provides totals for all channels and active channels as well as aggregated bandwidth and total receivers:
Last update: 2007-08-06T14:15:31, Total Channels: 10, Active Channels: 9
Aggregated Bandwidth: 88000 (kbits/sec), Total Receivers: 0
The Channel Lineups window has the same information that is defined for channels using VCPT but has the following additions. For information on the other data that appears in the Channel Lineups table, see
.
• Status—Indicates channel status as follows:
– Green with a checkmark—Channel is active. The VQE-S is receiving the multicast stream.
•
–
–
Yellow with exclamation mark (!)—Channel is inactive. The channel is successfully initialized, but the VQE-S is not receiving the multicast stream.
Red with an X—Channel is inoperative (for example, the channel is not configured correctly).
Member Receiver Population—Provides the number of VQE-Cs that are currently receiving this multicast stream.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-7
Chapter 4 Using the VQE-S AMT
Viewing Channel Configuration and Status
Viewing Channel Configuration
When you click a channel name in the navigation tree and then click the Configuration tab, the VQE-S
AMT displays the Channel Configuration window (see
).
Figure 4-4 Channel Configuration Window
Table 4-3 lists the information presented in the Channel Configuration window.
Table 4-3 Channel Configuration
Field Description
Channel Configuration
Channel Name
Feedback Target Address
Name of the channel.
Feedback Target IP address assigned on the VQE-S host.
RCC •
• true—RCC is enabled for this channel. false—RCC is not enabled for this channel.
Currently only Lookaside mode is supported. Mode
Error Repair •
• true—Unicast Retransmission is enabled for this channel. false—Unicast Retransmission is not enabled for this channel.
Post Repair Loss RLE Enabled • true—RTCP Extended Reports includes the Loss RLE (run-length encoded) report block type.
• false—RTCP Extended Reports does not include the Loss RLE report block type.
Original Source Stream
4-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Viewing Channel Configuration and Status
Table 4-3 Channel Configuration (continued)
Field Description
Multicast IP Address
Protocol
Multicast IP address for the channel’s original source stream.
Currently only RTP
1
is supported.
IP Source Filter
RTCP XR Enabled
Port
Source IP address of the channel’s original source stream.
• true—RTCP Extended Reports are enabled.
• false—RTCP Extended Reports are not enabled.
Number of the port for the original source stream. When the protocol is RTP, this is the RTP port number.
RTCP Port
Bit Rate (Kbps)
Number of the RTCP port for the original source stream.
Bit rate configured for the original source stream.
Reduced size RTCP Enabled • true—Sending reduced-size RTCP NACK compound packets is enabled.
• false—Sending reduced-size RTCP NACK compound packets is not enabled.
Unicast Retransmission Stream
Retransmission IP Address
RTCP Port
RTP Port
IP address of the Unicast Retransmission stream.
Number of the RTCP port for the Unicast Retransmission stream.
Number of the RTP port for the Unicast Retransmission stream.
1.
RTP = Real-Time Transport Protocol
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-9
Chapter 4 Using the VQE-S AMT
Viewing Channel Configuration and Status
Viewing Channel Statistics
When you click a channel name in the navigation tree and then click the Statistics tab, the VQE-S AMT displays the Channel Statistics window (see
Figure 4-5 Channel Statistics Window
Table 4-4 lists the information presented in the Channel Statistics window.
Table 4-4 Channel Statistics
Field Description
Channel Input Stream
Status •
• active—VQE-S is receiving the multicast stream.
inactive—Channel is successfully initialized, but the VQE-S is not receiving the multicast stream.
• inoperative—Channel is not operational. For example, it is not configured correctly.
4-10
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Viewing Channel Configuration and Status
Table 4-4 Channel Statistics (continued)
Field Description
Received Packets Number of RTP packets received by the VQE-S for this multicast stream.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
Lost RTP Packets Number of RTP packets sent but not received by the VQE-S for this multicast stream. Lost RTP Packets, in general, specifies the number of missing input
RTP packets for a channel, as determined by missing sequence numbers. Some lost packets can occur when a channel is first received because a few packets may be dropped internally by the VQE-S in the course of initializing the channel. After the channel has been initialized (typically less than a second delay), further increments in this counter may reflect lost packets in the network between the source of the RTP stream and the VQE-S.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
Average Stream Rate
(Mbps)
Average megabits per second received by the VQE-S for this multicast stream.
Received Bytes Number of bytes received by the VQE-S for this multicast stream.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
Error Repair Statistics—Generic NACK Messages Received
Total Messages
Invalid Messages
Number of NACK messages received by the VQE-S from VQE-C for this multicast stream.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
Number of invalid messages received by the VQE-S from VQE-C for this multicast stream. Invalid messages are received messages that, for example, cannot be parsed.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
Repair Packets
Requested Number of RTP packets VQE-Cs have requested for ER stream.
1
for this multicast
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
Sent Number of RTP packets sent by the VQE-S that have succeeded in repairing an error for this multicast stream.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-11
Chapter 4 Using the VQE-S AMT
Viewing Channel Configuration and Status
Table 4-4 Channel Statistics (continued)
Field Description
Not Sent Number of failed RTP packets that were not repaired by the VQE-S for this multicast stream. The VQE-S may not be able to send an ER packet for the following reasons:
•
•
Most likely cause is that the ER requests were bursty and exceeded the ER rate-policer limit at one point.
Requested RTP packets were not found in the VQE-S memory cache.
• VQE-S failed to send the RTP packets because of a socket sendto() failure.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31
.
Error Repair Average Rate (packets per second)
5 second, 5 minute,
1 minute, 15 minute
RCC Statistics—RCCs
Requested Number of RCC requested for this channel.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31
.
Accepted
The average number of packets per second that the VQE-S has sent to VQE-Cs to repair errors for this multicast stream for each time interval. Averages are calculated for ER each time interval over a period of time that is greater than the interval. For example, the 5 second calculation might be an average of 12 five-second intervals over a 1 minute period.
Refused
Number of RCCs requested for this channel where the VQE-S has accepted the request and sent IPTV packets and other channel data to a VQE-C on the STB.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31
.
Number of RCCs requested for this channel where the VQE-S refused the request. For example, the VQE-S may refuse an RCC request for the following reasons:
• If the VQE-S did not find an I-frame that is a suitable starting point for the
RCC burst.
•
•
If the VQE-S exceeded the output interface bandwidth limit or CPU load limit.
If the CPU load limit is exceeded, the Advanced Channel Debug Stats counter “Refused RCC - no core resources on DP” is displayed when the limit is exceeded.
The Refused RCC counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
Failed Number of RCCs that have failed. A VQE-C has made an RCC request, and the
VQE-S has accepted the request and sent IPTV packets and other channel data to a VQE-C. But the RCC failed. For example, an RCC can fail if the VQE-C stops receiving the packets from the VQE-S earlier than expected.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31
.
RTCP Packets
4-12
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Viewing Channel Configuration and Status
Table 4-4 Channel Statistics (continued)
Field Description
Received Number of RTCP packets received by the VQE-S for this multicast stream.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
Sent Downstream
Sent Upstream
Reduced Size RTCP
Received
Number of RTCP packets that the VQE-S sent downstream for this multicast stream.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
Number of RTCP packets that the VQE-S sent upstream for this multicast stream.
This counter is resettable. For information on resetting counters, see the
“Resetting VQE-S Counters” section on page 31 .
Number of reduced-size RTCP NACK compound packets sent for this multicast stream.
1.
ER = error repair
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-13
Chapter 4 Using the VQE-S AMT
Viewing Channel Configuration and Status
Viewing Channel Histograms
When you click a channel name in the navigation tree and then click the Histograms tab, the VQE-S
AMT displays the Channel Histograms window (see
Note The VQE-S AMT Channel Channel Time histogram is only supported for VQE-C integrations that have implemented the RCC instrumentation as described in the VQE-C System Integration Guide.
Figure 4-6 Channel Histograms Window
In the Channel Histogram window, the Channel Change Time histogram and table are displayed. The data displayed in the histogram and table include the following:
•
•
•
Total number of channel changes (CCs) per time bucket.
Number of successful RCCs for the selected time bucket.
•
Number of unsuccessful RCCs for the selected time bucket.
Number of non-rapid CCs (that is, channel changes where RCC was not requested) for the selected time bucket.
Each time bucket in this histogram represents a subset of channel change times from 0 to 7000 ms. Any channel change times that take longer than 7000 ms are collected in the uppermost bucket.
Move the slider below the histogram to change the way in which the histogram is displayed.
4-14
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Viewing Channel Configuration and Status
Note The histogram is displayed and populated, regardless of whether RCC is enabled at the VQE-S.
If no Multicast Acquisition (MA) XR report (a RTCP XR report block type) is received for a repair session, the histogram is unchanged.
Viewing RCC Troubleshooting
When you click a channel name in the navigation tree and then click the RCC Troubleshooting tab, the
VQE-S AMT displays the RCC Troubleshooting window (see
Figure 4-7 RCC Troubleshooting Window
OL-30119-01
The RCC Status window has the information listed in Table 4-5 .
Table 4-5 RCC Status
Field
Client CNAME
Timestamp
Failure Reason
Failure Detail
Description
Identifier for the STB for which the RCC was requested but failed.
Typically, the CNAME is the MAC address of the STB.
Time of the event. For example, 2009-07-21 08:42:03.05.
Specific reason for the failure on either the VQE-S or the VQE-C.
Additional information about the failure that may be used for debugging purposes.
The table presents the last 20 RCC failures on this channel. To reorder the list of RCC failures, click a column heading. For example, clicking Timestamp orders the RCC failures by date and time.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-15
Chapter 4 Using the VQE-S AMT
Monitoring Unicast Retransmission and RCC
Monitoring Unicast Retransmission and RCC
Note In VQE-S AMT, Error Repair is the term used for Unicast Retransmission.
Use the VQE-S AMT to view Error Repair and RCC statistics.
Viewing Error Repair and RCC Configuration
When you click Error Repair and RCC in the navigation tree and click the Configuration tab, the
VQE-S AMT displays the Error Repair and RCC Configuration window (see
Figure 4-8 Error Repair and RCC Configuration Window
Table 4-6 lists the information in the Error Repair and RCC Configuration window. Each of the
parameters listed in the table can be configured with the VQE Configuration Management System. For information on configuring the VQE-S, see
Chapter 7, “Configuring VQE Server and VQE Tools.”
Table 4-6 Error Repair and RCC Configuration
Field Description
Error Repair/RCC Configuration
RCC Mode
IGMP Join Variability (msec) Amount of variability (in milliseconds) between the fastest and slowest IGMP joins for RCC. This value is configured with the vqe.vqes.igmp_join_variability parameter. For information on this parameter, see
Excess Bandwidth Fraction
RCC mode can be aggressive or conservative. This value is configured with the vqe.vqes.rcc_mode parameter in VCDB. For information on this parameter, see
Percent of channel bandwidth that is available on the access link for
Unicast Retransmission and RCC. This value is configured with the vqe.vqes.excess_bw_fraction parameter. For information on this parameter, see
4-16
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Monitoring Unicast Retransmission and RCC
Table 4-6 Error Repair and RCC Configuration (continued)
Field Description
Maximum Interval between
MPEG RAPs (msec)
Maximum time interval (in milliseconds) between MPEG RAPs
1
for the entire channel lineup. This value is configured with the vqe.vqes.rap_inteval parameter in VCDB. For information on this
parameter, see Table A-3 on page A-6 .
Differentiated Services Code Point Configuration
RTCP Packets DCSP value for RTCP packets that the VQE-S sends. This value is configured with the vqe.vqes.rtcp_dscp parameter in VCDB. For information on this parameter, see
.
Retransmitted RTP Packets DCSP value for RTP packets that the VQE-S sends. This value is configured with the vqe.vqes.rtp_trans_dscp parameter in VCDB. For information on this parameter, see
.
1.
RAP = random access point.
Viewing Error Repair and RCC Statistics
When you click Error Repair and RCC in the navigation tree and click the Statistics tab, the VQE-S
AMT displays the Error Repair and RCC Statistics tab (see
Figure 4-9 ). The statistics are similar to the
Error Repair and RCC statistics displayed for individual channels but are for all channels in the current channel lineup.
The ER and RCC statistics are reset to 0 when the VQE-S service restarts or when the channel lineup changes.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-17
Monitoring Unicast Retransmission and RCC
Figure 4-9 Error Repair and RCC Statistics Tab
Chapter 4 Using the VQE-S AMT
Table 4-7 lists the information in the Error Repair and RCC Statistics window.
Table 4-7 Error Repair and RCC Statistics
Field Description
Generic NACK Messages Received
Total Messages Number of NACK messages received by this VQE-S from the VQE-Cs.
This counter is resettable. For information on resetting counters, see the
section.
Invalid Messages Number of invalid messages received by this VQE-S from VQE-Cs. Invalid messages are received messages that, for example, cannot be parsed.
This counter is resettable. For information on resetting counters, see the
section.
Repaired RTP Packets
Requested Number of RTP packets VQE-Cs have requested for ER from this VQE-S.
This counter is resettable. For information on resetting counters, see the
section.
4-18
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Monitoring Unicast Retransmission and RCC
Table 4-7 Error Repair and RCC Statistics (continued)
Field Description
Sent Number of RTP packets sent by this VQE-S that have succeeded in repairing an error.
This counter is resettable. For information on resetting counters, see the
Resetting VQE-S Counters section.
Not Sent Number of failed RTP packets that were not repaired by the VQE-S. The
VQE-S may not be able to send an ER packet for several reasons, among them:
•
•
Most likely cause is that the ER requests were bursty and exceeded the
ER rate-policer limit at one point.
Requested RTP packets were not found in the VQE-S memory cache.
• VQE-S failed to send the RTP packets because of a socket sendto() failure.
The Repaired RTP Packets Not Sent counter is resettable. For information on resetting counters, see the
Resetting VQE-S Counters section.
Inbound and Outbound Error Repair Average Rate (packets per second)
5 second, 5 minute,
1 minute, 15 minute
For each time period, the average number of packets per second that the
VQE-S has received (inbound) or sent (outbound) to VQE-Cs to repair errors
(Unicast Retransmission).
RCC Statistics—Rapid Channel Changes
Requested Number of RCCs requested for this channel.
This counter is resettable. For information on resetting counters, see the
Resetting VQE-S Counters section.
Accepted Number of RCCs requested for this channel where the VQE-S has accepted the request and sent IPTV packets and other channel data to a VQE-C on the
STB.
This counter is resettable. For information on resetting counters, see the
Resetting VQE-S Counters section.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-19
Chapter 4 Using the VQE-S AMT
Monitoring Unicast Retransmission and RCC
Table 4-7 Error Repair and RCC Statistics (continued)
Field Description
Refused Number of RCCs requested for this channel where the VQE-S has refused the request. For example, the VQE-S may refuse an RCC request for the following reasons:
•
•
VQE-S did not find an I-frame that is a suitable starting point for the
RCC burst.
VQE-S exceeded the output interface bandwidth limit or CPU load limit.
Failed
• CPU load limit is exceeded, the Advanced Channel Debug Stats counter
“Refused RCC - no core resources on DP” shows when the limit is exceeded.
This RCCs Refused counter is resettable. For information on resetting counters, see the
Resetting VQE-S Counters section.
Number of RCCs that have failed. A VQE-C has made an RCC request, and the VQE-S has accepted the request and sent IPTV packets and other channel data to a VQE-C but the RCC failed. For example, an RCC can fail if the
VQE-C stopped receiving RCC packets from the VQE-S earlier than was expected.
This counter is resettable. For information on resetting counters, see the
section.
4-20
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Monitoring Unicast Retransmission and RCC
Viewing Excess Bandwidth
When you click Error Repair and RCC in the navigation tree and click the Excess BW tab, the VQE-S
AMT displays the Excess BW window (see
).
Figure 4-10 Excess BW Window
OL-30119-01
If Error Repair or RCC is enabled and active, you can choose to display a client e-factor histogram or table by clicking the icons in the upper right corner of the window. Use the Select a client e-factor histogram drop-down menu to select Error Repair or RCC histograms.
An e-factor is an excess bandwidth fraction that determines the rate at which packets are sent during
Error Repair and RCC. The data displayed in the histograms and tables include the following:
• E-factor count with the number of times a client e-factor has been calculated. This appears on the vertical axis in the histograms.
• E-factor distribution of the client e-factor percentages that have been used. This appears on the horizontal axis in the histograms. If the distribution is widely dispersed, there can be more than one grouping of percentages.
Move the slider below the histograms to change the way in which the histograms are displayed. The e-factor percentages cannot be negative values.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-21
Chapter 4 Using the VQE-S AMT
Monitoring Unicast Retransmission and RCC
Viewing Channel Change Times
When you click Error Repair and RCC in the navigation tree and click the CC Times tab, the VQE-S
AMT displays the CC Times window (see
Figure 4-11 Channel Change Times Window
In this window, the Average Channel Change Time histogram and table are displayed. The data displayed in the histogram and table includes the following:
• Average channel change time in milliseconds for each channel on the VQE-S for the following three categories:
– Successful RCCs
–
–
Unsuccessful RCCs
Non-rapid CC (that is, channel changes where RCC was not requested).
The data displayed is based on the last 100 successful channel changes where RCC was enabled, the last
100 unsuccessful change changes where RCC was enabled, and the last 100 channel changes where RCC was disabled.
Move the slider below the histogram to change the way in which the histogram is displayed.
4-22
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Monitoring Unicast Retransmission and RCC
Viewing Error Repair and RCC Capacity Statistics
When you click Error Repair and RCC in the navigation tree and click the Capacity tab, the VQE-S
AMT displays the Error Repair and RCC Capacity tab (
Figure 4-12 ). The VQE-S provides capacity
statistics to indicate when Unicast Retransmission and RCC capacity limits have been exceeded.
The ER and RCC capacity counters and statistics are reset to 0 when the VQE-S service restarts or when the channel lineup changes.
Figure 4-12 Error Repair and RCC Capacity Tab
OL-30119-01
lists the information presented in the Error Repair and RCC Capacity tab.
Table 4-8 Error Repair and RCC Capacity Statistics
Field Description
Error Repair Requests Rejected (Over Capacity)
Requests Rejected Number of ER requests rejected due to ER capacity limits being exceeded since the VQE-S service was last started. For information on the maximum number of ER requests and the maximum number of output ER packets, see
.
This counter is resettable. For information on resetting counters, see the
Resetting VQE-S Counters section.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-23
Chapter 4 Using the VQE-S AMT
Monitoring Unicast Retransmission and RCC
Table 4-8 Error Repair and RCC Capacity Statistics (continued)
Field Description
% Requests Rejected Percentage of ER requests rejected due to ER capacity limits being exceeded out of the total number of ER requests received. For information on the maximum number of ER requests and the maximum number of output ER packets, see
This counter is resettable. For information on resetting counters, see the
section.
Last 24 Hours
% Last 24 Hours
Number of ER requests rejected in the last 24 hours due to ER capacity limits being exceeded. For information on the maximum number of ER requests and the maximum number of output ER packets, see
Percentage of ER requests rejected in the last 24 hours due to ER capacity limits being exceeded out of the total number of ER requests received during that same 24 hour period. For information on the maximum number of ER requests and the maximum number of output ER packets, see
.
Highwater 24 Hours Highest number of ER requests rejected during any 24 hour period due to ER capacity limits being exceeded. For information on the maximum number of
ER requests and the maximum number of output ER packets, see
% Highwater 24 Hours Percentage of ER requests rejected during the highest 24 hour period due to
ER capacity limits being exceeded out of the total number of ER requests received during that same 24 hour period. For information on the maximum number of ER requests and the maximum number of output ER packets, see
Highwater Time Date and time when the highwater mark was reached.
RCC Requests Rejected (Over Capacity)
Requests Rejected Number of RCC requests rejected due to RCC capacity limits being exceeded since the VQE-S service was last started. For information on the allocation of egress bandwidth to servicing RCC requests, see the
Performance Summary” section on page H-2 .
This counter is resettable. For information on resetting counters, see the
section.
% Requests Rejected Percentage of RCC requests rejected due to RCC capacity limits being exceeded out of the total number of RCC requests received. For information on the allocation of egress bandwidth to servicing RCC requests, see the
“Scaling and Performance Summary” section on page H-2 .
This counter is resettable. For information on resetting counters, see the
section.
Last 24 Hours
% Last 24 Hours
Number of RCC requests rejected in the last 24 hours due to RCC capacity limits being exceeded. For information on the allocation of egress bandwidth
to servicing RCC requests, see the “Scaling and Performance Summary” section on page H-2 .
Percentage of RCC requests rejected in the last 24 hours due to RCC capacity limits being exceeded out of the total number of RCC requests received during that same 24 hour period. For information on the allocation of egress
bandwidth to servicing RCC requests, see the “Scaling and Performance
Summary” section on page H-2 .
4-24
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Monitoring Unicast Retransmission and RCC
Table 4-8 Error Repair and RCC Capacity Statistics (continued)
Field Description
Highwater 24 Hours Highest number of RCC requests rejected during any 24 hour period due to
RCC capacity limits being exceeded. For information on the allocation of egress bandwidth to servicing RCC requests, see the
Performance Summary” section on page H-2
.
% Highwater 24 Hours Percentage of RCC requests rejected during the highest 24 hour period due to
RCC capacity limits being exceeded out of the total number of RCC requests received during that same 24 hour period. For information on the allocation of egress bandwidth to servicing RCC requests, see the
Performance Summary” section on page H-2
.
Highwater Time Date and time when the highwater mark was reached.
Receivers (Clients)
Currently Active Number of receivers currently active on the VQE-S.
% Currently Active
Highwater Active
% Highwater Active
Percentage of receivers currently active on the VQE-S out of the total number of allowed receivers. For information on the maximum number of simultaneous receivers, see
.
Highest number of receivers simultaneously active on the VQE-S.
Client Requests
Rejected
Percentage of receivers simultaneously active at the highwater mark out of the total number of allowed receivers. For information on the maximum number of simultaneous receivers, see
.
Number of client requests rejected due to the maximum number of simultaneous receivers being exceeded. For information on the maximum number of simultaneous receivers, see
.
This counter is resettable. For information on resetting counters, see the
Resetting VQE-S Counters section.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-25
Chapter 4 Using the VQE-S AMT
Monitoring Interfaces
Monitoring Interfaces
When you click Interfaces in the navigation tree, the VQE-S AMT displays three tables associated with the CDE Ethernet and bond interfaces: the Interface Summary Table, the Input Bandwidth Table, and the
Multicast Group Table.
Figure 4-13 shows these tables. (In Figure 4-13
, some channels in the Multicast
Group Table have been omitted.)
Figure 4-13 Interface-related Tables
Table 4-9 lists the information presented in the Interface Summary Table (shown in Figure 4-13
). The information is about the Ethernet and bond interfaces on the Cisco CDE that are currently configured for the VQE-S ingest and services traffic.
Table 4-9 Interface Summary Table
Column
I/F Name
IP Address
Status
Description
Name that is assigned to the Ethernet interface or bond interface by
Linux. For information on these names, see
Operating System for the VQE-S” section on page D-3 .
IP address of one of the following interfaces:
•
•
If this interface is an Ethernet interface and it does not belong to a bond interface, the IP address assigned to the Ethernet interface is displayed.
If this interface is an Ethernet interface and it belongs to a bond interface, the bond interface name is displayed.
• If this interface is a bond interface, the IP address assigned to the bond interface is displayed.
Interface is either up or down.
4-26
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Monitoring Interfaces
Table 4-9 Interface Summary Table (continued)
Column Description
Role One or more of the following:
Max BW (Mbps)
•
•
Ingest—Used for traffic for multicast streams from the upstream video sources.
Service—Used for the VQE-S services traffic (Unicast
Retransmission and RCC) to the downstream VQE-Cs on the
STBs.
•
•
Management—Used for the VQE-S management traffic to the management network.
Bond interface name—Used for Ethernet interfaces that are members of a bond interface. Displays the bond interface name.
Maximum speed of the interface.
lists information about the Input Bandwidth Table shown in
. The table provides information on the Ethernet interfaces or bond interfaces currently being used for VQE-S ingest traffic.
The interfaces listed in this table are currently under the control of the VQE-S Multicast Load Balancer.
Multicast Load Balancer distributes traffic for incoming multicast streams over the Ethernet interfaces that are configured for ingest. If a bond interface is used for ingest traffic, the Multicast Load Balancer distributes traffic over the Ethernet interfaces that are members of the bond interface. The interfaces must be correctly configured and operational (up) to participate in this load balancing. The Multicast
Load Balancer determines the best interface on which to join or leave the multicast group, distributing the joins across available interfaces to avoid oversubscription. It also monitors the status of these interfaces, moving the streams to other interfaces in case of interface failure.
Table 4-10 Input Bandwidth Table
Column
I/F Name
Max Input BW (Mbps)
Reserved Input BW
Description
Name of the interface that is being used for receiving multicast streams.
Maximum speed of the interface.
Percentage of maximum input bandwidth that has been reserved for all non-ingest traffic and is not be used for receiving multicast streams.
The VCDB parameter vqe.vqes.unicast_reservation specifies this percent.
•
•
If the interface is used for both VQE-S ingest and VQE-S services, the reservation should include sufficient bandwidth for receiving Unicast Retransmission and RCC requests, RTCP reports from the STBs, and control traffic, such as IGMP and
RTCP.
If the interface is used for ingest only, the reservation should include sufficient bandwidth for incoming control traffic, such as
IGMP and RTCP.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-27
Chapter 4 Using the VQE-S AMT
Monitoring RTCP Exporter
Table 4-10 Input Bandwidth Table (continued)
Column Description
Available Input BW (Mbps) Interface bandwidth that is available for ingest of multicast streams but that is not currently being used. Initially, when no multicast streams are being received by this interface, this value is equal to Max
Input BW minus Reserved Input BW.
Multicast Group Count Number of multicast streams that are currently being received by the interface.
Table 4-11 lists the information about the Multicast Group Table shown in
provides information about the multicast streams currently being received by this VQE-S.
Table 4-11 Multicast Group Table
Column
Multicast Address
Description
Destination IP address for this multicast group.
I/F Name Name of the interface that is being used for receiving this multicast stream.
Source Filter Source IP address of the multicast group’s sender.
Used Input Bandwidth (Mbps) Receive bandwidth consumed on this interface by receiving this multicast steam. This bandwidth is specified in the channel definition (for example, in the Bit Rate field of the VCPT).
Monitoring RTCP Exporter
When you click RTCP Exporter > VQM in the navigation tree and click the Configuration tab, the
VQE-S AMT displays the VQE-S RTCP Exporter parameters for the corresponding VQM. RTCP
Exporter currently has no parameters that can be configured with the VQE-S AMT, and the parameters are for viewing only. For information on configuring RTCP Exporter, see the
RTCP Exporter” section on page 2-42 .
4-28
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Monitoring RTCP Exporter
When you click RTCP Exporter > VQM in the navigation tree and click the Statistics tab, the VQE-S
AMT displays the RTCP Exporter Statistics window for the corresponding VQM (see
).
Note Starting with Cisco VQE 3.7 release, VQE-S AMT supports viewing Advanced Statistics of RTCP
Exporter in a separate window for each of the VQMs configured.
Figure 4-14 RTCP Exporter Statistics Window
OL-30119-01
lists the information presented in the RTCP Exporter Statistics window.
Table 4-12 RTCP Exporter Statistics
Field Description
VQM Application Configuration
VQM Host
VQM TCP Port
IP address of the host on which the video-quality monitoring (VQM) application resides.
TCP port number on which the VQM application listens for video quality data from RTCP Exporter.
Enabled
Filtering NACKs
Either true (enabled) or false (not enabled).
Either true (enabled) or false (not enabled). If enabled, RTCP
NACK compound packets are not sent to the VQM application.
Configuration Status
Operational Status
Either enabled or not enabled. It is possible for the value in the
Enabled field to be true, and the value in the Configuration
Status field to be not enabled (for example, if the host IP address or TCP port are not valid).
Message providing information on the operational status of
RTCP Exporter.
RTCP Exporter Stats
Packets Exported Number of RTCP compound packets that have been exported to a VQM host.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-29
Chapter 4 Using the VQE-S AMT
Monitoring the STUN Server
Table 4-12 RTCP Exporter Statistics
Field Description
Packets Dropped Number of RTCP compound packets that have been dropped rather than exported to a VQM host. In heavy load situations,
RTCP Exporter may intentionally drop RTCP packets.
NACKs Filtered
Details on dropped packets (number of dropped packets and the position and time where this loss occurred) is contained in the collection of reports exported by this VQE-S.
Number of RTCP NACK compound packets omitted from the
RTCP data sent to the VQM application.
For information on RTCP Exporter and the video-quality monitoring application, see the
Exporter for Video-Quality Monitoring” section on page 1-23
.
Monitoring the STUN Server
When you click STUN Server in the navigation tree, the VQE-S AMT displays the STUN Server
Statistics window (see
).
Figure 4-15 STUN Server Statistics Window
Table 4-13 lists information displayed in the STUN Server Statistics window.
Table 4-13 STUN Server Statistics
Field
Total Requested
Successfully Sent
Response Failed
Sent Failed
Description
Number of STUN binding requests that the VQE-C STUN Client sent to the STUN Server.
Number of responses to STUN binding requests that the STUN Server successfully sent to the VQE-C STUN Client.
Number of instances in which the STUN Server fails to generate a binding response because of an internal error.
Number of instances in which the STUN Server successfully generates a binding response but fails to send it to the VQE-C STUN
Client (for example, because of a socket error).
4-30
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Resetting VQE-S Counters
Resetting VQE-S Counters
The VQE-S maintains a set of counters for debugging purposes. A subset of counters can be manually reset from the VQE-S AMT GUI. The results of this action are visible to all AMT users, even those in separate AMT browser sessions. The Reset button is located on the Statistics tab of the Error Repair
and RCC window, and resets all counters displayed in
Table 4-14 Resettable VQE-S AMT counters
Category Counter
Error Repair and RCC counters on Statistics tab
Generic NACK Messages Received
Repaired RTP Packets
•
•
•
•
Total Messages
Invalid Messages
Requested
Sent
RCC
•
•
•
•
•
Capacity counters on Capacity tab
Capacity Statistics •
Not Sent
Requested
Accepted
Refused
Failed
•
•
•
Error Repair Requests Rejected (Over
Capacity)—Requests Rejected
Error Repair Requests Rejected (Over
Capacity)—% Requests Rejected
RCC Requests Rejected (Over
Capacity)—Requests Rejected
RCC Requests Rejected (Over Capacity)—%
Requests Rejected
• Receivers (Clients)—Client Requests
Rejected
Channel counters on Statistics/Status tab
Channel Input Stream • Received packets
•
•
Received bytes
Lost RTP Packets
Error Repair—Generic NACK Messages Received • Total Messages
Error Repair—Repaired RTP Packets
•
•
Invalid Messages
Requested
•
•
Sent
Not Sent
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-31
Chapter 4 Using the VQE-S AMT
Restoring VQE-S Counters
Table 4-14
Category
RCC
RTCP Packets
Resettable VQE-S AMT counters (continued)
•
•
•
•
Counter
• Requested
Accepted
Refused
•
•
Failed
Received
Sent Downstream
Sent Upstream
Note When one user resets the subset of counters displayed in
Table 4-13 , this change is reflected for all other
users on performing a refresh of the VQE-S AMT GUI.
To reset counters, do the following:
Step 1
Step 2
Step 3
In the VQE-S AMT navigation tree, click the Error Repair and RCC node.
The Configuration tab is displayed on the Error Repair and RCC window.
On the Error Repair and RCC window, click the Statistics tab.
The Reset button is displayed on the Statistics tab.
Click Reset.
The values of all counters listed in
Table 4-13 are reset to zero. The last reset timestamp is updated to
display the current time.
Restoring VQE-S Counters
Following a reset of the subset of counters listed in
, you can restore counters from the VQE-S
AMT GUI to display their cumulative value since the last start of the VQE-S service.
Note When one user restores the subset of counters displayed in
Table 4-14 to their cumulative value, this
change is reflected for all users on performing a refresh of the VQE-S AMT GUI.
To reset counters, do the following:
Step 1
Step 2
Step 3
In the VQE-S AMT navigation tree, click the Error Repair and RCC node.
The Configuation tab is displayed on the Error Repair and RCC window.
On the Error Repair and RCC window, click the Statistics tab.
The Restore button is displayed on the Statistics tab.
Click Restore.
4-32
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Change VQE-S Logging
All counters that were reset now display their cumulative value. The last reset timestamp is updated to display the text never.
Change VQE-S Logging
When you click Logging in the navigation tree, the VQE-S AMT displays the logging priority levels
(
Figure 4-16 ) for the VQE-S. The priority levels allow you to control the logging level for system
messages for all VQE-S processes (Process Monitor, Control Plane, Data Plane, and Multicast Load
Balancer). By default, all VQE-S system messages are written to the file /var/log/vqe/vqe.log. In addition, you can send system messages to remote servers for centralized logging. For information on
configuring remote syslog servers, see the “Remote Syslog Hosts” section on page 2-28 .
Figure 4-16 Logging Priority Levels
To change a VQE-S logging priority level, click the button next to the appropriate level and click Apply.
In VQE-S AMT, the logging priority levels are listed from least verbose to most verbose. The Emergency level generates the smallest number of messages, and the Info level generates the greatest number of messages. The default value is Warning.
When you select a logging level, log messages are generated for the levels below that level. For example, when the level is set to Error, messages are generated for Emergency, Alert, Critical, and Error.
The selected logging priority level does not persist when the VQE-S is stopped. When the VQE-S restarts, the logging priority level goes back to the default (Warning). To set a logging priority level that does persist, use the VQE-S parameter vqe.vqes.log_priority. For information on this parameter, see
.
Change VQE-S Debugging
When you click Debugging in the navigation tree and click a debug component, the debugging options for that component are displayed.
Figure 4-17 shows the debug components. The options allow you to
control the types of debugging messages that are written to the syslog file. By default, debug messages are written to the file /var/log/vqe/vqe.log.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-33
Chapter 4 Using the VQE-S AMT
Change VQE-S Debugging
Figure 4-17 Debug Components
To change VQE-S debugging, follow these steps:
Step 1 In the VQE-S AMT navigation tree, click the + sign next to Debugging and click the component for which you want to configure debug messages.
The debug flags and filters for that component are displayed.
For example,
shows the flags and filters for the RTP/RTCP category.
Figure 4-18 RTP/RTCP Flags and Filters
Note In the debug filters for the STUN Server, only the Client IP filter is supported. The Multicast IP filter is not supported because the STUN Server has no knowledge of channels. Filtering on the Client IP address provides debug messages for the specified client.
Step 2 To enable a debugging flag, click the check box in the On/Off column. To disable an enabled flag, click the check box in the On/Off column to uncheck it.
Note For the next step, be aware that not all debug flags support debug filters (in the Filter Status column). If debug filters are not supported, the check box next to the flag is grayed out.
Step 3 To filter debugging messages by a specific channel or VQE-C for an enabled debugging flag, do the following:
4-34
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 4 Using the VQE-S AMT
Change VQE-S Debugging
Step 4 a.
b.
In the Filter Status column, click the check box for the option.
In the Debug Filters section, click either Multicast IP or Client IP:
• For Multicast IP, enter the channel source stream IP address and (RTP/UDP) port number.
• For Client IP, enter the VQE-C IP address.
Click Apply.
The selected debugging options are enabled.
The selected debugging options do not persist when the VQE-S is stopped. When the VQE-S restarts, debugging goes back to the default—no options are enabled.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
4-35
Change VQE-S Debugging
Chapter 4 Using the VQE-S AMT
4-36
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
C H A P T E R
5
Using the VCDS AMT
This chapter describes how to use Cisco VQE Client Configuration Delivery Server (VCDS) Application
Monitoring Tool (AMT). The VCDS is a software component installed on each VQE Tools server, the
Cisco CDE that also hosts VCPT. The VCDS AMT is a web browser-based tool for displaying configuration, status, and statistics on the VCDS process and the VQE Tools server. The tasks that you can perform with the VCDS AMT are listed in
.
VCDS AMT Tasks Table 5-1
VCDS AMT Task
Log in to VCDS AMT
Monitor the health of the VCDS process and VQE Tools
Server
View configuration details and statistics for the VCDS
Change VCDS logging levels
Change VCDS debugging levels
Section Where Described
Logging into and Navigating in VCDS AMT, page 5-2
Change VCDS Debugging, page 5-9
Monitoring the Health of the VCDS Process and VQE Tools
Viewing VCDS Configuration and Statistics, page 5-4
Note VCDS AMT supports configuration capabilities for logging levels and debugging options. However, the configured values do not persist when VCDS is restarted.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
5-1
Chapter 5 Using the VCDS AMT
Logging into and Navigating in VCDS AMT
Logging into and Navigating in VCDS AMT
Before logging into VCDS AMT, you need a valid Linux username and password on the Cisco CDE hosting the VCDS AMT. The username does not have to belong to any special group. Creation of the username is the responsibility of the Cisco CDE system administrator.
The VCDS AMT supports two web browsers: Microsoft Internet Explorer version 6.0 or later, and
Mozilla Firefox version 2.0 or later. The minimum screen resolution required for the VCDS AMT is
1024 x 768 pixels.
The VCDS AMT uses secure HTTPS. Access by multiple simultaneous browsers is supported.
To login to VCDS AMT, follow these steps:
Step 1
Step 2
Step 3
Point your web browser to the Cisco CDE that hosts VCDS AMT using an IP address or fully qualified domain name: https://ip_address/vcds-amt
or https://fully_qualified_domain_name/vcds-amt
The VCDS AMT login dialog box is displayed.
Enter a Linux username and password.
Click OK.
If the username and password are valid, the VCDS AMT Status window is displayed.
shows the VCDS AMT navigation controls and buttons.
Figure 5-1
Navigation Tree
VCDS AMT Navigation
Navigation Tabs
VCDS AMT (
Figure 5-1 ) provides these controls and buttons for navigating and displaying VCDS data:
• Navigation tree—Use the collapsible and expandable tree to display the VCDS AMT items that can be viewed or configured. The navigation tree can be hidden by clicking the < arrow in its right border.
– The parent node (System) in the tree provides summary data.
5-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 5 Using the VCDS AMT
Monitoring the Health of the VCDS Process and VQE Tools Server
•
•
– Each child node in the tree (such as VCDS) provides data on the specific child node.
Navigation Tabs—Click the tabs to display VCDS data for viewing. The VCDS node has two tabs: a Configuration tab and a Statistics tab.
Refresh —Click to update the displayed data. The VCDS AMT statistical data are not automatically updated when the VCDS real-time counters are incremented. The Last refresh date-and-time information to the right of the Refresh button indicates when the last update of displayed data occurred.
Monitoring the Health of the VCDS Process and VQE Tools
Server
When you click the System node in the navigation tree and the VCDS Status tab, the VCDS AMT displays VCDS and VQE Tools Server status information (
Figure 5-2 VCDS Status Information
OL-30119-01
On the VCDS Status tab, a green icon with a checkmark indicates the VQE Tools server system is running and healthy. A red icon with an X indicates one or more problems with the VQE Tools server.
A yellow icon with an exclamation mark (!) indicates that one or more of the following files are invalid:
• Channel configuration file
•
•
From the VCDS Status tab, you can view the following status information:
• System Up Time—Time that the Cisco CDE hosting VQE Tools has been running.
•
Client database file
Group attribute file
Platform—Cisco CDE hardware platform that is hosting VQE Tools. Platform can be one of the following:
– Cisco CDE110 (models CDE110-1-036TXA-K9 and CDE110-1-036TXD-K9)
•
–
–
Cisco CDE111 (models CDE111-2-146TXA-K9 and CDE111-2-146TXD-K9)
UNKNOWN if the hardware platform cannot be determined
Process Status—One of the following status messages:
– VCDS Active—VCDS is running.
– VCDS Stopped—VCDS is not running
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
5-3
Chapter 5 Using the VCDS AMT
Viewing VCDS Configuration and Statistics
– VCDS Inactive—A configuration file is not correct.
• VCDS Version—Current version of the VCDS software.
In addition to the VCDS Status tab, you can get information on the VCDS and the VQE Tools server on the five other tabs.
lists the information that is available from each tab accessible from the
System node.
Table 5-2
System Info
System Node Tabs
System Node Tab
Hardware
Information Provided
Processor and memory on the Cisco CDE that hosts VQE Tools.
Each CDE has two physical processors and four virtual processors.
Hostname, operating system version, date and time, Network Time
Protocol servers, Domain Name System servers, and iptables information.
System Status
SNMP
Logs by ifconfig is for the four CDE Ethernet interfaces.
Detailed information on host uptime, currently running processes, and file system disk space.
SNMP information on the VQE Tools server host taken from the snmpd.conf file.
Most recent 300 lines from the following VQE Tools Server log files are displayed:
• VCDS log (/var/log/vqe/vqe.log)
•
•
•
•
•
System messages log (/var/log/messages)
HTTPD error log (/var/log/httpd/error_log)
SSL error log (/var/log/httpd/ssl_error_log)
Tomcat log (/usr/share/tomcat5/logs/catalina.out)
VCDS AMT log (/usr/share/tomcat5/logs/vcds.out)
Viewing VCDS Configuration and Statistics
When you click the VCDS node in the navigation tree and click the Configuration tab, the VCDS AMT displays information relating to the VCDS configuration, to VQE Client (VQE-C) channel configuration, to the client database file, and to the group attribute file (
information on the client database and the group attribute files, see
Provisioning Server Role” section on page 1-20
.
Note In the VCDS AMT, the group attribute file is referred to as the VQE-C network configuration file and the client database file is referred to as the VQE-C group map file.
5-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 5 Using the VCDS AMT
Viewing VCDS Configuration and Statistics
Viewing VCDS Configuration
When you click the Configuration tab, VCDS AMT displays the VCDS Configuration window
(
).
Figure 5-3 VCDS Configuration Window
OL-30119-01
The Configuration window has the information listed in
.
Table 5-3 VCDS Configuration
Field Description
VCDS Configuration
TCP Port
Max Connections Allowed
TCP port number on which the VCDS process listens.
Maximum number of clients allowed to connect to VCDS.
Inactive Connection Timeout
(sec)
Number of seconds of inactivity that is allowed to elapse before a client is disconnected from the VCDS.
VQE-C Channel Lineup
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
5-5
Chapter 5 Using the VCDS AMT
Viewing VCDS Configuration and Statistics
5-6
Table 5-3 VCDS Configuration (continued)
Field Description
Validation Check • Pass—Channel configuration file has passed a validation check performed by VCDS.
• Fail—Channel configuration file has failed a validation check performed by VCDS.
Note On receiving the contents of the channel configuration file from the VQE Channel Provisioning Tool (VCPT), the VCDS validates its contents based on SDP syntax.
No. of Channels in Lineup
Lineup File name
Number of channels in the channel configuration file.
Full pathname of the channel configuration file.
Last Modified Date and time the channel configuration file was last modified.
VQE-C Group Map
Validation Check •
•
Pass—Client database file has passed the validation check performed by VCDS.
Fail—Client database file has failed the validation check performed by VCDS.
Note On receiving the client database file from the VQE-C system configuration provisioning server, the VCDS validates its contents based on an XML schema defined by Cisco.
No. of CNames in Map Number of customer names (CNames) in the client database file. A
CName is a unique identifier for a VQE-C.
Full pathname of the client database file. Map Filename
Last Modified Date and time the client database file was last modified.
VQE-C Network Configuration
Validation Check •
•
Pass—Group attribute file has passed the validation check performed by the VCDS.
Fail—Group attribute file has failed the validation check performed by the VCDS.
No. of Groups in Network
Configuration File
Network Configuration
Filename
Last Modified
Note On receiving the contents of the group attribute file from the
VQE-C system configuration provisioning server, the VCDS validates its contents based on an XML schema defined by
Cisco.
Number of attribute groups in the group attribute file. Each VQE-C is associated with at least one group of attributes. Each group of attributes can be associated with one or more VQE-Cs.
Full pathname of the group attribute file.
Date and time the group attribute file was last modified.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 5 Using the VCDS AMT
Change VCDS Logging
Viewing VCDS Statistics
When you click the Statistics tab, the VCDS AMT displays the VCDS Statistics window (
).
Figure 5-4 VCDS Statistics Window
The VCDS Statistics window has the information listed in Table 5-4 .
Table 5-4 VCDS Statistics
Field Description
VCDS Stats
Validation check •
•
Pass—Channel configuration, client database and group attribute files have all passed the validation check performed by VCDS.
Fail—One or more channel configuration, client database, or group attribute files have failed the validation check performed by VCDS.
Number of clients currently connected to VCDS.
Current Open
Connections
Total Requests
Received
Total number of Real Time Streaming Protocol (RTSP) requests received from
STBs.
Total Responses Sent Total number of RTSP responses sent to STBs.
Change VCDS Logging
When you click Logging in the navigation tree, VCDS AMT displays the logging priority levels
(
) for VCDS. The priority levels allow you to control the logging level for system messages for the VCDS process. All VCDS system messages are written to the file /var/log/vqe/vqe.log. In addition, you can send system messages to remote servers for centralized logging. For information on
configuring remote syslog servers, see the “Remote Syslog Hosts” section on page 2-28 .
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
5-7
Change VCDS Logging
Figure 5-5 Logging Priority Levels
Chapter 5 Using the VCDS AMT
To change a VCDS logging priority level, click the button next to the level you want and click Apply.
In VCDS AMT, the logging priority levels are listed from least verbose to most verbose. The Emergency level generates the smallest number of messages, and the Info level generates the greatest number of messages. The default value is Warning.
When you select a logging level, log messages are generated for the levels below that level. For example, when the level is set to Error, messages are generated for Emergency, Alert, Critical, and Error.
The selected logging priority level does not persist when the VCDS service is stopped. When VCDS restarts, the logging priority level goes back to the default (Warning).
5-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 5 Using the VCDS AMT
Change VCDS Debugging
Change VCDS Debugging
When you click Debugging in the navigation tree, the debugging options for the VCDS are displayed.
Figure 5-6 shows the debug options. The options allow you to control the types of debugging messages
that are written to the syslog file. Debug messages are written to the file /var/log/vqe/vqe.log.
Figure 5-6 Debug Components
OL-30119-01
To change VQE-S debugging, follow these steps:
Step 1
Step 2
Step 3
In the VCDS AMT navigation tree, click Debugging.
The debug flags for VCDS are displayed.
To enable a debugging flag, click the check box in the On/Off column, or to disable an enabled flag click the check box to uncheck it.
Click Apply.
The selected debugging options are enabled.
Note The selected debugging options do not persist when the VCDS service is stopped. When the
VCDS restarts, debugging goes back to the default—no options are enabled. Debug filters are always disabled.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
5-9
Change VCDS Debugging
Chapter 5 Using the VCDS AMT
5-10
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
C H A P T E R
6
Troubleshooting VQE Software Components
This chapter describes how to identify and remedy problems related to the Cisco VQE-S (VQE-S), the
VQE-S Application Monitoring Tool (AMT), and the VQE Channel Provisioning Tool (VCPT). This chapter contains the following major topics:
•
•
•
•
•
•
VQE Logging and Log Files, page 6-2
VQE Files, Directories, and Permissions, page 6-3
VQE-S and VQE Tools Server Troubleshooting, page 6-7
RCC Troubleshooting, page 6-15
•
•
•
•
Using the vqereport Command, page 6-29
Gathering Information for a Service Request, page 6-30
Stopping, Starting, and Restarting VQE-S, page 6-30
Stopping, Starting, and Restarting VCDS, page 6-31
Resetting the Root Password on the VQE-S or VQE Tools Server, page 6-31
Useful Linux Tools
provides information on some Linux commands that are particularly useful for troubleshooting
VQE software components.
Table 6-1 Useful Linux Commands
Command
arp
ethtool
ifconfig
ip
netstat
Description
Manipulates the ARP cache of the kernel
Displays or changes Ethernet card settings
Configures a network interface
Notes
—
Detailed status on an Ethernet interface
Traditional interface configuration and status
Shows or manipulates routing, devices, policy routing, and tunnels
Most useful interface to all Linux networking
Displays network connections, routing tables, interface statistics, masquerade connections, and multicast memberships
Provides traditional network state information
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-1
Chapter 6 Troubleshooting VQE Software Components
VQE Logging and Log Files
Table 6-1 Useful Linux Commands (continued)
Command Description
ping
tcpdump
Sends ICMP ECHO_REQUEST to network hosts
Dumps and analyzes traffic on a network
Notes
—
Captures packet data
VQE Logging and Log Files
VQE-related log entries can provide useful information for troubleshooting. The VQE-related log files are described in these sections:
•
VQE Server and VQE Tools Logging and Log Files, page 6-2
•
VQE-S AMT, VCDS AMT, and VCPT Logging and Log Files, page 6-3
VQE Server and VQE Tools Logging and Log Files
The VQE Server (VQE-S) logging is based on the syslog-ng utility, which is part of the inetutils package in Linux. The following is a typical VQE-S log entry:
Oct 22 08:42:03 minnie vqes_mlb: <<%VQES_MLB-3-MLB_NIC_DOWN>> Network interface eth3 went down.
•
•
•
Every logged message contains the following five fields in this order:
• Timestamp (For example, Oct 22 08:42:03)
Host name (For example, minnie)
Name of process logging the message (For example, vqes_mlb)
•
Identity string—FACILITY-SEVERITY-MNEMONIC (For example,
<<%VQES_MLB-3-MLB_NIC_DOWN>>)
Message text (For example, Network interface eth3 went down.)
For information on VQE system messages, see
Appendix C, “VQE System Messages.”
By default, the VQE-S and VQE Tools system messages are written to the file /var/log/vqe/vqe.log. The location of the file is configured in the /etc/syslog.conf file. For information on configuring VQE-S logging, see the
“Change VQE-S Logging” section on page 4-33
.
The VQE-S and VQE Tools log files are rotated by logrotate. The logrotate facility is configured to rotate a log file when it is larger than 20 MB. The old versions of the log files are rotated up to 20 times before being removed.
Note If you move the VQE log file to another directory (for example, when backing up log files), be sure to stop the syslog-ng daemon before moving the vqe.log file. If syslog-ng is started with no vqe.log file in the /var/log/vqe directory, syslog-ng creates the vqe.log file.
In addition, you can send system messages to remote servers for centralized logging. For information on configuring remote syslog servers, see the
“Remote Syslog Hosts” section on page 2-28
.
6-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
VQE Files, Directories, and Permissions
VQE-S AMT, VCDS AMT, and VCPT Logging and Log Files
The VQE-S AMT, VCDS AMT, and VCPT are all web applications that make use of the Apache Tomcat application server. Apache Tomcat uses the log4j logging system. For the VQE-S AMT, the VCDS AMT, and the VCPT, the logging output is configured by these log4j configuration files:
• For the VQE-S AMT and the VCDS AMT, the configuration file is located at
/usr/share/tomcat5/webapps/ems/WEB-INF/classes/ log4j.properties.
• For the VCPT, the configuration file is located at
/usr/share/tomcat5/webapps/vcpt/WEB-INF/classes/ log4j.properties.
By default, the log files for the VQE-S AMT, the VCDS AMT, and the VCPT are saved in these locations:
• For the VQE-S AMT and the VCDS AMT, the log files (vqe.log) are saved in the
/usr/share/tomcat5/logs directory.
For VCPT, the log files (vcpt.log) are saved in /usr/share/tomcat5/logs directory. •
lists the most important default log4j configuration settings for VQE-S AMT, VCDS AMT, and VCPT logging.
Table 6-2 Log4j Default Configuration for VQE-S AMT, VCDS AMT, and VCPT
Configuration Property
Logging priority level
Default Setting
Warning
Logging output
Maximum size of the log file before it rotates
Maximum number of backup files 4
Log messages are written to both the console and the log file
100 KB
For information on configuring the log4j.properties file, see the log4j documentation at these URLs: http://tomcat.apache.org/tomcat-5.5-doc/logging.html
http://logging.apache.org/log4j/1.2/manual.html
VQE Files, Directories, and Permissions
If you encounter a problem related to VQE-related files, directories, or permissions, use the information in the following tables to resolve the issues:
•
provides information for the CDE that hosts the VQE-S.
•
provides information for the CDE that hosts VCPT, VCDS AMT, and VCDS.
These sections provide additional information on resolving problems:
•
•
Changing Permissions, page 6-5
Replacing a Lost or Corrupt VQE File, page 6-5
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-3
Chapter 6 Troubleshooting VQE Software Components
VQE Files, Directories, and Permissions
Table 6-3
File or Directory
VQE-S Files, Directories, and Permissions
/etc/opt/vqes (directory)
/etc/opt/vqes/vcdb.conf
/etc/opt/vqes/vcdb.conf.sample
/etc/opt/vqes/vqe_channels.cfg
/opt/vqes (directory)
/opt/vqes/bin (directory)
Required Permissions, Owner, and Group drwx------ vqes vqes
-rw-r--r-- root root
-r-------- vqes vqes
-rw-r--r-- vqes vqes drwxr-xr-x vqes vqes drwxr-xr-x vqes vqes
/opt/vqes/bin/mlb
/opt/vqes/bin/mlb_ethtool
/opt/vqes/bin/process_monitor
/opt/vqes/bin/stun_server
/opt/vqes/bin/vqe_cfgtool
/opt/vqes/bin/vqereport
/opt/vqes/bin/vqes_dp
/opt/vqes/bin/vqes_bin.sha1sum
/etc/syslog-ng/syslog-ng.conf
/opt/syslog-ng/sbin/syslog-ng
/opt/vqes/bin/xmlrpc
/var/log/vqe (directory)
/var/log/vqe/vqe.log
-r-xr-xr-x root root
-r-sr-x--- root vqes
-r-xr-xr-x root root
-r-xr-xr-x root root
-r-x------ vqes vqes
-r-x------ root root
-r-xr-xr-x root root
-r--r----- vqes vqes
-rw-r--r-- 1 root root
-rwxr-xr-x root root
-r-xr-xr-x vqes vqes drwxr-xr-x vqes vqes
-rw------- vqes vqes
Table 6-4
File or Directory
VQE Tools Files, Directories, and Permissions
/etc/opt/vqes (directory)
/etc/opt/vqes/vcdb.conf
/etc/opt/vqes/vcdb.conf.sample
Required Permissions, Owner, and Group drwx------ root root
-rw-r--r-- root root lrwxrwxrwx root root
/etc/opt/vqes/vqec_channels.cfg
/etc/opt/vcpt (directory)
/etc/opt/vcpt/data (directory)
VCPT configuration files in
/etc/opt/vcpt/data
-rw--r--r-- root root drwxr-xr-x root root drwxr-xr-x root root
-rw-r--r-- root root
Description
—
VCDB configuration file
VCDB sample configuration file
VQE-S channel configuration file
—
VQE-S binary directory
VQE-S feedback target flush script
VQE-S Multicast Load Balancer process
VQE-S Ethernet utility for Multicast Load
Balancer
VQE-S Process Monitor process
VQE-S STUN Server process
vqe_cfgtool command
vqereport command
VQE-S Control Plane process
VQE-S Data Plane process
SHA-1 checksums list
VQE-S syslog configuration file
VQE-S syslog-ng process
XML-RPC client utility
VQE log file directory
VQE system messages log file
Description
—
VCDB configuration file
Link to the VCDB sample configuration file
VCDB sample configuration file
VCDS channel configuration file
—
Directory for VCPT configuration files
VCPT configuration files (Filenames are user-defined and vary.)
6-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
VQE Files, Directories, and Permissions
Table 6-4
File or Directory
VQE Tools Files, Directories, and Permissions (continued)
/etc/opt/vcpt/data/sdp (directory)
Required Permissions, Owner, and Group drwxr-xr-x root root
SDP-formatted files in
/etc/opt/vcpt/data/sdp
/opt/vqes (directory)
/opt/vqes/bin (directory)
/opt/vqes/bin/vcds_send_file
/opt/vqes/bin/vqe_cfgtool
/opt/vqes/bin/vqereport
/etc/syslog-ng/syslog-ng.conf
/opt/syslog-ng/sbin/syslog-ng
/var/log/vqe (directory)
/var/log/vqe/vqe.log
-rw-r--r-- root root drwxr-xr-x vqes vqes drwxr-xr-x vqes vqes
-r-x------ vqes vqes
-r-x------ vqes vqes
-r-x------ root root
-rw-r--r-- 1 root root
-rwxr-xr-x root root drwxr-xr-x vqes vqes
-rw------- vqes vqes
Description
Directory for SDP-formatted files that VCPT creates for each valid VCPT configuration
SDP-formatted files for each valid VCPT configuration
—
—
Command to send a client database file and group attribute file to VCDS
vqe_cfgtool command
vqereport command
VQE-S syslog configuration file
VQE-S syslog-ng process
VQE log directory
VQE system messages log file
Changing Permissions
To change permissions on a file or directory, use the chmod command:
Step 1
Step 2
If needed, log in as root on the CDE that hosts VQE-S or that hosts VCPT.
To change permissions, issue the following command:
chmod mode file_or_dir_name
In the preceding command, the two arguments are as follows:
• mode specifies the correct permissions.
• file_or_dir_name specifies the file or directory whose permissions is set.
For example:
[root@system]# chmod 555 /opt/vqes/bin/vqes_cp
For information on setting permissions, see the man page for the chmod command.
Replacing a Lost or Corrupt VQE File
If a required VQE file that has not been backed up is lost or corrupted, you must reinstall the version of the VQE software that the CDE server is running. To preserve the current VQE configuration, the software reinstallation should be an ISO full upgrade. For information on VQE software installation, see the Release Notes for Cisco CDA Visual Quality Experience Application, Release 3.7.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-5
Chapter 6 Troubleshooting VQE Software Components
VQE Files, Directories, and Permissions
If a configuration file located in the directories under /etc is lost or corrupted and was not backed up, you can do one of the following:
•
•
Use the vqe_cfgtool command with the -fix_config option to discard the current copy of each /etc configuration file where there is a checksum mismatch and replace it with the original copy of the file that comes with the RPM package. Then apply the current VCDB configuration to the /etc configuration files using the vqe_cfgtool command and the -apply option.
Get a copy of the factory default version of the configuration file from the /vqe-etc/etc-pristine directory. To restore the lost or corrupted file, copy the factory default configuration file to its correct location under /etc, and apply the current VCDB configuration to the /etc configuration files using the vqe_cfgtool command and the -apply option.
For information on the vqe_cfgtool command, see the
“Using the VQE Configuration Tool
Command-Line Options” section on page 7-18
.
6-6
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
VQE-S and VQE Tools Server Troubleshooting
VQE-S and VQE Tools Server Troubleshooting
This section provides information on troubleshooting the following specific problems that can occur
with a VQE-S or VQE Tools server. Table 6-5 lists the troubleshooting topics by the category of the
problem.
Table 6-5 Troubleshooting Topics by Problem Category
Problem Category
Monitoring a VQE-S
VQE-S and VQE Tools servers
VQE-S
VQE-S AMT
VCDS AMT
VCPT or other channel-provisioning servers*
Troubleshooting Topics
Monitoring Received Multicast Streams, page 6-8
Repeated Message on CDE Hosting VQE-S or VQE
Repeated Message on CDE Hosting VQE-S or VQE
VQE-S AMT, VCDS AMT, or VCPT Unavailable, page 6-10
Channels Are Not Displayed in VQE-S AMT, page 6-11
VQE-S AMT Channels Status Summary Has No
VQE-S AMT, VCDS AMT, or VCPT Unavailable, page 6-10
VQE-S AMT, VCDS AMT, or VCPT Unavailable, page 6-10
VCPT Fails to Initialize, page 6-12
Channel-Provisioning Server Cannot Send Channel
Information to VQE-S: Trusted Provisioning Client
Channel-Provisioning Server Cannot Send Channel
Information to VQE-S: SSL Certificates Problems, page 6-13
Unable to Connect Error When VCPT Tries to Send
Channel Information, page 6-14
Internal Server Error When VCPT Tries to Send
Channel Information to VQE-S, page 6-15
* Some VCPT troubleshooting topics apply to other channel-provisioning servers, such as Cisco IPTV
Services Delivery Server (ISDS).
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-7
Chapter 6 Troubleshooting VQE Software Components
VQE-S and VQE Tools Server Troubleshooting
Monitoring Received Multicast Streams
For troubleshooting the VQE-S, using the VQE-S AMT to monitor received multicast streams is recommended.
We recommend that you use the VQE-S AMT to monitor received multicast streams. In the VQE-S AMT
Channel Statistics window for each channel (see
), the Lost RTP Packets field for the Channel
Input Stream is a per-channel counter that provides the number of missing RTP packets. The Lost RTP
Packets counter increments when an RTP packet is sent for the original source stream of the channel but is not received by the VQE-S.
Figure 6-1 Lost RTP Packets
6-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
VQE-S and VQE Tools Server Troubleshooting
Repeated Message on CDE Hosting VQE-S or VQE Tools
Symptom: During initial system configuration, a new Cisco CDE hosting the VQE-S or VQE Tools boots successfully, the root password is set successfully, but the following message displays repeatedly:
SIOCGIFADDR: Cannot assign requested address
SIOCGIFADDR: Cannot assign requested address
SIOCGIFADDR: Cannot assign requested address
SIOCGIFADDR: Cannot assign requested address
SIOCGIFADDR: Cannot assign requested address
SIOCGIFADDR: Cannot assign requested address
Explanation: This error can occur when you configure the CDE server manually (rather than use the vqe_cfgtool). The message may display so frequently that it is difficult to edit a file to continue the initial system configuration.
The message can be caused by an Ethernet interface configuration issue in the ifcfg-eth# files (ifcfg-eth1, ifcfg-eth2, and so on).
Remedy: Look for Ethernet interface address or other errors in the four ifcfg-eth# files. Use a text editor to correct any errors.
Use the ifconfig -a command to verify that the addresses specified in the ifcfg-eth# files have been assigned to the interfaces.
Continue with the initial configuration tasks.
Performing a Date and Time Change with NTP
When performing a date and time change with NTP, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Log in as root.
Stop the VQE-S services by issuing the following command:
[root@system]# service vqes stop
Stop the ntpd service by issuing the following command:
[root@system]# service ntpd stop
If needed, set the time zone with the vqe_cfgtool command using the -config option. Use the System
Parameters menu on the Configuration Tool and the Timezone choice.
Set the system date and time to a date and time close to the NTP server date and time by issuing the following command:
date -s “date_time_string”
For example:
[root@system]# date -s "16:55:30 July 7, 2008"
Synchronize the clock to the configured NTP servers by issuing the following command:
[root@system]# ntpd -q
If the system clock is off by a lot, the command takes considerable time to return.
Start the ntpd service by issuing the following command:
[root@system]# service ntpd start
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-9
Chapter 6 Troubleshooting VQE Software Components
VQE-S and VQE Tools Server Troubleshooting
Step 8 Synchronize the hardware clock by issuing the following command:
[root@system]# /sbin/hwclock --systohc
Step 9 Check NTP synchronization by issuing the following command:
[root@system]# ntpq -p
Step 10 Reboot the VQE-S by issuing the following command:
[root@system]# init 6
Performing a Date and Time Change with the Linux date Command
When performing a time and date change with the Linux date command only, perform the following commands:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Log in as root.
Stop the VQE-S services by issuing the following command:
[root@system]# service vqes stop
If needed, set the time zone with the vqe_cfgtool command using the -config option. Use the System
Parameters menu on the Configuration Tool and the Timezone choice.
Set the system date and time by issuing the following command:
date -s “date_time_string”
For example:
[root@system]# date -s "16:55:30 July 7, 2008"
Synchronize the hardware clock by issuing the following command:
[root@system]# /sbin/hwclock --systohc
Reboot the VQE-S by issuing the following command:
[root@system]# init 6
VQE-S AMT, VCDS AMT, or VCPT Unavailable
Symptom: The browser displays the message Page Cannot Be Found (status code 404) or Service
Temporarily Unavailable (status code 503) even if the user enters a valid IP address or fully qualified domain name to browse the VQE-S AMT, VCDS AMT, or VCPT.
Explanation: The VQE-S AMT, VCDS AMT, and VCPT require the Apache HTTP server service
(httpd) and the Apache Tomcat application server service (tomcat5) to be running. When you attempt to browse to the VQE-S AMT, VCDS AMT, or VCPT and one of these services is not running, the status codes are typically as follows:
•
•
“Page Cannot Be Found” (status code 404)—indicates that httpd is not running.
“Service Temporarily Unavailable” (status code 503)—indicates that tomcat5 is not running.
6-10
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
VQE-S and VQE Tools Server Troubleshooting
To check whether the httpd service is running, log in as root and issue the following command:
[root@system]# /sbin/service httpd status httpd (pid 15836 13179 2593 2592 2591 2590 2589 2588 2587 2586 2576) is running...
To check whether the tomcat5 service is running, log in as root and issue the following command:
[root@system]# service tomcat5 status
Tomcat is running...
Remedy: If either httpd or tomcat5 is not running, log in as root and start the services that are stopped as follows:
[root@system]# service httpd start
[root@system]# service tomcat5 start
Verify that the httpd and tomcat5 services are running, as shown earlier in the Explanation section. If the httpd or tomcat5 processes continue to fail, check the log files for the services to determine the cause.
• httpd log file is /etc/httpd/logs/error_log.
• tomcat5 log files are /var/log/tomcat5/catalina.date.log.
For information on the log files for each service, see the vendor documentation for the Apache HTTP server or for the Apache Tomcat application server.
Channels Are Not Displayed in VQE-S AMT
Symptom: The VQE-S AMT does not display the channels after channels are defined in VCPT and channel information is pushed to the servers.
Explanation: The most likely reason why the VQE-S AMT does not display the channels is that the
VQE-S was not associated with the channels in VCPT.
To determine whether the channels are associated with this VQE-S, follow these steps:
Step 1
Step 2
Step 3
Log in to VCPT.
Click the Association tab.
Select the VQE Server in the Select Server pull-down menu.
The channels should be in the Selected group. Also, make sure the VQE-S is defined with the role
VQE-S. If the role is wrong, correct it with VCPT from the Servers tab. For information on updating server information, see the
“Viewing or Updating Server Information” section on page 3-17 .
If the channels are correctly associated with the VQE-S, it is possible that there were problems when the
VQE-S attempted to process the channels. Check the VQE-S log files for errors in channel processing.
For information on these log files, see the
“VQE Server and VQE Tools Logging and Log Files” section on page 2
.
Remedy: If the channels have not been associated with the VQE-S in VCPT, associate the channels with the VCPT from the Association tab. For information on associating channels with servers, see the
“Defining Channel Associations for a Server” section on page 3-19
.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-11
Chapter 6 Troubleshooting VQE Software Components
VQE-S and VQE Tools Server Troubleshooting
VQE-S AMT Channels Status Summary Has No Graphs
Symptom: In the AMT VQE-S Status window (
Figure 4-2 ), the Channels Status Summary does not have
graphs for the channels.
Explanation: If one or more channels are successfully created in the VQE-S AMT, the channels should appear in a Channels Status Summary graph of active, inoperative, and inactive channels in the VQE-S
Status window. To be displayed, the graphs require that Adobe Flash Player be installed on the computer that hosts the browser accessing the VQE-S AMT.
Remedy: Download and install Adobe Flash Player on the computer that hosts the browser used to access the VQE-S AMT. The software is free and can be found at this URL: http://get.adobe.com/flashplayer/
It is recommended that you close all other open browser windows before performing the installation.
VCPT Fails to Initialize
Symptom: VCPT fails to initialize when the VQE Tools server starts. The following error message is displayed:
Initialization Failed. VCPT Data directory is missing, please refer to the Cisco CDA VQE
Application User Guide - Working with VCPT Configuration Files section."
Explanation: For VCPT to initialize successfully, the following directories must exist:
• /etc/opt/vcpt/data
• /etc/opt/vcpt/data/sdp
One or both of these directories are missing and may have been accidentally deleted.
Remedy: To recreate the directories and start VCPT, follow these steps:
Step 1
Step 2
Step 3
Step 4
Login as root.
Determine which directory or directories are missing.
Create each missing directory using the permissions, owner, and group specified in
directory.
If up-to-date VCPT configuration files for the /etc/opt/vcpt/data directory are available in a set of backup files, the backup files can be copied to the /etc/opt/vcpt/data directory.
Note There is no need to copy backup files for the set of SDP-formatted files in the /etc/opt/vcpt/data/sdp directory. The VCPT creates the SDP-formatted files when a request is made to send channel information to the VQE-S or VCDS servers.
Step 5
Step 6
Restart the Apache Tomcat application server:
[root@system]# service tomcat5 restart
The VCPT is a web application and should initialize successfully.
To verify that the VCPT is accessible from a web browser, enter as the URL the IP address of the Cisco
CDE that hosts VCPT: https://ip_address_of_VCPT_host
6-12
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
VQE-S and VQE Tools Server Troubleshooting
Log in with a Linux username and password.
If you are able to log in successfully, the VCPT is running correctly.
Channel-Provisioning Server Cannot Send Channel Information to VQE-S:
Trusted Provisioning Client Problem
Symptom: The channel-provisioning server (for example, VCPT or Cisco IPTV Services Delivery
Server [ISDS]) cannot send channel information to a VQE-S.
Explanation: When the channel-provisioning server attempts to send channel information to a VQE-S, the send operation fails. On the VQE-S, the VQE Configuration Tool parameter Trusted Provisioning
Client is not configured with the IP addresses for the channel-provisioning server.
If VCPT is the channel-provisioning server and the send operation fails because the Trusted Provisioning
Client parameter is not configured with the IP addresses of the Ethernet interfaces on the VCPT host,
VCPT displays the following in the Status of Last Send column in its VCPT Servers Summary window:
Failed - Connection refused
In addition, the following error message is written to the VCPT log file (/usr/share/tomcat5/logs/vcpt.log):
ERROR: Unable to send the SDP File java.net.ConnectException: Connection refused
Remedy: Use the VQE Configuration Tool to configure the System Parameter > Trusted Provisioning
Client with the IP addresses of the channel-provisioning servers. For information on using the
Configuration Tool, see the
“Using the VQE Configuration Tool” section on page 7-3 .
Note If VCPT is the channel-provisioning server, the IP addresses of all Ethernet interfaces (that have been assigned IP addresses) on the VCPT host must be configured as trusted provisioning clients on the
VQE-S host.
Note If ISDS is the channel-provisioning server, for the Trusted Provisioning Clients, use the Broadcast
System IP Address, which is configured on the ISDS VASP List. The VASP List can be found on the
ISDS Administrative Console under ISDS > Network Element Provisioning > VASP.
Channel-Provisioning Server Cannot Send Channel Information to VQE-S: SSL
Certificates Problems
Symptom: The channel-provisioning server (for example, VCPT or ISDS) cannot send channel information to a VQE-S.
Explanation: When the channel-provisioning server attempts to send channel information to a VQE-S, the send operation fails. On the VQE-S or the channel-provisioning server or both, the Secure Sockets
Layer (SSL) certificates are not valid or the needed items have not been copied to the correct locations.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-13
Chapter 6 Troubleshooting VQE Software Components
VQE-S and VQE Tools Server Troubleshooting
If VCPT is the channel-provisioning server and the send operation fails because of SSL certificate problems, VCPT displays the following in the Status of Last Send column in its VCPT Servers Summary window:
Failed - Unable to find valid certification path to requested target
In addition, the following error message is written to the VCPT log file (/usr/share/tomcat5/logs/vcpt.log):
ERROR: Unable to send the SDP File javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Remedy: Make sure all SSL certificate-related items have been created correctly and the needed items have been copied to the correct locations on the VQE-S and on the channel-provisioning server. For information on setting up SSL certificates, see the
“Setting Up SSL Certificates” section on page 2-5 .
After the certificate-related items have been copied to the correct locations on the VQE-S and on the channel-provisioning server, restart the httpd and tomcat5 services on both servers. For example, login as root and issue the following commands on both servers:
[root@system]# service httpd restart
[root@system]# service tomcat5 restart
Note If the tomcat5 service is not running when you try to restart it, an exception is displayed on the console when the attempt is made to stop the service. The exception can be ignored.
Unable to Connect Error When VCPT Tries to Send Channel Information
Symptom: When the VCPT tries to send channel information to a VQE-S or VCDS, the send operation fails. In VCPT, the Servers tab displays “Failed - Unable to connect with Server” in the Status of Last
Send column.
Explanation: Possible causes for the failed send operation are that the Apache HTTP server service (httpd) or the Apache Tomcat application server service (tomcat5) on the target VQE-S or VQE
Tools server (hosting VCDS) is not running.
To check whether the httpd service is running, log in as root and issue the following command:
[root@system]# service httpd status httpd (pid 15836 13179 2593 2592 2591 2590 2589 2588 2587 2586 2576) is running...
To check whether the tomcat5 service is running, log in as root and issue the following command:
[root@system]# service tomcat5 status
Tomcat is running...
Remedy: If either httpd or tomcat5 is not running, log in as root and start the services that are stopped as follows:
[root@system]# service httpd start
[root@system]# service tomcat5 start
Verify that the httpd and tomcat5 services are running, as shown earlier in the Explanation section. If the httpd or tomcat5 processes continue to fail, check the log files for the services to determine the cause.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-14 OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
• httpd log file is /etc/httpd/logs/error_log.
• tomcat5 log files are /var/log/tomcat5/catalina.date.log.
For information on the log files for each service, see the vendor documentation for the Apache HTTP server or for the Apache Tomcat application server.
Internal Server Error When VCPT Tries to Send Channel Information to VQE-S
Symptom: When VCPT tries to send channel information to the VQE-S, you get an “Internal Server
Error.” Java exceptions in the catalina.out file indicate that there is an address conflict or unreachable address.
Explanation: The Internal Server Error is displayed when you use the VCPT to send channel information to a VQE-S. The Status of Last Send column on the VCPT Servers tab shows the error.
From the CDE that hosts the VQE-S, you are able to successfully ping the machine running the web browser used for the VQE-S AMT, and ping the CDE hosting VCPT.
In the /usr/share/tomcat5/logs/catalina.out file of the Apache Tomcat application server, there are Java exceptions indicating an address conflict or unreachable address. For example: java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(Unknown Source)
...
java.net.SocketException: Network is unreachable at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source)
Remedy: The Internal Server Error can be caused by one or more errors in the /etc/hosts file on the CDE that hosts the VQE-S. Check the /etc/hosts file for typing or syntax errors, correct them, and save the file. Reboot the CDE.
If you still receive the same Internal Server Error and Java exceptions, check the following files to see if you can find some indication for what is causing the error.
•
•
•
•
•
/var/log/vqe/vqe.log
/var/log/httpd/error_log
/var/log/httpd/access_log
/usr/share/tomcat5/logs/catalina.out
/var/log/messages
RCC Troubleshooting
Symptom: If a rapid channel change (RCC) fails or there is degradation in the performance of an RCC, video freeze or macroblocking may be observed. The following section describes how to troubleshoot
RCC problems from the VQE-S.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-15
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
VQE-S RCC Troubleshooting
The section lists possible explanations for RCC problems and provides a remedy for each explanation:
•
Channel is not configured on the VQE-S, page 6-16
•
•
•
•
•
•
•
•
•
•
Channel is not active on the VQE-S, page 6-16
RCC is disabled on the channel, page 6-17
No connectivity between the VQE-C and the FBT on the VQE-S, page 6-18
No connectivity between the VQE-C and the VQE-S, page 6-18
RCC refused by the VQE-S control or data planes, page 6-18
RCC refused by the VQE-S—invalid e-factor, page 6-19
RCC refused by the VQE-S—insufficient bandwidth, page 6-19
MPEG Parser is unable to locate the burst start point, page 6-20
VQE-S MPEG Parser is unable to locate the ECM PID, page 6-21
Burst start point not found within the backfill range, page 6-21
•
No burst start point found—stream is invalid, page 6-22
To perform the troubleshooting activities described in this section you need to log in to the VQE-S AMT.
For information on accessing the VQE-S AMT, see
“Logging into and Navigating in the VQE-S AMT” section on page 4-2
.
To troubleshoot RCC problems, enable debugging of RCC messages on the VQE-S and analyze the
debug logs. To enable debugging, see the “Change VQE-S Debugging” section on page 4-33
. The debug messages are written to the file /var/log/vqe/vqe.log. Alternatively, to view RCC failures, click the channel name in the navigation tree in the VQE-S AMT and click the RCC Troubleshooting tab. The
RCC Troubleshooting tab displays the last twenty RCC failures on this channel.
Channel is not configured on the VQE-S
Explanation: An RCC fails if the new channel is not configured on the VQE-S. To verify that a channel is configured on the VQE-S, click the Channel node in the navigation tree, and verify that the new channel is listed in the channel lineup.
Remedy: If the channel is not displayed in the channel lineup, add the channel to the channel configuration using the VCPT. For more information on adding channels, see the
“Adding a Channel” section on page 8
. After the channel has been added to the channel configuration, send the updated configuration to the VQE-S and the VCDS. For information on deploying channel configurations, see the
“Sending or Pushing Channel Information to Servers” section on page 5
.
Channel is not active on the VQE-S
Explanation: An RCC fails if the new channel is not active on the VQE-S or if the channel is not receiving RTP packets. To verify that a channel is active on the VQE-S and receiving RTP packets, do the following:
Step 1
Step 2
Step 3
Click the Channel node in the navigation tree to expand the channel lineup.
Click the channel in the lineup.
Click the Status/Statistics tab.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-16 OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Verify that the Status field is set to active.
Verify that the value of the Received Packets field is greater than zero.
Take note of the value of the Average Stream Rate(Mbps) field.
Click the Configuration tab.
Take note of the value of the Multicast IP Address field.
Take note of the value of the Bit Rate(Kbps) field for the original stream.
Verify that the Average Stream Rate(Mbps) for the original stream is within 10% of the configured Bit
Rate (Kbps) for the original stream.
Remedy: If there is a mismatch between the expected bit rate and the actual bit rate, ensure that the configured bit rate represents the peak bit rate expected on the channel.
If the Status of the channel is inactive or if the number of received packets is zero, check that the interface on which the channel has joined is properly configured. To verify that the interface has been configured correctly, do the following:
Step 1
Step 2
Step 3
Click the Interfaces node in the navigation tree.
In the Multicast Group table, locate the multicast address of the channel and identify the name of the interface associated with the channel.
Verify that the interface has been configured correctly.
Note 10 or 100 Mbps interfaces are not supported on the VQE-S.
If the interface is configured correctly, verify that the multicast stream is being received by the networking stack. To output a record of all TCP traffic to and from an Ethernet interface to the screen, use secure shell (SSH) to connect to the VQE-S and run the command /sbin/tcpdump -i <ethx> host
<multicast_address> on the interface as user root.
RCC is disabled on the channel
Explanation: An RCC fails if RCC is disabled on the new channel. To verify that RCC is enabled on a channel, do the following:
Step 1
Step 2
Step 3
Step 4
Click the Channel node in the navigation tree to expand the channel lineup.
Click the new channel in the lineup.
Click the Configuration tab.
Verify that the Rapid Channel Change field is set to true.
Remedy: If the Rapid Channel Change parameter is set to false for the channel, update the channel configuration in VCPT by clicking the Enable Rapid Channel Change check box. For information on updating channel information, see the
“Viewing or Updating Channel Information” section on page 12
.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-17
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
After RCC has been enabled in the channel configuration, send the updated configuration to the VQE-S and the VCDS. For information on deploying channel configurations, see the
Channel Information to Servers” section on page 5
.
No connectivity between the VQE-C and the FBT on the VQE-S
Explanation: An RCC fails if there is no connectivity between the VQE-C and the feedback target (FBT) of the new channel on the VQE-S.
To verify that the VQE-C can connect to the feedback target of the new channel, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Click the Channel node in the navigation tree to expand the channel lineup.
Click the new channel in the lineup.
Click the Configuration tab.
Take note of the IP address in the Feedback Target Address field.
Ping the feedback target IP address from the VQE-C to verify that it is reachable.
Remedy: If there is no connectivity between the VQE-C and the FBT on the VQE-S, check that the channel is active. A channel that is inactive does not have a FBT that is reachable. If the channel is active and a FBT for this channel does not exist, check the VQE system messages in the /var/log/vqe/vqe.log file for a FBT failure message.
No connectivity between the VQE-C and the VQE-S
Explanation: An RCC fails if there is no connectivity between the VQE-C and the VQE-S.
To verify that the VQE-C can connect to the service interfaces of the VQE-S, do the following:
Step 1
Step 2
Step 3
Click the Interfaces node in the navigation tree.
In the Interfaces Summary Table, take note of the IP address of each service interface.
Ping the IP address of each service interface from the VQE-C to ensure it is reachable.
Remedy: If there is no connectivity between the VQE-C and the VQE-S service interfaces, fix problems in the network relating to cabling, interface configurations, and routing tables.
RCC refused by the VQE-S control or data planes
An RCC fails if the RCC is refused by the VQE-S control plane (CP) or data plane (DP). To verify that an RCC has not been refused for a channel by the VQE-S CP or DP, do the following:
Step 1
Step 2
Step 3
Click the Channel node in the navigation tree to expand the channel lineup.
Click the new channel in the lineup.
Click the Advanced button.
6-18
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
Step 4 Under RCC Debug Counters, verify that the values of the Refused RCC—RCC disabled on DP and
Refused RCC—RCC disabled on CP counters are zero.
Explanation: If the counter Refused RCC-RCC disabled on DP counter has been incremented, the RCC has been refused by the VQE-S DP.
Remedy: If an RCC has been refused by the VQE-S DP, verify that the following line is not included in the /etc/opt/vqes/vcdb.conf file: vqe.vqes.rcc_disable="true"
If the line is present in the file, remove the line, and use the vqe_cfgtool command with the -apply option to apply the change to the VQE-S.
Note The parameter vqe.vqes.rcc_disable is a hidden parameter and should only be used on the direction of the a Cisco technical support representative.
If the counter Refused RCC-RCC disabled on CP is incremented, the RCC has been refused by the
VQE-S CP. If the Refused RCC - RCC disabled on CP counter has been incremented, contact your Cisco technical support representative.
RCC refused by the VQE-S—invalid e-factor
Explanation: An RCC fails if the VQE-S refuses the RCC request because the e-factor is invalid. To verify that a valid e-factor has been configured on the VQE-S, check the that the value of the VCDB parameter vqe.vqes.excess_bw_fraction is within the defined range of 3 to 500 in the
/etc/opt/vqes/vcdb.conf file.
Remedy: If the e-factor value is outside of the permitted range, change the value of the parameter vqes.excess_bw_fraction in the /etc/opt/vqes/vcdb.conf file, and use the vqe_cfgtool command with the
-apply option to apply the change to the VQE-S.
RCC refused by the VQE-S—insufficient bandwidth
Explanation: An RCC fails if the VQE-S refuses an RCC because there is not enough bandwidth available on the access link to the VQE-C to perform the RCC.
To verify that there is sufficient bandwidth available to perform an RCC, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Click the Error Repair and RCC node in the navigation tree to expand the channel lineup.
Click the Statistics tab.
Click the Advanced button.
Verify that the total bandwidth available as displayed in the System available output b/w (Mbps) counter under the section CP Output Bandwidth Stats matches the expected total bandwidth of the service interfaces. For example, if two Gigabit Ethernet interfaces are configured and used for the access link, then the value of the System available output b/w (Mbps) counter should be 2000 Mbps.
Verify that the value of the Committed RCC output b/w (Mbps) counter is less than the value of the RCC output b/w budget (Mbps) counter.
Click the Interfaces node in the navigation tree.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-19
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
Step 7 Verify that all service interfaces have a role of service and have a status of Up. Verify that each service interface is a 1000 Mbps interface.
Remedy: If a service interface is a 10 Mbps or a 100 Mbps interface, you need to upgrade to a 1000
Mbps interface. If the committed budget for RCC is close to the maximum budget for RCC, you are close to reaching the scalability limit of the VQE-S.
MPEG Parser is unable to locate the burst start point
An RCC fails if the VQE-S MPEG parser is unable to locate the burst start point (that is, the Transport
Stream Random Access Point [TSRAP]). To verify that the VQE-S is correctly identifying the burst start point, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Click the Channel node in the navigation tree to expand the channel lineup.
Click the new channel in the lineup.
Click the Advanced button.
Locate the MPEG Parser: Locating a Random Access Point section.
Verify that the value of the Num RAPs found by Adaptation Field RAI bit counter and Num RAPs found by locating I-frame or IDR counter is zero.
Explanation: If the value of the Num RAPs found by Adaptation Field RAI counter and the Num RAPs found by locating I-frame or IDR counter has been incremented, it is likely that the VQE-S is unable to find a TSRAP. The VQE-S is optimized to skip the parsing of the Elementary Stream (ES) which contains the actual group of pictures (GOPs). Instead, the VQE-S uses the random_access_indicator
(RAI) bit in the MPEG2-TS packet header. However, in some deployments, the RAI bit is not set.
Without an RAI, random access points (RAPs) may be overlooked as valid RCC burst start points.
Remedy: To prevent the VQE-S from skipping the ES, add the following line to the
/etc/opt/vqes/vcdb.conf file: vqe.vqes.max_rai_gap=”0”
Use the vqe_cfgtool command with the -apply option to apply the change to the VQE-S.
Explanation: If RCCs continue to fail, it may be that the VQE-S is still unable to find a TSRAP. The
VQE-S is also optimized to skip to the beginning of the next MPEG Packetized Elementary Stream
(PES) once it determines the picture type. In some deployments, more than one GOP is contained in the
PES header. If multiple GOPs are skipped, some RAPs may be overlooked as valid RCC burst start points.
Remedy: To prevent the VQE-S from skipping multiple GOPs in a PES header, add the following line to the /etc/opt/vqes/vcdb.conf file: vqe.vqes.mpeg_search_limit_disable=”true”
Use the vqe_cfgtool command with the -apply option to apply the change to the VQE-S.
6-20
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
OL-30119-01
RCC Troubleshooting
VQE-S MPEG Parser is unable to locate the ECM PID
Explanation: When the new channel is scrambled, an RCC fails if the VQE-S MPEG parser is unable to locate the Entitlement Control Messages (ECM) Packet identifier (PID). To verify that the VQE-S is correctly locating the ECM PID, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Click the Channel node in the navigation tree to expand the channel lineup.
Click the new channel in the lineup.
Click the Advanced button.
Locate the MPEG Parser: PIDs section.
Verify that the list of PIDs includes a PID Type (ES Video), with a Stream Type of H.262 or H.264.
Verify that the list of PIDs includes a PID Type (ECM PID).
Verify that none of the error counters associated with either the ES Video PID or the ECM PID have been incremented.
Remedy: If either the ES Video PID or the ECM PID are not included under the list of PIDs, or if the error counters associated with either PID have been incremented, check the stream configuration and contact your Cisco technical support representative.
Burst start point not found within the backfill range
Explanation: An RCC is rejected by the VQE-S if it is unable to find a burst start point (TSRAP) within the backfill range sent by the VQE-C. The VQE-C sends the parameters min_rcc_backfill and max_rcc_backfill in its RCC request. The VQE-S must find a TSRAP within the range provided by these two parameters. If none is found, the RCC is rejected.
The following is an example of a VQE-C PLI APP message (that is, a request for an RCC) taken from a
VQE-S log file:
Feb 5 10:35:53 saturn-iptv vqes_cp: <{vqes-era}>Computed PLII APP received=TRUE, min_rcc_backfill=200, max_rcc_backfill=2105; use min_ref_a=1233848151597, max_age=1233848153492, idr=0
In this example, the VQE-C sends a min_rcc_backfill value of 200 ms and a max_rcc_backfill value of
2105 ms.
The following is an example of the message sent from the VQE-S in response to the RCC request:
Feb 5 10:35:53 saturn-iptv vqes_cp: <{vqes-era}>Candidate TSRAP #0
(96598729:1), ref_time=1233848153147(0.545301 secs ago), is_idr:1, rai:0, pts:10970145, pts_pcr_offset:74430[90kHz ticks]
In this example, the VQE-S indicates that it is selecting a burst start point that is 545 ms old and therefore, within the defined range.
If several RCCs have been rejected, check the VQE-S logs to verify that the backfill range for each rejected RCC was sufficiently large enough for the VQE-S to find burst start point within the backfill range.
Remedy: It is usually not a viable option to change the size of a GOP stream. Instead, consider increasing the size of the packet pool. For more information on sizing the packet pool, see VQE-C System
Integration Guide.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-21
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
No burst start point found—stream is invalid
Explanation: An RCC is rejected by the VQE-S if it is unable to locate a burst start point (TSRAP) in the stream sent by the stream source for one of the following reasons:
• Stream is of a type not supported by the VQE-S— VQE-S supports streams of type MPEG-2 part 2
(H.262) and MPEG-4 part 10 (H.264). The VQE-S does not support other stream types such as
MPEG-4 part 2 (H.263) or DigiCipher II (DC II).
•
•
•
•
Stream is empty or it is sent with null-padded packets.
Stream is using a Conditional Access System (CAS) that is not ETSI ETR 289 compliant.
Stream does not contain Program Map Tables (PMT) or Program Association Tables
(PAT)—Priming information required by the VQE-S to perform the RCC is missing.
Details of the PMT and PAT do not match the details of the stream—Priming information required by the VQE-S to perform the RCC is incorrect.
To verify that the VQE-S is correctly locating the burst start point, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Click the Channel node in the navigation tree to expand the channel lineup.
Click the new channel in the lineup.
Click the Advanced button.
Locate the RCC Debug Counters.
Verify that the RCC Refused—No RAP for stream counter did not increment during the RCC.
Remedy: If the RCC Refused—No RAP for stream counter has incremented, verify that the stream source is providing a valid stream for the channel and contact your Cisco technical support representative.
6-22
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
VQE-C RCC Troubleshooting
As a starting point, use the show counters command on the VQE-C command line interface (CLI) to identify how many previous RCC requests have been attempted by the VQE-C and how many have failed. For those RCC requests that have aborted, the output of the show counters command provides
RCC failure reasons and indicates the number of failures associated with each reason. The following is a sample output from the show counters command: vqec# show counters
... Omitted contents ...
--- RCC status ---
-- Channel Change Counters -requests: 8
rcc requests: 6
rcc with loss: 0
rcc aborts: 4
server stun response response burst burst
rejects timeout timeout invalid start activity other
0 0 0 0 0 4 0
...
In this example, the RCC requests field presents the number of channel change requests made by the
VQE-C. The RCC with loss field indicates the number of RCCs that did not abort but for which the post-repair loss rcc counter incremented. The number of RCCs aborted per failure reason is presented under the rcc aborts field. The following failure reason counters are presented:
•
•
•
Server rejects—Number of times an RCC request was rejected by the VQE-S.
Stun timeout—Number of times a STUN response was not received from the VQE-S.
•
Response timeout—Number of times an APP packet (that is, priming information) was not received from the VQE-S.
Response invalid—Number of times an APP packet received contained invalid contents.
•
•
Burst start—Number of times the first repair packet was not received on time.
• Burst activity—Number of times a burst activity timed out prior to completion.
For further information on using the show counters command, see VQE-C CLI Command Reference.
The following sections describe how to troubleshoot RCC problems from the VQE-C:
RCC not enabled on the VQE-C, page 6-24
•
•
•
Problem with priming information sent from the VQE-S, page 6-24
First packets from repair burst not received within expected time period, page 6-25
No multicast stream, page 6-25
Output loss during RCC, page 6-25
•
•
Output packets dropped, page 6-28
Each section presents possible explanations for RCC problems and provides a remedy for the explanation.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-23
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
RCC not enabled on the VQE-C
Explanation: RCC must be enabled on the VQE-C for RCC to operate. Use the show rcc command on the VQE-C CLI to verify that RCC is enabled. The following is a sample output from the show rcc command: vqec# show rcc rcc: enabled
Remedy: If RCC is disabled, use the rcc enable command from the VQE-C CLI in configuration mode to enable RCC. For more information on enabling RCC, see VQE-C System Integration Guide. RCC must also be enabled on the new channel. To verify that RCC is enabled on a channel, either check the channel configuration in the channel lineup from VQE-S AMT or use the show channel command on the VQE-C CLI and verify that the RCC field is set to enabled. For more information on verifying the
status of RCC from the VQE-S AMT, see the “RCC is disabled on the channel” section on page 17
.
Problem with priming information sent from the VQE-S
Explanation: An RCC may be unsuccessful on the VQE-C because of a problem with the APP packets
(that is, priming information) sent by the VQE-S. Possible explanations are as follows:
•
•
APP packet was not received within the rcc_start_timeout interval set at the VQE-C.
APP packet was received by the VQE-C , but was empty.
• APP packet was received by the VQE-S, but was invalid.
To verify from the VQE-C that an RCC has succeeded, use the show tuner <tuner name> rcc command and verify that the RCC result field has a value of success. The following is a sample output from the
show tuner <tuner name> rcc command: vqec# show tuner name tuner1 rcc
Tuner name: tuner1
... Omitted contents ...
--- RCC status ---
rcc enabled: true
rcc result: success
cp failure reason: NONE
dp failure reason: NONE
...
If the rcc result field displays a value of failure, check the values of the cp failure reason field and the dp failure reason field.
Remedy: The cp failure reason field displays the reason why the RCC was aborted by the control plane
(CP). If the field displays a value of APP_Timeout, the APP packet was not received within the RCC
start timeout period set at the VQE-C. See the “VQE-S RCC Troubleshooting” section on page 16 for
possible explanations why APP packets are not sent by the VQE-S within the timeout period.
The dp failure reason displays the reason why the RCC was aborted by the data plane (DP). If the field displays a value of NULL_APP, an empty APP packet was received. In this case, the VQE-S was unable to process the RCC. To identify why an RCC was refused by the VQE-S, view the Refused RCC counters on the Advanced window of the Error Repair and RCC tab of the VQE-S AMT. For more information on identifying reasons why the VQE-S rejects an RCC, see the
“VQE-S RCC Troubleshooting” section on page 16
. If the value of the dp failure reason is INVALID_APP, one or more of its fields in the APP packet was not set correctly by the VQE-S.
6-24
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
First packets from repair burst not received within expected time period
Explanation: The VQE-C aborts an RCC if it does not receive the first repair packet (specified in the
APP packet) from the VQE-S within the period of time specified by the VQE-C System Configuration parameter rcc_start_timeout and presents a FIRST_REPAIR_TIMEOUT error message on the CLI.
In a deployment that includes a NAT device between the STB and the VQE-S, the VQE-C must be configured to use NAT mode, as specified by the VQE-C System Configuration parameter sig_mode.
Remedy: Use Wireshark to determine that the unicast repair burst is being sent from the VQE-S and to determine that the repair burst is reaching the STB hosting the VQE-C. If the repair burst is reaching the VQE-C, the VQE-S is operating as intended, and the problem is occurring within the STB.
Furthermore, if the round-trip time on the network is large or inconsistent, it may help to increase the value of the VQE-C System Configuration parameter rcc_start_timeout, which increases the amount of time the VQE-C waits for a repair burst to start before failing with a FIRST_REPAIR_TIMEOUT error.
For more information on configuring the rcc_start_timeout parameter, see VQE Client System
Configuration Guide.
No multicast stream
Explanation: When an RCC unicast burst is received but no multicast burst is received for the primary stream, the RCC appears to start and then stop. To verify that multicast bursts are received after the initial
RCC unicast burst, use the show tuner name <tuner_name> rcc command on the VQE-C CLI to identify the time the primary packet was received. Verify that the value of the PRIM field under Actual
Relative Times is a non-zero value. In addition, verify that the first primary sequence field under Output statistics contains a non-zero value. For further information on using the show tuner name
<tuner_name> rcc command, see VQE-C CLI Command Reference. The following is a sample output from the command: vqec> show tuner name 0 rcc
Tuner name: 0
... Omitted contents ...
---Actual relative times (ms)---
CC Pli APP Rep Join Prim ER Join-lat
0 7 11 33 149 204 2422 30
... Omitted contents ...
--- Output statistics --first primary sequence: 13767 first repair sequence: 167261298
...
In the sample output, the Prim field under the Actual relative times (ms) section contains a non-zero value. The first primary sequence field under Output statistics also contains a non-zero value.
Remedy: If the multicast burst for the primary stream is not received, verify that IGMP is setup correctly in your network configuration.
Output loss during RCC
Explanation: Video freeze or macroblocking may be observed during an RCC if output loss occurs at the VQE-C. To check for output losses on a tuner, use the show tuner name <tuner_name> rcc command. The following is a sample output from this command: vqec> show tuner name 0 rcc
Tuner name: 0
... Omitted contents ...
--- Output statistics ---
first primary sequence: 3125
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-25
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
rcc output loss packets: 0
rcc output loss holes: 0
rcc duplicate packets: 26
repairs in 1st nack: 0
first packet output time 34
last packet output time 2363
first packet decode time 183
...
Under Output Statistics, the rcc output loss packets field displays the number of missing packets on the output stream and the rcc output loss holes field displays the number of missing packet holes on the output stream. If no output loss has occurred, the value of both fields should be zero. If losses are observed in the network, check you network configuration.
The following are possible explanations why RCC output losses may occur:
•
•
•
•
Packet pool is not size appropriately, page 6-27
Excess bandwidth fraction is larger than the available bandwidth, page 6-27
Previous stream is still flowing, page 6-28
IGMP join latency
Explanation: Video freeze or macroblocking may be observed during an RCC if the IGMP join latency is longer than expected. IGMP join latency is the time between a request to join a multicast group and the receipt of the first byte of data for a multicast group. The actual join latency should be less than the or equal to the value of the VCDB parameter vqe.vqes.igmp_join_variability. This parameter sets the amount of variability between the fastest and slowest IGMP joins for RCC.
To identify the actual IGMP Join Latency, use the show tuner name <tuner_name> rcc command on the VQE-C CLI. For information on using this command, see VQE-C CLI Command Reference. The following is a sample output from the show tuner name <tuner_name> rcc command: vqec> show tuner name 0 rcc
Tuner name: 0
... Omitted contents ...
---Actual relative times (ms)---
CC Pli APP Rep Join Prim ER Join-lat
0 7 11 33 149 204 2422 30
...
In the sample output, the Join-lat field is displayed under Actual relative times (ms).
Remedy: If Join-lat is greater than the value of the VCDB parameter vqe.vqes.igmp_join_variability, determine the maximum igmp join latency that will be experienced on your network, and set the VCDB parameter vqe.vqes.igmp_join_variability to this value in the /etc/opt/vqes/vcdb.conf file. Use the
vqe_cfgtool command with the -apply option to apply the change to the VQE-S.
Note Increasing the value of the VCDB parameter vqe.vqes.igmp_join_variability increases the VQE-C memory requirements and may lead to RCCs being refused.
A historical view of the IGMP join latencies across STBs is provided by the STB IGMP Join Latency histogram on the VQE-S AMT. To view this histogram, do the following:
Step 1 Click the System node in the navigation tree.
6-26
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
Step 2
Step 3
Click the Histograms tab.
The Set-top Box IGMP Latency Histogram is displayed.
Move the slider below the histogram to change the way in which the histogram is displayed.
Packet pool is not size appropriately
Explanation: If the packet pool is not sized appropriately, video freeze or macroblocking may be observed during an RCC, and may continue after an RCC has been cancelled. The packet pool is a fixed size memory buffer pool for storing packet data. To verify that the packet pool buffer is sized appropriately, use the show pak-pool command from the VQE-C CLI. The following is a sample output from the show pak-pool command: vqec# show pak-pool global input pak pool stats:
max entries: 1200
used entries: 76
high water entries: 1047
fail pak alloc drops: 0
The high water entries field records a high number of packets allocated in the packet pool memory. The max entries field displays the maximum number of packets that can be allocated from the packet memory pool. If the high water mark value is close in value to the max entries value, the VQE-C has reached the currently configured limit of the packet pool.
Remedy: The system configuration parameter pakpool_size should be sized appropriately for streams and for associated network characteristics. For more information on sizing the packet pool, see VQE-C
System Integration Guide.
Excess bandwidth fraction is larger than the available bandwidth
Explanation: Video freeze or macroblocking may be observed during an RCC if there is not enough bandwidth available on the access link to perform an RCC. To verify that the excess bandwidth factor has not exceeded the available bandwidth, check the values of the VCDB parameter vqe.vqes.excess_bandwidth_fraction or, in the case of a high definition channel, the VCDB parameter vqe.vqes.excess_bw_fraction_high_def. Verify that the values of these parameters are appropriate for the capacity of the access link.
Note The VQE-S does not take FEC into account when calculating available bandwidth. If your deployment uses FEC, consider the bandwidth used by FEC when determining the excess bandwidth fraction.
In your deployment, if the e-factor is determined on a per-client basis, verify that the e-factor calculated based on the VQE-C parameters max_recieve_bandwidth_sd and max_receive_bandwidth_hd is appropriate for the capacity of the access link.
Remedy: If a global e-factor value is used, modify the value of the VCDB parameter vqe.vqes_excess_bandwidth_fraction or the VCDB parameter vqe.vqes.excess_bw_fraction_high_def.
If the e-factor is determined on the per-client basis, modify the value of the VQE-C parameters max_receive_bandwidth_sd or max_receive_bandwidth_hd to accurately reflect the maximum receive bandwidth.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-27
Chapter 6 Troubleshooting VQE Software Components
RCC Troubleshooting
Previous stream is still flowing
Explanation: Video freeze or macroblocking may be observed during an RCC if the previous stream is still flowing into the VQE-C. If igmp_immediate_leave is not configured in the DSLAM, the combined bandwidth of the multicast stream of the previous channel and the bandwidth allocated for RCC on the new stream (the multicast bitrate of the new stream * [1 + VQE e-factor used for the RCC]) exceeds the bandwidth of the access link. In this scenario, some of the bandwdith is still being consumed by the previous stream, and there is not enough bandwidth remaining on the access link for the unicast burst required to start the RCC for the new channel. The problem disappears as soon as the VQE-C joins the multicast stream for the new channel, usually several hundred milliseconds to several seconds after the start of the unicast burst.
If you want to verify that the previous stream has stopped flowing, connect to the access link using packet capture software such as Wireshark to identify which streams are flowing.
Remedy: If the previous stream is still flowing, configure igmp immediate leave processing in the
DSLAM. Some DSLAMS may not stop the previous stream when an IGMP leave message is received.
Instead, the DSLAM may wait until a new multicast stream has been joined before stopping the previous stream.The VQE-C configuration parameter, rcc_extra_igmp_ip, allows you to specify a multicast IP address that the VQE-C can join briefly on leaving an old channel and joining a new channel as part of an RCC to stop the flow of the multicast stream of the old channel. For more information on configuring the rcc_extra_igmp_ip VCDB parameter, see VQE Client System Configuration Guide.
Output packets dropped
Explanation: Video freeze or macroblocking may be observed during an RCC if the capacity of the output packet queue is exceeded and output packets are dropped. To verify that output packets have not been dropped, use the show tuner name <tuner_name> detail command to view the value of the qdrops field under tuner status.
vqec# show tuner name 0 detail
Tuner name: 0
... Omitted contents ...
--- NAT status ---
... Omitted contents ... qinputs: 92026859 qdrops: 82586551 qdepth: 300 qoutputs: 9440008
...
If the qdrops field has been incremented, the set-top box (STB) decorder is not serving the VQE-C buffer fast enough to display the stream.
Remedy: If output packets are being dropped, increase the value of the output_pakq_limit parameter on the VQE-C. For more information on configuring the output_pakq_limit, see the VQE-C System
Integration Guide.
6-28
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
Using the vqereport Command
Using the vqereport Command
The vqereport command can be useful for VQE troubleshooting. You can use the vqereport command to gather information on the software and hardware configuration of the VQE system. The information can be used by the VQE administrator or Cisco technical support representative to diagnose problems with VQE software or with the Cisco CDE hardware.
Caution The vqereport command can take up to 15 minutes to complete and may cause VQE services (such as
Unicast Retransmission) to be degraded for the duration of the execution.
The syntax for the vqereport command is as follows:
vqereport [-h | -help]
Syntax Description -h | -help Displays help information.
Usage Guidelines The vqereport command generates a report file that, when the command finishes, is located in
/root/hostname.dateandtime.tar.bz2. If appropriate, the report file can be attached to field issue reports for Cisco technical support representatives.
Note You must log in as root to execute the vqereport command.
The vqereport command can be executed on the CDE that hosts the VQE-S or on the CDE that hosts
VCPT. The vqereport executable is located at /opt/vqes/bin/vqereport.
All information gathered is considered confidential, and Cisco uses this information for diagnostic purposes only.
Examples The following example shows the execution of the vqereport command and some abbreviated output:
[root@system ~]# /opt/vqes/bin/vqereport
This utility will go through and collect some detailed information about the hardware and setup of your VQE system. This information will be used to diagnose problems with your system and will be considered confidential information. Cisco will use this information for diagnostic purposes ONLY.
Please wait while we collect information about your system.
This process may take a while to complete....
No changes will be made to your system during this process.
NOTE: You can safely ignore a failed message. This only means a file we were checking for did not exist.
Press ENTER to continue, or CTRL-C to quit.
**********************************************************************
Collect Redhat sysreport
**********************************************************************
Collect information of installed RPM packages
...
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-29
Chapter 6 Troubleshooting VQE Software Components
Gathering Information for a Service Request output omitted
...
Report file /root/<hostname>.20071115164635.tar.bz2 has been generated, please send it to
Cisco support.
Gathering Information for a Service Request
If you are experiencing a problem with Cisco VQE and need to submit a service request to Cisco, please gather and provide the following information to assist Cisco technical support representatives in diagnosing your issue:
•
•
Report file that is generated from the vqereport command for issues involving the VQE-S or VQE
Tools server.
For an issue involving VQE-C, output from the following commands:
–
–
show tuner all detail
show pak-pool
–
–
show counters
show channel
– show system
For information on the vqereport command, see the “Using the vqereport Command” section on page 29 .
For information on submitting a service request, see the monthly What’s New in Cisco Product
Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Stopping, Starting, and Restarting VQE-S
The VQE-S application is a service that is started with the Linux service command.
To stop, start, or restart the VQE-S application, follow these steps:
Step 1
Step 2
Log in as root.
Depending on what is required, issue one of the following commands:
• To stop the VQE-S, issue the following command:
[root@system]# service vqes stop
• To start the VQE-S, issue the following command:
[root@system]# service vqes start
• To restart (stop and then start) the VQE-S, issue the following command:
[root@system]# service vqes restart
6-30
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 6 Troubleshooting VQE Software Components
Stopping, Starting, and Restarting VCDS
Stopping, Starting, and Restarting VCDS
The VCDS application is a service that is started with the Linux service command.
To stop, start, or restart the VCDS application, follow these steps:
Step 1
Step 2
Log in as root.
Depending on what is required, issue one of the following commands:
• To stop VCDS, issue the following command:
[root@system]# service vcds stop
• To start VCDS, issue the following command:
[root@system]# service vcds start
• To restart (stop and then start) VCDS, issue the following command:
[root@system]# service vcds restart
Resetting the Root Password on the VQE-S or VQE Tools Server
To reset the password on the VQE-S or the VQE Tools server, you need to boot into single-user mode from the GRUB loader and reset the password. To reset the password, do the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Connect to the serial console and reboot the VQE-S or the VQE Tools server by issuing the following command:
# reboot
The server reboots.
Press any key when the following message is displayed.
Press any key to continue.
Press any key to continue.
Press any Key to continue.
Red Hat Linux is selected as the operating system and the Grub Loader screen is displayed.
Select the entry "Red Hat Enterprise Linux Server (2.6.18-157.el5)" if not already selected, and press e.
Using the arrow keys, move the cursor to select the following line: kernel /boot/vmlinuz-2.6.15-1-686 root=dev/sda1 ro
Press e to enter edit mode.
Using the arrow keys, move the cursor to the end of the line, press the Spacebar and enter single.
For example: grub edit > kernel /boot/vmlinuz-2.6.15-1-686 root=dev/sda1 ro single
“single” is appended to the end of the line.
Press Enter to exit edit mode and return to the Grub Loader screen.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
6-31
Chapter 6 Troubleshooting VQE Software Components
Resetting the Root Password on the VQE-S or VQE Tools Server
Step 8
Step 9
Press b to boot the Linux kernel into single user mode.
The sh-3.2# prompt is displayed.
Enter passwd and specify the new password. For example: sh-3.2# passwd new-password
Step 10 Issue the following command to reboot the VQE-S or the VQE Tools sever:
# reboot
Step 11
The system reboots.
Login to the server using the new password.
Your root password has been changed.
6-32
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
C H A P T E R
7
Configuring VQE Server and VQE Tools
This chapter describes the following Cisco VQE Configuration Management System software components that reside on the VQE-S and the VQE Tools server: VQE Configuration Tool,
Configuration Engine, and the VCDB Parser. The chapter also provides task-based information on the following topics:
•
Managing /etc Configuration Files Using the VQE CMS, page 7-2
•
•
•
Using the VQE Configuration Tool, page 7-3
VQE Configuration Engine, page 7-11
Manually Editing the VCDB File, page 7-14
•
•
Using the VQE Configuration Tool Command-Line Options, page 7-18
The chapter also provides information on the VQE Configuration Engine and the VCDB Parser.
Note This chapter describes VQE configuration management facilities that are used after the VQE-S or VQE
Tools server has been initially configured (on first power on). For information on initial configuration, see
Chapter 2, “Initial VQE Configuration.”
provides acronyms or terms and descriptions for the major components of the VQE
Configuration Management System that you need to be familiar with.
VQE Configuration Management System Components Table 7-1
Acronym or Term
VCDB
Expansion and Description
VQE Configuration Database stores key-value pairs with the parameters and values you have specified with Configuration Tool or by manually editing the vdcb.conf file (the VCDB file).
CT VQE Configuration Tool provides a menu-driven user interface that you use to display VCDB parameters and their values, add parameters to VCDB, and specify values for VCDB parameters needed for the operation of a VQE Server (VQE-S) or a VQE Tools system. See the
VQE Configuration Tool” section on page 7-3 .
CE VQE Configuration Engine is used to apply the configuration values in VCDB (vcdb.conf) to the running the VQE-S or VQE Tools server. CE also ensures that the configuration values in the
VCDB and the configuration on the CDE server are synchronized. See the
Engine” section on page 7-11 .
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-1 OL-30119-01
Chapter 7 Configuring VQE Server and VQE Tools
Managing /etc Configuration Files Using the VQE CMS
Table 7-1
Acronym or Term
VQE Configuration Management System Components (continued)
Expansion and Description
/etc configuration files Configuration files in the directories under /etc. This is the set of configuration files for the CDE that hosts the VQE-S or the VQE Tools. These files include the existing VCDB file, all history
VCDB backup files, the password file, the SDP file, and so on.
Managing /etc Configuration Files Using the VQE CMS
Starting with Cisco VQE Release 3.0, the configuration files under the /etc directory can be managed by managing /etc configuration files with the VQE CMS (see section
Managing /etc Configuration Files with the VQE CMS, page 7-2
)
On both the VQE-S and VQE Tools hosts, the /etc configuration files are used for VQE software configuration and for CDE system and network configuration. For information on VQE, system, and
network parameters, see Appendix A, “VQE, System and Network Parameters.”
Note Using the VQE CMS is the recommended method for managing VQE, system, and network configuration files.
VQE is intended to be a closed system. As of Cisco VQE Release 3.0, all configuration should be done, whenever possible, using the VQE CMS.
There is no known deployment where manual editing is necessary. Furthermore, there is no support for any deployment where this is done without the permission of Cisco support. However, if you do manually edit /etc configuration files, these files that you manage manually are removed from the control of the VQE CMS.
Managing /etc configuration files by manually editing the /etc configuration files has this disadvantage:
When it becomes necessary to upgrade the VQE software to a later release, changes to the /etc files that you have made by manual file editing (outside the control of the VQE Configuration Management
System) are, in most cases, lost.
Managing /etc Configuration Files with the VQE CMS
Managing /etc configuration files with the VQE CMS consists of using the Configuration Tool or manual editing of the vcdb.conf file to set parameter values, and using the Configuration Engine to apply parameter values to the CDE server. Using the VQE CMS is the recommended method for managing
VQE, system, and network configuration files. The VQE CMS automates much of the work related to configuring a VQE system. If you manage /etc files with the VQE CMS, the CMS automatically does the following:
•
•
Provides the correct syntax for each /etc file parameter
Checks for the allowed set of values for each /etc file parameter
•
•
Restarts the appropriate system processes or reboots the CDE server so that changed parameter values take effect
When a VQE software upgrade is required, automatically preserves your deployment’s configuration in the upgraded software
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-2 OL-30119-01
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool
In addition to this automation, using the VQE CMS to manage /etc configuration files makes it possible to efficiently setup multiple CDE servers. With the exception of some server-specific parameter values, the same VCDB set of parameter values (the vcdb.conf file) may be appropriate for multiple
CDE servers.
Using the VQE Configuration Tool
VQE Configuration Tool (CT) provides a menu-driven user interface that you use to display VCDB parameters and their values, add parameters to VCDB, and specify values for VCDB parameters needed for the operation of a VQE-S or VQE Tools system. Only essential parameters required for a VQE-S or
VQE Tools system are configurable with CT. For those parameters that are not configurable with CT, you can use a text editor to manually modify the vcdb.conf file, which holds the VCDB. For information on editing vcdb.conf, see the
“Manually Editing the VCDB File” section on page 7-14 .
From the Linux command line, you start CT using the vqe_cfgtool command with the -config option.
You must have root privileges to invoke vqe_cfgtool. For information on the vqe_cfgtool command, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18
.
Note This section provides information on using CT when it is started with vqe_cfgtool -config. For information on the vqe_cfgtool, see
Chapter 2, “Initial VQE Configuration.”
Starting the Configuration Tool and Using the Root Menu
When CT is started with vqe_cfgtool -config, it calls the VCDB Parser to parse existing VCDB contents.
• If the Parser finds errors, CT displays the Parser output and quits. The Parser also logs the errors in the /var/log/vqe/vqe.log file.
Note To correct the parsing errors, you must use a text editor to manually edit the vcdb.conf file. You modify the file to correct parameter errors and remove parameters not recognized by the Parser.
• If the Parser finds no errors, CT displays the VQE Configuration Tool Root Menu:
VQE Configuration Tool Root Menu:
1) System Parameters
2) Network Parameters
3) VQE-S Parameters
S) Save and Exit
A) Save/Apply and Exit
E) Exit without saving
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-3
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool
Table 7-2 describes the choices on the CT Root Menu. You enter the number or letter for your choice.
Table 7-2 CT Root Menu Choices
Choice
1) System Parameters
2) Network Parameters
3) VQE-S Parameters
S) Save and Exit
A) Save/Apply and Exit
E) Exit without saving
Description
Configures the system parameters
Configures the network parameters. Contains sub-menus Interface
Parameters and Routing Parameters.
Configures the VQE-S parameters. This choice is present only on the
VQE-S system.
Saves the changes you have made to the VCDB parameters and exits
CT. Any new parameter values are not applied to the configuration files under /etc.
Saves the changes you have made to the VCDB parameters, applies any new parameter values to the configuration files under /etc, restarts services (as needed), and exits CT.
Exits CT. Any changes you have made to the VCDB parameters are
not saved.
Using the Configuration Tool Menus
The System Parameters, SNMP Parameters, Interface Parameters, Routing Parameters and the VQE-S
Parameters menus and prompts are self-documenting and do not require line-by-line explanation. The
System Parameters menu, which is typical of the menu format, is as follows:
VQE Configuration Tool <System Parameters> Menu:
1) Hostname: vqe_server1
2) DNS Server(s): []
3) DNS Search Domain: []
4) Timezone: [America/New_York]
5) NTP Server(s): []
6) Trusted Provisioning Client(s) []
7) Remote Syslog Host(s) []
8) SNMP Parameters []
R) Go to Root Menu
Enter a number choice followed by a letter 'd'(eg. 3d) will reset the
corresponding parameter to its factory default value.
Enter your choice:
To the right of the VQE Configuration Tool menu choice, one of the following is displayed:
• If a value is displayed, it is the current user-defined value for the parameter in VCDB. In the preceding example, vqe_server1 is the current user-defined value in VCDB for the Hostname parameter.
•
•
If a value enclosed by brackets is displayed, this is the default value—the value used when no user-defined value has been specified. In the preceding example, America/New York is a default value.
If empty brackets ([ ]) are displayed, there is no current user-defined value and no default value for the parameter.
7-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool
For the default values used for specific parameters, see the file /etc/opt/vqes/vcdb.conf.sample.
In the System Parameters menu and similar menus, the numbered menu choices allow you to configure the set of relevant parameters. The lettered menu choice “R) Go to Root Menu” returns you to the Root menu.
CT allows you to specify values for the system, network, and VQE parameters that require configuration as well as some of the most common optional parameters.
tells you where to find guidance on the system, network, and the VQE-S parameters that are configurable with CT.
Note When a VCDB parameter is not configurable with Configuration Tool, you can specify the parameter and a value for it by manually editing the /etc/opt/vqes/vcdb.conf file. For information on manually editing the vcdb.conf file, see the
“Manually Editing the VCDB File” section on page 7-14
.
Table 7-3 Where To Find Information on Configuration Tool Parameters
Configuration Tool Parameter Where To Find Information
System Parameters
Hostname
DNS Server(s)
DNS Search Domain
Hostname for the CDE, page 2-24
Domain Name System (DNS) IP Addresses and a Search Domain, page 2-24
Timezone
NTP Server(s)
Trusted Provisioning Client(s)
Remote Syslog Host(s)
NTP Server IP Addresses, page 2-25
Trusted Provisioning Clients, page 2-27
Remote Syslog Hosts, page 2-28
SNMP Parameters
SNMP RO Community String
SNMP System Location
SNMP System Contact
SNMP Trap Listeners
SNMP Read-Only Community String, Location, Contact, and Trap-Listener IP
Addresses or Hostnames, page 2-28
Enable Syslog Traps
Syslog Trap Priority
Enable Channel Up/Down Traps
Interface Parameters
Eth1 Interface IP/Mask
Eth2 Interface IP/Mask
Eth3 Interface IP/Mask
Eth4 Interface IP/Mask
Eth5 Interface IP/Mask
Eth6 Interface IP/Mask
Bond1 IP/Mask and members
Bond2 IP/Mask and members
Bond3 IP/Mask and members
Ethernet Interface Configuration: IP Address and Prefix Length, page 2-25
Note Earlier models of the CDE have four Ethernet ports (eth1 to eth4). These models did not have the Intel PRO/1000 PT Dual Port Server Adapter that provides the eth5 and eth6 ports.
Bond Interfaces on a VQE-S and VQE-Tools Server, page 2-12
Note Earlier models of the CDE have four Ethernet ports (eth1 to eth4) and support up to two bond interfaces (bond1 and bond2).
Management Interface(s)
Interface for a Management Network, page 2-18
Static Routing Parameters
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-5
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool
Table 7-3 Where To Find Information on Configuration Tool Parameters (continued)
Configuration Tool Parameter
Static Route(s)
Where To Find Information
Static Route Configuration: IP Address, Prefix Length, and Gateway Address, page 2-26
and
Configuring Static Routes, page 2-17
OSPF Parameters
OSPF Parameters
OSPF Configuration (VQE-S Host Only), page 2-28
VQE-S Parameters (for VQE-S Host Only)
Log Priority vqe.vqes.log_priority parameter in
Excess Bandwidth Fraction vqe.vqes.excess_bw_fraction parameter in
Traffic (Ingest+Service) Interface(s)
Interfaces for VQE-S Traffic (Ingest and Services) (VQE-S Host Only), page 2-30
Ingest Interface(s)
Service Interface(s)
Interfaces for VQE-S Ingest Traffic (VQE-S Host Only), page 2-29
Interfaces for VQE-S Services Traffic (VQE-S Host Only), page 2-30
Entering Data for Configuration Parameters
In the CT menus, when you enter a number for your choice, a set of prompts asks you for the required parameter information. This section provides information on using the System Parameters menu. Using the other CT menus is similar.
VCDB additions are appended to the end of the vcdb.conf file. That is, VCDB additions are added after the parameters that are already in the file.
The procedures for entering configuration data varies slightly depending on whether the parameter can have only one definition or multiple definitions.
Entering Data for Parameters That Can Have Only One Definition
To enter data for a VCDB configuration parameter that can have only one definition, do the following:
Step 1
Step 2
When the System Parameters menu is displayed, enter the number for the parameter you want to configure. In this example, a single definition is specified for the Hostname parameter.
VQE Configuration Tool <System Parameters> Menu:
1) Hostname: [localhost]
2) DNS Server(s): []
3) DNS Search Domain: []
4) Timezone: [America/New_York]
5) NTP Server(s): []
6) Trusted Provisioning Client(s): []
7) Remote Syslog Host(s): []
8) SNMP Parameters: []
R) Go to Root Menu
Enter a number choice followed by a letter 'd'(eg. 3d) will reset the
corresponding parameter to its factory default value.
Enter your choice: 1
At the Hostname prompt, enter a hostname.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-6 OL-30119-01
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool
Enter the Hostname of this server: vqe_server1
For a parameter that allows only one definition, enter the needed data for the parameter. Hostname allows only one definition. In this case, CT does not prompt for a multiple entries.
The System Parameters menu is displayed with the newly entered parameter value displayed to the right of the menu choice.
VQE Configuration Tool <System Parameters> Menu:
1) Hostname: vqe_server1
2) DNS Server(s): []
3) DNS Search Domain: []
...
Entering Data for Parameters That Can Have Multiple Definitions
To enter data for a VCDB configuration parameter that can have multiple definitions, do the following:
Step 1
Step 2
When the System Parameters menu is displayed, enter the number for the parameter you want to configure. In this example, multiple definitions are specified for the DNS Server(s) parameter.
VQE Configuration Tool <System Parameters> Menu:
1) Hostname: vqe_server1
2) DNS Server(s): []
3) DNS Search Domain: []
4) Timezone: [America/New_York]
5) NTP Server(s): []
6) Trusted Provisioning Client(s) []
7) Remote Syslog Host(s): []
8) SNMP Parameters: []
R) Go to Root Menu
Enter a number choice followed by a letter 'd'(eg. 3d) will reset the
corresponding parameter to its factory default value.
Enter your choice: 2
Configure DNS Server(s). Enter one DNS server on each subsequent line.
Hit Enter at the prompt will complete this configuration.
Enter one or more definitions on separate lines. To complete the configuration, press Enter at the prompt without entering data. For example, DNS Server(s) allows multiple definitions. In this case, CT prompts for multiple entries.
Enter a DNS server IP address: 1.2.3.4
Enter a DNS server IP address: 5.6.7.8
Enter a DNS server IP address:
The System Parameters menu is displayed with the newly entered parameter values displayed to the right of the menu choices.
VQE Configuration Tool <System Parameters> Menu:
1) Hostname: vqe_server1
2) DNS Server(s): 1.2.3.4, 5.6.7.8
3) DNS Search Domain: []
...
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-7
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool
Step 3 Repeat Step 1 and Step 2 to add further definitions for this parameter.
When configuring static routes, each static route is displayed as a sub-menu of the Static Route(s) menu.
For example:
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s):
1.1) 0.0.0.0/0 via 10.86.21.1
1.2) 0.0.0.0/0 via 10.86.21.2
P) Go to Parent Menu
R) Go to Root Menu
Entering New Values for Parameters That Have a Currently Defined Value
For a parameter that has one or more currently defined values in VCDB, with the exception of the Static
Route(s) parameter, the Configuration Tool does not allow you to add additional values or delete a subset of the existing parameter values. When you add a new value for a parameter, all old values for that parameter are deleted.
Note When you specify a value for a parameter that already has a user-defined value specified, the old value for that parameter is deleted and the value you have entered becomes the current value.
If there are multiple existing definitions for a parameter and you specify a value for that parameter, all existing definitions are deleted and the value you have entered becomes the current value.
To enter a new value for a parameter that currently has a value defined in VCDB, do the following:
Step 1
Step 2
Step 3
At the System Parameters menu, enter the number of the parameter. For example:
Enter your choice: 2
The prompt for the parameter is displayed:
Configure DNS Server(s). Enter one DNS server on each subsequent line.
Hit Enter at the prompt will complete this configuration.
Enter a DNS server IP address:
Enter the new parameter value. For example:
Enter a DNS server IP address: 9.9.9.9
Repeat this step if you want to add more parameter values. Each parameter value that you enter is added to VCDB in a cumulative manner.
If you have no further parameter values to add, press Enter.
Enter a DNS server IP address:
When the System Parameters menu is displayed, the new parameter value (9.9.9.9) replaces any existing definitions and values.
As an example, assume that before entering a new value for a parameter, the DNS Server(s) parameter had two definitions, one with the value 1.2.3.4 and one with the value 5.6.7.8:
7-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool
VQE Configuration Tool <System Parameters> Menu:
1) Hostname: vqe_server1
2) DNS Server(s): 1.2.3.4, 5.6.7.8
...
After the new value (9.9.9.9) is entered, the DNS Server(s) parameter has one definition with the value
9.9.9.9:
VQE Configuration Tool <System Parameters> Menu:
1) Hostname: vqe_server1
2) DNS Server(s): 9.9.9.9
...
In the case of the Static Route(s) parameter, when you add a new static route, it is displayed as a sub-menu of the Static Route(s) menu. In the following example, static route 0.0.0.0/0 via 10.86.21.1 exists:
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s):
1.1) 0.0.0.0/0 via 10.86.21.1
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default, enter
its number choice followed by the letter ‘d’ (e.g. 3d).
Default values are displayed inside square brackets [].
A new static route 192.0.0.0/8 via 10.2.9.1 is created:
Enter your choice: 1
Add new static routes by entering destination subnet IP/Prefix and gateway IP pairs when prompted.
To configure a default route, enter 0.0.0.0/0 as the destination subnet IP/Prefix.
To specify a specific gateway interface (optional), add it to the end of the gateway IP, separated by ":" (e.g. "5.6.7.8:eth3).
To complete the configuration, press <Enter> at the prompt without entering data.
Enter the destination subnet in IP/Prefix format (e.g., 1.0.0.0/8): 192.0.0.0/8
Enter the gateway IP address: 10.2.9.1
Enter the destination subnet in IP/Prefix format (e.g., 1.0.0.0/8)
The new static route is added as a sub-menu of the Static Route(s) menu. For example:
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s):
1.1) 0.0.0.0/0 via 10.86.21.1
1.2) 192.0.0.0/8 via 10.2.9.1
P) Go to Parent Menu
R) Go to Root Menu
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-9
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool
Reverting to the Default VCDB Values
To revert to the default VCDB value when an existing user-defined value has been specified, do the following:
When the System Parameters menu is displayed, enter the number of the parameter followed by the letter
“d”. For example:
VQE Configuration Tool <System Parameters> Menu:
1) Hostname: vqe_server1
2) DNS Server(s): 9.9.9.9
3) DNS Search Domain: []
4) Timezone: []
5) NTP Server(s): []
6) Trusted Provisioning Client(s) []
7) Remote Syslog Host(s): []
8) SNMP Parameters: []
R) Go to Root Menu
To reset a parameter to its factory default, enter
its number choice followed by the letter ‘d’ (e.g. 3d).
Default values are displayed inside square brackets [].
Enter your choice: 1d
Any existing values for the parameter that have been set in VCDB are deleted. The default value for the parameter is in effect.
In this example, when the System Parameters menu is displayed, the default value (localhost) is listed to the right of the parameter name (Hostname).
VQE Configuration Tool <System Parameters> Menu:
1) Hostname: [localhost]
2) DNS Server(s): 9.9.9.9
...
If the static route parameter has more than one value defined, and you want to restore the default value of a specific route, enter the number of the sub-menu for that specific route followed by the letter “d”.
For example:
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s):
1.1) 0.0.0.0/0 via 10.86.21.1
1.2) 0.0.0.0/0 via 10.86.21.2
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default, enter
its number choice followed by the letter ‘d’ (e.g. 3d).
Default values are displayed inside square brackets [].
Enter your choice: 1.2d
The existing value for that parameter definition in VCDB is deleted
.
In this example, when the Static
Route(s) menu is displayed, the menu shows that the static route 0.0.0.0/0 via 1.86.21.2 has been deleted.
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s):
1.1) 0.0.0.0/0 via 10.86.21.1
P) Go to Parent Menu
R) Go to Root Menu
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-10 OL-30119-01
Chapter 7 Configuring VQE Server and VQE Tools
VQE Configuration Engine
If you want to restore all static routes to their default value, enter the number for the static route(s) menu followed by the letter “d”. For example:
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s):
1.1) 0.0.0.0/0 via 10.86.21.1
1.2) 0.0.0.0/0 via 10.86.21.2
P) Go to Parent Menu
R) Go to Root Menu
To reset a parameter to its factory default, enter
its number choice followed by the letter ‘d’ (e.g. 3d).
Default values are displayed inside square brackets [].
Enter your choice: 1d
Any existing values for the static route parameter that have been set in VCDB are deleted. The default value for the parameter is in effect. In this example, static routes 0.0.0.0/0 via 10.86.21.1 and 0.0.0.0/0 via 10.86.21.2 have been deleted.
VQE Configuration Tool <Static Routing Parameters> Menu:
1) Static Route(s): []
P) Go to Parent Menu
R) Go to Root Menu
VQE Configuration Engine
Configuration Engine (CE) is used to apply the configuration values in VCDB (vcdb.conf) to the running
VQE-S or VQE Tools server. CE also ensures that the configuration values in vcdb.conf and the configuration on the server are synchronized.
CE is invoked in the following ways:
• Each time the VQE-S or VQE Tools server reboots, CE runs automatically.
•
•
From the Configuration Tool root menu, choose menu choice A—Save/Apply and Exit.
From the Linux command line, use the vqe_cfgtool command with the -apply option to start CE.
For information on the vqe_cfgtool command, see the
“Using the VQE Configuration Tool
Command-Line Options” section on page 7-18 .
1.
When CE is invoked, it does the following:CE (by calling the VCDB Parser) parses the entire vcdb.conf file for parameter validity. A line in vcdb.conf is invalid if it has unknown parameter keywords or syntax errors. If any invalid lines are found, CE logs an error for each invalid line and completes file parsing, but does not proceed to update the /etc configuration files. Instead, CE quits after parsing is complete. CE logs any invalid lines to the /var/log/vqe/vqe.log file on the VQE-S or on the VQE Tools server. CE also displays parsing errors on standard output when run interactively.
If CE quits because of invalid lines in the vcdb.conf file, you must manually edit vcdb.conf to correct the invalid lines. Then issue the command vqe_cfgtool -apply to apply the values in vcdb.conf to the server’s /etc configuration files.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-11
Chapter 7 Configuring VQE Server and VQE Tools
VQE Configuration Engine
Note When CE is automatically invoked during system reboot, no interactive questions are displayed. You are not prompted on whether to continue if CE detects a checksum mismatch for an /etc configuration file, or before changes are made to the running configuration and services restarted if a restart is needed to put a new parameter value into effect.
When CE is invoked using the vqe_cfgtool command and the -apply prompt-off option, no interactive questions are displayed before changes are made to the running configuration.
2.
CE verifies the checksum of each /etc configuration file managed by the CMS. If a checksum is different, this usually means that changes outside of VCDB control (manual changes) have been made to this /etc file since the last CE update. If such a file is found, CE logs the file name and checksum mismatch to /var/log/vqe/vqe.log. CE does not apply VCDB values to /etc files where there is a checksum mismatch.
If CE cannot find or cannot read an /etc file, CE logs the error and does nothing. In this case, you must replace the missing file before normal VQE-S operations can continue. You can use
vqe_cfgtool with -fix_config to replace missing or unreadable /etc configuration files with the factory default configuration files.
Note Copies of the factory default configuration files are in the /vqe-etc/etc-pristine directory.
3.
4.
5.
For synchronization, CE checks that all parameters in VCDB exist in the files under /etc, and that these parameters are effective within the running application. If there is a difference between the configuration values in VCDB and a configuration file under /etc, CE applies the VCDB values to the /etc configuration file where the differences exist.
VCDB is the authority for overall system configuration. If there is a conflict between VCDB and the configuration on the running system, the VCDB value always overrides the value in the /etc file.
CE backs up the VCDB files. The current running VCDB configuration is saved in the file
/etc/opt/vqes/vcdb-running.conf. When CE finds a difference between the VCDB file (vcdb.conf) and the vcdb-running.conf file, it does the following:
• Updates the latest running configuration file with the values in vcdb.conf.
• Saves a copy of vcdb.conf in the archive directory (/etc/opt/vqes/archive/).
The name of the archived file contains the software version, date, and time stamp (for example, vcdb-3.2.0-20080204.1150.conf). Up to 100 VCDB archived backup files can be saved. Backup files over the 100 file limit are deleted based on the time stamp in the filename. Oldest files are deleted first.
After applying the VCDB values, CE (if needed) restarts the associated services or reboot the system. CE restarts only those services that had a VCDB value applied to the corresponding /etc configuration file and that require a service restart or reboot for the changed value to take effect.
Note In interactive mode, CE warns you when service interruptions are required to put a VCDB value into effect for the service, or when a reboot is required to put a VCDB value into effect. You can choose to apply the changes and restart services, or to terminate CE processing.
• If the system.hostname parameter value has changed, CE reboots the server, and all services are restarted.
7-12
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 7 Configuring VQE Server and VQE Tools
VCDB Parser
• If the system.hostname parameter value has not changed, CE restarts individual services in the following order:
1. Syslog-NG
2. SNMP Master Agent
3. Syslog SNMP Subagent
4. network and routing
5. iptables
6. Network Time Protocol
7. VQE-S Process Monitor (VQE-S only)
8. VQE-S SNMP Subagent (VQE-S only)
9. VCDS SNMP Subagent (VQE Tools server only)
VCDB Parser
When the VCDB Parser starts, it reads the /etc/opt/vqes/vcdb.conf.sample file. This file contains information on all the valid VCDB parameters and their syntax. Next the VCDB Parser reads the
/etc/opt/vqes/vcdb.conf file line by line, validates the syntax and parameter keywords, and outputs messages as it proceeds. The VCDB Parser writes its output informing you about any problems to the
/var/log/vqe/vqe.log file and to standard output (if the Parser is used in an interactive mode). The VCDB
Parser does not stop when it finds an error but finishes parsing the whole VCDB file.
There are several categories of VCDB Parser output messages: debug, info, warning, error. The format for the log messages is the same as is used for VQE-S logging. For information on log entry format, see
“VQE Server and VQE Tools Logging and Log Files” section on page 6-2
.
In addition to checking syntax and parameter keywords, the VCDB Parser also performs limited semantic checks. For example, if identical values are specified for a parameter that requires unique values, the VCDB Parser logs a warning and continues.
The VCDB Parser is invoked in the following ways:
•
•
Each time the Configuration Tool runs, the VCDB Parser is automatically invoked.
Each time the Configuration Engine runs, the VCDB Parser is automatically invoked.
• From the Linux command line, use the vqe_cfgtool command with the -parse option to start the
VCDB Parser.
For information on the vqe_cfgtool command, see the
“Using the VQE Configuration Tool
Command-Line Options” section on page 7-18 .
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-13
Chapter 7 Configuring VQE Server and VQE Tools
Manually Editing the VCDB File
Manually Editing the VCDB File
The VQE Configuration Tool allows you to specify values for the required system, network, and VQE parameters. It also allows you to configure some of the most common optional parameters. When a
VCDB parameter is not configurable with Configuration Tool, you can specify the parameter and a value for it by manually editing the /etc/opt/vqes/vcdb.conf file.
This section provides information on how you specify parameters in the vcdb.conf file and how you use the reference information in the vcdb.conf.sample file to edit vcdb.conf:
•
•
Using VCDB File Syntax, page 7-14
Understanding the vcdb.conf.sample File, page 7-15
For information on the VCDB parameters, see
Appendix A, “VQE, System and Network Parameters.”
Note When you manually edit the vcdb.conf file to modify, add, or remove parameters, you must apply the parameter values in vcdb.conf to the server /etc configuration files for the changed parameters to take effect. To apply the values, use the vqe_cfgtool command with the -apply option. For information on
vqe_cfgtool, see the “Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
Tip After you manually edit and save the vcdb.conf file, use the vqe_cfgtool command with the -parse option to check that your changes have not created any errors in the file.
Using VCDB File Syntax
This section provides information on the syntax rules you need to follow when editing the vcdb.conf file.
The vcdb.conf file contains a list of key-value pairs. Each key-value pair is associated with a system, network, or VQE parameter that is used to configure a VQE-S or VQE Tools system. Each key-value pair has the following syntax:
section.subsection.parameter = "value"
Each key is associated with a section and subsection. Section names are vqe, system, and network. Some key-value pair examples are as follows: vqe.vqes.exporter_enable = "TRUE" system.global.hostname = "iptv_host" network.eth1.addr = "10.2.9.2/24"
The syntax rules for the vcdb.conf file are as follows:
• Allowed VCDB keys and their syntax are defined in the vcdb.conf.sample file.
•
•
•
•
•
Each key is case-sensitive.
Key and its value are separated by an equal sign (=).
Value is enclosed by quotation marks ("value").
Comment line starts with #. The VCDB Parser ignores these lines.
Following are allowed but ignored:
7-14
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 7 Configuring VQE Server and VQE Tools
Manually Editing the VCDB File
– Leading space before a key
–
–
Leading space before and trailing space after a value
Spaces before or after the equal sign (=)
Multiple Definitions
If a parameter definition appears more than once in vcdb.conf when multiple definitions of the parameter are not allowed, the VCDB Parser logs an error and terminates. None of the values in vcdb.conf are applied to the /etc configuration files.
When this multiple definition error occurs, you must edit vcdb.conf manually to correct the items that are in error.
Parameter Order
For those parameters that can only appear once in VCDB, parameter order is not important.
If a parameter can have multiple values, it requires multiple lines of definition. Each line defines one value. The order of these definitions in the vcdb.conf file is important because the same order is kept in the /etc configuration files. Consider the following vcdb.conf file items: system.snmp.trap_listener = "1.2.3.4" system.snmp.trap_listener = "5.6.7.8"
When the Configuration Engine applies these two system.snmp.trap_listener items to the
/etc/snmp/snmpd.conf file, listener 1.2.3.4 is defined in the snmpd.conf file before listener 5.6.7.8 because 1.2.3.4 is specified first in the vcdb.conf file.
Understanding the vcdb.conf.sample File
For each Cisco VQE release, the vcdb.conf.sample file provides user reference information on the parameters recognized by the VCDB Parser. For each VCDB parameter, vcdb.conf.sample contains the key-value pair, syntax rules, range of allowed values, and other information. The vcdb.conf.sample file is located in /etc/opt/vqes/vcdb.conf.sample. It is a read-only file and should not be moved.
To determine how to specify a VCDB parameter in vcdb.conf, you read about the parameter and its usage in vcdb.conf.sample. Some parameter examples from vcdf.conf.sample are as follows:
# system.global.hostname="localhost"
# Description: "Fully Qualified Domain Name (FQDN) or hostname of the system."
# Type: String, minimum length 3 characters, maximum length 200 characters
# Default value: localhost
# Required: N
# Service interruption: "System reboot. "
# Allow multiple definitions: N
# Target /etc file: ""127.0.0.1" in /etc/hosts and "HOSTNAME" in /etc/sysconfig/network"
# network.eth1.addr=""
# Description: "IP address and network mask length for interface eth1 in the for m ""1.2.3.4/24"""
# Type: IP_Prefix
# Default value:
# Required: N
# Service interruption: "Potential network traffic interruption. "
# Allow multiple definitions: N
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-15
Chapter 7 Configuring VQE Server and VQE Tools
Manually Editing the VCDB File
# Target /etc file: ""IPADDR" and "NETMASK" in /etc/sysconfig/network-scripts/if cfg-eth1"
# vqe.vqes.log_priority="4"
# Description: "Global logging priority level for all VQE applications. Valid va lues are 0-6. 0 - EMERGENCY, system is unusable, 1 - ALERT, action must be taken
immediately, 2 - CRITICAL, critical conditions, 3 - ERROR, error conditions, 4
- WARNING, warning conditions, 5 - NOTICE, normal but significant condition, 6 -
INFO, informational. Levels less than or equal to log-level will be logged.",
# Type: Integer, minimum value is 0, maximum value is 6
# Default value: 4
# Required: N
# Service interruption: "VQE Process Monitor restart."
# Allow multiple definitions: N
# Target /etc file: ""log-level" in /etc/opt/vqes/.vqes.conf"
In vcdb.conf.sample, the first line of an entry is the key-value pair for the parameter.
vcdb.conf.sample reference information that describes each VCDB parameter.
Table 7-4
Field
Description
Type
Default value
Parameter Information in the vcdb.conf.sample File
Description
Explains how the parameter is used.
Specifies one of the following data types and, if applicable, the range of values allowed.
•
•
•
•
Integer—Whole number.
Float—Floating-point number (for example, 10.25 or –5.75 or .50). The allowed floating-point numbers correspond to those allowed by the Perl float type.
String —One or more characters. The set of characters allowed varies depending on the parameter.
Boolean—Either true or false.
•
•
•
IP—IPv4 address in dotted-decimal form (for example, 10.0.0.1). The IP address must be in the range allowed for an IPv4 address.
IP_PREFIX—IP address and prefix length in the form ip-address/prefix-length (for example,
10.0.0.0/8). The ip_address is the same as in IP. The prefix-length must be in the range 0 to 32.
Route—Route in the format ip-address/prefix-length via ip-address (for example,
10.0.0.0/8 via 10.2.9.1). Each ip_address is the same as in IP. The prefix-length must be in the range 0 to 32.
• Host—Either an IP address or a string representing a fully qualified domain name (for example, myhost.company.com). The IP address is the same as in IP.
Specifies a default value. If there is no default value, this field is blank.
• Y—Parameter must be defined, and there is no default value.
• N—Parameter does not have to be defined.
You can define a parameter by using the Configuration Tool or by manually editing the vcdb.conf file with a text editor.
Service interruption Indicates whether VQE services are interrupted when the parameter definition is applied to the relevant configuration file (for example, when you invoke the vqe_cfgtool command with the -apply option).
7-16
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 7 Configuring VQE Server and VQE Tools
Manually Editing the VCDB File
Table 7-4 Parameter Information in the vcdb.conf.sample File (continued)
Field Description
Allow multiple definition
Specifies one of the following:
•
•
Y—Parameter can be specified more than once in the vcdb.conf file.
N—Parameter can be specified only once in the vcdb.conf file.
Target /etc file Specifies the configuration file under /etc that is written to when the parameter is applied. Also indicates the configuration items that are written to the /etc configuration file.
In the system.global.hostname parameter example preceding this table, “Target /etc file” indicates that a line 127.0.0.1 host_name is written to the file /etc/hosts, and a line HOSTNAME=host_name is written to the /etc/sysconfig/network file.
The host_name is the value specified for system.global.hostname. The exact syntax for the line that is added to the /etc file is not specified in the “Target /etc file” field.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-17
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool Command-Line Options
Using the VQE Configuration Tool Command-Line Options
The vqe_cfgtool command performs a variety of configuration tasks related to the VQE Configuration
Database (VCDB) and the configuration files under the /etc directory on a VQE-S or VQE Tools server.
The syntax for the vqe_cfgtool command is as follows:
vqe_cfgtool [-apply [prompt-off] | -backup | -config | -fix_config | -help |
-parse [full_pathname] | -restore full_pathname | -sanity_check | -version]
Syntax Description -apply [prompt-off]
-backup
-config
-fix_config
-help
-parse [full_pathname]
-restore full_pathname
-sanity_check
-version
Launches the Configuration Engine to apply the values in VCDB to the server /etc configuration files.
If you specify prompt-off, no interactive questions are displayed before changes are made to the running configuration.
Copies all files under /etc into a tar file and saves the tar file in
/vqe-etc/vqe-release-hostname-timestamp.tar.gz.
Launches the Configuration Tool so that you can modify the VQE configuration parameter values that are stored in VCDB.
Discards the current copy of each /etc configuration file where there is a checksum mismatch and replaces it with the original copy of the file that comes with the RPM package.
Displays information on how to use the vqe_cfgtool command and its options. If no valid option is specified when vqe_cfgtool is invoked,
-help is the default.
Performs validation of the VCDB contents (parameters, values, syntax, and so on) for the current vcdb.conf file.
If full_pathname is specified, that file is parsed rather than the current vcdb.conf file.
Extracts the contents of the tar file specified in full_pathname, and replaces all /etc configuration files with the tar file contents. The tar file is typically created with vqe_cfgtool -backup.
Compares the parameter values in VCDB with the values in the /etc configuration files, and displays any differences on the command line.
Displays software version information.
Usage Guidelines The vqe_cfgtool command is available on the VQE-S or VQE Tools server. The tool is located in the
/opt/vqes/bin directory. You must have root privileges to invoke vqe_cfgtool. The vqe_cfgtool command does not respond to Ctrl-C and cannot be exited prematurely once execution has started.
The vqe_cfgtool command writes its output to standard output (by default, it is displayed on the command line) and to the /var/log/vqe/vqe.log file.
-apply Option
When -apply is specified, vqe_cfgtool invokes the Configuration Engine to apply the VCDB values to the server /etc configuration files. After applying the VCDB values, CE (if needed) restarts the associated services or reboot the system. CE restarts only those services that had a VCDB value applied
7-18
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool Command-Line Options to the corresponding /etc configuration file and that require a service restart or reboot for the changed value to take effect. For a detailed description of Configuration Engine processing, see the
Configuration Engine” section on page 7-11 .
If prompt-off is specified with the -apply option, you are not prompted on whether to continue for these two situations:
• If the Configuration Engine detects a checksum mismatch for an /etc configuration file. If a checksum is different, this usually means that unauthorized changes (that is, changes outside of
VCDB control) have been made to this file after the last CE update.
• Before changes are made to the running configuration and services restarted (if a restart is needed to put any new parameter values into effect).
-backup and -restore Options
When -backup is specified, vqe_cfgtool saves all files under /etc into a tar file and saves the tar file in
/vqe-etc/vqe-release-hostname-timestamp.tar.gz. After vqe_cfgtool saves the tar file, it displays the location of the tar file and reminds you to use the scp command to copy the file to a remote server. The
-backup option is typically used before -config or -apply so that a backup copies of the /etc configuration files are available for rollback purposes.
When -restore full_pathname is specified, vqe_cfgtool extracts the contents of the tar file specified in
full_pathname, and replaces all /etc configuration files with the tar file contents. The full_pathname argument usually gives the path to a tar file that has been created with -backup.
-config Option
When -config is specified, vqe_cfgtool parses the vcdb.conf file and, if there are no errors, runs the
Configuration Tool so you can modify parameter values in VCDB. For information on how
Configuration Tool works, see the
“Using the VQE Configuration Tool” section on page 7-3 .
-fix_config Option
When -fix_config is specified, vqe_cfgtool discards each /etc configuration file where there is a checksum mismatch and replaces it with the factory default /etc configuration file from the RPM package. vqe_cfgtool then recomputes the checksum using the factory default file.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
7-19
Chapter 7 Configuring VQE Server and VQE Tools
Using the VQE Configuration Tool Command-Line Options
A missing or unreadable /etc configuration file is considered a checksum mismatch and –fix_config copies the default factory file into the appropriate directory below /etc. -parse Option
When -parse is specified, vqe_cfgtool parses the vcdb.conf file or, if the optional full_pathname is given, it parses the indicated file. This option is typically used to check the validity of offline VCDB configuration files. For information on the VCDB Parser, see the
“VCDB Parser” section on page 7-13
.
-sanity_check Option
When -sanity_check is specified, vqe_cfgtool checks the following:
• Whether the files under /etc have been manually edited (changes made not using VCDB)
•
•
Whether the RPM software on the server is intact and no piece is missing
Whether the vqe user account exists on the server
If vqe_cfgtool finds a problem with any of the preceding checks, it displays information about the issue on standard output.
Tip You can use the cron command to execute vqe_cfgtool -sanity_check periodically to check VQE-S or
VQE Tools system sanity.
7-20
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
A P P E N D I X
A
VQE, System and Network Parameters
OL-30119-01
This appendix provides descriptions of the VQE Configuration Database (VCDB) parameters.
The essential VCDB parameters—the subset typically required for a VQE-S or a VQE Tools system—can be configured by using the VQE Configuration Tool (CT) or by manually editing the vcdb.conf file. For information on using the VQE Configuration Tool, see
All VCDB parameters can be configured by manually editing the vcdb.conf file. For information on
manually editing the vcdb.conf file, see the “Manually Editing the VCDB File” section on page 7-14
The VQE-S, system, and network parameters are described in the following tables:
•
•
•
Table A-1 —VQE-S global parameters
Table A-2 —VQE-S Unicast Retransmission parameters
•
Table A-3 —VQE-S Rapid Channel Change (RCC) parameters
Table A-4 —VQE-S Unicast Retransmission and RCC parameters (parameters that affect the
behavior of both Unicast Retransmission and RCC)
•
•
•
Table A-5 —VQE-S RTCP Exporter parameters
Table A-7 —Interface parameters
Table A-8 —Static Routing parameters
•
•
For all parameters intended to be user-configurable, the preceding tables provide the parameter name, default value (if any), description, and allowed range of values. The parameter default value (if any) is in quotation marks following the parameter name. For example: vqe.vqes.log_priority="4"
For vqe.vqes.log_priority, 4 is the default value. Empty quotation marks indicate that there is no default value.
For more information on the VQE, system, and network parameters, see the /etc/vqes/vcdb.conf.sample file. The vcdb.conf.sample file provides the preceding information and the parameter type, service interruption information, whether multiple definitions are allowed, and the target /etc files where the parameter value is applied.
Note In the following tables, if a parameter is configurable with Configuration Tool, the Description lists the
CT menu and menu choice for the parameter in the brackets as follows: [CT: menu > menu_choice(s)].
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
A-1
Appendix A VQE, System and Network Parameters
Table A-1 VQE-S Global Parameters
Parameter and Default Value (if any) vqe.vqes.log_priority="4" vqe.vqes.max_pkts="5000000"
Description
Logging level for all VQE-S processes. The range is from 0 to 6. Logging levels are as follows:
• 0—Emergency (System is unusable)
•
•
•
1—Alert (Action must be taken immediately)
2—Critical (critical condition)
3—Error (error condition)
4—Warning (warning condition) •
•
•
5—Notice (normal but significant condition)
6—Info (informational condition)
Logging levels go from least verbose to most verbose. The Emergency level generates the smallest number of messages, and the Info level generates the most messages. By default, VQE-S logging messages are written to the file
/var/log/vqe/vqe.log.
When you select a logging level, log messages are generated for that level and the levels below that level. For example, when the level is set to Error, messages are generated for Emergency, Alert, Critical, and Error.
For information on configuring VQE-S debugging messages, see the
“Change VQE-S Debugging” section on page 4-33 .
[CT: VQE-S Parameters > Log Priority]
Maximum number of packet buffers in the VQE-S Cache Manager. Allowed range is 100,000 to 5,000,000.
A-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix A VQE, System and Network Parameters
Table A-1 VQE-S Global Parameters (continued)
Parameter and Default Value (if any) vqe.vqes.vqe_interfaces="eth1,eth2,eth3,eth4, eth5,eth6"
Description
Names of the interfaces to be used for ingest of multicast streams, Unicast
Retransmission and RCC traffic, and other non-management VQE-S traffic.
Multiple interface names should be separated by a comma without any space between names. If this parameter is used, the following rules apply:
•
•
•
•
Note
If this parameter is specified, the vqe.vqes.vqe_ingest_interfaces and vqe.vqes.vqe_service_interfaces parameters must not be specified.
If a dedicated interface is used for management traffic, it should not be specified in this parameter.
Multiple Ethernet interfaces or multiple bond interfaces may be specified in this parameter.
Ethernet interface that is a member of a bond interface must not be specified in this parameter.
For load balancing to work effectively, each interface to the access or distribution network must have the same capacity. Multiple bond interfaces should not be specified and a combination of Ethernet and bond interfaces cannot be specified in this parameter.
vqe.vqes.vqe_ingest_interfaces=""
Allowed values are eth1 to eth6 or bond1 to bond3. Interfaces eth5, eth6, and bond3 are available only on CDE servers that include the Intel
PRO/1000 PT Dual Port Server Adapter.
[CT: VQE-S Parameters > Traffic (Ingest+Service) Interface(s)]
Names of the interfaces to be used for ingest of multicast streams. Multiple interface names, separated by a comma without any space between names, should be specified in this parameter. If this parameter is used, the following rules apply:
•
•
•
•
At least one VQE-S services interface must be specified in the vqe.vqes.vqe_service_interfaces parameter.
Parameter vqe.vqes.vqe_interfaces must not be specified.
If a dedicated interface is used for management traffic, it must not be specified in this parameter.
Multiple Ethernet interfaces or multiple bond interfaces may be specified in this parameter.
•
Note
Ethernet interface that is a member of a bond interface must not be specified in this parameter.
For load balancing to work effectively, each interface to the distribution network must have the same capacity. Multiple bond interfaces should not be specified and a combination of Ethernet and bond interfaces cannot not be specified in this parameter.
Allowed values are eth1 to eth6 or bond1 to bond3. Interfaces eth5, eth6 and bond3 are available only on CDE servers that include the Intel PRO/1000
PT Dual Port Server Adapter.
[CT: VQE-S Parameters > Ingest Interface(s)]
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
A-3
Appendix A VQE, System and Network Parameters
Table A-1 VQE-S Global Parameters (continued)
Parameter and Default Value (if any) vqe.vqes.vqe_service_interfaces=""
Description
Names of the interfaces to be used for delivering VQE-S services—Unicast
Retransmission, RCC traffic, and other non-management VQE-S traffic.
Multiple interface names should be separated by a comma without any space between names. If this parameter is used, the following rules apply:
•
•
•
•
At least one ingest interface for incoming multicast streams must be specified in the vqe.vqes.vqe_ingest_interfaces parameter.
Parameter vqe.vqes.vqe_interfaces must not be specified.
If a dedicated interface is used for management traffic, it must not be specified in this parameter.
Multiple Ethernet interfaces or multiple bond interfaces may be specified in this parameter.
•
Note
Ethernet interface that is a member of a bond interface must not be specified in this parameter.
For load balancing to work effectively, each interface to the access network must have the same capacity. Multiple bond interfaces should not be specified and a combination of Ethernet and bond interfaces cannot not be specified in this parameter.
vqe.vqes.rtcp_dscp="24" vqe.vqes.rtp_inactivity_timeout="300" vqe.vqes.stun_enable="true" vqe.vqes.stun_dscp="–1"
Allowed values are eth1 to eth6 or bond1 to bond3. Interfaces eth5, eth6, and bond3 are available only on CDE servers that include the Intel
PRO/1000 PT Dual Port Server Adapter.
[CT: VQE-S Parameters > Service Interface(s)]
DSCP
1
value for transmitted RTCP packets. The default value (24) is for the
CS3 selector, which is used for broadcast video. The range is from 0 to 63.
Amount of time or the inactivity timeout on received RTP
2
streams, in ms.
If no packets are received on an input channel for this amount of time, the channel is declared inactive until the next input packet is received for that stream. The range is from 10 to 900.
Specifies whether the STUN
3
Server is enabled. The value true enables the
STUN Server, and false disables the STUN Server.
Unless you are sure that no STBs
4
being serviced by the VQE-S are behind
NAT devices, we recommend that the STUN Server be enabled.
DSCP value for STUN Server binding responses.
•
•
If the value –1 is specified, the DSCP value for the STUN binding response is set to the DSCP value in the STUN binding request.
If a value other than –1 is specified, the DSCP value for the STUN binding response is set to the value given. vqe.iptables.trusted_vcpt=""
The range is from –1 to 63.
Starting with Cisco VQE Release 3.2, this parameter is deprecated. Use the system.iptables.trusted_provisioner parameter.
1.
DSCP = Differentiated Services Code Point.
2.
RTP = Real-time Transport Protocol.
3.
STUN = Simple Traversal of User Datagram Protocol (UDP) through Network Address Translators (NATs)
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
A-4 OL-30119-01
Appendix A VQE, System and Network Parameters
4.
STB = set-top box.
Table A-2 VQE-S Unicast Retransmission (Error Repair) Parameters
Parameter and Default Value (if any) vqe.vqes.client_er_policing="true"
Description
Specifies whether per-VQE-C
1
policing is enabled for Unicast Retransmission
(error repair) packets. The value true enables per-VQE-C policing, and false disables per-VQE-C policing.
The VQE-C policing mechanism is intended to limit the fraction of the VQE-S error-repair resources that can be consumed by a single VQE-C on the STB.
When per-VQE-C policing is enabled, the policer is tuned by two parameters: vqe.vqes.client_er_tb_rate_ratio and vqe.vqes.client_er_tb_depth. vqe.vqes.client_er_tb_rate_ratio="5" Per-client policing token rate (percentage of stream rate) for each VQE-C for
Unicast Retransmission. The range is from 1 to 100.
Per-client policing uses token bucket policers. A token is the equivalent of a packet. The token rate for the policers is defined as a percent of a stream's packet rate. For example, assume an RTP stream with a packet rate of 350 packets per second, the default rate of five percent is set the per-client policer token rate to 18 packets per second.
Increasing this parameter increases the maximum load that a single STB can put on the VQE-S. By default, each VQE-C is permitted to request up to five percent of the overall stream bandwidth for whatever channel it is watching.
In a situation with only a few VQE-Cs, some or all of which have very high error rates, it may be desirable to increase this parameter to allow each client to get more errors repaired. In a situation with a large number of VQE-Cs, it may be necessary to decrease this parameter to prevent a small proportion of misbehaving or very error-prone client connections from consuming a disproportionate fraction of the
VQE-S error-repair resources.
The VQE-S AMT channel statistics for each channel provide data that you can use to tune the VQE-C policing mechanism. In the Channel Statistics window, click
Advanced. The Advanced Channel Debug Stats include the following parameters that indicate how many error-repair requests were refused because the VQE-S is overloaded and how many were refused because of per-client policing.
• Dropped repair pkts by Packet Policer—If the server is overloaded with error repairs, this statistic may be an indication that the per-client policing should be lowered.
• Aggregated dropped pkts by client policers—If many repairs are being refused because of per-client policing, but the server is not overloaded, this statistic may be an indication that the per-client policing can be raised. vqe.vqes.reserved_er_bw="543200000" Total amount of bandwidth (in bits per second) dedicated to Unicast
Retransmission. The bandwidth pools on a VQE-S include available non-management, output interface bandwidth. The range is from 0 to 543200000.
The VQE-S separates the output interface bandwidth that is dedicated to Unicast
Retransmission. The amount of bandwidth specified in this parameter is dedicated to Unicast Retransmission with the remainder used for RCC. This parameter allows the amount of output interface bandwidth dedicated to Unicast
Retransmission to be reduced so that the bandwidth is available for RCC instead.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 A-5
Appendix A VQE, System and Network Parameters
Table A-2 VQE-S Unicast Retransmission (Error Repair) Parameters (continued)
Parameter and Default Value (if any) Description vqe.vqes.client_er_tb_depth="10000" Length of time (in milliseconds) needed to fill the per-VQE-C policer bucket for
Unicast Retransmission (error repair). The range is from 1 to 60,000.
The bucket depth of the per-client packet policers is expressed as a duration over which the token limit would be reached if the bucket was initially empty and filled at the token rate with no tokens drained. Therefore, the maximum number of tokens (depth) of the policer bucket is calculated as follows: maximum number of tokens =
(client_er_tb_rate_ratio * stream packet rate * client_er_tb_depth) vqe.vqes.er_cache_time="3000" vqe.vqes.rtp_retrans_dscp="0" vqe.vqes.rtp_er_dscp="0"
The bucket size should be set large enough to cover the maximum burst loss that may ordinarily occur on a client STB. In most cases, the default value for vqe.vqes.client_er_tb_depth should be adequate.
Maximum time interval (in milliseconds) to cache the original source stream packets for Unicast Retransmission (error repair). The range is from 100 to 10,000.
Note Starting with Cisco VQE Release 3.7, the maximum value of this parameter has increased from 5000 to 10,000 to support 10 secs channel caching requirements
Starting with Cisco VQE Release 3.3, this parameter is deprecated. Use the vqe.vqes.rtp_er_dscp and vqe.vqes.rtp_rcc_dscp parameters.
DSCP value for RTP packets for Unicast Retransmission. The vqe.vqes.rtp_rcc_dscp parameter can be used for DSCP marking of RTP packets for RCC. The range is from 0 to 63.
1.
VQE-C = VQE client.
Table A-3 VQE-S RCC Parameters
Parameter and Default Value (if any) vqe.vqes.fastfill_enable="false" vqe.vqes.buff_size_preroll_max="1500" vqe.vqes.igmp_join_variability="100"
Description
Specifies whether FDBF 1 is enabled for RCC to reduce decoder buffering time. The value true enables FDBF, and false disables FDBF.
If FDBF is enabled for RCC, specifies the maximum assumed delay (in milliseconds) for the PTS-PCR offset (Presentation Time Stamp-Program
Clock Reference offset) for all streams going through the VQE-S. The parameter value is used only when sizing the VQE-S channel buffers. If
FDBF is not enabled, this parameter is ignored. The range is from 0 to
10,000.
Amount of variability (in milliseconds) between the fastest and slowest
IGMP joins for RCC. The range is from 0 to 1000.
Note This parameter can have a large impact on the amount of bandwidth consumed by RCC. It needs to be carefully tuned for a deployment.
A-6
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix A VQE, System and Network Parameters
Table A-3 VQE-S RCC Parameters (continued)
Parameter and Default Value (if any) vqe.vqes.max_idr_penalty="0" vqe.vqes.rap_max_interval="2000" vqe.vqes.rcc_burst_delay_to_send="10" vqe.vqes.rcc_mode="conservative"
Description
For MPEG-4 only, the maximum penalty (in milliseconds) that is permitted to begin an RCC burst with an instantaneous decoding refresh
(IDR) frame rather than I-frame. The range is 0 to 10000.
In cases in which there are several MPEG RAPs
2
from which an RCC could be performed, the RCC is normally started from the most recent feasible RAP. If vqe.vqes.max_idr_penalty is specified as greater than zero, then the RCC is started with an IDR frame instead of an I-frame, provided that the IDR is within vqe.vqes.max-idr-penalty milliseconds of the most recent feasible I-frame.
Maximum time interval (in milliseconds) between MPEG RAPs that the
VQE-S supports for RCC operations. The range is 500 to 5000.
Amount of time (in milliseconds) to delay before the Data Plane schedules an RCC repair burst. This parameter may be set to a larger value to compensate for lags in the IGMP fast leave mechanism in the access node
(for example, a DSLAM). The range is 0 to 100.
RCC mode. Can be specified as either of these values:
•
• aggressive—Conserves bandwidth if all DSLAMs that may receive an
RCC burst from the VQE-S are configured to give priority to the primary multicast video traffic over the unicast RCC burst traffic. conservative—Used when the DSLAM does not have the required
QoS capability for aggressive mode.
Use of aggressive mode in a situation where one or more access nodes
(DSLAMs) in the network have not been configured to give preference to the primary multicast traffic over the unicast stream causes degraded video quality during RCC operations for customers attached to DSLAMs that are not properly configured for aggressive mode RCC.
Caution Use of aggressive mode may cause brief, transient congestion of the access links during the RCC operation and therefore should not be used in situations in which such congestion may have undesirable side effects, such as loss of data or voice traffic on the access link.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
A-7
Appendix A VQE, System and Network Parameters
Table A-3 VQE-S RCC Parameters (continued)
Parameter and Default Value (if any) vqe.vqes.rtp_hold_time="20" vqe.vqes.rtp_rcc_dscp="–1"
Description
Amount of time (in milliseconds) to delay before making a packet in the
Data Plane cache available for RCC to allow for reordering of received packets. The range is from 0 to 500.
This parameter is needed to allow for reordering of received packets in case they were received out of order from the source (headend). The parameter should be set as small as possible but large enough to cover the maximum arrival time jitter of received packets. Setting the parameter too small may cause some RCC operations to fail or be degraded if packets are received out of order. Setting the parameter too large causes RCC operations to use more network bandwidth, on average, than is necessary.
DSCP value for transmitted RTP packets sent for RCC. If the value –1 is specified, the DSCP value is set to the value of vqe.vqes.rtp_er_dscp.
Note Use of the value –1 provides backward compatibility with earlier
Cisco VQE releases that had only the vqe.vqes.rtp_er_dscp parameter, which was used for DCSP marking of RTP packets for both Unicast Retransmission and RCC.
The range is from –1 to 63.
1.
FDBF = fast decoder buffer fill.
2.
RAP = random access points.
A-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix A VQE, System and Network Parameters
Note
Table A-4 lists parameters that affect the behavior of both Unicast Retransmission and RCC.
Table A-4 VQE-S Unicast Retransmission and RCC Parameters
Parameter and Default Value (if any) Description vqe.vqes.max_client_bw="0" vqe.vqes.excess_bw_fraction="20" non-ingest traffic. This parameter specifies the amount of input bandwidth that is not to be allocated to receiving multicast streams. The range is from 0 to 100.
•
•
If the interface is used for both VQE-S ingest and services, the reservation should include sufficient bandwidth for receiving Unicast Retransmission and RCC requests, RTCP reports from the STBs, and control traffic, such as IGMP and RTCP. Recommended value range is from 20 to 40.
If the interface is used for VQE-S ingest only, the reservation should include sufficient bandwidth for incoming control traffic, such as IGMP and RTCP. Recommended value is 5.
Maximum access link bandwidth (in bits per second) available for each VQE-C for Unicast Retransmission and RCC. The range is from 0 to 58500000.
If a non-zero value is specified, the vqe.vqes.excess_bw_fraction and the vqe.vqes.excess_bw_fraction_high_def are ignored. Instead, each time the STB tunes to a new channel, the implicit excess_bw_fraction for the client on the channel is calculated using vqe.vqes.max_client_bw.
Note If the VQE-C does not use the parameters max_receive_bandwidth_sd or max_receive_bandwdith_hd to send the MRB
1
to the VQE-S, the vqe.vqes.max_client_bw parameter is used to calculate the excess bandwidth fraction. If the vqe.vqes.max_client_bw is zero or not configured, either the vqe.vqes.excess_bw_fraction or the vqe.vqes.excess_bw_fraction_high_def is used depending on the channel bitrate and the value of the vqe.vqes.high_def_min_bw parameter.
Specifies the rate e (e = excess_bw_fraction / 100) that determines the rate at which packets are sent during Unicast Retransmission and RCC. The range is from 3 to 500.
• For Unicast Retransmission, the VQE-S sends packets at rate (e).
•
Note
During RCC, the VQE-S initially sends packets at rate (1+e).
If the VQE-C does not use the parameters max_receive_bandwidth_sd or max_receive_bandwdith_hd to send the MRB to the VQE-S, the vqe.vqes.max_client_bw parameter is used to calculate the excess bandwidth fraction. If the vqe.vqes.max_client_bw is zero or not configured, either the vqe.vqes.excess_bw_fraction or the vqe.vqes.excess_bw_fraction_high_def is used depending on the channel bitrate and the value of the vqe.vqes.high_def_min_bw parameter.
For information on defining an excess bandwidth fraction to use for HD channels, see the vqe.vqes.excess_bw_fraction_high_def parameter.
[CT: VQE-S Parameters > Excess Bandwidth Fraction]
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
A-9
Appendix A VQE, System and Network Parameters
Table A-4 VQE-S Unicast Retransmission and RCC Parameters (continued)
Parameter and Default Value (if any) Description vqe.vqes.excess_bw_fraction_high_def="" For high definition channels, specifies the rate e (e = excess_bw_fraction_high_def / 100) that determines the rate at which packets are sent during Unicast Retransmission and RCC. The range is from 3 to 500.
•
•
For Unicast Retransmission, the VQE-S sends packets at rate (e).
During RCC, the VQE-S initially sends packets at rate (1+e). vqe.vqes.high_def_min_bw=""
The VQE-S uses the value configured in the vqe.vqes.high_def_min_bw parameter to determine what constitutes a high-definition channel.
If either vqe.vqes.excess_bw_fraction_high_def or vqe.vqes.high_def_min_bw is not explicitly configured, the VQE-S uses vqe.vqes.excess_bw_fraction for all channels.
Note If the VQE-C does not use the parameters max_receive_bandwidth_sd or max_receive_bandwdith_hd to send the MRB to the VQE-S, the vqe.vqes.max_client_bw parameter is used to calculate the excess bandwidth fraction. If the vqe.vqes.max_client_bw is zero or not configured, either the vqe.vqes.excess_bw_fraction or the vqe.vqes.excess_bw_fraction_high_def is used depending on the channel bitrate and the value of the vqe.vqes.high_def_min_bw parameter.
Minimum bit rate (in bits per second) for a channel to be considered a high definition channel. The range is from 0 to 40,000,000.
For high definition channels, the vqe.vqes.high_def_min_bw value determines whether the vqe.vqes.excess_bw_fraction_high_def value is used for the bandwidth that is available on the access link for Unicast Retransmission and
RCC. For more information, see vqe.vqes.excess_bw_fraction_high_def.
If either vqe.vqes.excess_bw_fraction_high_def or vqe.vqes.high_def_min_bw is not explicitly configured, the VQE-S uses vqe.vqes.excess_bw_fraction for all channels.
A-10
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix A VQE, System and Network Parameters
Table A-4 VQE-S Unicast Retransmission and RCC Parameters (continued)
Parameter and Default Value (if any) vqe.vqes.max_client_excess_bw_fraction=
"500" vqe.vqes.min_client_excess_bw_fraction=
"0"
Description
If the VQE-C provides a MRB in a Unicast Retransmission error repair or RCC request to the VQE-S, this parameter specifies the maximum excess bandwidth fraction to use when that fraction is computed using a VQE-C-provided MRB.
The range is from 3 to 500.
If this parameter is not specified, the VQE-S caps incoming requests from the
VQE-C to use an excess bandwidth fraction of 500%.
The MRB is the maximum receive bandwidth available on each of the tuners for a specific VQE-C. The VQE-C configuration parameters max_receive_bandwidth_sd and max_receive_bandwidth_hd can be used to provide this information to the VQE-S.
The vqe.vqes.min_client_excess_bw_fraction and vqe.vqes.max_client_excess_bw_fraction parameters allow the service provider to control the range of allowed excess bandwidth fractions. This capability can be used to limit the peak and aggregate bandwidth used by the
VQE-S.
If the VQE-C provides a MRB in a Unicast Retransmission error repair or RCC request to the VQE-S, this parameter specifies the minimum excess bandwidth fraction to use when that fraction is computed using a VQE-C-provided MRB.
The range is from 0 and 3 to 500.
If this parameter is not specified or is set to 0, a minimum value of 3% is assumed and requests for an excess bandwidth fraction of less than 3% are rejected.
The MRB is the maximum receive bandwidth available on each of the tuners for a specific VQE-C. The VQE-C configuration parameters max_receive_bandwidth_sd and max_receive_bandwidth_hd can be used to provide this information to the VQE-S.
The vqe.vqes.min_client_excess_bw_fraction and vqe.vqes.max_client_excess_bw_fraction parameters allow the service provider to control the range of allowed excess bandwidth fractions. This capability can be used to limit the peak and aggregate bandwidth used by the
VQE-S.
1.
MRB = maximum receive bandwidth.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
A-11
Appendix A VQE, System and Network Parameters
Table A-5 VQE-S RTCP Exporter Parameters
Parameter and Default Value (if any) vqe.vqes.exporter_enable="false" vqe.vqes.vqm_host="" vqe.vqes.vqm_port="" vqe.vqes.exporter_filter_nack="false"
Description
Specifies whether RTCP exports are enabled. The value true enables
RTCP exports, and false disables RTCP exports.
If vqe.vqes.exporter-enable equals true, both vqe.vqes.vqm_host and vqe.vqes.vqm_port must be provided. For information on configuring the
VQE-S RTCP Exporter, see the “Configuring the VQE-S RTCP Exporter” section on page 2-42 .
Specifies the IP address or fully qualified Internet domain name of the host on which the VQM
1
application resides.
For information on configuring RTCP Exporter, see the “Configuring the
VQE-S RTCP Exporter” section on page 2-42
.
Specifies the TCP port number on which the VQM application listens for video-quality data from RTCP Exporter.
For information on configuring RTCP Exporter, see the “Configuring the
VQE-S RTCP Exporter” section on page 2-42
.
Specifies whether RTCP NACK compound packets are excluded from the
RTCP data exported to the VQM application. The value true excludes
RTCP NACK compound packets from being exported, and false includes
RTCP NACK compound packets in the data being exported.
For information on configuring the RTCP Exporter, see the
“Configuring the VQE-S RTCP Exporter” section on page 2-42
.
1.
VQM = video-quality monitoring.
Table A-6 System Parameters
Parameter and Default Value (if any) system.global.hostname="localhost" system.dns.server="" system.dns.search_domain="" system.ntp.server=""
Description
FQDN 1 or hostname of the system. Hostname is used in multiple Linux configuration files. The range is from 3 to 200 characters.
[CT: System Parameters > Hostname]
VQE-S host only—IP address of a DNS server and an optional search domain. The range for the search domain is from 3 to 200 characters.
[CT: System Parameters > DNS Server(s) and DNS Search Domain]
IP address of an external NTP
2
server.
[CT:System Parameters > NTP Server(s)]
A-12
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix A VQE, System and Network Parameters
Table A-6 System Parameters (continued)
Parameter and Default Value (if any) system.snmp.ro_community_string="" system.snmp.location="" system.snmp.contact="" system.snmp.trap_listener="" system.snmp.syslog_trap_enable="false" system.snmp.syslog_trap_priority="2" system.snmp.channel_trap_enable="false" system.clock.timezone="America/New York"
Description
• Read-only community string—Password for read-only access to the
VQE-S or VQE Tools server. The range is from 3 to 200 characters.
•
•
Location information—Physical location of the VQE-S or VQE
Tools server. The range is from 3 to 200 characters.
Contact information—User name of a contact person who has management information for the CDE server. The range is from 3 to
200 characters.
• Trap listener—IP address or fully qualified hostname of a management host that receives the SNMP messages.
[CT: System Parameters > SNMP RO Community String and SNMP
System Location, SNMP System Contact, and SNMP Trap Listener(s)]
Specifies whether system messages generate SNMP traps (syslog traps).
Allowed values are true or false.
If sending traps from system messages is enabled, use the parameter system.snmp.syslog_trap_priority to generate traps only if the severity level of a system message meets or is below a specified level. For more information on the configuration options for generating traps from system messages, see the
“Sending SNMP Traps” section on page 28 .
[CT: System Parameters > SNMP Parameters > Enable Syslog Traps]
If sending traps on the generation of system messages is enabled, specifies that traps should only be generated for system messages that meet or are lower than the severity level defined by this parameter. The range is from 0 to 7. The default value is 2 (critical). For more information on the configuration options for generating traps from system messages, see the
“Sending SNMP Traps” section on page 28 .
[CT: System Parameters > SNMP Parameters > Syslog Trap Priority]
Specifies whether to generate SNMP traps when the state of a channel changes. Allowed values are true or false. If SNMP is configured and channel traps are enabled, channel up traps and channel down traps are sent to a NMS
3
.
For more information on enabling channel traps, see the “Sending SNMP
.
[CT: System Parameters > SNMP Parameters > Enable Channel
Up/Down Traps] time zone that is used for this CDE server.
[CT: System Parameters > Timezone]
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
A-13
Appendix A VQE, System and Network Parameters
Table A-6 System Parameters (continued)
Parameter and Default Value (if any) system.iptables.trusted_provisioner="" system.syslog.remote_server=""
Description
Depending on the hardware platform, specifies the IP addresses of the following trusted provisioners:
• On a VQE-S host, specifies IP addresses of one or more trusted channel-provisioning servers (such as VCPT).
– If VCPT is the channel-provisioning server, the IP addresses of all Ethernet interfaces (that have been assigned IP addresses) on the VCPT host must be configured as trusted HTTPS clients on the VQE-S host.
•
•
On a VQE Tools host where a VCDS receives channel information from VCPT, specifies the IP addresses of all Ethernet interfaces (that have been assigned IP addresses) on the VCPT host sending the channel information. This requirement applies even when the VCDS is in the same VQE Tools server as the VCPT.
On a VQE Tools host, specifies IP addresses of one or more trusted
VQE-C system configuration provisioning servers. This type of provisioning server is not currently used in most deployments.
Multiple system.iptables.trusted_provisioner parameters are used when there is more than one Ethernet port IP address that must be specified.
This parameter is used for enhanced communications security beyond
HTTPS. The VQE-S or VQE Tools server is configured so that only trusted HTTPS clients (as specified in system.iptables.trusted_provisioner) can send information to the VQE-S or VQE Tools server.
[CT: System Parameters > Trusted Provisioning Client(s)]
Specifies the IP addresses of remote syslog servers. In addition to logging
VQE system messages locally, you can send system messages by UDP to remote servers for centralized logging.
On the VQE-S, specifying the priority levels for system messages using the VQE-S AMT
4
allows you to control the logging level for system messages for all VQE-S processes. For more information on configuring
logging levels on the VQE-S, see the “Change VQE-S Logging” section on page 4-33
.
On the VQE Tools server, specifying the priority levels for system messages using the VCDS AMT allows you to control the logging level for system messages for all VCDS processes. For more information on configuring logging levels on the VQE Tools server, see the
VCDS Logging” section on page 5-7
.
[CT: System Parameters > Remote Syslog Server(s)]
1.
FQDN = fully-qualified domain name.
2.
NTP = Network Time Protocol.
3.
NMS = Network Management System.
4.
AMT = Application Monitoring Tool.
A-14
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix A VQE, System and Network Parameters
Table A-7 Interface Parameters
Parameter and Default Value (if any) network.eth1.addr="" network.eth2.addr="" network.eth3.addr="" network.eth4.addr="" network.eth5.addr="" network.eth6.addr="" network.bond1.addr="" network.bond2.addr="" network.bond3.addr=""
Description
For one or more of the Ethernet ports on the Cisco CDE, an IP address and prefix length (for example, 1.2.3.4/24).
• On a VQE-S host, four Ethernet interfaces (eth1 to eth4) are typically configured and used for VQE-S traffic. On CDE servers that include the Intel PRO/1000 PT Daul Port Server Adapter, six Ethernet interfaces (eth1 to eth6) are typically configured and used for VQE-S traffic.
•
•
Note
On a VQE Tools host, at least one Ethernet interface is typically configured and used for VCPT and VCDS traffic.
Ethernet interfaces that are members of a bond interface should not be assigned an IP address and prefix length.
If one Ethernet interface is used for a management network, that interface should be included in the set for which you provide IP addresses and prefix-lengths.
[CT: Network Parameters > Interface Parameters > Eth1 Interface
IP/Mask, Eth2 Interface IP/Mask, Eth3 Interface IP/Mask, Eth4 Interface
IP/Mask, Eth5 Interface IP/Mask, and Eth6 Interface IP/Mask]
For one or more bond interfaces on the Cisco CDE, an IP address and prefix length (for example, 1.2.3.4/24).
Note Bond interfaces are not supported on the VQE Tools Server.
A bond interface may be used as a management interface and as one of the following:
•
•
VQE-S traffic interface
VQE-S services interface
• VQE-S ingest interface
For more information, see the
“Bond Interfaces on a VQE-S and
VQE-Tools Server” section on page 2-12 .
The VCDB parameters for bond3 is used only on CDE servers that include the Intel PRO/1000 PT Dual Port Server Adapter.
[CT: Network Parameters > Interface Parameters > Bond1 IP/Mask and members, Bond2 IP/Mask and members, Bond3 IP/Mask and members]
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
A-15
Appendix A VQE, System and Network Parameters
Table A-7 Interface Parameters (continued)
Parameter and Default Value (if any) network.bond1.member="" network.bond2.member="" network.bond3.member=""
Description
For each bond member, names of Ethernet interfaces that are members of the bond interface.
Note Bond interfaces are not supported on the VQE Tools Server.
network.network.interface.mgmt_interfaces="eth
1, eth2, eth3, eth4, eth5, eth6"
All members of a bond interface must have the same capacity. All members must not be assigned an IP address and prefix length nor be assigned as a member of an existing bond interface.
Bond interfaces are not supported on the VQE Tools Server.
The VCDB parameters for bond3 is used only on CDE servers that include the Intel PRO/1000 PT Dual Port Server Adapter.
For the rules on adding members to bond interfaces, see the
Interfaces on a VQE-S and VQE-Tools Server” section on page 2-12 .
Names of the Ethernet or bond interfaces or both to be used for management traffic. The default value is all Ethernet interfaces on the
VQE-S or VQE Tools server, regardless of their operational status.
Multiple interfaces (one or more Ethernet and one or more bond interfaces) may be used for management traffic.
At least one Ethernet interface or one bond interface must be specified as a management interface. If you specify an Ethernet interface, it must not be a member of a bond interface.
network.route.mgmt_route=""
The management interfaces on the VQE-S may also be used for one of the following interface types:
• VQE-S traffic interface
•
•
VQE-S ingest interface
VQE-S services interface.
For more information on configuring management interfaces, see the
“Interface for a Management Network” section on page 2-18 .
[CT: Network Parameters > Interface Parameters > Management
Interface(s)]
Starting with Cisco VQE Release 3.5, this parameter is deprecated. Use the network.route.static_route parameter.
Table A-8 Static Routing Parameters
Parameter and Default Value (if any) network.route.default_gateway=""
Description
Starting with Cisco VQE Release 3.5, this parameter is deprecated. Use the network.route.static_route parameter.
A-16
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix A VQE, System and Network Parameters
Table A-8 Static Routing Parameters (continued)
Parameter and Default Value (if any) network.route.static_route=""
Description
If your deployment makes use of static routes to the management, distribution, or access network, specify the following:
• Subnet IP address and prefix length for the target network. The allowed format for the subnet IP address and prefix length is as follows:
10.1.0.0/16
Note When creating a default route on the VQE-S, specify 0.0.0.0/0 as the subnet IP address and prefix length for the target nework.
• Gateway (next hop) IP address of the interface on the router that is directly attached to the VQE-S CDE interface that is used for the target network. The interface on the VQE-S and the attached edge router may be an Ethernet interface or a bond interface. The interface on the VQE Tools server is always an Ethernet interface.
• (Optional) Outbound interface on the VQE-S or VQE Tools server for the static route. To specify an outbound interface, you append the interface name to the Gateway IP address, and separate both with a colon. Specifying an outbound interface is generally not required, nor is it recommended.
For example:
network.route.static_route="10.1.0.0/16 via 5.6.7.8"
In this example,
• 10.1.0.0/16 is the subnet IP address and prefix-length for the target network.
•
Note
5.6.7.8 is the IP address of the interface on the router directly attached to the CDE Ethernet interface of the VQE-S.
On the VQE Tools server, proper route configuration is needed for external access to the VQE Tools server. Use the static route created by this parameter to configure this access.
On the VQE-S, multipath static routes can be configured for VQE-S traffic (ingest and services) or VQE-S services traffic. The VQE-S uses
ECMP
1
to load-balance its output traffic across CDE Ethernet interfaces or the physical Ethernet interfaces of a bond interface that are directly attached to the gateway router interfaces that are specified. If a default route (static route) is configured for each Ethernet interface that is available to the VQE-S for Unicast Retransmissions, RCC, and other
VQE-S traffic, ECMP load balances output traffic across all of the CDE interfaces directly attached to the gateway router interfaces. Similarly, if a default route is configured for a bond interface, ECMP load balances output traffic across all the CDE physical interfaces assigned to the bond interface.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
A-17
Appendix A VQE, System and Network Parameters
Table A-8 Static Routing Parameters (continued)
Parameter and Default Value (if any) Description
If you subsequently configure another Ethernet interface or bond interface for VQE-S traffic, be sure to also configure an associated static route for that interface.
For more information on configuring static routes, see the
Static Routes” section on page 2-17
.
[CT: Network Parameters > Routing Parameters > Static Routing
Parameters> Static Route(s)]
1.
ECMP = equal cost multipath.
Table A-9 OSPF Parameters
Parameter and Default Value (if any) Description network.route.type="static" VQE-S host only—Specifies whether OSPF is enabled for VQE-S services (where dedicated interfaces to the access network are configured) or VQE-S traffic (where shared interfaces to the access network are configured). Allowed values are static and ospf.
If OSPF routing is enabled, dynamic routing is used from the VQE-S to the access network. The following parameters can be configured:
•
•
•
•
• network.ospf.router_id network.ospf.area network.ospf.area_type network.ospf.md5_enable
•
•
• network.ospf.md5_key network.ospf.md5_keyid network.ospf.hello_interval network.ospf.dead_interval network.ospf.router_id=""
For descriptions of the preceding parameters, see
If network.route.type="static", OSPF is disabled but static routing is still enabled. For static routing, the network.route.static_route parameter can be configured for one or more default gateway (next hop) router interfaces.
[CT: Network Parameters > Routing Parameters > OSPF Parameters >
OSPF Enable]
VQE-S host only—If OSPF routing is enabled, specifies the IP address used as the router ID to uniquely identify the VQE-S in the OSPF network. The router ID must not be the same as the IP address of one of the CDE Ethernet interfaces because the router ID is added as an internal address to the loopback interface.
[CT: Network Parameters > Routing Parameters > OSPF Parameters >
Router ID]
A-18
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix A VQE, System and Network Parameters
Table A-9 OSPF Parameters (continued)
Parameter and Default Value (if any) Description network.ospf.area_type="normal" VQE-S host only—If OSPF routing is enabled, specifies the type of OSPF area that the VQE-S traffic interfaces and feedback target host addresses resides in. Allowed values are normal or nssa
1
. network.ospf.area="0"
[CT: Network Parameters > Routing Parameters > OSPF Parameters >
Area Type]
VQE-S host only—If OSPF routing is enabled, specifies the OSPF area that the VQE-S Ethernet interfaces and feedback target addresses reside in. The range of integer values is from 0 to 4,294,967,295.
[CT: Network Parameters > Routing Parameters > OSPF Parameters >
Area ID] network.ospf.md5_enable="false" VQE-S host only—If OSPF routing is enabled, specifies whether MD5
2 authentication is enabled on the Ethernet interfaces used for VQE-S traffic. When MD5 authentication is enabled, specifying an MD5 key and
MD5 key ID are required. Allowed values are true or false. (Ethernet interfaces used for VQE-S traffic are configured with the vqe.vqes.vqe_interfaces parameter.) network.ospf.md5_key=""
[CT: Network Parameters > Routing Parameters > OSPF Parameters >
Enable MD5]
VQE-S host only—If OSPF routing and MD5 authentication are enabled, specifies the key (a string) that is configured for all Ethernet interfaces used for VQE-S traffic. When MD5 authentication is enabled, specifying an MD5 key and MD5 key ID are required. network.ospf.md5_keyid="1" network.ospf.hello_interval="10"
[CT: Network Parameters > Routing Parameters > OSPF Parameters >
MD5 Key]
VQE-S host only—If OSPF and MD5 authentication are enabled, specifies an MD5 key ID (an integer) that is used for all Ethernet interfaces used for VQE-S traffic. When MD5 authentication is enabled, an MD5 key and MD5 key ID are required. The range of integer values is from 1 to 255.
[CT: Network Parameters > Routing Parameters > OSPF Parameters >
MD5 Key ID]
VQE-S host only—If OSPF routing is enabled, specifies the interval at which OSPF Hello packets are sent, in seconds. This value must be the same for all interfaces running OSPF in the network. The hello interval is set for all VQE-S interfaces running OSPF. The range is from 1 to 65,535.
[CT: Network Parameters > Routing Parameters > OSPF Parameters >
Hello Interval]
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
A-19
Appendix A VQE, System and Network Parameters
Table A-9 OSPF Parameters (continued)
Parameter and Default Value (if any) network.ospf.dead_interval="40"
Description
VQE-S host only—If OSPF routing is enabled, specifies the OSPF dead interval, in seconds. The dead interval is the maximum amount of time allowed to receive a Hello packet from a neighbor before that neighbor is declared down. This value must be the same for all interfaces running
OSPF in the network. The dead interval is set for all VQE-S interfaces running OSPF. The range is from 1 to 65,535.
[CT: Network Parameters > Routing Parameters > OSPF Parameters >
Dead Interval]
1.
nssa = not so stubby area.
2.
MD5 = Message Digest 5.
A-20
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
A P P E N D I X
B
SNMP MIBs
This appendix provides an overview of the SNMP feature of the Cisco VQE Server (VQE-S) and VQE
Tools server. This chapter contains the following topics:
•
•
SNMP Overview
The Simple Network Management Protocol (SNMP) is an application-layer protocol that provides a standardized framework and a common language for monitoring and managing devices in a network.
The SNMP framework has three parts:
•
•
SNMP manager—System to control and monitor the activities of network hosts that use SNMP. The most common managing system is called a Network Management System (NMS). A variety of network management applications are available for use with SNMP (for example, Net-SNMP).
SNMP agent—Software component in a managed device that maintains the data for the device and reports the data, as needed, to managing systems. The agent and Management Information Base
(MIB) reside on the network hosts rather than on the NMS.
• MIB—Database of the objects that can be managed on a device. The managed objects or MIB objects can be read or set to provide information on the network devices and interfaces, and are organized hierarchically. The MIB consists of collections of MIB objects identified by object identifiers.
MIB Objects
MIB objects comprise of one or more object instances, which are essentially variables. The Cisco implementation of SNMP uses the definitions of MIB II variables described in RFC 1213.
MIBs can contain two types of MIB objects:
• Scalar objects—Define a single object instance (for example, cvqsNumberofChannels in the
CISCO-VQES-MIB).
• Columnar objects—Define multiple related objects such as zero, one, or more instances at any point in time that are grouped together in MIB tables (for example, cvqsChannelTable in the
CISCO-VQES-MIB defines the status of each channel).
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
B-1 OL-30119-01
Appendix B SNMP MIBs
VQE MIB Support
System MIB variables are accessible through SNMP as follows:
•
•
Accessing a MIB variable—Function is initiated by the SNMP agent in response to a request from the NMS. The agent retrieves the value of the requested MIB variable and responds to the NMS with that value.
Setting a MIB variable—Function is initiated by the SNMP agent in response to a message from the
NMS. The SNMP agent changes the value of the MIB variable to the value requested by the NMS.
SNMP SETs are not supported on the VQE-S or VQE Tools server.
SNMP Notifications
An SNMP agent can notify the SNMP manager when important system events occur, such as when an interface card starts or stops running. SNMP notifications are sent as either one of the following:
• Traps—Unreliable messages, which do not require receipt acknowledgment from the SNMP manager.
• Informs—Reliable messages, which are stored in memory until the SNMP manager issues a response.
Object Identifiers
An object identifier (OID) uniquely identifies a MIB object on a managed network device. The OID identifies the MIB object location in the MIB hierarchy, and provides a means of accessing the MIB object in a network of managed devices:
•
•
Standard RFC MIB OIDs are assigned by the Internet Assigned Numbers Authority (IANA)
Enterprise MIB OIDs are assigned by Cisco Assigned Numbers Authority (CANA).
Each number in the OID corresponds to a level of the MIB hierarchy. For example, the OID
1.3.6.1.4.1.9.9.xyz represents the .xyz with the location in the MIB hierarchy as follows:
1.3.6.1.4.1.9.9.942
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).ciscoMgt(9).nn-MIB
Note that the numbers in parentheses are included to help show correspondence to the MIB hierarchy.
You can uniquely identify a MIB object, such as ifNumber in the IF-MIB, by its object name
(iso.org.dod.internet.mgmt.mib-2.interfaces.ifNumber) or by its OID (1.3.6.1.2.1.2.1). In actual use,
OIDs are represented as numerical values only.
For listings of OIDs assigned to MIB objects for all Cisco MIBs, see the link: ftp://ftp.cisco.com/pub/mibs/oid
VQE MIB Support
The VQE-S and the VQE Tools server provide a standard set of built-in MIBs for managing a Linux platform, as well as enterprise-specific MIBs for monitoring VQE services. The MIBs cover GETs and a limited number of TRAPs. Only SNMP version 2 (SNMPv2) is supported on both the VQE-S and the
VQE Tools server.
B-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix B SNMP MIBs
VQE MIB Support
Note Configuration of the standard Linux MIBs, the Cisco System Messages (Syslog) MIB, or the
VQE-specific Mibs using SNMP is disabled.
Net-SNMP
The VQE-S and the VQE Tools server use Net-SNMP, a third-party product, for its tools and libraries that support SNMP. Net-SNMP offers an extensible agent, an SNMP library, tools to request or set information from SNMP agents, and tools to generate and handle SNMP traps.
Note For information on configuring and using Net-SNMP, see the Net-SNMP website: http://www.net-snmp.com/docs/
In the VQE implementation, the SNMP agent consists of a master agent and three or more subagents.
The master agent is implemented by means of Net-SNMP. An Intel subagent is used to support the Linux
MIBs, while Cisco subagents support the VQE-specific MIBs and the syslog MIB. The master agent communicates directly with the NMS by means of SNMP, and directly with the subagents by means of the AgentX protocol. Each subagent has its own MIB file and OID.
Figure B-1 Subagent Architecture
OL-30119-01
shows the SNMP agent architecture. When a subagent initializes, it registers with the master agent, and informs the master agent of the range of OIDs for which it has responsibility. When a request for information is received from the NMS, the master agent sends a request to the subagent that is responsible for the OIDs defined in the request. The subagent processes the request and sends the information to the master agent, which forwards the information to the network manager.
On VQE-S and the VQE Tools server, the Intel subagent provides non-VQE system information, and the
Syslog subagent provides information on system messages. On the VQE-S, the VQE-S subagent provides VQE-S-specific information. On the VQE Tools Server, the VQE Configuration Deployment
Server (VCDS) subagent provides information specific to the VCDS.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
B-3
Appendix B SNMP MIBs
VQE MIB Support
Note The Net-SNMP master agent service (snmpd) must be installed and be running for the subagent service to run.
Standard Linux MIBs
Net-SNMP provides a set of standard built-in MIBs for Linux platforms. The built-in MIBs cover GETs and TRAPs for some areas of the Linux distribution, such as interface status and statistics, SNMP protocol-related counters, and host resources.
The sysDescr and sysObjectID objects in the SNMPv2-MIB identify a VQE system. The following values can be used to identify a CDE hosting a VQE-S or a VCPT:
• SNMPv2-MIB::sysDescr.0 = STRING: "Cisco VQE (Video Quality Experience) offers service providers a set of technologies and products associated with the delivery of IPTV video services."
• SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.942
Note
lists the standard MIBs that are supported on the CDEs that host a VQE-S and a VCPT. For information on the supported MIBs, see the MIB area of the Net-SNMP website: http://www.net-snmp.com/docs/mibs/
Table B-1
MIB/Table
MIBs for CDEs That Host the VQE-S and the VCPT
Description
SNMPv2-MIB/snmp SNMP protocol-related counters, including cold/warm start and authentication failure traps
SNMP-NOTIFICATION-MIB/snmpNotifyTable Used to configure TRAP listeners
IF-MIB Interface status and statistics
RMON/etherStatsTable Statistics for each Ethernet interface
RMON/alarmTable Stores configuration entries that each define a variable, polling period, and threshold parameters
RMON/eventTable Controls the generation and notification of events from this device
HOST-RESOURCE-MIB (except hrPrinterTable) System, memory, storage, device, processor, network, disc, partition, FS, and software version information about Linux host
INTEL-SERVER-BASEBOARD5 Supports the Intel Server Baseboard SNMP subagent for monitoring baseboard components, providing SNMP access to GET information for baseboard components, SET sensor thresholds and support events through the NOTIFICATION-TYPE construct. See: http://people.redhat.com/peterm/IPMI/sw/basebrd5.mib
B-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix B SNMP MIBs
VQE MIB Support
Syslog MIB
The MIB CISCO-SYSLOG-MIB provides the means to gather system messages generated by the VQE-S or VQE Tools server. The VQE-S and the VQE Tools server can be configured so that these system messages are logged locally as well as being sent to a remote syslog server. With this MIB, system messages can also be received by means of SNMP. This MIB provides SNMP notifications only.
Note An SNMP GET operation returns a zero value, and configuration of this MIB via an SNMP interface is disabled.
The MIB file is located in the /usr/share/snmp/mibs/ directory, and is available for download on
Cisco.com from the following URL: ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SYSLOG-MIB.my
The CISCO-SYSLOG-CAPABILITY MIB file describes the capabilities of the CISCO-SYSLOG-MIB for the VQE-S and VQE Tools platforms. The MIB file is located in the /usr/share/snmp/mibs/ directory, and is available for download on Cisco.com from the following URL: ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SYSLOG-CAPABILITY.my
VQE-Specific MIBs
A VQE-specific MIB, CISCO-VQES-MIB, is integrated with the VQE-S. This MIB reports the status of the channels, Rapid Channel Changes (RCC), Unicast Retransmissions, and VQE-S capacity. A
VQE-specific MIB, CISCO-VQE-TOOLS-MIB, is integrated with the VQE Tools server. This MIB reports the status of the VCDS.
The MIB files are located in the /usr/share/snmp/mibs/ directory, and are available for download on
Cisco.com from: ftp://ftp-sj.cisco.com/pub/mibs/v2/CISCO-VQES-MIB.my
ftp://ftp-sj.cisco.com/pub/mibs/v2/CISCO-VQE-TOOLS-MIB.my
CISCO-VQES-MIB
The MIB CISCO-VQES-MIB defines the managed objects that describe some of the VQE-S components. The MIB CISCO-VQES-MIB reports summary status information for several VQE-S components, including channel line ups, channels, Unicast Retransmission, and RCCs.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
B-5
Appendix B SNMP MIBs
VQE MIB Support
lists the types of summary information provided per component.
Table B-2
Components
Channel line up
Information Provided by CISCO-VQES-MIB by Component
Channel
Unicast Retransmission
RCC
VQE-S Capacity
•
•
•
•
•
•
•
•
•
Summary Information
• Total number of channels in the lineup.
• Total number of active channels in the channel line up.
Time and day when the channel line up was last updated.
Name of each channel in the channel line up.
•
•
State of each channel in the channel line up—A channel may be active, inactive, or inoperative.
Number of receivers on each channel in the line up.
Multicast IP address and port number of each channel in the line up.
Channel up trap.
Channel down trap.
Total number of requests for error repair (generic NACK RTCP messages) received.
•
•
•
•
•
•
•
Total number of Generic NACK RTCP messages received that were invalid.
Total number of individual RTP packets requested for retransmission.
Total number of individual RTP packets requested and sent for retransmission.
Total number of requests for RCC received.
Total number of requests for RCC received and accepted.
Total number of requests for RCC received but not accepted.
Number of currently active RTCP receivers.
Number of received RTCP packets (ER requests, RCC requests or
Receiver Reports) rejected by the VQE-S due to active RTCP receivers in the VQE-S reaching their limit of accepting RTCP requests.
Number of received ER requests rejected by the VQE-S due to the
VQE-S reaching its limit of accepting ER requests.
Number of received RCC requests rejected by the VQE-S due to
VQE-S reaching its limit of accepting RCC requests.
B-6
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix B SNMP MIBs
OL-30119-01
VQE MIB Support
The MIB CISCO-VQES-MIB contains fifteen scalar objects, one columnar object, and two traps. The tree structure of the CISCO-VQES-MIB is as follows:
+--ciscoVqeSMIB(942)
|
+--ciscoVqeSMIBNotifs(0)
| |
| +--cvqsChannelUp(1)
| +--cvqsChannelDown(2)
|
+--ciscoVqeSMIBObjects(1)
| |
| +--cvqsControlInfo(1)
| | |
| | +-- -RW- EnumVal cvqsNotificationsEnable(1)
| | Textual Convention: TruthValue
| | Values: true(1), false(2)
| |
| +--cvqsChannelInfo(2)
| | |
| | +-- -R-- Gauge cvqsNumberofChannels(1)
| | +-- -R-- Gauge cvqsActiveChannels(2)
| | +-- -R-- String cvqsLastUpdatedTime(3)
| | | Textual Convention: DateAndTime
| | | Size: 8 | 11
| | |
| | +--cvqsChannelTable(4)
| | |
| | +--cvqsChannelTableEntry(1)
| | | Index: cvqsChannelIndex
| | |
| | +-- ---- Unsigned cvqsChannelIndex(1)
| | | Range: 1..2147483647
| | +-- -R-- EnumVal cvqsChannelMulticastIPType(2)
| | | Textual Convention: InetAddressType
| | | Values: unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16)
| | +-- -R-- String cvqsChannelMulticastIPAddr(3)
| | | Textual Convention: InetAddress
| | | Size: 0..255
| | +-- -R-- Unsigned cvqsChannelMulticastPort(4)
| | | Textual Convention: InetPortNumber
| | | Range: 0..65535
| | +-- -R-- EnumVal cvqsChannelStatus(5)
| | | Values: active(1), inactive(2), inoperative(3)
| | +-- -R-- Gauge cvqsChannelMemberPopulation(6)
| |
| +--cvqsErrorRepair(3)
| | |
| | +-- -R-- Counter64 cvqsTotalReceivedERMsgs(1)
| | +-- -R-- Counter64 cvqsTotalReceivedInvalidERMsgs(2)
| | +-- -R-- Counter64 cvqsTotalReceivedERPkts(3)
| | +-- -R-- Counter64 cvqsTotalSentERPkts(4)
| |
| +--cvqsRCC(4)
| | |
| | +-- -R-- Counter64 cvqsTotalReceivedRCCs(1)
| | +-- -R-- Counter64 cvqsTotalAcceptedRCCs(2)
| | +-- -R-- Counter64 cvqsTotalRefusedRCCs(3)
| |
| +--cvqsCapacity(5)
| |
| +-- -R-- Gauge cvqsTotalRTCPReceivers(1)
| +-- -R-- Counter64 cvqsRejectedRTCPs(2)
| +-- -R-- Counter64 cvqsRejectedERs(3)
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
B-7
Appendix B SNMP MIBs
VQE MIB Support
| +-- -R-- Counter64 cvqsRejectedRCCs(4)
|
+--ciscoVqeSMIBConform(2)
|
+--cvqsMIBCompliances(1)
| |
| +--cvqsMIBCompliance(1)
|
+--cvqsMIBGroups(2)
|
+--ciscoVqeSControlGroup(1)
+--ciscoVqeSChannelGroup(2)
+--ciscoVqeSERGroup(3)
+--ciscoVqeSRCCGroup(4)
+--ciscoVqeSCapacityGroup(5)
|
+--ciscoVqeSNotifGroup(6)
CISCO-VQE-TOOLS-MIB
The CISCO-VQE-TOOLS-MIB is integrated with the VQE Tools server. It defines the managed objects and notifications that describe the VCDS component responsible for channel delivery. The data reported includes the following:
• Number of open connections
•
•
Number of requests received
Number of responses sent
• Number of requests per second.
The MIB CISCO-VQE-TOOLS-MIB contains four scalar objects. The tree structure of the
CISCO-VQE-TOOLS-MIB is as follows:
+--ciscoVQETOOLSMIB(969)
|
+--ciscoVqeToolsMIBNotifs(0)
|
+--ciscoVQETOOLSMIBObjects(1)
| |
| +--vcdsInfo(1)
| | |
| | +-- -R-- Unsigned numberOfSessions(1)
| | +-- -R-- Gauge cvqtNumberOfSessions(1)
| | +-- -R-- Counter64 requestsReceivedTotal(2)
| | | Textual Convention: Unsigned64
| | +-- -R-- Counter64 cvqtTotalReceivedRequests(2)
| | +-- -R-- Counter64 responsesSentTotal(3)
| | | Textual Convention: Unsigned64
| | +-- -R-- Counter64 cvqtTotalSentResponses(3)
| | +-- -R-- Unsigned requestsPerSecond(4)
| | +-- -R-- Gauge cvqtRequestRate(4)
| |
| +--cvqtVcdsInfo(1)
|
+--ciscoVqeToolsMIBObjects(1)
|
+--ciscoVQETOOLSMIBConformance(2)
| |
| +--ciscoVQETOOLSMIBCompliances(1)
| | |
| | +--cvqtMIBReadOnlyCompliance(1)
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
B-8 OL-30119-01
Appendix B SNMP MIBs
VQE MIB Support
| |
| +--cvqtMIBCompliances(1)
| |
| +--ciscoVQETOOLSMIBGroups(2)
| | |
| | +--ciscoVqeToolsVcdsGroup(1)
| |
| +--cvqtMIBGroups(2)
|
+--ciscoVqeToolsMIBConform(2)
Compiling VQE-Specific MIBs
If you plan to integrate the VQE-S or the VQE Tools server with an SNMP-based management application, then you must also compile the MIBs for that platform. For example, if you are running HP
OpenView on a UNIX operating system, you must compile VQE-S or VQE Tools server MIBs with the
HP OpenView Network Management System (NMS). For instructions, see the NMS documentation.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
B-9
VQE MIB Support
Appendix B SNMP MIBs
B-10
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
VQE System Messages
A P P E N D I X
C
This appendix provides information on the Cisco VQE system messages. The VQE software writes these messages to these locations:
• VQE-S system messages are written to the /var/log/vqe/vqe.log file.
• VQE Client Configuration Delivery Server (VCDS) system messages are also written to the
/var/log/vqe/vqe.log file.
Not all system messages indicate problems with VQE. Some messages are purely informational, while others may help diagnose problems with communications links or the operating system (for example, file permission problems). Only critical messages are displayed on the CDE console.
For information on the VQE-S AMT and VCPT logging output, see the
VCPT Logging and Log Files” section on page 6-3 .
System Message Structure
System messages are structured as follows:
FACILITY-SEVERITY-MNEMONIC: Message-text
• FACILITY code
The facility code consists of two or more uppercase letters that indicate the facility to which the message refers.
lists the VQE facility codes.
Table C-1 VQE Facility Codes
Code
STUN_SERVER
VQES_CP
VQES_DP_CLIENT
VQE Facility
STUN Server (VQE-S)
VQE-S Control Plane
VQE-S Data Plane Client
VQES_DP VQE-S Data Plane
VQES_MLB_Client VQE-S Multicast Load Balancer Client
VQES_MLB
VQES_PM
VQE-S Multicast Load Balancer
VQE-S Process Monitor
VQE_CFGTOOL
VQE_CFG
VQE Configuration Tool (vqe_cfgtool command)
VQE channel configuration
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
C-1
Appendix C VQE System Messages
System Message Structure
Table C-1 VQE Facility Codes (continued)
VQE_UTILS VQE utilities, such as hash table
VQE_RTP
VQE_RTSP
1.
RTCP = RTP Control Protocol.
VQE Real-Time Transport Protocol
(Many of these messages are related to the
RTCP
1
).
VQE Real Time Streaming Protocol (VCDS related)
• SEVERITY level
The severity level is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation.
Table C-2 lists the message severity levels.
Messages of severity 7 (Debugging) are not described in this appendix.
Table C-2 Message Severity Levels
Severity Level Name
0 Emergency
1 Alert
Description
System is unusable.
Immediate action is required.
5 Notification Normal but significant condition
7 Debugging Message that appear during debugging only
•
•
MNEMONIC code
The combination of the facility code and the mnemonic code uniquely identifies the error message.
Message-text
Message-text is a text string that describes the condition. The text string sometimes contains detailed information about the event, including port numbers and network addresses. Because variable fields change from message to message, they are represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec].
lists the variable fields in messages.
C-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix C VQE System Messages
System Message Example
Table C-3 Representations of Variable Fields in Messages
Representation Type of Information
[chars] or [char] Character string
[dec] Decimal
[int] Integer
[num] Number
System Message Example
The following is an example of a VQE system message:
VQES_CP-3-CP_CHANNEL_DELETE_ERR: Failed to delete a channel due to [chars]
•
•
•
•
VQES_CP is the facility code.
3 is the severity level.
CP_CHANNEL_DELETE_ERR is the mnemonic code.
“Failed to delete a channel due to [chars]” is the message text.
Basic Recovery Procedures
In the Recommended Actions of the system messages, certain recovery procedures that VQE users should perform are referred to numerous times.
provides references to where you can find more information on these recovery procedures.
Table C-4 Recovery Procedures in Recommended Actions
Recovery Procedure in Recommended Action
Reboot the VQE-S.
Restart the VQE-S application.
Restart the VQE-S channels.
Modify the channel configuration and resend it to the
VQE-Ss or VCDS servers.
Notes and Where to Find Information
Restarting the System and Verifying System and VQE-S Status, page D-28
Stopping, Starting, and Restarting VQE-S, page 6-30
In VCPT, use the Force Update button to send the channel
information to the VQE Server (VQE-S). See the “Force Update
.
Chapter 3, “Using the VQE Channel Provisioning Tool”
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
C-3
Appendix C VQE System Messages
VQE System Messages Reference Information
Table C-4 Recovery Procedures in Recommended Actions (continued)
Recovery Procedure in Recommended Action
Modify vcdb.conf and apply the configuration.
Issue the vqereport command to gather data that may help identify the nature of the error.
Notes and Where to Find Information
For VQE configuration (vcdb.conf) information, see
“Configuring VQE Server and VQE Tools.”
For information on applying a VQE configuration with the –apply option to vqe_cfgtool, see the
“Using the VQE Configuration Tool
Command-Line Options” section on page 7-18
.
“Using the vqereport Command” section on page 6-29
VQE System Messages Reference Information
Starting with Cisco VQE Release 3.0, reference information for the VQE system messages is listed in
HTML format in a file that is available for each release from the Error and Systems Messages page on
Cisco.com.
Tip The online system messages file with reference and recovery information is also available from the
VQE software download area on Cisco.com. The files are located with the VQE software installation file. The system messages link is named System Messages and Recovery Procedures for X.X(X).
For each system message, the HTML file contains the message text, an explanation of the message, and a recommended action describing what (if anything) you need to do. For example:
Error Message STUN_SERVER-2-SS_INIT_FAILURE_CRIT: STUN Server initialization failed due to [chars]
Explanation A software error has occurred during the initialization of the STUN Server process and the process will not start.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Note The Recommended Action frequently involves a recovery procedure (for example, “Restart the VQE-S application.”) that is described in the
“Basic Recovery Procedures” section on page C-3 .
C-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
A P P E N D I X
D
Manual Initial VQE System Configuration
This appendix explains how to perform manual initial configuration on the two categories of CDE servers running the VQE software:
• VQE server (VQE-S)—CDE hosting the VQE-S
• VQE Tools server—CDE hosting VQE Channel Provisioning Tool (VCPT), VQE Client
Configuration Delivery Server (VCDS) and VCDS AMT.
In a VQE deployment, use of a VQE Tools server and VCPT is optional.
The alternative to manual configuration is to use the Cisco vqe_cfgtool. For information on using the utility, see the
“VQE-S and VQE-Tools Server: Routing and Interface Configuration Overview” section on page 2-11 .
Note We recommend that you use the vqe_cfgtool rather than try to do the initial configuration manually because the utility simplifies your work and is known to produce correct results.
For information on installing or upgrading VQE software, see Release Notes for Cisco CDA Visual
Quality Experience Application.
The manual initial configuration procedures are explained in these sections:
•
•
Setting Up a Cisco CDE That Hosts VQE-S
Setting Up a Cisco CDE That Hosts VQE Tools
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-1
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Setting Up a Cisco CDE That Hosts VQE-S
This section explains how to perform the initial configuration tasks for a Cisco CDE hosting the VQE-S.
When performed manually, the initial configuration tasks involve editing the /etc/opt/vqes/vcdb.conf file to configure the essential VCDB parameters. The use of the vcdb.conf file simplifies the configuration tasks. Because the VQE Configuration Tool automatically applies the VCDB values to the /etc configuration files on system reboot, mistakes in configuration file syntax are unlikely.
For information on manually editing the vcdb.conf file, see the
“Manually Editing the VCDB File” section on page 7-14 .
Perform these initial configuration tasks in the order shown:
1.
6.
7.
4.
5.
2.
3.
Prerequisites for a Cisco CDE That Hosts the VQE-S, page D-3
Configuring the Linux Operating System for the VQE-S, page D-3
Configuring Bond Interfaces, page D-5
Configuring a Static Route for a Management Network (VQE-S Host), page D-6
Configuring Static Routes for VQE-S Traffic or VQE-S Services Traffic (VQE-S Host), page D-8
Enabling OSPF Routing for VQE-S Traffic or VQE-S Services Traffic, page D-10
8.
9.
Configuring Interfaces for VQE-S Traffic (Ingest and Services) and VQE-S Services Traffic, page D-15
Synchronizing the Time and Configuring Network Time Protocol, page D-19
10.
11.
12.
13.
VQE STUN Server Is Enabled By Default, page D-20
Ensuring That Only Trusted HTTPS Clients Can Communicate Using HTTPS, page D-21
Configuring Remote Syslog Servers, page D-22
14.
15.
Starting VQE-S System Services and Verifying Status, page D-22
Starting the VQE-S Processes and Verifying Status, page D-27
Restarting the System and Verifying System and VQE-S Status, page D-28
Note The configuration instructions in this section are intended for new installations of Cisco VQE
Release 3.7 software, where the Cisco CDE has the Cisco VQE Release 3.7 software preinstalled.
For information on upgrading an already configured Cisco CDE, see the Release Notes for Cisco CDA
Visual Quality Experience, Release 3.7.
For information on configuring the VQE-S RTCP Exporter, see the
Exporter” section on page 2-42 .
D-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Prerequisites for a Cisco CDE That Hosts the VQE-S
This section explains tasks that should be performed before setting up a Cisco CDE that hosts the
VQE-S.
Connecting Cables for the VQE-S
.
For the location of connectors on the Cisco CDE front and back panels, see the Cisco Content Delivery
Engine 110 Hardware Installation Guide.
Setting Up SSL Certificates for the VQE-S
It is recommended that you deploy your own Secure Sockets Layer (SSL) certificates or commercial SSL certificates before beginning the tasks for setting up a Cisco CDE that hosts the VQE-S. For information on setting up the certificates, see the
“Setting Up SSL Certificates” section on page 2-5 .
Configuring the Linux Operating System for the VQE-S
This section explains the initial Linux configuration tasks needed for a Cisco CDE appliance that runs the VQE-S software. The explanation assumes that the needed software for Linux and the VQE-S has been preinstalled on the Cisco CDE appliance. For Red Hat Enterprise Linux 5.1 documentation, go to the following website: http://www.redhat.com/docs/manuals/enterprise/
For software configuration, the RJ-45 NIC (Ethernet) ports on the Cisco CDE back panel are specified as eth1 to eth6 as shown in
Note Earlier models of the CDE have four Ethernet ports (eth1 to eth4). These models did not have the Intel
PRO/1000 PT Dual Port Server Adapter that provides the eth5 and eth6 ports.
Figure D-1 NIC Port Numbering for Software Configuration eth3 eth2 eth6 eth5
3
4
2
1 eth4 eth1
For the configuration examples in this section,
shows the IP addresses for interfaces eth1, eth2, bond1 (with eth3 and eth4 as its members), and the corresponding interfaces on the edge router.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-3
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Figure D-2 IP Addresses for VQE-S Configuration Examples
To configure the Linux operating system and other software for the VQE-S, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
If needed, login as root. You must have root privileges to modify the vcdb.conf file.
To create the password for the vqe username (a pre-created Linux user ID), issue the following command:
[root@system]# passwd vqe
Enter a password that follows the password guidelines:
A valid password should be a mix of upper and lower case letters, digits, and other characters. You can use an 8 character long password with characters from at least 3 of these 4 classes, or a 7 character long password containing characters from all the classes. An upper case letter that begins the password and a digit that ends it do not count towards the number of character classes used.
A passphrase should be of at least 3 words, 12 to 40 characters long and contain enough different characters.
This username and password can be used to log in to Linux directly using SSH. The vqe username and password can also be used log in to the VQE-S AMT.
To configure CDE Ethernet interfaces eth1 to eth6, edit the /etc/opt/vqes/vcdb.conf file by adding to the file one or more network.ethx.addr parameters, where ethx is eth1, eth2, and so on. Specify an IP address and prefix length for each interface that is not a member of a bond interface. The following example shows two vcdb.conf lines for the two Ethernet interfaces: network.eth1.addr="10.2.9.2/24" network.eth2.addr="10.2.10.2/24"
To configure the hostname for the CDE server, edit the /etc/opt/vqes/vcdb.conf file by adding to the file the system.global.hostname parameter and specifying a hostname. The following example specifies the hostname as starfire-iptv: system.global.hostname="starfire-iptv"
To configure a DNS server, edit the /etc/opt/vqes/vcdb.conf file by adding the VCDB parameters for the
IP address and optionally for the search domain of a DNS server and specifying the needed values:
• system.dns.server="IP_address"
• system.dns.search_domain="search_domain"
For example: system.dns.server="192.0.20.53." system.dns.search_domain="domain.com"
D-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Step 6 Save the vcdb.conf file.
Configuring Bond Interfaces
This section provides information on configuring bond interfaces on the CDE that hosts the VQE-S.
Bond interfaces may be used for the VQE-S traffic (ingest and services), VQE-S ingest traffic, or VQE-S service traffic, depending on whether shared or dedicated interfaces are configured. Bond interfaces may also be used for VQE-S management traffic.
Note For guidance on using bond interfaces, see the
“Bond Interfaces on a VQE-S and VQE-Tools Server” section on page 2-12 .
To configure a bond interface with one or more CDE Ethernet interfaces as members, follow these steps:
Step 1
Step 2
Step 3
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
To configure CDE bond interfaces bond1 to bond3, edit the /etc/opt/vqes/vcdb.conf file by adding to the file one or more network.bondx.addr parameters, where bondx is bond1, bond2, or bond3. Specify an IP address and prefix length for each bond interface. The following example shows a line added to the vcdb.conf file for a single bond interface: network.bond1.addr="10.2.11.2/24"
To add CDE Ethernet interfaces to a bond interface, edit the /etc/opt/vqes/vcdb.conf file by adding to the file one or more network.bondx.member parameters, where bondx is bond1, bond2, or bond3. Specify the CDE Ethernet interfaces to be added as members to each bond interface. The following example shows a line added to the vcdb.conf file to add two Ethernet interfaces to a bond interface: network.bond1.member=”eth3,eth4”
Note An Ethernet interface should not be assigned as a member of a bond interface if that Ethernet interface is either already assigned an IP address and prefix length, or if that Ethernet interface is already a member of another bond interface.
Step 4 Save the vcdb.conf file.
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status
section. Reboot once when all VCDB configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-5
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
After the VQE-S host is rebooted or the configuration has been applied, you can verify that the Ethernet interfaces and bond interfaces are configured correctly and up and running by issuing the following commands:
• Use the ifconfig interface command to verify that each Ethernet interface or bond interface is up and running and the IP address and netmask for each are set correctly. The following example is for eth1:
[root@system]# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:0E:0C:C1:F4:0F
inet addr:10.7.10.2 Bcast:10.7.10.255 Mask:255.255.255.0
inet6 addr: fe90::20e:cff:fec7:f30f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:192 (192.0 b) TX bytes:2700 (2.6 KiB)
Base address:0x3000 Memory:b8800000-b8820000
The following example is for bond1:
[root@system]# ifconfig bond1 bond1 Link encap:Ethernet HWaddr 00:0E:0C:C6:D4:2E
inet addr:8.5.28.2 Bcast:8.5.28.255 Mask:255.255.255.0
inet6 addr: fe90::20e:cff:fec5:d42e/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:1198174 errors:0 dropped:0 overruns:0 frame:0
TX packets:866284 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:124912504 (119.1 MiB) TX bytes:105570108
• Use the ip link show eth# command (where # is the Ethernet or bond interface number) to check that the link is up. The following example is for eth1:
[root@system]# ip link show eth1 eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0e:0c:c6:e4:fe brd ff:ff:ff:ff:ff:ff
The following is an example for bond1:
[root@system]# ip link show bond1 bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether 00:0e:0c:c6:d4:2e brd ff:ff:ff:ff:ff:ff
• Use the ping command to check that the Cisco CDE can reach the connected edge router. For example:
[root@system]# ping 10.2.9.1
Configuring a Static Route for a Management Network (VQE-S Host)
If your deployment makes use of a management network, a static route for the management network can be configured using the VCDB parameter network.route.static_route. The configuration example in this section configures CDE Ethernet interface eth1 as the interface to the management network.
D-6
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
When the VQE-S uses dedicated interfaces for ingest traffic for multicast streams, the network.route.static_route parameter can be used to define a static route to the distribution network where video sources reside. For information, see the
“Routing Configuration for Dedicated Interfaces and Shared Interfaces” section on page 2-16
.
Note If you configure a static route for a management network, the Multicast Load Balancer (MLB) monitors the status of this route. If the MLB detects that the underlying interface is admistratively down, the MLB attempts to re-create the route once the interface is brought back up.
To configure a static route for a management network, follow these steps:
Step 1
Step 2
Step 3
Step 4
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
Edit the /etc/opt/vqes/vcdb.conf file by adding to the file a network.network.interface.mgmt_interfaces parameter. Specify the name of the Ethernet interfaces and the bond interfaces designated for management traffic. One or more CDE Ethernet or bond interfaces may be specified. The Ethernet interface must not be a member of a bond interface.
For this example, assume CDE Ethernet interface eth1(10.2.9.2) on the VQE-S host is designated for management traffic.
The line in the vcdb.conf file is as follows: network.network.mgmt_interfaces=”eth1”
Add to the /etc/opt/vqes/vcdb.conf file a network.route.static_route parameter and specify the needed values using the following format: network.route.static_route="target-network-subnet-addr/prefix-length via
gateway-addr:outbound-interface"
The target-network-subnet-addr/prefix-length is the IP address and prefix length for the management network. The gateway-addr is the IP address of the router Ethernet interface or bond interface that is directly attached to the CDE Ethernet port or bond interface that is used for management network traffic.
The outbound-interface is the interface used on the VQE-S for this static route.
For this example, assume the following:
• CDE Ethernet interface eth1 (10.2.9.2) is used for the target management network on the VQE-S host.
• Management network is 192.0.0.0/8.
The line in the vcdb.conf file is as follows: network.route.static_route="192.0.0.0/8 via 10.2.9.1"
In the preceding example, 10.2.9.1 is the gateway-addr—the router interface that is directly attached to eth1 on the VQE-S host.
shows the IP addresses used in this example for the eth1 interface and the directly attached router.
Save the vcdb.conf file.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-7
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status
section. Reboot once when all VCDB configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18
.
After the VQE-S host is rebooted or the configuration has been applied, you can verify that the static route for the management network is present in the routing table by issuing the following command:
[root@system]# ip route show
The output is similar to the following:
192.0.0.0/8 via 10.2.9.1 dev eth1 default nexthop via 10.2.10.1 dev eth2 weight 1 nexthop via 10.2.10.1 dev bond1 weight 1
Configuring Static Routes for VQE-S Traffic or VQE-S Services Traffic (VQE-S
Host)
This section provides information on configuring static routes for VQE-S traffic to the access network on the CDE that hosts VQE-S. The configuration is similar regardless of whether dedicated interfaces or shared interfaces are used.
Note For information on configuring static routes for feedback targets on the directly attached router, see the
eth2, eth3, and eth4 and the corresponding interfaces on the edge router.
Figure D-3 IP Addresses for VQE-S Configuration Examples
Cisco CDE110
CDE110 eth1
10.2.9.2
eth2
10.2.10.2
10.2.11.2
eth3
10.2.12.2
eth4
10.2.9.1
10.2.10.1
10.2.11.1
10.2.12.1
Edge router
On the Cisco CDE that hosts the VQE-S, multiple Ethernet interfaces or multiple bond interfaces can be used for the VQE-S traffic, including incoming multicast streams, outgoing Unicast Retransmissions and
RCC unicast transmissions, and other VQE-S traffic. In addition, some VQE deployments may use one of the Ethernet or one of the bond interfaces as the interfaces to a management network.
D-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
If a default (next hop) route is configured for each CDE Ethernet interface or bond interface that is available for VQE-S traffic, Equal Cost Multipath (ECMP) is used to load-balance VQE-S output traffic across the CDE interfaces that are directly attached to the gateway router interfaces specified in the network.route.static_route parameter.
Note A static route should be configured for each interface used for VQE-S traffic. Otherwise, output load is not balanced and some interfaces may be overloaded.
To configure a static route for one or more CDE Ethernet interfaces or one or more bond interfaces, follow these steps:
Step 1
Step 2
Step 3
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
If disabling OSPF routing for VQE-S traffic is needed, edit the /etc/opt/vqes/vcdb.conf file by adding to the file the network.route.type parameter and specifying the value static for the parameter: network.route.type="static"
To configure default gateways for each Ethernet interface that is available for VQE-S traffic, edit the
/etc/opt/vqes/vcdb.conf file by adding to the file one or more network.route.static_route parameters and specify the needed values using the following format: network.route.static_route="target-network-subnet-addr/prefix-length via
gateway-addr:outbound-interface"
For the target-network-subnet-addr/prefix-length, specify 0.0.0.0/0.
The gateway-addr is the IP address of the router Ethernet interface or bond interface that is directly attached to the CDE Ethernet port or bond interface that is used for access network traffic. The
outbound-interface is the interface used on the VQE-S for this static route and is optional.
Note For load balancing to work effectively, each interface to the distribution network must have the same capacity. Multiple bond interfaces should not be specified and a combination of Ethernet and bond interfaces cannot not be specified in this parameter.
The following example shows two vcdb.conf lines that add default gateways for the Ethernet interfaces displayed in
network.route.static_route=”0.0.0.0/0 via 10.2.11.1” network.route.static_route=”0.0.0.0/0 via 10.2.12.1”
In the preceding example, 10.2.11.1 and 10.2.12.1 are the gateway (next hop) addresses on the router that is directly attached to the VQE-S host.
Note If one Ethernet interface is used is designated for a management network, that interface should not be included in the set for which gateway router interfaces are specified.
Step 4 Save the vcdb.conf file.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-9
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status” section on page D-28 . Reboot once when all VCDB configuration
tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18
.
After the VQE-S host is rebooted or the configuration has been applied, you can verify that the default gateway routes are present in the routing table of the CDE by issuing the following command:
[root@system]# ip route show
The output is similar to the following: default nexthop via 10.2.11.1 dev bond1 weight 1
Enabling OSPF Routing for VQE-S Traffic or VQE-S Services Traffic
This section provides information on enabling and configuring OSPF routing for VQE-S traffic (ingest and services) or VQE-S services traffic to the access network on the CDE that hosts the VQE-S. The configuration is similar regardless of whether dedicated interfaces or shared interfaces are used.
Note For guidance on configuring the attached router for OSPF routing, see the
“For OSPF Routing: Guidance for Configuring the Attached Router” section on page 2-48
.
To configure OSPF routing for the CDE Ethernet interfaces or bond interfaces that are used for VQE-S traffic or VQE-S services traffic, follow these steps:
Step 1
Step 2
Step 3
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
To enable OSPF routing for VQE-S traffic to the access network, edit the /etc/opt/vqes/vcdb.conf file by adding to the file the network.route.type parameter and specifying the value ospf for the parameter: network.route.type="ospf"
To configure OSPF routing for the VQE-S traffic or VQE-S services interface, edit the
/etc/opt/vqes/vcdb.conf file by adding one or more of the following parameters to the file. The OSPF parameters that you choose to use depend on your network implementation.
Note Some of the OSPF parameters have a default value if you do not add the parameter to and specify a value in the vcdb.conf file.
•
•
•
•
• network.ospf.router_id network.ospf.area network.ospf.area_type network.ospf.md5_enable network.ospf.md5_key
D-10
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Step 4
•
• network.ospf.md5_keyid network.ospf.hello_interval network.ospf.dead_interval •
For information on each of the preceding parameters and default values, see
Save the vcdb.conf file.
OL-30119-01
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status” section on page D-28 . Reboot once when all VCDB configuration
tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
On the VQE-S
After the VQE-S host is rebooted or the configuration has been applied, you can verify that the OSPF configuration is present on the CDE by issuing the following commands where:
• 8.31.200.1 is the OSPF router ID of the VQE-S.
•
•
•
8.31.1.1. is a feedback target address.
0.0.0.0/0 is the default route in the routing table on the VQE-S.
VQE-S traffic interfaces are eth2 (10.1.1.2) and eth3 (10.1.2.2).
[root@system]# show ip ospf vqe-s# show ip ospf
OSPF Routing Process, Router ID: 8.31.200.1
Supports only single TOS (TOS0) routes
This implementation conforms to RFC2328
RFC1583Compatibility flag is disabled
OpaqueCapability flag is disabled
Initial SPF scheduling delay 200 millisec(s)
Minimum hold time between consecutive SPFs 1000 millisec(s)
Maximum hold time between consecutive SPFs 10000 millisec(s)
Hold time multiplier is currently 1
SPF algorithm last executed 1m00s ago
SPF timer is inactive
Refresh timer 10 secs
This router is an ASBR (injecting external routing information)
Number of external LSA 1. Checksum Sum 0x0000efb2
Number of opaque AS LSA 0. Checksum Sum 0x00000000
Number of areas attached to this router: 1
Area ID: 0.0.0.1 (NSSA)
Shortcutting mode: Default, S-bit consensus: no
Number of interfaces in this area: Total: 3, Active: 3
It is an NSSA configuration.
Elected NSSA/ABR performs type-7/type-5 LSA translation.
It is not ABR, therefore not Translator.
Number of fully adjacent neighbors in this area: 2
Area has no authentication
Number of full virtual adjacencies going through this area: 0
SPF algorithm executed 4 times
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-11
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Number of LSA 6
Number of router LSA 2. Checksum Sum 0x0000a03d
Number of network LSA 2. Checksum Sum 0x00010556
Number of summary LSA 1. Checksum Sum 0x0000519e
Number of ASBR summary LSA 0. Checksum Sum 0x00000000
Number of NSSA LSA 1. Checksum Sum 0x0000693e
Number of opaque link LSA 0. Checksum Sum 0x00000000
Number of opaque area LSA 0. Checksum Sum 0x00000000
[root@system]# show ip ospf database
OSPF Router with ID (8.31.200.1)
Router Link States (Area 0.0.0.1 [NSSA])
Link ID ADV Router Age Seq# CkSum Link count
8.31.20.1 8.31.20.1 1120 0x80000012 0x1707 2
8.31.200.1 8.31.200.1 1120 0x8000001b 0x8936 3
Net Link States (Area 0.0.0.1 [NSSA])
Link ID ADV Router Age Seq# CkSum
25.1.1.1 8.31.20.1 1125 0x80000001 0x08a6
25.1.2.1 8.31.20.1 1120 0x80000001 0xfcb0
Summary Link States (Area 0.0.0.1 [NSSA])
Link ID ADV Router Age Seq# CkSum Route
0.0.0.0 8.31.20.1 159 0x8000000c 0x4f9f 0.0.0.0/0
NSSA-external Link States (Area 0.0.0.1 [NSSA])
Link ID ADV Router Age Seq# CkSum Route
8.31.1.1 8.31.200.1 1125 0x80000003 0x693e E2 8.31.1.1/32 [0x0]
AS External Link States
Link ID ADV Router Age Seq# CkSum Route
8.31.1.1 8.31.200.1 1125 0x80000003 0xefb2 E2 8.31.1.1/32 [0x0]
[root@system]# show ip ospf route
============ OSPF network routing table ============
N IA 0.0.0.0/0 [2] area: 0.0.0.1
via 25.1.1.1, eth2
via 25.1.2.1, eth3
N 8.31.200.1/32 [10] area: 0.0.0.1
directly attached to lo
N 25.1.1.0/24 [1] area: 0.0.0.1
directly attached to eth2
N 25.1.2.0/24 [1] area: 0.0.0.1
directly attached to eth3
============ OSPF router routing table =============
R 8.31.20.1 [1] area: 0.0.0.1, ABR, ASBR
via 25.1.1.1, eth2
via 25.1.2.1, eth3
============ OSPF external routing table ===========
D-12
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
OL-30119-01
Setting Up a Cisco CDE That Hosts VQE-S
[root@system]# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
I - ISIS, B - BGP, > - selected route, * - FIB route
O>* 0.0.0.0/0 [110/2] via 25.1.1.1, eth2, 00:01:40
via 25.1.2.1, eth3, 00:01:40
C>* 8.31.1.1/32 is directly connected, lo
O 8.31.200.1/32 [110/10] is directly connected, lo, 00:01:49
C>* 8.31.200.1/32 is directly connected, lo
O 25.1.1.0/24 [110/1] is directly connected, eth2, 00:01:45
C>* 25.1.1.0/24 is directly connected, eth2
O 25.1.2.0/24 [110/1] is directly connected, eth3, 00:01:44
C>* 25.1.2.0/24 is directly connected, eth3
C>* 127.0.0.0/8 is directly connected, lo
K>* 224.0.0.0/4 is directly connected, eth1
On the Cisco 7600 Edge Router
After the VQE-S host is rebooted, you can verify that the OSPF configuration is present on the Cisco
7600 edge router by issuing the following commands where:
•
•
8.31.20.1 is the OSPF router ID on the edge router.
In the show ip route command output, 8.31.1.1. is accessible from two interfaces, indicating the
ECMP is configured correctly.
• Configuration on the edge router is as follows: router ospf 100
router-id 8.31.20.1
log-adjacency-changes
area 1 nssa no-summary
traffic-share min across-interfaces
network 25.1.1.0 0.0.0.255 area 1
network 25.1.2.0 0.0.0.255 area 1
network 26.1.1.0 0.0.0.255 area 0
maximum-paths 8 c7600> show ip ospf
Routing Process "ospf 100" with ID 8.31.20.1
Start time: 00:00:04.540, Time elapsed: 06:07:33.660
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
It is an area border and autonomous system boundary router
Redistributing External Routes from,
Router is not originating router-LSAs with maximum metric
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Incremental-SPF disabled
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 1. Checksum Sum 0x002F1B
Number of opaque AS LSA 0. Checksum Sum 0x000000
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 2. 1 normal 0 stub 1 nssa
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-13
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
D-14
Number of areas transit capable is 0
External flood list length 0
IETF NSF helper support enabled
Cisco NSF helper support enabled
Reference bandwidth unit is 100 mbps
Area BACKBONE(0) (Inactive)
Number of interfaces in this area is 1
Area has no authentication
SPF algorithm last executed 06:07:24.744 ago
SPF algorithm executed 4 times
Area ranges are
Number of LSA 4. Checksum Sum 0x012D0C
Number of opaque link LSA 0. Checksum Sum 0x000000
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0
Area 1
Number of interfaces in this area is 2
It is a NSSA area
Perform type-7/type-5 LSA translation
Area has no authentication
SPF algorithm last executed 00:18:18.804 ago
SPF algorithm executed 10 times
Area ranges are
Number of LSA 6. Checksum Sum 0x025E70
Number of opaque link LSA 0. Checksum Sum 0x000000
Number of DCbitless LSA 2
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0 c7600> show ip ospf database
OSPF Router with ID (8.31.20.1) (Process ID 100)
Router Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Link count
8.31.20.1 8.31.20.1 288 0x8000000D 0x001B73 1
Summary Net Link States (Area 0)
Link ID ADV Router Age Seq# Checksum
8.31.200.1 8.31.20.1 1239 0x80000001 0x009B69
25.1.1.0 8.31.20.1 1244 0x80000011 0x004292
25.1.2.0 8.31.20.1 1234 0x80000013 0x00339E
Router Link States (Area 1)
Link ID ADV Router Age Seq# Checksum Link count
8.31.20.1 8.31.20.1 1249 0x80000012 0x001707 2
8.31.200.1 8.31.200.1 1250 0x8000001B 0x008936 3
Net Link States (Area 1)
Link ID ADV Router Age Seq# Checksum
25.1.1.1 8.31.20.1 1254 0x80000001 0x0008A6
25.1.2.1 8.31.20.1 1250 0x80000001 0x00FCB0
Summary Net Link States (Area 1)
Link ID ADV Router Age Seq# Checksum
0.0.0.0 8.31.20.1 289 0x8000000C 0x004F9F
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Type-7 AS External Link States (Area 1)
Link ID ADV Router Age Seq# Checksum Tag
8.31.1.1 8.31.200.1 1256 0x80000003 0x00693E 0
Type-5 AS External Link States
Link ID ADV Router Age Seq# Checksum Tag
8.31.1.1 8.31.20.1 1240 0x80000001 0x002F1B 0 c7600> show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
8.0.0.0/32 is subnetted, 2 subnets
O N2 8.31.1.1 [110/20] via 10.1.2.2, 00:20:45, GigabitEthernet0/2
[110/20] via 10.1.1.2, 00:20:45, GigabitEthernet0/1
O 8.31.200.1 [110/11] via 10.1.2.2, 00:20:45, GigabitEthernet0/2
[110/11] via 10.1.1.2, 00:20:45, GigabitEthernet0/1
10.0.0.0/24 is subnetted, 2 subnets
C 10.1.1.0 is directly connected, GigabitEthernet0/1
C 10.1.2.0 is directly connected, GigabitEthernet0/2
26.0.0.0/24 is subnetted, 1 subnets
C 26.1.1.0 is directly connected, GigabitEthernet0/3
Configuring Interfaces for VQE-S Traffic (Ingest and Services) and VQE-S
Services Traffic
The service provider can choose one of the following approaches when configuring the CDE interfaces:
• Dedicated Interfaces —If a VQE deployment requires that the Ethernet interfaces or bond interfaces used for VQE-S ingest traffic from upstream video sources be separate from the interfaces used for VQE-S services traffic to the downstream VQE Clients (VQE-Cs) on the set-top boxes
(STBs), the CDE Ethernet interfaces or bond interfaces must be configured as follows:
– One or more interfaces are configured as dedicated interfaces for VQE-S ingest traffic.
•
– One or more interfaces are configured as dedicated interfaces for VQE-S services traffic.
See the
Configuring Dedicated Interfaces for VQE-S Ingest Traffic and for VQE-S Services Traffic
section.
Shared Interfaces—If a VQE deployment does not require that the Ethernet interfaces or bond interfaces used for VQE-S ingest traffic be separate from the interfaces used for VQE-S services traffic, a single set of CDE Ethernet interfaces or one or more bond interfaces are configured as
VQE-S traffic interfaces that handle both types of traffic. See the
Configuring Shared Interfaces for
section.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-15
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Configuring Dedicated Interfaces for VQE-S Ingest Traffic and for VQE-S Services Traffic
On the VQE-S host, the vqe.vqes.vqe_ingest_interfaces and vqe.vqes.vqe_services_interfaces parameters in the /etc/vqes/vcdb.conf file allow you to specify the Ethernet interfaces or bond interfaces that are available, respectively, for VQE-S ingest traffic (incoming multicast streams) and for VQE-S services (Unicast Retransmission and RCC traffic). You manually edit the vcdb.conf file and specify the
Ethernet interfaces or bond interfaces that are used.
Note For information on the restrictions that apply to the vqe.vqes.vqe_ingest_interfaces and
.
eth2, bond1 (with eth3 and eth4 as its members), and the corresponding interfaces on the edge router.
Figure D-4 IP Addresses for VQE-S Configuration Examples
On the Cisco CDE that hosts VQE-S, to configure dedicated interfaces that are used for VQE-S ingest traffic and for VQE-S services traffic, follow these steps:
Step 1 If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
Note If your deployment uses one dedicated interface for a management network, be sure not to include that interface as one of the interfaces that are available for VQE-S ingest or services traffic.
For this example, assume that the implementation uses eth1 for management network traffic only.
Therefore, eth1 is not included in the set of interfaces that are available for VQE-S ingest or services traffic.
D-16
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Step 2 Edit the /etc/opt/vqes/vcdb.conf file. Add the vqe.vqes.vqe_ingest_interfaces parameter to the file and specify the required values using the following format: vqe.vqes.vqe_ingest_interfaces="ethernet-interface-name, ethernet-interface-name” or vqe.vqes.vqe_ingest_interfaces="bond-interface-name, bond-interface-name”
For example: vqe.vqes.vqe_ingest_interfaces="eth2"
Note For load balancing to work effectively, each interface to the access or distribution network must have the same capacity. Multiple bond interfaces should not be specified and a combination of Ethernet and bond interfaces cannot not be specified in this parameter.
Step 3
Step 4
Step 5
For information on manually editing the vcdb.conf file, see the
“Manually Editing the VCDB File” section on page 7-14 .
Add the vqe.vqes.vqe_services_interfaces parameter to the file and specify the required values using the following format: vqe.vqes.vqe_ingest_interfaces="ethernet-interface-name, ethernet-interface-name” or vqe.vqes.vqe_ingest_interfaces="bond-interface-name, bond-interface-name”
For example: vqe.vqes.vqe_services_interfaces="bond1"
If vqe.vqes.vqe_interfaces parameter is present in the vcdb.conf file, delete the line containing that parameter.
Save the vcdb.conf file.
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status” section on page D-28 . Reboot once when all VCDB configuration
tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
Configuring Shared Interfaces for All VQE-S Traffic
On the VQE-S host, the vqe.vqes.vqe_interfaces parameter in the /etc/vqes/vcdb.conf file allows you to specify the Ethernet interfaces or bond interfaces that are available for VQE-S traffic (ingest and services). You manually edit the vcdb.conf file and specify the Ethernet interfaces or bond interfaces that are used.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-17
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
eth2, eth3, and eth4 and the corresponding interfaces on the edge router.
Figure D-5
Cisco CDE110
IP Addresses for VQE-S Configuration Examples
CDE110 eth1
10.2.9.2
eth2
10.2.10.2
10.2.11.2
eth3
10.2.12.2
eth4
10.2.9.1
10.2.10.1
10.2.11.1
10.2.12.1
Edge router
On the Cisco CDE that hosts VQE-S, to configure shared interfaces to handle both VQE-S ingest traffic and VQE-S services traffic, follow these steps:
Step 1 If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
Note If your deployment uses one dedicated interface for a management network, be sure not to include that interface as one of the interfaces that are available for VQE-S ingest and services traffic.
For this example, assume that the implementation uses eth1 for management network traffic. Therefore, eth1 is not included in the set of interfaces that are available for VQE-S ingest and services traffic.
Step 2 Edit the /etc/opt/vqes/vcdb.conf file. Add the vqe.vqes.vqe_interfaces parameter to the file and specify the needed values using the following format: vqe.vqes.vqe_ingest_interfaces="ethernet-interface-name, ethernet-interface-name” or vqe.vqes.vqe_ingest_interfaces="bond-interface-name, bond-interface-name”
For example: vqe.vqes.vqe_interfaces="eth2,eth3,eth4"
Note For load balancing to work effectively, each interface to the access or distribution network must have the same capacity. Multiple bond interfaces should not be specified and a combination of Ethernet and bond interfaces cannot not be specified in this parameter.
Step 3
Step 4
For information on manually editing the vcdb.conf file, see the
“Manually Editing the VCDB File” section on page 7-14 .
If vqe.vqes.vqe_ingest_interfaces or vqe.vqes.vqe_services_interfaces parameter is present in the vcdb.conf file, delete the lines containing those parameters.
Save the vcdb.conf file.
D-18
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status” section on page D-28 . Reboot once when all VCDB configuration
tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
Synchronizing the Time and Configuring Network Time Protocol
To keep system time correct and synchronized, we recommend that you use Network Time
Protocol (NTP) on the VQE-S host. To synchronize the time and configure NTP, follow these steps:
Step 1
Step 2
Step 3
Step 4
If needed, log in as root.
To set the time zone, issue the tzselect command and follow the prompts:
[root@system]# /usr/bin/tzselect To set the date and time, issue the date command as follows:
date -s "date_time_string"
For example:
[root@system]# date -s "16:55:30 July 7, 2008"
Edit the /etc/opt/vqes/vcdb.conf file by adding to the file one or more system.ntp.server parameters and specifying the IP address of an external NTP server for each of the parameters. For example: system.ntp.server="10.2.26.2"
In the preceding example, the IP address of the external NTP server is 10.2.26.2.
Save the vcdb.conf file.
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status” section on page D-28 . Reboot once when all VCDB configuration
tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
For information on starting the NTP service (ntpd daemon), see the
“Starting VQE-S System Services and Verifying Status” section on page D-22
.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-19
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
VQE STUN Server Is Enabled By Default
Starting with Cisco VQE Release 3.0, the VQE STUN Server is enabled by default. The STUN Server allows STBs behind NAT devices to be supported by VQE-S. Unless you are sure that no STBs being serviced by VQE-S are behind NAT devices, we recommend that you leave the STUN Server enabled.
Configuring SNMP
The CDE that hosts the VQE-S uses Net-SNMP, a third-party product, for SNMP support for some basic, non-VQE system services. Net-SNMP offers a set of built-in MIBs for Linux platforms.
The VQE-S also provides a VQE-specific MIB and a system messages (Syslog) MIB. System messages that meet a specified severity level can be converted to SNMP traps and sent to a Network Management
System (NMS). SNMP traps for indicating changes in a channel’s state may also be generated. A channel up trap can be generated when a channel’s state changes from inactive to active, and a channel down trap can be generated when a channel’s state changes from active to inactive. Generating syslog and channel traps is optional. For more information on the SNMP MIBs on the VQE-S, see
To configure SNMP on the Cisco CDE that hosts the VQE-S, follow these steps:
Step 1
Step 2
Step 3
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
Edit the /etc/opt/vqes/vcdb.conf file by adding the following VCDB parameters and specifying the needed values for each:
• system.snmp.ro_community_string="community_string"
•
•
• system.snmp.location="server_location" system.snmp.contact="contact_person" system_snmp_trap_listener="listener_IP_or_host_name" system.snmp.syslog_trap_enable="false" •
•
• system.snmp.syslog_trap_priority="2" system.snmp.channel_trap_enable="false"
For more information on these SNMP-related VCDB parameters, see
.
The following example shows the four vcdb.conf lines that specify the SNMP parameters: system.snmp.ro_community_string="XXYYZZ" system.snmp.location="Building 6 San Francisco" system.snmp.contact="[email protected]" system_snmp_trap_listener="192.0.2.25" system.snmp.syslog_trap_enable="true" system.snmp.syslog_trap_priority="4" system.snmp.channel_trap_enable="true"
Save the vcdb.conf file.
D-20
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status
section. Reboot once when all VCDB configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
Ensuring That Only Trusted HTTPS Clients Can Communicate Using HTTPS
In your IPTV deployment, VCPT (VCPT) or another channel-provisioning server sends channel information to the VQE-Ss. You must configure each CDE that hosts the VQE-S so that only trusted
HTTPS clients (the channel-provisioning servers) can send the channel information to the CDE. If VCPT is the channel-provisioning server, the IP addresses of all Ethernet interfaces (that have been assigned
IP addresses) on the VCPT host must be configured as trusted HTTPS clients on the VQE-S host. For more information on VCPT and how it sends channel information, see the
Information” section on page 1-15
.
The system.iptables.trusted_provisioner parameter is for enhanced communications security beyond
HTTPS. The VQE-S is configured so that only trusted HTTPS clients (as specified in system.iptables.trusted_provisioner) can send it information using HTTPS.
To allow only traffic from trusted HTTPS clients on the CDE port used for HTTPS, follow these steps:
Step 1
Step 2
Step 3
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
Edit the /etc/opt/vqes/vcdb.conf file by adding to the file one or more vqe.iptables.trusted_provisioner parameters and specifying the IP address of a trusted channel-provisioning server, such as VCPT. For example: system.iptables.trusted_provisioner="10.86.17.200"
In the preceding example,
10.86.17.200
is the IP address of a trusted channel-provisioning server.
Save the vcdb.conf file.
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status
section. Reboot once when all VCDB configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-21
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Configuring Remote Syslog Servers
VQE system messages can be sent by means of UDP to remote servers for centralized logging. The use of remote syslog servers is optional. For more information on configuring remote syslog servers, see the
“Remote Syslog Hosts” section on page 2-28 .
To configure remote syslog servers on the Cisco CDE that hosts the VQE-S, follow these steps:
Step 1
Step 2
Step 3
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
Edit the /etc/opt/vqes/vcdb.conf file by adding the following VCDB parameter and specifying it’s value:
• system.syslog.remote_server="IP_address"
For more information on the remote logging VCDB parameters, see
.
The following example shows the two vcdb.conf lines that specifies the remote logging parameter: system.syslog.remote_server="192.0.7.25" system.syslog.remote_server="192.0.7.26"
Save the vcdb.conf file.
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status
section. Reboot once when all VCDB configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18
.
Starting VQE-S System Services and Verifying Status
lists the system services that you configure and start for the CDE that hosts the VQE-S. Use of the SNMP and NTP services are optional depending on your deployment requirements.
Table D-1 System Services for CDE That Hosts VQE-S
Service sshd httpd tomcat5
Description
The Secure Shell daemon.
HyperText Transfer Protocol daemon (the Apache web server).
The Apache Tomcat application server. snmpd snmpsa
(Optional) The SNMP daemon.
(Optional) The Intel SNMP subagent. vqes_snmpsa (Optional) VQE-S SNMP subagent.
syslog_snmpsa (Optional) Syslog SNMP subagent.
ntpd (Optional) The NTP daemon.
D-22
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
OL-30119-01
Table D-1 System Services for CDE That Hosts VQE-S (continued)
Service Description check_daemons A script that monitors httpd and tomcat processes and attempts to restart them if they fail. The script runs once a minute as a cron job owned by root.
If OSPF Is Enabled for VQE-S traffic or VQE-S services interfaces watchquagga The Quagga watchdog process. If a Quagga daemon crashes or hangs, watchquagga restarts it automatically.
ospfd zebra
The OSPF daemon.
The zebra daemon.
To start the VQE-S system services and verify their status, follow these steps:
Note In the following procedure, abbreviated output is shown for some commands.
Step 1
Step 2
If needed, log in as root on the CDE that hosts the VQE-S.
To configure the system services to be managed by chkconfig and started automatically at run levels 2,
3, 4, and 5, and to start the services, issue the following commands:
[root@system]# chkconfig --add sshd
[root@system]# chkconfig sshd on
[root@system]# service sshd start
[root@system]# chkconfig --add httpd
[root@system]# chkconfig httpd on
[root@system]# service httpd start
[root@system]# chkconfig --add tomcat5
[root@system]# chkconfig tomcat5 on
[root@system]# service tomcat5 start
The following commands for the Quagga routing package and OSPF are optional depending on whether these services for Quagga and OSPF are used in your deployment:
[root@system]# chkconfig --add ospfd
[root@system]# chkconfig ospfd on
[root@system]# service ospfd start
[root@system]# chkconfig --add zebra
[root@system]# chkconfig zebra on
[root@system]# service zebra start
[root@system]# chkconfig --add watchquagga
[root@system]# chkconfig watchquagga on
[root@system]# service watchquagga start
The following commands for SNMP, SNMP subagents, and NTP are optional depending on whether these services are used in your deployment:
[root@system]# chkconfig --add snmpd
[root@system]# chkconfig snmpd on
[root@system]# service snmpd start
[root@system]# chkconfig --add snmpsa
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-23
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
[root@system]# chkconfig snmpsa on
[root@system]# service snmpsa start
Step 3
Step 4
Step 5
Step 6
[root@system]# chkconfig --add vqes_snmpsa
[root@system]# chkconfig vqes_snmpsa on
[root@system]# service vqes_snmpsa start
[root@system]# chkconfig --add syslog_snmpsa
[root@system]# chkconfig syslog_snmpsa on
[root@system]# service syslog_snmpsa start
[root@system]# chkconfig --add ntpd
[root@system]# chkconfig ntpd on
[root@system]# service ntpd start
To configure the check_daemons script to run as a cron job under root, issue the following command:
[root@system]# /usr/bin/check_daemons >> /var/spool/cron/root
To verify the sshd run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep sshd sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service sshd status sshd (pid 2772) is running...
[root@system]# ps -ef | grep sshd root 2772 1 0 Jul23 ? 00:00:00 /usr/sbin/sshd
To verify the httpd run levels and that the services and process are running, issue the following commands:
[root@system]# chkconfig --list | grep httpd httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service httpd status httpd (2894) is running...
[root@system]# ps -ef | grep httpd apache 447 2894 0 Jul23 ? 00:00:00 /usr/sbin/httpd root 2894 1 0 Jul02 ? 00:00:00 /usr/sbin/httpd apache 30078 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30079 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30080 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30082 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30083 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30084 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30085 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30087 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd
To verify the tomcat5 run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep tomcat5 tomcat5 0:off 1:off 2:on 3:on 4:on 5:on 6:off
D-24
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
OL-30119-01
Step 7
Step 8
Step 9
[root@system]# service tomcat5 status
Tomcat is running...
[root@system]# ps -ef | grep tomcat5 root 19800 1 0 Jul23 ? 00:00:08 /usr/java/default/bin/java
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/usr/share/tomcat5/conf/logging.properties
-Djava.endorsed.dirs=/usr/share/tomcat5/common/endorsed -classpath
:/usr/share/tomcat5/bin/bootstrap.jar:/usr/share/tomcat5/bin/commons-logging-api.jar
-Dcatalina.base=/usr/share/tomcat5 -Dcatalina.home=/usr/share/tomcat5
-Djava.io.tmpdir=/usr/share/tomcat5/temp org.apache.catalina.startup.Bootstrap start
If you have configured OSPF and started the ospfd service, to verify the ospfd run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep ospfd ospfd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service ospfd status ospfd (pid 6173) is running...
[root@system]# ps -ef | grep ospfd quagga 6173 1 0 Sep22 ? 00:00:07 /usr/sbin/ospfd -d -A 127.0.0.1 -f
/etc/quagga/ospfd.conf
If you have configured OSPF and started the zebra service, to verify the zebra run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep zebra zebra 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service zebra status zebra (pid 6139) is running...
[root@system]# ps -ef | grep zebra quagga 6139 1 0 Sep22 ? 00:00:00 /usr/sbin/zebra -d -A 127.0.0.1 -f
/etc/quagga/zebra.conf
If you have configured OSPF and started the watchquagga service, to verify the watchquagga run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep watchquagga watchquagga 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service watchquagga status watchquagga (pid 2513) is running...
[root@system]# ps -ef | grep watchquagga root 2513 1 0 Sep15 ? 00:00:00 /usr/sbin/watchquagga -Az -d -b_
-r/sbin/service_%s_restart -s/sbin/service_%s_start -k/sbin/service_%s_stop zebra ospfd
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-25
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Step 10 If you have configured and started the SNMP service, to verify the snmpd run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep snmpd snmpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service snmpd status snmpd (pid 17654) is running...
[root@system]# ps -ef | grep snmpd root 17654 1 0 Jul25 ? 00:09:24 /usr/sbin/snmpd -Lsd -Lf /dev/null -p
/var/run/snmpd.pid -a
Step 11 If you have configured and started the SNMP Intel subagent service, to verify the snmpsa run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep snmpsa snmpsa 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service snmpsa status
The SNMP subagent is running.
[root@system]# ps -ef | grep snmpsa root 17678 1 0 Jul25 ttyS1 00:09:14 /usr/local/snmpsa/bin/smSubagent
Step 12 If you have configured and started the VQE-S SNMP subagent service, to verify the vqes_snmpsa run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep vqes_snmpsa vqes_snmpsa 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service vqes_snmpsa status vqes_subagent (pid 28603) is running...
[root@system]# ps -ef | grep vqes_snmpsa root 17878 17956 0 09:16 pts/3 00:00:00 grep vqes_snmpsa
Step 13 If you have configured and started the Syslog SNMP subagent service, to verify the syslog_snmpsa run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep syslog_snmpsa syslog_snmpsa 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service syslog_snmpsa status syslog_subagent (pid 9886) is running...
[root@system]# ps -ef | grep syslog_snmpsa root 17984 17946 0 09:16 pts/2 00:00:00 grep syslog_snmpsa
D-26
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Step 14 If you have configured and started the NTP service, to verify that the ntpd service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep ntpd ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service ntpd status ntpd (pid 17219) is running...
[root@system]# ps -ef | grep ntpd ntp 17219 1 0 Jul25 ? 00:00:06 ntpd -u ntp:ntp -p /var/run/ntpd.pid -g
Starting the VQE-S Processes and Verifying Status
To start the VQE-S service and processes and verify status, follow these steps:
Step 1
Step 2
If needed, log in as root on the CDE that hosts the VQE-S.
To configure the VQE-S service to be managed by chkconfig and started automatically at run levels 2,
3, 4, and 5, and to start the service, issue the following commands:
[root@system]# chkconfig --add vqes
[root@system]# chkconfig vqes on
[root@system]# service vqes start
Note System error messages are displayed indicating that the VQE-S processes are starting without a channel configuration file. This is normal behavior because a channel configuration file from the VCPT has not yet been sent to the VQE-S. Creating and sending the file is done when the Cisco CDE that hosts VCPT is configured, and VCPT is used to create and send the file.
Step 3
Step 4
To verify that the VQE-S service is running, issue the following command:
[root@system]# service vqes status process_monitor (pid 15189) is running...
To check that the VQE-S processes are running, issue the following commands:
[root@system]# ps -ef | grep vqe root 2965 1 0 09:17 pts/0 00:00:00 /opt/vqes/bin/process_monitor vqes 2978 2965 0 09:17 pts/0 00:00:00 stun_server --ss-uid 499 --ss-gid 499
--xmlrpc-port 8054 --dscp -1 --log-level 6 root 3007 2965 99 09:17 pts/0 09:25:31 vqes_dp --group vqes --max-channels 500
--max-outstanding-rpcs 100 --max-pkts 1000000 --log-level 6 --rtp-inactivity-tmo 300
--max-core-bw 1100000000 --reserved-core-rcv-bw 300000000 --reserved-core-er-bw 200000000
--reserved-er-bw 543200000 --max-rai-gap 15 vqes 3061 2965 7 09:17 pts/0 00:13:56 vqes_cp --cp-uid 499 --cp-gid 499
--xmlrpc-port 8051 --cfg /etc/opt/vqes/vqe_channels.cfg --er-cache-time 3000
--rtp-hold-time 20 --max-channels 500 --max-outstanding-rpcs 100 --max-queued-rpcs 1000
--max-reserved-rpcs 32000 --max-clients 32000 --exporter-enable --vqm-host 10.86.21.4
--vqm-port 8192 --reserved-er-bw 543200000 --er-pkt-tb-rate 50000 --er-pkt-tb-depth 100
--er-blp-tb-rate 10000 --er-blp-tb-depth 100 --client-er-policing
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-27
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
Step 5
--client-er-tb-rate-ratio 5 --client-er-tb-depth 10000 --log-level 6 --rcc-mode conservative --igmp-join-variability 100 --max-client-bw 0 --max-idr-penalty 0
--rap-interval 2000 --excess-bw-fraction 20 --buff-size-preroll-max 1500
--rcc-burst-delay-to-send 10 --rtp-dscp 0 --rtp-rcc-dscp -1 --rtcp-dscp 24 --overlap-loss
0 --intf-output-allocation 90 --max-rpr-stream-burst-msecs 30 --max-rpr-stream-burst-pkts
2 --unity-e-factor-interval 5 --min-client-excess-bw-fraction 0
--max-client-excess-bw-fraction
[root@system]# ps -ef | grep mlb root 2989 2965 0 09:17 pts/0 00:00:03 mlb --interface eth2,eth3,eth4
--xmlrpc-port 8052 --unicast-reservation 20 --poll-interval 1 --ssm --log-level 6
In the preceding output, the VQE-S processes to check for are as follows:
•
•
•
• process_monitor—Process Monitor stun_server—STUN Server vqes_dp—Data Plane vqes_cp—Control Plane
• mlb—Multicast Load Balancer
To use the VQE-S AMT from a web browser, enter as the URL the IP address of the Cisco CDE that hosts the VQE-S: https://ip_address_of_VQES_host
Log in using the vqe username and password. (Any valid Linux username and password can be used to log in to the VQE-S AMT.)
If you click System in the left pane, the VQE-S AMT displays information on the VQE-S processes.
shows an example.
Restarting the System and Verifying System and VQE-S Status
To restart the Cisco CDE and verify system and the VQE-S status, follow these steps:
Note The output for the commands issued in this section has been omitted. For example output, see the previous sections in this chapter where the same commands were issued.
Step 1
Step 2
If needed, log in as root on the CDE that hosts the VQE-S.
To restart the system, issue the following command:
[root@system]# reboot
The operating system boots.
Note Syslog error messages are displayed indicating that the VQE-S processes are starting without a channel configuration file. This is normal behavior because a channel configuration file from the VCPT has not yet been sent to the VQE-S. Creating and sending the file is done when the Cisco CDE that hosts VCPT is configured, and VCPT is used to create and send the file.
D-28
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE-S
OL-30119-01
Step 3
Step 4
Step 5
Step 6
Step 7
Log in as root.
To verify that interfaces eth1 to eth6 are up and running and the IP address and netmask for each are set correctly, issue the following command:
[root@system]# ifconfig -a
... Output omitted
To check that the vqes service is running, issue the following command:
[root@system]# service vqes status
... Output omitted
To check that the STUN Server process is running, issue the following command:
[root@system]# ps -ef | grep stun
... Output omitted
To verify that the sshd service is running, issue the following command:
[root@system]# service sshd status
Step 8
... Output omitted
To verify that the httpd service is running, issue the following command:
[root@system]# service httpd status
Step 9
... Output omitted
To verify that the tomcat5 service is running, issue the following command:
[root@system]# service tomcat5 status
... Output omitted
Step 10 If you have configured OSPF, to verify the ospfd service is running, issue the following command:
[root@system]# service ospfd status
... Output omitted
Step 11 If you have configured OSPF, to verify the zebra service is running, issue the following command:
[root@system]# service zebra status
... Output omitted
Step 12 If you have configured OSPF, to verify the watchquagga service is running, issue the following command:
[root@system]# service watchquagga status
... Output omitted
Step 13 If you have configured SNMP, to verify that the snmpd service is running, issue the following command:
[root@system]# service snmpd status
... Output omitted
Step 14 If you have configured SNMP, to verify that the Intel snmpsa service is running, issue the following command:
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-29
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
[root@system]# service snmpsa status
... Output omitted
Step 15 If you configured SNMP, to verify that the VQE-S subagent service is running, issue the following command:
[root@system]# service vqes_snmpsa status
... Output omitted
Step 16 If you configured SNMP, to verify that the Syslog subagent service is running, issue the following command:
[root@system]# service syslog_snmpsa status
... Output omitted
Step 17 If you have configured an external NTP server, to verify that the ntpd service is running, issue the following command:
[root@system]# service ntpd status
... Output omitted
Step 18 Do one of the following:
• If the preceding checks indicate that all is well, proceed to the
Setting Up a Cisco CDE That Hosts
• If one of the preceding checks fails, inspect the configuration of the item that failed and make any needed adjustments.
Setting Up a Cisco CDE That Hosts VQE Tools
This section explains how to perform the initial configuration tasks for a Cisco CDE hosting VQE Tools
(VCPT, VCDS, and VCDS AMT).
When performed manually, the initial configuration tasks involve editing the /etc/opt/vqes/vcdb.conf file to configure the essential VCDB parameters. The use of the vcdb.conf file simplifies the configuration tasks. Because the VQE Configuration Tool automatically applies the VCDB values to the /etc configuration files on system reboot, mistakes in configuration file syntax are unlikely.
For information on manually editing the vcdb.conf file, see the
“Manually Editing the VCDB File” section on page 7-14 .
Perform these initial configuration tasks in the order shown:
1.
4.
5.
2.
3.
Prerequisites for a Cisco CDE That Hosts VQE Tools, page D-31
Configuring the Linux Operating System for VQE Tools, page D-31
Configuring a Static Route for a Management Network (VQE Tools Host), page D-34
Synchronizing the Time and Configuring Network Time Protocol, page D-36
6.
7.
8.
Ensuring That Only Trusted HTTPS Clients Can Communicate Using HTTPS, page D-38
Configuring Remote Syslog Servers, page D-39
Starting VQE Tools System Services and Verifying Status, page D-39
D-30
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
9.
Starting the VCDS Service and Verifying VCDS, VCDS AMT and VCPT Status, page D-43
10.
Restarting the System and Verifying System, VCPT, VCDS AMT, and VCDS Status, page D-44
On the VQE Tools server, proper route configuration is needed for external access to the VQE Tools server. You can use the static route explained in the
“Configuring a Static Route for a Management
Network (VQE Tools Host)” section on page D-34 to configure this access.
Note The configuration instructions in this section are intended for new installations of Cisco VQE
Release 3.7 software, where the Cisco CDE has the Cisco VQE Release 3.7 software preinstalled.
For information on upgrading an already configured Cisco CDE, see the Release Notes for Cisco CDA
Visual Quality Experience, Release 3.7
.
Prerequisites for a Cisco CDE That Hosts VQE Tools
This section explains tasks that should be performed before setting up a Cisco CDE that hosts VQE
Tools.
Connecting Cables
For information on connecting cables on the VQE Tools server, see the
“Connecting Cables to the CDE” section on page 2-4 .
For the location of connectors on the Cisco CDE front and back panels, see the Cisco Content Delivery
Engine 110 Hardware Installation Guide.
Setting Up SSL Certificates for VCPT
It is recommended that you deploy your own or commercial Secure Sockets Layer (SSL) certificates before beginning the tasks for setting up a Cisco CDE that hosts VCPT. For information on setting up the certificates, see the
“Setting Up SSL Certificates” section on page 2-5
.
Configuring the Linux Operating System for VQE Tools
This section explains the initial Linux configuration tasks needed for a Cisco CDE appliance that runs the VQE Tools (VCPT and VCDS) software. The explanation assumes that the needed software for
Linux, VCPT, and VCDS have been preinstalled on the Cisco CDE appliance. For Red Hat Linux 5.1 documentation, go to the following : http://www.redhat.com/docs/manuals/enterprise/
For software configuration, the RJ-45 NIC (Ethernet) ports on the Cisco CDE back panel are specified as eth1 to eth6 as shown in
Note Earlier models of the CDE have four Ethernet ports (eth1 to eth4). These models did not have the Intel
PRO/1000 PT Dual Port Server Adapter that provides the eth5 and eth6 ports.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-31
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Figure D-6 NIC Port Numbering for Software Configuration eth3 eth2 eth6 eth5
3
4
2
1 eth4 eth1
For the configuration examples in this section,
Figure D-7 shows the IP addresses for interface eth1 and
the corresponding interface on the edge router.
Figure D-7
Cisco CDE110
IP Addresses for VQE Tools Configuration Examples
CDE110 eth1
10.2.15.2
eth2 eth3 eth4
10.2.15.1
Edge router
Note The configuration examples in this section assume that one CDE Ethernet interface (eth1) are used to connect to the VQE network.
To configure the Linux operating system and other software for the VQE Tools (VCPT and VCDS), follow these steps:
Step 1
Step 2
Step 3
If needed, login as root. You must have root privileges to modify the vcdb.conf file.
To create the password for the vqe username (a pre-created Linux user ID), issue the following command:
[root@system]# passwd vqe
Enter a password that follows the password guidelines:
A valid password should be a mix of upper and lower case letters, digits, and other characters. You can use an 8 character long password with characters from at least 3 of these 4 classes, or a 7 character long password containing characters from all the classes. An upper case letter that begins the password and a digit that ends it do not count towards the number of character classes used.
A passphrase should be of at least 3 words, 12 to 40 characters long and contain enough different characters.
This username and password can be used to log in to Linux directly using SSH. The vqe username and password can also be used log in to the VCPT.
To configure CDE Ethernet interfaces eth1 to eth6, edit the /etc/opt/vqes/vcdb.conf file by adding to the file one or more network.ethx.addr parameters, where ethx is eth1, eth2, and so on. Specify an IP address and prefix length for each interface. The following example shows one vcdb.conf line for the eth1
Ethernet interface:
D-32
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Step 4
Step 5
Step 6 network.eth1.addr="10.2.15.2/24"
To configure the hostname for the CDE server, edit the /etc/opt/vqes/vcdb.conf file by adding to the file the system.global.hostname parameter and specifying a hostname. The following example specifies the hostname as starfire1-iptv: system.global.hostname="starfire1-iptv"
To configure a DNS server, edit the /etc/opt/vqes/vcdb.conf file by adding the VCDB parameters for the
IP address and optionally for the search domain of a DNS server and specifying the needed values:
• system.dns.server="IP_address"
• system.dns.search_domain="search_domain"
For example: system.dns.server="192.0.20.53." system.dns.search_domain="domain.com"
Save the vcdb.conf file.
OL-30119-01
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System, VCPT, VCDS AMT, and VCDS Status section. Reboot once when all VCDB
configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
After the VQE Tools host is rebooted, you can verify that the eth1 interface is configured correctly and up and running.
• Use the ifconfig interface command to verify that the Ethernet interface is up and running and the
IP address and netmask is set correctly. The following example is for eth1:
[root@system]# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:0E:0C:C6:F3:0F
inet addr:10.2.15.2 Bcast:10.2.15.255 Mask:255.255.255.0
inet6 addr: fe80::20e:cff:fec6:f30f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:192 (192.0 b) TX bytes:2700 (2.6 KiB)
Base address:0x3000 Memory:b8800000-b8820000
• Use the ip link show eth# command (where # is the Ethernet interface number) to check that the link is up. For example:
[root@system]# ip link show eth1 eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0e:0c:c6:e4:fe brd ff:ff:ff:ff:ff:ff
• Use the ping command to check that the Cisco CDE can reach the connected edge router. For example:
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-33
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
[root@system]# ping 10.2.15.1
Configuring a Static Route for a Management Network (VQE Tools Host)
If your deployment makes use of a management network, a static route for the management network can be configured using the VCDB parameter network.route.static_route. The configuration example in this section assumes that one CDE Ethernet interface (eth1) is used to connect to the VQE network.
On the VQE Tools server, proper route configuration is needed for external access to the VQE Tools server. You can use the static route parameter to configure this access.
To configure a static route for a management network, follow these steps:
Step 1
Step 2
Step 3
Step 4
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
Edit the /etc/opt/vqes/vcdb.conf file by adding to the file a network.network.interface.mgmt_interfaces parameter and specifying the needed values using the following format: network.network.interface.mgmt_interfaces=”ethernet-interface-name, ethernet-interface-name”
The ethernet-interface-name arguments are names of the interfaces designated for management traffic.
One or more CDE Ethernet interfaces may be designated for management traffic. For this example, assume CDE Ethernet interface eth1(10.2.9.2) on the VQE Tools host is designated for management traffic.
The line in the vcdb.conf file is as follows: network.network.mgmt_interfaces=”eth1”
Edit the /etc/opt/vqes/vcdb.conf file by adding to the file a network.route.static_route parameter and specifying the needed values using the following format: network.route.static_route="target-network-subnet-addr/prefix-length via
gateway-addr:outbound-interface"
The target-network-subnet-addr/prefix-length is the IP address and prefix length for the management network. The gateway-addr is the IP address of the router interface that is directly attached to the CDE
Ethernet port that is used for management network traffic. The outbound-interface is the interface used on the VQE Tools server for this static route
For this example, assume the following:
• CDE Ethernet interface eth1 (10.2.15.2) is used for the management network.
• Management network is 192.0.0.0/8.
The line in the vcdb.conf file is as follows: network.route.static_route="192.0.0.0/8 via 10.2.15.1"
In the preceding example, 10.2.15.1 is the gateway-addr—the router interface that is directly attached to eth1.
Figure D-7 shows the IP addresses used in this example for the eth1 interface and the directly
attached router.
Save the vcdb.conf file.
D-34
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System, VCPT, VCDS AMT, and VCDS Status” section on page D-44
. Reboot once when all
VCDB configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-35
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
After the VQE Tools host is rebooted, you can verify that the static route for the management network is present in the routing table by issuing the following command:
[root@system]# ip route show
The output is similar to the following:
192.0.0.0/8 via 10.2.9.1 dev eth1
Synchronizing the Time and Configuring Network Time Protocol
To keep system time correct and synchronized, we recommend that you use Network Time
Protocol (NTP) on the VQE Tools host. To synchronize the time and configure NTP, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
If needed, log in as root on the CDE that hosts VQE Tools.
To set the time zone, issue the tzselect command and follow the prompts:
[root@system]# /usr/bin/tzselect
To set the date and time, issue the date command as follows:
date -s "date_time_string"
For example:
[root@system]# date -s "16:55:30 July 7, 2008"
Edit the /etc/opt/vqes/vcdb.conf file by adding to the file one or more system.ntp.server parameters and specifying the IP address of an external NTP server for each of the parameters. For example: system.ntp.server="10.2.26.2"
In the preceding example, the IP address of the external NTP server is 10.2.26.2.
Save the vcdb.conf file.
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System, VCPT, VCDS AMT, and VCDS Status
section. Reboot once when all VCDB configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18
.
For information on starting the NTP service (ntpd daemon), see the
Starting VQE Tools System Services and Verifying Status section.
D-36
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Configuring SNMP
The CDE that hosts the VQE Tools sever uses Net-SNMP, a third-party product, for SNMP support for some basic, non-VQE system services. Net-SNMP offers a set of built-in MIBs for Linux platforms.
The VQE Tools server also provides a VQE-specific MIB and a system messages (Syslog) MIB. System messages that meet a specified severity level can be sent as SNMP traps to a NMS. Sending syslog traps is optional. For more information on the SNMP MIBs, see
To configure SNMP on the Cisco CDE that hosts VQE Tools, follow these steps:
Step 1
Step 2
Step 3
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
Edit the /etc/opt/vqes/vcdb.conf file by adding the following VCDB parameters and specifying the needed values for each:
•
•
• system.snmp.ro_community_string="community_string" system.snmp.location="server_location" system.snmp.contact="contact_person" system_snmp_trap_listener="listener_IP_or_host_name" •
•
• system.snmp.syslog_trap_enable="false" system.snmp.syslog_trap_priority="2"
For more information on these SNMP-related VCDB parameters, see
The following example shows the four vcdb.conf lines that specify the SNMP parameters: system.snmp.ro_community_string="XXYYZZ" system.snmp.location="Building 6 San Francisco" system.snmp.contact="[email protected]" system_snmp_trap_listener="192.0.2.25" system.snmp.syslog_trap_enable="true" system.snmp.syslog_trap_priority="4"
Save the vcdb.conf file.
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System, VCPT, VCDS AMT, and VCDS Status, page D-44
section. Reboot once when all
VCDB configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-37
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Ensuring That Only Trusted HTTPS Clients Can Communicate Using HTTPS
The system.iptables.trusted_provisioner parameter must be configured for both of the following:
• For a VQE Tools host where a VCDS receives channel information from VCPT, all Ethernet
interfaces (that have been assigned IP addresses) on the VCPT host sending the channel information must be specified as addresses using the system.iptables.trusted_provisioner parameter. This requirement applies even when the VCDS is in the same VQE Tools server as the VCPT.
• For a VQE Tools host, if a VQE-C system configuration provisioning server or the vcds_send_file command sends a network configuration file to the VCDS, you specify, on the VQE Tools host, the
IP address of the trusted VQE-C system configuration provisioning server or vcds_send_file. If
vcds_send_file is used, all Ethernet interfaces (that have been assigned IP addresses) on the
vcds_send_file host have to be specified as trusted provisioning clients. This requirement applies even when the VCDS is in the same VQE Tools server as the vcds_send_file command.
The system.iptables.trusted_provisioner parameter is for HTTPS communications security. The VQE
Tools server is configured so that only trusted HTTPS clients (as specified in system.iptables.trusted_provisioner) can send it information using HTTPS.
To allow only traffic from trusted HTTPS clients on the CDE port used for HTTPS, follow these steps:
Step 1
Step 2
Step 3
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
Edit the /etc/opt/vqes/vcdb.conf file by adding to the file one or more vqe.iptables.trusted_provisioner parameters and specifying the IP addresses as explained in the preceding discussion. For example, when
VCPT send channel information to one of more VCDS’s, you specify the IP addresses of all Ethernet
interfaces that has been assigned an IP address on the VQE Tools host.
system.iptables.trusted_provisioner="10.2.15.2"
In the preceding example, 10.2.15.2
is the IP address of the only Ethernet interface that has been assigned an IP address on the VQE Tools host.
Save the vcdb.conf file.
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status
section. Reboot once when all VCDB configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18
.
D-38
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Configuring Remote Syslog Servers
VQE system messages can be sent by means of UDP to remote servers for centralized logging. The use of remote syslog servers is optional. For more information on configuring remote syslog servers, see the
“Remote Syslog Hosts” section on page 28
.
To configure remote syslog servers on the Cisco CDE that hosts VQE Tools, follow these steps:
Step 1
Step 2
Step 3
If needed, log in as root. You must have root privileges to modify the vcdb.conf file.
Edit the /etc/opt/vqes/vcdb.conf file by adding the following VCDB parameter and specifying it’s value:
• system.syslog.remote_server="IP_address"
For more information on the remote logging VCDB parameters, see
The following example shows the two vcdb.conf lines that specifies the remote logging parameter: system.syslog.remote_server="192.0.7.25" system.syslog.remote_server="192.0.7.26"
Save the vcdb.conf file.
Note VCDB configurations are applied to the CDE when it is rebooted in the
Verifying System and VQE-S Status
section. Reboot once when all VCDB configuration tasks are completed.
Alternatively, to avoid a reboot of the system, you can use the vqe_cfgtool command with the -apply option to restart only the required services. For more information on the -apply option, see the
“Using the VQE Configuration Tool Command-Line Options” section on page 7-18 .
Starting VQE Tools System Services and Verifying Status
of the SNMP and NTP services are optional depending on your deployment’s requirements.
Table D-2 System Services for CDE That Hosts VQE Tools
Service sshd httpd tomcat5
Description
The Secure Shell daemon.
HyperText Transfer Protocol daemon (the Apache web server).
The Apache Tomcat application server. snmpd vcds_snmpsa
(Optional) The SNMP daemon.
VCDS SNMP subagent syslog_snmpsa Syslog SNMP subagent.
snmpsa (Optional) The SNMP subagent.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-39
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Table D-2 System Services for CDE That Hosts VQE Tools (continued)
Service Description ntpd (Optional) The NTP daemon. check_daemons A script that monitors httpd and tomcat processes and attempts to restart them if they fail. The script runs once a minute as a cron job owned by root.
To start the VQE Tools system services and verify their status, follow these steps:
Note In the following procedure, abbreviated output is shown for some commands.
Step 1
Step 2
Step 3
Step 4
If needed, log in as root on the CDE that hosts VQE Tools.
To configure the system services to be managed by chkconfig and started automatically at run levels 2,
3, 4, and 5, and to start the services, issue the following commands:
[root@system]# chkconfig --add sshd
[root@system]# chkconfig sshd on
[root@system]# service sshd start
[root@system]# chkconfig --add httpd
[root@system]# chkconfig httpd on
[root@system]# service httpd start
[root@system]# chkconfig --add tomcat5
[root@system]# chkconfig tomcat5 on
[root@system]# service tomcat5 start
The following commands for SNMP and NTP are optional depending on whether these services are used in your deployment:
[root@system]# chkconfig --add snmpd
[root@system]# chkconfig snmpd on
[root@system]# service snmpd start
[root@system]# chkconfig --add snmpsa
[root@system]# chkconfig snmpsa on
[root@system]# service snmpsa start
[root@system]# chkconfig --add vcds_snmpsa
[root@system]# chkconfig vcds_snmpsa on
[root@system]# service vcds_snmpsa start
[root@system]# chkconfig --add syslog_snmpsa
[root@system]# chkconfig syslog_snmpsa on
[root@system]# service syslog_snmpsa start
[root@system]# chkconfig --add ntpd
[root@system]# chkconfig ntpd on
[root@system]# service ntpd start
To configure the check_daemons script to run as a cron job under root, issue the following command:
[root@system]# /usr/bin/check_daemons >> /var/spool/cron/root
To verify the sshd run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep sshd
D-40
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Step 5
Step 6
Step 7 sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service sshd status sshd (pid 2772) is running...
[root@system]# ps -ef | grep sshd root 2772 1 0 Jul23 ? 00:00:00 /usr/sbin/sshd
To verify the httpd run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep httpd httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service httpd status httpd (2894) is running...
[root@system]# ps -ef | grep httpd apache 447 2894 0 Jul23 ? 00:00:00 /usr/sbin/httpd root 2894 1 0 Jul02 ? 00:00:00 /usr/sbin/httpd apache 30078 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30079 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30080 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30082 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30083 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30084 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30085 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd apache 30087 2894 0 Jul19 ? 00:00:00 /usr/sbin/httpd
To verify the tomcat5 run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep tomcat5 tomcat5 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service tomcat5 status
Tomcat is running...
[root@system]# ps -ef | grep tomcat5 root 19800 1 0 Jul23 ? 00:00:08 /usr/java/default/bin/java
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=/usr/share/tomcat5/conf/logging.properties
-Djava.endorsed.dirs=/usr/share/tomcat5/common/endorsed -classpath
:/usr/share/tomcat5/bin/bootstrap.jar:/usr/share/tomcat5/bin/commons-logging-api.jar
-Dcatalina.base=/usr/share/tomcat5 -Dcatalina.home=/usr/share/tomcat5
-Djava.io.tmpdir=/usr/share/tomcat5/temp org.apache.catalina.startup.Bootstrap start
If you have configured and started the SNMP daemon, to verify the snmpd run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep snmpd snmpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service snmpd status
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-41
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Step 8
Step 9 snmpd (pid 17654) is running...
[root@system]# ps -ef | grep snmpd root 17654 1 0 Jul25 ? 00:09:24 /usr/sbin/snmpd -Lsd -Lf /dev/null -p
/var/run/snmpd.pid -a
If you have configured and started the Intel SNMP subagent, to verify the snmpsa run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep snmpsa snmpsa 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service snmpsa status
The SNMP subagent is running.
[root@system]# ps -ef | grep snmpsa root 17678 1 0 Jul25 ttyS1 00:09:14 /usr/local/snmpsa/bin/smSubagent
If you have configured and started the VCDS SNMP subagent, to verify the vcds_snmpsa run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep vcds_snmpsa vcds_snmpsa 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service vcds_snmpsa status vcds_subagent (pid 10088) is running...
[root@system]# ps -ef | grep vcds_snmpsa root 17273 17182 0 08:54 pts/2 00:00:00 grep vcds_snmpsa
Step 10 If you have configured and started the Syslog SNMP subagent, to verify the syslog_snmpsa run levels and that the service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep syslog_snmpsa syslog_snmpsa 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service syslog_snmpsa status syslog_subagent (pid 9886) is running...
[root@system]# ps -ef | grep syslog_snmpsa root 17984 17946 0 09:16 pts/2 00:00:00 grep syslog_snmpsa
Step 11 If you have configured and started the NTP service, to verify run levels and that the ntpd service and process are running, issue the following commands:
[root@system]# chkconfig --list | grep ntpd ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@system]# service ntpd status ntpd (pid 17219) is running...
[root@system]# ps -ef | grep ntpd
D-42
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools ntp 17219 1 0 Jul25 ? 00:00:06 ntpd -u ntp:ntp -p /var/run/ntpd.pid -g
Starting the VCDS Service and Verifying VCDS, VCDS AMT and VCPT Status
This section explains how to start the VCDS service and verify that the process is running and that VCPT and the VCDS AMT are available.
Note VCPT and VCDS AMT are web applications and have no dedicated processes associated with them. The processes needed for the VCPT and VCDS AMT web applications to work (for example, the web server) are started automatically when the Cisco CDE is started.
To start the VCDS service and verify VCDS, VCDS AMT, and VCPT status, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
If needed, log in as root on the CDE that hosts VQE Tools.
To configure the VCDS service to be managed by chkconfig and started automatically at run levels 2, 3,
4, and 5, and to start the service, issue the following commands:
[root@system]# chkconfig --add vcds
[root@system]# chkconfig vcds on
[root@system]# service vcds start
To verify that the VCDS service is running, issue the following command:
[root@system]# service vcds status
VCDServer (pid 29860) is running...
To check that the VCDS process (VCDServer) is running, issue the following command:
[root@system]# ps -ef | grep VQECCfg root 29860 1 0 Jul25 ? 00:00:00 /opt/vqes/bin/VCDServer
To verify that VCPT is accessible from a web browser, enter as the URL the IP address of the Cisco CDE that hosts VCPT: https://ip_address_of_VCPT_host
Log in using the vqe username and password. (Any valid Linux username and password can be used to log in to VCPT.)
If you are able to log in successfully, VCPT is running correctly.
To use the VCDS AMT from a web browser, enter as the URL the IP address of the Cisco CDE that hosts
VQE Tools server https://ip_address_of_VQE_Tools_host/vcds-amt
Log in using the vqe username and password. (Any valid Linux username and password can be used to log in to the VCDS AMT.)
If you are able to log in successfully, VCDS AMT is running correctly.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-43
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Restarting the System and Verifying System, VCPT, VCDS AMT, and VCDS
Status
To restart the Cisco CDE and verify system, VCPT, VCDS (VCDS), and VCDS AMT status, follow these steps:
Note The output for the commands issued in this section has been omitted. For example output, see the previous sections in this chapter where the same commands were issued.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
If needed, log in as root on the CDE that hosts VQE Tools.
To restart the system, issue the following command:
[root@system]# reboot
The operating system boots.
To verify that interface eth1 is up and running and the IP address and netmask is set correctly, issue the following command:
[root@system]# ifconfig -a
... Output omitted
To verify that the sshd service is running, issue the following command:
[root@system]# service sshd status
... Output omitted
To verify that the httpd service is running, issue the following command:
[root@system]# service httpd status
... Output omitted
To verify that the tomcat5 service is running, issue the following command:
[root@system]# service tomcat5 status
... Output omitted
If you have configured SNMP, to verify that the snmpd service is running, issue the following command:
[root@system]# service snmpd status
... Output omitted
If you have configured SNMP, to verify that the Intel snmpsa service is running, issue the following command:
[root@system]# service snmpsa status
... Output omitted
If you configured SNMP, to verify that the VCDS subagent service is running, issue the following command:
[root@system]# service vcds_snmpsa status
... Output omitted
D-44
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix D Manual Initial VQE System Configuration
Setting Up a Cisco CDE That Hosts VQE Tools
Step 10 If you configured SNMP, to verify that the Syslog subagent service is running, issue the following command:
[root@system]# service syslog_snmpsa status
... Output omitted
Step 11 If you have configured an external NTP server, to verify that the ntpd service is running, issue the following command:
[root@system]# service ntpd status
... Output omitted
Step 12 To check that the vcds service is running, issue the following command:
[root@system]# service vcds status
... Output omitted
Step 13 To verify that VCPT is accessible from a web browser, enter as the URL the IP address of the Cisco CDE that hosts VCPT: https://ip_address_of_VQE_Tools_host
Step 14
Log in with a Linux username and password.
If you are able to log in successfully, VCPT is running correctly.
To that VCDS AMT from a web browser, enter as the URL the IP address of the Cisco CDE that hosts
VQE Tools server https://ip_address_of_VQE_Tools_host/vcds-amt
Step 15
Log in using the vqe username and password. (Any valid Linux username and password can be used to log in to the VCDS AMT.)
If you are able to log in successfully, VCDS AMT is running correctly.
Do one of the following:
• If the preceding checks indicate that all is well, you are ready to start using VCPT and VCDS AMT.
For information on VCPT, see
Chapter 3, “Using the VQE Channel Provisioning Tool.”
For information on VCDS AMT, see
Chapter 5, “Using the VCDS AMT.”
• If one of the preceding checks fails, inspect the configuration of the item that failed and make any needed adjustments.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
D-45
Setting Up a Cisco CDE That Hosts VQE Tools
Appendix D Manual Initial VQE System Configuration
D-46
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
OL-30119-01
A P P E N D I X
E
Configuring DHCP and DNS Servers for VCDS
The VQE configuration delivery infrastructure (CDI) is used to deliver a channel configuration file and per-client network configuration file to the VQE Clients (VQE-Cs) in a VQE system. The VQE Client
Configuration Delivery Server (VCDS) or a Real Time Streaming Protocol (RTSP) server sends the channel configuration file and network configuration file to the VQE-Cs on the set-top boxes (STBs).
This appendix provides information on configuring the Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) servers so that they work correctly with the VCDS or with an RTSP server compatible with the VQE CDI. This appendix assumes you have knowledge of DHCP and DNS configuration.
Note The VQE-C parameter cdi_enable must be set to TRUE to enable a VQE-C to use the configuration delivery infrastructure. For information on the VQE-C system configuration parameters, see the Cisco
CDA Visual Quality Experience Client System Configuration Guide listed in the
Documentation” section on page XV
.
The components and interactions of the VQE CDI are shown in
Figure E-1 . In this example, the VCDS
sends the channel configuration file to the VQE-C. The example provides guidance on the following
VQE requirements for the DHCP and DNS server configuration.
•
•
For a domain search request, the DHCP server must be configured to provide the domain of the
VCDS to the VQE-C.
For a DNS service request, the DNS server must be configured to return the hostname of one or more of the VCDS interfaces to VQE-C when the service lookup is for _vqe_channel_cfg._tcp (exact
string required) with the VCDS domain name appended, as in
_vqe_channel_cfg._tcp.<VCDS_domain_name>.
Caution The _vqe_channel_cfg._tcp part of the string is hardcoded in the VQE-C and is not configurable. The
DNS server must be configured for this exact string (_vqe_channel_cfg._tcp) with the domain name appended.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
E-1
Appendix E Configuring DHCP and DNS Servers for VCDS
Figure E-1
VQE-Client
VQE Configuration Delivery Infrastructure
DHCP Server DNS Server VCDS
DHCP domain search
“iptv.myvqec.com”
SRV lookup for “_vqe_channel_cfg._tcp.iptv.myvqec.com”
“vqe-channel-cfg-server.iptv.myvqec.com”
DESCRIBE rtsp://vqe-channel-cfg-server.iptv.myvqec.com/channel-config RTSP/1.0”
RTSP/1.0 200 OK with SDP descriptions for the entire channel set
As shown in Figure E-1 , the interactions between the VQE-C and the other components of the
configuration delivery infrastructure are as follows:
1.
2.
The VQE-C on the STB sends out a DHCP domain search request.
The DHCP server returns the domain (in this example, iptv.myvqec.com) to which the VCDS belongs. The domain is user-defined and configured in the DHCP server.
3.
4.
5.
After receiving the domain name from the DHCP server, the VQE-C makes a DNS service request for the following string:
_vqe_channel_cfg._tcp.iptv.myvqec.com
The DNS server responds with the hostname of each of the VCDS server interfaces defined in the
SRV records in the DNS. In addition, the response may include the IP address of each VCDS server interfaces. If the IP addresses are not returned, the VQE-C initiates a separate request for them.
If the DNS query is successful, the VQE-C parses out the VCDS IP addresses from the DNS server response. If multiple interfaces are returned in the DNS response, the VQE-C randomizes the list of
VCDS IP addresses returned by the DNS. The VQE-C sends out an RTSP DESCRIBE request for channel configuration data to the first VCDS interface on the list. The VQE-C waits 5 seconds for a response before it tries to connect to the next VCDS interface in the list. If the VQE-C tries all listed interfaces and no response is received, the RTSP DESCRIBE operation has failed.
Note The TCP implementation determines how many SYN packets are sent to the VCDS interface within the 5–second timeout interval.
6.
If the RTSP DESCRIBE operation is successful, the VCDS sends back to the VQE-C the channel configuration data for the entire channel set in Session Description Protocol (SDP) format.
The VQE-C attempts to update the local channel_lineup file. During VQE-C initialization, if either the
DNS query or the RTSP DESCRIBE operation fails, the VQE-C attempts to retrieve the channel configuration locally if a channel_lineup file is specified in the VQE-C system configuration file. If the appropriate channel configuration cannot be obtained, the VQE-C does not perform error repair. After the VQE-C has initialized, if either the DNS query or the RTSP DESCRIBE operation fails, the channel configuration is not updated.
E-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
A P P E N D I X
F
Using the vcds_send_file Command
This appendix provides overview information on network-based per-client configuration of the VQE
Client (VQE-C). It also explains how to use the vcds_send_file command to send the client database file and group attribute file to one or more VQE Client Configuration Delivery Servers (VCDSs).
VQE CDI and VQE-C Network-based Per-Client Configuration
The VQE configuration delivery infrastructure (CDI) is used to deliver a channel configuration file and per-client network configuration file to the VQE-Cs on the set-top boxes (STBs). With the CDI, a VCDS or an RTSP server sends these two files to the VQE-Cs.
To create the network configuration files for the VQE-Cs, VCDS requires the following files:
•
•
Client database file—In this file, each STB VQE-C has a unique identity (for example, MAC address) that is associated with a group identifier (group ID) for the specific network configuration that should be applied to the VQE-C system. Each VQE-C is associated with one group ID. The client database file can be a complete set of all STBs or a subset which adds to or modifies a previous set that exists on the VCDS.
Group attribute file—In this file, different sets of per-client network configurations are defined.
Each set of attributes is identified by a group ID.
The client database file and the group attribute file are XML-based and follow a schema specified by a specification defined by Cisco.
• Schema for the client database file is located at
/usr/share/tomcat5/webapps/vcds-amt/WEB-INF/db_schema.xsd. The example file
/etc/opt/vqes/groupmap_sample.xml contains an example of how to do group mapping.
• Schema for the group attribute file is located at
/usr/share/tomcat5/webapps/vcds-amt/WEB-INF/grp_cfg_schema.xsd. The example file
/etc/opt/vqes/clientcfg_sample.xml contains an example with all VQE-C attributes that are allowed.
Note The example client database and group attribute files are not preserved during an upgrade of the VQE-S.
Any changes made to either file are lost.
A VQE-C system configuration provisioning server or the vcds_send_file command is used to send the client database file and the group attribute file to one or more VCDS servers. The vcds_send_file command is included with the VQE Tools software.
For more information on the roles VCDS and the VQE-C system configuration provisioning server, see the
“VCDS Delivery of the Per-Client Network Configuration File” section on page 18 .
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 F-1
Appendix F Using the vcds_send_file Command
The vcds_send_file Command
The vcds_send_file Command
The vcds_send_file command can be used to send the client database file and the group attribute file to a VCDS.
The syntax for the vcds_send_file command is as follows:
vcds_send_file type hostname filename
Syntax Description type hostname
filename
Specifies the type of file that is sent to the VCDS. The following values are allowed:
• VQE-GROUPMAP—Client database file
• VQE-GROUPATTR—Group attribute file
Specifies the hostname or IP address of the VCDS to which the file is sent.
If the VCDS to which the file is sent resides on the same VQE Tools server as the sending vcds_send_file command, localhost can be used for
hostname.
Specifies the full pathname of the file that is sent to the VCDS. The file contents (a client database file or a group attribute file) must match the value given in the type argument.
Usage Guidelines The vcds_send_file command sends the client database file and the group attribute file to the VCDS using HTTPS. The VCDS to which the files are sent can be located on the same VQE Tools server where the vcds_send_file command is issued or can be located on a different VQE Tools server. On the VQE
Tools server, the vcds_send_file executable is located at /opt/vqes/bin/vcds_send_file.
Note You must log in as root to execute the vcds_send_file command.
To have the operating system find the vcds_send_file executable, you must set the PATH environment variable to include the location of the /opt/vqes/bin directory, or use the full path to vcds_send_file when executing the command.
Examples
F-2
The following examples show how to use the vcds_send_file command to send a client database file and a group attribute file.
[root@system ~]# /opt/vqes/bin/vcds_send_file VQE-GROUPMAP localhost
/etc/opt/vqes/groupmap_sample.xml
Status Code: 200
Status Message: Succeeded -- Received a new group map file for VQE-C
[root@system ~]# /opt/vqes/bin/vcds_send_file VQE-GROUPATTR localhost
/etc/opt/vqes/clientcfg_sample.xml
Status Code: 200
Status Message: Succeeded -- Received a new attribute file for VQE-C
[root@system ~]#
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
A P P E N D I X
G
Changing the Boot Sequence to Start from the
CD/DVD Drive
This appendix explains how to change the BIOS setting on the Cisco CDE server so that the server boots first from the CD/DVD Combo drive.
For VQE Server (VQE-S) and VQE Tools hosts, the CD for an ISO installation of VQE software works correctly only when the BIOS of the Cisco CDE server is configured so that the server boots first from the CD/DVD Combo drive.
Note A Cisco CDE server with Cisco VQE Release 3.0 or later software preinstalled is configured at the factory so that the server boots first from the CD/DVD Combo drive. Therefore, unless someone has changed the BIOS setting for boot sequence or the CDE server was delivered with software earlier than
Cisco VQE Release 3.0, changing the boot sequence should not be needed.
For information on installing VQE software, see the release notes for your version of the VQE software.
If your CDE server is set up so that it boots from something other than the CD/DVD Combo drive, to change the BIOS setting so that the server boots first from the CD/DVD Combo drive, do the following:
Step 1
Step 2
Power on or power cycle the CDE.
When the system boots and displays “Press <F2> to enter SETUP,” press F2 to go enter BIOS Setup.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
G-1
Appendix G Changing the Boot Sequence to Start from the CD/DVD Drive
Step 3 When the BIOS Setup utility is displayed, use the arrow keys to move to the Boot Options menu (
).
Figure G-1 Boot Options Menu
Step 4 So that the CD/DVD Combo drive is first in the boot order, you need to change the boot sequence to the following:
1.
2.
3.
4.
IDE PM: SlimType COMBO SSC-2485
#0440 ID01 LUN0 FUJITSU MAY203
IBA GE Slot 0600
[EFI SHELL]
Note Because the components used in the CDE can vary, the name of the CD/DVD Combo drive may be different from what is shown in the preceding list.
Step 5
Step 6
To change the boot sequence, use the arrow keys to move to the boot option you change (for example,
Boot Option #1) and press Enter. Then use the arrow keys to move to the required boot device and press
Enter.
The updated Boot Option is displayed.
To save and exit the BIOS Setup, press F10. (As an alternative to pressing F10, use the arrow keys to move to Exit in the BIOS Setup menu and select Save Changes and Exit.)
The Setup Confirmation message “Save Configuration Changes and exit now?” is displayed.
Select Yes and press Enter.
The CDE restarts.
G-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
A P P E N D I X
H
VQE Server Performance and Scaling Limits
This appendix summarizes performance information of the Cisco CDE110, CDE111 and CDE250 platforms hosting the Cisco VQE Server (VQE-S), and provides information on how to access VQE-S capacity statistics. The information is for general deployment estimates only and may vary according to network designs.
Ingress and Egress Bandwidth Limits
Table H-1 presents ingress and egress bandwidth limits for all Cisco VQE releases of the CDE110
platform hosting the VQE-S.
Table H-1 Ingress and Egress Bandwidth Limits of the CDE110 Platform hosting the VQE-S
Version
Cisco VQE Release 2.1
Cisco VQE Release 3.0
Cisco VQE Release 3.1
Cisco VQE Release 3.2
Cisco VQE Release 3.3
Cisco VQE Release 3.4
Cisco VQE Release 3.5
Cisco VQE Release 3.6
Ingress Maximum
Bandwidth (Gbps)
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
Egress Maximum
Bandwidth (Gbps)
1.0
1.5
2.0
2.0
2.0
2.0
2.0
2.0
Combined Egress and
Ingress Maximum
Bandwidth (Gbps)
2.0
2.5
3.0
3.0
3.0
3.0
3.0
3.0
Table H-2 presents ingress and egress bandwidth limits for all VQE releases of the CDE111 platform
hosting the VQE-S.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
H-1 OL-30119-01
Appendix H VQE Server Performance and Scaling Limits
Scaling and Performance Summary
Table H-2 Ingress and Egress Bandwidth Limits of the CDE111 Platform hosting the VQE-S
Version
Cisco VQE Release 3.2
Cisco VQE Release 3.3
Cisco VQE Release 3.4
Cisco VQE Release 3.5
Cisco VQE Release 3.6
Ingress Maximum
Bandwidth (Gbps)
1.0
1.0
2.0
2.0
2.0
Egress Maximum
Bandwidth (Gbps)
3.0
3.0
3.0
3.0
3.0
Combined Egress and
Ingress Maximum
Bandwidth (Gbps)
4.0
4.0
4.0
4.0
4.0
, in Cisco VQE Release 3.4 and later releases, the maximum ingress bandwidth on the CDE111 platform hosting the VQE-S is up to 2 Gbps, and the maximum egress bandwidth is up to 3 Gbps. The combination of ingress and egress bandwidth cannot exceed 4 Gbps. For example, if 1
Gbps of ingress bandwidth is used, up to 3 Gbps of egress bandwidth may be used. Similarly, if 2 Gbps of ingress bandwidth are used, up to 2 Gbps of egress bandwidth may be used.
presents ingress and egress bandwidth limits for all Cisco VQE releases of the CDE250 platform hosting the VQE-S.
Table H-3 Ingress and Egress Bandwidth Limits of the CDE250 Platform hosting the VQE-S
Version
Cisco VQE Release 3.6
Ingress Maximum
Bandwidth (Gbps)
3.0
Cisco VQE Release 3.7
4.0 ( 5.0 if possible)
Egress Maximum
Bandwidth (Gbps)
9.0
9.0
Combined Egress and
Ingress Maximum
Bandwidth (Gbps)
12.0
13.0 (14.0 if possible)
Note In Cisco VQE Release 3.7, since the system always allocates the bandwidth for the ingest first and utilizes all the bandwidth for the channel lineup, the input channel lineup aggregate bandwidth should not exceed the 4Gbps limit as it may affect the bandwidth required for the RCC request from the STB clients.
Scaling and Performance Summary
presents scaling and performance summary for all releases of the CDE110 and CDE111 platforms hosting the VQE-S.
Table H-4 Scaling and Performance Summary of the CDE110 and CDE111 Platforms hosting the
VQE-S across all Releases
Scale Factor
Maximum number of Unicast Retransmission
Repair Requests (NACKs) input per second.
Maximum Value across all Cisco VQE Releases
10,000 bitmaps resulting in a maximum of 50,000
RTP
1
packets
H-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix H VQE Server Performance and Scaling Limits
Scaling and Performance Summary
Table H-4 Scaling and Performance Summary of the CDE110 and CDE111 Platforms hosting the
VQE-S across all Releases (continued)
Maximum Unicast Retransmission Rate—packets output per second.
Maximum Number of Ingest Channels—This is subject to an additional constraint of platform ingest limits.
Maximum Number of Simultaneous Client
Subscribers—Subscriber is defined as a consumer of video channel data. For a STB
2
with multiple tuners (such as a watch one, record one capable
STB), the VQE-S counts this as 2 subscribers.
50,000
500 channels or the maximum ingest bandwidth in
Gbps, whichever limit is reached first.
32,000
1.
RTP = Real-time Transport Protocol.
2.
STB = set-top box.
Table H-5 presents scaling and performance summary for all releases of the CDE250 platforms hosting
the VQE-S.
Table H-5 Scaling and Performance Summary of the CDE250 Platforms hosting the VQE-S across all Releases
Scale Factor
Maximum number of Unicast Retransmission
Repair Requests (NACKs) input per second.
Maximum Value across all Cisco VQE Releases
30,000 bitmaps resulting in a maximum of
150,000 RTP
1
packets
150,000 Maximum Unicast Retransmission Rate—packets output per second.
Maximum Number of Ingest Channels—This is subject to an additional constraint of platform ingest limits.
Maximum Number of Simultaneous Client
Subscribers—Subscriber is defined as a consumer of video channel data. For a STB
2
with multiple tuners (such as a watch one, record one capable
STB), the VQE-S counts this as 2 subscribers.
1,000 channels or the maximum ingest bandwidth in Gbps, whichever limit is reached first.
128,000
Server Cache Depth, the caching time of input multicast streams to service the RCC request from the STB clients
In Release 3.7, this value has been increased from
5 secs to 10 secs
1.
RTP = Real-time Transport Protocol.
2.
STB = set-top box.
The VQE-S separates the bandwidth resources that are dedicated to Unicast Retransmission and Rapid
Channel Change (RCC). A VQE-S configuration parameter (vqe.vqes.reserved_er_bw) controls the bandwidth resources that are dedicated to Unicast Retransmission. The parameter allows the amount of resources dedicated to Unicast Retransmission to be reduced so that the resources are available for RCC instead. For information on this parameter, see
of Appendix A, “VQE, System and Network Parameters.”
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
H-3
Appendix H VQE Server Performance and Scaling Limits
VQE-S Capacity Statistics
Note VQE licenses for Unicast Retransmission and RCC are sold separately per STB. Software licenses for
Unicast Retransmission and RCC are sold separately from the hardware.
Note Each scaling limit is applied separately and all scaling limits must be met for proper service. Exceeding any of the scaling limits causes service to be denied.
VQE-S Capacity Statistics
The VQE-S Application Monitoring Tool (AMT) displays several counters and statistics under Capacity
Statistics on the Statistics tab of the Error Repair and RCC Configuration window which together indicate whether the Unicast Retransmission, RCC, or client subscriber capacity limits, presented in the
Scaling and Performance Summary
section, have been exceeded. For information on the capacity
statistics, see the “Viewing Error Repair and RCC Configuration” section on page 4-16 .
Note The capacity statistics indicate when VQE services have been refused due to a capacity limit being reached. The capacity statistics provide no advanced warning of capacity limits being reached, nor do they provide an indication of when additional server capacity is required.
H-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
VCPT Configuration Files
A P P E N D I X
I
This appendix describes the VQE Channel Provisioning Tool (VCPT) import and export configuration file formats, and provides examples of both formats. This appendix contains the following sections:
•
•
•
•
VCPT Configuration File Data Rules, page I-2
VCPT Configuration in XML Format, page I-8
VCPT Configuration in CSV Format, page I-21
Introduction
The VCPT is an optional channel-provisioning utility that assists with creating channel lineups required by both the VQE Server (VQE-S) and the VQE Client (VQE-C). A VCPT configuration contains a set of channel definitions, server definitions, and channel-server associations. The data can be entered directly using the VCPT GUI, or it can be imported from an external file. For more information on importing a configuration file, see the
“Importing a Configuration” section on page 3-4
. The VCPT also provides an option to export a configuration to a file. For more information on exporting a configuration
file, see the “Exporting a Configuration” section on page 3-5
.
The VCPT supports two configuration formats; extensible markup language (XML) and text-based, comma-separated values (CSV). A file in XML format must reference the XML schema file, vcpt_doc.xsd, which resides in the directory /usr/share/tomcat5/webapps/vcpt/WEB-INF on the VQE
Tools server. The schema file constrains the set of elements that may be used in the configuration file and the order in which elements appear. It defines which attributes are applied to each elements, and describes parent/child relationships. When the VCPT loads a configuration file in XML format, it checks the configuration file against the file vcpt_doc.xsd for validity. A file in CSV format is made up of lines of ASCII text with values separated by commas. The benefit of using the CSV format is its simplicity.
You can create a file in CSV format using any text editor.
The VCPT configuration file provides the following information for each channel in the channel lineup:
• Channel Identification
•
•
•
•
•
Original Stream Configuration
Unicast Retransmission Stream Configuration
FEC 1 Stream Configuration
FEC 2 Stream Configuration
Enabling Channel Features Options
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-1
Appendix I VCPT Configuration Files
VCPT Configuration File Data Rules
The VCPT configuration file provides the following information for each server in the channel lineup:
•
•
•
•
•
•
•
Server name
Unique identifier for the server
Server role (such as VQE-S or VCDS)
Server IP address
Real-Time Transport Control Protocol (RTCP) Interval
Maximum Receivers
Channels assigned to the server
VCPT Configuration File Data Rules
below details the channel and server information included in both formats of the channel configuration file. The table presents the data type of each field and lists the rules associated with field.
I-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration File Data Rules
Table I-1 Data Rules for Channel and Server Fields
In Format Data Type Data Field
Channel Information
Leading Label
Channel Identifier
Channel Data
Rule
CSV only String In Cisco VQE Release 3.5.4 and earlier releases the following data rules apply:
•
•
•
Each row representing a VQE-S or VCDS server must use SERVER as its label.
Each row representing a remote server must use SCP
1
as its label.
Each row representing a channel must use CHANNEL as its label.
Starting with Cisco VQE Release 3.5.5 the following data rules apply:
• Each row representing a VQE-S or VCDS server must use SERVER as its label.
•
•
Each row representing a remote server must use SCP as its label.
Each row representing a channel must use one of the following three labels:
XML and CSV String
XML only
–
–
ER_CHANNEL—Channel data does not include
FEC
2
services.
FEC_CHANNEL—Channel data includes FEC services.
– CHANNEL—Provided for backward compatibility with Cisco VQE Release 3.5.4 and earlier releases.
The following data rule is common to all VQE 3.5 and later releases:
• Only one label should be provided for each channel.
The following data rules apply:
•
•
Unique identifier for the channel.
Range is from 1 to 20 alphanumeric characters.
•
•
Valid values include lowercase letters a to z, uppercase letters A to Z, and numeric characters from 0 to 9.
No duplicate channel entries are allowed in the configuration file.
attributeGroup The following data rules apply:
•
•
•
Set of attributes representing a channel.
Set of attributes includes id only.
Minimum number of channelData elements in an XML file is 0.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-3
Appendix I VCPT Configuration Files
VCPT Configuration File Data Rules
Table I-1
Data Field
Channel Name
Original Source Stream
Multicast IP address
Original Source Stream
RTP
3
Data Rules for Channel and Server Fields (continued)
Port Number
Original Source Stream
RTCP Port Number
Original Source Stream
Source Filter IP Address
In Format Data Type
XML and CSV String
XML and CSV IP address
XML and CSV Integer
XML and CSV Integer
XML and CSV IP address
Rule
The following data rules apply:
•
•
Range is from 1 to 40 alphanumeric characters.
Valid values include lowercase letters a to z, uppercase letters A to Z, and numeric characters 0 to 9.
• No spaces are allowed.
The following data rules apply:
• Multicast IP address must be unique for each channel.
That is, the address cannot be used by another channel as its Original Stream Multicast IP address.
• Range is from 224.0.0.0 to 239.255.255.255.
The following data rules apply:
• RTP port number of the original source stream of the channel cannot be the same as the RTCP port number of the original source stream of the channel.
• Range is from 1024 to 65535.
The following data rules apply:
•
•
RTP port number of the original source stream of the channel cannot be the same as the RTCP port number of the original source stream of the channel.
• Range is from 1024 to 65535.
The following data rules apply:
Unicast IP address.
•
•
Source filter IP address must not be equal to the
Feedback Target IP address.
Range is from 0.0.0.0 to 223.255.255.255.
Note A channel may be defined with a source IP address of 0.0.0.0 for the Original Stream. When the channel
Source IP address is 0.0.0.0 for the original stream, the SDP entry for this channel does not include the source-filter line in the original stream section that would be used to perform a SSM
4
join. In this case, the VQE-S and VQE-C does not perform an SSM join.
I-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration File Data Rules
Table I-1 Data Rules for Channel and Server Fields (continued)
Data Field In Format Data Type
Original Source Stream Bit
Rate
XML and CSV Integer
Rule
The following data rules apply:
•
•
Bit rate of the original source stream of the channel in kilobits per second.
Range is from 1000 to 30000.
• Specified bit rate should be equal to the primary stream bandwidth but should not include bandwidth used for
FEC.
Valid values are true and false.
Enable Unicast
Retransmission
Enable Rapid Channel
Change
XML and CSV Boolean
XML and CSV Boolean
Enable RTCP Extended
Reports
XML and CSV Boolean
Enable Reduced-size RTCP XML and CSV Boolean
Valid values are true and false.
Valid values are true and false.
Feedback Target Address
Unicast Retransmission
RTP Port
Unicast Retransmission
RTCP Port
FEC 1 Multicast Address
XML and CSV IP address
XML and CSV Integer
XML and CSV Integer
XML and CSV IP address
Valid values are true and false. This field was introduced in
Cisco VQE Release 3.5.5.
The following data rules apply:
• Unique anycast IP address on the VQE-S that provide services for this channel.
•
•
Feedback Target unicast IP address must be unique for each channel.
• Range is from 0.0.0.0 to 223.255.255.255.
The following data rules apply:
RTP port number of the Unicast Retransmission source stream of the channel cannot be the same as the RTCP port number of the Unicast Retransmission source stream of the channel.
• Range is from 1024 to 65535.
The following data rules apply:
• RTP port number of the Unicast Retransmission source stream of the channel cannot be the same as the RTCP port number of the Unicast Retransmission source stream of the channel.
• Range is from 1024 to 65535.
The following data rules apply:
•
•
Multicast IP address.
Range is from 224.0.0.0 to 239.255.255.255.
•
•
Configuring an FEC 1 Stream or an FEC 2 Stream provides 1-dimension FEC for the channel.
Configuring an FEC 1 Stream and an FEC 2 Stream provides 2-dimension FEC for the channel.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-5
Appendix I VCPT Configuration Files
VCPT Configuration File Data Rules
Table I-1
Data Field
FEC 1 RTP Port
FEC 1 Source Filter
Address
FEC 2 Source Filter IP address
Data Rules for Channel and Server Fields (continued)
FEC 2 Multicast Address
FEC 2 RTP Port
In Format Data Type
XML and CSV Integer
XML and CSV IP address
XML and CSV IP address
XML and CSV Integer
XML and CSV IP address
Rule
The following data rules apply:
•
•
Range is from 1024 to 65535.
RTP port number of the FEC 1 stream of the channel cannot be the same as the RTCP port number of the FEC
1 stream of the channel.
The following data rules apply:
•
•
Unicast IP address.
Range is from 0.0.0.0 to 223.255.255.255.
The following data rules apply:
• Multicast IP address.
•
•
Range is from 224.0.0.0 to 239.255.255.255.
Configuring an FEC 1 Stream or an FEC 2 Stream provides 1-dimension FEC for the channel.
• Configuring an FEC 1 Stream and an FEC 2 Stream provides 2-dimension FEC for the channel.
The following data rules apply:
• Port number specified for an FEC 2 stream cannot be the same as the port number used for the RTP or RTCP port for the Original Stream.
•
•
RTP port number of the FEC 2 stream of the channel cannot be the same as the RTCP port number of the FEC
2 stream of the channel.
• Range is from 1024 to 65535.
The following data rules apply:
Unicast IP address.
• Range is from 0.0.0.0 to 223.255.255.255.
VQE-S Data
Server Name
Server Identifier
Server Data
XML and CSV String The following data rules apply:
•
•
Range is from 1 to 40 characters.
No spaces are allowed.
The following data rules apply: XML and CSV String
XML only
•
•
Unique identifier for the server.
Range is from 1 to 20 alphanumeric characters.
attributeGroup The following data rules apply:
• Set of attributes representing a server.
• Set of attributes includes id only.
I-6
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration File Data Rules
Table I-1
Data Field
Server Management IP
Address
Server Role
Data Rules for Channel and Server Fields (continued)
Remote Server Port
Remote Server Username
Remote Server Location
VQE-S and Channels
Association
RTCP Interval
In Format Data Type
XML and CSV IP address.
XML and CSV Enumeration
XML and CSV Integer
XML and CSV String
XML and CSV String
XML only Array
XML and CSV Integer
Rule
The following data rules apply:
• IP address of an Ethernet interface on the Cisco CDE server or Management IP address of an Ethernet interface on the remote server.
• Unicast IP address.
The following data rules apply:
•
•
Role of the Cisco CDE server.
Valid values are:
–
–
VQE-S
VCDS
– SCP
The following data rules apply:
•
•
SCP port number on the remote server.
Range is from 1 to 65535.
The following data rules apply:
• Username of the person authorized to access the path on the remote server.
• Range is from 1 to 40 characters.
Remote path and filename for SCP operation.
Array of channels associated with the server.
Maximum Receivers
Channel Identifiers
XML and CSV Integer
CSV only String
The following data rules apply:
•
•
Defines how often VQE-Cs send an RTCP report.
Range is from 5 to 800.
The following data rules apply:
•
•
Maximum number of receivers per server.
Range is from 1 to 128,000.
Channel Identifiers for each channel associated with the server.
1.
SCP = Secure Copy Protocol.
2.
FEC = Forward Error Correction.
3.
RTP = Real-time Transport Protocol.
4.
SSM = source specific multicast
When you import an external VCPT configuration file in either CSV or XML format, the only mandatory fields are Channel Identifier and Server Identifier. You can fill in all other fields using the VCPT GUI.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-7
Appendix I VCPT Configuration Files
VCPT Configuration in XML Format
VCPT Configuration in XML Format
A configuration file in XML format may be used to import configuration data into the VCPT or to export configuration data from the VCPT for modification or backup.
XML Schema
On the VQE Tools server, the full path name of the XML schema file associated with the VCPT configuration file is /usr/share/tomcat5/webapps/vcpt/WEB-INF/vcpt_doc.xsd. The following is the
XML schema defined in the file vcpt_doc.xsd:
<xs:schema xmlns:vqe="http://www.cisco.com/vqe/vcpt1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.cisco.com/vqe/vcpt1.0"
version="1.0.0"
elementFormDefault="qualified">
<xs:element name="VcptFile" type="vqe:VcptFileType">
</xs:element>
<xs:complexType name="VcptFileType">
<xs:sequence>
<xs:element ref="vqe:channelData" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="vqe:serverData" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="version" type="xs:string" use="required"/>
</xs:complexType>
<!-- ************************ -->
<!-- VQE basic types -->
<!-- ************************ -->
<xs:simpleType name="vqeStringType">
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="40"/>
<xs:whiteSpace value="preserve"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="vqeIdType">
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="20"/>
<xs:pattern value="[0-9a-zA-Z]+"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="vqePortType">
<xs:restriction base="xs:positiveInteger">
<xs:minInclusive value="1024"/>
<xs:maxInclusive value="65535"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="vqeBooleanType">
<xs:restriction base="xs:boolean"/>
</xs:simpleType>
<xs:simpleType name="vqeMulticastAddrType">
<xs:restriction base="xs:string">
<xs:pattern value="(22[4-9]|23[0-9])\.(([1-9]?[0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){2}([1-9]?[0-9]|1[0-9][0-9]|2[0-4]
[0-9]|25[0-5])"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="vqeUnicastAddrType">
<xs:restriction base="xs:string">
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-8 OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration in XML Format
<xs:pattern value="([1-9]?[0-9]|1[0-9][0-9]|2[0-1][0-9]|22[0-3])\.(([1-9]?[0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){2}([1
-9]?[0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="vqeFBTAddrType">
<xs:restriction base="xs:string"> <xs:pattern value="([1-9]|[1-9][0-9]|1[0-9][0-9]|2[0-1][0-9]|22[0-3])\.(([1-9]?[0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){
2}([1-9]?[0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="vqeRoleType">
<xs:restriction base="xs:string">
<xs:enumeration value="VQE-S"/>
<xs:enumeration value="VCDS"/>
<xs:enumeration value="SCP"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="extension_type">
<xs:sequence>
<xs:any processContents="lax" minOccurs="1"
maxOccurs="unbounded" namespace="##targetNamespace"/>
</xs:sequence>
</xs:complexType>
<xs:element name="extension" type="vqe:extension_type"/>
<!-- ************************ -->
<!-- VQE channel data -->
<!-- ************************ -->
<xs:element name="channelData"> <xs:complexType>
<xs:all>
<xs:element ref="vqe:channel-name"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:orig-multicast-addr"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:orig-RTP-port"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:orig-RTCP-port"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:src-filter-for-orig"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:bit-rate"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:error-repair"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:rapid-channel-change"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:RTCP-XR-report"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:RTCP-reduced-size"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:fbt-addr"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:rtx-RTP-port"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:rtx-RTCP-port"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:fec-col-multicast-addr"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:fec-col-RTP-port"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:src-filter-for-fec-col"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:fec-row-multicast-addr"
minOccurs="0" maxOccurs="1"/>
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 I-9
VCPT Configuration in XML Format
<xs:element ref="vqe:fec-row-RTP-port"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:src-filter-for-fec-row"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:extension"
minOccurs="0" maxOccurs="1"/>
</xs:all>
<!-- Channel id attribute -->
<xs:attribute name="id" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="20"/>
<xs:pattern value="[0-9a-zA-Z]+"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
<!-- channel-id -->
<xs:element name="channel-id">
<xs:annotation>
<xs:documentation>Unique channel id.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeIdType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- channel-name -->
<xs:element name="channel-name">
<xs:annotation>
<xs:documentation>Channel name for viewing purpose only.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeStringType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- orig-multicast-addr -->
<xs:element name="orig-multicast-addr">
<xs:annotation>
<xs:documentation>Multicast address for the original media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeMulticastAddrType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- orig-RTP-port -->
<xs:element name="orig-RTP-port">
<xs:annotation>
<xs:documentation>RTP port for the orginal media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqePortType"/>
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-10
Appendix I VCPT Configuration Files
OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration in XML Format
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- orig-RTCP-port -->
<xs:element name="orig-RTCP-port">
<xs:annotation>
<xs:documentation>RTCP port for the orginal media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqePortType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- src-filter-for-orig -->
<xs:element name="src-filter-for-orig">
<xs:annotation>
<xs:documentation>Source filter address for original media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeUnicastAddrType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- bit-rate -->
<xs:element name="bit-rate">
<xs:annotation>
<xs:documentation>Bit rate for original stream.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:nonNegativeInteger">
<xs:minInclusive value="1000"/>
<xs:maxInclusive value="30000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- error-repair -->
<xs:element name="error-repair">
<xs:annotation>
<xs:documentation>Option for unicast error repair.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeBooleanType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- rapid-channel-change -->
<xs:element name="rapid-channel-change">
<xs:annotation>
<xs:documentation>Option for rapid channel change.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeBooleanType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 I-11
VCPT Configuration in XML Format
<!-- RTCP-XR-report -->
<xs:element name="RTCP-XR-report">
<xs:annotation>
<xs:documentation>Option for RTCP XR report.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeBooleanType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- RTCP-reduced-size -->
<xs:element name="RTCP-reduced-size">
<xs:annotation>
<xs:documentation>Option for reduced-size RTCP.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeBooleanType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- fbt-addr -->
<xs:element name="fbt-addr">
<xs:annotation>
<xs:documentation>FBT address for the original media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeFBTAddrType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- rtx-RTP-port -->
<xs:element name="rtx-RTP-port">
<xs:annotation>
<xs:documentation>RTP port for retransmission media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqePortType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- rtx-RTCP-port -->
<xs:element name="rtx-RTCP-port">
<xs:annotation>
<xs:documentation>RTCP port for retransmission media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqePortType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- fec-col-multicast-addr -->
<xs:element name="fec-col-multicast-addr">
<xs:annotation>
<xs:documentation>Multicast address for FEC column media stream.
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-12
Appendix I VCPT Configuration Files
OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration in XML Format
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeMulticastAddrType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- fec-col-RTP-port -->
<xs:element name="fec-col-RTP-port">
<xs:annotation>
<xs:documentation>RTP port for FEC column media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqePortType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- src-filter-for-fec-col -->
<xs:element name="src-filter-for-fec-col">
<xs:annotation>
<xs:documentation>Source filter address for FEC column media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeUnicastAddrType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- fec-row-multicast-addr -->
<xs:element name="fec-row-multicast-addr">
<xs:annotation>
<xs:documentation>Multicast address for FEC row media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeMulticastAddrType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- fec-row-RTP-port -->
<xs:element name="fec-row-RTP-port">
<xs:annotation>
<xs:documentation>RTP port for FEC row media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqePortType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- src-filter-for-fec-row -->
<xs:element name="src-filter-for-fec-row">
<xs:annotation>
<xs:documentation>Source filter address for FEC row media stream.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 I-13
VCPT Configuration in XML Format
<xs:extension base="vqe:vqeUnicastAddrType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- ************************ -->
<!-- VQE server data -->
<!-- ************************ -->
<xs:element name="serverData">
<xs:complexType>
<xs:all>
<xs:element ref="vqe:svr-name"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:svr-addr"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:svr-role"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:svr-port"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:svr-username"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:svr-remote-location"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:svr-channel-association"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:svr-rtcp-interval"
minOccurs="0" maxOccurs="1"/>
<xs:element ref="vqe:svr-max-receivers"
minOccurs="0" maxOccurs="1"/>
</xs:all>
<!-- Server id attribute -->
<xs:attribute name="id" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="20"/>
<xs:pattern value="[0-9a-zA-Z]+"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
<!-- svr-name -->
<xs:element name="svr-name">
<xs:annotation>
<xs:documentation>VQE server name for viewing purpose only.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeStringType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- svr-addr -->
<xs:element name="svr-addr">
<xs:annotation>
<xs:documentation>VQE server IP address.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeUnicastAddrType"/>
</xs:simpleContent>
</xs:complexType>
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-14
Appendix I VCPT Configuration Files
OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration in XML Format
</xs:element>
<!-- svr-role -->
<xs:element name="svr-role">
<xs:annotation>
<xs:documentation>VQE server role.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeRoleType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- svr-port -->
<xs:element name="svr-port">
<xs:annotation>
<xs:documentation>Remote port for SCP operation.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:nonNegativeInteger">
<xs:minInclusive value="1"/>
<xs:maxInclusive value="65535"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- svr-username -->
<xs:element name="svr-username">
<xs:annotation>
<xs:documentation>Remote user name for SCP operation.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeStringType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- svr-remote-location -->
<xs:element name="svr-remote-location">
<xs:annotation>
<xs:documentation>Remote path and filename for SCP operation.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:simpleContent>
<xs:extension base="vqe:vqeStringType"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<!-- svr-channel-association -->
<xs:element name="svr-channel-association">
<xs:annotation>
<xs:documentation>VQE server and channels association.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element ref="vqe:channel-id"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- svr-rtcp-interval -->
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 I-15
Appendix I VCPT Configuration Files
VCPT Configuration in XML Format
<xs:element name="svr-rtcp-interval">
<xs:annotation>
<xs:documentation>RTCP report interval.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:nonNegativeInteger">
<xs:minInclusive value="5"/>
<xs:maxInclusive value="800"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- svr-max-receivers -->
<xs:element name="svr-max-receivers">
<xs:annotation>
<xs:documentation>Max receivers per server.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:nonNegativeInteger">
<xs:minInclusive value="1"/>
<xs:maxInclusive value="128000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:schema>
XML Data Elements and Attributes
presents the elements and attributes defined in vcpt_doc.xsd. This table maps each element and attribute to a data field.
defines the data rules associated with each data field.
Table I-2 Configuration File - XML Elements and Attributes
Element/Attribute channelData id (attribute)
Data Field
Channel Information
Channel Data
Channel Identifier orig-multicast-addr orig-RTP-port orig-RTCP-port
Original Source Stream Multicast IP address
Original Source Stream RTP Port Number
Original Source Stream RTCP Port Number src-filter-for-orig bit-rate
Original Source Stream Source Filter IP Address
Original Source Stream Bit Rate error-repair Enable Unicast Retransmission rapid-channel-change Enable Rapid Channel Change
RTCP-XR-Report
RTCP-reduced-size fbt-addr
Enable RTCP Extended Reports
Enable reduced-size RTCP
Feedback Target Address
I-16
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration in XML Format
Table I-2 serverData id (attribute)
Configuration File - XML Elements and Attributes
Element/Attribute rtx-RTP-port rtx-RTCP-port fec-col-multicast-addr fec-col-RTP-port src-filter-for-fec-col fec-row-multicast-addr fec-row-RTP-port src-filter-for-fec-row
Data Field
Unicast Retransmission RTP Port
Unicast Retransmission RTCP Port
FEC 1 Multicast Address
FEC 1 RTP Port
FEC 1 Source Filter Address
FEC 2 Multicast Address
FEC 2 RTP Port
FEC 2 Source Filter IP Address
VQE-S Data
Server attributeGroup
Server Identifier svr-addr Server Management IP Address svr-port srv-username svr-remote-location
Remote Server Port
Remote Server Username
Remote Server Location svr-channel-association svr-rtcp-interval
VQE-S and Channels Association
RTCP Interval svr-max-receivers Maximum Receivers channel-id Channel Identifier
XML Example
The following section shows an example of the VQE Channel configuration file in XML format:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<VcptFile
xmlns = "http://www.cisco.com/vqe/vcpt1.0"
xmlns:xsi = "http://www.w3.org/2001/XMLSchema"
version = "1.0.0">
<channelData id = "1206996909">
<channel-name>Channel 230.151.1.9</channel-name>
<orig-multicast-addr>230.151.1.9</orig-multicast-addr>
<orig-RTP-port>10032</orig-RTP-port>
<orig-RTCP-port>10033</orig-RTCP-port>
<src-filter-for-orig>5.8.37.2</src-filter-for-orig>
<bit-rate>20000</bit-rate>
<error-repair>true</error-repair>
<rapid-channel-change>true</rapid-channel-change>
<RTCP-XR-report>true</RTCP-XR-report>
<RTCP-reduced-size>true</RTCP-reduced-size>
<fbt-addr>8.61.1.9</fbt-addr>
<rtx-RTP-port>10034</rtx-RTP-port>
<rtx-RTCP-port>10035</rtx-RTCP-port>
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 I-17
VCPT Configuration in XML Format
I-18
</channelData>
<channelData id = "1206996908">
<channel-name>Channel 230.151.1.8</channel-name>
<orig-multicast-addr>230.151.1.8</orig-multicast-addr>
<orig-RTP-port>10028</orig-RTP-port>
<orig-RTCP-port>10029</orig-RTCP-port>
<src-filter-for-orig>5.8.37.2</src-filter-for-orig>
<bit-rate>15000</bit-rate>
<error-repair>true</error-repair>
<rapid-channel-change>true</rapid-channel-change>
<RTCP-XR-report>true</RTCP-XR-report>
<RTCP-reduced-size>true</RTCP-reduced-size>
<fbt-addr>8.61.1.8</fbt-addr>
<rtx-RTP-port>10030</rtx-RTP-port>
<rtx-RTCP-port>10031</rtx-RTCP-port>
</channelData>
<channelData id = "1206996907">
<channel-name>Channel 230.151.1.7</channel-name>
<orig-multicast-addr>230.151.1.7</orig-multicast-addr>
<orig-RTP-port>10024</orig-RTP-port>
<orig-RTCP-port>10025</orig-RTCP-port>
<src-filter-for-orig>5.8.37.2</src-filter-for-orig>
<bit-rate>15000</bit-rate>
<error-repair>true</error-repair>
<rapid-channel-change>true</rapid-channel-change>
<RTCP-XR-report>true</RTCP-XR-report>
<RTCP-reduced-size>true</RTCP-reduced-size>
<fbt-addr>8.61.1.7</fbt-addr>
<rtx-RTP-port>10026</rtx-RTP-port>
<rtx-RTCP-port>10027</rtx-RTCP-port>
</channelData>
<channelData id = "1206996906">
<channel-name>Channel 230.151.1.6</channel-name>
<orig-multicast-addr>230.151.1.6</orig-multicast-addr>
<orig-RTP-port>10020</orig-RTP-port>
<orig-RTCP-port>10021</orig-RTCP-port>
<src-filter-for-orig>5.8.37.2</src-filter-for-orig>
<bit-rate>2000</bit-rate>
<error-repair>true</error-repair>
<rapid-channel-change>true</rapid-channel-change>
<RTCP-XR-report>true</RTCP-XR-report>
<RTCP-reduced-size>true</RTCP-reduced-size>
<fbt-addr>8.61.1.6</fbt-addr>
<rtx-RTP-port>10022</rtx-RTP-port>
<rtx-RTCP-port>10023</rtx-RTCP-port>
</channelData>
<channelData id = "1206996905">
<channel-name>Channel 230.151.1.5</channel-name>
<orig-multicast-addr>230.151.1.5</orig-multicast-addr>
<orig-RTP-port>10016</orig-RTP-port>
<orig-RTCP-port>10017</orig-RTCP-port>
<src-filter-for-orig>5.8.37.2</src-filter-for-orig>
<bit-rate>2000</bit-rate>
<error-repair>true</error-repair>
<rapid-channel-change>true</rapid-channel-change>
<RTCP-XR-report>true</RTCP-XR-report>
<RTCP-reduced-size>true</RTCP-reduced-size>
<fbt-addr>8.61.1.5</fbt-addr>
<rtx-RTP-port>10018</rtx-RTP-port>
<rtx-RTCP-port>10019</rtx-RTCP-port>
</channelData>
<channelData id = "1206996904">
<channel-name>Channel 230.151.1.4</channel-name>
<orig-multicast-addr>230.151.1.4</orig-multicast-addr>
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
Appendix I VCPT Configuration Files
OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration in XML Format
<orig-RTP-port>10012</orig-RTP-port>
<orig-RTCP-port>10013</orig-RTCP-port>
<src-filter-for-orig>5.8.37.2</src-filter-for-orig>
<bit-rate>3750</bit-rate>
<error-repair>true</error-repair>
<rapid-channel-change>true</rapid-channel-change>
<RTCP-XR-report>true</RTCP-XR-report>
<RTCP-reduced-size>true</RTCP-reduced-size>
<fbt-addr>8.61.1.4</fbt-addr>
<rtx-RTP-port>10014</rtx-RTP-port>
<rtx-RTCP-port>10015</rtx-RTCP-port>
</channelData>
<channelData id = "1206996903">
<channel-name>Channel 230.151.1.3</channel-name>
<orig-multicast-addr>230.151.1.3</orig-multicast-addr>
<orig-RTP-port>10008</orig-RTP-port>
<orig-RTCP-port>10009</orig-RTCP-port>
<src-filter-for-orig>5.8.37.2</src-filter-for-orig>
<bit-rate>3750</bit-rate>
<error-repair>true</error-repair>
<rapid-channel-change>true</rapid-channel-change>
<RTCP-XR-report>true</RTCP-XR-report>
<RTCP-reduced-size>true</RTCP-reduced-size>
<fbt-addr>8.61.1.3</fbt-addr>
<rtx-RTP-port>10010</rtx-RTP-port>
<rtx-RTCP-port>10011</rtx-RTCP-port>
</channelData>
<channelData id = "1206996902">
<channel-name>Channel 230.151.1.2</channel-name>
<orig-multicast-addr>230.151.1.2</orig-multicast-addr>
<orig-RTP-port>10004</orig-RTP-port>
<orig-RTCP-port>10005</orig-RTCP-port>
<src-filter-for-orig>5.8.37.2</src-filter-for-orig>
<bit-rate>3750</bit-rate>
<error-repair>true</error-repair>
<rapid-channel-change>true</rapid-channel-change>
<RTCP-XR-report>true</RTCP-XR-report>
<RTCP-reduced-size>true</RTCP-reduced-size>
<fbt-addr>8.61.1.2</fbt-addr>
<rtx-RTP-port>10006</rtx-RTP-port>
<rtx-RTCP-port>10007</rtx-RTCP-port>
</channelData>
<channelData id = "1206996901">
<channel-name>Channel 230.151.1.1</channel-name>
<orig-multicast-addr>230.151.1.1</orig-multicast-addr>
<orig-RTP-port>10000</orig-RTP-port>
<orig-RTCP-port>10001</orig-RTCP-port>
<src-filter-for-orig>0.0.0.0</src-filter-for-orig>
<bit-rate>3750</bit-rate>
<error-repair>false</error-repair>
<rapid-channel-change>false</rapid-channel-change>
<RTCP-XR-report>false</RTCP-XR-report>
<RTCP-reduced-size>true</RTCP-reduced-size>
<fbt-addr>8.61.1.1</fbt-addr>
<rtx-RTP-port>10002</rtx-RTP-port>
<rtx-RTCP-port>10003</rtx-RTCP-port>
<fec-col-multicast-addr>230.151.1.1</fec-col-multicast-addr>
<fec-col-RTP-port>20000</fec-col-RTP-port>
<src-filter-for-fec-col>5.8.37.2</src-filter-for-fec-col>
<fec-row-multicast-addr>230.151.1.1</fec-row-multicast-addr>
<fec-row-RTP-port>20001</fec-row-RTP-port>
<src-filter-for-fec-row>5.8.37.2</src-filter-for-fec-row>
</channelData>
<channelData id = "1206996910">
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 I-19
VCPT Configuration in XML Format
I-20
<channel-name>Channel 230.151.1.10</channel-name>
<orig-multicast-addr>230.151.1.10</orig-multicast-addr>
<orig-RTP-port>10036</orig-RTP-port>
<orig-RTCP-port>10037</orig-RTCP-port>
<src-filter-for-orig>5.8.37.2</src-filter-for-orig>
<bit-rate>12500</bit-rate>
<error-repair>true</error-repair>
<rapid-channel-change>true</rapid-channel-change>
<RTCP-XR-report>true</RTCP-XR-report>
<RTCP-reduced-size>true</RTCP-reduced-size>
<fbt-addr>8.61.1.10</fbt-addr>
<rtx-RTP-port>10038</rtx-RTP-port>
<rtx-RTCP-port>10039</rtx-RTCP-port>
<fec-col-multicast-addr>230.151.1.10</fec-col-multicast-addr>
<fec-col-RTP-port>20038</fec-col-RTP-port>
<src-filter-for-fec-col>5.8.37.2</src-filter-for-fec-col>
<fec-row-multicast-addr>230.151.1.10</fec-row-multicast-addr>
<fec-row-RTP-port>20039</fec-row-RTP-port>
<src-filter-for-fec-row>5.8.37.2</src-filter-for-fec-row>
</channelData>
<serverData id = "1246310633746">
<svr-name>VCDS</svr-name>
<svr-addr>10.86.21.70</svr-addr>
<svr-role>VCDS</svr-role>
<svr-channel-association>
<channel-id>1206996901</channel-id>
<channel-id>1206996910</channel-id>
<channel-id>1206996902</channel-id>
<channel-id>1206996903</channel-id>
<channel-id>1206996904</channel-id>
<channel-id>1206996905</channel-id>
<channel-id>1206996906</channel-id>
<channel-id>1206996907</channel-id>
<channel-id>1206996908</channel-id>
<channel-id>1206996909</channel-id>
</svr-channel-association>
</serverData>
<serverData id = "1242662355264">
<svr-name>VQE Server</svr-name>
<svr-addr>10.86.21.70</svr-addr>
<svr-role>VQE-S</svr-role>
<svr-channel-association>
<channel-id>1206996901</channel-id>
<channel-id>1206996910</channel-id>
<channel-id>1206996902</channel-id>
<channel-id>1206996903</channel-id>
<channel-id>1206996904</channel-id>
<channel-id>1206996905</channel-id>
<channel-id>1206996906</channel-id>
<channel-id>1206996907</channel-id>
<channel-id>1206996908</channel-id>
<channel-id>1206996909</channel-id>
</svr-channel-association>
</serverData>
<serverData id = "1259680856543">
<svr-name>Carousel</svr-name>
<svr-addr>10.86.21.76</svr-addr>
<svr-role>SCP</svr-role>
<svr-port>22</svr-port>
<svr-username>vqe</svr-username>
<svr-remote-location>/etc/opt/vqes</svr-remote-location>
<svr-channel-association>
<channel-id>1206996901</channel-id>
<channel-id>1206996910</channel-id>
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
Appendix I VCPT Configuration Files
OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration in CSV Format
<channel-id>1206996902</channel-id>
<channel-id>1206996903</channel-id>
<channel-id>1206996904</channel-id>
<channel-id>1206996905</channel-id>
<channel-id>1206996906</channel-id>
<channel-id>1206996907</channel-id>
<channel-id>1206996908</channel-id>
<channel-id>1206996909</channel-id>
</svr-channel-association>
</serverData>
</VcptFile>
In this example, 10 channels, a VCDS, a VQE-S, and a remote server are configured. Unicast retransmission and RCC are enabled on all channels, except for channel 230.151.1.1. FEC is configured on two channels: channel 230.151.1.1 and channel 230.151.1.10. Sending reduced-size RTCP packets is enabled on all channels. All 10 channels are associated with each server.
VCPT Configuration in CSV Format
A configuration file in CSV format may be used to import configuration data into the VCPT or to export configuration data from the VCPT for modification or backup. Each line in the CSV configuration file represents a channel configuration, a server configuration, or a remote server configuration.
defines the data rules associated with each field of the configuration file.
Starting with Cisco VQE Release 3.5.5, the enable reduced-size RTCP option is added to the channel configuration. In this same release, the channel row in the CSV configuration file is separated into two rows: one for configuration of channels with no FEC services enabled, and one for configuration of channels with FEC services enabled.
The following list presents the data fields in Cisco VQE Release 3.5.5 and later releases for a channel configuration with no FEC services enabled in the CSV version of the configuration file. You must add fields in the order in which they are presented.
•
•
•
•
•
Leading Label—ER_CHANNEL
Channel Identifier
Channel Name
Original Stream Multicast IP Address
•
•
•
•
Original Source Stream RTP Port Number
Original Source Stream RTCP Port Number
Original Source Stream Source Filter IP Address
Original Source Stream Bit Rate
•
•
•
•
Feedback Target Address
Unicast Retransmission RTP Port
Unicast Retransmission RTCP Port
Enable RTCP XR Reports
•
•
Enable Unicast Retransmission
Enable RCC
Enable Reduced-Size RTCP
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-21
Appendix I VCPT Configuration Files
VCPT Configuration in CSV Format
The following list presents the data fields in Cisco VQE Release 3.5.5 and later releases for a channel configuration with FEC services enabled in the CSV version of the configuration file. You must add fields in the order in which they are presented.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Leading Label—FEC_CHANNEL
Channel Identifier
Channel Name
Original Stream Multicast IP Address
Original Source Stream RTP Port Number
Original Source Stream RTCP Port Number
Original Source Stream Source Filter IP Address
Original Source Stream Bit Rate
Feedback Target Address
Unicast Retransmission RTP Port
Unicast Retransmission RTCP Port
Enable RTCP XR Reports
Enable Unicast Retransmission
Enable RCC
FEC 1 Multicast Address
FEC 1 RTP Port
FEC 1 Source Filter Address
FEC 2 Multicast Address
FEC 2 RTP Port
FEC 2 Source Filter IP Address
Enable Reduced-Size RTCP
Note In Cisco VQE Release 3.5.5 and later releases, if more than one channel label is provided in the CSV file, the first label is accepted and all subsequent channel rows containing a different label are ignored.
The following list presents the data fields in Cisco VQE Release 3.5.4 and earlier releases for a channel configuration in the CSV version of the configuration file. You must add fields in the order in which they are presented.
• Leading Label—CHANNEL
•
•
•
•
•
Channel Identifier
Channel Name
Original Stream Multicast IP Address
Original Source Stream RTP Port Number
•
•
Original Source Stream RTCP Port Number
Original Source Stream Source Filter IP Address
Original Source Stream Bit Rate
I-22
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration in CSV Format
•
•
Feedback Target Address
Unicast Retransmission RTP Port
Unicast Retransmission RTCP Port •
•
•
•
•
•
•
Enable RTCP XR Reports
Enable Unicast Retransmission
Enable RCC
FEC 1 Multicast Address (Optional) •
•
•
•
•
•
•
•
FEC 1 RTP Port (Optional)
FEC 1 Source Filter Address (Optional)
FEC 2 Multicast Address (Optional)
FEC 2 RTP Port (Optional) •
• FEC 2 Source Filter IP Address (Optional)
The following list presents the data fields for a server (VCDS or VQE-S) configuration in the CSV version of the configuration file. You must add fields in the order in which they are presented.
• Leading Label
Server Identifier
Server Name
Server Management IP Address
Server Role
Server RTCP Interval
Server Maximum Receivers
Channel Identifiers
The following list presents the data fields for an SCP (remote server) configuration in the CSV version of the configuration file. You must add fields in the order in which they are presented.
• Leading Label
•
•
•
•
•
Server Identifier
Server Name
Server Management IP Address
Server Role
•
•
•
•
•
Server RTCP Interval
Server Maximum Receivers
Remote Server Port
Remote Server Username
Remote Server Location
Channel Identifiers
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-23
Appendix I VCPT Configuration Files
VCPT Configuration in CSV Format
CSV Example
The following example shows a channel configuration file in CSV format prior to Cisco VQE Release
3.5.5:
#CHANNEL,id,name,multicast-addr,rtp-port,rtcp-port,src-ip,bit-rate,fbt-addr,rtx-rtp-port,r tx-rtcp-port,xr-report-opt,err-opt,rcc-opt[,fec-col-addr,fec-col-port,fec-col-src-ip,fec-r ow-addr,fec-row-port,fec-row-src-ip]
CHANNEL,1206996909,Channel 230.151.1.9,230.151.1.9,10032,10033,5.8.37.2,20000,8.61.1.9,100
34,10035,true,true,true
CHANNEL,1206996908,Channel 230.151.1.8,230.151.1.8,10028,10029,5.8.37.2,15000,8.61.1.8,100
30,10031,true,true,true
CHANNEL,1206996907,Channel 230.151.1.7,230.151.1.7,10024,10025,5.8.37.2,15000,8.61.1.7,100
26,10027,true,true,true
CHANNEL,1206996906,Channel 230.151.1.6,230.151.1.6,10020,10021,5.8.37.2,2000,8.61.1.6,1002
2,10023,true,true,true
CHANNEL,1206996905,Channel 230.151.1.5,230.151.1.5,10016,10017,5.8.37.2,2000,8.61.1.5,1001
8,10019,true,true,true
CHANNEL,1206996904,Channel 230.151.1.4,230.151.1.4,10012,10013,5.8.37.2,3750,8.61.1.4,1001
4,10015,true,true,true
CHANNEL,1206996903,Channel 230.151.1.3,230.151.1.3,10008,10009,5.8.37.2,3750,8.61.1.3,1001
0,10011,true,true,true
CHANNEL,1206996902,Channel 230.151.1.2,230.151.1.2,10004,10005,5.8.37.2,3750,8.61.1.2,1000
6,10007,true,true,true
CHANNEL,1206996901,Channel 230.151.1.1,230.151.1.1,10000,10001,0.0.0.0,3750,8.61.1.1,10002
,10003,false,false,false,230.151.1.1,20000,5.8.37.2,230.151.1.1,20001,5.8.37.2
CHANNEL,1206996910,Channel 230.151.1.10,230.151.1.10,10036,10037,5.8.37.2,12500,8.61.1.10,
10038,10039,true,true,true,230.151.1.10,20038,5.8.37.2,230.151.1.10,20039,5.8.37.2
#SERVER,id,name,ip,role,rtcp-interval,max-receivers,channel-ids...
SERVER,1246310633746,VCDS,10.86.21.70,VCDS,,,1206996901,1206996910,1206996902,1206996903,1
206996904,1206996905,1206996906,1206996907,1206996908,1206996909
SERVER,1242662355264,VQE Server,10.86.21.70,VQE-S,,,1206996901,1206996910,1206996902,12069
96903,1206996904,1206996905,1206996906,1206996907,1206996908,1206996909
#SCP,id,name,ip,role,rtcp-interval,max-receivers,port,username,remote-location,channel-ids
...
SCP,1259680856543,Carousel,10.86.21.76,SCP,,,22,vqe,/etc/opt/vqes,1206996901,1206996910,12
06996902,1206996903,1206996904,1206996905,1206996906,1206996907,1206996908,1206996909
In this example, 10 channels, a VCDS, a VQE-S, and a remote server are configured. Unicast retransmission and RCC are enabled on all channels, except for channel 230.151.1.1. FEC is configured on two channels: channel 230.151.1.1 and channel 230.151.1.10. All 10 channels are associated with each server.
The following example shows a channel configuration file in CSV format in Cisco VQE Release 3.5.5:
#ER_CHANNEL,id,name,multicast-addr,rtp-port,rtcp-port,src-ip,bit-rate,fbt-addr,rtx-rtp-por t,rtx-rtcp-port,xr-report-opt,err-opt,rcc-opt,rtcp-rsize-opt
ER_CHANNEL,1206996909,Channel 230.151.1.9,230.151.1.9,10032,10033,5.8.37.2,20000,8.61.1.9,
10034,10035,true,true,true,false
ER_CHANNEL,1206996908,Channel 230.151.1.8,230.151.1.8,10028,10029,5.8.37.2,15000,8.61.1.8,
10030,10031,true,true,true,false
ER_CHANNEL,1206996907,Channel 230.151.1.7,230.151.1.7,10024,10025,5.8.37.2,15000,8.61.1.7,
10026,10027,true,true,true,false
ER_CHANNEL,1206996906,Channel 230.151.1.6,230.151.1.6,10020,10021,5.8.37.2,2000,8.61.1.6,1
0022,10023,true,true,true,false
ER_CHANNEL,1206996905,Channel 230.151.1.5,230.151.1.5,10016,10017,5.8.37.2,2000,8.61.1.5,1
0018,10019,true,true,true,false
ER_CHANNEL,1206996904,Channel 230.151.1.4,230.151.1.4,10012,10013,5.8.37.2,3750,8.61.1.4,1
0014,10015,true,true,true,false
ER_CHANNEL,1206996903,Channel 230.151.1.3,230.151.1.3,10008,10009,5.8.37.2,3750,8.61.1.3,1
0010,10011,true,true,true,false
ER_CHANNEL,1206996902,Channel 230.151.1.2,230.151.1.2,10004,10005,5.8.37.2,3750,8.61.1.2,1
0006,10007,true,true,true,false
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-24 OL-30119-01
Appendix I VCPT Configuration Files
VCPT Configuration in CSV Format
#SERVER,id,name,ip,role,rtcp-interval,max-receivers,channel-ids...
SERVER,1246310633746,VCDS,10.86.21.70,VCDS,,,1206996902,1206996903,1206996904,1206996905,1
206996906,1206996907,1206996908,1206996909
SERVER,1242662355264,VQE Server,10.86.21.70,VQE-S,,,1206996902,1206996903,1206996904,12069
96905,1206996906,1206996907,1206996908,1206996909
#SCP,id,name,ip,role,rtcp-interval,max-receivers,port,username,remote-location,channel-ids
...
SCP,1259680856543,Carousel,10.86.21.76,SCP,,,22,vqe,/etc/opt/vqes,1206996902,1206996903,12
06996904,1206996905,1206996906,1206996907,1206996908,1206996909
In this example, eight channels, a VCDS, a VQE-S, and a remote server are configured. Unicast retransmission and RCC are enabled on all channels. No FEC services are enabled. All eight channels are associated with each server. The field rtcp_rsize-opt was introduced in Cisco VQE Release 3.5.5.
The option to send reduced-size RTCP packets is disabled for each channel.
How to create the CSV format
You can create the CSV file by using lines of ASCII text with values separated by commas.
Use the following procedure to create a channel configuration file in CSV format.
Step 1
Step 2
Step 3
Open a text editor (such as Microsoft Notepad) or any application that allows you to export or create a
CSV file.
Use a separate line to enter the values for a channel configuration or a server configuration. You must observe the following rules when you create the CSV data file.
• Always include comma separators, even if a field is blank.
•
•
You must enter channel, server, and remote server configurations on separate rows.
Label the first field of a row either CHANNEL, SERVER, or SCP to identify the type of data that the row represents.
• If you insert a blank line an error will occur.
Upload the CSV file to the VQE Tools server on which the VCPT resides.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
I-25
VCPT Configuration in CSV Format
Appendix I VCPT Configuration Files
I-26
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
A P P E N D I X
J
Using IPMI on Cisco CDE 250
This appendix provides supplementary information on the Intelligent Platform Management Interface
(IPMI) for VQE on Cisco CDE-250 hardware. This appendix has the following major topics
Configuring IPMI on Cisco CDE-250, page J-1
Configuring Active Directory Settings for IPMI, page J-2
Remote Server Health Monitoring, page J-4
Remote Control of Cisco CDE 250 via IPMI, page J-5
Overview
IPMI provides access to multiple users from different locations to monitor system health and manage computer events from a remote location. IPMI operates independently of the operating system (i.e. out-of-band) to allow administrators to manage a system remotely in the absence of an operating system or a system management software. This interface can be used before an OS has booted and after OS or system failure. It allows for managing mutiple disparate servers from a single remote location.
IPMI functionality is provided by the BMC Controller present in the motherboard. This controller provides serial link connections between the South Bridge (one of the components in the BMC
Controller) and other onboard system components, allowing for network interfacing via remote access.
IPMI configuration can be done via a GUI interface.
Configuring IPMI on Cisco CDE-250
To configure IPMI on Cisco CDE-250, do the following:
Step 1
Step 2
Connect the CDE 250 IPMI Ethernet Port to a IP Network with a valid DHCP Server. The IPMI
Controller present in the hardware sends DHCP requests to the DHCP Server and acquires an IP Address to be assigned to IPMI Ethernet port.
Execute the following linux CLI command to verify the IP Address configured: ipmiutil lan -c
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01 J-1
Appendix J Using IPMI on Cisco CDE 250
Configuring Active Directory Settings for IPMI
Note
Step 3
In absence of a DHCP server, the linux CLI command ipmiutil lan -e -l <IP Address> -G <Gateway
IP> can be used to configure IP Address and Gateway IP for IPMI dedicated ethernet port.
Using your web browser, enter the IP address of IPMI.
Note IPMI GUI Interface supports Internet Explorer version 6 or higher, and Mozilla Firefox version 3.6 or higher.
Step 4
For example, if the IP address of your CDSM is 192.168.0.236, enter: http://192.168.0.236
Enter the username and password and click Login. The IPMI home page is displayed.
The built-in username is ADMIN and the initial password is ADMIN.
Configuring Active Directory Settings for IPMI
To configure Active Directory Settings for IPMI, do the following:
Step 1
Step 2
Step 3
Choose Configuration > Active Directory. The Active Directory Settings Table page is displayed.
Click Advanced Settings. The Active Directory- Advanced Settings page is displayed.
Enter the settings as appropriate. See Table J-1
for a description of fields.
Table J-1 Active Directory Advanced Settings Fields
Field
Enable Active Directory Authentication
User Domain Name
Port
Time Out
Domain Controller Server Address 1
Description
To enable/disable Active Directory, check or uncheck the "Enable Active Directory
Authentication" checkbox respectively.
Specifies the domain name of the user
Specifies the port number for sending active directory queries. The default value is 389
Note If the port value is incorrect, then it will take a couple of minutes, while trying to authenticate to the Active Directory server and finally authentication will fail.
In the meantime, web server will not be able to serve any other request(s).
Specifies the time in seconds for Active Directory queries to complete. The range is from 15 to 300 seconds. The default is 120 seconds.
The IP address of Active Directory server. Atleast one Domain Controller Server Address must be configured.
J-2
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix J Using IPMI on Cisco CDE 250
Configuring Active Directory Settings for IPMI
Table J-1 Active Directory Advanced Settings Fields
Field
Domain Controller Server Address 2
Domain Controller Server Address 3
Default Active Directory Certificate
Uplaod New Active Directory Certificate
Description
The IP address of Active Directory server. Atleast one Domain Controller Server Address must be configured.
The IP address of Active Directory server. Atleast one Domain Controller Server Address must be configured.
Specifies the defauly active directory certificate.
If no certificate is uplaoded then the default certificate is used.
Browse the Active Directory Certificate file using
Browse button.
Step 4 Click Save to save the settings.
Configuring Role Group
To configure Role Group for the serve, do the following:
Step 1
Step 2
Step 3
Choose Configuration > Active Directory. The Active Directory Settings Table page is displayed.
Select an empty slot in the list and click Add Role Group button. Add New Role Group page is displayed
Enter the settings as appropriate. See
Table J-1 for a description of fields.
Table J-2 Role Group Settings Fields
Field
Role Group Name
Description
Enter a name that identifies the role group in the
Active Directory. This name should match the role group name configured in the Active
Directory server.
Note Role Group Name is a string of 255 alpha-numeric characters.Special symbols hyphen, underscore and dot are allowed.
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
J-3
Appendix J Using IPMI on Cisco CDE 250
Remote Server Health Monitoring
Table J-2
Field
Role Group Settings Fields
Role Group Domain
Role Group Privelege
Description
Enter a domain where the role group is located.
Note
•
Domain Name is a string of 255 alpha-numeric characters.Special symbols hyphen, underscore and dot are allowed.
Choose the level of privilege to assign to this role group. The drop-down list has the following values:
Administrator
•
•
•
•
Operator
User
Call Back
No Access
Step 4 Click Add to save the settings and return to Role Group list page
Note After creating role groups, a new user can be created in the Active Directory Server and can be assigned to appropriate group and domain in the AD server. The user can also be assigned suitable privileges depending on his role.
Note For additional information on Configuring Active Directory via IPMI GUI, see Chapter 2 Section 2.4.4 of SuperMicro Embedded BMC/IPMI Manual, Revision 2.0
Remote Server Health Monitoring
The data related to server health such as sensor readings and the event log, can be viewed remotely via
IPMI GUI Interface.
Viewing System Sensor Information
To view system sensor information of various sensors, do the following:
Step 1
Step 2
Step 3
Step 4
Choose Server Health > Sensor Readings. The Sensor Readings page is displayed, that displays a list of the sensors with their Name, Status, and Readings.
To select the type of sensor readings to be displayed in the list, select the Sensor Type from the dropdown list.
To refresh the Sensor Reading, click Refresh.
To view the low and high threshold assignments for each sensor, click Show Thresholds.
J-4
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix J Using IPMI on Cisco CDE 250
Remote Control of Cisco CDE 250 via IPMI
Viewing Event Log Information
To view event log information, do the following:
Step 1
Step 2
Step 3
Choose Server Health > Event Log. The Event Log page is displayed, that displays a list of event logs with their ID, Timestamp, Sensor Name, Sensor Type and Sensor Description.
To select a particular event log category to be displayed in the list, select the event log category from the dropdown list.
To clear event logs, click Clear Event Log.
Note For additional information on Remote Server Health Monitoring via IPMI GUI, see Chapter 2 Section
2.3 of SuperMicro Embedded BMC/IPMI Manual, Revision 2.0
Remote Control of Cisco CDE 250 via IPMI
IPMI provides support for the user to carry out activities and perform operations on a remote server via remote access. It provides support for the following remote activities:
• To launch remote console support and manage the remote server using JAVA plugin installed on IE or Firefox
Note Ensure JAVA plugin for the browser is installed on the remote host from where console is launched
•
•
•
To enable Serial_Over_LAN support.
To display server power state and configure server power settings.
To configure virtual media settings.
Launching Remote Console
To launch remote console, do the following:
Step 1
Step 2
Step 3
Choose Remote Control, the Remote Control Operations page is displayed.
Click Launch Console option and download jviewer.jnlp (Java Web Start File).
Open jviewer.jnlp file to launch the console. The remote console is dsiplayed through IPMI dedicated
LAN port.
Note There will be few seconds delay in display of the output on the console screen. Press Enter multiple times for immediate display of output on the console screen. When reboot command is issued, there will be few seconds deloy before the output is displayed on the screen
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
J-5
Appendix J Using IPMI on Cisco CDE 250
Remote Control of Cisco CDE 250 via IPMI
Launching SOL
SOL feature provides serial port connections over LAN to allow the user to access / monitor a host server via Console Redirection from a remote site.
Note Ensure JAVA plugin for the browser is installed on the remote host from where the console is launched
To launch SOL, do the following:
Step 1
Step 2
Step 3
Choose Remote Control, the Remote Control Operations page is displayed.
Click Launch SOL option. The console screen appears.
Select the baud rate as 9600 (CISCO configured baudrate in BIOS on CDE 250) from the drop-down list and click Start.
Note There will be few seconds delay in display of the output on the console screen. Press Enter multiple times for immediate display of output on the console screen.
Power Control Operations
To view the current server power state and perform remote power control operations, do the following:
Step 1
Step 2
Step 3
Step 4
Choose Remote Control, the Remote Control Operations page is displayed.
Click Power Control option. The Power Control and Status page is displayed.
To perform one of the remote power control operations, do the following: a.
Check Reset Server checkbox to reboots the system without powering off (warm boot).
d.
e.
b.
c.
Check Power Off Server- Immediate checkbox to immediately power off the server.
Check Power Off Server - Orderly Shutdown checkbox to initiate Operating System shutdown.
Check Power On Server checkbox to power on the server.
Check Power Cycle Server checkbox to power off the server and then reboot (cold boot)
Click Perform Action to perform the operation.
Virtual Media Operations
The virtual media feature is used for reimaging the system with a software (iso image) when the system is suspected to be corrupted.
To configure the image file, do the following:
Step 1
Step 2
Choose Remote Control, the Remote Control Operations page is displayed.
Click Virtual Media option. The Virtual Media page is displayed.
J-6
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
Appendix J Using IPMI on Cisco CDE 250
Unit Reset
Step 3 Enter the settings as appropriate. See
Table J-3 for a description of fields.
Table J-3 Virtual Media Fields
Field
Share Host IP
Share Folder Name
Path to Image
Image Type
Description
The IP Address of the Host where the iso image is placed
The name of the shared folder
Location of the iso image within the shared folder
Identifies the type of emulation and the options are
•
•
Note
Floppy Disk
CD-ROM
User Name
Password
Step 4 Click Set to save the settings. Once the iso file is mounted as CDROM, the page displays Successfully
Set Virtual CD message is displayed.
Note Once the above steps are completed successfully, system should be Rebooted / Powered On to start the installation from the ISO image mounted as a Virtual CD Drive on this host.
Unit Reset
To reset the IPMI device, do the following:
Step 1
Step 2
Choose Maintenance > Unit Reset. the Unit Reset page is displayed.
Click Reset to reboot the IPMI device.
References
For additional information on IPMI GUI, see SuperMicro Embedded BMC/IPMI Manual, Revision 2.0
OL-30119-01
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
J-7
References
Appendix J Using IPMI on Cisco CDE 250
J-8
Cisco CDA Visual Quality Experience Application User Guide Release 3.7
OL-30119-01
I N D E X
Symbols
/etc configuration files description
managing with VQE CMS
A access link bandwidth for each VQE-C
access routes
address and port-dependent mapping (with NAT)
anycast addresses
Apache Tomcat application server
Application Monitoring Tool (AMT)
See VQE-S Application Monitoring Tool (AMT)
-apply option to vqe_cfgtool
Area ID parameter
Area Type parameter
average stream rate
B
-backup option to vqe_cfgtool 7-19
bandwidth conserving with RCC
excess fraction
maximum receive for a VQE-C
on the access link for each VQE-C
per VQE Client policing
reserved for Unicast Retransmission
reserving for incoming unicast traffic
binding requests to STUN Server
78-xxxxx-xx
BIOS settings on CDE110 server
Bit Rate field
Bond interfaces configuring
description
boot sequence on CDE110 server
C
cache time
capacity statistics
CD/DVD drive
centralized logging 2-28, D-22, D-39
certificate authority (CA) certificates deploying commercial certificates
generating
installing
Certificate Signing Request (CSR) generating
Certificate-Signing Request (CSR) signing
channel change time
Channel Lineups window
channel-provisioning servers 2-27, D-21
channels associating with servers
cloning with VCPT
configuration database in VQE-S
configuring
copying associations with a server
defining server associations
defining with VCPT
Book Title
IN-1
Index deleting with VCPT
enabling Rapid Channel Change
error-repair options
Member Receiver Population
modifying configuration
multicast streams
provisioning with VCPT
rules for adding
viewing configuration with VQE-S AMT
viewing details with VCPT
viewing details with VQE-S AMT
viewing statistics with VQE-S AMT
check_daemons script
Cisco CDA Visual Quality Experience Application
Cisco CDE
Cisco CDE110
bandwidth limits
configuring MIBs
initial configuring for VQE-S 2-23, D-2
initial configuring for VQE Tools
restarting
terminal emulation software
viewing hardware information
Cisco CDE111 bandwidth limits
Cisco CDE250
bandwidth limits
Cisco Digital Content Manager (DCM)
Cisco end-to-end IPTV solution model
Cisco set-top boxes
CISCO-SYSLOG-MIB
Cisco technical support
Cisco VQE benefits
deployment options
deployment requirements
Book Title
IN-2
Hybrid Error Repair
overview
reference architecture model
software components
software installation and upgrade
Cisco VQE Client (VQE-C)
Cisco VQE Server (VQE-S)
CISCO-VQES-MIB
client database file
cloning channels
commands
vcds_send_file
vqereport
-config option to vqe_cfgtool
configuration delivery infrastructure (CDI)
Configuration Engine (CE)
configuration files managing with VQE CMS
Configuration Management System
See VQE Configuration Management System (VQE
CMS) configuration parameters (VCDB) description
OSPF parameters
Rapid Channel Change parameters A-6, A-9
RTCP Exporter parameters
system parameters
Unicast Retransmission parameters
VQE-S global parameters
Configuration Tool (CT) description
78-xxxxx-xx
information on parameters
parsing errors
Root Menu
using
vqe_cfgtool command
configuring VQE-S and VQE Tools servers
manually
Control Plane process monitoring by Process Monitor
monitoring with Linux commands
monitoring with VQE-S AMT
CPE (customer premises equipment)
VQE-C integration
VQE-C interface to VQE-S
D
Data Plane process monitoring by Process Monitor
monitoring with Linux commands
monitoring with VQE-S AMT
date and time changing with Network Time Protocol
changing with the date command
dead interval (OSPF)
Dead Interval parameter
debugging configuring options
4-33 messages written to vqe.log file 4-33, 5-9
options in VQE-S AMT
dedicated interfaces
defining a channel
defining channel associations with VCPT
delay of IPTV packets
Delete button in VCPT
deleting channels
Differentiated Services Code Point (DSCP) configuring for RCC
configuring for RTCP packets
78-xxxxx-xx
Index configuring for STUN Server binding requests
configuring for Unicast Retransmission A-6
description
viewing configuration
Digital Content Manager (DCM) 1-3, 1-5, 1-7, 1-14
directories for VCPT
for VQE-S
Domain Name System (DNS) servers
DSL
Cisco VQE for
noise issues
Dynamic Host Configuration Protocol (DHCP) servers
dynamic routing feature
E
Enable MD5 parameter
Entitlement Control Messages (ECM)
Equal Cost Multipath (ECMP) routes
error messages
error repair
configuring
options
See also Unicast Retransmission
Ethernet ports
CDE110
configuring
Layer 3 connection
MIB
numbering
excess bandwidth fraction
configuring
maximum
viewing configuration
Book Title
IN-3
Index viewing distributions
Export button in VCPT
exporting RTP statistics
F facility codes
failover protection
Fast Decoder Buffer Fill (FDBF) 1-7, A-6
FEC configuring
description
Hybrid Error Repair
one and two dimensions
stream generator
VQE-C implementation
feedback target addresses anycast addresses
static routes on attached router
Feedback Target IP field
feedback target routes
filenames
VCPT configuration files
VQE-S and VCPT
files for VCPT
for VQE-S
replacing a lost file
-fix_checksum -option to vqe_cfgtool
-fix_config option to vqe_cfgtool
Force Update button
forward error correction
G
IN-4
Book Title
H hello interval (OSPF)
Hello Interval parameter
hostname configuring
parameter
HOST-RESOURCE-MIB
httpd service automatic start
error log
log files
restarting
verifying status
HTTPS clients (trusted) configuring on a VQE-S
configuring on a VQE Tools server
Hybrid Error Repair
Cisco VQE benefit
configuring
description
HyperText Transfer Protocol daemon
I
If
IF-MIB
I-frames
IGMP channel change delay
fast leave in access node
join variability
latency data
VQE-S and multicast groups
Import button in VCPT
ingest of multicast streams
initial configuration tasks
78-xxxxx-xx
Index with manual configuration
Input Bandwidth Table
INTEL-SERVER-BASEBOARD5 MIB
Interface parameters reference information
interfaces configuring
2-25, 2-26, A-3, D-4, D-5, D-15, D-18, D-32
configuring with Configuration Tool 7-6
configuring with VCDB parameters A-3, A-4
dedicated
for VQE-S ingest and services traffic 2-30, A-3, D-17
for VQE-S ingest traffic
for VQE-S services traffic
shared
Interface Summary Table
ip link show command
IPTV existing and new deployments
packet loss
packets
statistics
video services
IPTV Packet Loss Monitoring description
with VQE-S RTCP Exporter
IPTV Services Delivery Server (ISDS) cannot send channel information
J jitter
L
LACP bonding for VQE-S
Linux operating system
78-xxxxx-xx initial configuration
load balancing of VQE-S services
log files (VQE-related)
logging configuring levels
levels
messages written to vqe.log file
viewing log files
look-aside mode
Loss RLE report block type
lost files
M management networks configuring for VQE-S hosts
configuring for VQE Tools hosts
configuring with VQE Configuration Tool
maximum receive bandwidth (MRB)
MD5 authentication VCDB parameters A-19
MD5 Key ID parameter
MD5 Key parameter
Member Receiver Population 1-22, 4-7
messages
Microsoft Internet Explorer
Mozilla Firefox
MPEG Parser
Multicast Group Table
multicast IP addresses
Multicast IP field
multicast IPTV
multicast latency
Multicast Load Balancer process description
monitoring
Book Title
IN-5
Index
Process Monitor role
verifying it is running
viewing statistics
multicast streams
for channels
monitoring
multiple definitions of VCDB parameters
N
NACK messages
NAT statistics
See Network Address Translation
Net-SNMP
Network Address Translation (NAT) description
STUN Server
network configuration file
network parameters configuring
Network Time Protocol (NTP) configuring
daemon
parameter
with SSL certificates
New Config button
configuring and starting
started automatically
verifying it is running
O
Open Configuration button
open-source software
IN-6
Book Title
original stream for a channel 3-10
OSPF
configuring for VQE-S traffic D-10
configuring system services
initial configuration parameters
on router attached to VQE-S host
on VQE-S host
routing type VCDB parameter A-18
status in VQE-S AMT
VCDB parameters
verifying edge router configuration
verifying system services
verifying VQE-S configuration D-11
VQE-S host in area 0
VQE-S host in separate area
ospfd service
P packet loss
packets for IPTV
lost
received
repair
repair statistics
RTCP
parameters
passwords
for vqe user
requirements
per-client network configuration
permissions for files and directories changing
for VCPT
78-xxxxx-xx
Index policing
port usage on VQE-S
Process Monitor process
Program Association Tables (PAT)
Program Clock Reference (PCR)
Program Map Tables (PMT)
Q
Quagga processes
routing package
R random access points (RAPs)
Rapid Channel Change (RCC)
enabling with VCPT
monitoring statistics
viewing configuration
viewing statistics
VQE-S role
Re-Activate button in VQE-S 4-7
Real Time Streaming Protocol (RTSP) 1-17
Real-Time Transport Protocol (RTP)
repair packet statistics
rebooting
VQE-S
recovery procedures
Red Hat Enterprise Linux 5.1 operating system
redundancy for VQE-S
reset counters
Resetting the root password
78-xxxxx-xx resiliency of VQE-S
restarting
VCDS
VQE-S
VQE-S channels
restore counters
-restore option to vqe_cfgtool
root user
router attached to VQE-S host
OSPF routing guidance
static routes for feedback targets
Router ID parameter
router ID VCDB parameter
routing configuration for shared interfaces
overview
routing types with VQE-S
RTCP Exporter
RTCP Port field
RTCP Reports description
viewing configuration
RTP Control Protocol (RTCP) compound packets
description
industry standards
packet statistics
sender and receiver reports
RTP inactivity timeout
RTP Port field
RTSP DESCRIBE
S
-sanity_check option to vqe_cfgtool
Book Title
IN-7
Index
Scientific-Atlanta IPTV Layer (SAIL) 1.x and 2.x
screen resolution requirements
SDP files created by VCPT
Secure Shell (SSH)
Secure Shell daemon
Secure Sockets Layer (SSL) certificates
See SSL certificates
security restrictions
selective retransmission
Send button
sending channel information
serial ports
server.key file
servers adding
defining with VCPT
deleting with VCPT
viewing server information
services configuring and starting
started automatically
traffic for VQE-S
VQE-S
Session Description Protocol (SDP) 1-7
severity levels
shared interfaces
SMPTE 2022 standard stream orderings
VQE-C extensions
SNMP agent
AgentX
CISCO-SYSLOG-MIB
CISCO-VQES-MIB
CISCO-VQE-TOOLS-MIB
Book Title
IN-8 columnar objects
community strings
configuring
events
Intel subagent
MIB
object identifier
parameters
protocol-related counters
scalar objects
snmp manager
SNMP subagent
snmp subagent
SNMPv2
trap
viewing SNMP configuration
SNMP-NOTIFICATION-MIB
snmpsa service
SNMP subagent
SNMP subagent daemon 2-31, 2-32
SNMPv2-MIB MIB
software components of Cisco VQE 1-4
software development kit (SDK) for VQE-C
software installation and upgrade
Source IP field
SSH certificates
sshd service
SSL certificates deploying commercial
deploying your own
error log
setting up
VQE Configuration Tool
stackedChain.pem file
starting
VCDS
VQE-S
78-xxxxx-xx
Index static routes configuring for VQE-S traffic
for a distribution network
for a management network
for feedback targets
limitations
on VQE-S
statistics
Error Repair
packet-loss monitoring
RTCP Exporter
Status of Last Send messages
status of VQE-S processes
stopping
VCDS
VQE-S
Store As button
Store button
stream generators for FEC
STUN Server
configuration
enabling
monitoring
su or sudo commands
symmetric NAT
syslog_snmpsa service
syslog messages
See system messages
syslog snmp service
system.iptables.trusted_provisioner parameter
system console
system information system status
system messages description
no channel configuration
78-xxxxx-xx online file with reference information
setting logging level
severity
structure
viewing system log
VQE-S logging
written to vqe.log
system parameters configuring
reference information
system services
on VQE Tools host
system time changing with Network Time protocol
changing with the date command
T
Telco Alarm Management
terminal emulation software
terminal servers
tomcat5 service automatic start
restarting
verifying status
Tomcat log
TR-135 statistics
TRAP listeners
troubleshooting
channels not displayed in VQE-S AMT 6-11
internal server error in VCPT
multicast streams
no graphs in VQE-S AMT
repeated messages on Cisco CDE110
VCPT cannot send channel information
Book Title
IN-9
Index
VCPT unavailable
VQE-S, VQE-S AMT, and VCPT
VQE-S AMT unavailable
trustedca file
trusted provisioning clients
trusted provisioning servers
U unicast reservation
Unicast Retransmission bandwidth reserved
configuring
description
Hybrid Error Repair
parameters
per VQE Client policing
viewing statistics
VQE-C role
VQE-S AMT
VQE-S role
Unicast Retransmission Stream fields
upgrading software
usage statistics for channels
V vcdb.conf.sample file
description
on VQE-S
parameter information in
vcdb.conf.tools.sample file 6-4
VCDB file (vcdb.conf)
RTCP Exporter
VCDB parameters entering data
IN-10
Book Title multiple definitions allowed or not allowed
order of
reference information
those not configurable with CT
VCDB Parser
VCDS
See VQE Client Configuration Delivery Server
(VCDS) vcds_send_file command
vcds_snmpsa service
VCDS AMT
SeeVQE Client Configuration Delivery Server
(VCDS)
VCDS Application Monitoring Tool (VCDS AMT)
configuring VCDS debugging
description
log files
logging in
navigating
VCDS Configuration Window
VCDS Status Information
VCDServer process
vcds service configuring and starting
started automatically
verifying status
VCPT
See VQE Channel Provisioning Tool (VCPT)
verifying host system for VCPT
verifying system services
video quality
video-quality monitoring (VQM) application 1-23
viewing channel details
VQE
78-xxxxx-xx
Index
vqe.log file
vqe_cfgtool command
-config option
VQE Channel Provisioning Tool
VQE Channel Provisioning Tool (VCPT) adding servers
cloning channels
configuration filenames
configuration files
copying channel associations
csv format
defining channel associations
defining channels
defining servers
deleting channels
deleting servers
description
exporting
export to remote server
GUI
initial configuring
interactions with VQE Client Configuration Delivery
Server
interactions with VQE-S
log files
logging in
provisioning channels
sending channel information
software
SSL certificates
Status of Last Send messages
troubleshooting
trusted HTTPS clients
using
verifying status
78-xxxxx-xx viewing channel information
viewing server information
VQE deployment
VQE reference architecture model
xml schema
VQE Client (VQE-C)
Cisco end-to-end IPTV solution model
description
DHCP and DNS servers
Error Repair
IPTV Packet Loss Monitoring
maximum receive bandwidth A-11
Network Address Translation (NAT)
network configuration
network connectivity
number receiving a channel
per-client policing
policing
policing for Unicast Retransmission
Rapid Channel Change
set-top box integration
software development kit
system configuration provisioning server
VQE reference architecture model
VQE Client Configuration Delivery Server (VCDS) defining with VCPT
description
DHCP and DNS servers
interactions with VQE Client
role in VQE-C network configuration
software
starting and stopping
system messages
verifying status
VQE reference architecture
VQE Configuration Database (VCDB)
Book Title
IN-11
Index description
parameters
used for multiple CDE110 servers 7-3
VQE Configuration Management System (VQE CMS) description
vqe_cfgtool command
VQE Configuration Tool configuration items
VQE-C system configuration provisioning server 1-19,
VQE-GROUPATTR keyword
VQE-GROUPMAP keyword
vqes_snmpsa service
VQE-S Application Monitoring Tool (AMT) configuring logging
configuring VQE-S debugging
logging in
monitoring health of VQE-S processes
monitoring interfaces
monitoring Multicast Load Balancer
monitoring VQE-S RTCP Exporter
navigating
troubleshooting
using
viewing channel configuration and status 4-7, 5-4
viewing log files
web application
VQE-S Application Monitoring Tool (VQE-S AMT) description
VQE Server (VQE-S) bandwidth reserved for inbound requests
cable connections
configuring
configuring static routes
configuring VCDB parameters
counters restarted
Book Title
IN-12 current status
debugging levels
defining with VCPT
description
Equal Cost Multipath (ECMP) routes
global parameters
ingest and services traffic
ingest traffic
initial configuring
log files
logging levels
monitoring health of processes
policers
processes
resiliency
routing overview
service (vqes) 1-10, 2-31, 6-30
services traffic
software version
starting
STUN Server
system messages
trusted channel-provisioning servers 2-27, D-21
Unicast Retransmission
verifying status
viewing log file
VQE-S RTCP Exporter configuring and enabling
description
IPTV Packet Loss Monitoring
monitoring with VQE-S AMT
78-xxxxx-xx
Index
RTCP packet statistics
vqe-s snmpsa service
VQE Startup Configuration Utility pre-configuration worksheets
Root Menu choices
routing configuration
VQE Tools server configuring
verifying status
vqe user ID
2-4, 2-24, 2-32, 2-34, 2-41, 2-42, D-4, D-32
vqm_host parameter
vqm_port parameter
VQM Host information
VQM TCP Port information
W watchquagga process
web browser requirements
X xDSL
XML schema and examples
for client database file 1-20, F-1 for group attribute file 1-20, F-1
Z zebra service
78-xxxxx-xx
Book Title
IN-13
Index
IN-14
Book Title
78-xxxxx-xx
Tải xuống
Đã cập nhật liên kết công khai
Liên kết công khai đến cuộc trò chuyện của bạn đã được cập nhật. You may view and manage your chat links after registration here.
Liên kết công khai tài liệu
Quảng cáo