Guest

Cisco Videoscape Distribution Suite for Television

Release Notes for Cisco VDS-TV 3.2.3

  • Viewing Options

  • PDF (402.8 KB)
  • Feedback
Release Notes for Cisco VDS-TV 3.2.3

Table Of Contents

Release Notes for Cisco VDS-TV 3.2.3

Contents

Enhancements

Open Caveats

Resolved Caveats

Accessing Bug Tool kit

Upgrading to Release 3.2.3

Upgrading to Cisco VDS-TV Release 3.2.3

Downgrading from Release 3.2.3

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco VDS-TV 3.2.3


These release notes cover Cisco Videoscape Distribution Suite for Television (VDS-TV) Release 3.2.3.

Revised: September 2013 OL-30484-01

Contents

The following information is in the release notes:

Enhancements

Open Caveats

Resolved Caveats

Upgrading to Release 3.2.3

Related Documentation

Obtaining Documentation and Submitting a Service Request

Enhancements

The following enhancements have been added in Release 3.2.3:


Note It is recommended that the user refer only the Cisco VDS-TV 3.2.3 Release Note for all 3.2.3 enhancements. In this release, GUI Online Help will not reflect changes on the GUI side.


From 3.2.3 Release, avsdb will resync/patrol CONTENT_OBJECT table only from lowest server id instead of pulling data from master vault. This enhancement is mainly to reduce some load on master vault due to resyncing of more than 300K contents (CSCue71124).

From 3.2.3 Release, avsdb will detect remote server record corruption during resync and avoids adding those records in the local database. This detection can be witnesed through the log messages RECV ERROR : UNEXPECTED STRUCTTYPE or RECV ERROR : FOUND INVALID ENTRY IN RECORD or RECVd len(xx) not matching expected len (CSCuh97238).

Enhanced the cdsinstall deployment to include a cdsinstall generic script.

With this Enhancement, the cdsinstall script has been simplified so that it will delegate all the actions specific to a deployment to another script there by remaining generic across all deployments.

Output of the script has been logged in to cdsinstall.log, in addition to the console logging. The /etc/cisco-version-history will be logged with current image version.

Release 3.2.3 of the Cisco VDS-TV is enhanced to support 512 servers in the Cserver side if the group members are running in the 3.2.3 version (CSCug62458).


Note The Database is restricted to support maximum of 256 replication members. To support more servers in the system enable the Vault Master feature.


The number of concurrent ingest request is enhanced to include a maximum of 2/3 of configured value. If the number of threads configured in the GUI is 32, then the maximum number of concurrent ingest would be 21. It allows the customer to change the maximum number of threads in the GUI in order to increase the number of concurrent ingest request (CSCug60685).


Note The above feature is supported only in the ISA Environment.


RTSP delays due to DB sluggishness has been fixed. A separate thread pool has been introduced which will handle the non-critical DB transactions (reporting information). Since the non-critical transactions are off-loaded all critical transactions are completed on time. This is applicable to only RTSP deployment (CSCug54427).

Release 3.2.3 of the Cisco VDS-TV is enhanced to support dynamic configuration of the poll timer to the appropriate number (maximum: 5minutes) if it finds any poll timer expiry error with the default value (CSCug89852).

If the DB is down in any of the replication members for more than 4 hours (default configuration is 4 hours), then local avsdb will move status of all down servers to new state called FULL_DOWN. Once the server status changes to FULL_DOWN, replication manager won't keep any records in REPLAY.db for replication to all down servers. When the server is back online it does a full resync and starts participating in the replication group in regular way.

If the replication data in REPLAY.db crosses certain threshold (configurable) then the replication manager will delete the oldest records more aggressively. The deletion rate is dynamically calculated to keep up to the incoming rate. This will ensure that we are not increasing the entries in REPLAY.db indefinitely (CSCug89796)

In 3.2.3 avsdb will delete the records from REPLAY.db file aggressively when record count crosses its threshold value. In this scenario avsdb should read the records and need to take backup of trick mode /session info related records for Advertisement insertion.

This enhancement bug is done to take a backup of Provision multiple, trick mode report and stream object table before aggressive deletion. These back file will be created and rotated every one hour if the deletion request comes.repdbbkputil binary will take all the back up file which are in created last one hour and it will read and send the data to all the controller mentioned in the .arroyorc file. If the records were moved to controllers, it will delete the backup file.

If NO_BACKUP file is placed in /arroyo/db folder then records will not be taken backup and records will not move to controllers.(CSCui66872).

A manual compact is required to run so that all the unused space is released back. This enhancement is to run compact during run time without impacting any functionality. Running compact is a costly process, so this has to be carefully dealt with. A separate light weight thread will be initiated which will perform the compact functionality in smaller chunks (CSCuh45370).

This enhancement provides an interface exposed by statsd, which can be used to move master to a desired server, by IP address (CSCug67386).

The statsd performs additional checks when the Vault is not in a good state to become a master (CSCug67376).

The following are the additional checks that have been implemented:

Check the presence of a "noapplication" line in the /home/isa/.arroyorc file:

If a "noapplication 1" line is present, the failover threads will not be started by statsd running on this vault

Failover threads not starting means that this vault will not participate in the failover process and will not assume master

This line is read from the .arroyorc file when statsd starts

This check will be performed only if the "nofailover" flag is not set (if it is set, failover threads won't be started anyway)

Any change to this line (or to the .arroyorc) will not take effect until statsd is restarted

Check whether cServer is up:

statsd will not attempt to make this vault master if cServer is not running

This is a periodic check and the check will succeed if at some point cServer comes-up while statsd is running.

Check whether back-office is up:

statsd will not attempt to make this vault master if back-office cannot be pinged

This is a periodic check and the check will succeed if at some point back-office becomes reachable.

This enhancement will enable the ARP parameters to configure from GUI. During failover scenarios, statsd running on a master vault would look for these ARP configurations and use the right parameter for ARP. Navigate to Maintain > Software > CDSM/VVIM Setup in order to configure the ARP parameters (CSCug89698).

The Cisco VDS-TV Release 3.2.3 is enhanced to support NTP server configuration on the CDSM (CSCuh03092).

From the 3.2.3 Release, the alarms are generated whenever statsd fails to update any of the files (FillSourceConfigFile, SetupFile, Remoteserver), or when the size of the partitions (/arroyo, /arroyo/db, REPLAY.DB file) increases beyond the threshold value (CSCuh00551).

This feature provides an option to select a group of servers and offload in one shot. To select a group and offload you need to navigate to Maintain > Servers > Server Offload in the GUI. This will facilitate better operational activities. (CSCuh00615).

This feature will enable the user to know how long the server is running from GUI ( Monitor > System Level > System Health ). This information will be displayed in the format ('n' Days, HH:MM) since the server's last reboot (CSCug97610).

The AVS monitoring script will help in automatically login to all the servers and collects the required info. This script has been integrated to CDSM/VVIM GUI. Navigate to Monitor > System Level > System Health Scan to know the system health scan information (CSCug87479).

Open Caveats

Table 1 lists the open issues in the VDS-TV 3.2.3 release.

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

Table 1 Open Caveats in VDS-TV 3.2.3 Release 

Bug ID
Description

CSCuh97077

AVSDB tserver thread got stuck

CSCui72478

DESCRIBE response for Real Time Ingest

CSCui32417

Serviceability: CRC checks for every content copy within a deployment

CSCui32709

Thin Pipe Configurations must maintain same name reference in setupfile

CSCui59682

CONTENT_REPORT.db ever increasing

CSCui80269

Bad SSD drive in streamer causes soft cpu lock ups

CSCuh88403

Expired packages were not deleted after the master vault failover

CSCuj06852

PKES encrypted MPEG 4 trick files showing white flash

CSCuc57520

Vault crashed with \"areCopiesOnUniqueDrives\" in 3.2.0

CSCuh06712

File system changed to read-only mode


Resolved Caveats

Table 2 lists the issues resolved in the VDS-TV 3.2.3 release.

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

Table 2 Resolved Caveats in VDS-TV 3.2.3 Release 

Bug ID
Description

CSCud82193

Which interface is streaming an arbitrary stream

CSCue84240

CDE250 cserver-prod-3.2.1-b3 does not handle "HTTP" in the R2 setup req

CSCue92785

After long pause, play is not resuming near pause npt

CSCui48691

Thinpipe changes through VVIM requires cserver to be running

CSCui01209

Rtsp service got crashed after streaming nDVR and VOD streams

CSCtt15084

Primary role for setup or control should failover if db goes down

CSCui66872

AVSDB should maintain trick/session info records during deletion

CSCui53245

VVIM database getting stuck and recovered by own

CSCug81788

Need a configurable option on GUI to enter homeID entry for CV Account

CSCug39574

Database in constant reboot cycle due to memory exhaustion

CSCub17028

ContentStore(Master) restarts due to TAO threads deadlock in SCS env

CSCub38015

2.5.5 & 2.5.6 Servers not creating core file when hung in kernel debug

CSCuh89262

Vault hit KDB with assert (pollsPerSecond != 0) || g_isExecutingFromKdb

CSCue12314

Vault crashes due to corrupt Linux kernel memory

CSCue60505

RTSP send mixed up response messages to BO under heavy load

CSCue71124

Ingest services could be restarted

CSCue75384

RTSP crashes in memcpy () from /lib/libc.so.6

CSCui23981

TAO Memory corruption (stack overflow)

CSCug90301

ISA restarts due to memory corruptions

CSCue78940

VMcore is not generated on systems with 2.6.32 kernels

CSCuh24147

Network adapter is unable to transmit packages (corrupted tx_ring)

CSCuf77052

Streamer crashed when empty fill source configuration was pushed to it

CSCuf81691

Play does not resume at beginning of asset aka pause point

CSCth14750

arrayID values handed out by the CDSMs at these VHOs are out-of-bounds

CSCui20469

Resume play failing due to trick restrictions

CSCug21980

SETUP MULTI: specify range in seconds, not milliseconds

CSCui13171

Locate Timeout - High Priority Fill locate timeout

CSCug29480

DESCRIBE call not supported in RTSP MULTI

CSCug42138

DB resync causes data deletion during error scenarios

CSCuh50035

DESCRIBE response in multi session should consist of 1 RTSP 200 OK

CSCug48973

ISA Watchdog script restarts ISA

CSCug54427

Comcast RTSP sluggishness issue

CSCuh42243

statsd hang causing the avsdb process memory leak and ultimately a crash

CSCug66741

No log archival on the RTSP master streamers

CSCui02381

Virtual CS fails provisioning of ATIS contents

CSCuh27111

RTSP Pause results in ANNOUNCE end-of-stream

CSCuh97238

During Resync local record validation missing

CSCui60837

CALYPSO ASSERT: \"\"addHole failed\"\" causes LocalMirror to get stuck

CSCui70245

Bandwidth reservation not being released

CSCud84024

Unnecessary LSC_DONE when Rewind-Skip feature build 2.5.7b13

CSCud84042

Incorrect StreamNpt value on PSE_START_SEGMENT build 2.5.7b13

CSCue04267

Poll CPU normalization

CSCue48129

Cache Thread failing to run once a hour, too many Goids

CSCue68020

CS master failover to streamer rather than other available vault in group

CSCue77503

CDSM db hang

CSCue86332

Admin user failed to login

CSCue92348

In controllers Log file archive not happening

CSCuf20128

Back office points to the old master after master failover

CSCuf60360

Issue on the free_transmit_allocated for the http adapter which lost li

CSCuf78341

AVSDB crashes due to corrupt STREAM_SERVICE_LIST.db and IOR_OBJECT.db

CSCuf86036

Vault taking an FSI master role when there is an existing FSI master

CSCug17990

PaidToGoidCache should not cache the entries for in progress live record

CSCug28355

Resource Manager continuously restarts during peak periods

CSCug29921

Incorrect PSE_END_SEGMENT & VE_STOP values on playlist pause

CSCug29926

Incorrect ISA Stream Extension time value

CSCug43823

SNMPd High Memory Usage

CSCug55351

statsd crashes on parsing statsd.conf with missing double-quotes

CSCug69081

New partno are missing the details in CDSMGUI

CSCug86346

One vault down lead to all of the content ingest to other vault

CSCug89595

GETALL request to CONTENT_OBJECT table returns incorrect result

CSCuh08734

2.5.8 - Empty values for 'segmentIndex' and 'mode' in Everstream API

CSCuh41984

CISCOVOD-87- Everstream type 161 with empty segment Index & mode fields

CSCuh42079

CISCOVOD-84-Orphan streams missing Everstream's last closing segment tag

CSCuh65878

Contents can't be deleted via CDSM-GUI in case of a CDSM/SSV setup

CSCuh66768

Active transmit/receive Bandwidth is not shows in graph ports NIC monitor page

CSCuh69101

Master Vault DB core due to statsd

CSCuh78227

AVSDB command \"db_shutdown\" does not work when partition is full

CSCuh80184

ISA StreamX: An extra PSE_END_SEG event is generated

CSCuh88403

Expired packages weren't deleted after master vault failover

CSCui05688

memmove() corruption with I to IDR conversion

CSCui41841

Handling memp_trickle error codes

CSCua91655

KDB at ServiceAddressManager process in a race condition

CSCui57706

mid-roll ad insertion issue that results in an error with multiple PMT

CSCud34091

GUI can't response and httpd usage to 100%

CSCud51267

Wrong content played due to GOID mismatch in avsdb

CSCud84008

LSC_DONE with incorrect LSC MODE build 2.5.7b13

CSCuh89418

H264 dummy p-frames support for pause

CSCuf88777

Multiple Trick Restriction are not updated properly in StreamService log

CSCud84173

LSC T mode transitioned incorrectly to TP mode - build 2.5.7b13

CSCud63864

QAM gateway preferences display wrong when add new stream group

CSCug89698

Provide controls to configure ARP parameters in CDSM/VVIM

CSCuh13565

Stop replication and resync from isa to non-isa vaults

CSCug87479

System Health Scan - AVS Monitoring script support in GUI

CSCug67386

Make particular server master

CSCug67376

Multiple checks before statsd failover

CSCug27401

getCBD calls to master vault do not indicate which VHO it is from

CSCtz60354

2.3.2 Tool to delete contents that does not have a corresponding package

CSCuh80139

Better Logging Mechanism in RTSP Server

CSCue28061

Parallel ingests not possible with CORBA interface

CSCuh17820

Multicultural VOD in MediaX

CSCug89796

Controlling REPLAY.db size to configurable limits

CSCui68463

AVSDB crash during resync of contentpendingdel table


Accessing Bug Tool kit

This section explains how to use the Bug Toolkit to search for a specific bug or to search for all bugs in a release.


Step 1 Go to http://tools.cisco.com/Support/BugToolKit.

Step 2 At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Toolkit 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, click the Search Bugs tab, enter the bug ID in the Search for Bug ID field, and click Go.

Step 4 To search for bugs in the current release, click the Search Bugs tab and specify the following criteria:

Select Product Category—Video.

Select Products—Cisco Content Delivery Engine Series.

Software Version—[3.2].

Search for Keyword(s)—Separate search phrases with boolean expressions (AND, NOT, OR) to search within the bug title and details.

Advanced Options—You can either perform a search using the default search criteria or define custom criteria for an advanced search. To customize the advanced search, click Use custom settings for severity, status, and others and specify the following information:

Severity—Choose the severity level.

Status—Choose Terminated, Open, or Fixed.

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

Choose 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. For example, if you want to view only new bugs in Prime Optical 9.5, choose only New.

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

Advanced—Check the Show only bugs containing bug details check box to view only those bugs that contain detailed information, such as symptoms and workarounds.

Modified Date—Choose this option to filter bugs based on the date when the bugs were last modified.

Results Displayed Per Page—Specify the number of bugs to display per page.

Step 5 Click Search. The Bug Toolkit displays the list of bugs based on the specified search criteria.

Step 6 To export the results to a spreadsheet:

a. In the Search Bugs tab, click Export All to Spreadsheet.

b. Specify the filename and location at which to save the spreadsheet.

c. Click Save. All bugs retrieved by the search are exported.

Search for Keyword(s)—Separate search phrases with boolean expressions (AND, NOT, OR) to search within the bug title and details.

Advanced Options—You can either perform a search using the default search criteria or define custom criteria for an advanced search. To customize the advanced search, click Use custom settings for severity, status, and others and specify the following information:

Severity—Choose the severity level.

Status—Choose Terminated, Open, or Fixed.

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

Choose 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. For example, if you want to view only new bugs in Prime Optical 9.5, choose only New.

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

Advanced—Check the Show only bugs containing bug details check box to view only those bugs that contain detailed information, such as symptoms and workarounds.

Modified Date—Choose this option to filter bugs based on the date when the bugs were last modified.

Results Displayed Per Page—Specify the number of bugs to display per page.

Step 7 Click Search. The Bug Toolkit displays the list of bugs based on the specified search criteria.

Step 8 To export the results to a spreadsheet:

a. In the Search Bugs tab, click Export All to Spreadsheet.

b. Specify the filename and location at which to save the spreadsheet.

c. Click Save. All bugs retrieved by the search are exported.

If you cannot export the spreadsheet, log into the Technical Support website at http://www.cisco.com/cisco/web/support/index.html or contact the Cisco Technical Assistance Center (TAC).

If the CDS is running an earlier software release, you must first upgrade to one of the supported releases before upgrading to Release 3.2.3.

For software upgrade procedures, see the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide.

Upgrading to Release 3.2.3

The supported upgrade paths are the following:

Release 2.5.2 to Release 3.2.3

Release 2.5.3 to Release 3.2.3

Release 2.5.5 to Release 3.2.3

Release 2.5.6 to Release 3.2.3

Release 2.5.7 to Release 3.2.3

Release 3.0.1 to Release 3.2.3

Release 3.0.2 to Release 3.2.3

Release 3.2.1 to Release 3.2.3

Release 3.2.2 to Release 3.2.3

If the CDS is running an earlier software release, you must first upgrade to one of the supported releases before upgrading to Release 3.2.3.

For software upgrade procedures, see the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide.

Upgrading to Cisco VDS-TV Release 3.2.3

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 CDS 3.2 Installation, Upgrade, and Maintenance Guide.

To upgrade a VDS device, do the following:


Step 1 Download the ISO image file (CDS-TV-3.2.3-.iso) and the cdsinstall-3.2.3 script from the Cisco Software Download website. For more information on downloading the software files, see the "Overview" chapter in the Cisco TV CDS 3.2 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 Streamer or Caching Node, select Offline (No Ingest & Fill) for a Vault.

d. Click Submit.

e. Ensure the VDS server has been 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.2.3 script to the VDS server.

# scp -p <user>@<remote_ip_address>:CDS-TV-3.2.3.iso /

# scp -p <user>@<remote_ip_address>:cdsinstall-3.2.3 /

 
   

Step 6 Run the cdsinstall script to upgrade the ISO image to Release 3.2.3.

# cd /root
# ./cdsinstall-3.2.3 /CDS-TV-3.2.3.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 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 Setup
 
   

Make 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
# mv /etc/rc.d/rc.local /etc/rc.d/rc.local.bak
# reboot
 
   

Step 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/null
 
   

Start 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 statsd

# /home/stats/statsd.bin -i <Server IP> -s <subnet mask> -d eth0
 
   

Step 11 For VDS servers, after the VDS server has been 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.2.3

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 CDS 3.2 Installation, Upgrade, and Maintenance Guide.

To downgrade a VDS device, do the following:


Step 1 Download the ISO image file (for example, CDS-TV-2.5.6.iso) and the cdsinstall script (for example, cdsinstall-2.5.6) for Release 2.5.2, 2.5.3, 2.5.5, 2.5.6, 3.0.1, 3.0.2, 3.2.1 or 3.2.2 from the Cisco software download website. For more information on downloading the software files, see the "Overview" chapter in the Cisco TV CDS 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.2.3").

Step 3 Log in to the VDS device 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 script to the /root directory and run the cdsinstall script to download the software. For example, the following commands are for downgrading to Release 2.5.6:

# scp -p <user>@<remote_ip_address>:CDS-TV-2.5.6.iso /

# scp -p <user>@<remote_ip_address>:cdsinstall-2.5.6 /
# cd /root
# ./cdsinstall-2.5.6 /CDS-TV-2.5.6.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
# reboot
 
   

Step 8 For VDS servers, after the VDS server has been came 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 Setup
 
   

Start 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
 
   

Move 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 has been 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. (see Step 7 in "Upgrading to Cisco VDS-TV Release 3.2.3" procedure).

Related Documentation

Refer to the following documents for additional information about the Cisco VDS-TV 3.2:

Cisco VDS-TV 3.2 ISA Software Configuration Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_2/configuration/isa_guide/tv_cds_3_2_isa_config.html

Cisco VDS-TV 3.2 RTSP Software Configuration Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_2/configuration/rtsp_guide/tv_cds_3_2_rtsp_config.html

Cisco VDS-TV 3.2 API Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_2/developer_guide/tv_cds_3_2_api_guide.html

Cisco VDS-TV 3.2 Installation, Upgrade, and Maintenance Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_2/installation_guide/TV_cds_3_2_install_upgrade_maint.html

Cisco VDS-TV 3.2.2 Release Note

http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_2/release_notes/TVCDS_RelNotes3_2_2.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


Note CDE460 is not applicable for Cisco VDS-TV 3.2.3 Release.


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 Cisco Content Delivery Engines

http://www.cisco.com/en/US/docs/video/cds/cde/regulatory/compliance/CDE_RCSI.html

Open Source Used in VDS-TV 3.2

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.