| Either of these configurations should work. VMS will need to be at version
5.4-3. I know that DECnet, LAT, and LAVC traffic will work (and I'd guess that
the others will as well, but you'll want to confirm this). One caveat is that
if you have multiple Ethernet/FDDI adapters on a system connected to the same
extended LAN, you can only run DECnet Phase IV on one of them at a time. On
the other hand, having the second adapter can help your system availability
somewhat.
Re: support of over 96 nodes in an LAVC, talk to the VAXcluster Product
Manager, Nick Carr (STAR::NCARR) about plans in this area.
Oh, by the way, I think the DECbridge 500 only has 1 Ethernet port; it's the
600 which has three.
|
| The DEC FDDIcontroller 400 for XMI-based VAX 6000 and 9000 systems has
VMS support for LAT and DECnet Phase IV as announced in the 5/28 issue
of Sales Update. With the actual release of VMS V5.4-3, we also have
full VAXcluster support, with a few configuration rules as explained in
the VMS cover letter and the VMS and VAXcluster SPDs. For instance,
the maximum number of VAXcluster members that may be directly connected
to FDDI via the DEC FDDIcontroller 400 is 16. We just submitted a
Sales Flash announcing the VAXcluster support since it was not included
in the product announcement article in May. I'll include that article
as a reply to this note.
TCP/IP Services for VMS V2.0 (formerly UCX) will provide TCP/IP support
for the FDDIcontroller 400, but it has not yet been product announced.
We did demo it at Interop 91 last week. As for the other protocols on
your list, I'm not sure I understand. Appletalk protocols are handled
by the DECbridge 5xx/6xx devices, not the controller. And if by DSS
you mean naming and time services, those are applications that run over
the network and are independent of the interconnect.
-karen
|