Feedback
|
Table Of Contents
Database Access Error Messages
IPM Error Messages
This appendix provides a list of the IPM error messages and includes an explanation and recommended action for each. IPM error messages fall into three categories, which are described in the following sections:
•
Database Access Error Messages
Note
If you receive an error message while running IPM and following the recommended actions does not resolve your problem, please contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. When you contact Cisco's TAC, please make sure you have a copy of the message log file and noted the error message that appeared on the screen.
Configuration Error Messages
This section provides explanations and recommended actions for error messages that you might encounter when configuring or viewing the properties of collectors, targets, source routers, or operations.
Error MessageFailed to open Managed Object File %s or %sExplanation The Managed Object File list file in the /opt/CSCOipm/misc directory is not accessible. This error message only appears if you launch IPM without using the ipm script.
Recommended Action Set the CWBIPMROOT variable to the IPM installed directory and restart the servers.
Error MessageIPM Target Host Name is NULLExplanation When defining an SNA target, a host name must be provided.
Recommended Action In the Add Target window, enter a host name in the Host Name field.
Error MessageIPM Target SSCP Name is NULLExplanation When defining an SNA SSCP target, a PU name must be provided.
Recommended Action In the Add Target window, enter a PU name in the VTAM PU Name field.
Error MessageIPM Target LU Names (Host/Application) are NULLExplanation When defining an SNA SSCP target, an LU name must be provided.
Recommended Action In the Add Target window, enter an LU name in the VTAM PU Name field.
Error MessageGeneral Database Error.Explanation The requested source is in use or unavailable.
Recommended Action Try to perform the operation again. If repeating the operation fails to resolve the problem, exit the IPM client and shut down IPM using the following command:
# cd /opt/CSCOipm/bin# ./ipm stopThis command stops the IPM server, database, and process manager. Restart the IPM database, server, process manager, and client using the following command:
# cd /opt/CSCOipm/bin# ./ipmError MessageOperation already exists.Explanation An operation already exists that has the same operation name as the operation that you are attempting to define.
Recommended Action Use a different name for the operation that you are defining.
Error MessageTarget already exists.Explanation A target already exists that has the same target name as the target that you are attempting to define.
Recommended Action Use a different name for the target that you are defining.
Error MessageCollector name is not unique.Explanation A collector already exists that has the same collector name as the target that you are attempting to define.
Recommended Action Use a different name for the collector that you are defining.
Error MessageOperation name is empty.Explanation When defining an operation, an operation name must be provided.
Recommended Action In the Add Operation window, enter an operation name in the Name field.
Error MessageOperation is being used.Explanation The operation that you are trying to delete is currently in use. You cannot delete an operation while it is being used by a collector.
Recommended Action Before you can delete the operation, you must stop and delete any collectors that are using that operation. Then you can delete the operation.
Error MessageInvalid Target Address.Explanation The target address that you provided cannot be resolved.
Recommended Action Verify that the target address is resolvable by DNS or by the /etc/hosts file.
Error MessageError: SNMP error while getting sysUpTime from the router.Explanation IPM was unable to communicate with the source router to obtain the sysUpTime.
Recommended Action Check the availability of the source router and verify its read community string.
Error MessageError: Read community string is greater than 32 characters.Explanation The read community string must be less than 32 characters in length.
Recommended Action Use a read community string that is less than 32 characters long.
Error MessageError: IP name cannot be NULL.Explanation When defining a source router or target, a host name or IP address must be provided.
Recommended Action Enter an IP address or host name in the Source Router field of the Add Source Router window or the IP Address or Host Name field of the Add Target window.
Error MessageError: Source router is already configured.Explanation The source router that you are attempting to configure is already configured.
Recommended Action Check the router list before configuring the source routers.
Error MessageError: Connection to SNMP server lost.Explanation SNMP operations cannot be processed.
Recommended Action Try to perform the operation again. If repeating the operation fails to resolve the problem, exit the IPM client and then shut down IPM using the following command:
# cd /opt/CSCOipm/bin# ./ipm stopThis command stops the IPM server, database, and process manager. Restart the IPM database, server, process manager, and client using the following command:
# cd /opt/CSCOipm/bin# ./ipmError MessageError: Not a valid IOS version on the source router for IPM application.Explanation The source router is not running the supported version of the Cisco IOS software.
Recommended Action Upgrade the Cisco IOS software on the source router to release 11.2(15) or later.
Error MessageError: Collector instance is in use. Cannot perform requested operation.Explanation The collector instance is currently being displayed.
Recommended Action Close the display window and retry the operation.
Error MessageError: Cannot locate RTR feature on the source router.Explanation The Cisco IOS software on the source router does not contain the RTR feature.
Recommended Action Check in the Internetwork Performance Monitor Installation Guide for valid Cisco IOS software versions and a feature list.
Error MessageError: The write community string specified does not match with the one on the router.Explanation The SNMP write community string that you entered does not match the write community string for the router.
Recommended Action Verify the SNMP write community string for the router and enter it again.
Error MessageError: Invalid falling threshold specified. The Falling threshold cannot be greater than threshold.Explanation It is invalid to specify a Falling threshold that has a greater value than the threshold.
Recommended Action Modify the Falling threshold value so that it is greater than the threshold.
Error MessageError: Interval must be greater than 10 seconds.Explanation The sampling interval for the operation must be 10 seconds or greater.
Recommended Action From the Add Operation window or Update Operation window, change the sampling interval for the operation to a value of 10 seconds or greater.
Error MessageError: Interval must be less than 3600 seconds.Explanation The sampling interval for the operation must be less than 3600 seconds (1 hour).
Recommended Action From the Add Operation window or Update Operation window, change the sampling interval for the operation to a value of 3600 seconds or less.
Error MessageError: Invalid timeout specified. Timeout value must be less than sampling interval.Explanation When defining a threshold, the timeout value must be less than the sampling interval for the operation.
Recommended Action From the Add Operation window or Update Operation window, change the timeout to a value less than the sampling interval or change the sampling interval to a value greater than the timeout value.
Error MessageError: Invalid Count2 value specified. For X of Y Threshold type Count2 should not be smaller than Count1.Explanation When defining an X of Y threshold, the Count2 value must be greater than the Count1 value.
Recommended Action From the Add Operation window or Update Operation window, change Count2 to be a value greater than Count1, or change Count1 to be a value less than Count2.
Error MessageError: Invalid Operation Type specified. If Target type is other than ICMP_ECHO, Operation type cannot be a Path Echo.Explanation The PathEcho protocol can only be used for a target whose target type is IP.
Recommended Action From the Add Target window, change the target's target type to ICMP_ECHO. If the target is not using IP, you must use and operation that has Echo as its protocol type.
Error MessageError: No Running instance found with specified running ID.Explanation The IPM client and servers not synchronized.
Recommended Action Exit the IPM client and then shut down IPM using the following command:
# cd /opt/CSCOipm/bin# ./ipm stopThis command will stop the IPM server, database, and process manager. Restart the IPM database, server, process manager, and client using the following command:
# cd /opt/CSCOipm/bin# ./ipmError MessageError: Remove Target from List failed.Explanation IPM was unable to delete the target. An internal error occurred. The workstation must be out of available memory.
Recommended Action Exit the IPM client and then shut down IPM using the following command:
# cd /opt/CSCOipm/bin# ./ipm stopThis command will stop the IPM server, database, and process manager. Restart the IPM database, server, process manager, and client using the following command:
# cd /opt/CSCOipm/bin# ./ipmError MessageError: Unable to insert Operation item in list.Explanation IPM was unable to add the operation to the operation list. An internal error occurred. The workstation must be out of available memory.
Recommended Action Exit the IPM client and then shut down IPM using the following command:
# cd /opt/CSCOipm/bin# ./ipm stopThis command stops the IPM server, database, and process manager. Restart the IPM database, server, process manager, and client using the following command:
# cd /opt/CSCOipm/bin# ./ipmError MessageError: Remove operation from List failed.Explanation IPM was unable to delete the operation from the operation list. An internal error occurred. The workstation must be out of available memory.
Recommended Action Exit the IPM client and then shut down IPM using the following command:
# cd /opt/CSCOipm/bin# ./ipm stopThis command stops the IPM server, database, and process manager. Restart the IPM database, server, process manager, and client using the following command:
# cd /opt/CSCOipm/bin# ./ipmError MessageError: Error occurred while creating message unit.Explanation IPM was unable to create the message unit used for passing information between the configuration server and the SNMP server. An internal error occurred. The workstation is out of available memory.
Recommended Action Exit the IPM client and then shut down IPM using the following command:
# cd /opt/CSCOipm/bin# ./ipm stopThis command stops the IPM server, database, and process manager. Restart the IPM database, server, process manager, and client using the following command:
# cd /opt/CSCOipm/bin# ./ipmError MessageError: The filename cannot be NULL.Explanation When loading collectors, source routers, or targets from a seed file, a filename for the seed file must be provided.
Recommended Action From the Seed File window, enter the appropriate filename in the Seed File Name field.
Error MessageError: The filename is in use by another client.Explanation The filename for the seed file that you specified is currently in use by another instance of the IPM client.
Recommended Action Load the seed file at a later time to avoid a conflict with another IPM client.
Error MessageError: Invalid type field specified.Explanation When loading a seed file from the command line using the ipm seed command, this error occurs when the type specified for the seed file was invalid. The valid seed file types are 1 for source routers, 2 for targets, and 3 for collectors.
Recommended Action Reenter the ipm seed command and include the appropriate seed file type for the seed file that you are trying to load.
Error MessageEntity UnknownExplanation The collector entry, which contains information stored on the source router for the collector, is missing.
Recommended Action Create another instance of the same collector.
Error MessageInvalid Value SpecifiedExplanation When defining an operation or target an invalid value was specified.
Recommended Action Verify the values specified for the target and operation.
Error MessageResource UnavailableExplanation The SNMP server is busy.
Recommended Action Try the operation at a later time.
Error MessageResponse Timed OutExplanation The SNMP server timed out.
Recommended Action The SNMP server might time out for any of the following reasons:
•
SNMP is not enabled on the router
•
Server could not reach the source router
•
Invalid read community string
•
SNMP agent is not configured on port 161 on the management station
•
Invalid IP address for the source router
•
Source router is not operational
Data Access Error Messages
This section provides explanations and recommended actions for error messages that you might encounter when viewing statistics, viewing real-time response-time data, or when using the demand polling option.
Error MessageRegistration with Display Server failed. Display Server Proxy failed to connect to the Data RetrieverExplanation The Display Server is unable to establish communications with the Data Retriever process.
Recommended Action Retry the operation that resulted in this message. If the problem persists, perform the following actions:
•
Stop all IPM processes using the ipm stop command.
•
Restart the IPM server and IPM client applications using the ipm command.
Error MessageRegistration with Display Server failed. Exception: <client-name>Explanation The client application attempted to register with the display server using a name identical to that of an existing client.
Recommended Action Retry the operation that resulted in this message. If the problem persists close the IPM client application window and restart it.
Error MessageGet Hops failed. Invalid Path ID: <path-id>Explanation The Display Server is unable to retrieve the list of hops of the selected path from the database because an invalid path ID is specified.
Recommended Action Retry the operation that resulted in this message. If the problem persists, perform the following actions:
•
Stop all IPM processes using the ipm stop command.
•
Restart the IPM server and IPM client applications using the ipm command.
Error MessageDeregistration with Display Server failed. Exception: <name>.Explanation The last window closed failed to deregister with the display server.
Recommended Action If the problem persists, perform the following actions:
•
Stop all IPM processes using the ipm stop command.
•
Restart the IPM server and IPM client applications using the ipm command.
Error MessageDemand Poll failed.Explanation The Display Server is unable to perform the requested demand poll operation.
Recommended Action Retry the operation that resulted in this message. If the problem persists, perform the following actions:
•
Stop all IPM processes using the ipm stop command.
•
Restart the IPM server and IPM client applications using the ipm command.
Error MessageStart Polling failed. Unable to start new poller.Explanation The Display Server is unable to start a real-time poller.
Recommended Action Retry the operation that resulted in this message. If the problem persists, perform the following actions:
•
Stop all IPM processes using the ipm stop command.
•
Restart the IPM server and IPM client applications using the ipm command.
Error MessageStop Polling failed. Unable to stop requested pollerExplanation The Display Server is unable to stop the specified real-time poller.
Recommended Action Perform the following actions:
•
Stop all IPM processes using the ipm stop command.
•
Restart the IPM server and IPM client applications using the ipm command.
Error MessageUnregistration with Display Server failed. Exception: <name>.Explanation The last window closed failed to deregister with the display server.
Recommended Action Perform the following actions:
•
Stop all IPM processes using the ipm stop command.
•
Restart the IPM server and IPM client applications using the ipm command.
Database Access Error Messages
This section provides explanations and recommended actions for error messages that you might encounter when IPM is unable to access the IPM database.
Error MessagesRegistration with Display Server failed. Unable to access databaseStart Polling failed. Unable to access the databaseGet Threshold Data failed. Unable to access databaseGet Hourly Response Data failed. Unable to access databaseGet Daily Response Data failed. Unable to access databaseGet Weekly Response Data failed. Unable to access databaseGet Monthly Response Data failed. Unable to access databaseGet Hourly Hop Response Data failed. Unable to access databaseGet Daily Hop Response Data failed. Unable to access databaseGet Weekly Hop Response Data failed. Unable to access databaseGet Monthly Hop Response Data failed. Unable to access databaseGet Hourly Error Distribution Data failed. Unable to access databaseGet Daily Error Distribution Data failed. Unable to access databaseGet Weekly Error Distribution Data failed. Unable to access databaseGet Monthly Error Distribution Data failed. Unable to access databaseGet Hops failed. Unable to access databaseGet Path Data failed. Unable to access databaseExplanation The Display Server is unable to retrieve the requested information from the database.
Recommended Action Verify that the database server is running using the ps command. For example:
# ps -ef | grepThe database server process is CWB_ipmDBserver. If the database server is running, this process appears in the list of active processes.
Then perform the following actions:
•
Stop all IPM processes using the ipm stop command.
•
Start the database server and the IPM server using the ipm start command.
•
Restart the IPM client application using the ipm start client command.
Feedback