Home » HP Manuals » Storage Devices » HP P6000 » Manual Viewer

HP P6000 HP P6300/P6500 Enterprise Virtual Array User Guide (593079-001, June - Page 57

Verifying virtual disks from the host, OpenVMS, Updating the AlphaServer console code

Add to My Manuals
Save this manual to your list of manuals

Page 57 highlights

This line identifies the location of the binary RPM. 4. Copy the binary RPM to the production servers and install it using the following command: # rpm -ivh hp_qla2x00-version-revision.architecture.rpm Verifying virtual disks from the host To verify the virtual disks, first verify that the LUN is recognized and then verify that the host can access the virtual disks. • To ensure that the LUN is recognized after a virtual disk is presented to the host, do one of the following: ◦ Reboot the host. ◦ Enter the /opt/hp/hp_fibreutils/hp_rescan -a command. • To verify that the host can access the virtual disks, enter the # more /proc/scsi/scsi command. The output lists all SCSI devices detected by the server. An P6300/P6500 EVAs LUN entry looks similar to the following: Host: scsi3 Channel: 00 ID: 00 Lun: 01 Vendor: HP Model: HSV340 Rev: Type: Direct-Access ANSI SCSI revision: 02 OpenVMS Updating the AlphaServer console code, Integrity Server console code, and Fibre Channel FCA firmware The firmware update procedure varies for the different server types. To update firmware, follow the procedure described in the Installation instructions that accompany the firmware images. Verifying the Fibre Channel adapter software installation A supported FCA should already be installed in the host server. The procedure to verify that the console recognizes the installed FCA varies for the different server types. Follow the procedure described in the Installation instructions that accompany the firmware images. Console LUN ID and OS unit ID HP P6000 Command View software contains a box for the Console LUN ID on the Initialized Storage System Properties window. It is important that you set the Console LUN ID to a number other than zero (0). If the Console LUN ID is not set or is set to zero (0), the OpenVMS host will not recognize the controller pair. The Console LUN ID for a controller pair must be unique within the SAN. Table 11 (page 58) shows an example of the Console LUN ID. You can set the OS unit ID on the Virtual Disk Properties window. The default setting is 0, which disables the ID field. To enable the ID field, you must specify a value between 1 and 32767, OpenVMS 57

Section	Page
HP P6300/P6500 Enterprise Virtual Array User Guide	1
Contents	3
1 P6300/P6500 EVA hardware	13
SAS disk enclosures	13
Small Form Factor disk enclosure chassis	13
Front view	13
Rear view	13
Drive bay numbering	13
Large Form Factor disk enclosure chassis	14
Front view	14
Rear view	14
Drive bay numbering	14
Disk drives	15
Disk drive LEDs	15
Disk drive blanks	15
Front status and UID module	16
Front UID module LEDs	16
Unit identification (UID) button	17
Power supply module	17
Power supply LED	17
Fan module	17
Fan module LED	18
I/O module	18
I/O module LEDs	19
Rear power and UID module	19
Rear power and UID module LEDs	20
Unit identification (UID) button	21
Power on/standby button	21
SAS cables	21
Controller enclosure	21
Controller status indicators	24
Controller status LEDs	25
Power supply module	26
Battery module	27
Fan module	27
Management module	28
HSV controller cabling	28
Storage system racks	29
Rack configurations	29
Power distribution units	30
PDU 1	30
PDU 2	30
PDMs	31
Rack AC power distribution	31
Moving and stabilizing a rack	32
2 P6300/P6500 EVA operation	35
Best practices	35
Operating tips and information	35
Reserving adequate free space	35
Using SAS-midline disk drives	35
Failback preference setting for HSV controllers	35
Changing virtual disk failover/failback setting	37
Implicit LUN transition	37
Recovery CD	38
Adding disk drives to the storage system	38
Handling fiber optic cables	38
Storage system shutdown and startup	39
Powering on disk enclosures	39
Powering off disk enclosures	40
Shutting down the storage system from HP P6000 Command View	40
Shutting down the storage system from the array controller	40
Starting the storage system	41
Restarting the iSCSI or iSCSI/FCoE module	42
Using the management module	42
Connecting to the management module	42
Connecting through a public network	43
Connecting through a private network	44
Accessing HP P6000 Command View on the management module	44
Changing the host port default operating mode	44
Saving storage system configuration data	45
Saving or restoring the iSCSI or iSCSI/FCoE module configuration	47
3 Configuring application servers	49
Overview	49
Clustering	49
Multipathing	49
Installing Fibre Channel adapters	49
Testing connections to the array	50
Adding hosts	50
Creating and presenting virtual disks	51
Verifying virtual disk access from the host	51
Configuring virtual disks from the host	51
HP-UX	51
Scanning the bus	51
Creating volume groups on a virtual disk using vgcreate	52
IBM AIX	53
Accessing IBM AIX utilities	53
Adding hosts	53
Creating and presenting virtual disks	53
Verifying virtual disks from the host	53
Linux	54
Driver failover mode	54
Installing a QLogic driver	54
Upgrading Linux components	55
Upgrading qla2x00 RPMs	55
Detecting third-party storage	55
Compiling the driver for multiple kernels	56
Uninstalling the Linux components	56
Using the source RPM	56
Verifying virtual disks from the host	57
OpenVMS	57
Updating the AlphaServer console code, Integrity Server console code, and Fibre Channel FCA firmware	57
Verifying the Fibre Channel adapter software installation	57
Console LUN ID and OS unit ID	57
Adding OpenVMS hosts	58
Scanning the bus	59
Configuring virtual disks from the OpenVMS host	60
Setting preferred paths	60
Oracle Solaris	60
Loading the operating system and software	60
Configuring FCAs with the Oracle SAN driver stack	60
Configuring Emulex FCAs with the lpfc driver	61
Configuring QLogic FCAs with the qla2300 driver	62
Fabric setup and zoning	64
Oracle StorEdge Traffic Manager (MPxIO)/Oracle Storage Multipathing	64
Configuring with Veritas Volume Manager	64
Configuring virtual disks from the host	66
Verifying virtual disks from the host	67
Labeling and partitioning the devices	68
VMware	69
Installing or upgrading VMware	69
Configuring the EVA with VMware host servers	69
Configuring an ESX server	70
Loading the FCA NVRAM	70
Setting the multipathing policy	70
Specifying DiskMaxLUN	71
Verifying connectivity	71
Verifying virtual disks from the host	72
4 Replacing array components	73
Customer self repair (CSR)	73
Parts-only warranty service	73
Best practices for replacing hardware components	73
Component replacement videos	73
Verifying component failure	73
Identifying the spare part	73
Replaceable parts	74
Replacing the failed component	76
Replacement instructions	76
5 iSCSI or iSCSI/FCoE configuration rules and guidelines	78
iSCSI or iSCSI/FCoE module rules and supported maximums	78
HP P6000 Command View and iSCSI or iSCSI/FCoE module management rules and guidelines	78
HP P6300/P6500 EVA storage system software	78
Fibre Channel over Ethernet switch and fabric support	78
Operating system and multipath software support	79
iSCSI initiator rules, guidelines, and support	80
General iSCSI initiator rules and guidelines	80
Apple Mac OS X iSCSI initiator rules and guidelines	80
Microsoft Windows iSCSI Initiator rules and guidelines	80
Linux iSCSI Initiator rules and guidelines	81
Solaris iSCSI Initiator rules and guidelines	81
VMware iSCSI Initiator rules and guidelines	82
Supported IP network adapters	82
IP network requirements	82
Set up the iSCSI Initiator	83
Windows	83
Multipathing	88
Installing the MPIO feature for Windows Server 2008	89
Installing the MPIO feature for Windows Server 2003	91
About Microsoft Windows Server 2003 scalable networking pack	92
SNP setup with HP NC 3xxx GbE multifunction adapter	92
iSCSI Initiator version 3.10 setup for Apple Mac OS X (single-path)	93
Set up the iSCSI Initiator for Apple Mac OS X	93
Storage setup for Apple Mac OS X	97
iSCSI Initiator setup for Linux	97
Installing and configuring the SUSE Linux Enterprise 10 iSCSI driver	97
Installing and configuring for Red Hat 5	99
Installing and configuring for Red Hat 4 and SUSE 9	100
Installing the initiator for Red Hat 3 and SUSE 8	100
Assigning device names	101
Target bindings	102
Mounting file systems	102
Unmounting file systems	102
Presenting EVA storage for Linux	103
Setting up the iSCSI Initiator for VMware	103
Configuring multipath with the Solaris 10 iSCSI Initiator	105
MPxIO overview	106
Preparing the host system	106
Enabling MPxIO for HP P6300/P6500 EVA	106
Edit the scsi_vhci.conf file	106
Edit the sgen.conf file	107
Create an sgen driver alias	108
Enable iSCSI target discovery	108
Modify target parameter MaxRecvDataSegLen	109
Monitor Multipath devices	110
Managing and Troubleshooting Solaris iSCSI Multipath devices	111
Configuring Microsoft MPIO iSCSI devices	111
Load balancing features of Microsoft MPIO for iSCSI	112
Microsoft MPIO with QLogic iSCSI HBA	113
Installing the QLogic iSCSI HBA	113
Installing the Microsoft iSCSI Initiator services and MPIO	113
Configuring the QLogic iSCSI HBA	113
Adding targets to QLogic iSCSI Initiator	114
Presenting LUNs to the QLogic iSCSI Initiator	115
Installing the HP MPIO Full Featured DSM for EVA	116
Microsoft Windows Cluster support	117
Microsoft Cluster Server for Windows 2003	117
Requirements	117
Setting the Persistent Reservation registry key	117
Microsoft Cluster Server for Windows 2008	118
Requirements	118
Setting up authentication	119
CHAP restrictions	119
Microsoft Initiator CHAP secret restrictions	119
Linux version	120
ATTO Macintosh Chap restrictions	120
Recommended CHAP policies	120
iSCSI session types	120
The iSCSI or iSCSI/FCoE controller CHAP modes	120
Enabling single–direction CHAP during discovery and normal session	120
Enabling CHAP for the iSCSI or iSCSI/FCoE module-discovered iSCSI initiator entry	122
Enable CHAP for the Microsoft iSCSI Initiator	123
Enable CHAP for the open-iscsi iSCSI Initiator	123
Enabling single–direction CHAP during discovery and bi-directional CHAP during normal session	124
Enabling bi-directional CHAP during discovery and single–direction CHAP during normal session	126
Enabling bi-directional CHAP during discovery and bi-directional CHAP during normal session	128
Enable CHAP for the open-iscsi iSCSI Initiator	130
6 Single path implementation	132
Installation requirements	132
Recommended mitigations	132
Supported configurations	133
General configuration components	133
Connecting a single path HBA server to a switch in a fabric zone	133
HP-UX configuration	135
Requirements	135
HBA configuration	135
Risks	135
Limitations	135
Windows Server 2003 (32-bit) and Windows Server 2008 (32–bit) configurations	136
Requirements	136
HBA configuration	136
Risks	136
Limitations	137
Windows Server 2003 (64-bit) and Windows Server 2008 (64–bit) configurations	137
Requirements	137
HBA configuration	137
Risks	138
Limitations	138
Oracle Solaris configuration	138
Requirements	138
HBA configuration	139
Risks	139
Limitations	139
OpenVMS configuration	140
Requirements	140
HBA configuration	140
Risks	141
Limitations	141
Xen configuration	141
Requirements	141
HBA configuration	141
Risks	142
Limitations	142
Linux (32-bit) configuration	142
Requirements	142
HBA configuration	143
Risks	143
Limitations	143
Linux (Itanium) configuration	143
Requirements	143
HBA configuration	144
Risks	144
Limitations	144
IBM AIX configuration	145
Requirements	145
HBA configuration	145
Risks	145
Limitations	145
VMware configuration	146
Requirements	146
HBA configuration	146
Risks	147
Limitations	147
Mac OS configuration	147
Failure scenarios	147
HP-UX	147
Windows Servers	148
Oracle Solaris	148
OpenVMS	149
Linux	149
IBM AIX	150
VMware	150
Mac OS	151
7 Troubleshooting	152
If the disk enclosure does not initialize	152
Diagnostic steps	152
Is the enclosure front fault LED amber?	152
Is the enclosure rear fault LED amber?	152
Is the power on/standby button LED amber?	153
Is the power supply LED amber?	153
Is the I/O module fault LED amber?	153
Is the fan LED amber?	154
Recognizing disk drive failure	154
Effects of a disk drive failure	154
Compromised fault tolerance	154
Factors to consider before replacing disk drives	154
Automatic data recovery (rebuild)	155
Time required for a rebuild	155
Failure of another drive during rebuild	156
Handling disk drive failures	156
iSCSI module diagnostics and troubleshooting	156
iSCSI and iSCSI/FCoE diagnostics	156
Locate the iSCSI or iSCSI/FCoE module	157
iSCSI or iSCSI/FCoE module's log data	158
iSCSI or iSCSI/FCoE module statistics	158
Troubleshoot using HP P6000 Command View	158
Issues and solutions	158
Issue: HP P6000 Command View does not discover the iSCSI or iSCSI/FCoE modules	158
Issue: Initiator cannot login to iSCSI or iSCSI/FCoE module target	159
Issue: Initiator logs in to iSCSI or iSCSI/FCoE controller target but EVA assigned LUNs are not appearing on the initiator	159
Issue: EVA presented virtual disk is not seen by the initiator	159
Issue: Windows initiators may display Reconnecting if NIC MTU changes after connection has logged in.	160
Issue: When communication between HP P6000 Command View and iSCSI or iSCSI/FCoE module is down, use following options:	160
HP P6000 Command View issues and solutions	161
8 Error messages	162
9 Support and other resources	179
Contacting HP	179
HP technical support	179
Subscription service	179
Documentation feedback	179
Related documentation	179
Documents	179
Websites	179
Typographic conventions	180
Customer self repair	180
Rack stability	181
A Regulatory compliance notices	182
Regulatory compliance identification numbers	182
Federal Communications Commission notice	182
FCC rating label	182
Class A equipment	182
Class B equipment	182
Declaration of Conformity for products marked with the FCC logo, United States only	183
Modification	183
Cables	183
Canadian notice (Avis Canadien)	183
Class A equipment	183
Class B equipment	183
European Union notice	183
Japanese notices	184
Japanese VCCI-A notice	184
Japanese VCCI-B notice	184
Japanese VCCI marking	184
Japanese power cord statement	184
Korean notices	184
Class A equipment	184
Class B equipment	185
Taiwanese notices	185
BSMI Class A notice	185
Taiwan battery recycle statement	185
Turkish recycling notice	185
Vietnamese Information Technology and Communications compliance marking	185
Laser compliance notices	186
English laser notice	186
Dutch laser notice	186
French laser notice	186
German laser notice	187
Italian laser notice	187
Japanese laser notice	187
Spanish laser notice	188
Recycling notices	188
English recycling notice	188
Bulgarian recycling notice	188
Czech recycling notice	188
Danish recycling notice	188
Dutch recycling notice	189
Estonian recycling notice	189
Finnish recycling notice	189
French recycling notice	189
German recycling notice	189
Greek recycling notice	189
Hungarian recycling notice	190
Italian recycling notice	190
Latvian recycling notice	190
Lithuanian recycling notice	190
Polish recycling notice	190
Portuguese recycling notice	191
Romanian recycling notice	191
Slovak recycling notice	191
Spanish recycling notice	191
Swedish recycling notice	191
Battery replacement notices	192
Dutch battery notice	192
French battery notice	192
German battery notice	193
Italian battery notice	193
Japanese battery notice	194
Spanish battery notice	194
B Non-standard rack specifications	195
Internal component envelope	195
EIA310-D standards	195
EVA cabinet measures and tolerances	195
Weights, dimensions and component CG measurements	196
Airflow and Recirculation	196
Component Airflow Requirements	196
Rack Airflow Requirements	196
Configuration Standards	196
UPS Selection	196
Shock and vibration specifications	197
C Command reference	199
Command syntax	199
Command line completion	199
Authority requirements	199
Commands	199
Admin	200
Beacon	200
Clear	200
Date	201
Exit	201
FRU	202
Help	202
History	204
Image	204
Initiator	205
Logout	207
Lunmask	207
Passwd	210
Ping	211
Quit	212
Reboot	212
Reset	212
Save	213
Set	213
Set alias	214
Set CHAP	215
Set FC	215
Set features	216
Set iSCSI	217
Set iSNS	218
Set Mgmt	218
Set NTP	219
Set properties	219
Set SNMP	220
Set system	221
Set VPGroups	221
Show	222
Show CHAP	224
Show FC	224
Show features	226
Show initiators	226
Show initiators LUN mask	228
Show iSCSI	229
Show iSNS	231
Show logs	231
Show LUNinfo	232
Show LUNs	233
Show lunmask	234
Show memory	234
Show mgmt	235
Show NTP	235
Show perf	236
Show presented targets	237
Show properties	240
Show SNMP	241
Show stats	241
Show system	243
Show targets	244
Show VPGroups	244
Shutdown	245
Target	245
Traceroute	246
D Using the iSCSI CLI	247
Logging on to an iSCSI or iSCSI/FCoE module	247
Understanding the guest account	247
Working with iSCSI or iSCSI/FCoE module configurations	248
Modifying a configuration	249
Saving and restoring iSCSI or iSCSI/FCoE controller configurations	249
Restoring iSCSI or iSCSI/FCoE module configuration and persistent data	250
E Simple Network Management Protocol	251
SNMP parameters	251
SNMP trap configuration parameters	251
Management Information Base	252
Network port table	252
FC port table	254
Initiator object table	255
LUN table	257
VP group table	259
Sensor table	260
Notifications	261
System information objects	262
Notification objects	263
Agent startup notification	263
Agent shutdown notification	263
Network port down notification	263
FC port down notification	263
Target device discovery	264
Target presentation (mapping)	264
VP group notification	264
Sensor notification	265
Generic notification	265
F iSCSI and iSCSI/FCoE module log messages	266
Glossary	280

Match case Limit results 1 per page

This line identifies the location of the binary RPM.

Copy the binary RPM to the production servers and install it using the following command:

# rpm -ivh hp_qla2x00-

version-revision.architecture

.rpm

Verifying virtual disks from the host

To verify the virtual disks, first verify that the LUN is recognized and then verify that the host can

access the virtual disks.

•

To ensure that the LUN is recognized after a virtual disk is presented to the host, do one of

the following:

◦

Reboot the host.

◦

Enter the

/opt/hp/hp_fibreutils/hp_rescan -a

command.

•

To verify that the host can access the virtual disks, enter the

# more /proc/scsi/scsi

command.

The output lists all SCSI devices detected by the server. An P6300/P6500 EVAs LUN entry

looks similar to the following:

Host: scsi3 Channel: 00 ID: 00 Lun: 01

Vendor: HP

Model: HSV340

Rev:

Type: Direct-Access

ANSI SCSI revision: 02

OpenVMS

Updating the AlphaServer console code, Integrity Server console code, and Fibre

Channel FCA firmware

The firmware update procedure varies for the different server types. To update firmware, follow

the procedure described in the Installation instructions that accompany the firmware images.

Verifying the Fibre Channel adapter software installation

A supported FCA should already be installed in the host server. The procedure to verify that the

console recognizes the installed FCA varies for the different server types. Follow the procedure

described in the Installation instructions that accompany the firmware images.

Console LUN ID and OS unit ID

HP P6000 Command View software contains a box for the Console LUN ID on the Initialized

Storage System Properties window.

It is important that you set the Console LUN ID to a number other than zero (0). If the Console LUN

ID is not set or is set to zero (0), the OpenVMS host will not recognize the controller pair. The

Console LUN ID for a controller pair must be unique within the SAN.

Table 11 (page 58)

shows

an example of the Console LUN ID.

You can set the OS unit ID on the Virtual Disk Properties window. The default setting is 0, which

disables the ID field. To enable the ID field, you must specify a value between 1 and 32767,

OpenVMS