Conference 7.286::fddi

365.0. "FDDIcontroller 400 Sales Flash" by FROSTY::LEONARD () Thu Oct 17 1991 17:40

AUDIENCE:	WORLDWIDE SALES AND SALES SUPPORT

SUBJECT:	DEC FDDICONTROLLER 400 HAS FULL VAXCLUSTER SUPPORT

AUTHOR:		KAREN LEONARD, DTN: 264-8119, MKO2


The DEC FDDIcontroller 400 announcement article in the May 28, 1991 
issue of Sales Update included LAT and DECnet Phase IV support, but 
referred to "future" VAXcluster support because of the need to do 
considerable configuration and performance testing.  That testing 
was completed in time for VAXcluster FDDI support to be included 
in the release of VMS V5.4-3, announced in the October 7, 1991 issue 
of Sales Update.

VMS Version 5.4-3 supports the use of the DEC FDDIcontroller 400 in 
multiple adapter, Local Area VAXcluster configurations. CPUs that use the
FDDIcontroller 400 for VAXcluster communications may concurrently 
use it for the other supported network protocols (LAT and DECnet Phase IV).  

FDDI support for VAXclusters provides customers with 100 Megabit/second 
bandwidth and configuration flexibility.  FDDI allows for extended distances
between VAXcluster systems of 2 KM to 40 KM, depending on the DECconcentrator 
500 management module option selected.  The DEC FDDIcontroller 400 is a single
attachment station (SAS) device that connects to the FDDI ring via a
concentrator. 

When configuring an FDDI VAXcluster, use the following rules: 

  o VMS Version 5.4-3 must be installed prior to installing the DEC 
    FDDIcontroller 400.

  o The maximum number of VAX-6000 or VAX-9000 VAXcluster members 
    that may be directly connected to FDDI via the DEC FDDIcontroller 400 
    is 16.  Other VAXcluster nodes may be bridged from Ethernet via DECbridge 
    500/600 devices.

  o VAXcluster software will not operate when nodes are distributed across
    encapsulating bridges.  

  o In a VAXcluster environment, heavy network loads can result 
    when many satellite nodes are booted simultaneously. It may 
    be necessary to minimize simultaneous booting, or to limit 
    the number of nodes that use LAN bridges.  As a general guideline, 
    limit the number of VAXcluster nodes on the Ethernet side of 
    Ethernet to FDDI bridges to 10.

Consult the VAXcluster Software Product Description (SPD 29.78.04) for 
additional rules and configuration recommendations.