problems with tg3 (linux) driver on PE1750

[Paul M. Dyer]

It might be better to just edit /etc/sysconfig/network-scripts/ifcfg-eth0,1,2,3 and remove the hardware address that was copied from the origin server.

Paul
----- Original Message -----
From: "Ryan Moore" <ryan.moore at perigee.net>
To: linux-poweredge at dell.com
Sent: Thursday, December 11, 2008 5:43:57 PM (GMT-0600) America/Chicago
Subject: Re: problems with tg3 (linux) driver on PE1750

Actually I found the problem and it wasn't anything related to the Dell 
software at all. Turns out the problem was that the udev daemon was seeing the 
mac address for the nics in the original box not being present, so it 
reassigned the nics to eth2 and eth2. The file was 
/etc/udev/rules.d/75-network-devices.rules, which stored the mac addresses. 
Deleting that file and rebooting fixed the problem.

Ryan Moore
----------
Perigee.net Corporation
704-849-8355 (sales)
704-849-8017 (tech)
www.perigee.net



-------- Original Message  --------
Subject: problems with tg3 (linux) driver on PE1750
From: Ryan Moore <ryan.moore at perigee.net>
To: linux-poweredge at dell.com
Date: Wed 10 Dec 2008 03:38:21 PM EST

> I've been working on getting a set of PE1750 boxes setup using Slackware 12.0, 
> and have most everything working but have run into an issue. I've only setup 
> two machines so far, as I was getting a single box configured and setup and 
> then rsyncing everything to a network spool so it could be easily copied over 
> to the subsequent servers.
> 
> The exact problem appears to be that once the OMSA software is loaded on 
> bootup, eth0 and eth1 become eth2 and eth3 respectively, which seems a little 
> strange. The 'master' machine didn't have this problem, and with the exception 
> of the cpu's being different speeds and the master have a PERC4/di in it (2nd 
> server using software raid via the LSI 53c1030/FusionMPT), the hardware is 
> identical (both have been updated to the latest bios/firmware/etc). All the 
> software (kernel, omsa, etc) is identical between the servers as well with the 
> exception of the hostname and ip addresses.
> 
> Has anyone else run into this issue? I've done some searching via google but 
> haven't found anything. On bootup I can clearly see the tg3 driver being bound 
> to eth0 and eth1, but then have init starts the next mention of the eth 
> interfaces has eth2 and eth3, and an `ifconfig -a` doesn't list eth0/1 at all. 
> I could probably setup a script to configure eth2/3 after everything is said 
> and done, but I'd rather not resort to something as ugly as that, especially 
> since the original machine works normally.
> 

-- 

Ryan Moore
----------
Perigee.net Corporation
704-849-8355 (sales)
704-849-8017 (tech)
www.perigee.net

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq