Got the boxes networked alright. Am bonded with eth0 and eth1 in both machines (192.168.2.0); eth2 in node1 goes to other half of network (192.168.1.0) and internet. Between the bonding and firewall is where I'd messed up the issue with routing. node2 now as it needs to if I just drop the firewall. This I do only to get updates when notified. Am looking over the LAM info and subscribed to the Beowulf List to see about others there that may've tried/trying the same thing. Will keep y'all notified as to the progress here. Thanks for your support, GregS <>< gswallow@xxxxxxxxxx On Tue, 2004-06-15 at 22:36, T. 'Nifty New Hat' Mitchell wrote: > On Mon, Jun 14, 2004 at 08:00:45AM -0400, Greg Swallow wrote: > > > > Am wondering if any one has had any luck building a Beowulf style > > cluster with FC2. Found much information, but most about Reliability > > Servers Clusters. Not what I am trying to accomplish with this cluster. > > Am building a small, 4 processor (SMP); 2 box (MPI), Beowulf > > Supercomputer cluster. > > > > Really need a step by step. So far am working in pieces searching the > > internet for information one piece at a time. Way too much time > > searching and too little time "Super" computering. > > Install and look at LAM to start. > > LAM - introduction to Local Area Multicomputer (LAM) > http://www.lam-mpi.org/faq/ > > On FC1... > $ rpm -q --whatprovides /usr/bin/lamtrace > lam-6.5.9-3 > $ rpm -q --whatprovides /usr/bin/mpicc > lam-6.5.9-3 > etc... > > On FC2 the lam version is newer... > # rpm -qa lam > lam-7.0.3-6.4 > > As soon as the boxes are networked together you can begin. >
