[ubuntu] New File Server, No Network? Doctored /etc/network/interfaces From Old One?

[JRA]

Hi all, hopefully I'll be explaining this well enough.

 

Right, my old fileserver (call it FS1) needs replacing. Bought a new one (we'll call that NEWFS1.) Old one has 2x bonded NICs, new one has 4x NICs I'd like to bond. Old one pings and works fine, but can't seem to talk to the new one. The new one's plugged into the core switch and all four of its ports are set to the same trunk as the old one.

 

It's almost as if the old one 'understands' tagged packets on the trunk and the new one doesn't, if you get me.

 

So, in setting up I copied /etc/network/interfaces from the old one to the new one, with a bit of changing re the hardware on the new one, IP addy etc. First up, the original one:

 

# 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


auto eth0
iface eth0 inet manual
       bond-master bond0


auto eth1
iface eth1 inet manual
       bond-master bond0


auto bond0
iface bond0 inet static
       address 10.108.1.9
       netmask 255.255.255.0
       network 10.108.1.0
       broadcast 10.108.1.255
       gateway 10.108.1.1
       # dns-* options are implemented by the resolvconf package, if
       # installed
       dns-nameservers 10.108.1.200 10.108.1.201
       dns-search myschool.sch.uk
       bond-slaves none
       bond-mode 802.3ad
       bond-miimon 100

 

And next, the one I've altered and put on the new one:

 

# The loopback network interface
auto lo
iface lo inet loopback

#Added by me. Herpderp.
auto enp3s0f0
iface enp3s0f0 inet manual
       bond-master bond0

auto enp3s0f1
iface enp3s0f1 inet manual
       bond-master bond0

auto enp3s0f2
iface enp3s0f2 inet manual
       bond-master bond0

auto enp3s0f3
iface enp3s0f3 inet manual
       bond-master bond0

auto bond0
iface bond0 inet static
       address 10.108.1.111
       netmask 255.255.255.0
       network 10.108.1.0        
       broadcast 10.108.1.255
       gateway 10.108.1.1
       # dns-* options are implemented by the resolvconf package, if installed
       dns-nameservers 10.108.1.200 10.108.1.201
       dns-search myschool.sch.uk
       bond-slaves none
       bond-mode 802.3ad
       bond-miimon 100

 

Won't ping, nothing. Just in case it's handy, I have a visual investigated in MSPaint (attached.)

 

So, can anyone see where I'm going wrong or if there's anything to try?

 

Thanks everyone!

Edited August 1, 2016 by JRA

[Steve21]

You shouldn't have both servers live on the same trunk, VLAN yes, but not trunk as it's not a single connection etc. You'd have 1 trunk per FS surely?

 

Steve

[JRA]

You'd have 1 trunk per FS surely?

 

...

 

...I would?

[Steve21]

Well I'm assuming when you say trunk you mean it in the sense of bonded links/aggregation, so you get in your original example 2Gig to FS1.

 

Therefore effectively with your setup you've got 1 virtual-port on a switch going to 2 devices.

 

Steve

[JRA]

Okay don't look now but I think I'm getting it. But shouldn't it ping at least or is that not what it'd do?

 

Would it be then the best thing to set up another trunk for the new one, just with the same VLANs going on?

 

Bless you for helping!

[pantscat]

Would it be then the best thing to set up another trunk for the new one, just with the same VLANs going on?

 

Yep...

 

One device per trunk... otherwise how will the switch know which device the packets are meant for?

[Steve21]

Okay don't look now but I think I'm getting it. But shouldn't it ping at least or is that not what it'd do?

 

Honestly not sure how Linux would deal with that, but wouldn't expect it normally to understand as effectively the ports 2-6 of the bond are just an extension of port 1 and wouldn't expect something else on it.

 

The other thing I'd say to check are you sure your NIC names are right? Normally it's Eth0-4 etc or did they change that in Ubuntu recently?

 

Steve

[JRA]

Thanks everyone. Okay, that's now unplugged pending its own LACP trunk.

 

Sometimes your NICs get called things other than eth0, eth1 etc. I usually just lshw -class network and see what it fancies calling it.