HP Insight Control 7.2 Release Notes

Transcription

1 HP Insight Control 7.2 Release Notes Abstract This document describes the HP Insight Control 7.2 release content and provides information about limitations, and major and minor issues with suggested actions. HP Part Number: c Published: July 2013 Edition: 4

2 Copyright 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , 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. Acknowledgments HP-UX Release and later and HP-UX Release 11i and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products. UNIX is a registered trademark of The Open Group. Java is a US trademark of Sun Microsystems, Inc. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Warranty HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management products. Revision history Document part number Software version Supported operating systems Document edition Publication date See the HP Insight Management Support Matrix 1 March a See the HP Insight Management Support Matrix 2 April b See the HP Insight Management Support Matrix 3 May c See the HP Insight Management Support Matrix 4 July 2013

3 Contents 1 Insight Control release notes...5 Description...5 Update recommendation...5 Supercedes...5 Operating systems and devices...5 Enhancements...5 Web browser support...5 HP Insight Control HP Insight Control server provisioning...5 HP Insight Control server migration...6 HP Insight Control power management...7 HP Insight Control virtual machine management...7 HP Insight Control performance management...7 Prerequisites...8 Installation instructions...8 Issues and suggested actions...8 HP Insight Manager Online Help...8 Limitation...8 HP Insight Control power management...8 Limitations...8 Major issues...9 Minor issues...9 HP Insight Control server migration...11 Limitations...11 Major issues...11 Minor Issues...12 HP Insight Control server provisioning...13 First Time Setup Issues...13 Limitations...14 Major issues...16 Minor issues...20 HP Insight Control server deployment...23 Limitations...23 Major issues...24 Minor issues...24 HP Insight Control virtual machine management...25 Limitations...25 Major issues...25 Minor issues...25 HP Insight Control performance management...26 Limitations...26 Major issues...26 Minor issues...26 Insight Managed System Setup Wizard...28 Limitations...28 Major issues Support and other resources...29 Information to collect before contacting HP...29 How to contact HP...29 Security bulletin and alert policy for non-hp owned software components...29 Subscription service...29 Contents 3

4 Registering for software technical support and update service...29 How to use your software technical support and update service...30 HP authorized resellers...30 Related Technical Documentation...30 Related information...30 Typographic conventions Documentation feedback Contents

5 1 Insight Control release notes Description This document contains information you should know before installing or upgrading the HP Insight Control 7.2 release. For information concerning Insight Control, refer to the HP Insight Management Support Matrix. Update recommendation Supercedes HP recommends that customers running prior to 6.2 version should upgrade to 6.2 version and customers running 6.2 or later versions upgrade to version 7.2. This version replaces HP Insight Management 7.1 Update 2 Release Notes Operating systems and devices This release supports the operating systems and devices listed in the Insight Management Support Matrix. Enhancements Please read this document in its entirety to understand what you should expect from this software. These release notes describe HP Insight Control software. Web browser support This release adds support for these browsers: Microsoft Internet Explorer 10.0 (Compatibility View only) Mozilla Firefox 17.0.x (ESR) HP Insight Control 7.2 The following sections list the new capabilities available in this release, organized by HP Insight Control feature or functional area. The HP Insight Software Support Matrix lists the minimum hardware, firmware, and software requirements for installing and running Insight Control 7.2 and lists the latest revisions of already supported operating systems and hypervisors, non-os software, and hardware that were introduced in this release. Deprecated software and hardware is also noted. The support matrix is located in the HP Insight Management Information Library: New hardware, operating system and hypervisor support for all components (with differences noted under specific components) HP Insight Control server provisioning HP Insight Control includes the rights for HP Insight Control server provisioning, which is a new feature replacing HP Insight Control server deployment. HP Insight Control server provisioning performs multi-server operating system provisioning to bare metal ProLiant and BladeSystem servers. You can download the HP Insight Control server provisioning installation instructions from Description 5

6 Insight Control server provisioning is licensed as part of Insight Control, eliminating the additional licensing step that is required by Insight Control server deployment. NOTE: Insight Control server deployment is still available on the DVD, and can be used for upgrade purposes. However, the Insight Control server deployment software license will no longer be included with the sale of Insight Control. Insight Control customers wanting a new Insight Control server deployment license will be required to purchase a standalone Insight Control server deployment license. To continue using Insight Control server provisioning after the first 60-days, only licensed users should register by selecting Register to receive the Activation Key, and then follow the instructions. Trial users must purchase an Insight Control license before they can activate. If your Insight Control server provisioning appliance is not connected to an external network, register at Insight Control server provisioning allows you to: Install Windows, Linux, and ESXi on ProLiant G6, G7, and Gen8 servers. Update drivers, utilities, and firmware on ProLiant servers using the HP Service Packs for ProLiant (SPPs). Configure ProLiant system hardware, ilos, BIOS, and HP Smart Array. Deploy to target servers without using PXE (HP ProLiant Gen8 and later). Run deployment jobs on multiple servers simultaneously. Customize your ProLiant deployments via an easy to use browser-based interface. Migrate from HP Insight Control server deployment to Insight Control server provisioning. Work from a fast and simple VM appliance. HP Insight Control server migration In this release, HP Insight Control server migration has added the following support: New Server support HP ProLiant SL4545 G7 HyperStorage System HP ProLiant SL4540 Gen8 HyperStorage System New OS support Microsoft Windows Server 2012 (Standard and Datacenter Editions) RHEL 5.9 for x86 and x64 New Virtualization support Microsoft Windows Server 2012 with Hyper-V VMware ESXi 4.1 Update 3 and VMware ESXi 5.0 Update 2 (on managed node) New Browser support Microsoft Internet Explorer 10.0.x (Compatibility View only) Mozilla Firefox 17.0.x (ESR) New Adapter support HP Ethernet 1Gb 4-port 366FLR Adapter HP Ethernet 10Gb 2-port 530T Adapter HP Ethernet 10Gb 2-port 560FLR SFP+ Adapter HP Ethernet 10Gb 2-port 560M Adapter 6 Insight Control release notes

7 HP Insight Control power management In this release, HP Insight Control power management has added the following features and enhancements: New Hardware Support HP Integrity Superdome 2 HP Integrity Superdome HP Blade System c7000 Platinum Enclosure New CMS Support Microsoft Windows Server 2012 (Standard and Datacenter Editions) New Managed Node Support HP-UX 11i v3 (11.31) 1303 Microsoft Windows Server 2012 (Standard and Datacenter Editions) RHEL 5.9 KVM on RHEL 5.9 VMware ESXi 4.1 Update 3 VMware ESXi 5.0 Update 1 VMware ESXi 5.0 Update 2 New Feature Implemented Calculate Power History To calculate the power history independently, from generating the power/thermal reports, to draw reports faster for a longer duration of time period. HP Insight Control virtual machine management In this release, HP Insight Control virtual machine management has added support for the following features and enhancements: New hypervisor support Microsoft Windows Server 2012 (Standard and Datacenter Editions) VMware ESXi 5.0 Update 2 New CMS Support Microsoft Windows Server 2012 (Standard and Datacenter Editions) New SCVMM Support Microsoft System Center Virtual Machine Manager 2012 Service Pack 1 (SP1) HP Insight Control performance management In this release, HP Insight Control performance management has added support for the following: Hardware HP ProLiant SL4540 Gen8 HyperStorage System HP ProLiant SL4545 G7 HyperStorage System Software Microsoft Windows Server 2012 (Standard and Datacenter Editions) RHEL 5.9, Vmware ESXi 4.1 Update 3, and VMware ESXi 5.0 Update 2 as a managed node Microsoft Windows Server 2012 with Hyper-V, and Microsoft Hyper-V Server 2012 Enhancements 7

8 Prerequisites Hardware, firmware, and software requirements for this release are listed in the Insight Management Support Matrix. Installation and upgrade prerequisites are documented in the Insight Management Support Matrix. These documents are available on the HP Insight Management website. Installation instructions Installation instructions are documented in the Insight Management Installation and Configuration Guide available on the HP Insight Management website. Issues and suggested actions Issues and limitations of this release are listed below, organized by HP Insight Control product or functional area. The following categories are used. If a product area has no limitations or issues, that category will not appear. Limitations Major issues Minor issues HP Insight Manager Online Help Limitation Limitations of the implemented functions and features of this release Issues that may significantly affect functionality and usability in this release Issues that may be noticeable but do not have a significant impact on functionality or usability When a search in the online help results in no hits, the system returns a truncated form of search terms that have many characters For example, when there are no hits for Orchestration, your search returns no results for orchestr. This is expected behavior. Suggested Action See the HP Systems Insight Manager Release Notes under Known Issues for additional information. HP Insight Control power management NOTE: All of the following issues apply to Linux and HP-UX. Limitations Power delivery devices should not use a resolvable hostname Power delivery devices should not use a name (or hostname) that conflicts with any other hostname that is resolvable to an IP address in the datacenter (irrespective of whether that name is discovered in HP SIM or not). If a power delivery device is created with a name that is a resolvable hostname, HP SIM starts discovering with this IP address. When this occurs, power management analysis views that attempt to display the power delivery device and may report the following error message: Circuit {Name} does not exist. To correct this situation, you must correct the system type of the {Name} to be a power delivery device by performing the following: 1. In the Systems Insight Manager Search box, enter the {Name} to find the System page for {Name} and click on the link for {Name}. 2. Click the Tools & Links tab. 8 Insight Control release notes

9 3. Click the Edit System Properties link. 4. Change the System type: option to Power Delivery Device. 5. Ensure that the Prevent the Discovery, Identification and Data Collection processes from changing these system properties is checked. 6. Click OK. Incompatibility between Internet Explorer 7 and Adobe Flex When typing targets with system name in the Define Rules page, click the search box in the left panel of the HP Systems Insight Manager to determine whether the system can be discovered, then click the target box in Data Center Power Control to type the system name discovered. The text field becomes inaccessible. NOTE: This issue applies to ProLiant systems only. Major issues Minor issues Use another supported browser. Scheduled tasks for Power Regulator or Power Cap are not listed under Scheduled tasks list or not editable If you have scheduled a Power Regulator or Power Cap task using Power Management 6.0 or earlier and when you upgrade your system to Power Management 7.2, the task may not be listed in the Scheduled tasks list or may result in failure when you try to edit the task. Delete the existing power regulator or power cap task and schedule new task. Error messages or incorrect graphs are displayed for the Power/Thermal graphs Error messages or incorrect graphs are displayed for the Power/Thermal graphs when the graph redisplay or refresh data is activated multiple times in close succession. Do not activate graph redisplay or refresh data multiple times in close succession. Immediate Power data collection is not happening for racks and datacenter For the unmanaged node to receive power data information, perform one of the following steps. Calculate power history using the Reports Power Management Calculate Power History menu option. Click Refresh Data from the Display Power/Thermal data page to refresh the data for the unmanaged node. The web browser crashes while creating/editing a datacenter or rack The web browser crashes while creating/editing a datacenter or rack. The crash information dialog in Mozilla Firefox (about:crashes) may contain the following signature: Caused by a plugin: Shockwave Flash (npswf32.dll) Download and install the supported version of Adobe Flash player from flashplayer. Issues and suggested actions 9

10 Unable to shut down the hosts and guests in either a forced or graceful manner VMware ESXi versions do not support SSH capability. A manual shutdown of the guests or hosts will be required. The hosts and guests can be powered on and off until HP more fully integrates power management with VMware vcenter. Inconsistent system details displayed when multiple browser instances opened sharing the same user session If you have multiple browser windows open to view different systems and these browser instances share the same browser session, inconsistent system details data can be displayed inside some of the browser instances. Refresh the browser window that displays inconsistent system details. Start and sign in to HP Systems Insight Manager using separate browser session: For Microsoft Internet Explorer 8 (IE8), click File->New Session to start the new browser session. For Mozilla Firefox, start multiple browser sessions using separate profiles. For example, firefox.exe -no-remote -P profile_name. Unable to display graphs and reports when the time difference between the CMS and Onboard Administrator is more than 24 hours HP Insight Control power management cannot display power/utilization/temperature graphs if the time difference between the CMS and managed node is more than 24 hours, although data collection status reports as successful. Power data is stored based on the managed node's time. If the date and time on the CMS and managed nodes are inconsistent with their respective time zones, then change the date and time to be consistent with their respective time zones. HP Systems Insight Manager may not recognize the installed HP Insight Control power management that followed immediately after an uninstallation of power management When uninstalling HP Insight Control power management from HP-UX, HP Systems Insight Manager will be restarted. If power management is installed immediately after it is uninstalled and before Systems Insight Manager has fully restarted, power management will be installed successfully but Systems Insight Manager may not recognize that power management is installed. Use mxstatus to verify that Systems Insight Manager has fully restarted before attempting to install power management. Use the mxstop and mxstart options to install the tools waiting to be installed. Crystal Reports: Racks in datacenter views show wrong color in Japanese The DataCenter View page on these reports shows each rack in the datacenter in the column and row it occupies by color, which represents the maximum recorded temperature for equipment in that rack. That maximum temperature value is also displayed in the view. When you run the reports in Japanese, the colors do not reflect the temperature; instead, they are random colors. However, the temperature still shows the correct value in the Japanese reports. Run the report in English or ignore the color of the racks and look only at the temperature value displayed in the racks. 10 Insight Control release notes

11 Insight Control power management can underreport consumer power, resulting in the appearance of a large drop in power Underreported use of consumer power can appear in the Power/Thermal graphs as large stair-step drops in power when you view the power history of the rack and datacenter. However, not all graphed power drops are due to underreporting, so not all power drops should be considered false. Use the Clear Calculated History tool to clear the history of the rack, datacenter, and so forth and then use Calculate Power History to re-aggregate the history power data. Then view the Power/Thermal page to see the revised results. HP Insight Control server migration Limitations Major issues HP Insight Control server migration does not at this time support multipath I/O on Windows In this release, HP Insight Control server migration supports multipath I/O only on Linux with the source system configured on multipath and the destination system configured on a single path. Multipath I/O on Windows is planned for the future. Agent launch from the CMS to a source server with, :, or \ characters in the password is not supported Windows source agent deployment does not support Administrator passwords that contain the, :, or \ characters. SLES11 SP2 with Errata kernel migration is failing on Gen8 servers Use the following procedure to resolve SLES11 SP2 with Errata kernel migration failing on Gen8 servers: 1. Copy and rename the xml file to xml in the <SMP Installation base>\dudprofile\suse folder. 2. Update the line <module ssorder= 32 ipversion= 1.10 >/scsi/hpvsa.ko</module> to <module ssorder= 32 ipversion= 1.10 srckernel= >/scsi/hpvsa.ko</module> in the xml file. 3. Restart the server migration service and proceed with the migration. Unable to detect HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter configured as iscsi disk in step 5 of migration wizard When you start an X2P migration of any OS from any server to any supported ProLiant Gen8 servers with HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter configured as iscsi disk and then start an auto boot in step 3, you will observe that the adapter is not detected in step 5 of migration wizard and displays the following error message: HP Insight Control could not find any disks on destination server Disable IOMMU in RBSU. Issues and suggested actions 11

12 Minor Issues Microsoft Windows 2008 R2 SP1 does not boot on any ProLiant Gen8 with Emulex Le1205A FC storage controller After a successful migration of Windows 2008 R2 SP1 to any ProLiant Gen8 configured with Emulex Le1205A FC storage controller, the OS does not boot up on the destination server. During migration, make PSP installation the default option. Operating system will fail to boot on destination server after migration when existing logical volumes are not erased on destination disks After a completed Insight Control server migration, the OS may not boot on the destination server. This issue occurs if a server is repurposed and the following criteria is met: This issue may occur if the disks attached to the primary storage controller are not clear of logical volumes, which may have been created previously with the controller configured in RAID mode. For example, the server was configured to use Controller in RAID mode and had some logical volumes created on it. Now, if the same controller is configured in non-raid mode without erasing the logical volumes and migration is performed, the OS will fail to boot up. The server will continue trying to boot from the disk in endless loop. Perform one of the following actions: Configure the controller in RAID mode and erase all logical volumes, then reconfigure the controller into non-raid mode and run the migration again. Configure the server to use the RAID mode of the controller and run migration. Verification of Digitally Signed Application could possibly fail on some Microsoft Windows servers If the Microsoft Windows server does not contain the VeriSign Class 3 Public Primary Certification Authority - G5 root certificate, the digital signature verification for the application may fail. The verification failure occurs on servers that do not have the latest ROOT certificate update from Microsoft. The latest updates may not be available for reasons such as Windows update has been disabled and server is not connected to the internet. Perform the instructions from VeriSign available from the VeriSign website. SPP is not applied on ProLiant Gen8 servers After successful migration to the Microsoft Windows 2008 SP2 (x32 and x64 bit) operating systems, SPP does not get applied on ProLiant Gen8 servers. But, the post migration log file (c:\windows\ temp\smppostmigration.txt) lists the status as complete with the following message: Post Migration Script for HPSPP DONE Manually install the SPP. Windows migrations are not supported for more than 14 partitions on a single disk If you select 14 partitions or more on a Windows OS, then the following error is displayed in Step 4 of the V2V migration wizard: The destination disk <target disk name> has reached its partition limits. Try migrating one or more Volume Groups selected for this disk to another disk or go to 'Step 2' of migration wizard to deselect few partition/volume Group. 12 Insight Control release notes

13 The maximum number of partitions supported for Windows migration is 13 for a single disk. To resolve this issue, perform one of the following: You can migrate one or more Volume Groups selected for this disk to another disk. Go to Step 2 of the migration wizard to deselect a few partitions/volume Groups. The name of HP Ethernet 1Gb 4-port 331i-SPI Adapter is displayed incorrectly When X2P migration is initiated to HP ProLiant DL 580 G7 configured with HP Ethernet 1Gb 4-port 331i-SPI Adapter and when you manually boot the destination server with HP Insight Control server migration ProLiant Boot CD, the NIC name is not shown correctly under System Information and Network Configuration pages. The name is displayed as Broadcom Corporation, Unknown device instead of HP Ethernet 1Gb 4-port 331i-SPI Adapter. No action required. HP Insight Control server provisioning NOTE: For additional issues and suggested actions, see Troubleshooting index in the Insight Control server provisioning Online Help. First Time Setup Issues Appliance host name does not allow more than 6 characters in the top-level-domain During initial set up, if the right most label or the top-level domain has more than 6 characters, the following validation error appears: The virtual IPv4 host name has no corresponding address. The specified domain name has an invalid format. Make sure that the top-level domain of the appliance host name is 6 or less characters. The time on your ESXi VM host must be accurate or the appliance may hang after first time network setup Make sure the ESXi VM host has the time set correctly, otherwise the appliance may hang at the Please wait while the appliance starts screen. 1. Either manually set the time on the host, or, use the Linux /bin/date command to set the current time. 2. Reboot the appliance. Console browser may display an empty "Servers" screen after entering First Time Network setup information After entering the network information on the console during initial appliance setup and clicking OK, the "Applying network settings" screen displays at first, but then the "Servers" screen displays a message that it cannot retrieve any servers. This is expected and can be ignored. Do not do anything in this mode. The appliance reboots after one to two minutes. Appliance may not reboot automatically after entering First Time Network setup information After entering the network information on the console during initial appliance setup and clicking OK, the appliance may hang at the "Applying network settings" screen and not reboot. Issues and suggested actions 13

14 Limitations If the appliance does not reboot within 10 minutes, use the VMware tools to reboot the server manually, and then log in again with your new Administrator password. The network setting screen displays the information you already entered. Click OK and the settings will take effect and the appliance will reboot again. You can then use the appliance normally. Maximum number of jobs for display in the IC server provisioning GUI is limited For performance reasons, the number of jobs that can be displayed on the Jobs screen is capped between 800 and 1200 jobs. This number varies dynamically based on when the jobs are run. HP recommends the following options: Discover servers in chunks of 200 at a time so that the results of those discoveries can be reviewed before going on to the next chunk. If deploying many servers at once in Insight Control server provisioning, a single job is created. However, if deploying servers one at a time, as is done when using Matrix OE where each server action generates several Insight Control server provisioning jobs, consider deploying servers in chunks of 150 at a time to be certain all the job results can be examined before proceeding to the next chunk. Version of curl used in Insight Control server provisioning appliance backup/restore scripts must have SSL support The backup script provided in the IC-server-provisioning-backup-restore zip file fails if the curl version being used does not support SSL. The following error appears: Download error: Could not download the backup Verify that the version of curl contains SSL support by running the curl V command. If it does not support SSL, download a version of curl that supports SSL (such as download/curl win64-ssl-sspi.zip for 64bit Windows). Searching for objects can fail if the search query contains special characters Using the search text box for queries with the special characters such as #, %, &, +, \,, or? can cause the search to fail. Double quotes can still be used, but only for phrase search. For example, a query with phrases such as Red Hat Linux yields a successful phrase search. For successful searches, do not use characters such as #, %, &. +, \,, or? in your search query. QLogic HBA (SN1000Q) option card is not supported for Insight Control server provisioning when deploying RHEL 5.9, SLES 11.2, and VMware ESXi 5.x. Support for RHEL 5.9, SLES 11.2, and VMware ESXi 5.x will be provided in a future release. If the.zip file containing your winpe image contains characters like ( or ) in its name, the upload of the file will fail The file name of the.zip file for the winpe image cannot contain special characters such as an open or closed parentheses. Remove the special characters from the.zip file name. 14 Insight Control release notes

15 Windows 2008 SP1 and Windows 2008 R2 OS Build Plan may fail on Gen8 servers with Emulex LPe1205 HBA configured with open zoning After installing Windows 2008 SP2 or Windows 2008 R2 on a server with an Emulex LPe1205 HBA, the server may fail to boot from SAN and continuously reboot itself. Reconfigure HBA with fabric zoning. Refer to the HP SAN Design Reference Guide located at: OS Build Plan may fail on servers with an HP NC551m or NC551i FlexFabric Network Adapter During first production boot, the OS Build Plan my fail on ProLiant servers with an HP NC551m or NC551i FlexFabric Network Adapter and operating system RHEL 5.9, RHEL 6.3, Windows 2012, or VMware ESXi. A Buffer I/O Errors and Kernel Panic or Blue Screen may display. This typically occurs when the server is configured with FCoE and/or Boot from SAN. 1. Set the HP Power Profile mode in the ROM-Based Setup Utility (RBSU) to the "Maximum Performance" setting by performing the following steps: a. During system boot, press F9 to enter the RBSU. b. Select Power Management Options. c. Select HP Power Profile. d. Select Maximum Performance option. e. Save and exit RBSU. 2. Re-run the OS Build Plan. RHEL 5.9 OS Build Plan may fail on ProLiant servers configured with SAN multipath RHEL 5.9 OS Build Plan may fail on ProLiant servers configured with SAN multipath and the following error appears in the target console: Unable to create LVM partition RHEL 5.9 requires a special kernel argument, mpath, to correctly configure SAN multipath devices. For a single server, using the Insight Control server provisioning user interface, set the kernel_arguments custom attribute at server level with the value mpath. 1. Open the Servers view in the Insight Control server provisioning interface. 2. Select the server with the error and select Actions > Edit. 3. From the Edit server screen, select Create custom attribute. 4. On the Create Custom Attribute screen, set the kernel_arguments value to mpath. 5. Click OK to save the custom attribute. If all servers in the environment are configured as SAN multipath, then the custom attribute can also be defined at Facility level (select Settings > Facility Custom Attributes), so that the custom attribute is inherited by all servers in the environment. The mpath kernel argument forces RHEL 5.9 to treat the server as a SAN multipath environment. When this argument is used with servers configured with SAN single path, the installation may fail. Do not use the mpath argument for servers configured with a SAN single path. OS Build Plan may fail if Media Server user password contains special characters If the password used in the Media Server Settings contains any of the following special characters: '@' (an at sign), '#' (a pound sign), '/' (a forward slash), ':' (a colon), '\\' (two backward slashes), or '?' (a question mark); then, the OS Build Plan fails with the following error: Issues and suggested actions 15

16 Major issues Failed To Set Media Source: NET use Z: /USER:xyz /persistent:no ****** failed with exit code 2. Do not use the at sign a pound sign (#), a forward slash (/), a colon (:), two backward slashes (\\), or a question mark (?) in the password for the media server user. Install Linux OS Build Plan will fail if port 1002 on target server is not open When installing a Linux OS in which the firewall has been enabled, port 1002 must be opened for TCP connections on the target server to allow communication with the SA agent. If port 1002 is not opened, the OS installation will fail at the final Wait For HP SA Agent step. If a firewall is enabled on your target server, open port 1002 in the Kickstart/Autoyast configuration file before attempting to install a Linux OS. Create Stub Partition error occurs during a PXE-less deployment of a Linux OS Build Plan The following two use cases may cause the Create Stub Partition step to fail with the following error during a PXE-less deployment of a Linux OS Build Plan. Device /dev/sde is busy, cannot create stub partition error 1. The boot disk and one or more other disks on the target server contain a previously installed Windows operating system. 2. The boot disk on the target server is connected to a SAN with a multi-path configuration and contains a previously installed Windows operating system. 1. Edit your Build Plan and add the Unmount All Boot Disk Partitions step before the Create Stub Partition step. 2. Re-run the Build Plan. The boot step of a Build Plan may fail on Gen8 servers On rare occasions, the boot step of a Build Plan may fail on Gen8 servers with the following ilo error: IloException:ID: HPSA-1915 Code: com.opsware.ilo.ilo_write_blob_store_failure Details: An error occurred while performing writeblobstore operation. Cause: [ilo ( )] Error : Internal error. Action: Please contact your SA administrator. An attempt to re-run the Build Plan, or another Build Plan, results in the same error. The ilo must be restarted in one of the following ways: 1 1. Establish a connection to the ilo via a browser and log in using your ilo credentials. 2. Select Information Diagnostics 3. Press Reset. Your browser connection is lost while the ilo resets Establish an SSH connection to the ilo and log in using your ilo credentials. 2. At the ilo prompt, enter reset map1. After ilo resets, the SSH connection disconnects. 16 Insight Control release notes

17 A Linux or ESXi OS Build Plan may fail with a copy boot error A Linux or ESXi build plan may fail with error message: Copy Boot Media failed with exit code 3 Possible cause 1 The OS distribution is not present in the Insight Control server provisioning Media Server. 1 Run the Insight Control server provisioning Media Server Setup utility on the Media Server to copy the OS distribution to the correct folder. Or manually copy the distribution to the correct folder location. Possible cause 2 The OS distribution is present but the build plan still fails. When the build plan tries to reach the URL via a browser where the distribution is present, the following error appears: HTTP Error Internal Server Error The Microsoft Internet Information Services (IIS) web server does not have access permission to the physical folder requested by the browser. 2 Grant read permission to the IIS_IUSRS windows group for the Media Server top level folder: 1. In Windows Explorer, locate the top level folder associated with the Media Server. 2. Right-click the folder and click Properties. 3. Click the Security tab, and then click Edit. 4. Click Add. 5. In the Enter the object names to select box, type <computername>\iis_iusrs, click Check Names, and then click OK. 6. Select the Read check box and click OK. 7. In the Properties dialog box for the folder, click OK. For more information or alternative resolution methods for this problem, please see the KB article from Microsoft: A Linux or ESXi OS Build Plan may fail on servers with ilo On rare occasions, a Linux OS Build Plan may fail at the Wait for HP SA Agent step or an ESXi OS Build Plan may fail at the Wait for ESXi Installation step due to the target server booting into the Intelligent Provisioning environment instead of the target server's Linux or ESXi installation kernel. The build plan failure may be seen on servers with ilo 4 firmware version The target server console appears in the Intelligent Provisioning environment and the following error appears in the Jobs screen: Wait for SA Agent failed with exit code 6 Reboot the target server. If the failure persists, contact your authorized support representative. An OS Build Plan fails at the Wait for HP SA Agent step if the target server s clock does not match the time on the appliance The time on the target server must match the time on the Insight Control server provisioning appliance in order for the HP SA Agent running on the target server to register with the appliance. If the clocks disagree, the registration can fail. During startup, the agent attempts to set the server s clock to the time of the appliance. This corrective action requires certain network ports to be open in network firewalls between the target server and the Insight Control server provisioning appliance. Issues and suggested actions 17

18 Manually set the BIOS clock on the target server. To automate the clock setting, ensure the following ports are open in the network firewalls: For servers booting with a Windows agent, TCP port 445 should be open. For servers booting with a Linux agent, UDP port 123 should be open. Contact your network administrator or consult the documentation for your network firewall on how to open ports. OS Build Plan may fail at the Wait for HP SA Agent step if the target server is not configured properly A red screen can occur on the target server during OS deployment if a USB port is connected to a drive or if there are firmware or BIOS configuration issues. If a red screen is displayed on the target server during deployment, check the following: Make sure that none of the USB ports are connected to a drive. Verify that the target server is running supported firmware. Clear the BIOS and reset the boot record in RBSU. 1. During system boot, press F9 to enter RBSU. 2. In RBSU, select System Default Options Restore Settings/Erase Boot Disk. 3. After reset, if you have configuration settings that are different from the factory default, log in to RBSU to reconfigure your settings. Build plan steps may fail after rebooting a server in production When rebooting a server while the server is in production, the atleast parameter of the Wait for SA Agent step is ignored. Because this parameter is ignored, the target server's OS may not have sufficient time to shutdown and reboot before the next step in the build plan occurs. Subsequent steps after the Wait for SA Agent step may fail because the target server has not finished rebooting. 1. In the Insight Control server provisioning UI, access the Scripts Resource screen and create an Open Global File System (OGFS) script named Sleep to sleep for 3 minutes: #!/bin/bash sleep Add this script to your Build Plan steps, before Wait for HP SA Agent and after Reboot as shown: Reboot Sleep Wait for HP SA Agent (with parameters --production --atleast=3 --atmost=30') Add server or deploy OS Build Plan may fail if the target server has more than one NIC connected to the deployment network In adding a new server, Insight Control server provisioning may fail to discover a server which has more than one NIC connected to the deployment network at the time. The server s job list shows the ilo add was not successful. In addition, after a successful discovery, an OS Build Plan may fail with the following error if more than one NIC is connected: Wait for HP SA Agent failed with exit code 6 18 Insight Control release notes

19 Make sure one and only one NIC on the target server is being used as the deployment NIC, and make sure that NIC is accessible via the appliance either directly or through a router. Installing Linux SPP Build Plan may fail at the Set Media Source step if the Media Server is part of a Windows domain If the Windows Media Server is part of a Windows domain, and the username is not in one of the following formats, the Set Media Source step fails: Domain\username Hostname\username To correct the username: 1. Make a copy of the Install Linux SPP Build Plan. 2. Modify the Set Media Source step in the Install Linux SPP Build Plan by adding,domain=media_server_host_name to the end of the following OPSW-Media-WinUser@@ OPSW-Media-WinPassword@@ OPSW-Media-WinPath@#/mnt/ms?noserverino The new parameter should OPSW-Media-WinUser@@ OPSW-Media-WinPassword@@ OPSW-Media-WinPath@#/ mnt/ms?noserverino,domain=media_server_host_name NOTE: The parameter value must not contain any spaces. 3. Save the Build Plan. 4. Run the new Build Plan. RHEL 6.3 OS deployments fail on servers with iscsi or FCoE due to automatic disk partitioning in default kickstart file Target servers with iscsi or FCOE require advanced configuration of the kickstart file. Otherwise, the automatic disk partitioning (Autopart) in the default kickstart file creates an error when installing to these systems. Create a custom kickstart file with the required settings. Autopart must be commented out. See the example partitioning instructions below. part /boot --fstype=ext4 --size=500 part pv.01 --grow --size=1 volgroup vg_01 --pesize=4096 pv.01 logvol / --fstype=ext4 --name=lv_root --vgname=vg_01 --grow --size=1024 logvol swap --name=lv_swap --vgname=vg_01 --grow --size= maxsize=20480 Changing the deployment IP address of the Insight Control server provisioning appliance once it has been initially set is not supported Even though the user interface allows the deployment IP address of the appliance to be changed and this feature is listed in Online help, the IP address should not be changed once it is initially set. If the deployment IP address was changed after it was set initially, delete all of the target servers, add the target servers, and then reinstall with a new OS so that the SA agent on these target servers can communicate with the new deployment IP address. Issues and suggested actions 19

20 Minor issues RHEL 5.9 deployment may fail during reboot after OS installation On rare occasions, the RHEL 5.9 x64 OS Build Plan may fail at step 17 Wait for HP SA Agent so that the target server may not reboot after OS installation. The target server console shows "Congratulations, your Red Hat Enterprise Linux Server installation is complete" indicating the operating system was installed on the target server. However, the SA agent installation did not complete and the target server does not reboot as instructed by the previous OS Build Plan step. In Matrix OE, the following error appears on the infrastructure orchestration Requests screen and the failed server is moved to the maintenance pool: Major,"Failed while deploying operating system for service <server-name>. Cause: Logical server job (ID = <server-fqdn>) completed with a failure status. Failure: At least one OS or software deployment has failed. Check the Deployment Service to diagnose the details.." If the server is being deployed through Insight Control server provisioning, rerun the OS Build Plan. If the build plan fails again, contact your authorized support representative. If the server is being deployed through Matrix Operating Environment, perform a manual clean up: 1. Delete and clean the boot disk. 2. Deactivate the logical server associated with the target server. a. From the HP Matrix Operating Environment menu, click Tools HP Matrix OE Visualization. b. Select Logical Server from the Perspective drop-down menu. c. Select the logical server and click Tools Logical Servers Deactivate... d. Monitor the status of the task by selecting Report Logical Server Job Status. e. Wait for the task to complete successfully before continuing to the next step. 3. Select the deactivated logical server and click Delete Delete Logical Server Move the target server from the IO maintenance pool to the desired server pool. a. From the HP Matrix Operating Environment menu, click Tools Infrastructure Orchestration. b. Click the Servers tab and verify that the Usage column indicates that the servers are not in use. c. Move the servers under the maintenance pool to the desired server pool by using the Modify Pool option. 5. Remove the managed node from the IC server provisioning server. A server s ilo may not get registered when the server is PXE-booted When adding a server to Insight Control server provisioning via a PXE boot, the Registers IloManagerService job may fail preventing the registration of ilo on the server. The following message appears: Cannot add user. The login/ user name already exists. This error can occur if there is an existing ilo user account where the User Name or Login Name field contains a <, >, or double quote character. Do one of the following actions: 1 1. Using a browser, connect to the ilo and the User Administration page. 20 Insight Control release notes

21 2. Edit the user accounts containing the <, >, or double quote characters in the User Name or Login Name field, removing those characters. 2 Add the server to Insight Control server provisioning: 1. Select Servers Add Server. 2. Enter the ilo s IP address and credentials. The ProLiant HW - Erase Server Build Plan may fail on the final Boot step The Reboot to apply BIOS Changes and Power Off step may not allow sufficient time for some servers to apply the BIOS changes, causing the subsequent Boot step to fail when it is attempting to set the one-time boot. NOTE: Even though the build plan failed, the disk on the target server will have gotten erased. 1. Make a copy of the ProLiant HW - Erase Server build plan. 2. Add the --wait 180 parameter to the Reboot to apply BIOS Changes and Power Off step so that the Build Plan will succeed the next time it is run. 3. Power off the target server to ensure that another Build Plan can be run on this server. Windows OS Build Plan may fail if deployed during the initial 24 hours after completing First Time Setup An OS Build Plan that installs a Windows OS image that has been localized or otherwise customized to use a time zone that is earlier than Pacific Standard Time (for example, Tokyo Standard Time) may fail on the final Wait for HP SA Agent step if deployed during the initial 24 hours after completing First-Time Setup (FTS) of the IC server provisioning appliance. The failure occurs due to improper handling of certificate validity dates. The certificates become valid for all time zones 24 hours after FTS. 1 Wait for 24 hours after FTS for the certificates to become valid. 2 Although the build plan will fail, the Windows OS will be installed and booted into production; however, the target server s clock will likely be incorrect and the SA agent on the target server will not be able to communicate with the IC server provisioning appliance due to the target server s clock not being correct. To fix the target server, perform the following steps: 1. Log into the target server. 2. Manually fix the clock time. 3. Reboot the server. 3 Perform the following steps during the initial 24 hours: 1. Create a script that advances the time on the target server by 24 hours. For example, create a Visual Basic Script named TimePlus24h, using a copy of An Empty Template Windows VBScript : Scripts An Empty Template Windows VBScript Actions Save as TimePlus24h 2. Edit the script TimePlus24h and add the following commands: Option Explicit Dim strnow Dim strdatetime, sdt1, sdt2 Dim shell Issues and suggested actions 21

22 strnow = Now strdatetime = DateAdd("h", 24, strnow) sdt1 = Left(strDateTime, 10) sdt2 = Right(strDateTime, 8) Set shell = wscript.createobject("wscript.shell") shell.exec "cmd /C date " + sdt1 shell.exec "cmd /C time " + sdt2 Set shell = Nothing Add a step to run the script TimePlus24h in your Windows OS Build Plan. Insert the step after Integrate HP SA Agent and before Reboot. 3. Run the OS Build Plan hours after FTS, edit the Windows OS Build Plan and remove the TimePlus24h step. SLES 11 SP2 does not handle multipath SAN appropriately when displaying all drives The deployment completes successfully via the Insight Control server provisioning OSBP, but after the production OS Boots, you will see duplicate drives for those with multiple paths. There is no workaround and this has been reported to SUSE. It will be fixed in a future release. Note that the OS deployment completes successfully even though you will see duplicate drives for those with multiple paths. BL2x220c G7 servers cannot be added to appliance using the PXE (Preboot Execution environment) discovery method Add the BL2x220c G7 server to your appliance selecting Actions > Add Server. or Script the ilo discovery using the add server REST call documented in the HP Insight Control server provisioning Administration Guide. ProLiant SW Install Windows SPP OS Build Plan may incorrectly appear to complete successfully when it did not The ProLiant SW Install Windows SPP OS build plan may appear to complete successfully, even though the connection to the media server was not valid or the SPP version did not exist on the media server. When this occurs, the job status will return success, but you will see errors in the OS build plan log file that look similar to the following: The system cannot find the drive specified. The system cannot find the path specified. The network connection could not be found. 1. Verify that the Set Media Source script step in the OS Build Plan is included and completes successfully. 2. Verify there are SPP files on the media server under \media\spp. Navigating to the Online Help for the User Page might lead to a blank page if the User Page is reached via the top right User icon Navigate to the User Page from the Settings menu before accessing Online Help. 22 Insight Control release notes

23 The ilo may become unresponsive causing steps in Build Plan to fail The ilo may become unresponsive to certain commands that HP Insight Control Server Provisioning uses to control the behavior of the server. This may prevent the Boot build plan step from booting to the service OS specified in the --serviceos parameter, which causes the subsequent Wait For HP SA Agent build plan step to fail. Suggested Action Reset the ilo by doing the following: 1. Etablish an SSH connection to the ilo. 2. Log in using your ilo credentials. 3. At the ilo prompt, type reset map1. When the ilo is reset, you are disconnected from SSH. Build Plan may fail server if server has not rebooted into Production OS When another build plan is launched immediately following the Install Linux SPP build plan, it may fail to run with error messages indicating Cannot configure ilo One Time Boot. Suggested Action Ensure your target server has rebooted back into the Production OS before running another OS build plan. HP Insight Control server deployment Limitations Network installation of RHEL 6.1 fails on HP P6000 EVA servers Network installation of RHEL 6.1 fails on HP P6000 Enterprise Virtual Array servers with the following message: Error was encountered while formatting device /dev/mapper/mpthap1 for RHEL 6.1. This remains a limitation; however, the HBA vendor recommends consulting with Red Hat or using a small configuration. Deploying SLES 11 SP1 x64/x86 to Gen8 servers and Servers with IL processors using ICDepl 7.0 Perform the following steps to deploy SLES 11 SP1 x64/x86 to ProLiant Gen8 servers and Servers with IL processors using ICDepl 7.0: X64 Gen8 1. Copy and rename the existing SLES 11 SP1 x64 job to ProLiant Gen8 - Deploy SLES 11 SP1 x64 (EN-US) or any convenient name. 2. Edit Run Script - Configure Boot Environment to pass the KISO parameter. Change export kiso=no to export kiso=gennext. 3. Copy the extracted ProLiant Gen8 SLES 11 SP1 x64 KISO to hpfeatures/sles11sp1x64/oem/errata-gennext/. G7IL Issues and suggested actions 23