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 or causes
`Dropping the traps`	The probe is dropping events.	The trap limit specified by the TrapQueueMax property has been exceeded.
`Going Down`	The probe is shutting down.	The probe is shutting down after performing the shutdown routine.
`Heartbeat Message`	The heartbeat message that the probe sends to the ObjectServer.	The probe has not received any events for the time specified by the Heartbeat property. This may be useful for debugging purposes.
`Running ...`	The probe is running normally.	The probe has just been started up.
`Unable to get events`	A problem occurred while trying to listen for traps.	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 connection failure.
`mttrapd on [ip_address] is blocked`	The host at the IP address specified is currently blocked.	The host at the IP address specified is currently sending too many traps.
`mttrapd on [ip_address] is unblocked`	The previously blocked host at the IP address specified is now unblocked.	The rate of traps sent by a previously blocked IP address has reduced. While the probe is exiting, each IP in the drop list will be removed as part of the clean up process.
`TRAP_FLOOD_REPORT_START at [time]` `TRAP_FLOOD_REPORT_HOST: message` `TRAP_FLOOD_REPORT_STOP at [time]`	These three ProbeWatch messages will appear together and form the periodic flood report. The first and the last message indicate the start and the end of the reporting period. The middle part of the message contains the trap statistics for the host at the IP address specified. This can be a combination of the following: `TRAP_FLOOD_REPORT_HOST:ip= [ip_addr] status=[DROP] since "timestamp" seconds. inqueue=[ip_trap_count] nosdrop=[ip_drop_count]` and `TRAP_FLOOD_REPORT_HOST:ip= [ip_addr]status=[ACCEPT] inqueue=[number_of_traps]` If the message exceeds the `Summary` length limit, it will be truncated.	This is the periodic flood report that the probe generates. The periodic flood report shows the trap statistics of the blocked, or a newly unblocked IP addresses (`ip_addr`) specified in the ProbeWatch messages.