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

Configuring Emulex FCAs with the lpfc 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 94 highlights

Configuring Emulex FCAs with the lpfc driver NOTE: The lpfc driver cannot be used with Oracle StorEdge Traffic Manager/Oracle Storage VM Multipathing. Emulex does not support using both the lpfc driver and the emlxs driver (provided with the Oracle SAN driver stack) concurrently. To use the emlxs driver, see Configuring FCAs with the Oracle SAN driver stack. To determine which Emulex FCAs and driver version HP supports with the lpfc driver, contact your HP representative. The lpfc driver is not supported on x86 architecture. Configure Emulex FCAs with the lpfc driver as follows: • Ensure you have the latest supported version of the lpfc driver (available from http:// www.emulex.com). • Edit the /kernel/drv/lpfc.conf driver configuration file to set up the FCA for a SAN infrastructure: topology = 2; • If multiple FCAs and VxVM are used, adjust the following parameters to assure correct VxVM behavior: no-device-delay=0; nodev-tmo=30; linkdown-tmo=30; # verify, should be default value • 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 lputil utility. The following example illustrates the binding of target 20 (lpfc instance 2) to WWPN 50060e8003285301 and the binding of target 30 (lpfc instance 0) to WWPN 50060e8003285311: fcp-bind-WWPN="50060e8003285301:lpfc2t20", "50060e8003285311:lpfc0t30"; (Replace the WWPNs in the previous example with the WWPNs for your array ports.) • For each LUN that needs to be accessed, add an entry to the /kernel/drv/sd.conf file. For example, assume you want to access LUNs 1 and 2 through both paths. You would add the following entries (preferably at the end of the file): name="sd" parent="lpfc" target=20 lun=1; name="sd" parent="lpfc" target=20 lun=2; name="sd" parent="lpfc" target=30 lun=1; name="sd" parent="lpfc" target=30 lun=2; • Perform a reconfiguration reboot to implement the changes to the configuration files. • 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). 94 Solaris

  • 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 Emulex FCAs with the lpfc driver
NOTE:
The lpfc driver cannot be used with Oracle StorEdge Traffic Manager/Oracle Storage
VM Multipathing. Emulex does not support using both the lpfc driver and the emlxs driver (provided
with the Oracle SAN driver stack) concurrently. To use the emlxs driver, see
Configuring FCAs
with the Oracle SAN driver stack
.
To determine which Emulex FCAs and driver version HP supports with the lpfc driver, contact your
HP representative. The lpfc driver is not supported on x86 architecture. Configure Emulex FCAs
with the lpfc driver as follows:
•
Ensure you have the latest supported version of the lpfc driver (available from
h
t
tp://
w
w
w
.e
m
ule
x
.co
m
).
•
Edit the
/kernel/drv/lpfc.conf
driver configuration file to set up the FCA for a SAN
infrastructure:
topology = 2;
•
If multiple FCAs and VxVM are used, adjust the following parameters to assure correct VxVM
behavior:
no-device-delay=0;
nodev-tmo=30;
linkdown-tmo=30; # verify, should be default value
•
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
lputil
utility. The following example illustrates the
binding of target 20 (lpfc instance 2) to WWPN 50060e8003285301 and the binding of
target 30 (lpfc instance 0) to WWPN 50060e8003285311:
fcp-bind-WWPN="50060e8003285301:lpfc2t20",
"50060e8003285311:lpfc0t30";
(Replace the WWPNs in the previous example with the WWPNs for your array ports.)
•
For each LUN that needs to be accessed, add an entry to the
/kernel/drv/sd.conf
file.
For example, assume you want to access LUNs 1 and 2 through both paths. You would add
the following entries (preferably at the end of the file):
name="sd" parent="lpfc" target=20 lun=1;
name="sd" parent="lpfc" target=20 lun=2;
name="sd" parent="lpfc" target=30 lun=1;
name="sd" parent="lpfc" target=30 lun=2;
•
Perform a reconfiguration reboot to implement the changes to the configuration files.
•
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)
.
94
Solaris