Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1016471.1
Update Date:2011-05-03
Keywords:

Solution Type  Problem Resolution Sure

Solution  1016471.1 :   VSM - VTSS fails to initialize after SLS6675E with RC=xxxxxx0C  


Related Items
  • Sun StorageTek VSM System
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Tape>Tape Virtualization
  •  

PreviouslyPublishedAs
226247


Applies to:

Sun StorageTek VSM System
All Platforms
***Checked for relevance on 03-05-2011*** (dd-mm-yyyy)

Symptoms

VTSS fails to initialize during VTCS start-up
Lack of SLS6632I VTSS server ready message
Message SLS6675E with RC=6A40FF0C

SLS6608E NO VIRTUAL DEVICES DEFINED FOR VTSS nnnnnnnn
SLS6698I ECAM I/O ERROR ON VTD dddd
SLS6675E VTSS:nnnnnnnn VTD:dddd CONFIGURATION ERROR RC=6A40FF0C
SLS6675E VTSS:XXXXXXXX VTD:DDDDDD CONFIGURATION ERROR RC=RRRRRRRR SUBSYSTEM INFO:ZZZZZ1/ZZZZZ2/ZZZZZ3

Cause

Problem is usually caused by DAC (data assurance check) due to VSM(s) being powered down for move to different location(s). The DAC (Data Assurance Check) errors on the VTSS are preventing ECAM I/O completion.

Solution


The VTSS box has a potential DAC issue. Please contact Oracle VTSS hardware support to have this validated.



Additional Information
Change to environment: New installation of VTSS or VTSS(s) powered down and physically moved to different location(s).


Note:  The return code xxxxxx0C indicates the following:

   1. That there was an available I/O path to the VTD
   2. That an ECAM I/O operation was successfully started
   3. That the I/O operation completed with an error that was not an interface control check

While the above does not specifically indicate a DAC, it does point to the VTSS as the source of the problem.

HSC/VTCS can not establish communications to a VTSS that has an active DAC on it.  The reason for this is that the VTSS is presenting error information in response to any I/O requests.  HSC/VTCS does not know how to handle the error information and assumes the VTSS is not available and continues to initialize without it.  This problem is difficult to recognize since the error indications are not clear on what is really the root cause.  The HSC messages that indicate a DAC are as follows:

SLS6675I with RC=xxxxxx0C for each VTD
SLS6698I with RC=xxxxxx0C for each VTD
SLS6608E is issued
"VTSS server ready" message is not issued                                                                                                                                                                                                                                                   

1. Contact the Field Service engineer (FSE) to check the VTSS op panel and logs for error conditions.

2. The FSE must reset the DACs (refer to internal document 1016272.1) occurring in all VTSSs.

3. After DAC conditions are reset, customer will need to run a VTSS Audit.

If message SLS6675E with RC=6A40FF0C occurs for every VTD followed by message SLS6608E, and none of the steps listed above or responses listed in the VTCS Messages and Codes Manual for message SLS6675E resolve the problem, then this is a VTSS hardware and/or microcode problem. 





References

<NOTE:1016272.1> - How to reset a DAC on a VTSS box

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback