Channel bonding doesn't show eth0

Shadok · 5. Februar 2014

Hello,

I'm running ovm 0.5.33 (up-to-date) on a HP Proliant N54L.

I have an motherboard integrated nic as eth0 and a pcie x1 Intel PRO/1000 card (Intel Corporation 82572EI Gigabit Ethernet Controller).
eth0 is configured with a static ip and eth1 isn't configured at all.

When I try to create a bonding interface, the form only show eth1 in the slave and master sections.

Any idea ?

Thanks.

donh · 11. Februar 2014

Did you try deleting the existing one?

Shadok · 11. Februar 2014

Which existing one ?
I don't currently have any bonding interface.

I think I can't see eth0 in the list because that's the one i'm using.
I'll try again with a dual nic ethernet card.

datadigger · 11. Februar 2014

Zitat von "Shadok"

I think I can't see eth0 in the list because that's the one i'm using.

I believe that, too. Just tried the same, I have an unused port in the home box and saw the same behaviour.
Beside this I would bond ports of the same type and position only, an onboard and an off-board expansion card port may not work in tune.

Zitat von "Shadok"

I'll try again with a dual nic ethernet card.

That's a better idea, I have this setup running in the company box and that works pretty well. Make sure that you use the latest OMV version, until 0.5.0.31 link bonding was not possible and that your system fully recognizes the expansion card, installing the backport kernels opens a new dimension of supported hardware.

Shadok · 11. Februar 2014

Ok, i've setup the 2 nics ethernet card.
I now have eth1 and eth2 in OMV (manual method) but when i try to add a bonding interface i got no interfaces to select ... (master or slave).

donh · 11. Februar 2014

Before doing the below, the problem is probably the way the info is stored in the config.xml file. Maybe someone knows how to init the network better than bute force. Maybe run omv-firstaid on boot? (from the cd?)

You might need to edit /etc/network/interfaces. Here is my working version so fix it to your needs. Maybe you should also post a bug at http://bugtracker.openmediavault.org. save yours first as .bak or something and maybe post it here.

Code

# The loopback network interface
auto lo
iface lo inet loopback


# bond0 network interface
auto bond0
iface bond0 inet dhcp
    post-up /sbin/ifconfig $IFACE mtu 9000
    dns-nameservers 10.0.83.215 10.0.83.1
    bond-slaves eth0 eth1
    bond-primary eth0
    bond-mode 6
    bond-miimon 100
    bond-downdelay 200
    bond-updelay 200

Alles anzeigen

Shadok · 11. Februar 2014

Nope, i already checked OMV config file, udev and network/interfaces files.
It is definitely an OVM bug.

Right now, I manually created my bonding by editing network/interfaces file and OVM xml configuration.
It works but i don't know if it will fully persist after a reboot.

donh · 11. Februar 2014

Please post it at the bugtracker

Shadok · 11. Februar 2014

Already did it
http://bugtracker.openmediavault.org/view.php?id=983

Shadok · 12. Februar 2014

Yeah, and if I unplug eth0, bonding on eth1/eth2 doesn't work anymore, server become unreachable.

hawaix · 12. Februar 2014

me too have this problem

Jetzt mitmachen!