Refrigerator User Manual

Integration in Tivoli NetView 41
Configuration and Operation Status Indication in Map
5.2.3 Automatic Monitoring of the ServerView Status
The following components automatically monitor this ServerView status:
– Data Collection for the MIB object sniInvCondition from the INVENTORY-MIB
– The Threshold and Rearm events for this Data Collection
– A reaction script for evaluating the values received, which sets the status of
the ServerView component symbol accordingly.
I All devices for which this status monitoring is enabled must be configured
as Fujitsu Siemens servers, i.e., represented by at least one symbol with
the symbol type FujitsuSiemens in the map. If you do not want any such
status monitoring to be performed, you can undo the configuration of the
nodes.
5.2.4 How Status Monitoring Works
The value of the MIB variable sniInvCondition is periodically polled for each
required Fujitsu Siemens server via the Data Collection.
I To keep the network load down to a minimum, you should adapt the
“generic” Data Collection created during the installation of the integration
package (with the source definition “*.*.*.*”) before using it.
The related threshold monitoring is defined so that both the Threshold and the
Rearm events are triggered at each successful poll.
As a reaction to the Threshold event, the \usr\ov\bin\setServerViewStatus.bat
reaction script is executed. This script receives the NetView-Object-ID of the
corresponding server and the current value of the MIB variable sniInvCondition
as its parameters. No automatic reaction is involved in the Rearm event. It
simply serves to reactivate the Threshold event.
The \usr\ov\bin\setServerViewStatus.bat script determines a corresponding
NetView status from the ServerView status and the selection name of the
related ServerView component symbol from the NetView-Object-ID of the
server involved. The determined status of this ServerView component symbol
is then set in the submap of the server using the OV_Set_Status_Color event.