In this scenario, IBM® Tivoli® Monitoring agents are
configured to forward events directly to either the Netcool/OMNIbus
Probe for Tivoli EIF or the
Netcool/OMNIbus Probe for SNMP.
This architecture eliminates the interaction with the hub monitoring
server. If your environment uses firewalls, you must ensure any IBM Tivoli Monitoring
agents and Netcool/OMNIbus probes can communicate with each other
and are not restricted by the firewall. Because events are forwarded
directly to Netcool/OMNIbus by the IBM Tivoli Monitoring agents, no
bidirectional communication is required. Any actions taken on events
through Netcool/OMNIbus are not forwarded back to the IBM Tivoli Monitoring
agent.
The Netcool/OMNIbus Probe for Tivoli EIF supports both SSL and non-SSL connections
with monitoring agents. If you want to use an SSL connection, you
must have version 12.0 or later of the probe.
You can configure the agents to send heartbeat events at regular
intervals to Netcool/OMNIbus. You can enable heartbeat automation
in the Netcool/OMNIbus ObjectServer. By using heartbeat automation,
a "Heartbeat Missing" event is opened if a heartbeat event is not
received from an agent in the expected time frame. By enabling heartbeat
automation, the Netcool/OMNIbus operator knows when a monitoring agent
is not available. The heartbeat interval is configurable.
Figure 1. Multiple IBM Tivoli Monitoring
Agents and one Netcool/OMNIbus ObjectServer
Uses
Use this scenario when you have agents
that are not connected to IBM Tivoli Monitoring Server. You
can also use this architecture if you want monitoring server connected
agents to send their critical events to the Netcool/OMNIbus Objectserver.
The agents can send events directly to the OMNIbus server through
the Netcool/OMNIbus Probe for Tivoli EIF
or the Probe for SNMP.