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-1535732.1
Update Date:2017-08-03
Keywords:

Solution Type  Problem Resolution Sure

Solution  1535732.1 :   Sun Storage 6000 and 2500 Arrays Reporting ASC: 0x3f (inquiry data has changed), ASCQ: 0x3, FRU: 0x0 Errors  


Related Items
  • Sun Storage 6580 Array
  •  
  • Sun Storage 6180 Array
  •  
  • Sun Storage 2510 Array
  •  
  • Sun Storage 2540 Array
  •  
  • Sun Storage 6780 Array
  •  
  • Sun Storage 2540-M2 Array
  •  
  • Sun Storage 6140 Array
  •  
  • Sun Storage 2530 Array
  •  
  • Sun Storage Flexline 380 Array
  •  
  • Sun Storage 2530-M2 Array
  •  
  • Sun Storage 6540 Array
  •  
  • Sun Storage 6130 Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-6908841211>

Applies to:

Sun Storage 2510 Array - Version Not Applicable and later
Sun Storage 6140 Array - Version Not Applicable and later
Sun Storage 2530 Array - Version Not Applicable and later
Sun Storage 2540 Array - Version Not Applicable and later
Sun Storage 6130 Array - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

The messages file on the data server attached to a Sun Storage 2500 or 6000 array is logging error messages against the array.

server-name         Error for Command: write(10)               Error Level: Retryable
server-name scsi: [ID 107833 kern.notice]   Requested Block: 102238942        Error Block: 102238942
server-name scsi: [ID 107833 kern.notice]   Vendor: SUN                       Serial Number:
server-name scsi: [ID 107833 kern.notice]   Sense Key: Unit Attention
server-name scsi: [ID 107833 kern.notice]   ASC: 0x3f (inquiry data has changed), ASCQ: 0x3, FRU: 0x0
  • The I/O error will occur on different block locations.
  • The Error Level is Retryable
  • The ASC and ASCQ codes is always the same.    ASC: 0x3f (inquiry data has changed), ASCQ: 0x3
  • No other types of errors are being logged, (Bus Resets, Fatal r/w, Timeouts, etc..)

Changes

 There have been no changes to the server or the array. The array is not reporting any alarms.  There is no interruption to I/O.  Everything appears to be fine.

Cause

The errors are caused by a link failure with the Out-Of-Band (oob) management connection to the array. If Common Array Manager (CAM) host loses its oob connection to either controller, the data host will log this error. The error has nothing to do with in-band I/O. It's the network connection that needs troubleshooting. <Document 1008327.1>  How to validate Sun StorageTek[TM] 2500, Sun Storage[TM] 6000, and Flexline Array Controller Out of Band Communication may be used to validate the oob management connection on the array.  

 

Solution

There is no firmware fix or work around available for this issue.

These errors can be ignored if it generated when there was a link up/down event on management ports on the controller.

The real solution to this problem is to re-establish the link between the CAM server and the array.

 

 

Following bugs are reported against this issue and marked as fix unverified because no new reports after 7.60.53.10 release. This is not true because recently one customer reported similar issue and recent lab tests prove the issue still exists on latest f/w 07.60.63.10.

See 15656502SUNBT6969709 MANAGEMENT PORT LINK DOWN/UP TRIGGERING CONNECTED DATA HOSTS SEEING for the 2500

See 15629157 SUNBT6934384 MANAGEMENT PORT LINK DOWN/UP TRIGGERING CONNECTED DATA HOSTS SEEING for the 6000

Since the product is EOLed there will be no effort made to update these bugs to get a fix.


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