[Info-vax] MSA1000 on ES47 using OpenVMS V7.3-2 Change Battery

[will.lee at connecmax.com]

On Friday, August 22, 2014 at 3:46:16 PM UTC+8, alan.h... at de.atu.eu wrote:
> Hello,
> 
> I have a question regarding MSA1000.
> 
> We have two identical towers called ALPHA2 and ALPHA3 which form a Cluster (together with an ALPHA4 - not relevant here). In each tower there is (amongst other things)
> - ES47  - we are using  OpenVMS V7.3-2
> - TWO SAN-Switches
> - TWO MSA100, whereby one is ACTIVE and the other is STANDBY Software 4.48
> - TWENTYTWO DISKS (all identical, each ca. 146GB).
> 
> The disks in each tower are completely identical to each other (Shadowing)
> 
> It has been working for years and still works, but I wanted to change the batteries in the four MSA Controllers so therefore need to do something which I have never needed to do before. 
> 
> We have 6 logical disks called DSA20, DSA21...DSA25 For example
> 
> Device                  Device           Error    Volume         Free  Trans Mnt
>  Name                   Status           Count     Label        Blocks Count Cnt
> DSA20:                  Mounted              0  ALPHASYS     171854650   656   2
> $1$DGA220:    (ALPHA2)  ShadowSetMember      0  (member of DSA20:)
> $1$DGA320:    (ALPHA2)  ShadowSetMember      0  (member of DSA20:)
> 
> The $1$DGA2xx Disks are in the ALPHA2 tower. 
> The $1$DGA3xx Disks are in the ALPHA3 tower.
> 
> If I use SYS$ETC:MSA_UTIL, I see four Controllers
> $1$GGA200 (Standby) and $1$GGA201 (Active)  which are the two controllers in the ALPHA2 tower.
> $1$GGA300 (Active)  and $1$GGA301 (Standby) which are the two controllers in the ALPHA3 tower.
> 
> MSA> set controller $1$GGA200
> MSA> show unit 20
> 
> Unit 20:
> In PDLA mode, Unit 20 is Lun 21.
> Unit Identifier: 220
> HSG Unit Identifier: 220
> Device Identifier: 01000010:6008-05F3-0016-0AC0-0000-0000-A1E1-0003
> Cache status      : enabled
> Max Boot Partition: Unknown
> Volume status     : VOLUME OK
> 2 Data Disk(s) used by lun 21:
>    Disk 0: Partition 0; (SCSI bus 0, SCSI id 0)
>    Disk 100: Partition 0; (SCSI bus 1, SCSI id 0)
> Spare physical drives:
> 2 Spare Disk(s) used by lun 5376:
>    Disk 215: (SCSI bus 2, SCSI id 15)
>    Disk 315: (SCSI bus 3, SCSI id 15)
> Logical Volume Raid Level: RAID 1.  Mirroring
>                            stripe_size=128.0KB
> Logical Volume Capacity : 136.73 [146.81] GB
> 
> MSA> set controller $1$GGA300
> MSA> show unit 20
> 
> Unit 20:
> In PDLA mode, Unit 20 is Lun 21.
> Unit Identifier: 320
> HSG Unit Identifier: 320
> Device Identifier: 01000010:6008-05F3-0016-33A0-0000-0000-F293-0007
> Cache status      : enabled
> Max Boot Partition: Unknown
> Volume status     : VOLUME OK
> 2 Data Disk(s) used by lun 21:
>    Disk 0: Partition 0; (SCSI bus 0, SCSI id 0)
>    Disk 100: Partition 0; (SCSI bus 1, SCSI id 0)
> Spare physical drives:
> 2 Spare Disk(s) used by lun 5376:
>    Disk 215: (SCSI bus 2, SCSI id 15)
>    Disk 315: (SCSI bus 3, SCSI id 15)
> Logical Volume Raid Level: RAID 1.  Mirroring
>                            stripe_size=128.0KB
> Logical Volume Capacity : 136.73 [146.81] GB
> 
> 
> The DSA20 is created with the following command
> MOUNT/SYSTEM/CLUSTER/NOASSI DSA20: /SHADOW=($1$DGA220:,$1$DGA320:) ALPHASYS
> 
> I have used the following commands
> On ALPHA3
> $ DISM $1$DGA220 /POLI=MINICOPY
> I can continue working and then
> $ MOUNT /SYST /CLUS /POLI=MINICOPY DSA20 /SHAD=$1$DGA220 alphasys
> The Minicopy works. It takes a couple of minutes - longer, if more copying has to been done. Great
> 
> Similarly. I have used the following commands
> On ALPHA2
> $ DISM $1$DGA320 /POLI=MINICOPY
> I can continue working and then
> $ MOUNT /SYST /CLUS /POLI=MINICOPY DSA20 /SHAD=$1$DGA320 alphasys
> The Minicopy works. It takes a couple of minutes - longer, if more copying has to been done. Great again.
> 
> What I do not understand is, that I thought that the DISM $1$DGA220 /POLI=MINCOPY command would stop all accessing to the drives in the ALPHA2 tower. That is not the case. The drives are still as active as usual (by observing the lights on the disks)
> 
> What I want to do is
> - stop all DISK activity in one tower (without a SHUTDOWN of the ES47)
> - pull the STANDBY MSA1000 and change the batteries
> - put the MSA1000 back in
> - change the Active -> Standby and Standby -> Active (I know how to do that)
> - pull the second MSA1000 and change the batteries
> - put this MSA100 back in
> - change the Active -> Standby and Standby -> Active back to the original order
> - Restart DISK activity in this tower using a MINICOPY
> 
> How do I stop all DISK activity in one tower?
> Am I inputting the DISM command on the wrong machine?
> 
> Yes I do know the MSA1000 are hot-swappable. I have orders to do it the way described above.
> Yes I do know that I could shutdown the whole tower and switch the power off and MINICOPY would still work. I wish to avoid the SHUTDOWN of the ES47
> Presumably I could just pull all disks, change the batteries, push the disks back in and do a MINICOPY - just does not seem right.
> 
> Anyone got ideas?  Thanks

Dear Friend,
 
We produce all kinds of SCSI cable with good performance. Certificates of SGS have achieved. We have own logistics company to save your cost . And OEM is supported.
 
All the Wire is Bare Copper. Here are the SCSI cables we produce, if the items you interested, pls inquiry us.
 SCSI Lead Ultra 68 male to Ultra 68 male (VHDCI) SCSI cable
 SCSI Cable HD68M to HD68M  cable
 SCSI-5 (VHDCI) 0.8mm to SCSI-3 (HPDB68) 68-Pin Male/Male Cable
 SCSI Lead 50 Centronic male to 50 Centronic Male SCSI cable
 SCSI Lead Half Pitch 50 male to 50 Centronic male cable
 SCSI HPDB50 Male to Cen50 Male External Drive Cable
 SCSI HPDB50 Male to VHDCI68 Male Cable
 
Waiting for your inquiry.
 
Best regards!