HP XP20000/XP24000 HP StorageWorks XP Disk Array Configuration Guide (T5278-96 - Page 95

Configuring QLogic FCAs with the qla2300 driver

Get HP XP20000/XP24000 PDF manuals and user guides View all HP XP20000/XP24000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 95 highlights

Configuring QLogic FCAs with the qla2300 driver NOTE: The qla2300 driver cannot be used with Oracle StorEdge Traffic Manager/Oracle Storage Multipathing. To configure a QLogic FCA using the Oracle SAN driver stack, see Configuring FCAs with the Oracle SAN driver stack. Contact your HP representative to determine which QLogic FCAs and driver version HP supports with the qla2300 driver. The qla2300 driver is not supported on x86 architecture. Configure QLogic FCAs with the qla2300 driver as follows: • Ensure you have the latest supported version of the qla2300 driver (available from http:// www.qlogic.com). • Edit the /kernel/drv/qla2300.conf driver configuration file to set up the FCA for a SAN infrastructure: hba0-connection-options=1; hba0-link-down-timeout=30; hba0-persistent-binding-configuration=1; • Persistent bindings are necessary in a fabric topology and are used to bind a SCSI target ID to a particular WWPN (of an array port). This is required to guarantee that the SCSI target IDs will remain the same when the system is rebooted. Persistent bindings can be set by editing the configuration file or by using the SANsurfer utility. The following example illustrates the binding of target 20 (hba instance 0) to WWPN 50060e8003285301 and the binding of target 30 (hba instance 1) to WWPN 50060e8003285311: hba0-SCSI-target-id-20-fibre-channel-port-name="50060e8003285301"; hba1-SCSI-target-id-30-fibre-channel-port-name="50060e8003285311"; (Replace the WWPNs in the previous example with the WWPNs for your array ports.) • With qla2300 v4.13.01 and earlier (legacy support on XP10000/XP12000): If LUNs have been preconfigured in the /kernel/drv/sd.conf file, use the devfsadm command to perform LUN rediscovery after configuring LUNs as explained in "Defining the paths" (page 15). • With qla2300 v4.20, 5.02, or later: Verify that the following entry is present in /kernel/drv/sd.conf: name="sd" parent="qla2300" target=0; Perform a reconfiguration reboot to implement the changes to the configuration files. Use the /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig -d qla2300 -s command to perform LUN rediscovery after configuring LUNs as explained in "Defining the paths" (page 15). Configuring AMCC/JNI FCAs (legacy support XP12000 only) Applied Micro Circuits Corporation (AMCC) merged with Jaycor Networks Incorporated (JNI) and discontinued their FCA hardware and software products. HP recommends to migrate to different FCAs. Support is limited to legacy environments with Solaris 8 and 9 only. Configure 2 Gbit FCAs differently as explained below. For 1 Gbit FCAs, see the HP StorageWorks XP12000 Disk Array Configuration Guide for Oracle Solaris. AMCC/JNI legacy drivers are available from AMCC/JNI at http://www.jni.com. The JNI EZFibre FCA configuration utility does not allow dynamic LUN addition. Instead edit the configuration files manually as explained below, and use EZFibre for view-only purposes. If you do not plan to use dynamic LUN addition, you may use EZFibre to configure the FCA. Persistent bindings are necessary in a fabric topology and are used to bind a SCSI target ID to a particular WWPN (of an array port). This is required to guarantee that the SCSI target IDs will Installing and configuring the host 95

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
Configuring QLogic FCAs with the qla2300 driver
NOTE:
The qla2300 driver cannot be used with Oracle StorEdge Traffic Manager/Oracle
Storage Multipathing. To configure a QLogic FCA using the Oracle SAN driver stack, see
Configuring FCAs with the Oracle SAN driver stack
.
Contact your HP representative to determine which QLogic FCAs and driver version HP supports
with the qla2300 driver. The qla2300 driver is not supported on x86 architecture. Configure
QLogic FCAs with the qla2300 driver as follows:
•
Ensure you have the latest supported version of the qla2300 driver (available from
h
t
tp://
w
w
w
.qlogi
c
.co
m
).
•
Edit the
/kernel/drv/qla2300.conf
driver configuration file to set up the FCA for a SAN
infrastructure:
hba0-connection-options=1;
hba0-link-down-timeout=30;
hba0-persistent-binding-configuration=1;
•
Persistent bindings are necessary in a fabric topology and are used to bind a SCSI target ID
to a particular WWPN (of an array port). This is required to guarantee that the SCSI target
IDs will remain the same when the system is rebooted. Persistent bindings can be set by editing
the configuration file or by using the
SANsurfer
utility. The following example illustrates the
binding of target 20 (hba instance 0) to WWPN 50060e8003285301 and the binding of
target 30 (hba instance 1) to WWPN 50060e8003285311:
hba0-SCSI-target-id-20-fibre-channel-port-name="50060e8003285301";
hba1-SCSI-target-id-30-fibre-channel-port-name="50060e8003285311";
(Replace the WWPNs in the previous example with the WWPNs for your array ports.)
•
With qla2300 v4.13.01 and earlier (legacy support on XP10000/XP12000):
If LUNs have been preconfigured in the
/kernel/drv/sd.conf
file, use the
devfsadm
command to perform LUN rediscovery after configuring LUNs as explained in
“Defining the
paths” (page 15)
.
•
With qla2300 v4.20, 5.02, or later:
Verify that the following entry is present in
/kernel/drv/sd.conf
:
name="sd" parent="qla2300" target=0;
Perform a reconfiguration reboot to implement the changes to the configuration files.
Use the
/opt/QLogic_Corporation/drvutil/qla2300/qlreconfig
–
d qla2300
-s
command to perform LUN rediscovery after configuring LUNs as explained in
“Defining
the paths” (page 15)
.
Configuring AMCC/JNI FCAs (legacy support XP12000 only)
Applied Micro Circuits Corporation (AMCC) merged with Jaycor Networks Incorporated (JNI) and
discontinued their FCA hardware and software products. HP recommends to migrate to different
FCAs. Support is limited to legacy environments with Solaris 8 and 9 only.
Configure 2 Gbit FCAs differently as explained below. For 1 Gbit FCAs, see the
HP StorageWorks
XP12000 Disk Array Configuration Guide for Oracle Solaris
. AMCC/JNI legacy drivers are
available from AMCC/JNI at
h
t
tp://w
w
w
.jni
.co
m
. The JNI EZFibre FCA configuration utility does
not allow dynamic LUN addition. Instead edit the configuration files manually as explained below,
and use EZFibre for view-only purposes. If you do not plan to use dynamic LUN addition, you may
use EZFibre to configure the FCA.
Persistent bindings are necessary in a fabric topology and are used to bind a SCSI target ID to a
particular WWPN (of an array port). This is required to guarantee that the SCSI target IDs will
Installing and configuring the host
95