Systems side of networking is a lot more complicated than I thought

[geopfarth]

So I am having a hard time setting up the networking properly on my server. As this is a home network, I am running a single VLAN, and using a Netgear Nighthawk X6 as the DHCP server. I roped off everything above .209 for the server, and I added a 16 port Netgear Prosafe GS116Ev2 for breakout to the various TVs, entertainment centers and the server.

The switch is capable of creating a LAG, and the server has 4 ethernet ports capable of LACP as well. I noticed that one of the ports on the server immediately auto configured to 100M, while the other 3 stayed at 1G. I am assuming the 100M port is the IPMI port, or reserved for managing the NAS.....the network page on the server is delightfully free of that kind of specificity.

After reading all of the very useful information about configuring LACP, I am still unclear on how to set up the server.

The threads seem to say I only need one network interface because I have a very small network and very few nodes will be accessing the server (basically Plex only system). However, if the first port configured sets itself to 100M, I believe I will get a bottleneck in throughput when trying to run multiple streams.

I initially tried to set up a LAG that encompassed 2 of the remaining 3 ports, but I couldn't access any of the plugins or jails I set up.

Any help on this would be appreciated. I get the feeling from all of the threads that this is really basic for most of you, but this is really the first time I have tried to configure any server from scratch. I usually just spin up the port channels and let my systems team handle the servers at work.

 

[Ericloewe]

Most people just don't bother. You gain little and it's always a headache to get working and the first thing to break.

 

[chris crude]

I only have a learners permit in network management/administration, but I think it's safe to say that even if multiple plex streams are running concurrently you would choke your servers processing power before you would choke your network bandwidth. If you want to learn more about these things then no-one can fault you for wanting to learn more, but I don't think only using one network interface will hurt your use case.

 

[geopfarth]

Most people just don't bother. You gain little and it's always a headache to get working and the first thing to break.

So, how do I get a single port to auto configure to 1G instead of the 100M that always seems to come up? Forcing it to 1G on the switch seems to also cause issues.

 

[craigdt]

Setting up LACP, its pretty easy via the FreeNAS side of things, you can find excellent documentation for it here: http://doc.freenas.org/9.10/network.html

Setting up the Netgear for LACP you will have to consult its documentation, I found it wasn't as intuitive when I did it on my Cisco switches. (Don't get me started when I updated their firmware and they changed all the interfaces) but then I'm only a software developer, not really my area of expertise ;)

In regards to your VLAN's that could be a different matter, unfortunately I have no experience in setting up VLAN's on FreeNAS, even though the documentation suggests its reasonably easy. Will probably do that soon myself as my current VLAN setup is less than ideal for flexibility...

The Ethernet ports on your server you mention, what model motherboard are you using, I find it strange that you have 4 ports and not 5 if you actually do indeed have a IPMI port ? But yes, 100mbit port does indeed sound like the IPMI port, either that or a faulty port/cable...

 

[geopfarth]

Setting up LACP, its pretty easy via the FreeNAS side of things, you can find excellent documentation for it here: http://doc.freenas.org/9.10/network.html

Setting up the Netgear for LACP you will have to consult its documentation, I found it wasn't as intuitive when I did it on my Cisco switches. (Don't get me started when I updated their firmware and they changed all the interfaces) but then I'm only a software developer, not really my area of expertise ;)

In regards to your VLAN's that could be a different matter, unfortunately I have no experience in setting up VLAN's on FreeNAS, even though the documentation suggests its reasonably easy. Will probably do that soon myself as my current VLAN setup is less than ideal for flexibility...

The Ethernet ports on your server you mention, what model motherboard are you using, I find it strange that you have 4 ports and not 5 if you actually do indeed have a IPMI port ? But yes, 100mbit port does indeed sound like the IPMI port, either that or a faulty port/cable...

I am running a Supermodel X9 server with a X9DR3-LN4F+ motherboard. It has 5 connections but I only have 4 cables available where I set up the server. I could use 1 of the 4 for that IPMI port but it seemed to have issues when I booted up the server the first time. I just set up the 4 pack and moved on.

The switch has a really basic GUI for management. You can turn on a LAG using up to all 16 ports, but there are no other options.

Thanks for the link, I have read that about 5 times and I still don't really understand everything in there.

 

[Spearfoot]

I am running a Supermodel X9 server with a X9DR3-LN4F+ motherboard. It has 5 connections but I only have 4 cables available where I set up the server. I could use 1 of the 4 for that IPMI port but it seemed to have issues when I booted up the server the first time. I just set up the 4 pack and moved on.

The switch has a really basic GUI for management. You can turn on a LAG using up to all 16 ports, but there are no other options.

Thanks for the link, I have read that about 5 times and I still don't really understand everything in there.

Yes, the X9DR3-LN4F+ has 4 gigabit ethernet ports grouped together in a bloc - they're the ones you want to use in your LAG group, and these should always link up at 1 Gbps.

The fifth port linking at 100 Mbps is the IPMI port and you use it for remote administration of the server. IPMI is a great tool, and once you get used to it you'll wonder how you ever got by without it! You configure the network settings for this port in the system BIOS.

 

[craigdt]

I am running a Supermodel X9 server with a X9DR3-LN4F+ motherboard. It has 5 connections but I only have 4 cables available where I set up the server. I could use 1 of the 4 for that IPMI port but it seemed to have issues when I booted up the server the first time. I just set up the 4 pack and moved on.

The switch has a really basic GUI for management. You can turn on a LAG using up to all 16 ports, but there are no other options.

Thanks for the link, I have read that about 5 times and I still don't really understand everything in there.

It seems Spearfoot beat me to an answer in regards your motherboard Ethernet ports, very nice motherboard if I do say so myself.

Unfortunately I found the manual to your switch: http://www.downloads.netgear.com/files/GDC/GS105EV2/WebManagedSwitches_UM_EN.pdf#page21

(It is the same manual for a bunch of models so don't be put off with the model in the URL, it is stated earlier on in the PDF)

And unless I'm mistaken, I found this in it:

"Note: The switch does not support IEEE 802.3ad Link Aggregation or Link Aggregation Control Protocol (LACP) groups. The switch supports manual static LAGs only."

 

[pschatz100]

So I am having a hard time setting up the networking properly on my server. As this is a home network, I am running a single VLAN, and using a Netgear Nighthawk X6 as the DHCP server. I roped off everything above .209 for the server, and I added a 16 port Netgear Prosafe GS116Ev2 for breakout to the various TVs, entertainment centers and the server.

The switch is capable of creating a LAG, and the server has 4 ethernet ports capable of LACP as well. I noticed that one of the ports on the server immediately auto configured to 100M, while the other 3 stayed at 1G. I am assuming the 100M port is the IPMI port, or reserved for managing the NAS.....the network page on the server is delightfully free of that kind of specificity.

To the OP: For troubleshooting, it would be helpful to understand a few things about your set up:
1) What do you mean by "roping off" everything above .209 for the server?
2) What are you trying to accomplish with LACP?
3) Are the connections to your TV's and entertainment centers all wired? How many, and why the need for the Netgear Prosafe GS116Ev2?
4) What is connected to the port that's running at 100M? Even if the network page does not report device names, it should report mac addresses and you can figure out which device is connected from its mac address (yes, even IPMI has a mac address.)

 

[geopfarth]

To the OP: For troubleshooting, it would be helpful to understand a few things about your set up:
1) What do you mean by "roping off" everything above .209 for the server?
2) What are you trying to accomplish with LACP?
3) Are the connections to your TV's and entertainment centers all wired? How many, and why the need for the Netgear Prosafe GS116Ev2?
4) What is connected to the port that's running at 100M? Even if the network page does not report device names, it should report mac addresses and you can figure out which device is connected from its mac address (yes, even IPMI has a mac address.)

1) I set up my DHCP scope to stop at .209. Everything from 210 - 254 is available for Jails/plugins
2)during initial setup, I was trying to increase transfer rates from my old server to the new one. Having dual NICs in the old gaming rig I was originally using as a Plex server, I figured I could increase the transfer rate a little. It doesn't really matter now that all the data is over there, it would have been nice to have but it wasn't a requirement.
3) I have 5 port 1G switches at each TV/Entertainment Center, all of those connect back to to Netgear switch. I am currently running a single network, no VLANs. I was playing with the idea of using a Cisco 3750 from work that we are retiring. But right now it seems like overkill.
4) I fixed that issue as well.

Thanks for continuing to offer assistance! I appreciate any advice I can get.

 

[FreeNASftw]

Most people just don't bother. You gain little and it's always a headache to get working and the first thing to break.

This ^^ - I set it up just because I could and now have all kinds of fun troubleshooting issues with it.

Also, what others have said, a single Gb connection will stream multiple HD streams no problems.

Lastly, SMB 3 supports multichannel streaming - this isn't LAGG but multiple independent connections to the source. I haven't played with this as I simply have no need but it may be of interest to you (and me when I get sick of LAGG).

 

[pschatz100]

1) I set up my DHCP scope to stop at .209. Everything from 210 - 254 is available for Jails/plugins
2)during initial setup, I was trying to increase transfer rates from my old server to the new one. Having dual NICs in the old gaming rig I was originally using as a Plex server, I figured I could increase the transfer rate a little. It doesn't really matter now that all the data is over there, it would have been nice to have but it wasn't a requirement.
3) I have 5 port 1G switches at each TV/Entertainment Center, all of those connect back to to Netgear switch. I am currently running a single network, no VLANs. I was playing with the idea of using a Cisco 3750 from work that we are retiring. But right now it seems like overkill.
4) I fixed that issue as well.

Thanks for continuing to offer assistance! I appreciate any advice I can get.

So it looks like everything is now working as you like? That's great. I would suggest that you avoid assigning IP addresses above .250. Some internet providers like to use the high IP addresses for their own purposes. Just something to keep in mind.

 

[geopfarth]

So it looks like everything is now working as you like? That's great. I would suggest that you avoid assigning IP addresses above .250. Some internet providers like to use the high IP addresses for their own purposes. Just something to keep in mind.

I will keep it in mind, thanks. Right now I only have the Plex jail running so I don't need to worry about it yet.