ProbeWatch messages
During normal operations, the probe generates ProbeWatch messages and sends them to the ObjectServer. These messages tell the ObjectServer how the probe is running.
The following table describes the raw ProbeWatch error messages that the probe generates. For information about generic ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).
ProbeWatch message |
Description |
Triggers/causes |
---|---|---|
Communication failure: Lost connection to NotifiationIRP CORBA.TRANSIENT Exception: Lost connection to NotificationIRP CORBA.OBJECT_NOT_EXIST Exception: Lostconnection to NotificationIRP Failed to connect to NotificationIRP: Shutting down Failed to Connect: Either, the server is not running, the IOR is out of date, or probe cannot reach remote Server |
The communication with the notification IRP server has failed. |
The probe lost its connection to the notification IRP server. |
END SYNCHRONIZATION |
The synchronization of alarms has stopped. |
The probe has resynched all the available alarms in the server. |
Failed to find IOR file alarmirp_ior_file |
The specified alarm IRP file does not exist. |
The IRP manager has been set up incorrectly. |
Failed to find IOR file notificationirp_ior_file |
The specified notification IRP file does not exist. |
The IRP manager has been set up incorrectly. |
Failed to get IRP Outline (GetIRPOutline exception caught when calling get_IRP_outline) |
The probe could not get the IRP object. |
There is a problem with the CORBA interface. |
Failed to get IRP reference (GetIRPReference exception caught when calling get_IRP_reference Failed to get IRP references - invalid parameter (InvalidParameter exception caught when calling get_IRP_reference). |
The probe could not get the IRP version. |
An incorrect reference is specified in the IRP file. |
Failed to listen for commands on port number listening_port |
A problem occurred while trying to listen for commands. |
Either there was a problem initializing the connection due to insufficient memory or (if this message was sent after some events had been parsed) there was a license or a connection failure. |
Failed to log in to interface (InvalidParameter exception caught when calling get_IRP_outline) |
The probe failed to login to the server. |
The specified user name and password are incorrect. |
Failed to log in to the Nortel SecurityIRP - incorrect user name/password |
The probe has failed to login to the Nortel Security IRP. |
The password entered is mismatching the user name. |
Invalid IRPVersion (InvalidIRPVersion exception caught when calling get_IRP_outline) |
The specified IRP version is incorrect. |
An incorrect IRP name is specified in the properties file. |
NetcoolIRPManager: Failed to find IOR file ior_file |
The specified IOR file does not exist. |
The IRP Manager has been set up incorrectly. |
PermissionDenied (PermissionDenied exception caught when calling get_IRP_outline) |
The permission to login to the server is denied. |
The probe does not have appropriate permissions set to log in to the server. |
START SYNCHRONIZATION |
The synchronization of alarms has started. |
The probe started to resynchronize alarms collected in the system during the timeout period. |
Will listen for commands on port number listening_port |
The probe will listen for commands on the specified port number. |
The probe has successfully created the specified command port in the properties file. |