hidden:Replace a tape drive in HPSS: Difference between revisions
From Lsdf
Jump to navigationJump to search
No edit summary |
No edit summary |
||
(17 intermediate revisions by the same user not shown) | |||
Line 11: | Line 11: | ||
'''1. preparation of replacement''' |
'''1. preparation of replacement''' |
||
'''1.1 log-in |
'''1.1 log-in hpss core and hpss gui''' |
||
log in on active hpss core (e.g. hpsscr01 or hpsscr02) |
|||
⚫ | |||
'''1.2 call hpss gui''' |
|||
/opt/hpss/bin/hpssgui.pl & |
/opt/hpss/bin/hpssgui.pl & |
||
'''1. |
'''1.2 set drive "locked"''' |
||
select Monitor: Device/Drive List (if necessary choose Preferences "Movers(tape)") |
HPSS GUI: select Monitor: Device/Drive List (if necessary choose Preferences "Movers(tape)") |
||
select the drive to be replaced |
select the drive to be replaced |
||
set "locked" the drive to be replaced: |
set "locked" the drive to be replaced: Drive Administration-->Lock |
||
after dismount also "lock" the device: Device Administration-->Lock |
|||
'''1. |
'''1.3 drive is ready for replacement''' |
||
'''2. replace the drive in the tape library''' |
'''2. replace the drive in the tape library''' |
||
Line 30: | Line 30: | ||
https://team.kit.edu/sites/scc-sdm/Dokumente/Data_Protection/Hardware/HardwareListDataProtection.xlsx?Web=1 |
https://team.kit.edu/sites/scc-sdm/Dokumente/Data_Protection/Hardware/HardwareListDataProtection.xlsx?Web=1 |
||
'''2. |
'''2.2 documentation of exchange''' |
||
insert documentation of the replacement in LSDF Wiki (System Logs): |
insert documentation of the replacement in LSDF Wiki (System Logs): |
||
http://wiki.scc.kit.edu/lsdf/index.php/hidden:System_Logs_(HPSS,_TSM) |
http://wiki.scc.kit.edu/lsdf/index.php/hidden:System_Logs_(HPSS,_TSM) |
||
Line 36: | Line 36: | ||
'''3. Reconfigure and reactivate the replaced drive''' |
'''3. Reconfigure and reactivate the replaced drive''' |
||
'''3.1 Show the drive configuration in hpss gui |
'''3.1 Show the drive configuration in hpss gui''' |
||
Select the drive |
HPSS GUI: Select the drive |
||
Choose Configure |
Choose Configure |
||
Read field "Drive Address" x,y,z,t |
Read field "Drive Address" x,y,z,t |
||
'''3.2 |
'''3.2 Reconfigure the replaced drive in acsls''' |
||
log-in on acsls mashine (scc-stk-lib01, 172.21.238.64) |
log-in on acsls mashine (scc-stk-lib01, 172.21.238.64) |
||
su - acsss |
su - acsss |
||
⚫ | |||
check configuration of replaced drive in acsls (check if old serial number): |
|||
cmd_proc -ql |
cmd_proc -ql |
||
ACSSA> display drive * -f serial_num |
ACSSA> display drive * -f serial_num |
||
ACSSA>logoff |
ACSSA>logoff |
||
⚫ | |||
reconfigure the replaced drive in acsls (automatically sets new serial number): |
|||
config drive x,y,z |
config drive x,y,z |
||
Line 54: | Line 57: | ||
0 T1D unchanged * 579004007294 |
0 T1D unchanged * 579004007294 |
||
'''NOTICE:''' "drive id" is the number t read from Step 3.1 |
'''NOTICE:''' "drive id" is the number t read from Step 3.1 |
||
⚫ | |||
'''3.3 Add the replaced drive to StorSentry configuration''' |
'''3.3 Add the replaced drive to StorSentry configuration''' |
||
⚫ | |||
Verify, that StorSentry Server sees the new drive via commands sg_map and sg_inq |
Verify, that StorSentry Server sees the new drive via commands sg_map and sg_inq |
||
for example: |
for example: |
||
[root@scc-histor-n01 ~]# sg_map -st -x -i | grep T10000 | cut -f 1 -d " " | while read drive; do echo $drive;sg_inq $drive | grep 57900400xNEW done |
[root@scc-histor-n01 ~]# sg_map -st -x -i | grep T10000 | cut -f 1 -d " " | while read drive; do echo $drive;sg_inq $drive | grep 57900400xNEW; done |
||
... |
... |
||
/dev/sg95 |
/dev/sg95 |
||
Line 66: | Line 68: | ||
Afterwards do an update to the configuration: |
Afterwards do an update to the configuration: |
||
[root@scc-histor-n01 ~]# /opt/histor/storsentry/agent/support/Update_config.sh |
[root@scc-histor-n01 ~]# /opt/histor/storsentry/agent/support/Update_config.sh -force -auto |
||
Start the GUI and verify the exchange, the new drive will be seen by its serial number.<br> |
Start the GUI and verify the exchange, the new drive will be seen by its serial number.<br> |
||
Line 76: | Line 78: | ||
Rename the new drive from "SerialNumber new drive" to DriveName. |
Rename the new drive from "SerialNumber new drive" to DriveName. |
||
Via Administration/Libraries the drive can be put in the right logical ACSLS library. |
Via Administration/Libraries the drive can be put in the right logical ACSLS library. |
||
⚫ | |||
'''3.4. reconfigure the drive in hpss''' |
'''3.4. reconfigure the drive in hpss''' |
||
⚫ | |||
⚫ | |||
field Device Name has not to be changed anymore, since it contains Drive Node WWN which does not change |
|||
log-in HPSS GUI |
|||
select Information: Drive Info at the right, change SN in field comment |
|||
⚫ | |||
Read field "Mover" "that is the mover the drive is connected to" |
|||
⚫ | |||
log-in on the mover |
|||
ls -l /dev/hpss --> note the new SerialNumber |
|||
HPSS GUI: change field configure-->Device Name with the new device read from mover |
|||
Press '''Update''' at the bottom of the window |
Press '''Update''' at the bottom of the window |
||
'''3.5. unlock the drive in hpss''' |
'''3.5. unlock the drive in hpss''' |
||
HPSS GUI: Devices and Drives-->select the drive |
HPSS GUI: Devices and Drives-->select the drive |
||
⚫ | |||
Device Administration-->Unlock |
Device Administration-->Unlock |
||
⚫ | |||
'''3.6 check documentation of drive exchange in LSDF Wiki (System Logs)''' |
'''3.6 check documentation of drive exchange in LSDF Wiki (System Logs)''' |
||
Check if exchange was documented: |
Check if exchange was documented: |
||
http://wiki.scc.kit.edu/lsdf/index.php/hidden:System_Logs_(HPSS,_TSM) |
http://wiki.scc.kit.edu/lsdf/index.php/hidden:System_Logs_(HPSS,_TSM) |
||
'''3.7 Update Device Name on the StorSentry GUI''' |
|||
Reboot Storsentry, if neccessary, to add the new drive into the scsi layer |
|||
Afterwards do an update to the configuration if the drive is not seen |
|||
[root@storsentry-test ~]# /opt/histor/storsentry/agent/support/Update_config.sh |
|||
Start the GUI and verify the exchange, the new drive will be seen by its serial number. |
|||
StorSentry GUI: |
|||
Administration: Log in (no password) |
|||
Rename the replaced drive from DriveName to DriveName-removed. |
|||
Rename the new drive from "SerialNumber of the new drive" to DriveName. |
|||
----[[ hidden:HPSS|<small>back to HPPS main page</small>]] |
----[[ hidden:HPSS|<small>back to HPPS main page</small>]] |
Latest revision as of 11:36, 24 September 2020
Replace a tape drive in HPSS
A call at Oracle should be generated automatically for T10KD drives.
Otherwise open a service request at Oracle https://support.oracle.com with the Tray Serial Number.
The Tray Serial Number of the drive can be determined via SL-Console or in file
https://team.kit.edu/sites/scc-sdm/Dokumente/Data_Protection/Hardware/HardwareListDataProtection.xlsx?Web=1
When the call at Oracle was opened, please set the Icinga State for the Check "Drive_Trap" of the corresponding library to OK: https://icinga.scc.kit.edu/icinga-web
1. preparation of replacement 1.1 log-in hpss core and hpss gui log in on active hpss core (e.g. hpsscr01 or hpsscr02) /opt/hpss/bin/hpssgui.pl & 1.2 set drive "locked" HPSS GUI: select Monitor: Device/Drive List (if necessary choose Preferences "Movers(tape)") select the drive to be replaced set "locked" the drive to be replaced: Drive Administration-->Lock after dismount also "lock" the device: Device Administration-->Lock 1.3 drive is ready for replacement
2. replace the drive in the tape library 2.1 Physical exchange Physical exchange of the drive is done by oracle engineer. If neccessary, set the IP adress, documented in https://team.kit.edu/sites/scc-sdm/Dokumente/Data_Protection/Hardware/HardwareListDataProtection.xlsx?Web=1 2.2 documentation of exchange insert documentation of the replacement in LSDF Wiki (System Logs): http://wiki.scc.kit.edu/lsdf/index.php/hidden:System_Logs_(HPSS,_TSM)
3. Reconfigure and reactivate the replaced drive 3.1 Show the drive configuration in hpss gui HPSS GUI: Select the drive Choose Configure Read field "Drive Address" x,y,z,t 3.2 Reconfigure the replaced drive in acsls log-in on acsls mashine (scc-stk-lib01, 172.21.238.64) su - acsss check configuration of replaced drive in acsls (check if old serial number): cmd_proc -ql ACSSA> display drive * -f serial_num ACSSA>logoff reconfigure the replaced drive in acsls (automatically sets new serial number): config drive x,y,z Drive id Old Type New Type chg Drive Serial Number -------- -------- -------- ----------------------- 0 T1D unchanged * 579004007294 NOTICE: "drive id" is the number t read from Step 3.1 3.3 Add the replaced drive to StorSentry configuration Verify, that StorSentry Server sees the new drive via commands sg_map and sg_inq for example: [root@scc-histor-n01 ~]# sg_map -st -x -i | grep T10000 | cut -f 1 -d " " | while read drive; do echo $drive;sg_inq $drive | grep 57900400xNEW; done ... /dev/sg95 Unit serial number: 57900400xNEW Note: In this case device /dev/sg95 is used for the new drive. Afterwards do an update to the configuration: [root@scc-histor-n01 ~]# /opt/histor/storsentry/agent/support/Update_config.sh -force -auto Start the GUI and verify the exchange, the new drive will be seen by its serial number.
If the new drive is not seen by its serial number, a reboot of the StorSentry Server might help to add the new drive to the scsi layer. Rename the drive via the GUI: Administration: Log in (no password) Rename the old drive from DriveName to DriveName-removed. Rename the new drive from "SerialNumber new drive" to DriveName. Via Administration/Libraries the drive can be put in the right logical ACSLS library. 3.4. reconfigure the drive in hpss HPSS GUI: Devices and Drives-->select the drive field Device Name has not to be changed anymore, since it contains Drive Node WWN which does not change select Information: Drive Info at the right, change SN in field comment Press Update at the bottom of the window 3.5. unlock the drive in hpss HPSS GUI: Devices and Drives-->select the drive Drive Administration-->Unlock Device Administration-->Unlock 3.6 check documentation of drive exchange in LSDF Wiki (System Logs) Check if exchange was documented: http://wiki.scc.kit.edu/lsdf/index.php/hidden:System_Logs_(HPSS,_TSM)