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 ProbeWatch messages that the probe generates. For information about generic Netcool/OMNIbus ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

Table 1. ProbeWatch messages
ProbeWatch message	Description	Triggers/causes
`Error in Retry property value. Probe will shutdown`	The Retry property is set to invalid value and so the probe is shutting down.	An invalid value was set for the Retry property.
`Probe has lost connection to CORBA interface, error external to CORBA interface`	The probe has lost the connection to the CORBA interface.	The connection between the SpectroSERVER and the CA Spectrum EMS is down.
`Probe has lost connection to CORBA interface. Error internal to CORBA interface`	The probe has lost the connection to the CORBA interface.	The connection between the probe and the server is down due to incorrect probe settings or an inactive SpectroSERVER.
`New successful connection to the CORBA interface, connected to the Primary SpectroSERVER`	The probe connected to the primary SpectroSERVER.	The connection to the primary SpectroSERVER was successful.
`New successful connection to the CORBA interface, connected to the Secondary SpectroSERVER`	The probe connected to the secondary SpectroSERVER.	The primary SpectroSERVER has failed, and the probe has connected to the secondary SpectroSERVER.
`Start resync for spectroServerName`	The probe started the resynchronization process with the Spectrum server indicated.	Either a resynchronization was requested by a CLI command, or one was initiated automatically following the elapsing of a resynchronization interval, or the failover of the Spectrum server.
`Complete resync for spectroServerName`	The probe's resynchronization with the Spectrum server indicated has completed.	The resynchronization with the Spectrum server indicated completed successfully.
`Probe successfully connected to <target host>`	The probe started and is running successfully.	The probe process was started by the operator.
`Running ...`	The probe started and is running successfully.	The probe process was started by the operator.
`Probe is shutting down Going Down ...`	The probe is shutting down.	The system has been requested to shut down the probe because the probe process was terminated manually by the operator.
`<target host> head is shutting down, remove from active host list`	CA Spectrum EMS is shutting down after the probe connected to SpectroSERVER. This ProbeWatch will be shown when the retry value for the probe is set to 0.	CA Spectrum EMS that is connecting to the probe is shutting down. This is either because the Spectrum service has been stopped manually by operator or has aborted.
`Error in spectrum alarm severity values. Probe will shutdown.`	Invalid values have been set for either the MaxSpectrumSeverity property or the MinSpectrumSeverity property .	Either the value set for the MinSpectrumSeverity property is higher than that set for the MaxSpectrumSeverity, or the value set for either MinSpectrumSeverity or MaxSpectrumSeverity is not between 0 and 6.
`Received connection from 127.0.0.1`	The probe connected to command port session and is ready to receive CLI commands.	The operator managed to successfully telnet to the command port.
`Failed to open listening socket: java.lang.Illegal ArgumentException: Port value out of range: <invalid value>`	The probe failed to listen to the command port socket.	The CommandPort property is set to an invalid value. Either the value is not an integer, or it is set to a negative value.
`Failed to open listening socket: java.net.BindException: Address already in use`	The probe failed to listen to the command port socket.	The CommandPort property is set to a value that is not already in use.
`Error in parsing host configuration file. Probe will shutdown`	The probe failed to parse the host configuration file.	Either there are missing values in the host configuration file (for example a missing SpectroServer host), duplicate entries were found in the host configuration file for at least one of the following properties: AlarmAttributes, TimeStampFile, FetchEventFormatFields, FetchEventString, EventFormatFile, ProbCauseLookupFile, ResyncInterval, ResyncSQLCmd, or the path to the host configuration file specified for the Host property is an invalid path.