HP Sim - Sun

Third Party System Management
Integration Software
Monitoring Sun Servers in an HP SIM Environment
Servers supported:
▪ Sun Fire x64 Servers
▪ Sun SPARC Enterprise Servers
A complete, current list of supported Sun servers, service processors, and service
processor firmware is available at the following web site:
http://www.sun.com/systemmanagement/tools.jsp
Please consult this web site before configuring HP SIM to work with Sun servers. .
Part No. 820-0540-12

Sun Microsystems, Inc.
www.sun.com
May 2008, Revision 01

Copyright 2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and
without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents
and one or more additional patents or pending patent applications in the U.S. and in other countries.
This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and
ecompilation. No part of the product or of this document may be reproduced in any form by any means without prior written
authorization of Sun and its licensors, if any.
Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered
trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.
Sun, Sun Microsystems, the Sun logo, Sun Blade, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in
the U.S. and in other countries.
U.S. Government Rights—Commercial use. Government users are subject to the Sun Microsystems, Inc. standard license agreement
and applicable provisions of the FAR and its supplements.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND
WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE
HELD TO BE LEGALLY INVALID.
Copyright 2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, États-Unis. Tous droits réservés.
Sun Microsystems, Inc. possède les droits de propriété intellectuels relatifs à la technologie décrite dans ce document. En particulier,
et sans limitation, ces droits de propriété intellectuels peuvent inclure un ou plusieurs des brevets américains listés sur le site
http://www.sun.com/patents, un ou les plusieurs brevets supplémentaires ainsi que les demandes de brevet en attente aux les États-
Unis et dans d’autres pays.
Ce document et le produit auquel il se rapporte sont protégés par un copyright et distribués sous licences, celles-ci en restreignent
l’utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune
forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a.
Tout logiciel tiers, sa technologie relative aux polices de caractères, comprise, est protégé par un copyright et licencié par des
fournisseurs de Sun.
Des parties de ce produit peuvent dériver des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque
déposée aux
États-Unis et dans d’autres pays, licenciée exclusivement par X/Open Company, Ltd.
Sun, Sun Microsystems, le logo Sun, Sun Blade, et Solaris sont des marques de fabrique ou des marques déposées de Sun
Microsystems, Inc. aux États-Unis et dans d’autres pays.
LA DOCUMENTATION EST FOURNIE "EN L’ÉTAT" ET TOUTES AUTRES CONDITIONS, DÉCLARATIONS ET RANTIES
EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES DANS LA LIMITE DE LA LOI APPLICABLE, Y COMPRIS
NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE À LA QUALITÉ MARCHANDE, À L’APTITUDE À UNE
UTILISATION PARTICULIÈRE OU À L’ABSENCE DE CONTREFAÇON.
Monitoring Sun Servers in an HP SIM Environment ii

Contents
Introduction 1
Categories of Sun Servers 1
HP SIM and Sun MIBs 2
Working with Sun MIBs 2
Obtaining Sun MIBs 4
Levels of Integration with HP SIM 5
This Manual 6
Requirements 6
Monitored Devices 6
HP SIM Management Server 7
Configuring Sun Devices to be Monitored by HP SIM 8
Configuring Sun Servers to be Monitored by HP SIM (Operating System Integration) 8
Configuring SNMP on Sun Fire x64 Servers Running Windows 8
Configuring ILOM and Embedded LOM Service Processors to be Monitored by HP SIM 10
Configuring Sun ILOM 1.1 Service Processors to be Monitored by HP SIM 11
Configuring Sun ILOM 2.0 Service Processors to be Monitored by HP SIM 14
Configuring Sun Embedded LOM Version 2.91 Service Processors to be Monitored by
HP SIM 18
Configuring Sun Embedded LOM Version 4.x Service Processors to be Monitored by HP
SIM 21
Configuring HP SIM to Discover and Monitor Sun Devices 25
Configuring HP SIM to Discover and Monitor Sun Servers 25
Configuring HP SIM to Discover and Monitor Sun Service Processors (Service Processor
Integration) 27
Configuring Proper SNMP Strings 28
Compiling and Registering Sun MIBs 28
Defining a SUN ILOM Product Model for ILOM 30
Defining a SUN ELOM Product Model 36
Discovering Sun Devices 45
Discovering Sun Devices Automatically 45
Monitoring Sun Servers in an HP SIM Environment iii

Discovering Sun Devices Manually 45
Verifying Overall Configuration 47
Verifying Successful Configuration for HP SIM 47
Verifying Configuration Manually 48
Verifying Configuration Remotely Using ALOM 48
Verifying Configuration Remotely Using IPMItool 49
Verifying Configuration Remotely Using psradm 51
Monitoring Sun Devices in HP SIM 53
HP SIM Views on Sun Servers (Operating System Level Integration) 53
Server Identity Information 54
Tools & Links to Device Resources 54
Server Events Information 54
WBEM Views on Sun Fire x64 Servers (Operating System Level Integration) 55
Server Identity Information 56
Server Status Information 57
Server Configuration Information 58
HP SIM Views on Sun Service Processors (Service Processor Level Integration) 59
Service Processor Identity Information 59
Tools and Links to Service Processor Resources 59
Service Processor Events Information 63
Release Notes 65
SNMP MIB Compilation in HP SIM 65
Sun MIBs 66
What’s New? 67
Server and Firmware Support 67
Improved SNMP Sensor Reporting 67
Index 68
Monitoring Sun Servers in an HP SIM Environment iv

CHAPTER 1
Introduction
HP Systems Insight Manager (hereafter HP SIM) is an enterprise management

application that is built primarily for managing HP ProLiant, HP Integrity, and HP
9000 servers running the Microsoft® Windows®, Linux®, and HP-UX operating
systems. Although designed primarily to support HP servers, HP SIM does support
non-HP devices via industry-standard protocols such as the Simple Network
Management Protocol (SNMP), Web Based Enterprise Management (WBEM), and
secure Hypertext Transfer Protocol (HTTPS).
The configurations discussed in this manual have been tested with HP SIM Release
5.0 and with the Sun servers listed in the Supported Servers section of this chapter.
The servers tested were running Microsoft® Windows® Server 2003.
▬▬▬▬▬
Categories of Sun Servers
The Sun-HPSIM configuration described in this whitepaper is one of several Sun
ISV System Management solutions that provide Sun-specific resources for
monitoring Sun servers in enterprise or workgroup data centers.
All the Sun servers supported by these integration packs fall into four categories
differentiated by architecture (x64 or SPARC) and by service processor type
(ALOM, ILOM, or Embedded LOM). The integration pack that you are installing or
the configuration that you are implementing may not support all categories of
servers, so consult the following website to verify that a particular server in one of
these categories is supported by the Sun-HPSIM configuration described in this
whitepaper:
Category Supported Description Examples
x64 Servers Yes x64 servers and blade server modules with the Sun Fire X4100 M2
with ILOM Integrated Lights Out Manager (ILOM) service Sun Fire X4600 M2
processor Sun Blade X6220
Server Module
Hereafter referenced as x64/ILOM servers. Sun Blade X8440
These servers are monitored at the service Server Module
processor level.
SPARC Yes SPARC Solaris servers and blade server Sun SPARC
Servers with modules with the Integrated Lights Out Enterprise T5120
ILOM Manager (ILOM) service processor Sun SPARC
Enterprise T5220
Monitoring Sun Servers in an HP SIM Environment 1

Category Supported Description Examples
Hereafter referenced as SPARC/ILOM servers. Sun Blade T6320
Server Module
For most integrations or configurations,
SPARC/ILOM servers can be monitored at
either the service processor level or at the
operating system level via the Sun SNMP
Management Agent for Sun Fire and Netra
Systems. The Sun-HPSIM configuration
described in this whitepaper does not support
this Sun SNMP Management Agent for Sun
Fire and Netra Systems.
x64 Servers Yes x64 servers and blade server modules with the Sun Fire X2100 M2
with Embedded Embedded Lights Out Manager (Embedded Sun Fire X2200 M2
LOM LOM) service processor
Hereafter referenced as x64/EmbeddedLOM
servers.
These servers are monitored at the service
processor level.
SPARC No SPARC Solaris servers with the Advanced Sun SPARC

Servers with Lights Out Manager (ALOM) service processor Enterprise T1000
ALOM Sun SPARC
Hereafter referenced as SPARC/ALOM Enterprise T2000
servers. Sun Blade T6300
These servers are monitored at the operating Server Module
system level via the Sun™ SNMP
Management Agent for Sun Fire™ and Netra™
Systems.
The matrix of servers and service processors supported by Sun integration packs is
expanding dynamically. A complete, current list of supported Sun servers, service
processors, and service processor firmware is available at the following web site:
Please consult this web site before performing installation and/or configuration of the
Sun-HPSIM configuration described in this whitepaper.
▬▬▬▬▬
HP SIM and Sun MIBs
Before you proceed with this configuration, it is important to understand how HP
SIM works with Sun system management MIBs.
Working with Sun MIBs

The Sun offers two SNMP management mibs:
▪ SUN-ILOM-PET-MIB.mib
▪ SUN-HW-TRAP-MIB.mib

ILOM 1.1 and EmbeddedLOM service processors support the
SUN-ILOM-PET-MIB.mib. With ILOM 2.0 service processors, you can choose to
configure ILOM to send PETs from the SUN-ILOM-PET-MIB.mib, traps from the
SUN-HW-TRAP-MIB.mib, or from both simultaneously. Each has its advantages and
disadvantages.
▪ SUN-ILOM-PET-MIB.mib: The events from this mib do not show the name of
the component or sensor that is generating the event.
▪ SUN-HW-TRAP-MIB.mib: The events from this mib display the exact name of
the sensor in the alert, but are all categorized as informational (although
severity state of the component appears in one of the varbind for threshold
events).
The same event generated by the SUN-HW-TRAP-MIB.mib provides

significantly more detail.

The following screen shot illustrates what ILOM 2.0 events look like in the Event
browser when both ILOM is configured to send both SUN-ILOM-PET-MIB.mib and
SUN-HW-TRAP-MIB.mib events.
Obtaining Sun MIBs

Before you can compile Sun mibs in HP SIM, you must download them from the
following web site:

▬▬▬▬▬
Levels of Integration with HP SIM
Each Sun server presents itself to a management application such as HP SIM as two
devices with similar services that are monitored separately. The operating system
installed on the server offers services (SNMP and WBEM) that can be integrated
with HP SIM at one level while the embedded service processor on the Sun server
presents itself as a separate device.
Installed Operating Systems: Operating System

- Windows - Linux - Solaris Level Integration
Systems Insight
Manager
Embedded Service Processor: Service Processor
- Integrated Lights Out Manager Level Integration
- Embedded Lights Out Manager
You can configure HP SIM and your Sun servers to integrate at either the operating
system level, at the service processor level, or at both levels. The tasks that you must
perform to achieve integration depend on which level or levels of integration you
want.
Level of Integration Integration Tasks to Perform …
Operating System Discover and classify the monitored servers.
Display system properties extracted through SNMP

and WBEM (when supported by the host OS).
Configure a server to send OS-level SNMP traps.
X64 Service Processor Discover and classify the service processor.
Display system properties extracted through SNMP.
Configure a service processor to send Platform Event

Traps (PETs) or traps defined in SUN-HW-TRAP-MIB
to HP SIM.
Compile SUN-ILOM-PET-MIB.mib and/or SUN-HW-

TRAP-MIB.mib on the HPSIM server to be able to
decode PETs and SNMP hardware traps.
Each level of integration operates independently.

Once you have configured HP SIM and your Sun devices (servers or service
processors), HP SIM can extract information from those devices. The following
screen shot illustrates the system information that HP SIM has extracted from a Sun
Fire X4200 server.

▬▬▬▬▬
This Manual
This manual contains the following chapters:
Chapter 1 “Introduction”
Chapter 2 “Configuring Sun Devices to be Monitored by HP SIM”
Chapter 3 “Configuring HP SIM to Discover and Monitor Sun Devices”
Chapter 4 “Discovering Sun Devices”
Chapter 5 “Verifying Overall Configuration”
Chapter 6 “Monitoring Sun Devices in HP SIM”

This manual is intended for experienced HP SIM administrators, field sales
representatives, and support engineers.
▬▬▬▬▬
Requirements
The monitored devices and the HP SIM server software have different software
requirements.
Monitored Devices
Monitored devices (servers and service processors) must have the following software
installed and configured properly.

Device Software Requirement
Sun Servers Consult the system documentation for your Sun

server for information about operating system
support.
SNMP service installed and running
WBEM service installed and running (wherever

supported by the operating system)
Sun Service Processors Sun Integrated Lights Out Manager (ILOM) firmware
Sun Embedded Lights Out Manager (ELOM)

firmware
HP SIM Management Server

Integration between HP SIM and Sun servers has been tested with version 5.0 of the
HP SIM software. Earlier versions of the HP SIM software will probably work as
well.

CHAPTER 2
Configuring Sun Devices to be

Monitored by HP SIM
This chapter describes how to configure your Sun devices (servers and service
processors) to be discovered and monitored by HP SIM.
HP SIM uses SNMP to discover and communicate with monitored nodes and uses
other protocols such as WBEM (where supported by a host operating system) to
extract and to display asset information for Sun servers. To be discovered and
monitored properly, the following tasks must be performed on the server and service
processor:
■ Configure SNMP on all Sun servers.
■ Configure WBEM settings on each Sun Fire x64 server.
■ Configure SNMP settings on each Sun service processor.
▬▬▬▬▬
Configuring Sun Servers to be Monitored
by HP SIM (Operating System Integration)
For HP SIM to use SNMP and WBEM (x64 Windows servers only) to discover and
monitor Sun servers, those services need to be enabled and configured on your Sun
servers.
Note: Before you can configure SNMP and WBEM services, they must be
installed on your HP SIM server. For more information about installing and
configuring SNMP, SNMP v1 and v2 agents, and Windows Management
Instrumentation (WMI), refer to the technical documentation at
http://www.microsoft.com.
The following example is applicable only to Sun Fire x64 servers hosting the
Windows Server 2003 operating system. Refer to your Linux or Solaris operating
system documentation for equivalent instructions.
Configuring SNMP on Sun Fire x64 Servers Running Windows

To configure SNMP on your Sun Fire x64 servers running Windows Server 2003 on
a monitored node, do the following:
1. Choose Start – Settings - Control Panel - Administrative Tools – Services-
SNMP Service.
Windows displays the SNMP Service Properties dialog box.
2. Click the Traps tab.

3. Click the Add button.
4. Enter the host name or IP address of the HP SIM server.
Note: In the following screen shot, the trap destination is configured to
129.148.97.169.
5. Click the Add button to submit the changes.
6. Click the Security tab.

7. Update the following fields in the SNMP Services Properties dialog box.
• Add the appropriate community string to the list displayed.
Note: Select READ ONLY unless otherwise required. The read-only
(RO) setting permits HP SIM only to read SNMP mib values and
prevents it from modifying any mib values. The configured string
should match at least one of the strings that is configured on the
HP SIM server.
• Click Add to submit the entered community string.
• Check the Accept SNMP packets from any host box.
Note: If entering this setting poses a security issue at your site, check
the Accept SNMP packets from these hosts box and enter the host
name or IP address of the HP SIM server.

▬▬▬▬▬
Configuring ILOM and Embedded LOM
Service Processors to be Monitored by HP
SIM
For a SPARC/ILOM, x64/ILOM, or x64/EmbeddedLOM service processor to be
monitored by HP SIM, you must configure SNMP on it.
A complete, current list of supported Sun servers, service processors, and service
processor firmware is available at the following web site:
Please consult this web site before deploying the Sun-HPSIM configuration
described in this whitepaper.
Sun Server Configuration Tasks
SPARC/ILOM and x64/ILOM Configure SNMP on your ILOM service

processor
x64/EmbeddedLOM Configure SNMP on your Embedded LOM

service processor running firmware Version 2.91
Configure SNMP on your Embedded LOM

service processor running firmware Version 4.x

Configuring Sun ILOM 1.1 Service Processors to be Monitored by HP
SIM
To configure SNMP protocol settings on your Sun ILOM 1.1 service processor, do
the following:
1. Launch the web GUI (ILOM) on the service processor to be configured and
managed.
2. Log in to the ILOM graphical interface as root.
3. Click Configuration – System Management Access – SNMP to display the
SNMP configuration screen.
4. Verify the following settings.
Setting Value(s)
Port 161 (default)
Set Requests Optional.
v1 Protocol
Checked.

Setting Value(s)
v2c Protocol Optional.

v3 Protocol
5. Click the Add button under the SNMP Communities section of the page to
open a dialog box for entering SNMP community strings.
6. Enter the appropriate community string.

Note: At least one of the community strings with at least read-only (ro)
permissions should match one of the configured community strings in
the HP SIM server.
7. Click the Save button to submit the changes.

8. Click the Configuration – Alert Management tab.

9. Click one of the entries marked containing the value 0.0.0.0 under the
Destination IP Address column.
10. Choose Edit from the Actions drop-down box.
11. Verify the following configuration settings.

Field Value
IP Address: The IP address of the server on which HP SIM is installed
Level: Informational
12. Click the Save button to submit the change.

Tip: Verify that the information that you just entered in the dialog box
appears in the updated Alert Management table.
Your Sun ILOM 1.1 service processor is now configured to send IPMI PETs to all
trap destinations.
Configuring Sun ILOM 2.0 Service Processors to be Monitored by HP

SIM
To configure SNMP protocol settings on your Sun ILOM 2.0 service processor, do
the following:
1. Launch the web GUI (ILOM) on the service processor to be configured and
monitored.
2. Log in to the ILOM graphical interface as root.
3. Click Configuration – System Management Access – SNMP to display the
SNMP configuration screen.

4. Verify the following settings.
Setting Value(s)
Port 161 (default)
Set Requests Optional.
v1 Protocol
Checked.
v2c Protocol Optional.

v3 Protocol
5. Click the Save button to submit the changes.

6. Click the Configuration - Alert Management tab to display the Alert
Settings screen.

7. Click one of checkboxes for an entry that has no value for the Destination
Summary field.
8. Click the Actions drop-down box and choose Edit.
ILOM 2.0 displays the following screen.

9. Set (or verify) the following configuration settings.
Field Value
Level: Minor (to view the maximum number of traps at all

severity levels)
Type: SNMP Trap (for the SUN-HW-TRAP-MIB)

Note: Although ILOM 2.0 continues to support the
SUN-ILOM-PET-MIB MIB, Sun strongly recommends
configuring your service processors to use the more
robust SUN-HW-TRAP-MIB MIB.
Note: See “Working with Sun MIBs” in Chapter 1 for
more information about Sun service processor MIBs and
HP SIM.
IP Address: IP_address_of_destination_server
SNMP Version: v1, v2c, or v3 (if supported) for your management

configuration
Note: Check v1 for the Sun-HPSIM configuration.
Community Name: public
Note: At least one of the community strings with at least

read-only (ro) permissions must match one of the

Field Value
community strings configured in the Element Manager.
10. Click the Save button to submit the change.

Tip: Verify that the information that you just entered in the dialog box
appears in the updated Alert Management table.
Your Sun ILOM 2.0 service processor is now configured to send
SUN-HW-TRAP-MIB SNMP traps or IPMI PETs to all trap destinations.
Configuring Sun Embedded LOM Version 2.91 Service Processors to be

Monitored by HP SIM
To configure SNMP protocol settings on an Embedded LOM service processor, do
the following:
1. Launch the Embedded LOM service processor web GUI (Server
Management) on the service processor to be configured and managed.
2. Log in to the Server Management application as root.

3. Click Control – Platform Event Filter in the menu pane.
The Embedded LOM GUI displays the Platform Event Filter form.

4. Verify or set the following settings:
Setting name Setting value
PEF Global Control Enable PEF is checked.
IP Address IP_address of the HP SIM management server, for

example 129.148.97.209
MAC Address Mac_address of the HP SIM management server, for

example 00-13-72-5A-A4-0E
5. Scroll down to the next section of the form.

6. Set the options appropriate for your environment.
Note: The checkbox labeled Enable Send Alert Action must be checked.
7. Click the Submit button to apply the settings.

8. Click SNMP - SNMP Settings in the menu pane.
9. Verify or enter the following settings:

Port 161 (the default)
v1 Protocol Checked
v2 Protocol Optional

Your Embedded LOM service processor is now configured to send IPMI PETs to all
trap destinations listed.
Configuring Sun Embedded LOM Version 4.x Service Processors to be

Monitored by HP SIM
To configure SNMP protocol settings on an Embedded LOM Version 4.x service
processor, do the following:
1. Launch the Embedded LOM service processor web GUI (Server
Management) on the service processor to be configured and managed.
2. Log in to the Server Management application as root.

3. Click Configuration - Platform Event Filter in the tabbed interface.
The Embedded LOM GUI displays the Platform Event Filter form.
4. Verify or set the following settings:
PEF Global Control Enable PEF is checked.

IP Address IP_address of the server hosting HP SIM, for

example 129.148.97.117
MAC Address Mac_address of the server hosting HP SIM, for

example 00-03-BA-F1-36-D8
5. Scroll down to the next section of the form.

6. Set the options appropriate for your environment.
Note: The checkbox labeled Enable Send Alert Action must be checked.
8. Click Configuration - SNMP - SNMP Settings in the tabbed interface.
9. Verify or enter the following settings:
Port 161 (the default)

v1 Protocol Checked
v2c Protocol Optional
Your Embedded LOM Version 4.x service processor is now configured to send
IPMI PETs to all trap destinations listed.

CHAPTER 3
Configuring HP SIM to Discover

and Monitor Sun Devices
This chapter describes how to configure HP SIM to discover and monitor Sun
devices (servers and service processors) at both the operating system and service
processor levels of integration.
During the discovery process, HP SIM uses primarily SNMP and WBEM protocols
to extract system information from monitored devices and to classify those devices
(servers or service processors) under the appropriate category. HP SIM uses the
SNMP protocol to discover and identity Sun servers and the WBEM protocol to
retrieve asset inventory details. To configure HP SIM for SNMP, you must provide
proper SNMP community strings.
▬▬▬▬▬
Configuring HP SIM to Discover and
Monitor Sun Servers
For HP SIM to use SNMP and WBEM to discover and monitor Sun servers, you
need to configure SNMP and WBEM protocol settings in HP SIM.
To configure SNMP and WBEM protocol settings on your HP SIM server, do the
following:
1. Launch HP SIM.
2. Log in to HP SIM as Administrator.
3. Modify protocol settings at the global or system level.
• To modify product settings at the global level (settings to be applied to all
monitored servers), choose Options – Protocol Settings – Global Protocol
Settings.
• To modify product settings at the individual system level (settings to be
applied to one monitored server), choose Options – Protocol Settings –
System Protocol Settings.
4. Modify SNMP protocol settings in the SNMP settings section of the page.
• Check the Enable SNMP box.
• Add appropriate SNMP community strings to the displayed list of
community strings.
Note: At least one of the community strings must match one of the
community strings on the monitored server or service processor.

5. Modify WBEM protocol settings in the Default WBEM settings section of
the page.
• Check the Enable WBEM box.
• Enter the username and password of the Sun server that you want HP SIM
to discover and monitor.
Note: These settings are applicable only to devices that support WBEM.

▬▬▬▬▬
Configuring HP SIM to Discover and
Monitor Sun Service Processors (Service
Processor Integration)
For HP SIM to discover, classify, and receive alerts from a Sun x64/ILOM,
SPARC/ILOM, or x64/ELOM service processor, you need to perform the following
tasks:
Devices to be Integrated Task
All Sun Servers Configure proper SNMP strings on HP SIM.
Note: Perform this step here only if you have not

done so in the previous section.
Sun x64/ILOM 1.1 Service Compile and register the

Processors SUN-ILOM-PET-MIB.mib file to decode and
display platform event traps (hereafter PETs).
Define an HP SIM Product Model “SUN ILOM”
for your Integrated Lights Out Manager (ILOM)
service processor.
Sun x64/ILOM 2.0 and Compile and register SUN-ILOM-PET-MIB.mib

SPARC/ILOM Service the and/or SUN-HW-TRAP-MIB.mib file to decode
Processors and display traps.
Define an HP SIM Product Model “SUN ILOM”
for your Integrated Lights Out Manager (ILOM)
service processor.
Sun x64/EmbeddedLOM Compile and register the

SUN-ILOM-PET-MIB.mib file to decode and

Devices to be Integrated Task
Service Processors display platform event traps.
Define an HP SIM Product Model “SUN ELOM
2.91” for your Embedded LOM service
processor.
The following sections document each of these tasks.
Configuring Proper SNMP Strings

If you have not done so, complete Step 4 in “Configuring HP SIM to Discover and
Monitor Sun Servers.”
Compiling and Registering Sun MIBs

The service processor in your Sun x64/ILOM, SPARC/ILOM, or
x64/EmbeddedLOM server supports both the SNMP protocol and the IPMI protocol.
For the traps sent by the service processor to be properly decoded by HP SIM, you
must compile and register on HP SIM either the corresponding SUN-ILOM-PET-
MIB.mib and/or the SUN-HW-TRAP-MIB.mib.
Service Processor Trap Type Sun MIB to be Compiled
x64/ILOM 1.1 IPMI Platform Event SUN-ILOM-PET-MIB.mib

Traps (PETs)
x64/ILOM 2.0 IPMI Platform Event SUN-ILOM-PET-MIB.mib or

Traps (PETs) or SUN-HW-TRAP-MIB.mib
Hardware Traps
SPARC/ILOM IPMI Platform Event SUN-ILOM-PET-MIB.mib or

Traps (PETs) or SUN-HW-TRAP-MIB.mib
Hardware Traps
x64/EmbeddedLOM IPMI Platform Event SUN-ILOM-PET-MIB.mib

Traps (PETs)
All PET traps are sent as SNMP v1 traps with the following format.
Enterprise OID = iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).

wired_for_management(3183).PET(1).version(1)
Agent-addr Network Address
Generic-trap EnterpriseSpecific (6)
Specific-trap The field is of type “INTEGER”. This is a decimal version of a

hex string that contains information like Event Sensor Type,
Event Type, and Event Offset.
Time-stamp Time elapsed between last (re) initialization of the network

entity and the generation of the trap

Variable-bindings A single octet-string, varying between 47 to 110 octets which
(varbind) holds bulk of information regarding sensor, severity, etc.
For specific procedures about integrating new mibs into HP SIM, see the HP SIM
administration documentation.
To compile and register the appropriate Sun mib(s) for HP SIM, do the following:
1. Copy the SUN-ILOM-PET-MIB.mib and/or SUN-HW-TRAP-MIB.mib file into
the following directory:
\Program Files\HP\Systems Insight Manager\mibs
2. Launch a command window.

3. Change the working directory to the following:
4. Execute, as appropriate, the following command(s) in the Command

Window.
mcompile SUN-ILOM-PET-MIB.mib
mcompile SUN-HW-TRAP-MIB.mib
If the mib successfully compiles, it should return the message “Mib Compilation
completed successfully”. Successful compilation of the mib should also create a
files called SUN-ILOM-PET-MIB.cfg or SUN-HW-TRAP-MIB.cfg file in the
following directory:
5. Execute, as appropriate, the following command(s):

mxmib -a SUN-ILOM-PET-MIB.cfg
mxmib -a SUN-HW-TRAP-MIB.cfg
This command should register the mib and return the message “COMMAND
COMPLETED SUCCESSFULLY”. The following screen shot illustrates the
execution of Step 4 and Step 5.
The following screen shot depicts a compilation of the
SUN-ILOM-PET-MIB.mib.

The following screen shot depicts a compilation of the
SUN-HW-TRAP-MIB.mib.
The SUN mibs are now compiled and registered for HP SIM to decode IPMI PETs
and/or hardware traps.
Defining a SUN ILOM Product Model for ILOM

To create a SUN ILOM product model in HP SIM, do the following:
1. Launch HP SIM.
2. Log in as HP SIM Administrator.

3. Select Options - Manage System Types.
HP SIM displays the Manage System Types page.
4. Click the New button.

HP SIM expands the Manage System Types page to display a New rule section.

You can enter values here manually or you can use values retrieved from the
device. Since object identifiers (OIDs) are long strings of numbers, there is a
chance of typographical errors. To avoid this, consider retrieving values from
the device. This also serves to confirm the working of SNMP communication
between HP SIM and the device.
5. Click the Retrieve from system button next to System object identifier field.
HP SIM expands the Manage System Types page to display a new Retrieve
from system section.
Note: The Target hostname or IP address described here refers to the
hostname or IP address of the server’s service processor, not the
hostname or IP address of the server host operating system.

6. Update the Community string and Target hostname or IP address fields.
• Enter the appropriate default community string for the target service
processor whose IP address you specify in the next field. The default
Community string used in HP SIM is public.
• Enter the IP address or hostname of a target service processor that can
communicate with HP SIM.
7. Click the Get response button.

HP SIM queries the target device to determine its SNMP data type and response
value.

Depending on which type of Sun server or blade module you are querying here,
you will see OBJECTIDENTIFIER return a value starting with
1.3.6.1.4.1.42.2.200.
8. Click the OK button to accept these retrieved values.
HP SIM collapses the Manage System Types page and displays a retrieved value
in the System object identifier field.
9. Evaluate the value in the System object identifier field.
System object identifier value Action
1.3.6.1.4.1.42.2.200 Accept the value
1.3.6.1.4.1.42.2.200.1.2 Trim the value to 1.3.6.1.4.1.42.2.200

(or other values with digits
trailing .200)
10. In the Compare rule drop-down box, select the value starts with.
11. Click OK to accept these retrieved values.

HP SIM enters these values in fields of the New rule section of the Manage
System Types page.
12. Specify or verify the following values in this section.
• Select Management Processor in the System type drop-down box.

• Select None in the Subtype drop-down box.
• Enter SUN ILOM in the Product Model text box.
• Leave the Custom management page field empty.
13. Click the OK button to complete the procedure.

HP SIM collapses the Manage System Types page and displays the name of the
new product model in the list of product models.
To test whether the new Product Model definition works properly, identify the IP
address of an ILOM service processor that has not been discovered by HP SIM and
perform a manual discovery of that device. If the new Product Model definition is
configured properly, that newly discovered device should appear in the list of
discovered systems under the category SUN ILOM.

Defining a SUN ELOM Product Model
x64/EmbeddedLOM service processors use different System Object Identifiers, so
you must define separate product models in HP SIM, one for version 2.91 and one
for the new versions. In the following procedure, we’ll differentiate these types of
x64/embeddedLOM servers as Sun ELOM 2.91 and Sun ELOM Other.
To determine the version of the ELOM firmware installed on the service processor of
a monitored node, log in to the ELOM command-line interface and note the version
number that is displayed by ELOM.
The product models need to be defined according to the following rules.
ELOM Model ELOM Version Category Evaluation …
2.91 2.91 System Object Identifier Matches 1.3.6.1.4.1.42.

(X2100-M2
/X2200-M2)
System Description Matches ServiceProcessor.
(SysDescr)
Other All others System Object Identifier Starts with 1.3.6.1.4.1.42.2.208
To create this Sun-specific product model in HP SIM, do the following:

1. Launch HP SIM.
2. Log in as HP SIM Administrator.
3. Select Options - Manage System Types.
HP SIM displays the Manage System Types page.

4. Click the New button.
HP SIM expands the Manage System Types page to display a New rule section.

You can enter values here manually or you can use values retrieved from the
device. Since object identifiers (OIDs) are long strings of numbers, there is a
chance of typographical errors. To avoid this, consider retrieving values from
the device. This also serves to confirm the working of SNMP communication
between HP SIM and the device.
5. Click the Retrieve from system button next to System object identifier field.
HP SIM expands the Manage System Types page to display a new Retrieve
from system section.
6. Update the Community string and Target hostname or IP address fields.

• Enter the appropriate default community string for the target service
processor whose IP address you specify in the next field. The default
Community string used in HP SIM is public.
• Enter the IP address or hostname of a target service processor that can
communicate with HP SIM. In the following example, the IP address is
129.148.97.216.
7. Click the Get response button.

value.
ELOM 2.91 and ELOM Other service processors return different System Object
Identifier values.
ELOM Model ELOM Version System Object Identifier
2.91 2.91 1.3.6.1.4.1.42
Other All others 1.3.6.1.4.1.42.2.208
In the screen shot above, the System Object Identifier value starting with
1.3.6.1.4.1.42.2.208, identifying it as an ELOM Other type server with firmware
that is not Version 2.91.
Note: All ELOM Other service processors return System Object Identifiers
with digits after 208.
8. Click the OK button to accept these retrieved values.
HP SIM collapses the Manage System Types page and displays the retrieved
value starting with 1.3.6.1.4.1.42.2.208 in the System object identifier field at
the top of the page.
Note: When defining a System Object Identifier, trim the value in the System
object identifier box to 1.3.6.1.4.1.42.2.208 if it returns addition
numbers at the end.
9. In the Compare rule drop-down box, set the appropriate rule (match or
starts with) for your ELOM 2.91 or ELOM Other service processor.

ELOM Model ELOM Version Compare rule
2.91 2.91 match 1.3.6.1.4.1.42
Other All others starts with 1.3.6.1.4.1.42.2.208
Note: Steps 10 – 14 are not required for defining a product model for an
ELOM Other service processor. Skip to Step 15 if you are defining a
product model for an ELOM Other service processor.
10. [ELOM 2.91] Click the Retrieve from MIB button.
HP SIM expands the Manage System Types page to display a section titled
Retrieve from MIB.
11. [ELOM 2.91 only] Specify the following values in the MIB definition file
name and MIB variable name fields.
Field name Value
MIB definition file name rfc1213.mib
MIB variable name fields sysDescr
12. [ELOM 2.91 only] Click OK to accept these changes.

HP SIM collapses the Manage System Types page and displays the results of the
MIB inquiry.

13. [ELOM 2.91 only] Click the Retrieve from system button.
HP SIM expands the page to display the Retrieve from system section.
14. [ELOM 2.91 only] Click the Get response button.
value.

15. [ELOM 2.91 only] Click OK to accept these retrieved values.
HP SIM enters these values in fields of the New rule section of the Manage
System Types page.
16. [ELOM 2.91 only] In the Compare rule drop-down box, set the value to
match.
17. Specify or verify the following values in this section.
Field name Value
System type Management Processor
Subtype None
Product SUN ELOM 2.91

model
or …
SUN ELOM Other
Custom [Blank]
management
page
18. Click the OK button to complete the procedure.

HP SIM collapses the Manage System Types page and displays the name of the
new product model in the list of product models.

The following screen shots depict completed product definitions for SUN ELOM
2.91 and SUN ELOM Other.

CHAPTER 4
Discovering Sun Devices
Once you properly configure the HP SIM server and the monitored Sun devices
(servers or service processors), HP SIM is able to discover your Sun servers and
service processors.
There are two general methods for HP SIM to discover your Sun servers or service
processors: automatic discovery or manual discovery.
▬▬▬▬▬
Discovering Sun Devices Automatically
By default, HP SIM server software is not configured to discover devices
automatically. Consult the HP Systems Insight Manager Technical Reference Guide
for detailed information about configuring HP SIM to perform automatic discovery
in one of the following ways:
■ HP SIM can be configured to poll a list of IP addresses (or a range of IP
addresses) at some predetermined regular intervals and to discover the devices
that respond.
■ HP SIM can be configured to discover a new server or service processor when
HP SIM receives a trap from an undiscovered server or service processor.
▬▬▬▬▬
Discovering Sun Devices Manually
You can also discover a Sun server or service processor manually. To discover a
device manually, do the following:
1. Launch HP SIM and log in as Administrator.
2. Select Options - Discovery.
HP SIM displays the Discovery page.

3. Click the Manual tab to display the System Information page.

4. Select the IP address radio button and enter the IP address of your Sun
server.
5. Click the Add System button to add the system to the database or click
More Settings to enter additional information.
HP SIM pings the IP address or hostname to discover the device.
If discovery is successful, HP SIM displays the newly discovered device (server
or service processor) in its various lists of monitored devices.

CHAPTER 5
Verifying Overall Configuration
Once you properly configured both the HP SIM server and the monitored Sun
devices, you can verify that the overall configuration is working properly.
Note: Currently the Sun-HPSIM configuration described in this whitepaper does
not support OS-level monitoring of SPARC/ILOM or SPARC/ALOM
servers.
▬▬▬▬▬
Verifying Successful Configuration for HP
SIM
To the extent that the Sun-HPSIM configuration described in this whitepaper
employs a variety of system management technologies to monitor different types of
Sun servers, there is no one procedure that exercises every interface on each
monitored system in order to verify that the entire integration has been installed and
configured properly. If you are physically located with your monitored systems, you
could always manually remove and re-insert a non-critical component on one Sun
server after another. See the section “Verifying Configuration Manually” below for
more information on manual verification. This manual procedure becomes
impractical at large installations and impossible at remote locations. Performing
remote verification is more convenient, but requires different procedures for OS-
level or SP-level integrations and for different types of Sun servers (x64 or SPARC).
To determine which remote procedures are appropriate for your test plan and for the
types of Sun servers supported by your management application, consult the
following table.
CPU Type SP Type OS-level Procedure(s) SP-level Procedure(s)
x64 ILOM Not supported See “Verifying Configuration

Remotely Using IPMItool”
Embedded LOM Not supported See “Verifying Configuration

Remotely Using IPMItool”
SPARC ILOM See “Verifying Configuration See “Verifying Configuration

Remotely Using psradm” Remotely Using IPMItool”
Note: Currently the Sun-HPSIM

configuration discussed in this
publication does not support OS-
level monitoring of SPARC/ILOM

CPU Type SP Type OS-level Procedure(s) SP-level Procedure(s)
or SPARC/ALOM servers.
ALOM See “Verifying Configuration Not supported

Remotely Using ALOM”
Note: Currently the Sun-HPSIM
configuration discussed in this
publication does not support OS-
level monitoring of SPARC/ILOM
or SPARC/ALOM servers.
The following sections describe how to perform each of these procedures.
Verifying Configuration Manually

If you are located physically near one or more of your Sun servers, you can always
verify configuration by generating a physical event. The most reliable way to
accomplish this is to remove and re-insert a non-critical component.
To test your configuration manually, do the following:
1. Locate the Sun server or blade module in your data center.
2. Identify a component on that system that is non-critical and hot-pluggable
(for example, a redundant power supply or fan tray).
Note: Be certain that removal and re-insertion of this component will not
affect the normal and routine operation of the server. Verify that the
redundant component is, in fact, not critical to the current state of the
system.
3. Remove that non-critical component.
Note: Be certain to follow all required software and firmware procedures
required for the safe removal of any hot-pluggable component. Consult
the Sun manual or online information system that ships with your Sun
server for specific procedures related to removing that hot-pluggable
component.
4. After an appropriate amount of time, re-insert the non-critical component.
5. In the message or event console of your management package, verify that
removing/re-inserting the non-critical component has generated one or
more traps with the appropriate event summary and severity.
If you do not see these traps in the console, review this manual for required
configuration steps or consult the troubleshooting section of this manual.
Verifying Configuration Remotely Using ALOM

To verify that a remote ALOM-based SPARC Solaris system is configured correctly,
do the following:
1. Identify the name and/or IP address of the ALOM-based SPARC Solaris
server that you want to test.
2. Log in to the ALOM CMT command shell on that remote system via an
Ethernet or serial connection.

3. Enter the following command to determine the current state of the system
locator LED.
sc> showlocator
ALOM returns one of the following messages:

• Locator led is ON
• Locator led is OFF
The following example assumes that the locator LED is currently OFF.
4. Enter the following command to turn the locator LED on.
sc> setlocator on
5. In the message or event console of your management package, verify that it

has received an event from ALOM indicating that the locator LED is on.
6. Enter the following command to restore the locator LED to off.
sc> setlocator off
7. (Optional) In the message or event console of your management package,

verify that it has received an event from ALOM indicating that the locator
LED is off.
If you do not see these messages in the console, review this manual for required
Verifying Configuration Remotely Using IPMItool

Recent Sun servers support either an Integrated Lights Out Manager (ILOM) service
processor or an Embedded LOM service processor. You can communicate with these
ILOM and Embedded LOM service processors via their IPMI interfaces to have
them generate non-critical, simulated events. If HP SIM receives these non-critical,
simulated events from ILOM or from Embedded LOM, it is configured properly for
actual events.
IPMItool is an open-source utility for managing and configuring devices that support
the Intelligent Platform Management Interface (IPMI) version 1.5 and version 2.0
specifications. Versions of IPMItool are available for the Solaris, Linux, and
Windows operating systems.
Operating System IPMItool Distribution(s)
Solaris http://ipmitool.sourceforge.net/
Many software resource CDs distributed with Sun servers.
Linux http://ipmitool.sourceforge.net/
Windows http://www.sun.com/systemmanagement/tools.jsp
To verify that your management program is configured to receive traps from a

supported service processor, do the following:

1. Collect the following information about the remote service processor that
you want to test.
Field Description
<SPname> The name or IP address of the service processor

Example: 192.168.1.1
<SPadminname> The administrator login name for the service

processor
Example: root
<SPadminpassword> The administrator password for the service

processor
Example: changeme
2. Open a command shell on the system that has IPMItool installed.

3. Enter the following IPMItool command to generate a list of all available
sensors on that remote Sun server.
# ipmitool -U <SPadminname> -P <SPadminpassword> \
-H <SPname> -v sdr list
For example, to get the list of available sensors on a Sun SPARC Enterprise
T5120 server at IP address 192.168.1.1 with ILOM SP login/password
root/changeme, you would enter the following command:
# ipmitool -U root -P changeme -H 192.168.1.1 –v sdr list
4. In the output from IPMItool, identify the Sensor ID name of a sensor that
has at least one entry in the Assertions Enabled or Deassertions Enabled
fields.
In the following example, IPMItool returns the following information about the
sensor named /MB/T_AMB.
Sensor ID : /MB/T_AMB (0x9)
Entity ID : 7.0 (System Board)
Sensor Type (Analog) : Temperature
. . .
Upper critical : 55.000
. . .
Assertions Enabled : lnc- lcr- lnr- unc+ ucr+ unr+
Deassertions Enabled : lnc- lcr- lnr- unc+ ucr+ unr+
This sensor monitors ambient temperature on the motherboard of servers.

Note: Exercise caution in choosing a sensor to use for a simulated event.
Simulating unrecoverably high or low temperature for some sensors
may cause the server to shut down.
5. Enter the following IPMI command to generate a simulated event
-H <SPname> event <sensorname> <option>
For example, to generate a simulated event for exceeding the upper critical
(ucr) ambient temperature on a Sun SPARC Enterprise T5120 server at IP

address 192.168.1.1 with ILOM SP login/password root/changeme, you
would enter the following command:
# ipmitool -U root -P changeme -H 192.168.1.1 \
event /MB/T_AMB ucr assert
In the command shell, IPMItool returns information like the following:

Finding sensor /MB/T_AMB … ok
0 | Pre-Init Time-stamp | Temperature /MB/T_AMB | \
Upper Critical going high | Reading 56 > Threshold \
55 degrees C
6. In the message or event console of your management package, verify that it

has received an event from ILOM or from Embedded LOM relevant to the
sensor that you specified in your IPMItool command.
7. (Recommended) Clear the simulated event with the following syntax:
-H <SPname> event <sensorname> <option>
To clear (deassert) the simulated event in the previous example, enter the
following command:
# ipmitool -U root -P changeme -H 192.168.1.1 \
event /MB/T_AMB ucr deassert
Verifying Configuration Remotely Using psradm

The Solaris utility psradm(1M) performs configuration on multiprocessor CPUs.
When you use psradm to disable or to re-enable a CPU core, it generates a trap that
should appear in the HP SIM event console. This procedure is appropriate if you are
verifying configuration for a Sun SPARC Enterprise server supporting the ILOM
service processor such as the SPARC Enterprise T5120 or T5220 server.
To use psradm to generate a trap for one of these supported systems, do the
following:
1. Identify the name and/or IP address of the server that you want to test.
2. Log in to that server as root or with administrator privileges.
3. Enter the following command to disable a specific CPU core on that remote
server.
# psradm -f <CPU_Core_ID>
where <CPU_Core_ID> is the ID for one CPUcore. For example, to disable core
0 on a Sun SPARC Enterprise T5120, you would enter the following command:
# psradm -f 0
The trap generated by the T5120 should appear in the HP SIM event console in
a format like the following:
CH/MB/CMP0/P0/CPU Device has been removed
4. (Recommended) Enter the following command to re-enable that same CPU

core on that remote server.

# psradm -n <CPU_Core_ID>

CHAPTER 5
Monitoring Sun Devices in HP SIM
Once you have configured the HP SIM server and the Sun devices (servers or service
processors) to be monitored, HP SIM can discover your Sun devices and extract
information about those devices using standard protocols such as SNMP or WBEM.
HP SIM provides consistent views of information derived from two types of
monitored devices:
Sun servers integrated with HP SIM at the operating system level
Sun servers integrated with HP SIM at the service processor level

Each of these views is discussed in subsequent sections of this chapter.
▬▬▬▬▬
HP SIM Views on Sun Servers (Operating
System Level Integration)
For every device that HP SIM discovers, it presents information about that system in
a System Page. Each System Page has three tabs that allow you to view additional
information about Identity, Tools & Links, and Alerts (Events).
To display the System Page for any monitored device, click the device in the left-
hand pane of the HP SIM administrative console.

Server Identity Information
HP SIM displays information about the identity of the discovered device on the
Identity page. Here is sample data in the Identity page for a discovered Sun Blade
X8420 server module.
Tools & Links to Device Resources

In the Tools & Links page, HP SIM displays URL links to various web-launchable
applications/tools on the monitored device. During discovery, HP SIM scans some
predefined ports to check any HTTP/HTTPS servers listening on those particular
ports. If the check is positive, it provides a link on Tools & Links page to launch that
particular application/tool. Port numbers can be added to or deleted from the
predefined list of ports. HTTP should be enabled in 'Global Protocol Settings' for the
above functionality to work. Please refer to the HP manual HP Systems Insight
Manager Technical Reference Guide for detailed information about adding more
port numbers to the predefined list.
Server Events Information

In the Events page, HP SIM displays alerts from the managed server. Currently HP
SIM can only receive alerts in the form of SNMP traps. HP SIM also polls the
monitored device at regular intervals and displays corresponding status alerts about
the accessibility of the monitored device. The following screen shot depicts
operating system level events received from a Sun Fire x64 server.

▬▬▬▬▬
WBEM Views on Sun Fire x64 Servers
(Operating System Level Integration)
HPSIM, through WBEM calls, can extract information from monitored servers that
support WBEM. HP SIM categorizes and displays this extracted information in web
page with three tabs: Identity, Status, and Configuration.
Note: WBEM views are available only for devices and operating systems that
support the WBEM protocol.
To launch WBEM views for any device, do the following:
1. From the HP SIM administrative console, choose Tools – System
Information – Properties.
2. Select the system for which you want HP SIM to display WBEM properties
in a WBEM view.

3. Click the Run now button.
Server Identity Information

The following screen shot depicts server Identity information retrieved by HP SIM
through WBEM for a Sun Blade X8420 server module.

Server Status Information
Similarly, WBEM displays information about the status of various components of a
discovered server. The following screenshot depicts Status/Memory Utilization
information about a discovered Sun server. To view more information about other
subcategories, click the name of the subcategory in the left-hand column of the
Status page. This page should display more information about the selected
subcategory in the right-hand column.

Server Configuration Information
WBEM also displays information about the components that have been installed and
configured on a particular server. The following screen shot depicts
Configuration/Motherboard information about a discovered Sun Fire X4200 server.
To view more information about other subcategories, click the name of the
subcategory in the left-hand column of the Configuration page. This page should
display more information about the selected subcategory in the right-hand column.

▬▬▬▬▬
HP SIM Views on Sun Service Processors
(Service Processor Level Integration)
Once you have defined in HP SIM a Product Model and System Type for Sun
service processors, HP SIM can discover new service processors and display detailed
information about them in the Identity, Tools & Links, and Events pages.
Service Processor Identity Information

HP SIM displays the following information about the discovered service processor
(in this case ILOM) on the System page.
Note: HP links its Service Processor, which is called Integrated Lights-Out (iLO),
with the host of the Service Processor and vice versa. Similar association is
not possible with Sun server and the ILOM service processor at this time.
Tools and Links to Service Processor Resources

In the Tools & Links page, HP SIM displays URL links to available service
processor web servers provided its ports for HTTP and HTTPS are predefined in the
HP SIM configuration file. The following two sections address how HP SIM
provides Tools and Links integration with both the ILOM and the Embedded LOM
service processors.
Integration with ILOM Service Processors

The ILOM web server link is available if the port used for HTTP or HTTPS is in the
list of predefined ports in HP SIM's configuration file. The default HTTP port (80)
and default HTTPS port (443) are already defined in the HP SIM configuration file.

In this particular example, the ILOM web server is listening on the default ports -- 80
(HTTP) and 443 (HTTPS). HP SIM detects the web servers on these two ports and
provides two links on Tools & Links page, the first for the HTTP port and the second
for the HTTPS port.
By default, HP SIM displays “Web Server: Default Home Page” as the name of each
link. If you want HP SIM to replace this default name with the actual name of the
ILOM web server page, “Log In - Sun(TM) Sun Integrated Lights Out Manager,”
you need to cause HP SIM to query the ILOM service processor web server. To
instruct HP SIM to perform that query when it starts up, you must update the
following configuration file in the root directory on your HP SIM host server:
\config\identification\additionalWsDisc.props
When HP SIM reads additionalWsDisc.props and sees an entry for a particular

port, it polls the web server on that port, extracts its web page name, and uses that
name when it constructs links to its home page in its own Tools & Links pages. For
example, to instruct HP SIM to poll the ILOM web server on the default port 443 to
derive its web page name, edit (or create) the entry for port 443 in the
additionalWsDisc.props configuration file:
443=SUN_ILOM,iPages/i_login.asp,true,false, ,https
where SUN_ILOM is an arbitrary string.

Note: If the web server is configured to listen on a different port, please replace
the port number 443 in the previous example with the port number on which
the service processor web server is configured to listen.
After you save this modified configuration file, restart the HP SIM server. The new
link name appears on the Tools & Links pages for all newly discovered Sun ILOM
service processors. To apply this new link name to previously discovered ILOM
service processors, select each of those devices and choose Options – Identify
Systems.
If you have configured your ILOM service processor to use the SUN-ILOM-PET-
MIB.mib, you will see PET-based events in the event console.

The detailed information about this PET-based event looks as follows.
If you configure your ILOM 2.0 service processor to use the

SUN-HW-TRAP-MIB.mib, you will see HW-based events in the event console.

The detailed information about this HW-based event looks as follows.
Note that the HW-based event provides significantly more information about the
particular sensor or component on your Sun server.

Integration with Embedded LOM Service Processors
The Embedded LOM web server link is available if the port used for HTTP or
HTTPS is in the list of predefined ports in HP SIM's configuration file. By default
HTTP uses port 80 and HTTPS uses port 443 in the HP SIM configuration file.
In this particular example, the Embedded LOM web server is listening on the default
ports -- 80 (HTTP) and 443 (HTTPS). If HP SIM detects web servers on both of
these ports, it provides two links on Tools & Links page, the first for the HTTP port
and the second for the HTTPS port. Otherwise it provides one link.
Service Processor Events Information

In the Events page, HP SIM displays a short summary of the event, the severity of
event, the IP address/hostname of the alert-generating device, and the time of the
alert. By double-clicking the event or selecting 'open' in the right-click menu opens
'Event Details' of that particular event that shows additional details like description.
The following screen shot depicts representative information in an Events page.
When you double-click an event in the list, HP SIM displays more detailed
information about that event. The following screen shot depicts event details for an
Embedded LOM service processor.

Automatic actions like emailing and paging can be configured for a particular event
which triggers the specific actions when that particular alert happens.

APPENDIX A
Release Notes
SNMP MIB Compilation in HP SIM

Because of a limitation of the HP SIM application, the single varbind of PET cannot
be decoded. The Specific-trap value of a PET is dependent on Event Sensor Type,
Event Type and Event Offset and is independent of Sensor. Since Specific-trap is
independent of Sensor, the alerts that will be displayed in HP SIM convey the type of
the event and do not convey information regarding the actual sensor.
For specific procedures about integrating new mibs into HP SIM, see the HP manual
Compiling and Customizing SNMP MIBs with HP Systems Insight Manager.

APPENDIX B
Sun MIBs
Many Sun system management integration packages depend on the SNMP protocol
and use one or more of the following Sun SNMP MIBs:
▪ SUN-PLATFORM-MIB: This MIB is used by Solaris-based servers to extend the
ENTITY-MIB Physical Entity Table to represent new classes of component and
the Logical Entity Table to represent high value platform and server objects.
This MIB supplies the Sun™ SNMP Management Agent for Sun Fire™ and
Netra™ Systems with traps. The operation of this MIB is described in the Sun
publication Sun SNMP Management Agent Administration Guide for Sun Blade,
Sun Fire and Netra Servers (819-7978).
Filename: SUN-PLATFORM-MIB.mib
▪ SUN-ILOM-PET-MIB: This MIB enables management platforms that are not
IPMI compliant to partly decode standard IPMI Platform Event Traps (PETS)
generated by the ILOM and Embedded LOM service processors.
Filename: SUN-ILOM-PET-MIB.mib
▪ SUN-HW-TRAP-MIB: This MIB supplements and enhances the
SUN-ILOM-PET-MIB for ILOM 2.0 systems.
Filename: SUN-HW-TRAP-MIB.mib
To view a summary of the entries in these MIBs or to download them, consult the
following Sun web site:

APPENDIX C
What’s New?
The enhancements to the HP SIM configuration fall into two areas:

▪ Server and firmware support
▪ Improved SNMP Sensor Reporting
The following section addresses that area.
▬▬▬▬▬
Server and Firmware Support
The Sun-HPSIM configuration described in this whitepaper now supports the
following Sun servers and updated Sun system management firmware.
Category Enhancements
New servers SPARC/ILOM Servers

x64/ILOM Servers
Updated firmware Integrated Lights Out Manager (ILOM) 2.0

Embedded LOM Version 4.x
▬▬▬▬▬
Improved SNMP Sensor Reporting
The Sun-HPSIM configuration described in this whitepaper now supports a much-
improved SNMP agent:
▪ SUN-HW-TRAP-MIB Mib: For Sun servers supporting ILOM 2.0, the SUN-
HW-TRAP-MIB supplants the PET MIB in generating SNMP traps. The SUN-
HW-TRAP-MIB provides more detailed information about sensors.

Index
configuration service processor views, 59
managed servers, 8 integration levels, 5
management server for managed servers, 25 introduction, 1
device configuration product models
Embedded LOM, 18, 21 ELOM, 36
Embedded LOM service processors, 18 release notes, 65
Embedded LOM version 4.x service processors, 21 requirements
ILOM, 11 managed devices, 6
ILOM 2.0, 14 management server, 7
Sun service processors, 10 Sun MIBs, 66
discovery compilation, 2, 28
automatic, 45 supported servers, 1
manual, 45 verification
HP SIM ALOM simulated events, 48
configuration, 25 manual, 48
requirements, 7 overview, 47
server views (OS), 53 simulated IPMI events, 49
server views (WBEM), 55

HP Sim - Sun

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

HP Sim - Sun

Încărcat de

Drepturi de autor:

Formate disponibile

Third Party System Management

Monitoring Sun Servers in an HP SIM Environment

Part No. 820-0540-12

May 2008, Revision 01

Monitoring Sun Servers in an HP SIM Environment ii

Monitoring Sun Servers in an HP SIM Environment iii

Monitoring Sun Servers in an HP SIM Environment iv

HP Systems Insight Manager (hereafter HP SIM) is an enterprise management

Category Supported Description Examples

Monitoring Sun Servers in an HP SIM Environment 1

SPARC No SPARC Solaris servers with the Advanced Sun SPARC

Working with Sun MIBs

Monitoring Sun Servers in an HP SIM Environment 2

The same event generated by the SUN-HW-TRAP-MIB.mib provides

Monitoring Sun Servers in an HP SIM Environment 3

Obtaining Sun MIBs

Monitoring Sun Servers in an HP SIM Environment 4

Installed Operating Systems: Operating System

Level of Integration Integration Tasks to Perform …

Operating System Discover and classify the monitored servers.

Display system properties extracted through SNMP

Configure a server to send OS-level SNMP traps.

X64 Service Processor Discover and classify the service processor.

Display system properties extracted through SNMP.

Configure a service processor to send Platform Event

Compile SUN-ILOM-PET-MIB.mib and/or SUN-HW-

Each level of integration operates independently.

Monitoring Sun Servers in an HP SIM Environment 5

 Chapter 2 “Configuring Sun Devices to be Monitored by HP SIM”

 Chapter 3 “Configuring HP SIM to Discover and Monitor Sun Devices”

 Chapter 4 “Discovering Sun Devices”

 Chapter 5 “Verifying Overall Configuration”

 Chapter 6 “Monitoring Sun Devices in HP SIM”

Monitoring Sun Servers in an HP SIM Environment 6

Sun Servers Consult the system documentation for your Sun

SNMP service installed and running

WBEM service installed and running (wherever

Sun Embedded Lights Out Manager (ELOM)

HP SIM Management Server

Monitoring Sun Servers in an HP SIM Environment 7

Configuring Sun Devices to be

Configuring SNMP on Sun Fire x64 Servers Running Windows

Monitoring Sun Servers in an HP SIM Environment 8

6. Click the Security tab.

Monitoring Sun Servers in an HP SIM Environment 9

Sun Server Configuration Tasks

SPARC/ILOM and x64/ILOM Configure SNMP on your ILOM service

x64/EmbeddedLOM Configure SNMP on your Embedded LOM

Configure SNMP on your Embedded LOM

Monitoring Sun Servers in an HP SIM Environment 10

4. Verify the following settings.

Port 161 (default)

Set Requests Optional.

Monitoring Sun Servers in an HP SIM Environment 11

v2c Protocol Optional.

6. Enter the appropriate community string.

7. Click the Save button to submit the changes.

Monitoring Sun Servers in an HP SIM Environment 12

10. Choose Edit from the Actions drop-down box.

11. Verify the following configuration settings.

Monitoring Sun Servers in an HP SIM Environment 13

IP Address: The IP address of the server on which HP SIM is installed

Chapter 2 “Configuring Sun Devices to be Monitored by HP SIM”

Chapter 3 “Configuring HP SIM to Discover and Monitor Sun Devices”

Chapter 4 “Discovering Sun Devices”

Chapter 5 “Verifying Overall Configuration”

Chapter 6 “Monitoring Sun Devices in HP SIM”