XG-7100 and 2 Stacked Netgear Switches
-
First: Those switches are not "stacked."
Stacked switches utilize special, usually-proprietary protocols to connect two or more switches so they operate as one unit. You are simply connecting two switches with a VLAN trunk/tagged port.
I would concentrate on ONE aspect of your design and make that work. I am unsure what you are doing with all of those physical router interfaces going to the switch.
I would probably LACP two, three, or four of the expansion port NICs to the switch and just trunk VLANs there unless you KNOW you're going to be pushing 800Mbit+ on them all. That way if a VLAN needs more than a gigabit, there is at least the possibility LACP can give the bw needed - depending on the type of traffic it is carrying. Keep in mind that the aggregate bandwidth from the built-in switch to the XG-7100 SoC is 5 gigabits (2 x 2.5Gbit links in a LAG. Switch ports 9 and 10 to SoC ports ix2 and ix3 (lagg0))
-
First: Those switches are not "stacked."
Stacked switches utilize special, usually-proprietary protocols to connect two or more switches so they operate as one unit. You are simply connecting two switches with a VLAN trunk/tagged port.
I would concentrate on ONE aspect of your design and make that work. I am unsure what you are doing with all of those physical router interfaces going to the switch.
I would probably LACP two, three, or four of the expansion port NICs to the switch and just trunk VLANs there unless you KNOW you're going to be pushing 800Mbit+ on them all. That way if a VLAN needs more than a gigabit, there is at least the possibility LACP can give the bw needed - depending on the type of traffic it is carrying. Keep in mind that the aggregate bandwidth from the built-in switch to the XG-7100 SoC is 5 gigabits (2 x 2.5Gbit links in a LAG. Switch ports 9 and 10 to SoC ports ix2 and ix3 (lagg0))
In regards to the "Stacked" configuration yes this is true. The two models of switches that I am running do not support the stacking feature that Netgear has since they are not from the same model or series number. As far as the unsure part as to what I am trying to do with all the interfaces connected to the switch, I am trying to have each interface act as a separate VLAN. Your suggestion on using LACP seems interesting I wonder if it would be easier to get that going than what I have been trying. Also in regards to the SoC I have all the lower priority stuff that wont use that much bandwidth on those ports. The additional 4-port NIC is where I seperated stuff like server traffic and a vMotion network. All the VLANS on the SoC seem to work on both switches I am assuming because they are switched and not separate interfaces but the 4 port NIC add-on I have not been having much luck with. Hope that helps and I appreciate you taking the time to reply.
-
Your storage should simply not go through your firewall period. It should be a blank VLAN with your host storage interfaces and your storage device(s).
Storage through the firewall will just plain suck. Zero reason to do that.
-
Oh. I didnt know that. Then most of this headache will go away because thats where I was having the big issue. I wanted to set storage up first before anything so that has been the sticking point for me. So okay cool! I will add FreeNAS to my primary LAN network and then go from there. ESXi trunking is the next phase of my project. I appreciate that.
-
I would make a dedicated storage VLAN but that's probably just me.
-
ahh shoot… thats what i was trying lol VLAN 90 was supposed to be for storage only the issue i was having was that I wasnt getting a DHCP address and couldnt ping that gateway when trying it. I honestly think it may have something to do with FreeNAS though. I think I am supposed to tag all VLANS except 1 (untagged) on the trunk port connecting both switches. I think from what I am understanding the Access ports (Ports connecting to end devices need to be untagged members of their vlans) I hope I am soaking all this information in correctly or I am about to tear some stuff up lol.
-
Not sure why you need DHCP on your SAN/Storage.
-
Not sure why you need DHCP on your SAN/Storage.
LOL thats not the intended design i only did it to see if it would get an address. I had a static address on it before but was not able to ping the gateway. I switched it to DHCP to see if it would at least pull an address from it eventually while I was changing port configs on the switch. I'm new but not that new :D
-
Not sure why you need DHCP on your SAN/Storage.
I actually just said "forget it" and reset everything. Now I only have one Network (LAN 10.1.1.x) and am going to try to take this slow. Am I able to make separate posts for each thing when I run into it or is that frowned upon? My first thing I want to get down is creating the VLANS on pfSense correctly before even getting into the switches.
-
Several posts with each restricted to a very specific issue is fine IMO. Often easier to diagnose issues like that. Long rambling posts encompassing numerous issues can be hard to follow but do sometimes allow a better overall picture of the issues.
If you're not using those 10GbE ports for anything else eight now I'd pick up a direct attach cable and use that to the switch. Assuming they are physically local. Better total throughput in almost any situation. Only drawback there is no failover if that one connection does fail but there are multiple other single points of failure so it's not really an increased risk.
Steve
