2 bonded nics working slowing down imaging speed

[george1421]

Well, I think this line is in error
bond-primary em1 p255p1
Since you already have that defined for em1 or I would only select one, probably the internal one for primary.

Secondly I think I would use bond mode 5 or if you have access to the switch setup LACP mode.

Did you deploy only one client in the test above or more than one? The packets transmitted seem to indicate the second nic is not being used. If you had only two actors in the conversation I would understand the packet mismatch.

[Sebastian Roth]

And why bond-primary em1 eth1?? You don’t have eth1 as ifconfig shows.

[mitzayapa]

True , there´s no eth1 device in my config. Just delete it ?

[mitzayapa]

Whould any of you be kind and paste a corrected interfaces file for my configuration?

[Sebastian Roth]

I’d suggest this config:

auto em1
iface em1 inet manual
  bond-master bond0
  bond-primary em1

auto p255p1
iface p255p1 inet manual
  bond-master bond0

auto bond0
iface bond0 inet static
  bond-slaves em1 p255p1
  bond-mode 2
  bond-miimon 100
  ...

[george1421]

@Sebastian-Roth In some of the ubuntu examples they always use bond-slaves none. Not sure why. I would agree with your setting.

As for the primary, I still think I would use the onboard nic for primary, but again I don’t know what a p255p network interface is. Also if the xor mode (bond mode 2) (not really intelligent but fast) isn’t properly sharing the bandwidth during 3 or more installs at the same time, I would switch to bond-mode 5 or setup lacp on the switch and use bond-mode 4.

[mitzayapa]

The p255p is the second NIC I added to the server.

em1 - built in
p255p - 1gigabit ethernet card

auto em1
iface em1 inet manual
  bond-master bond0
  bond-primary em1

auto p255p1
iface p255p1 inet manual
  bond-master bond0

auto bond0
iface bond0 inet static
  bond-slaves em1 p255p1
  bond-mode 2
  bond-miimon 100
  ... -> is there missing something or thats all ?

[jbsclm]

I used round robin, it gave both speed and resilience, however that was on an unmanaged switch.

[george1421]

@mitzayapa Sorry I was reading fast before I started my commute into work. I read p255p1 as your primary interface. I thought it was strange, but I’ve seen some pretty strange stuff in the last few days.

As for the bonding, what you have is correct, you still need to assign the normal IP address stuff to the bond0 interface.

At the very least these:

address 192.168.137.51
netmask 255.255.255.0
gateway 192.168.137.1

[mitzayapa]

This is what i should have then ?

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface

auto lo
iface lo inet loopback

# The primary network interface

auto em1
iface em1 inet manual
  bond-master bond0
  bond-primary em1

auto p255p1
iface p255p1 inet manual
  bond-master bond0

auto bond0
iface bond0 inet static
  bond-slaves em1 p255p1
  bond-mode 2
  bond-miimon 100
  address 192.168.137.51
  netmask 255.255.255.0
  gateway 192.168.137.1

[george1421]

@mitzayapa I agree that looks reasonable. Restart the network service and see what you have with ip addr show

I do have to say I’ve only seen where they bond like adapters. This should work but now you have two network drivers loaded. Again not a problem, just not standard.

[ch3i]

@mitzayapa said:

This is what i should have then ?

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface

auto lo
iface lo inet loopback

# The primary network interface

auto em1
iface em1 inet manual
  bond-master bond0
  bond-primary em1

auto p255p1
iface p255p1 inet manual
  bond-master bond0

auto bond0
iface bond0 inet static
  bond-slaves em1 p255p1
  bond-mode 2
  bond-miimon 100
  address 192.168.137.51
  netmask 255.255.255.0
  gateway 192.168.137.1

It’s seem to be good, it’s not necessary to configure your p255p1 and em1 interfaces :

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface

auto lo
iface lo inet loopback

# The primary network interface

#auto em1
#iface em1 inet manual
#  bond-master bond0
 # bond-primary em1

#auto p255p1
#iface p255p1 inet manual
#  bond-master bond0

auto bond0
iface bond0 inet static
  bond-slaves em1 p255p1
  bond-mode 2
  bond-miimon 100
  address 192.168.137.51
  netmask 255.255.255.0
  gateway 192.168.137.1

[mitzayapa]

Without configuring the p255p1 and em1 the network ainºt working.(as i have no connection to server)

It works like this :

auto em1
iface em1 inet manual
  bond-master bond0
  bond-primary em1

auto p255p1
iface p255p1 inet manual
  bond-master bond0

auto bond0
iface bond0 inet static
  bond-slaves em1 p255p1
  bond-mode 2
  bond-miimon 100
  address 192.168.137.51
  netmask 255.255.255.0
  gateway 192.168.137.1```

and this is what i get :

```root@fog1:~# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: p255p1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether e8:39:35:63:fa:bb brd ff:ff:ff:ff:ff:ff
3: em1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP group default qlen 1000
    link/ether e8:39:35:63:fa:bb brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether e8:39:35:63:fa:bb brd ff:ff:ff:ff:ff:ff
    inet 192.168.137.51/24 brd 192.168.137.255 scope global bond0
       valid_lft forever preferred_lft forever
    inet6 fe80::ea39:35ff:fe63:fabb/64 scope link tentative dadfailed
       valid_lft forever preferred_lft forever```