PCIe Intel I350-T2 'Port Down' after reboot (bond+bridge)


Recommended Posts

Hey guys,

after having pretty much everything setup (for the 3rd time) I'm now definitely stuck.


-nic1 onboard
-nic2 I350
-nic3 I350

 

nic 1 got a static IP
nic 2+3 are bond and bridged; switch is properly setup [switch:static-lag - unraid:round-robin]

 

and this works until the server is rebooted, then the bond/I350-T2 won't come up automatically.

 

I know of the concept of a server but however I can't always hookup a screen to start in the GUI to 'port-up'., and it's not the time yet for a kvm-switch.

 

 

The host is temporarily in my home-office, but will move sooner or later, so I have to figure this out:

There is a second card coming, the goal would be to bond all 5 together, and connect that to a 1/5/10G switch.

 

So the cards are pcie_x2, fitted in a x1 slot, working perfectly:
pc:pcie3_x1 / card:pcie2_x2
breakdown:
1 ethernet-port is at max. pulling 250MB/s (125MB/s upstream - 125MB/s downstream) so one card is pulling 0,5GB/s which is the max. of pci2_x1

 

I'd like to achieve that the ports stay up due reboots. 10G card isn't a solution due to no available slots left.

 

> In the mainboard-bios I deactivated network-boot (as I've read it here somewhere)
> I saw that the Intel-I350 has a bios splash-screen /CTRL+S/ entered, couldn't uncheck the possibility to 'pxe-boot'.

So now I may got a hint, could flashing the card be a thing?


Has anybody input how I could proceed, what to try next?
This is driving me nuts. (Tagged the title appropriately so whoever comes after me has a better time finding a solution) 

 

Thanks in advance for any input! After this I'm sold to the pro-version

 

PS: Will attach logs asap

 

Kind regards

screencapture-kaby-Settings-NetworkSettings-2021-02-18-19_09_59.png

Edited by Hank Moody
attachement/network-settings
Link to comment
  • Hank Moody changed the title to PCIe Intel I350-T2 'Port Down' after reboot (bond+bridge)

...when the bond stops working, but all ethx interfaces are available I can only think of a mismatched configuration between unraid and switch.
Using static LAG is IMHO not a good idea.
Try dynamic LACP/802.3ad instead.

By looking at your configuration, you do use the same network (192.168.10.0/24) for eth0(no VLAN) and Bond0-VLAN10.
What's the PID on the switch port where eth0 is connected?

Gesendet von meinem SM-G960F mit Tapatalk

Link to comment

Thanks for chiming in!

So I'd prefer LACP too but the (current) switch only supports static LAG.

 

eth0 port9 pvid10 vl10-UNtagged

eth1 port8 pvid10 vl10-tagged vl20-tagged vl30++

eth2 port7 pvid10 vl10-tagged++

*eth3 port6 pvid10 vl10-tagged++

*eth4 port5 pvid10 vl10-tagged++

 

LAG

current 7+8 (*coming 5-9 =5gb/s)

 

 

 

cheers, and have a nice fridaynight!

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.