Again Problems with Supermicro Board and Intel I350 NIC

[MisterIX]

Dear Forum Guests,

I tested Proxmox well on a simple hardware setup (IBM Thinkcenter) and found it was the ideal solution for virtualizing in my company. However, now that the servers arrived, I don't get all the network interfaces up and running.

The Supermicro [FONT=&amp]X9DRi-LN4F Board comes with 4* Intel® i350 Gigabit Ethernet controllers, additionally I want to add a 10GB Intel card later for connecting my NAS-Server. As I experienced problems, I took this card out of the server for now, to just focus on the onboard NICs.

The first NIC is brought up correctly during install, but the second one (eth1) can not be initialized. It even drops out of physical function, when wheezy starts to populate /dev during boot. (the physical connection lights on the interface and the switch stop blinking.) Still all the interfaces are shown with ifconfig –a. Ifup eth1 gives out the error:

Ignoring unknown interface eth1=eth1.


I found an older thread with a similar problem here: http://forum.proxmox.com/threads/13...er-shown-but-not-working?highlight=INtel+I350
and therefore followed the recommendation:
[/FONT]
Please post the output of following commands to find the issue:
Code:

ifconfig -a
lspci -v | egrep "^[0-9]|Kernel"
cat /etc/udev/rules.d/70-persistent-net.rules
dmesg | grep eth
The outputs from these commands are attached as a text file here (mac Adresses and IPs have been X'd).

Your help is grately appreciated.

MisterIX.

 

[WaltervdSchee]

I had the same issue with a SuperMicro A1SRM-2758F, you need to look at specifically which MAC addresses and which ports are which, because its a little confusing at first.
LAN1(eth0) and LAN2(eth1) are next to each other on the bottom on my board, then LAN3(eth2) and LAN 4(eth3) are the top 2 interfaces (on my board)

While I was hooking my machine up, I expected LAN 1/LAN2 to be Bottom and top on the left, and LAN3/LAN4 to be Bottom and Top on the right,
which turned out to be false ....

Do check the MACs and the eth0 through eth3 in the rules file to see if things are correct there...

 

[MisterIX]

Thank you Walter,

actually it was (like always) my fault. All the interfaces and mac adresses were correctly setup in 70-persistent-net.rules. I just asumed that the network ports were disturbed because they stopped blinking. Actually they where just deactivated.
Instead I should have looked in the grafical webbrowser surface under Servername->Networking. Here I could setup a second linux-bridge (vmbr1) and choose interface eth1. The interface started happily blinking.

Problem solved.