Join us for a month-long contest with heaps of swag to win!Learn More ›
We have one network with two switches plugged directly into the firewall Mx84. Upon looking at the topology for this network, there is a red diamond on the leg to the second switch. The message, when the cursor is hovered over it is, "A switch was detected that improperly forwards LLDP packets. This can cause your network topoplogy to be incomplete or incorrect."
I read somewhere that you should not connect more than one switch to the firewall, and that switches should be connected to each other. Is this correct? Also how do I solve this issue.
Thanks in advance.
Yes as Phil mentioned you either have something between the MX and MS unit. If not try rebooting them both and see if it comes right. If that doesn't work Open a support case.
Just another quick thought you haven't recently added the MS unit on the link thats reporting the error have you? it could simply be the dashboard hasn't updated yet.
Do you have pair of MX's and are those directly connected together with cable? Recommended topology is that there is not direct connection between MX's. https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair#Fully_R...)
I am seeing similar thing on my network:
Does Sonos devices caused STP issues since they are connected via ethernet and also WiFi?
Hi there all,
I have just done a virgin install of an MX84, MS120/24 and MS120/8 and am seeing the same error / issue, I have no dumb switches or anything else in the mix, thoughts would be appreciated.
I have the same issue.
I have Three MS120 Switches connected to the MX84.
And the red diamond moves between them when i refresh the screen!
Two screenshots below for reference.
Im thinking this means that the MX does not like having multiple MS120 switches connected to it perhaps?
I did indeed solve mine.
I put a pair of MS210 switches in the mix acting as Agg Switches in a Physical Stack.
Now i get a consistent topology page with no LLDP errors.
The main thing i dont like now, is that it makes it look like the MX device is downstream of the switch stack instead of being upstream of the switch stack.
But apart from that, no issues