|
|
Essentials is a suite of web-based network management tools integrated into a network desktop. Essentials includes a web-server component, web-based tools, and web browser capability. Essentials is based on a client/server architecture that connects multiple web-based clients to a network server. Essentials enables the deployment, monitoring, and troubleshooting of devices across your network.
This chapter consists of the following sections:
Table 2-1 provides an overview of how to install Essentials, including references to where you can find more details about each task.
| Task | Steps | References | ||
|---|---|---|---|---|
| Step 1 Verify that server requirements are met. | |||
Step 2 Verify that client requirements are met. | ||||
Step 3 (Optional) verify that your intended device import software is supported. | ||||
Step 4 Note that Essentials uses the server's IP address to communicate with clients. | ||||
Step 5 Note the TCP ports that Essentials uses and check for conflicts with existing applications. | "TCP and UDP Ports Used" section on | |||
Step 6 Note the system files that are modified during installation. | ||||
| Step 1 (Upgrade only) back up your data files. | |||
Step 2 Mount the Essentials CD-ROM. | ||||
Step 3 Run the installation program. | ||||
Step 4 Answer any questions that result from the installation program's checks. | ||||
Step 5 Select the Express or Custom installation option. | ||||
Step 6 (Custom only) select the installation directory. | ||||
| Step 1 Verify that the correct files and directories are installed. | "Checking Files and Directories After Installation" in Appendix A | ||
Step 2 Analyze installation error messages. | ||||
Step 3 Collect the server information to determine if the installation is complete. |
Before you install Essentials, make sure your server and client environments meet the hardware and software requirements described in the following sections:
Make sure your server meets the following hardware and software requirements and software compatibility recommendations.
The Essentials hardware and software requirements are given in the "System Requirements" section of "Before You Begin."
To verify the amount of available disk space in each of the specified partitions and directories, enter the following command:
# df -k directory
# bdf directory
Where directory is the partition or directory for which you want to check the available disk space.
The software required for the Essentials server is HP-UX 10.20 or 11.0.
HP-UX 10.2 and 11.0 require HP DCE/9000 Core Client Software. Additionally, the following patches are required:
The Essentials installation program aborts if these patches are not installed on the system. If the installation program aborts for this reason, install the patch, then run the installation program again.
Set the following environment variables for Essentials system administrators. These variables are not required for tasks that users perform using the web interface.
Essentials includes manual (man) pages for its command line commands. To view these man pages, set the MANPATH variable to include the path /opt/CSCOpx/man (where /opt/CSCOpx is the directory in which Essentials was installed). Then you can view the man pages from any directory using the following command:
$ man pagename
where pagename is the name of the man page. Refer to the section "Setting Environmental Variables" for information about setting up administrator systems.
Make sure that you do not have the Cisco DNS/DHCP Manager (CDDM) installed on the machine on which you plan to install Essentials. CDDM, which can be downloaded from CCO, provides syslog and TFTP daemons as part of its product. You cannot run CDDM Syslog or TFTP on the same machine as Essentials because they are not compatible. Essentials installation will fail if CDDM Syslog or TFTP are present on the machine.
Clients use a web browser running on a workstation or PC to access the Essentials server. The hardware and software requirements for the client workstations or PCs are as follows:
Essentials supports client systems with the web browsers listed in Table 2-1.
| Browser | Version | Operating System |
|---|---|---|
Netscape Navigator 1 | 4.05 and 4.5 | HPUX 10.20 or 11.0, Solaris 2.5.1 or 2.6, Windows NT 4.0, Windows 95 and AIX 4.2.1 or 4.3 |
Microsoft Internet Explorer 2 | 4.01 with Service Pack 1 3 | Windows NT 4.0 and Windows 95 |
If you are using Netscape as your browser and it has not been installed, you can install it at any time. You must start Netscape at least once before starting CWSI Campus help to accept the Netscape licensing agreement. If you do not start Netscape before starting CWSI Campus help for the first time, CWSI Campus help does not start.
To configure a client system to use with Essentials, follow these steps:
Step 1 On Microsoft Windows systems, set the display to use small fonts.
(a) Select Start > Settings > Control Panel. The Control Panel window appears.
(b) Double-click the Display icon. The Display Properties dialog box appears.
(c) Click the Settings tab. If Small Fonts is selected in the Font Size list, your display font is set correctly; go to Step 2.
(d) Select Small Fonts from the Font Size list, then click OK. The System Settings Change dialog box appears.
(e) Click Yes to restart your system. Windows restarts using the small display font.
Step 2 Configure the Web browser.
(a) Enable Java and JavaScript.
(b) Set your browser cache to at least 4 MB.
(c) Configure your browser to accept all cookies.
(d) Configure your browser to compare each page with its cached version every time it loads a page.
(e) (Internet Explorer only) Set the security level to Medium. Select View > Internet Options > Security, then select the Medium (more secure) radio button and click OK.
(f) (Internet Explorer only) Change the default timeout value to 20 minutes. Instructions are provided on the Microsoft Support Web site at the following URL:
http://support.microsoft.com/support/kb/articles/q181/0/50.asp
(g) Enable style sheets.
(h) Change the default font to a sans serif font for easier readability.
If you experience browser problems after configuring your browser as described above, increase your disk cache settings.
After the web browser is installed on the client machine, there are no additional disk space requirements. However, because the browser uses the local machine's disk to store cached information, make sure you have enough disk space for the amount of cached information you want to store. All Essentials information is stored on the Essentials server.
Table 2-2 lists the software that Essentials supports for importing device information. You can import devices remotely from UNIX systems only.
| Software | Version |
|---|---|
HP OpenView | 5.01 and 6.0 |
CiscoWorks | 4.0 |
CiscoWorks for Switched Internetworks (CWSI) | 2.1.1 |
CWSI Campus | 2.3 |
Essentials can be installed on the same machine as HP OpenView, OpenView Professional Suite, CiscoWorks 4.0, and CWSI Campus with no compatibility problems.
For remote device imports, the remote server must be a Solaris, HP-UX, or AIX machine. Essentials does not support remote device imports from Windows NT machines.
To avoid inconsistencies in how domain names are used in networks, Essentials uses the IP address of the server on which you installed Essentials when it interacts with web browsers. By using the IP address of the server, Essentials reduces the likelihood of name lookup failures between the server and the client machines that run web browsers.
You then need to restart the Essentials server by entering the following commands as root:
# /sbin/init.d/dmgtd stop # /sbin/init.d/dmgtd start
In addition to the standard network ports (telnet, tftp, etc.) Essentials uses the following TCP and UDP ports. These ports are added to /etc/services when you install Essentials:
http://server_name:1741
The Essentials installation program detects whether any of the default TCP ports are already in use on your system and prompts you to enter an available TCP port number for each port that has a conflict.
Refer to the "Setting Up Essentials" chapter for more information about accessing the server. Refer to the "Troubleshooting" appendix if you encounter problems.
The following system files are modified during the installation of Essentials:
Before starting CW2000, the kernel must be properly tuned. On most HP-UX machines, the values of nfile (kernel parameter for maximum number of open files) and ninode (parameter for maximum number of open inodes) are low by default. When CW2000 is started without tuning these parameters, the file table becomes full and the system must be rebooted.There might also be insufficient kernel resources such as semaphores or shared-memory segments.
At the end of a successful installation, the install script checks the kernel parameter values to ensure proper kernel tuning. If the parameters are found to be low, you are prompted with the following message:
INFO: Needs to tune the kernel.This will require a reboot Proceed with kernel rebuilding? [Y]
Upon confirmation, the script builds the kernel. Before the kernel is overwritten, you are prompted with the following message:
INFO: Kernel build completed. Overwrite /stand/system and Reboot with new kernel ? [Y]
Upon confirmation, the script completes the installation and reboots the machine from the newly built kernel.
If the kernel build is unsuccessful, daemons are not started. You are asked to tune the kernel and start the daemons.
This section describes how to install Essentials. If you are upgrading from an evaluation version or are reinstalling the product, see the "Installing Upgrades" section section for instructions before running the installation program.
The Essentials installation program takes approximately 20 minutes to complete if you use the express installation option. If you do not specify the express installation option, the installation takes longer because you have to respond to questions asked by the installation tool. See the "Custom Installation" section to see the questions asked.
Follow these steps to install Essentials:
Step 1 As root, mount the Essentials CD-ROM on a local or remote CD-ROM drive. Refer to "Mounting and Unmounting on HP-UX," for detailed instructions on mounting.
Step 2 Run the installation program.
For a local CD installation, enter the following commands:
# cd /cdrom # /setup.sh
For a remote CD installation, enter the following commands:
# cd remotedir # ./setup.sh
Where remotedir is the remote location where the Essentials CD-ROM is mounted.
The following message is displayed:
Software Install Tool Started.
The installation program then performs several preinstallation checks on your machine, such as TCP/IP address resolution, TCP/IP port usage, and disk space usage. These preinstallation checks cause some text to appear on the screen.
These preinstallation checks can generate two types of results:
Step 3 Answer any questions that result from the preinstallation checks. These questions could include one or more of the following:
If the preinstallation checks generate any of these questions, the installation program automatically selects the Custom installation option. Go to the section "Custom Installation" to continue with the installation.
If the preinstallation checks do not generate any of these questions, the installation program displays the following information about express installation and prompts you to select an install option:
The express install takes all defaults and places the product into /opt/CSCOpx. No more questions will be asked of you.Do you want the Express Install (y/n)? [Y]
Step 4 Select one of the two options for continuing with the Essentials installation:
If you entered Y when asked if you want the express installation, Essentials is installed using the default TCP ports specified in the "TCP and UDP Ports Used" section.
You do not need to answer any additional questions. The installation program keeps you updated on the status of the installation as it installs Essentials using the default TCP ports specified in the "TCP and UDP Ports Used" section. Any error or warning messages are displayed on your screen. When the install completes, any error messages that appeared during the installation appear on the screen again, followed by this message:
Software Install Tool Completed.
You have now completed the installation program. If you encountered any errors, or to verify the directories installed on your system, see "Troubleshooting."
If you entered N when asked if you want the express installation, or if you had to answer any questions that resulted from the installation program's preinstallation checks, the installation tool begins the Custom installation option by asking a question similar to the following:
Where should the product be installed? [/opt/CSCOpx]
To accept the default, which is shown in square brackets, press Return or enter a new path where you want Essentials to be installed.
The installation program installs Essentials using the default TCP ports specified in the "TCP and UDP Ports Used" section. Any error or warning messages are displayed on your screen. When the install completes, any error messages that appeared during the installation appear on the screen again. The following message appears when the installation is complete:
Software Install Tool Completed.
You have now completed the Essentials installation. If you encountered any errors during the installation, or to verify the directories installed on your system, see "Troubleshooting."
Continue the installation process by doing one of the following:
You can reinstall Essentials while preserving your existing data. In addition, you can add new functionality to Essentials by downloading new components from CCO.
To reinstall Essentials, follow these steps:
Step 1 As root, create a directory for example /var/tmp/backup, to store your backup database:
# mkdir /var/tmp/backup
Step 2 Change the ownership of the backup directory to bin by entering the following command:
# chown bin backup_dir
where backup_dir is the directory you selected as the backup location.
Step 3 From the Essentials interface, select Admin > System Admin > Back Up Data Now. The Back Up Data Now dialog box appears.
Step 4 Enter the name of the directory you specified in Step 1 in the Backup Directory field. Click Finish to complete the backup.
You are notified that the data files were successfully backed up and the files px.db and px.log were created in the directory you specified. In addition, a new tar file is created, CRM_filebackup.tar, which includes software image files and other files that Essentials needs to back up.
Step 5 Install Essentials as explained in the "Running the Essentials Installation Program" section. The upgrade procedure is identical to performing a new installation.
If you have CCO access, you can consult the Essentials web page at the following URL to download any available software enhancements:
http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000
Refer to the readme files and Resource Manager Essentials Release Notes for HP-UX for additional information on installing new features and enhancements.
To stop and restart the Essentials Daemon Manager, follow these steps:
Step 1 Log in as root.
Step 2 Open a command prompt or shell window.
Step 3 Stop the server by entering the following command at the prompt:
# /etc/init.d/dmgtd stop
Step 4 Start the server by entering the following command at the prompt:
# /etc/init.d/dmgtd start
 | Caution You must use the Essentials uninstallation program to remove the product. If you attempt to remove Essentials manually, you can damage your system. |
To remove Essentials, follow these steps:
Step 1 Uninstall CWSI Campus.
Step 2 Stop all CWSI server processes.
Step 3 Enter the following commands as root to start the uninstall script:
# cd /opt/CSCOpx/bin # ./uninstall.sh
where /opt is the directory you specified to install Essentials if you did not use the default location.
A list of all installed Essentials packages appears, followed by this prompt:
INFO:Delete all the CiscoWorks2000 Essentials packages listed above? [yes]
Step 4 To remove all Essentials packages, press Return or enter Y (yes). The specified packages are removed and a verification message appears. To cancel the removal of Resource Manager Essentials, enter N (no).
When you remove Essentials, the uninstall script removes the changes made to the /etc/services file. The /etc directory still contains all system file changes. The uninstall messages are written to the /var/tmp/ciscouninstall.log file.
When the uninstall script completes, two lists of packages appear on the screen: those that were removed, and those that could not be removed.
Step 5 Check /etc/syslog.conf for syslog changes. Check /etc/services to make sure port assignments for the Daemon Manager and web server have been removed. See the "Troubleshooting" appendix for more information.
Software Management stores images that are not removed by the Essentials uninstallation procedure. If you want to permanently remove Essentials, you must manually remove these files from /opt/CSCOpx/files/sw_images.
If you move the configuration archive directory to a new location, for example, newDir, the Essentials uninstallation script deletes all files with the following extensions:
newDir/config/any_subdirectory/*running.cfg
newDir/config/any_subdirectory/*startup.cfg
newDir/config/any_subdirectory/*running.dfr
newDir/config/any_subdirectory/*running.dfc
newDir/config/any_subdirectory/*running.cmt
If you created your own files with these extensions, you must move them to a different directory before uninstalling Essentials.
To reinstall Essentials, follow the instructions in the "Running the Essentials Installation Program" section.
Posted: Wed Nov 17 16:16:54 PST 1999
Copyright 1989-1999©Cisco Systems Inc.