[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference spezko::cluster

Title:+ OpenVMS Clusters - The best clusters in the world! +
Notice:This conference is COMPANY CONFIDENTIAL. See #1.3
Moderator:PROXY::MOORE
Created:Fri Aug 26 1988
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5320
Total number of notes:23384

5265.0. "Three node DSSI cluster full support help" by COWBOY::MIRGHANE () Mon Mar 24 1997 07:45

    Is the following Three node DSSI cluster fully supported?
    
    
    
    NODE A ------------disks-------NODE B ------------disks---------NODE C
    VAX4000            DSSI        VAX4000            DSSI          VAX4000
    (1 DSSI adapter)    shadowed    (2 DSSI adapters) Sshadowed     (1 DSSI adapter)
    
    The customer wants to do this because NODE B may have to run NODE A
    applications or (exclusive) NODE C applications in case of failure
    of respective nodes.
    
    The 3 nodes are also connected by an Ethernet LAN.
    
    Thanks very much for a quick help.
    
    Regrads.
    Soumetty.
T.RTitleUserPersonal
Name
DateLines
5265.1With Assumptions, Yes...XDELTA::HOFFMANSteve, OpenVMS EngineeringMon Mar 24 1997 13:5427
    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.