HP Insight Management WBEM Providers User Manual

HP Insight Management WBEM Providers User Guide

HP Part Number: Part Number 481592-401 Published: November 2011 (Tenth Edition)

Notices

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.

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

Part Number 481592–401 November 2011 Tenth Edition

Microsoft, Windows, Windows Vista, and Windows Server are U.S. registered trademarks of Microsoft Corporation.

Intended audience

This guide is intended for individuals who are familiar with the configuration and operation of Microsoft® Windows®, Windows Server® 2008, and WMI Providers. Because of the risk of data loss, only individuals experienced with using this software should implement the procedures in this guide.

1 Introduction...............................................................................................7

Overview................................................................................................................................7

Windows Management Instrumentation.......................................................................................7

2 Installing the HP WBEM Provider Components from Intelligent Provisioning (IP)

1.0 Software.................................................................................................9

Installing the HP Service Pack Proliant (SPP) Package on Proliant Servers from IP 1.0 Software.............9

3 Uninstalling the HP WBEM Provider Components from Proliant Servers............11

Introduction............................................................................................................................11

Uninstalling HP WBEM Provider Components Installed on a single local Proliant Server...................11

Uninstalling HP WBEM Provider Components Installed on a single remote server............................11

Scripting commands for uninstalling HP WBEM Providers.............................................................11

4 Using the SMH with the Insight Providers.....................................................13

Change Data Source..............................................................................................................13

Auto Refresh..........................................................................................................................13

Threshold settings...................................................................................................................13

Data collection.......................................................................................................................14

5 Security...................................................................................................15

Security concerns....................................................................................................................15

Implementation.......................................................................................................................15

Best practices.........................................................................................................................15

Configuring Insight Provider Security for a User Account using HP SIM Configure and Repair

Agents..................................................................................................................................15

Configuring Insight Provider Security using the Windows Command Line........................................17

6 Windows Server® 2008 Firewall configuration............................................19

Firewall configuration introduction.............................................................................................19

Firewall configuration..............................................................................................................19

7 Insight Providers architecture......................................................................21

Architecture overview..............................................................................................................21

Data model...........................................................................................................................22

Microsoft Visual Basic Scripting Edition examples........................................................................24

Insight Providers usage............................................................................................................27

Additional documentation........................................................................................................27

8 Scripting.................................................................................................29

Scripting examples.................................................................................................................29

WMIC example.................................................................................................................29

Scripting references.................................................................................................................29

Table of Contents 3

9 Troubleshooting Insight Provider and HP WBEM Tools...................................31

Accessing Insight Providers from a client tool or Insight Provider tools.............................................31

10 Technical support....................................................................................33

Reference documentation.........................................................................................................33

HP contact information............................................................................................................33

Acronyms and abbreviations.........................................................................35

Index.........................................................................................................37

4 Table of Contents

List of Figures

9-1 .....................................................................................................................................31

1 Introduction

Overview

This document applies to the HP Insight Management WBEM Providers for Windows Server® 2008 and Windows Small Business Server 2011 on ProLiant servers, version 9.0 (Insight Providers). For details regarding supported servers, options, and operating system, see the HP Insight Management WBEM Providers 9.0.0 Hardware Support Matrix document.

Many management products have been built on SNMP, a common network management technology. However, SNMP-based management solutions have a simple structure and weak security protocol relative to alternatives. These limitations prevent comprehensive, industry-standard, and secure system management.

In place of SNMP, SMASH and SMI-S are secure, robust standards endorsed by the DMTF and SNIA, respectively. These standards provide the foundation for future server management infrastructures.

The Insight Providers are based on SMASH and SMI-S. The Insight Providers employ the set of base-level instrumentation provided by system management controllers and drivers, I/O controllers and drivers, and system firmware interfaces. These components deliver in-depth hardware management, including hardware inventory data, system state, and event notifications.

The data model implemented in the Insight Providers provides industry standard compliance by conforming to SMASH and SMI-S profiles.

Windows Management Instrumentation

WMI is the Microsoft® implementation of WBEM, a set of industry-standard technologies for accessing system information in a distributed management environment. WBEM and WMI use the CIM standard to represent systems, networks, applications, devices, and other managed components in an object-oriented manner. The WMI Providers extend CIM to make ProLiant-specific management data and events available to system administrators, enabling administrative tasks to be automated.

For more information on WBEM and WMI, see the following websites:

• CIM (http://www.dmtf.org/standards/cim)

• WBEM (http://www.dmtf.org/standards/wbem/)

• WMI (http://msdn.microsoft.com/en-us/library/aa394582.aspx)

• About WMI (http://msdn.microsoft.com/en-us/library/aa384642(VS.85).aspx)

Overview 7

2 Installing the HP WBEM Provider Components from

Intelligent Provisioning (IP) 1.0 Software

Installing the HP Service Pack Proliant (SPP) Package on Proliant Servers from IP 1.0 Software

The HP SPP package includes individual Management software smart components and firmware smart components. This package is available only on web for download. The Management software smart components include the following products:

• Agentless Management — HP ProLiant Agentless Management Service for Windows Server is the default Management software option installed on Gen8 servers from HP SPP. This component collects information from the operating system and provides data to the iLO. AMS is supported on both Windows Server® 2008 x86 and x64 OS. For more information about the features supported by AMS, see Agentless Management Software documents available at the following location:http://h20000.www2.hp.com/bizsupport/TechSupport/

ProdSearch.jsp?prod=Agentless Management Software&lang=en&cc=us&prodTypeId=18964&prodSeriesId=489496

• HP Insight Management WBEM Providers — HP Insight Management WBEM providers deliver in-depth hardware management, inventory data, system state, and event notifications for ProLiant and Integrity servers. WBEM Providers are based on the Distributed Management Task Force’s (DMTF) Web-based Enterprise Management standard for managing server hardware, operating systems and applications. HP SIM and SMH WBEM clients use these providers to gather data on Windows Server® 2008 x64 and x86 OS.

• HP Insight Management Agents — HP Insight Management Agents are SNMP agents that obtain information on the status of various server subsystems and display this information at the System Management Home Page (SMH). The SNMP agents are installed by default on G7 and earlier servers. This component provides management agents for Windows Server 2008 x64 and x86 OS on HP ProLiant servers. HP SIM and SMH WBEM clients use HP Insight Management Agent to gather data. For more information about the features supported by the Insight Management Agents (IMA), see the Insight Management Agents User Guide available at the following location:

http://h20000.www2.hp.com/bizsupport/TechSupport/ DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=3923526.

To install the HP SPP package on Proliant servers, follow the steps listed below:

1. Download the HP SPP package from the web available at the following location:

http://www.hp.com/go/spp/download

2. Extract the package to a local folder.

3. Run the HPSUM.exe or setup.exe script by navigating to the extracted folder. The HP Smart Update Manager (SUM) application GUI is opened.

4. Select the data repository location in the HP SUM GUI interface.

5. Enter login credentials for authenticating the data repository access.

6. Select the SPP package components to be installed on Proliant servers.

NOTE: By default, the AMS smart component is installed on the system. Both Insight Management WBEM Provider and Insight Management Agent components are optional smart components.

Installing the HP Service Pack Proliant (SPP) Package on Proliant Servers from IP 1.0 Software 9

3 Uninstalling the HP WBEM Provider Components from

Proliant Servers

Introduction

This section provides instructions for uninstalling the HP WBEM Providers components that are installed on Proliant servers.

Uninstalling HP WBEM Provider Components Installed on a single local Proliant Server

To uninstall HP WBEM Provider components on a single local server:

1. Choose the following option:

• For Windows Server® 2008, open the Windows® Programs and Features interface.

2. Select HP Insight Management WBEM Providers for Windows Server 2008 x86 /x64 editions to uninstall HP WBEM Providers.

3. Choose the following option:

• For Windows Server® 2008, right-click, and select Uninstall.

4. At the prompt, to confirm the removal of HP WBEM Providers from the system, click Yes.

5. If the HP System Management Homepage is active in a browser window, close and reopen

it to verify that it reflects the change.

Uninstalling HP WBEM Provider Components Installed on a single remote server

To uninstall HP WBEM Provider components installed on a single remote server:

1. Connect to the remote system:

• From a Microsoft® Windows® 2000 system, use the Terminal Services Client to connect

to the remote system.

• From a Microsoft® Windows® XP or a Windows Server® 2008 system, use the Remote

Desktop to connect to the remote system.

2. On the remote system, choose the following option:

• For Windows Server® 2008, open the Programs and Features interface.

3. Select the HP Insight Management WBEM Providers for Windows Server 2008 x86 /x64 editions to uninstall HP WBEM Providers.

4. Choose the following option:

• For Windows Server® 2008, right-click, and select Uninstall.

5. At the prompt, to confirm the removal of the HP Insight Management WBEM Providers for Windows Server 2008 x86 /x64 editions. click Yes.

6. If the HP System Management Homepage is active in a browser window, close and reopen it to verify that it reflects the change.

Scripting commands for uninstalling HP WBEM Providers

Use the following scripting command to uninstall HP WBEM Providers. To uninstall HP WBEM Providers, run the following Microsoft® Visual Basic Scripting Edition

(VBScript) code from a Windows® command prompt on a target system:

strComputer = "." SW = "HP Insight Management WBEM Providers" Set objWMIService = GetObject("winmgmts:" _

Introduction 11

& "{impersonationLevel=impersonate}!\\" _ & strComputer & "\root\cimv2") Set colSoftware = objWMIService.ExecQuery _ ("Select * from Win32_Product")

For Each objSoftware in colSoftware If objSoftware.Name=SW Then objSoftware.Uninstall() End If Next

12 Uninstalling the HP WBEM Provider Components from Proliant Servers

4 Using the SMH with the Insight Providers

Change Data Source

The SMH now enables data collected from the Insight Providers. After the Insight Providers are installed, SMH defaults to WBEM as the data source.

To change this setting:

1. Log in to the SMH, and then click Settings > Select SMH Data Source > Select.

2. Click the WBEM or SNMP radio button.

3. Click Select.

4. Log out of the SMH.

5. Log back in to the SMH.

Auto Refresh

When the SMH uses the SNMP data source, each page must be refreshed manually to retrieve the latest information. When using WBEM as the data source, you can refresh the information manually or set an Auto Refresh interval to get updates.

To enable WBEM Auto Refresh and to set the Refresh interval:

1. Click Settings>Auto Refresh>Configure Page Refresh Settings.

2. Select a refresh interval between 5 seconds and 30 minutes.

3. Click the Auto Refresh radio button.

After WBEM Auto Refresh is enabled, the browser refreshes the pages at the specified interval.

Threshold settings

The SMH enables the user to set thresholds on CPU utilization and Disk utilization. To create threshold settings:

1. Click Tasks (Tab) > Server Configuration > Threshold Information.

2. Enter values for processors and disks. If there are many processors or disks, you can set them

all at once using the global options.

3. Click the appropriate Set button.

Thresholds are now set. The value of these thresholds is persistent and is not lost during a reboot. If the Insight Providers are upgraded, these threshold values are preserved.

If utilization surpasses a threshold, an indication is generated. For an indication to be received, a subscription must exist for one of the following indication classes:

• HP_CpuThresholdIndication (to get only the CPU indications)

• HP_DiskThresholdIndication (to get only the Disk indications)

• HP_ThresholdIndication

• CIM_ThresholdIndication

• CIM_AlertIndication

• CIM_ProcessIndication

• CIM_Indication

• CIM_OperatingSystem

If the server is being managed by HP SIM, the threshold values can be captured and pushed to other HP SIM-managed servers through the replicate agent settings functionality.

Change Data Source 13

Data collection

The SMH enables data collected from the Insight Providers. After the Insight Providers are installed, SMH defaults to WBEM.

To change this setting:

1. Log into the SMH, and click Settings > Select SMH Data Source > Select.

2. Click the WBEM or SNMP radio button.

3. Click Select.

14 Using the SMH with the Insight Providers

5 Security

Security concerns

Users can increase security by switching from SNMP Agent-based server management to Insight Provider-based server management. The HP Insight Management WBEM Providers for Windows® use Windows-based authentication for local and remote access to server management data.

Implementation

The Insight Providers for Windows® are implemented as a set of WMI providers. The access control is in the form of standard Windows® account level access restrictions.

An administrator account has sufficient rights and security group memberships to access the Insight Providers management information for both local and remote access.

For a standard user account, there are two considerations for configuring security in order to access WMI information from the Insight Providers:

• WMI namespace security

• Distributed COM Users group membership

A standard user account needs security configurations to remotely access the Insight Provider management information on a remote server.

WMI namespace security settings govern access to WMI information. Windows user accounts can be allowed or denied specific privileges per WMI namespace.

For more information on namespace security, see Access to WMI Namespaces (http://

msdn2.microsoft.com/en-us/library/aa822575.aspx).

Only standard users who belong to the Distributed COM Users group can remotely connect to WMI and access management information. Administrators are in this group by default. Non-administrator users must be added to the Distributed COM Users group for remote WMI connectivity.

For more information, see Connecting to WMI on a Remote Computer (http://msdn2.microsoft.com/

en-us/library/aa389290.aspx).

Best practices

HP recommends using a low-level rights user account (non-administrator) to perform most read-only management tasks. Use of certain Insight Provider functionality, such as rebooting the system, requires an administrator-level account. You do not need to be an administrator of the managed system and do not need logon rights. HP recommends that the domain administrator creates a special purpose domain account.

Configuring Insight Provider Security for a User Account using HP SIM Configure and Repair Agents

NOTE: When you must configure a non-administrator account on an x64 target server, verify that the system is identified to HP SIM as a server and that it has the system subtype. For more information, see the HP SIM help file.

The following procedure provides access rights to allow a standard user account to view most management information. However, you must use an administrator account to perform some management tasks such as rebooting a server.

To configure a domain or local user (non-administrator) account for remote management:

Security concerns 15

1. From HP SIM, select Configure > Configure or Repair Agents.

If the targets are selected, the Step 1: Select Target Systems page appears.

2. Click Next.

The Step 2: Enter credentials page appears.

3. The credentials you specify on this page are for a privileged account on the target system. In

addition, the credentials must work for all selected target systems. HP recommends using domain administrator credentials. HP SIM only saves these credentials to run a scheduled task later.

a. In the User name field, enter the system administrator name. b. In the Password field, enter the system administrator password. c. In the Password (Verify) field, re-enter the system administrator password. d. If you are using a domain account, enter the Windows domain in the Domain field.

4. Click Next.

The Step 3: Install Providers and Agents (Optional) page appears.

5. Select the Install WBEM / WMI Provider (HP Insight Management WBEM Provider) for Windows

box.

6. Click Next.

The Step 4: Configure or Repair Agents page appears.

7. (Optional) Select the Configure a non-administrative account for HP SIM to access WMI data

option. This option applies to Windows® systems with the Insight Providers. The configuration of the

managed system is updated to allow users to access WMI information over the network. This user account is used by HP SIM to read inventory and configuration information from the system, and is configured as the WBEM user in the System Protocol Settings.

This configuration step is not necessary if HP SIM is configured with a user with Windows® administrator rights. HP SIM does not create this user. The user must exist as a domain user or one local to the managed system.

Users are added to the Distributed COM Users group on the managed system and given read-only access to WMI information in addition to read-write permissions to the HPQ name space.

This user does not need to be an administrator of the managed system and does not need login rights. HP recommends that the domain administrator create a special-purpose domain account.

8. Enter the credentials for HP SIM to access the managed systems: a. In the User name field, enter a user name. b. In the Password field, enter the password for the user. c. In the Password (Verify) field, re-enter the password. d. If the user account is a domain account, enter the Windows domain in the Domain field.

If configuring a nonadministrative user is successful, these credentials are saved as the System Protocol settings for WBEM access in HP SIM.

9. Choose one of the following options:

• Click Run Now.

• Click Schedule, and then set up a schedule to run this task at a later time.

16 Security

The Task Results page appears and displays the following information.

• Status — Displays the details for each target system in a task instance.

• Exit Code — Represents the success or failure of an executable program, but does not indicate if all attempts were successful. If the return value is zero or positive, the executable ran successfully. If the return value is negative value, the executable failed.

• Target Name — Displays the name and IP address of the target.

• The stdout tab — Displays output text information.

• The stderr tab — Displays information if the executable experienced an error.

• View Printable Report — Enables you to print reports for the selected target system or for all target systems associated with the task instance.

10. (Optional) To print a report: a. Click View Printable Report. b. From the Options Message box, select the report to display.

You can generate a report containing the selected target system or all systems associated with the task instance.

c. To display the report, click OK, or to return to the View Task Results page, click Cancel.

NOTE: The Configure or Repair Agents tool can update multiple target systems, each

of which might have different results. The log results indicate whether the configure/repair attempt was successful.

Configuring Insight Provider Security using the Windows Command Line

To configure a domain user or local user (non-administrator) account for remote management:

1. Open a Command Prompt window.

2. Change to the \Program Files\HPWBEM\Tools folder of the system drive.

3. Invoke the EnableRWMI.exe program to configure the account security for remote WMI access

using one of the following options:

• EnableRWMI -a:localuser

• EnableRWMI -a:domain\user

Configuring Insight Provider Security using the Windows Command Line 17

6 Windows Server® 2008 Firewall configuration

Firewall configuration introduction

This section describes a configuration method for enabling direct remote WMI access on a server running the Windows Server® 2008 Firewall.

There are many methods to establish remote communication with WMI. Locally privileged programs can establish communication with WMI locally and serve up a private or standardized remote management interface. The SMH and Windows Remote Management (an implementation of WS Management) are examples.

This documentation does not apply to these or other indirect methods of WMI related communication, only to direct remote connections to WMI. Firewall configurations for indirect WMI communication methods are independent of establishing a direct remote connection to WMI.

In addition to being used to set up the firewall, some user privileges are used in creating direct remote WMI access. For example, when a user is not an Administrator, some privileges might not exist by default.

For more information, see the MSDN article Securing a Remote WMI Connection (http://

msdn2.microsoft.com/en-us/library/aa393266.aspx).

Firewall configuration

You can establish direct remote WMI access on a computer running the Windows Server® 2008 Firewall, but the default configuration does not provide for this access. However, by using the built-in firewall rules, you can enable remote WMI access with two commands.

Locally execute the following commands on the Windows Server® 2008 machine that is providing WMI access (on a computer running the Insight Providers on Windows Server® 2008):

netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes

Output: Updated 4 rule(s). Ok.

The commands enable all firewall rules contained in the specified firewall group. If the command output does not confirm that the rules were updated, check that the group name and each word in the command are correct. The following is an example of a group name with spacing highlighted in bold:

"Windows<SPACE>Management<SPACE>Instrumentation<SPACE>(WMI)"

This first command is equivalent to selecting the Windows Management Instrumentation (WMI) checkbox in the Control Panel > Windows Firewall > Settings > Exceptions tab.

An additional firewall rule is needed to enable a remote user to establish a WMI session. It can be enabled with the following command:

netsh advfirewall firewall set rule name="Network Discovery (NB-Name-In)" new enable=yes

This command updates a portion of a rule group (a single rule). It can also be done in the user interface, using the following procedure:

1. Click Administrative Tools > Windows Firewall with Advanced Security > Inbound Rules.

2. Enable the Network Discovery (NB-Name-In) rules.

3. Select the rule, and then click Action > Enable Rule.

This rule and its equivalent rule appear in the Network Discovery and the File and Printer Sharing firewall rule groups, respectively.

If the Windows® Firewall has either of these already enabled, the latter command does not affect a change, and only first command is necessary.

Firewall configuration introduction 19

Similar rules can be created that are more restrictive but that enable remote WMI access in specific circumstances (such as restricting which users, computers, and network addresses can remotely access), depending on your setup.

There can be additional configuration and connection requirements on the client-side depending on the client operating system and firewall used.

For more information, see Connecting to WMI Remotely Starting with Vista® (http://

msdn2.microsoft.com/en-us/library/aa822854.aspx).

20 Windows Server® 2008 Firewall configuration

7 Insight Providers architecture

Architecture overview

The following architecture diagram gives an overview of Insight Provider components. The diagram distinguishes between Microsoft®-provided components, HP components, and ProLiant WMI components.

The Insight Providers extend the industry-standard CIM data model to support information that is specific to ProLiant platforms. The Insight Providers collect data from sources such as drivers and system firmware to populate the data model.

By using scripting hosts or writing directly to the WMI COM-based client API, you can create custom applications that can access the data model, providing automated administrative tasks.

The Insight Providers implement the following instrumentation:

• Server providers: — Processor information and indications — Memory information and indications — PCI devices and system slots information — Sensor information and indications, including redundancy, fans, temperature sensors,

and power supplies

Architecture overview 21

— Computer system information, including physical location, unit ID visual indicator, IML,

system ROM, and aggregate computer system status (rollup of connected components and devices)

— Computer system indications, including ASR reboot, POST error, and thermal reboot

• Network providers — Network controller information and indications — 10/100 Mb Ethernet — 1 Gb Ethernet — 10 Gb Ethernet — NIC teaming — IPv6 support

• Storage providers — Storage controller information and indications — Ultra3 and Ultra320 SCSI — SmartArray 5x and 6x — SAS/SATA information — Fibre Channel HBA information — Tape information — Host Discovered Resources (HDR) information (OS volumes)

• Other providers — c-Class blade enclosure provider — Enclosure information for c-Class blades — Management processor provider — Management processor information — Software inventory providerInstalled — HP software information — Indications to event log providerInsight — Provider indications that are logged to the

Windows® system event log

— BIOS Provider — Specific BIOS current settings.

Data model

The following table lists the set of DMTF profiles included in the data model implemented by this version of the Insight Providers.

(specialized)

LinkVersionProfile name

1.0.0DSP1004 Base Server Profile

1.0.2DSP1009 Sensors Profile

1.0.1DSP1010 Record Log Profile

1.0.2DSP1011 Physical Asset Profile

1.0.1DSP1013 Fan Profile

1.0.0DSP1014 Ethernet Port Profile

1.1.0DSP1015 Power Supply Profile

1.0.0DSP1022 CPU Profile

http://www.dmtf.org/sites/default/files/standards/ documents/DSP1004_1.0.0_0.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1009_1.0.2.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1010_1.0.1.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1011_1.0.2.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1013_1.0.1.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1014_1.0.0.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1015_1.1.0.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1022_1.0.0.pdf)

22 Insight Providers architecture

LinkVersionProfile name

Profile

1.0.1DSP1023 Software Inventory Profile

1.0.0DSP1026 System Memory Profile

1.0.1DSP1027 Power State Management

1.0.0DSP1029 OS Status Profile

1.0.0DSP1033 Profile Registration

1.0.0DSP1035 Host LAN Network Port

1.0.1DSP1036 IP Interface Profile

1.0.0DSP1040 Platform Watchdog Profile

1.0.0DSP1052 Computer System Profile

1.0.0DSP1075 PCI Device Profile

http://www.dmtf.org/standards/ published_documents/DSP1023_1.0.1.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1026_1.0.0.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1027_1.0.1.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1029_1.0.0.pdf)

http://www.dmtf.org/sites/default/files/standards/ documents/DSP1033_1.0.0.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1035_1.0.0.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1036_1.0.1.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1040_1.0.0.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1052_1.0.0.pdf)

http://www.dmtf.org/standards/ published_documents/DSP1075_1.0.0.pdf)

The following table lists the set of SMI-S profiles, subprofiles, and packages included in the data model implemented by this version of the Insight Providers.

VersionProfile/Subprofile name

1.4.4Host Hardware RAID Controller (HHRC) Profile

1.4.4Array Profile

1.2.0Block Services Package

1.3.0Disk Drive Lite Subprofile

1.2.0Multiple Computer System Subprofile

1.3.0Disk Sparing Subprofile

1.3.0Physical Package

1.3.0Location Subprofile

1.3.0Extent Mapping Subprofile (deprecated)

1.2.0Direct Attach (DA) Ports Profile

1.2.0Parallel SCSI (SPI) Initiator Ports Profile

1.3.0Software Subprofile

1.2.0FC HBA Profile

1.2.0Host Discovered Resources Profile

1.3.0Media Access Device Profile

1.2.0SAS Target Port Subprofile

1.2.0SPI Target Port Subprofile

Data model 23

The following table lists the set of HP profile extensions included in the data model implemented by this version of the Insight Providers.

File nameVersionProfile name

P00100_-_HP_Profile_Registration Profile.pdf1.0.0P00100 HP Profile Registration

Profile

P00101_-_HP_Mgmt_Proc_Lite_Profile.pdf2.1.0P00101 HP Management Processor

Lite Profile

P00102_-_HP_Fan_Profile.pdf1.3.0P00102 HP Fan Profile

P00103_-_HP_Power_Supply_Profile.pdf1.3.1P00103 HP Power Supply Profile

P00104_-_HP_Sensors_Profile.pdf1.2.0P00104 HP Sensor Profile

P00105_-_HP_Base_Server_Profile.pdf2.0.0P00105 HP Base Server Profile

P00106_-_HP_CPU_Profile.pdf1.0.0P00106 HP CPU Profile

P00107_-_HP_CPU_Consolidated_Status_Profile.pdf1.0.0P00107 HP CPU Consolidated Status

Profile

P00108_-_HP_CPU_Physical_Asset_Profile.pdf1.0.0P00108 HP CPU Physical Asset

Profile

P00109_-_HP_Record_Log_Profile.pdf1.1.0P00109 HP Record Log Profile

P00110_-_HP_Memory_Profile.pdf1.0.0P00110 HP Memory Profile

Profile

Asset Profile

Profile

P00111_-_HP_Memory_Physical_Asset_Profile.pdf1.0.0P00111 HP Memory Physical Asset

P00113_-_HP_Consolidated_Status_Profile.pdf1.0.1P00113 HP Consolidated Status

P00114_-_HP_Base_Server_Physical_Asset_Profile.pdf1.4.0P00114 HP Base Server Physical

P00115_-_HP_Fan_Physical_Asset_Profile.pdf1.1.0P00115 HP Fan Physical Asset Profile

P00116_-_HP_Power_Supply_Physical_Asset_Profile.pdf1.0.2P00116 HP Power Supply Physical

P00117_-_HP_Ethernet_Teaming Profile.pdf1.0.1P00117 HP Ethernet Teaming Profile

P00119_-_HP_FC_HBA_Profile.pdf1.0.5P00119 HP FC HBA Profile

P00120_-_HP_Storage_Enclosure_Profile.pdf1.0.2P00120 HP Storage Enclosure Profile

P00121_-_HP_Smart_Array_Profile.pdf2.0.0P00121 HP Smart Array Profile

P00122_-_HP_SAS_HBA_Profile.pdf1.1.0P00122 HP SAS HBA Array Profile

P00123_-_HP_SCSI_HBA_Profile.pdf1.0.1P00123 HP SCSI HBA Profile

P00124_-_HP_Location_Profile.pdf1.1.0P00124 HP Location Profile

P00125_-_HP_Blade_System_Lite_Profile.pdf2.1.0P00125 HP Blade System Lite Profile

P00129_-_HP_Standalone_Tape_Drive_profile.pdf1.0.0P00129 HP Standalone Tape Drive

P00130_-_HP_Host_Attached_SATA_profile.pdf1.0.0P00130 HP Host Attached SATA

Profile

Microsoft Visual Basic Scripting Edition examples

You can write scripts to obtain data from the Insight Providers using Microsoft® Visual Basic Scripting Edition (VBScript) or any other scripting language that supports Microsoft® ActiveX.

24 Insight Providers architecture

The following are example codes for accessing Insight Provider data using VBScript code. This VBScript code is used to display computer system operational status information:

strComputer = "." strNamespace = "\root\hpq" Set objWMIService = GetObject("winmgmts:\\" & strComputer & strNamespace)

Set colComputerSystem = objWMIService.ExecQuery("Select * from HP_WinComputerSystem")

For Each objComputerSystem in colComputerSystem WScript.Echo "Caption: " & objComputerSystem.Caption For Each objStatusDescription in objComputerSystem.StatusDescriptions WScript.Echo "Status description: " & objStatusDescription Next For Each objOperationalStatus in objComputerSystem.OperationalStatus WScript.Echo "Operational status: " & objOperationalStatus Next Next The following VBScript code is used to display system firmware version: strComputer = "." strNamespace = "\root\hpq" Set objWMIService = GetObject("winmgmts:\\" & strComputer & strNamespace)

Set colSystemROMFirmware = objWMIService.ExecQuery("Select * from HP_SystemROMFirmware")

For Each objSystemROMFirmware in colSystemROMFirmware WScript.Echo "Caption: " & objSystemROMFirmware.Caption WScript.Echo "Version: " & objSystemROMFirmware.VersionString WScript.Echo Next

This VBScript code is used to display computer system chassis model name, serial number and asset tag:

strComputer = "." strNamespace = "\root\hpq" Set objWMIService = GetObject("winmgmts:\\" & strComputer & strNamespace)

Set colComputerSystemChassis = objWMIService.ExecQuery("Select * from HP_ComputerSystemChassis")

For Each objComputerSystemChassis in colComputerSystemChassis WScript.Echo "Model: " & objComputerSystemChassis.Model WScript.Echo "Serial number: " & objComputerSystemChassis.SerialNumber WScript.Echo "Asset tag: " & objComputerSystemChassis.UserTracking Next

This VBScript code is used to list system memory modules and their capacities:

strComputer = "." strNamespace = "\root\hpq" Set objWMIService = GetObject("winmgmts:\\" & strComputer & strNamespace)

Set colMemoryModule = objWMIService.ExecQuery("Select * from HP_MemoryModule")

For Each objMemoryModule in colMemoryModule WScript.Echo "Caption: " & objMemoryModule.Caption WScript.Echo "Capacity (bytes): " & objMemoryModule.Capacity Wscript.Echo Next

This VBScript code is used to list system processors, current clock speed, and the number of enabled cores:

Microsoft Visual Basic Scripting Edition examples 25

strComputer = "." strNamespace = "\root\hpq" Set objWMIService = GetObject("winmgmts:\\" & strComputer & strNamespace) Set colProcessor = objWMIService.ExecQuery("Select * from HP_Processor") For Each objProcessor in colProcessor WScript.Echo "Caption: " & objProcessor.Caption WScript.Echo "Description: " & objProcessor.Description

WScript.Echo "Current clock speed (MHz): " & objProcessor.CurrentClockSpeed

WScript.Echo "Number of enabled cores: " & objProcessor.NumberOfEnabledCores

Wscript.Echo Next

This VBScript code is used to list fans and operational status information:

strComputer = "." strNamespace = "\root\hpq" Set objWMIService = GetObject("winmgmts:\\" & strComputer & strNamespace) Set colFan = objWMIService.ExecQuery("Select * from HP_WinFan") For Each objFan in colFan WScript.Echo "Caption: " & objFan.Caption WScript.Echo "Description: " & objFan.Description For Each objStatusDescription in objFan.StatusDescriptions WScript.Echo "Status description: " & objStatusDescription Next For Each objOperationalStatus in objFan.OperationalStatus WScript.Echo "Operational status: " & objOperationalStatus Next WScript.Echo Next

This VBScript code is used to clear the record log:

strComputer = "." strNamespace = "\root\hpq" Set objWMIService = GetObject("winmgmts:\\" & strComputer & strNamespace)

Set colCommonRecordLog = objWMIService.ExecQuery("Select * from HPQ_CommonRecordLog")

Wscript.Echo "Clearing the record log…" For Each objCommonRecordLog in colCommonRecordLog objCommonRecordLog.ClearLog() Next

This VBScript code is used to receive an alert indication:

strComputer = "." strNamespace = "\root\hpq" Set objWMIService = GetObject("winmgmts:\\" & strComputer & strNamespace)

Set objIndication = objWMIService.ExecNotificationQuery("SELECT * FROM HP_AlertIndication")

Wscript.Echo "Waiting for alert indication..." Set objReceivedIndication = objIndication.NextEvent WScript.Echo "Provider Name = " & objReceivedIndication.ProviderName WScript.Echo "Event ID = " & objReceivedIndication.EventID WScript.Echo "Severity = " & objReceivedIndication.PerceivedSeverity WScript.Echo "Description = " & objReceivedIndication.Description

26 Insight Providers architecture

Insight Providers usage

Access data and events from the Insight Providers using the SMH supplied in the SPP, HP SIM, other client applications, or scripts that supports WMI and SMASH.

The SMH provides a web interface for accessing management data locally or remotely. SMH support for the Insight Providers is composed of two components

• The SMH for Windows® Smart Component that is included with the SPP for Windows®. This is the SMH framework.

• The web application plug-in (SMH WebApp) that is installed with the Insight Providers. This provides the web pages that show management data using the Insight Providers.

HP SIM 6.3 and later support the Insight Providers. For information on configuring HP SIM for use with the Insight Providers, see Chapters 4 and 12 of the HP Systems Insight Manager 6.x Installation

and Configuration Guide.

Any client application or script that support WMI and SMASH can also be used to access data and events from the Insight Providers. The Microsoft MSDN website provides information on building WMI clients such as Visual Basic scripts or C++ and C# applications. For more details, see the following WMI references on the MSDN website:

• Using WMI (http://msdn2.microsoft.com/en-us/library/aa393964.aspx)

• Scripting Access to WMI (http://msdn2.microsoft.com/en-us/library/aa393256.aspx)

• Further Information (http://msdn2.microsoft.com/en-us/library/aa390436.aspx)

For sample scripts for use with the Insight Providers, see Scripting Examples (“Scripting examples”). Specific information about HP ProLiant WBEM classes and properties for servers, storage controllers,

and network controllers can be found in the profiles, MOF files, and data sheet (see Additional Documentation (“Additional documentation”)).

Additional documentation

In addition to this User Guide, the following Insight Providers documentation is available on the HP Insight Management WBEM Providers website (http://www.hp.com/go/hpwbem):

• HP Insight Management WBEM Provider Data Sheet—This document describes indication details, and class implementations not defined in a MOF or profile.

• SNMP Instrumentation Migration Guide—This document describes the mapping of SNMP OIDs to WBEM classes and properties, and SNMP traps to WBEM indications.

• MOFs—When the Insight Providers are installed, the MOF files are copied to the HP_Base, Server, Storage, and Network folders in the C:\Program Files\HPWBEM\MOF directory.

MOF files are text files that contain definitions of classes and object instances using the MOF language. The CIM data model is represented in MOF files, as are HP ProLiant-specific extensions.

• Windows Indication Eventlog Messages—This document maps the Insight Management WBEM indications to the messages that are logged to the Windows System Event Log.

Insight Providers usage 27

8 Scripting

Scripting examples

This section provides examples for accessing data exposed by the Insight Providers using scripting.

WMIC example

You can also write scripts to obtain data from the Insight Providers using WMIC and Microsoft® Windows® PowerShell.

The following command is used to display computer system status information using WMIC in noninteractive mode:

wmic /namespace:\\root\hpq path hp_wincomputersystem get caption,OperationalStatus,StatusDescriptions

The following Windows PowerShell script code can be used to list fans in the system:

$strComputer = "." $strNamespace = "root\hpq" $colFan = Get-WMIObject -class "hp_winfan" -namespace $strNamespace -computername

$strComputer foreach ($objFan in $colFan) { write-host $objFan.Name, $objFan.Description }

Scripting references

For more information regarding WMI scripting, see the following WMI references on the MSDN website (http://msdn.microsoft.com):

• Scripting Access to WMI (http://msdn2.microsoft.com/en-us/library/aa393256.aspx)

• Visual Basic Scripting Edition (http://msdn2.microsoft.com/en-us/library/t0aew7h6.aspx)

• WMIC (http://msdn2.microsoft.com/en-us/library/aa394531.aspx)

• Windows® PowerShell (http://msdn2.microsoft.com/en-us/library/bb905330.aspx)

Scripting examples 29

9 Troubleshooting Insight Provider and HP WBEM Tools

Accessing Insight Providers from a client tool or Insight Provider tools

This section describes problem you may encounter while accessing Insight providers from a client tool or any other provider tools.

Problem A super user with administrative privilege and with a user name other than

administrator, encounters the following error while sending a test event from HP WBEM Test Event Tool to the Insight providers:

Figure 9-1

Solution To enable access to HP Insight WBEM Providers from the HP WBEM Test Event Tool,

for a user account with administrative privileges and with the user name other than administrator, following steps must be performed:

1. Add specific user name to the following namespaces:

• root\HPQ

• root\HPQ\default

• root\HPQ\TestEvent

• root\Interop

• root\CIMv2

2. For each of the above mentioned namespace, complete the following namespace security steps:

1. Right-click My Computer > Manage > Services and Applications

2. Right-click WMI Control

3. Click Properties

3. Select the Security tab

4. Select the namespace

5. Click the Security button and enable the following permissions for the user:

• Execute Methods

• Full Write

• Partial Write

• Provider Write

• Enable Account

• Remote Enable

• Read Security

• Edit Security

NOTE: Any client tool facing issues in accessing Insight providers due to user name and namespace security privileges, follow the steps 1 through 5 to resolve the issue.

Accessing Insight Providers from a client tool or Insight Provider tools 31

10 Technical support

Reference documentation

For more information about SPPs, see the SPP website (http://www.hp.com/servers/SPP). To download the latest SPPs, see the software and drivers download page (http://www.hp.com/

servers/swdrivers).

For general information on management products, see the ProLiant Essentials website (http://

www.hp.com/servers/proliantessentials).

For information about operating systems supported by ProLiant servers, see the operating system support matrices (http://www.hp.com/go/supportos).

HP contact information

For the name of the nearest HP authorized reseller:

• See the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/

en/wwcontact.html).

For HP technical support:

• In the United States, for contact options see the Contact HP United States webpage (http://

welcome.hp.com/country/us/en/contact_us.html). To contact HP by phone:

— Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7

days a week. For continuous quality improvement, calls may be recorded or monitored.

— If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more

information about Care Packs, refer to the HP website (http://www.hp.com/hps).

• In other locations, see the Contact HP worldwide (in English) webpage (http://

welcome.hp.com/country/us/en/wwcontact.html).

Reference documentation 33

Acronyms and abbreviations

API application program interface ASR Automatic Server Recovery CIM common information model DMTF Distributed Management Task Force HP SIM HP Systems Insight Manager IML Integrated Management Log MOF managed object format MSDN Microsoft® Developer Network POST Power-On Self Test SAS serial attached SCSI SATA serial ATA SMASH System Management Architecture for Server Hardware SMH System Management Homepage SMI-S Storage Management Initiative Specification SPP HP Service Pack Proliant WBEM Web-Based Enterprise Management WMI Windows Management Instrumentation WMIC Windows Management Instrumentation Command-line

Index

access rights, setting user

Configuring Insight Provider Security using the Windows

Command Line, 17

Implementation, 15 accessing data and events, 27 AMS

Data collection, 14

Introduction, 11

Scripting commands for HP Insight Management Agents

7.70 or later, 11 Technical support, 33 Uninstalling AMS, 11 Uninstalling HP Insight Management Agents on a single

local server, 11

Uninstalling HP Insight Management Agents on a single

remote server, 11 AMS data collection, 14 AMS, uninstalling on single local server, 11 architecture, 21 authorized reseller

HP contact information, 33 Technical support, 33

auto-refresh setting, 13

bundles, WMI support, 7

compatibility

Windows Management Instrumentation, 7

data models, 22 documentation

Additional documentation, 27 Reference documentation, 33

firewall settings, configuring

Firewall configuration, 19 Firewall configuration introduction, 19 Security, 15 Windows Server? 2008 Firewall configuration, 19

Insight Providers, integration with HP SIM

Architecture overview, 21

Insight Providers, removing

Uninstalling HP Insight Management Agents on a single

local server, 11

Uninstalling HP Insight Management Agents on a single

remote server, 11 integration with HP SIM, 21 introduction, 7

new features

Change Data Source, 13 Threshold settings, 13

overview, WBEM Providers, 7

references, 33 refreshing data, 13 resources

Additional documentation, 27 Reference documentation, 33 Scripting references, 29

scripted uninstallation

Scripting commands for HP Insight Management Agents

7.70 or later, 11 scripting examples, 29 scripting options, 24 scripting, references for, 29 scripts

Microsoft Visual Basic Scripting Edition examples, 24 Scripting examples, 29 Scripting references, 29

WMIC example, 29 security, 15 security considerations

Best practices, 15

Configuring Insight Provider Security for a User Account

using HP SIM Configure and Repair Agents, 15

Configuring Insight Provider Security using the Windows

Command Line, 17 Implementation, 15 Security, 15 Security concerns, 15

SMI-S (Storage Management Initiative Specification), 7 SNMP Agents, uninstalling on single remote server, 11 Storage Management Initiative Specification (SMI-S), 7 System Management Homepage

Auto Refresh, 13 Change Data Source, 13 Data collection, 14 Threshold settings, 13 Using the SMH with the Insight Providers, 13

System Management Homepage, changing data source,

System Management Homepage, creating threshold

settings, 13 System Management Homepage, data collection, 14 System Management Homepage, enabling Auto-Refresh,

technical support

HP contact information, 33 Technical support, 33

thresholds, configuring, 13

uninstalling the AMS

Introduction, 11 Scripting commands for HP Insight Management Agents

7.70 or later, 11 Uninstalling AMS, 11 Uninstalling HP Insight Management Agents on a single

local server, 11

Uninstalling HP Insight Management Agents on a single

remote server, 11 uninstalling the AMS, single local server, 11 uninstalling the SNMP Agents, single remote server, 11 user access

Best practices, 15 Configuring Insight Provider Security for a User Account

using HP SIM Configure and Repair Agents, 15

Configuring Insight Provider Security using the Windows

Command Line, 17

Implementation, 15

WBEM data collection, 14 WBEM Providers, overview, 7 websites

Additional documentation, 27 Insight Providers usage, 27 Reference documentation, 33

Windows Management Instrumentation, 7 Windows Management Instrumentation (WMI), 7 Windows Management Instrumentation Command-line

(WMIC), 29 WMI (Windows Management Instrumentation), 7 WMI Providers, architecture, 21 WMI support, 7 WMIC (Windows Management Instrumentation

Command-line), 29

38 Index

HP Insight Management WBEM Providers User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

HP Insight Management WBEM Providers User Guide

Table of Contents

1 Introduction

Overview

Windows Management Instrumentation

Installing the HP Service Pack Proliant (SPP) Package on Proliant Servers from IP 1.0 Software

Introduction

Uninstalling HP WBEM Provider Components Installed on a single local Proliant Server

Uninstalling HP WBEM Provider Components Installed on a single remote server

Scripting commands for uninstalling HP WBEM Providers

4 Using the SMH with the Insight Providers

Change Data Source

Auto Refresh

Threshold settings

Data collection

5 Security

Security concerns

Implementation

Best practices

Configuring Insight Provider Security for a User Account using HP SIM Configure and Repair Agents

Configuring Insight Provider Security using the Windows Command Line

6 Windows Server® 2008 Firewall configuration

Firewall configuration introduction

Firewall configuration

7 Insight Providers architecture

Architecture overview

Data model

Microsoft Visual Basic Scripting Edition examples

Insight Providers usage

Additional documentation

8 Scripting

Scripting examples

WMIC example

Scripting references

9 Troubleshooting Insight Provider and HP WBEM Tools

Accessing Insight Providers from a client tool or Insight Provider tools

10 Technical support

Reference documentation

HP contact information

Acronyms and abbreviations

Index