Sam,

Has anyone seen this?  While testing new systems I have observed that
the 3rd on board ethernet stops working after days of moderate network
load testing.  I'm unable to ping out via the interface, or ping to the
interface's ip address from outside.  No errors are observed in logs,
ifconfig, route, or ethtool.  If I manually reconfigure the interface
with ifconfig it works fine.  (Leading me to think the driver or chipset
gets in an odd state and needs to be reset.)

We are seeing this with R300 onboard NICs. Have not checked whether they are using the same chip, but somewhat likely.

The NICs are actually loosing the MAC address, system needs to be powered down to bring the NICs back to life.

Dell told us to shut down the OS properly as it happens even more often if you reset the server. Our R300s are used for RedHat cluster testing, so fencing operations are quite common tasks in that environment.

Updating the NIC's firmware (with lots of iSCSI-related fixes) has worsened the situation. The MAC address is even lost if the cluster is idle (no tests or services running, just node to node status communication going on).

regards, Gunther

--
Gunther Schlegel
Manager IT Infrastructure


.............................................................
Riege Software International GmbH  Fon: +49 (2159) 9148 0
Mollsfeld 10                       Fax: +49 (2159) 9148 11
40670 Meerbusch                    Web: www.riege.com
Germany                            E-Mail: [email protected]
---                                ---
Handelsregister:                   Managing Directors:
Amtsgericht Neuss HRB-NR 4207      Christian Riege
USt-ID-Nr.: DE120585842            Gabriele  Riege
                                  Johannes  Riege
.............................................................
YOU CARE FOR FREIGHT, WE CARE FOR YOU


<<attachment: schlegel.vcf>>

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

Reply via email to