SUNWjfca will not have any bug fixed

Asset ID:	1-72-1009343.1
Update Date:	2011-01-10
Keywords:

Solution Type Problem Resolution Sure

Solution 1009343.1 : SUNWjfca will not have any bug fixed

Applies to:

Sun Storage 3310 Array
Sun Storage 3320 SCSI Array
Sun Storage 3510 FC Array
Sun Storage 3511 SATA Array
Sun Storage 6130 Array
All Platforms

Symptoms

When a customer connects a SunStorEdge[TM] array to SUNWjfca hba, they may meet known bugs which will not be corrected by the provider AMCC .

In some cases there are customers who connect SunStoEdge[TM] arrays to SUNWjfca. These HBAs are either newly bought, or already installed on hosts.

According to the configuration used (ie: loop or Fabric), they may have Fiber Channel problems with scsi errors when overloaded and/or poor performance.

These problems have been encountered only on shared LOOP configuration.

Changes

N/A

Cause

Known bugs which will not be corrected by the provider AMCC .

Solution

Sun Bug: 6255879
3510 shared with 8 direct connected hosts has the following scsi errors:


Apr  7 11:59:27 nas0003 jfca: [ID 276417 kern.info] jfca1: Link Down
Apr  7 11:59:27 nas0003 jfca: [ID 277441 kern.info] jfca3: Link Down
Apr  7 11:59:27 nas0003 scsi: [ID 107833 kern.warning] WARNING:/scsi_vhci/ssd@g600c0ff00000000007ff4e1c7dd48b00 (ssd24):
Apr  7 11:59:27 nas0003          SCSI transport failed: reason 'tran_err': retrying command
Apr  7 11:59:28 nas0003 jfca: [ID 551955 kern.info] jfca1: Auto-Configured as Private Loop port
Apr  7 11:59:29 nas0003 jfca: [ID 359586 kern.info] jfca1: Link Up: 2Gig Loop
Apr  7 11:59:29 nas0003 fctl: [ID 999315 kern.warning] WARNING: fctl(1): AL_PA=0x2 doesn't exist in LILP map
Apr  7 11:59:38 nas0003 jfca: [ID 780306 kern.info] jfca3: Link Failure event detected
Apr  7 11:59:40 nas0003 jfca: [ID 302589 kern.info] jfca3: Auto-negotiating link speed
Apr  7 11:59:40 nas0003 jfca: [ID 556780 kern.info] jfca3: Topology configuration is set to Auto-Negotiate
Apr  7 11:59:55 nas0003 jfca: [ID 302589 kern.info] jfca3: Auto-negotiating link speed
Apr  7 11:59:55 nas0003 jfca: [ID 556780 kern.info] jfca3: Topology configuration is set to Auto-Negotiate
Apr  7 11:59:57 nas0003 jfca: [ID 276417 kern.info] jfca1: Link Down
Apr  7 11:59:57 nas0003 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600c0ff00000000007ff4e1c7dd48b01 (ssd23):
Apr  7 11:59:57 nas0003          SCSI transport failed: reason 'tran_err': retrying command
Apr  7 11:59:57 nas0003 jfca: [ID 551963 kern.info] jfca3: Auto-Configured as Private Loop port
Apr  7 11:59:57 nas0003 jfca: [ID 551955 kern.info] jfca1: Auto-Configured as Private Loop port
Apr  7 11:59:58 nas0003 jfca: [ID 551963 kern.info] jfca3: Auto-Configured as Private Loop port
Apr  7 11:59:58 nas0003 last message repeated 1 time
Apr  7 11:59:58 nas0003 jfca: [ID 359586 kern.info] jfca1: Link Up: 2Gig Loop
Apr  7 11:59:59 nas0003 jfca: [ID 841822 kern.info] jfca3: Link Up: 2Gig Loop
Apr  7 12:00:31 nas0003 jfca: [ID 276417 kern.info] jfca1: Link Down
Apr  7 12:00:31 nas0003 jfca: [ID 277441 kern.info] jfca3: Link Down
Apr  7 12:00:32 nas0003 jfca: [ID 551955 kern.info] jfca1: Auto-Configured as Private Loop port
Apr  7 12:00:32 nas0003 jfca: [ID 551963 kern.info] jfca3: Auto-Configured as Private Loop port
Apr  7 12:00:33 nas0003 jfca: [ID 359586 kern.info] jfca1: Link Up: 2Gig Loop
Apr  7 12:00:33 nas0003 jfca: [ID 841822 kern.info] jfca3: Link Up: 2Gig Loop
Apr  7 12:00:33 nas0003 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600c0ff00000000007ff4e1c7dd48b01 (ssd23):
Apr  7 12:00:33 nas0003          Error for Command: write(10)             Error Level: Retryable
Apr  7 12:00:33 nas0003 scsi: [ID 107833 kern.notice]     Requested Block: 40384                  Error Block: 40384
Apr  7 12:00:33 nas0003 scsi: [ID 107833 kern.notice]     Vendor: SUN                                Serial Number: 1C7DD48B-01

Sun Bug: 6329781
6130 shared with two direct-connected hosts
Note that SUNWjfca is not listed as supported HBA for the array , although SFK support them.

Sep 22 10:11:05 pythie1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b800018928e0000327342c4bfe5   (ssd11):----$modifiedBy----
Sep 22 10:11:05 pythie1         SCSI transport failed: reason 'tran_err': retrying command----$modifiedBy----
Sep 22 10:19:58 pythie1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b800018928e0000327242c4bd69   (ssd9):----$modifiedBy----
Sep 22 10:19:58 pythie1         SCSI transport failed: reason 'tran_err': retrying command----$modifiedBy----
Sep 22 10:20:58 pythie1 scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):----$modifiedBy----
Sep 22 10:20:58 pythie1         /scsi_vhci/ssd@g600a0b800018928e0000327242c4bd69 (ssd9): Command Timeout on path   /pci@1e,600000/SUNW,jfca@3/fp@0,0 (fp1)----$modifiedBy----
Sep 22 10:20:58 pythie1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b800018928e0000327242c4bd69   (ssd9):----$modifiedBy----
Sep 22 10:20:58 pythie1         SCSI transport failed: reason 'timeout': retrying command----$modifiedBy----
Sep 22 10:21:34 pythie1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b800018928e0000327242c4bd69
......

After basic troubleshooting included SFK patches upgrade, the only way to recover the issue is to replace the faulty HBA by SUNWqlgc. .

Product
Sun StorageTek 6130 Array (SATA)
Sun StorageTek 6130 Array
Sun StorageTek 3511 SATA Array
Sun StorageTek 3310 SCSI Array
Sun StorageTek 3320 SCSI Array
Sun StorageTek 3510 FC Array

Internal Comments
The following is strictly for the use of Sun employees:

It is mentioned by PDE in the bug for 6130 that these HBA are withdrawn and not supported by the
AMCC provider . Hence new issues where this brand of HBA are involved will be resolved only by
their replacement. A swap out plan is on going for this issue
SUNWjfca, SUNWqlgc timeout, tran_err, Link Down
Previously Published As
82814

Change History
Date: 2005-10-10
User Name: 7058
Action: Approved

Attachments

This solution has no attachment