Managing your infrastructure from chip to the business service

Figure 3 shows a service view of the IM Agent services running on a HP ProLiant Server. The HP SIM
integration discovery has found IM Agents on the node “DIDICAS” and created a Systems
Infrastructure service map showing the discovered services.
Figure 3: Service map on HP OM displaying Insight Management Agent services
ProLiant system monitoring
The SIM SPI provides SNMP trap interceptor policies (templates) to monitor ProLiant servers. The
templates generate messages regarding the status of the monitored node network interface, storage,
environmental, power management, and so on. An incoming message automatically acknowledges
any previous message from the same monitored object. This helps display the latest status of the node
in the HP OM active message browser and service views. The message contains an operator action to
launch the System Management Homepage for the node so that the root cause of the message can be
investigated.
To use this capability, you must install the IM Agent and the OM Agent on the managed server. You
must configure the IM Agent trap destination manually using the application provided in the SIM SPI
or through the server Systems Management Homepage, and then deploy the SNMP trap policies
manually to the IM Agent nodes.
When the event forwarding configuration steps are completed, the OM agent (opcmsg) forwards the
HP SIM events to the HP OM server through so that the messages reach HP OM in a reliable manner.
Event forwarding
When IM and OM agents cannot be installed on the ProLiant managed server, or to manage a
device other than a ProLiant server, HP SIM event forwarding feature can be used to provide basic
monitoring. Using this feature, specified events received by the HP SIM central management server
are forwarded to the OM central management server, where they are associated with the HP SIM
icon in the HP SIM service view. Clearing or acknowledging the event in either the OM or the HP SIM
console clears or acknowledges it in the other console. Note that multiple occurrences of the same
message type are not collapsed in the OM message browser for this type of integration. Also, the
ProLiant SNMP trap interceptor policies are not active in this configuration.