NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
M4300 spine and leaf with more than 8 switches
I'm upgrading our networking infrastructure using M4300 switches which I was planning on installing in a spine and leaf topology. In location A we have a pair of 12X12F's that we're going to use as the spine, two 52G's for the server racks, and five 52G-PoE+ for workstations, phones, APs which will be the leaves. A sixth 52G-PoE+ may be added in the near future. In location B we have two 8X8F's as the core, and three 52G-PoE+ as the leaves. Location A and B are connected by WAN.
Obviously I'm going to need more than one stack at location A due to the eight switch limit. Should I even create stacks? With multiple stacks, how would I best handle inter-VLAN routing? I'm also planning to incorporate 802.1x port authentication if that makes a difference. Suggestions?
Hi Greg,
For your 1st question, " what will I do if I need to add another 52G-PoE+ leaf? "
I have add six M4300-52G-PoE+ as leaf In example "Location A" just as above reply.
So your new M4300-52G-PoE+ will work together with leaf-spine stack same with other five M4300-52G-PoE+.
2nd " 12X12F switches in a leaf-spine stack with the two 52G (non-PoE) switches,The PoE switches would then be made into a normal stack,"
I just suggest you to put M4300-52G-PoE+ into leaf-spine stack, because the five(six) M4300-52G-PoE+ need leaf-spine topology more than two M4300-52G in your network topology design.
The five(six) M4300-52G-PoE+ is access layer and M4300-12X12F is core, it's a typical topology in leaf-spain network.
But you can also add two M4300-52G into leaf-spine stack instead of five(six)M4300-52G-PoE+ just as you with.:smileyhappy:
3rd " When connecting the stacks together, how would the LAG memberships be best configured between the stacks? Static or Dynamic? STP? Enhanced Hashing mode?"
The dynamic mode(LACP) will offer a better reliability link than static mode.
I suggest you to configure LAG type to dynamic mode(LACP).
You need to chose a hashing mode on LAG accord with your real network traffic due to every hashing mode has different purpose.
such as:
Src MAC,VLAN,EType,incoming port
this mode just used for the packets came form different port with different source mac-address or 802.1q VLAN tag or Ethernet Type.
Src IP and Src TCP/UDP Port Fields
this mode just used for the packets with different source IP address and source TCP/UDP port
Please check more information about other hashing mode as below:
4th "Should I be using dynamic routing protocols between the three stacks? Any other suggestions?"
This is not necessarily to chose dynamic routing protocol between three stacks.
For location A,
The static route will work fine with simple L3 network just like yours due to many switches worked into same stack.
Or you can use OSPF to connect stack A and stack B because its worked in a same LAN due to more reliability and expandability.
For location B,
You said it connected to location A with WAN, I'm not sure your ISP allow dynamic routing protocol or not.
So please use the special protocol (OSPF/RIP/static route) accord with the regulation from ISP.
May the solution help you.:smileyhappy:
Regards,
Daniel.
5 Replies
Replies have been turned off for this discussion
Hi Greg,
Welcome to NETGEAR community！:smileyhappy:
We had analyze your question carefully and I want to share a spine and leaf stacking design example for you.
For location A,
Please setup two stack as below:
In leaf-spine stack A, every M4300-52G-PoE+(Leaf) need to connect with two M430012X12F(Spine).
In normal stack B, the link to Stack A should be LAG and through every member with LACP mode on both side.
For location B,
Please setup the stack as below:
Please check document carefully before you configure stack on M4300.
M4300 Software Administration Manual -
-->Chapter 21-Manage switch stacks
-->Page 311 -802.1X.
-->Chapter 5 -VLAN routing.
When you configure inter-VLAN routing and 802.1X function on stack, please deploy it just as usual on a standalone switch.
The stack will work normally just as a standalone switch that has multi-unit and mutli ports.
For the link type of stack, please chose copper / fiber module / DAC as you wish.:smileyhappy:
Please reference to example about spine and leaf stack as below when you want to deploy new stack:
Looking forward to your reply:smileyhappy:
Daniel,
Thanks for the welcome, and wow, thanks for the very detailed reply!
Your example is very helpful, but what will I do if I need to add another 52G-PoE+ leaf? I'm thinking it might be better to have the 12X12F switches in a leaf-spine stack with the two 52G (non-PoE) switches. The PoE switches would then be made into a normal stack, which I'd connect to the spine and leaf stack, but with more than just two 10G links. This would give me room for expansion in both stacks.
When connecting the stacks together, how would the LAG memberships be best configured between the stacks? Static or Dynamic? STP? Enhanced Hashing mode?
Should I be using dynamic routing protocols between the three stacks? Any other suggestions?
Hi Greg,
For your 1st question, " what will I do if I need to add another 52G-PoE+ leaf? "
I have add six M4300-52G-PoE+ as leaf In example "Location A" just as above reply.
So your new M4300-52G-PoE+ will work together with leaf-spine stack same with other five M4300-52G-PoE+.
2nd " 12X12F switches in a leaf-spine stack with the two 52G (non-PoE) switches,The PoE switches would then be made into a normal stack,"
I just suggest you to put M4300-52G-PoE+ into leaf-spine stack, because the five(six) M4300-52G-PoE+ need leaf-spine topology more than two M4300-52G in your network topology design.
The five(six) M4300-52G-PoE+ is access layer and M4300-12X12F is core, it's a typical topology in leaf-spain network.
But you can also add two M4300-52G into leaf-spine stack instead of five(six)M4300-52G-PoE+ just as you with.:smileyhappy:
3rd " When connecting the stacks together, how would the LAG memberships be best configured between the stacks? Static or Dynamic? STP? Enhanced Hashing mode?"
The dynamic mode(LACP) will offer a better reliability link than static mode.
I suggest you to configure LAG type to dynamic mode(LACP).
You need to chose a hashing mode on LAG accord with your real network traffic due to every hashing mode has different purpose.
such as:
Src MAC,VLAN,EType,incoming port
this mode just used for the packets came form different port with different source mac-address or 802.1q VLAN tag or Ethernet Type.
Src IP and Src TCP/UDP Port Fields
this mode just used for the packets with different source IP address and source TCP/UDP port
Please check more information about other hashing mode as below:
4th "Should I be using dynamic routing protocols between the three stacks? Any other suggestions?"
This is not necessarily to chose dynamic routing protocol between three stacks.
For location A,
The static route will work fine with simple L3 network just like yours due to many switches worked into same stack.
Or you can use OSPF to connect stack A and stack B because its worked in a same LAN due to more reliability and expandability.
For location B,
You said it connected to location A with WAN, I'm not sure your ISP allow dynamic routing protocol or not.
So please use the special protocol (OSPF/RIP/static route) accord with the regulation from ISP.
May the solution help you.:smileyhappy:
Regards,
Daniel.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
