|
|
This document discusses Cisco Resource Manager 1.1. Use this document with the Cisco Resource Manager Installation Guide for Solaris.
This release notes document consists of the following sections:
Make sure your server meets the following hardware and software requirements.
The hardware platform, memory, and disk space requirements for the Resource Manager server are
If your disk becomes full or your system runs out of memory, the Resource Manager database might become corrupted, requiring you to restore the database from a backup. To avoid any potential loss of data, make sure you back up the Resource Manage database frequently. [CSCdj83169]
Resource Manager requires either Solaris 2.6 or Solaris 2.5.1 (with patch 103738-xx).
If you are using Solaris 2.5.1, Cisco recommends you use patch 103738-03 or later (103738-05 as of the writing of this document) because it fixes a known Solaris problem with syslogd. The Solaris patch is available only to users with Sun service contracts. You can find additional information about the Solaris 2.5.1 patch at the following location:
http://www.cisco.com/kobayashi/sw-center/netmgmt/rm-planner.shtml
Resource Manager lets you import device information from both local and remote network management databases identified in Table 1.
Resource Manager can be installed on the same machine as HP OpenView, CiscoWorks, and CiscoWorks for Switched Internetworks (CWSI) without any compatibility problems.
For remote device imports, the remote server must be a Solaris, HP-UX, or AIX machine. Resource Manager does not support remote device imports from Windows NT machines.
| Software | Version |
|---|---|
HP OpenView | 4.11, 5.0, and 5.01 |
CiscoWorks | 3.2 and 4.0 |
CiscoWorks for Switched Internetworks (CWSI) | 1.3 |
Resource Manager is supported on the browsers shown in Table 2.
| Browser | Version1 | Operating System |
|---|---|---|
Netscape Navigator2 | 3.03 | Solaris 2.6 and Solaris 2.5.1 |
3.04 | Windows NT 4.0 and Windows 95 | |
4.03 | Solaris 2.6, Solaris 2.5.1, Windows NT 4.0, Windows 95, HP-UX 10.20, and AIX 4.2 | |
Microsoft Internet Explorer3 | 3.02 | Windows NT 4.0 and Windows 95 |
4.0 | Windows NT 4.0 and Windows 95 |
Resource Manager supports the devices listed in Table 3. See the "Cisco IOS Versions Supported" section for information on the supported Cisco IOS versions. See the "Devices Supported by Software Management" section for the devices the Resource Manager Software Management module supports.
| Routers and Access Servers | Switches | Hubs | ||
|---|---|---|---|---|
| Cisco | CiscoPro | Cisco | CiscoPro | |
CS500 |
|
| Viper Switch CPW16, ESP2015 | FastHub 300 and FastHub 100+Series FastHub 316T, 316C, 3116, 216T, 116T, 116C, 1116 |
741, 742, 743, 744, 751, 752, 753, 761, 762, 765, 766, 771, 772, 775, 776 | CPA741, CPA742, CPA743, CPA744, CPA751, CPA752, CPA753, CPA761, CPA762, CPA765, CPA766, CPA771, CPA772, CPA775, CPA776 | Catalyst 1200, 1220, 1600, 1700, 1800, 1900, 2200, 2600, 2820, 2900, 2910, 2926, 3000, 3001, 3011, 3100, 3200, 3500, 3900, 5000, 5002, 5301, 5500, 5505 |
|
|
1000, 1003, 1004, 1005, 1020 | CPA1000, CPA1003, CPA1004, CPA1005, CPA1020 | Etherswitch 1000, 10/100, 1200, 1220, 1400, 1402, 1408, 1420, 1422, 1428, 1442, 1448, 1600, 1601, 1900, 2100, 2200 | CPW1100, CPW1200, CPW1220, CPW1400, CPW1402, CPW1408, CPW1420, CPW1422, CPW1428, CPW1442, CPW1448, CPW1600, CPW1601, CPW1900, CPW2200 |
|
1601, 1602, 1603, 1604 | CPA1601, CPA1602, CPA1603, CPA1604 | Workgroup concentrator 1000, 1100, 1400 |
|
|
|
| LS1010, LS2020 |
|
|
2500, 2501, 2502, 2503, 2504, 2505, 2507, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 2516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF | CPA2500, CPA2501, CPA2502, CPA2503, CPA2504, CPA2505, CPA2507, CPA2509, CPA2510, CPA2511, CPA2512, CPA2513, CPA2514, CPA2515, CPA2516, CPA2517, CPA2518, CPA2519, CPA2520, CPA2521, CPA2522, CPA2523, CPA2524, CPA2525, CPA2501CF, CPA2502CF, CPA2501LF, CPA2502LF | Stratacom BPX, IPX, IGX (Version 8.1 and later) StrataCom Axis (Version 2.1 and later) |
|
|
2102, 2202 |
|
|
|
|
3000, 3620, 3640, 3101, 3102, 3103, 3104, 3202, 3204 | CPA3620, CPA3640
|
|
|
|
4000, 4000-M, 4500, 4500-M, 4700, 4700-M | CPA4000, CPA4000-M, CPA4500, CPA4500-M, CPA4700, CPA4700-M |
|
|
|
AS5200, AS2509RJ, AS2511RJ, AS5300 access servers |
|
|
|
|
7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513 |
|
|
|
|
Router IGS, AGS+, AccessPro RC, AccessPro EC, Router Gateway Server |
|
|
|
|
The Resource Manager Software Management module supports Cisco IOS system software upgrades for the following devices:
Full support is provided for devices running Cisco IOS Versions 10.3 to 11.2 only. Unless your devices are running at least Cisco IOS Version 10.3, all MIB values might not be supported. As a result, devices running versions of IOS earlier than 10.3 might not provide all device details.
The documentation for Resource Manager consists of:
Customer documentation can also be found on the Cisco Enterprise Customer Documentation CD or on Cisco Connection Online (CCO).
A CCO web page for Resource Manager contains links to marketing and technical documentation and includes the latest downloadable Resource Manager files. To find the latest Resource Manager information, point your web browser to the following location:
http://www.cisco.com/kobayashi/sw-center/netmgmt/rm-planner.shtml
This section contains the notes and general caveats that apply to Resource Manager on the Solaris 2.6 and 2.5.1 operating systems. It consists of the following sections:
A Solaris SPARC20 or equivalent is the lowest workstation in the Sun product line on which Cisco recommends you install Resource Manager.
Resource Manager relies on host-name-to-IP-address lookup for accessing devices and interacting with the web server. The lookup mechanism used by the Resource Manager server must guarantee that all host name lookups for a given IP address always return the same string for all environments in your network. See the Cisco Resource Manager 1.1 Installation Guide for Solaris for more information about server requirements.
Using the Apache http server to support software not installed by Cisco Resource Manager is not supported.
The following caveats describe installation issues.
If the Solaris system on which you are installing Resource Manager already has a web server running on port 80, you must ensure the following line appears in /etc/services to indicate its presence:
httpd 80/tcp # web server
If you do not enter this line, Resource Manager will conflict with the other web server. [CSCdj60413]
If you install Resource Manager somewhere other than the default directory (/opt/CSCOpx), the uninstall script, uninstall.sh, does not remove the Resource Manager directory. To resolve this issue, run the following commands after running uninstall.sh:
# cd /opt # rm -f ./CSCOpx # rm -rf directory
where directory is the full pathname to the directory in which Resource Manager was installed.
If you are upgrading to Resource Manager 1.1 from Resource Manager 1.0, Cisco recommends you back up your database completely when you complete the upgrade.
If any screens do not look right, for example, if a graph looks awkward or text scrolls off a screen, reload or refresh the browser page. Usually, if you reload or refresh the page, the problem corrects itself.
Printing does not work reliably. To print an exact copy of a Resource Manager screen, use the Print Screen or Capture Screen function on your machine.
If your site operates behind a firewall that is filtering JavaScript, you might not connect successfully to the CCO home page if you select Home > Cisco Connection Online > Home Page. Instead, the CCO home page causes errors to be generated because of JavaScript references outside <SCRIPT> tag boundaries. To avoid this situation, do not select the Home Page, as it is the only page using JavaScript. [CSCdj56560]
The following sections describes caveats for particular web browsers.
If you alternate between Resource Manager windows and windows not generated by Resource Manager, Navigator 3.x might not display the Resource Manager navigation tree. If you have administrative privileges, click Login. If you logged in previously, the navigation tree appears. If you did not log in previously, the Login dialog box appears and you can log in as you normally would.
If you do not have administrative privileges, exit the browser and relaunch it.
To avoid this situation completely, do not use the Resource Manager browser window for interacting with other Web-based applications. Launch a separate browser instead. [CSCdj56775]
The Navigator 4.03 right mouse button popup menu offers the Open Frame in New Window option. If you select this option while in Resource Manager and continue using Resource Manager in the new window, you will receive error messages and Resource Manager will not complete its tasks. To avoid this, complete all tasks in Resource Manager-presented windows. [CSCdj50947]
On Solaris, HP-UX, and AIX systems, Navigator 4.03 does not dynamically update the Reachability Dashboard (Tasks > Availability > Reachability Dashboard) when devices change state. To update the information in the Reachability Dashboard, click the Navigator Reload button. [CSCdj55007]
If you access the Glossary (Help > Glossary) with Navigator 4.03 on a Solaris, HP-UX, or AIX system, clicking the Back button in the help window might take you to the help contents page instead of the beginning of the glossary section. To return to the Glossary, click Glossary. [CSCdj57449]
If you are using Navigator 4.03 on an HP-UX system, the Get button does not appear when you open the Ping dialog box (Tools > Connectivity Tools > Ping) or the Traceroute dialog box (Tools > Connectivity Tools > Traceroute). To display the Get button, either enter the desired name in the Device field and press Enter, or click on the space between the Device field and the Clear button. With either action, the Get button appears. [CSCdj58691]
If you click the Help button in the Filter Select Devices window after logging into Resource Manager when using Navigator 4.03, Navigator displays a message stating that access is disallowed. The Filter Select Devices window appears when you add static or dynamic views, or when you produce reports. [CSCdj60013]
If you click the Help button in the Filter Select Devices window when using Internet Explorer 3.02, Internet Explorer displays a Microsoft Jscript runtime error instead of help. The Filter Select Devices window appears when you add static or dynamic views, or when you produce reports. [CSCdj62204]
You cannot correct typing errors in the Save Static Views dialog box (Admin > Device Views > Add Static Views > Next) with the Backspace key if you are using Internet Explorer 4.0. To correct text, you can either select it and enter the desired information, or you can move the cursor to the left of the mistyped characters and press the Delete key to remove them. [CSCdj56328]
The following caveats describe issues with administration functions.
In the software management debug log file, both Telnet access information (Telnet password, enable password, TACACS, enable secret, local username password, and CCO passwords) and read/write device community strings were found to be written in clear text, enabling unauthorized access to managed devices.
A patch is available that prevents Telnet access information from being written to the debug log file. In addition, the existing debug file containing password information is removed. Refer to the Readme file for Cisco Resource Manager 1.1 supporting your platform (NT or Solaris) and the Cisco Rescource Manager 1.x Security Issues document for additional information on the security patch. [CSCdk13298]
You can download the patch using the URL: http://www.cisco.com/kobayashi/sw-center/netmgmt/rm-planner.shtml.
Change Device Attributes incorrectly has debugging mode permanently enabled when it updates the database with changes to device attributes such as SNMP community strings, Telnet user ID, and passwords. These values written to the database will appear in a debugging log named dbi_debug.pl, which is stored in /tmp. Only those values modified by the Change Device Attributes command will appear in the debugging log.
This file contains information that could potentially allow access to users with unauthorized access to devices. Resource Manager system administrators should be aware that this file exists and should be removed after running Change Device Attributes. [CSCdk13579]
In the "Preparing to Use Resource Manager Packages" chapter of the Cisco Resource Manager 1.1 Installation Guide for Solaris, you are told to verify TFTP is enabled by entering either of the following commands:
# netstat -a | grep tftp
or:
# /opt/CSCOpx/bin/mping -s tftp localhost_machine_name
The /opt/CSCOpx/bin/mping command does not work for Solaris 2.6. Use the netstat command instead. [CSCdj58219]
If you start Resource Manager by logging in as root and entering the following command in a C shell
# /etc/init.d/dmgtd start
make sure you do not suspend the root session using the suspend command. If you suspend the root session after manually starting Resource Manager, other processes such as the Daemon Manager, DIServer, and IcServer are also suspended. To resolve this issue, unsuspend the root session, and the processes restart normally.
If you select Tasks > Availability > Availability Monitor and select a device to view its availability, the Availability Monitor dialog box appears. If you click the Interface Status icon for a device, the Interface Details dialog box appears. If you use the page up or page down keys to scroll up and down the screen, you might get the following error:
Internal Error: Unable to retrieve cookie for form element <element> Probable Cause: The cookie might have expired or it was not set in the browser.
This might result from the expiration of the cookies, which are used to pass cgi-bin parameters to the reports. To resolve this issue, retry the operation. [CSCdj19695]
The Resource Manager Inventory Manager was designed to actively manage approximately 1,000 devices. Due to restrictions in the software, the Availability module does not correctly track devices if you ever added or imported more than 4,000 devices into the Resource Manager database. If you added or imported more than 4,000 devices, the AvInputGen process has a memory failure, and the list of devices polled by the Availability module is never updated. To avoid this issue, upgrade to Availability 1.2 when it becomes available on CCO. Until Availability 1.2 is available, contact the TAC for assistance. [CSCdj83419]
When you add or import a device or change device information, avoid using angle brackets (< or >) in the User or Serial Number fields. When some browsers encounter these characters, they might interpret the information incorrectly. [CSCdj24567]
If you encounter problems when importing devices, make sure your target system is configured correctly. Consult the following Resource Manager online help topics for instructions on what you need to do before importing devices:
The import process writes files containing community strings in /tmp under two conditions:
A workaround is to restrict permissions that enable access to root and bin directories. [CSCdk14993] and [CSCdk14992]
When troubleshooting a device import from HP OpenView or CiscoWorks, you can run the DataPrep.pl script from the command line to help determine the cause of the failure. If you enter the command-line options incorrectly or omit them, DataPrep.pl will not report any errors. Refer to the Resource Manager online help for the correct use of the DataPrep.pl script and troubleshooting. [CSCdj54272]
Software Management provides the capability of distributing software to most Cisco IOS devices and Catalyst switches. The distribution is verified and scheduled so multiple devices can be updated quickly and easily.
The following caveats describe issues with Software Management.
Cisco Resource Manager 1.1 will always attempt to erase Flash memory when a new Cisco IOS image is downloaded [CSCdj79501].
If you import a large number of images that takes more than 20 minutes to complete, the browser might time out and display a message that says, "Document contains no data." To avoid this issue, decrease the number of images you import at one time to ensure the import takes less than 20 minutes. [CSCdj25733]
If you import an image from CCO when the temporary directory's file system is full, you might receive server errors when executing other Resource Manager functions. To avoid these errors, keep the temporary directory clear of unneeded files. [CSCdj44161]
If you select the Use tftp fallback option in the Job Control Information dialog box when setting up an upgrade for IOS devices, Resource Manager leaves unused image software image files in your temporary directory (/var/tmp). Cisco recommends you remove these files from this directory when the upgrade is complete. [CSCdj62050]
If you do not select the Error halts processing of subsequent devices option in the Job Control Information dialog box, the software upgrade status is reported as complete even if some devices failed to upgrade their software. Review the Job Summary windows to confirm the success or failure of the upgrade on each device in the job. [CSCdj57460]
When upgrading software images, single Flash bank devices require Telnet access. Therefore, when adding the device to the Resource Manager, you must provide the appropriate passwords and access information. Refer to the online help for more information about passwords and access information.
RSP 7000 and 7500 series routers running Cisco IOS Versions 10.3(x) through 11.0(x) do not support Flash MIBs. As a result, RSP 7000 and 7500 series routers running one of these Cisco IOS versions require Telnet access when you upgrade their software images and you must provide the appropriate passwords and access information. Refer to the online help for more information about passwords and access information.
Router Switch Modules (RSMs) on Catalyst 5000 and 5500 devices run IOS software and have their own host names and IP addresses. To upgrade the RSM on a Catalyst device, select the IOS device type in the Select Device Type dialog box (Tasks > Software Management > Distribute Images) and click Next. The Select IOS Devices dialog box appears. Click Add and enter the host name of the RSM module in the device name field in the dialog box that appears. Add the RSM host name to inventory as well. [CSCdj62469]
The following caveats describe issues with syslog analysis.
Syslog analysis does not show the primary facility of Channel Interface Processor (CIP) messages. For example, the CIP message
..%CIP4-6-MSG: %MSG802-6-LLC.START: Starting LLC-2...
will be stored as
%MSG802 6 LLC_START Starting LLC-2...
where MSG802 is the facility, 6 is the severity, LLC_START is the mnemonic, and the remaining text is the description. The first part (CIP4-6-MSG) is not used. Only the second part of the CIP messages is stored. [CSCdj16580]
For Catalyst devices only: If you do not receive syslog messages in the syslog analysis reports (Tasks > Syslog Analysis) and the syslog message file (/var/log/syslo.info file pointed to by local7.info in the /etc/syslog.conf file) does contain messages, the DNS name or the name defined in /etc/hosts is different from the name in the Resource Manager inventory. To resolve this issue, change the DNS name or the name in /etc/hosts so the device name is the same as the name in the Resource Manager inventory. [CSCdj58347]
Syslog analysis ignores some valid messages if the message it is processing is from a device that is imported with an IP address and is in an unmanaged state. To avoid this situation, import devices using their host names rather than their IP addresses. [CSCdj60068]
Syslog reports do not have IOS explanations for some messages. Refer to the latest IOS reference manual for additional information on reported messages. [CSCdj61218]
SmartNet or warranty support calls for Resource Manager 1.1 running on the Solaris Japanese release are handled during Japan standard time only through the Japanese TAC.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
This section lists the bug ID numbers and the page on which they are found in this document.
CSCdj16580 16
CSCdj19695 12
CSCdj24567 13
CSCdj25733 14
CSCdj44161 14
CSCdj50947 10
CSCdj54272 14
CSCdj55007 10
CSCdj56328 11
CSCdj56560 9
CSCdj56775 10
CSCdj57449 10
CSCdj57460 15
CSCdj58219 12
CSCdj58347 16
CSCdj58691 10
CSCdj60013 10
CSCdj60068 16
CSCdj60413 8
CSCdj61218 16
CSCdj62050 14
CSCdj62204 10
CSCdj62469 15
CSCdj79501 14
CSCdj83169 2
CSCdj83419 13
CSCdk13298 11
CSCdk13579 11
CSCdk14992 13
CSCdk14993 13
Posted: Thu Sep 30 16:19:04 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.