Preferred networking order

[1812]

Not sure where to look for this one.

 

I did have my 10gbe cards cabled between each server (both running unRaid) and life was nice.

 

I picked up a quanta with 10gbe ports. Plugged both into each other. Works fine. Now a couple vm's that need greater than gigabit networking should be happy.

 

To make the 10gbe card the primary networking interface for unRaid, I switched the interface rules mac address order, putting the 10gbe card as eth0, and flipping the on that was there to eth4. 

 

Bridging is only setup on the 10gbe card and bonding is not on.

 

But regardless, when using Krusader unRaid uses the gigabit port to transfer data. The quick info in the header of the gui shows the ip of the 10gbe card. 

 

It is listed correctly in network config rules.

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:55:2a:2b:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:55:2a:2b:e6", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:55:2a:2b:e8", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x14e4:0x1639 (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:26:55:2a:2b:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

# PCI device 0x15b3:0x6750 (mlx4_core)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:c9:4e:b5:80", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

 

 

and here is the network.cfg

 

# Generated settings:
IFNAME[0]="br0"
BRNAME[0]="br0"
BRSTP[0]="no"
BRFD[0]="0"
BRNICS[0]="eth0"
DESCRIPTION[0]=""
USE_DHCP[0]="yes"
DHCP_KEEPRESOLV="no"
MTU[0]=""
IFNAME[1]="eth4"
DESCRIPTION[1]=""
USE_DHCP[1]="yes"
IPADDR[1]="192.168.1.121"
NETMASK[1]="255.255.255.0"
MTU[1]="1500"
SYSNICS="2"

 

If I set the gigabit port to down, then all traffic goes across the 10gbe card. But I wanted to keep the second ip to have access to the the gui incase something happened to the 10gbe card.

 

So how do make the 10gbe card primary and keep the gigabit as backup, if this is not how it should be done?

[1812]

I decided on a workaround for now. Put the onboard gigabit ports in active backup-bond with the 10gbe card. All data goes through 10gbe now since it is eth0. Not what I was hoping for, but it will have to do for now.

 

Sidenote: When transferring data from a vm to the array in the previously described setup, the data left the 10gbe card and re-entered the the server through the gigabit nic. Even when I specified the ip of the 10gbe card in the server,  the data going to the array would take the path out of the specified 10gbe nic, and back in the one that was not specified.