Proxmox no Ethernet Dell R200

guik

Renowned Member
May 10, 2010
12
1
68
Hi,

I've been meaning to install Proxmox on a Dell R200 dedicated server but I'm facing some issues.
Each time I boot on the 2.6.18-2-pve kernel the server stop to answer to the ping, I tried to but on rescue (with a netboot).
It seems that with the kernel 2.6.18-2-pve the network card stop to work when on the other hand with the original one (2.6.309 no problem at all.

I tried to search on the forum and i checked that the driver for the Broadcom is installed.

Following the wiki I edited (with netboot) the /etc/udev/rules.d/70-persistent-net.rules file and checked that each card has it own name.

Code:
# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add",  DRIVERS=="?*", ATTR{address}=="a4:ba:Db:Df:1c:e4", ATTR{dev_id}=="0x0",  ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x14e4:0x1659  (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",  ATTR{address}=="a4:ba:Db:Df:1c:e5", ATTR{dev_id}=="0x0", ATTR{type}=="1",  KERNEL=="eth*", NAME="eth1"

# PCI device 0x14e4:0x1659  (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",  ATTR{address}=="a4:ba:Db:Df:1c:e5", ATTR{type}=="1", KERNEL=="eth*",  NAME="eth2"

# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net",  ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:Db:Df:1c:e4",  ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
~
The info in /etc/network/interfaces are correct.

Have someone here been experimenting that kind of issue?

Regards
Guillaume
 
Hi,

i try to delete the lines, reboot the server and ping timeout.

I request again a netboot, the new data of /etc/udev/rules.d/70-persistent-net.rules :
# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:df:1c:e5", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:df:1c:e4", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
 
The entire file:
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x14e4:0x1659 (tg3)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:df:1c:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x14e4:0x1659 (tg3)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:df:1c:e5", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x14e4:0x1659 (tg3)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:df:1c:e5", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x14e4:0x1659 (tg3)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:df:1c:e4", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:df:1c:e5", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:df:1c:e4", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
 
The entire file:
Hi,
How many reboots you have done with which kernel?
If you delete all lines after
Code:
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
the first boot use "a4:ba:db:df:1c:e4" as eth0.
The next different boot use "a4:ba:db:df:1c:e4" as eth3

You can also change the brigde-interface vmbr0 from eth0 to eth3.

Udo
 
Yes !

I'd inverse eth0 & eth1:

# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:df:1c:e5", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:df:1c:e4", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
Reboot and server ping :)

Many thanks for your suggestion and time passed.

Regards
Guillaume
 
Sorry for the bump, but I thought this thread suited best.

I have a Poweredge860 with a similar problem. It's a fresh install of proxmox-ve_1.5-4627-3

I already tried this with no luck:
Code:
ifconfig vmbr0 down
ifconfig eth0 172.34.0.205 netmask 255.255.0.0 up
ifconfig -a output:
Code:
eth0      Link encap:Ethernet  HWaddr 00:10:18:31:9b:f3  
          inet addr:172.34.0.205  Bcast:172.34.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:169 Memory:fe5f0000-fe600000 

eth1      Link encap:Ethernet  HWaddr 00:1d:09:f1:7f:5d  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:169 Memory:fe3f0000-fe400000 

eth2      Link encap:Ethernet  HWaddr 00:1d:09:f1:7f:5e  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:58 Memory:fe1f0000-fe200000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5341 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5341 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:557888 (544.8 KiB)  TX bytes:557888 (544.8 KiB)

sit0      Link encap:IPv6-in-IPv4  
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vmbr0     Link encap:Ethernet  HWaddr 00:10:18:31:9b:f3  
          inet addr:172.34.0.205  Bcast:172.34.255.255  Mask:255.255.0.0
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15883 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:667302 (651.6 KiB)
dmesg | grep eth output:
Code:
eth0: Tigon3 [partno(BCM95721A211F) rev 4201 PHY(5750)] (PCI Express) 10/100/1000Base-T Ethernet 00:10:18:31:9b:f3
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]
eth1: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCI Express) 10/100/1000Base-T Ethernet 00:1d:09:f1:7f:5d
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[76180000] dma_mask[64-bit]
eth2: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCI Express) 10/100/1000Base-T Ethernet 00:1d:09:f1:7f:5e
eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] WireSpeed[1] TSOcap[1]
eth2: dma_rwctrl[76180000] dma_mask[64-bit]
device eth0 entered promiscuous mode
type=1700 audit(1275489144.477:2): dev=eth0 prom=256 old_prom=0 auid=4294967295 ses=4294967295
ADDRCONF(NETDEV_UP): eth0: link is not ready
/etc/network/interfaces

Code:
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
    address 172.34.0.205
    netmask 255.255.0.0
    gateway 172.34.0.1
    bridge_ports eth0
    bridge_stp off
    bridge_fd 0
I also tried to delete the content of /etc/udev/rules.d/70-persistent-net.rules
After a reboot, this is the content:
Code:
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:09:f1:7f:5e", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:10:18:31:9b:f3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x14e4:0x1659 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:09:f1:7f:5d", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
Any other thing I could try? Thanks a lot!
 
we are running a Dell R200 with proxmox.

So it will work, and we dont have any problems .. but you have a extra NIC in yours right ?
 
The Poweredge 860 comes with 3 NICs by default.

This did the trick for me:
Code:
/etc/netowork/intercaces
    bridge_ports eth0 ->     bridge_ports eth1
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!