|
|
These notes supplement the User Guide for Cisco IP Manager version 2.0. (The most recently published edition of the User Guide is the 2.0 version. Significant changes have been made to the product since version 1.0.)
1. The Cisco IP Manager system has been tested with the following devices and Cisco Internetwork Operating System (Cisco IOS) versions. The specific Cisco IOS version that was tested is listed for each device.
| Device | Cisco IOS Release Version | |
|---|---|---|
| 11.x | 12.0.x | |
7513 | 11.2 |
|
7507 | 11.1(18) | 12.0(4a), 12.0(5) |
7200 | 11.3(8) | 12.0(7) |
5300 | 11.3(4)T | 12.0(6) |
5200 | 11.2(18), 11.2(14) | 12.0(6) |
4500 | 11.2(18) | 12.0(6) |
3810 |
| 12.0(2a)T1 |
2524 | 11.2(18) |
|
2525 |
| 12.0(5) |
2514 | 11.2(17)P |
|
2505 | 11.2(18) |
|
1604 | 11.3(11a) | 12.0(4) |
802 | 12.0(1)XB |
|
1720 |
| 12.0(4)T |
2611 | 11.3.9T | 12.0(4)T |
3620 | 11.2(18)P | 12.0(5) |
3640 | 11.3(8) | 12.0(3)T3 |
5800 (router shelf) | 11.3(3a)AA |
|
5800 (dial shelf) | 11.3(3a)AA | 12.0.5T1 |
6400(NSP) |
| 12.0(4)DB |
UBR72461 |
| 12 |
GSR 12000 | 11.2 | 12.0(6)S1 |
LS 1010 |
| 12.0(4) |
MGX 88502 |
| 12.0(2.5)T |
2. The Cisco IP Manager system has been tested with the following storage devices and Cisco Internetwork Operating System (Cisco IOS) versions:
.
| Device | Cisco IOS Version | Connect Method | Storage Device |
|---|---|---|---|
GSR12000 | 12.0(6)S1 | VTY | Flash |
UBR7246 | 12.0(5)T1 | VTY | Flash, bootflash |
1720 | 12.0(4)T | VTY, Console | Flash |
3620 | 11.2(18)P | VTY, Console | Flash |
3640 | 12.0(3)T3 | VTY, Console | Flash |
3810 | 12.0(2a)T1 | VTY, Console | Flash |
4500 | 12.0(6) | VTY | Flash |
5300 | 12.0(6) | VTY | Flash |
7200 | 12.0(7) | VTY | Flash |
7507 | 12.0(5) | VTY | Flash |
LS1010 | 12.0(4) | VTY, Console | Bootflash |
3. To check Java's memory usage, choose the About command on the CIPM Help menu. The total memory figure displayed refers to the amount of memory currently allocated to CIPM by the Java Virtual Machine (JVM). The free memory figure refers to the amount of allocated total memory that is not currently in use. If the amount of available memory (free memory plus the difference between total memory and the maximum allowed) is small, the JVM may not be able to supply CIPM with enough memory and you may receive a Java out-of-memory exception. Exit and restart the GUI application to clear the memory-management error condition. CIPM puts a 96-megabyte cap on the amount of memory the JVM is allowed to claim. This can be changed with the Java Runtime Environment flag -Xmx by editing the launchgui.sh script. Search for java -Xmx and specify memory in megabytes, kilobytes, or bytes, as:
java -Xmx70m java -Xmx70k java -Xmx70
However, if you allocate more than the default maximum value, you will increase the risk of memory contention, especially when any of the CIPM servers are running on the same host as the GUI application.
4. The maximum number of slots in a container element is 32, not 100 as documented in the Managing Network Elements chapter of the Cisco IP Manager (Lite) User's Guide (page 5-10).
The following items list known problems in Cisco IP Manager 2.0. The problems are listed by their identifiers in the Distributed Defect Tracking System (DDTs) used by Cisco to track product defects and enhancement requests.
Problem: If you run Cisco IP Manager in a distributed fashion, that is, with the NEMServer and TGServer installed on a separate host other than where the CENTER-LITE package is installed, the telnet process spawned by the TGServer may hang if you specify a device host name instead of an IP address.
Workaround: We recommend specifying a device IP address if the NEMServer and TGServer installed in a distributed fashion. Other possibilities include modifying the ipmgr.launch script and manually launching the remote TGServer.
Problem: After some modal dialogs are dismissed, the first right click to bring up a context menu has no effect.
Workaround: Right click a second time to bring up the context menu.
Problem: NEM can hang when importing elements and running the GUI at the same time.
Workaround: The first time you import elements, do so before running the GUI. You can use the command-line utility importElement to add new elements that are defined in a text file. How to do this is described in the Cisco IP Manager User Guide.
Problem: Orbix can core-dump after a long running session and Orbix runs out of file descriptors.
Workaround: Restart all servers on that machine.
Problem: NS core-dumps when invoked with the -V flag (show version).
Workaround: Don't invoke the server with the -V flag. This flag is not needed for normal operation, so it is not a problem.
Problem: You may get a Java out-of-memory exception when Cisco IP Manager is used heavily.
Workaround: Restart the GUI or increase the JVM heap size (using, for example, java -Xmx128m). Refer to "Important Notes" for information on how to increase the JVM heap size.
Problem: If you run multiple instances of the Template Config Builder subsystem on the same template with the same user name, you will implicitly unlock the template when you close any of these Template Config Builder subsystems.
Workaround: Go to the Template Manager window and explicitly lock the template from its pop-up menu after you close a Template Config Builder window.
Problem: Sometimes the Template Config Builder subsystem may cease to function after you type certain special characters.
Workaround: Save the template body and data using the pull-down menu, and then select Revert from the same menu. The editor will be reset and function normally again.
Problem: The NEMServer core-dumps when two GUIs are trying to do group deletion of elements.
Workaround: Do not have more than one GUI at a time do group deletion of elements.
Problem: Cannot remove SNMP trap information from the GUI. When deregistering SNMP trap information, the values do not get deleted from the database.
Workaround: There is no workaround since SNMP trap values do not need to be removed for normal operation.
Problem: A virtual device download generates the Unknown Error message. This is a wrong error code returned by the NEMServer when dealing with virtual devices.
Workaround: There is no workaround, since virtual devices are used only for training and practice.
Problem: Password fields show spaces rather than asterisks after you enter more than 16 characters.
Workaround: None. This is a cosmetic problem and does not affect functionality.
Problem: In the SubTemplate Data dialog brought up from the Config Builder, the selected SubTemplate sometimes contains template data that no longer exist.
Workaround: In the SubTemplate Data dialog, remove these template data by using the << button and then click the Ok button.
Problem: When you try to do an upload operation by means of SNMP and the router does not support that operation on that particular IOS version, the GUI displays an incorrect error message ("SGS operation failed: check SNMP community strings and TFTP server parameters"). The log viewer does, however, display the correct error message ("IOS version not supported").
Workaround: Check log viewer messages when this error message occurs.
Problem: After a Cisco IP Manager user is deleted by a client other than the User Manager, the User Manager still shows deleted users.
Workaround: Restart the GUI to see the updated list. Closing the User Manager does not refresh the user list.
Problem: If you use the configure terminal mode to download to a router's running configuration, banners with the following character pattern may cause problems to the current download script:
% end
config followed by 0 or more characters and then the characters )## >
Workaround: Avoid these character patterns in banner content, or use the TFTP download method as an alternative.
Problem: Whenever an illegal value is entered for operation timeout and prompt timeout in the Telnet gateway property page, or no value is entered, the GUI provides default values of 60 and 0, respectively. These values are inconsistent with TGServer's defaults of 1200 and 10, respectively.
Workaround: Check the assigned value as shown in these fields after clicking the Apply button, and make sure the values are within the acceptable range before clicking OK. If they are not, type in acceptable values.
Problem: Deleting a network element does not generate a log message.
Workaround: None.
Problem: Blank lines are added intermittently in the User List of the User Manager.
Workaround: Add or remove a user to refresh the user list or restart the GUI to see the updated list.
Problem: Within the Log Viewer, when the log is viewed with the local time option and an invalid date is entered in the Search or More Search dialog, the Cisco IP Manager GUI does not behave properly. There are no error messages and the search operation did not perform.
Workaround: Enter the date in valid format (YYYY/MM/DD) in the Search and More Search dialogs.
Problem: The GUI Diff operation in the Archive Manager window can throw Java exceptions when you try to compare two files containing the same content, when using the following steps: Click on the Complete Diff button, click on the Difference Only button, and then click on Complete Diff again.
Workaround: Normally, the exception has no operation impact. If you have problem bringing up the GUI Diff window after the Java exception, close the Archive Manager window and open it up again.
Problem: If a composite element is locked by a user, that user cannot verify the connection.
Workaround: Do not lock composite elements.
Problem: The GUI displays a dialog "Continue paste operation?" even though there are no more elements to paste.
Workaround: Dismiss the dialog.
Problem: When all Cisco IP Manager servers and Orbix daemon are killed, connection is refused and exceptions are displayed when the GUI continues running without servers.
Workaround: Either exit from the GUI, or kill all GUI Java processes, or both.
Problem: Domain Properties dialogs remain opened after closing the Element Manager. At this point, applying properties results in a Java exception.
Workaround: Close the Domain Properties dialog before closing the Element Manager. Reopen the Element Manager and then reopen the Domain Properties dialog to apply properties.
Problem: Deleting a child element does not check whether parent elements might need that child.
Workaround: When deleting child elements, make sure no one else needs the child.
Problem: Sometimes performing an immediate reload (either right away, or specifying 0 hours 0 minutes as the "Reload in" length of time) on a child element of an MGX composite element can result in a generic TGServer operation failure message, even though the reload on the child element is successful.
Workaround: Don't use the immediate reload feature on an MGX composite element. Instead, schedule the reload in a small amount of time (1 minute, for example) to give the expect script enough time to exit normally before the reload, thus avoiding the race condition that causes the error message.
Problem: Sometimes performing an immediate reload (either right away, or specifying 0 hours 0 minutes as the "Reload in" length of time) through VTY connection on an element would results in an operation timeout failure message, even though the reload on the element is successful.
Workaround: Don't use the immediate reload feature on a VTY-connected element. Instead, schedule the reload in a small amount of time (1 minute, for example) to give the expect script enough time to exit normally before the reload, thus avoiding the race condition that causes the error message.
Problem: Operations on a deleted domain with the Config Builder show no error messages in the Message Console. Instead, error messages are shown on the Xterm where the GUI was started (using ipmgr.gui). Moreover, CTMServer deletes all templates and template data under the deleted domain and removes these templates from the database. Make sure you check the domain before deleting it.
Workaround: Close the Config Builder, because the domain and its templates are no longer valid, and make sure there are no templates currently in use before deleting the domain.
Problem: A communication server's console port may be left in a busy state when you perform a single or compound operation (for example, Download to Running plus Update Startup plus Reload Element).
Workaround: For a single operation, you should manually clear the console port and retry the operation. For a compound operation, the GUI should inform you the progress of each stage of the compound operation that has finished successfully. You should then manually clear the console port and continue with the rest of the operations. Also, we recommend using the "no logging console" command when using the console connect method in Cisco IP Manager. This may alleviate or entirely eliminate the problem.
Problem: When trying to create add a new element to a domain from the GUI, if disk space is low, the NEMServer can generate a core dump and display the following message:
org.OMG.CORBA.COMM_FAILURE:unlucky.cisco.com/1604
Workaround: A minimum of 15 percent of any volume used by a CIPM process (including the Oracle database) should be kept free.
Problem: Storage-device-related commands such as dir filename and delete filename do not work on the 3620 device with Cisco IOS version 11.2(18)P.
Workaround: None.
Problem: A CIPM server becomes unresponsive, even though the server process is running, and the following log message is stored in the database: "Database exception - cursor error : Number ORA-03113: end-of-file on communication channel,offset: 0."
Workaround: Restart the CIPM server (use the ipmgr.killit and ipmgr.launch utilities). The error message indicates that a break has occured in the network connection between the CIPM server and the Oracle database, and the Oracle process has timed out. This condition can occur with any CIPM server that connects directly to the database.
Problem: Within template data, CTM generates error code 6011 ("Data encoding is not correct in data file") if there any element names are duplicated in the Device column of the Config Builder. This is due to CTM not comparing the full name (using the format of domain:element).
Workaround: Remove duplicated element name in Device column or put the duplicated name in another template.
The section "Information Groups" in the Cisco IP Manager (Lite) User's Guide contains incomplete information. The following appears:
Add the following:
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 and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Fri Feb 25 17:03:48 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.