VTL - How to replace a controller in a VTL attached disk array

Asset ID:	1-71-1382836.1
Update Date:	2012-01-07
Keywords:

Solution Type Technical Instruction Sure

Solution 1382836.1 : VTL - How to replace a controller in a VTL attached disk array

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 Storage Appliance - Version: 4.0 - Build 1221 to 4.0 - Build 1221 [Release: 4.0 to 4.0]
Sun StorageTek VTL Prime System - Version: 1.0 - Build 1813 to 1.1 - Build 2076 [Release: 1.0 to 1.0]
Information in this document applies to any platform.

Goal

Provide special instructions for replacing a VTL attached disk array controller.

Oracle VTL servers that use LSI storage arrays (FLX280/380, 6140, 6540 and 2540) and 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 replace array controller on disk arrays:

NOTE: This must be done by Oracle personnel. Please open support ticket to request this activity.
Only certain array firmware levels are certified by VTL Engineering for VTL - Question, please contact VTL support to verify the certified firmware for the arrays.
Internal doc VTL Compatible FW

Collect Xray
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.
Suspend all jobs (or let jobs complete) on backup application client hosts that connect to VTL server(s)
Stop VTL processes:

Note: If failover server in configuration, suspend failover on both servers first, then stop processes on both VTL server(s):
# vtl stop all

Refer to VTL Users Guide for details.
Replace array controller (see Disk Array Maintenance manual for details or CAP doc id 1312958.1)
NOTE: Use part number for controller only and not for the "Controller Assembly"
Using SANtricity, verify AVT is enabled (see SANtricity online help for details)

If disabled, enable AVT (please contact Midrange disk support for assistance if needed)

Reboot VTL servers:
Can be done via VTL Console (right click server name>System Maintenance>Reboot), or from Solaris commandline:
# init 6
Check if all the vtl modules started or not from the VTL console GUI or with the following command from Solaris:
#sms -v
Note: If failover server in configuration, resume failover on both servers, after server come up completely. Check the Failover status is in UP status - (FailOverStatus: 1(UP)
Confirm that there are no offline devices
Check SANtricity, make sure all the LUNS are on their preferred path (see SANtricity online help for details)
Take another Xray just to keep as reference for future need.
Resume backup application job schedules.

Attachments

This solution has no attachment