|
|
This document discusses Cisco Resource Manager 1.1. Use this document with the Cisco Resource Manager 1.1 Installation Guide for Windows NT.
This release notes document consists of the following sections:
Make sure your server meets the following hardware and software requirements and software compatibility recommendations.
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]
The software requirements for Resource Manager are:
The following software is recommended:
Step 1 Install Microsoft Windows NT Server 4.0 or Microsoft Windows NT Workstation 4.0.
Step 2 Install IIS 2.0.
Step 3 Install Service Pack 3.0.
Step 4 Install IIS 3.0.
Step 5 Install Internet Explorer 4.0 if this is your selected browser.
Step 6 Reboot your system.
Resource Manager lets you import device information from both local and remote network management databases, identified in Table 1 and Table 2, respectively.
Resource Manager can be installed on the same machine as HP OpenView, CiscoWorks 3.x, and CiscoWorks for Switched Internetworks (CWSI) without any compatibility problems. If you plan to install all products on the same machine, check the compatibility notes of each product.
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 Network Node Manager | 5.0, 5.01 |
CiscoWorks for Switched Internetworks (CWSI) | 1.3, 2.1 |
Castlerock SNMPc | 4.1n, 4.2.04 |
| Software | Version |
|---|---|
HP OpenView | 4.11, 5.0, 5.01 |
CiscoWorks | 3.2, 4.0 |
Resource Manager is supported on the browsers shown in Table 3.
| Browser | Version1 | Operating System |
|---|---|---|
Netscape Navigator2 | 3.03 | Solaris 2.6, Solaris 2.5.1 |
3.04 | Windows NT 4.0, 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, Windows 95 |
4.0 | Windows NT 4.0, Windows 95 |
Resource Manager supports the devices listed in Table 4. See the "Cisco IOS Versions Supported" section for information on which Cisco IOS versions are supported. See the "Devices Supported by Software Management" section for the devices Software Management 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 in the inventory reports.
The documentation for Resource Manager for Windows NT 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 Windows NT operating systems. It consists of the following sections:
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 Windows NT for more information about server requirements.
The IIS server must be dedicated to Resource Manager. Do not use IIS to service other applications or internet clients requesting web pages other than those generated by Resource Manager.
The following caveats describe installation issues.
Cisco recommends you do not install Cisco Resource Manager on a Windows NT system that is configured to be a Primary Domain Controller (PDC).
If you must install Resource Manager on a PDC, the CRM login mechanism does not work as documented. That is, the default username (admin) and password (admin) will not work. You will need to specify the domain name with the username when logging in. For example, to log into Resource Manager on a PDC for the NT domain DomainABC, you must enter:
Username: DomainABC\admin Password: admin
CRM will not operate correctly if it is installed on a Windows NT system configured as a Backup Domain Controller (BDC). CRM will appear to install correctly, but you will not be able to log into Resource Manager, thereby preventing access to all privileged operations such as importing devices, creating users, and so on.
To avoid this problem, install Resource Manager on a Windows NT workstation or server that is not configured to act as a BDC. [CSCdk09898]
If you received Resource Manager as part of a bundled package with CiscoWorks for Switched Internetworks (CWSI), refer to Installing CWSI with CRM for installation instructions.
If you install Resource Manager 1.1 and CWSI 2.1 as a bundled package, be aware that some components and processes are shared between the two applications. For more information, refer to Installing CWSI with CRM.
If you stop the Resource Manager installation procedure before it completes, not all required components are installed and Resource Manager will not operate successfully. To recover from an aborted installation, start the Resource Manager installation procedure from the beginning. [CSCdj64037]
If the Resource Manager database on your system is corrupted, the following error occurs in the Microsoft Event Viewer for the Source DbServer during Resource Manager installation:
***Error*** Assertion failed: 31110|File is shorter than expected.
The following message also appears in syslog.log:
Dec 26 13:51:21 localhost dmgt[284]: 2095(W): Internal error: The Daemon Manager cannot execute application DbServer
If this occurs, you must restore the Resource Manager database from your backed-up copy of your database. [CSCdj63566]
The Uninstall procedure displays a dialog box saying, "Installation will change the following setting of IIS ...", but then it restores the IIS settings that were in effect before Resource Manager was installed.
If you install Resource Manager 1.1 and CWSI 2.1 on the same machine as part of the CRM/CWSI bundled package, you cannot uninstall all of Resource Manager without first uninstalling CWSI. Refer to Installing CWSI with CRM for more information.
Software Management stores Cisco IOS images that are not removed by the Resource Manager uninstallation procedure. If you want to permanently remove Resource Manager, you need to remove these files manually.
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.
You might encounter display problems when running Java applets if you use a browser on a multiprocessor PC. To correct the display problem, refresh or reload the browser page, or force a window refresh. [CSCdj66427]
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, 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 Resource Manager operation 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 in 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. To obtain help for the desired task, click Help in the left Resource Manager frame. When the help window appears, click Contents and then either Basic Administration for help on views or Inventory Tasks for help on 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. To obtain help for the desired task, click Help in the left Resource Manager frame. When the help window appears, click Contents and then either Basic Administration for help on views or Inventory Tasks for help on reports. [CSCdj62204]
When distributing images (Tasks > Software Management > Distribute Images) for selected IOS devices, you might see the following error:
User Error: Could not find this file Recommended action: Check whether file .../swd/881174285/probe.str exists
This message appears when Internet Explorer uses cached information instead of reexecuting the script. To correct this behavior, restart the browser. [CSCdj63710]
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 the 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, Telnet access information (Telnet password, enable password, TACACS, enable secret, local username password, and CCO passwords) as well as 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 (CRM) 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]
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 sections for instructions on what you need to do before importing devices:
The import process writes files containing community strings in C:\Program Files\CSCOpx\Temp under two conditions:
All Resource Manager scripts are executed by the web server in the bin account. This account is initially created by the Microsoft Internet Information Server (IIS) installation as IUSR_pc-name (where pc-name is the host name) and renamed to bin by the Resource Manager installation procedure.
This account is created for anonymous Web login and is restrictive so it can provide security. It is also created as local to the system on which IIS is installed. As a result, Resource Manager does not usually see shared network directories on Windows NT servers.
If you determine that it is appropriate for Resource Manager to access a network drive, you can add the necessary permissions for accessing the network drive to the bin account. All persistent drive mappings will be available to Resource Manager.
As an alternative, you can temporarily set Anonymous Login User in WWW Service Properties to a user who can access the desired network drive and who has set the necessary persistent drive mappings.
Cisco recommends that you not make network drives available for Resource Manager because this can potentially become a security flaw. [CSCdj53223]
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 that 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 could receive server errors when executing other Resource Manager functions. To avoid these errors, keep the temporary directory clear of unneeded files and verify that you have the recommended minimum disk space available. [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 (C:\Program Files\CSCOpx\temp). Cisco recommends you remove these files from this directory when the upgrade is complete. [CSCdj62050]
If you do not select Error halts processing... 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 window to confirm the success or failure of the upgrade on each device in the job. [CSCdj57460]
When upgrading the software images, single Flash bank devices require Telnet access. Therefore, when adding the device to 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 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 does contain messages, the DNS name of the device is different from the name defined in the Resource Manager inventory. To resolve this issue, change the DNS name to be the same as the name in the Resource Manager inventory. [CSCdj58347]
Syslog reports do not have IOS explanations for some messages. Refer to the latest IOS reference manual for additional information on reported messages. [CSCdj61218]
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 pages on which they are found in this document.
CSCdj16580 18
CSCdj19695 14
CSCdj24567 15
CSCdj25733 16
CSCdj44161 17
CSCdj50947 12
CSCdj53223 16
CSCdj55007 12
CSCdj56328 13
CSCdj56560 11
CSCdj56775 12
CSCdj57449 12
CSCdj57460 17
CSCdj58691 12
CSCdj60013 13
CSCdj61218 18
CSCdj62050 17
CSCdj62204 13
CSCdj62469 18
CSCdj63566 11
CSCdj63710 13
CSCdj64037 10
CSCdj66427 11
CSCdj79501 16
CSCdj83169 2
CSCdj83419 15
CSCdk09898 10
CSCdk13298 14
CSCdk13579 14
CSCdk14992 15
CSCdk14993 15
Posted: Thu Sep 30 16:17:34 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.