Marty Kuhrt wrote on 09/11/2008 12:19:18 PM:

> John Santos wrote:
> > norm.raphael@metso.com wrote:
> >>
> >> Marty Kuhrt wrote on 09/09/2008 12:38:20

PM:
> >>
> >> > Since the VAX in OP's question is probably only talking to the

cluster
> >> > via its 10M network cable, it might be as simple as a that.
> >>
> >> No such luck. Talking on FDDI for SCS traffic. 10MB network for

other.
> >
> > Are you certain? IIRC, the default cluster configuration is to enable

all
> > SCS-capable circuits, and normally all the traffic would end up on the
> > fastest one (FDDI), but if there was a momentary failure or excessive
> > congestion on the FDDI, it might have failed over to the ethernet,

thus
> > hitting the VAX's 10Mb bottleneck, and then never failed back. I
> > think the show cluster circuit counters should reveal if this has
> > happened. (I think the 2nd example shows circuit counters by circuit,
> > but not circuit names, so I can't tell which is which, though possibly

a
> > cluster expert could.)
> >
> > There is a way to force it to use *only* the FDDI, and I think there's
> > a way to force to fail back to FDDI if for some reason it has failed
> > over to the Ethernet.
> >
> > HTH.

>
> Now that I think on it, was there a FDDI interconnect for VAXen? I
> vaguely remember that Nemonix was making an after market one, but I
> don't remember a "native" one. Of course, that doesn't mean too much,
> since I occasionally forget I have my glasses on my head. ;^)

TurboChannel FDDI adapter and yes, Nemonix. Good memory after all.