Table Of Contents
Troubleshooting the Installation
If the Installer Window Does Not Appear
Logging In After Upgrading
Microsoft Internet Explorer
Netscape Navigator
Verify the Server Is Running
To make sure your server is running, enter Proxy Server Problems
Daemon Manager Not Running
Viewing Process Status
Browser Problems
Improving Server Performance
Frequently Asked Questions
Troubleshooting the Installation
This appendix provides troubleshooting information for Essentials installation and setup, and contains these sections:
•
If the Installer Window Does Not Appear
•Logging In After Upgrading
•Understanding Installation Messages
•Failure to Delete a Package During Uninstallation
•Accessing the CiscoWorks Server
•Viewing Process Status
•Browser Problems
•Improving Server Performance
•Frequently Asked Questions
If the Installer Window Does Not Appear
If the Installer window does not appear after you insert the CD-ROM, you can run the installation program from the Run dialog box.
Step 1 Select Start > Run.
The Run dialog box appears.
Step 2 In the Open field, enter:
where drive is the CD-ROM drive letter.
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 a few seconds after the server starts before logging in. If you have trouble logging in, click the Reload button on your browser.
Microsoft Internet Explorer
Step 1 Select Tools > Internet Options.
The Internet Options dialog box appears.
Step 2 Select the General tab.
Step 3 Click Delete Files, then click OK in the Delete Files dialog box.
Netscape Navigator
Step 1 Select Edit > Preferences.
The Preferences dialog box appears.
Step 2 Select Advanced > Cache.
Step 3 Click Clear Memory Cache, then click OK in the Memory Cache dialog box.
Step 4 Click Clear Disk Cache, then click OK in the Disk Cache dialog box.
The messages that might appear during installation are:
•Information messages, that give you important details
•Warning messages, that tell you that something might be wrong with a particular process, but the process will complete
•Error messages, that tell you that a particular process could not complete
All messages that appear during Essentials installation are logged in the SystemDrive:\cw2000_inxxx.log, where xxx is the log file for the last CiscoWorks application installed.
Table B-1 Installation Messages
Message
|
Reason for Message
|
User Action
|
<...> is already running! Wait for it to finish and press the OK button below
|
An installation subtask is still running.
|
Wait for installation subtask to complete running, then click OK to proceed.
|
Cannot find script to upgrade database
|
Problem with database upgrade.
|
Contact your technical support representative.
|
Cannot stop service servicename
|
The installation (or uninstallation) tried to stop the service servicename unsuccessfully.
|
Select Control Panel > Services and try to stop service servicename manually, then proceed with installing or uninstalling.
|
CiscoWorks installation cannot proceed because you are not logged in as an administrator.
|
You are not logged in to Windows 2000 with administrator privileges.
|
Log in with local administrator privileges and try installing again.
|
Database upgrade failed
|
Problem with database upgrade.
|
Contact your technical support representative.
|
Database upgrade result unknown
|
Problem with database upgrade.
|
Contact your technical support representative.
|
Decompression failed on file. The error was for error code per CompressGet
|
If Essentials was downloaded, a transmission error occurred, or the installation media is damaged.
|
Retry the download. If you still have errors, contact your technical support representative.
|
Error creating user casuser <... > See the troubleshooting section in User Guide for Resource Manager Essentials 3.5.
|
Installation program could not create the user casuser account.
|
Fix problem, then rerun the installation.
|
Failed to set file permissions.
|
Installation program is unable to set file permissions. The likely causes are:
•Account you used to log in to the system has insufficient permissions.
•Drive on which you are installing the product has a FAT file system.
|
Fix problem, then rerun installation program.
|
function failed: DLL function not found
|
dll is expected to be available at any time for any process, but the operating system failed to load it.
|
Check permissions on Windows system32.
or
If dll is secure.dll or r_inst.dll, check the Essentials installation medium for errors.
or
Reinstall Windows.
|
General file transmission error. Please check your target location and try again. Error number: error code
|
If Essentials was downloaded, a transmission error might have occurred.
|
Retry the download. If you still have errors, contact your technical support representative.
|
Launch of isql script failed
|
Existing database file is broken, or the previous version of Essentials is destroyed. (You may see this message during installation.)
|
Contact your support representative.
|
OpenFile failed: pathname
|
A file open operation failed.
|
Run the file system checking utility, then repeat the installation.
|
ProtectFile failed: file: error. WWW admin security may be incomplete
|
Setting file permissions failed because the user might not be allowed to change them.
|
Log in as administrator.
Note If you are installing on a FAT file system, Essentials cannot provide file security.
|
The installer has determined that the destination drive has an NTFS or FAT file system. You have size and units of space. The product requires size and units on this drive.
|
Insufficient disk space available to install the product.
|
Create additional free space on the drive or install both
Common Services and Essentials on a different drive.
|
The installer has verified the following on your system: Insufficient disk space (footprint and runtime).
|
Insufficient disk space available to install the product.
|
Create additional free space on the drive or install both
Common Services and Essentials on a different drive.
|
The installer has verified the following on your system: Insufficient memory (RAM).
|
Insufficient RAM to meet Essentials requirements.
|
Complete the installation, then reconfigure the system.
|
The installer has verified the following: Insufficient CPU.
|
Insufficient CPU to meet Essentials recommendations.
|
Install both Common Services and Essentials on a different system.
|
The installer has verified the following: Insufficient swap space (or paging file).
|
Insufficient swap space to meet Essentials recommendations.
|
Complete the installation, then increase paging file size.
|
The installer requires temporary workspace. You have less than 8 MB of free space on drive_on_which_temporary_directory is located: Please free up some space and try again.
|
Insufficient drive space for temporary installation files.
|
Make more drive space available, then rerun installation.
|
These files are currently being used by another running process. You must stop all processes listed below to proceed successfully with this installation.
Click Next to proceed with the installation.
Click Cancel to exit.
|
Some of the executables and DLLs installed by CiscoWorks are locked.
|
Stop all applications. Stop IPM if it is running. Close Browsers and make sure CiscoWorks CLIs are not used at the moment. After stopping all the applications, proceed with the installation.
|
Unable to create/open log file.
|
Installation program was unable to create or open installation log file cw2000_inxxx.log, where xxx is a sequential number starting from 001 (in the root directory of the system drive).
|
Determine why file could not be created or opened, fix problem, then rerun installation. You may not have enough disk space or the file may be write protected.
|
Unable to write infoFile or Unable to create infoFile
|
A file-write operation failed.
|
Run the file system checking utility, then repeat the installation.
|
UseDLL failed for dll
where dll is the name of a dll file.
|
dll is supposed to be available at any time for any process, but Windows failed to load it.
|
Check permissions on the Windows system32 folder.
or
If the dll is secure.dll or r_inst.dll, check the Essentials installation medium for errors.
or
Reinstall Windows.
|
You have enough space to install Essentials. However, if you want to install other applications after installing Essentials, please check the system requirements for those products.
|
Possibly insufficient disk space available to install the other products.
|
If you plan to install other products that depend on Essentials, you might need to create additional free space on the drive or install Common Services, Essentials, and other products on a different drive.
|
If you try to remove Essentials but the uninstallation program fails to delete a package, try running the uninstall program again. Several circumstances can allow a package to remain. Usually running the uninstallation program again removes the package.
If secure shell (SSL) is enabled, enter:
For more information on secure shell (SSL) refer User Guide for CiscoWorks Server.
Verify the Server Is Running
To make sure your server is running, enter Proxy Server Problems
You should specify a proxy server in Netscape Navigator under
Daemon Manager Not Running
CiscoWorks relies on the Daemon Manager to control its processes. If the Daemon Manager is not running, you cannot access the server. If you interrupt an installation or uninstallation, the Daemon Manager might not have restarted.
Note Wait a few seconds after the server starts before logging in. If you have trouble logging in, click the Reload button on your browser.
To start (or stop) the Daemon Manager from the GUI:
Step 1 From the Windows Start menu, select
Start > Settings > Control Panel > Administrative Tools > Services.
or
Start > Programs > Administrative Tools > Services.
Step 2 Select CiscoWorks Daemon Manager from the dialog box.
Step 3 Click Start to start the server.
Step 4 Click Stop to stop the server.
To start (or stop) the Daemon Manager from the command-line interface:
Step 1 Log in as administrator.
Step 2 Open a command prompt window or shell window.
Step 3 Stop the server by entering:
Step 4 Start the server by entering:
Viewing Process Status
To check for failures of back-end server processes select Server Configuration >
Administration > Process Management > Process Status. Only users with administrator privileges can start and stop processes. For details, see 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 information about setting up browsers, refer to Installation and Setup Guide for Common Services on Solaris.
Improving Server Performance
To improve server performance for Essentials:
•Reduce the number of managed devices polled by Availability.
•Increase the interval used by Availability to poll managed devices.
•Reduce the number of syslog messages saved to the CiscoWorks database.
•Increase the interval used by Configuration Management to collect information for managed devices.
•While using CMF Syslog Service, you can turn off DNS lookup to improve performance of Syslog Analyzer.
To turn off, set the registry key MACHINE > System > CurrentControlSet > Services > crmlog > Parameters > CrmDnsResolution to 0.
Frequently Asked Questions
•I modified the date and time on the CiscoWorks Server, but Essentials does not reflect the change. What should I do?
•How do I re-initialize the Essentials database on a Windows system, if the Essentials database is corrupted and the database restore operation has failed?
•Can I use Essentials within a network containing firewalls? If so, what are special configurations I need to take care of?
•Can I change the Essentials Database password? If so, how?
•How do I back up a converted database
•When I perform a backup of the Essentials database, what data is backedup?
•When I export the Essentials database, what data is exported?
•I performed a fresh installation of Essentials 3.5 on a machine. I also reinstalled Essentials 3.5 on another machine. Why did the installation prompt me for new a password in the latter scenario?
•What is an IDU?
•Why should I install the latest IDU?
•Where can I download an IDU?
•How do I know which version of IDU I have installed?
•I have upgraded to Essentials 3.5. But, I have lost support for some devices. Why?
Q. I modified the date and time on the CiscoWorks Server, but Essentials does not reflect the change. What should I do?
A. You will need to stop and restart the CiscoWorks Daemon Manager for Essentials to reflect the changes in date, time or timezone.
For more information on stoping and starting the Daemon Manager, see "Daemon Manager Not Running" section.
Q. How do I re-initialize the Essentials database on a Windows system, if the Essentials database is corrupted and the database restore operation has failed?
A. You can use the dbRestoreOrig.pl utility to re-initialize the Essentials database.
To re-initialize the Essentials database follow this procedure:
Step 1 Open a command prompt window, and stop the daemon manager by entering:
net stop crmdmgtd
Step 2 At the prompt, run the PERL script, dbRestoreOrig.pl:
%NMSROOT%\bin\perl %NMSROOT%\bin\dbRestoreOrig.pl
where %NMSROOT% is the directory in which CiscoWorks is installed.
The usage details for dbRestoreOrig.pl are displayed.
Enter the required variable parameters and the corresponding values based on your application (see "Variable Parameters" table).
Caution All the user configurable variable parameters are case-sensitive. Ensure that you enter the exact value as mentioned in the table below— if not, the database will get corrupted.
It is recommended that you reinitialize the database for both the applications—Common Services and Essentials. Else, the database may become inconsistent. You can follow any order for reintialization.
.
Table B-2 Variable Parameters
Variable Parameter
|
For Common Services enter
|
For Essentials enter
|
|
cmf
|
rme
|
|
Cmf
|
Essentials
|
|
Note It is optional to enter a new password for this variable. Enter a new password only if you want to change your database password.
|
Your new password
|
Your new password
|
You will see a message that the initialization is complete.
Step 3 Restart the daemon manager by entering:
net start crmdmgtd
Q. Can I use Essentials within a network containing firewalls? If so, what are special configurations I need to take care of?
A. Yes, you can use Essentials in a network containing firwalls.
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. If all you are interested in is Essentials, then you have to open TCP 1741 (or whichever port cscoweb is set to) as well as all established TCP connections.
If you require client support for Campus Manager, ACLM, or IPM, you have to take into account CORBA which requires you to open all TCP ports above 1023 on your firewall. In such a case, a better solution would be to create VPN tunnels 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 B-3 are open.
Table B-3 Devices outside firewall
Path
|
Ports
|
From Essentials server to device.
|
•UDP 161,
•TCP 80,
•TCP 23 (and/or 22 (SSH) and/or 514 (RCP))
|
From device to Essentials server.
|
•UDP sourced from 161,
•UDP 69 (TFTP),
•UDP 514 (syslog),
•All established TCP sessions
|
Your firewall is engaged in NAT (Network Address Translation).
In this scenario, if you need to manage devices outside the NAT boundary, you must modify %NMSROOT%/www/classpath/com/cisco/nm/archive/
config.properties file, and set USE_NAT to yes and decide on which USER_FIELD you wish to store the public address of the server (the default is field 3). Edit the attributes of the devices which fall outside of the NAT boundary so that the public address of the server is in the user field configured above. 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 B-3.
Q. Can I change the Essentials Database password? If so, how?
A. Yes, you can change the Essentials Database password. To do so:
Step 1 On the CiscoWorks Server, at the command prompt, enter these commands:
This stops the daemon manager.
Step 2 Enter:
where %NMSROOT% is the directory in which Essentials is installed (SystemDrive:\Program Files\CSCOpx by default).
Note For detailed usage information, you can enter the following:
perl dbpasswd.pl
The following message appear:
Please enter the new password for database rme:
Step 3 Enter the new password. The following message appears:
Please enter the new password again for verification:
Step 4 Enter the password again for verification. The following message appears:
Do you want to encrypt the database username and password, YES[Y] or
keep the encryption mode as it is [N]:
Step 5 Enter Y to encrypt.
Step 6 Start the daemon manager. Enter:
Q. How do I back up a converted database
A. After a successful installation of Essentials it is a good practise to back up your newly converted database. This creates a backup compatible with Essentials 3.5 in case you have a problem and need to restore your database. This also prevents overwriting your database by restoring a database backup from the previous version of Essentials.
To back up your database:
Step 1 Access the CiscoWorks desktop and log in. For information, see the "Accessing the Server" section on page 2-4 and the "Logging In" section on page 2-5.
Step 2 Select Server Configuration > Administration > Database Management > Back Up Data Now.
The Back Up Data Now dialog box appears.
Step 3 Enter the pathname of the target directory. It is recommended that you use a different directory from the one where Essentials is located, for example, SystemDrive:\Essentials\backups.
Step 4 To begin the backup, click Finish. This process could take some time to complete.
For more information, see the online help.
Q. When I perform a backup of the Essentials database, what data is backedup?
A. The following files are backed up:
•Properties file for performing Configuration Management.
•Directory containing Device Configurations
•Configuration Jobs and NetConfig Templates
•Software Image Management image repository
Q. When I export the Essentials database, what data is exported?
A. The following data is exported:
Essentials Application
|
What gets Exported
|
Availability
|
Data collected during polling
|
Inventory
|
The Essentials and Syslog databases
|
Configuration Management
|
Properties file for performing configuration management
|
Device Configurations
|
Directory containing device configuration information
|
Configuration Jobs
|
•NetConfig, NetShow and ConfigEditor jobs
•NetConfig templates
|
Software Image Management
|
Software Image Management image repository
|
Q. I performed a fresh installation of Essentials 3.5 on a machine. I also reinstalled Essentials 3.5 on another machine. Why did the installation prompt me for new a password in the latter scenario?
A. When you perform an installation of Essentials 3.5 and choose the typical installation mode, the installation will generate a random password for the Essentials database. In the second scenario, you might have opted for a custom installation. For more information see the table below:
Installation Type
|
Typical Mode
|
Custom Mode
|
Quiet Mode
|
New installation
|
Installation generates a random password.
You can click on Show Details in the Summary window during installation to view the generated password.
|
You are prompted to enter a new password. If you leave the fields empty, Essentials installation will generate a random password for you.
You can click on Show Details in the Summary window during installation to view the password.
|
Installation generates a random password.
You can click on Show Details in the Summary window during installation to view the generated password.
|
Upgrade installation
|
Password from previous installation of Essentials is retained.
|
You are prompted to enter a new password. You can click on Show Details in the Summary window during installation to view the password you entered.
If you leave the fields empty, Essentials installation will retain the password from previous installation of Essentials.
|
Password from previous installation of Essentials is retained.
|
Reinstallation
|
Password from previous installation of Essentials is retained.
|
You are prompted to enter a new password. You can click on Show Details in the Summary window during installation to view the password you entered.
If you leave the fields empty, Essentials installation will retain the password from previous installation of Essentials.
|
Password from previous installation of Essentials is retained.
|
Q. What is an IDU?
A. IDU (Incremental Device Update) for a CiscoWorks application is a downloadable package containing a collection of updated files to provide you with support for new devices. In addition, the package also contains fixes to certain known problems, as well as fixes to newly discovered problems. IDUs are available for download for various versions of CiscoWorks applications.
Q. Why should I install the latest IDU?
A. If you had installed IDU 2.0 on Essentials, and then upgraded to Essentials 3.5, you will not lose any device support. This is because IDU 2.0 has been merged into Essentials 3.5. But, if you had installed a version of IDU later than 2.0 on Essentials, and then upgraded to Essentials 3.5, you will lose support for new devices, and fixes to known problems.
Q. Where can I download an IDU?
A. To retain support for the new devices, we recommend that you download and install the latest IDU for Essentials 3.5 from
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme.
Q. How do I know which version of IDU I have installed?
A. To check the version of IDU installed on your system, from the CiscoWorks desktop, select Server Configuration > About the Server > Applications and Versions.
The Patches Installed table displays the installed version of the application in the following format:
If Patches Installed table displays
|
IDU version installed is...
|
RME3_3_IDU-2_0
|
IDU 2.0 on Essentials 3.3
|
RME3_3_IDU-3_0
|
IDU 3.0 on Essentials 3.3
|
RME3_4_IDU-2_0
|
IDU 2.0 on Essentials 3.4
|
RME3_4_IDU-3_0
|
IDU 3.0 on Essentials 3.4
|
Q. I have upgraded to Essentials 3.5. But, I have lost support for some devices. Why?
A. If you had installed IDU 2.0 on Essentials, and then upgraded to Essentials 3.5, you will not lose any device support. This is because IDU 2.0 has been rolled into Essentials 3.5. But, if you had installed a version of IDU later than 2.0 on Essentials, and then upgraded to Essentials 3.5, you will lose support for new devices.
To retain support for the new devices, we recommend that you download and install the latest IDU for Essentials 3.5 from
http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme.
Feedback
