SG-2100 packetloss in internal 5 port switch
-
@keyser Have you tested the 25.07-RC on it? Funny, that reddit post you linked to has a reply from me 3 years ago, so I guess I encountered this same issue too (I'd forgotten).
-
@luckman212 No, and that’s obviously the next step.
I don’t have any hopes of improvement though.Do you know if there is any tweaks to be done with software on the built in Marvell switch? Buffers, see packetdrops and such
-
-
Did you try enabling dot1q mode and trunking the VLANs through the internal switch on one port? Hard to see why that would be any different but....
Did you try a different external switch?
-
@stephenw10 said in SG-2100 packetloss in internal 5 port switch:
Did you try enabling dot1q mode and trunking the VLANs through the internal switch on one port? Hard to see why that would be any different but....
Did you try a different external switch?
Yes, I tried all combinations, and the issue remains as long as the builtin switch is the connection to the Internal aruba Switch.
-
Hmm, do you only see it when connected to that one external switch though. I've never seen that but I also don't have that switch. That would seem very odd though.
-
@stephenw10 Unfortunately I don't have another switch to test with, so I cannot rule out its a specific link issue between Aruba CX 6100 switches and netgate 2100s. But it might seem that is the case.
The Aruba switch does not show any link issues, dropped packets, CRC errors or speed negotiations after link is established
-
And I assume they are linked at 1G auto-select?
-
@stephenw10 Yes, both ends are 1000 auto by default and I have tried fixing them to 1000 FDX fixed with no luck.
Also - If I limit the client uplink to 100Mbps so the speed cannot really put heavy pressure on the 2100, the problem still arises.
So it's most definitively an issue with the stability of the link or some buffer bursting as seen from the builtin 5 port switch side. -
Just as a followup, I have been unable to solve this issue, and it happens with two different 2100’s.
So the workaround for now is to use mvneta0 as the uplink to the switch carrying multiple VLANs in a 802.1q trunk (leaves the builtin 5 port switch out of the inter VALN routing).
At some point I will try with another managed switch model to see if it’s the specific Switch/SG-2100 combination only, or a general issue.
