|
Please skim through the available VMScluster documentation.
This configuration is fully supported, assuming the following:
o The customer will need to configure all nodes and all DSSI
ISEs into the same disk and tape allocation classes, and will
need to configure all disks within the same disk allocation
class to unique unit numbers, and all tapes within the same
tape allocation class to unique unit numbers. (This is
required for failover of disk and tape serving.)
o All nodes involved in all shared DSSI busses have the SYSGEN
parameter VAXCLUSTER set non-zero.
o At most, eight connections -- including disks, tapes, and
host controllers -- are permitted on each DSSI bus.
o Be aware that hot-disconnecting the DSSI busses can cause
problems, and be aware of where individual disks receive
power. (eg: NodeB:: cannot run a NodeA:: application from
a NodeA:: disk located inside the NodeA:: system cabinet,
if NodeA:: is currently powered down...)
Depending on the particular DSSI controller, the customer could
also use a tri-host DSSI configuration.
|