HP XP20000/XP24000 Manuel de configuration - Page 17

Parcourez en ligne ou téléchargez le pdf Manuel de configuration pour {nom_de_la_catégorie} HP XP20000/XP24000. HP XP20000/XP24000 42 pages. Hp storageworks xp disk array configuration guide: vmware (a5951-96106, september 2010)
Également pour HP XP20000/XP24000 : Note de mise à jour (13 pages), Manuel d'intégration (29 pages), Note de mise à jour (4 pages), Manuel de l'administrateur (50 pages), Manuel de configuration (40 pages), Manuel de configuration (40 pages), Manuel de configuration (36 pages), Manuel de configuration (36 pages), Manuel de configuration (30 pages), Manuel de configuration (36 pages), Note de mise à jour (5 pages), Manuel de configuration (46 pages), Manuel de configuration (46 pages), Manuel de référence (46 pages), Manuel de configuration (40 pages), Manuel de configuration (44 pages), Manuel de configuration (38 pages), Manuel de configuration (34 pages), Manuel de configuration (30 pages), Manuel de configuration (30 pages)

Configuring Emulex FCAs with the lpfc driver

NOTE:

The lpfc driver cannot be used with Sun StorEdge Traffic Manager/Sun Storage Multipathing. Emulex

does not support using both the lpfc driver and the emlxs driver (provided with the Sun SAN driver

stack) concurrently. To use the emlxs driver, refer to

Configuring FCAs with the Sun SAN driver

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

www.emulex.com).

Edit the /kernel/drv/lpfc.conf driver configuration file to set up the FCA for a SAN infra-

structure:

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 con-

figuration 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 above 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 fol-

lowing 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" on page 21.

stack" on page 15.

XP Disk Array Configuration Guide for Sun Solaris

http://