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-71-1146359.1
Update Date:2010-11-22
Keywords:

Solution Type  Technical Instruction Sure

Solution  1146359.1 :   VSM-How to downgrade microcode on VSM4 VSM5  


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


VSM- How to downgrade from D02.05.xx.xx microcode

In this Document
  Goal
  Solution


Oracle Confidential (PARTNER). Do not distribute to customers
Reason: Microcode downgrade procedure

Applies to:

Sun Storage VSM System - Version: Not Applicable and later   [Release: NA and later ]
Information in this document applies to any platform.
The release of VSM4/5 code D02.05.xx.xx (D25xx), Sun engineering altered the VTSS Config files in support of 32 RTD’s.

Goal

Downgrade microcode on VSM hardware product.

Solution

Procedure one:
Previous level still exists on the VTSS.
NOTE: ONLY use these methods if there have been no configuration changes or FRU replacements. If there is any uncertainty, delete the old SRL and follow procedure 2 (below).
1) VTSS offline from the customer
2) IML VIP on to the VTSS (VSM4 -floppy version 4.2.1.11 or
higher)
3) Select and activate the pre-D25xx SRL from the Software System Directory Display screen
4) EPO the VTSS
5) Remove the VIP floppy (VSM4 only)
6) IML the VTSS back onto functional code
7) Verify the VTSS is on the desired SRL and is 100%
8) Have the customer vary the VTSS back online
9) Vary the RTDs and VTDs online

Procedure two:
Previous level does not exist on the VTSS
Because there is a change in the config file version, backing down to a Code version which does not exist is time consuming
1) Preload the desired SRL onto the VTSS
2) Manually record the following items:
a) All Nearlink and Clink interface configuration information.
b) The CSRC call home number information
NOTE: Subsystem name and RTD names are reloaded from VTCS and are not part of the Configuration.
3) Get the VTSS offline from the customer
4) IML VIP on to the VTSS (VSM4 -floppy version 4.2.1.11 or higher)
5) Select and activate the pre-D25xx SRL from the Software
System Directory Display screen
6) EPO the VTSS
7) Remove the VIP floppy (VSM4 only)
8) IML the VTSS back onto functional code
9) Configure all the NEARLINKS and RTD pathing information
10) Verify the VTSS is on the desired SRL and is 100%
11) Perform a path validate to verify RTD information is correct
12) Have the customer vary the VTSS back online
13) Vary the RTDs and VTDs online

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