Professional Documents
Culture Documents
HP Sim - Sun
HP Sim - Sun
HP Sim - Sun
Integration Software
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. .
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.
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
Introduction
▬▬▬▬▬
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:
http://www.sun.com/systemmanagement/tools.jsp
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
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.
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:
http://www.sun.com/systemmanagement/tools.jsp
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.
▪ SUN-HW-TRAP-MIB.mib
▪ 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).
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.
Chapter 1 “Introduction”
▬▬▬▬▬
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.
Sun Service Processors Sun Integrated Lights Out Manager (ILOM) firmware
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.
http://www.sun.com/systemmanagement/tools.jsp
Please consult this web site before deploying the Sun-HPSIM configuration
described in this whitepaper.
Setting Value(s)
v1 Protocol
Checked.
5. Click the Add button under the SNMP Communities section of the page to
open a dialog box for entering SNMP community strings.
Level: Informational
Setting Value(s)
v1 Protocol
Checked.
Field Value
IP Address: IP_address_of_destination_server
The Embedded LOM GUI displays the Platform Event Filter form.
v1 Protocol Checked
v2 Protocol Optional
v3 Protocol Optional
v1 Protocol Checked
v3 Protocol Optional
Your Embedded LOM Version 4.x service processor is now configured to send
IPMI PETs to all trap destinations listed.
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.
All PET traps are sent as SNMP v1 traps with the following format.
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
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:
\Program Files\HP\Systems Insight Manager\mibs
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 SUN mibs are now compiled and registered for HP SIM to decode IPMI PETs
and/or hardware traps.
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.
10. In the Compare rule drop-down box, select the value starts with.
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.
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.
ELOM 2.91 and ELOM Other service processors return different System Object
Identifier values.
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.
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.
HP SIM expands the page to display the Retrieve from system section.
14. [ELOM 2.91 only] Click the Get response button.
HP SIM queries the target device to determine its SNMP data type and response
value.
Subtype None
or …
Custom [Blank]
management
page
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.
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.
or SPARC/ALOM servers.
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
Solaris http://ipmitool.sourceforge.net/
Many software resource CDs distributed with Sun servers.
Linux http://ipmitool.sourceforge.net/
Many software resource CDs distributed with Sun servers.
Windows http://www.sun.com/systemmanagement/tools.jsp
Many software resource CDs distributed with Sun servers.
Field Description
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+
For example, to generate a simulated event for exceeding the upper critical
(ucr) ambient temperature on a Sun SPARC Enterprise T5120 server at IP
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
If you do not see these messages in the console, review this manual for required
configuration steps or consult the troubleshooting section of this manual.
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
If you do not see these messages in the console, review this manual for required
configuration steps or consult the troubleshooting section of this manual.
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:
▬▬▬▬▬
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.
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.
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
Note that the HW-based event provides significantly more information about the
particular sensor or component on your Sun server.
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.
Release Notes
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:
http://www.sun.com/systemmanagement/tools.jsp
What’s New?
▬▬▬▬▬
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
▬▬▬▬▬
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.