10.5.2  Simple Network Management Protocol (SNMP) to HP SIM or OVO

HP Systems Insight Manager 4.2 extends existing management capabilities for ProLiant, Integrity, and HP 9000 systems with a HP BladeSystem Integrated Management and support for value added plug-ins, improved rapid deployment, vulnerability and patch management, and virtual machine management and control.

HP SIM runs on Port 280 and uses the SNMP service provided by the operating system for monitoring SNMP traps.

HP SIM is not required to be installed on the same system as SEA.

The desta snmp [on | off] command (see Chapter 3) enables or disables SNMP Notification.

HP SIM Service Notification overview:

The HP Services analysis tools, WEBES and OSEM, generate service notifications to HP SIM via a specific SNMP trap type if analysis has determined there are serviceable events.

This is supported in Web-Based Enterprise Services (WEBES) v4.4.1 or greater and Open Service Event Manager (OSEM) v1.3 or greater. This capability has been a part of HP SIM since v4.0.

To download HP SIM and for more information on HP SIM, go to:

http://www.hp.com/go/hpsim

HP SIM handling of Service Trap Notifications:

Upon receipt of service trap notifications from WEBES, HP SIM handles them in much the same way as any other management event.

There are several ways to view these events. One way is to view them under All Events as this will always be done by default. Another way is to view them under Event Lists using the Advanced Search capability. For HP SIM 4.x, the user must use Advanced Search and do the following:
Search for events where event category name is HP Service Events and type name is any. In HP SIM 5.0, this is done by default by showing HP Service Events under Event Lists, Events by Severity list.

The Event Type is shown as `A Service Incident has been reported'.

The System Name and Event Time refer to the failing system or subsystem and the time the error was reported.

The Severity is shown as Major since the service notification is only sent if analysis has determined that a maintenance action should be performed and also since the service trap contains information in addition to what may be found in the original events such as SNMP traps sent by Insight Management agents.

In the case of WEBES, notification is sent based on the operating system event log analysis so there may or may not be other traps sent by management agents.

New Service Trap and Service MIB information:

HP SIM 5.0 ships with a newer version of the service MIB to support enhanced service traps sent by WEBES v4.4.3.

The new MIB can be compiled into older versions of HP SIM 4.x and will recognize both the old and new versions of service traps. To obtain the latest Service MIB, visit the following link:

http://h18023.www1.hp.com/support/svctools/

Select download service MIB under WEBES or OSEM. To register the new service MIB with HP SIM perform the following procedure on the system running HP SIM:

Open an MS-DOS window or UNIX shell.
Change to the directory containing the MIBs such as c:\program files\hp\systems insight manager\mibs for Windows or /opt/mx/mibs for Linux.
Run "mxmib -d cpqservice.mib" to unregister the old service MIB.
Delete the old cpqservice.mib and cpqservice.cfg.
Copy the new cpqservice.mib to the MIBS directory.
Run "mcompile cpqservice.mib" to compile the new service MIB into the ,cfg format.
Run "mxmib -a cpqservice.cfg" to register the new service MIB.

10.5.2.1  Unknown Host Exception in Director Log When Manually Analyzing Files with Notifications

If you have enabled SNMP service trap notifications using the "desta snmp on" command, then the following commands will cause WARNING messages in the Director log. These messages are expected and ignorable. The Director will attempt to find the IP address of the TLV_Computer_Name in the binary event, to fill in another field of the trap for informational purposes. Since that host name will not exist on the TCP/IP network for the SEA Test Event (and probably not for any of the SEA example binary event logs provided either), the WARNING is logged, but the SNMP trap will still be sent successfully. This is working as designed.

The following command:

wsea test nosys

...causes the following error in the Director log:

RECOVERED FROM ERROR on May 3, 2005 7:28:17 AM MDT (2888.161 sec elapsed)
Error formatting problem report for SNMP
Current Thread[Thread-79,5,main]
EXCEPTION java.net.UnknownHostException: *SEATEST*: *SEATEST*
at java.net.InetAddress.getAllByName0(InetAddress.java:1011)

The following command:

wsea ana input <file> notify [customer|visible|every]

...causes the following error in the Director log, where "Computer Name Here" will be the contents of the "Reporting Node" field of the SEA Problem Report:

RECOVERED FROM ERROR on May 3, 2005 8:15:54 PM PDT (990.047 sec elapsed)
Error formatting problem report for SNMP
Current Thread[Thread-91,5,main]
EXCEPTION java.net.UnknownHostException: Computer Name Here
at java.net.InetAddress.getAllByName0(Unknown Source)