Phil Forrest wrote: > Hello Fine People of SIS User Community, > > This is my first post and that is saying a LOT. The product has been > VERY easy to use, haven't needed help until now and my academic budget > would buy a round for you all if it had funds ;-)
Thanks! registering your cluster on the cluster map would be also appreciated. :-) http://www.systemimager.org/cluster-register/ > > Background: Very homogeneous cluster with 90 nodes on a strictly private > lan (192.168.x.x) the head node has external access. We are running RHEL > 5, PBS Pro 9, and PGI CDK 7.1-5. Hardware is Tyan either S2466-4M or > S2460 boards. > > My slight problem has to do with getting SIS to behave in a non-optimal > system. My cluster is getting old (5 years) and it was spec'd before I > arrived, therefore I did not have any input onto the selection of the > ethernet cards. > > Well, the original genius set us up with the Netgear (1000mbs) GA622T > card that CANNOT use BOOTP or PXE :( :( > On a quirk of fate, we were upgraded with some Tyan Tiger MPX boards > that came with the 3com ethernet (100mbs) 3C905 chip that DOES do PXE > > Now, I only have one procurve switch, so in the past I've had to use > this method: > > Create and use 'boot floppy' > load os via 3com port, > reboot, > pull the Cat 5e cable > put cable into Netgear GA622T card > > It was a fairly major pain for 90 nodes, but it worked. > > Now, on this latest incarnation of my cluster, I would like to try PXE > directly to each node. Early tests were great, I could reimage quickly > BUT upon rebooting, the system thought the eth0 card (the 3com) was now > the eth1 card (the Netgear).....I thought, ok, let's switch the cards > around, get the prime node O/S happy, and pull a new image and try > again....This time the eth0 card (the Netgear) was claiming to be the > eth1 card (the 3com) and vice versa. > > Ok, so I thought, maybe a mod alias would help here...this is the > contents of my modprobe.conf: > > alias eth0 3c59x > alias eth1 ns83820 > alias char-major-89 i2c-dev > options w83781d force_w83782d=0,0x2d force_subclients=0,0x2d,0x48,0x49 > force_w83627hf=0,0x2c force_subclients=0,0x2c,0x4a,0x4b init=0 > > > So, in looking at the above, no matter what order I place the two cards > in, I *always* get the inverse upon reboot. If I were to image the > system with that modprobe.conf, upon reboot I would see eth1 using 3c59x > driver and eth0 using ns83820 driver. > > I do not see any problems on the DHCP server and the config files look > normal. > > Can any kind soul shed some light on my issue? I wish I had another set > of eyes, but I'm the only engineer on this project. > > I'm sure it's operator error, just can't find it at the moment. > A solution could be to force network interface names by udev rules. Look at the troubleshooting guide: http://wiki.systemimager.org/index.php/Troubleshooting#A_possible_solution_to_fix_network_interface_naming -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
