  VAX disk hardware, mixed version cluster? 
 The Question is:
 
I've got to break out a VAX-6440 from a 3-node homogenous CI cluster and
have one XMI slot and two BI slots open.   I need to put a FDDI card in it
and add some disk drives for standalone booting.  While it will be part of
a new FDDI cluster and provide migration support, in essence it will have
it's own systems disks.  This system will be  running V5.5-2 in the new FDDI
cluster and provide migration support to a mix of 2-AS1200s running V7.2 and
2-VAX0496s running V5.5-2 i
n a FDDI ring.   This will be temporary for maybe a couple of months.
 
The CI cards are still in the system, but buying an HSC or HSJ for temporary
use is sort of expensive, even using used parts.   How can I best configure
this and use cheaper interface boards?
  a)  Is it best to to use XMI-FDDI card and then a BI-SCSI for disks?
   b) Or use an XMI-SCSI interface for disks and then run BI-FDDI card?
   c) Are any of the two above scenarios possible?  Something better?
I need about 10 to 20GB of system disk space for this 6440 and think it'll
work with any SCSI interface to a BA356 storage works deskside box that we
have here in house.  I do have spare Star coupler in house and cables in
case the HSJ or HSC is the only
way to go for disks.
 
Ron Deaton
 
 
 
 
 
 
------_=_NextPart_001_01BEE331.C53CBDAC
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
 
&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"&gt;
&lt;HTML&gt;
&lt;HEAD&gt;
&lt;META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1"&gt;
&lt;META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2540.0"&gt;
&lt;TITLE&gt;FW: Ask the Wizard: 'rdeaton@usa.alcatel.com'&lt;/TITLE&gt;
&lt;/HEAD&gt;
&lt;BODY&gt;
&lt;BR&gt;
&lt;BR&gt;
 
&lt;P&gt;&lt;FONT SIZE=3D2&gt;-----Original Message-----&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;From: =
&amp;quot;VMS001::WWW&amp;quot;@vms001.das-x.dec.com&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT =
SIZE=3D2&gt;[mailto:&amp;quot;VMS001::WWW&amp;quot;@vms001.das-x.dec.com] &lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;Sent: Tuesday, August 10, 1999 8:41 AM&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;To: sander@vmsbiz.eng.pko.dec.com; =
vms001@vmsweb.eng.pko.dec.com;&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;wizard@vmsmkt.zko.dec.com&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;Subject: Ask the Wizard: =
'rdeaton@usa.alcatel.com'&lt;/FONT&gt;
&lt;/P&gt;
&lt;BR&gt;
 
&lt;P&gt;&lt;FONT SIZE=3D2&gt;Remote Host: (null)&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;Browser Type: Mozilla/4.5 [en] (Win95; I)&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;Date/Time: Tue August 10, 1999 08:41:09 AM &lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;Remote Info: &amp;lt;null&amp;gt;&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;Name: Ron Deaton&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;Email Address: rdeaton@usa.alcatel.com&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;CPU Architecture: VAX&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;Version: V 5.5-2&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;Questions:&lt;/FONT&gt;
&lt;/P&gt;
 
&lt;P&gt;&lt;FONT SIZE=3D2&gt;I've got to break out a VAX-6440 from a 3-node =
homogenous CI cluster and have one XMI slot and two BI slots =
open.&amp;nbsp;&amp;nbsp; I need to put a FDDI card in it and add some disk =
drives for standalone booting.&amp;nbsp; While it will be part =
of&lt;/FONT&gt;&lt;/P&gt;
 
&lt;P&gt;&lt;FONT SIZE=3D2&gt;a new FDDI cluster and provide migration support, in =
essence it will have it's own systems disks.&amp;nbsp; This system will =
be&amp;nbsp; running V5.5-2 in the new FDDI cluster and provide migration =
support to a mix of 2-AS1200s running V7.2 and 2-VAX0496s running =
V5.5-2 i&lt;/FONT&gt;&lt;/P&gt;
 
&lt;P&gt;&lt;FONT SIZE=3D2&gt;n a FDDI ring.&amp;nbsp;&amp;nbsp; This will be temporary for =
maybe a couple of months. &lt;/FONT&gt;
&lt;/P&gt;
 
&lt;P&gt;&lt;FONT SIZE=3D2&gt;The CI cards are still in the system, but buying an =
HSC or HSJ for temporary&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;use is sort of expensive, even using used =
parts.&amp;nbsp;&amp;nbsp; How can I best configure this and use cheaper =
interface boards?&amp;nbsp; &lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;&amp;nbsp; a)&amp;nbsp; Is it best to to use XMI-FDDI card =
and then a BI-SCSI for disks?&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;&amp;nbsp;&amp;nbsp; b) Or use an XMI-SCSI interface for =
disks and then run BI-FDDI card?&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;&amp;nbsp;&amp;nbsp; c) Are any of the two above scenarios =
possible?&amp;nbsp; Something better?&lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;I need about 10 to 20GB of system disk space for =
this 6440 and think it'll work with any SCSI interface to a BA356 =
storage works deskside box that we have here in house.&amp;nbsp; I do have =
spare Star coupler in house and cables in case the HSJ or HSC is the =
only &lt;/FONT&gt;&lt;/P&gt;
 
&lt;P&gt;&lt;FONT SIZE=3D2&gt;way to go for disks.&lt;/FONT&gt;
&lt;/P&gt;
 
&lt;P&gt;&lt;FONT SIZE=3D2&gt;Ron Deaton&lt;/FONT&gt;
&lt;/P&gt;
&lt;BR&gt;
 
&lt;P&gt;&lt;FONT SIZE=3D2&gt;&amp;nbsp;&amp;nbsp; &lt;/FONT&gt;
&lt;BR&gt;&lt;FONT SIZE=3D2&gt;&amp;nbsp;&lt;/FONT&gt;
&lt;/P&gt;
 
&lt;/BODY&gt;
&lt;/HTML&gt;
------_=_NextPart_001_01BEE331.C53CBDAC--
 
 
 The Answer is:
 
  OpenVMS VAX V5.5-2 and OpenVMS Alpha V7.2 are not supported in the
  same OpenVMS Cluster.
 
  All nodes connected to a CI must be members of the same cluster.
 
  Compaq does not offer an XMI to SCSI adapter for OpenVMS VAX, and
  relatively few new BI widgets are presently available (if any).
 
  If price and performance and current technology are not requirements,
  the KDB50 or KDM70 controller and RA-series disks would work, as would
  DSSI disks and the XMI KFMSA controller.  Alternatively, the use of one
  or more HSD-series controllers via the KFMSA XMI to DSSI controller would
  permit access to SCSI devices.
 
  Upgrading the OpenVMS VAX systems to V6.2, and then configuring them into
  the same OpenVMS Cluster with the OpenVMS V7.2 systems is another course
  of action.
 
