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

Conference decwet::winnt-clusters

Title:WinNT-Clusters
Notice:Info directories moved to DECWET::SHARE1$:[NT_CLSTR]
Moderator:DECWET::CAPPELLOF
Created:Thu Oct 19 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:863
Total number of notes:3478

705.0. "Intel Clusters on non-DEC servers - Has anyone tried it ?" by CHEFS::rasmodem9.reo.dec.com::WorkBenchUser () Fri Mar 21 1997 06:10

Hello,

If anyone has built a cluster with Intel Digital Clusters for Windows NT on 
non-DEC servers, please can they let me know on what platforms they tried it 
and any problems they encountered.

bye for now

Trevor...
T.RTitleUserPersonal
Name
DateLines
705.1Of course it runsTAVEIS::SHALOMSun Mar 23 1997 13:0716
re .-1

	I did it on a couple of unnamed industrial boxes having "generic"
motherboards and off the shelf components. Used the FR-ba356-NT kit, meaning
carefully doing the SCSI thing.

	Worked without a hitch. Why shouldn't it.

	I haven't run intensive and real life tests, just saw that the thing
boots and fails over.

	Real question is: in Many situations , the customer REQUIRES a support
contract for the configuration. As always, seeing the thing run doesn't mean we
will sign a service contract for it.

Shalom
705.2trojan horseMPOS01::naiad.mpo.dec.com::mpos01::cerlingI'm@witz.endMon Mar 24 1997 15:1621
	Whenever I ever have a customer ask about running to software on 
	another vendor's system, I tell them there is no reason for it not
	to run if the other vendor is abiding by all the hardware interface
	standards.  However, we won't support it except on our platforms,
	mainly because not every vendor is as particular about standards
	as we are.  Therefore, if a customer wants to run the cluster
	software on another vendor's hardware, make sure they buy at least
	a single hardware configuration from Digital.  Then if they have
	problems with the cluster software running on the other vendor's
	configuration, they need to try the same thing on the Prioris
	configuration.  If the problem occurs on the Prioris (and they have
	support), they can call for support.  If they can't get the problem
	to occur on the Prioris configuration, it is most likely something
	in the other vendor's setup and there is no way we can support that
	as we have no means of testing it.  Any customer I have proposed this
	to has said it makes sense.  (Then, after the see the quality of our
	products, they begin to wonder why they don't just use our stuff all
	over!)

tgc