HP BladeSystem Management Pack (v 1.x) for Microsoft System Center User Guide

Transcription

1 HP BladeSystem Management Pack (v 1.x) for Microsoft System Center User Guide Abstract This guide provides information on using the HP BladeSystem Management Pack for System Center version 1.x to manage and monitor HP BladeSystem enclosures. The management pack is used with HP Insight Control for Microsoft System Center. This information is for system administrators who use the HP BladeSystem Management Pack and other HP tools to operate and manage HP BladeSystem enclosures in a Microsoft System Center environment. HP Part Number: Published: March 2013 Edition: 1

2 Copyright 2008, 2013 Hewlett Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , 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. Warranty The information contained herein is subject to change without notice. The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgements Microsoft, Windows, Windows Server, and Windows NT are U.S. registered trademarks of Microsoft Corporation.

3 Contents 1 Overview...6 Introduction...6 Product operation Installing HP BladeSystem Management Pack 1.x...8 Installation overview...8 Installing the HP BladeSystem Management Pack 1.x...9 Installation results...10 Uninstalling the HP BladeSystem Management Pack for Operations Manager...11 Repairing the installation of the HP BladeSystem Management Pack for Operations Manager...12 Modifying the HP BladeSystem Management Pack for Operations Manager installation Using the Enclosure Monitor Manager...14 Launching the Enclosure Monitor Manager...15 Connecting to the Enclosure Monitor Service...15 Refreshing monitor data...16 Adding enclosures...16 Removing managed enclosures...17 Modifying enclosure configuration...17 Modifying enclosure login...17 Launching the HP Onboard Administrator website...17 Launching the HP BladeSystem Management Pack help Using the HP BladeSystem Management Pack with Operations Manager...18 Launching HP Onboard Administrator...18 Launching HP Integrated Lights-Out...18 Using Run As Profiles...18 Customizing connection setting for the HTTP proxy environment...19 Configuring a proxy server...19 Configuring a bypass list...19 Setting up a non-administrator account to use the monitor manager...20 Analyzing HP alerts More about the HP BladeSystem Management Pack...23 HP BladeSystem Enclosure views...23 Active Alerts view...24 Device Bay State view...25 Group Diagram view...26 Enclosure State view...27 Health Explorer...28 Health Collection State view...31 Monitor Service State view...31 Task Status view...32 Predefined tasks...33 Security for HP tasks...33 Classes...34 Discovery rules...38 State monitors...38 Propagation monitors Enclosure monitor performance and scalability guidelines...40 Hardware and software configuration guidelines...40 Capacity planning guidelines and best practices...40 Practical configurations with resource guidelines...42 Contents 3

4 7 BladeSystem NT events...44 Service NT events...44 Monitor NT events...44 SOAP NT events...45 SNMP trap NT events Troubleshooting...47 Introduction...47 Enclosure monitor management issues...47 Operations Manager does not discover HP BladeSystem enclosures...47 Operations Manager does not alert HP BladeSystem enclosures...47 Authoring issues...48 Adding custom information to HP Management Packs by adding a custom task to an HP class and overriding a parameter to HP rules...48 Operational and usage issues...48 Researching state monitoring...48 An HP p-class Server Blade does not appear in the HP BladeSystem Enclosure Group...49 Expected associated classes are not displaying in the Enclosure State view or the Health Collection view...49 Event view and Performance view are empty...49 Alert notifications value is repeated in Path; Path and Source values appear to be swapped...49 Tasks cannot be launched from the Health Explorer properties page or the Product Knowledge page...49 The Group Diagram view displays initials of folder names...49 State icon or alert state appears gray...50 A fan or power supply icon appears when no fan or power supply is installed in the bay slot...50 Active Alert view displays only one alert when there are multiple device state changes...50 Management console displays the same enclosure multiple times...50 Management console does not display alerts in the Active Alert view window when opened from the Enclosure State view...50 Health Explorer does not display Knowledge information for computers and certain Windows components...50 HP Custom Data Manager cannot be used in the HP BladeSystem Management Pack...50 Enclosure Monitor Manager operational and usage issues...50 The monitor manager is unable to connect to the monitor service because of a connection issue...51 The monitor manager is unable to connect to the monitor service because of an incompatible version...51 The monitor manager is unable to connect to the monitor service because of user credentials...51 The monitor manager status line displays failure status...51 The monitor manager fails to validate an enclosure registration...51 The Details pane in the monitor manager is not updated automatically...51 A critical state displays in the monitor manager for the monitor service...51 A critical state displays in the monitor manager for a managed enclosure...51 The default Internet browser is not used when opening the Onboard Administrator web page...51 Unable to launch a wizard in the monitor manager due to a lost connection...52 Unable to launch a wizard in the monitor manager due to multiple user connections...52 Add Enclosure wizard does not add an unverified enclosure...52 Modify Enclosure Login wizard or Modify Enclosure Configuration wizard does not update an unverified enclosure...52 Changes made in Modify Enclosure Login wizard or Modify Enclosure Configuration wizard are not immediately reflected in the monitor service...52 A newly added enclosure appears in the Tree pane, but no information is available in the Details pane...52 Downgrade of Onboard Administrator firmware is not supported...52 Updating the Onboard Administrator password Contents

5 9 Support and other resources...53 Information to collect before contacting HP...53 How to contact HP...53 Registering for software technical support and update service...53 How to use your software technical support and update service...53 Warranty information...54 HP authorized resellers...54 Related information...54 Typographic conventions Documentation feedback...56 A HP BladeSystem Management Pack (v 1.x) for Microsoft System Center Support Information...57 HP SCOM Management Packs support...57 HP BladeSystem Management Pack (v 1.x) for System Center...58 Index...59 Contents 5

6 1 Overview Introduction This guide is intended for system administrators who use the HP BladeSystem Management Pack and other HP applications and tools to manage HP BladeSystem enclosures in a Microsoft System Center environment. You must be familiar with the configuration and operation of Microsoft Windows, Microsoft Systems Center Operations Manager, HP Insight Management WBEM Providers, and HP Insight Management Agents. Because of the potential risk of data loss, only individuals who are experienced with using this software should implement the procedures described in this guide. This guide supplements the Microsoft System Center user documentation. Complete information on supported hardware and software is included in HP BladeSystem Management Pack (v 1.x) for Microsoft System Center Support Information (page 57). For links to other product documentation, see Related information (page 54). The HP BladeSystem Management Pack complements and extends Operations Manager by adding alert processing, state monitoring, and hardware resource lifecycle management for HP BladeSystem enclosures. The management pack provides user discovery of HP BladeSystem enclosures, predefined views, monitors, event processing rules, and tasks. These features enable administrators to streamline IT operations and ensure increased systems availability by monitoring HP BladeSystem enclosure hardware platforms through a common management console. The HP BladeSystem Management Pack features include user configuration, monitoring, and automatic grouping of the HP BladeSystem enclosures into a common view. Default monitoring highlights the state of HP BladeSystem hardware subsystems and components, and presents a consolidated view of the enclosure status. For advanced hardware lifecycle management and remote administration of HP BladeSystem enclosures, the HP BladeSystem Management Pack includes tasks that launch HP Onboard Administrator (OA) and HP Integrated Lights-Out web consoles for advanced remote enclosure and server administration. The HP BladeSystem Management Pack manages only enclosures. HP BladeSystem servers are managed by the HP ProLiant Server Management Pack (for servers running Windows). Product operation The HP BladeSystem Management Pack performs the following tasks: Identifies, groups, and displays HP BladeSystem enclosures in the management console Populates Operations Manager with HP BladeSystem enclosure attributes and configuration data for HP BladeSystem enclosure hardware and the associated management services Monitors and displays the state of HP BladeSystem enclosure hardware and associated management services Identifies, translates, and displays HP BladeSystem enclosure hardware events written to the Windows Event Log as Operations Manager alerts Provides links to HP management tools for hardware resource management and advanced remote administration from Operations Manager The monitor service uses the information entered through the monitor manager to connect to and monitor enclosures. If the connection succeeds, the monitor service continues to monitor the enclosure for inventory, health state, and events. After the HP BladeSystem Management Pack is installed, the Operations Manager server transfers the management pack to the Operations Manager Agent managed by the Operations Manager 6 Overview

7 server. The management pack discovers the monitor service. When the discovery and monitor process completes, HP enclosure information is displayed on the management console. Product operation 7

8 2 Installing HP BladeSystem Management Pack 1.x This chapter contains the information for installing the HP BladeSystem Management Pack 1.x available for downloading from HP. Installation overview NOTE: You must register the BladeSystem c-class enclosure with the Enclosure Monitor Manager to complete the installation of HP BladeSystem Management Pack. For more information, see Using the Enclosure Monitor Manager (page 14). To install the management pack: 1. Download the management pack from the HP website ( products/servers/management/mom2007/index.html), and then unzip the file. 2. Run the self-extracting executable kit, and then select the management pack to install. The following kits are available for selection. Kit name HP BladeSystem Enclosure Management Pack for Operations Manager (x86) HP BladeSystem Enclosure Management Pack for Operations Manager (x64) File name HPBladeSystemMP0n_n(x86).exe HPBladeSystemMP0n_n(x64).exe Description Installs HP BladeSystem Enclosure management capability in an x86 environment Installs HP BladeSystem Enclosure management capability in an x64 environment NOTE: 1.5). In the file names, n_n represents the version number (for example, use 1_5 for version 3. Install the HP BladeSystem Management Pack for Operations Manager into the appropriate environment. Complete installation All modules on the Operations Manager server environment including Management Pack, Enclosure Monitor Service, Enclosure Monitor Manager, and documents Custom installation HP BladeSystem Management Pack on the Operations Manager server environment HP BladeSystem Enclosure Monitor Service and the HP BladeSystem Enclosure Monitor Manager on a managed node environment (requires.net 2.0 framework, PowerShell version 1.0, and SNMP trap service) HP BladeSystem Enclosure Monitor Manager on the Operations Manager console environment (requires.net 2.0 framework) 4. To launch HP BladeSystem Enclosure Monitor Manager, select the Launch HP BladeSystem Enclosure Monitor Manager checkbox. The installer imports the management packs to the Operations Manager server. 5. Register the HP BladeSystem c-class enclosures in the HP BladeSystem Enclosure Monitor Manager. 6. To view HP BladeSystem c-class enclosures in the Operations Manager console, complete the post-installation procedures. 8 Installing HP BladeSystem Management Pack 1.x

9 Installing the HP BladeSystem Management Pack 1.x NOTE: 1.7). In the file names, n_n represents the version number (for example, use 1_7 for version 1. If the Operations Manager console is running, close it. 2. Install the HPBladeSystemMP0n_n(x86).exe file or the HPBladeSystemMP0n_n(x64).exe file on the selected environment. For more information on choosing the appropriate environment, see step 3 of Installation overview (page 8). 3. Execute the HPBladeSystemMP0n_n(x86).exe file or the HPBladeSystemMP0n_n(x64).exe file. The Welcome screen appears. 4. In the Welcome screen, click Next. The License Agreement screen appears. 5. Select I accept the terms in the license agreement, and click Next. The Destination Folder screen appears. 6. Choose one of the following options: Accept the destination. Select a different folder: a. From the Destination Folder screen, select Change. b. Use the folder navigation button to browse to the folder location, or enter the folder name in the textbox, and then click OK. 7. Click Next. 8. If the Dependency Warning screen appears, omit this step, and proceed to step 9. If the Setup Type screen appears, perform one of the following setup types, and then proceed to step 10: Complete Select this to install all features into the Operations Manager environment. Custom 9. Click Next. Select this to specify individual features to install into the Operations Manager environment (for example, the Remote Operations Manager console), and then click Next. The Custom Setup screen appears. Select the features to install. The Custom Setup screen appears. Features that are unavailable for installation (referred to as pre-unselected features) require dependent modules that are missing. 10. Click Next. The Ready to Install the Program screen appears. 11. To begin Installation, click Install. The Installation Progress screen appears. After the selected features are installed, the Setup Completed screen appears. 12. To start monitoring the HP BladeSystem c-class enclosures, select the Launch HP BladeSystem Enclosure Monitor Manager check box. 13. Click Finish. Installing the HP BladeSystem Management Pack 1.x 9

10 Installation results The installation updates the system with components in the following table. By default, files are installed in the following directory: %Program Files%\HP BladeSystem Management Packs for Operations Manager. If you selected a different folder during the installation, files are installed in the selected folder. Name Type Feature Description HPBladeSystemManagementPackDir Environment variable N/A Stores the destination folder Management Packs \HewlettPackard.Servers.BladeSystem.mp Management pack Management packs Management pack Monitor Service \HewlettPackard.Servers.BladeSystem. HPBladeSystemEnclosureCmdLets.dll Dynamic link library Monitor service PowerShell CmdLet DLL Monitor Service \HewlettPackard.Servers.BladeSystem. HPBladeSystemEnclosureCmdLets.dll.InstallState InstallUtil State file Monitor service State file generated by InstallUtil during the installation Monitor Service \HewlettPackard.Servers.BladeSystem. HPBladeSystemEnclosureEventManager.dll Dynamic link library Monitor service DLL used for monitoring Monitor Service \HewlettPackard.Servers.BladeSystem. HPBladeSystemEnclosureEventManager.dll.InstallState InstallUtil State file Monitor service State file generated by InstallUtil during the installation Monitor Service \HPBladeSystemEnclosureEventMessages.dll Dynamic link library Monitor service NT Event message catalog file Monitor Service \ HPBladeSystemEnclosureMonitorService.exe Executable Monitor service The monitor service software Monitor Service \HPBladeSystemEnclosureMonitorService.exe.config Configuration file Monitor service Configuration file for the monitor service Release Notes and Documents \HPBladeSystemMPTroubleshootingAssistant.chm Document Release notes and documents Troubleshooting Assistant document Release Notes and Documents \HPBladeSystemMPUserGuide.chm Document Release notes and documents User guide Release Notes and Documents \HPBladeSystemMPLicense.rtf Document Release notes and documents License document Release Notes and Documents \HPBladeSystemMPReleaseNotes.rtf Document Release notes and documents Release notes Tools \HPBladeSystemEnclosureMonitorManager.exe Tool Console Task Tools HP BladeSystem Enclosure Monitor Manager HPBladeSystemMPInstallation.log Log N/A Logging text data of installation scripting result 10 Installing HP BladeSystem Management Pack 1.x

11 The HP BladeSystem Management Pack is installed into the Operations Manager server. It defines all of the HP BladeSystem monitoring capability. To view installation results, use the Management Packs view in the Operations Manager console. To confirm that the management pack was installed, go to the Administration view, and click Management Packs. Hewlett-Packard BladeSystem Management Pack is listed. Import and installation logging data created during the installation is available in the HPBladeSystemMPInstallation.log file in the installation destination folder. The installation adds entries in the programs menu on the Windows Start menu. Uninstalling the HP BladeSystem Management Pack for Operations Manager NOTE: Uninstalling the kits will not delete the imported Management Pack from the Operations Manager servers. Before using the Add/Remove Programs menu to remove kits, you must delete dependent management pack data from the Operations Manager console and the HP BladeSystem Management Pack. You can verify current dependencies in the Administration screen. To verify dependencies: 1. Right-click a management pack to verify. 2. Select Properties. 3. Select the Dependencies tab. If the management pack that depends on this management pack list does not show a dependency, you can delete the selected management pack. If dependencies are present, verify that it is safe to delete them. After you delete the HP BladeSystem Management Pack from the Operations Manager server, complete the following to uninstall kit contents. 1. Locate the HP BladeSystem Management Pack for Operations Manager in the Windows Add/Remove programs menu, and then choose one of the following options: Uninstall To remove all features, select Uninstall, and then click Yes to confirm the process. The kit entry in the Windows Add/Remove programs menu is removed. Change To change individual features, click Change. The Program Maintenance screen appears. 2. Select Modify, and then click Next. The Custom Setup screen appears. 3. Select required features, and then click Next. 4. To complete the modification, follow the instructions that appear. Uninstalling the HP BladeSystem Management Pack for Operations Manager 11

12 Repairing the installation of the HP 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 HP 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%\HP 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 HP BladeSystem Enclosure Monitor Service on the Services MMC snap-in. Modifying the HP 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 HP 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 click Modify. 12 Installing HP BladeSystem Management Pack 1.x

13 5. When the modification is complete, click Finish. Modifying the HP BladeSystem Management Pack for Operations Manager installation 13

14 3 Using the Enclosure Monitor Manager IMPORTANT: The Enclosure Monitor Manager is used with version 1.x of the HP BladeSystem Management Pack for Microsoft System Center to manage enclosures for monitoring. Version 2.x of the HP BladeSystem Management Pack uses the HP Device Monitor to manage HP BladeSystem enclosures. If you are using version 2.x, see the HP Device Manager for Microsoft System Center User Guide for information on managing enclosures. See Related information (page 54) for a link to this guide. The Enclosure Monitor Manager only supports the Enclosure Monitor Service included with the same installation package. If any issues occur that could be caused by incompatible versions, update the monitor manager and monitor service with the same installation package, and then verify that you entered the correct IP address or DNS name. The Enclosure Monitor Manager enables you to easily monitor the health of HP BladeSystem enclosures. The monitor manager requires user configuration for the Onboard Administrator to begin monitoring an enclosure. The monitor manager enables you to configure the required credentials and configuration information. The monitor manager task appears in the Monitor Service State view when at least one enclosure is registered. The Enclosure Monitor Manager interface includes the following fields: Tree pane (left) This pane, which can be collapsed and expanded, contains a tree that displays the connected monitor service and enclosures managed by the monitor service. The root node is the HP BladeSystem Enclosure Monitor Manager. The second level lists the connected Enclosure Monitor Service. The third level shows enclosures managed by the Enclosure Monitor Service. 14 Using the Enclosure Monitor Manager

15 The Tree pane also displays the status of the monitor service and the enclosure monitoring status. Detail pane (middle) The content of this pane changes according to the node selected from the Tree pane. Actions pane (right) The content of this pane, which can be collapsed and expanded, changes according to the node selected from the Tree pane. Status line Located at the bottom of the Enclosure Monitor Manager, this field displays the following messages: Ready There is no problem with the monitor service. Failed with Monitor Service The monitor manager failed to communicate with the monitor service Wizard and data autorefresh are disabled. To re-enable wizards and auto refresh, see Refreshing monitor data (page 16). Connecting/Refreshing An auto or manual refresh is in progress. Updating A wizard was launched, and the enclosure configuration is changing. Launching the Enclosure Monitor Manager The monitor manager can be launched in any of the following ways: From the actions pane of the Group diagram and Monitor Service views From the Start menu From a command line When launching from a command line, the IP address of the target monitor service can be passed to the monitor manager. For example, the following command uses the local host IP address for a monitor service that is running locally: HPBladeSystemEnclosureMonitorManager.exe Multiple monitor managers can run at the same time and simultaneously connect to the same monitor service. Only one user at a time can launch a wizard to change the enclosure configuration to a particular monitor service. Connecting to the Enclosure Monitor Service If the monitor manager is launched without having a command line argument or Connect button specifying the monitor service, the Connect screen is displayed. The Connect button is available from the File menu, or from the Actions pane and menu when you select the HP BladeSystem Enclosure Monitor Manager from the Tree pane. 1. Select or enter the Monitor Service Hostname, and then click Connect. The Monitor Service Hostname field enables you to select a previously chosen monitor service connection. Launching the Enclosure Monitor Manager 15

16 2. When connecting to a remote monitor service, verify that the monitor service can be reached and that the current user has the necessary privileges to access the remote system hosting the monitor service. Refreshing monitor data The monitor manager automatically refreshes using data from the monitor service. To manually refresh the data shown in the monitor manager, click Refresh from the Actions pane, or click the Refresh icon. The monitor manager queries the monitor service for the most current information. A refresh is required to see the latest connection and enclosure monitoring state. A manual refresh or connection to another monitor service is needed to re-enable auto refresh and wizards. Adding enclosures To add enclosures to the monitor service: 1. Configure the Onboard Administrator enclosure with login and SNMP settings. The primary and optional secondary IP addresses or DNS name of the Onboard Administrator and the login information are required to add enclosures. Each OA for a managed enclosure must have the SNMP Trap Destination set to forward events to the server running the Enclosure Monitor Service. 2. In the Actions pane, click Add Enclosure. The Add Enclosure Wizard appears. The wizard validates the information with the OA before adding an enclosure. The wizard also ensures that the OA meets the minimum supported firmware version. 3. Follow the instructions to add the enclosure to the monitor service. The monitor service begins monitoring the enclosures immediately after the wizard completes. However, newly added enclosures are not available in the management console until the next discovery cycle completes. 16 Using the Enclosure Monitor Manager

17 Removing managed enclosures To remove managed enclosures from the monitor service: 1. In the Actions pane, click Remove Managed Enclosure. The Remove Managed Enclosure Wizard appears. 2. Follow the instructions to remove the enclosure from the monitor service. The monitor service stops monitoring the removed enclosures immediately after the wizard completes. However, the management console continues to display the removed enclosures and subsystems until these elements are removed after the next discovery cycle. Modifying enclosure configuration If OA information changes, such as the IP address or the enclosure name, modify the enclosure configuration as follows: 1. From the Actions pane, click Modify Enclosure Configuration. The Modify Enclosure Configuration Wizard appears. 2. Follow the instructions to update the enclosure configuration. If the Apply changes to the Monitor Service immediately check box is selected, the modified monitor service starts using the updated information immediately after the wizard completes. Otherwise, the modified information is not applied until the monitor service reconnects with the OA. Changes to the management console are not applied until after the next discovery cycle. Modifying enclosure login If the OA information changes, such as the login credentials, modify the enclosure login information as follows: 1. From the Actions pane, click Modify Enclosure Login. The Modify Enclosure Login Wizard appears. 2. Follow the instructions to update the login information. If the Apply changes to the Monitor Service immediately check box is selected, the modified monitor service starts using the updated information immediately after the wizard completes. Otherwise, the modified information is not applied until the monitor service reconnects with the OA. Changes to the management console are not applied until after the next discovery cycle. Launching the HP Onboard Administrator website To launch the website for Onboard Administrator, select the managed enclosure from the Tree pane, and click Onboard Administrator Web from the Actions pane. The Onboard Administrator Web link opens in Internet Explorer. Launching the HP BladeSystem Management Pack help To launch the management pack help, click Help from the Actions pane. Removing managed enclosures 17

18 4 Using the HP BladeSystem Management Pack with Operations Manager This chapter describes how to use the various management pack components to manage HP BladeSystem enclosures. IMPORTANT: Before attempting to use the HP BladeSystem Management Pack, be sure it has been properly installed and configured. For more information, see Installing HP BladeSystem Management Pack 1.x (page 8). Launching HP Onboard Administrator The Onboard Administrator task launches Internet Explorer to access the Onboard Administrator Web console. This task is available from the HP BladeSystem Enclosure and any HP BladeSystem Health Collections. To access the Onboard Administrator Web console, you must input your username and password in the initial login screen. To launch Onboard Administrator: 1. Select an enclosure or a Health Collection from views such as Enclosure State view, Health Collection view or Group Diagram view. 2. Click HP Onboard Administrator. 3. Log in to HP Onboard Administrator. Launching HP Integrated Lights-Out Blade Servers in HP BladeSystem enclosures include an HP Integrated Lights-Out management processor, which enables you to perform advanced, secure, and operating system-independent remote server management using a standard browser interface. The HP BladeSystem Management Pack includes a task that collects HP Integrated Lights-Out management processor data and creates an associated browser link to remotely access the selected HP ProLiant Blade Server. To launch HP Integrated Lights-Out to display information: 1. Select a Device Bay from the Device Bay State view or by navigating to the desired bay using the Group Diagram view. 2. Click HP Integrated Lights-Out. 3. Log in to HP Integrated Lights-Out. Using Run As Profiles The HP BladeSystem Management Pack includes Run As profiles that enable non-default Run As accounts to be used for discovery and monitoring of HP enclosures. The following Run As profiles are included: HP BladeSystem Enclosure Discovery Account Used for all discovery of HP enclosures HP BladeSystem Enclosure Monitoring Account Used for all monitoring of HP enclosures The Agent Action Account specified in the Discovery Wizard is used for discovery and monitoring of HP enclosures by default. If the Local System account is not selected and another account is specified with insufficient privileges, discovery and monitoring of HP enclosures could fail. To enable successful discovery and monitoring of HP enclosures, the Agent Action Account must have sufficient privileges. To configure a Run As profile: 18 Using the HP BladeSystem Management Pack with Operations Manager

19 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 HP enclosures. The default Local System Windows Account Run As account has sufficient privileges and can be associated to HP enclosure Run As profiles. 2. Select the Run As Profile Wizard for the HP 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 HP 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. Customizing connection setting for the HTTP proxy environment The Enclosure Monitor Manager and Enclosure Monitor Service work with the WinHTTP networking infrastructure and its default settings. The Internet Explorer setting would be applied to the monitor manager in the current user's context. However, the Internet Explorer setting cannot be applied to the monitor service because it runs on a Local Service account. To modify the HTTP proxy setting to the monitor service, follow the steps described in the following sections. Configuring a proxy server 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 and insert the following XML code immediately after it. The </configsections> element is shown for clarity. </configsections> <system.net> <defaultproxy> <proxy proxyaddress=" </defaultproxy> </system.net> The proxyaddress attribute defines the proxy address and port number. For more information, see the Microsoft website ( 5. Save the configuration file. 6. Restart the monitor service from Service Control Manager. Configuring a bypass list 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 and insert the following XML code immediately after it. The </configsections> element is shown for clarity. </configsections> <system.net> Customizing connection setting for the HTTP proxy environment 19

20 <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 hp.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 For more information, see the Microsoft website ( 5. Save the configuration file. 6. Restart the monitor service from Service Control Manager. 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. Use the following information to determine which settings are required for your environment. Settings Both the monitor manager and the monitor service on single system (default) Only the monitor service on the system Only the monitor manager on the system 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. 20 Using the HP BladeSystem Management Pack with Operations Manager

21 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. Analyzing HP alerts The HP alerts contain HP hardware and services information that enable you to identify the cause of an issue and implement a timely and effective response. To view complete knowledge information, click View additional knowledge in the Alert Details pane. The Product Knowledge tab displays suggested resolutions to the alert. If necessary, launch the console tasks listed in Product Knowledge. Analyzing HP alerts 21

22 For additional system data, launch the Enclosure Monitor Manager for the monitoring configuration, launch Onboard Administrator on the individual enclosure from the link in the Alert Description in the Alert Details panel, or use HP SIM to manage multiple enclosures. To set up the custom HP Systems Insight Manager task, see the HP ProLiant Server Management Pack for System Center User Guide. 22 Using the HP BladeSystem Management Pack with Operations Manager

23 5 More about the HP BladeSystem Management Pack This chapter provides more background information about the HP BladeSystem Management Pack components. All the management pack components are copied to the management database and include: Views Tasks Classes Discoveries Monitors Rules These components are discussed in the following sections. HP BladeSystem Enclosure views The management console provides a collection of folders and windows for viewing information stored in the management database. The HP BladeSystem Management Pack includes HP BladeSystem Enclosure views that present information about each enclosure and associated alerts. The following views are added on the management console after installation of the management pack: HP BladeSystem Enclosures This root folder includes all HP BladeSystem views. This folder appears in the HP Systems folder which is defined by HP ProLiant Server Management Pack for System Center. Some enclosure-monitored information appears in HP Systems views. HP BladeSystem Enclosures/Active Alerts This view displays active alerts generated from the HP BladeSystem Enclosures and the Enclosure Monitor Service. The same alerts appear in the HP Systems/Active Alerts view. HP BladeSystem Enclosures/Device Bay State This view displays device bays with state and properties in managed HP BladeSystem Enclosures. HP BladeSystem Enclosures/Group Diagram This view displays the Diagram view, starting with the HP BladeSystem Enclosure Group. The same group also appears in the HP Systems/Group Diagram view. HP BladeSystem Enclosures/Enclosure State This view displays the State view provided by HP BladeSystem Enclosures. HP BladeSystem Enclosures/Health Collection State This view displays the State view provided by HP BladeSystem Health Collections. The same health collections appear in the HP Systems/Health Collection State view. HP BladeSystem Enclosures/Monitor Service State This view displays the State view of the Enclosure Monitor Service. The same monitor service state appears at HP Systems/HP Management Servers. HP BladeSystem/Task Status This view displays the task results. Only remote tasks appear. HP BladeSystem Enclosure views 23

24 Active Alerts view The Active Alerts view displays active alerts associated with HP BladeSystem classes including SNMP Trap alerts from the HP BladeSystem and software alerts from the Enclosure Monitor Service. To display details for an alert, select the BladeSystem Enclosure alert from the Active Alerts pane. The Alert Details pane displays HP Knowledge Base text with the originated Windows NT Event message in the Alert Description. Event processing rules included with the HP BladeSystem Management Pack identify and display HP BladeSystem events received in the Windows Event Log as Operations Manager alerts. These events are located in the HP BladeSystem event log and are generated by the Enclosure Monitor Service. NOTE: In an alert, the Path shows the Enclosure Monitor Service instance name that is monitoring the blade enclosure. The HP BladeSystem Management Pack alert does not include the Server Hostname field in the alert description. The following information appears in the Alert Details pane: Alert name Alert source Path Alert rule name Created time Alert description Knowledge Resolution (with links to console tasks) Causes Summary Related links 24 More about the HP BladeSystem Management Pack

25 Device Bay State view The Device Bay State view displays the state of device bays in managed enclosures. The device bay contains blades such as Server Blade, Storage Blade, Workstation Blade, and IO Blade. The Detail View in the lower pane displays properties of the device bay. HP BladeSystem Enclosure views 25

26 Group Diagram view The Group Diagram view provides a display of groups and associated HP BladeSystem Enclosures, subsystems (collections), and components. Expand each icon node to move to the next level of information. The Group Diagram view displays an associated hierarchical view with following order: Enclosure Group Enclosure Health Collection Device Bays Interconnect Bays Onboard Administrators Power Subsystem Thermal Subsystem Health Component Device Bay under Device Bays Interconnect Bay under Interconnect Bays Onboard Administrator under Onboard Administrators Power Supply under Power Subsystem Fan under Thermal Subsystem 26 More about the HP BladeSystem Management Pack

27 The state of the lower component is rolled up to Enclosure Group. Enclosure State view The Enclosure State view displays each state of the HP BladeSystem Enclosure associated with the Health Collection information. HP BladeSystem Enclosure views 27

28 Health Explorer To view detailed state information for an HP Health Collection and components for an enclosure, select the enclosure, and then launch the Health Explorer from the Context menu or from the link in the Actions panel. The Health Explorer can be launched from the State view and the Diagram view after selecting a target component. It displays the result of state propagation in folder style. The Health Explorer automatically expands those folders in which warning or critical states are observed. Select the last node in the folder to get the knowledge information, and then click the State Change Event tab to view state change history. 28 More about the HP BladeSystem Management Pack

29 The following figure is an example of health state change history and state property data. The Details pane contains a list of properties with HealthState and OperationalStatus data.. HP BladeSystem Enclosure views 29

30 The Health State is available by enclosure, subsystems, and components. The following are the key words used in the Details pane: Enclosure Summary state of an enclosure Thermal Fan Summary state of the thermal subsystem A fan state PowerSupplies Summary state of the power subsystem 30 More about the HP BladeSystem Management Pack

31 PowerSupply A power supply state OnboardAdministrator An HP Onboard Administrator state InterconnectBay An interconnect bay state DeviceBay A device bay state Health Collection State view The Health Collection State view displays the state of health collections of HP BladeSystem Enclosures. You can view failed collections simultaneously by sorting the State column. Monitor Service State view The Monitor Service State view displays the state of each Enclosure Monitor Service. HP BladeSystem Enclosure views 31

32 Task Status view The Task Status view displays task results. There are no predefined remote tasks, so this view might display no status most of the time. 32 More about the HP BladeSystem Management Pack

33 Predefined tasks The HP BladeSystem Management Pack includes predefined tasks that can be used to access in-depth HP BladeSystem information, carry out advanced remote server administration, and perform lifecycle management on multiple enclosures. HP tasks appear in the Actions window from the associated class instance. Not all tasks appear in every view because tasks are associated with specific classes. The management pack includes the following tasks: Enclosure Monitor Manager (see Using the Enclosure Monitor Manager (page 14)) HP Onboard Administrator (see Launching HP Onboard Administrator (page 18)) HP Integrated Lights-Out (see Launching HP Integrated Lights-Out (page 18)) Security for HP tasks Security settings are required to run HP tasks properly. HP tasks include the following types: Type A Console tasks that launch an external tool that does not communicate with the Operations Manager interface, such as: HP Onboard Administrator HP Integrated Lights-Out Type B Console tasks that launch an external tool which communicates to the Enclosure Monitor Service. For example, the console task that launches the Enclosure Monitor Manager. Predefined tasks 33

34 Classes To work with these tasks properly, the following user role profile and credentials are required: Type A These tools are launched locally using the current user's credentials. The password validation process requires individual login information. The tools depend on the user's credentials and the security management of the tool. Type B Enclosure Monitor Manager accesses the Enclosure Monitor Service remote interface. The interface carries current user credentials to verify access to resources on the system where monitor service is running. By default, only Local or Domain Administrators can access the Enclosure Monitor Service interface. Access can be provided for non-adminstrator accounts if necessary. For more information, see Setting up a non-administrator account to use the monitor manager (page 20). The structure of management pack classes is defined to seamlessly provide operations with HP ProLiant Server Management Pack for System Center. The HP BladeSystem Management Pack defines the classes in the following list. The classes are also shown in Figure 1 (page 35). HP BladeSystem Enclosure Monitor Service (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemEnclosureMonitorService) HP BladeSystem Enclosure Group (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemEnclosureGroup) HP BladeSystem Enclosure (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemEnclosure) HP BladeSystem Health Collection (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemHealthCollection) HP BladeSystem Health Component (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemHealthComponent) HP BladeSystem Onboard Administrator Collection (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemOnboardAdministratorCollection) HP BladeSystem Onboard Administrator (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemOnboardAdministrator) HP BladeSystem Thermal Subsystem (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemThermalSubsystem) HP BladeSystem Fan (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemFan) HP BladeSystem Power Subsystem (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemPowerSubsystem) HP BladeSystem Power Supply (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemPowerSupply) HP BladeSystem Device Bay Collection (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemDeviceBayCollection) HP BladeSystem Device Bay (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemDeviceBay) HP BladeSystem Interconnect Bay Collection (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemInterconnectBayCollection) HP BladeSystem Interconnect Bay (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemInterconnectBay) HP BladeSystem All Instance Group (ID=HewlettPackard.Servers.BladeSystem.HPBladeSystemAllInstanceGroup) 34 More about the HP BladeSystem Management Pack

35 Figure 1 BladeSystem classes The following table displays the properties of each class. Class HP BladeSystem Enclosure HP BladeSystem Device Bay Collection Property name Name Model Name Enclosure Serial Number Part Number Spare Part Number Rack Name Asset Tag Manufacturer Number of Device Bays Number of Power Supply Bays Number of Fan Bays Number of Interconnect Bays Number of OA Bays IP Address Name Number of Present Device Bays Enclosure Serial Number Server Name Sample value IT03-ENC-A BladeSystem c7000 Enclosure ABC1234DEF B IT03-Rack-A IT03-ENC-A-2007 HP Device BaysIT03-ENC-A 5 ABC1234DEF N/A Classes 35

36 Class HP BladeSystem Device Bay HP BladeSystem Thermal Subsystem HP BladeSystem Fan HP BladeSystem Interconnect Bay Collection HP BladeSystem Interconnect Bay Property name Name Bay Number Blade Type Manufacturer Product Name Part Number System Board Spare Part Number Serial Number BIOS Server Name BIOS Asset Tag ROM Version Integrated Lights-Out Name Integrated Lights-Out Address Integrated Lights-Out MAC Address Integrated Lights-Out Model Integrated Lights-Out Firmware Version Name Redundancy Enclosure Serial Number Server Name Name Bay Number Part Number Present Power (Watts) Spare Part Number Serial Number Product Name Fan Speed (% of max) Name Number of Present Interconnect Bays Enclosure Serial Number Server Name Name Bay Number Type Product Name Sample value Device Bay 2ProLiant Server 2 Workstation HP ProLiant BL685c G B ABC1234DEF BL480c-VS13 Xxxxxxx I14 05/17/2006 ILOUSM62500TE :16:35:3D:71:BB ilo Jun Thermal SubsystemIT03-ENC-A Redundant ABC1234DEF N/A FanBay B (empty) BladeSystem fan 30 Interconnect BaysIT03-ENC-A 2 ABC1234DEF N/A Interconnect BayBay 3 3 Ethernet Brocade 4/12 SAN Switch for HP BladeSystem 36 More about the HP BladeSystem Management Pack

37 Class HP BladeSystem Onboard Administrator Collection HP BladeSystem Onboard Administrator HP BladeSystem Power Subsystem HP BladeSystem Power Supply Property name Management IP Address User Assigned Name Part Number Spare Part Number Serial Number Manufacturer Temperature Sensor Name Number of Present OA Bays Enclosure Serial Number Server Name Name Bay Number Spare Part Number Firmware Version Manufacturer Part Number Role IP Address Serial Number Device Name Name Enclosure Power Mode Enclosure Serial Number Server Name Name Bay Number Present Output (Watts) Output Capacity (Watts) Spare Part Number Serial Number Part Number Sample value Swd77 AE370A ABC1234DEF BROCADE Present Onboard Administrators IT03-ENC-A 2 ABC1234DEF N/A <Active Standby> Onboard Administrator HP ACTIVE ABC1234DEF BladeSystem c7000 Onboard Administrator Power SubsystemIT03-ENC-A AC Redundant with Power Ceiling ABC1234DEF N/A Power Supply Bay ABC1234DEF B21 Classes 37

38 Discovery rules The management pack contains the following discovery rules: HP BladeSystem Enclosure All Instance Group Discovery This discovery rule establishes group memberships to the HP BladeSystem Enclosure All Instance Group singleton class instance. HP BladeSystem Enclosure Discovery Rule This discovery rule discovers HP BladeSystem Enclosure, HP BladeSystem Health Collection, and HP Blade Health Component class instances. HP BladeSystem Enclosure Group to HP Blade Enclosure Membership Rule This rule creates membership to the HP BladeSystem Enclosure into HP Blade Enclosure Group. HP Servers Group to HP BladeSystem Enclosure Group Membership Rule This rule creates membership to the HP BladeSystem Enclosure Group into HP Servers Group. HP BladeSystem Enclosure Monitor Service Discovery Rule State monitors This rule discovers the monitor service on a managed node. This rule is the primary rule to locate the monitor service and start the management pack into action. The management pack contains the following state monitors: HP BladeSystem Enclosure Health Monitor This monitor rule monitors the health of HP BladeSystem enclosures. HP BladeSystem Onboard Administrator Health Monitor This monitor rule monitors the health of Onboard Administrator of HP BladeSystem Enclosure. HP BladeSystem Thermal Subsystem Health Monitor This monitor rule monitors the health of Cooling Collection of HP BladeSystem Enclosure. HP BladeSystem Fan Health Monitor This monitor rule monitors the health of Fan of HP Blade Enclosure. HP BladeSystem Power Subsystem Health Monitor This monitor rule monitors the health of Power Supply Collection of HP BladeSystem Enclosure. HP BladeSystem Power Supply Health Monitor This monitor rule monitors the health of Power Supply of HP BladeSystem Enclosure. HP BladeSystem Interconnect Bay Health Monitor This monitor rule monitors the health of Interconnect Bay of HP BladeSystem Enclosure. HP BladeSystem Device Bay Health Monitor This monitor rule monitors the health of Device Bay of HP BladeSystem Enclosure. 38 More about the HP BladeSystem Management Pack

39 Propagation monitors The HP BladeSystem Enclosures Management Pack contains the following propagation monitors: HP BladeSystem Enclosure Monitor Service To Windows Computer Health Rollup Monitor (ENABLED default) HP BladeSystem Enclosure To HP BladeSystem Enclosure Monitor Service Health Rollup Monitor (DISABLED default) HP BladeSystem Enclosure Group To HP Servers Group Health Rollup Monitor (ENABLED default) HP BladeSystem Enclosure To HP Blade Enclosure Group Health Rollup Monitor (ENABLED default) HP BladeSystem Onboard Administrator Collection To HP BladeSystem Enclosure Health Rollup Monitor (ENABLED default) HP BladeSystem Onboard Administrator To HP BladeSystem Onboard Administrator Collection Health Rollup Monitor (ENABLED default) HP BladeSystem Cooling Collection To HP BladeSystem Enclosure Health Rollup Monitor (ENABLED default) HP BladeSystem Fan To HP BladeSystem Cooling Collection Health Rollup Monitor (ENABLED default) HP BladeSystem Power Supply Collection To HP BladeSystem Enclosure Health Rollup Monitor (ENABLED default) HP BladeSystem Power Supply To HP BladeSystem Power Supply Collection Health Rollup Monitor (ENABLED default) HP BladeSystem Device Bay Collection To HP BladeSystem Enclosure Health Rollup Monitor (ENABLED default) HP BladeSystem Device Bay To HP BladeSystem Device Bay Collection Health Rollup Monitor (ENABLED default) HP BladeSystem Interconnect Bay Collection To HP Blade Enclosure Health Rollup Monitor (ENABLED default) HP BladeSystem Interconnect Bay To HP BladeSystem Interconnect Bay Collection Health Rollup Monitor (ENABLED default) Propagation monitors 39

40 6 Enclosure monitor performance and scalability guidelines NOTE: This appendix describes general performance and scalability guidelines for monitoring HP BladeSystem c-class enclosures using the HP BladeSystem Management Pack (v 1.x) for Operations Manager. The HP BladeSystem Management Pack processes state monitoring and alert rules within the Operations Manager agent, and it includes the HP BladeSystem Enclosure Monitor Service to perform primary enclosure monitoring. The monitor service communicates to the Onboard Administrator of each registered HP BladeSystem enclosure through a SOAP transport and listens to SNMP traps from the OA in real-time. The management pack uses the monitor service as a data source to produce class instances, state, and alerts to the Operations Manager server. The monitor service requires system and network resources that are shared with the Operations Manager server or other applications on the system where it is configured. As the number of enclosures in an Operations Manager domain increases, resource utilization by the monitor service may also increase. This information describes performance characteristics and scalability options for the monitor service and recommends hardware configurations for typical scenarios. Because your specific scenario may differ from these guidelines, key factors influencing performance are presented so that you can adapt the information in this guide to your specific requirements. Hardware and software configuration guidelines These guidelines are based on specific hardware and software configurations. If your hardware and software configurations differ, the recommended hardware may not adequately address your needs. As a starting point, it is recommend that: The Operations Manager agent and Operations Manager server are on a well-connected network with low latency (for example, a 100 Mbps LAN with a single switch). The HP BladeSystem Enclosure Monitor Services and HP Onboard Administrators are on a well-connected network with low latency (for example, a 100 Mbps LAN with a single switch). Capacity planning guidelines and best practices The HP BladeSystem Enclosure Monitor Service monitors multiple enclosures simultaneously with a secured HTTPS/SOAP connection to each HP Onboard Administrator. The monitor service establishes an HTTPS connection for each enclosure that has been registered through the HP BladeSystem Enclosure Monitor Manager. Each connection goes through the following phases: 1. Connectionestablishes connection to an HP Onboard Administrator. 2. Data collectioninitial collection of inventory and state information of an enclosure. 3. Monitoringmonitoring for changes to inventory or state information of an enclosure. 4. Data recollectionrecollection of updated inventory and state information of an enclosure as reported during the monitoring phase (phase 3). The connection phase and data collection phase occur once in a connection. The data collection phase (phase 2) is the busiest phase and uses a significant amount of system and network resources. After the data collection is completed, the management pack can access all enclosure data to produce inventory and state information. The monitor service spends most of the time in the monitoring phase listening to the network heartbeat from the HP Onboard Administrator and watching for any information change to the monitored enclosure. If a change is found, the data recollection phase starts and will collect partial data only where a change is reported. After the data recollection is completed, the monitor service continues the monitoring phase. 40 Enclosure monitor performance and scalability guidelines

41 SNMP trap monitoring is performed simultaneously with the above 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 into the network. Factors influencing performance characteristics of the monitor service Number of registered HP BladeSystem c-class enclosures The connection, data collection, and monitoring phases are processed on a per enclosure basis. Adding more enclosures to a monitor service increases system and network utilization. Number of components in an enclosure The duration of the data collection phase is related to the number of components in an enclosure (for example, number of server blades, storage blades, and interconnect switches). The number of components is not a significant factor in capacity planning. Rate of configuration changes and error events to enclosures Any configuration change with an enclosure will trigger 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 for the monitor service while the information updates. Connection recovery The monitor service 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 monitor service and the HP Onboard Administrator, the monitor service will be busy re-establishing connection to the OA until it succeeds. Best practices based on these factors Move the monitor service to non-operations Manager servers If the Operations Manager server is highly utilized, you may not want the monitor service to share that same resource. You can move the monitor service to a managed node to free up resource sharing from the Operations Manager server. Identify an under-utilized managed node in a good network infrastructure for both the Operations Manager and HP Onboard Administrator. After the monitor service is configured on the managed node, the management pack automatically discovers the monitor service, and the Operations Manager console displays enclosure information after the next Operations Manager agent discovery cycle. To install the monitor service on a managed node: 1. Bring the installation kit on the managed node and install it with the custom setup. 2. Select the monitor service and the monitor manager. 3. Use the monitor manager to register enclosures. The login information of enclosures cannot be copied from one monitor service node to another node because the login information is securely encrypted and protected. Capacity planning guidelines and best practices 41

42 Figure 2 Partitioning enclosure monitoring to two monitor services on a segmented network Partition monitored enclosures with multiple monitor services Multiple monitor services can be deployed to multiple managed nodes in an Operations Manager domain. If the number of enclosures registered to a monitor service is causing resource issues, you can partition the enclosure monitoring to multiple monitor services. The partitioning configuration solution may be useful in the following additional cases: A single monitor service is monitoring many enclosures. If more than 50 enclosures are monitored by a single monitor service, the load to the system is significant. High CPU utilization, high network use, and single point failure might be of concern. The managed node, where the monitor service is configured, is not reliable and you want to spread the risk of a monitoring disruption. The monitor service and the HP Onboard Administrators are not in an immediate network segment. Deploying a monitor service to each network segment may remove unnecessary network usage over network segments. Avoid power cable and power source issues Frequent condition changes to the power subsystem in enclosures causes increased monitor service activity because the service works to update information as it detects each change. Resolve the issue permanently for quality enclosure monitoring. Avoid network cable issues Frequent interruptions to the network connectivity causes increased monitor service activity because the service works to re-establish connections each time it detects a disruption. Resolve the issue permanently for quality enclosure monitoring. Practical configurations with resource guidelines Although the monitor service does not require a dedicated system, it does require some system resources to reliably perform while sharing resources with applications on the system. Table 1 shows performance measurements on sample configurations. Use this information as a reference for planning your initial deployment. Further re-configuration may be needed to accommodate your conditions and network environment. 42 Enclosure monitor performance and scalability guidelines

43 Sample hardware and software configuration: Hardware HP ProLiant DL365 server (Single Dual-core AMD Opteron processor GHz, 3GB RAM, 1Gbps Ethernet) Mixed HP BladeSystem c3000 and c7000 enclosures with Version 2.10 firmware Software X86 environment Windows Server 2003 Enterprise Server R2 x86.net Framework 2.0 x86 ProLiant Support Pack 8.00 x86 HP BladeSystem Management Pack kit Version 1.5 x86 Software X64 environment Windows Server 2003 Enterprise Server R2 x64.net Framework 2.0 x64 ProLiant Support Pack 8.00 x64 HP BladeSystem Management Pack kit Version 1.5 x64 Table 1 Average CPU and memory utilization of the monitor service when the monitor service is in an active phase Number of enclosures Software Environment Average CPU utilization in the data collection phase Average memory utilization in the data collection phase 10 X86 6% 41 MB X64 4% 55 MB Practical configurations with resource guidelines 43

44 7 BladeSystem NT events Service NT events Service events log the monitor service activity when it begins and ends. Table 2 Service NT events NT event Description Enclosure Monitor Service started Enclosure Monitor Service stopped SNMP Trap Service is not available Monitor NT events Monitor events log the monitoring process of the monitor service to communicate with the Onboard Administrators. Table 3 Monitor NT events NT event Description Connecting to enclosure Connected to enclosure Disconnected from enclosure Connection to enclosure failed Data collection started The following module list appears: Enclosure Information Blade Information Onboard Administrator Information Cooling related Information Power related Information Interconnect Information LCD Information Data collection completed SOAP event collection started SOAP event collection stopped Data collection failed SNMP trap collection started Health check started Health check stopped Health Check restarted a monitoring Health Check failed to stop a monitoring Monitor service failed to load the configuration data Monitor service failed to respond 44 BladeSystem NT events

45 SOAP NT events All SOAP events are logged in raw data format. Table 4 SOAP NT events NT event 31 Description SOAP event informational SNMP trap NT events SNMP Trap Events log all SNMP traps generated by the Onboard Administrator registered by the user. It uses an IP Address to identify SNMP traps. Table 5 SNMP trap NT events NT event Description HP BladeSystem Test alert (Test SNMP Trap) HP BladeSystem rack enclosure overheated An enclosure temperature sensor has been tripped indicating an overheat condition. HP BladeSystem rack enclosure overheating An enclosure temperature sensor has been tripped indicating a possible overheat condition. HP BladeSystem rack enclosure fan failed An enclosure fan has failed and fewer than the minimum number of fans in the redundant fan group are operating. This can cause the enclosure to overheat. HP BladeSystem rack enclosure fan degraded An enclosure fan has failed, but other fans in the redundant fan group are still operating. This can cause the enclosure to overheat. HP BladeSystem rack power supply failed A power supply has failed. HP BladeSystem rack power supply degraded A power supply has degraded. HP BladeSystem rack power subsystem not redundant The rack power subsystem is no longer in a redundant state. HP BladeSystem rack power subsystem input voltage problem The rack power supply detected an input line voltage problem. HP BladeSystem rack power subsystem overload The rack power subsystem is in overload condition. HP BladeSystem Onboard Administrator degraded An Onboard Administrator has failed, but the other Onboard Administrator is still operating. HP BladeSystem Onboard Administrator role primary An Onboard Administrator has taken the role of primary. HP BladeSystem Server Blade E-keying failed A server blade e-keying has failed, and there is a port mapping problem between a server mezz card and the interconnect. HP BladeSystem interconnect failed An interconnect has failed. SOAP NT events 45

46 Table 5 SNMP trap NT events (continued) NT event Description HP BladeSystem interconnect degraded An interconnect has degraded. HP BladeSystem server blade does not respond to the group capper The server blade is not responding to capping requests from the enclosure group capper. 46 BladeSystem NT events

47 8 Troubleshooting Introduction The following information is designed to help resolve some common operating issues that might occur when you use Operations Manager. The troubleshooting issues are organized into the following categories: Enclosure monitor management issues (page 47) Authoring issues (page 48) Operational and usage issues (page 48) Enclosure Monitor Manager operational and usage issues (page 50) Enclosure monitor management issues This section provides troubleshooting information for enclosure monitor issues with Operations Manager. Operations Manager does not discover HP BladeSystem enclosures Every HP enclosure must be registered with the Enclosure Monitor Manager. Use the Enclosure Monitor Manager 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 Enclosure Monitor Service. The service displays the monitoring progress in the HP BladeSystem log (in the NT Event log). However, the Operations Manager 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 HP BladeSystem enclosures, you must perform the following actions: On the HP Onboard Administrator Web console, verify that a monitor account exists and that the account has managing permission to each managed enclosure component. To see the user settings, select Enclosure Information User/Authentication Local Users or Directory Groups, and then select a user or a group. Check the HP BladeSystem log (in the NT Event Log). Review the Error and Warning entries that can cause monitoring issues. Launch the Enclosure Monitor Manager 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. Operations Manager does not alert HP BladeSystem enclosures SNMP Settings on the HP Onboard Administrator Web console must be set up to enable SNMP Trap-based Alerts. To view and update the SNMP Settings: 1. Select Enclosure Information Enclosure Settings SNMP Settings. 2. Verify that the IP address of the system (where the monitor service is running) is registered with a community string. On OA firmware version 2.10 or later, test SNMP trap can be generated from the same SNMP Settings screen. Click Send Test Alerts. If the Management Pack is functioning properly, a test Introduction 47

48 SNMP trap posts in the HP BladeSystem log (in the NT Event log), and an alert generates on the management console. To test the SNMP trap connectivity on OA firmware older than version 2.10: 1. Update the enclosure name. 2. Verify that the HP BladeSystem log (in the NT Event Log) contains an event entry that displays the enclosure name update. 3. If the HP BladeSystem log contains an event entry, but an alert does not appear on the management console, verify that the monitor service class instance is discovered and appears on the Monitor Service State view. Authoring issues The following section provides troubleshooting information for authoring issues with Operations Manager. Adding custom information to HP Management Packs by adding a custom task to an HP class and overriding a parameter to HP rules Adding custom information such as company knowledge, custom tasks, and overriding rules to HP Management Packs creates a dependency from the custom management pack to the HP Management Packs. HP Management Packs are sealed and protected from any modification, so the custom task is stored in an external management pack. HP recommends that you create a new custom management pack for custom information management that is specific to HP Management Packs to ease future upgrades and migration paths. Operational and usage issues This section provides troubleshooting information for operational and usage issues with Operations Manager. Researching state monitoring Enclosures are monitored by the following methods after initially importing the HP BladeSystem Management Pack: Discovery and state monitoring Event monitoring The discovery and state monitoring displays the current state of the HP BladeSystem enclosures. The event monitoring displays historical alerts from the time that monitoring begins. After you initially configure enclosure monitoring, only discovery and state monitoring displays current issues. Resolve all current issues on each enclosure to use event monitoring. Use the Onboard Administrator Web console to diagnose any active issues. The discovery and state monitoring provides the latest HP BladeSystem inventory and state results to the management console. This monitoring displays a near realtime state of the HP enclosure and provides the state down to the HP Health Component level. HP Health Components present detailed component-level information. However, it does not display diagnostic-level information for each component. To get the diagnostic information, launch the Onboard Administrator Web console task. Event monitoring provides the best possible information for failed descriptions and failed components. If event monitoring generates an alert on the management console, you must resolve the issue immediately. Events are generated only once. If a state change was detected, look at the Active Alerts view to find detailed information about the issue. 48 Troubleshooting

49 An HP p-class Server Blade does not appear in the HP BladeSystem Enclosure Group HP BladeSystem Management Pack does not support HP p-class Server Blades. HP ProLiant Server Management Packs monitor HP Blade Servers. Expected associated classes are not displaying in the Enclosure State view or the Health Collection view By default, the Enclosure State view and the Health Collection State view do not display the expected associated class instances. The layout of the view can be different according to the installation order of the management packs, the discovery results, and the user's console operation. To include associated classes and properties in each view, open the Personalize View dialog box and select the ones to be included. Event view and Performance view are empty The HP BladeSystem Management Pack does not have data collection rules for events or performances. Though the Event and Performance views are accessible from HP Classes, data does not appear in these views. To view an NT Event: 1. Launch the Computer Management task. 2. View the Event Viewer folder under System Tools. Events from the Enclosure Monitor Service are stored in the HP BladeSystem log. Alert notifications value is repeated in Path; Path and Source values appear to be swapped In alert notifications for devices managed by HP: The value for Source indicates the entity that generated the alert, such as the HP Insight Management Agents. The value for Path indicates the target server or device that is affected by the alert. The actual value for Path is displayed twice, separated by a semicolon. Sample alert notification: Alert: HP Smart Array SAS/SATA Event Notification Service failed. Source: HP Insight Management Agents Path: bcalfe1b2cnet.mylab.net;bcalfe1b2cnet.mylab.net Last modified by: System Last modified time: 3/16/2011 5:01:02 PM Alert description: The HP Insight Management Agents have failed; the HP Smart Array SAS/SATA Event Notification service is not running. Tasks cannot be launched from the Health Explorer properties page or the Product Knowledge page The link to the Enclosure Monitor Manager displays in the Alert Properties view on the Health Explorer properties page and the Product Knowledge page. Clicking the link will not launch a task. Use the link in the Actions panel to launch a task, or right-click the HP BladeSystem Enclosure, and select a task. The Group Diagram view displays initials of folder names Operations Manager groups the health components of the HP BladeSystem Management Pack into subfolders and displays only the initial letters of the first and last health component names within the folder. Expand the folders to view the entire health component of the management pack for a specific health collection. Operational and usage issues 49

50 State icon or alert state appears gray Operations Manager displays a green check to indicate a healthy state, a yellow exclamation point to indicate a warning, and a red X to indicate an error. When one of these icons appears gray instead of its normal color, the managed server where the monitor service is running has lost connection with Operations Manager. To verify that the network connection is working: 1. Select Administration Agent Managed and right-click the target system where the monitor service is running. 2. Click Repair. 3. Follow the instructions to reset the server status. A fan or power supply icon appears when no fan or power supply is installed in the bay slot If a bay slot is empty, but a fan or a power supply is needed in the bay slot to maintain enclosure total health, a red or yellow fan or power supply icon appears on the Diagram and State views. After you make a configuration change to the enclosure, the Diagram and State views might not reflect the state change for up to one hour. The properties of the fan of an empty bay slot fan or power supply does not display the proper information other than the bay number. Active Alert view displays only one alert when there are multiple device state changes The event processing rules of this management pack are designed to consolidate similar events and to not repeat issues. The consolidated status appears by enabling the Repeat Count property in the Active Alerts view settings. If events are consolidated, the Alert Description in the Alert Details pane shows the first event that was generated only. To view the most recent similar alert, click View additional knowledge... from the Alert Details pane and select the Alert Context tab on the Alert Properties screen. Management console displays the same enclosure multiple times If an enclosure is registered to multiple monitor services, the management console might display the same enclosure multiple times. Register different enclosures under different monitor services to fix this issue. Management console does not display alerts in the Active Alert view window when opened from the Enclosure State view State view does not always map to alerts, and the Active Alert view window might be empty. This is according to the design of most Microsoft management packs and the HP BladeSystem Management Pack. Health Explorer does not display Knowledge information for computers and certain Windows components Knowledge bases are components of Microsoft Management Pack and display limited or no information. HP Custom Data Manager cannot be used in the HP BladeSystem Management Pack Although the HP Custom Data Manager (CDM) is accessible from the HP BladeSystem Enclosure Group on the Diagram and State views, CDM only supports servers for custom data management. Enclosure Monitor Manager operational and usage issues This section provides troubleshooting information for operational and usage issues with the Operations Manager. 50 Troubleshooting

51 The monitor manager is unable to connect to the monitor service because of a connection issue The monitor manager displays an error message indicating that it failed to connect to the monitor service. To verify that the current system can connect to the target system through the network: 1. Select Computer Management Services from the target system. 2. Verify that the HP BladeSystem Enclosure Monitor Service is running. The monitor manager is unable to connect to the monitor service because of an incompatible version The monitor manager supports the monitor service only with the same installation package. If the versions are incompatible, update the monitor manager and the monitor service with the same installation package, and then verify that you entered the correct IP address or DNS name. The monitor manager is unable to connect to the monitor service because of user credentials The monitor manager uses the current user's credentials to access remote monitor service. Verify that the current user has been granted access to the remote system hosting monitor service. The monitor manager status line displays failure status The monitor manager is configured to periodically connect with the monitor service to update its data. The monitor manager displays failure status when it fails to connect with the monitor service. Ensure that the network connection is working and that the monitor service is running. Manually refresh or connect to another monitor service to restore the monitor manager to the Ready state. The monitor manager fails to validate an enclosure registration If the web browser proxy setting is not properly configured, the monitor manager fails to validate the details for a new enclosure. Adjust the proxy settings or include the enclosure IP in the exceptions list. The Details pane in the monitor manager is not updated automatically The monitor manager is configured to automatically refresh the view when data is updated in the monitor service. However, the monitor manager displays failure status if it is unable to connect with the monitor service. Manually refresh or connect to another monitor service to re-enable auto refresh. A critical state displays in the monitor manager for the monitor service The monitor manager has an issue communicating with the monitor service. Select Computer Management Services and verify that the HP BladeSystem Enclosure Monitor Service is running. If the service is not running, restart the monitor service. Verify that the HP BladeSystem event log does not contain any error messages for the monitor service. A critical state displays in the monitor manager for a managed enclosure The monitor manager displays an error message indicating that the monitor service has an issue communicating with the managed HP enclosure. Verify that the network connection and login credentials are properly configured. The default Internet browser is not used when opening the Onboard Administrator web page The monitor manager always uses Microsoft Internet Explorer to open the Onboard Administrator web page. Enclosure Monitor Manager operational and usage issues 51

52 Unable to launch a wizard in the monitor manager due to a lost connection The monitor manager is configured to update data by periodically connecting with the monitor service. The monitor manager displays failure status when it fails to connect with the monitor service. All wizards are disabled when the connection with the monitor service is lost. Ensure that the network connection is working and that the monitor service is running. Manually refresh or connect to another monitor service to restore the Ready state and re-enable all wizards. Unable to launch a wizard in the monitor manager due to multiple user connections Multiple monitor managers can simultaneously connect to the same monitor service. However, only one user at a time can launch a wizard to change the enclosure configuration to a specific monitor service. Run the wizard after the other user completes the operation. Add Enclosure wizard does not add an unverified enclosure The Add Enclosure wizard verifies the address, login credentials, and firmware version on the enclosure Onboard Administrator before adding the enclosure to the monitor service. You can add only valid enclosures to the monitor service. Modify Enclosure Login wizard or Modify Enclosure Configuration wizard does not update an unverified enclosure Modify Enclosure Login wizard and Modify Configuration wizard verify the address, login credentials, and firmware version on the enclosure Onboard Administrator before modifying the enclosure login information to the monitor service. You must update the login credentials in the enclosure Onboard Administrator before using the wizard to update the monitor service. 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 monitor service reconnects with Onboard Administrator. 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 monitor service, the added enclosure appears immediately in the Tree pane. However, the monitor service takes a few minutes to collect the inventory information. The management console is updated after the operation is complete on the monitor service. Downgrade of Onboard Administrator firmware is not supported The supported Onboard Administrator firmware versions are 2.04 and above. Do not downgrade the Onboard Administrator firmware on enclosures that have been added and are currently managed. Updating the Onboard Administrator password If the Onboard Administrator password has been changed, you must update the password to the Enclosure Monitor Service in the Enclosure Monitor Manager. Launch the Update Enclosure Login wizard from the monitor manager. You can update the login and password information for the enclosures managed by the monitor service. The new login information will be updated for all enclosures selected in this wizard. Information is not saved to the monitor service until you complete the wizard. 52 Troubleshooting

53 9 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: Software product name Hardware product model number Operating system type and version Applicable error message Third-party hardware or software Technical support registration number (if applicable) If you purchased HP Insight Control for Microsoft System Center as part of an HP Insight Control license, you are entitled to 24 x 7 HP Software Technical Support and Update Service. See the information below on how to register and use this service. If you did not purchase licenses for HP Insight Control, then you may receive technical assistance via at SMSIntegrationPack.Support@hp.com or from the HP Service Support Center forum at How to contact HP Use the following methods to contact HP technical support: See the Contact HP worldwide website: Use the Contact hp link on the HP Support Center website: In the United States, call to contact HP by telephone. This service is available 24 hours a day, 7 days a week. For continuous quality improvement, conversations might be recorded or monitored. Registering for software technical support and update service Insight Management includes one year of 24 x 7 HP Software Technical Support and Update Service. This service provides access to HP 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 HP. 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 HP Insight Management Software Services website: Registration for this service takes place following online redemption of the license certificate. How to use your software technical support and update service As HP 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 HP software support agreement. You can access this portal from the HP Support Center: Information to collect before contacting HP 53

54 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: Warranty information HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management products. HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: In the United States, see the HP U.S. service locator website: In other locations, see the Contact HP worldwide website: Related information HP Insight Control for Microsoft System Center documentation HP Insight Software documentation HP Insight Management WBEM Providers documentation HP Insight Management Agents documentation HP ProLiant servers Typographic conventions This document uses the following typographical conventions: Book title Command Computer output Ctrl+x or Ctrl-x ENVIRONMENT VARIABLE Key Term User input Replaceable The title of a book. On the web, this can be a hyperlink to the book itself. A command name or command phrase, for example ls -a. Information displayed by the computer. A key sequence that indicates you must hold down the keyboard key labeled Ctrl while you press the letter x. The name of an environment variable, for example, PATH. The name of a keyboard key. Return and Enter both refer to the same key. A term or phrase that is defined in the body text of the document, not in a glossary. Indicates commands and text that you type exactly as shown. The name of a placeholder that you replace with an actual value. [ ] In command syntax statements, these characters enclose optional content. { } In command syntax statements, these characters enclose required content. The character that separates items in a linear list of choices.... Indicates that the preceding element can be repeated one or more times. 54 Support and other resources

55 WARNING CAUTION IMPORTANT NOTE TIP An alert that calls attention to important information that, if not understood or followed, results in personal injury. An alert that calls attention to important information that, if not understood or followed, results in data loss, data corruption, or damage to hardware or software. An alert that calls attention to essential information. An alert that contains additional or supplementary information. An alert that provides helpful information. Typographic conventions 55

56 10 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback Include the document title and part number, version number, or the URL when submitting your feedback. 56 Documentation feedback

57 A HP BladeSystem Management Pack (v 1.x) for Microsoft System Center Support Information This appendix describes the latest requirements to install HP BladeSystem Management Pack for Microsoft System Center. These requirements include supported hardware, software (Microsoft System Center and Operating Systems), and firmware. HP SCOM Management Packs support HP SCOM Management Packs includes the following products that integrate with Microsoft System Center Operations Manager (SCOM): HP ProLiant Server Management Pack (v 1.60) for System Center HP BladeSystem Management Pack (v 1.50) for System Center This illustration shows the relationships between the HP installation features for SCOM and the Microsoft SCOM components. The arrows point to the SCOM components where the features can be installed. For more information regarding installation features, see the HP Insight Control for Microsoft System Center Installation and Configuration Guide, available at the HP Insight Control Integrations website: The following sections describe support information for each HP SCOM Management Packs product and the associated installation feature. NOTE: HP SCOM Management Pack products are English only. However, the installation features and managed Windows servers may run other language versions of Microsoft Windows including English, French, German, Italian, Spanish, Simplified Chinese, and Japanese. HP SCOM Management Packs support 57