HP Matrix Operating Environment 7.3 Update 1 Release Notes Abstract This document describes the HP Matrix Operating Environment 7.3 Update 1 release content and provides information about limitations, and major and minor issues with suggested actions.
© Copyright 2006–2014 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. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.
Contents 1 Description....................................................................................4 Update recommendation...........................................................................................4 Supersedes..............................................................................................................4 Operating systems and devices...................................................................................4 Enhancements..........................................
1 Description HP Matrix Operating Environment is advanced infrastructure management software that allows you to analyze and optimize both physical and virtual resources in the same way. Matrix OE gives you a powerful toolkit to accelerate complex technology projects and simplify daily operations. It enables you to plan capacity and power continuously, provision infrastructure consistently, and balance across physical and virtual resources.
New features in Matrix Operating Environment • • • Software support for: ◦ RHEL (Red Hat Enterprise Linux) 5.1 ◦ RHEL 6.5 ◦ VMware vSphere 5.1 ◦ VMware ESXi 5.
◦ Support for ESXi deployment through IC server provisioning (in addition, the current method of automated ESXi provisioning through VMware Auto Deploy) ◦ For more information about custom attributes, see Using custom attributes in HP Insight Control Server Provisioning Administrator Guide.
to display networks from vCenter, configure those networks in IO, assign networks to organizations, and provision infrastructure using service templates. Prerequisites to configure the VMware VXLAN environment 1. 2. 3. 4. Ensure that all of the ESX clusters which need to be part of the VXLAN are in the same VMware vSphere datacenter. Add all the clusters of the datacenter to VXLAN Networking. All hosts in a cluster must be connected to a distributed switch to enable VXLAN networking (same VDS name).
Installation Installation instructions are documented in the HP Insight Management Installation and Configuration Guide. These documents are available from the Enterprise Information Library. Newer version available for download Matrix Operating Environment for HP-UX The latest version of Matrix OE for Integrity is available from the following location: https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.
Back up user-modified properties files before upgrade During an upgrade, Matrix OE properties files from an earlier release are replaced by new properties files for the new release. If you made any modifications or customizations to the properties files, your changes are lost. Suggested action Before beginning an upgrade to Matrix OE, save a copy of user-modified properties files or note any changes made to the files so that you can insert those modifications into the new versions of the files.
Hyper-V VM hosts are moved to the IO unassigned pool after upgrade from 6.3 After an upgrade from Matrix OE 6.3 to 7.2 or later, all Hyper-V VM hosts are automatically moved to the infrastructure orchestration Unassigned server pool. This issue does not occur after an upgrade from Matrix OE 7.0 to 7.2 or later. Manually move the Hyper-V VM hosts back to their original server pool in order to provision virtual servers to Hyper-V VM hosts.
Check logical server management upgrade log file When Matrix OE logical server management is upgraded, the pre-upgrade task completes even if there are exceptions or missing objects. Suggested action After the upgrade is complete, check for important upgrade messages at ../Program Files/HP/Virtual Server Environment/logs/vselog.lsm.log, and make any changes as necessary. Changing the CMS password Use the mxpassword command to change the CMS password.
Managing Microsoft Windows servers without OpenSSH installed Even though the product documentation states OpenSSH is required, Matrix OE supports Microsoft Windows environments not running OpenSSH. However, for Microsoft Windows systems without OpenSSH, there are several limitations with agent installation and troubleshooting. For details on using Matrix OE with Microsoft Windows systems not running OpenSSH, see the HP Matrix Operating Environment 7.
Download from http://www.hp.com/go/hpsc. Log on with an HP Passport. From the Download options list, select Patch management and enter the patch number in the search box. Click Search. Install Utilization Provider version A.01.08.07.00 for HP-UX 1203 Integrity VM host Utilization Provider version A.01.08.07.00 is required for systems that have HP-UX vPars and Integrity VM 6.1. Download this version from the HP Software Depot.
969049 to modify the cluster DNS behavior, and then rediscover the cluster in Systems Insight Manager. User experience and application performance Matrix OE is based on web client server technologies. Your perception of performance can be affected by many external sources, including the central management server’s health, network congestion and latency, and client side equipment and browser.
2 Issues and suggested actions The issues and limitations in this release are listed in this chapter, organized by Matrix Operating Environment feature or functional area. If a feature or functional area has no limitations or issues, that category will not appear.
(ioTurbine version 2.0.3.1) – Supported Environments and Scenarios White Paper and the Insight Management and HP IO Accelerators (ioTurbine version 2.1) – Supported Environments and Scenarios White Paper at Enterprise Information Library.
Capacity Advisor Limitations Capacity Advisor provides support for the HP ProLiant WS460c Gen8 workstation Capacity Advisor is able to collect historical data from ProLiant WS460c Gen8 after following the steps described in the How to license HP ProLiant WS460c Gen8 Blade Workstations for Capacity Advisor White Paper located at Enterprise Information Library.
whether the results are full or partial. Additionally, you can change the analysis interval to a time period where all of the data is more likely to be available. Matrix infrastructure orchestration Matrix infrastructure orchestration runs on an x64 Windows CMS. Enabling Matrix infrastructure orchestration provisioning support of Linux VMs on Hyper-V NOTE: The hpio.properties value skip.linux.on.hyperv.template.personalization allows Linux VMs on Hyper-V, but it is deprecated.
In the above example, for non-redundant storage, Matrix tries FabricA, FabricB, FabricC and FabricD in that order. For redundant storage, Matrix tries the FabricC & FabricD pairing. NOTE: The fabrics listed in this property are used by all auto-generated storage pool entries from Matrix infrastructure orchestration on that CMS. It cannot be set up to only be used by some users or some organizations.
a. b. c. 5. From the HP Matrix Operating Environment menu, click Tools→Infrastructure Orchestration. Click the Servers tab. Make sure the servers are not being used by checking the “Usage” column. Move the servers under the “Maintenance” pool to the desired server pool by using the “Modify Pool” option. Recreate the service request.
a. b. c. 5. From the HP Matrix Operating Environment menu, click Tools→Infrastructure Orchestration. Click the Servers tab. Make sure the servers are not being used by checking the “Usage” column. Move the servers under the “Maintenance” pool to the desired server pool by using the “Modify Pool” option. Recreate the service request.
If this error message appears, the HAProxy configuration file is too big and the infrastructure orchestration/OO Load Balancer workflows are not able to process this request. To create many services that use this load balancer, HP recommends that you use the F5 BIG-IP Load Balancer. For more information, see the F5 - BIG-IP Local Traffic Manager website at http://h17007.www1.hp.com/one/alliance/f5/big-ip.htm? jumpid=reg_r1002_usen_c-001_title_r0001.
NOTE: By default, specifying storage volume names when adding a disk to a VM is restricted to administrators. To enable all users to specify storage volume names when adding a disk to a VM, change the value of the hpio.properties user.disk.add.storage.volume.names.restricted properly from true to false. Setting this property to false also means that the users can specify storage volume names which are not part of the service template.
Required HBA firmware and OS drivers to access multi-initiator N-Port ID Virtualization (NPIV) data disks The multi-initiator NPIV feature allows you to configure multiple WWNs for a single HBA connected with a Virtual Connect Fibre Channel module. Although Matrix OE automates the configuration, certain versions of HBA firmware and drivers are required to access multi-initiator NPIV data disks configured for any target BL server.
Required software versions for FlexFabric Integrity physical provisioning support Matrix OE infrastructure orchestration requires the following minimum software versions to support HP FlexFabric for Integrity physical provisioning: • Ignite-UX C.7.12.
Cluster shared volume does not appear after Microsoft Hyper-V VM provisioning with high availability enabled If you use infrastructure orchestration to create and deploy a virtual provisioning template on a Microsoft Hyper-V VM host with the High Availability (HA) option enabled, and then view the virtual machine in the Failover Cluster Manager on the Hyper-V host, the cluster shared volume (CSV) is not displayed in the provisioned VM information.
Suggested action 1 1. 2. Cancel the Create or Add Server request. Modify the template to remove the HA requirement, or Modify the template to deselect linked clones and add a cluster disk for each virtual machine. 3. Resubmit the Create request, or For the Add Server request, delete the existing service and recreate it with the updated template. Take care to migrate data from the existing service to the new service before deleting the existing service.
Major Issues High Availability Hyper-V VMs with RDM/pass-through disks violating various constraints from Hyper-V result in errors Service provisioning or logical server VM creation or reactivation fails with a job message similar to the following: The operation has failed. (The start function on virtual machine vsels_name [VM info and XML path] failed. ) Matrix OE supports High Availability (HA) Hyper-V VMs with RDM/pass-through disks, with various constraints from Hyper-V.
step to fail with an error stating Error customizing Logical Server Logical server name realized by target UUID. Suggested action Matrix OE environments can have the newly provisioned server join the domain by using deployment server custom attributes. For additional information on this, see HP Matrix Operating Environment Infrastructure Orchestration User Guide.
Task for Logical Server has failed. Logical server job (logicalservername_FQDN) completed with a failure status. Failure: At least one OS or software deployment has failed In the Insight Control server provisioning appliance console, the following error appears: Wait for HPSA Agent failed with exit code 6 at step 21 Suggested Action 1. 2.
a. b. Use the Systems Insight Manager menu selection Options→Discovery..., or Use the Systems Insight Manager command: mxnode -a -w where is the IP address that was assigned to the Integrity blade after provisioning. Add the root login of the Integrity blade using the Systems Insight Manager menu selection Options→Security→Credentials→System Credentials.... 3. 4.
Provisioning a service may fail when storage volumes in a logical server group contain different tags In an Matrix infrastructure orchestration 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.
VM cluster provisioning requires restart of VMware Management Agents for preferred hostname to be registered in DDNS The VM cluster Operations Orchestration workflows enable Dynamic DNS integration by setting a VMware property. For this property to be activated, and the DDNS registration performed, the management network on the ESX host must be manually restarted.
The browser requires a method to accept self-signed certificate to access IO By default, IO is configured to use self-signed certificate, which may result in your browser displaying one of the following errors: • Chrome displays: The site's security certificate is not trusted! or a blank page with the icon • . Internet Explorer 11 displays: There is a problem with this website’s security certificate or Content was blocked because it was not signed by a valid security certificate.
Templates that connect a physical disk to an Hyper-V HA virtual server group cannot be provisioned Designer allows a physical disk to be connected to a High Availability Hyper-V virtual server group and allows you to set the Raw Device Mapping Type for the physical disk. However, provisioning a template with this configuration returns an error.
Suggested action If a feature fails to configure correctly because of privilege elevation password requirements, configure the feature outside of the managed system setup wizard. To turn off the requirement for a password, use the Systems Insight Manager Options→Security→Privilege Elevation menu, and uncheck the check box labeled “A password is required for this privilege elevation tool.” Note that systems managed by the CMS must be reconfigured to reflect this configuration change.
Logical server management Logical server management runs on an x86/x64 Windows CMS. Limitations Restrictions on using cross-technology logical servers Cross-technology logical servers can be moved between ProLiant server blades with Virtual Connect to ESX and back, between Integrity server blades with Virtual Connect and Integrity VM and back, and between servers with Virtual Connect with unlike configurations.
cross-technology logical servers that may be activated on an ESX or Integrity VM host. ◦ Integrity VM storage requirements: – SAN-based logical server storage is supported, including storage pool entries. File based storage is not supported with Integrity VM cross-technology logical servers. NOTE: SAN volumes used for Integrity VM fluid cross-technology logical servers should not be presented to the Integrity VM host.
VM host operation you Steps to perform on VM guests Steps to perform for the VM host after want to perform performing the steps on the VM guests Delete the VM host logical server • If you no longer need the VM guests, delete them. Otherwise, move all VM guests to a suitable host. • If you have VM guests that are not logical servers, then use the appropriate tools to relocate the guests. 1. Unregister the VM host from Insight Control virtual machine management.
• Hyper-V VM linked clone disks must either specify the same storage volume name not specify a name at all. • Microsoft does not support VM Linked Clone using multiple data stores.
Microsoft Hyper-V virtual machine logical server boot disk is IDE and data disks are SCSI When you create a Hyper-V virtual machine logical server, the boot disk (where Windows or Linux is installed) is always created using an IDE controller. Data disks are created using a SCSI controller. The IDE controller is required to allow the installation of the operating system using Deploy Tools or using images without additional drivers.
Suggested action At the Integrity Virtual Machine EFI prompt, execute the following commands to see LUN mappings. When these steps are complete, the user can select the required LUN from the displayed device list to boot up or to install the operating system. 1. Check configurable controllers using the drvcfg command. Shell> drvcfg Configurable Components Drv[2C] Ctrl[29] Lang[eng] 2. Enumerate all SCSI and FC LUNs using drvcfg -s . (drvnum and ctrlnum are displayed as part of step 1.
Suggested Action: 1. 2. 3. 4. 5. 6. 7. 8. 9. Log on to SPM using an account that is a member of the server’s local Administrators group. In the Administration section, click Roles. In the list of roles, click the Matrix Administrator link, and then change to the Users and Groups tab. Check that the list includes a group with a long strange name similar to S-1-5-21–3058410101–4014573073–2151168493–1007. If not then you have not been affected by this issue.
1. Determine the WWNs of the unmanaged Integrity VM logical server by logging onto the VM host and using the hpvmstatus command: hpvmstatus –P Name_of_Unmanaged_VM | grep npiv Sample output: hba avio_stor 0 1 npiv /dev/fclp0-0x5001438002A30041,0x5001438002A30044 Make a note of the server WWNs, converting them to lsmutil format. In this example, 0x5001438002A30041 and 0x5001438002A30044 become 50:01:43:80:02:A3:00:41 and 50:01:43:80:02:A3:00:44. 2. 3. 4.
Suggested action 1 To correct the GC overhead limit and/or Java heap space errors, modify the configuration file to increase memory allocation: 1. 2. 3. Modify the configuration file (shown in the default location) at C:\Program Files\HP\Virtual Server Environment\conf\hp_lsa_service.conf. Increase the value of wrapper.java.maxmemory=1024. HP suggests a value of 2048. Restart the HP Logical Server Automation service.
value, the activation may fail with the error “Value x.x for entitlement_min is below minimum, setting to 5.0.” This error is displayed on the VM host. Suggested action On the Integrity VM host, set the Integrity VM configuration variable GUESTMHZMIN to the nearest integer value that is five percent of the host processor speed in cycles.
HP Matrix Operating Environment recovery management Limitations Required configuration for disaster recovery Storage pool entry names must be the same at both the preferred and secondary site. HP Storage Provisioning Manager Storage Provisioning Manager runs on an x86/x64 Windows CMS. Limitations Required version of Brocade Network Advisor and HP B-Series Network Advisor Brocade Network Advisor 11.1.3, 11.1.4, or 12.1.4 or HP B-Series Network Advisor 11.1.3, 11.1.4, or 12.1.
or to any value less than 100%, then a thin volume is expected to be created by the adapter. This behavior is expected irrespective of the storage pool being sent in the request. Thus the adapter implementation overrides the way EMC creates the thick and thin volumes: ◦ When SPM requests a thick volume on a thin pool, the adapter will create a thin volume on the given thin pool. ◦ When SPM requests a thin volume on a concrete pool, the adapter will create a thick volume on the concrete pool.
HP 3PAR StoreServ Storage Peer Motion has limited support in SPM If Peer Motion is used on an HP 3PAR StoreServ Storage System that is imported into an SPM catalog, a number of steps must be performed in order to ensure that SPM and Matrix OE can properly use the storage affected by Peer Motion. For details on these steps, see the SPM 3PAR StoreServ Storage Peer Motion Technical White Paper at Enterprise Information Library. HP 3PAR StoreServ Storage Peer Persistence is not supported in SPM SPM 2.
KVM virtual machine provisioning NOTE: There are no updates to the KVM appliance in the 7.3 or 7.3.1 releases. Major issues RHEL 6.4 with KVM OS Build Plan fails with error The default Insight Control server provisioning RHEL 6.4 KVM OS Build Plan configures the “br0” device, causing post-installation customization to fail with the following error: Error customizing Logical Server realized by .
3 Support and other resources Contacting HP Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • See the Contact HP Worldwide website for contac
After creating your profile and linking your support agreements to your profile, see the Software Updates and Licensing portal at http://www.hp.com/go/ hpsoftwareupdatesupport to obtain software, documentation, and license updates. Warranty information HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management software products.
Related information The latest versions of manuals and white papers for Matrix Operating Environment and related products can be downloaded from the HP Web. Documents for Matrix OE software can be found at Enterprise Information Library. For more information about Matrix OE and related products and solutions, visit the following HP websites: • • HP Insight Management: ◦ http://www.hp.com/go/insightmanagement ◦ Enterprise Information Library HP Matrix Operating Environment: ◦ http://www.hp.
4 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
