|
|
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 network 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 Essentials installation, and references to more detailed information about each task. The information in the rest of this chapter follows the same order as the quick reference.
| Task | Steps | References | ||
|---|---|---|---|---|
| Step 1 Verify that server requirements are met. | "Server Requirements" section "Before You Begin" chapter, "System Requirements" section | ||
Step 2 Verify that client requirements are met. | "Client Requirements" section | |||
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. | "Using Server IP Address" section | |||
Step 5 Note the TCP ports that Essentials uses and check for conflicts with existing applications. | "TCP and UDP Ports Used" section | |||
Step 6 Note the system files that are modified during installation. | ||||
| Step 1 (Upgrade only) Back up your data files. | "Installing Upgrades" section | ||
Step 2 Mount the Essentials CD-ROM. | "Mounting and Unmounting on Solaris" appendix | |||
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. | "Custom Installation" section | |||
| Step 1 Verify that the correct files and directories are installed. | "Troubleshooting" appendix, "Checking Files and Directories After Installation" section | ||
Step 2 Analyze installation error messages. | "Troubleshooting" appendix, "Understanding Installation Error Messages" section | |||
Step 3 Collect the server information to determine if the installation is complete. | "Troubleshooting" appendix, "Collecting Server Information" section |
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 "Before You Begin" chapter, "System Requirements" section.
To verify the amount of available disk space in each of the specified partitions and directories, enter the following command:
# df -k 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 Solaris 2.5.1 (with patch 103738-03) or Solaris 2.6. Patch 103738-03 is required for Solaris 2.5.1 only when a significant number of messages are processed by syslogd (the daemon process that reads and forwards system messages to the appropriate log file and users when necessary).
Use the showrev -p command to make sure the 103738-03 patch (for Solaris 2.5.1) is applied.You can find additional information about the Sun patch at the following location:
http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000/rm-essentials.shtml
CDDM (Cisco DNS/DHCP Manager) can be downloaded from CCO and provides Syslog and TFTP daemons as part of its product. Make sure that you do not have the CDDM installed on the system on which you plan to install Essentials. 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 system.
Clients use a web browser running on a workstation or PC to access the Essentials server. The hardware and software requirements for client workstations or PCs are as follows:
Essentials supports clients running the browsers shown in Table 2-2.
| Browser | Version |
|---|---|
Netscape Navigator | 4.04 and 4.05 on Solaris 2.5.1 or 2.6, Windows NT 4.0, Windows 95, AIX 4.2.1 or 4.3, and HP-UX 10.20 or 11.0 |
Microsoft Internet Explorer | 4.01 with Internet Explorer Service Pack 1 on Windows NT 4.0 and Windows 95 |
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.
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. You can view these man pages in the following ways:
1. 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.
2. If the MANPATH variable is not set, you can view the man pages while you are in the directory /opt/CSCOpx/man (where /opt/CSCOpx is the directory in which Essentials was installed) using the following command:
man -M . pagename
Where pagename is the name of the man page.
3. If the MANPATH variable is not set, you can view the man pages from any directory using the following command:
man -M /opt/CSCOpx/man pagename
Where /opt/CSCOpx is the directory in which Essentials was installed and pagename is the name of the man page.
Table 2-3 lists the software that Essentials supports for importing device information. You can import devices remotely from a UNIX system only. Essentials does not support remote device imports from Windows NT systems.
| Software | Version |
|---|---|
HP OpenView | 4.11, 5.01 |
CiscoWorks | 3.2, 4.0 |
CiscoWorks for Switched Internetworks (CWSI) | 2.1.1 |
CWSI Campus | 2.2 |
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 must restart the Essentials server by entering the following commands as root:
# /etc/init.d/dmgtd stop # /etc/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 Essentials installation:
This section describes how to install Essentials. If you are upgrading from a previous version of the product, or you are reinstalling the product, go to the "Installing Upgrades" section for instructions before running the installation program.
If you do not specify the express installation option, the installation takes longer because you must respond to questions asked by the installation tool. See the "Custom Installation" section to see the questions asked.
To install Essentials, follow these steps:
Step 1 As root, mount the Essentials CD-ROM.
You can mount the CD-ROM using either of the following methods:
Or
Refer to the appendix "Mounting and Unmounting on Solaris" for detailed instructions for mounting the CD-ROM.
Step 2 Run the installation program.
For a local CD installation, enter the following commands:
# cd /cdrom/cdrom0/ # sh ./setup.sh
For a remote CD installation, enter the following commands:
# cd remotedir # sh ./setup.sh
where remotedir is the remote location where the Essentials CD-ROM is mounted.
The following message is displayed:
Software Install Tool Started.
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.
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 and 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 and displays any error or warning messages on your screen. When the install completes, any error messages that appeared during the installation appear on the screen again, followed by the following message:
Software Install Tool Completed.
You have now completed the installation program. If you encountered any errors, check the installation log file /opt/CSCOpx/ciscoinstall.log (where /opt/CSCOpx is the directory in which you installed Essentials). For troubleshooting information, or to verify the directories installed on your system, refer to the "Troubleshooting" appendix.
Continue the installation process by doing one of the following:
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, check the installation log file /opt/CSCOpx/ciscoinstall.log (where /opt/CSCOpx is the directory in which you installed Essentials). For troubleshooting information, or to verify the directories installed on your system, refer to the "Troubleshooting" appendix.
Continue the installation process by doing one of the following:
This section explains how to install Essentials if you have Cisco Resource Manager or Essentials installed on your machine. Upgrading to Essentials involves the following major steps:
1. Backing up your current data files to avoid any potential loss of data.
2. Running the Essentials installation program to install the new version.
In addition, you can add new functionality to Essentials by downloading new components from CCO.
 | Caution If your existing installation of Cisco Resource Manager is not working properly, remove it before installing Essentials. For instructions, see the Cisco Resource Manager 1.1 Installation Guide for Solaris. Then you can install Essentials using the procedure for a new installation, as described in the "Running the Essentials Installation Program" section. This process will not preserve your existing database. |
The procedure for upgrading from Resource Manager 1.1 to Essentials is slightly different from the procedure for reinstalling Essentials or upgrading from the Essentials evaluation version to the licensed version. The following sections describe each type of upgrade.
You can upgrade from Resource Manager 1.1 to Essentials 2.0. Your existing device information will be preserved and automatically added to the Essentials device inventory. Resource Manager 1.1 user logins and passwords are not preserved during the upgrade.
| Caution If you upgrade Resource Manager 1.1 to Essentials 2.0, CWSI 2.1 will not work on your system. You must also upgrade CWSI to CWSI Campus 2.2 to continue using CWSI/CWSI Campus. |
To upgrade from Resource Manager 1.1 to Essentials 2.0, 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 Resource Manager interface, select Admin > System Admin > Backup Data. The Backup Data dialog box appears.
Step 4 To perform the backup now, click Now.
Step 5 Enter the name of the directory you specified in Step 1 in the Backup Directory field.
Step 6 Leave Now as the backup date and time (do not modify the values), then click Next.
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 7 Install Essentials as explained in the "Running the Essentials Installation Program" section. The upgrade procedure is identical to performing a new installation.
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 Resource Manager 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 refer to 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 Essentials Release Notes for Solaris for additional information on installing new features and enhancements.
| 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 Enter the following commands as root to start the uninstall script:
# cd /opt/CSCOpx/bin # sh ./uninstall.sh
where /opt is the directory you specified to install Resource Manager 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 above listed Resource Manager Essentials pkgs from the system? [yes]
Step 2 To remove all Resource Manager 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 Resource Manager 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: packages that were removed, and packages that could not be removed.
Step 3 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.
To reinstall Essentials, follow the instructions in the "Running the Essentials Installation Program" section.
Posted: Thu Sep 30 10:31:40 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.