Sun StorageTek VSM System
 

PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VTL
 
PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VSM
 

Steps to analyze base file to determine RTD, MVC, VTV which caused the warmboot.

In this Document

Symptoms

Cause

Solution

Created from <SR 3-3623862983>

Applies to:

Symptoms

VSM took a 8ECB statesave
FSC8F8A_RTDM_RECALL_TIMEOUT_IMMINENT
CHK0 FSC8ECB_RTDM_MIGRATE_OR_RECALL_DATA_XFER_TIMEOUT
Warmboot occurred

Cause

The VTSS detected a stalled recall or migrate task to a RTD.

Solution

- Move base files on zenobia.
- Crunch the files using script: crunch_it all
- Create a nearlink report using script: taperpt
- Review the nlkout.txt looking for the 8ecb event.
  The 8ECB indicates the RTD task has stalled for 15 minutes before the statesave.  You should see three FSC 8F8A or FSC 8F8B events exactly 5,10, and 15 minutes before the  FSC 8ECB
  
   Example below:
   10:05:11 FSC8F8A_RTDM_RECALL_TIMEOUT_IMMINENT
   10:10:11 FSC8F8A_RTDM_RECALL_TIMEOUT_IMMINENT
   10:15:11 FSC8F8A_RTDM_RECALL_TIMEOUT_IMMINENT
   10:20:11 CHK0 FSC8ECB_RTDM_MIGRATE_OR_RECALL_DATA_XFER_TIMEOUT
   NOTE: this is an example id recall, event could also be migrate task!

- Review the PFAELG4A.DMP file for the 8F8A or 8F8B that match the time stamps identified in the previous steps:

   The MVC, VTV, RTD is in the extended sense bytes:
   * MVC in bytes 0-5 (in hex)
   * VTV in bytes 6-11 (in hex)
   * RTD is last byte in the record

   EXAMPLE: 
   Entry FSC = 8f8a Submitted by an IUP
   fsc define = FSC8F8A_RTDM_RECALL_TIMEOUT_IMMINENT
   Extended Sense Data: (hex)
   e5 f1 f8 f5 f8 f5 c4 f1 f5 f3 f8 f3 53 a3 50 00
   31 9a 60 00 65 00 00 00 00 00 00 00 00 00 00 01
   MVC = e5 f1 f8 f5 f8 f5 = V18585
   VTV = c4 f1 f5 f3 f8 f3 = D15383
   RTD = 01 (as displayed on the RTD screen of the VTSS.

- Review badrtds.txt and nlkout.txt files to see if the RTD or MVC have any history of being defective.

This solution has no attachment