HPE BladeSystem Management Pack

(v 1.70) for Microsoft System Center

User Guide

Abstract
This guide describes the procedures and prerequisites to installing and using the BladeSystem Management Pack Kit, which
provides support for monitoring BladeSystem enclosures.

Part Number: 678364-006R

Published: November 2015
Edition: 2
© Copyright 2008, 2015 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services
are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting
an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR
12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed
to the U.S. Government under vendor's standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not
responsible for information outside the Hewlett Packard Enterprise website.
Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries.

Microsoft® and Windows® are trademarks of the Microsoft group of companies.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Contents
1 Introduction..........................................................................................................5
2 Support matrix.....................................................................................................6
Supported System Center products......................................................................................................6
Supported infrastructure.......................................................................................................................6
3 Installing the HPE BladeSystem MP Kit..............................................................7
Installing................................................................................................................................................9
Configuring...........................................................................................................................................9
Upgrading...........................................................................................................................................10
Uninstalling ........................................................................................................................................10
Repairing the installation of the HPE BladeSystem Management Pack for Operations Manager.....10
Modifying the HPE BladeSystem Management Pack for Operations Manager installation................11
4 Using the Enclosure Monitor Manager..............................................................12
Adding enclosures..............................................................................................................................13
Removing managed enclosures.........................................................................................................13
Modifying enclosure configuration......................................................................................................13
5 BladeSystem MP Reference.............................................................................14
Views..................................................................................................................................................14
Tasks...................................................................................................................................................15
Events.................................................................................................................................................15
Groups................................................................................................................................................15
Discovery rules...................................................................................................................................16
Unit monitors.......................................................................................................................................16
Dependency rollup monitors...............................................................................................................16
Run As Profiles...................................................................................................................................17
6 Enclosure Monitor Service Reference...............................................................18
Events.................................................................................................................................................19
7 Troubleshooting.................................................................................................20
BladeSystem enclosures are not discovered.....................................................................................20
The EMM is unable to connect to the EMS because of a connection issue.......................................20
The EMM is unable to connect to the EMS because of an incompatible version...............................20
The EMM is unable to connect to the EMS because of user credentials...........................................20
The EMM status line displays failure status........................................................................................20
The EMM fails to validate an enclosure registration...........................................................................20
The EMM Details pane is not updated automatically.........................................................................21
A critical state displays in the EMM for the EMS................................................................................21
A critical state displays in the EMM for a managed enclosure...........................................................21
Unable to launch a wizard in the EMM due to a lost connection........................................................21
Unable to launch a wizard in the EMM due to multiple user connections..........................................21
Changes made in Modify Enclosure Login wizard or Modify Enclosure Configuration wizard are not
immediately reflected in the monitor service.......................................................................................21
A newly added enclosure appears in the Tree pane, but no information is available in the Details
pane....................................................................................................................................................21
Downgrade of OA firmware is not supported......................................................................................21
Customizing connection settings for an HTTP proxy environment.....................................................21
8 Using the BladeSystem Management Pack with Operations Manager ............23
Using Run As Profiles.........................................................................................................................23
Setting up a non-administrator account to use the monitor manager.................................................23

Contents 3
9 Support and other resources.............................................................................25
Accessing Hewlett Packard Enterprise Support.................................................................................25
Accessing updates..............................................................................................................................25
Websites.............................................................................................................................................25
Customer self repair...........................................................................................................................26
Remote support..................................................................................................................................26
Registering for software technical support and update service..........................................................26
How to use your software technical support and update service..................................................26
Warranty information.....................................................................................................................27
HPE authorized resellers....................................................................................................................27
10 Documentation feedback.................................................................................28
Index.....................................................................................................................29

4 Contents
1 Introduction
The BladeSystem Management Pack (MP) Kit provides the following for SCOM:
• Identifies, groups, and displays supported BladeSystem enclosures
• Displays the properties of supported BladeSystem enclosures
• Monitors the state of supported BladeSystem enclosures
• Identifies, translates, and displays traps/events of supported BladeSystem enclosures
• Provides links to lower-level HPE management tools

5
2 Support matrix
Supported System Center products
The kit can be installed on the following versions of SCOM:

SCOM 2007

SCOM 2007 R2

SCOM 2012

SCOM 2012 SP1

SCOM 2012 R2

Supported infrastructure
Device

BladeSystem c3000 Enclosure

BladeSystem c7000 Enclosure

NOTE: Hewlett Packard Enterprise recommends OA firmware version 4.0 or later.

IMPORTANT: For BladeSystem enclosures managed by HPE OneView, use the OneView
SCOM Integration Kit, refer to the oneview SCOM integration kit user guide, available at http://
www.hpe.com/info/ovsc/docs.

6 Support matrix
3 Installing the HPE BladeSystem MP Kit
The kit consists of the follow installable components:
Table 1 Prerequisites
Component Prerequisites

Management Pack (MP) • SCOM console is installed and closed.

• HPE ProLiant Server MP Kit 1.80 or later.

Enclosure Monitor Service (EMS) 1.50.0.0
Acts as a proxy to facilitate communication between the
management pack and OAs.
• Physical or virtual machine.
• Windows Server 2003 or later (architecture, edition,
SP, and R agnostic).
• .NET Framework 2.0.
• PowerShell 1.0 or later.
• SNMP Trap Service is installed and enabled.
• SCOM agent is installed and configured.

Enclosure Monitor Manager (EMM) 1.60.0.0
Used to add or remove devices from an EMS.
• Physical or virtual machine.
• Windows Server 2003 or later (architecture, edition,
SP, and R agnostic), or Windows Vista or later
(architecture, edition agnostic).
• .NET Framework 2.0.
• Any existing EMMs are closed.
• SCOM console is installed.

Each management pack has the following dependencies:

Table 2 Dependencies
Management Pack Dependency

BladeSystem MP 1.60.0.0 • HPE Servers Core Library MP 1.0.33.0 or later.

HewlettPackard.Servers.BladeSystem.mp • EMS 1.50.0.0 or later.

7
 The supported EMS configurations are:
Table 3 EMS configurations
1
SCOM Maximum number of enclosures per EMS
1
2007 Up to 50 enclosures
1
2012 Up to 50 enclosures
1
2012 R2 Up to 50 enclosures
1
The maximum number of devices and servers per EMS varies. See “Enclosure Monitor Service Reference” (page 18)
for more details.

Before installing any component, you must plan accordingly. See “Enclosure Monitor Service
Reference” (page 18) for complete details.
• Per standard management pack process, the management packs need to be imported in
the SCOM console for each SCOM management server.
• Hewlett Packard Enterprise recommends installing the EMM on each SCOM console machine.
This will enable the HPE BladeSystem Enclosure Monitor Manager action to work.
For a small environment, each component can be installed on the SCOM management server.

For larger environments, multiple instances of the EMS are required. For example:

8 Installing the HPE BladeSystem MP Kit

Installing
To install the management pack:
1. Ensure the prerequisites listed in Table 1 are met and:
• The installer is launched using Run as administrator.
2. On a SCOM console machine, extract the installation package by executing
HPBladSystemMPKits#_##.exe.
3. Specify a folder, and then click Unzip.
4. In the folder from Step 3, start the installer by executing the appropriate binary, e.g.
HPBladeSystemMP##_##(x64).exe.
5. Follow the wizard steps. Select the following options:
• On the Setup Type step, select Custom.
• On the Custom Setup step, select Management Packs.
To install the EMS:
1. Ensure the prerequisites listed in Table 1 are met and:
• The installer is launched using Run as administrator.
2. On one or more SCOM agent-managed machines, extract the installation package by
executing HPBladSystemMPKits#_##.exe.
3. Specify a folder, and then click Unzip.
4. In the folder from Step 3, start the installer by executing the appropriate binary, e.g.
HPBladeSystemMP##_##(x64).exe.
5. Follow the wizard steps. Select the following options:
• On the Setup Type step, select Custom.
• On the Custom Setup step, select Monitor Service.
To install the EMM:
1. Ensure the prerequisites listed in Table 1 are met and:
• The installer is launched using Run as administrator.
2. On each SCOM console machine, extract the installation package by executing
HPBladSystemMPKits#_##.exe.
3. Specify a folder, and then click Unzip.
4. In the folder from Step 3, start the installer by executing the appropriate binary, e.g.
HPBladeSystemMP##_##(x64).exe.
5. Follow the wizard steps. Select the following options:
• On the Setup Type step, select Custom.
• On the Custom Setup step, select Tools.

Configuring
1. Optionally, change the frequency of the discovery rules. By default, the Hewlett Packard
Enterprise discovery rules run every 4 hours. To change the frequency, for the particular
rule, create an override that sets IntervalSeconds appropriately.
2. For each EMS instance, use the EMM to add the devices. See “Using the Enclosure Monitor
Manager” (page 12) for complete usage details.
3. For each EMS monitored device, set its SNMP community string and trap destination to the
EMS’ IP Address.

NOTE: The management pack follows the standard Microsoft management pack methodology.

Installing 9
Upgrading
Follow the steps in “Installing” (page 9).

Uninstalling
To uninstall the kit:
1. Delete all management packs from the SCOM console.
2. On every server where a component is installed, in Program and Features, uninstall HPE
BladeSystem Management Pack for Operations Manager 2007.

Repairing the installation of the HPE BladeSystem Management Pack

for Operations Manager
You can repair installed components if a file becomes corrupt after the installation or operations.
The repair installation initializes the current configuration file and the encryption phrase in the
registry. The encryption phase decrypts the password data in the configuration file. After the
repair installation, the configuration data is copied to a different location for safe recovery.
1. In the Windows Add/Remove programs menu, locate BladeSystem Management Pack for
Operations Manager.
2. Begin the repair process by clicking Change.
The Welcome screen appears.
3. Click Next.
The Installation Type screen appears.
4. Select Repair, and then click Next.
5. Click Install.
The repair operation is completed.
6. Click Finish.
7. To recover the configuration file and the encryption phrase:
a. Open Windows File Explorer on the following folder:
%Program Files%\BladeSystem Management Pack for Operations Manager
2007\Monitor Service.
b. Delete the HPBladeSystemEnclosureMonitorService.exe.config file.
c. Rename the HPBladeSystemEnclosureMonitorService.exe.config.Backup
file to the following:
HPBladeSystemEnclosureMonitorService.exe.config.
d. Close Windows File Explorer.
e. Open Windows Registry Editor at the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP BladeSystem
Enclosure Monitor Service
f. If it exists, delete Phrase.
g. Rename Phrase Backup to Phrase.
h. Close Windows Registry Editor.
i. Restart HPE BladeSystem Enclosure Monitor Service on the Services MMC snap-in.

10 Installing the HPE BladeSystem MP Kit

Modifying the HPE BladeSystem Management Pack for Operations
Manager installation
Use the following procedure modify the installation configuration of the BladeSystem Management
Pack for Operations Manager.
1. Launch the BladeSystem Management Pack for Operations Manager installer.
The installer Welcome screen is displayed.
2. Click Next.
The Program Maintenance screen is displayed with Modify, Repair, and Remove options.
3. Select Modify, and then click Next.
The Modify the Program screen is displayed.
4. Select the desired new feature, and then click Modify.
5. When the modification is complete, click Finish.

Modifying the HPE BladeSystem Management Pack for Operations Manager installation 11
4 Using the Enclosure Monitor Manager
The EMM is used to add or remove enclosures from an EMS.

Pane Description

Configurations Displays a hierarchy of connected EMSes and their

registered enclosures.

Managed Enclosure Displays details of the selected EMS or enclosure.

Actions Displays actions for the selected EMS or enclosure.

To open the EMM:

• From the Windows Start menu, click HPE BladeSystem Enclosure Monitor Manager, or
• From the SCOM console, in the Actions pane, click HPE BladeSystem Enclosure Monitor
Manager.

NOTE: The BladeSystem Enclosure Monitor Manager SCOM console action will only work
if the EMM is installed locally on the SCOM console machine.
To add an EMS:
1. Select File > Connect, or click the Connect toolbar button, or click the Connect action link.
2. Enter the host name or IP address of the Window server where the EMS is located.
3. Click Connect.

12 Using the Enclosure Monitor Manager

Adding enclosures
To add a new enclosure:
1. Select an EMS.
2. In the Actions pane, click Add Enclosure.
3. Follow the wizard steps.

Removing managed enclosures

To delete an enclosure:
1. Select an EMS.
2. In the Actions pane, click Remove Managed Enclosure.
3. Follow the wizard steps.

Modifying enclosure configuration

To update an enclosure’s configuration:
1. Select an enclosure.
2. In the Actions pane, click Modify Enclosure Configuration or Modify Enclosure Login.
3. Follow the wizard steps.

Adding enclosures 13
5 BladeSystem MP Reference
This management pack inherits from the HPE Servers Core Library MP. See the proliant servers
management pack kit user guide, available at http://www.hpe.com/info/ovsc/docs, for more details.

Views
The HPE BladeSystem Enclosures view folder is located under the HPE Systems folder in the
Monitoring pane.

View Description

Active Alerts Displays enclosure SNMP traps processed by the EMS into SCOM alerts.
• The Path field shows the EMS instance name that is monitoring the enclosure.
• The alerts do not include the Server Hostname field.

Device Bay State Displays device bay state and properties.

Enclosure State Displays enclosure state and properties.

Group Diagram Displays a graphical, hierarchical diagram of the enclosures.

Health Collection State Displays health collection state and properties.

Monitor Service State Displays EMS state and properties.

Task Status Displays remote task results.

NOTE: This management pack propagates information into the following parent views: Active
Alerts, Health Collection State, and Management Servers.

14 BladeSystem MP Reference
Tasks
The following tasks appear in the Actions pane. Not all tasks appear in every view because tasks
are associated with specific classes.

Task Description

BladeSystem Launches the local EMM using the current user’s credentials. By default, only Local or Domain
Enclosure Monitor Administrators can access the EMS.
Manager

HPE Integrated Launches Internet Explorer to the iLO web console (login required).
Lights-Out

HPE Onboard Launches Internet Explorer to the Onboard Administrator web console (login required).
Administrator

Events
NT Event ID Description

11003 BladeSystem test alert.

22005 BladeSystem rack enclosure has overheated.

22006 BladeSystem rack enclosure is overheating.

22008 BladeSystem rack enclosure fan has failed.

22009 BladeSystem rack enclosure fan has degraded.

22013 BladeSystem rack power supply has failed.

22014 BladeSystem rack power supply has degraded.

22018 BladeSystem rack power subsystem is not redundant.

22019 BladeSystem rack power subsystem input has a voltage problem.

22020 BladeSystem rack power subsystem is overloaded.

22037 BladeSystem Onboard Administrator degraded.

22041 BladeSystem Onboard Administrator role has changed to Primary.

22042 BladeSystem server blade e-keying has failed.

22046 BladeSystem interconnect has failed.

22047 BladeSystem interconnect has degraded.

22055 BladeSystem server blade group has a capper error.

Groups
Group Contains

BladeSystem All BladeSystem Enclosure Group

Instance Group

BladeSystem OAs
Enclosure Group

Tasks 15
Discovery rules
• BladeSystem Enclosure Discovery Rule
• BladeSystem Enclosure All Instance Group Discovery
• BladeSystem Enclosure Monitor Service Discovery Rule

Unit monitors
• BladeSystem Device Bay Health Monitor
• BladeSystem Enclosure Health Monitor
• BladeSystem Enclosure Monitor Service Health Monitor
• BladeSystem Fan Health Monitor
• BladeSystem Interconnect Bay Health Monitor
• BladeSystem Onboard Administrator Health Monitor
• BladeSystem Power Subsystem Health Monitor
• BladeSystem Power Supply Health Monitor
• BladeSystem Thermal Subsystem Health Monitor

IMPORTANT: By default, the state change alerts are disabled in this management pack; i.e.
Generate Alerts is set to False. To receive the state change alerts, create an override that sets
Generate Alerts to True.

Dependency rollup monitors

• BladeSystem Device Bay Collection To BladeSystem Enclosure Health Rollup Monitor
• BladeSystem Device Bay To BladeSystem Device Bay Collection Health Rollup Monitor
• BladeSystem Enclosure Group To Servers Group Health Rollup Monitor
• BladeSystem Enclosure Monitor Service To Windows Computer Health Rollup Monitor
• BladeSystem Enclosure To Blade Enclosure Group Health Rollup Monitor
• BladeSystem Enclosure To BladeSystem Enclosure Monitor Service Heath Rollup Monitor
(Disabled)
• BladeSystem Fan to BladeSystem Thermal Subsystem Health Rollup Monitor
• BladeSystem Interconnect Bay Collection To BladeSystem Enclosure Heath Rollup Monitor
• BladeSystem Interconnect Bay To BladeSystem Interconnect Bay Collection Health Rollup
Monitor
• BladeSystem Onboard Administrator Collection to BladeSystem Enclosure Health Rollup
Monitor
• BladeSystem Onboard Administrator To BladeSystem Onboard Administrator Collection
Health Rollup Monitor
• BladeSystem Power Subsystem to BladeSystem Enclosure Health Rollup Monitor
• BladeSystem Power Supply to BladeSystem Power Subsystem Health Rollup Monitor
• BladeSystem Thermal Subsystem to BladeSystem Enclosure Health Rollup Monitor

16 BladeSystem MP Reference
Run As Profiles
• BladeSystem Enclosure Discovery Account
• BladeSystem Enclosure Monitoring Account

Run As Profiles 17
6 Enclosure Monitor Service Reference
The EMS acts as a proxy to facilitate communication between the management pack and
enclosures.
A single EMS instance monitors multiple enclosures simultaneously. The monitoring process
consists of four phases: Connection (establishes a connection to the devices), Data Collection
(collects inventory and state information), Monitoring (monitors for inventory or state changes),
and Data Recollection.
The Connection and Data Collection phases occur only once. The Data Collection phase is the
busiest phase and uses a significant amount of system and network resources. The EMS spends
most of the time in the Monitoring phase to detect any changes to the monitored device. If a
change is found, the Data Recollection phase starts and collects only the data that has changed.
After the Data Recollection phase is complete, the EMS continues the Monitoring phase.
SNMP trap monitoring is performed simultaneously with the above data phases. SNMP trap
monitoring establishes communication to the SNMP trap service and is not a factor in performance
characteristics unless a significant number of SNMP traps are generated.
There are several factors that influence EMS performance:
• Number of registered enclosures
The Connection, Data Collection, and Monitoring phases are processed on a per-enclosure
basis. Adding more monitored enclosures to a EMS increases system and network utilization.
• Rate of configuration changes and error events
Any configuration change of a monitored enclosures triggers the Data Recollection phase.
If a failing component continually changes between healthy and degraded states, every state
change triggers the Data Recollection phase and causes additional load to the EMS.
• Connection recovery
The EMS uses heartbeat monitoring to recover the connection if it is disrupted for 60 seconds
or longer. If no heartbeat is detected for a connection, the current connection disconnects
and a new connection starts. If there is a network infrastructure issue that causes instability
between the EMS and the monitored enclosures, the EMS will be busy re-establishing a
connection to the monitored enclosures until it succeeds.
• Enclosure configurations
The number of hardware components in each enclosure can impact EMS performance.
• SCOM agent
The SCOM agent, especially outside of the SCOM management server, may not be able to
process all of the data.
• System configuration
The EMS is sharing the system with other processes. So the overall CPU utilization, amount
of free memory, overall network utilization, etc., can impact EMS performance.
Therefore, the maximum number of supported enclosures per EMS will vary and thus the overall
number of EMSes for the environment will vary.

18 Enclosure Monitor Service Reference

Events
NT Event ID Description

1 Enclosure Monitor Service started.

2 Enclosure Monitor Service stopped.

3 SNMP Trap Service is not available.

11 Connecting to enclosure.

12 Connected to enclosure.

13 Disconnected from enclosure.

14 Connection to enclosure failed.

15 Data collection started. [The following module list appears: Enclosure Information, Blade Information,
Onboard Administrator Information, Cooling related Information, Power related Information,
Interconnect Information, and LCD Information.]

16 Data collection completed.

17 SOAP event collection started.

18 SOAP event collection stopped.

19 Data collection failed.

20 SNMP trap collection started.

21 Health check started.

22 Health check stopped.

23 Health Check restarted a monitoring.

24 Health Check failed to stop a monitoring.

25 Monitor service failed to load the configuration data.

26 Monitor service failed to respond.

31 SOAP event informational.

Events 19
7 Troubleshooting
Refer to the HPE SCOM integration kit user guide, available at http://www.hpe.com/info/ovsc/
docs, for additional troubleshooting information.

BladeSystem enclosures are not discovered

Use the EMM to review each monitored enclosure state. If a red state appears on an enclosure,
resolve the issue, and then update the enclosure registration information.
The updated registration information appears immediately in the EMS. The service displays the
monitoring progress in the BladeSystem log (in the NT Event log). However, the SCOM discovery
process does not occur immediately. The discovery results do not appear on the management
console until after the next discovery cycle.
In addition to registering BladeSystem enclosures, you must perform the following actions:
• On the OA web console, verify that a monitor account exists and that the account has
managing permission to each managed enclosure componsent. To see the user settings,
select Enclosure Information > User/Authentication > Local Users or Directory Group,
and then select a user or a group.
• Check the BladeSystem log (in the NT Event Log). Review the Error and Warning entries
that can cause monitoring issues. Launch the EMM to resolve any registration issues.
• Check all current Active Alerts in the domain of Operations Manager. Resolve all active alert
issues, and then close Active Alerts.
• Check the Operations Manager log (in the NT Event log). Review the Error and Warning
entries that can cause issues with the system. Report these issues to Microsoft.

The EMM is unable to connect to the EMS because of a connection issue

Verify that the EMM machine has a network connection to the EMS machine and that the EMS
service is running.

The EMM is unable to connect to the EMS because of an incompatible

version
The EMM only supports the EMS from the same installation package.

The EMM is unable to connect to the EMS because of user credentials

The EMM uses the current user's credentials to access remote EMS. Verify that the current user
has been granted access to the remote system hosting monitor service.

The EMM status line displays failure status

The EMM is configured to periodically connect with the EMS to update its data. The EMM displays
failure status when it fails to connect with the EMS. Ensure that the network connection is working
and that the EMS is running. Manually refresh or connect to another EMS to restore the EMM
to the Ready state.

The EMM fails to validate an enclosure registration

If the web browser proxy setting is not properly configured, the EMM fails to validate the details
for a new enclosure. Adjust the proxy settings or include the enclosure IP in the exceptions list.

20 Troubleshooting
The EMM Details pane is not updated automatically
The EMM is configured to automatically refresh the view when data is updated in the EMS.
However, the EMM displays failure status if it is unable to connect with the EMS. Manually refresh
or connect to another EMS to re-enable auto refresh.

A critical state displays in the EMM for the EMS

The EMM has an issue communicating with the EMS. Verify that the EMS service is running. If
the service is not running, restart it. Verify that the BladeSystem event log does not contain any
error messages for the EMS.

A critical state displays in the EMM for a managed enclosure

The EMM displays an error message indicating that the EMS has an issue communicating with
the managed enclosure. Verify that the network connection and login credentials are properly
configured.

Unable to launch a wizard in the EMM due to a lost connection

The EMM is configured to update data by periodically connecting with the EMS. The EMM displays
failure status when it fails to connect with the EMS. All wizards are disabled when the connection
with the EMS is lost. Ensure that the network connection is working and that the EMS service is
running. Manually refresh or connect to another EMS to restore the Ready state and re-enable
all wizards.

Unable to launch a wizard in the EMM due to multiple user connections

Multiple EMMs can simultaneously connect to the same EMS. However, only one user at a time
can launch a wizard to change thMultiple EMMs can simultaneously connect to the same EMS.
However, only one user at a time can launch a wizard to change the enclosure configuration to
a specific EMS. Run the wizard after the other user completes the operation.e enclosure
configuration to a specific EMS. Run the wizard after the other user completes the operation.

Changes made in Modify Enclosure Login wizard or Modify Enclosure

Configuration wizard are not immediately reflected in the monitor service
If the Apply changes to the Monitor Service Immediately check box is cleared, the modified
information is not applied until the EMS reconnects with OA.

A newly added enclosure appears in the Tree pane, but no information

is available in the Details pane
After adding a new managed enclosure to the EMS, the added enclosure appears immediately
in the Tree pane. However, the EMS takes a few minutes to collect the inventory information.
The management console is updated after the operation is complete on the EMS.

Downgrade of OA firmware is not supported

Do not downgrade the OA firmware on enclosures that have been added and are currently
managed.

Customizing connection settings for an HTTP proxy environment

The EMM and EMS work with the WinHTTP networking infrastructure and its default settings.
The Internet Explorer settings would be applied to the EMM in the current user's context. However,
the Internet Explorer settings cannot be applied to the EMS because it runs on a Local Service
account. To modify the HTTP proxy setting to the EMS, follow the steps described in the following
sections.

The EMM Details pane is not updated automatically 21

 1. Open File Explorer and locate the following folder:
%Program Files%\HP BladeSystem Management Pack for Operations Manager
2007\Monitor Service
2. Make a backup copy of the following configuration file:
HPBladeSystemEnclosureMonitorService.exe.config
3. Open the configuration file with an ASCII editor such as Notepad.
4. Locate the </configSections> XML element.
5. To set up a proxy server, insert the following XML code immediately after the
</configSections> element.
</configSections>
<system.net>
<defaultProxy>
<proxy proxyaddress="http://ProxyName:PortNumber"/>
</defaultProxy>
</system.net>
The proxyaddress attribute defines the proxy address and port number. For more
information, see the Microsoft website (http://msdn2.microsoft.com/en-us/library/
sa91de1e.aspx).
6. To set up a bypass list, insert the following XML code immediately after the
</configSections> element.
</configSections>
<system.net>
<defaultProxy>
<bypasslist>
<add address="BypassAddress1"/>
<add address="BypassAddress2"/>
</bypasslist>
</defaultProxy>
</system.net>
The address attribute defines the bypass address with a regular expression. For example,
<add address="[a-z]+\.hp\.com$" /> bypasses the proxy for all servers in the
hpe.com domain. The command <add address="192\.168\.\d{1,3}\.\d{1,3}"
/> bypasses the proxy for all servers whose IP addresses begin with 192.168. For more
information, see the Microsoft website (http://msdn2.microsoft.com/en-us/library/
sa91de1e.aspx).
7. Save the configuration file.
8. Restart the EMS service.

22 Troubleshooting
8 Using the BladeSystem Management Pack with
Operations Manager
This chapter describes how to use the various management pack components to manage
BladeSystem enclosures.

IMPORTANT: Before attempting to use the BladeSystem Management Pack, be sure it has
been properly installed and configured. For more information, see “Installing the HPE BladeSystem
MP Kit” (page 7).

Using Run As Profiles

The BladeSystem Management Pack includes Run As profiles that enable non-default Run As
accounts to be used for discovery and monitoring of HPE enclosures. The following Run As
profiles are included:
• BladeSystem Enclosure Discovery Account
Used for all discovery of enclosures
• BladeSystem Enclosure Monitoring Account
Used for all monitoring of enclosures
The Agent Action Account specified in the Discovery Wizard is used for discovery and
monitoring of enclosures by default. If the Local System account is not selected and another
account is specified with insufficient privileges, discovery and monitoring of enclosures could fail.
To enable successful discovery and monitoring of enclosures, the Agent Action Account must
have sufficient privileges.
To configure a Run As profile:
1. Create a Run As account using the Create Run As Account Wizard, and then specify an
account that has sufficient privileges to perform discovery and monitoring of enclosures.
The default Local System Windows Account Run As account has sufficient privileges
and can be associated to enclosure Run As profiles.
2. Select the Run As Profile Wizard for the HPE BladeSystem Enclosure Discovery Account
profile and specify the Run As account with sufficient privileges, or select the Local System
Windows Account Run As account.
3. Select the Run As Profile Wizard for the HPE BladeSystem Enclosure Monitoring
Account profile, and then specify the Run As account with sufficient privileges, or select
the Local System Windows Account Run As account.

Setting up a non-administrator account to use the monitor manager

Two settings are used to configure a non-administrator account to access the monitor manager.
• Setting A provides user or group access to the Enclosure Monitor Manager tool in the
installed folder.
• Setting B provides user or group access to the Enclosure Monitor Service. This access is
controlled by the permission setting of the registry key.

Using Run As Profiles 23

 Use the following information to determine which settings are required for your environment.

Settings Both the monitor manager Only the monitor service Only the monitor manager
and the monitor service on the system on the system
on single system (default)

Setting A Required Not required Required

Setting B Required Required Read-only registry setting

required.

Changing Setting A
1. Open File Explorer.
2. Locate the %ProgramFiles%\HP BladeSystem Management Pack for Operations
Manager 2007\Tools folder.
3. Right-click the file folder and in the options menu, select Properties.
4. Click the Security tab.
5. To allow read/execute access to the monitor manager tool, click Edit, and then choose either
of the following:
• Add Users group (Computer Domain Name\Users).
• For a non-English operating system, use the appropriate name instead of Users.
6. Close the dialog box and exit File Explorer.

Changing Setting B
1. Select Start > Run and enter regedit in the Open field.
2. Locate the key at HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP
BladeSystem Enclosure Monitor Service.
3. Right-click the key and in the options menu select Permission.
4. Click Add, and then register a user or a group.
5. Update the permission to the user or the group:
• To enable the user or group members who manage Onboard Administrator credential
data such as add, remove, and update, select the Full Control check box.
• To enable the user to only view currently registered Onboard Administrator and status,
select the Read check box.
6. Close the permission dialog box and exit the Registry Editor.

NOTE: If read-only access is set, an error message is displayed if the user attempts to connect
to the monitor service using the monitor manager.

24 Using the BladeSystem Management Pack with Operations Manager

9 Support and other resources
Accessing Hewlett Packard Enterprise Support
• For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
www.hpe.com/assistance
• To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website:
www.hpe.com/support/hpesc

Information to collect
• Technical support registration number (if applicable)
• Product name, model or version, and serial number
• Operating system name and version
• Firmware version
• Error messages
• Product-specific reports and logs
• Add-on products or components
• Third-party products or components

Accessing updates
• Some software products provide a mechanism for accessing software updates through the
product interface. Review your product documentation to identify the recommended software
update method.
• To download product updates, go to either of the following:
◦ Hewlett Packard Enterprise Support Center Get connected with updates page:
www.hpe.com/support/e-updates

◦ Software Depot website:

www.hpe.com/support/softwaredepot

• To view and update your entitlements, and to link your contracts, Care Packs, and warranties
with your profile, go to the Hewlett Packard Enterprise Support Center More Information
on Access to Support Materials page:
www.hpe.com/support/AccessToSupportMaterials

IMPORTANT: Access to some updates might require product entitlement when accessed
through the Hewlett Packard Enterprise Support Center. You must have an HP Passport
set up with relevant entitlements.

Websites
Website Link

Hewlett Packard Enterprise Information Library www.hpe.com/info/enterprise/docs

Hewlett Packard Enterprise Support Center www.hpe.com/support/hpesc

Accessing Hewlett Packard Enterprise Support 25

 Website Link

Contact Hewlett Packard Enterprise Worldwide www.hpe.com/assistance

Subscription Service/Support Alerts www.hpe.com/support/e-updates

Software Depot www.hpe.com/support/softwaredepot

Customer Self Repair www.hpe.com/support/selfrepair

Insight Remote Support www.hpe.com/info/insightremotesupport/docs

Serviceguard Solutions for HP-UX www.hpe.com/info/hpux-serviceguard-docs

Single Point of Connectivity Knowledge (SPOCK)

nl
www.hpe.com/storage/spock
Storage compatibility matrix

Storage white papers and analyst reports www.hpe.com/storage/whitepapers

Customer self repair

Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product.
If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at
your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized
service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website:
www.hpe.com/support/selfrepair

Remote support
Remote support is available with supported devices as part of your warranty, Care Pack Service,
or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure
submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a
fast and accurate resolution based on your product’s service level. Hewlett Packard Enterprise
strongly recommends that you register your device for remote support.
For more information and device support details, go to the following website:
www.hpe.com/info/insightremotesupport/docs

Registering for software technical support and update service

Insight Management includes one year of 24 x 7 Software Technical Support and Update Service.
This service provides access to technical resources for assistance in resolving software
implementation or operations problems.
The service also provides access to software updates and reference manuals in electronic form
as they are made available from Hewlett Packard Enterprise. Customers who purchase an
electronic license are eligible for electronic updates.
With this service, Insight Management customers benefit from expedited problem resolution as
well as proactive notification and delivery of software updates. For more information about this
service, see the Insight Management Software Services website:
http://www.hpe.com/services/insight
Registration for this service takes place following online redemption of the license certificate.

How to use your software technical support and update service

As Hewlett Packard Enterprise releases updates to software, the latest versions of the software
and documentation are made available to you. The Software Updates and Licensing portal gives
you access to software, documentation, and license updates for products on your software
support agreement.

26 Support and other resources

 You can access this portal from the Hewlett Packard Enterprise Support Center:
http://www.hpe.com/info/hpesc
After creating your profile and linking your support agreements to your profile, to obtain software,
documentation, and license updates, see the Software Updates and Licensing website:
http://www.hpe.com/info/hpesoftwareupdatesupport

Warranty information
Hewlett Packard Enterprise will replace defective delivery media for a period of 90 days from the
date of purchase. This warranty applies to all Insight Management products.

HPE authorized resellers

For the name of the nearest authorized reseller, see the following sources:
• In the United States, see the Hewlett Packard Enterprise U.S. service locator website:
http://www.hpe.com/service_locator
• In other locations, see the Contact Hewlett Packard Enterprise Worldwide website:
http://www.hpe.com/info/assistance

HPE authorized resellers 27

10 Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To
help us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document
title, part number, edition, and publication date located on the front cover of the document. For
online help content, include the product name, product version, help edition, and publication date
located on the legal notices page.

28 Documentation feedback
Index
Support matrix, 6
A supported infrastructure, 6
accessing supported products, 6
updates, 25
adding enclosures, 13 T
alerts Troubleshooting, 20
Introduction, 5
U
B uninstalling software, 10
BladeSystem MP Reference, 14 updates
accessing, 25
C
contacting Hewlett Packard Enterprise, 25 W
customer self repair, 26 websites, 25
customer self repair, 26
D
documentation
providing feedback on, 28

E
enclosure monitor manager
using, 12
Enclosure Monitor Service Reference, 18
enclosures, adding, 13

H
HPE website
Installation overview, 9

I
installation and configuration, 9, 10
installation instructions
Repairing the installation of the HPE BladeSystem
Management Pack for Operations Manager, 10
installation issues
Repairing the installation of the BladeSystem
Management Pack for Operations Manager, 10
installation overview
Installation overview, 9

M
modifying enclosure configuration, 13
monitor manager, 12
Setting up a non-administrator account to use the
monitor manager, 23

N
non-administrator account, setting up, 23

R
remote support, 26
removing managed enclosures, 13
Run As Profiles, 23

S
support
Hewlett Packard Enterprise, 25

29