2 broadcast mode, Broadcast mode – HP NonStop G-Series User Manual
Page 54

Event Delivery Management 54
6-2 Broadcast Mode
The broadcast mode is used to send NonStop event messages to multiple Enterprise Management Servers.
The figure below shows a monitoring scenario where the HP Operations Manager (HPOM) Servers are
configured for Broadcast mode.
Figure 6-1
Event Monitoring in Broadcast Mode – for HPOM Environment
The broadcast mode can be used in the following scenarios to ensure guaranteed delivery of events:
•
Enterprise Manager Services Down
In the broadcast mode, if the Enterprise Manager Service(s) fail and are not available for any reason, then
a SAF file is used to store the events until the Enterprise Manager Services are started. OVNM and the
communication link on the Enterprise Manager Server continue running to ascertain whether the Enterprise
Manager environment is down.
•
OVNM Connection with the NonStop Server Down
When the connection to the NonStop fails then the Elink or the OVNM detects a connectivity failure. On re-
establishing of connection, the Elink registered with the NonStop will send a Catch-up request to recollect
the lost messages. In the catch-up monitoring mode the events which have been missed are retrieved and
replayed via the catch-up distributor and are sent directly to the OVNM. While catch-up is in progress, the
real-time incoming messages are retrieved from the primary distributor and are stored in a temporary SAF
files and are processed as soon as the catch-up processing terminates. This ensures that the messages are
always logged in sequence to the Enterprise Manager and state-propagation in service views is always in
synchronism with real-time. SAF files are currently numbered 0 upwards for each node connected.
To set up the broadcast mode:
•
The -msgqueuing parameter should be used in the ovnm_start.sh script. This parameter enables OVNM to
request a catch-up of lost events during the disconnection to the NonStop Server. When the connection to
the NonStop is reconnected then the events, which have been missed are retrieved and replayed via the
catch-up distributor and sent directly to the OVNM.
•
The Service type parameter in the elink.cfg file should be set to Alert.