From: Jolet, John (John.Jolet@MISYSHEALTHCARE.COM)
Date: Wed Jun 19 2002 - 13:34:39 EDT
we had ours in such a configuration, using hacmp. The previous sysadmins
had lots of trouble with hacmp, so they turned it off (mostly), but it was
pain from the hdisk side because you couldn't really tell that the drive had
been "fence off" until you went to do something with it...and if you reboot
one machine in the loop, they ALL start puking errors because the loop is
open.
-----Original Message-----
From: Andrew Garnett [mailto:andrewwdg@YAHOO.CO.UK]
Sent: Wednesday, June 19, 2002 11:05 AM
To: aix-l@Princeton.EDU
Subject: Shared SSA Drives
Hi All,
We have just (for the first time) reconfigured our SSA
drawers so that 4 systems are in a loop with all their
SSA drawers. We intend to develop a manual failover
process to exploit this.
Of course, this means that each system now has a large
number of "hdisks" and pdisks belonging to the others.
Now, I can document these, or a process to identify
them, but is there a recommended approach to making
them identifiable on all systems ?
Should I be renaming the "hdiskn" to "node1_hdisknn" ?
What do you use ?
And come to mention it, is there a recognised document
for this kind of failover ?
Thanks in advance,
Andy
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:00 EDT