SOLVED Link Aggregation Trouble

Status
Not open for further replies.

codyf51

Dabbler
Joined
Feb 11, 2017
Messages
24
So I have a total of 6 NIC's, 1 IPMI, 2 Built in Intel, a 2 port RealTrek PCIe card, and a QSFP DAC 40G PCI card. All the ethernet ports work as I have used them for jails. The QSFP NIC is new but I am getting a data-link and FreeNAS sees it.
So I want to setup link Aggregation for all four ethernet ports, with two vLan's, LAN and a management LAN for the GUI. The QSFP is going to be used for a ESXi server to target iSCSi on FreeNAS. My problem is that anytime I configure any network setting I'm immediately locked out of the GUI and the server goes off the network. I verified that It was not simply a IP change. The only exception is when I change global settings. My solution is to reset the NIC's via console.
I have watched and read several tutorials and I do not believe that I'm doing anything wrong. Below are a few screenshots of my current config before I make any changes. One thing that is very suspicious is that when I make a change, for example clicking OK to add link aggregation I never receive a warning that this could disrupt network connectivity like others do in the guides. Instead my server just goes offline, completely on all NIC's. Right now I'm only using two ports em0 LAN & GUI, re0 NextCloud Jail to DMZ. While I must point out that I have never setup LACP and I hope this is just a case of nube user, I have no idea what could be wrong. O... Almost forgot my switch is a Unifi 24 port smart switch that supports vLan's and Link Aggregation.

I tera-appreciate any help! :)



FreeNAS Build

Build FreeNAS-9.10.2-
Platform Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz
Memory 65472MB
 

Attachments

  • Screen Shot 2017-03-29 at 10.02.06 PM.jpg
    Screen Shot 2017-03-29 at 10.02.06 PM.jpg
    164.1 KB · Views: 594
  • Screen Shot 2017-03-29 at 10.02.17 PM.jpg
    Screen Shot 2017-03-29 at 10.02.17 PM.jpg
    153.1 KB · Views: 610
  • Screen Shot 2017-03-29 at 10.02.12 PM.jpg
    Screen Shot 2017-03-29 at 10.02.12 PM.jpg
    162.2 KB · Views: 543
  • Screen Shot 2017-03-29 at 10.02.21 PM.jpeg
    Screen Shot 2017-03-29 at 10.02.21 PM.jpeg
    138.7 KB · Views: 580
  • Screen Shot 2017-03-29 at 10.02.25 PM.jpeg
    Screen Shot 2017-03-29 at 10.02.25 PM.jpeg
    141.3 KB · Views: 552
  • Screen Shot 2017-03-29 at 10.02.27 PM.jpeg
    Screen Shot 2017-03-29 at 10.02.27 PM.jpeg
    139 KB · Views: 547
  • Screen Shot 2017-03-29 at 10.02.31 PM.jpeg
    Screen Shot 2017-03-29 at 10.02.31 PM.jpeg
    133.8 KB · Views: 528
  • Screen Shot 2017-03-29 at 10.02.33 PM.jpeg
    Screen Shot 2017-03-29 at 10.02.33 PM.jpeg
    134.5 KB · Views: 530
  • Screen Shot 2017-03-29 at 10.02.37 PM.jpeg
    Screen Shot 2017-03-29 at 10.02.37 PM.jpeg
    135 KB · Views: 627
Last edited:

codyf51

Dabbler
Joined
Feb 11, 2017
Messages
24
Thank you for the quick reply. Please correct me if I'm mistaken, but creating a LAG should only affect network connectivity momentarily when I am editing the same port that I'm using to connect to the web GUI. In my case any network changes result with me immediately not being able to connect to the server. Even after waiting several minutes and restarting the machine the server will not even respond to pings.
 
D

dlavigne

Guest
It wouldn't hurt to create a bug report at bugs.freenas.org to make sure it's not a bug (or, at the very least, something that can be improved upon). If you do, post the issue number here.
 

codyf51

Dabbler
Joined
Feb 11, 2017
Messages
24
SOLVED!

My apologies everyone. In addition to my FreeNAS box, within a relatively short time I have built my entire home network including a pfSense firewall, and a ESXi VM Server, along with several web apps using the ESXi Server and a iSCSI link to FreeNAS. NextCloud, Unifi Video, FreePBX, and Plex to name a few. Unfortunately it's seen recently that everything had been failing or suffering from issues that did not seem to be related to config problems or admin error. Well, it got so bad that at one point I burned my entire network and started from scratch.... Twice. I thought to myself either someone really has a lot of time on their hands and is messing with me or I have lost my mind. Port Forwards would stop working randomly, servers would just go offline for no reason, and it was just a mess.
The Good News is that I found the problem and resolved it. To Install FreeNAS, pfSense, and ESXi I had used a single flash drive and simply re-imaged it for each install. This drive was the root cause of all my issues. After using a newer Flash Drive I had experience zero issues. In fact I am now running a 4 port LAG on FreeNAS and a 40Gb SFP+ DAC to my ESXi Host and it works great! Whether that drive had bad flash chips or a root kit installed... I don't know, but I am glad to see everything purring along and working. What a weird issue. I always tried to eliminate single points of failure when it comes to network integrity. But I never thought to check my installation media... Lesson Learned. I can only imagine what this would've been like had I been managing a real enterprise network with thousands of computers. The more I learn about networking and technology, the more I realize how much I have to learn.
 

Attachments

  • 2017-04-16 14-27-22 2480.jpg
    2017-04-16 14-27-22 2480.jpg
    160.2 KB · Views: 684
Status
Not open for further replies.
Top