Guest

Cisco Video Surveillance Manager

Installing and Upgrading Cisco Video Surveillance Manager (VSM) Release 6.3

  • Viewing Options

  • PDF (202.6 KB)
  • Feedback
Installing and Upgrading Cisco Video Surveillance Manager Release 6.3

Table Of Contents

Installing and Upgrading Cisco Video Surveillance Manager Release 6.3

Overview

System Requirements and Recommended Baseline Configuration

Server

Client PC

Installation Notes

Preparing Your System to Install VSM

Installing MySQL

Installing Dependencies for VSMS

Installing VSM

Configuring VSM

Backing Up and Restoring VSOM and VSMS

Backing up VSOM

Backing up VSMS

Restoring VSOM

Restoring VSMS

Upgrading VSM

Upgrading the VSM Software

Upgrading IP Camera Firmware


Installing and Upgrading Cisco Video Surveillance Manager Release 6.3


Overview

This document provides information about installing Cisco Video Surveillance Manager (VSM), which includes Cisco Video Surveillance Operations Manager (VSOM), Cisco Video Surveillance Media Server (VSMS), Cisco Video Surveillance Encoding Server (VSES), and Cisco Video Surveillance Virtual Matrix (VSVM).


Note The software build or version numbers that are included in the code samples in this document may differ slightly from the versions that you have on your system.


This document includes these topics:

System Requirements and Recommended Baseline Configuration

Installation Notes

Preparing Your System to Install VSM

Installing VSM

Configuring VSM

Backing Up and Restoring VSOM and VSMS

Upgrading VSM

System Requirements and Recommended Baseline Configuration

The following sections describes the requirements for the server on which you install VSM, and describes the requirements and recommended baseline configuration for the client PC that you use to access video on VSM.

Server

Client PC

Server

The server must meet the following minimum requirements:

Operating system (one of the following):

Red Hat Enterprise Linux (RHEL) 4.2

SuSE Enterprise 9 Service Pack 3 (SLES9-SP3)

SuSE Enterprise 10 Service Pack 1 (SLES10-SP1)

Recommended; preinstalled on the Cisco Physical Security Multiservices Platform

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

Hardware—Cisco Physical Security Multiservices Platform. For additional information, go to this URL:

http://www.cisco.com/en/US/products/ps10823/tsd_products_support_series_home.html

Client PC

This section provides information about the configuration of a dedicated client PC. It includes baseline recommendations, which are designed to ensure that a client PC provides the desired quality of the monitoring experience.

The performance of a client PC on which you display multiple windows of surveillance video depends on many variables, including, CPU, memory, bus speeds, graphics card capabilities, and other applications that are installed on the client PC. The quality of the monitoring experience also can vary depending on the type of system used, the number of video streams being rendered, and the characteristics of those streams.

This section also describes the minimum requirements for any client PC. A client PC must meet these requirements so that it can install and run the VSM AXClient and display a single video stream.

For related information, see Video Surveillance Monitoring Workstation Recommended Baseline Specification, which is available here:

http://www.cisco.com/en/US/products/ps9153/prod_technical_reference_list
.html

Minimum System Requirements

Operating system—Microsoft Windows XP SP3 (32-bit) with DirectX 9.0 or later

Browser—Microsoft Internet Explorer 7.0, 8.0

Network connection—Gigabit Ethernet (GigE)

VMR—Required for the following features:

High definition video

Motion configuration with motion configuration rectangles

Digital PTZ

Hue, saturation, luminosity, contrast controls

Alpha blending of the VMR toolbar

CVA clip playback

Recommended Baseline Specification

Hardware

CPU—Intel 950 i7 Core, 3.07 GHz

Memory—6 GB DDR3

Graphics—NVIDIA GeForce GTX260 896MB PCIe

Display configuration—Single monitor or extended mode dual monitors

Installation Notes

For all installations, the host name must be modified. Before you install VSM, edit the /etc/hosts file and change

127.0.0.1               VSM-RHEL4U2 localhost

to

127.0.0.1                localhost

Cisco strongly recommends that you use an uninterruptible power supply (UPS) with the servers in your VSM deployment and ensure that each UPS operates correctly.

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

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.

The permissions for each media repository used by VSM (both for archives and server-side clips) should be set to 755 using the command chmod 755 directory. The user and group ownership for the repository directory should be set to nobody using the command chown nobody.nobody directory.

Preparing Your System to Install VSM

Before you install VSM, you must install MySQL and the appropriate dependencies for VSMS, as described in the following sections:

Installing MySQL

Installing Dependencies for VSMS

Installing MySQL

VSOM requires MySQL 5.0.x, which is included with SLES10 SP1. For other Linux distributions, go to the MySQL website to obtain the software. The MySQL server, client, and shared libraries are required. There are also additional package dependencies, as listed in the following procedure.


Note You must install the 32-bit version of the MySQL shared libraries, even if you are running a 64-bit operating system (such as SLES 10, SP1, 64 bit). You do not need to install the 32-bit versions of MySQL server or client packages.


To install MySQL, follow these steps:

Procedure


Step 1 Install the following RPMs:

MySQL-server 5.0.x

MySQL-client 5.0.x

MySQL-shared 5.0.x

Step 2 Install the following additional dependencies, depending upon your operating system:

RHEL 4 Update 2 (4.2):

perl-DBI

SLES10 SP1:

perl-DBI

perl-DBD

SLES10 SP1 (64-bit):

MySQL-shared (32-bit)

perl-DBI

perl-DBD

Step 3 Start the MySQL database by running the following command:

shell> service mysql start

Step 4 Set the MySQL database to start on boot by running the following command:

shell> chkconfig mysql on 


Installing Dependencies for VSMS

Before installing VSMS, you must install the following RPMs. For information about installing the RPMs, see your Linux documentation.

SLES9 SP3:

libelf-0.8.5-47.2.i586.rpm

db1-1.85-101.2.i586.rpm

sysstat-6.0.2-16.19.i586.rpm

SLES10 SP1 (32-bit and 64-bit):

libelf-0.8.5-47.2.i586.rpm

db1-1.85-101.2.i586.rpm

sysstat-6.0.2-16.19.i586.rpm

RHEL4 Update 2:

compat-db

perl-Net-SNMP

perl-Socket6

perl-Crypt-DES

Installing VSM

This section describes how to install VSM.


Note For information about upgrading VSM, see the "Upgrading VSM" section.


Procedure


Step 1 Take these actions to obtain the VSM software:

a. Go to the following URL:

http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=281522804

b. Choose Physical Security > Network-Centric Video Surveillance.

c. Download the .zip file for each VSM product that you want to install.

Step 2 Extract the contents of the downloaded .zip files into a directory that you create. The following example shows the commands if you are installing all VSM products.

shell> mkdir vsm-6.3.0
shell> unzip Cisco_VSOM-6.3.0-xx-xxxxx.zip -d vsm-6.3.0
shell> unzip Cisco_VSMS-6.3.0-xx-xxxxx.zip -d vsm-6.3.0
shell> unzip Cisco_VSES-6.3.0-xx-xxxxx.zip -d vsm-6.3.0
shell> unzip Cisco_VSVM-6.3.0-xx-xxxxx.zip -d vsm-6.3.0

Step 3 Verify that all required files are present for the products that you want to install (see Table 1; "Yes" indicates that a file is required).

Table 1 RPM Files Required for VSM Products 

Product
VSOM
VSMS
VSES
VSVM

Cisco_VSBase-6.3.0-xx-xxxxx.rpm

Yes

Yes

Yes

Yes

Cisco_VSRecorder-6.3.0-xx-xxxxx.rpm

Yes

Yes

Yes

Cisco_VSMS-6.3.0-xx-xxxxx.rpm

Yes

Yes

Yes

Cisco_VSES-6.3.0-xx-xxxxx.rpm

 

Yes

 

Cisco_VSDrivers-6.3.0-xx-xxxxx.rpm

Yes

Yes

Yes

Cisco_BWT-6.3.0-xx-xxxxx.rpm

Yes

Yes

Yes

Cisco_VSDocs-6.3.0-xx-xxxxx.rpm

Yes

Yes

Yes

Yes

Cisco_VSVM-6.3.0-xx-xxxxx.rpm

Yes

Cisco_VSOM-6.3.0-xx-xxxxx.rpm

Yes

Cisco_Tomcat-6.0.18-x.rpm

Yes

Yes

Yes

Yes

Cisco_VSOM_BE-6.3.0-xx-xxxxx.rpm

Yes

Cisco_VSTools-6.3.0-xx-xxxxx.rpm

Yes

Yes

Yes

Yes

jre-6u17-linux-i586.rpm

Yes

Yes

Yes


Step 4 For VSOM, VSMS, and VSES, Install the JRE RPM by running the following command from the folder to which you extracted the jre-6u17-linux-i586.rpm file:

shell> rpm -ivh jre-6u17-linux-i586.rpm

The JRE is installed under the /usr/java directory (for example, /usr/java/jre1.6.0_17).

Step 5 Run the following commands to verify that JRE is installed correctly:

shell> cd /usr/java
shell> ls -l java

The output should be a symbolic link that includes the following at the end:

java -> /usr/java/jre1.6.0_17

If a symbolic link does not include this text or does not appear at all, use these commands to resolve this issue:

shell> rm -rf java
shell> ln -s jre1.6.0_17 java 

Step 6 Install the Cisco .rpm files from the directory using the rpm -ivh command. Run the command for each .rpm file that is included with your product. The appropriate zip files are provided based on the Table 1.

shell> rpm -ivh Cisco_*.rpm

For example:

shell> rpm -ivh Cisco_VSMS-6.3.0-xx-xxxxx.rpm

Step 7 If you are installing VSOM, create the VSOM database in MySQL, and enter the MySQL password when prompted.

shell> bash /usr/BWhttpd/vsom_be/db/database_create.sh

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 'root'@'localhost' = 
PASSWORD("new_password");
mysql> SET PASSWORD FOR 'root'@'%' = PASSWORD("new_password");

Step 8 Click Restart Server, Restart Now, and then Verify.


Note You can set the default home page from the Management Console. For instructions, see the "Using the VSM Management Console" chapter in Cisco Video Surveillance Manager User Guide.



Configuring VSM

To configure each installed VSM product using the Video Surveillance Management Console (VSMC), follow these steps.

Procedure


Step 1 Open a web browser from a Windows PC and enter the following:

http://server/vsmc.html

where server is the IP address or host name of the VSM host.


Note The system prompts you to log in the first time you access a page to modify the configuration. The default user name is root and the default password is secur4u.


Step 2 For VSOM:

a. Click the Operations Manager link to access the VSOM configuration.

b. Choose Change the default home page to VSOM.

c. Click Update.

Step 3 For VSMS:

a. Click the Media Server link to access the VSMS configuration.

b. Check the Local Archives Repositories check box for recording archives.

c. Choose a local BWM/X clip repository for storing BWM and BWX clips.

d. Choose one or more backup repositories.

e. Click Update.

Step 4 Click Restart Server, Restart Now, and then Verify.


Backing Up and Restoring VSOM and VSMS

After configuring VSM, you can back up the VSOM database and configuration and the VSMS configuration. Make sure to back up the configuration before upgrading. For related information, see Cisco Video Surveillance Manager User Guide.

The following sections describe how to back up and restore VSOM and VSMS:

Backing up VSOM

Backing up VSMS

Restoring VSOM

Restoring VSMS

Backing up VSOM

To back up VSOM, follow these steps:

Procedure


Step 1 Open a web browser from a Windows PC and enter the following:

http://server/vsmc.html

where server is the IP address or host name of the VSM host.


Note The system prompts you to log in the first time you access a page to modify the configuration. The default user name is root and the default password is secur4u.


Step 2 Click the Operations Manager Backup link on the Console page.

Step 3 Click Download.


Note If a MySQL password is defined, you must enter the password before you can click Download.


Step 4 When prompted, save the .gz file to a secure directory.

The VSOM backup file is named VSOM_Server_backup_Timestamp. Server is the host name or IP address of the VSOM host from which you are running the backup. Timestamp is the date and time at which you initiated the backup. For example, VSOM_PST_backup_20100227153851.tar.gz.


Backing up VSMS

To back up VSMS, follow these steps:

Procedure


Step 1 Open a web browser from a Windows PC and enter the following:

http://server/vsmc.html

where server is the IP address or host name of the VSM host.


Note The system prompts you to log in the first time you access a page to modify the configuration. The default user name is root and the default password is secur4u.


Step 2 Click the Media Server Backup link on the Console page.

Step 3 Click Download.

Step 4 When prompted, save the .gz file to a secure directory.

The VSMS backup file is named VSMS_Server_backup_timestamp. Server is the host name or IP address of the VSOM host from which you are running the backup. Timestamp is the date and time at which you initiated the backup. For example, VSMS_PST_backup_20100227153851.tar.gz.


Restoring VSOM

Restoration is needed only if a system failure occurs. To restore the VSOM configuration, perform the following steps.


Note This process is not intended for copying a configuration from VSOM server to another VSOM server. All of the feeds, archives, and events will work in VSOM only if these configurations are available in VSMS as well.


Procedure


Step 1 Enter the following command to stop the server:

shell> /etc/init.d/cisco stop 

Step 2 Uninstall the VSOM packages (see Table 1 for the list of packages).

Step 3 Reinstall the VSOM packages (see Table 1 for the list of 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.

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

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

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

d. From the SSH command line, enter the following command, where filename is the name of the backup file, and must include the .tar.gz extension:

shell> /usr/BWhttpd/bin/vsom_backup_restore filename

For example:

shell> /usr/BWhttpd/bin/vsom_backup_restore 
VSOM_psbu-dev03_backup_20100128164352.tar.gz

Step 5 Restart the server.

Shell> /etc/init.d/cisco restart


Restoring VSMS

Restoration is needed only if a system failure occurs. To restore the VSMS configuration, perform the following steps.


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


Procedure


Step 1 Enter the following command to stop the server:

shell> /etc/init.d/cisco stop

Step 2 Uninstall the VSMS packages (see Table 1 for the list of packages).

Step 3 Reinstall the VSMS packages (see Table 1 for the list of packages).

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

a. Locate the VSMS backup file that was created by using the Media Server Backup command.

b. Use SSH to access the new VSMS server as the root user.

c. Copy the VSMS backup file from its current location to the VSMS server.

d. Use the following command to extract the backup file, where filename is the name of the backup file, and must include the .tar.gz extension:

shell> gunzip filename.tar.gz

e. From the SSH command line, enter:

shell> tar -Pxvf filename.tar

For example:

shell> tar -Pxvf VSMS_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 VSM

This section describes how to upgrade VSM. Upgrading includes these general steps:

1. Upgrade the VSM software

2. Upgrade IP camera firmware

The following sections describe these steps in more detail:

Upgrading the VSM Software

Upgrading IP Camera Firmware

Upgrading the VSM Software

To upgrade VSM, follow these steps:

Procedure


Step 1 Back up the VSOM database and configuration and the VSMS configuration. For instructions, see the "Backing Up and Restoring VSOM and VSMS" section.

Step 2 Stop the Cisco service:

shell> /etc/init.d/cisco stop

Step 3 Uninstall all existing versions of Java:

a. Check for existing Java RPMs by using the following commands:

shell> rpm -qa | grep j2sdk
shell> rpm -qa | grep jdk
shell> rpm -qa | grep java
shell> rpm -qa | grep jre

b. If there are any RPMs, remove them by using the following command, where java_rpm refers to each RPM that was returned in the previous step:

shell> rpm -e java_rpm

Step 4 Use the following commands to verify that there are no versions of Java RPMs remaining on the system:

shell> rpm -qa | grep j2sdk
shell> rpm -qa | grep jdk
shell> rpm -qa | grep java
shell> rpm -qa | grep jre

Step 5 Use the following command to obtain a list of older Cisco .rpm files to uninstall:

shell> rpm -qa | grep Cisco

Step 6 Uninstall each RPM by using the following command, where rpmname is the name of the package:

shell> rpm -e rpmname

Step 7 Follow the instructions in Step 1 through Step 6 in the "Installing VSM" section.

Step 8 If you are upgrading VSOM, update the VSOM database in MySQL, entering the MySQL password when prompted.

shell> bash /usr/BWhttpd/vsom_be/db/database_update.sh

Step 9 Open a browser and log in to the Management Console at http://server/vsmc.html, where server is the IP address or host name of the VSM host.

a. Click the Restart Server link under Monitoring at the left side of the console window.

b. Click Restart Now.


Upgrading IP Camera Firmware

After you perform the VSM upgrade, upgrade the firmware on your Cisco IP cameras, if needed. VSM 6.3 is compatible with the following IP camera versions:

Standard definition IP cameras—Firmware release 2.1.2 or later. Firmware release 2.1.5 or later is recommended.

High definition IP cameras— Firmware release 1.0.3 or later. Firmware release 1.1.0 or later is recommended.

To update IP camera firmware, follow these guidelines:

Upgrading firmware on a standard definition camera from release 1.x to release 2.x requires the Video Surveillance IP Camera Utility. You can download this utility by going to Cisco.com and choosing Support > Download Software > Physical Security and Building Systems > Physical Security -> Video Surveillance IP Cameras > Cisco Video Surveillance 2500 Series IP Cameras > Cisco Video Surveillance 2500 IP Camera > Video Surveillance IP Camera Utility. For related information, see your IP camera documentation.

Upgrading firmware on a standard definition camera from release 2.x to release 2.x can be performed by using the Camera Firmware Upgrade feature in the VSM Management Console. For instructions, see the "Using the VSM Management Console" chapter in Cisco Video Surveillance Manager User Guide.

Upgrading firmware on a high definition camera HD can be performed by using the Camera Firmware Upgrade feature in the VSM Management Console. For instructions, see the "Using the VSM Management Console" chapter in Cisco Video Surveillance Manager User Guide.