HP WBEM Providers for OpenVMS_______________________ Installation and Administrator's Guide February 2011 This document describes how to install and administer the Web-Based Enterprise Management (WBEM) Providers software and its components. Revision/Update Information: This is a revised manual. Operating System: OpenVMS Version 8.4 for Integrity servers Software Version: HP WBEM Providers for OpenVMS, Version 2.2-3 Hewlett-Packard Company Palo Alto, California ________________________________________________________________ © 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. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Windows is a U.S. registered trademark of Microsoft Corporation. _________________________________________________________________ Contents Preface................................................... v 1 Introduction 1.1 Overview...................................... 1-1 1.2 Features and Benefits......................... 1-1 1.3 WBEM Providers Product Components............. 1-3 1.3.1 Instance Providers........................ 1-3 1.3.2 Indication Providers...................... 1-7 1.3.3 OpenVMS Event Monitoring Service.......... 1-8 1.3.4 WBEM Utilization Provider Daemon.......... 1-9 1.3.5 WBEM Set Host Parameters Daemon........... 1-9 1.4 HP Systems Insight Manager.................... 1-9 1.5 Architecture on Integrity server Systems...... 1-9 2 Installing the WBEM Providers Software 2.1 Prerequisites................................. 2-1 2.2 Installing the WBEM Providers Software on an OpenVMS Integrity server...................... 2-2 2.3 Configuring the WBEM Providers Software....... 2-4 2.4 Configuring WBEM Services for OpenVMS to Support HP SIM................................ 2-6 2.5 Deconfiguring the WBEM Providers Software..... 2-7 2.6 Removing the WBEM Providers Software.......... 2-12 2.7 Testing the WBEM Providers Instances.......... 2-12 iii 3 Administering Indications and Instances Using HP SIM 3.1 Prerequisites for HP SIM...................... 3-1 3.1.1 Setting the Global Protocol............... 3-2 3.1.2 Discovering a System...................... 3-2 3.1.3 Identifying a System...................... 3-3 3.2 Subscribing to Indications (Events)........... 3-4 3.3 Unsubscribing to Indications (Events)......... 3-5 3.4 Viewing Indications (Events).................. 3-5 3.5 Viewing Instances............................. 3-6 Glossary Index Tables 1-1 Instance Providers........................ 1-3 1-2 Indication Providers...................... 1-7 iv _________________________________________________________________ Preface About This Document This document describes how to install and administer the Web-Based Enterprise Management Providers, herein after referred to as WBEM Providers software. Document updates may be issued between editions to correct errors or to document product changes. Intended Audience This document is intended for system administrators responsible for installing and managing remote systems using the WBEM Providers software. This document is also intended for users working on the client systems. Administrators and users are expected to have knowledge of operating system concepts and commands. This document is not a tutorial. Document Structure HP WBEM Providers Installation and Administrator's Guide is organized as follows: Chapter 1 Introduction Introduces the WBEM Providers software. It also discusses the features and benefits of this software, and the architecture of the WBEM Providers software. v Chapter 2 Installing the WBEM Providers Software Describes how to install, configure, deconfigure, and remove the WBEM Providers software. Chapter 3 Administering Indications and Instances Using HP SIM Describes how to use the HP Systems Insight Manager (HP SIM) Graphical User Interface (GUI) to administer indications and view instances on remote systems. Related Information The WBEM Providers product documentation is available at the following website: http://h71000.www7.hp.com/doc/wbem.html The following documents support this version of the WBEM Providers for OpenVMS software: o HP WBEM Providers Release Notes o HP WBEM Providers Installation and Administrator's Guide o HP WBEM Providers Data Sheets o HP WBEM Providers Events List Reader's Comments HP welcomes your comments on this manual. Include the document title, manufacturing part number, and any comment, error found, in this document. Also, include what we did right, so we can incorporate it into other documents. Send your comments or suggestions to openvmsdoc@hp.com. vi Conventions The following conventions are used in this manual: Ctrl/x A sequence such as Ctrl/x indicates that you must press and hold the key labeled Ctrl while you press another key or a pointing device button. . . . A horizontal ellipsis in examples indicates one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. Monospace text Monospace type indicates code examples and interactive screen displays. In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example. - A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line. italic text Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where dd represents the predefined code for the device type). vii UPPERCASE Uppercase text indicates the name of a routine, the name of a file, the name of a file protection code, or the abbreviation for a system privilege. ( ) In command format descriptions, parentheses indicate that you must enclose the options in parentheses if you specify more than one. [ ] In command format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets must be included, however, in the syntax of a directory name in an OpenVMS file specification or in the syntax of a substring specification in an assignment statement.) $ user input User input is shown in bold. $ The dollar sign is used to indicate the DCL prompt on OpenVMS systems. viii 1 _________________________________________________________________ Introduction This chapter introduces the WBEM Providers software and the tools that this software includes. It also discusses the features and benefits of the WBEM Providers software, and their architecture on Integrity server systems. This chapter addresses the following topics: o Overview o Features and Benefits o WBEM Providers Product Components o HP Systems Insight Manager o Architecture on Integrity Server Systems 1.1 Overview The WBEM Providers software is a collection of tools that enables you to monitor the health of HP servers running HP OpenVMS. This software retrieves information about hardware devices such as CPU, memory, power supply, and cooling devices. It operates within the WBEM environment. 1.2 Features and Benefits On request, the WBEM Providers software queries property information about a hardware device on a local or remote system. It offers the following features and benefits: o Displays information on standards-compliant graphical and command-line system management applications, such as HP SIM. o Operates within the WBEM environment. o Enables you to view and administer the WBEM indications. Introduction 1-1 Introduction 1.2 Features and Benefits o Enables you to view the WBEM instances. 1-2 Introduction Introduction 1.3 WBEM Providers Product Components 1.3 WBEM Providers Product Components The WBEM Providers software comprises instance providers, indication providers and supporting daemons. This section describes these components. 1.3.1 Instance Providers Table 1-1 lists the instance providers. Table_1-1_Instance_Providers_______________________________ Instance_Provider_____Description__________________________ (continued on next page) Introduction 1-3 Introduction 1.3 WBEM Providers Product Components Table_1-1_(Cont.)_Instance_Providers_______________________ Instance_Provider_____Description__________________________ CPU The CPU Instance Provider retrieves the following types of information: o Logical processor information, such as the following: - Current clock speed - Processor family - Processor status information, including configuration and deconfiguration, failure status, and active and inactive status - Load percentage o Physical processor chip information, such as chip revisions and architecture revisions o Location details, such as the following: - Location attributes such as cabinet number, cell number, slot number, and so on. Instance providers display or retrieve information only for the filled slots - Processor IDs (continued on next page) 1-4 Introduction Introduction 1.3 WBEM Providers Product Components Table_1-1_(Cont.)_Instance_Providers_______________________ Instance_Provider_____Description__________________________ Memory The Memory Instance Provider retrieves the following types of information: o Memory slot information o Memory module information, such as the following: - Serial number - Part number - Memory capacity - Module form factor - Module status (for example, configuration status and failure status) Environmental The Environmental Instance Provider retrieves information about the following hardware components: o Fans o Power supply o Bulk power supply o AC input lines They also retrieve consolidated health of cooling, and power subsystems on HP servers. On the Blade systems, the cooling and power information is not displayed, as the cooling and power devices are connected to enclosure and not to individual blades. (continued on next page) Introduction 1-5 Introduction 1.3 WBEM Providers Product Components Table_1-1_(Cont.)_Instance_Providers_______________________ Instance_Provider_____Description__________________________ Computer System Retrieves the HP base server physical Chassis Instance asset information of the system from Provider HP Integrity servers. The provider retrieves properties such as the serial number, product ID, and Logical Universally Unique ID (UUID). Firmware Revision The Firmware Revision Instance Provider retrieves firmware revision information for firmwares present on the managed system and their related details. Management Processor The MP Instance Provider retrieves (MP) information about the Management Processor of the managed system. Enclosure/Blade OA The Enclosure Instance Provider retrieves information about the Rack/Enclosure and the blade on an Integrity server blade system. Utilization Retrieves information about the CPU, memory, disk and network utilization. OPENVMS_UTILD is a process that runs in the background, and it is required by the utilization provider. LAN Retrieves the consolidated status of the Ethernet interfaces. VM Retrieves the information about the underlying Integrity VM Host on which ______________________the_OpenVMS_guest_is_hosted._________ ________________________ Note ________________________ The CPU Instance Provider, Memory Instance Provider, Environmental Instance Provider, Management Processor Provider and Enclosure/Blade OA Instance Provider are not supported on HP VM OpenVMS Guest, since the guest runs in a virtual system. For information about hardware devices present on the underlying VM host, 1-6 Introduction Introduction 1.3 WBEM Providers Product Components use WBEM Providers running on the VM host operating system. ______________________________________________________ 1.3.2 Indication Providers Table 1-2 lists the indication providers. Table_1-2_Indication_Providers_____________________________ Indication_Provider___Description__________________________ EMS Wrapper Provider The EMS Wrapper Provider performs the following tasks: o Converts hardware events captured by the OpenVMS EMS component into WBEM indications. o Common Information Model Object Manager (CIMOM) is a component of WBEM that manages the interaction between the providers and other modules in the WBEM environment. CIMOM manages CIM objects. It receives and processes CIM operation requests and issues responses. The EMS Wrapper Provider reports the WBEM indications to the CIMOM. Using a management application, such as HP SIM, you can subscribe to and receive OpenVMS EMS events generated on a remote system. (continued on next page) Introduction 1-7 Introduction 1.3 WBEM Providers Product Components Table_1-2_(Cont.)_Indication_Providers_____________________ Indication_Provider___Description__________________________ LAN Indication LAN Indication Provider delivers Provider indications for events that occur on Ethernet interfaces. Client applications can subscribe and start receiving indications based on events generated by Ethernet interfaces. Supported indications are: o Link down for unknown reasons o Link up ___________________________________________________________ ________________________ Note ________________________ The terms events and indications are used interchangeably. ______________________________________________________ 1.3.3 OpenVMS Event Monitoring Service OpenVMS Event Monitoring Service, herein after referred to as OpenVMS EMS is a component that is included in the WBEM Providers software. This component monitors and captures the hardware events and saves them in an OpenVMS index file. OPENVMS_EMS process gathers the events for the EMS Wrapper Provider. The EMS Wrapper Provider queries the index file and wraps these hardware indications (events). OpenVMS EMS supports the following types of hardware monitors: o IA64 Core Hardware Monitor (Events) o IPMI Forward Progress Log Monitor (Events) For a list of events that can be generated on OpenVMS, see HP WBEM Providers Events List available at: http://h71000.www7.hp.com/doc/wbem.html 1-8 Introduction Introduction 1.3 WBEM Providers Product Components 1.3.4 WBEM Utilization Provider Daemon The WBEM Utilization Provider Daemon (OPENVMS_UTILD) is a process that runs in the background to gather and record utilization of the CPU, Memory, LAN and disk resources on the system. It is required by the Utilization Provider. 1.3.5 WBEM Set Host Parameters Daemon The WBEM Set Host Parameters Daemon (WBEMPROV$HOST_P) is a process that runs in the background, and sets host-related parameters (host name, Operating System name & version, and System Management Homepage URL) on the Integrated Lights- Out (iLO) or Management Processor (MP). 1.4 HP Systems Insight Manager HP Systems Insight Manager (HP SIM) is the foundation for HP's unified server-storage management strategy. It is a multiple operating system and a hardware level management product. HP SIM provides the basic management features of system discovery and identification, single event view, inventory data collection, and reporting. This software is a web-based user interface that enables you to control and monitor resources within a large environment on OpenVMS. You can use HP SIM for creating subscriptions, event handling, provisioning, and viewing the indications and instances, among many other functions, on a remote system. You must install HP SIM on the Central Management Server (CMS) run on Microsoft Windows. 1.5 Architecture on Integrity server Systems This section illustrates the architecture of the WBEM Providers software installed on an Integrity server client system. The client system is managed by the CMS. Processing a request for information involves the following steps: 1. The CIMOM receives requests from the CMS for device information. 2. The CIMOM converts the requests to a format that is read by the WBEM Providers software and directs the requests to the appropriate provider, for example, the CPU Instance Provider. Introduction 1-9 Introduction 1.5 Architecture on Integrity server Systems 3. The WBEM Providers software queries the associated hardware device for property information. 4. The WBEM Providers software returns the query information to the CIMOM. 5. The CIMOM conveys the responses from the provider to the CMS. The OpenVMS EMS monitors and captures the hardware events required by OpenVMS. The EMS Wrapper Provider wraps the events and retrieves the information. ________________________ Note ________________________ Information can be viewed using HP SIM on the remote system. ______________________________________________________ 1-10 Introduction 2 _________________________________________________________________ Installing the WBEM Providers Software The WBEM Providers software is installed by default with the HP OpenVMS Operating Environment (OE) media. However, at some point you may need to install the WBEM Providers software separately. This chapter describes how to install the WBEM Providers software as a standalone component on the OpenVMS operating system. It also describes how to configure and remove the WBEM Providers software. In addition, it describes how to test the WBEM Providers instances. This chapter addresses the following topics: o Prerequisites o Installing the WBEM Providers Software on an OpenVMS Integrity server o Configuring the WBEM Providers Software o Configuring WBEM Services for OpenVMS to Support HP SIM o Deconfiguring the WBEM Providers Software o Removing the WBEM Providers Software o Testing the WBEM Providers Instances 2.1 Prerequisites Following are the prerequisites for installing the WBEM Providers software: o HP OpenVMS Version 8.4 for Integrity servers o HP WBEM Services for OpenVMS, Version 2.9-9 o HP TCP/IP Stack Installing the WBEM Providers Software 2-1 Installing the WBEM Providers Software 2.1 Prerequisites o Latest SYS and UPDATE patches ________________________ Note ________________________ On the rx2800 i2 servers, you must have the VMS84I_UPDATE-V0500 or later update kit installed and running before installing WBEM Providers. On the BL860c i2, BL870c i2, and BL890c i2 server blades, you must have the VMS84I_UPDATE-V0200 or later update kit installed and running before installing WBEM Providers. ______________________________________________________ ________________________ Note ________________________ The WBEM Providers kit is supported for installation only on the OpenVMS system disk. Installation of WBEM Providers kit on a non-system disk is not supported. ______________________________________________________ ________________________ Note ________________________ HP recommends that you install HP SIM to remotely administer indications and instances. ______________________________________________________ 2.2 Installing the WBEM Providers Software on an OpenVMS Integrity server This section describes how to install the WBEM Providers software using the POLYCENTER Software Installation (PCSI) utility. To install the WBEM Providers software, follow these steps: 1. Log on to the system with the SYSTEM account. 2. Ensure that the WBEM Providers software kit and manifest files are in the current directory. 3. Enter the following command at the command prompt: $ PRODUCT INSTALL WBEMPROVIDERS An output similar to the following is displayed. When the system asks whether you want to continue with the installation, answer YES. 2-2 Installing the WBEM Providers Software Installing the WBEM Providers Software Installing the WBEM Providers Software on an OpenVMS Integrity server Performing product kit validation ... %PCSI-I-VALPASSED, validation of _$1$DGA413:[KITS.IA64.WBEMPROVIDERS] HP-I64VMS-WBEMPROVIDERS-V0200-3-1.PCSI;1 succeeded%PCSI The following product has been selected: HP I64VMS WBEMPROVIDERS V2.0-3 Layered Product Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. Configuring HP I64VMS WBEMPROVIDERS V2.0-3: HP WBEM providers for OpenVMS I64 2007 Hewlett-Packard Development Company, L.P. All rights reserved. Hewlett Packard Company * This product does not have any configuration options. Execution phase starting ... The following product will be installed to destination: HP I64VMS WBEMPROVIDERS V2.0-3 DISK$ORANGE-1H1:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: HP I64VMS WBEMPROVIDERS V2.0-3 Layered Product The shareable images and other files are copied to the following locations: o The shareable images are copied to SYS$SHARE o The common files are copied to SYS$COMMON:[WBEMPROVIDERS] o The Managed Object Format (MOF) files are copied to SYS$COMMON:[WBEMPROVIDERS.MOF] o The documentation files are are available for download at: http://h71000.www7.hp.com/doc/wbem.html Installing the WBEM Providers Software 2-3 Installing the WBEM Providers Software 2.2 Installing the WBEM Providers Software on an OpenVMS Integrity server o The configuration and deconfiguration command procedure files are copied to SYS$COMMON:[WBEMPROVIDERS] 2.3 Configuring the WBEM Providers Software After the installation of the WBEM Providers software for OpenVMS, to configure the WBEM Providers software, follow these steps: 1. Log on to the system with the SYSTEM account, if you are have logged on using a different account. 2. To define the WBEM Services logicals, enter the following command: $ @SYS$COMMON:[WBEM_SERVICES]WBEM_SERVICES$DEFINE_COMMANDS.COM 3. Ensure that the CIM Server is running and verify the list of Providers installed by entering the following command: $ CIMPROVIDER -L -S An output similar to the following is displayed: MODULE STATUS OperatingSystemModule OK ComputerSystemModule OK ProcessModule OK IPProviderModule OK 4. To configure the WBEM Providers software, enter the following command: $ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM Enter the "Primary Owner name" and "Primary owner contact" when prompted. If you want to change the "Primary Owner name" and "Primary owner contact", edit the SYS$SPECIFIC:[WBEMPROVIDERS]WBEMPROVIDERS$LOGICALS.COM and change the "WBEM_PRIMARY_OWNER" and "WBEM_PRIMARY_ OWNER_CONTACT" logical definitions appropriately. 2-4 Installing the WBEM Providers Software Installing the WBEM Providers Software 2.3 Configuring the WBEM Providers Software The configuration process takes a few minutes to complete. An output similar to the following is displayed: %WBEMPROVIDERS-I-STARTING, Info:Starting WBEMPROVIDERS Configuration. Enter Primary Owner name of the system: system Enter Primary owner contact information: 25166235 %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of EventIndicationConsumerModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of EMSWrapperProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HPVMSLANIndicationProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of StateChangeIndicationProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of ChassisProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of cpuprovidermodule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of MemoryModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of FirmwareRevisionProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of MPProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of EnclosureProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HPHealthStateProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HPVMSLANProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HPVMSLANCSProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of CSChassisProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HPVMProviderModule... %WBEMPROVIDERS-I-CONTINUECONFIG, Info:configuration of HP_UtilizationProviderModule... %WBEMPROVIDERS-I-STARTING , Info:Starting OPENVMS_UTILD Process. %RUN-S-PROC_ID, identification of created process is 21A0B046 %WBEMPROVIDERS-I-WAIT, Info:Inventory is not ready..! Waiting for 2 Minutes %WBEMPROVIDERS-I-STARTING , Info:Starting OPENVMS_EMS Process. %RUN-S-PROC_ID, identification of created process is 21A0B047 %WBEMPROVIDERS-I-STARTING , Info:Starting WBEMPROV$HOST_P Process. %RUN-S-PROC_ID, identification of created process is 21A0B048 %WBEMPROVIDERS-I-PROVCONFIG, Info:Completed configuration of WBEMPROVIDERS. This command procedure registers the WBEM Providers software with the CIM Server and copies the node specific files to SYS$SPECIFIC:[WBEMPROVIDERS] 5. Verify the list of providers installed and their status by entering the following command: $ CIMPROVIDER -L -S Installing the WBEM Providers Software 2-5 Installing the WBEM Providers Software 2.3 Configuring the WBEM Providers Software An output similar to the following is displayed along with the WBEM Services providers: MODULE STATUS OperatingSystemModule OK ComputerSystemModule OK ProcessModule OK IPProviderModule OK EventIndicationConsumerModule OK EMSWrapperProviderModule OK HPVMSLANIndicationProviderModule OK StateChangeIndicationProviderModule OK ChassisProviderModule OK cpuprovidermodule OK MemoryModule OK FirmwareRevisionProviderModule OK MPProviderModule OK EnclosureProviderModule OK HPHealthStateProviderModule OK HPVMSLANProviderModule OK HPVMSLANCSProviderModule OK CSChassisProviderModule OK HPVMProviderModule OK HP_UtilizationProviderModule OK 2.4 Configuring WBEM Services for OpenVMS to Support HP SIM For HP SIM to discover an OpenVMS system, follow these steps to configure WBEM Services for OpenVMS to support HP SIM before discovering a system: 1. Log on to the system with the SYSTEM account, if you have logged on using a different account. 2. To define the WBEM Services logicals, enter the following command: $ @SYS$COMMON:[WBEM_SERVICES]WBEM_SERVICES$DEFINE_COMMANDS.COM 3. Add the username that you want to use in HP SIM to access the system, by entering the following command: $ CIMUSER -A -U "" 2-6 Installing the WBEM Providers Software Installing the WBEM Providers Software 2.4 Configuring WBEM Services for OpenVMS to Support HP SIM Where: is an user account on the OpenVMS system, which must be provided again while setting the Global Protocol Settings on HP SIM. For example, $ CIMUSER -A -U "system" Ensure that the user name is case sensitive. The same name must be provided in the HP SIM protocol settings. Executing this command prompts you to enter the password for the on the OpenVMS system. Enter the password. ________________________ Note ________________________ Use the command CIMUSER -R -U to remove the added Cimuser. For more information about Cimuser commands, enter the CIMUSER -HELP command. ______________________________________________________ 2.5 Deconfiguring the WBEM Providers Software To deconfigure the WBEM Providers software, follow these steps: 1. Log on to the system with the SYSTEM account, if you have logged on using a different account. 2. To define the WBEM Services logicals, enter the following command: $ @SYS$COMMON:[WBEM_SERVICES]WBEM_SERVICES$DEFINE_COMMANDS.COM 3. Ensure that the CIM Server is running, and verify the list of Providers installed by entering the following command: $ CIMPROVIDER -L -S An output similar to the following is displayed: Installing the WBEM Providers Software 2-7 Installing the WBEM Providers Software 2.5 Deconfiguring the WBEM Providers Software MODULE STATUS OperatingSystemModule OK ComputerSystemModule OK ProcessModule OK IPProviderModule OK EventIndicationConsumerModule OK EMSWrapperProviderModule OK HPVMSLANIndicationProviderModule OK StateChangeIndicationProviderModule OK ChassisProviderModule OK cpuprovidermodule OK MemoryModule OK FirmwareRevisionProviderModule OK MPProviderModule OK EnclosureProviderModule OK HPHealthStateProviderModule OK HPVMSLANProviderModule OK HPVMSLANCSProviderModule OK CSChassisProviderModule OK HPVMProviderModule OK HP_UtilizationProviderModule OK 4. To deconfigure the WBEM Providers software, enter the following command: $ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$DECONFIGURE.COM The deconfiguration process displays the following sample output and prompts you to remove the files. Answer YES if you want to completely remove the product specific files. Answer NO if you intend to upgrade to a higher version of the WBEM Providers software. This process also unregisters the WBEM Providers software. 2-8 Installing the WBEM Providers Software Installing the WBEM Providers Software 2.5 Deconfiguring the WBEM Providers Software %WBEMPROVIDERS-I-PROVDECONFIG, Info:De-configuration procedure for WBEM Providers. OperatingSystem Information Host: orange Name: OpenVMS Version: V8.4 UserLicense: Unlimited user license Number of Users: 2 users Number of Processes: 46 processes OSCapability: 64 bit LastBootTime: Jul 30, 2009 9:57:55 (-0500) LocalDateTime: Aug 20, 2009 0:31:34 (-0500) SystemUpTime: 1780419 seconds = 20 days, 14 hrs, 33 mins, 39 secs Deconfiguration is going to remove all the Providers and Restart Cimserver. Do you want to continue?(Y/N) [Y]: %WBEMPROVIDERS-I-STOP, Info: Stopping the OpenVMS_EMS process %WBEMPROVIDERS-I-STOP, Info: Stopping the WBEMPROV$HOST_P process %WBEMPROVIDERS-I-DEL, Info:Deleting the Obsolete files from SYS$SPECIFIC:[WBEMPROVIDERS] directory %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of HPHealthStateProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of cpuprovidermodule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of MemoryModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of ChassisProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of FirmwareRevisionProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of EventIndicationConsumerModule... Installing the WBEM Providers Software 2-9 Installing the WBEM Providers Software 2.5 Deconfiguring the WBEM Providers Software Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of StateChangeIndicationProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of EMSWrapperProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of MPProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of EnclosureProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of HPVMSLANProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of HPVMSLANCSProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of HPVMSLANIndicationProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of CSChassisProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... 2-10 Installing the WBEM Providers Software Installing the WBEM Providers Software 2.5 Deconfiguring the WBEM Providers Software Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of HPVMProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DECONFPROV, Info:De-configuration of HP_UtilizationProviderModule... Disabling provider module... Provider module disabled successfully. Deleting provider module... Provider module deleted successfully. %WBEMPROVIDERS-I-DEL, Info:Deleting Log/Temporary files generated by WBEMProviders %WBEMCIM-I-SHUTDOWN, Shutting down WBEM Services for OpenVMS... %WBEMCIM-I-SHUTDOWNCS, Shutting down CIMServer.exe... CIM Server stopped. %WBEMCIM-I-SERVERWAIT, Waiting for CIMServer to shut down. 60 seconds remaining... %WBEMCIM-S-STARTSTOP, CIMServer has stopped. %WBEMCIM-I-SHUTDOWNCSSUCCESS, Shutdown of CIMServer.exe successful. sts=%X00000001. %RUN-S-PROC_ID, identification of created process is 21A0B070 %WBEMCIM-I-SERVERWAIT, Waiting for CIMServer to start. 180 seconds remaining... %WBEMCIM-S-STARTSTOP, CIMServer successfully started. OperatingSystem Information Host: orange Name: OpenVMS Version: V8.4 UserLicense: Unlimited user license Number of Users: 2 users Number of Processes: 43 processes OSCapability: 64 bit LastBootTime: Jul 30, 2009 9:57:55 (-0500) LocalDateTime: Aug 20, 2009 0:35:13 (-0500) SystemUpTime: 1780638 seconds = 20 days, 14 hrs, 37 mins, 18 secs %WBEMPROVIDERS-I-PROVDECONFIG, Info:De-configuration of WBEMProviders successful. 5. To ensure that the WBEM Providers software is unregistered, query the CIM server by entering the following command: $ CIMPROVIDER -L -S The providers that were displayed earlier will not be displayed now. Installing the WBEM Providers Software 2-11 Installing the WBEM Providers Software 2.5 Deconfiguring the WBEM Providers Software 6. To ensure that all the shareable images are unloaded from the CIM Server image, restart the CIM Server after deconfiguration by entering the following command: $ @SYS$STARTUP:WBEM_SERVICES$SHUTDOWN.COM Wait for few minutes for the process to complete, and enter the following command: $ @SYS$STARTUP:WBEM_SERVICES$STARTUP.COM 2.6 Removing the WBEM Providers Software To remove the WBEM Providers software, complete the deconfiguration steps described in the Section 2.5 "Deconfiguring the WBEM Providers Software" and enter the following command at the command prompt: $ PRODUCT REMOVE WBEMPROVIDERS An output similar to the following is displayed: The following product has been selected: HP I64VMS WBEMPROVIDERS V2.0-3 Layered Product Do you want to continue? [YES] The following product will be removed from destination: HP I64VMS WBEMPROVIDERS V2.0-3 DISK$ORANGE-1H1:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been removed: HP I64VMS WBEMPROVIDERS V2.0-3 Layered Product 2.7 Testing the WBEM Providers Instances To test the WBEM Providers instances, follow these steps: 1. To define the WBEM Services logicals, enter the following command: $ @SYS$COMMON:[WBEM_SERVICES]WBEM_SERVICES$DEFINE_COMMANDS.COM 2. A set of XML files are provided in the SYS$COMMON:[WBEMPROVIDERS.TEST] directory that can be used to test the WBEM Providers software. The name of the XML file indicates the Provider that you want to test. Enter the following commands to generate instances using the WBEMEXEC request and the XML file: 2-12 Installing the WBEM Providers Software Installing the WBEM Providers Software 2.7 Testing the WBEM Providers Instances $ SET DEF SYS$COMMON:[WBEMPROVIDERS.TEST] $ WBEMEXEC For example, $ SET DEF SYS$COMMON:[WBEMPROVIDERS.TEST] $ WBEMEXEC CS_ENUMERATE_INSTANCES.XML ! Enumerates instances of the CS provider $ WBEMEXEC CS_ENUMERATE_INSTANCE_NAMES.XML ! Enumerates instance names of the ! CS Provider Installing the WBEM Providers Software 2-13 3 _________________________________________________________________ Administering Indications and Instances Using HP SIM This chapter describes how to administer the WBEM Providers software using HP SIM. ________________________ Note ________________________ You can perform similar tasks using other management applications that are compliant with the Common Information Model (CIM) schema of the Distributed Management Task Force (DMTF). ______________________________________________________ This chapter addresses the following topics: o Prerequisites for HP SIM o Subscribing to Indications (Events) o Unsubscribing to Indications (Events) o Viewing Indications (Events) o Viewing Instances 3.1 Prerequisites for HP SIM To use HP SIM to administer and view indications and instances, ensure that the following prerequisites are satisfied: o Setting the Global Protocol o Discovering a System o Identifying a System Administering Indications and Instances Using HP SIM 3-1 Administering Indications and Instances Using HP SIM 3.1 Prerequisites for HP SIM 3.1.1 Setting the Global Protocol To set the Global Protocol Settings using HP SIM, follow these steps: 1. On OpenVMS system, complete the steps described in the Section 2.4 "Configuring WBEM Services for OpenVMS to Support HP SIM". 2. Enter the following URL to launch HP SIM on the browser: http://:/ The system name is the name of CMS. For example, http://abc.com:280/ The HP SIM home page is launched. 3. To set the global protocol, select Options->Protocol Settings->Global Protocol Settings. The Global Protocol Settings window is displayed. 4. Under the Default WBEM settings section, select Enable WBEM. 5. Add the users and their associated password that were added while configuring WBEM Services for HP SIM on OpenVMS. Click OK to save the settings. ________________________ Note ________________________ For more information, see the HP Systems Insight Manager Installation and User's Guide at: http://docs.hp.com/en/netsys.html ______________________________________________________ 3.1.2 Discovering a System To discover an OpenVMS system using HP SIM, follow these steps: 1. Select Options ->Discovery in the HP SIM home page. The Discovery page is displayed. 2. Click New to add a new system.Enter the IP address, and click OK to save the settings. 3. Or click Edit to modify the discovered system settings. 3-2 Administering Indications and Instances Using HP SIM Administering Indications and Instances Using HP SIM 3.1 Prerequisites for HP SIM 4. Click Run Now. ________________________ Note ________________________ For more information, see the HP Systems Insight Manager Installation and User's Guide at: http://docs.hp.com/en/netsys.html ______________________________________________________ 3.1.3 Identifying a System Identify a system on HP SIM, if the system has not been discovered properly, or if the Global Protocol Settings are different from the System Protocol Settings. To identify a system, follow these steps: 1. In the left pane of the HP SIM page, from the All Systems option, select the required OpenVMS system to open the Systems page. 2. Click Tools & Links, and click the System Protocol Settings link. The System Protocol Settings page is displayed. 3. Under the WBEM settings section, select Updated values for this protocol. Select Use values specified below, and enter the required user credentials, if the system protocol settings are different from the global protocol settings. Click OK to save the settings. 4. Select Options->Identify Systems to identify the system. 5. Select the required system, and click Run Now to verify the target system. Administering Indications and Instances Using HP SIM 3-3 Administering Indications and Instances Using HP SIM 3.1 Prerequisites for HP SIM The Task Results page is displayed. ________________________ Note ________________________ For more information, see the HP Systems Insight Manager Installation and User's Guide at: http://docs.hp.com/en/netsys.html ______________________________________________________ 3.2 Subscribing to Indications (Events) When creating subscriptions on the CMS using HP SIM, indications are delivered to the CMS whenever an event occurs on the managed system. To subscribe to indications or events generated on the selected systems, follow these steps: 1. Log on to the Windows system on which HP SIM is installed. Ensure that the account used to log on has administrator privileges on HP SIM. 2. Select the required system, and click Options->Events- >Subscribe to WBEM Events . The Subscribe to WBEM Events page is displayed. 3. Click Run Now to view the Task Results. The Task Results page is displayed. 3-4 Administering Indications and Instances Using HP SIM Administering Indications and Instances Using HP SIM 3.3 Unsubscribing to Indications (Events) 3.3 Unsubscribing to Indications (Events) If you want to unsubscribe to indications or events generated on the selected systems, follow these steps: 1. Click Options->Events->Unsubscribe to WBEM Events to unsubscribe for event. 2. Click Next. 3. Click Run Now. The Task Results page is displayed. 3.4 Viewing Indications (Events) To view the list of indications or events generated on the selected systems, follow these steps: 1. Select All Events in the left pane of the HP SIM window. The list of events is displayed. 2. To view the details of an event, select the event. The details are displayed at the bottom of the same window. 3. To obtain the printable version of the event details, click View Printable Details at the bottom of the window. The printable report is displayed in a new window. ________________________ Note ________________________ For more information, see the HP Systems Insight Manager Installation and User's Guide at: http://docs.hp.com/en/netsys.html ______________________________________________________ Administering Indications and Instances Using HP SIM 3-5 Administering Indications and Instances Using HP SIM 3.5 Viewing Instances 3.5 Viewing Instances To view the various instances, follow these steps: 1. On the System Page of HP SIM, click Properties. The Properties window is displayed. This window provides details about the system. 2. To view the status of various instances, click Status. 3. Click the required instance link to view more information about the instance. 4. To view information about the instance configuration , click Configuration. 5. Click the required instance link to view the detailed instance configuration information. ________________________ Note ________________________ For more information, see the HP Systems Insight Manager Installation and User's Guide at: http://docs.hp.com/en/netsys.html ______________________________________________________ 3-6 Administering Indications and Instances Using HP SIM _________________________________________________________________ Glossary Central Management Server (CMS) The server monitoring the client systems in the network using the WBEM Providers software. Common Information Model (CIM) An object-based model for describing managed resources. CIM uses the object-oriented paradigm, where managed objects are modeled using the concepts of classes and instances. Common Information Model Object Manager (CIMOM) The component of WBEM that manages the interaction between the providers and other modules in the WBEM environment. CIMOM manages CIM objects. It receives and processes CIM operation requests and issues responses. CIM client An entity in WBEM architecture which sends CIM Operation requests and receives CIM Operation responses. For example, HP SIM and other network management applications are considered CIM clients. CIM server The component of WBEM that manages the interaction between the providers and other modules in the WBEM environment. It is also known as CIMOM. consumer A recipient of services. For example, an indication consumer will receive indications (events) that occur in system hardware components. Glossary-1 Distributed Management Task Force (DMTF) An industry organization involved in the development, adoption, and interoperability of management standards and initiatives for enterprise and Internet environments. event An alert generated when an unusual activity is detected on a monitored hardware device. HP Systems Insight Manager (HP SIM) HP's management application installed on the CMS that uses WBEM instrumentation on operating systems, such as HP-UX, HP OpenVMS, Linux, and Windows. indication An alert or a warning about the failure of a monitored hardware device. It is equivalent to an event in the Event Monitoring Service (EMS) framework. indication provider It translates events generated by the Event Monitoring Service (EMS) monitors into WBEM indications, and reports them to the CIMOM. instance A representation of the actual physical object that belongs to a class. instance provider It provides information about devices, such as model number and serial number of a CPU. In the Support Tools Manager (STM), this functionality is accomplished by Information (Info) Tools. managed resource A hardware device that is monitored. management application Any application that can be used to query for information about monitored devices and view indications and instances. For example, HP Systems Insight Manager (SIM). Glossary-2 subscription Configuring WBEM Providers for consumers to receive indications. For example, HP SIM can subscribe to indications that are generated on hardware devices on a system. WBEM (Web-Based Enterprise Management) A collection of standards that aid large-scale systems management. WBEM allows management applications to monitor systems in a network. Glossary-3 _________________________________________________________________ Index B data sheet, vi _______________________________ DMTF, 3-1 benefits documentation files, 2-3 WBEM Providers, 1-1 E______________________________ C______________________________ EMS Wrapper Provider, 1-7 Central Management Server See Enclosure Provider, 1-6 CMS Environmental Instance Common Information Model See Provider, 1-5 CIM event CIM, 3-1 details, 3-5 CIMOM, 1-7, 1-9 printable report, 3-5 CIMPROVIDER Event Monitoring Service, 1-8 -L -S option, 2-4, 2-5, 2-7 events list, 1-8 CIMUSER -A -U option, 2-6 F______________________________ -HELP option, 2-7 Forward Progress Log See FPL -R -U option, 2-7 features CMS, 3-4 WBEM Providers, 1-1 command procedure file, 2-4 Firmware Revision Instance common files, 2-3 Provider, 1-6 Computer System Chassis FPL, 1-8 Instance Provider, 1-5 CPU Instance Provider, 1-3 G______________________________ D global protocol, 3-2 _______________________________ Distributed Management Task H______________________________ Force See DMTF hardware indications, 1-8 daemon hardware monitor WBEM Set Host Parameters, FPL, 1-8 1-9 ia64 Core Hardware, 1-8 WBEM Utilization Provider, 1-9 Index-1 HP OpenVMS Integrity Servers, OpenVMS EMS 2-1 See Event Monitoring Service HP TCP/IP, 2-1 HP WBEM Services, 2-1 P______________________________ logicals, 2-4, 2-7 POLYCENTER Software I Installation See PCSI _______________________________ PCSI, 2-2 index file, 1-8 indication provider S______________________________ EMS Wrapper, 1-7 Systems Insight Manager See LAN Indication Provider, 1-7 SIM instance shareable image, 2-3 configuration, 3-6 SIM, 1-9 property, 3-6 system protocol, 3-3 status, 3-6 instance provider Computer System Chassis, 1-5 T______________________________ CPU, 1-3 task result, 3-4 Enclosure, 1-6 Environmental, 1-5 U______________________________ Firmware Revision, 1-6 Utilization Provider, 1-6 LAN Provider, 1-6 Management Processor, 1-6 Memory, 1-4 V______________________________ Utilization Provider, 1-6 VM Provider, 1-6 VM Provider, 1-6 W______________________________ L______________________________ Web-Based Enterprise LAN Indication Provider, 1-7 Management See WBEM LAN Provider, 1-6 WBEM, 1-1 WBEMEXEC, 2-12 M______________________________ WBEM Providers manifest file, 2-2 architecture, 1-9 Memory Instance Provider, 1-4 indication providers, 1-7 MOF file, 2-3 instance provider, 1-3 MP Instance Provider, 1-6 register, 2-5 _______________________________ X______________________________ Operating Environment See OE XML file, 2-12 OE, 2-1 Index-2