Installing the VPN/Security Management Solution (VMS) 2.3 on Solaris
Installing and Uninstalling VMS

Table Of Contents

Installing and Uninstalling VMS

Order of Installation

Installing VMS

Installing Common Services with Service Pack 3 (Disk 1)

Workaround for Reinstallation of VMS over Existing VMS 2.3 Installation (CSCsa50479)

Installing VMS Configuration Components (Disk 2)

Workaround for Router MC CSCsa49241

Installing VMS Monitoring Components (Disk 3)

Installing RME 3.5 and IDU 12 (Disk 4)

New Installation—Typical

New Installation—Custom

Installing IDU 12

Uninstalling VMS


Installing and Uninstalling VMS


This chapter includes the following installation and uninstallation information:

Order of Installation

Installing VMS

Uninstalling VMS

Order of Installation

VMS Disk 1, which contains Common Services with an embedded update (Service Pack 3), must be installed first. All VMS components rely on the VMS 2.3 version of Common Services that has Service Pack 3 embedded in its installation.


Note Even if you have Common Services 2.2 with Update 1 installed, you must reinstall Common Services from VMS 2.3 Disk 1.


After Common Services is installed or upgraded, any other component can be installed or upgraded. The only exception is that IDU 12 included on VMS Disk 4 can only be installed after RME 3.5 has been installed or upgraded.


Caution There is a serious problem installing Common Services on Solaris 8 with Sun Update 110934-20 (CSCsa34490). Please see "Troubleshooting Installation" section on page A-1 for important instructions before starting installation.

Installing VMS


This section assumes you intend to install VMS in its entirety including all components on Disks 1, 2, 3, and 4 as listed in Chapter 1, "VPN/Security Management Solution Overview." Complete installation on most systems takes about one hour.

Before You Begin

Verify that all system requirements are met as listed in Chapter 1, "VPN/Security Management Solution Overview."

Perform all proper system checks and safety measures as listed in Chapter 1, "Preparing to Install or Upgrade VMS."


Caution To avoid unnecessarily slow response times while using VMS, we recommend that you install VMS security configuration management components (Firewall MC, Router MC, IPS MC, and AUS) on a separate server from VMS monitoring components (Performance Monitor and Security Monitor).

For each VMS CD-ROM, follow these steps to install VMS 2.3:


Step 1 Log in as root on the Solaris server.

Step 2 Mount the CD-ROM. See Appendix A, "Troubleshooting Installation."

Step 3 Start the installation program by entering:

cd /cdrom/cdrom0/ 
./setup.sh 

The License agreement page appears.

Step 4 Press Enter to view the license agreement page, or q to quit. The following message appears:

You must accept this License agreement for the installation to 
proceed. 
Do you accept all the terms of the preceding License agreement? (y/n) 
[y] 

Step 5 Enter y to accept the agreement, or n to quit.

Step 6 Do one of the following:

Go to "Installing Common Services with Service Pack 3 (Disk 1)" to install Common Services with Service Pack 3.

Go to "Installing VMS Configuration Components (Disk 2)" to install AUS, Firewall MC, IPS MC, or Router MC.

Go to "Installing VMS Monitoring Components (Disk 3)" to install Performance Monitor or Security Monitor, or both.

Go to "Installing RME 3.5 and IDU 12 (Disk 4)" to install RME and IDU 12.

Reboot your system after each component is installed using the reboot command.


Installing Common Services with Service Pack 3 (Disk 1)

To install Common Services with Service Pack 3 (embedded):


Step 1 Follow Step 1 through Step 5 in "Installing VMS" in the preceding section. Determine whether an Express, Typical or Custom installation is necessary. There is a brief description of each type of installation next to the number indicating its option.


Note For more details about the different types of Common Services installation, see the Installation and Setup Guide for CiscoWorks Common Services 2.2 (Includes CiscoView 5.5) on Solaris at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/2.2/cd_one/installation/solaris/guide/InstallSetupGuideForComSerCVSol.pdf.


Step 2 Enter one of the following:

1 for an Express installation that installs the product using the default settings.

2 for a Typical installation, which is recommended for most computers.

3 for a Custom installation, which is recommended if you are customizing the setup option.

q to quit the installation.

Step 3 Enter the location where you want to install Common Services if it differs from the default /opt/CSCOpx.

The Disk 1 components are listed in detail (including Cisco View and Integration Utility) and you are asked to select which ones you are installing. You are also given the option to select all (recommended).

Step 4 Enter the number(s) corresponding to the components you want to install or 4 to install all VMS Disk 1 components.

The installation program displays the details of your available system resources against the product requirements.


Caution If your system does not meet the disk space or memory requirements, exit the installation and make the necessary changes to your system.

The installation program continues.

Step 5 Follow the prompts that ask you to enter an admin password or accept one that is randomly generated. Installation completes.

Step 6 Reboot your system.


Workaround for Reinstallation of VMS over Existing VMS 2.3 Installation (CSCsa50479)

Reinstallation of Common Services on top of an existing VMS 2.3 installation might cause files already patched in the initial installation to be overwritten. You can repair this in one of two ways:

1. Download the patch for CSCsa50479 from the software planner page at: http://www.cisco.com/go/vms and reapply it.

2. Delete the /opt/CSCOpx/setup/patch/CSCsa50479-1.0.info file and reinstall Common Services from Disk 1 as described in "Installing Common Services with Service Pack 3 (Disk 1)".

Installing VMS Configuration Components (Disk 2)

This procedure assumes you have installed Common Services with Service Pack 3.

To install any or all VMS Disk 2 components:


Step 1 Follow Step 1 through Step 5 in "Installing VMS".

Step 2 Enter the number(s) corresponding to the components you want to install or enter 5 to install all VMS Disk 2 components: Firewall MC, Router MC, IPS MC, and AUS.


Caution Router MC will not launch if the default installation folder for Common Services contains wildcards in the path, such as, opt/Custom-CSCO_PX (CSCsa49241). See "Workaround for Router MC CSCsa49241" for instructions.

Step 3 Enter the location where you want to install Disk 2 components if it differs from the host IP address displayed.

You will be prompted for VMS database and Lock Manager passwords. These passwords, if different from database passwords already installed, will only be applied to those components being installed or upgraded now. They will not be applied to installed components that are not being upgraded.

The installation program displays the Lock Manager (LM) Port configuration information.

Step 4 To accept the default port, press Enter. To specify a different port, enter that port number, then press Enter. The default is port number 1272. If the port number that you provide is not available, it will ask for another port number. Port number parameters (1 to 65535) are displayed.

Installation progress is displayed while files are copied and components are configured.

Step 5 Reboot your system.


Workaround for Router MC CSCsa49241

Router MC fails to launch when Common Services 2.2 is installed in a directory whose name contains special characters.

After installing Router MC 1.3.1 from the VMS 2.3 installer, do the following (using /opt/Custom-CSCO_PX as an example):


Step 1 Stop the Daemon Manager:

/etc/init.d/dmgtd stop

Step 2 Unregister the Router MC services:

/opt/CSCOpx/bin/pdreg -u iosmdcAppSrv

/opt/CSCOpx/bin/pdreg -u iosmdcMainSrv

Step 3 Change the permissions to "Write" (chmod 777) to enable editing of the following file:

opt/Custom-CSCO_PX/MDC/iosmdc/bin/services/EJBServer/EJBServer.sh

Step 4 Edit the file by adding the "exec" command to the beginning of line 33, as follows:

exec ${NMSROOT}/MDC/jre/bin/java ....

Step 5 Change the permissions (chmod 755) to enable execution of the file:

/opt/Custom-CSCO_PX/MDC/iosmdc/bin/services/EJBServer/EJBServer.sh

Step 6 Change the permissions (chmod 755) to enable execution of the file:

/opt/Custom-CSCO_PX/MDC/iosmdc/bin/servi ces/Main/RouterMCMain.sh

Step 7 Register the Router MC services again:

/opt/CSCOpx/bin/pdreg -r iosmdcAppSrv -d SqlCoreDB -e/opt/CSCOpx/MDC/iosmdc/bin/services/EJBserver/EJBServer.sh

/opt/CSCOpx/bin/pdreg -r iosmdcMainSrv -d SqlCoreDB -e/opt/CSCOpx/MDC/iosmdc/bin/services/Main/RouterMCMain.sh

Step 8 Start the Daemon Manager:

/etc/init.d/dmgtd start


After a restore operation, if Router MC fails to launch after restarting the Daemon Manager, do the following (using /opt/Custom-CSCO_PX as an example):


Step 1 Stop the Daemon Manager:

/etc/init.d/dmgtd stop

Step 2 Obtain the process ID of the Router MC service:

ps -ef | grep /opt/Custom-CSCO_PX

If there is no process, start the Daemon Manager. Otherwise, run:

kill -9 process-id

Step 3 Start the Daemon Manager:

/etc/init.d/dmgtd start


Installing VMS Monitoring Components (Disk 3)

This procedure assumes you have installed Common Services with Service Pack 3.

To install any or all VMS Disk 3 components:


Step 1 Follow Step 1 through Step 5 in "Installing VMS".

Step 2 Enter the number(s) corresponding to the components you want to install or enter 3 to install Performance Monitor and Security Monitor.

Step 3 Enter the location where you want to install Disk 2 components if it differs from the host IP address displayed.

You will be prompted for a VMS database password. We recommend using the same password as you did in "Installing VMS Configuration Components (Disk 2)", Step 5.

Installation progress is displayed while files are copied and components are configured.

Step 4 Reboot your system.


Installing RME 3.5 and IDU 12 (Disk 4)

This procedure assumes you have installed Common Services 2.2 with Service Pack 3.

To install VMS Disk 4 components (RME 3.5 and IDU 12):


Step 1 Follow Steps 1 and 2 in "Installing VMS".

Step 2 Navigate to the RME directory (not IDU 12 directory).

Step 3 Start the installation program by entering:

cd /cdrom/cdrom0/ 
./setup.sh 

The License agreement page appears.

Step 4 Press Enter to view the license agreement page, or q to quit. The following message appears:

You must accept this License agreement for the installation to 
proceed. 
Do you accept all the terms of the preceding License agreement? (y/n) 
[y] 

Step 5 Enter y to accept the agreement, or n to quit.

The installation program checks for required patches and other dependencies and displays:

1) Typical ("Typical installation is recommended for all computers.")
2) Custom ("Custom installation can be selected if you want to 
customize the setup options.")
Select one of the installation modes using its number or enter q to 
quit [1]


Note If you choose Typical installation mode, the RME database password is randomly generated for you. You can view the password at the end of installation. If you choose Custom installation mode, you are prompted to enter the RME database password.


Step 6 Do one of the following:

If you want the Typical installation mode, see "New Installation—Typical".

If you want the Custom installation mode, see "New Installation—Custom".


New Installation—Typical

For a Typical installation:


Step 1 Enter 1 and press Return.

Step 2 The installation program checks dependencies and system requirements.

If your system does not meet the requirements, a warning appears:

System memory is less than the minimum requirement, which may affect 
performance.

Step 3 Make necessary changes to your system to ensure that they meet the system requirements if needed.

If the drive does not have enough space, an error message appears:

There is not enough space in drive drive name.

Step 4 Select another drive, or free some space on drive drive name.

The installation proceeds without displaying more questions. The following message appears:

Do you want to see the passwords that were entered/randomly generated? 
If yes, please remember that passwords are security sensitive data and 
hence make sure they are kept secure. [y/n]

If you enter y, the password appears in clear text on the console. If you enter n, the password does not appear.

The following message appears:

To ensure that you retain the latest device support and bug fixes, 
please install the latest Incremental Device Update (IDU) for Resource 
Manager Essentials 3.5. You can download the latest IDU from 
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme Please refer to 
the Installation and Setup Guide for details.


Note All IDUs necessary for the VMS version of RME are included in IDU 12 on VMS Disk 4. You do not need to download or install any IDUs from Cisco.com.


Step 5 The installation completes without displaying more questions.

Step 6 Reboot your system.


New Installation—Custom

For a Custom installation:


Step 1 Enter 2 and press Return.

Step 2 The installation program checks dependencies and system requirements.

If your system does not meet the requirements a warning appears:

System memory is less than the minimum requirement, which may affect 
performance.

Step 3 Make necessary changes to your system to ensure that they meet the system requirements if needed.

If the drive does not have enough space, an error message appears:

There is not enough space in drive drive name.

Step 4 Select another drive, or free some space on drive drive name.

The installation program displays the following message:

Enter RME database password:

Step 5 Enter a new password.

The following message appears:

Confirm Password.

Step 6 Enter the password again to confirm.

The installation proceeds without displaying more questions. The following message appears:

To ensure that you retain the latest device support and bug fixes, 
please install the latest Incremental Device Update (IDU) for Resource 
Manager Essentials 3.5. You can download the latest IDU from 
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-rme Please refer to 
the Installation and Setup Guide for details.


Note All IDUs necessary for the VMS version of RME are included in IDU 12 on VMS Disk 4. You do not need to download or install any IDUs from Cisco.com.


Step 7 Reboot your system.


Installing IDU 12

This procedure assumes you have installed Common Services with Service Pack 3 and RME 3.5.


Step 1 Follow Step 1 through Step 5 in "Installing VMS", but substitute the change directory commands to navigate to IDU 12 directory (as opposed to the RME component directory).

Installation messages display as the installation program checks for updates. Since IDU 12 is a compilation of updates, you are asked if you are reinstalling any Incremental Device Updates that the installation program notices you have already installed.

Step 2 Enter n when prompted to reinstall any patches already installed.

You are advised to back up existing VMS and RME databases before the installation program allows IDU 12 to install. Unless otherwise specified, the databases are backed up to the /var/adm/CSCOpx/log/daemonsbackup.log directory.


Note For more information on IDU installation see Readme for Incremental Device Update (IDU) 12.0 on Resource Manager Essentials 3.5 (Solaris) on Cisco.com at:
http://www.cisco.com/pcgi-bin/Software/Tablebuild/doftp.pl?ftpfile=cisco/cw2000/patches/rme/RME35.IDU.v12-0.sol.readme.pdf&app=Tablebuild&status=showC2A.


Step 3 The installation proceeds with IDU and VMS update messages displaying.

Step 4 Reboot your system.


Uninstalling VMS

Step 5

The uninstallation program removes all, or selected VMS component files and settings. Uninstallation takes about 30 minutes.

You can remove any part of VMS or all solution components in their entirety.You cannot uninstall CiscoWorks Common Services without uninstalling all other VMS components.


Caution You must use the VMS uninstallation programs to remove the product. If you try to remove any VMS components manually you can damage your system.

To uninstall VMS or any of its components:


Step 1 Log in as root on the Solaris server.

Step 2 Enter the following commands to start the uninstallation program:

# cd / 
# /opt/CSCOpx/bin/uninstall.sh 

where /opt/CSCOpx is the default installation directory. If you specified a different directory when you installed CiscoWorks Common Services, use the name of that directory.

A message similar to the following appears:

1) Auto Update Server
2) CiscoView
3) IPS Management Center
4) Monitoring Center for Performance
5) Integration Utility
6) Management Center for Firewalls
7) CiscoWorks Common Services with SP3
8) IPS MC/Security Monitor Common Framework
9) Resource Manager Essentials
10) Security Monitor
11) All of the above
Select one or more of the items using its number separated by comma or 
enter q to quit [q]

Step 3 Enter the number(s) that corresponds to those VMS components you want to uninstall, q to cancel and return to the uninstallation program later, or 11 to uninstall all.

A prompt asks you to verify that you want to uninstall the components you chose and lists them individually.

Step 4 Enter y to confirm or n to have the list repeated if you made an error and want to reselect.

The uninstallation program checks for CiscoWorks packages on the system. The following prompt appears:

Delete the CiscoWorks packages? (y/n)

Step 5 Enter y and press Enter to remove packages, or n to quit.

Step 6 Enter y to all prompts asking if you want to remove packages.


Note Most messages that appear are for user information only. If the uninstallation program does not appear to wait for or accept input, please disregard.


When uninstallation is complete, the following message appears:

==============- Software Uninstall Tool Ended -==================
=========================================================Un-install 
ended on  DATE TIME YEAR
Host: NAME OF HOST MACHINE
=================================================================
===================- Possible Warnings/Errors Encountered ===========
No Errors were encountered during uninstallation.