HP Matrix Operating Environment 7.1 Release Notes

the following steps can be followed to disable the installation of Insight Management WBEM
providers. Insight Management SNMP agents continue to provide management capabilities when
WBEM providers are not installed.
1. Edit the install.cmd file, found under the <Insight Software installation>\rdp\
deployment server\hpfeatures\hpagents-ws\components folder.
2. Remove the following two lines:
call :installsc wbem%PROCESSOR_ARCHITECTURE%
if %cpresult% geq 1 set /a cpresults=cpresults+1
“Any Of” and “All Of” requirements in SPM are not displayed correctly in infrastructure
orchestration designer
Using SPM, you can define complex requirements with nested “Any of” (or) and “All of” (and)
constructs. These requirements are correctly applied when provisioning storage in SPM, but
infrastructure orchestration designer does not display these requirements in detail. The IO template
architect may be allowed to enter values when defining storage that will cause storage provisioning
to fail. For example, a combination of the “Any Of” or “All Of” requirements allows only a specific
RAID level or specific size range. If the architect picks a RAID level or range that is not allowed in
the template, storage provisioning will fail.
Suggested action
When defining SPM storage templates, use the Description field to summarize the requirements
(for example, if the template supports only RAID 1 and RAID 5). That description is visible to the
architect in infrastructure orchestration designer. When using a specific SPM storage template in
IO, be aware of the storage template's capacity, RAID, and tag requirements (included in the
Description field). Do not specify values that conflict with these requirements or subsequent storage
provisioning will fail.
Provisioning a service may fail when storage volumes in a logical server group contain
different tags
In an IO template, different storage tags can be assigned to the individual volumes in a logical
server group. When storage is auto-generated, each volume is provisioned based on a number
of defined requirements, including these tags. Within a logical server group, if the private data
disk(s) contain different tags than the boot disk, the service will fail to provision.
Suggested action
Use the same storage tags for the boot disk and private data disks in a logical server group. If
separate tags are needed, separate storage pool entries can be manually defined for the boot
disk and private data disks with those separate tags.
Storage auto provisioning does not select a preconfigured data disk if the storage pool
entry does not contain a boot disk
During storage provisioning, if a storage pool entry contains a volume that matches the requirements
of an infrastructure orchestration service, the matching volume is used for the service.
If the IO template contains a boot disk and a data disk, and the storage pool entry contains only
a boot disk, the boot disk is used and the data disk is automatically created. However, if the storage
pool entry contains only a data disk, the volume is not used. Both the boot and data disk will be
created.
Suggested action
Add a boot disk to the storage pool entry containing the desired data disk, or allow both disks to
be automatically created.
Infrastructure orchestration 25