HP Insight Control for VMware vCenter Server User Guide Abstract This document contains detailed instructions for configuring and using HP Insight Control for VMware vCenter Server. The intended audience is system administrators who are experienced in virtual and physical IT infrastructure administration and understand server virtualization, storage, and networking concepts.
© Copyright 2011 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. The information contained herein is subject to change without notice.
Contents 1 Overview..................................................................................................6 2 Configuring Insight Control for vCenter..........................................................7 Configuring the Server Module for vCenter..................................................................................7 Onboard Administrator Single Sign-On..................................................................................8 Associating the VMware host to iLO.............
Customizing Storage Module for vCenter tables.....................................................................35 Viewing VM or datastore overview information......................................................................36 Viewing storage information for a host..................................................................................36 Viewing storage information for a cluster...............................................................................
Clicking HP Insight power management launch link does not go to expected HP SIM page.........78 Cost Advantage field not showing values..............................................................................78 Events not delivered by Insight Control for vCenter to vCenter Server.........................................78 Firmware inventory information is not shown..........................................................................
1 Overview HP Insight Control for VMware vCenter Server (Insight Control for vCenter) includes the core Insight Control capabilities for VMware vCenter Server, the HP Insight Control Server Module for vCenter (Server Module for vCenter), and the HP Insight Control Storage Module for vCenter (Storage Module for vCenter). Insight Control for vCenter is delivered as a single integrated application. The application consists of three modules.
2 Configuring Insight Control for vCenter After installation, configure the server and storage modules. IMPORTANT: Proxy-enabled Windows clients can fail to communicate with an ESX host using iLO 3. If this occurs, you must disable or bypass the Windows Proxy Server for the connection between the Insight Control for vCenter/vSphere client and iLO 3 on the ProLiant server running as an ESX/ESXi host system. For instructions, see “Error Communicating with iLO at VM host” (page 76).
Onboard Administrator Single Sign-On To enable SSO, you must upload the Insight Control for vCenter certificate to the Onboard Administrator. 1. On the Onboard Administrator, navigate to Users/Authentication→Local Users→HP SIM Integration. 2. Set the trust mode to Trust by Certificate. 3. Locate and copy the certificate using one of the following methods: • In the vSphere Client, access the HP Home Settings page. See “Configuring the Server Module for vCenter” (page 7).
4. Enter the iLO Username, iLO Password, iLO IP address and iLO MAC address, and then click OK. Using the Insight Control for vCenter Properties page 1. 2. 3. Select a host, and then click the HP Insight Software tab. Click the Properties link in the upper right corner. Enter the iLO IP address or Host name, and a User Name and Password. NOTE: If global credentials have been supplied using the Insight Control for vCenter setup wizard, only the Host name needs to be entered.
servers. After you configure storage arrays and management servers, configure the VMware VASA provider (optional). For information about initialization and the Storage Administrator Portal, see “Checking the initialization status” (page 10) and “About the Storage Administrator Portal” (page 10). For configuration instructions, see “Configuring arrays and management servers” (page 11) and “Configuring the VMware VASA provider” (page 19).
Figure 2 Setting storage pool access To access the Storage Administrator Portal: 1. Log in to the vSphere Client. 2. Select a host, VM, or datastore, and then click the HP Insight Software tab. 3. Click Overview in the HP Management pane. 4. Click the Properties link. 5. Click the Storage Properties tab. The list of configured arrays and management servers appears, displaying the array name, type, model, firmware, identifier, managers/managing, storage pools, and storage pool access settings.
2. 3.
TIP: Click Add All or Remove All, respectively, to add or remove all arrays. The Add HP P6000 Command View (4 of 4) page appears, listing the storage pools on the selected P6000 EVA arrays. If you selected one or more passively managed P6000 EVA arrays, you must configure the storage pool access for those arrays when you add their active P6000 Command View management servers. 6. Select the Full Access check box for one or more storage pools to enable provisioning by the Storage Module for vCenter.
6. Click Next. The Add P6000 EVA (3 of 3) page appears, listing the storage pools on the selected P6000 EVA array. 7. Select the Full Access check box for one or more storage pools to enable provisioning by the Storage Module for vCenter. If you will not perform provisioning operations on a particular storage pool, you do not need to enable Full Access for that storage pool. 8. Click Finish. The array is added to the Configured Arrays and Management Servers list.
IMPORTANT: You must install version 1.1.2.0 of the MSA SMI-S proxy provider to add support for the MSA in your VMware environment. Earlier versions of the MSA SMI-S proxy provider are not supported by the Storage Module for vCenter. For installation instructions, see the MSA SMI-S proxy provider documentation. P6000 Command View and the MSA SMI-S proxy provider cannot coexist on the same server. 3. Log in to the Storage Administrator Portal.
8. Click Finish. The P2000 G3 MSA System is added to the Configured Arrays and Management Servers list. Adding HP P9000 arrays To add an HP P9000 array: 1. Verify that a command device from the P9000 array is presented to the host running the Storage Module for vCenter. 2. Log in to the Storage Administrator Portal. For instructions, see “About the Storage Administrator Portal” (page 10). 3. Click Add. The Add Storage Array or Management Server (1 of ...) page appears. 4.
5. Click the Storage Properties tab.
2. Select an array or management server in the Configured Arrays and Management Servers list, and then click Modify. The Modify management server or array type page appears. 3. Depending on the array type, do one of the following: • For P6000 Command View management servers, P4000 arrays, and P2000 G3 MSA arrays: Enter the required user name and password, and then click Next. NOTE: When working with P6000 EVA arrays, this step is required for P6000 Command View management servers only.
2. Select an array or management server in the Configured Arrays and Management Servers list, and then click Remove. The Remove array or management server type page appears. 3. Click Yes to confirm that you want to remove the array or management server. Configuring the VMware VASA provider If you want to use the VASA functionality in the vSphere Client, add the Storage Module for vCenter to the vendor providers list and add a CA-signed certificate.
4. 5. 6. 7. Select Generate a Certificate Signing Request. Enter the following information: • Country • State • Locality • Organization • Common Name – The fully qualified vCenter Server name. If desired, enter the following information in the Optional Certificate Info section: • Organizational Unit • Email • Surname • Given Name Click Generate. The certificate signing request is generated (see “Certificate request” (page 20)). Figure 4 Certificate request 8. 9.
3 Using Insight Control for vCenter This chapter describes the processes for accessing and using the software. Accessing Insight Control for vCenter After completing the installation and configuration procedures, you can access Insight Control for vCenter using the vSphere Client: 1. Start the vSphere Client. 2. When prompted, enter the IP address/host name, user name, and password to sign in to the vCenter Server. 3. Do one of the following: 4. 5.
For the Server Module for vCenter, the Overview page includes health status information and links to iLO, Onboard Administrator, HP SIM, and Virtual Connect Manager. For the Storage Module for vCenter, the Overview page includes a link to the array management software (if available), and the array health status information (Green, Yellow, or Red, which indicate Info, Warning, or Error status, respectively).
This section describes how to access the following information: • • Cluster management ◦ Health summary ◦ Infrastructure ◦ Power ◦ Firmware Host/Server management ◦ Status ◦ Configuration ◦ Power/Thermal ◦ Networking ◦ Firmware ◦ Logs NOTE: For information about Navigating the HP Insight Software tab with the Storage Module for vCenter, see “Navigating the HP Insight Software tab with the Storage Module” (page 31).
The Cost Advantage value is calculated as follows: Cost Advantage = (number of hours the server was down) × (power cost) × (average power) Entering the Power Cost will only calculate the Cost Advantage if all of the requirements in this section are applicable for the cluster. If the requirements are not met by the cluster, the cost advantage is always zero.
Viewing infrastructure information for a cluster To view information about a selected cluster: 1. Select a cluster in the inventory tree. 2. Click the HP Insight Software tab. 3. Click Infrastructure in the Cluster Management section of the HP Management pane.
To update firmware for the cluster or selected systems in the cluster, complete the following steps: 1. Select the Smart Component Update tabbed page. 2. Select one of the following options and enter the required information: • Update from URL — Enter the URL of a web server from which to distribute the firmware update. • Update from Managed Smart Components – Select one or more updates which you have uploaded using the Managed Smart Components tabbed page (see “Manage Smart Components” (page 26).
Summary tab The Summary tab displays a health summary for the selected HP ProLiant and BladeSystem server. Use this tab to view the server, power, health, and other system statuses reported by iLO, Onboard Administrator, HP SNMP agents, and HP CIM providers. You can turn a system's UID ON from the default OFF position as needed. When the UID is turned off, click the Off link to turn it on. When the UID is on, click the On link to turn it off.
3. Click Power/Thermal in the Server Management section of the HP Management pane. The Power/Thermal page displays the following information: Server tab The Server tab appears automatically and displays the power status, 24 hour power history information, alerts, and other power data as well as fan health status. It also has a link to Insight Control power management if it is in the configuration. Infrastructure tab The Infrastructure tab displays power and thermal information for the enclosure.
Figure 10 Virtual Connect Network Diagram Viewing and updating firmware on selected servers NOTE: Firmware information is available for ESXi systems only. To view firmware information and/or update firmware for the selected server: 1. Select a server in the inventory tree. 2. Click the HP Insight Software tab. 3. Click Firmware in the Server Management section of the HP Management pane.
2. Select one of the following options and enter the required information: • Update from URL — Enter the URL of a web server from which to distribute the firmware update. • Update from Managed Smart Components – Select one or more updates which you have uploaded using the Managed Smart Components tabbed page (see “Manage Smart Components” (page 30)).
Prerequisites Before using the wizard, you must have installed: • HP Insight Control for vCenter • HP RDP from the HP Insight Rapid Deployment website. • HP Deployment Connector (included with Insight Control for vCenter) NOTE: If you try to use the HP Insight Control Deployment Wizard without installing the Deployment Connector, the wizard prompts you to download and install it. Follow the on-screen instructions.
Figure 11 HP Insight Software tab When using the HP Insight Software tab: 32 • Click Properties to view and configure management servers and arrays. For more information, see “Configuring the Storage Module for vCenter” (page 9). • Click Overview in the HP Management pane to view storage and server module information. For more information, see “HP Management pane overview” (page 21). • Click Refresh to refresh the Storage Module for vCenter data that is displayed in the vSphere Client.
• ◦ “Viewing related host information” (page 41) ◦ “Viewing detailed storage information” (page 41) Click Help for context-sensitive help. Refreshing Storage Module for vCenter data After installation, the Storage Module for vCenter collects information about the VMware environment and configured HP storage arrays. By default, this information is refreshed one hour after the previous refresh is complete, unless the vSphere Client has been inactive for three hours.
To start a data refresh immediately: 1. Click the Refresh link in the top right corner of any Storage Module for vCenter page. The HP Insight Software tab displays the options shown in Figure 13 (page 34). Figure 13 Manual data refresh options 2. Click OK to continue the data refresh, or click Cancel to stop the refresh. Canceling a data refresh To cancel a data refresh: 1. Click the Refresh link in the top right corner of any Storage Module for vCenter page.
2. Change the following parameters: • Caching.RefreshInterval: Specifies the time, in milliseconds, to wait between cache refreshes • Caching.InactivityTimeout: Specifies the time, in milliseconds, to wait after inactivity before stopping cache refreshes For example: 3600000 10800000 3. Restart the HP Insight Control Storage Module for vCenter Service.
• Click the triangle icon to the left of a column heading to sort data by the selected column. To sort data in multiple columns, Shift+Click the title of the respective columns. To return to sorting by a single column, click the title of the column. • Customize the tables as needed.
NOTE: The HP Storage Used value might differ from the HP Storage Provisioned value if thin provisioning or demand-allocated snapshots are used. • HP Storage Available in Pool: Amount of available storage in all arrays that are configured in the environment. On each array, the number reflects the difference between configured storage and used storage. Storage Arrays The Storage Arrays section lists the arrays that present disks to the selected host.
NOTE: The HP Storage Used value might differ from the HP Storage Provisioned value if thin provisioning or demand-allocated snapshots are used.
Storage Arrays The Storage Arrays section lists the configured arrays that provide storage to the selected datastore. TIP: To start the array management software, click the management software link (if available). Viewing detailed information Click the Storage Disks, Virtual Disks, or Hosts tab to view detailed information about the selected datastore.
Viewing summary information The Related Virtual Machines page displays the following information for the VMs associated with the selected host, cluster, datastore, or VM: • Name: VM name • VMDK/RDM Provisioned Capacity: Amount of storage provisioned for VM use • VMDK/RDM Used Capacity: Amount of storage used by the VM Viewing detailed information To view detailed information about a VM: 1. Click the row of a VM in the Related Virtual Machines table. 2.
• “Viewing paths” (page 44) • “Viewing replications” (page 47) Viewing related host information To view information about a selected host, hosts where the selected VM's storage is presented, or hosts where the selected datastore's storage is presented: 1. Select a VM, host, or datastore in the inventory tree. 2. Click the HP Insight Software tab. 3. Click Related Hosts in the Storage Information section of the HP Management pane.
NOTE: The detailed information provided in the Storage Module for vCenter tabs might vary depending whether a VM, host, or datastore is selected. For example, the Current Owner column in the Hosts tab is visible only when a VM is selected. Viewing storage disks The Storage Disks tab is displayed in the HP Insight Software tab for selected hosts, VMs, and datastores.
• Array Disk Type: Array disk type and characteristics (for example, HP_LHN_VOLUME, HP_EVA_SNAPSHOT, or HP_XP_THIN_PROVISIONED_VOLUME) • Storage Pool ◦ P9000/XP: Disk group or storage pool used for allocating storage to the disk. This might be a P9000 or XP Thin Provisioning pool, a P9000 or XP Snapshot pool, an internal parity group, or an external group. ◦ P6000 EVA: Disk group where the vdisk is located. This value is displayed only when demand allocated snapshots are used.
• Virtual Disk Allocated Capacity: Disk capacity reserved by VMware for the VMDK or RDM For an RDM, this value will match the provisioned capacity value. For a VMDK, this value might be less than the provisioned capacity value if VMware thin provisioning is used. This is separate from thin provisioning configured in the storage array.
Figure 22 Paths tab This tab displays the following information: • • • • Array Disk Name ◦ P9000/XP: Emulation type and LDKC:CU:LDEV (for example, HP OPEN-V-CVS (00:04:3F)) ◦ P6000 EVA: Path for the virtual disk on the storage array ◦ P4000: Volume name ◦ P2000/MSA2000: Volume name Array Name ◦ P9000/XP: Array serial number ◦ P6000 EVA: Array display name ◦ P4000: Management group name ◦ P2000/MSA2000: System name Host HBA Port WWN/IQN ◦ P9000/XP: WWN for the host port on the host end
• • • Array Port: Storage array's port identifier used for this path ◦ P9000/XP: Port number ◦ P6000 EVA: Port name configured in P6000 Command View ◦ P4000: Not applicable ◦ P2000/MSA2000: Port on the array controller used for this path Hostgroup ◦ P9000/XP: Name of the host group containing the HBA WWN on the array port for this path ◦ P6000 EVA: Name of the host object containing the host WWN for this path ◦ P4000: Name configured for the host's IQN in the management console ◦ P2000/MSA
• Active Path: Specifies whether the path is active or in standby status If a path is active and then goes offline, a standby path takes over. • Path ID: Path ID assigned by VMware Viewing replications The Replications tab is displayed in the HP Insight Software tab for selected hosts, clusters, VMs, and datastores (see “Replications tab” (page 47)).
Figure 24 View All tab The same VM will appear multiple times in this table, based on the number of available paths to a storage disk. To hide duplicate entries, select the Hide duplicate cells option.
• ◦ P4000: IQN assigned to the host ◦ P2000/MSA2000 (FC, SAS): WWN for the host port on the host end of this path ◦ P2000/MSA2000 (iSCSI): IQN assigned to the host Array Port WWN/IQN ◦ P9000/XP: WWN for the storage array port on the storage array end of this path ◦ P6000 EVA: WWN for the storage array port on the storage array end of this path ◦ P4000: IQN used by the host for connecting to this disk on this storage array ◦ P2000/MSA2000 (FC, SAS): WWN for the storage array port on the storage
◦ P4000: Not applicable ◦ P2000/MSA2000: Not applicable • Active Path: Specifies whether the path is active or in standby status • Path ID: Path ID assigned by VMware Using Insight Control for vCenter
4 Provisioning storage The Storage Module for vCenter supports storage provisioning for P6000 EVA, P2000 G3 MSA, and P4000 arrays. You can perform storage provisioning operations such as adding a new datastore, deleting or expanding an existing datastore, creating new VMs, or cloning existing VMs. For P6000 EVA, provisioning operations are supported for thick-provisioned virtual disks.
Changing the default location for all P6000 EVA arrays To change the default location for all P6000 EVA arrays, modify the value \Virtual Disks\ in the following section of the configuration.xml file: \Virtual Disks\ Changing the default location for a specific P6000 EVA array To change the default location for a specific P6000 EVA array, add the following text to the configuration.
2. Use one of the following methods to start the Add Datastore wizard: • Right-click a host or cluster and select HP Insight Software→Add Datastores. • Select a host or cluster in the inventory tree, and then click the HP Insight Software tab. Click Storage Tools in the HP Management pane, and then click the Add Datastores link. • Right-click a host or cluster in any Storage Module for vCenter table, and then select Add Datastores. The Add Datastores – Specify Storage window opens.
Figure 26 Storage Array capacity If there is not enough space available in the selected storage pool, a message is displayed in the Warnings box. • 4. RAID Level: Select a RAID level for the new datastores. The wizard lists all RAID levels supported by the selected storage pool. Click Next. The Add Datastores – Specify New Names window opens. See Figure 27 (page 54). Figure 27 Add Datastores – Specify New Names window 5.
6. Click Next. The Add Datastores – Review and Validate window opens. See Figure 28 (page 55). Figure 28 Add Datastores – Review and Validate window (before validation) 7. Click Next to validate that it is possible to create the datastores. The Review and Validate window is updated with icons showing the success or failure of the validation processes. A green icon indicates success and a red icon indicates failure.
Figure 30 Add Datastores – Summary window 9. Click Finish to create the specified datastores. You can view the progress of the task in the Recent Tasks pane at the bottom of the vSphere Client window. TIP: No manual data refresh is necessary. When a provisioning operation is complete, the Storage Module for vCenter data is refreshed automatically. Expanding a datastore You can expand the size of a datastore if it is located on a single disk. 1. Start the vSphere Client. 2.
Figure 31 Expand Datastore window 3. Enter the requested new capacity in the Requested Datastore Capacity box. The following rules apply when expanding datastores: • A datastore can be expanded only if it is located on a single disk on an array that supports provisioning by the Storage Module for vCenter. • The requested capacity cannot exceed the total capacity of the storage pool. • The requested capacity cannot be less than or equal to the original datastore capacity.
To delete a datastore: 1. Start the vSphere Client. 2. Use one of the following methods to specify a datastore to delete: • Right-click a datastore and select HP Insight Software→Delete Datastore. • Select a datastore in the inventory tree, click Storage Tools in the HP Management pane, and then click the Delete Datastore link. • Right-click a datastore in any Storage Module for vCenter table and select Delete Datastore. The Storage Module for vCenter prompts you to confirm the delete request. 3.
Creating a VM from a template You can create one or more VMs from a VM template. While creating VMs: • The VM template must exist in the vSphere Client. • Creating a VM has the same prerequisites as creating a datastore. For more information, see “Adding a new datastore” (page 52). During the process of creating the new VM, one or more new datastore are created. • All of the files associated with the new VMs are created on the new datastores.
3. 4. Enter the following information: • Owner: Select the host or cluster that will own the new VMs. This information is entered automatically if you initiated the VM creation from a host or cluster. • VM Template: Select the template to use for the new VMs. This information is entered automatically if you initiated the VM creation from a VM template. • VM Quantity: Enter the number of VMs to create. • VM Initial State: Specify whether the initial VM state is Power On or Power Off.
Figure 35 Create Virtual Machines – Specify Names window 7. Enter the following information: • VM Names: Enter the base name for the new VMs. The # symbol is required and represents the numeric sequence for the new names. In the generated VM names, the # symbol is replaced with a number. The default values are as follows: Number Default start value for numeric sequence 1–9 1 10–99 01 100–999 001 The Generated Names box shows the names of the VMs that will be created.
Figure 36 Create Virtual Machines – Review and Validate window (before validation) 9. Click Next to validate that it is possible to create the VMs. The Create Virtual Machines – Review and Validate window is updated with icons showing the success or failure of the validation processes. A green icon indicates success and a red icon indicates failure. If a validation step fails, a message is displayed in the Warning and Validation Results box.
Figure 38 Create Virtual Machines – Summary window 11. Click Finish to create the specified VMs and datastores. You can view the progress of the task in the Recent Tasks pane at the bottom of the vSphere Client window. TIP: No manual data refresh is necessary. When a provisioning operation is complete, the Storage Module for vCenter data is refreshed automatically. Cloning a VM You can clone one or more VMs from an existing VM.
2. Use one of the following methods to start the Clone Virtual Machine wizard: • Right-click a VM and select HP Insight Software→Clone Virtual Machine. • Right-click a VM in any Storage Module for vCenter table, and then select Clone Virtual Machine. • Select a VM in the inventory tree, click Storage Tools in the HP Management pane, and then click the Clone Virtual Machine link. The Clone Virtual Machine – Clone Parameters window opens. See Figure 39 (page 64).
Figure 40 Clone Virtual Machine – Specify New Names window 5. Enter the following information: • New VM Names: Enter the base name for the new VMs. The # symbol is required and represents the numeric sequence for the new names. In the generated VM names, the # symbol is replaced with a number. The default values are as follows: Number Default start value for numeric sequence 1–9 1 10–99 01 100–999 001 The Generated Names box shows the names of the VMs that will be created.
Figure 41 Clone Virtual Machine – Review and Validate window (before validation) 7. Click Next to validate that it is possible to create the cloned VMs. The Review and Validate window is updated with icons showing the success or failure of the validation processes. A green icon indicates success and a red icon indicates failure. If a validation step fails, a message is displayed in the Warning and Validation Results box. Correct the problem, and then click Retry to repeat the validation step.
Figure 43 Clone Virtual Machine – Summary window 9. Click Finish to create the specified VMs. You can view the progress of the task in the Recent Tasks pane at the bottom of the vSphere Client window. TIP: No manual data refresh is necessary. When a provisioning operation is complete, the Storage Module for vCenter data is refreshed automatically.
5 Viewing hardware alert notifications This chapter describes the Insight Control for vCenter hardware alert events and alarms. Insight Control for vCenter events Insight Control for vCenter loads events from Onboard Administrator, HP SNMP agents, and HP CIM providers into vCenter Server, enabling administrators to view and manage them from the vSphere Client Tasks & Events tab. This provides administrators with a single, heterogeneous view of all host system events within the managed environment.
Enclosure name: Interconnect in bay number status changed to other. Enclosure name: Interconnect in bay number: inserted Enclosure name: Interconnect in bay number: removed Power supply events Enclosure name: Power supply in bay number status changed to OK. Enclosure name: Power supply in bay number status changed to other. Enclosure name: Power supply in bay number: inserted Enclosure name: Power supply in bay number: removed Fan events Enclosure name: Fan in bay number status changed to OK.
Enclosure name: Power subsystem status changed to degraded. Fan zone events Enclosure name: Fan zone number status changed to unknown. Enclosure name: Fan zone number status changed to degraded. vCenter Server event category: error Blade events Enclosure name: Blade in bay number status changed to non-recoverable error. Enclosure name: Blade in bay number status changed to predictive failure. Enclosure name: Blade in bay number status changed to error.
HP SNMP agent and HP CIM provider events HP Insight Control for vCenter registers with HP SNMP agents and HP CIM providers to receive traps from HP SNMP agents and indications from HP CIM providers as they occur. Events created based on these traps and indications fit into the defined vCenter Server categories.
Alarm icon When an alarm occurs, an icon appears to the right of the vSphere Client window along the bar above the vSphere Client tabs or on the host icon in the inventory tree. To view the alarm in the Alarms tab, click the icon. The Alarms tab displays a list of all alarms.
6 Troubleshooting Before troubleshooting issues with Insight Control for vCenter, you must: • Verify that the correct user name and password are entered for vCenter Server. • Verify that the software is installed and configured as described in the HP Insight Control for VMware vCenter Server Installation Guide. • View the log files. For instructions, see “Viewing the log files” (page 73). Viewing the log files The Insight Control for vCenter hpicvcsvc.log file is located in the installation directory.
Action: • Ensure that a host, cluster, datastore, or VM is selected in the left pane of the vSphere Client window. • Use the arrows to scroll through the vCenter Server tabs and locate the HP Insight Software tab. The HP Insight Software tab might be collapsed by vSphere Client due to lack of space on the GUI. • Verify network connectivity between the systems running Insight Control for vCenter, vCenter Server, and the vSphere Client. Ensure that at least one network path exists between these systems.
Figure 44 Internet Explorer script error: buttons.0.0 is null Possible cause: The vSphere user is not assigned the vCenter Administrator role. Action: Close the window, assign the required role to the user, and then try clicking the HP icon again in the vCenter Console. For instructions, see the HP Insight Control for VMware vCenter Server Installation Guide.
Action: Close the window, add the vCenter host to the Internet Explorer list of trusted sites, and then start the vSphere Client again. For instructions on adding hosts to the list, see “Internet Explorer script error when you select host and click Overview in HP Management pane” (page 75).
Software section, and then click Properties in the upper right corner. Enter the iLO settings, and then click OK. • Configure iLO from the HP Insight Software tab. Select a host and click the HP Insight Software tab. Click the Overview link in the HP Management pane, and then click the Properties link in the upper right corner. Enter the iLO settings, and then click Save. • Use automatic association.
settings for each iLO, Onboard Administrator, or and HP SIM on the network. For more information about managing passwords and other system administration tasks, see “Configuring the Server Module for vCenter” (page 7). • For SSO to Onboard Administrator, follow the procedure for configuring the SSO certificate described in “Onboard Administrator Single Sign-On” (page 8).
c-Class server blade and that the corresponding Onboard Administrator is accessible from the default system browser on the system where Insight Control for vCenter is installed. For all other events delivered by Insight Control for vCenter to vCenter Server, the HP SNMP agents or HP CIM providers must be installed and configured. • Verify that the Onboard Administrator is configured to forward events to Insight Control for vCenter. 1. Access the Insight Control for vCenter Home Settings page.
(page 73). For troubleshooting information specific to the Server Module for vCenter, see “Troubleshooting the Server Module for vCenter” (page 76). Storage Administrator Portal login credentials During the Storage Module for vCenter installation, you specify the login credentials to use for the Storage Administrator Portal.
Port conflict occurs when trying to configure P6000 Command View and MSA proxy provider for use with Storage Module for vCenter Possible cause: P6000 Command View and the MSA2000 G2 SMI-S proxy provider cannot coexist on the same server because they use the same ports to communicate.
RMI connection exception in Storage Overview page When a Storage Module for vCenter data refresh is in progress, and a user initiates the VMware re-scan process, the following message might be displayed if you try to view the Storage Overview page for a host: Error Occurred. java.rmi.ConnectException refused to host: IP_address;nested exception is: java.net.ConnectException: Connection refused:connect Possible cause: The Storage Module for vCenter service is not running.
1. 2. 3. 4. 5. Select a host in the vSphere Client. Click the Configuration tab. Click Advanced Settings in the Software pane. Click Scsi in the list of advanced settings. Edit the Scsi.CompareLUNNumber value, and then click OK. LUN displayed multiple times for VM or datastore that is part of a cluster Possible cause: The Storage Module for vCenter uses an ESX Host+LUN number as the unique identifier.
not met, JBoss logs erroneous exceptions indicating that several ports are in use, but the reported ports are not listed in the output of the netstat –a command. TIP: You should be able to perform both forward and reverse lookup. Use the command nslookup FQDN for a forward lookup or nslookup IP address for a reverse lookup. Cause 1: The CMS might not be registered with the DNS server(s). Cause 2: The CMS is not part of a domain. Action: Add the CMS to the domain. This registers the server with the DNS.
7 Support and other resources This chapter describes the support available for Insight Control for vCenter.
HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: • In the United States, see the HP U.S. service locator website: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide website: http://www.hp.com/go/assistance Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to: docsfeedback@hp.
A Firewall port requirements To achieve full functionality, an Insight Control for vCenter 6.3.1 server requires that the firewall ports listed in Table 1 (page 87) are opened (inbound/outbound) . The system on which the software package is installed needs to route via a firewall to Onboard Administrators/ Virtual Connects.
Glossary CIM Common Information Model. CLI Command-line interface. An interface comprised of various commands which are used to control operating system responses. datastore A storage location for VM files in the VMware environment. DNS Domain name system. DPM Distributed power management. DRS Distributed Resource Scheduler. ESX An enterprise-level virtualization product offered by VMware. EVA Enterprise Virtual Array. FC Fibre Channel.
SPOCK Single Point of Connectivity Knowledge website. SPOCK is the primary portal used to obtain detailed information about supported HP storage product configurations. SSO Single Sign-On. SUM Software Update Manager. UID Unit Identification Light. VASA VMware Aware Storage APIs. VDS Microsoft Virtual Disk Service. The Windows service that manages storage through the HWPs. VM Virtual Machine. VMDK Virtual Machine Disk Format. VMFS Virtual Machine File System.
Index A accessing HP Insight Control for vCenter, 21 adding arrays MSA2000 G2, 14 P2000 G3 MSA System, 15 P4000, 14 P6000 EVA, 13 P9000, 16 XP, 16 adding management servers P6000 Command View, 12 administration, 7 air flow monitoring, 27 alarm conditions, 71 alarms troubleshooting, 68, 71 alert notification hardware, 68 arrays modifying, 17 removing, 18 viewing, 16 auto-login failure, 77, 78 B blade events, 68, 69, 70 C CA-signed certificate VASA provider, 19 certificate administration, 7 certificate uplo
troubleshooting, 73 HP Insight Software tab not available, 73 HP Management pane using, 21 HP SIM events, 71 I iLO logs, 30 IML, 30 infrastructure, 25 initialization status, 10 Insight power management plug-in, 78 Integrated Management Log see IML interconnect events, 68, 69, 70 Internet Explorer ActiveX, 83 cache, 76 pop-up blocker, 51 security settings, 51 temporary files, 80 troubleshooting, 74, 75, 83 L logs, 30 iLO, 30 Onboard Administrator, 30 M Management pane using, 21 management servers modifyin
single sign-on see SSO smart components, 25, 29 SSO enabling, 8 failure, 77 Storage Administrator Portal about, 10 troubleshooting, 80 storage disks viewing, 42 Storage Module for vCenter configuring, 9 refreshing data, 33 troubleshooting, 73 using, 31 storage tools, 51 accessing, 51 system information summary, 27 T tables customizing, 35 thermal events, 69, 70 troubleshooting datastore block size, 84 duplicate LUNs, 82, 83 exporting data, 83 GUI anomalies, 76 Internet Explorer, 74, 75, 83 missing HP Insig
