HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide

HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide AT459-96002 Part number: AT459-96002 First edition: April 2009

Legal and notice information Copyright 2009 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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website: http://www.hp.com/go/storagewarranty Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Adobe and Acrobat are trademarks of Adobe Systems Incorporated.

Contents About this guide... 7 Intended audience... 7 Prerequisites... 7 Related documentation... 7 Document conventions and symbols... 8 Rack stability... 9 HP technical support... 9 Subscription service... 9 HP websites... 10 Documentation feedback... 10 1 VSA requirements... 11 2 Supported configurations... 13 Storage configuration inside the enclosure... 13 External storage configuration... 15 3 Hardware installation... 17 c-class blade enclosure installation... 17 Configure storage inside the enclosure using excess capacity from local server blade drives... 19 Configure storage inside the enclosure using the SB40c... 20 Adding the SB40c to an existing HP server blade loaded with VMware ESX server... 20 Adding the SB40c with a new HP server blade... 20 Configure storage externally to an MDS600 or MSA2000sa... 21 Adding the MDS600 or MSA2000sa to an existing HP server blade loaded with VMware ESX Server... 21 Adding the MDS600 or MSA2000sa with a new HP server blade... 23 4 Software installation... 27 Installing the VSA... 27 Configuring the capacity of the data disk... 27 Installing with the VMware VI Client... 28 Add VSA to Inventory... 28 Select a network connection... 28 Configure a data disk... 28 Power on the VSA and configure IP address and host name... 29 Power on the VSA... 29 Setting the IP address... 30 Finishing up with VI Client... 32 Installing the Centralized Management Console... 33 Installing the CMC in Windows... 33 Installing the CMC in Linux... 33 Getting started with the Centralized Management Console... 34 HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 3

Configuring the hardware... 35 Configuring monitoring and network... 35 Creating the iscsi SAN... 35 5 Best practices... 37 Replication... 37 Volumes and snapshots... 37 iscsi sessions... 37 Storage nodes in the Management Group... 37 Storage nodes in the cluster... 37 4

Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Half-height server blade configuration... 14 Full-height server blade configuration... 14 Optional redundant link between blade enclosures... 15 External SAS configuration... 16 c7000 full-height blade numbering scheme... 17 c3000 full-height blade numbering scheme... 17 c7000 half-height blade numbering scheme... 18 c3000 half-height blade numbering scheme... 19 Logging into the SAN/IQ Configuration Interface... 30 Logging into the Configuration Interface... 31 Configuration Interface menu... 31 Selecting an interface to configure... 31 Setting the Hostname... 31 Logging out of the Configuration Interface menu... 32 Opening the CMC for the first time... 34 Newly found VSA in CMC... 35 Configuring the hardware... 35 HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 5

Tables 1 2 3 4 5 Document conventions... 8 Memory requirements... 11 Half-height blade and SB40c locations in the c7000 enclosure... 18 Half-height blade and SB40c locations in the c3000 enclosure... 19 Block size per maximum disk size... 27 6

About this guide This guide provides information about: Supported configurations for the HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem Environment Installing hardware and software on the HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem Environment Intended audience This guide is intended for users with knowledge of: Storage area networks Basic operating system commands and utilities Prerequisites Prerequisites for installing this product include: c-class blade infrastructure HP VSA Server Blade(s) for VMware ESX 3.5 U3 or later, or VMware 3.5i U3 or later server(s) VMware ESX 3.5 U3 or later or VMware 3.5i U3 or later licenses NOTE: Further references to VMware ESX Server are equivalent to VMware ESX Server 3.5 U3 or later or VMware ESXi Server. HP LeftHand P4000 VSA for VMWare ESX Storage options discussed in this guide include: Local blade storage HP StorageWorks SB40c Storage Blade HP StorageWorks MDS600 HP StorageWorks MSA2000sa Related documentation The following documents provide related information: HP LeftHand P4000 VSA user guide HP LeftHand P4000 VSA Quick Start user guide See the MDS600 QuickSpecs for server compatibility list See the MSA2000sa QuickSpecs for server compatibility list See individual server blade QuickSpecs for SB40c support HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 7

You can find these documents from the following websites: http://www.hp.com/support http://www.hp.com/go/p4000 http://h18000.www1.hp.com/products/quickspecs/ In the Storage section, click bladesystem and then select your product. Document conventions and symbols Table 1 Document conventions Convention Blue text: Table 1 Blue, underlined text: http://www.hp.com Bold text Italic text Monospace text Monospace, italic text Monospace, bold text Element Cross-reference links and e-mail addresses Website addresses Keys that are pressed Text typed into a GUI element, such as a box GUI elements that are clicked or selected, such as menu and list items, buttons, tabs, and check boxes Text emphasis File and directory names System output Code Commands, their arguments, and argument values Code variables Command variables Emphasized monospace text WARNING! Indicates that failure to follow directions could result in bodily harm or death. CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: Provides clarifying information or specific instructions. 8 About this guide

NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Rack stability Rack stability protects personnel and equipment. WARNING! To reduce the risk of personal injury or damage to equipment: Extend leveling jacks to the floor. Ensure that the full weight of the rack rests on the leveling jacks. Install stabilizing feet on the rack. In multiple-rack installations, fasten racks together securely. Extend only one rack component at a time. Racks can become unstable if more than one component is extended. HP technical support For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 9

HP websites For additional information, see the following HP websites: http://www.hp.com http://www.hp.com/go/storage http://www.hp.com/support/manuals http://www.hp.com/support/downloads http://www.hp.com/go/bladesystem http://www.hp.com/go/storageblades Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to storagedocsfeedback@hp.com. All submissions become the property of HP. 10 About this guide

1 VSA requirements Before beginning the software installation, ensure that the ESX Server meets the following requirements: Available drive space of up to 10 TB per VSA 1, 2 or 4GB of memory reserved depending on the VSA disk capacity Table 2 Memory requirements Total capacity of all installed disks Less than 500GB 500GB 4.5TB 4.5TB 9TB 9TB 10TB Minimum required memory 384MB 1GB 2GB 3GB Two full CPU cores available A Gigabit Ethernet or internal network environment See the list below for additional information: You must designate a host name for the VSA. Plan the network configuration, including an IP address, subnet mask, and gateway for the VSA, or use DHCP. NOTE: The use of DHCP is not recommended for VSA implementations. Have a virtual switch comprised of dual Gigabit Ethernet or more. Providing network redundancy and greater bandwidth improves both performance and reliability. Ensure the ethernet or network environment is located on the same virtual switch as the VMkernel network used for iscsi traffic. This allows for a portion of iscsi I/O to be served directly from the VSA to the iscsi initiator without using a physical network. Ensure the ethernet or network environment is on a virtual switch that is separate from the VMkernel network used for VMotion. This prevents VMotion traffic and VSA I/O traffic from interfering with each other and affecting performance. The server is configured to automatically start before any other virtual machines, when the ESX Server on which it resides is started. This ensures that the VSA is brought back online as soon as possible to automatically re-join its SAN/IQ cluster. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 11

12 VSA requirements

2 Supported configurations The following are supported configurations. Storage configuration inside the enclosure There are two storage configurations inside the enclosure. Excess capacity from local server blade drives creates the shared storage pool. Install HP LeftHand VSA software in a virtual machine on a VMware ESX Server host adjacent to the SB40c, creating an iscsi SAN out of the SB40c. The SB40c can also provide VM data stores to other VMs running on the adjacent server blade. The configuration for using excess capacity from local server blade drives to create the shared storage pool is shown below. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 13

Figure 1 Half-height server blade configuration Figure 2 Full-height server blade configuration 14 Supported configurations

The configuration using the SB40c as an iscsi SAN is shown below. Figure 3 Optional redundant link between blade enclosures External storage configuration There are two supported external storage configurations. Connecting externally to an MDS600 Connecting externally to an MSA2000sa HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 15

Figure 4 External SAS configuration 16 Supported configurations

3 Hardware installation c-class blade enclosure installation This section details the supported c-class Blade Enclosure configurations and installation processes. Figure 5 c7000 full-height blade numbering scheme Figure 6 c3000 full-height blade numbering scheme HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 17

Figure 7 c7000 half-height blade numbering scheme Table 3 shows the preferred half-height blade and SB40c locations in the c7000 enclosure. The server blade and the corresponding SB40c must be in adjacent enclosure slots. For example the server blade is directly connected to the A-SB40c. Table 3 Half-height blade and SB40c locations in the c7000 enclosure Possible locations Enclosure slot number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Half-height series A B C D E F G H SB40c A B C D E F G H 18 Hardware installation

Figure 8 c3000 half-height blade numbering scheme Table 4 shows the preferred half-height blade and SB40c locations in the c3000 enclosure. The server blade and the corresponding SB40c must be in adjacent enclosure slots. For example the server blade is directly connected to the A-SB40c. Table 4 Half-height blade and SB40c locations in the c3000 enclosure Possible locations Enclosure slot number 1 2 3 4 5 6 7 8 Half-height series A B C D SB40c A B C D Configure storage inside the enclosure using excess capacity from local server blade drives This configuration provides support for both full-height blades and half-height blades. The local, internal blade hard drives are used for all storage for this configuration. To add the VSA solution to an existing server blade with ESX Server: 1. If an enclosure blank is in the corresponding, adjacent enclosure slot, remove it. If installing a full-height server blade you may need to remove the half-height blade shelf. 2. Insert the HP server blade into the desired c-class enclosure slot. 3. Log in to the enclosures Onboard Administrator. 4. Select the blade that you have just added. 5. Click the ilo link for that blade. 6. Click either the Integrated Remote Console or the Remote Console. 7. Start the blade using the Virtual Devices Power button. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 19

8. Observe the boot process and press F8 when the SmartArray configuration is presented. 9. Build an array with all drives using RAID5. 10. Save the array configuration. 11. Escape out of the SmartArray Configuration Utility. 12. Install VMware ESX Server on the new server blade on the internal hard drives. 13. Configure the VMware ESX Server. 14. Add storage from the current ESX Storage Pool to the VSA. 15. Install VSA. Configure storage inside the enclosure using the SB40c This configuration provides support for half-height blades only. The local, internal blade hard drives are used for the VMware ESX Server installation. The SB40c is used to provide storage for the VSA. Adding the SB40c to an existing HP server blade loaded with VMware ESX server To add the VSA solution to an existing server blade loaded with VMware ESX Server: 1. Make sure that all Virtual Machines on the VMware ESX Server have been shutdown. 2. Shutdown the VMware ESX Server. 3. If an enclosure blank is in the corresponding, adjacent enclosure slot, remove it. 4. Insert the SB40c in the corresponding, adjacent enclosure slot. 5. Log into the enclosures Onboard Administrator. 6. Select the blade that now contains the SB40c. 7. Click the ilo link for that blade. 8. Click either the Integrated Remote Console or the Remote Console. 9. From the Onboard Administrator, start the blade using the Virtual Devices Power button. 10. Observe the boot process and press F8 when the P400 SmartArray configuration is presented. 11. Build an array with at least three drives using RAID5. 12. Save the array configuration. 13. Exit out of the P400 SmartArray Configuration Utility. 14. Allow the blade to fully boot to VMware ESX Server. 15. Add the new SB40c storage to the VMware ESX Server Storage Configuration. 16. Install the VSA. Adding the SB40c with a new HP server blade To add the VSA solution to a new server blade loaded with VMware ESX Server: 1. Install the server blade in one of the recommended enclosure slots that is available. 2. If an enclosure blank is in the corresponding, adjacent enclosure slot, remove it. 20 Hardware installation

3. Insert the SB40c in the corresponding, adjacent enclosure slot. 4. Log in to the enclosures Onboard Administrator. 5. Select the blade that now contains the SB40c. 6. Click the ilo link for that blade. 7. Click either the Integrated Remote Console or the Remote Console. 8. Start the blade using the Virtual Devices Power button. 9. Observe the boot process and press F8 when the P200i SmartArray configuration is presented. 10. Build an array with all drives using RAID5. 11. Observe the boot process and press F8 when the P400 SmartArray configuration is presented. 12. Build an array with at least three drives using RAID5. 13. Save the array configuration. 14. Escape out of the P400 SmartArray Configuration utility. 15. Install VMware ESX Server on the new server blade on the internal hard drives. 16. Configure the VMware ESX Server. 17. Add the SB40c storage to the VMware ESX Server Storage Configuration. 18. Install the VSA as described in the Software Installation Section of this document. Configure storage externally to an MDS600 or MSA2000sa This configuration provides support for half-height blades only. The local, internal blade hard drives are used for the VMware ESX Server installation. The MDS600 or MSA2000sa is used to provide storage for the VSA. Adding the MDS600 or MSA2000sa to an existing HP server blade loaded with VMware ESX Server To add the VSA solution to an existing server blade with VMware ESX Server: 1. Ensure that all Virtual Machines on the VMware ESX Server have been shutdown. 2. Shut down the VMware ESX Server. 3. Remove the server blade and install the P700m Mezzanine card in the server blade and the HP StorageWorks 3GB SAS BL Switch in the enclosures interconnect bays. Use the following rules for Mezzanine and interconnect bay positioning: c3000 Enclosure: For full-height and half-height blades, place the P700m in Mezzanine slot two. Place the HP StorageWorks 3GB SAS BL Switches in interconnect bays three and four. c7000 Enclosure: For full-height and half-height blade,s place the P700m in Mezzanine slot two. Place the HP StorageWorks 3GB SAS BL Switches in interconnect bays five and six. 4. Connect the MDS600 or MSA2000sa to the HP StorageWorks 3GB SAS BL Switches. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 21

5. Power on the MDS600 or MSA2000sa and configure the storage array for management. NOTE: If you are using the MSA2000sa, be sure that it is configured for management. 6. Replace the blade in the blade enclosure and then boot the VMware ESX Server blade. 7. Log into the blade enclosure's Onboard Administrator. 8. Go to Interconnect Bays>3Gb SAS Switches>Management Console. This is the HP Virtual SAN Manager. 9. Click HP 3G SAS Blade Switch... in the left panel. 10. In the right panel, click Advanced Settings. 11. In the right panel, enable the Multi-initiator Mode. 12. In the left panel, click Zone Groups. 13. In the right panel, click Create Zone Group. MDS600 disk enclosures are listed under the Drive Bay radio button. MSA2000sa Arrays are listed under the Switch Port radio button. 14. In the left panel, under Blade Device Bay, grant Zone Access for each VSA Server. 22 Hardware installation

15. Complete the following, depending on which storage configuration you are using. If you are using the MSA2000sa Storage array: 1. Log into the MSA2000sa Administrative web interface and verify that the VMware ESX Servers SAS WWID(s) were discovered. 2. Assign aliases to each of the SAS WWID(s). 3. Create a single MSA2000 volume out of all of the available hard drives except one. Use one hard drive as a global hot spare. 4. Determine the number of VSAs that will be homed to this MSA2000 and build equal sized Vdisks for each of the VSAs on the volume previously created. 5. Present the MSA2000 Vdisks to the respective VMware ESX Server. 6. Add the new MSA2000 Vdisk storage to the VMware ESX Server storage configuration. If you are using the MDS600: 1. Log into the enclosure's Onboard Administrator. 2. Select the blade that will house the VSA and has access to the MDS600. 3. Click the ilo link for that blade. 4. Click either Integrated Remote Console or Remote Console. 5. From the Onboard Administrator, start the blade using the Virtual Devices Power button. 6. Observe the boot process and press F8 when the P700m SmartArray configuration is presented. 7. Build an array with as many as needed, but at least three drives using RAID5. 8. Save the array configuration. 9. Exit out of the P700m SmartArray Configuration utility. 10. Allow the blade to fully boot to VMware ESX Server. 11. Add the new MDS600 storage to the VMware ESX Server Storage Configuration. 16. Install the VSA. Adding the MDS600 or MSA2000sa with a new HP server blade To add the VSA solution to a new server blade loaded with VMware ESX Server: 1. Install the P700m Mezzanine card in the new server blade and the HP StorageWorks 3GB SAS BL Switch in the enclosures interconnect bays. Use the following rules for mezzanine and interconnect may positioning: c3000 Enclosure: For full-height and half-height blades place the P700m in Mezzanine slot two. Place the HP StorageWorks 3GB SAS BL Switches in interconnect bays three and four. c7000 Enclosure: For full-height and half-height blades place the P700m in Mezzanine slot two. Place the HP StorageWorks 3GB SAS BL Switches in interconnect bays five and six. 2. Connect the MDS600 or MSA2000sa to the HP StorageWorks 3GB SAS BL Switches. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 23

3. Power on the MDS600 or MSA2000sa. NOTE: If you are using the MSA2000sa be sure that it is configured for management. 4. Install the VMware ESX Server on the new server blade. 5. Configure the VMware ESX Server. 6. Log into blade enclosure's Onboard Administrator. 7. Go to Interconnect Bays>3Gb SAS Switches>Management Console. This is the HP Virtual SAN Manager. 8. Click HP 3G SAS Blade Switch... in the left panel. 9. In the right panel, click Advanced Settings. 10. In the right panel, enable the Multi-initiator Mode and click Save Changes. 11. In the left panel, click Zone Groups. 12. In the right panel, click Create Zone Group. MDS600 disk enclosures are listed under the Drive Bay radio button. MSA2000sa Arrays are listed under the Switch Port radio button. 13. Create Zone Group and click Save Changes. 14. In the left panel under, Blade Device Bay, grant Zone Access for each VSA Server and save changes. 24 Hardware installation

15. Complete the following, depending on which storage configuration you are using. If you are using the MSA2000sa Storage array: 1. Log in to the MSA2000sa s Administrative web interface and verify that the VMware ESX Servers SAS WWID(s) are discovered. 2. Assign aliases to each of the SAS WWID(s). 3. Create a single MSA2000 volume out of all of the available hard drives except one. Use one hard drive as a global hot spare. 4. Determine the number of VSAs that will be homed to this MSA2000 and build equal sized Vdisks for each of the VSAs on the volume previously created. 5. Present the MSA2000 Vdisks to the respective VMware ESX Server. 6. Add the new MSA2000 Vdisk storage to the VMware ESX Server storage configuration. If you are using the MDS600: 1. Log into the enclosures Onboard Administrator. 2. Select the blade that will house the VSA and has access to the MDS600. 3. Click the ilo link for that blade. 4. Click either the Integrated Remote Console or the Remote Console. 5. From the Onboard Administrator, start the blade using the Virtual Devices Power button. 6. Observe the boot process and press F8 when the P700m SmartArray configuration is presented. 7. Build an array with all drives using RAID5. 8. Save the array configuration. 9. Exit out of the P700m SmartArray Configuration utility. 10. Allow the blade to fully boot to VMware ESX Server. 11. Add the new MDS600 storage to the VMware ESX Server Storage Configuration. 16. Add the Storage to the VMware ESX Server storage configuration. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 25

26 Hardware installation

4 Software installation Installing the VSA There are two ways you can obtain the VSA. VSA can be downloaded as a zip package from HP LeftHand Networks web site or as an OVF package imported through the VI client Import Virtual Appliance Wizard. To install the packaged VSA for the first time: 1. Unzip to the prepared directory and start the VMware VI Client. 2. Transfer the virtual machine to the ESX Server. 3. Add the VSA to inventory. 4. Select the network. 5. Configure the data disk. 6. Reserve the CPU and memory. 7. Power on the VSA. 8. Set the IP address and host name of the VSA. To import the VSA as an OVF package through the VI Client: 1. Configure the data disk. 2. Reserve the CPU and memory. 3. Power on the VSA. 4. Set the IP address and host name of the VSA. Configuring the capacity of the data disk When you configure the data disk, use Table 5 to determine the proper size to configure the disk. The maximum disk size on the ESX Server is limited by the block size used to format the datastore. Table 5 Block size per maximum disk size Block size 1MB 2MB 4MB 8MB Max VMDK 256GB 512GB 1024GB 2048GB HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 27

Installing with the VMware VI Client To install with the VMWare VI Client: 1. Connect to VMware ESX Server host via VC or VI Client. 2. Click VMware ESX Server host and go to Configuration tab. 3. Select Storage. 4. Find the local VMFS datastore where VSA would be hosted. 5. Right-click and select Browse DataStore. 6. Create new directory and click the upload files icon. 7. Upload unzipped folder for VSA. Add VSA to Inventory Using the VI Client: 1. In the Inventory Panel, select VMware ESX Server. 2. In the Information Panel, select the Configuration tab. 3. In the Hardware section, select Storage (SCSI, SAN, and NFS). 4. In the Storage section, right-click the datastore icon and select Browse Datastore. 5. Right-click the VSA.vmx file and select Add to Inventory. 6. In the Add to Inventory Wizard, enter a name for the new VSA and click Next. 7. Select the Resource Pool to run the VSA and click Next. 8. Verify the information and click Finish. 9. Close the Datastore browser. Select a network connection To select a network connection: 1. In the Inventory Panel select the VSA. 2. In the Information Panel select Edit Settings in the Commands section. The Virtual Machine Properties window opens. 3. On the Hardware tab, select Network Adapter 1. 4. Select the appropriate network connection from the Network label list on the right. Configure a data disk To configure a data disk: 1. Click Add at the bottom of the Hardware, then Select Device Type. 2. Select Hard Disk as the type of device you want to add and click Next. 28 Software installation

3. Select Create a new virtual disk and click Next. 4. In the Disk Capacity section, designate a capacity that is suitable for the amount of storage available on your ESX Server. See Table 5 for information about maximum disk size. 5. In the Location section, select Store with Virtual Machine and click Next. 6. For the first disk select the Virtual Device Node to be SCSI 1:0 from the drop-down menu. For additional disks, assign SCSI 1:1 through 1:4, in sequential order in the drop down menu. NOTE: The VSA supports up to five VDMKs for VSA storage. 7. Select Mode, Independent >Persistent and click Next. 8. Review the device configuration and click Finish to complete the Add Hardware wizard. The Virtual Machine Properties window opens. 9. Click the Resources tab. 10. Select CPU and reserve at least 2000 MHz. 11. Select Memory and reserve 1024MB. 12. Click OK to close the Virtual Machine Properties window. 13. Select ESX Server in the Inventory panel. 14. Click the Resource Allocation tab. 15. Verify the CPU and memory reservations just set. Power on the VSA and configure IP address and host name Power on the VSA To turn on the VSA: 1. In the inventory panel, select the new VSA and power it on using the Power On command on the Information panel. 2. Click the Console Tab and wait for the VSA to boot. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 29

3. When the VSA has finished booting, a login prompt appears. See Figure 9. Figure 9 Logging into the SAN/IQ Configuration Interface 4. Log in and use the SAN/iQ Configuration Interface to configure an IP address and host name for the VSA. Setting the IP address Use the Configuration Interface to set IP addresses and host names for all the VSAs in your environment. You can return to the Configuration Interface to find or change an IP address or host name. 30 Software installation

1. Type Start and press Enter. The Configuration Interface window opens. See Figure 10. Figure 10 Logging into the Configuration Interface 2. Press Enter to log in. The Configuration Interface main menu opens. See Figure 11. Figure 11 Configuration Interface menu 3. Tab to Network TCP/IP Settings and press Enter. The Available Network Devices window opens. See Figure 12. Figure 12 Selecting an interface to configure 4. Tab to the network interface and press Enter. The Network Settings window opens. See Figure 13. The cursor should be in the Hostname field. Tab to the field if necessary. Figure 13 Setting the Hostname 5. Press Backspace in the Hostname field to delete the default name and type your own host name. This host name displays in the CMC. It does not change the name of the original.vmx file, nor does it change the name in VMware. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 31

6. Configure the IP Address. NOTE: HP recommends configuring the IP address manually. 1. Configure IP address manually. 1. Tab to the choice Use the Following IP Address and press Enter. The IP Address, Netmask, and Gateway list opens for editing. 2. Tab to each field and enter the appropriate information. Gateway is a required field. If you do not have a gateway, enter 0.0.0.0. 2. Using DHCP 1. Tab to the choice Obtain IP address automatically using DHCP and press Enter to select it. 2. Tab to OK and press Enter. A message opens, asking you to verify the request. 3. Tab to OK and press Enter. After a short pause, another message opens that displays the new IP address. Record this IP address for later use. 7. Tab to OK and press Enter. A confirmation message opens. 8. Press Enter. The network interface is now configured (wait a few seconds). The Available Network Devices window opens. 9. On the Available Network Devices window, tab to Back and press Enter to return to the Configuration Interface menu. See Figure 14. Figure 14 Logging out of the Configuration Interface menu 10. Tab to Log Out and press Enter. The Configuration Interface entry window is displayed again. See Figure 10. 11. Press Ctrl+Alt to get the cursor back from the console. Finishing up with VI Client 1. In the VI Client Information Panel, click the Summary tab. 2. In the General section on the Summary tab, verify that the IP address and host name are correct, and that VMware Tools are running. NOTE: If VMware Tools show out of date then they are running correctly. The show out of date status is not a problem. VMware tools are updated with each SAN/iQ software upgrade. 32 Software installation

3. In the inventory panel, right-click the VSA and select Rename. 4. Change the name of the VSA to match the host name, if desired. Your VSA is ready to use. 5. Minimize your VI Client session. See Installing the Centralized Management Console and Getting started with the Centralized Management Console. Installing the Centralized Management Console Install the CMC on the computer or virtual machine that you use to administer the VSA. You administer the entire network of VSAs from this CMC. Installing the CMC in Windows IMPORTANT: You must be running Windows in order to run the application. 1. Start the CMC installer. The installation wizard opens and starts the installation process. 2. At the Choose Install Set window, select the configuration most appropriate for your setup. 3. When the installation completes, HP LeftHand Networks is added as a separate Program Group and an icon is added to the Microsoft Windows desktop. 4. To start the CMC, double-click the icon on your desktop, or from the Start menu, select All Programs > HP Lefthand Networks -> HP LeftHand Centralized Management Console. Installing the CMC in Linux 1. Click the CMC installer. The installation wizard opens and starts the installation process. 2. At the Choose Install Set window, select the configuration most appropriate for your setup. 3. When the installation completes, HP LeftHand Networks is added as a separate Program Group. 4. From the directory into which you installed the files, run the script./console to start the CMC. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 33

Getting started with the Centralized Management Console 1. Open the CMC. See Figure 15. Figure 15 Opening the CMC for the first time 2. Click Find Nodes Wizard. 34 Software installation

3. Click Next on the Find Nodes Wizard and proceed through the steps. The wizard guides you through the steps for finding a VSA on your network. After finishing the wizard, the VSA appears in the navigation window in the Available pool. See Figure 16. Figure 16 Newly found VSA in CMC Configuring the hardware Configure hardware settings before you add the VSA to a management group. Select the VSA in the navigation window to expand the hardware configuration categories. Use these categories to configure RAID, monitoring, and the network. See Figure 17. Figure 17 Configuring the hardware Configuring monitoring and network Use the rest of the configuration categories to change settings for the following features: Alerts and monitoring SNMP traps Network settings such as NIC bonding Creating the iscsi SAN The VSAs are on the network and operating properly. Use the Centralized Management Console to create the clustered iscsi SAN with the VSAs. Use the Management Groups, Clusters, and Volumes wizard to create your storage pool. For information about using the wizards, see LeftHand SAN User Manual or the online help. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 35

36 Software installation

5 Best practices Replication HP recommends that the Network RAID level be a minimum of two to ensure high availability of your data. Volumes and snapshots The management group contains 1,001 to 1,500 volumes and snapshots. The Configuration Summary displays orange when there are between 1,001 and 1,500 volumes and snapshots. When more than 1,500 volumes and snapshots appear a warning triggers by turning that line red. As soon as the total number reduces below the boundary, the summary bar returns to the previous indicator, either orange or green. iscsi sessions The optimum number of iscsi sessions connected to volumes in a management group ranges up to 4,000. If the management group contains 4,001 to 5,000 iscsi sessions, the Configuration display for that line turns orange. iscsi sessions trigger a warning by turning that line red. As soon as the total number of iscsi sessions reduces below the boundary, the summary bar returns to the previous indicator, either orange or green. Storage nodes in the Management Group The optimum number of storage nodes in a management group ranges up to 20. If the management group contains 21 to 30 storage nodes, the Configuration Summary displays orange for that line of the management group. Over 30 storage nodes triggers a warning by turning that line red. As soon as the total number of storage nodes reduces below the boundary, the summary bar returns to the previous indicator, either orange or green. Storage nodes in the cluster The optimum number of storage nodes in a cluster ranges up to 10. If the cluster contains 11 to 16 storage nodes, the Configuration Summary displays orange for that line of the management group. Over 16 storage nodes in a cluster triggers a warning by turning that line red. As soon as the total number of storage nodes reduces below the boundary, the summary bar returns to the previous indicator, either orange or green. HP recommends that a minimum of three (3) VSAs be installed. This configuration will not require a Failover Manager VM. If two (2) VSAs are installed, a third VM for the Failover Manager will be required. The Failover Manager should be installed on an ESX Server that does not have a VSA installed on it. HP LeftHand P4000 Virtual SAN Appliance in an HP BladeSystem environment solution guide 37

38 Best practices