HP Insight Management WBEM Providers on Integrity Servers
User's Guide
Abstract
This guide is intended for individuals who are familiar with the configuration and operation of Microsoft® Windows®, Windows
Server® 2008 R2, Windows Server® 2008 SP2, and Web-Based Enterprise Management Providers. Because of the risk of
data loss, only individuals experienced with using this software should implement the procedures in this guide.
HP Part Number: T2369-96024
Published: April 2011
Edition: 5
© Copyright 2011 Hewlett-Packard Development Company, L.P.
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. 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. UNIX is a registered
trademark of The Open Group.
Microsoft, Windows, Vista, and Windows Server are U.S. registered trademarks of Microsoft Corporation.
Contents
About This Document.....................................................................................4
HP Encourages Your Comments..................................................................................................4
1 Introduction...............................................................................................5
Overview................................................................................................................................5
Windows Management Instrumentation.......................................................................................5
Installing and Configuring the WBEM Providers............................................................................5
2 Security.....................................................................................................6
Implementation.........................................................................................................................6
Best Practices...........................................................................................................................6
Configuring Insight Provider Security for a User Account via the Windows® Command Line...............6
3 Microsoft Windows Server™ 2008 Firewall configuration................................8
Configuration...........................................................................................................................8
4 Insight Providers architecture......................................................................10
Data model...........................................................................................................................11
Insight Provider usage.............................................................................................................14
HP Insight Management Services..............................................................................................14
Additional documentation........................................................................................................15
5 Scripting examples...................................................................................16
Microsoft Visual Basic Scripting Edition examples........................................................................16
Other examples......................................................................................................................19
Scripting references.................................................................................................................19
6 Support and other resources......................................................................21
Operating system support........................................................................................................21
Hardware support..................................................................................................................21
Contacting HP........................................................................................................................21
Documentation feedback.........................................................................................................22
Typographic conventions.........................................................................................................22
Typographic Conventions....................................................................................................22
Contents 3
About This Document
HP Encourages Your Comments
4
1 Introduction
This document applies to the HP Insight Management Web-Based Enterprise Management (WBEM)
Providers for Windows Server® 2008 R2 and Windows Server® 2008 SP2 on Integrity servers,
version 7.1.0.0 (Insight Providers).
This release of the Insight Providers supports Integrity servers running Windows Server® 2008 R2
and Windows Server® 2008 SP2. For information regarding supported servers, options, and
operating system versions, see Chapter 6 (page 21).
Overview
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 that are quickly gaining momentum. 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 DMTF, SMASH, and SMI-S profiles. The data model implemented in the Insight
Providers provides industry standard compliance by conforming to DMTF, 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 Integrity-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:
• WBEM (http://www.dmtf.org/standards/wbem/)
• WMI (http://msdn.microsoft.com/library/en-us/wmisdk/wmi/wmi_start_page.asp)
• About WMI (http://msdn.microsoft.com/library/en-us/wmisdk/wmi/about_wmi.asp)
• CIM (http://www.dmtf.org/standards/cim)
Installing and Configuring the WBEM Providers
The WBEM Providers are installed by default when you install the Integrity Support Pack. For
information on configuring the WBEM Providers, see the Windows Server™ 2008 R2 on HP
Integrity Servers Installation Guide and Windows Server™ 2008 SP2 on HP Integrity Servers
Installation Guide.
Overview 5
2 Security
Security is a major concern and one of the primary reasons to switch 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 Windows Management
Instrumentation (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
Provider 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 user group membership
A standard user account needs security configurations to remotely access the Insight Provider
management information on a remote server. For more information, see the Windows Server™
2008 R2 on HP Integrity Servers Installation Guide and Windows Server™ 2008 SP2 on HP
Integrity Servers Installation Guide.
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 on this topic, see Connecting to WMI on a Remote Computer
(http://msdn2.microsoft.com/enus/ library/aa389290.aspx).
Best Practices
According to the principle of least privilege, HP recommends you use a low rights user account
(nonadministrator) to perform most read-only management tasks. Use of certain Insight Provider
functionality always requires an administrator level account. An example of this is a method to
reboot the system. This user does not need to be an administrator of the managed system and does
not need logon rights. HP recommends that the domain administrator creates a special purpose
domain account.
Configuring Insight Provider Security for a User Account via the Windows® Command Line
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 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.
6 Security
3. Invoke the EnableRWMI.exe program to configure the account security for remote WMI
access:
EnableRWMI –a:localuser
Or
EnableRWMI –a:domain\user
Configuring Insight Provider Security for a User Account via the Windows® Command Line 7
3 Microsoft Windows Server™ 2008 Firewall configuration
This section describes a configuration method for enabling direct remote WMI access on a server
running the Microsoft Windows Server 2008 Firewall. These configuration steps were derived
from testing on RC1 of Microsoft Windows Server 2008, and so might not apply to the latest
version of Microsoft 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 System Management Homepage (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.
Apart from setting up the firewall, some user privileges are a consideration in allowing direct
remote WMI access. For example, when the user is not an Administrator, some privileges might
not exist by default.
For more information, see the Microsoft® Windows Server™ 2008 R2 on HP Integrity Servers
Installation Guide, Microsoft® Windows Server™ 2008 SP2 on HP Integrity Servers Installation
Guide, and the Securing a Remote WMI Connection MSDN article at http://msdn2.microsoft.com/
en-us/library/ aa393266.aspx.
Configuration
You can establish direct remote WMI access on a computer running the Windows Server 2008
Firewall, but the default configuration does not allow it. However, by using the built-in firewall
rules, you can enable remote WMI access in as little as two commands.
You execute the following commands locally on the Windows Server 2008 machine that is providing
WMI access (that is, 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 command enables 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 group name with spacing emphasized is below:
”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 allow a remote user to establish a WMI session. You can
enable it 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). You can also be enable it in the
GUI, as follows:
1. Click Administrative Tools→Windows Firewall with Advanced Security→Inbound Rules.
2. Enable the “Network Discovery (NB-Name-In)” rule(s).
3. Select the rule, and click Action→Enable Rule.
This rule and an equivalent rule appear in the Network Discovery and the File and
Printer Sharing firewall rule groups, respectively.
8 Microsoft Windows Server™ 2008 Firewall configuration
If the Windows Firewall has either of these already enabled, this latter command does not affect
a change, and only first command is necessary.
You can create similar rules that are more restrictive, but that allow remote WMI access in specific
circumstances (such as restricting which users, computers, and network addresses can remotely
access), depending on the details of your setup.
There can be additional configuration and connection requirements on the client-side depending
on the client OS and firewall used.
For more information, see Connecting to WMI Remotely Starting with Vista (http://
msdn2.microsoft.com/en-us/library/aa822854.aspx).
Configuration 9
4 Insight Providers architecture
WMI
Browser
HP existing components
Microsoft WMI Framework
HP added components
Custom Scripting
(VBS, Powershell, etc.)
HPQ
namespaces
HP Insight Mana gement WBEM providers
(servers, storage, network, Blad e enclosures)
Insight providers
WebApp
SMH
Framework
WMI Proxy
WMI-W BEM
Mapper
HP SIM
Property pages
Data collection
Identification
Indications
Status polling
DCOM WMI client API
HTTP
WMI Reposi tory
Figure 1 shows an overview of Insight Provider components. The figure is color-coded to distinguish
between Microsoft-provided components, HP components, and Integrity WMI components.
Figure 1 Insight Providers Architecture
The Insight Providers extend the industry-standard CIM data model to support information that is
specific to Integrity 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
10 Insight Providers architecture
◦ Computer system information, including physical location, unit ID visual indicator, IPMI
System Event Log (SEL), 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 Megabit Ethernet
◦ Gigabit Ethernet
◦ NIC teaming
• Storage providers
Storage controller information and indications◦
◦ Ultra320 SCSI
◦ SmartArray
◦ SAS/SATA information
◦ Fibre Channel HBA information
• Other Providers
C-Class blade enclosure provider—Enclosure information for c-Class blades◦
◦ Management processor provider—Management processor information
◦ Software inventory provider—Installed HP software and firmware information
◦ Indications to event log provider—Insight Provider indications that are logged to the
Data model
Table 1 lists the set of DMTF profiles included in the data model implemented by this version of
the Insight Providers.
Table 1 DMTF profiles included in the data model
(specialized)
Windows® system event log
1.0.0DSP1004 – Base Server Profile
1.0.2DSP1009 – Sensor Profile
1.0.1DSP1010 – Record Log Profile
1.0.2DSP1011 – Physical Asset Profile
1.0.1DSP1013 – Fan Profile
LinkVersionProfile Name
http://www.dmtf.org/standards/published_documents/
DSP1004_1.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
(specialized)
1.0.0DSP1014 – Ethernet Port Profile
1.1.0DSP1015 – Power Supply Profile
1.0.0DSP1022 – CPU Profile
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
Data model 11
Table 1 DMTF profiles included in the data model (continued)
LinkVersionProfile Name
Profile
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 Profile
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/standards/published_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
Table 2 lists the set of SMI-S profiles, subprofiles, and packages included in the data model
implemented by this version of the Insight Providers.
Table 2 SMI-S profiles, subprofiles and packages included in the data model
VersionProfile/Subprofile Name
1.4.4Host Hardware RAID Controller 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
12 Insight Providers architecture
1.2.0FC HBA Profile
1.2.0Host Discovered Resources Profile
1.3.0Media Access Device Profile
Table 2 SMI-S profiles, subprofiles and packages included in the data model (continued)
VersionProfile/Subprofile Name
1.2.0SAS Target Port Subprofile
1.2.0SPI Target Port Subprofile
Table 3 lists the set of HP profile extensions included in the data model implemented by this version
of the Insight Providers.
Table 3 HP profile extensions included in the data model
File NameVersionProfile Name
P00100_-_HP_Profile_Registration Profile.pdf1.0.0P00100 – HP Profile Registration
Profile
P00101_-_HP_Mgmt_Proc_Lite_Profile.pdf2.0.1P00101 – 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.pdf1.5.0P00105 – HP Base Server Profile
P00106_-_HP_CPU_Profile.pdf1.0.0P00106 – HP CPU Profile
Status Profile
Profile
Profile
Profile
Asset Profile
Profile
Asset Profile
Profile
P00107_-_HP_CPU_Consolidated_Status_Profile.pdf1.0.0P00107 – HP CPU Consolidated
P00108_-_HP_CPU_Physical_Asset_Profile.pdf1.0.0P00108 – HP CPU Physical Asset
P00109_-_HP_Record_Log_Profile.pdf1.1.0P00109 – HP Record Log Profile
P00110_-_HP_Memory_Profile.pdf1.0.0P00110 – HP Memory 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
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.4P00119 – HP FC HBA Profile
P00120_-_HP_Storage_Enclosure_Profile.pdf1.0.1P00120 – HP Storage Enclosure
P00121_-_HP_Smart_Array_Profile.pdf1.4.4P00121 – HP Smart Array Profile
P00122_-_HP_SAS_HBA_Profile.pdf1.0.1P00122 – 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
Data model 13
Table 3 HP profile extensions included in the data model (continued)
Profile
Profile
Insight Provider usage
You access data and events from the Insight Providers using the SMH supplied in the Integrity
Support Pack (ISP), HP SIM, other client application, or script 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 parts:
• The HP System Management Homepage for Windows Smart Component that is included with
the Integrity Support Pack for Windows. This is the SMH framework.
• The web application plug-in that is installed with the Insight Providers. This provides the web
pages that show management data using the Insight Providers.
HP SIM 5.2 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 5.2 Technical
Reference Guide.
Any client application or script that supports 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 information, see
the following WMI references on the MSDN website:
File NameVersionProfile Name
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
• 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 Chapter 5 (page 16).
Specific information about HP Integrity 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” (page 15)).
HP Insight Management Services
The Integrity WBEM Providers Smart Component includes the following components:
Predictive Failure Monitor Enables a service that monitors failures in the system and
Event subsystem information Enables a service that monitors events from the System Events
Automatic Server Recovery Enables a service that verifies if the system is frozen and
that generates events when specific thresholds are reached.
Currently monitored failures include memory errors, internal
cache errors, external cache for MX2 processor errors,
fabric errors, Enhanced Thermal Management, Front Side
Bus, and Intel Cache Safe Performance Technology
performance errors.
Log (SEL), Forward Process Log (FPL), and management
Processor (MP).
reboots the system automatically (if frozen).
14 Insight Providers architecture
Additional documentation
In addition to this User Guide, the following Insight Provider documentation is available at http://
www.hp.com/go/hpwbem:
• Profiles — A separate document exists for each HP profile extension.
• Provider Data Sheet, HP Insight Management WBEM Provider Data Sheet for
Integrity Servers.pdf —This document describes indication details and class
implementations not defined in an MOF or profile.
• 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 Integrity-specific
extensions.
• Event and Indication Reference, HP Management WBEM Events and Indications
Reference.pdf — This document lists all the events logged to the Windows System Log
and the indications generated by the Integrity WBEM providers.
Additional documentation 15
5 Scripting examples
This section provides examples for accessing data exposed by the Insight Providers using scripting.
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. This section
shows examples for accessing Insight Provider data using VBScript code.
16 Scripting examples
Example 1 Displaying computer 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
Example 2 Displaying the 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
Example 3 Displaying 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
Microsoft Visual Basic Scripting Edition examples 17
Example 4 Listing 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
Example 5 Listing system processors, current clock speed, and the number of enabled cores
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
Example 6 Listing 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
18 Scripting examples
Example 7 Clearing 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
Example 8 Receiving 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
Other examples
You can also write scripts to obtain data from the Insight Providers using Microsoft Windows
Management Instrumentation Command-line (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:
• 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)
Other examples 19
• WMI Command-line (http://msdn2.microsoft.com/en-us/library/aa394531.aspx)
• Windows PowerShell (http://msdn2.microsoft.com/en-us/library/bb905330.aspx)
• WMIC (http://msdn2.microsoft.com/en-us/library/aa394531.aspx)
20 Scripting examples
6 Support and other resources
Operating system support
Table 4 lists the operating systems supported by version 7.1.0.0 of the Insight Providers. For
information about the operating system versions supported by each server platform, see the Windows
Server Operating System Support on HP Servers website at http://h10018.www1.hp.com/
wwsolutions/windows/index-all.html.
Table 4 Supported operating systems
Hardware support
The following HP Integrity servers are supported:
• rx2660
• rx2800 i2
• rx3600
CommentsOperating System
Supported with Service Pack 2 onlyMicrosoft Windows Server 2008 (English and Japanese)
Supported with and without Service Pack 1Microsoft Windows Server 2008 R2 (English and Japanese)
• rx6600
• rx7640
• rx8640
• HP Integrity BL860c
• HP Integrity BL870c
• HP Integrity BL860c i2
• HP Integrity BL870c i2
• HP Integrity BL890c i2
• HP Integrity Superdome Server sx2000
Contacting HP
For the name of the nearest HP authorized reseller:
In the United States, see the HP US service locator webpage at:
http://www.hp.com/service_locator
In other locations, see the Contact HP worldwide (in English) webpage at:
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 at:
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.
Operating system support 21
If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information
about Care Packs, see the HP website at http://www.hp.com.
In other locations, see the Contact HP worldwide (in English) webpage at:
http://welcome.hp.com/country/us/en/wwcontact.html
Documentation feedback
HP welcomes your feedback. To make comments and suggestions about this document, send a
message to http://www.hp.com/bizsupport/feedback/ww/webfeedback.html.
Include the document title and manufacturing part number. All submmissions become the property
of HP.
Typographic conventions
Typographic Conventions
This document uses the following typographical conventions:
Command A command name or qualified command phrase.
Computer output Text displayed by the computer.
Ctrl+x A key sequence. A sequence such as Ctrl+x indicates that you
ENVIRONMENT VARIABLE The name of an environment variable, for example, PATH.
must hold down the key labeled Ctrl while you press another key
or mouse button.
ERROR NAME The name of an error, usually returned in the errno variable.
User input Commands and other text that you type.
Variable The name of a placeholder in a command, function, or other
syntax display that you replace with an actual value.
[] The contents are optional in syntax. If the contents are a list
separated by |, you must choose one of the items.
{} The contents are required in syntax. If the contents are a list
separated by |, you must choose one of the items.
| Separates items in a list of choices.
WARNING A warning calls attention to important information that if not
understood or followed will result in personal injury or
nonrecoverable system problems.
CAUTION A caution calls attention to important information that if not
understood or followed will result in data loss, data corruption,
or damage to hardware or software.
IMPORTANT This alert provides essential information to explain a concept or
to complete a task
NOTE A note contains additional information to emphasize or supplement
important points of the main text.
22 Support and other resources
Loading...