![]() |
Table Of Contents
Release Notes for Cisco TV VDS 3.4
New Hardware Features in Cisco VDS TV Release 3.4.1
CDD Storage Management Utility
SCTE35 Detection and Reporting
White Space / Carriage Return Removal
New Hardware Features in Cisco VDS TV Release 3.4.2
Open Caveats for Cisco VDS TV Release 3.4.2
Resolved Caveats Cisco VDS TV Release 3.4.2
Open Caveats for Cisco VDS TV Release 3.4.0
Resolved Caveats Cisco VDS TV Release 3.4.0
Upgrading to Cisco VDS-TV Release 3.4.2
Downgrading from Release 3.4.2
Downgrading from Fresh-installed Release 3.4.2
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco TV VDS 3.4
OL-30870-02
Last Updated: December 10, 2013
These release notes describe the features and caveats for all releases in the Cisco TV VDS Release 3.4 train.
These release notes are updated with each release in the train. This update adds information for Cisco TV VDS Release 3.4.2. For a list of the caveats that apply to this release, see the "Caveats" section.
Contents
The following information is in the release notes:
•
Upgrading to Cisco VDS-TV Release 3.4.2
•
Downgrading from Release 3.4.2
•
Obtaining Documentation and Submitting a Service Request
New Features
These sections list the new features supported by the Cisco TV VDS:
•
New Hardware Features in Cisco VDS TV Release 3.4.1
•
New Hardware Features in Cisco VDS TV Release 3.4.2
New Hardware Features in Cisco VDS TV Release 3.4.1
CDE470 Hardware Support
The Cisco TV VDS Release 3.4 introduces CDE470 Hardware support that allows Digital Video Recording storage in a high capacity cloud. See the Cisco Content Delivery Engine 205/220/250/420/460/470 Hardware Installation Guide.
Video On Demand
The Cisco TV VDS Release 3.4 is enhanced to further support Multi-Bitrate ATS and IP Delivery via the Videoscape Origin Server (VOS) and Content Delivery Network (CDN) to the IP Client.
CDD Storage Management Utility
The CDD Storage Management utility (CDDM) for VDS-TV's Content Delivery Devices (CDD) is a new and robust interface for reporting device attributes and statistics, and to manage devices in events such as device failure, device identification, device suspension, device removal, device failure prediction and replacement. It is available from the Linux prompt as any other Linux utility. See its man page for details.
SCTE35 Detection and Reporting
The Cisco TV VDS 3.4 Release supports the correct detection, reporting and filtering of signal packets. In addition, corrects Splice Out/In points reporting to Recorder Manager. The Recorder will have to filter out any invalid or duplicated signal packets to make sure Recorder Manager & CNS receives the correct SCTE35 Splice In and Splice Out points. Recorder will also log and report drop statistics due to detection of invalid signal points. The detection will be done in recorder's ingest process and only consider SCTE-35 time signal messages without supporting SCTE-35 splice insert messages anymore. In the time signal message, NPT will be derived from the PTS in the time signal and signal id will be retrieved from the segmentation descriptor of the same message. If there are multiple SCTE-35 PIDs, recorder will only consider the first SCTE-35 PID. Recorder Manager can simply pass the correct Splice Out/In points received via R8 interface and report as part of RecordingInfo message to CNS via C3 interface without significant effort.
White Space / Carriage Return Removal
A new tunable was introduced to control formatting of XML entity bodies for HTTP requests and responses. This new tunable is named /proc/calypso/tunables/xml_pretty_print, and by default is set to zero. To be compatible with some XML parsers, XML response bodies cannot have whitespace that could be used to format the XML in a way that is more human readable. With this tunable set to zero, human readable XML is not generated, and whitespace such as carriage returns, new lines and tabs are not inserted into the XML body.
The affected XML bodies are:
•
C2 Locate Request
•
C2 Locate Response
•
C2 Describe Request
•
C2 Describe Response
•
C2 Delete Transfer ID Request
•
Generic HTTP MPD Response
Multi-Purpose port support
This feature allows the Cserver and Linux network stacks share the 10GbE hardware while using the same IP address/Subnet information. Packets intended for Linux and Cserver are filtered by hardware and directed to their respective queues without cross-contamination. This helps to leverage the wide bandwidth available with the 10GbE hardware without the need for additional hardware for specific purposes.
New Hardware Features in Cisco VDS TV Release 3.4.2
ATIS C2 Server Support
The Cisco TV VDS Release 3.4 expands on client (Streamer) side support for Alliance for Telecommunications Industry Solutions (ATIS) C2.
It introduces the ATIS C2 in the server (Vault) side. This support will enable the Cisco Vaults to serve content to third party streamers in addition to Cisco streamer's capability to stream contents from third party servers. These ATIS C2 enabled Vaults will be serving as National Vaults, which will be controlled by a VVIM unlike the Local VoD market's vault which is controlled by CDSM.
Cisco's Vault will act as ATIS C2 server where it can ingest contents (ATIS indexing) and serve contents to Cisco's streamer via ATIS C2. This ATIS enabled vault is at the national level. Local VoD market will remain the same. Once the content is provisioned and ingested in ATIS index format in the national vault, Local VoD market's vault will provision the same, there by triggering the code flow path supported for earlier releases.
A new index format is added to the Configure > Server Level > Server Setup Page. The user can view the index format as ATIS based on the ATIS C2 mode field configured in the CDSM Setup page.
A new Interface type is added to the Vault Server to configure the locate interface for ATIS C2 Server setup. This setting will be available to configure via the Configure > Server Level > Interface Setup Page.
A new provision is added for the user to configure the Location virtual IP and Subnet mask for that particular vault group. This setting will be available via the Configure > Array Level > Vault Group Setup page.
ATIS Media Resource Requirements
Each media resource in an ATIS environment has a MediaResourceSet consisting of the following:
•
Base media file, also called the 1X file.
•
Media Resource Metadata (MRM) file in XML format, which has information about the presence and location (URI) of trick-mode files and index files.
•
Index file (ATIS standard index file), which has information about the 1X file, properties of the MPEG TS, Index data for Entry/Exit points in the 1X file, and associated trick-mode file.
DNS Support
Currently VDS-TV supports host name resolution based on the /etc/hosts file. Starting from Release 3.4, as a more dynamic way to resolve host name, VDS-TV supports DNS lookup based host name resolution.
A new field is added to the Maintain > Software > VVIM Setup Page, to fill the Domain Name details, under the ATIS C2 Support division itself.
Asset Ingest Manager Support
The Cisco TV VDS Release 3.4 provisions the support to publish ATIS packages. These functionalities will be carried out by Asset Ingest Manager (AIM) with critical supports from Management Components like Virtual Video Infrastructure Manager (VVIM) and Database.
The AIM ensures ingestion by facilitating transfer of content and metadata or control information between the various components on the Recorder Vaults at a National Site.
A new button is added to the Maintain > Software > CDSM/VVIM Setup page to enable or disable the ATIS C2 setup. In order to differentiate ATIS Server and Client, select from a drop-down list that includes options as None, Client and Server.
The user can specify a list of VOD market sites under Configure > System Level > VOD Market Sites, to register the list of VOD Market site
A new option is added to the Maintain > Software > System Configs for the user to set default values for AIM. The user can then navigate to Configure > System Level > Ingest Manager page to set the remaining configuration details for AIM.
A new provision had been added for the publish mode. This setting will be available via the Configure > System Level > Ingest Manager Page. AIM will support auto publish mode. Enabling this mode from GUI will let AIM to automatically publish packages to the configured VOD Market Sites at the end of each successful package ingest.
The user can view the package publish status for a particular package via the Monitor > System Level.
The user can also view a list of Unpublished Packages, their corresponding VOD Market sites and the retry count information via the Monitor > System Level.
Package Status Support
The Cisco TV VDS Release 3.4.2 introduces changes to GUI, The package details can be viewed on the Package Publish Status Monitor screen which can be access via Under Monitor > System Level > Package Publish Status. Publish status can be viewed in two modes:
•
Package name
•
VOD Market Site
A auto completion list replaces what was previously a drop down list. A list of package names appears as the first character of the package name is typed in the text box. To view the publish status click Display.
Package Expiration Support
The Cisco TV VDS Release 3.4.2 introduces changes to GUI, The package details can be viewed and deleted on the Package Expiration Monitor screen which can be access via Under Monitor > System Level > Package Expiration page.
Supported Environments
Release 3.4 of the Cisco TV VDS supports both the ISA and RTSP environments. Some RTSP environment features are only applicable to certain RTSP Deployment Types.
System Requirements
The Cisco TV VDS Release 3.4 runs on the CDE110, CDE220, CDE250, CDE420, CDE460 and CDE470. See the Cisco Content Delivery Engine110 Hardware Installation Guide, and the Cisco Content Delivery Engine 205/220/250/420/460/470 Hardware Installation Guide.
The Cisco TV VDS Release 3.4 does not run on the CDE100, CDE200, CDE300, and CDE400 hardware models.
Note
If you are using Internet Explorer 8 to access the CDSM GUI, for the online help to display correctly, you need to turn on Compatibility View. To turn on Compatibility View in Internet Explorer 8, choose Tools > Compatibility View.
Caveats
Caveats describe unexpected behavior in Cisco VDS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only selected severity 3 caveats are included in the caveats document.
Caveat numbers and brief descriptions for Cisco VDS TV Release 3.4.0-based releases are listed in this section.
Open Caveats for Cisco VDS TV Release 3.4.2
Table 3 lists the open issues in the VDS-TV 3.4.2 release.
Click on the bug ID to view the bug details. This information is displayed in the Bug Search.
Resolved Caveats Cisco VDS TV Release 3.4.2
Table 3 lists the fixed issues in the VDS-TV 3.4.2 release.
Click on the bug ID to view the bug details. This information is displayed in the Bug Search.
Open Caveats for Cisco VDS TV Release 3.4.0
Table 3 lists the open issues in the VDS-TV 3.4.0 release.
Click on the bug ID to view the bug details. This information is displayed in the Bug Search.
Resolved Caveats Cisco VDS TV Release 3.4.0
Table 3 lists the fixed issues in the VDS-TV 3.4.0 release.
Click on the bug ID to view the bug details. This information is displayed in the Bug Search.
Accessing Bug Search Tool
This section explains how to use the Bug Search tool to search for a specific bug or to search for all bugs in a release.
Step 1
Go to https://tools.cisco.com/bugsearch/.
Step 2
At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The
Bug Search page opens.
Note
If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.
Step 3
To search for a specific bug, enter the bug ID in the Search For field, and press Enter.
Step 4
To search for bugs in the current release, specify the following criteria:
•
Select the Model/SW Family Product Category drop-down list box, then enter Cisco Videoscape Distribution Suite for Television or select the name from the Select from list option.
•
Select Cisco Videoscape Distribution Suite for Television from the list that displays.
•
The VDS Television Software type displays in the Software Type drop-down list box.
•
Releases: 3.4.
•
Advanced Filter Options—Define custom criteria for an advanced search by selecting an appropriate value from the drop-down lists by choosing either one Filter or multiple filters from the available categories. After each selection, the results page will automatically load below the filters pane. If you select multiple filters, it behaves like an AND condition.
–
Modified Date—Select one of these options to filter bugs: Last Week, Last 30 days, Last 6 months, Last year, or All.
–
Status—Select Fixed, Open, Other, or Terminated.
Select Fixed to view fixed bugs. To filter fixed bugs, uncheck the Fixed check box and select the appropriate suboption (Resolved or Verified) that appears below the Fixed check box.
Select Open to view all open bugs. To filter the open bugs, uncheck the Open check box and select the appropriate suboptions that appear below the Open check box.
Select Other to view any bugs that are duplicates of another bug.
Select Terminated to view terminated bugs. To filter terminated bugs, uncheck the Terminated check box and select the appropriate suboption (Closed, Junked, or Unreproducible) that appears below the Terminated check box. Select multiple options as required.
–
Severity—Select the severity level:
1: Catastrophic.
2: Severe
3: Moderate
4: Minor
5: Cosmetic
6: Enhancement
–
Rating—Select the bug's quality rating: 5 Stars (excellent), 4 or more Stars (good), 3 or more Stars (medium), 2 or more Stars (moderate), 1 or more Stars (poor), or No Stars.
–
Support Cases—Select whether the bug Has Support Cases or No Support Cases.
–
Bug Type—Select whether the bug is Employee Visible & Customer Visible or Customer Visible Only.
Step 5
The Bug Toolkit displays the list of bugs based on the specified search criteria.
Step 6
You can save or email the current search by clicking their respective option.
If you have any problems using the Bug Search tool, log into the Technical Support website at http://www.cisco.com/cisco/web/support/index.html or contact the Cisco Technical Assistance Center (TAC).
Upgrading to Cisco VDS-TV Release 3.4.2
For the upgrade sequence of the VDS devices in your system (CDSM/VVIM and VDS servers [Vault, Streamer, Caching Node, ISV]), see the "Overview" chapter in the Cisco TV VDS 3.4 Installation, Upgrade, and Maintenance Guide.
To upgrade a VDS device, do the following:
Step 1
Download the ISO image file (VDS-TV-3.4.x-.iso) and the cdsinstall-3.4 script from the Cisco Software Download website. For more information on downloading the software files, see the "Overview" chapter in the Cisco TV VDS 3.4 Installation, Upgrade, and Maintenance Guide.
Step 2
For the VDS servers, offload the device before upgrading the software.
a.
From the CDSM GUI, choose Maintain > Servers > Server Offload. The Server Offload page is displayed.
b.
From the Server IP drop-down list, select the IP address or nickname of the sever and click Display.
c.
From the New Server Status drop-down list, select Offline for a Recorder or Streamer or Caching Node, select Offline (No Ingest & Fill) for a Vault.
d.
Click Submit.
e.
Ensure the VDS server is offloaded by checking the protocol timing log.
Step 3
Log in to the VDS server as user root.
Step 4
For VDS servers, before installing the image file, stop the database with the following command:
# db_shutdown
Wait until the following command returns no output:
# netstat -an | grep 9999 and #pgrep avsdb
Step 5
Copy the ISO image file and the cdsinstall-3.4 script to the VDS server.
# scp -p <user>@<remote_ip_address>:CDS-TV-3.4.iso /# scp -p <user>@<remote_ip_address>:cdsinstall-3.4 /
Step 6
Run the cdsinstall script to upgrade the ISO image to Release 3.4.
# cd /root
# ./cdsinstall-3.4 /CDS-TV-3.4.iso
Step 7
For the CDSM or VVIM, when the script has completed, reboot the server.
Step 8
For the CDSM or VVIM, log in to the GUI as a user with Engineering access level and configure the settings on the CDSM Setup page.
Step 9
For VDS servers, start DB and statsd
# su - isa -c "arroyo start avsdb" >& /dev/null# /home/stats/statsd.bin -i <Server IP> -s <subnet mask> -d eth0Wait till statsd connects to avsdb and both are operational
Submit Server Interface Setup page for this VDS server from GUI
Configure -> Server Level -> Interface SetupMake sure the /arroyo/test/<server type>/setupfile is updated with the e1000e driver for the 1 Gig cache fill interfaces
Shutdown DB
Reboot the server
# pgrep avsdb
Move the rc.local to the original location
# mv /etc/rc.d/rc.local /etc/rc.d/rc.local.bak
# rebootStep 10
After server has come up, start the services as per the sequence in the /etc/rc.local,
Start avsdb
# su - isa -c "arroyo start avsdb" >& /dev/nullStart avslauncher to start setup and control IP (incase if the VDS server is streamer)
# /usr/bin/avslauncher >& /arroyo/log/avslauncher.out&Start cserver
# /arroyo/test/runStart FSI application (incase if the VDS server is vault)
# su - isa -c "arroyo start fsi ns nfs aim" >& /dev/nullStart statsd
# /home/stats/statsd.bin -i <Server IP> -s <subnet mask> -d eth0Start Recorder application (if the VDS server is Recorder)
# su - isa -c "arroyo start recsvr" >& /dev/null# su - isa -c "arroyo start dnsresolver" >& /dev/null
Step 11
For VDS recorder, if the upgrade is from any version lower than 3.4.2 to version 3.4.2, DB conversion is required.
a.
Shutdown avsdb
# db_shutdownb.
Backup DATADIR
# cd /arroyo/db/# cp -rf DATADIR DATADIR-bkc.
Restart avsdb
# su - isa -c "arroyo start avsdb" >& /dev/nulld.
Dump recording profiles data
# /arroyo/db/AVSDBUtilEnter: 8, 10, 5 respectively by following the command prompts
Note
•
8: RECORDER DB
•
10: Dump All RecordingProf
•
5: Verbose (file)
•
the dump file "RecordingProfDump.txt" is generated in /arroyo/db/ directory.
e.
Run check and convert data
# /arroyo/db/AVSDBUtilEnter: 8, 12, 1, respectively by following the command prompts
Notes:
Note
•
8: RECORDER DB
•
12: Check Recording Index
•
1: Convert index
•
Following files are generated in /arroyo/db/ for debug purpose
–
RecordingProfConv.txt
Example of RecordingProfConv.txt:
"Delete operation successfully completed: 01497a2eae41e67819099da7fd8d0bf8_1306168
Add operation successfully completed: 01497a2eae41e67819099da7fd8d0bf8_Profile5"
–
RecordingProfIndex.txt
Example of RecordingProfIndex.txt:
"Name: 01497a2eae41e67819099da7fd8d0bf8_1306168"
Step 12
For VDS servers, after the VDS server is verified as reachable, return the server to online.
a.
Choose Maintain > Servers > Server Offload. The Server Offload page is displayed.
b.
From the Server IP dropdown list, select the IP address or nickname of the server and click Display.
c.
Choose Online and click Submit.
d.
Verify the VDS server is online by viewing the status on the Monitor > System Level > System Health page.
Downgrading from Release 3.4.2
For the downgrade sequence of the VDS devices in your system (CDSM/VVIM and VDS servers [Vault, Streamer, Caching Node, ISV]), see the "Overview" chapter in the Cisco TV VDS 3.4 Installation, Upgrade, and Maintenance Guide.
To downgrade a VDS device, do the following:
Step 1
Download the ISO image file (for example, VDS-TV-3.3.2.iso) and the cdsinstall script (for example, cdsinstall-3.3.2) for Release 3.4 from the Cisco software download website. For more information on downloading the software files, see the "Overview" chapter in the Cisco TV VDS 3.2 Installation, Upgrade, and Maintenance Guide.
Step 2
For VDS servers, offload the server (see Step 2 in "Upgrading to Cisco VDS-TV Release 3.4.2").
Step 3
Log in to the VDS device as user root.
Step 4
For VDS recorder, disable RAID on 3.4
# echo 0 > /proc/calypso/tunables/allowvaultraidMake sure RAID is disabled by the "RS=0" parameter in the /arroyo/log/protocoltiming.log.
# tail -f /arroyo/log/protocoltiming.log | grep RS= RS=0 Active=0:0 read=0 write=0 (12:2)
Step 5
For VDS recorder, downgrade the file system to support 3MB allocation unit for 3.3.2 code
Issue the following command to downgrade the file system
# echo 107 > /proc/calypso/tunables/cm_logserverinfoWait for the message "Downgrade of file system complete" on the console indicating that the file system downgrade is complete.
# Downgrade of file system completeStep 6
For VDS recorder, if the downgrade is from any version lower than 3.4.2 to any lower version (such as 3.4.1, 3.3.2), DB conversion is required.
a.
Shutdown avsdb
# db_shutdownb.
Backup DATADIR
# cd /arroyo/db/# cp -rf DATADIR DATADIR-bkc.
Restart avsdb
# su - isa -c "arroyo start avsdb" >& /dev/nulld.
Run check and convert data
# /arroyo/db/AVSDBUtilEnter: 8, 12, 2 respectively by following the command prompts
Note
•
8: RECORDER DB
•
12: Check Recording Index
•
2: Reverse conversion
•
Following files are updated in /arroyo/db/ for debug purpose
–
RecordingProfConv.txt
Example of RecordingProfConv.txt:
"Add operation successfully completed: 01497a2eae41e67819099da7fd8d0bf8_1306168
Delete operation successfully completed: 2e958999bb43ee013d93cbab4468c2d8_Profile1"
–
RecordingProfIndex.txt
Example of RecordingProfIndex.txt:
"Name: 01497a2eae41e67819099da7fd8d0bf8_Profile1"
Step 7
For VDS recorder, before installing the image file, stop the database with the following command:
# db_shutdownWait until the following command returns no output:
# netstat -an | grep 9999 and #pgrep avsdbStep 8
Copy the ISO image file and the cdsinstall script to the /root directory and run the cdsinstall script to download the software. For example, the following commands are for downgrading to Release 3.3.2:
# scp -p <user>@<remote_ip_address>:CDS-TV-3.3.2.iso /
# scp -p <user>@<remote_ip_address>:cdsinstall-3.3.2 /
# cd /root
# ./cdsinstall-3.3.2 /CDS-TV-3.3.2.iso
Step 9
For the CDSM or VVIM, when the script has completed, reboot the server.
Step 10
For VDS servers, make sure that the database is not running and reboot the server.
# pgrep avsdb
# mv /etc/rc.d/rc.local /etc/rc.d/rc.local.bak
# rebootStep 11
For VDS servers, after the VDS server has come up from reboot, start DB, statsd, submit the interface setup page and start cserver
# su - isa -c "arroyo start avsdb" >& /dev/null
# /home/stats/statsd.bin -i <Server IP> -s <subnet mask> -d eth0
Wait till statsd connects to avsdb and both are operational
Submit Server Interface Setup page for this VDS server from GUI
Configure -> Server Level -> Interface SetupStart avslauncher to start setup and control IP (incase if the VDS server is streamer)
# /usr/bin/avslauncher >& /arroyo/log/avslauncher.out&Start cserver
# /arroyo/test/run
Start FSI application (incase if the VDS server is vault)
# su - isa -c "arroyo start fsi ns nfs aim" >& /dev/null
Start Recorder application (incase if the VDS server is Recorder)
# su - isa -c "arroyo start recsvr" >& /dev/null# su - isa -c "arroyo start dnsresolver" >& /dev/nullMove the rc.local to the original location
# mv /etc/rc.d/rc.local.bak /etc/rc.d/rc.local
Step 12
For VDS servers, after the VDS server is verified as reachable, return the server to online.
a.
Choose Maintain > Servers > Server Offload. The Server Offload page is displayed.
b.
From the Server IP dropdown list, select the IP address or nickname of the server and click Display.
c.
From the New Server Status drop-down list, select Online and click Submit.
d.
Verify the VDS server is online by viewing the status on the Monitor > System Level > System Health page.
Downgrading from Fresh-installed Release 3.4.2
For the downgrade sequence of the VDS devices in your system (CDSM/VVIM and VDS servers [Vault, Streamer, Caching Node, ISV]), see the "Overview" chapter in the Cisco TV VDS 3.4 Installation, Upgrade, and Maintenance Guide.
Note
If the VDS recorder is a brand-new device and has not registered to CDSM yet, skip the following steps 1, 2, 3, and 4.
To downgrade a VDS device, do the following:
Step 1
Download the ISO image file (for example, VDS-TV-3.3.2.iso) and the cdsinstall script (for example, cdsinstall-3.3.2) for Release 3.4 from the Cisco software download website. For more information on downloading the software files, see the "Overview" chapter in the Cisco TV VDS 3.2 Installation, Upgrade, and Maintenance Guide.
Step 2
For VDS servers, offload the server (see Step 2 in "Upgrading to Cisco VDS-TV Release 3.4.2").
Step 3
Log in to the VDS device as user root.
Step 4
For VDS recorder, before installing the image file, stop the database with the following command:
# db_shutdownWait until the following command returns no output:
# netstat -an | grep 9999 and #pgrep avsdbStep 5
Copy the ISO image file and the cdsinstall script to the /root directory and run the cdsinstall script to download the software. For example, the following commands are for downgrading to Release 3.3.2:
# scp -p <user>@<remote_ip_address>:CDS-TV-3.3.2.iso /
# scp -p <user>@<remote_ip_address>:cdsinstall-3.3.2 /
# cd /root
# ./cdsinstall-3.3.2 /CDS-TV-3.3.2.iso
Step 6
For the CDSM or VVIM, when the script has completed, reboot the server.
Step 7
For VDS servers, make sure that the database is not running and reboot the server.
# pgrep avsdb
# mv /etc/rc.d/rc.local /etc/rc.d/rc.local.bak
# rebootStep 8
For VDS recorder, after the VDS server has come up from reboot, start DB, statsd, submit the interface setup page and start cserver
Note
For a brand-new VDS recorder, see the "Overview" chapter in the Cisco TV VDS 3.4 Installation, Upgrade, and Maintenance Guide for additional configuration if needed.
# su - isa -c "arroyo start avsdb" >& /dev/null
# /home/stats/statsd.bin -i <Server IP> -s <subnet mask> -d eth0
Wait till statsd connects to avsdb and both are operational
Submit Server Interface Setup page for this VDS server from GUI
Configure -> Server Level -> Interface SetupStart avslauncher to start setup and control IP (incase if the VDS server is streamer)
# /usr/bin/avslauncher >& /arroyo/log/avslauncher.out&Start cserver
# /arroyo/test/run
Start Recorder application (incase if the VDS server is Recorder)
# su - isa -c "arroyo start recsvr" >& /dev/nullMove the rc.local to the original location
# mv /etc/rc.d/rc.local.bak /etc/rc.d/rc.local
Step 9
For VDS servers, after the VDS server is verified as reachable, return the server to online.
a.
Choose Maintain > Servers > Server Offload. The Server Offload page is displayed.
b.
From the Server IP dropdown list, select the IP address or nickname of the server and click Display.
c.
From the New Server Status drop-down list, select Online and click Submit.
d.
Verify the VDS server is online by viewing the status on the Monitor > System Level > System Health page.
Related Documentation
Refer to the following documents for additional information about the Cisco VDS-TV 3.4:
•
Cisco VDS-TV 3.4 ISA Software Configuration Guide
•
Cisco VDS-TV 3.4 RTSP Software Configuration Guide
•
Cisco VDS-TV 3.4 API Guide
•
Cisco VDS-TV 3.4 Installation, Upgrade, and Maintenance Guide
•
Cisco VDS-TV 3.4 Release Note
•
Cisco Content Delivery Engine 205/220/250/420 Hardware Installation Guide
•
Cisco Content Delivery Engine 110 Hardware Installation Guide
•
Regulatory Compliance and Safety Information for Cisco Content Delivery Engines
•
Open Source Used in VDS-TV 3.4
http://www.cisco.com/en/US/products/ps12653/products_licensing_information_listing.html
The entire VDS software documentation suite is available on Cisco.com at:
http://www.cisco.com/en/US/products/ps7127/tsd_products_support_series_home.html
The entire VDS hardware documentation suite is available on Cisco.com at:
http://www.cisco.com/en/US/products/ps7126/tsd_products_support_series_home.html
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:
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.
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)
This product contains watermarking technology that is licensed from Verimatrix, Inc., and such functionality should not be used or distributed further by you without any additional license(s) required from Verimatrix, Inc.
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.
© 2013 Cisco Systems, Inc. All rights reserved.