Hp sim handling of service event notifications – HP Systems Insight Manager User Manual
Page 484
If you do not use Public for the SNMP community string, OSEM will not perform SNMP Gets properly. For
this to happen, you must set the HP Systems Insight Manager trap community name field to the desired
value in the OSEM Settings: Internal.
HP SIM handling of service event notifications
Upon receipt of service trap notifications from WEBES or OSEM, HP SIM handles them in much the same
way as any other management events.
There are two ways to view these events:
•
View them under All Events, which is always done by default.
•
View them under event collections using the Advanced Search capability.
For HP SIM 4.x, you must use Advanced Search and search for events where the event category
selection name is HP Service Events and type name is any. From here, you can select View to
•
see the HP Service Events, or you can select Save As to create a collection category. This collection
can be viewed under the left pane based on the location where you saved it.
•
For HP SIM 5.0 and later, this search is performed by default with the All HP Service Events
collection, located under Events
→Service Events in the System and Event Collections panel.
On the event table view page, the Event Type is shown as A Service Incident has been reported (Type
x)
, where Type x is the version of the SNMP trap or SOAP event. See the table under
for a list of differences between the service event notification types. The System Name and Event
Time
refer to the failing system or subsystem and time the error was reported. The Severity is shown as
Major
because the service notification is only sent if analysis has determined that a maintenance action
should be performed and because the service trap contains information in addition to what can be found
in the original events such as SNMP traps sent by Insight Management Agents. Beginning with HP SIM 5.0
with SP3, the severity follows the severity assigned by the OSEM or WEBES event type. For most events the
severity will still be shown as Major indicating these are hardware events requiring service intervention and
are submitted as incidents by the Remote Support Pack software. For service events generated as a result of
test traps or that provide customer notification only, the severity is Informational.
In WEBES, notification is sent based on operating system event log analysis so there might be other traps
sent by management agents.
HP SIM Service Notification overview and setup information
HP SIM 5.0 ships with a Service MIB to properly recognize service traps sent by OSEM and WEBES. HP
recommends using the version of the Service MIB that shipped with HP SIM. If you need to replace the MIB,
download it from
by selecting Service MIB Zip file under
WEBES or OSEM, and instructions will be provided on the version to select. The zip file contains the .mib
and .cfg files, and a readme file.
There are currently two versions of the MIB, which are based on the version of HP SIM being used, and the
service trap type being sent by WEBES or OSEM; there are currently three types or revisions of the service
trap. A new type of notification known as type 4 is done through SOAP, but does not require the MIB. See
the table under
“Service trap notification details”
for a list of differences between the service event notification
types.
Although the new version of the Service MIB recognizes all three service event trap types, it does not work
properly if compiled or updated into HP SIM 5.0 with SP5.
To update the new service MIB with HP SIM, perform the following procedure on the system running HP SIM:
1.
Open an MS-DOS window or UNIX shell.
2.
Change to the directory containing the MIBs.
•
For Windows:
c:\program files\hp\systems insight manager\mibs
•
For Linux:
/opt/mx/mibs
484 Administering systems and events