StorageTek Virtual Storage Manager System 7 (VSM7)
 
StorageTek Virtual Storage Manager System 6 (VSM6)
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
 

In this Document

Goal

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Internal FSE procedure

Applies to:

Goal

 How to collect VSM6 Support file bundle and State Save files for sending to VSM support for remote troubleshooting

Solution

 DISPATCH INSTRUCTIONS
   WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?: VSM6 trained, T4 server, Solaris 11
   TIME ESTIMATE: 240 minutes

• Can be 60-240 minutes

   TASK COMPLEXITY: 3

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
   PROBLEM OVERVIEW: How to collect VSM6 Support file bundle and State Save files for sending to VSM support for remote troubleshooting

   WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?: Must be able to get to VSM6 server Solaris command line.

   WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE?:

Connect and Log into the server on each node (logs are to be collected on both nodes unless otherwise instructed

A SFB will generate whenever a hardware problem or ASR initiated action occurs.  A daily SFB occurs at 14:10 (node1) and 14:25 (node2).

       Locate the latest Support File Bundle (SFB) on each node in the following directory:

             /var/opt/StatusService/output/archive

       The SFB format is <VSM S/N>-<node>-<date>_<time>.tar.bz2) 

             example: AK00060070-vsmpriv1-2017.07.13_19.33.08.tar.bz2

       Copy the SFB from each node to a PC using a file transfer utility (i.e. WinSCP)

If a manual SFB is necessary:

       To generate a manual SFB, enter the following command:

              sudo /var/opt/StatusService/scripts/ManualNoASR

              The process takes approximately 10-15 minutes to create the SFB

For more information regarding a VSM manual SFB, see Knowledge article:

VSM6, VSM7 - How to initiate a manual ASR to collect Support File Bundle (SFB) (Doc ID 1510362.1)

A Statesave will occur if the node reboots, typically due to a microcode initiated problem.

       Run the following command on each node to create a current statesave:

               /opt/vsm/bin/collectLocal.pl   

              When completed, the message Data Collection COMPLETED, will occur.

       The statesave format is vsmss.<VSM S/N>-<node>-<date>_<time>.tar.gz. 

              A created statesave will indicate “nokill” after the time.

              example: vsmss.AK00060070-vsmpriv1-2017.07.10_07.17.10nokill.tar.gz

       Using a file transfer utility, copy all of the statesave files in the following directory to the PC:

               /var/cores/collectedFiles

               The directory will contain all of the statesaves that have occurred since the last time collectLocal.pl was run.

        Engineering may require some, or all of these statesaves. 

        Each statesave has a date-time related to the time of the failure.  Be prepared to send those related to the time of the current problem.

         (NOTE: the last 20 system-generated statesaves are saved in directories /var/cores/current.*)

Attach all files to the SR for VSM Support review

        Visit "Uploading Files to Oracle Support (DOC ID 1547088.2)" for further information.

OBTAIN CUSTOMER ACCEPTANCE
   WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE?: N/A

PARTS NOTE: N/A

REFERENCE INFORMATION: Refer to the latest VSM6 Installation, Configuration and Service Guide or VSM7 Installation, Configuration and Service Guide for more details

This solution has no attachment