Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1927613.1
Update Date:2018-03-07
Keywords:

Solution Type  Problem Resolution Sure

Solution  1927613.1 :   FC HBA Emlxs Firmware Update - ERROR:1522: Firmware Download Failed. (Unable to Erase Flash. Mailbox cmd=1c status=fe)  


Related Items
  • Sun SPARC Enterprise M5000 Server
  •  
  • Emulex FC HBA
  •  
  • Solaris Operating System
  •  
  • Solaris Operating System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>HBA>SN-DK: FC HBA
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-9265034731>

Applies to:

Emulex FC HBA - Version Not Applicable and later
Solaris Operating System - Version 8 6/00 U1 and later
Sun SPARC Enterprise M5000 Server - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

Solaris 10 M5000 server "server01" with two Oracle FC HBAs LPe12002-S ,
two ports connected to the SAN to access EMC disk storage arrays:

C# INST# PORT WWN MODEL FCODE STATUS DEVICE PATH
-- ----- -------- ----- ----- ------ -----------
c2 emlxs0 10000090fa3XXXX1 LPe12002-S 3.01a1 CONNECTED /pci@2,600000/SUNW,emlxs@0
c3 emlxs1 10000090fa3XXXX2 LPe12002-S 3.01a1 NOT CONNECTED /pci@2,600000/SUNW,emlxs@0,1
FC HBA2:
c4 emlxs2 10000000c9eXXXX1 LPe12002-S 3.01a1 CONNECTED /pci@12,600000/SUNW,emlxs@0
c5 emlxs3 10000000c9eXXXX2 LPe12002-S 3.01a1 NOT CONNECTED /pci@12,600000/SUNW,emlxs@0,1

Customer has installed emlxs patch 149173-04 on 24 June:
patch_date.out:drwxr-xr-x 2 root root 6 Jun 24 05:38 149173-04


On server reboot at "Jun 30 13:35:43" we see firmware update was required:

Jun 30 13:35:43 server01 emlxs: [ID 349649 kern.info] [ 1.037A]emlxs0:WARNING:1540: Firmware update required. (To trigger an update, a manual HBA or link reset using luxadm, fcadm, or emlxadm is required.)
Jun 30 13:35:43 server01 emlxs: [ID 349649 kern.info] [ 1.037A]emlxs1:WARNING:1540: Firmware update required. (To trigger an update, a manual HBA or link reset using luxadm, fcadm, or emlxadm is required.)
Jun 30 13:35:43 server01 emlxs: [ID 349649 kern.info] [ 1.037A]emlxs2:WARNING:1540: Firmware update required. (To trigger an update, a manual HBA or link reset using luxadm, fcadm, or emlxadm is required.)
Jun 30 13:35:43 server01 emlxs: [ID 349649 kern.info] [ 1.037A]emlxs3:WARNING:1540: Firmware update required. (To trigger an update, a manual HBA or link reset using luxadm, fcadm, or emlxadm is required.)


Customer initiated firmware update with "luxadm -e forcelip" as explained on doc:
Warning:1540: Firmware Update Required. (A Manual Hba Reset Or Link Reset (Using Luxadm Or Fcadm) Is Required (Doc ID 1356876.1)

Firmware update worked fine on first FC HBA (emlxs0 and emlxs1), these are the expected messages when firmware update is completed:

Jun 30 13:42:13 server01 emlxs: [ID 349649 kern.info] [13.02D5]emlxs1: NOTICE: 200: Adapter initialization. (Firmware update needed. Updating. id=36 fw=6)
Jun 30 13:42:13 server01 emlxs: [ID 349649 kern.info] [ 3.114A]emlxs1: NOTICE:1520: Firmware download. (AWC file: KERN: old=1.11a3 new=1.11a8 Update.)
Jun 30 13:42:13 server01 emlxs: [ID 349649 kern.info] [ 3.116A]emlxs1: NOTICE:1520: Firmware download. (DWC file: TEST: new=1.00a4 Update.)
Jun 30 13:42:13 server01 emlxs: [ID 349649 kern.info] [ 3.117E]emlxs1: NOTICE:1520: Firmware download. (DWC file: STUB: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:42:13 server01 emlxs: [ID 349649 kern.info] [ 3.119C]emlxs1: NOTICE:1520: Firmware download. (DWC file: SLI2: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:42:13 server01 emlxs: [ID 349649 kern.info] [ 3.11AB]emlxs1: NOTICE:1520: Firmware download. (DWC file: SLI3: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:42:24 server01 emlxs: [ID 349649 kern.info] [ 3.0159]emlxs1: NOTICE:1521: Firmware download complete. (Status good.)


Jun 30 13:42:55 server01 emlxs: [ID 349649 kern.info] [ 5.03EF]emlxs0: NOTICE: 710: Link down.
Jun 30 13:42:59 server01 emlxs: [ID 349649 kern.info] [13.02D5]emlxs0: NOTICE: 200: Adapter initialization. (Firmware update needed. Updating. id=36 fw=6)
Jun 30 13:42:59 server01 emlxs: [ID 349649 kern.info] [ 3.114A]emlxs0: NOTICE:1520: Firmware download. (AWC file: KERN: old=1.11a3 new=1.11a8 Update.)
Jun 30 13:42:59 server01 emlxs: [ID 349649 kern.info] [ 3.116A]emlxs0: NOTICE:1520: Firmware download. (DWC file: TEST: new=1.00a4 Update.)
Jun 30 13:42:59 server01 emlxs: [ID 349649 kern.info] [ 3.117E]emlxs0: NOTICE:1520: Firmware download. (DWC file: STUB: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:42:59 server01 emlxs: [ID 349649 kern.info] [ 3.119C]emlxs0: NOTICE:1520: Firmware download. (DWC file: SLI2: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:42:59 server01 emlxs: [ID 349649 kern.info] [ 3.11AB]emlxs0: NOTICE:1520: Firmware download. (DWC file: SLI3: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:43:11 server01 emlxs: [ID 349649 kern.info] [ 3.0159]emlxs0: NOTICE:1521: Firmware download complete. (Status good.)
Jun 30 13:43:17 server01 emlxs: [ID 349649 kern.info] [ 5.062D]emlxs0: NOTICE: 720: Link up. (8Gb, fabric, initiator)


***BUT firmware update had a problem with FC HBA2,
here are the messages observed and the final error when updating emlxs3
(the instance associated to the FC HBA port not connected to any storage device)

--> firware update started fine
Jun 30 13:43:39 server01 emlxs: [ID 349649 kern.info] [13.02D5]emlxs3: NOTICE: 200: Adapter initialization. (Firmware update needed. Updating. id=36 fw=6)
Jun 30 13:43:39 server01 emlxs: [ID 349649 kern.info] [ 3.114A]emlxs3: NOTICE:1520: Firmware download. (AWC file: KERN: old=1.11a3 new=1.11a8 Update.)
Jun 30 13:43:39 server01 emlxs: [ID 349649 kern.info] [ 3.116A]emlxs3: NOTICE:1520: Firmware download. (DWC file: TEST: new=1.00a4 Update.)
Jun 30 13:43:39 server01 emlxs: [ID 349649 kern.info] [ 3.117E]emlxs3: NOTICE:1520: Firmware download. (DWC file: STUB: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:43:39 server01 emlxs: [ID 349649 kern.info] [ 3.119C]emlxs3: NOTICE:1520: Firmware download. (DWC file: SLI2: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:43:39 server01 emlxs: [ID 349649 kern.info] [ 3.11AB]emlxs3: NOTICE:1520: Firmware download. (DWC file: SLI3: old=2.01a4 new=2.01a10 Update.)

--> then we see some scsi errors against disk on the SAN,
not sure if these scsi errors could be related with the firmware update failure,
weird because emlxs3 has not IO traffic at all, as there is no FC cable connected to it,
only emlxs2 has a FC cable connected to the SAN and could have some IO

Jun 30 13:43:56 server01 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Jun 30 13:43:56 server01 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Jun 30 13:43:56 server01 scsi: [ID 583861 kern.info] ssd308 at scsi_vhci0: unit-address g60000970000292603495533030393135: g60000970000292603495533030393135
Jun 30 13:43:56 server01 genunix: [ID 936769 kern.info] ssd308 is /scsi_vhci/ssd@g60000970000292603495533030393135
Jun 30 13:43:57 server01 scsi: [ID 583861 kern.info] ssd726 at scsi_vhci0: unit-address g60000970000292603487533030413130: g60000970000292603487533030413130
Jun 30 13:43:57 server01 genunix: [ID 936769 kern.info] ssd726 is /scsi_vhci/ssd@g60000970000292603487533030413130

Jun 30 13:44:01 server01 scsi: [ID 583861 kern.info] ssd315 at scsi_vhci0: unit-address g60000970000292603495533030393032: g60000970000292603495533030393032
Jun 30 13:44:01 server01 genunix: [ID 936769 kern.info] ssd315 is /scsi_vhci/ssd@g60000970000292603495533030393032
Jun 30 13:44:01 server01 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60000970000292603495533030393135 (ssd308): Error for Command: mode_sense(10) Error Level: Retryable
Jun 30 13:44:01 server01 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0
Jun 30 13:44:01 server01 scsi: [ID 107833 kern.notice] Vendor: EMC Serial Number: 95915000@
Jun 30 13:44:01 server01 scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Jun 30 13:44:01 server01 scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0

---> NOTICE here the relevant errors, after 10 min the firmware update failed:
Jun 30 13:53:48 server01 emlxs: [ID 349649 kern.info] [13.0D85]emlxs3: ERROR: 530: Mailbox timeout. (DOWN_LOAD: mb=6012b602340 tmo=300 Polled. (20000000,1e40,166200))
Jun 30 13:53:48 server01 emlxs: [ID 349649 kern.info] [ 3.0C8A]emlxs3: ERROR:1522: Firmware download failed. (Unable to erase flash. Mailbox cmd=1c status=fe)
Jun 30 13:53:48 server01 emlxs: [ID 349649 kern.info] [ 3.0D48]emlxs3: ERROR:1522: Firmware download failed. (Failed to program flash.)
Jun 30 13:53:48 server01 emlxs: [ID 349649 kern.info] [13.02EB]emlxs3: NOTICE: 200: Adapter initialization. (Firmware update failed.)
Jun 30 13:54:18 server01 genunix: [ID 408114 kern.info] /pci@12,600000/SUNW,emlxs@0,1 (emlxs3) down

 

Due to that an fma fault was created:

Jun 30 13:54:18 server01 fmd: [ID 377184 daemon.error] SUNW-MSG-ID: PCIEX-8000-0A, TYPE: Fault, VER: 1, SEVERITY: Critical EVENT-TIME: 20
PLATFORM: SUNW,SPARC-Enterprise, CSN: BDF1152A9C, HOSTNAME: server01
SOURCE: eft, REV: 1.16 EVENT-ID: d2a57941-310a-4e93-b9f4-f01d4e3e3193
DESC: A problem was detected for a PCIEX device.
AUTO-RESPONSE: One or more device instances may be disabled
IMPACT: Loss of services provided by the device instances associated with this fault REC-ACTION: Use 'fmadm faulty' to provide a more detailed view of this event. Please refer to the associated reference document at http://sun.com/msg/PCIEX-8000-0A for the latest service procedures and policies regarding this diagnosis.




The same problem was found with emxls2 :

Jun 30 13:59:44 server01 emlxs: [ID 349649 kern.info] [ 5.03EF]emlxs2: NOTICE: 710: Link down.
Jun 30 13:59:49 server01 emlxs: [ID 349649 kern.info] [13.02D5]emlxs2: NOTICE: 200: Adapter initialization. (Firmware update needed. Updating. id=36 fw=6)
Jun 30 13:59:49 server01 emlxs: [ID 349649 kern.info] [ 3.114A]emlxs2: NOTICE:1520: Firmware download. (AWC file: KERN: old=1.11a3 new=1.11a8 Update.)
Jun 30 13:59:49 server01 emlxs: [ID 349649 kern.info] [ 3.116A]emlxs2: NOTICE:1520: Firmware download. (DWC file: TEST: new=1.00a4 Update.)
Jun 30 13:59:49 server01 emlxs: [ID 349649 kern.info] [ 3.117E]emlxs2: NOTICE:1520: Firmware download. (DWC file: STUB: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:59:49 server01 emlxs: [ID 349649 kern.info] [ 3.119C]emlxs2: NOTICE:1520: Firmware download. (DWC file: SLI2: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:59:49 server01 emlxs: [ID 349649 kern.info] [ 3.11AB]emlxs2: NOTICE:1520: Firmware download. (DWC file: SLI3: old=2.01a4 new=2.01a10 Update.)

Jun 30 14:04:03 server01 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60000970000292603487533030363837 (ssd899): Error for Command: mode_sense(10) Error Level: Retryable
Jun 30 14:04:03 server01 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0
Jun 30 14:04:03 server01 scsi: [ID 107833 kern.notice] Vendor: EMC Serial Number: 87687000@
Jun 30 14:04:03 server01 scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Jun 30 14:04:03 server01 scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Jun 30 14:04:03 server01 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60000970000292603487533030363837 (ssd899): Error for Command: mode_sense(10) Error Level: Retryable
Jun 30 14:04:03 server01 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0
Jun 30 14:04:03 server01 scsi: [ID 107833 kern.notice] Vendor: EMC Serial Number: 87687000@
Jun 30 14:04:03 server01 scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Jun 30 14:04:03 server01 scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
...
Jun 30 14:09:58 server01 emlxs: [ID 349649 kern.info] [13.0D85]emlxs2: ERROR: 530: Mailbox timeout. (DOWN_LOAD: mb=6011e2da180 tmo=300 Polled. (20000000,1e40,166200))
Jun 30 14:09:58 server01 emlxs: [ID 349649 kern.info] [ 3.0C8A]emlxs2: ERROR:1522: Firmware download failed. (Unable to erase flash. Mailbox cmd=1c status=fe)
Jun 30 14:09:58 server01 emlxs: [ID 349649 kern.info] [ 3.0D48]emlxs2: ERROR:1522: Firmware download failed. (Failed to program flash.)
Jun 30 14:09:58 server01 emlxs: [ID 349649 kern.info] [13.02EB]emlxs2: NOTICE: 200: Adapter initialization. (Firmware update failed.)
Jun 30 14:10:04 server01 emlxs: [ID 349649 kern.info] [ 5.062D]emlxs2: NOTICE: 720: Link up. (8Gb, fabric, initiator)
Jun 30 14:10:04 server01 scsi: [ID 243001 kern.info] /pci@12,600000/SUNW,emlxs@0/fp@0,0 (fcp8): Lun=0 for target=711600 disappeared
Jun 30 14:10:04 server01 scsi: [ID 243001 kern.info] /pci@12,600000/SUNW,emlxs@0/fp@0,0 (fcp8): Lun=0 for target=720300 disappeared
Jun 30 14:10:13 server01 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60000970000292603495533030443834 (ssd935): Error for Command: write(10) Error Level: Retryable
Jun 30 14:10:13 server01 scsi: [ID 107833 kern.notice] Requested Block: 21025184 Error Block: 21025184
Jun 30 14:10:13 server01 scsi: [ID 107833 kern.notice] Vendor: EMC Serial Number: 95D84000@
Jun 30 14:10:13 server01 scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Jun 30 14:10:13 server01 scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Jun 30 14:10:28 server01 genunix: [ID 408114 kern.info] /pci@12,600000/SUNW,emlxs@0 (emlxs2) down

 

Jun 30 14:10:28 server01 fmd: [ID 377184 daemon.error] SUNW-MSG-ID: PCIEX-8000-0A, TYPE: Fault, VER: 1, SEVERITY: Critical EVENT-TIME: 20
PLATFORM: SUNW,SPARC-Enterprise, CSN: BDF1152A9C, HOSTNAME: server01
SOURCE: eft, REV: 1.16 EVENT-ID: 18ffd406-dce9-4a69-ef05-87d7dccce7cb
DESC: A problem was detected for a PCIEX device.
AUTO-RESPONSE: One or more device instances may be disabled
IMPACT: Loss of services provided by the device instances associated with this fault REC-ACTION: Use 'fmadm faulty' to provide a more detailed view of this event. Please refer to the associated reference document at http://sun.com/msg/PCIEX-8000-0A for the latest service procedures and policies regarding this diagnosis.

 

Cause

The cause was investigated on this BUG , worked by Emulex

Bug 19149937 - FC HBA becomes unusable due to emlxs Mailbox Timeout during firmware update

RCA could not be identified, a Driver and Firmware dump from the Emulex FC HBA was required

In this case the DOWNLOAD command is failing.
Description of Download command given in the SLI3 is below:
"It is timing out. Generally timeout happens when FW or hardware is not responding."

 

There was also a known issue of Driver Version: 2.90.15.0 (2014.01.22.14.50)  fails to update older firmware (Firmware Version: LPe12002-S 2.00a4)

"luxadm -e forcelip" command triggers the firmware update on emlxs driver.

Solution

Use the latest drivers and firmware, you should update OneCommand Manager CLI to the latest version
and then update the adapter to the latest firmware using that CLI.

In case you hit this issue, use the Emulex-supplied utilities, on the Broadcom site https://www.broadcom.com/support/oem/oracle-fc/ there are utilities for Solaris, Linux and Windows.

Notice. The drivers, and firmware, and utilities are released by Emulex as a kit. Best practice is to use the releases from the same kit.

 

Workaround to complete the firmware upgrade

1) Clear / repair the fma fault with command 

# fmadm repair <uuid>

 

See also

How To Clear FMA faults from Solaris[TM] and SC (System Controller) on T1000/T2000 T5120/T5220/T5140/T5240/T5440, T3-1/T3-2/T3-4, T4-1/T4-2/T4-4 (Doc ID 1004229.1)

In a situation where "fmadm repaired [fmri|label]" or "fmadm acquit [fmri|label]" does not clear the device from the
persistent store (ie /etc/devices/retire_store file), the workaround is to delete the store and reboot solaris.

rm /etc/devices/retire_store
reboot Solaris (e.g. init 6, reboot )

 

- After that try again the firmware upgrade with "luxadm -e forcelip"

# luxadm -e forcelip /devices/pci@12,600000/SUNW,emlxs@0,1/fp@0,0:devctl

 

2) If "luxadm -e forcelip " command does not trigger any new firmware update , then run

/opt/EMLXemlxu/bin/emlxadm <device> get_fw_rev  --> to get the firmware version, because an "fcinfo hba-port" doesn't show the truth until the system becomes rebooted.
/opt/EMLXemlxu/bin/emlxadm <device> diag emlxs_post  --> to get get further information about the HBA

These commands should cause the adapter back to a good state that allows another update to be started.

About: /opt/EMLXemlxu/bin/emlxadm get_fw_rev
This command reads fw_version from the internally stored driver variable.

About: /opt/EMLXemlxu/bin/emlxadm diag emlxs_post
This command takes the adapter offline, resets adapter and takes the adapter again online.
emlxs_post reinitializes the adapter. Here all the Software data structure
is freed, adapter is reset and again reinitialized. In this case the adapter
must be coming out of the error, if any as we are reinitializing it.

 

- If you don't have older EMLXemlxu packaged installed, you can install the new Emulex One Command Manager ( OCM ).

As example, the equivalent command to get the firmware version using the OCM tool is:

# /opt/ELXocm/hbacmd HbaAttributes <pwwn>

#./hbacmd HbaAttributes 10:00:00:90:fa:19:31:75
HBA Attributes for 10:00:00:90:fa:19:31:75

Host Name                     : t4-4-tvp540-f
Manufacturer                  : Oracle Corporation
Serial Number                 : 4925381+13100000X4
Model                         : LPem16002-M6-O
Model Desc                    : 7101690, Oracle 16Gb EM Universal HBA
Node WWN                      : 20 00 00 90 fa 19 31 75
Node Symname                  : Emulex LPem16002-M6-O FV1.1.60.1 DV2.90.15.0
HW Version                    : 0000000b
FW Version                    : 1.1.60.1  <<---
Vendor Spec ID                : 10DF
Number of Ports               : 1
Driver Name                   : emlxs
Device ID                     : E200
HBA Type                      : LPem16002-M6-O
Operational FW                : 1.1.60.1  <<----
IEEE Address                  : 00 90 fa 19 31 75
Boot Code                     : Enabled
Boot Version                  : KT8.04a3
Driver Version                : 2.90.15.0 (2014.01.22.14.50)  <<---
Board Temperature             : Normal
Function Type                 : FC
Sub Device ID                 : E20C
PCI Bus Number                : 0
PCI Func Number               : 1
Sub Vendor ID                 : 10DF
Service Processor FW Name     : 1.1.60.1
ULP FW Name                   : 1.1.60.1
FC Universal BIOS Version     : KT8.04a3
FC x86 BIOS Version           : KA6.02a12
FC EFI BIOS Version           : KD6.11a9
FC FCODE Version              : KN4.03a4
Flash Firmware Version        : 1.1.60.1

 

This software can be downloaded here, for Solaris 10 u11:

https://www.broadcom.com/support/oem/oracle-fc/fibre-channel-8gb/sg-xpcie2fc-em8-z/

OneCommand Manager Enterprise Application Kit (GUI)
https://docs.broadcom.com/docs/12357358

OneCommand Manager Core Application Kit (CLI)
https://docs.broadcom.com/docs/12357359


You can install the CLI ( core ) package.

Once installed, the equivalents commands to run will be:

# /opt/ELXocm/hbacmd ListHBAs
# /opt/ELXocm/hbacmd GetVPD <WWPN>
# /opt/ELXocm/hbacmd PostTest <WWPN>

 

- After that, try another "luxadm-e forcelip" triggers second firmware update and it completes fine.

Example. See here how second luxadm -e forcelip (after running /opt/EMLXemlxu/bin/emlxadm diag emlxs_post) worked fine:

# luxadm -e forcelip /devices//pci@12,600000/SUNW,emlxs@0,1/fp@0,0:devctl

Jun 30 13:57:54 server01 emlxs: [ID 349649 kern.info] [ 1.037A]emlxs3:WARNING:1540: Firmware update required. (To trigger an update, a manual HBA or link reset using luxadm, fcadm, or emlxadm is required.)
Jun 30 13:57:54 server01 emlxs: [ID 948823 kern.notice] WARNING: emlxs3: Firmware update required. (To trigger an update, a manual HBA or link reset using luxadm, fcadm, or emlxadm is required.)
Jun 30 13:58:50 server01 emlxs: [ID 349649 kern.info] [13.02D5]emlxs3: NOTICE: 200: Adapter initialization. (Firmware update needed. Updating. id=36 fw=6)
Jun 30 13:58:50 server01 emlxs: [ID 349649 kern.info] [ 3.114A]emlxs3: NOTICE:1520: Firmware download. (AWC file: KERN: old=1.11a8 new=1.11a8 Skip.)
Jun 30 13:58:50 server01 emlxs: [ID 349649 kern.info] [ 3.116A]emlxs3: NOTICE:1520: Firmware download. (DWC file: TEST: new=1.00a4 Update.)
Jun 30 13:58:50 server01 emlxs: [ID 349649 kern.info] [ 3.117E]emlxs3: NOTICE:1520: Firmware download. (DWC file: STUB: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:58:50 server01 emlxs: [ID 349649 kern.info] [ 3.119C]emlxs3: NOTICE:1520: Firmware download. (DWC file: SLI2: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:58:50 server01 emlxs: [ID 349649 kern.info] [ 3.11AB]emlxs3: NOTICE:1520: Firmware download. (DWC file: SLI3: old=2.01a4 new=2.01a10 Update.)
Jun 30 13:59:00 server01 emlxs: [ID 349649 kern.info] [ 3.0159]emlxs3: NOTICE:1521: Firmware download complete. (Status good.)

 

3) If problem persist, please contact with Oracle Support and open a new SR to address this problem.

In case problem is reproduced, it is required the following information:


Please download and install Emulex's OneCapture software for Solaris, available also in the OEM Qualified Downloads for Oracle (as explained above)

OneCapture Utility for Solaris Embedded File
https://docs.broadcom.com/docs/12357100


You'll need to install the above , reproduce the
issue, run OneCapture with the " --deaddump " option immediately after the
reproduction, then you can obtain the Solaris crash dump.


Tested this emulex tool on the Oracle Lab server :
Test done on Solaris 10 server while writing on storage LUN, problem not reproduced,
but I'm able to run OneCapture_Solaris_ocmcore.sh or OneCapture_Solaris.sh while there is IO to the storage,
although during a period of 15 secs the link is down (while firmware dump is taken from FC HBA)
so applications could be affected

(not on my case , copying a file to a UFS filesystem on the storage LUN, only one scsi error "Command failed to complete" , no IO to the filesystem during these 15 secs)


/dev/dsk/c1t600A0B800035E82F0000352654190FA7d0s6
                    103008078 33463313 68514685    33%    /test


# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
      0. c0t0d0 <FUJITSU-MBB2147RC-3703 cyl 14087 alt 2 hd 24 sec 848>
         /pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0
      1. c0t1d0 <FUJITSU-MBB2147RC-3703-136.73GB>
         /pci@0,600000/pci@0/pci@0/scsi@0/sd@1,0
      2. c1t600A0B800035E82F0000352654190FA7d0 <SUN-LCSM100_F-0735 cyl 51198 alt 2 hd 64 sec 64>  vol0
         /scsi_vhci/ssd@g600a0b800035e82f0000352654190fa7
Specify disk (enter its number): ^D
# luxadm display /dev/rdsk/c1t600A0B800035E82F0000352654190FA7d0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c1t600A0B800035E82F0000352654190FA7d0s2
 Vendor:               SUN
 Product ID:           LCSM100_F
 Revision:             0735
 Serial Num:           SF71101701
 Unformatted capacity: 102400.000 MBytes
 Write Cache:          Enabled
 Read Cache:           Enabled
   Minimum prefetch:   0x3
   Maximum prefetch:   0x0
 Device Type:          Disk device
 Path(s):

 /dev/rdsk/c1t600A0B800035E82F0000352654190FA7d0s2
 /devices/scsi_vhci/ssd@g600a0b800035e82f0000352654190fa7:c,raw
  Controller           /devices/pci@1,700000/pci@0/pci@9/SUNW,emlxs@0/fp@0,0
   Device Address              202400a0b835e82f,0
   Host controller port WWN    10000000c9c07ba0
   Class                       primary
   State                       ONLINE

#


bash-3.2# date
Mon Sep 29 14:28:32 CEST 2014
bash-3.2# ./OneCapture_Solaris_ocmcore.sh
Verifying archive integrity... All good.
Uncompressing Emulex OneCapture...
Running Emulex OneCapture Solaris, version 10.2.370.16
Emulex Corporation Report Utility
Started at Mon Sep 29 14:28:38 CEST 2014
Initializing report environment for host:m3000-tvp540-a
Collecting System Information...
Capture Completed
Generating Compressed Capture...
Done
OneCapture_Solaris_2014-09-29_142838.tgz is under current directory /var/tmp/onecap
bash-3.2#



Sep 29 13:28:56 m3000-tvp540-a emlxs: [ID 349649 kern.info] [ 5.03EF]emlxs0: NOTICE: 710: Link down.
Sep 29 13:28:56 m3000-tvp540-a scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Sep 29 13:28:56 m3000-tvp540-a  /scsi_vhci/ssd@g600a0b800035e82f0000352654190fa7 (ssd0): Command failed to complete (3) on path fp0/ssd@w202400a0b835e82f,0
Sep 29 13:29:08 m3000-tvp540-a emlxs: [ID 349649 kern.info] [13.0303]emlxs0: NOTICE: 200: Adapter initialization. (Firmware update not needed.)
Sep 29 13:29:10 m3000-tvp540-a emlxs: [ID 349649 kern.info] [ 5.062D]emlxs0: NOTICE: 720: Link up. (4Gb, fabric, initiator)




bash-3.2# ./OneCapture_Solaris.sh
Verifying archive integrity... All good.
Uncompressing Emulex OneCapture...
Running Emulex OneCapture Solaris, version 10.2.370.16
Emulex Corporation Report Utility
Started at Mon Sep 29 14:30:17 CEST 2014
Initializing report environment for host:m3000-tvp540-a
Collecting System Information...
Capture Completed
Generating Compressed Capture...
Done
OneCapture_Solaris_2014-09-29_143017.tgz is under current directory /var/tmp/onecap
bash-3.2#

Sep 29 13:30:34 m3000-tvp540-a emlxs: [ID 349649 kern.info] [ 5.03EF]emlxs0: NOTICE: 710: Link down.
Sep 29 13:30:34 m3000-tvp540-a scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Sep 29 13:30:34 m3000-tvp540-a  /scsi_vhci/ssd@g600a0b800035e82f0000352654190fa7 (ssd0): Command failed to complete (3) on path fp0/ssd@w202400a0b835e82f,0
Sep 29 13:30:46 m3000-tvp540-a emlxs: [ID 349649 kern.info] [13.0303]emlxs0: NOTICE: 200: Adapter initialization. (Firmware update not needed.)
Sep 29 13:30:48 m3000-tvp540-a emlxs: [ID 349649 kern.info] [ 5.062D]emlxs0: NOTICE: 720: Link up. (4Gb, fabric, initiator)






bash-3.2# ./OneCapture_Solaris_ocmcore.sh --deaddump
Verifying archive integrity... All good.
Uncompressing Emulex OneCapture...

You have chosen capture which include dead dump
Require to have a system reboot to revover your CNA/HBA
Please do not use this if system is boot from SAN thru HBA
use option --nodeaddump or --bootfromsan to skip dead dumps or all core dumps

Do you wish to continue this capture? (y/n) y
Running Emulex OneCapture Solaris, version 10.2.370.16
Emulex Corporation Report Utility
Started at Mon Sep 29 15:39:43 CEST 2014
Initializing report environment for host:m3000-tvp540-a
Collecting System Information...
Capture Completed
Generating Compressed Capture...
Done
OneCapture_Solaris_2014-09-29_153929.tgz is under current directory /var/tmp/onecap
bash-3.2#

Sep 29 14:40:01 m3000-tvp540-a emlxs: [ID 349649 kern.info] [ 5.03EF]emlxs0: NOTICE: 710: Link down.
Sep 29 14:40:01 m3000-tvp540-a scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
Sep 29 14:40:01 m3000-tvp540-a  /scsi_vhci/ssd@g600a0b800035e82f0000352654190fa7 (ssd0): Command failed to complete (3) on path fp0/ssd@w202400a0b835e82f,0
Sep 29 14:40:13 m3000-tvp540-a emlxs: [ID 349649 kern.info] [13.0303]emlxs0: NOTICE: 200: Adapter initialization. (Firmware update not needed.)
Sep 29 14:40:15 m3000-tvp540-a emlxs: [ID 349649 kern.info] [ 5.062D]emlxs0: NOTICE: 720: Link up. (4Gb, fabric, initiator)

The output seems to be the same on all

-rw-r--r--   1 root     root      158540 Sep 29 14:29 OneCapture_Solaris_2014-09-29_142838.tgz
-rw-r--r--   1 root     root      159446 Sep 29 14:30 OneCapture_Solaris_2014-09-29_143017.tgz
-rw-r--r--   1 root     root      159812 Sep 29 15:40 OneCapture_Solaris_2014-09-29_153929.tgz

The three files have the same content:

bash-3.2# gzcat OneCapture_Solaris_2014-09-29_142838.tgz|tar tvf -
drwxr-xr-x   0/0        0 Sep 29 14:29 2014 dump/
drwxr-xr-x   0/0        0 Sep 29 14:28 2014 dump/System_Information/
-rw-r--r--   0/0    29524 Sep 29 14:28 2014 dump/System_Information/sys_info
-rw-r--r--   0/0      190 Sep 29 14:28 2014 dump/System_Information/BiosInfo
-rw-r--r--   0/0   154589 Sep 29 14:28 2014 dump/System_Information/pciconf_output
drwxr-xr-x   0/0        0 Sep 29 14:28 2014 dump/System_information/
-rw-r--r--   0/0      946 Sep 29 14:28 2014 dump/System_information/fcinfo_output
drwxr-xr-x   0/0        0 Sep 29 14:28 2014 dump/NIC_Information/
-rw-r--r--   0/0     5836 Sep 29 14:28 2014 dump/NIC_Information/OneConnect_NIC_information
-rw-r--r--   0/0   1116492 Sep 29 14:28 2014 dump/NIC_Information/sysdef_output
-rw-r--r--   0/0    22807 Sep 29 14:28 2014 dump/NIC_Information/netstat_output
-rw-r--r--   0/0     2260 Sep 29 14:28 2014 dump/NIC_Information/vmstat_output
-rw-r--r--   0/0      527 Sep 29 14:28 2014 dump/NIC_Information/interrupt_output
drwxr-xr-x   0/0        0 Sep 29 14:28 2014 dump/Roce_Information/
-rw-r--r--   0/0    49829 Sep 29 14:28 2014 dump/Roce_Information/Roce_information
drwxr-xr-x   0/0        0 Sep 29 14:28 2014 dump/Storage_Scsi_Info/
-rw-r--r--   0/0     3124 Sep 29 14:28 2014 dump/Storage_Scsi_Info/StorScsiInfo
drwxr-xr-x   0/0        0 Sep 29 14:28 2014 dump/MILI/
-rw-r--r--   0/0      171 Sep 29 14:28 2014 dump/MILI/mili2d.log
-rw-r--r--   0/0      153 Sep 29 14:28 2014 dump/MILI/mili_report
-rw-r--r--   0/0      279 Sep 29 14:28 2014 dump/MILI/MILIservice_info.txt
drwxr-xr-x   0/0        0 Sep 29 14:28 2014 dump/OCM/
-rw-r--r--   0/0     1030 Sep 29 14:28 2014 dump/OCM/ocm_info
-rw-r--r--   0/0     1394 Sep 29 14:28 2014 dump/OCM/rm.log
-rw-r--r--   0/0     1254 Sep 29 14:28 2014 dump/OCM/cnaboardmgmt.log
-rw-r--r--   0/0    12202 Sep 29 14:28 2014 dump/OCM/utils-install.log
-rw-r--r--   0/0     2846 Sep 29 14:28 2014 dump/OCM/hbacmd_hba_attr
-rw-r--r--   0/0     2324 Sep 29 14:28 2014 dump/OCM/hbacmd_port_attr
drwxr-xr-x   0/0        0 Sep 29 14:29 2014 dump/CoreDump/
-rw-r--r--   0/0   2266683 Sep 29 14:29 2014 dump/CoreDump/m3000-tvp540-a_10000000c9c07ba0_140929-142855.dmp
-rw-r--r--   0/0    12334 Sep 29 14:29 2014 dump/CoreDump/m3000-tvp540-a_10000000c9c07ba0_140929-142855.txt
-rw-r--r--   0/0      858 Sep 29 14:29 2014 dump/cmds_output
-rw-r--r--   0/0    33617 Sep 29 14:29 2014 dump/kernel_log
-rw-r--r--   0/0     2203 Sep 29 14:29 2014 dump/kernel_config
drwxr-xr-x   0/0        0 Sep 29 14:29 2014 dump/CrashDump/
-rw-r--r--   0/0     2638 Sep 29 14:29 2014 OneCapture-Solaris.html
bash-3.2#


References

<BUG:19149937> - FC HBA BECOMES UNUSABLE DUE TO EMLXS MAILBOX TIMEOUT DURING FIRMWARE UPDATE
<NOTE:1356876.1> - Firmware Update Required. (A Manual Hba Reset Or Link Reset (Using Luxadm Or Fcadm) Is Required
<NOTE:1629921.1> - How To Get a Firmware Dump From an Emulex FC HBA

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback