sd.conf file in sun solaris

When you replace the HBA, the lpfc instance may change. For example, if lpfc0 is replaced, the new HBA may have an instance number of lpfc2. How you identify the new instance number is to examine the boot sequence in /var/adm/messages and pinpoint the new HBA wwpn.

Then, and only if the instance has changed, you will replace the old lpfc number with the new lpfc number in lpfc.conf. As already stated, if sd.conf is correctly configured, you don't have to edit it. Also, you keep the existing target information in lpfc.conf. All that changes is the lpfc instance if it is different to before. Of course, you must also take care of your zoning and masking operations.

The short answer is no. If sd.conf is set up correctly such as below:
name="sd" parent="lpfc" target=20 lun=0;

Then you will not need to edit it.

However, you may have to edit the relevant HBA file (lpfc.conf or qlaxxx.conf) where the persistent binding is specified if the controller instance has changed.

i have thoes 2 lines in the grab ....so i have to delete the lines from the files you specified?




NOTICE: FA with WWPN 5006048c4a84eaae has been persistently bound to HBA instance lpfc0 on target 16.
NOTICE: FA with WWPN 5006048c4a84eaa1 has been persistently bound to HBA instance lpfc1 on target 17 .

the problem is we are changing to qlogic not emulex
so i think it will change

Run a "powermt save" prior to replacing the HBA. This will keep the emcpower devices correct and ensure that asm won't have problems.

But the change will be on native names not pesudo names ...am i right ?

So if the asm uses the emcpower names it will not effect anything.
and in case the emcpower names changed we can rename it back to what it was
by emcpadm unless the slice alco changed

Definetly. It WILL change

Qlogic and emulex have different kernel drivers, different config files, different everything.

Again, sd.conf should not have to be changed. sd.conf should already be propagated with target information for 2 paths which can be reused without being changed after the HBA has been replaced.

What you need to update is the persistent binding.
You need to propagate /kernel/drv/2xxx.conf with the new HBA number.

From page 1-12 of the qlogic configuration guide (available at http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/ResourceByOS.aspx?productid=253&oemid=65&oemcatid=58603):

The persistent binding entry must be in this format:
hbaX-SCSI-target-id-Y-fibre-channel-port-name="PPPP";

where X is the new controller number, Y is the existing target (from sd.conf) and PPPP is the WWPN of the symmetrix FA.
When you've completed your new zoning, masking and persistent binding, you will then need to run a reboot -- -r.

ya

but in the powerpath configuration 5.1 "sun" manual it says that you have to update " /kernel/drv/sd.conf " file to include target/logical
device entries for all multipath storage system logical devices.

is this step important ? or we can skip it by rebooting the host " i mean automatic cofiguration"

Thanks Man

As you already learned, replacing an HBA with a different one will give brand new native names. But powerpath pseudo won't change (if you follow the directions you received)

i know that from before but i don't know the application if it was using native or pesudo.........also this server empower names has changed once . so i wanted to know all the possiblities.....
thanks for help stef

if need to upgrade powerpath from 5.0.2 to 5.2.1 ..which is better to do it before the replacement or after ?

sorry i mean
1 hba at time ..or replace them at once
because we will replace the 2 emulex hba's with 2 qlogic...

Message was edited by:
jade