We have the CISCO SG300 28 port switch. I have noticed some log warning that appear like this:
2147451055 2017-Aug-30 11:35:01 Warning %NT_GREEN-W-EeeLldpMultiNeighbours: Multiple LLDP neighbours on port gi12 - EEE operational state is FALSE 2147451230 2017-Aug-30 11:35:01 Warning %NT_GREEN-W-EeeLldpSingleNeighbour: Single LLDP neighbour on port gi12 - EEE operational state can be TRUE 2147451405 2017-Aug-30 11:29:35 Warning %NT_GREEN-W-EeeLldpMultiNeighbours: Multiple LLDP neighbours on port gi12 - EEE operational state is FALSE
My initial research yielded that this is likely caused by a user/port/LAN that has multiple devices on it. That is true in my case. Port GE12 is connected to one of our offices that has limited ethernet jacks, so we run separate ethernet cables from the desktop and IP phone into an unmanaged switch, and from there they become one, connecting to a single ethernet jack. (to help explain this I have included a diagram below)
Assuming that this setup is what is causing the error I am wondering how I can resolve it. Is there a specific setting that I can configuration that will be more optimized for the way port GE12 is setup?
Any reference I have seen to trunk ports (maybe in the VLAN settings?) has all ports, including GE12, set to trunk. Does the tagged/untagged setting make any difference? I am fairly certain they are all untagged as well.
If it isn't obvious already, my knowledge of CISCO switches, or any managed switch, is almost non-existant. So I apologize in advance if I say something that doesn't make any sense :)
Got it. I will have to look over the settings again. Was I correct earlier the ability to set trunked is in the VLAN settings?
Understood. I appreciate the suggestion. I will look into it when I get back into the office tomorrow.
I decided to come back into the office tonight to investigate your suggestion, and all ports are indeed trunked. Sadly, on arrival the switch was in boot error again. This is actually the real issue I am trying to resolve, the warning message in this topic was just a lead I was chasing down, which I hoped was the cause.
Just for the hell of it I have copied in the log file from tonight. It doesn't really show much in the way of a major event that might have caused it to restart or lose connection. I'm hoping someone has a suggestion or two that I can investigate further.