-
Installation and Setup Guide for Resource Manager Essentials 4.0 on Solaris (With LMS 2.5)
-
Preface
-
Installing Resource Manager Essentials
-
Preparing to Use Resource Manager Essentials
-
Licensing
-
Installing Remote Syslog Collector
-
Configuring Resource Manager Essentials with Cisco Secure ACS
-
Troubleshooting the Installation
-
Mounting and Unmounting the CD-ROM
-
Navigational Changes from 3.x to 4.0
-
Index
-
Table Of Contents
Troubleshooting the Installation
Clearing the Cache in Microsoft Internet Explorer
Clearing the Cache in Netscape Navigator
Understanding Installation Messages
Failure to Delete a Package During Uninstallation
CiscoWorks Server Access Problems
Troubleshooting the Installation
This appendix provides troubleshooting information for Resource Manager Essentials (RME 4.0) installation and setup. It contains these sections:
•
Understanding Installation Messages
•
•
Logging In After Upgrading
If the Login Manager dialog box on the CiscoWorks desktop does not appear correctly when you try to log in for the first time after upgrading, clear your browser cache as follows, then reenter the server URL in your browser.
Wait for a few seconds after the server starts before logging in. If you have trouble logging in, use the Reload button on your browser.
Clearing the Cache in Microsoft Internet Explorer
Step 1
The Internet Options dialog box appears.
Step 2
Step 3
Clearing the Cache in Netscape Navigator
Step 1
The Preferences dialog box appears.
Step 2
Step 3
Step 4
Understanding Installation Messages
The messages that might appear during installation are:
•
•
•
All messages that appear during installation are logged in the /var/tmp/ciscoinstall.log file.
Table A-1 shows messages that might occur during installation and describes their reasons.
Table A-1 Installation Messages
Base package did not install. Exiting.
Installation program cannot install a required package.
Contact your technical support representative.
Cannot backup /etc/services, no change will be made.
Installation program cannot make a copy of /etc/services before modifying it.
Make sure there is enough space in /tmp.
Cannot change ownership of library. Exiting.
Installation program cannot write to product root directory.
Check the permissions on the directory you specified.
Cannot create directory.
Installation program cannot write to the directory you specified.
Check the permissions on the directory you specified.
Cannot create symlink: ln -s root /opt/CSCOpx.
Installation program cannot create a link from /opt/CSCOpx to the product root directory you specified.
Contact your technical support representative.
Cannot determine the RME version.
Installation disk is corrupted.
Contact your technical support representative.
Cannot determine the version of product.
Installation program cannot determine product version.
Contact your technical support representative.
Cannot make list of packages for installation.
Installation suffered a major failure.
Contact your technical support representative.
Copy setupdir to nmsroot failed.
Installation program could not write to product root directory.
Check the permissions on the root.
Installation in progress
You are already running an installation on this machine.
Run only one installation program at a time.
For more information, see Frequently Asked Questions.
Missing file file.
Installation program cannot find a file.
Contact your technical support representative.
No Syslog facility is available.
No available Syslog facilities.
Make one of the facilities available.
Not enough disk space: root.
File system has insufficient space to load RME.
Make at least 4 GB of disk space available on the partition on which you install RME.
Package verification failed: pkg aborting.
While loading packages, one loaded incorrectly.
Contact your technical support representative.
Syslog is not running.
Installation program cannot start syslogd on this machine.
Restart syslogd.
The components have dependency errors.
Installation program suffered a major failure.
Contact your technical support representative.
User must be root.
You must be root to install.
Log in as root and enter the correct password.
User casuser appears in /usr/lib/cron/at.deny. Software Image Manager requires casuser to be able to run at. Contact your local technical support representative to edit the file /usr/lib/cron/at.deny and remove the entry for casuser.
User casuser appears in /usr/lib/cron/cron.deny. Software Image Manager requires casuser to be able to run crontab. Contact your local technical support representative to edit the file /usr/lib/cron/cron.deny and remove the entry for casuser.
Software Management requires that the user casuser be allowed to use at and cron.
Edit the relevant files to allow the user casuser to use at and cron. For details, see "Allowing the User casuser to Use at and cron" section.
Wrong OS.
Operating system is not Solaris or not a supported version of Solaris.
Make sure you are running Solaris 2.8 or 2.9.
Installing Syslog Analyzer
If the RME installation fails during Syslog Analyzer installation, make sure you do not have the Cisco DNS/DHCP Manager (CDDM) installed on the same machine as RME. CDDM provides syslog and TFTP daemons as part of its product. CDDM can be downloaded from Cisco.com.
You cannot run CDDM Syslog or TFTP on the same machine as RME because they are not compatible. Make sure the server on which you install RME is not running CDDM Syslog or TFTP.
Caution
Failure to Delete a Package During Uninstallation
If you try to remove RME but the uninstallation program fails to delete a package, try running the uninstall program again. Several circumstances can cause a package to remain after uninstallation. Usually, running the uninstall program again, removes the package.
CiscoWorks Server Access Problems
The CiscoWorks Server uses port 1741 by default. This port is normally used by web servers. If you receive an error message that an existing web server is already configured to run on port 1741, and the alternative port is used instead, verify that you entered the correct URL for the server:
http://server_name:port_numberwhere server_name is the name of the machine where CiscoWorks was installed, and port_number is the alternative port on which CiscoWorks is installed if port 1741 is in use.
•
https://server_name:443where server_name is the name of the machine where CiscoWorks was installed.
•
https://server_name:customportwhere server_name is the name of the machine where CiscoWorks was installed.
Verify Server Status
To make sure your server is running, enter:
ping server_namewhere server_name is the name of the machine where CiscoWorks was installed.
Proxy Server Problems
If you get a message that the server is "alive," and get a proxy error when you try to connect to the server, make sure the proxy is set up correctly.
You will get proxy errors if both these conditions are true:
•
•
You should specify a proxy server in Netscape Navigator under Edit > Preferences > Advanced > Proxies and in Internet Explorer under Tools > Internet Options > Connections > LAN Settings.
Your proxy is set up incorrectly if:
•
•
•
•
•
Daemon Manager Not Running
You can use the following command to verify whether the daemon manager is running:
# /opt/CSCOpx/bin/pdshowIf the daemon manager is not running, following error message is displayed:
connect to dmgtd process on "127.0.0.1" on port 42340 failed:If the Daemon Manager is not running, CiscoWorks cannot run. When you install or uninstall CiscoWorks, the Daemon Manager is temporarily stopped and then restarted. If the install or uninstall process is interrupted, the Daemon Manager might remain in the stopped state.
Note
To start or stop the Daemon Manager:
Step 1
Step 2
Step 3
# /etc/init.d/dmgtd startStep 4
# /etc/init.d/dmgtd stop
Viewing Process Status
You can check back-end server process failures by selecting Common Services > Server > Admin > Processes. Only users with administrator privileges can start and stop processes. For details, refer to User Guide for CiscoWorks Server.
Browser Problems
If the desktop buttons do not work, Java and JavaScript are not enabled. Make sure you enable Java and JavaScript.
Make sure the browser cache is not set to zero.
Do not resize the browser window while the desktop main page is loading. This can cause a Java error.
For more information about setting up browsers, refer to Installation and Setup Guide for Common Services 3.0 (Includes Ciscoview) on Solaris.
Improving Server Performance
To improve system performance for RME:
•
•
•
To turn off, set the registry key HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > crmlog > Parameters > CrmDnsResolution to 0.
Frequently Asked Questions
•
•
•
•
•
•
Q.
A.
Q.
A.
For more information on stopping and starting the Daemon Manager, see "Daemon Manager Not Running" section.
Q.
A.
Step 1
/etc/init.d/dmgtd stopStep 2
/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/dbRestoreOrig.plThe usage details for dbRestoreOrig.pl appear.
Step 3
Caution
We recommend that you reinitialize the database for both the applications—Common Services and RME. Else, the database may become inconsistent. You can follow any order for reintialization.
A message appears that the initialization is complete.
Step 4
/etc/init.d/dmgtd startQ.
A.
Let us consider a few scenarios here:
Your server is behind a firewalled network, while your clients are outside the firewall.
In this scenario, you have to open ports on the firewall for your clients.
•
•
You want to manage devices outside a firewall.
In this scenario, you need to open a few ports. For maximum manageability, ensure that the ports listed in Table A-3 are open.
Your firewall is engaged in NAT (Network Address Translation).
In this scenario, if you need to manage devices outside the NAT boundary,
Step 1
Step 2
Consequently, when you perform Software Image Management operations, and configuration TFTP operations, this IP address will be used as the TFTP server address. Note, you must still open all the ports listed in Table A-3.
Q.
A.
Step 1
# /etc/init.d/dmgtd stopThis stops the daemon manager.
Step 2
# cd /opt/CSCOpx/bin# ./dbpasswd.pl dsn=rmengFor detailed usage information, you can enter the following:
# ./dbpasswd.plThe following message appears:
Please enter the new password for database rme:Step 3
The following message appears:
Please enter the new password again for verification:Step 4
Do you want to encrypt the database username and password, YES[Y] or keep the encryption mode as it is [N]:Step 5
Step 6
# /etc/init.d/dmgtd startQ.
A.
•
•
•
•
•
•
•
•
Q.
A.
For more information see the table below:
Q.
A.
/var/tmp/ciscoinstall.log/var/tmp/ciscouninstall.logFor a product upgrade, the database upgrade log information appears in the installation log file and in
/var/adm/CSCOpx/log/migration.log.Q.
A.
–
–
–
–
–
To verify the Windows 2000 SP4 install:
Select Start > Programs > Administrative Tools > Computer Management > System Tools > System Information > System Summary.
You should see:
Version 5.0.2195 Service Pack 4 Build 2195To verify the IE 6.0.2800 SP1 installation:
Select Internet Explorer > Help > About Internet ExplorerYou should see:
Microsoft Internet ExplorerVersion: 6.0.2800.1106COUpdate versions:;SP1;To verify Windows Scripting Host (WSH):
a.
b.
The following will appear if WSH is installed:
Microsoft (R) Windows Scripting Host Version 5.1 for WindowsQ.
A.
•
Or
•
Use the procedure below only as a last resort after exhausting all other options, like reinstalling RME.
Caution
Step 1
# BEGIN COPY#!/usr/bin/shPromptResponse (){RESPONSE=""VALID_RES=""if [ -n "$2" ] ; then VALID_RES="$2" ; fiDEF_ARG=""if [ -n "$3" ] ; then DEF_ARG="$3" ; fiuntil [ "${RESPONSE}" != "" ];doif [ "${DEF_ARG}" = "" ] ; thenecho "$1 \c"elseecho "$1 [${DEF_ARG}] \c"firead RESPONSEif [ "$VALID_RES" = "1" ]; thencase "${RESPONSE}" in"")RESPONSE="${DEF_ARG}";;[Yy]|[Yy][Ee][Ss])RESPONSE="y";;[Nn]|[Nn][Oo])RESPONSE="n";;*)RESPONSE="";;esacelsecase "${RESPONSE}" in"")RESPONSE="${DEF_ARG}";;1)RESPONSE="1";;2)RESPONSE="2";;3)RESPONSE="3";;*)RESPONSE="";;esacfidoneunset DEF_ARGreturn 0}# Mainif [ "`uname`" != "SunOS" ]; thenecho "This script can only run on Solaris."exit 0fiif [ `/bin/id | sed -e 's/(.*$//' -e 's/^.*=//'` != 0 ] ; thenecho "ERROR: You must be logged in as root to run this script."exit 0fiecho "\nThis script will try to remove CiscoWorks from the system.\It is kind of risky to do it especially when you have bundles installed.\Please make sure you already tried any of these TWICE:"echo "\n\t* /opt/CSCOpx/bin/uninstall.sh"echo "\t* pkgrm CSCOxxx"echo "\t (CSCOxxx is one of CiscoWorks packages)"echo "\nWARNING: Don't try this script unless the system"echo "WARNING: contents file corrupted (bad or garble"echo "WARNING: entry) which makes above commands failed.\n"PromptResponse "Do you want to continue (y/n)?" 1 nif [ "$RESPONSE" != "y" ]; thenexit 0fiBackup_c=0Backup_s=0echo "\nStop daemon manager ..."if [ -x /etc/init.d/dmgtd ]; then/etc/init.d/dmgtd stop 2> /dev/nullsleep 10fiecho "\nChecking CSCO packages installed ... \c"csco_pkgs=`ls -d /var/sadm/pkg/CSCO* 2> /dev/null |sed -e 's#/var/sadm/pkg/##' -e 's#/##'`if [ "$csco_pkgs" = "" ]; thencsco_pkgs=`grep " CSCO" /var/sadm/install/contents |awk '{print $NF}' |grep CSCO |sort -u`fiif [ "$csco_pkgs" = "" ]; thenecho "No"elseecho "Yes\n"for pkg in `echo $csco_pkgs`; do echo "\t$pkg"; doneecho "\nAbove packages found in the system. Some of them might not belong\to CiscoWorks when you have other Cisco product installed. If you are\not sure about this, verify these packages with Cisco TAC before go ahead."echo "\n\t1. Clean them all in one step."echo "\t2. Clean them one by one. (later you can select to skip any of them)"echo "\t3. Quit.\n"PromptResponse "Please input your decision -->" 2if [ "$RESPONSE" != "1" -a "$RESPONSE" != "2" ]; thenexit 0fiMETHOD=$RESPONSEecho "\nBackup contents file in /var/sadm/install/contents.save.$$"cp /var/sadm/install/contents /var/sadm/install/contents.save.$$Backup_c=1echo "\nCleaning packages from system registry ..."cp /var/sadm/install/contents /tmp/contentsfor pkg in `echo $csco_pkgs`;doif [ "$METHOD" = 2 ]; thenPromptResponse "Clean $pkg ?" 1if [ "$RESPONSE" != "y" ]; then continue; fifigrep -v $pkg /tmp/contents > /tmp/contents.tmpmv /tmp/contents.tmp /tmp/contentsrm -rf /var/sadm/pkg/$pkgecho "$pkg cleaned"donemv /tmp/contents /var/sadm/install/contentsfiif [ "`grep CSCO /etc/services`" != "" ]; thenecho "\nBackup system services file in /etc/services.save.$$"cp /etc/services /etc/services.save.$$Backup_s=1echo "Cleaning system services file ..."grep -v CSCO /etc/services > /tmp/remove.tmpmv /tmp/remove.tmp /etc/servicesfiecho "\nCleaning CiscoWorks runtime trees ..."if [ -d /opt/CSCOpx -o -h /opt/CSCOpx ]; thenPromptResponse "Remove /opt/CSCOpx ?" 1if [ "$RESPONSE" = "y" ]; thenrm -rf /opt/CSCOpx/*rm -rf /opt/CSCOpxfifiif [ -d /var/adm/CSCOpx ]; thenPromptResponse "Remove log directory /var/adm/CSCOpx ?" 1if [ "$RESPONSE" = "y" ]; thenrm -rf /var/adm/CSCOpxfifiif [ -d /tmp/cscotmp -o -f /tmp/csco* ]; thenPromptResponse "Remove temp files /tmp/csco* ?" 1if [ "$RESPONSE" = "y" ]; thenrm -rf /tmp/csco*fifiechoif [ "$Backup_c" = "1" ]; thenecho "INFO: Original contents file saved in /var/sadm/install/contents.save.$$"fiif [ "$Backup_s" = "1" ]; thenecho "INFO: Original system services file saved in /etc/services.save.$$"fiecho "\nCleaning is done."# END COPYStep 2
For example, you can save the file as cleanup.sh.
Step 3
For example if you saved the file as cleanup.sh, enter:
# chmod 750 cleanup.shStep 4
# ./cleanup.shThe script removes files installed by all CiscoWorks applications.
Q.
A.
In addition to that, before rebooting the CiscoWorks server, you must change the hostname for CTMJrmServer daemon registration.
a.
b.
After making the changes in the CTMJrmServer, the new hostname entry appears as follows,
CTMJrmServer y y 120000 RMEDbMonitor,jrm,TomcatMonitor,RMECSTMServer /opt/CSCOpx/bin/cwjava -cw /opt/CSCOpx -cw:jre lib/jre -server -cp:p MDC/tomcat/webapps/rme/WEB-INF/classes:MDC/tomcat/webapps/rme/WEB-INF/lib/ctm.jar:MDC/tomcat/webapps/rme/WEB-INF/lib/log4j.jar com.cisco.nm.rmeng.jrmwrapper.server.CTMJobManagerServer CW-Server1
Where, CW-Server1 is the new hostname.
Troubleshooting Tips
