HP Pavilion p6000 - Desktop PC User manual

HP P6300/P6500 Enterprise Virtual Array
Installation Guide
Abstract
The P6300 EVA is customer self installable. However, you may purchase installation service by an HP-authorized service
provider if preferred. The P6500 EVA requires installation service by an HP-authorized service provider. For more information,
contact HP technical support in North America at 1-800-474-6836. Outside North America, call HP technical support at the
nearest location. Telephone numbers for worldwide technical support are listed on the HP website: http://www.hp.com/support.
To assist you in installing the P6300/P6500 EVAs, videos of the procedures have been produced. Go to the Services Media
Library website: http://www.hp.com/go/sml and navigate to your product to view these videos.
*5697-8091*
HP Part Number: 5697-8091
Published: May 2011
Edition: 1

© Copyright 2011 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. 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
To obtain a copy of the warranty for this product, see the warranty information website: http://www.hp.com/go/storagewarranty
Acknowledgements
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Linux® is a registered trademark of Linus Torvalds in the U.S. and other countries.
Printed in Puerto Rico

Contents
1 Reviewing and confirming your plans............................................................5
Overview................................................................................................................................5
Prerequisites.............................................................................................................................5
Plan your storage configuration..................................................................................................5
General IP-SAN recommendations..........................................................................................6
Recommended switch infrastructure for an IP-SAN.....................................................................7
Network latency..................................................................................................................9
Network bandwidth.............................................................................................................9
Total number of iSCSI and iSCSI/FCoE initiators....................................................................11
Number of paths required per initiator..................................................................................12
Using Internet Storage Name Service (iSNS) .........................................................................13
Using iSCSI ports ..............................................................................................................13
Security............................................................................................................................13
System and performance expectations..................................................................................17
RAID levels.......................................................................................................................17
HP P6000 Command View implementation................................................................................18
2 Preparing your site...................................................................................19
Overview..............................................................................................................................19
Provide adequate structural support for the floor.........................................................................19
Provide adequate clearance space and ventilation......................................................................19
Provide adequate and redundant sources of power.....................................................................19
Remove product from packaging...............................................................................................19
3 Installing components................................................................................21
Overview..............................................................................................................................21
Rack installation best practices.................................................................................................21
Attach the brackets for a longer chassis.....................................................................................22
Attach the rails.......................................................................................................................24
Install the enclosures...............................................................................................................25
Installing the disk drives into the drive bays................................................................................27
4 Connecting cables and power cords...........................................................29
Overview..............................................................................................................................29
Cabling best practices.............................................................................................................29
Connecting cables..................................................................................................................29
Connecting the array to the disk enclosures...........................................................................29
Connecting the array to servers and switches.........................................................................30
Labeling cables using labeling kit........................................................................................30
Connecting the power cords....................................................................................................30
5 Turning on power.....................................................................................31
Power on the devices...............................................................................................................31
Power on best practices......................................................................................................31
Power on procedure...........................................................................................................31
Verify the operating status of the controller enclosures..................................................................31
Verify the operating status of the disk enclosures.........................................................................32
Verify the operating status of the Fibre Channel switches and adapters..........................................33
Contents 3

Installing Fibre Channel drivers.................................................................................................33
6 Managing the iSCSI or iSCSI/FCoE module using HP P6000 Command View..34
Configuring the iSCSI and iSCSI/FCoE module management ports...............................................34
Fibre Channel zoning..............................................................................................................37
HP P6000 Command View discovery........................................................................................38
Configuring the iSCSI IP ports..................................................................................................43
Setting the time on the iSCSI or iSCSI/FCoE modules..................................................................43
Upgrading the iSCSI or iSCSI/FCoE module firmware.................................................................44
Restarting the iSCSI or iSCSI/FCoE module ...............................................................................45
Saving or restoring the iSCSI or iSCSI/FCoE module configuration................................................45
Locating the iSCSI or iSCSI/FCoE modules ................................................................................46
7 Connecting to the management module......................................................48
Overview..............................................................................................................................48
Connecting to the management module.....................................................................................48
Connecting through a public network...................................................................................48
Connecting through a private network..................................................................................49
Accessing HP P6000 Command View on the management module...............................................50
Changing the host port default operating mode..........................................................................50
Accessing the HP P6000 WOCP through HP P6000 Command View...........................................51
8 Configuring servers using HP P6000 SmartStart...........................................52
Configuring management servers using HP P6000 SmartStart.......................................................52
Configuring application servers using HP P6000 SmartStart.........................................................52
Configuring application servers manually...................................................................................52
Using and monitoring your storage...........................................................................................52
Controller software recovery ...............................................................................................52
Installing HP Insight Remote Support software........................................................................52
9 Support and other resources......................................................................54
Contacting HP........................................................................................................................54
HP technical support..........................................................................................................54
Subscription service............................................................................................................54
Documentation feedback....................................................................................................54
Related information.................................................................................................................54
Documents........................................................................................................................54
Websites..........................................................................................................................54
Typographic conventions.........................................................................................................55
Customer self repair................................................................................................................56
Rack stability..........................................................................................................................56
Location of WWN and serial number........................................................................................56
A Cabling the P6300/P6500 EVA................................................................58
Overview..............................................................................................................................58
Connecting P6300 EVA controllers to the disk enclosures (2C6D)..................................................58
Connecting P6500 EVA controllers to the disk enclosures (2C6D)..................................................63
Connecting the P6300/P6500 EVA to servers and switches.........................................................67
Fibre Channel....................................................................................................................67
iSCSI and iSCSI/FCoE........................................................................................................70
4 Contents

1 Reviewing and confirming your plans
Overview
Before installing the P6300/P6500 EVA, HP recommends that you:
•Develop an installation and configuration plan for your Fibre Channel FC-SAN and/or Ethernet
IP-SAN environments.
•Review all videos and documentation.
•Determine if the FC host ports will be fabric-attached (N port connected to a Fibre Channel
switch) or direct-attached (NL port connected to a Fibre Channel adapter in a server or to a
bridge). The P6300/P6500 EVAs are factory configured for fabric-attached. To change to
direct-attached mode, see “Connecting to the management module” (page 48).
•Determine if the IP SAN will be lossy or lossless and if iSCSI and/or FCoE are being supported.
Prerequisites
Prerequisites for using this product include:
•A Fibre Channel switch installed in your environment for fabric-attached configurations
•An equipment cabinet suitable for 2U sized enclosures
•A 1 GbE or 10 GbE Ethernet switch, if you configure the P6300/P6500 EVA 1 GbE iSCSI
modules (or iSCSI modules) or the 10 GbE iSCSI/FCoE modules (or iSCSI/FCoE modules) as
iSCSI targets
•A converged network switch, if you configure the P6300/P6500 EVA 10 GbE iSCSI/FCoE
modules as iSCSI/FCoE targets, and separately configured iSCSI and FCoE VLANs
•One of the following is required for P6300/P6500 EVA management:
A management server running Windows for HP P6000 Command View software
(server-based management); the management server should have either an FC HBA, a 1
GbE iSCSI initiator, a 10 GbE iSCSI initiator, or a converged network adapter
◦
◦A management module running HP P6000 Command View software (array-based
management)
•A CD-ROM drive attached to either the management server or the server attached to the
management module
•Cat5E or Cat6 cabling to the 1 GbE iSCSI module data ports
•For connections to the controller 10GbE iSCSI/FCoE module data ports, HP recommends a)
10GbE SFP+ optical transceivers with optical Fibre Channel cables (PremierFlex or OM3
cables) when connecting outside of the cabinet, or b) 10GbE SFP+ copper cabling when
connecting inside of the cabinet. See the P6000 QuickSpecs for SFP and cable part numbers.
Plan your storage configuration
Proper planning of the system storage and its subsequent performance is critical to a successful
deployment of the EVA. Improper planning or implementation can result in wasted storage space,
degraded performance, or inability to expand the system to meet growing storage needs. Planning
considerations include:
•System and performance expectations
•Striping methods
•RAID levels
Overview 5

•Disk drive sizes and types
•Spare drives
•Array sizing (capacity)
•Number of Fibre Channel presented virtual LUNs
•Number of iSCSI and FCoE initiators
iSCSI module: Maximum of 256 initiators or logins◦
◦iSCSI/FCoE module: Maximum of 1024 initiators or logins
•Number of virtual LUNs to be presented to the iSCSI and FCoE initiators
iSCSI module: Maximum of 255 LUNs (plus LUN 0)◦
◦iSCSI/FCoE module: Maximum of 1020 combined iSCSI and FCoE LUNs (plus LUN 0
from each virtual port group)
NOTE: FCoE requires a converged network switch which implements data center bridging (DCB)
standards for lossless Ethernet.
Building a high-performance, highly available IP storage network (IP-SAN) can be done several
ways. In general, consider enterprise-class switch infrastructure (described in “Minimum
recommended switch capabilities for a P6300/P6500 EVA-based IP-SAN” (page 7)) to minimize
packet discard, packet loss, and unpredictable performance. For the 10 GbE IP-SAN, consider
implementing it on a lossless Ethernet network, utilizing DCB switches. Within a 10 GbE based
data center, consider implementing the FCoE protocol.
General IP-SAN recommendations
•For Microsoft Windows Server environments, implement MPIO and HP DSM for NIC
fault-tolerance and superior performance.
•For other operating systems, where supported, implement NIC bonding in the host software
for NIC fault-tolerance and performance.
•Implement a separate subnet or VLAN for the IP storage network for dedicated bandwidth.
•Implement separate FCoE and iSCSI VLANs.
•Implement a fault-tolerant switch environment as a separate VLAN through a core switch
infrastructure or multiple redundant switches.
•Set the individual 1 and 10 gigabit ports connected to the storage nodes and servers at auto
negotiate full-duplex at both the switch and host/node port level.
•Implement switches with full-duplex non-blocking mesh backplanes with sufficient port buffer
cache (at least 512 KB per port).
•Implement flow control on the storage network switch infrastructure. Flow control can
dramatically impact performance in a 10 GbE environment. This is especially true in mixed
1 GbE and 10 GbE environments. When a network port becomes saturated, excess frames
may be dropped because the port cannot physically handle the amount of traffic received.
This causes the packets to be resent, and the overhead of resending the packets can decrease
performance.
For example, if a 10 GbE link sends data at 10 Gb/s to a single 1 GbE link, flow control
eliminates any problems by controlling the speed at which data is sent to the port. Best practices
dictate that flow control always be enabled and it must be enabled on both the switches and
6 Reviewing and confirming your plans

the NICs/iSCSI initiators to function properly. If it is not enabled everywhere, the network
defaults to the lowest common denominator, which is flow control disabled.
•(Optional) Implement jumbo frames support on the switch, the 1 GbE iSCSI modules, and the
10 GbE iSCSI/FCoE modules when iSCSI is configured, and all servers connected to the
IP-SAN. Consider using 4K jumbo frames instead of 9K jumbo frames for better streaming
performance.
NOTE: FCoE requires jumbo frames and is the default configuration of a converged network
adapter, converged network switch, and the 10 GbE iSCSI/FCoE modules when FCoE is configured.
Recommended switch infrastructure for an IP-SAN
HP does not recommend a particular IP switch. However, there are minimum switch capabilities
that make building a high-performance, fault-tolerant storage network a relatively easy and cost
effective task. As a general rule, any enterprise-class managed switch typically has the capabilities
most IP-SAN customers require. Table 1 (page 7) summarizes the minimum recommended switch
capabilities for a P6000-based IP-SAN.
For FCoE, HP recommends converged network switches. For more information about these switches,
go to:
http://h18006.www1.hp.com/storage/networking/index.html
These switches are also referenced in the HP SAN Design Reference Guide, which is also available
through this website. For additional FCoE configuration details, see the HP Fibre Channel Over
Ethernet Application Note (part number: AA-RWQ5H-TE).
Table 1 Minimum recommended switch capabilities for a P6300/P6500 EVA-based IP-SAN
DescriptionSwitch capability
The iSCSI module option of the P6000 comes equipped with eight copper gigabit Ethernet
ports (802.3ab). To take advantage of full duplex gigabit capabilities, the cabling
infrastructure must be Cat5e or Cat6 cabling. The iSCSI/FCoE module option of the
P6000 comes equipped with four SFP+ 10 gigabit ports, and you configure either SFP+
optical or SFP+ copper connectivity. Server connections and switch interconnects can
be done with SFP+ fiber and SFP+ copper cabling, in addition to Cat5e or Cat6 cabling,
depending on IP switch capabilities.
1 and 10 gigabit Ethernet
support
In order to achieve maximum performance on the IP-SAN it is important to select a switch
that has a fully subscribed backplane. This means that the backplane is capable of
supporting all ports at full-duplex mode. For instance, if the switch has 24 gigabit ports,
it will have to have a 48 gigabit backplane to support full duplex gigabit communications.
Fully subscribed
non-blocking backplanes
For optimal switch performance, HP recommends that the switch have at least 512 KB
of buffer cache per port. Consult your switch manufacturer specifications for the total
buffer cache. For example, if the switch has 48 gigabit ports, this recommendation is to
have at least 24 MB of buffer cache dedicated to those ports. If the switch aggregates
cache among a group of ports (for example, 1 MB of cache per 8 ports), space your
used ports appropriately to avoid cache oversubscription.
Adequate per port buffer
cache
Plan your storage configuration 7

Table 1 Minimum recommended switch capabilities for a P6300/P6500 EVA-based IP-SAN
(continued)
DescriptionSwitch capability
IP storage networks are unique in the amount of sustained bandwidth that is required to
maintain adequate performance levels under heavy workloads. Gigabit Ethernet flow
control (802.3x) technology should be enabled on the switch to eliminate receive and/or
transmit buffer cache pressure.
NOTE: Some switch manufacturers do not recommend configuring flow control when
using jumbo frames, or jumbo frames with flow control. Consult the switch manufacturer
documentation for guidance on this issue. HP recommends implementing flow control
over jumbo frames for optimal performance. Flow control is required when using the HP
DSM and MPIO.
Flow control support
All ports on the switch, servers, and storage nodes should be configured to auto-negotiate
duplex and speed settings. Although most switches and NICs will auto negotiate the
optimal performance setting, if a single port on the IP storage network negotiates a
sub-optimal (100 megabit or less and/or half-duplex) setting, the entire SAN performance
can be impacted negatively. Check each switch and NIC port to make sure the
auto-negotiation is resolved to be 1000 Mb/s or 10 Gb/s with full-duplex.
Individual port speed and
duplex setting
Link aggregation and/or trunking support is important to enable when building a high
performance fault-tolerant IP storage network. HP recommends implementing link
aggregation and/or trunking technology when doing switch-to-switch trunking, server
NIC load balancing, and server NIC link aggregation (802.3ad).
Link aggregation/trunking
support
Implementing a separate subnet or VLAN for the IP storage network is a best IP-SAN
practice. If implementing VLAN technology within the switch infrastructure, you typically
need to enable VLAN tagging (802.1q) and/or VLAN trunking (802.1q or InterSwitch
Link [ISL] from Cisco). Consult your switch manufacturer configuration guidelines when
enabling VLAN support.
VLAN support
In order to build a fault-tolerant IP storage network, multiple switches are typically
connected into a single Layer 2 (OSI Model) broadcast domain using multiple
interconnects. In order to avoid Layer 2 loops, the Spanning Tree protocol (802.1D) or
Rapid Spanning Tree protocol (802.1w) must be implemented in the switch infrastructure.
Failing to do so can cause numerous issues on the IP storage networks, including
performance degradation or even traffic storms. HP recommends implementing rapid
spanning tree if the switch infrastructure supports it for faster spanning tree convergence.
If the switch is capable, consider disabling spanning tree on the server switch ports so
that they do not participate in the spanning tree convergence protocol timings.
NOTE: FCoE should be configured with spanning-tree disabled at the first level server
edge switch.
Spanning tree/rapid
spanning tree
Sequential read and write, or streaming workloads, can benefit from a larger maximum
frame size than 1514 bytes. The iSCSI and iSCSI/FCoE modules are capable of frame
sizes up to 9 Kbytes. Better performance is realized when the NICs and iSCSI initiators
are configured for 4 Kbyte (maximum frame size of 4088 bytes) jumbo frames. Jumbo
frames must be enabled on the switch, the iSCSI and iSCSI/FCoE modules, and all
servers connected to the IP-SAN. Typically, jumbo frames are enabled globally on the
switch or per VLAN and on a per port basis on the server.
NOTE: Some switch manufacturers do not recommend configuring jumbo frames when
using flow control, or flow control with jumbo frames. Consult the switch manufacturer
documentation for guidance on this issue. HP recommends implementing flow control
over jumbo frames for optimal performance.
Jumbo frame support
8 Reviewing and confirming your plans

Key configuration notes:
•Switch infrastructure: Use dual redundant 1 or 10 gigabit switches trunked together for
bandwidth and fault-tolerance.
•iSCSI and iSCSI/FCoE module connectivity: Ensure at least one port from each module is
connected to each switch.
•Host server connectivity: Use dual NICs connected to the IP storage network with a single port
connected to each switch. For Windows 2003/2008, use HP DSM for MPIO for multiple NIC
support.
Network latency
High network latency can be the primary cause of slow I/O performance or iSCSI drive disconnects.
It is important to keep network latency (for example, ping response time measurement) on the
IP-SAN subnet below two milliseconds. Many factors can contribute to increasing network latency;
the most common being congestion, distance, and router hops. Configuring the IP-SAN on a single
IP subnet with Layer-2 switching can help lower network latency.
Network bandwidth
Network bandwidth required for an IP-SAN depends on the server applications, maintenance
utilities, and backup/recovery processes. Most I/O intensive applications, like Microsoft Exchange
and SQL Server, do not consume much network bandwidth but are more sensitive to network
latency issues. Bandwidth becomes more important during maintenance operations, like
backup/recovery. Any sequential read/write stream could consume significant bandwidth.
NOTE: Storage data transfer rates are typically measured in bytes, while network data transfer
rates are measured in bits. A 1 Gb/sec network connection can transfer a maximum of 120–130
MB/sec. Microsoft Windows provides performance monitor counters that can help determine the
data-path bandwidth requirements. Disk bytes/sec is the rate bytes are transferred to or from the
disk during write or read operations.
The P6300/P6500 EVA is available as a single protocol (FC) or as a multi-protocol (FC/iSCSI or
FC/iSCSI/FCoE) array. The iSCSI protocol transport is supported at 1 GbE and 10 GbE rates
through the 1 GbE iSCSI modules or 10 GbE iSCSI/FCoE modules. Figure 1 (page 10) illustrates
the normal multi-protocol data and management connectivity. HP P6000 Command View requires
Ethernet access to the 1 GbE iSCSI modules and can also use array-based management with the
management module or in-band host-based management with the FC, iSCSI, or FCoE connectivity.
Plan your storage configuration 9

Figure 1 P6300/P6500 multi-protocol management and data connectivity example
Figure 2 (page 10) illustrates HP P6000 Command View management of the P6300/P6500
through the iSCSI connectivity and the 1 GbE iSCSI modules through IP connectivity. When LUN
0 from each controller is presented through the iSCSI or FCoE connectivity, HP P6000 Command
View can manage the P6300/P6500 EVA controllers.
Figure 2 P6300/P6500 iSCSI and Ethernet management and data connectivity example
Figure 3 (page 11) illustrates a simplified multi-protocol data and management configuration.
10 Reviewing and confirming your plans

Figure 3 P6300/P6500 FCoE management and data connectivity example
NOTE: For the minimum supported configuration and other configuration information, see the
QuickSpecs at:
http://h18006.www1.hp.com/storage/disk_storage/eva_diskarrays/index.html
Total number of iSCSI and iSCSI/FCoE initiators
For one P6300/P6500 EVA controller, and assuming a redundant configuration, HP P6000
Command View supports 256 initiators and 255 LUNs, plus LUN 0. On the iSCSI/FCoE modules,
HP P6000 Command View supports 1024 initiators, 1024 LUNs, and 256 LUNs per virtual port
group (VPG).
HP P6000 Command View supports configuring the iSCSI and iSCSI/FCoE modules for redundant
operation. Although each module can be configured separately, an expert level of knowledge is
required to manage the two LUN presentation levels and to use the CLI of the iSCSI and iSCSI/FCoE
modules. HP does not recommend separate module configurations.
When configuring the iSCSI initiators, create path logins to the .1 and .2 iSCSI target IQNs to
ensure redundant iSCSI controller path connectivity. For a simplified network configuration,
Figure 4 (page 12) illustrates four target paths being displayed for login for the iSCSI module pair.
Figure 5 (page 12) shows sixteen target paths (four x four VPGs) being displayed for login for the
iSCSI/FCoE module pair.
Plan your storage configuration 11

Figure 4 iSCSI initiator's view of the P6300/P6500 1 GbE iSCSI module's target paths
Figure 5 iSCSI initiator's view of P6300/P6500 10 GbE iSCSI/FCoE module's target paths
The FCoE initiators complete automated logins on all discovered paths, so verify that FCoE
connectivity is established to both 10 GbE iSCSI/FCoE modules prior to presenting LUNs using
HP P6000 Command View.
Number of paths required per initiator
After establishing the number of initiators, determine how many paths are required by each initiator.
The number of connections per iSCSI controller is finite, and every initiator login constitutes a
connection to the iSCSI modules or iSCSI/FCoE modules. In a multipath environment, HP
recommends a minimum of one connection per module; high-performance applications may require
full path connectivity to each iSCSI module.
12 Reviewing and confirming your plans

Using Internet Storage Name Service (iSNS)
The 1 GbE iSCSI modules present two iSCSI targets (P6300/P6500 EVA controller 1 and controller
2), for a total of four targets to the pair of iSCSI or iSCSI/FCoE controllers. Each initiator, therefore,
discovers two or four FC targets depending on the IP Ethernet configuration. The 10 GbE iSCSI/FCoE
modules present one iSCSI target for each virtual port group (VPG) for a total of four. Each iSCSI
initiator, therefore, discovers four times the number of FC targets. HP recommends that you use
iSNS to present only the required iSCSI targets to the initiator.
Using iSCSI ports
When configuring the iSCSI module and iSCSI/FCoE module, HP recommends that you use all
eight 1 GbE or all four 10 GbE ports for higher average performance and maximum initiator
connectivity. When multiple initiators are configured, ensure that logins are spread across the
target ports on either the iSCSI modules or iSCSI/FCoE modules.
Security
When configuring a secure IP storage network based on iSCSI, the Challenge Handshake
Authentication Protocol (CHAP) is configurable on the iSCSI modules and iSCSI/FCoE modules.
CHAP is a protocol used to authenticate the peer of a connection. It is based on the peer sharing
a password or secret. Both single-direction (target) and mutual (bi-directional) CHAP are supported.
The target iSCSI modules or iSCSI/FCoE modules can have a unique password for the one-way
CHAP option. The iSCSI initiator can have a unique password for the bi-directional CHAP option
with the target iSCSI modules or the iSCSI/FCoE modules.
NOTE: IPsec is not a supported protocol with iSCSI connectivity of the target iSCSI or iSCSI/FCoE
modules.
To enable single direction CHAP for the discovered iSCSI initiator entry of the iSCSI or iSCSI/FCoE
modules:
Plan your storage configuration 13

1. Run the set chap command in the iSCSI CLI to determine if the iSCSI initiator IQN is listed.
MEZ75 (admin) #> set chap
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Index iSCSI Name
----- ----------
0 iqn.2004-09.com.hp:fcgw.mez75.1
1 iqn.2004-09.com.hp:fcgw.mez75.1
2 iqn.2004-09.com.hp:fcgw.mez75.1.01.5001438004c68968
3 iqn.2004-09.com.hp:fcgw.mez75.1.01.5001438004c6896c
4 iqn.2004-09.com.hp:fcgw.mez75.1.02.5001438004c68968
5 iqn.2004-09.com.hp:fcgw.mez75.1.03.5001438004c68968
6 iqn.2004-09.com.hp:fcgw.mez75.1.04.5001438004c68968
7 iqn.2004-09.com.hp:fcgw.mez75.1.02.5001438004c6896c
8 iqn.2004-09.com.hp:fcgw.mez75.1.03.5001438004c6896c
9 iqn.2004-09.com.hp:fcgw.mez75.1.04.5001438004c6896c
10 iqn.1991-05.com.microsoft.perf2.sanbox.com
Please select a iSCSI node from the list above ('q' to quit): 10
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
CHAP (0=Enable, 1=Disable) [Disabled] 0
CHAP Secret (Max = 100 characters) [ ] ************
All attribute values that have been changed will now be saved.
If the iSCSI initiator IQN is listed, enter the index number of the initiator. Then, enter 0 (zero)
to enable CHAP, and enter the CHAP secret as shown in the CLI example.
2. If the iSCSI initiator IQN is not listed, you can use either the CLI or HP P6000 Command View
to add the iSCSI initiator IQN:
•CLI: Use the initiator add command.
MEZ75 (admin) #> initiator add
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Initiator Protocol (0=ISCSI, 1=FC, 2=FCOE) [ISCSI ] 0
Only valid iSCSI name characters will be accepted. Valid characters include
lower-case alphabetical (a-z), numerical (0-9), colon, hyphen, and period.
iSCSI Initiator Name (Max = 223 characters) [ ] iqn.1991-05.com.microsoft.perf2.sanbox.com
OS Type (0=Windows, 1=Linux, 2=Solaris,
3=OpenVMS, 4=VMWare, 5=Mac OS X,
6=Windows2008, 7=HP-UX, 8=AIX,
9=Other) [Windows ] 6
All attribute values that have been changed will now be saved.
•HP P6000 Command View: Add the iSCSI initiator IQN using the Add Host function
(select Hosts in the Navigation pane, and then select Add Host).
To enable CHAP for the Microsoft iSCSI initiator running on the iSCSI server:
14 Reviewing and confirming your plans

1. Click the Discovery tab and when manually discovering iSCSI target portals:
a. Click Add under Target Portals.
b. Enter the IP address of the iSCSI port of the 1 GbE iSCSI Modules or the 10GbE
iSCSI/FCoE modules.
c. Click Advanced.
d. Select the CHAP Login Information check box.
e. Enter the CHAP secret for the 1 GbE iSCSI modules or the 10GbE iSCSI/FCoE modules
discovered iSCSI initiator in the Target Secret box, for example, CHAPsecret01.
f. Click OK and the initiator completes target discovery.
2. Click Targets and select the appropriate target for login.
3. Click Log On and then click Advanced.
4. Select the CHAP Login Information check box.
5. Enter the CHAP secret for the discovered iSCSI initiator of the iSCSI or iSCSI/FCoE modules
in the Target Secret box.
6. Click OK twice.
To enable bi-directional CHAP for the iSCSI initiator entries of the iSCSI or iSCSI/FCoE modules:
1. Run the set chap CLI command to determine if the iSCSI initiator IQN is listed.
MEZ75 (admin) #> set chap
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Index iSCSI Name
----- ----------
0 iqn.2004-09.com.hp:fcgw.mez75.1
1 iqn.2004-09.com.hp:fcgw.mez75.1
2 iqn.2004-09.com.hp:fcgw.mez75.1.01.5001438004c68968
3 iqn.2004-09.com.hp:fcgw.mez75.1.01.5001438004c6896c
4 iqn.2004-09.com.hp:fcgw.mez75.1.02.5001438004c68968
5 iqn.2004-09.com.hp:fcgw.mez75.1.03.5001438004c68968
6 iqn.2004-09.com.hp:fcgw.mez75.1.04.5001438004c68968
7 iqn.2004-09.com.hp:fcgw.mez75.1.02.5001438004c6896c
8 iqn.2004-09.com.hp:fcgw.mez75.1.03.5001438004c6896c
9 iqn.2004-09.com.hp:fcgw.mez75.1.04.5001438004c6896c
10 iqn.1991-05.com.microsoft.perf2.sanbox.com
Please select a iSCSI node from the list above ('q' to quit): 10
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
CHAP (0=Enable, 1=Disable) [Disabled] 0
CHAP Secret (Max = 100 characters) [ ] ************
All attribute values that have been changed will now be saved.
Plan your storage configuration 15

2. Perform one of the following, depending on whether the IQN was listed.
a. If the iSCSI initiator IQN is listed, enter the index number of the initiator. Then, enter 0
(zero) to enable CHAP, and enter the CHAP secret as shown in the CLI example.
b. If the iSCSI initiator IQN is not listed, you can use either the CLI or HP P6000 Command
View to add the iSCSI initiator IQN.
•Using the initiator add command with the CLI:
MEZ75 (admin) #> initiator add
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Initiator Protocol (0=ISCSI, 1=FC, 2=FCOE) [ISCSI ] 0
Only valid iSCSI name characters will be accepted. Valid characters include
lower-case alphabetical (a-z), numerical (0-9), colon, hyphen, and period.
iSCSI Initiator Name (Max = 223 characters) [ ] iqn.1991-05.com.microsoft.perf2.sanbox.com
OS Type (0=Windows, 1=Linux, 2=Solaris,
3=OpenVMS, 4=VMWare, 5=Mac OS X,
6=Windows2008, 7=HP-UX, 8=AIX,
9=Other) [Windows ] 6
All attribute values that have been changed will now be saved.
•Using HP P6000 Command View: Add the initiator IQN using the Add Host function
(select Hosts in the Navigation pane, and then select Add Host).
3. Enable CHAP for the iSCSI or iSCSI/FCoE port using HP P6000 Command View or the CLI.
•If using HP P6000 Command View:
Choose the appropriate iSCSI or iSCSI/FCoE controller, select the IP Ports tab, and
then select the appropriate IP port.
a.
b. Under Security, select Enabled in CHAP Status, then type in the CHAP secret. For
example: hpstorageworks
c. Click the Save Changes tab to save the changes.
•If using the CLI to enable CHAP for the iSCSI or iSCSI/FCoE port:
a. Enter the set chap command.
b. Select the appropriate Portal IQN name index to which the initiator will log in.
c. Select 0to enable CHAP.
d. Enter a CHAP secret. For example: hpstorageworks.
4. Enable CHAP for the iSCSI or iSCSI/FCoE presented target. To enable CHAP for the Discovered
iSCSI Initiator entry using the CLI:
a. Enter the set chap command.
b. Select the presented target to which the initiator will log in.
c. Enable CHAP and enter a CHAP secret. For example: hpstorageworks.
16 Reviewing and confirming your plans

5. Enable CHAP for the Microsoft iSCSI initiator running on the iSCSI server:
a. Click the General tab.
b. Click Secret in the middle of the screen.
c. Click Reset.
d. Enter the iSCSI or iSCSI/FCoE presented target CHAP secret. For example: hpstorageworks
e. Click OK.
f. Click the Discovery tab and when manually discovering iSCSI target portals:
i. Click Add under Target Portals.
ii. Enter the IP address of the iSCSI port of the 1 GbE iSCSI modules or the 10GbE
iSCSI/FCoE modules.
iii. Click Advanced.
iv. Select the CHAP Login Information check box.
v. Enter the CHAP secret for the 1 GbE iSCSI modules or the 10GbE iSCSI/FCoE
modules discovered iSCSI initiator in the Target Secret box. For example,
CHAPsecret01.
vi. Select the Mutual Authentication check box.
vii. Click OK twice and the initiator completes target discovery.
g. Click Targets and select the appropriate target for login.
h. Click Log On and then click Advanced.
i. Select the CHAP Login Information check box.
j. Enter the CHAP secret for the discovered iSCSI initiator of the iSCSI or iSCSI/FCoE
modules in the Target Secret box. For example, CHAPsecret01.
k. Select the Mutual Authentication check box.
l. Click OK twice, and the initiator completes normal login.
System and performance expectations
To help determine the best way to configure your storage, rank the following three storage
characteristics in order of importance:
•Fault tolerance (high availability)
•I/O performance
•Storage efficiency
With your priorities established, you can determine which striping method and RAID level to use.
As highlighted in the following section, some configuration methods offer greater fault tolerance,
while other configuration methods offer better I/O performance or storage efficiency.
RAID levels
Vraid is the HP term for the implementation of RAID (Redundant Array of Independent Disks) storage
on EVAs. Vraid is also referred to as redundancy in HP management software. Virtual disks with
HP Vraid use three key RAID methods: data striping, data mirroring, and parity error checking.
Unlike traditional RAID, all HP Vraid levels distribute data across all available physical disks.
Data striping improves speed by performing virtual disk I/O with an entire group of physical disks
at the same time. Mirroring provides data redundancy by storing data and a copy of the data.
Parity also provides data redundancy by storing data and the calculated parity for each stripe of
data. If a subset of the data on a physical disk becomes corrupt or the entire physical disk fails,
the data can be automatically recovered from redundancy so that data loss does not occur.
The EVA has four Vraid types: Vraid0, Vraid1, Vraid5, and Vraid6. Each Vraid type provides
unique I/O speed and has a different level of data redundancy, which directly effects the amount
of physical space used. Once a virtual disk is created, the Vraid type or level cannot be changed.
Plan your storage configuration 17

See Table 2 (page 18) for a comparison of the different RAID levels.
Table 2 RAID level comparison
RAID methodData redundancyBest practicesSummary
StripingNoneIMPORTANT: HP does not
recommend using Vraid0 for virtual
disks when high availability is
required. Consider Vraid0 only for
noncritical storage. Vraid0 virtual
disks provide the best performance
for applications that use random I/O.
Vraid0 is optimized for I/O
speed and efficient use of
physical disk capacity, but
provides no data redundancy.
Vraid0
Striping and
mirroring
HighIn general, Vraid1 virtual disks
provide better performance
characteristics over a wider range of
application workloads than Vraid5.
Vraid1 is optimized for data
redundancy and I/O speed,
but uses the most physical disk
space.
IMPORTANT: Vraid1 uses
about 100% more physical
disk space than Vraid0.
Vraid1
Striping and
parity
MediumVraid5 virtual disks provide as good
or better performance than Vraid1
for applications that use sequential
writes. Vraid5 has much lower
random write performance in
comparison to Vraid1, but has much
higher capacity efficiency.
Vraid5 provides a balance of
data redundancy, I/O speed,
and efficient use of physical
disk space. Vraid5 uses about
20% more physical disk space
than Vraid0.
Vraid5
Striping and
double parity
Very highPerformance characteristics of Vraid6
for random and sequential write
workloads will be slightly slower than
Vraid5. Vraid6 provides the highest
level of redundancy protection of all
the Vraid types.
IMPORTANT: If a disk group includes
large physical disks (for example, 1
TB or larger), HP recommends using
Vraid6 for the virtual disk.
Vraid6 is similar to Vraid5, but
provides a higher level of
redundancy by storing two
parity blocks per stripe instead
of one. Vraid6 uses 33% more
physical disk space than
Vraid0.
Vraid6
NOTE: For best practice information, see the HP P6300/P6500 Enterprise Virtual Array Systems
configuration best practices white paper available at:
http://h18006.www1.hp.com/storage/arraywhitepapers.html?jumpid=reg_R1002_USEN
HP P6000 Command View implementation
HP P6000 Command View can be implemented in two ways:
•Server-based management—HP P6000 Command View is installed on a management server
connected to the EVA, providing management of multiple storage systems. All components of
the software suite (HP P6000 Command View, HP Command View EVAPerf, HP Storage
System Scripting Utility, SMI-S EVA) are installed. Server-based management is applicable to
all EVA models.
•Array-based management—The P6300/P6500 EVAs are shipped with HP P6000 Command
View pre-installed on the management module within the controller enclosure. Only one
component of the software suite (HP P6000 Command View) is installed.
18 Reviewing and confirming your plans

2 Preparing your site
Overview
Preparing your site means providing:
•Physical rack space for the equipment
•AC power for the array
•Proper ventilation and temperature conditions
•LAN or Fibre Channel cables to attach the array hardware to your network
To ensure continuous, safe, and reliable operation of your equipment, place your system in an
approved environment.
Consider using the HP Enterprise Configurator (eCO) to help plan and configure racks and
rack-mountable devices. The eCO is available on the HP website:
http://h30099.www3.hp.com/configurator
Click Configure under Disk products.
Provide adequate structural support for the floor
Calculate the total weight of your equipment and verify that your site can support the weight.
Provide adequate clearance space and ventilation
Be sure to provide adequate clearance around the front and back of the racks. Provide at least
25 inches (63.5 cm) in the front of the rack to allow the doors to open fully and provide at least
30 inches (76.2 cm) in the rear of the rack to allow for servicing and airflow.
If there are unused spaces in your rack, attach blanking panels across those empty spaces to force
the airflow through the components instead of through the open spaces.
Provide adequate and redundant sources of power
Make sure that you have two high-line power feeds installed near your computer. These two power
sources usually come from the same external power grid, but occasionally may originate from
different grids or even entirely different sources.
For protection against a power-source failure, obtain and include two uninterruptible power supplies
in your installation.
For power consumption specifications, see the QuickSpecs document at:
http://www.hp.com/go/P6000
Remove product from packaging
1. Remove product from boxes.
2. Verify that contents match your expectations and site requirements.
•P6300 EVA controller enclosure should contain:
One 2U controller enclosure with two HSV340 controller modules, two power supply
modules, two fan modules, and two battery modules installed.
◦
◦Rack mounting hardware
◦Two 2.0 meter SAS cables
◦Two power cords
Overview 19

◦Installation documentation
◦XCS controller software recovery CD
•P6500 EVA controller enclosure should contain:
One 2U controller enclosure with two HSV360 controller modules, two power supply
modules, two fan modules, and two battery modules installed.
◦
◦Rack mounting hardware
◦Two 2.0 meter SAS Y-cables
◦Two power cords
◦Installation documentation
◦XCS controller software recovery CD
•Each FC disk enclosure should contain:
◦A minimum of one 2U M6612 or M6625 disk enclosure, two power supply modules,
two fan modules, and two battery modules.
◦Rack mounting hardware kit
◦Two 0.7 meter SAS cables
◦Two power cords
NOTE: Controllers are shipped with Small Form Factor Pluggable (SFP) transceiver
modules on all FC ports. If you ordered the AF092A rack, HP recommends that you use
the 1.37 meter (minimum length) power cords.
3. Inspect for damage.
If damage is present, contact your local HP representative.
20 Preparing your site