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 process for FSE

Applies to:

Goal

 How to upgrade VSM6 application code

Solution

  DISPATCH INSTRUCTIONS
   WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?: VSM6/7 trained, T4/7 server, Solaris 11
   TIME ESTIMATE: 120 minutes
   TASK COMPLEXITY: 3

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
   PROBLEM OVERVIEW: How to upgrade VSM6/VSM7 application code

   WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?:

     • The VSM6/VSM7 VTSS must be operational with no failed components or no failed VSM resources.
     • For a disruptive upgrade, the VSM VTSS mus have no host access and offline through VTCS.
     • FSE must be able to connect to the VSM servers and access the Solaris command line and verify all VSM processes are online and fully operational.

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

    1. Verify the planned upgrade action and schedule with the customer

         • For a disruptive upgrade, the VSM6 must be offline to the customer.
         • For a non-disruptive upgrade, each node is upgraded individually and is taken offline one at a time.
            (Refer to release notes for procedure options.)

    2. Collect VSM6/VSM7 Support File Bundle (SFB)

         • Refer to doc id 1511702.1 for details on collecting SFB from both nodes.
         • Verify the machine has no failures before starting the upgrade.
         • Run the VSM command scstat to verify that all resources are operational.

    3. Download the VSM6/VSM7 code from System Assurance Center (SAC)
         • https://sac.us.oracle.com/download/index.html

    4. Upgrade microcode following the procedures in the release notes.
         • Review the microcode release notes packaged with the code to determine upgrade options and procedures.

    5. Verify upgrade completion success
         • Run scstat command to verify VSM6 is online and fully operational with all resources.
         • Verify the code version using VSM6 CLI command “show system all”
         • Take a manual SFB on both nodes and upload to SPLAT.

OBTAIN CUSTOMER ACCEPTANCE
 

  WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE?:

     • Have the customer vary all VTCS paths taken offline, back online.
     • Have the customer vary host FICON devices and paths back online
     • Verify that the customer data processing on the VSM is operational.

PARTS NOTE: N/A

REFERENCE INFORMATION:
Refer to System Assurance Center (SAC)
Refer to VSM6 Installation, Configuration and Service Guide

Refer to VSM7 Installation, Configuration and Service Guide

This solution has no attachment