HP WBEM Services Version A.02.09.
© Copyright 2012 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.09.12 Release Notes....................................4 Announcement.........................................................................................................................4 What is in this version?.............................................................................................................4 Security ..................................................................................................................................
1 HP WBEM Services Version A.02.09.12 Release Notes Announcement The following information is for HP WBEM Services Version A.02.09.12: 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.07 and A.02.09: • From this release, the CIM Repository (/var/opt/wbem/repository) is a database instead of a file-based repository. This is done to increase the robustness of the CIM repository. • wbemassist - A command-based troubleshooting utility to identify problems related to HP WBEM Services on the managed nodes.
• ◦ 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.09.10, see “Installation information” (page 12).
NOTE: OpenSSL is an open source cryptography toolkit that implements the network protocols and related cryptography standards of SSL v2 and v3, and TLS (Transport Layer Security). HP WBEM Services supports only SSL v3 and TLS protocols. For more information, see OpenSSL website at http://www.openssl.org. On the HTTPS port, the CIM clients uses SSL to establish connections with the CIM Server and to send CIM requests.
you must edit the/etc/pam.conf file and add a "wbem" service entry. See the following example. For additional information, see the pam(3) and pam.conf(4) manpages. # # Example of /etc/pam.conf file with WBEM services (using LDAP) # # Authentication management wbem auth required libpam_hpsec.so.1 wbem auth sufficient libpam_unix.so.1 wbem auth required libpam_ldap.so.1 try_first_pass # Account management wbem account required libpam_hpsec.so.1 wbem account sufficient libpam_unix.so.
The wbemexec command uses the trust store for server certificate verification. Be sure to import the certificate in the /etc/opt/hp/sslshare/cert.pem file from the system where the CIM Server is running to the client system’s trust store. For more information about the wbemexec command, see the wbemexec manpage. For more information about certificates, see “Importing server certificates to trust store” (page 10).
Importing server certificates to trust store CIM client applications must maintain a trust store in the .pem file. The CIM client applications must import the certificates stored in /etc/opt/hp/sslshare/cert.pem to a trust store file on the client machine from various CIM Server machines (machines that the client wants to connect to). With C++ CIM client libraries, the trust store should be in PEM format.
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.05.00.03 A.02.09.12 NParProvider nPartition Provider - HP-UX B.31.02.03 SW-DIST HP-UX Software Distributor B.11.31.1203.373 WBEMP-LAN LAN Provider for Ethernet LAN interfaces B.11.31.1203.06.01 VParProvider vPar Provider - HP-UX B.11.31.01.05 WBEMP-FCP WBEM Provider for FC HBAs B.11.31.1203.05.
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. To resolve this situation, you have the following two alternatives: Alternative 1 To continue running the provider in a privileged context, you need to explicitly register the provider to run in a “Privileged User” context.
• 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/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.
For HP-UX, the following providers are bundled with HP WBEM Services: • Computer System • Operating System • Process • Domain Name Service • Network Time Protocol • Network Information Service • IP • SD • IOTree After installing HP WBEM Services, the following filesets are visible on the system: • WBEM-CORE, A.02.09.10 - WBEM Services core fileset for HP Integrity servers • WBEM-CORE-COM, A.02.09.
Removing HP WBEM Services Before removing the software, back up any files that you want to retain, such as the repository, log files, configuration files, and certificate files. If these files are removed or overwritten during the re-installation, you cannot restore them. To remove HP WBEM Services, run the following HP-UX command: # swremove WBEMServices When there are providers in your environment that have a dependency on the file sets of HP WBEM Services, then this command results in an error.
Table 4 Defects fixed in HP WBEM Services Version A.02.09.xx (continued) Identifier Description Resolution QXCR1001103470 The StorageNative Provider module hangs when it is continuously enabled and disabled for one process, while EnumerateInstances is running for StorageNative Provider in another process. There is a race condition during the provider shutdown. This defect is fixed in the current release. A mutex has been added to ensure that the race condition does not occur.
Table 4 Defects fixed in HP WBEM Services Version A.02.09.xx (continued) Identifier Description Resolution authentication is completed, the authentication created for connections that are token is not removed from /var/opt/wbem/ terminated before authentication is localauth file. completed. QXCR1001071978 When upgrading from HP-UX 11i v2 OS to This defect is fixed in the current release.
Table 4 Defects fixed in HP WBEM Services Version A.02.09.xx (continued) Identifier Description Resolution QXCR1000873670 The manpage for the osinfo command does The manpage for the osinfo command not indicate that the /etc/opt/hp/ has been updated. sslshare/client.pem file is required for Client Based Authentication (CBA). QXCR1000914874 The cimmof and other WBEM client commands result in a core dump while accessing ICU libraries. This defect has been fixed to resolve these error messages.
NOTE: If you do not manually add the group and the user before installing HP WBEM Services, the installation scripts add a group and user using locally available IDs, returned by useradd(1M) and groupadd(1M), which may already be in use on the network. For systems using NIS the problem is encountered when HP WBEM Services is installed as part of a custom bundle that requires a system reboot or if NIS is stopped for any other reason whilst the HP WBEM Services installation is performed.
