Installing Cisco Video Assurance Management Solution 3.0
This chapter contains the following sections:
•Before You Install
•Install Cisco Info Center
•Starting Cisco Info Center
•Upgrading to Cisco VAMS 3.0
Before You Install
This chapter describes the procedure for a new installation of Cisco VAMS 3.0.
Note Important: The procedures in this chapter are for a new installation of Cisco VAMS 3.0 and the Cisco Info Center components. Installing the Cisco Info Center components provided with Cisco VAMS where there is an existing Cisco Info Center installation might result in overwriting rules files and existing configuration settings. If you are installing VAMS 3.0 in an existing Cisco Info Center environment, please contact Cisco Advanced Services for assistance
Note You must meet all preinstallation tasks listed in Chapter 2, "Preinstallation" before continuing. Complete these tasks before installing the Cisco VAMS 3.0 software package.
Release Notes
Before you install Cisco VAMS 3.0, see the Release Notes for Cisco Video Assurance Management Solution, 3.0, which are available online on Cisco.com:
http://www.cisco.com/en/US/products/ps9518/prod_release_notes_list.html
The release notes contain important information about system requirements, installation and upgrade, and open and resolved caveats.
Software on the Installation Media
The Cisco VAMS 3.0 software package contains two DVDs:
• DVD 1—Cisco Video Assurance Manager 3, Extension to CIC - Disk 1.
This DVD contains the following file:
VAMS-3.0bg-001
• DVD 2—Cisco Video Assurance Manager 3, Extension to CIC - Disk 2.
This DVD contains the following file:
VAMS-3.0bg-002
Install Cisco Info Center
The the VAMS 3.0 installation DVD contains the Cisco Info Center software. Install the hardware and software for the Cisco Info Center/Netcool on dedicated servers.
The Cisco Info Center software provided with Cisco VAMS 3.0 includes:
•Netcool Omnibus—Includes the Tivoli Netcool Object Server, probes, gateways, desktop tools, and administration tools.
•TBSM—Tivoli Business Service Manager (TBSM) is the high-level interface used to view network services, including the devices in your Cisco VAMS 3.0 installation. It allows you to launch an event list that includes Cisco VAMS 3.0 alerts, and also allows you to launch CMM to perform additional monitoring functions.
•Netcool Web GUI—Tivoli Netcool Web GUI is the web-based event viewer that provides event views in Tivoli Business Service Manager (TBSM).
•Impact—Netcool/Impact is a set of runnable server components that work together to provide enhanced event management processing and integration functionality for the Netcool suite of products.
•Netcool Knowledge Library (NcKL)—Includes the Tivoli Netcool probes and the Netcool Knowledge Library.
This section contains:
•Obtain the IP Address of the CMM Server
•Prepare the Server
•Install and Customize the Software
Obtain the IP Address of the CMM Server
Make a note of the IP address of the CMM Server. You are prompted to enter the CMM IP addresses during product customization.
Prepare the Server
Complete these steps to install the Cisco Info Center software:
Step 1 On the host where you want to install the Cisco Info Center components, complete these steps install the GNU Compiler Collection (GCC) the as required for your specific system.
a. Create a local/src directory under the /usr directory:
mkdir -m 777 /usr/local/src
b. Obtain the GCC software, for example, GCC 3.4.6 (gcc-3.4.6-sol10-sparc-local).
You can download the Sun software from www.sunfreeware.com and other sites.
c. Download the software packages and perform a package add to add the packages.
d. Obtain the libiconv software for your host, for example libiconv-1.9.2-sol9-sparc-local (or the version for Solaris 10).
You can download the libiconv software from www.sunfreeware.com and other sites.
Step 2 Complete these steps to create a non-root user, for example, a user with the ID ncoadmin:
a. Enter the following command to create an ncoadmin directory:
b. As the root user, enter the following command:
# useradd -m -s /bin/bash -d /export/home/ncoadmin ncoadmin
You are prompted to enter a password for the administrative user:
c. Enter a password. For example, enter:
d. When prompted to verify the password, verify it:
# Re-enter new Password:ncoadmin
Step 3 As the root user, create a Netcool directory for CIC and give the ncoadmin user permissions:
chown ncoadmin:other tivoli
chown ncoadmin:other netcool
drwxr-xr-x 2 ncoadmin other 512 Apr 30 15:46 netcool
chown ncoadmin:other ncoadmin
drwxrwxrwx 2 ncoadmin other 512 Apr 26 18:26 ncoadmin
Step 4 As the root user, Create a .bash_profile file for the user in the home directory for the user.
e. Add the following lines to the .bash_profile file for the user:
MANPATH=/opt/SUNWspro/man
PATH=${PATH}:/usr/local/bin:/usr/sbin
NCHOME=/opt/vams/tivoli/netcool
NC_RULES_HOME=$NCHOME/omnibus/probes/solaris2/rules
LD_LIBRARY_PATH=/usr/local/lib
NCLICENSE=/opt/vams/tivoli/netcool/license
NETCOOL_LICENSE_FILE=27000@localhost
TIPHOME=/opt/vams/tivoli/tip
TBSMHOME=/opt/vams/tivoli/tbsm
export PATH MANPATH NCHOME NC_RULES_HOME LD_LIBRARY_PATH NCLICENSE
NETCOOL_LICENSE_FILE
f. Save the .bash_profile file.
Step 5 Ensure that the ncoadmin user sources the .bash_profile file:
Step 6 Alternatively, the user may log out and then back in to create the changes.
Step 7 As the su user, copy the files on the two Cisco VAMS 3.0 distribution DVDs to a temporary directory, for example:
# cp VAMS-3.0b6-001.tar /tmp/
# cp VAMS-3.0b6-002.tar /tmp/
Step 8 Issue the following command to combine the two files into one tar file:
cat /tmp/VAMS-3.0b6-00* > VAMS-3.0b6.tar
Step 9 Untar the combined file:
For example, enter
tar -xf /opt/VAMS-3.0b6.tar
The extraction process creates an image directory and extracts the Cisco Info Center distribution files to the directory. Messages similar to the following appear:
x VAMS-3.0-image, 0 bytes, 0 tape blocks
x VAMS-3.0-image/images, 0 bytes, 0 tape blocks
x VAMS-3.0-image/images/omnibus, 0 bytes, 0 tape blocks
x VAMS-3.0-image/images/omnibus/Netcool-OMNIbus-7.2-Solaris.tar, 181621248 bytes, 354729
tape blocks
x VAMS-3.0-image/images/webtop, 0 bytes, 0 tape blocks
x VAMS-3.0-image/images/webtop/ncw-2.1.59-solaris2.tar, 248013312 bytes, 484401 tape
blocks
x VAMS-3.0-image/images/tbsm, 0 bytes, 0 tape blocks
x VAMS-3.0-image/images/tbsm/TBSM-v4.1.1-Solaris.tar, 1669099520 bytes, 3259960 tape
blocks
x VAMS-3.0-image/images/impact, 0 bytes, 0 tape blocks
x VAMS-3.0-image/images/impact/NetcoolImpact-Solaris_V4.0.tar, 513187840 bytes, 1002320
tape blocks
x VAMS-3.0-image/images/ncsm, 0 bytes, 0 tape blocks
x VAMS-3.0-image/images/ncsm/ncsm-1.3-solaris2.tar, 92426240 bytes, 180520 tape blocks
Step 10 Change the permissions for the ncoadmin directory and the files in the directory to ncoadmin:other:
# chown -R ncoadmin:other VAMS-3.0b1
drwxr-xr-x 5 ncoadmin other 512 Apr 23 00:21 VAMS-3.0b1
You will see two shell script files listed:
•install_vams.sh—Installation script for Cisco VAMS 3.0.
•customize_vams.sh—Customization script for Cisco VAMS 3.0.
You are now ready to install the software.
Install and Customize the Software
Complete these steps to install and customize the software:
1. Run the install_vams.sh script to install the software.
2. Copy CSV files containing CMM Address Management Data to the following directory:
VAMS_IMAGE_DIR/custom/impact
For detailed information on setting up the CSV files for Cisco Info Center see:
•Configuring Channel Mapping in Cisco Info Center, page 5-43.
3. Run the customize_vams.sh script to enable additional customization
Note These steps must be completed by the ncoadmin user or another non-root user who is configured as an ncoadmin user.
Step 1 Log in as ncoadmin or obtain su access for a non-root user who has ncoadmin priviliges.
Step 2 Start the Cisco Info Center installation script:
The script starts and prompts you to select the components to install:
====================================================
====================================================
====================================================
Step 3 Enter s to select all products.
The products are marked as SELECTED:
====================================================
====================================================
====================================================
Step 4 Enter i to install all of the selected products.
Messages display indicating the progress of the installation.
Note If you want to install the components separately, then you must the components in this order: Impact, Omnibus, TBSM, Web GUI, NcKl.
You are prompted to customize the products:
Would you like to customize the products? [y]:
Note Before you proceed with the customization process, make sure that you have copied the .csv files for the CMM address management database from the CMM server to the VAMS_IMAGE_DIR/custom/impact directory on the CIC server.
Step 5 Enter n to exit the installation script.
Step 6 Copy the Cisco Info Center CSV files from CMM to the following directory on the Cisco Info Center host:
VAMS_IMAGE_DIR/custom/impact
For detailed information on setting up the CSV files for Cisco Info Center see:
–Configuring Channel Mapping in Cisco Info Center, page 5-43.
Step 7 Start the VAMS customization script:
The product customization menu appears:
====================================================
Product Customization Menu
====================================================
====================================================
Step 8 Enter s to select all of the products.
The products are marked as SELECTED.
====================================================
Product Customization Menu
====================================================
====================================================
Step 9 Enter c to start customization.
The installation script customizes the products and displays informational messages similar to the following:
DEBUG: 04/30/10 22:49:37 - Customizing omnibus
DEBUG: 04/30/10 22:49:37 - Updating ObjectServer SQL files
DEBUG: 04/30/10 22:49:55 - Adding TBSM fields to Object Server
Netcool/OMNIbus Object Server - Version 7.3.0
(C) Copyright IBM Corp. 1994, 2007
Server 'NCOMS' initialised - entering RUN state.
DEBUG: 04/30/10 22:50:19 - Adding Advance Correlation fields to the Object Server
DEBUG: 04/30/10 22:50:19 - Update Generic Clear to the Object Server
DEBUG: 04/30/10 22:50:20 - Alter problem events to the Object Server
DEBUG: 04/30/10 22:50:20 - Adding users to the Object Server
DEBUG: 04/30/10 22:50:20 - Adding VAMS triggers
DEBUG: 04/30/10 22:50:20 - Finished updating NCOMS
DEBUG: 04/30/10 22:50:20 - Update objectserver fields
DEBUG: 04/30/10 22:50:22 - Customizing impact
DEBUG: 04/30/10 22:50:22 - Searching for libgcc_s.so
DEBUG: 04/30/10 22:50:22 - Found libgcc_s.so in /usr/local/lib
DEBUG: 04/30/10 22:50:22 - Impact Server running already
DEBUG: 04/30/10 22:50:22 - Setting NCHOME in CMM.ds datatype
DEBUG: 04/30/10 22:50:22 - Setting NCHOME in NCI_server.props
DEBUG: 04/30/10 22:50:22 - Setting NCHOME in NCI_versioncontrol.props
DEBUG: 04/30/10 22:50:22 - Setting HOSTNAME in nameserver.props
DEBUG: 04/30/10 22:50:22 - Setting HOSTNAME in NCI_server.props
DEBUG: 04/30/10 22:50:22 - Setting HOSTNAME in NCI_emailsender.props
DEBUG: 04/30/10 22:50:22 - Setting HOSTNAME in emailsender.props
DEBUG: 04/30/10 22:50:22 - Setting HOSTNAME in defaultobjectserver.ds
DEBUG: 04/30/10 22:50:22 - Setting HOSTNAME in NCI_wsadmin.props
DEBUG: 04/30/10 22:50:22 - Starting nci_import
DEBUG: 04/30/10 22:52:15 - NCI Import completed successfully
DEBUG: 04/30/10 22:52:15 - Adding CSV files for CMM policy
DEBUG: 04/30/10 22:52:15 - Shutting down Impact Server
DEBUG: 04/30/10 22:53:56 - Starting Impact Server
DEBUG: 04/30/10 22:56:03 - Customizing TBSM
DEBUG: 04/30/10 22:56:03 - Starting TBSMProfile for Data Server
DEBUG: 04/30/10 22:57:28 - Starting TIPProfile for Dashboard Server
DEBUG: 04/30/10 22:58:05 - Updating TBSM Service Details page properties
DEBUG: 04/30/10 22:58:05 - Updating TBSM Event Broker properties
DEBUG: 04/30/10 22:58:05 - Install TBSM Service Templates
DEBUG: 04/30/10 22:58:50 - Stopping TIP Server
DEBUG: 04/30/10 22:59:50 - Stopping TBSM Dashboard Server
DEBUG: 04/30/10 23:00:50 - Starting TBSMProfile for Data Server
DEBUG: 04/30/10 23:02:10 - Starting TIPProfile for Dashboard Server
DEBUG: 04/30/10 23:03:59 - Customizing Web GUI
DEBUG: 04/30/10 23:03:59 - Update hostname in the datasources file
DEBUG: 04/30/10 23:03:59 - Registering CGI tools
You are prompted to enter the IP address of the CMM server:
Enter the IP address of the CMM Server: <X.X.X.X>
Step 10 Enter the IP address of the CMM server.
Messages similar to the following appear:
DEBUG: 04/30/10 23:10:48 - Install Page Import/Export Utility
DEBUG: 04/30/10 23:10:48 - Copied tree template to
/opt/vams/tivoli/tip/profiles/TBSMProfile/installedApps/TBSMCell/tbsm.ear/sla.war/av/xmlco
nfig
DEBUG: 04/30/10 23:10:48 - Install Custom VAMS pages
DEBUG: 04/30/10 23:10:53 - Cleaning up /opt/vams/tivoli/tip/output
DEBUG: 04/30/10 23:10:53 - Stopping TIP Server
DEBUG: 04/30/10 23:11:53 - Stopping TBSM Dashboard Server
DEBUG: 04/30/10 23:12:51 - Starting TBSMProfile for Data Server
DEBUG: 04/30/10 23:14:12 - Starting TIPProfile for Dashboard Server
DEBUG: 04/30/10 23:16:00 - Updated VAMS Rules files
Installation of the Cisco Info Center components is now complete. All processes are started automatically after installation.
Step 11 Enter the following command to verify that the processes are running:
-bash-3.00$ ps -ef | grep /opt/vams
You should see output similar to the following:
ncoadmin 10139 10138 0 17:02:36 pts/2 0:00 /opt/vams/tivoli/tbsm/pgsql8/bin/postmaster -B
2000 -N 20 -i -p 5435 -c transfo
/opt/vams/tivoli/tbsm/pgsql8/bin/postmaster -B 2000 -N 20 -i -p 5435 -c transfo
ncoadmin 4247 10134 0 23:14:05 pts/2 0:00 /opt/vams/tivoli/tbsm/pgsql8/bin/postmaster -B
2000 -N 20 -i -p 5435 -c transfo
ncoadmin 4249 10134 0 23:14:07 pts/2 0:00 /opt/vams/tivoli/tbsm/pgsql8/bin/postmaster -B
2000 -N 20 -i -p 5435 -c transfo
ncoadmin 1515 1 0 22:49:56 pts/2 0:11
/opt/vams/tivoli/netcool/omnibus/platform/solaris2/bin/nco_objserv
ncoadmin 10138 10134 0 17:02:36 pts/2 0:00 /opt/vams/tivoli/tbsm/pgsql8/bin/postmaster -B
2000 -N 20 -i -p 5435 -c transfo
ncoadmin 10134 1 0 17:02:36 pts/2 0:00 /opt/vams/tivoli/tbsm/pgsql8/bin/postmaster -B 2000
-N 20 -i -p 5435 -c transfo
ncoadmin 6250 1521 0 23:28:05 pts/2 0:00 grep /opt/vams
ncoadmin 10137 10134 0 17:02:36 pts/2 0:01 /opt/vams/tivoli/tbsm/pgsql8/bin/postmaster -B
2000 -N 20 -i -p 5435 -c transfo
ncoadmin 4192 1 0 23:12:59 pts/2 2:14 /opt/vams/tivoli/tip/java/bin/java
-XX:MaxPermSize=256m -Dwas.status.socket=371
ncoadmin 4291 1 0 23:14:20 pts/2 2:27 /opt/vams/tivoli/tip/java/bin/java
-XX:MaxPermSize=256m -Dwas.status.socket=371
ncoadmin 4487 10134 0 23:15:37 pts/2 0:00 /opt/vams/tivoli/tbsm/pgsql8/bin/postmaster -B
2000 -N 20 -i -p 5435 -c transfo
ncoadmin 1959 1 0 22:54:05 pts/2 3:19
/opt/vams/tivoli/netcool/eWAS/java/jre/bin/sparcv9/java -Dwas.status.socket=367
Step 12 Complete these steps to populate the VAMS services in TIP/TBSM
•To have the services populated automatically, log in to TIP/TBSM and wait for events to come in. This will cause the services to populate automatically.
–Go to the URL for the TBSM application:
https://tip_server_address:16316/ibm/console/logon.jsp
where tip_server_address is the IP address of the TIP/TBSM serve
–Navigate to the Video Assurance Dashboard and wait for events to come in. This will cause the Service Viewer to be populated with events.
•To populate the services manually:
–Log in to Netcool Impact.
–Click Policies in the menu bar.
–Trigger the CreateServiceInstanceUpdated policy.
Starting Cisco Info Center
This section describes how to start and stop the Cisco Info Center components of Cisco VAMS. This section contains:
•Starting and Stopping the Product Components
•Starting the Object Server
•Stopping the Object Server
•Starting the Syslog Probe
•Stopping the Syslogd Probe
•Starting the SNMP (MtTrapd)Probe
•Stopping the SNMP EMS Probe
•Starting Netcool/Impact
•Stopping Netcool/Impact
•Starting TBSM
•Stopping TBSM
Starting and Stopping the Product Components
The processes for the product components must be started in the following order:
1. ObjectServer—as ncoadmin.
2. SYSLOG (nco_p_syslog) probe—as root.
3. SNMP EMS (nco_p_mttrapd_ems) probe—as root.
4. Netcool/Impact—as ncoadmin.
5. TBSM postgres DB—as ncoadmin.
6. TBSM Data Server—as ncoadmin.
7. TBSM Dashboard Server—as ncoadmin.
The product components should be stopped in the following order:
1. TBSM Dashboard Server
2. TBSM Data Server
3. TBSM postgres DB
4. Netcool/Impact
5. SNMP EMS (nco_p_mttrapd_ems) probe
6. SYSLOG (nco_p_syslog) probe
7. ObjectServer
Starting the Object Server
To start the Object Server:
Step 1 Change directory to $NCHOME/omnibus/bin, for example:
cd /opt/vams/tivoli/netcool/omnibus/bin
Step 2 Issue the following command:
The Object Server starts and runs in background mode.
Stopping the Object Server
The preferred method for stopping the VAMS ObjectServer is to log in to the ObjectServer interactively and perform a graceful shutdown:
To stop the Object Server:
Step 1 Change directory to $NCHOME/omnibus/bin. For example, enter:
cd /opt/vams/tivoli/netcool/omnibus/bin
Step 2 Enter the following command:
Step 3 Enter the ObjectServer root password (blank by default)
Step 4 At the Object Server prompt, enter the following commands
Step 5 Enter quit to exit nco_sql.
Alternatively, you can determine the PID for the nco_objserv process by entering ps -ef | grep objs, and then perform a standard kill operation on the process (kill <PID>. This will also cause the ObjectServer to shut down in an orderly fashion.
Note Performing a kill -9 <PID> of the ObjectServer process is NOT recommended, and might result in the corruption of the ObjectServer database.
Starting the Syslog Probe
Step 1 Login as (or su to) root.
Step 2 Change directory to $NCHOME/omnibus/probes, for example:
cd /opt/vams/tivoli/netcool/omnibus/probes
Step 3 Edit the $NCHOME/omnibus/probes/solaris2/syslog.props file as follows:
LogFile : "/var/adm/messages"
Step 4 Save the file.
Step 5 Change directory to the $NCHOME/omnibus/probes directory, for example:
/opt/vams/tivoli/netcool/omnibus/probes
Step 6 Enter:
./nco_p_syslog -rulesfile
opt/vams/tivoli/netcool/omnibus/probes/solaris2/rules/syslog.rules &
Note This command starts the Syslog probe in background mode.
Stopping the Syslogd Probe
Step 1 Enter the following command:
Step 2 Using the PID for the probe, enter:
Starting the SNMP (MtTrapd)Probe
To start the SNMP probe:
Step 1 Login as root or su to root.
Step 2 Change directory to $NCHOME/omnibus/probes, for example:
cd /opt/vams/tivoli/netcool/omnibus/probes
Step 3 Enter:
./nco_p_mttrapd -rulesfile $NC_RULES_HOME/snmptrap.rules &
Note This command starts the MtTrapd probe in background
Stopping the SNMP EMS Probe
Step 1 Enter the following command:
The system displays the PID for the probe.
Step 2 Using the PID for the probe, enter:
Starting Netcool/Impact
To start Netcool/Impact:
Step 1 Change directory to $NCHOME/omnibus/bin. For example, enter:
Step 2 Enter the following command:
Stopping Netcool/Impact
To stop Netcool/Impact:
Step 1 Change directory to $NCHOME/omnibus/bin. For example, enter:
Step 2 Enter the following command:
./ewas.sh stop -username wasadmin -password netcool
Note The default password for the wasadmin user is netcool.
Starting TBSM
TBSM 4.2.1 consists of three processes:
•A Postgres database.
•The Data Server (performs the data processing for TBSM 4.2.1.
•The Dashboard Server (provides the display functionality for TBSM 4.2.1, and also includes Netcool/Webtop 2.2).
Starting the Postgres Database
To start the Postgres database:
Step 1 Change directory to $TBSMHOME/bin; for example:
cd /opt/vams/tivoli/tbsm/bin
Step 2 Enter:
Starting the Data Server:
Step 1 Change directory to $TIPHOME/bin, for example:
cd /opt/vams/tivoli/tip/bin
Step 2 Enter:
./startServer.sh server1 -profileName TBSMProfile -username tipadmin -password netcool
Starting the Dashboard Server
Step 1 Change directory to $TIPHOME/bin, for example:
cd /opt/vams/tivoli/tip/bin
Step 2 Enter:
./startServer.sh server1 -profileName TIPProfile -username tipadmin -password netcool
Stopping TBSM
Stop the TBSM processes in the reverse order from the order in which they were started.
Stopping the Dashboard Server
Step 1 Change directory to $TIPHOME/bin, for example:
cd /opt/vams/tivoli/tip/bin
Step 2 Enter:
./stopServer.sh server1 -profileName TIPProfile -username tipadmin -password netcool
Stopping the Data Server
To stop the Data Server:
Step 1 Change directory to $TIPHOME/bin, for example:
cd /opt/vams/tivoli/tip/bin
Step 2 Enter:
./stopServer.sh server1 -profileName TBSMProfile -username tipadmin -password netcool
Stopping the Postgres Database
To stop the Postgres database:
Step 1 Change directory to $TBSMHOME/bin, for example:
cd /opt/vams/tivoli/tbsm/bin
Step 2 Enter:
Logging in to TIP/TBSM
To log in to TIP/TBSM, go to the URL for the TBSM application:
https://tip_server_address:16316/ibm/console/logon.jsp
where tip_server_address is the IP address of the TIP/TBSM server.
Upgrading to Cisco VAMS 3.0
If you need to upgrade an existing Cisco VAMS 2.0 or 2.0.1 installation to Cisco VAMS 3.0, consult with Cisco Advanced Services for assistance in the upgrade.