How to replace a drive in a VSM6 or VSM7 stpool (JBOD):ATR:1533980.1:3

Asset ID:	1-71-1533980.1
Update Date:	2017-12-29
Keywords:

Solution Type Technical Instruction Sure

Solution 1533980.1 : How to replace a drive in a VSM6 or VSM7 stpool (JBOD):ATR:1533980.1:3

Applies to:

StorageTek Virtual Storage Manager System 6 (VSM6) - Version All Versions and later
StorageTek Virtual Storage Manager System 7 (VSM7) - Version 7.0.0 and later
Oracle Solaris on SPARC (64-bit)

Goal

Field procedure to replace a VSM6 stpool drive.

Solution

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

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
   PROBLEM OVERVIEW: How to replace stpool drive in a VSM6 server.

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

--The VSM6 can be online to the customer and does not require to be in any sort of maintenance state.

--Obtain customer approval before performing any maintenance action on VSM6.

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

Connect to the correct node that requires maintenance.
--If the failed drive is in stpool0100 then connect to node 1 to run replacement scripts.
--If the failed drive is in stpool0200 then connect to node 2 to run replacement scripts.

* * * * * * * * IMPORTANT NOTE * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

VSM7 8TB drive PN 7301588 is no longer being produced.

It is unknown how long the exising spares pool will be able to supply these drives for current replacement requirements.

PN 7337414 is a compatible replacement but requires an installed minimum VSM microcode of 7.1.1.06.000 or higher

Do NOT install an 8TB drive PN 7337414 until the VSM is at microcode 7.1.1.06.000 or higher

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

For all VSM6 and VSM7 running app code 7.1.1.01.000 and higher:

For complete details on replacing stpool drive:
Reference the VSM6 or VSM7 Service guides.
Chapter: Servicing VSM6
Section: Replacing a drive in a VSM6/VSM7 stpool0100 or stpool0200

Links to the VSM internal documents can be found on the Tape Support web site under the Tape Products.

For all VSM6 and VSM7 running app code 7.0.0.12.000 and lower a new drive replacement script should be used.

The attachment contains the new script and instructions to install it in the VSM.

Note:

The service manual may indicate logging into the server as root. That is not necessary. Instead run the command using the "sudo" prefix.

sudo /opt/vsm/bin/replace_stpool_drive

cd /opt/vsm/bin

sudo ./replace_stpool_drive

CAUTION: Make sure you remove the correct (failed) drive. Drive release latch and drive LEDs are on opposite sides of the failed drive. See this diagram for further clarification on this caution as it pertains to the DE2-24C JBODs.

OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTION DOES THE FE/CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:

Run the following command to make sure the nodes are still up in the cluster and online.
# /usr/cluster/bin/scstat -g
The service guide has an example of a healthy VSM6 scstat -g output for reference.
Run the following command to verify these services are still online.
# /var/opt/StatusService/scripts/display_svc_info
============> Summary: Services <===============
EXPECTED: All services listed as "online"
online         Nov_29   svc:/application/StatusService:default
online         Nov_29   svc:/system/fmservice:default
online         Nov_29   svc:/system/fmd:default

PARTS NOTE:

REFERENCE INFORMATION:

Attachments

This solution has no attachment