|
|
This chapter describes the factors that you should consider before installing Essentials and CWSI Campus on a Solaris system and a high-level quick reference of the tasks required to install both products.
This chapter contains the following sections:
The CiscoWorks2000 Family of Products consists of two products: Resource Manager Essentials (Essentials) and CWSI Campus. It ships in two configurations:
If you order Essentials only, you do not receive the CWSI Campus product or documentation (other than the CWSI Campus information in this document). If you order Essentials and CWSI Campus together, you receive both products and their documentation.
![]() | Caution You must install Essentials on the system before installing CWSI Campus. CWSI Campus will not install if Essentials is not installed first. |
The system requirements for Essentials and Essentials and CWSI Campus combined are summarized in Table 1-1. The requirements listed for Essentials are for the server system only. For Essentials client system requirements, refer to the "Installing Essentials" chapter, "Client Requirements" section.
For more current and detailed system requirements, and information about how many devices you can manage with Essentials and CWSI Campus, refer to the Release Notes for CW2000 (Solaris).
| Requirement Type | Essentials Server | Essentials and CWSI Campus |
|---|---|---|
System hardware |
|
|
Memory (RAM) | 160 MB minimum | 256 MB minimum |
Available drive space1 |
|
|
System software2 | Solaris 2.5.1 or Solaris 2.6 | Solaris 2.5.1 or Solaris 2.6 |
Browser | None3 | Netscape 4.0 or higher4 |
Additional required software | None | Essentials |
| 1See the "Installing Essentials" chapter, "Server Requirements" section for information about checking the available disk space on your system. 2Solaris 2.5.1 might require a patch. See the "Installing Essentials" chapter, "Server Requirements" section for detailed information. 3No browser is required for the Essentials server system. Client systems must have a supported browser installed. Refer to the "Installing Essentials" chapter, "Client Requirements" section for more information. 4The browser is used only to display the CWSI Campus online help. |
Files that Essentials downloads to the server are stored in the /tmp directory or it's subdirectories. You should make sure that there is sufficient available space in the /tmp directory for all files that you plan to download.
Typically, the majority of these downloaded files are device software image files. These files are up to 4 MB in size. To determine how much available space you need in the /tmp directory, multiply the number of device software image files you plan to store by 4 MB. For example, if you plan to store 30 software image files, you will need at least 120 MB (30 x 4 MB) available in the /var directory.
In addition, you will need space for some smaller downloaded files and temporary files. To accommodate these other space needs, add at least 10% to the space that you need for software image files for your final calculation of available space in the /var directory. In the previous example, you would need at least 132 MB (120 MB + [120 MB x .10]) of available space in the /var directory.
This section describes the supported upgrade paths for this product release.
The following Essentials upgrade paths are supported in this product release:
All of these upgrades are performed using the Essentials installation program. Refer to the "Installing Essentials" chapter for instructions for using the installation program.
![]() | 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 2.1 to CWSI Campus 2.2 to continue using the CWSI/CWSI Campus product. |
The following CWSI Campus upgrade paths are supported in this product release:
These upgrades are performed using the CWSI Campus installation program. Refer to the "Installing CWSI Campus" chapter for instructions for using the installation program.
The next four chapters of this guide describe the process of installing Essentials and CWSI Campus and setting up Essentials. Setting up CWSI Campus is described in the document Getting Started with CWSI Campus.
Each chapter starts with a quick-reference overview of the process described in the chapter. The detailed information follows the same order as the quick reference. Table 1-2 is a quick reference overview of the entire installation process.
| Task | Steps | References | ||
|---|---|---|---|---|
| Step 1 Prepare for installation. | "Installing Essentials" chapter, "Preparing To Install Essentials" section | ||
Step 2 Install the software. | "Installing Essentials" chapter, "Running the Essentials Installation Program" section | |||
Step 3 Verify and troubleshoot the installation. | "Troubleshooting" appendix | |||
| Step 1 Prepare for installation. | "Installing CWSI Campus" chapter, "Preparing To Install CWSI Campus" section | ||
Step 2 Install the software. | "Installing CWSI Campus" chapter, "Installing CWSI Campus" section | |||
Step 3 Start CWSI Campus. | "Installing CWSI Campus" chapter, "Starting CWSI Campus" section | |||
| Step 1 Access the server. | "Setting Up Essentials" chapter, "Accessing the Server" section | ||
Step 2 Perform administrator setup tasks. | "Setting Up Essentials"chapter, "Performing Administrator Tasks" section | |||
| Step 1 Set up Inventory (including Contract Connection). | "Preparing To Use Essentials Applications" chapter, "Setting Up Inventory" section | ||
Step 2 Set up Availability Manager. | "Preparing To Use Essentials Applications"chapter, "Setting Up Availability" section | |||
Step 3 Set up Syslog Analysis. | "Preparing To Use Essentials Applications" chapter "Setting Up Syslog Analysis" section | |||
Step 4 Set up Software Management. | "Preparing To Use Essentials Applications" chapter, "Setting Up Software Management" section | |||
| Step 1 Refer to Getting Started with CWSI Campus. | Getting Started with CWSI Campus |
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Sep 30 10:34:32 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.