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

Conference 7.286::fddi

Title:FDDI - The Next Generation
Moderator:NETCAD::STEFANI
Created:Thu Apr 27 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2259
Total number of notes:8590

10.0. "VAXclusters and FDDI, what is expected?" by CVG::PETTENGILL (mulp) Thu Oct 05 1989 22:44

Being involved in testing VAXclusters, especially I/O, my primary interest
in FDDI is how does it relate to VAXclusters.

Do you see a major benefit in using FDDI in VAXclusters?

Where/how do you see it being used?

To act as a switch between Ethernet-FDDI bridges?

As a CPU to CPU interconnect?

As a workstation interconnect?

As a replacement for CI?

Not at all?

What kinds of products to you think we should be offering in the area of
VAXcluster and FDDI?  FDDI HSCs?  Q-bus FDDI adapters?  FDDI LAT servers?
T.RTitleUserPersonal
Name
DateLines
10.1KONING::KONINGNI1D @FN42eqMon Oct 09 1989 18:456
All of those applications in VAXclusters sound sensible.

FDDI LAT servers?  Qbus FDDI adapters??  Both of them seem to be cases
where the bandwidth of FDDI doesn't match at all.

	paul
10.2FDDI should make a great Cluster interconnectHYEND::BLYONSVAXcluster SASETue Jan 02 1990 15:5121
Some random thoughts:

	The CI is expensive and the NI can be very limited in bandwidth,
	FDDI has great potential.

	We will need multiple FDDI adaptors to replace the CI in customer
	installations and have no noticable performance impact.

	If the price of the FDDI interface is close to the price of an
	NI interface then we have a new migrate path for LAVc configurations.

	FDDI LATs will allow a customer to avoid having two communications
	backbones strung around the building(s).

>What kinds of products to you think we should be offering in the area of
>VAXcluster and FDDI?  FDDI HSCs?  Q-bus FDDI adapters?  FDDI LAT servers?

	All of the above will have a market.  It's just a mater of time
	till someone offers such products...

		Bob L.