NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
M4300 stacking problems
I'm trying to create an 8 switch spine and leaf stack with two XSM4324S (M4300-12X12F) and six GSM4352PB-100NES (M4300-52G-PoE+) and I'm having some major issues. The stack created fine with 7 of the...
Hi again Dainel,
The stack ports of the two 12x12f switches are set to Management and OprStandby with priority 15 and 14 respectively. All of the PoE switches have undefined priority and are Stack Members. The switches are connected with either DAC, CAT6 (to stack ports), SMF, or MMF. The DACs and all transcievers are NETGEAR compatible from FiberStore. Diagram below. The switches that aren't stacking properly are Access-7 and Access-8. I'll get the diagnostic files uploaded shortly. Access-8 is not currently connected to the stack as I need the devices connected to it uplinked to our network. Currently the access stack shown is uplinked to our existing core switch (not shown) during transition.
I just noticed.. On the diagram, the uplinks from the CORE stack to the firewall are only 1G, not 10G even though the legend says it all is.
Hi Greg,
I suggest you to upgrade the M4300 to latest firmware before we continue troubleshooting this case.
You can find the firmware from following link:
M4300 Firmware Version 12.0.2.10
I also have some question and suggestion for you.
1. The port link between stack_1 and stack_2 should be Ethernet mode not the Stack mode.
(I can't see the LAG configure on master/standby.)
2. Could you share us the techsupport file on stack_2?
I'll see if I can get the firmware updated tonight. The LAG ports are all ethernet, and right now only one is connected and it isn't configured as a LAG. They were, but it kept going down. One side would report "D-Disabled" and I couldn't fix it, so I broke the LAG and am just using one uplink right now. I was going to save that problem for another post. I can still upload the tech support for the other stack though when I get into the office in a couple of hours.
Hi Greg,
Looks like a STP BPDU storm appeared in this topology of port LAG 1 on Stack_1.
lag 1 D-Disable Down Disable N/A Disable lag 2 Enable Up Enable N/A Disable lag 3 Enable Up Disable N/A Disable lag 4 Enable Up Disable N/A Disable
So the port which get many STP BPDU packets will shutdown as D-Disable.
I suggest to check the link first if any loop exist probably.
1. Check the link of Stack_2 .
2. Check the link of Stack_1 .
3. Check the link between Stack_1 and Stack_2.
If the error appeared all the same after the loop disappear.
The best way to resolve your concern is creating online support case form here about stack configuration and PVSTP design.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
