|
|
This document discusses Cisco Resource Manager. Use this document with the Cisco Resource Manager Installation Guide for Solaris.
This release notes document includes the following sections:
The hardware platforms, memory, and disk space requirements for the Resource Manager server are
The software required for Resource Manager is
ftp://sunsolve.sun.com/pub/patches/patches.html#2.4-rec
xx is recommended because it fixes a known Solaris problem with syslogd. The 2.5.1 patch is recommended, but not required, because Resource Manager runs adequately in environments with light to medium syslogd traffic. The Solaris patch 103738-03 (the most current version of this patch) is available only to users with Sun service contracts. 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 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 |
Resource Manager is supported on the browsers shown in Table 2.
| Browser | Version1 |
|---|---|
| Netscape Navigator | 3.01 with NT 4.0, Windows 95, and Solaris 2.4 (with Sun recommended 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 |
Resource Manager supports the devices listed in Table 3. See the "Cisco IOS Releases Supported" section for information on which Cisco IOS Releases are supported. See the "Software Management Caveats" section for the devices supported by Software Management.
| Routers and Access Servers | Switches | Hubs |
|---|---|---|
| Cisco CS500 | Viper Switch CPW16, ESP2015 | |
| Cisco and Cisco Pro 751, 752, 753, 761, 762, 765, 766, 771, 772, 775, 776 | Catalyst 1200, 1220, 1600, 1700, 1800, 1900, 2200, 2600, 2800, 2820, 2900, 3000, 3001, 3011, 3011 Router, 3100, 3200, 3500, 5000, 5002, 5301, 5500 | FastHub 300 and FastHub 100+Series FastHub 3116T, 316C, 3116, 216T, 116T, 116C, 1116 |
| Cisco and CiscoPro 1000, 1003, 1004, 1005, 1020 | EtherSwitch 10/100 (CPW1100), 1200 (CPW1200), 1220 (CPW1220), 1220 (CPW1220L), 1400 (CPW1400), 1402 (CPW1402), 1408 (CPW1408), 1420 (CPW1420), 1422 (CPW1422), 1428 (CPW1428), 1442 (CPW1442), 1448 (CPW1448), 1448 Pro 16, 1600 (CPW1600), 1601 (CPW 1601), 1900 (CPW1900), 2200 (CPW2200) | MicroHub 1503, 1502 |
| Cisco and CiscoPro 1601, 1602, 1603, 1604 | Workgroup concentrator 1000, 1100, 1400 | |
| Cisco 2501, 2502, 2503, 2504, 2505, 2507, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 2516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501LF, 2502LF | LS1010, LS2020 | |
| CiscoPro 2501, 2502, 2503, 2504, 2505, 2507, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 2516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525 | ||
| Cisco 2102, 2202 | ||
| Cisco 3000, 3620, 3640, 3101, 3102, 3103, 3104, 3202, 3204 | ||
| CiscoPro 3620, 3640 | ||
| Cisco and CiscoPro 4000, 4000-M, 4500, 4500-M, 4700, and 4700-M | ||
| Cisco AS5200, AS5209RJ, AS5211RJ, and AS5300 Access Servers | ||
| Cisco 7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513 | ||
| Router IGS, AGS+, AccessProRC, AccessPro EC, Router Gateway Server |
Full support is provided for devices running Cisco IOS Release 10.3 to 11.2 only. Unless your devices are running at least Cisco IOS Release 10.3, all MIB values might not be supported.
Partial support is provided for devices running Cisco IOS Release 9.1, 9.21, and 10.21. For example, some information is not displayed in the Detailed Device Report for devices running Cisco IOS Release 9.1 and 9.21, but the information is complete for devices running Cisco IOS Release 10.21, as shown in Table 4.
| Cisco IOS Release | Information Not Displayed in Detailed Device Report |
|---|---|
| 9.1 | Chassis Information
Chassis Cards Flash Information |
| 9.21 | Chassis Cards
Flash Information |
| 10.21 | All information is displayed |
Table 5 lists routers that will have missing summary information in the Detailed Device Report if they are not running at least Cisco IOS Release 10.3.
| SysObjecID number | Router Name |
|---|---|
| 1.3.6.1.4.1.9.1 | Router Gateway Server |
| 1.3.6.1.4.1.9.1.1 | Router Gateway Server |
| 1.3.6.1.4.1.9.1.11 | Router AGS+ |
| 1.3.6.1.4.1.9.1.5 | Router IGS |
| 1.3.6.1.4.1.9.1.3 | Router Trouter |
To avoid this issue, make sure devices are running at least Cisco IOS Release 10.3. [CSCdj19992]
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).
There is a CCO web page for Resource Manager that 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 describes the notes and general caveats that apply to Resource Manager on Solaris operating systems and includes the following sections:
A Solaris SPARC20 or equivalent is the lowest workstation in the Sun product line on which we recommend you install Resource Manager. Performance problems will occur if you use, for example, a SPARC2.
The Japanese TAC supports the local Solaris version of Cisco Resource Manager 1.0. SmartNet or warranty support calls are handled during Japan standard time.
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 Installation Guide for Solaris for more information about server requirements.
Using the Apache http server to support other software not installed by Cisco Resource Manager is not supported.
The following caveats describe installation issues for customers that have the beta version of Cisco Resource Manager installed on their machines.
If you have the beta version of Resource Manager installed and you have software images in the library, you need to save the software images before installing version 1.0. Follow these steps to ensure you will be able to use your existing software images in version 1.0 of Resource Manager.
Step 1 Make a directory to store your software images by entering the following command:
# mkdir /opt/my_images
where my_images is the name of the directory in which you want to save your software images.
Step 2 To copy your images from the Resource Manager datastore to your new directory, enter the following command:
# mv /opt/CSCOpx/objects/data/sw_images /opt/my_images
Step 3 To remove the current version of Resource Manager, enter the following command as root:
# /opt/CSCOpx/bin/uninstall.sh
Step 4 Remove the following directories if they were not removed by the uninstall script:
Step 5 Reboot the Resource Manager server.
Step 6 Install Resource Manager as explained in the Cisco Resource Manager Installation Guide for Solaris.
After you have installed version 1.0 of Resource Manager, you need to log in with the appropriate administrator login and password and follow these steps to check in your software images:
Step 7 With administrator privileges, select Tasks > Software Management > Add Image to Library. The Select Image Source screen appears.
Step 8 Select File System in the Select Image Source screen.
Step 9 Click Next. The Select Image Type screen appears.
Step 10 To check in IOS system images, enter the following directory in the Source Directory field of the Select Image Type screen:
my_images/sw_images/ios/system
Step 11 If you have boot or Catalyst images in the /opt/my_images/sw_images directory, enter the corresponding path in the Source Directory field of the Select Image Type screen.
If you have the beta release of the Resource Manager installed on your machine, make sure you do the following before installing version 1.0:
Step 1 Stop all Resource Manager processes by entering the following command as root:
# /etc/init.d/dmgtd stop
Step 2 Remove Resource Manager as explained in steps 3 and 4 in the previous section, "Installing Version 1.0 of Resource Manager."
After you have removed the beta version of Resource Manager, you can install version 1.0.
The following caveats describe installation issues.
If you install Resource Manager somewhere other than the default directory (/opt/CSCOpx), the uninstall script, uninstall.sh, does not remove the directory that Resource Manager is installed in. To resolve this issue, after running uninstall.sh, enter the following commands:
# cd /opt
# rm -f ./CSCOpx
# rm -rf directory
where directory is the full path to the directory in which Resource Manager was installed.
If your host name is set to a fully-qualified domain name, you may see the following errors after starting the setup.sh script:
ERROR: unix host name does not match TCP/IP host name. ERROR: use uname -S to set unix host name to match TCP/IP name. Exiting.To check your host name, enter uname -n. If this command returns a fully-qualified domain name such as myhost.mycompany.com, you need to perform a workaround. The workaround is to enter the command:
uname -S myhost
and then once again run setup.sh:
setup.sh
Once setup has completed, return the host's name to its previous value by entering:
uname -S myhost.mycompany.com
Resource Manager uses the default port 80. The Resource Manager installation tool checks /etc/services to verify if port 80 is in use. If it finds a definition for port 80 in /etc/services, it assumes that port 80 is not available and assigns the web server to port 1741.
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. Most often, 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.
The following sections describes caveats with particular web browsers.
Some of the Resource Manager screens require scrolling. When you scroll quickly, elements drop off the screen. This causes the Next and Back buttons to disappear, the pull-down lists to disappear, and other abnormalities. This is a known Netscape 3.01 bug. To resolve this issue, from Netscape Navigator, select View > Refresh. [CSCdj17627]
Long view names, for example, those over 20 characters, are truncated in some Resource Manager dialog boxes (namely, list boxes and selection lists). For list boxes, the horizontal scroll bar is missing in the NT environment on Netscape Navigator and Internet Explorer. (They display correctly in Netscape Navigator in a UNIX environment.) To avoid truncated names in dialog boxes, use view names of less than 20 characters. [CSCdj08223]
In addition, when you use Microsoft Internet Explorer, the links on the alphabetical strip at the top of the online help index screen might not take you to the letter you click on. This problem does not occur in Netscape Navigator. To resolve this issue, scroll to the appropriate letter instead of using the alphabetical links at the top of the screen. [CSCdj27371]
The following caveats describe issues with administration functions.
If you start Resource Manager by logging in as root and entering the following command
#/etc/init.d/dmgtd start
make sure you do not suspend the root session. 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 Monitor and select a device to view its availability, the Availability Monitor screen appears. If you click the Interface Status icon for a device, the Interface Details screen 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 maybe due to the expiration of the cookies, which are used to pass cgi-bin parameters to the reports. To resolve this issue, retry the operation. [CSCdj19695]
When you add or import a device, or change device information, avoid using the characters < or > in the User Fields or Serial Number fields. When some browsers encounter these characters, the information might not be interpreted correctly. [CSCdj24567]
When importing devices, do not specify the device IP address and a domain name.
If you encounter problems when importing devices, make sure your CiscoWorks system is configured correctly. Consult the following Resource Manager online help sections for instructions on what you need to do before importing devices:
If you encounter problems related to how CiscoWorks is configured, follow these steps:
Step 1 Change the contents of /etc/group to correct the problem.
Step 2 Stop and restart Resource Manager processes by entering the following commands:
# /etc/init.d/dmgtd stop
# /etc/init.d/dmgtd start
CiscoWorks can import interface addresses from HP OpenView and treat them as separate devices when the Sync with Sybase option is used. Resource Manager treats any CiscoWorks devices as separate devices; therefore, a database could contain duplicate entries for the same physical device.
To avoid this issue,
There is an alternative method of importing devices using a Comma Separated Values (CSV) formatted device integration file that you create. There are two parts to this method:
The CSV file format does not allow you to include password information, which might affect future upgrades of the product, but will not compromise current functionality.
After you have created the CSV device integration file, use the crmimport.pl script to import the device data from your CSV file. Refer to the crmimport.pl manual page for details. Manual pages are located in /opt/CSCOpx/man/man1m. [CSCdj27346]
When you select Admin > Inventory > Add Devices, then fill in the Add a Single Device screen, the Add Passwords screen appears. Currently, the Enable Password field in the Add Passwords screen is not used by Resource Manager. Do not enter anything in the Enable Password field. [CSCdj29697]
You cannot delete devices using Admin > Inventory > Delete Devices if you have the following conditions:
To resolve this issue, add dummy import entries for the devices using Admin > Inventory > Add Devices using invalid community strings (for example, dummy). Then use Admin > Inventory > Delete Devices to remove the Managed devices, and then remove the dummy imported devices which are in the suspended state. [CSCdj28759]
The DIServer and IcServer might appear to be running but not making any progress.
If the Add/Import Status Summary screen (found in Admin > Inventory > Import Status) displays the message "DIServer processing device_name" at the bottom of the status table for more than 15 minutes with the same device_name even after you repeatedly click Update, the DIServer might be hung.
If the information message on the Process Status screen (found in Admin > System Admin > Process Status) in the IcServer entry displays the message "IcServer processing device_name" for more than 15 minutes with the same device_name even after you repeatedly click Update, the IcServer might be hung.
To resolve this issue, restart the DIServer or the IcServer by following these steps:
Step 1 Select Admin > System Admin > Stop Process. The Stop Process screen appears.
Step 2 Click Process in the Stop column, then select the appropriate process (DIServer or IcServer) under Process Name.
Step 3 Click Finish.
Step 4 Select Admin > System Admin > Start Process. The Start Process screen appears.
Step 5 Select the appropriate process (DIServer or IcServer) under Process Name.
Step 6 Click Finish.
The process continues processing. [CSCdj21846]
If you select System Admin > Move Data to move the database back to its original location after first moving it to a new location, the operation fails. This occurs because during the first move operation, a link is created in the original location that points to the new location. If you attempt to move the database back to the original location, the link causes the tool to assume that a database file exists in the original location. To resolve this issue, move the database to a new location instead of moving it back to its original location. [CSCdj27546]
The Logout button lets you close the main browser window, but it does not close any open report windows or other browser windows as part of the logout process. The open browser windows present a security risk because a new browser window launched from these open browser windows has the same login permissions as the browser window closed by the Logout button. To avoid a possible security risk, close all browser windows launched from the main browser before clicking Logout. [CSCdj14847]
Software Management provides the capability of distributing software to most Cisco IOS devices and the Catalyst line of switches. The distribution is verified and scheduled so that multiple devices can be updated quickly and easily.
Software Management supports Cisco IOS system software upgrades for the following devices:
The following caveats describe issues with Software Management.
LS1010 devices do not support any MIB to determine its current configuration register value. The configuration register boot field value controls how a device is rebooted:
For Core and Access IOS devices, CHASSIS MIB tells the current configuration register value. You can set the bootfield to 2 (if it is not already 2), by using this command:
config-registernew-value
Because LS1010 does not have a MIB to determine its current configuration register value, this check is not done on LS1010.
Before you try Software Management on any LS1010 device, make sure the configuration register boot field is set to 2. To change the configuration register value, enter config mode and specify the following command:
config-register new-value
If your configuration register value is set so that it doesn't use the boot helper image in the ROM/bootflash, then the tftp fall-back option might not work. If the fourth bit of the configuration register is set to 1, the ROM monitor code on the device does not use the boot helper image and tries to boot only from the flash image. Therefore, the forth bit of the configuration register should be set to 0, if it is 1 for your device. For example, if your configuration register value is 0x2112, then it should be modified to 0x2102. To change the configuration register, enter the enable mode on the device and change it using the config-register command described above. [CSCdj27135]
Software Management does not support Cisco IOS software upgrades on
SFB (Single Flash Bank) 2500 devices that are running the current image from flash. However, if you netboot these devices from a tftp server, Software Management will perform software upgrades on these devices if the device's RAM size is at least twice the size of the Cisco IOS image.
To upgrade system software on SFB 2500 devices, follow these steps:
Step 1 Copy the currently running image on your SFB 2500 device to a tftp server.
Step 2 Modify the configuration on the SFB 2500 device so that the device netboots from the tftp server at the next reboot. (Refer to your router/access server configuration guide for more details on how to netboot a device.)
Step 3 Save the configuration changes to a startup configuration file and reboot the SFB 2500 device.
Step 4 Update the inventory for the SFB 2500 device in Resource Manager by selecting Admin > Inventory > Update Inventory.
Step 5 Schedule a job to upgrade the SFB 2500 device.
When you select Admin > Software Management > Update Configuration, you cannot enter http:// in the Proxy URL field. Instead, enter just the server name. For example,
server_name.com:80
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 operation takes less than 20 minutes. [CSCdj25733]
You cannot add images to the Software Management library using CCO if you have a proxy setup for FTP in your network. To avoid this issue, use an FTP that is compatible with your firewall and download the images from CCO. [CSCdj28163]
The result file for the Catalyst software image upgrade jobs contain the wrong text. Instead of "Up time in seconds since reboot," the file should say "Up time in milli-seconds since reboot." [CSCdj28986]
If neither at.allow nor at.deny files exists on the Resource Manager server, the user bin is not allowed to use at (the Solaris scheduler) to schedule Software Management image transfers to devices. To resolve this issue, on the Resource Manager server, create a /usr/lib/cron/at.allow file that contains users root and bin before you schedule image transfers. [CSCdj27151]
If you cancel the software upgrade job while it is still running, Software Management does not cancel the software upgrades that have already been completed. The job stops only after the software upgrade on the currently working device is complete. During this time, the Browse Job Status screen indicates that the job is running. In addition, if you cancel a job while it is running, and then you reactivate the job, the job restarts the software upgrade from the first device in the job.
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]
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 or the name defined in /etc/hosts is different than the name in the Resource Manager inventory. To resolve this issue, change the DNS or the name in/etc/hosts so that the name of the device is the same as in the Resource Manager inventory. [CSCdj27338]
Syslog analysis discards messages in /var/log/syslog.info that have a source IP address of six octets. To resolve this issue, add an entry to DNS or /etc/hosts for the IP address of the device so that the Solaris syslogd can resolve it. The device name must be the same name as the one in the Resource Manager inventory. [CSCdj26320]
Resource Manager does not process Catalyst syslog messages. Catalyst messages have a different format than Cisco IOS devices. Because Catalyst messages do not contain a mnemonic field, syslog analysis discards the messages.
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.
This section lists the bug ID numbers and the page on which they are found in this document.
CSCdj08223 11
CSCdj14847 17
CSCdj16580 21
CSCdj17627 11
CSCdj19695 12
CSCdj19992 6
CSCdj21846 16
CSCdj22689 14
CSCdj24567 12
CSCdj25733 20
CSCdj26320 22
CSCdj27135 19
CSCdj27151 20
CSCdj27338 21
CSCdj27346 14
CSCdj27371 11
CSCdj27546 16
CSCdj28163 20
CSCdj28415 20
CSCdj28759 15
CSCdj28986 20
CSCdj32651 10
|
|