Sun Storage T3 Array
 
Sun Storage T3+ Array
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other
 

- 2.x Firmware
The appropriate method of automating the run of "vol verify" on 2.x or lower
firmware is through StorADE.

- 3.x Firmware
Sun strongly recommends having T3 firmware 3.x "disk_scrubber" parameter set to ON.

-Why is having T3 firmware 3.x "disk_scrubber" parameter set to ON strongly recommend?
The whole point of 3.x having disk_scrubber is to prevent a much bigger issue
of data loss due to multiple disk failure "before" it's too late. The "disk_scrubber" should
NOT be switched off.

 ----------------------------------------------------------------
#!/bin/sh
# t3-auto.sh  -- Script to automate the vol verify vix procedure

 (sleep 5;echo "root";\
sleep 5;echo "[t3 password]";\
sleep 5;echo "vol verify $1 fix rate 8";\
sleep 5;echo "y";\
sleep 5;echo "exit")| telnet [T3 HostName] >> [Log file on Host]
----------------------------------------------------------------

2.Edit the crontab file for the user that has access to the T3
Edit crontab to be execute the shell script created in step 1 above.

<example>
In the following example, the T3 in question has two volumes, v0 and v1.
the goal is to automate a "vol verify" for these two volumes.  The shell
script t3-auto.sh was created as shown above.

- t3-auto.sh
----------------------------------------------------------------
#!/bin/sh
# t3-auto.sh  -- Script to automate the vol verify fix procedure

 (sleep 5;echo "root";\
sleep 5;echo "root";\
sleep 5;echo "vol verify $1 fix rate 8";\
sleep 5;echo "y";\
sleep 5;echo "exit")| telnet t3 >> /var/tmp/t3-verify.log
----------------------------------------------------------------

The following two lines (one for each volume) have been added to
the crontab file.

- crontab

 ----------------------------------------------------------------
00 00 * * * /var/tmp/shima/t3-auto.sh v0
00 03 * * * /var/tmp/shima/t3-auto.sh v1
----------------------------------------------------------------

After the script runs, you can see the following vol verify messages
in the T3 syslog.

 Nov 18 15:58:36 sh06[1]: N: vol verify v0 fix rate 8
Nov 18 15:58:42 sh06[1]: N: Vol verify started for volume (Raid set) v0
Nov 18 17:01:18 sh06[1]: N: Vol verify ended for volume (Raid set) v0
Nov 18 18:58:36 sh07[1]: N: vol verify v1 fix rate 8
Nov 18 18:58:42 sh07[1]: N: Vol verify started for volume (Raid set) v1
Nov 18 20:01:21 sh07[1]: N: Vol verify ended for volume (Raid set) v1

This procedure will be helpful because a check has been added to T3A(New firmware) and
T3B which requires the operator to confirm the 'vol verify' with a "y" prior to execution. The procedure
above provides a means to script the process and provide the answer to the check question below.

 t3:/:<20>vol verify v0 fix rate 8
WARNING - Volume verification can take a significant amount of time.
Continue ? [N]:      <--- need to input "y"

This solution has no attachment