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. It is intended for system administrators who are experienced in virtual and physical IT infrastructure administration and understand server virtualization, storage, and networking concepts.
© Copyright 2012, 2013, 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. The information contained herein is subject to change without notice.
Contents 1 Overview..................................................................................................7 2 Configuring Insight Control for vCenter..........................................................8 vSphere Web Client administration pages...................................................................................8 vSphere Client administration pages...........................................................................................9 Role-based security.....................
Manage networking...........................................................................................................36 Setting host network configuration preferences..................................................................36 Managing clusters.............................................................................................................37 Cluster Overview page..................................................................................................
Viewing HBAs...............................................................................................................71 Viewing paths...............................................................................................................72 Viewing replications......................................................................................................74 Switching Peer Persistence..............................................................................................
Virtual Connect Manager launch link from Insight Control for vCenter prompts for login credentials......................................................................................................................121 HP SIM auto-login fails from Insight Control for vCenter.........................................................121 Clicking HP Insight power management launch link does not go to expected HP SIM page.......121 Cost Advantage field not showing values.........................................
1 Overview HP Insight Control for VMware vCenter Server (Insight Control for vCenter) is a single integrated application that you use to manage ProLiant servers and HP storage systems. The application consists of four modules. The core module is required along with one of the three optional components: the Server Module for vCenter, the Storage Module for vCenter, or the Recovery Module for HP 3PAR StoreServ.
2 Configuring Insight Control for vCenter Insight Control for vCenter is managed as a plug-in in the vCenter Server environment. Several settings can impact the interaction between Insight Control for vCenter and vCenter Server. The configuration settings are accessed from the client Home Settings page. To access the Home Settings page: 1. Run the vSphere Client or vSphere Web Client and access the home page. 2. Under Administration, click the HP Insight Management Administration icon.
vSphere Client administration pages The vSphere Client home page provides access to the following administration pages. The page links are provided in drop-down list. • GUI Theme Selection This page enables you to select your preferred view of the vCenter vSphere Client GUI, either dark text on a light background or light text on a dark background. • vCenter Credential Management This page lists the credentials for all vCenters that are configured in the environment.
• Launch HP management tools using SSO • Access the Insight Control for vCenter Server vSphere Client home page A read-only user can: • View Insight Control for vCenter A user can: • Launch HP management tools, and then log on to use them • View Insight Control for vCenter For information about assigning a user access role, see the HP Insight Control for VMware vCenter Server Installation Guide.
Using the Insight Control for vCenter Host Properties page 1. Select a host, and then click the HP Insight Management tab. 2. 3. Click the Settings icon and select Host Properties. Depending on which client you are using, do one of the following: • vSphere Web Client: Select the iLO global settings, or enter the iLO IP address or host name, and a valid user name and password. • vSphere Client: Enter the iLO IP address or host name, and a valid user name and password.
Lists the credentials for all HP OneView controllers that are configured in the environment. You can perform the following tasks: • Add a new HP OneView controller—Click the Add icon and enter the credentials. If the host or the credentials are invalid, the HP OneView controller is not added. • Delete an HP OneView instance—Select the appropriate instance and click the Delete icon . To access the Server Module Credentials page: 1. Run the vSphere Web Client and access the home page. 2.
2. Enter your user name and password, and then click OK. This is the login information that you configured during the installation process. A list of configured storage systems and management servers appears, displaying the storage system name, type, model, firmware, identifier, management servers/managed storage systems, current user, storage pools, and storage pool access settings.
Adding HP StoreVirtual storage systems To add an HP StoreVirtual storage system (also called a management group): 1. Access the Storage Administrator Portal. For instructions, see “About the Storage Administrator Portal” (page 12). 2. Click Add. The Add Storage System or Management Server page appears. 3. Select HP StoreVirtual in the Type list, and then click Next. The Add HP StoreVirtual page appears. 4.
5. Review the HP 3PAR StoreServ storage system certificate. The certificate displayed is the most current certificate returned from the HP 3PAR StoreServ storage system. To verify the data in the certificate, perform the following steps: a. Copy the entire certificate text into a text file named .cer. b. Open the file in a browser to view the details of the certificate. Verify the certificate data. 6. Click Next.
If you selected one or more passively managed HP EVAs, you must configure the storage pool access for those storage systems when you add their active HP EVA 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. Storage pools do not need to be assigned Full access if they are not intended to be used for provisioning operations. 7. Click Finish.
8. Click Finish. The storage system is added to the Configured Storage Systems and Management Servers list. Adding HP MSA storage systems To add an HP MSA storage system: 1. Verify that a supported version of the HP MSA firmware is installed. For the supported firmware versions, see the HP SPOCK website: http://www.hp.com/storage/spock 2. Access the Storage Administrator Portal. For instructions, see “About the Storage Administrator Portal” (page 12). 3. Click Add.
4. Select HP XP P9000 in the Type list, and then click Next. The Add HP XP P9000 storage systems page appears. The available P9000 storage systems are listed by serial number. 5. 6. Select a storage system. Enter the Remote Web Console credentials, and then click Finish. The array is added to the Configured Storage Systems and Management Servers list. NOTE: The HP XP P9000 storage system does not support provisioning by the Storage Module for vCenter.
5. Click Finish. The HP StoreOnce Backup array is added to the Configured Storage Systems and Management Servers list. NOTE: The HP StoreOnce Backup system needs to be configured as a cluster (single node or multi node), for it to be added to the Storage Administrator Portal. Adding a non-clustered HP StoreOnce Backup system is not supported.
• HP XP and HP XP P9000 storage systems: Change the Remote Web Console user name, and password. • HP 3PAR StoreServ, HP StoreOnce Backup: Change the user name, and password. NOTE: • The HP EVA Command View server password is required to modify HP EVA Command View servers. • The storage node password is required to modify HP StoreVirtual information. • The controller user name and password are required to modify HP MSA array information.
2. Select a storage system or management server in the Configured Storage Systems and Management Servers list, and then click Remove. A confirmation dialog box opens. 3. Click Yes to confirm that you want to remove the storage system 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.
Registering the VASA Provider from the vSphere Web Client To add the Storage Module for vCenter to the Storage Providers list: 1. Right-click a datastore in the left pane of Insight Control for vCenter, and then click Manage Storage Providers. The Storage Providers page opens. 2. Click the green add icon (+). The Add Vendor Provider dialog box opens. 3. Enter the following information: • Name: Enter HPICSM. • URL: Enter https://vasaProvider_server_name:port/vasa_provider_ws/vasaService.
6. 7. • Organization • Common Name—The fully qualified vCenter Server name. Optionally, enter the following information in the Optional Certificate Info section: • Organizational Unit • Email • Surname • Given Name Click Generate. The certificate signing request is generated. A certificate request with 1024-bit encryption is generated. . 8. 9. Copy the certificate signing request text. Use the Certification Authority tool to generate the CA-signed certificate.
Both the vCenter Server and VASA Provider use SSL certificates. The VASA Provider support included with Recovery Manager for VMware uses the same certificate used by the Plug-in web service. However, before you can use the vCenter Server to register the VASA provider, you must manually install the SMS certificate extracted from the vCenter server onto the VASA installed host. This process is required for every vCenter Server you intend to register with the VASA provider.
Installing the SMS Certificate Manually 1. 2. 3. 4. 5. 6. 7. 8. Copy the certification file to the VASA installed host. Right click the certification file and select Install Certificate. Supply the appropriate responses and information requested by the Certificate Import Wizard. On Certificate Store page, select the Place all certificates in the following store radio button and click Browse. For the Select Certificate Store dialog, check the Show physical stores check box.
3 Using Insight Control for vCenter This chapter describes the processes for accessing and using the software. You can access resource inventory, HP Insight Management Administration tools and the HP Insight Management Deployment Wizard from the vSphere Client home page. Figure 2 vSphere Client home page Figure 3 vSphere Web Client home page For more information about HP Insight Management Administration, see “Configuring Insight Control for vCenter” (page 8).
Accessing Insight Control for vCenter After completing the installation and configuration procedures, you can access Insight Control for vCenter two ways: • “Using the vSphere Client to access Insight Control for vCenter” (page 28) • “Using the vSphere Web Client to access Insight Control for vCenter” (page 28) • The vSphere Client is a .Net client that utilizes drop-down lists to navigate Insight Control for vCenter. See Figure 4 (page 27).
Figure 5 vSphere Web Client — Overview Using the vSphere Client to access Insight Control for vCenter After completing the installation and configuration procedures, you use the vSphere Client to access Insight Control for vCenter: 1. Log into the vSphere Client. In most configurations, this is the same server that you configured during the installation process. 2. 3.
4. Click the HP Insight Management tab. An overview of the VMware component that you selected appears. While Insight Control for VMware vCenter collects information about this VMware component or corresponding HP iLO, HP Onboard Administrator, or Virtual Connect modules; the panes in the overview page display loading.... HP Insight Management refreshes the contents on a periodic basis and updates information.
The main section in the Overview page displays multiple boxes called portlets that provide summary information about the selected VMware component. The portlets will vary based on your configuration and the selected component.
• The HP icon • A row of tabs used to display different views and level of detail. The Monitor page tabs are the same for all components. The Manage page tabs differ depending on the component selected. .
• Software/Firmware • Storage • News Feed (a list of recent events) For detailed information about portlet items, do one of the following: • Click More at the bottom of the portlet. News Feed details are displayed under the Monitor page. All other portlet details are displayed on the Manage page. • Click the corresponding tab. The tabs for some of the information are on the Monitor page.
If you have a server module installed and a cluster is selected in the inventory tree, HP Insight Management provides the following information: • Status/Health • Infrastructure • Software/Firmware • News Feed • Cluster • Tasks If you have a server module installed and a host is selected in the inventory tree, HP Insight Management provides the following information: • Status/Health • Overview • Host • Networking • Software/Firmware • Infrastructure • News Feed • Tasks NOTE: For
From the HP Insight Management Administration page, select Server Module Configuration screen for the cluster, enter the power cost. Entering the power cost for a cluster generates the cost advantage information, which is displayed for each host on the Cluster detail page.
5. Drag and drop the OS onto all or selected host systems, and then click Next. The Step 4 – Add to vCenter window opens. 6. Select the host systems that you want to configure, enter the user names and passwords, select the cluster or datacenter to which you want to add the system, and then click Next. The Step 5 – Summary window opens. 7. Monitor the status of the deployment and when the process is complete, click Finish. The hosts that you selected in Step 6 are added to vCenter. 8.
Manage networking Setting host network configuration preferences NOTE: This feature is available only on the vSphere Web Client. These settings are used to evaluate the network configuration of a host with respect to its Virtual Connect/OneView profile. This page is accessed by selecting Host Network Configuration Preferences in the left pane of the HP Insight Management Administration page. After setting the preferences, click Save or Clear to reset all the selections to the default values.
Port Group Names Displays the port group names defined for the networks. By default, the name of the network in Virtual Connect or HP OneView is used as the port group name. If necessary, the port group name can be changed. • Port Group Name: Enter the new port group name for the network. TIP: Custom port group names simplify configuration of active-active network configuration with Virtual Connect.
Figure 7 Cluster overview page (vSphere Web Client) The Overview page for Cluster Management displays status summary information. Depending on the software installed, links may be available for the following management tools: • HP SIM • Onboard Administrator • HP OneView (vSphere Web Client) Cluster Overview page The Cluster Overview page displays information for all hosts in the selected cluster. The information is displayed in portlets that provide summary information about the cluster.
If the Storage Module for vCenter is installed, the Overview page includes the following: • A Storage portlet • Links to the array management software for configured arrays (if available) • Array health status information • Array firmware version information • Storage-related News Feed topics Click the Settings icon to view the Product Version or set Cluster Properties. Networking portlet information NOTE: Cluster networking is available only on the vSphere Web Client.
The cluster networking page displays status for the selected cluster and each host in the cluster. It also provides the capability for setting a reference host and resolving network mismatches. The page includes the following: • • Overall Cluster Status— indicates the overall cluster status. The status values are: ◦ OK ( ◦ Mismatch ( ) —indicates that a host or hosts in the cluster have a Server Profile Network mismatch status or a Host Network Configuration status mismatch.
NOTE: • This feature is available only on the vSphere Web Client. • Only servers having Virtual Connect/HP OneView profile information are supported as a reference host. • Ensure that no host network configuration operations are being performed within the cluster when selecting or changing a reference host.
2. 3. Click the Manage tab and then click HP Insight Management. Select Networking. The cluster networking page opens displaying information for all hosts in the cluster and the status for each. 4. Select a host that has a status of Mismatch ( ) for either Server Profile Network status or Host Network Configuration Status. Use the Select check box to select a single host or multiple hosts. The recommended actions required in the Virtual Connect/OneView profile are displayed.
Growing a cluster Using the HP Grow Cluster feature, you can expand the capacity of an existing cluster. This feature presents two options for growing a cluster: basic deployment and enhanced deployment. Both of these options use Insight Control server provisioning for deployment of ESXi on the HP server. The basic deployment option presents a list of bare-metal servers discovered by Insight Control server provisioning, installs ESXi, and adds the server to the cluster.
NOTE: The enhanced deployment option works only with a custom build plan. For more information, see “Creating a custom build plan” (page 145). 6. Select the Reference Profile if necessary. If the selected cluster has a reference host, the profile of the reference host is used and the Reference Profile field is not displayed. 7. Select the target server. Multiple servers can be selected. Use the checkbox at the top of the table to select all the targets displayed.
Figure 8 Host Overview page — vSphere Client view Figure 9 Host Overview page — vSphere Web Client view The Overview page provides overall details of Host, Infrastructure (Enclosure), networking, Storage (If storage is installed), Software/Firmware, and News Feed events associated with the selected HP Proliant Server. Depending on the HP Management tools and software installed and configured with Insight Control for vCenter, links are available to launch HP Tools.
NOTE: The appropriate HP ESXi Offline Bundle is required to get provider data and generated events. Without the appropriate bundle, the following information is not displayed. • HP Insight Provider Bundle • News Feed • Software/Firmware The HP ESXi Offline Bundle can be downloaded from the following website: http://h18004.www1.hp.com/products/servers/software/vmware-esxi/driver_version.
To view the IML or iLO logs for a host: 1. Select an HP ProLiant server, BladeSystem enclosure, or host in the inventory tree, and then access HP Insight Management. The Overview page opens. 2. Click More at the bottom of the Host Information portlet, or select Host. Detailed host information is displayed, which includes both iLO and IML logs. To view the Onboard Administrator logs for a host: 1. Select a blade from the inventory tree and navigate to HP Insight Management. 2.
2. For detailed networking information, click More at the bottom of the Networking portlet or do one of the following: • From the vSphere Client, select Networking from the drop-down list. • From the vSphere Web Client, click the Networking tab on the Manage page. The Network Detail view is displayed. Click Network Diagram to see a diagram of the network. The following networking information is displayed.
1. The Host Network Configuration status on the Networking portlet of the Host Overview page indicates one of the following: • OK ( )—indicates the host networking configuration matches the networks configured in the Virtual Connect/OneView Profile for this host. No action is required on a host in this state. • Mismatch ( )—indicates the host network configuration does not match the networks configured in the Virtual Connect/OneView Profile for this host.
3. Click Apply Recommended Actions. Confirmation screen is displayed which lists all the networking configuration changes that will be done. Review the changes that will be made. 4. Click Apply to perform the actions. Once the changes are applied, the final status is shown in the news feed section. To view progress updates, access the Tasks page under HP Insight Management. NOTE: • Host network configuration can fail on hosts having VMs running on them.
While viewing the diagram: • If you move the cursor over a Virtual Connect Ethernet network, iSCSI network, or FC SAN, the end-to-end network connection appears brighter. Potential bottlenecks are indicated when an information icon symbol is shown. You can modify bottleneck thresholds by selecting Home→Administration→HP Insight Management Administration→Server Module Configuration. Select the Virtual Connect Over Subscription factor to set the threshold.
2. For detailed software and firmware information, click More at the bottom of the Software/Firmware portlet or do one of the following: • From the vSphere Client, select Software/Firmware from the drop-down list. • From the vSphere Web Client, click the Software/Firmware tab on the Manage page. The details include software/firmware name, version, and a brief description.
4. Click Upload Update firmware using Smart Components To update firmware for the hosts on a cluster or selected hosts in the cluster, complete the following steps: 1. From the Actions drop-down list, select Update Firmware. 2. Click Smart Component Update. 3. Select a Smart Component from the drop down list or enter the URL of the location where a Smart Component is staged on your web server. 4.
HPSUM Firmware Management The HPSUM Firmware Management page is used with the vSphere Web Client to schedule firmware updates for hosts with firmware that is not managed by HP OneView. An instance of HPSUM 6.2 or higher must be configured, running, and accessible by Insight Control for vCenter. NOTE: • The minimum HPSUM version supported is 6.2.0. • The HPSUM credentials must be configured in Insight Control for vCenter prior to using this feature.
2. For detailed news feed information, click More at the bottom of the News Feed portlet or do one of the following: • From the vSphere Client, select News Feed from the drop-down list. • From the vSphere Web Client, click the News Feed tab on the Monitor page. Detailed event information is displayed. The details include object status, timestamp and a brief message. If a cluster is selected, information is displayed for all hosts in the cluster.
Launching into HP tools Insight Control for vCenter provides links to launch HP tools if available. Some of the tools that can be launched from the HP Insight Management tab are as follows: • Integrated Lights Out (iLO) • Onboard Administrator (OA) • Virtual Connect (VC). Link for launching Virtual Connect at host level. • Virtual Connect Enterprise Manager (VCEM). This link is displayed when VC is locked by VCEM.
vSphere Client, select the HP Insight Management tab. In the vSphere Web Client, click the Manage tab and click HP Insight Management. For more information, see “Accessing Insight Control for vCenter” (page 27). The Overview page for servers and clusters is shared between the Server Module and Storage Module. The Overview page for datastores and VMs is available only when the Storage Module is installed.
Click Check Refresh Progress to update the refresh status. The time it takes for a refresh to complete depends on the size of the environment and the number of arrays configured in the Storage Module. NOTE: Previously gathered data is displayed in the GUI during a cache refresh. You can change the automatic cache refresh settings or manually refresh the cache. For more information, see “Manually refreshing the cache” (page 58).
Figure 12 Manual cache refresh options—Storage Administrator Portal 3. 4. Click OK to continue the cache refresh. Optional: Click Check Refresh Progress to update the elapsed time and estimated time remaining. See Figure 11 (page 57). Restarting a cache refresh Restarting a cache refresh stops the existing refresh process and starts a new one.
2. Click Restart. Changing the automatic cache refresh settings You can change the default cache refresh settings by editing the standalone.xml file. 1. Open the standalone.xml file, which is located in the following directory (assuming that the default installation directory was used): \JBoss\standalone\configuration 2. Add the following parameters in the system-properties node: • Caching.RefreshInterval: Specifies the time, in milliseconds, to wait between cache refreshes • Caching.
The Select columns dialog box lists the currently displayed columns on the left and the hidden columns on the right. See Figure 14 (page 61). • Click the minus icon next to a column to remove it from the table, or click Remove all to remove every column. • Click the plus icon next to a column to add it to the table, or click Add All to add every column. • Enter a value in the text box above the hidden columns to filter the list by a specific value.
Figure 15 Adding and removing columns (vSphere Web Client) Viewing host storage information To view storage information for a host: 1. Select a host in the inventory tree and access HP Insight Management. The Storage portlet on the Overview page provides an overview of the storage systems. 2. For detailed storage information, click More at the bottom of the Storage portlet or do one of the following: • From the vSphere Client, select Storage Details from the drop-down list.
HP Storage Provisioned to Host • Volumes—Number of volumes available to the host from configured HP storage arrays and whether any are thin-provisioned • HP Storage Provisioned—Amount of storage available to the host from configured HP storage arrays • HP Storage Used—Amount of storage from configured HP storage arrays that is used by the host NOTE: The HP Storage Used value can differ from the HP Storage Provisioned value if thin provisioning or demand-allocated snapshots are used.
This section lists the datastores provisioned from the selected host to VMs. For each datastore, move the cursor over the status bar to view storage information.
HP Storage Provisioned to Cluster • Volumes—Number of volumes available to the cluster from configured HP storage arrays and whether any are thin-provisioned • HP Storage Provisioned—Amount of storage available to the cluster from configured HP storage arrays • HP Storage Used—Amount of storage from configured HP storage arrays that is used by the cluster NOTE: The HP Storage Used value can differ from the HP Storage Provisioned value if thin provisioning or demand-allocated snapshots are used.
Viewing datastore storage information To view information about datastore storage availability and use: 1. Select a datastore in the inventory tree and access HP Insight Management. The Storage portlet on the Overview page provides an overview of the storage. 2. For detailed storage information, click More at the bottom of the Storage portlet or do one of the following: • From the vSphere Client, select Storage Details from the drop-down list.
This section lists the arrays that provide storage to the selected datastore. For each array, move the cursor over the status bar to view storage information.
• “Viewing HBAs” (page 71) • “Viewing paths” (page 72) • “Viewing replications” (page 74) • “Viewing VMs to volumes” (page 76) VM storage summary information This tab displays the following information about the selected VM: HP Storage Provisioned to Virtual Machine • Volumes—Number of volumes available to the VM from configured HP storage arrays and whether any are thin-provisioned • HP Storage Provisioned—Amount of storage available to the VM from HP storage arrays • HP Storage Used—Amount of
For each configured backup system, all the service sets are displayed. For each service set the following information is displayed: • Used—The amount of data stored on the service set by the services on the service set. • Total—Total amount of storage on the service set. • Deduplication Ratio—The deduplication ratio of data stored on the service set.
• VMware Disk Identifier—Disk name assigned by VMware • Path ID—Path ID assigned by VMware • Array Disk RAID—RAID level of the array disk • Array Disk Total Capacity—Array disk capacity (in GB) • Array Disk Allocated Capacity—Capacity allocated by the storage system. For a thin-provisioned disk, this value might differ from the Array Disk Total Capacity value.
• Array Disk Emulation Type (HP XP P9000 and HP XP arrays only)—LDEV emulation type. • Replicated—Specifies whether the disk is replicated • Physical Device Type—The type of device in the CPG (applies only to HP 3PAR StoreServ). The types can be FC, NL, or SSD.
Viewing paths The Paths tab is displayed for selected components.
◦ HP MSA (iSCSI)—IQN used by the host for connecting to this disk on this storage array ◦ HP XP P9000/HP XP—WWN for the storage array port on the storage array end of this path ◦ HP StoreOnce Backup—Not applicable • LUN—LUN used for presenting the storage disk from the storage array port to the host HBA port • Host—Host that is currently running the selected VM • Array Type—HP array type • Array Controller—Controller used for this path • Array Port—Storage array's port identifier used for thi
• • • • Array Port Speed ◦ HP StoreVirtual—Not applicable ◦ HP 3PAR StoreServ—Speed at which the port is connected to the SAN (Gb/s) ◦ HP EVA—Speed at which the port is connected to the SAN (Gb/s) ◦ HP MSA – FC—Speed at which the port is connected to the SAN (Gb/s) – iSCSI—Speed at which the network port is connected to the network (Gb/s) – SAS—Speed at which the port is connected to the host or switch (Gb/s) ◦ HP XP P9000/HP XP—Speed at which the port is connected to the SAN (Gb/s) ◦ H
• Replication Type—The type of replication used: ◦ HP StoreVirtual—Snapshot, Remote Snapshot ◦ HP 3PAR StoreServ—Virtual copy, Physical copy, Peer Persistence ◦ HP EVA—Snapshot, Snapclone, Mirrorclone, Continuous Access ◦ HP MSA—Not applicable ◦ HP XP P9000/HP XP—P9000 or XP Business Copy, P9000 or XP Snapshot, P9000 or XP Continuous Access ◦ HP StoreOnce Backup—Not applicable • Replica Name—Target replication disk • Replica Array—Array identifier for the remote (target) array; displayed on
3. Click OK. Viewing VMs to volumes The VMs to volumes page displays the following information: On the VMs to volumes page click Details to display the information in table format or click Graphics to display a graphical representation of the VMs to volumes paths. Details format NOTE: The same VM can appear multiple times, based on the number of available paths to a storage disk.
• Array Disk Total Capacity—Total amount of storage available to the datastore • Array Disk Allocated Capacity—Size of the virtual disk on the array • Array Disk Provisioned—Whether the virtual disk uses thick or thin provisioning • Array Controller—Controller used for this path • Array Port—Storage array's port identifier used for this path • Host Group • ◦ HP StoreVirtual—Name configured for the host's IQN in the management console ◦ HP 3PAR StoreServ—Name of the host object containing the
• • ◦ HP StoreVirtual—IQN assigned to the host ◦ HP 3PAR StoreServ (FC)—WWN for the host port on the host end of this path ◦ HP 3PAR StoreServ (iSCSI)—IQN assigned to the host ◦ HP EVA—WWN for the host port on the host end of this path ◦ HP MSA (FC, SAS)—WWN for the host port on the host end of this path ◦ HP MSA (iSCSI)—IQN assigned to the host ◦ HP XP P9000/HP XP—WWN for the host port on the host end of this path ◦ HP StoreOnce Backup—Not applicable Array Port WWN ◦ HP StoreVirtual—IQN
Graphics format The graphics format provides a representation of the paths between the following entities: • Virtual Machine • Virtual Disk Name • Datastore • Array Disk Name • Storage pool • Array Name Here are some tips for using the graphic: • A legend describing each element in the graphic can be displayed by right-clicking a column heading and selecting the Show Legend option. • Columns can be sized by dragging the border.
TIP: • After configuring storage systems, initiate cache refresh and make sure the refresh action is finished before opening the HP Storage Systems infrastructure page. • Use the small expand/contract icon to the left of a field to view detailed information. The storage system infrastructure information is organized into the following sections: • Header—The first line of information includes details like health, storage system type, and the name of the item selected.
• Fans portlet—lists the enclosure fan information including model, status, and speed. • Interconnects portlet—lists the interconnect information including status, product name, and firmware version. • Power Supplies portlet—lists the enclosure power supply information including model, status, and current power output. TIP: Use the icon in the upper right corner of a portlet to maximize it.
4 Provisioning storage The Storage Module for vCenter supports storage provisioning for HP 3PAR StoreServ, HP StoreVirtual, HP EVA, and HP MSA arrays. You can perform storage provisioning operations such as creating a new datastore, deleting or expanding an existing datastore, creating new VMs, or cloning existing VMs. For HP EVAs, provisioning operations are supported for thick-provisioned virtual disks.
Viewing the audit log The Storage Module for vCenter provides an audit log for provisioning operations. The audit log, provisionAuditLog.txt, is available in the following directory: /Storage/JBoss/standalone/log. Creating a datastore You can create a new datastore on a host or cluster that meets the following prerequisites. Hosts • The host must exist in the vSphere Client. • In an FC environment, the SAN must be zoned between the storage pools and the host.
TIP: You can minimize the wizard using the minimize control ( ) in the upper right corner of the screen. The wizard will be added to the Work in Progress panel on the right. Click on it to resume the wizard. The Create Datastores wizard opens and displays the Select Location window. 3. Select the host or the cluster which will own the new datastore in Select location. A compatibility check is done to ensure the selected location is valid.
5. 6. Enter the number of datastores to create in the Number of datastores box. Enter the capacity for the new datastores in the Datastore Capacity box. NOTE: The actual value used by the software might be slightly higher than specified in order to accommodate the VMware overhead. 7. 8. Select a storage pool. Depending on the type of array selected, perform one of the following steps: • For an HP 3PAR StoreServ, select a Copy Space Pool to use for the new datastore.
If Enable Peer Persistence was selected, the Configure Peer Persistence window opens. Continue with step 11.
11. To enable Peer Persistence, perform the following steps: a. Select a storage pool. b. Select a remote copy space pool. c. Click Next. The Specify Names window opens. 12. If a single datastore is being created, perform the following steps: a. Enter the name for the new datastore in the Datastore Name box. The name is added to Generated Names. b. Click Next.
13. If more than one datastore is being created, perform the following steps: a. Enter the name for the new datastores in the Datastore Name box. The # symbol is required and represents the numeric sequence for the new datastore names. In the generated datastore names, the # symbol is replaced with a number. b. Enter the start value for the numeric sequence of datastore names in Where # is numeric and starts at. The Generated Names box displays the names of the datastores that will be created. c.
14. Review the information that will be used to create the datastore. Validation of the information begins automatically. During the validation process a green icon indicates a successful validation step, and a red icon indicates failure. If a validation step fails, a message is displayed at the bottom of the provisioning wizard.. Correct the problem, and then click Retry to repeat the validation step. If you need to change values entered in the wizard, use the Back and Next buttons to navigate.
4. Click Next. For HP 3PAR StoreServs only, the Specify Copy Space window opens. 5. 6. Select the copy space for the HP 3PAR StoreServ. Click Next. The Specify New Names window opens. 7. Enter the following information: • New Datastore Names: Enter the base name for the new datastores. The # symbol is required and represents the numeric sequence for the new datastore names. In the generated datastore names, the # symbol is replaced with a number.
To expand a datastore: 1. Start the vSphere Web Client and access HP Insight Management. 2. Use one of the following methods to open the Expand Datastore window: • Right-click a datastore and select HP Insight Management→Expand Datastore. • Select Actions→Expand Datastore on the HP Insight Management page for a datastore. • Right-click a datastore in any Storage Module for vCenter table, and then select Expand Datastore. The Expand Datastore window opens. 3.
2. Use one of the following methods to open the Expand Datastore window: • Right-click a datastore and select HP Insight Management→Expand Datastore. • In the vSphere Client, select Expand Datastore from the Actions drop-down list. • In the vSphere Web Client, select Actions→Expand Datastore on the HP Insight Management page for a datastore. • Right-click a datastore in any Storage Module for vCenter table, and then select Expand Datastore. The Expand Datastore window opens. 3.
3. If any errors are shown, address them and then retry the operation. Otherwise, click Delete to confirm the operation. The Storage Module for vCenter unpresents the storage volumes from all hosts, deletes the volumes, and re-scans the hosts. When these tasks are complete, the deleted datastore is no longer displayed in the vSphere Client. If the delete operation cannot be performed, an error message is displayed describing why the operation failed.
3. Right-click the volume and select Delete Volume. The Storage Module for vCenter prompts you to confirm the delete request. 4. Click Delete. The Storage Module for vCenter removes the LUN presentation from all hosts, deletes the volume, and re-scans the hosts. When these tasks are complete, the deleted volume is no longer displayed in the vSphere Client. TIP: No manual cache refresh is necessary. When a provisioning operation is complete, the Storage Module for vCenter data is refreshed automatically.
3. Select the host or the cluster which will own the new virtual machine(s) in Select location. A compatibility check is done to ensure the selected location is valid. If it is not, an error message is displayed and a different location must be selected. 4. Click Next. The Select VM Template window opens. 5. Enter the number of VMs to create in Number of virtual machines.
6. Select the template to be used to create new VM(s). When a template is selected, the wizard displays the required storage capacity per VM and for all VMs, if multiple VMs are being created. 7. Specify a customization specification (if available) in Customization Specification. For more information, see the VMware documentation. 8. 9. Select the Power on virtual machines after creation option if desired. Click Next. The Select Storage window opens 10.
be used for the Peer Persistence on the array should be configured with Read-Write access. In addition, the Peer Storage Pools should be in the same domain as the selected host(s). Select the Storage Pool on the Peer and then click Next. The Specify Names window opens 18. Enter the base name for the new virtual machine(s) in the Virtual Machine name. For single virtual machine, the # symbol is not required. For multiple virtual machines, the # symbol is required. It represents a numeric sequence.
22. Review the information that will be used to create the virtual machines. Validation of the information begins automatically. During the validation process a green icon indicates a successful validation step, and a red icon indicates failure. If a validation step fails, a message is displayed at the bottom of the wizard screen. Correct the problem by going Back to the previous screens. 23. When validation completes successfully, click Next. The Ready to Complete window opens 24.
The Specify VMs window opens. 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.
The Generated Names box shows the names of the VMs that will be created. • Datastore Names: Enter the base name for the new datastores. The # symbol is required and represents the numeric sequence for the new names. In the generated datastore names, the # symbol is replaced with a number. The Generated Names box shows the names of the datastores that will be created. • 8. Where # is numeric and starts at: For both the VM and datastore names, enter the start value for the numeric naming sequence.
1. 2. Start the vSphere Web Client. Use one of the following methods to start the Clone Virtual Machine wizard: • Right-click a VM and select All HP Insight Management Actions→Clone VM. • Select Actions→Clone VM on the HP Insight Management page for a VM. • Right-click a VM in any Storage Module for vCenter table, and then select Clone VM. TIP: You can minimize the wizard using the minimize control ( ) in the upper right corner of the screen.
5. 6. Enter the Number of copies to make of the selected virtual machine. Select the virtual machines to be cloned. If a datastore associated with the selected VM contains additional VMs, the additional entries will be shown in the table. The datastores that will be cloned are selected automatically. The related RDMs that will be cloned are listed. 7. Click Next. The Specify VM Details window opens.
9. Select a customization specification (if any are available) in Customization Specification. For more information, see the VMware documentation. 10. Enter the base name for the new virtual machine(s) in Virtual Machine Name. The Generated Names box displays the names of the VMs that will be created. For a single virtual machine, the # symbol is not required. For multiple virtual machines, the # symbol is required. It represents a numeric sequence.
17. Review the information that will be used to create the virtual machines. Validation of the information begins automatically. During the validation process a green icon indicates a successful validation step, 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 by going Back to the previous screens. 18. When validation completes successfully, click Next. The Ready to Complete window opens. 19.
3. Enter the following information: • Target Owner: Select the host or cluster that will own the new VMs. • Target VM Quantity: Enter the number of VMs to create. • Target VM Initial State: Specify whether the initial VM state is Power On or Power Off. • Customization Specification: Specify a customization specification (if available). For more information, see the VMware documentation. • Clone Type: Select Snapshot or Clone.
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 cache refresh is necessary. When a provisioning operation is complete, the Storage Module for vCenter data is refreshed automatically.
5 Working with VASA Provider The communication between HP 3PAR VASA provider and vCenter server is a secure connection based on SSL certificate and Windows credential. Before HP 3PAR VASA Provider can be registered by vCenter server, VASA provider requires that you extract the SMS certificate from vCenter server and install it to the HP 3PAR Recovery Manager for VMware installed host to allow client certificate negotiation in the Transport Layer.
Figure 17 Add Vendor Provider Screen Table 1 Add Vendor Provider Information Fields Field Name Value Name Any name to identify the VASA provider. URL VASA Service Web URL. For example (https://:/). Login Windows user name to Recovery Manager for VMware installed host. Password Windows Password. Once registration is successful, the provider status is available online. NOTE: To register VASA Provider, the user must have the StorageViews Configure privilege.
Figure 18 Manage Storage Capabilities Screen The name of an HP 3PAR storage capability has five parts and each identifies the value of one of the volume attributes. The following table shows the volume attributes and possible values.
NOTE: 110 Consult the appropriate VMware documentation for more details.
6 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. This provides administrators with a single, heterogeneous view of all host system events within the managed environment.
For more information, see the HP BladeSystem Onboard Administrator User Guide, which is available on the HP website: http://www.hp.com/go/oa. vCenter Server event category: info Blade events Enclosure name: Blade in bay number status changed to OK. Enclosure name: Blade in bay number status changed to other.
Enclosure name: Blade in bay number: iLO dead Interconnect events Enclosure name: Interconnect in bay number status changed to unknown. Enclosure name: Interconnect in bay number: reset Power supply events Enclosure name: Power supply in bay number status changed to unknown. Enclosure name: Power supply in bay number status changed to degraded. Fan events Enclosure name: Fan in bay number status changed to unknown. Enclosure name: Fan in bay number status changed to degraded.
Enclosure name: Power subsystem status changed to non-recoverable error. Enclosure name: Power subsystem status changed to predictive failure. Enclosure name: Power subsystem status changed to error. Fan zone events Enclosure name: Fan zone number status changed to non-recoverable error. Enclosure name: Fan zone number status changed to predictive failure. Enclosure name: Fan zone number status changed to error.
• Alarms associated with HP ProLiant and HP BladeSystem fan zones These alarms are triggered by an HP BladeSystem subsystem event. The alarm states are controlled by the type (severity) of the event. The alarms are triggered on all HP ProLiant and BladeSystem servers in the affected fan zone. • Alarms associated with HP ProLiant and HP BladeSystem power subsystem These alarms are triggered by an HP BladeSystem power subsystem event. The alarm states are controlled by the type (severity) of the event.
7 Troubleshooting Before troubleshooting issues with Insight Control for vCenter, you must do the following: • 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 116).
HP Insight Management tab not available in the vSphere Web Client Possible cause: The vSphere Web Client has not deployed the plug-in. NOTE: The plug-in is deployed only when the vSphere Web Client is executed. Action: Execute the vSphere Web Client. 1. If the vSphere Web Client was running when the plug-in was installed, log out of the vSphere Web Client. 2. Log into the vSphere Web Client.
• HP Insight Control for vCenter Server • HP Insight Control Storage Module for vCenter • HP Insight Control for vCenter UI Manager Slow response in the vSphere Client Possible cause: The system on which Insight Control for vCenter is installed does not meet the hardware requirements for all software installed on the server. Action: Ensure that: • HP SIM and vCenter Server are not installed on the same server. This is not a supported configuration.
Error Communicating with iLO at VM host The following error appears if the Windows Proxy Server is enabled and the host is using iLO 3: Error Communicating with iLO at "VM hostname" Text object has no attribute 'ribcl' . Possible cause: Windows proxy server settings are not configured to allow LAN communication from the Insight Control for vCenter Server to iLO 3 on the target vSphere 5.x/ESXi 5.x host system.
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 Management tab. Select a host and click the HP Insight Management tab. Move your cursor over the Settings icon, and then select Host Properties. Enter the iLO settings, and then click Save. • Use automatic association.
Virtual Connect Manager launch link from Insight Control for vCenter prompts for login credentials Cause: Virtual Connect Manager does not support auto-login. HP SIM auto-login fails from Insight Control for vCenter Possible cause: HP SIM uses cookies for auto-login. If the browser is configured to block all cookies, the HP SIM auto-login feature for Insight Control for vCenter does not work. Action: Configure the Microsoft Internet Explorer browser to accept cookies. 1. Select Tools→Internet Options. 2.
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. 2.
provisioning features, you must configure the VMware Administrator role in a vSphere session. For instructions, see the HP Insight Control for VMware vCenter Server Installation Guide. Storage Module for vCenter GUI not responsive to mouse clicks Possible cause: The Temporary Internet Files directory is full. Action: Delete the temporary files created by Internet Explorer. Refresh takes a long time to complete In environments with HP EVAs, a cache refresh takes a long time.
IMPORTANT: This procedure restarts the HP MSA array controller. If you restart a management controller, communication with it is lost until it restarts successfully . This will not affect disk access. If the restart fails, the partner management controller remains active with full ownership of operations and configuration information. Other applications (such as Microsoft VSS and VDS) that rely on the management controller services might be affected. 1. 2. 3. 4. 5. 6. 7. 8.
Action: LUNs with the same disk names are duplicates and represent a single disk on the storage array. Storage Administrator Portal information cannot be exported Possible cause: The required ActiveX controls are disabled.
Troubleshooting for VASA For information about system alerts, go to http://www.hp.com/support/hpgt/3par and select your server platform. NOTE: If you are using HP 3PAR OS Software version 3.1.1 or lower, refer to HP 3PAR OS 3.1.1 Messages and Operators Guide for information about system alerts.
MESSAGE (ID:e0002) -{Info} SUGGESTED ACTION Refer to Alert Code 0xe0002 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:e0006) -{Info} SUGGESTED ACTION Refer to Alert Code 0xe0006 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:110004) -{Info} SUGGESTED ACTION Refer to Alert Code 0x110004 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:150002) -{Info} SUGGESTED ACTION Refer to Alert Code 0x150002 in HP 3PAR OS Message and Operator's Guide.
SUGGESTED ACTION Refer to Alert Code 0x230003 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:230004) -{Info} SUGGESTED ACTION Refer to Alert Code 0x230004 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:250002) -{Info} SUGGESTED ACTION Refer to Alert Code 0x250002 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:270001) -{Info} SUGGESTED ACTION Refer to Alert Code 0x270001 in HP 3PAR OS Message and Operator's Guide.
MESSAGE (ID:270007) -{Info} SUGGESTED ACTION Refer to Alert Code 0x270007 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:270008) -{Info} SUGGESTED ACTION Refer to Alert Code 0x270008 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:270050) -{Info} SUGGESTED ACTION Refer to Alert Code 0x270050 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:30003) -{Info} SUGGESTED ACTION Refer to Alert Code 0x0030003 in HP 3PAR OS Message and Operator's Guide.
SUGGESTED ACTION Refer to Alert Code 0x0050002 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:50003) -{Info} SUGGESTED ACTION Refer to Alert Code 0x0050003 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:60006) -{Info} SUGGESTED ACTION Refer to Alert Code 0x0060006 in HP 3PAR OS Message and Operator's Guide. Message (ID:150004) -{Info} Suggested Action Refer to Alert Code 0x0150004 in HP 3PAR OS Message and Operator's Guide.
Message (ID:460003) -{Info} Suggested Action Refer to Alert Code 0x0460003 in HP 3PAR OS Message and Operator's Guide. Message (ID:1a000a) -{Info} Suggested Action Refer to Alert Code 0x01a000a in HP 3PAR OS Message and Operator's Guide. Message (ID:1a000b) -{Info} Suggested Action Refer to Alert Code 0x01a000b in HP 3PAR OS Message and Operator's Guide. Message (ID:1a000c) -{Info} Suggested Action Refer to Alert Code 0x01a000c in HP 3PAR OS Message and Operator's Guide.
Suggested Action Refer to Alert Code 0x01a0011 in HP 3PAR OS Message and Operator's Guide. Message (ID:1a0012) -{Info} Suggested Action Refer to Alert Code 0x01a0012 in HP 3PAR OS Message and Operator's Guide. Message (ID:1a0021) -{Info} Suggested Action Refer to Alert Code 0x01a0021 in HP 3PAR OS Message and Operator's Guide. Message (ID:1a001a) -{Info} Suggested Action Refer to Alert Code 0x01a001a in HP 3PAR OS Message and Operator's Guide.
Message (ID:3b0002) -{Info} Suggested Action Contact HP Technical Support. MESSAGE (ID:2900de) -{Info} SUGGESTED ACTION Refer to Alert Code 0x2900de in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:3700de) -{Info} SUGGESTED ACTION Refer to Alert Code 0x3700de in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:3700fa) -{Info} SUGGESTED ACTION Refer to Alert Code 0x3700fa in HP 3PAR OS Message and Operator's Guide.
SUGGESTED ACTION Refer to Alert Code 0x30005 in HP 3PAR OS Message and Operator's Guide. Message (ID:a0004) -{Info} Suggested Action Refer to Alert Code 0x00a0004 in HP 3PAR OS Message and Operator's Guide. Message (ID:e0016) -{Info} Suggested Action Refer to Alert Code 0x00e0016 in HP 3PAR OS Message and Operator's Guide. Message (ID:e0017) -{Info} Suggested Action Refer to Alert Code 0x00e0017 in HP 3PAR OS Message and Operator's Guide.
Event Type Message MESSAGE (ID:3000fa) -{Info} SUGGESTED ACTION Refer to Alert Code 0x3000fa in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:3000de) -{Info} SUGGESTED ACTION Refer to Alert Code 0x3000de in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:400fa) -{Info} SUGGESTED ACTION Refer to Alert Code 0x400fa in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:90001) -{Info} SUGGESTED ACTION Refer to Alert Code 0x90001 in HP 3PAR OS Message and Operator's Guide.
SUGGESTED ACTION Refer to Alert Code 0xe0002 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:e0005) -{Info} SUGGESTED ACTION Refer to Alert Code 0xe0005 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:1a0002) -{Info} SUGGESTED ACTION Refer to Alert Code 0x1a0002 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:1a00de) -{Info} SUGGESTED ACTION Refer to Alert Code 0x1a00de in HP 3PAR OS Message and Operator's Guide.
MESSAGE (ID:270012) -{Info} SUGGESTED ACTION Refer to Alert Code 0x270012 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:27000e) -{Info} SUGGESTED ACTION Refer to Alert Code 0x27000e in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:27000f) -{Info} SUGGESTED ACTION Refer to Alert Code 0x27000f in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:270010) -{Info} SUGGESTED ACTION Refer to Alert Code 0x270010 in HP 3PAR OS Message and Operator's Guide.
SUGGESTED ACTION Refer to Alert Code 0x270016 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:270017) -{Info} SUGGESTED ACTION Refer to Alert Code 0x270017 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:270019) -{Info} SUGGESTED ACTION Refer to Alert Code 0x270019 in HP 3PAR OS Message and Operator's Guide. MESSAGE (ID:27001a) -{Info} SUGGESTED ACTION Refer to Alert Code 0x27001a in HP 3PAR OS Message and Operator's Guide.
MESSAGE (ID:10000002) - Existing LUN in 3PAR Storage Server has been removed. Additional information: {Info} SUGGESTED ACTION This indicates that an existing exposure to the monitored ESX host has been removed. Please contact your storage administrator if this is not an intended operation. MESSAGE (ID:10000005) - Existing LUN in 3PAR Storage Server has been renamed. Additional information: {Info} SUGGESTED ACTION No action is required.
MESSAGE (ID:1000000b) -Node status has been changed. Additional information: {Info} SUGGESTED ACTION This indicates that there is a node status change. This might be caused by node shutdown or recovery. Please check your storage system for more information.
8 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.
9 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.
A Firewall port requirements For complete information on port requirements, see the “Default port values” appendix in the HP Insight Control for VMware vCenter Server Installation Guide.
B Creating a custom build plan When using the enhanced deployment option to grow a cluster, a custom build plan is required. Use the following procedure to create a custom build plan for growing a cluster. 1. Log in to HP Insight Control Server Provisioning. 2. Select Configuration Files from the DEPLOYMENT options. 3. Select the Kickstart configuration file to modify and then select Save as in the Actions menu. 4. Enter a valid name for the new Kickstart file and then click OK. 5.
Figure 21 Script example 7. 8. 9. 10. 11. Click OK to save the updated Kickstart configuration file. Select OS Build Plans from the DEPLOYMENT options. Select the OS Build Plan to modify and then select Save as in the Actions menu. Enter a valid name for the new custom OS Build Plan and then click OK. Select the new custom OS Build Plan and then select Edit in the Actions menu. The OS Build Plan Edit window opens. 12. Select the ESXi 5.
13. In the Configuration File field, select the new Kickstart configuration file created in the preceding steps. 14. Verify that the Install path field value is maintained from the original OS Build Plan. 15. Click OK to save the edits to the step. 16. Click OK in the OS Build Plan Edit window to save the new build plan. The new custom build plan can now be used to grow a cluster using the enhanced deployment option.
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.
SMU Storage Management Utility. The web browser interface that system administrators can use to configure, monitor, and manage MSA2000 Family storage systems. SMU is accessible from any management host that can access a system through an out-of-band Ethernet connection. 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.
Index A accessing HP Insight Control for vCenter, 27 adding arrays HP StoreOnce Backup, 18 adding management servers HP EVA Command View, 15 adding storage systems EVA , 16 HP 3PAR StoreServ, 14 HP MSA, 17 HP StoreVirtual, 14 HP XP, 18 HP XP P9000, 17 administration, 8 alarm conditions, 114 alarms troubleshooting, 111, 114 alert notification hardware, 111 auto-login failure, 120, 121 B bare-metal provisioning, 34 blade events, 112, 113 C CA-signed certificate VASA provider, 22 certificate administration,
H I hardware alert notification, 111 HBAs viewing, 71 health information viewing, 54 health status, 120 health status information missing, 120 host infrastructure information, 47 network information, 47 overview page, 45 viewing information, 46 host management, 44 host network configuration, 48 host network configuration preferences setting, 36 virtual connect, 36 hosts managing, 44 viewing storage information, 62 HP 3PAR StoreServ adding storage systems, 14 HP EVA adding storage systems, 16 customizing v
Peer Persistence switching, 75 poll interval, 8 portlets, 32 Power Control, 52 power cost setting, 33 power events, 113 power subsystem events, 112, 113 power supply events, 112, 113 powering cycling a server, 52 properties server management, 33 provisioning storage, 82 adding datastores, 83 cloning VMs, 100 creating VMs, 94 deleting datastores, 92 deleting unassigned volumes, 93 expanding datastores, 90 SSO enabling, 56 failure, 120 Storage Administrator Portal about, 12 troubleshooting, 122 storage modul
VCM launching, 56 vendor providers list VASA provider, 21 viewing cluster storage information, 64 datastore storage information, 66 HBAs, 71 host storage information, 62 management servers, 19 paths, 72 replications, 74 storage systems, 19 storage volumes, 69 virtual disks, 71 VM storage information, 67 VMs to volumes, 76 Virtual Connect network diagram, 50 virtual connect, 36 virtual disks customizing location, 82 viewing, 71 virtual machines (VMs) cloning, 100 creating from a template, 94 viewing storage
