Sun StorageTek VSM System
 
Sun StorageTek V2X SVA Disk System
 
Sun StorageTek VSM5 System
 

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

FSC79A5 pfa log overflow  FSC 79A5

Applies to:

Purpose

Determine cause of FSC79A5:

The PFAELG4A.DAT file has grown beyond its size threshold.
FRL on the ISP has renamed the file to PFAELG4B.DAT and
has created a new PFAELG4A.DAT file. If a PFAELG4B.DAT file
existed, it was renamed to PFAELG4C.DAT. If a PFAELG4C.DAT
file existed, it was renamed to PFAELG4D.DAT. If a
PFAELG4D.DAT file existed, it was deleted.

Troubleshooting Steps

 After downloading base files, use the following procedure to identify the issue.

1. Upload base files to SPLAT (refer to doc id 1399676.1(Internal) and check the HIC_STAT.DIA and/or HIC.DMP 

files and verify that the files are indeed for the machine serial number 

documented in the case.

2. Check the same files and note the level of microcode in use. This can be 
important because some errors are addressed in more recent levels of microcode.

3. Check the PFAELG4B.CNT file and determine the error or errors that logged most 

frequently (have the highest quantity of errors logged).

4. Perform an extract of the errors identified in step 2.  

There are multiple extraction tools available.  The most common are as follows:

xfsc – extracts error data from the PFAELG4A files, output is xxxx.out
xfscb – extracts error data from the PFAELG4B files, output is xxxx.b_out
xfscc – extracts error data from the PFAELG4C files, output is xxxx.c_out
xfscd – extracts error data from the PFAELG4D files, output is xxxx.d_out
(where xxxx = the fsc being extracted)

5. Examine the PFAELG4B.DOM file and the extracted error log information and 

look for a common pattern (domain information is found at the end of the files 

created in step 3).  Can you identify a single FRU which is logging a higher 

number of events than comparable FRUS?  If yes, then that FRU may be marginal 

and may need to be replaced as a proactive measure (judgment call).  

However, if the errors are well distributed across multiple FRUs then check to 

see if a more recent level of microcode has a fix for these errors.

6. It may be appropriate to repeat steps 3 through 5 for each of the error log 

files available.

7. Make a determination as to what if any action needs to be taken.  Update the 

case with your findings and if appropriate dispatch it to local support to have 

them follow your action plan.  If no action is required update the case with your

findings and close the case.

PLEASE NOTE: 
The steps above may not be adequate to islolate the source of FSC 8FC1 or FSC 8FC2 errors.
For help in diagnosing these interface errors please click on the following link:
FSC 8FC1 and/or FSC 8FC2 diagnostic supplement.

This solution has no attachment