HP WBEM Services Version A.02.11.
© Copyright 2012, 2013 Hewlett-Packard Development Company, L.P. Legal Notices 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.
Contents 1 HP WBEM Services Version A.02.11.00 Release Notes....................................4 Announcement.........................................................................................................................4 What's new in this version?.......................................................................................................4 Security ..................................................................................................................................
1 HP WBEM Services Version A.02.11.00 Release Notes Announcement The following information is for HP WBEM Services Version A.02.11.00: HP WBEM Services for HP-UX is available from http://software.hp.com. HP-UX implements the Distributed Management Task Force (DMTF) WBEM standard and this enables HP WBEM Services to deliver increased control of enterprise resources at reduced cost.
Following are the key differences between the HP WBEM Services version A.02.09.14 and A.02.11.00: • New config property maxFailedProviderModuleRestarts: The new release includes a new config property called “maxFailedProviderModuleRestarts”. By default, this value is zero. If set to a positive integer (maximum 3), this value specifies the number of times the failed provider module with indications enabled is restarted automatically before being moved to Degraded state.
HP WBEM Services Version A.02.11.00 contains the following: • Support for WBEM Indications • HP WBEM Services run-time environment • ◦ Binary command line executables ◦ Shared libraries ◦ Configuration files ◦ CIM schemas Packaged provider modules ◦ Computer System ◦ Operating System ◦ Process ◦ Domain Name Service ◦ Network Time Protocol ◦ Network Information Service ◦ IP ◦ SD ◦ IOTree For information on installing HP WBEM Services Version A.02.11.
Security considerations When you use the Simple Network Management Protocol (SNMP), Process Resource Manager (PRM), and Workload Manager (WLM) tools, consider the following security conditions: • You can use tools such as PRM and WLM to limit computing resources used by the WBEM Services processes. You can purchase these products from http://www.software.hp.com.
Table 2 Remote user authentication methods (continued) Certificate Based Authentication (CBA) HTTP Basic Authentication Benefits and Considerations • Requires a one-time server configuration. • Does not require any server configuration and hence, easy to set up. • Does not require the remote user to provide a password • Requires the remote user to provide a password to each time to access the WBEM data. access the WBEM data.
Using Certificate Based Authentication To use the Certificate Based Authentication (CBA) method, you must do the following: 1. Use the cimconfig command, to enable CBA . By default, the CBA is disabled. For more information, see the cimconfig(1M) and cimtrust(1M) manpages. 2. Use the cimtrust command to include the client certificates from the trust store in the cimserver and associate that certificate with a system user. 3.
1. Delete the existing /var/opt/wbem/server_2048.pem and /var/opt/wbem/ server.pem files and use the certificates in the /etc/opt/hp/sslshare directory. Or 2. Overwrite the new certificate in the /etc/opt/hp/sslshare/cert.pem file and the private key in the /etc/opt/hp/sslshare/file.pem file with the existing certificate and key in either /var/opt/wbem/server_2048.pem or /var/opt/wbem/ server.pem files. Before overwriting the /etc/opt/hp/sslshare/cert.pem and /etc/opt/hp/sslshare/file.
For more information, see the DMTF WBEM and CIM standards at http://www.dmtf.org. Compatibility information This section describes the compatibility information for HP WBEM Services Version A.02.11.00. Compatibility for WBEM providers Table 3 lists the product bundle and WBEM version information for HP-UX 11i v3. Use this table to determine, which bundle is compatible with your version of HP-UX. Use the swlist command to view your product bundle version number.
Table 3 HP-UX 11i v3 WBEM Solution Compatibility Table Product Tag Product Title Product Version Supported HP WBEM Services Version iCOD HP-UX iCOD (Instant Capacity) B.11.31.10.07.00 A.02.11.00 NParProvider nPartition Provider - HP-UX B.31.02.04 SW-DIST HP-UX Software Distributor B.11.31.1303.390 WBEMP-LAN LAN Provider for Ethernet LAN interfaces B.11.31.1303.04.01 VParProvider vPar Provider - HP-UX B.11.31.01.06 WBEMP-FCP WBEM Provider for FC HBAs B.11.31.1303.05.
Prior to this release, all WBEM Providers executed in a privileged context. With the release of HP WBEM Services Version A.02.05.02 for HP-UX 11i v3, WBEM Providers will, by default, be invoked in the context of the user requesting an operation (i.e., “Run-As-Requestor”). This default setting can break backward compatibility for certain types of providers. This means that existing providers that run in the user context of the CIM Server can break.
• Disk space requirements HP WBEM Services requires the following disk space to install: / 5 MB /opt 46 MB /var 184 KB /usr 1 MB Depending on the number of CIM objects to be stored in the CIM Repository, additional disk space might be needed for the/var/opt/wbem directory. • Port requirements HP WBEM Services uses dedicated ports for CIM-XML traffic. Two ports are dedicated for CIM-XML communications between CIM clients and the CIM Server.
/opt/wbem/mof MOF files /opt/wbem/mx Reserved /opt/wbem/providers/lib Links to shared libraries for providers /opt/wbem/sbin Commands and executables that only root user can run /opt/wbem/share/man Manpages /var/opt/wbem Configuration files, CIM repository, log files, and so on IMPORTANT: Do not move these files from the default location. If these files are moved, it can result in problems in the functioning of the CIM Server. 5.
Running the CIM Server After installation, the HP WBEM Services CIM Server process (cimserver) is active. To restart it, first stop CIM Server with the cimserver -s command. Use the cimserver command, with no options to start the cimserver daemon on the system where the command is issued. Once the CIM Server has been installed, the CIM Server automatically starts as part of the system reboot process.
Table 4 Defects fixed in HP WBEM Services Version A.02.11.00 and A.02.09.xx (continued) Identifier Description Resolution specify two fields, and one without PropertyList which would select all fields, the resulting WBEM response when compared were identical. The PropertyList parameter did not reduce the network traffic as expected. Defects fixed in A.02.09.14 QXCR1001219079 cimserver fails to start with duplicate entries in namespace authorization.
Table 4 Defects fixed in HP WBEM Services Version A.02.11.00 and A.02.09.xx (continued) Identifier Description Resolution process, while EnumerateInstances is running for StorageNative Provider in another process. The core dump occurs due to an incorrect destruction sequence in one of the cimprovagt objects. QXCR1001095699 Multiple instances of the cimprovagt processes are created for one provider.
Table 4 Defects fixed in HP WBEM Services Version A.02.11.00 and A.02.09.xx (continued) Identifier Description Resolution QXCR1001060784 With the current fix, cimserverd daemon The cimserverd daemon checks if the monitors the status of both cimserver and cimservermain process is running and restarts cimservermain processes and restarts cimserver if cimservermain is not active. cimserver if either one of the process is not active. QXCR1001064867 This defect is fixed in the current release.
Table 4 Defects fixed in HP WBEM Services Version A.02.11.00 and A.02.09.xx (continued) Identifier Description Resolution WBEMServices/ WBEM-CORE.2/configure[913]: 25842 Memory fault (coredump) WARNING: Unable to load SD mof files With the cimservermain coredump, the following connection error message is displayed: PGS08001: CIM HTTP OR HTTPS CONNECTOR CANNOT CONNECT TO 10.162.5.25:5989. CONNECTION FAILED Known problems and workarounds Following known problems and workarounds are for this release.
125) ensuring that these IDs are not in use by LDAP or other network services.
