lpfc0 & 1 changes to lpfc2 & 3 after firmware upgrade 1

[tntva]

I'm running Solaris 8, kernel patch 108528-27 with Emulex 9002L-E HBA. After upgrading the firmware to the latest version and performing a reboot -- -r, lpcf0 & 1 became lpfc2 & 3. Can someone explain how this may have happen? Is there a way to revert back to lpfc 0 & 1?

 

[Chacalinc]

Problem:
Changed HBA firmware and performed reconfiguration reboot (reboot -- -r) of host.

Causes of this problem:
New firmware created a different physical path for the connection to the CLARiiON array. This happens when the host bus adapter (HBA) previously had FCode and the new firmware does not (or vice versa). You must clear the current logical/physical paths from /dev/dsk, /dev/rdsk, and the PowerPath database and then recreate them.

How do I correctly delete logical/physical paths and clean the PowerPath database?

If the Sun host is running Solaris 8 and above, run the devfsadm -C command.

Note: If there is a logical link and the physical path is valid for the array, Solaris will not delete the paths. The only way to ensure that devfsadm -C will work in that case is to disable the Fibre connections to the array.

If the devfsadm command does not work or the Sun host is running a revision of Solaris earlier than 2.8, follow these steps:

1. Delete the physical paths:

From the /dev/rdsk directory run the ls -l command on the logical links associated with the CLARiiON array. For this example, the physical path is "/devices/pci@9,700000/fibre-channel*" and /devices/pci@9,600000/fibre-channel*:

    * rm -r /devices/pci@9,700000/fibre-channel*
    * rm -r /devices/pci@9,600000/fibre-channel*

2. Delete the logical links under /dev/rdsk and /dev/dsk for the controllers and emcpower devices:

    * rm /dev/dsk/c6*
    * rm /dev/dsk/emcp*
    * rm /dev/rdsk/c7*
    * rm /dev/rdsk/emcp*

3. Delete the pseudo devices associated with the emcpower devices:

    * rm /devices/pseudo/emcp*blk
    * rm /devices/pseudo/emcp*raw

4. Create a zero /kernel/drv/emcp.conf and /etc/powermt.custom files:

    * >/kernel/drv/emcp.conf
    * >/etc/powermt.custom

5. Remove all the entries for the HBA associated with the CLARiiON array from the "/etc/path_to_inst" file:

    * cp /etc/path_to_inst /etc/path_to_inst.11072003
    * grep -v fibre-channel /etc/path_to_inst > /tmp/path_to_inst  (Make sure the file /tmp/path_to_inst have all the entries for the internal boot device.)
    * mv /tmp/path_to_inst /etc/path_to_inst

6 Reboot reconfigure the host:

            reboot -- -r

7. When the host is back, make sure the PowerPath database will be created with the new paths:

    * powercf -q
    * powermt config

Hope this help you.
Cheers.

 

[Chris78]

Hi chacalin,

Nothing to add, it's perfect ;-)

Christian

NB : Tntva, can you tell us which release of Emulex driver and firmware are you using because there some know issues (HBAs no logging during reboot) with firmware 3.91a3 (Symmetrix or Clariion connection). Emulex is working to fix it in the next release.
To find the previous release of the firmware 3.90a7, go on ftp://ftp.emulex.com/pub/fibrechannel/firmware_and_utils/

 

[tntva]

We have two Symm 8530s. We are in the process of upgradeing from 3.90a7 to 3.91a3. What are some of the issues with 3.91a3?. Thanks.

 

[Chacalinc]

Problems found with firmware 3.91a3:

* HBAs not logging in to switch during reboot.
* PowerPath marking all paths "dead" at boot time.
* Emulex HBAs running firmware 3.91a3 in Solaris host connected to CLARiiON or Symmetrix array do not log in to switch during reboot

The cause of the problem is related to a timing issue with the 3.91a3 firmware. The problem will occur if the following combinations of driver/switch settings are used:

* Switch hard set to 1 GB, driver set to topology=2, and link-speed=1
* Switch hard set to 2 GB, driver set to topology=2, and link-speed=2
* Switch set to "auto-negotiate," driver set to topology=2, and link-speed=2

Note: The problem was uncovered during testing with Emulex LP9002-E (PCI) and LP9002S (SBus) HBAs. Since other HBAs use the 3.91a3 firmware, the problem is assumed to be related to the firmware and therefore may also occur with other HBAs using the same firmware.

Workaround:
Downgrade the HBA firmware to revision 3.90a7. Emulex will release a fix in the near future.

Cheers.

 

[Chris78]

Hi,

Thanks for your update Chacalin, you answered more quickly than me!

Cheers

Chris

 

[wardy66]

There's also a script /usr/sbin/lpfc/convert_path_lpfc that you might find interesting

It does similar things and is supplied as part of the driver install