Asset ID:	1-71-1014157.1
Update Date:	2011-09-22
Keywords:

---

Solution Type  Technical Instruction Sure

Solution  1014157.1 :   VTL - What is the VTL Procedure for Upgrading Disk Array Firmware?  


PreviouslyPublishedAs
220492

Applies to:

Sun StorageTek VTL Plus Storage Appliance - Version: 1.0 - Build 1323 to 2.0 - Build 1656 - Release: 1.0 to 2.0
Sun StorageTek VTL Prime System - Version: 1.0 - Build 1813 to 1.1 - Build 2076   [Release: 1.0 to 1.0]
All Platforms

Goal

This technical instruction contains information and instructions related to LSI disk array upgrades for disk arrays behind Sun VTL servers.
Oracle VTL servers that use LSI storage arrays like 6140, 6540 and 2540 are tested with specific releases of array firmware, and only upgrades to tested/certified versions of array firmware are allowed behind Oracle VTL appliances.

Solution

Recommended VTL procedure to update firmware on disk arrays:

NOTE: This must be done by Oracle personnel.  Please open support ticket to request this activity.

1. Verify the array Firmware level you are upgrading to is certified by VTL - Contact the VTL support to verify the certified firmware for the arrays.
Internal doc VTL Compatible FW

2. Get Xray

3. Take backup of VTL configuration

For VTL+ 1.0 see VTL Users Guide for details
For VTL+ 2.0 (Console GUI option was removed) tar up /usr/local/vtl/etc directory and offload to a safe place.

4. Suspend all jobs (or let jobs complete) on backup application client hosts that connect to VTL server(s)

5. Stop VTL processes servers:
Note: If failover server in configuration, suspend failover on both servers, then stop processes on both VTL server(s):
   # vtl stop all
   Refer to VTL Users Guide for details

6. Upgrade storage firmware (see Disk Array Maintenance manual for details)

7. Using SANtricity, verify AVT is enabled (see SANtricity online help for details)
a. If disabled, run AVT enabling script (to obtain script, please contact OS disk support)
Scripts are SANtricity version specific, be sure to obtain proper version.

8. Reboot VTL servers:
Can be done via VTL Console (right click server name>System Maintenance>Reboot), or from Solaris commandline:
   # init 6  

Note: If failover server in configuration, resume failover on both servers, after server come up completely.
 

9. Confirm that there are no offline devices

10. Check SANtricity, make sure all the LUNS are on their preferred path (see SANtricity online help for details)

11. Resume backup application job schedules.



Attachments

This solution has no attachment