Installing and Upgrading the Cisco Video Surveillance Operations Manager (VSOM), Release 4.2

Table Of Contents

Installing and Upgrading the Cisco Video Surveillance Operations Manager (VSOM) Release 4.2.1

Contents

System Requirements

Installation Notes

Obtaining VSOM Software

Before You Install

Software Prerequisites

Installing VSOM

Configuring VSOM

Backing up VSOM

Restoring VSOM

Upgrading VSOM

Installing and Upgrading the Cisco Video Surveillance Operations Manager (VSOM) Release 4.2.1

---

May, 2010

Contents

This document provides the following information and instructions:

Installation and Initial Configuration

1. Verify minimum system requirements—System Requirements

2. Understand general installation information—Before You Install

3. Obtain the VSOM software—Obtaining VSOM Software

4. Perform pre-installation procedures—Before You Install

5. Install the VSOM software—Installing VSOM

6. Configure video repositories for archives and clips—Configuring VSOM

After Installation

7. (Recommended) Back up the VSOM configuration—Backing up VSOM, and Restoring VSOM

8. (As needed) Upgrade VSOM to a new software release—Upgrading VSOM

System Requirements

This section describes the requirements of the server and client systems on which you install VSOM.

The server must meet the following minimum requirements:

•Hardware

–Intel Celeron or Pentium, 1.7 GHz

– 1 GB DRAM

– 10 GB hard disk

•Operating System (one of the following):

–Red Hat Enterprise 4 Update 2 (RHEL4)

– SuSE Enterprise 9 Service Pack 3 (SLES9-SP3)

– SuSE Enterprise 10 Service Pack 1 (SLES10-SP1)

– SuSE Enterprise 10 Service Pack 1 64-bit (SLES10-SP1-64)

A client PC must meet the following minimum requirements:

•Hardware

–1.7 GHz Pentium III if running 1 video window

–1.7 GHz Pentium 4 if running 2 video windows

–3.2 GHz Pentium 4 with hyperthreading enabled if running 4 video windows

–1 GB DRAM

–ATI or Nvidia DirectX 9 compatible graphics interface. The graphics interface and Drivers must support DirectX Acceleration, Direct3D Acceleration, and AGP texture acceleration and have at least 128 MB of video memory.

•Operating system:

–Microsoft Windows XP SP2 (32-bit)

•Software:

–Microsoft Internet Explorer 6.0

–Microsoft DirectX 9.0c

Installation Notes

•Licenses are no longer required for VSOM, Cisco Video Surveillance Media Server (VSMS), and Cisco Video Surveillance Virtual Matrix (VSVM).

•On the Cisco Video Surveillance Management Console (VSMC) you can set the default server home page to VSMC or VSOM.

•The Pegasus MJPEG video decoder is installed automatically with the VSOM client.

•Cisco recommends that you use NTP source to maintain the correct time on the server. Configuring NTP should be done before video recording is configured. The hardware clock should be set to use UTC time and the appropriate time zone for the server. If you are using SUSE, you can use YaST to configure the server time.

•The performance of client devices can vary depending on client configuration and applications.

Obtaining VSOM Software

The VSOM software is available from

http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=281550158

You must log in to the Cisco website to access the software. Select the Cisco Video Surveillance Operations Manager software version for the appropriate for your Linux version.

Before You Install

Before you install VSOM, you must install all software pre-requisites.

Software Prerequisites

In addition to the default SUSE or Red Hat installation, the following software packages are required. Unless otherwise indicated, all packages are provided by the operating system, refer to the media from the operating system vendor to locate the necessary files.

•All platforms

– MySQL server 5.0.x

– MySQL client 5.0.x

– MySQL shared libraries 5.0.x

•SLES10-SP1-64

–MySQL shared libraries 5.0.x (32-bit version)

Installing VSOM

Copy the downloaded .zip file containing the VSOM software to the server and then follow these steps:

Procedure

---

Step 1 Extract the contents of the downloaded .zip file. Cisco recommends that you create a directory for the extracted contents.

shell> mkdir vsom-4.2.1

shell> unzip Cisco_VSOM-4.2.1-xx-xxxxx.zip -d vsom-4.2.1

Step 2 Verify that all files are present:

shell> cd vsom-4.2.1

shell> ls -1

Cisco_VSBase-6.2.1-xx-xxxx-i586.rpm

Cisco_VSOM-4.2.1-xx.i586.rpm

Cisco_VSTools-6.2.1-noarch.rpm

Step 3 Install the VSOM .rpm files:

shell> rpm -ivh Cisco_VSBase-6.2.1-xx-xxxxx-i586.rpm

shell> rpm -ivh Cisco_VSOM-4.2.1-xx-xxxxx-i586.rpm

shell> rpm -ivh Cisco_VSTools-6.2.1-noarch.rpm

Step 4 Create the VSOM database in MySQL:

shell> mysql -u root -p < /usr/BWhttpd/vsom/db/mysql-create-<version>.sql

Step 5 Enter the MySQL password when prompted. It is a best practice to set a MySQL user root password. If you need to set this password, perform the following steps:

a. Log in to the server console as the user "root."

b. Enter the following command:

shell> mysql -u root

The command prompt changes to mysql.

c. Enter the following commands, replacing new_password with the password you want to set:

mysql> SET PASSWORD FOR ''@'localhost' = PASSWORD("new_password");

mysql> SET PASSWORD FOR ''@'%' = PASSWORD("new_password");

---

Configuring VSOM

After you install VSOM, perform the following steps to use the Management Console (VSMC). The VSMC authentication information is as follows:

•Userid: root

•password: secur4u

Procedure

---

Step 1 Create the VSOM database in MySQL:

# mysql -u root -p < /usr/BWhttpd/vsom/db/mysql-create-<version>.sql

Enter the MySQL password when prompted. The default password is blank; press enter if there is no password.

Step 2 Open a web browser from a Windows PC and enter http://<server name/IP address>/vsmc.html.

Step 3 Click the Operations Manager link to access the VSOM configuration. You are prompted to authenticate.

Step 4 Click Update.

Step 5 Click Restart Server, Restart Now, and Verify.

---

Backing up VSOM

After configuring VSOM, you can back up the VSOM configuration.

Procedure

---

Step 1 In a web browser, open http://<Server HostName>/vsmc.html and navigate to the Encoding Server Backup on the Console page.

Step 2 Click Download.

Step 3 When prompted, save the .tar file to a secure directory.

The VSOM backup file is named VSOM_<ServerName>_backup_timestamp. For example, VSOM_PST_backup_20070327153851.tar.

---

Restoring VSOM

To restore the VSOM configuration, follow these steps:

---

Note This process is not intended for copying a configuration from VSOM server to another VSOM server.

---

Procedure

---

Step 1 Enter the following command to stop the server:

shell>  /etc/init.d/cisco stop 

Step 2 Uninstall the VSOM packages.

Step 3 Reinstall the VSOM packages.

Step 4 Perform the following steps to extract the backed up VSOM configuration data to the new server. This process extracts all necessary configuration files, including proxy, archive, and event data.

d. Locate the VSOM backup file that was created by using the VSOM console Backup command.

e. Use SSH to access the new VSOM server as the root user.

f. Copy the VSOM backup file from its current location to the VSOM server.

g. From the SSH command line, enter:

shell> tar -Pxvf <filename>.tar

For example:

shell> tar -Pxvf VSOM_PST_backup_20070327153851.tar 

Step 5 Restart the server.

Shell> /etc/init.d/cisco restart

Step 6 Open the Management Console and set the storage, PTZ, and other configuration information as needed.

---

Upgrading VSOM

To upgrade VSOM, follow these steps:

Procedure

---

Step 1 Extract the contents of the downloaded .zip file. Cisco recommends that you create a directory for the extracted contents.

shell> mkdir vsom-6.2.1

shell> unzip Cisco_VSOM-6.2.1-xx-xxxxx.zip -d vsom-6.2.1

Step 2 Verify that all files are present:

shell> cd vsom-4.2.1

shell> ls -1

Cisco_VSBase-6.2.1-xx-xxxx-i586.rpm

Cisco_VSOM-4.2.1-xx.i586.rpm

Cisco_VSTools-6.2.1-noarch.rpm

Step 3 Stop the VSOM service:

shell> /etc/init.d/cisco stop

Step 4 VSDrivers must be removed prior to uninstalling Cisco_VSOM. Uninstall all previous MS modules including some (but not all) of the following based on the previously installed version:

shell>  rpm -e Cisco_VSTools

shell>  rpm -e Cisco_VSOM

shell>  rpm -e Cisco_VSBase

If the Cisco Video Surveillance Operations Manager (VSOM) is installed you may get an error message when uninstalling the Cisco_VSBase package; to uninstall the Cisco_VSBase package run

shell>  rpm -e Cisco_VSBase --nodeps

This leaves the VSOM module installed.

Step 5 Run the following commands in the following order to install VSOM 6.2.1:

shell>  rpm -ivh Cisco_VSBase-6.2.1-xx-xxxxx-i586.rpm

shell>  rpm -ivh Cisco_VSOM-4.2.1-xx-xxxxx-i586.rpm

shell>  rpm -ivh Cisco_VSTools-6.2.1-noarch.rpm

Step 6 Upgrade the VSOM database in MySQL. Enter the MySQL password when prompted. The default password is blank; press enter if there is no password.

•If you are upgrading from Release 4.1.1 to Release 4.2.1, run the following commands in sequence to upgrade the VSOMdatabase:

shell> mysql -u root -p < /usr/BWhttpd/vsom/db/mysql-update-4.1.1-6_to_4.2.0.sql

shell> mysql -u root -p < /usr/BWhttpd/vsom/db/mysql-update-4.2.0-16_to_4.2.1.sql

•If you are upgrading from Release 4.0.0 to Release 4.2.1, run the following commands in sequence to upgrade the VSOM database:

shell> mysql -u root -p < /usr/BWhttpd/bas/db/mysql-update-4.0.0-23_to_4.1.0.sql

shell> mysql -u root -p < /usr/BWhttpd/bas/db/mysql-update-4.1.0-15_to_4.1.1.sql

shell> mysql -u root -p < /usr/BWhttpd/bas/db/mysql-update-4.1.1-6_to_4.2.0.sql

shell> mysql -u root -p < /usr/BWhttpd/bas/db/mysql-update-4.2.0-16_to_4.2.1.sql

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 and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© <year> Cisco Systems, Inc. All rights reserved.