HP3000-L Archives

December 2003, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Bob J." <[log in to unmask]>
Reply To:
Bob J.
Date:
Thu, 4 Dec 2003 17:44:14 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
Simpkins, Terry wrote:
> If we "split the bus" on the array mechanism into two separate groups of drives, and
> then connect a separate controller to the other half of the bus.  You can't have the
> hardware mirrored drive on the other controller, (I'm told you can do this on UX).
> It must be on the same path as the "master" drive because MPE sees them as a single
> device.

That isn't exactly accurate. Actually ALL of the drives are accessible
from EITHER controller but of course via different addresses. Your
installer should set the DEFAULT ownership of drives to each controller.
To improve throughput each controller should share the load. Only one
controller is necessary to address ALL of the drives.......but....where
MPE falls short is not having a mechanism for auto fallover of a failing
controller. In other words sysgen reconfiguration would be necessary to
run on a single controller after SP failure in a dual SP configuration.
You could have alternate configurations stored on your system to cover
both cases of a single failing controller but the best solution is to
get it fixed when it breaks. The best news is that SP failures are not
very common.

                          Bob J. -- Ideal Computer Services
                          http://www.icsgroup.net

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2