home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!linac!att!cbnewsm!cbnewsl!att-out!walter!qualcom.qualcomm.com!network.ucsd.edu!sdcc12!xm9
- From: xm9@sdcc12.ucsd.edu (richard g. adair)
- Newsgroups: comp.sys.hp
- Subject: Re: clusters
- Summary: Clusters
- Keywords: cluster
- Message-ID: <42692@sdcc12.ucsd.edu>
- Date: 18 Dec 92 06:09:45 GMT
- References: <BzFsCM.H5u@bunyip.cc.uq.oz.au>
- Sender: news@sdcc12.ucsd.edu
- Organization: University of California, San Diego
- Lines: 23
- Nntp-Posting-Host: sdcc12.ucsd.edu
-
- In article <BzFsCM.H5u@bunyip.cc.uq.oz.au> werner@dirac.physics.uq.oz.au writes:
- >We are investigating buying several HP7?? snakes and have heard about
- >something called a cluster environment for HP workstations.
- >Has anybody used this system , what is the implementation (i.e RPC calls?),
- >what are the capabilities, what are the management problems, what are the
- >limitations, do all the machines have to be identical?
-
- Clusters work great under HP-UX. The machines don't have to be
- identical, but using the same series is best. You should set up
- your computers with a small local swap disk (although net swapping
- works ;-). The HPs also support local file systems. The actual
- method is HP proprietary, but it works just the same. Very
- reliable. I just wish that the 700s would loop retry start-up after a
- crash. After a short time out, reboot quits and you have to hike to
- the console to restart the client-boot selection process...
- Essentially you save about 100MB disk per machine, since a single
- copy of the OS is shared between the cluster members.
-
- Of course, if the server crashes, everything crashes! :-)
-
- Tony Burzio
- Arete Associates
- San Diego, CA
-