NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
M4300 24X24F Stack Bandwidth
Hi, we are trying to build a core setup with 4x M4300 24x24 switches. We want to split the core into 2 switches per fire zone, but keep them working as one logical unit by using stacking in ring...
Hi Norbert_T
Thank you for your message and congratulations, NETGEAR M4300 series is world-class for high performance and nonstop forwarding (NSF) stacking topologies.
If System \ Stacking \ Advanced \ Stack-port Diagnostics show 1 path, it might indicate other "stack ports" are not working. Are we sure System \ Stacking \ Advanced \ Stack-port Configuration shows all your Stack Ports with "stack" in both Configured Stack Mode and Running Stack Mode for ALL units?
If not, the stack should be initialized again, one switch after the other?
Please let the Community know.
Regards,
Hi LaurentMa,
thanks for your fast response. Reint of stack did not help, current firmware is 12.0.2.6, Please see my configured Stack-Ports
Thanks, Norbert
SW1
1 0/19 SFP+ AXM761 Stack Stack Link Up 10
1 0/21 SFP+ AXM761 Stack Stack Link Up 10
1 0/23 SFP+ AXM761 Stack Stack Link Up 10
1 0/43 Stack Stack Link Up 10
1 0/45 Stack Stack Link Up 10
1 0/47 Stack Stack Link Up 10
SW2
2 0/19 SFP+ AXM761 Stack Stack Link Up 10
2 0/21 SFP+ AXM761 Stack Stack Link Up 10
2 0/23 SFP+ AXM761 Stack Stack Link Up 10
2 0/43 Stack Stack Link Up 10
2 0/45 Stack Stack Link Up 10
2 0/47 Stack Stack Link Up 10
SW3
3 0/19 SFP+ AXM761 Stack Stack Link Up 10
3 0/21 SFP+ AXM761 Stack Stack Link Up 10
3 0/23 SFP+ AXM761 Stack Stack Link Up 10
3 0/43 Stack Stack Link Up 10
3 0/45 Stack Stack Link Up 10
3 0/47 Stack Stack Link Up 10
SW4
4 0/19 SFP+ AXM761 Stack Stack Link Up 10
4 0/21 SFP+ AXM761 Stack Stack Link Up 10
4 0/23 SFP+ AXM761 Stack Stack Link Up 10
4 0/43 Stack Stack Link Up 10
4 0/45 Stack Stack Link Up 10
4 0/47 Stack Stack Link Up 10
In System --> Stacking --> Stack-port Diagnostics ---> ALL, I can see the following Stack-Port packet path:
| Direction | Packet-path |
| from unit2 to unit1 | unit-2 port 2/0/43 to unit-1 Total hop count: 1 |
| from unit3 to unit1 | unit-3 port 3/0/19 to unit-1 Total hop count: 1 |
| from unit4 to unit1 | unit-4 port 4/0/21 to unit-1 Total hop count: 1 |
Hi LaurentMan,
I upgraded to firmware 12.0.2.20 and did a complete factory reset. After that I tried to build a stack between SW1 and SW2 by using 3x 10G copper connections. The packet-path summary shows, that only one stack connection is used.
For me this means that only 1x 10G port is in use, while port 2/0/45 + 2/0/47 are not.
Thanks, Norbert
Direction Packet-path
from unit2 to unit1 unit-2 port 2/0/43 to unit-1
Total hop count: 1Hi Norbert_T
I suspect an interpretation issue here, packet path is just a summary for the number of "hops" from one switch in the stack, to the other, when a packet needs to travel to reach its destination. The 2/0/43 physical interface is taken as the "main" one and shows up in the packet path summary. It shouldn't mean the other Stack Ports don't work, the other ports are considered as the same "path" from a switch-to-switch route standpoint. Your Stack Port configuration summary shows all 6 Stack Ports (per switch) running at 10G in Stack mode, so the stack algorithm should already parse traffic across all ports (load-balancing scheme).
I am exploring this "display issue" and will come back later on it. In the meantime, we need to control how your 3 x Copper and 3 x Fiber Stack Ports behave on each switch. Can you post the output of following two stacking commands (please consult M4300-24X24F support page, the CLI manual, Stack Port commands section starting page 38). Log in the M4300-24X24F stack using CLI, either local console or remote telnet/ssh, go (M4300-24X24F) >enable and enter the two commands:
(M4300-24X24F) #show stack-port
and
M4300-24X24F) #show stack-port counters all
If the stack is up and running, we should see the link status and the link speed for each of your Stack Ports with the first command, and the statistics (data rates, error rates, total errors, link flaps) for each of your Stack Ports with the second command. There should be no doubts left with it.
Thank you very much!
Regards,
Hi Norbert_T
I confirm it is normal that the diagnostics show one port only, this port makes part of your Stack Ports and the packets can use any Stack Port, a little bit like in a LAG. I agree the unique port number can cause some confusion as you were expecting to see 3 ports from one switch to the other. We may want to enhance the Diagnostics table with the switch to switch route (number of hops) but without the port numbers, or with all of them. Thank you for reporting this cosmetic issue: please run the commands I provided and let us know if you have any doubt left.
Regards,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
