Emulex LP9000 lpfc instance match to WWPN
From: Carlos Sevillano (carlos_sevillano_at_ureach.com)
Date: 01/26/05
- Previous message: Paul: "answerbook add-on packages link?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 25 Jan 2005 20:38:43 -0500 To: sunmanagers@sunmanagers.org
Emulex LP9000
Solaris 8/9
lpfc 5.x driver
Does anyone know of a reason not to manually edit the
/etc/path_to_inst file to fix the the lpfc instance names
to WWPNs?
The problem... lpfc targes change during Flashing of Emulex
Firmware, during rebuild of systems or OS upgrade. The right
solution is to go through a SAN group and re-SAN to the targets
(to what they changed) and that takes some times days or even
weeks.
We noticed that if we manually reverse or change the fiber
instances (using an editor) on the /etc/path_to_install. After
Flashing the Emulex Card or an OS upgrade the numbers of lpfc
WWPN might/will not match what was SANed.
To manually replace the lpfc target numbers to their original
configuration ei (replace 4, 5, 6, 7 with 0, 1, 2, 3) and if
with a clean-up (posted some place on the NET - does not always
work) replace the wrong order (0, 1 and 2, 3 with 1, 0 and 3, 2
to reverse the reversing) ei:
"/pci@8,7600000/pci@1/ribre-channel@4" 0 "lpfc" (change the 0
to the order you originally had)
"/pci@8,7600000/pci@1/ribre-channel@5" 1 "lpfc" (change the 1
to the order you originally had)
"/pci@8,7600000/pci@1/ribre-channel@4" 2 "lpfc" (change the 2
to the order you originally had)
"/pci@8,7600000/pci@1/ribre-channel@5" 3 "lpfc" (change the 3
to the order you originally had)
Then reboot -- -r
and your have the original order before the Flashing of the
cards:
Back to Original:
lpfc0: WWPN:10:00:00:00:c9:3b:2a:e9
WWNN:20:00:00:00:c9:3b:2a:e9
lpfc1: WWPN:10:00:00:00:c9:3b:2a:ea
WWNN:20:00:00:00:c9:3b:2a:ea
lpfc2: WWPN:10:00:00:00:c9:3b:26:75
WWNN:20:00:00:00:c9:3b:26:75
lpfc3: WWPN:10:00:00:00:c9:3b:26:76
WWNN:20:00:00:00:c9:3b:26:76
The above solution works even after repeated reboot -- -r. It
is practical and does the job. It is very good for OS upgrades
without having SAN to re SAN to the new lpfc WWPN layout... you
can change to match the OS before the rebuild and reboot -- -r
and be up and running. Any down side to this?
SAMPLE PROBLEM WITH PATH TO INST:
Aftet Emulex Firmware update lpfc0, 1, 2 and 3 become 4, 5, 6
and 7. Also, on OS rebuild or upgrade lpfc0 can switch with
lpfc 1 and 2 with 3 making the WWPN not match what was SAN by
Storage.
Here is a sample were the clean-up procedure (rediscover the
lpfc instance by removing them from /etc/path_to_inst) did not
work after doing the flash update of the new Emulex LP9000-L2:
cat /etc/path_to_install | grep -v lpfc >
/etc/path_to_inst_clean
cp /etc/path_to_inst_clean /etc/path_to_install
On reboot the new lpfc WWPN order was still different; (lpfc0
switch with lpfc1 and c2 with c3). Should we tell the SAs?
Did I make any mistakes? Have you seen this before? The only
procedure that worked 100% is to have a clean backup of
/etc/path_to_install and revert to that after the flash update:
Original with default FCODE:
NOTICE: lpfc0: Fcode Rev 1.40a0
NOTICE: lpfc0: WWPN:10:00:00:00:c9:41:90:bc
WWNN:20:00:00:00:c9:41:90:bc
NOTICE: lpfc1: Firmware Rev 3.90A7 (C2D3.90A7)
NOTICE: lpfc1: Fcode Rev 1.40a0
NOTICE: lpfc1: WWPN:10:00:00:00:c9:41:90:bd
WWNN:20:00:00:00:c9:41:90:bd
NOTICE: lpfc2: Firmware Rev 3.90A7 (C2D3.90A7)
NOTICE: lpfc2: Fcode Rev 1.40a0
NOTICE: lpfc2: WWPN:10:00:00:00:c9:41:90:d4
WWNN:20:00:00:00:c9:41:90:d4
NOTICE: lpfc3: Firmware Rev 3.90A7 (C2D3.90A7)
NOTICE: lpfc3: Fcode Rev 1.40a0
NOTICE: lpfc3: WWPN:10:00:00:00:c9:41:90:d5
WWNN:20:00:00:00:c9:41:90:d5
Upgrade Firmware to SOE (WWPN switched to 4 5 6 and 7):
Emulex LightPulse FC SCSI/IP 5.02c
NOTICE: lpfc4: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc4: WWPN:10:00:00:00:c9:41:90:bc
WWNN:20:00:00:00:c9:41:90:bc
NOTICE: lpfc5: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc5: WWPN:10:00:00:00:c9:41:90:bd
WWNN:20:00:00:00:c9:41:90:bd
NOTICE: lpfc6: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc6: WWPN:10:00:00:00:c9:41:90:d4
WWNN:20:00:00:00:c9:41:90:d4
NOTICE: lpfc7: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc7: WWPN:10:00:00:00:c9:41:90:d5
WWNN:20:00:00:00:c9:41:90:d5
With Clean-up (clean discovery of lpfc cards) DID NOT worked
lpfc0 and lpfc1 are switched and so are lpfc2 and lpfc3:
NOTICE: lpfc1: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc1: WWPN:10:00:00:00:c9:41:90:bc
WWNN:20:00:00:00:c9:41:90:bc
NOTICE: lpfc0: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc0: WWPN:10:00:00:00:c9:41:90:bd
WWNN:20:00:00:00:c9:41:90:bd
NOTICE: lpfc3: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc3: WWPN:10:00:00:00:c9:41:90:d4
WWNN:20:00:00:00:c9:41:90:d4
NOTICE: lpfc2: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc2: WWPN:10:00:00:00:c9:41:90:d5
WWNN:20:00:00:00:c9:41:90:d5
With original backup of /etc/path_to_install restored from
before the flash (works back to normal):
Emulex LightPulse FC SCSI/IP 5.02c
NOTICE: lpfc0: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc0: WWPN:10:00:00:00:c9:41:90:bc
WWNN:20:00:00:00:c9:41:90:bc
NOTICE: lpfc1: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc1: WWPN:10:00:00:00:c9:41:90:bd
WWNN:20:00:00:00:c9:41:90:bd
NOTICE: lpfc2: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc2: WWPN:10:00:00:00:c9:41:90:d4
WWNN:20:00:00:00:c9:41:90:d4
NOTICE: lpfc3: Firmware Rev 3.92A2 (C2D3.92A2)
NOTICE: lpfc3: WWPN:10:00:00:00:c9:41:90:d5
WWNN:20:00:00:00:c9:41:90:d5
Does anyone know of a reason why not to do this? The manual
change seems to work fine without any impact to the system and
survives reboots with reconfigure.
Carlos
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
- Previous message: Paul: "answerbook add-on packages link?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
