|
|
Cisco Resource Manager is a suite of web-based network management tools integrated into a network desktop. Resource Manager includes a web-server component, web-based tools, and web browser capability. Resource Manager is based on a client/network architecture that connects multiple web-based clients to a network server. Resource Manager enables the deployment, monitoring, and troubleshooting of devices across your network.
Resource Manager consists of the following packages:
You can install the Resource Manager server on a Solaris workstation and use your web browser tool on a Windows PC or UNIX workstation to display Resource Manager.
This chapter includes the following sections:
Before you install Resource Manager, you need to make sure your server and client environments meet the hardware and software requirements described in the following sections. In addition, if you plan on importing device information from CiscoWorks, you must have CiscoWorks Version 3.2 installed on your system or on a system on your network before installing Resource Manager.
Make sure your server meets the following hardware and software requirements and software compatibility recommendations.
The hardware platforms, memory, and disk space requirements for the Resource Manager server are
| Package Name | Size |
|---|---|
| System Administration and Device Views Tools | < 60 MB |
| Availability | < 10 MB |
| Inventory | < 1 MB |
| Syslog Analysis | < 2 MB |
| Software Management | < 3 MB |
# df -k /opt
The software required for Resource Manager is
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 2.5.1 patch at the following location:
http://www.cisco.com/kobayashi/sw-center/netmgmt/ rm-planner.shtm
Table 1-2 lists the Resource Manager supported software for device import.
| Software | Version |
|---|---|
| HP OpenView | 4.0.1, 4.1, or 4.111 |
| CiscoWorks | 3.2 and 3.032 |
You can install Resource Manager on the same machine as CiscoWorks for Switched Internetworks (CWSI) 1.3, but device import is not supported.
Resource Manager is supported on the browsers shown in Table 1-3.
| Browser | Version |
|---|---|
| Netscape Navigator | 3.01 with NT 4.0, Windows 95, and Solaris 2.4 (with Oct/Nov 1996 cluster patch) and 2.5.1 (with patch 103738-03) |
| Microsoft Internet Explorer | 3.01 and 3.02 with NT 4.0 and Windows 95 |
To avoid conflicts due to inconsistencies in how domain names are used in networks, Resource Manager uses the IP address of the server when it interacts with web browsers. By using the IP address of the server, Resource Manager reduces the likelihood of name lookup failures between the server and the client machines that run web browsers. Because the IP address is used, the following conditions apply:
kill -HUP <server_process_id_number>
Resource Manager uses the following Transmission Control Protocol (TCP) ports. These ports are added to /etc/services when you install Resource Manager:
Resource Manager uses the default port 80. If an existing web server is already configured to run on port 80 on the same machine on which Resource Manager runs, you receive a warning that port 80 is in use, and port 1741 is used for Resource Manager. If Resource Manager uses port 1741, make sure you append :1741 to the end of your server name when accessing the Resource Manager server through your browser, for example:
http://server_name:1741
Clients can use a workstation or PC to access the Resource Manager server. The following section explains client machine requirements.
The hardware and software requirements for the client workstations or PCs are
Once 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 information that is cached, you might want to make sure you have enough disk space for the amount of cached information you want to store. All Resource Manager information is stored on the Resource Manager server.
Client systems need to have either of the following web browsers:
If you experience browser problems, increase your disk cache settings. Disk cache should never be set to zero.
Clients must specify port 1741 if that is the port used by Resource Manager, for example:
http://server_name:1741
System administrators should set the following environmental variables for those users that need to perform administrator tasks directly on the server. It is not required for tasks users perform using the web interface.
This section describes how to install Resource Manager. The installation takes approximately 20 minutes to complete if you use the express install on a SPARCstation 20. If you do not specify the express install, the installation takes longer because you have to respond to each prompt issued by the installation tool.
The installation tool installs each Resource Manager package one at a time and ends with the following packages installed:
Follow these steps to install Resource Manager:
Step 1 As root, mount the Resource Manager CD-ROM or a local or remote CD-ROM drive. Refer to Appendix B, "Mounting and Unmounting on Solaris," for detailed instructions on mounting.
Step 2 To install Resource Manager
# cd /cdrom/cdrom0/
# ./setup.sh
# cd /cdrom/px/
# ./setup.sh
You get the following message:
Software Install Tool Started.
The Resource Manager installation tool performs several checks on your machine, such as TCP/IP address resolution, TCP/IP port usage, and disk space usage, and then displays information about express install.
The Express Install takes all defaults and places the product into /opt/CSCOpx. No more questions will be asked of you.
You now have two options to continue with the Resource Manager installation:
If you entered Y (yes) when asked if you want the express install, the Resource Manager installation begins. The installation tool informs you that it is installing Resource Manager into /opt/CSCOpx and /var/adm/CSCOpx and uses the following defaults:
The express installation takes approximately 20 minutes.
You do not need to answer any additional questions. The Resource Manager installation tool keeps you updated on the status of the installation. You see the following message when the installation is complete:
Software Install Tool Completed.
After the express installation completes, check the installation log, /tmp/ciscoinstall.log, for any lines that begin with ERROR or WARNING.
Now that you have installed Resource Manager, you can continue with Chapter 2, "Setting Up Resource Manager." To verify the directories installed on your system, see Appendix A, "Troubleshooting."
If you entered N (no) when asked if you want the express install, the installation tool asks the following question:
Where should the product be installed? [/opt/CSCOpx]
Step 1 To accept the default, which is shown in square brackets [opt/CSCOpx], press Return or enter a new path where you want Resource Manager to be installed. The installation tool tells you to enter a TCP port for the Daemon Manager to use.
Enter tcp port for Daemon Manager to use ? [42340]
Step 2 To accept the default TCP port [42340], press Return, or enter a different TCP port. The installation tool displays the input validation and asks you if the information is correct.
Step 3 Press Return if the values are correct.
The installation tool installs Resource Manager. After the Resource Manager base is installed, you see the following message:
The following packages are available:
CSCOavail (Availability) CSCOhlp (Online help) CSCOinv (Inventory) CSCOsa (Syslog Analysis)CSCOswim (Software Management)
Select package(s) you wish to process (or 'all' to process all packages). (default:all)
Step 4 To process all packages, press Return (or enter all). The installation tool processes all packages. When the installation tool reaches the Software Management package, it asks you if you want to test the mail notification.
Step 5 Press Return to test the mail notification. The installation tool tells you to enter the e-mail address to send the test message to.
Step 6 Enter the e-mail address of the administrator that is to receive mail notifications after the distribution of software to devices, and press Return. That person receives a test message indicating that the mail notification is working correctly.
Step 7 To exit the installation process, enter q (quit) when asked again which packages you wish to process. The installation tool verifies that the packages were installed correctly and returns your system prompt.
You have now completed the Resource Manager installation. Continue with Chapter 2, "Setting Up Resource Manager." To verify the directories installed on your system, see Appendix A, "Troubleshooting."
If you want to remove Resource Manager, follow these steps:
Step 1 To remove Resource Manager, you must be root and enter the following script:
# /opt/CSCOpx/bin/uninstall.sh
The following message is displayed:
INFO:Checking for packages on the system. Please wait . . .
INFO:List of packages installed on this system:
CSCOsa CSCOavail CSCOinv CSCOhlpCSCOswim CSCOxrtsCSCOmd
CSCOnetc
CSCOweb
CSCOtcl
CSCOperl
CSCOdb
INFO:Delete all the above listed packages from the system? [yes]
If the installation tool encountered problems and did not install uninstall.sh, enter the following command to remove the packages:
# pkgrm pkg_name (where pkg_name can be any package in step 1 above)
Step 2 To remove all Resource Manager packages, press Return or enter Y. The specified packages are removed and a message is displayed indicating the removal was successful. To cancel the removal of Resource Manager, enter N.
When you remove Resource Manager, /etc still contains all system file changes.
Step 3 Remove the following files, which are used for Daemon Manager startup and shutdown, if they still exist after running uninstall.sh:
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 Appendix A, "Troubleshooting," for more information.
To reinstall Resource Manager, refer to the "Running the Resource Manager Installation Script" section earlier in this chapter.
|
|