Guest

CiscoWorks LAN Management Solution 3.2 and earlier

Managing CiscoWorks LAN Management Solution 5th Edition Installation

Document ID: 28782

Updated: Oct 26, 2005

   Print

Introduction

These instructions are to assist in a new CiscoWorks LAN Management Suite installation on a supported Solaris server or supported Windows platform. This information is intended to guide the installer through the necessary documentation; it is not intended to replace the normal product documentation.

Before You Begin

CiscoWorks applications are sold together as a bundle, but developed by individual development teams. Thus each application has documentation, and there is a separate set of bundle documentation apart from the applications. Ensure that you are familiar with the bundle documentation, which will sometimes supercede individual application documentation on issues like device limitations.

Conventions

For more information on document conventions, see the Cisco Technical Tips Conventions.

Prerequisites

Before attempting this configuration, please ensure that you meet the following prerequisites:

Components Used

This document was developed and tested using the knowledge gained by TAC engineers over time on a variety of hardware/software combinations, thus no single combination of hardware and software was used.

  • CiscoWorks LMS Bundle on Solaris 2.8

  • Supported Windows platforms

Installation -- Windows

The steps below guide you through a CiscoWorks LMS Bundle Installation on Windows platforms.

Guidelines

General guidelines/cautions before starting:

  1. Install on NTFS partition. Do not install using FAT partitions.

  2. Check for pre-SP3 patches. Check in the Windows Control Panel's "Add/remove programs" applet to see if pre-SP3 Service Pack is applied.

  3. Do not install Windows 2000 Advanced Server; disable Terminal Services if they are present in the Control Panel Services applet. These are not supported.

  4. Do not install remotely using Terminal Services.

  5. Login as the local Administrator to install and administer. DO NOT LOGIN as a domain administrator.

  6. Do not install this under the root directory. Please create the subdirectory you wish to use and then install (e.g.) Do not attempt to install to C:\ or D:\.

    Note: If you do not have the original CD-ROM, but got the files from Cisco Systems Engineer OR a TAC engineer posted this on CCO, please ensure that the byte count matches the following:

    CiscoWorks Component Windows Solaris
    Cd-One 5th Ed 310,598,890 bytes 343,694,973 bytes
    RME 3.4 35,090,866 bytes 36,586,544 bytes
    Campus Manager 3.2 27,712,390 bytes 26,248,472 bytes
    DFM 1.2 23,631,891 bytes 49,622,719 bytes
    IPM 2.4 88,549,490 bytes 148,546,746 bytes

  7. Assign a static IP address for the CiscoWorks server

  8. DNS entry for CiscoWorks should be configured correctly with PTR reccord as well. To check this, run nslookup CiscoWorks_server_name and nslookup IP_address. Both outputs should be consistent.

  9. If you are performing an upgrade install, ensure the you apply the patch_1x_20.pl mentioned in the upgrade (local or remote) install procedure. This is critical... failing to apply this patch will necessitate complete removal of CiscoWorks and reinstallation (see CSCdy62657).

  10. Test each application before installing the next, this keeps uninstalls to a minimum. For instance, after installing CD-One, test that CiscoView can be used. After RME, add a device to the inventory. After Campus, perform a discovery.

Install Sequence

Refer to the bundle Quick Start Guide.

  1. Install in this sequence:

    • Cd_One 5th Ed ( Choose Option 4 )

    • RME 3.4

    • Campus Mgr 3.2

    • DFM 1.2

    • nGenius RTM 1.4

      Note: nGenius RTM needs a separate server.

  2. Install these CiscoWorks patches:

Uninstalling CiscoWorks 2000 from Windows

Use one of these regular uninstall methods.

  • Start > Programs > Programs > CiscoWorks2000 >Uninstall

  • Control Panel > Add/Remove Programs

Verify that the files have been removed from the install directory. If uninstall is not complete, you must manually clean the registry by following these steps:

  1. Make a backup of the Registry by going to Registry and selecting Export Registry File. Save it to a safe location.

  2. In the registry, go to HKEY_LOCAL_MACHINE\SOFTWARE\Cisco\Resource Manager and delete the Current Version subkey.

  3. In Edit -> Find , type CSCOpx and enter. It will take you to the first occurence of CSCOpx in registry Values.

    Press Tab and then Check if the Key is Environment (or) Recent Files. If so,do not delete. Otherwise Delete the key from the registry.

    For example, in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services, there is a list of keys with matching values CSCOpx like crmrsh, crmtftp etc. You can delete them. But in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment, you will find CSCOpx matching in PATH. Do not delete it. Modify it by removing the paths containing CSCOpx in the value of the key. Also, do not delete anything from HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00x (x is any number like 1,2...). These are only internal Windows Backups of registry keys. The registry will also have some CSCOpx matching entries in HKEY_LOCAL_MACHINE\SOFTWARE\ODBC and Apache. Delete the subkey of ODBC.

  4. Repeat 2nd step for all values matching CSCOpx by pressing F3 and then pressing tab.

  5. Then repeat Find & Remove operations for the keyword CW2000.

  6. Remove the directory in which CW2000 is installed.

  7. Remove the directory, CiscoWorks 2000, in Start Menu -> Programs. Right-clicking on Start button and clicking Explore button.

  8. Reboot the system.

Troubleshooting LMS Windows Installation

The following steps give guidelines with LMS Windows installation.

  1. Remove Win 2K SP3. At the time of release of CiscoWorks (CD-One 5th Ed), SP3 was in beta and was not tested.

  2. Do not add the computer to any NT/Windows domain (This is not a stringent requirement, but if you experience problems with CiscoWorks services not starting, remove the computer from the domain and determine if CiscoWorks functions.

Installation - Solaris

The steps below guide you through a CiscoWorks LMS Bundle Installation on Solaris platforms.

Guidelines

General Guidelines/cautions before starting:

  1. Have you met the pre-requisites?

  2. Confirm that Solaris patches (latest versions) are applied.

  3. Also confirm kernel patch -15 is applied as well

  4. Ensure that you have 108528-15 (If you have 108528-16, you will run into CSCdz11668 caused by Solaris defect Id 4769296)

  5. During installation, if you see ERRORS, start from scratch. Still having problems? Contact TAC. If you see WARNINGS, proceed with caution.

  6. If you are performing an Upgrade install, ensure the you apply the patch_1x_20.pl mentioned in the upgrade (local or remote) install procedure. This is critical... failing to apply this patch will necessitate complete removal of CiscoWorks and reinstallation (see CSCdy62657).

  7. Install will fail if ... If the cmd "psrinfo" indicates processor is in any slot other than slot 0, you are running into defect CSCdx87041. This applies for LMS and RWAN installations. The workaround is given below; the steps below guide you through a CiscoWorks LMS Bundle Installation on Solaris platforms.

    • Copy the image from CDONE CD to a local directory.

    • Go to the directory, open setup-lib.sh in vi.

    • Replace line 1752 by the following : Ultr=`psrinfo -v | grep -i "operates at" | head -1 | cut -c37-39`

    • Then run setup.sh from that directory.

    • Repeat the same procedure for other CiscoWorks packages (RME 3.4, Campus Manager 3.2, etc.)

Install Sequence

Refer to the bundle Quick Start Guide.

  1. Install in this sequence:

    • Cd_One 5th Ed (Choose Option 4)

    • RME

    • Campus Mgr

    • DFM

    • IPM

    Note: nGenius RTM needs a separate server CW2000 patches.

  2. Apply the following patches:

Uninstalling CiscoWorks from Solaris

Download and run the script clean_system.sh.

If you are unable to run the script, you may not have the correct permissions for the script or one of the executables within the script is not allowing the permissions.

In this case, follow these steps to manually clean up the installation.

  1. Go to /var/sadm/install.

  2. Open the contents file in an editor.

  3. Search for CSCO*. Delete any line with CSCO in it.

  4. Make a backup of the edited contents file.

  5. Go to var/sadm/pkg and confirm that no CSCO* sub-directory exists.

  6. Go to /opt and confirm that a CSCOpx dir does not exist.

  7. Go to /var/tmp and remove the file ciscoinstall.log.

  8. Go to / and search for CSCO. If any directory or file exists, remove it.

Verify

This section provides information you can use to confirm your configuration is working properly.

  • Do not forget backup.

    Under Server Config > Setup > Administration > Database Mgt there are two options: back up data now and schedule a backup. The directory you specify for the backup should already exist. CiscoWorks does not create the directory for you. It is a good practice to designate a separate partition from where you have installed CiscoWorks. This backup would contain the data from your databases. You should check the backup logfile frequently to verify the success of the backup. The log file is located as follows:

    • Solarus: /var/adm/CSCOpx/log/dbbackup.log

    • Windows: progra~1\CSCOpx\log/dbbackup.log

  • You should regularly export the device attributes (such as telnet/enable passwords, SNMP Ro/RW community strings, and RADIUS/TACACS usernames) to a CSV file. Therefore, if you are unable to restore from your backup, you can use this file to import device information into RME. To export device attributes, go to: RME > Administration > Inventory >Export to file. You cannot specify the location where this file is saved, it is saved in the following location:

    • Solaris: /var/adm/CSCOpx/files/inventory

    • Windows: CSCOpx\files\inventory

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.

Related Information

Updated: Oct 26, 2005
Document ID: 28782