Error messages

Error messages provide information about problems that occur while running the probe. You can use the information that they contain to resolve such problems.

The following table describes the error messages specific to this probe. For information about generic error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).

Table 1. Error messages
Error	Description	Action
`Cannot connect to host`	There is a problem connecting to the host.	Check that the host is running. If it is, try using the IP address instead of the host name.
`Connection in unknown state`	There is a problem with the connection between the probe and the fault adapter.	Check that the fault adapter is working correctly. If it is, restart the probe.
`Connection closed`	The probe lost its connection to the target system.	Check that the Tellabs 8000 host is running correctly.
`Connection closed during expect call`	The probe failed to receive data from the target system while logging in.	Make sure your authentication information is correct and connection to the host is not lost.
`Failed to connect - aborting`	The ObjectServer is not available.	Check that the ObjectServer is running, that the interfaces file on the system where the probe is installed has an entry for the ObjectServer, and that there is no networking problem between the two systems.
`Failed to inform Process Agent of status - aborting`	The probe was unable to inform the process agent that it is running.	Restart the probe.
`Failed to process arguments` `Failed to initialize probe API` `Session create failed - aborting`	These are internal errors.	Contact IBM Software Support.
`Failed to retrieve value for property: property_name`	The value for the named property has not been set correctly.	Check the properties file for the named property, and adjust its value accordingly.
`Failed to read rules - aborting`	A property or command-line option is pointing to a non-existent rules file.	Check that the command-line option or the properties file refers to the correct rules file.
`Failed to send command command`	When the probe tried to log in or log out of the host, a chat command failed. The given `command` is the one the probe failed to send.	Check that the host you are connecting to is running correctly.
`Fault buffer memory alloc error` `Failed to allocate memory`	The probe failed to allocate internal storage.	Make more memory available.
`Hearbeat Timeout number_of_seconds is larger than Heartbeat Interval number_of_seconds`	The heartbeat timeout has been set to a value that is greater than the heartbeat interval.	Adjust the values set for the HeartbeatTimeout and HeartbeatInterval properties so that the length specified for the heartbeat timeout is not larger than the heartbeat interval.
`Login/Logout timed out after number seconds` `Protocol timed out after number seconds`	The probe timed out while trying to log in to the host.	Check that the Tellabs 8000 host is running correctly.
`Read error from switch`	The probe read a message from the target switch but it could not interpret the message.	Check that the fault adapter is working correctly.
`SendAlert failed`	The probe was unable to send an alert to the ObjectServer.	Check that the ObjectServer is available.
`Tellabs fault adapter may be down`	There is a problem connecting to the fault adapter.	Check that the fault adapter is running properly. You may need to restart the Tellabs 8000 INM system.
`SessionProcess failed %d`	The probe was unable to process the alert against the rules file.	Contact IBM Software Support.
`Unable to get events`	If this message was sent at startup, it indicates that there was a problem initializing the connection due to insufficient memory. If this message was sent after some events had been parsed, it indicates that there was a connection failure.	Check that the ObjectServer is running and check the connection between the Tellabs 8000 host and the host running the ObjectServer. Then try again to run the probe.
`Unable to open stream capture file file_name`	The probe was unable to open the stream capture file indicated by the error message.	Check that the file permissions have been set correctly.
`Unable to log in to host_name : port_number`	The probe could not log in to the host on the port indicated in the error message.	Check the values set for the Host and Port properties.
`Unable to compile regexp for string`	A regular expression is incorrectly formed in the rules file.	Check the rules file for the regular expression indicated and correct the entry.
`Unable to log in to switch number`	The probe was unable to log in to the switch.	Check that the properties are set correctly.
`Unknown byte swap requested for size size`	This is an internal error.	Contact IBM Software Support.
`Unknown connection error` `Unknown expect connection error`	The probe is working correctly but a library used by the probe has been changed.	Contact IBM Software Support.