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 (SC23-6373).

Table 1. Error messages
Error	Description	Action
`AlcatelOSOS: alarm parser failed to parse message - discarding` `AlcatelOSOS: alarm parser failed to create events from parsed message - discarding` `AlcatelOSOS: alarm parser was unable to understand message. Next tokens are:` `AlcatelOSOS: alarm parser found unbalanced brackets starting at:` `AlcatelOSOS: alarm parser was unable to understand message. Next tokens are:`	The probe could not parse the alarms correctly. The alarm could be corrupted or unsupported.	Check the value specified for the AttributeSeparatorIndicator and AttributeDelimiterIndicator properties.
`AlcatelOSOS: alarm parser found value with no name`	The probe found an alarm without field names. The probe will create tokens for these alarms with the name `unknownDataxx`, where `xx` is an integer.	No action required, this message is for information only.
`AlcatelOSOS: unable to understand hostname and port given for OSOS host:`	The probe could not use the hostname and port specified.	Check the values specified for the Host and Port properties.
`AlcatelOSOS: unable to resolve hostname host name`	The probe could not resolve the host name to a specified address.	Check the values specified for the Host property. Check the resolver setting on the probe host.
`AlcatelOSOS: login timed out`	An attempted login by the probe to the Alcatel-Lucent OS-OS system has timed out.	Increase the value of the LoginTimeout property. Ensure that the OS-OS interface is operating correctly. Check the connection between the probe and the OS-OS interface.
`HeartbeatManager: exceeded consecutive heartbeat threshold`	The number of heartbeat requests that the probe has sent to the host has exceeded the set limit.	Increase the value of the RestartOnIdleTimeout property.
`HeartbeatManager: failed to receive heartbeat response` `Heartbeat Manager: number of lost heartbeats N exceeds threshold nn`	The probe has not received a response to its heartbeat requests.	Check that OS-OS system is working correctly. Increase the value of the HeartbeatTimeout property.
`Probe: AttributeDelimiter Indicator property should be one character` `Probe: AttributeSeparator Indicator property should be one character`	The probe found that the value of the named properties exceeded the set limit.	Change the value of the AttributeDelimiterIndicator property or the AttributeSeparatorIndicator property to a single character.
`ResyncManager: resynchronisation is taking too long` `ResyncManager: resynchronisation request has timed out`	The resynchronization of the alarms is taking too long or has timed out.	Check the value of the SynchronizationTimeout property.
`UnsolicitedAlarmsManager: failed to subscribe for notifications: request timed out` `UnsolicitedAlarmsManager: failed to subscribe for notifications: OSOS rejected request`	The probe failed to subscribe for notifications.	Ensure that the OS-OS system allows the probe to subscribe. Check the connection between the probe and the OS-OS system.