Should client MAC addresses be hitting my core via LLDP

[Jaan]

I'm getting a lot of these on my core switch logs:

 

*May 10 14:36:56: %LLDP-4-AGEOUTREM: Port TenGigabitEthernet 1/0/5 one neighbor aged out, Chassis ID is 0.0.0.0, Port ID is 805e.c098.467d.

*May 10 14:33:55: %LLDP-4-CREATEREM: Port TenGigabitEthernet 1/0/5 created one new neighbor, Chassis ID is 0.0.0.0, Port ID is 805e.c098.467d.

*May 10 14:25:07: %LLDP-4-TOOMANYREM: Failed to create new neighbor for the neighbor number on Port TenGigabitEthernet 2/0/10 reached max 5.

*May 10 14:18:02: %LLDP-4-TOOMANYREM: Failed to create new neighbor for the neighbor number on Port TenGigabitEthernet 2/0/14 reached max 5.

*May 10 14:16:52: %LLDP-4-CREATEREM: Port TenGigabitEthernet 1/0/12 created one new neighbor, Chassis ID is 54b2.0371.27b9, Port ID is 54b2.0371.27b9.

*May 10 14:15:37: %LLDP-4-AGEOUTREM: Port TenGigabitEthernet 1/0/12 one neighbor aged out, Chassis ID is b4a9.fc89.2e27, Port ID is b4a9.fc89.2e27.

*May 10 14:15:05: %LLDP-4-CREATEREM: Port TenGigabitEthernet 2/0/14 created one new neighbor, Chassis ID is 54b2.0371.281c, Port ID is 54b2.0371.281c.

*May 10 14:14:28: %LLDP-4-AGEOUTREM: Port TenGigabitEthernet 2/0/14 one neighbor aged out, Chassis ID is f4b5.201d.d318, Port ID is f4b5.201d.d318.

 

MACs relate to client MOBOs

 

We use LLDP/med on the access/edge switches to drop the voip phone onto another vlan.

 

Thought the only neighbours on my core should be edge switches from the AGG link from edge to core.

 

any thoughts?

[Jaan]

Any thoughts....

 

i'm not having any network issues as such..... just lots of these errors in the logs

[psydii]

So what are actually connected to ports 1/0/5, 1/0/12 and 2/0/14?

[Jaan]

Each port is connected to an edge access switch. With each core port being connected to the edges via LAGG

 

[psydii]

Never used an FS switch, and its been a decade since I used a v1910 (the best value switch ever made. IYKYK)

 

I'd be tempted to suggest it might be a) a bug - are the switch's firmware fully up to date? b) just the way LAGG works in this combination of settings c) an artefact of some other services running on the network, perhaps multicast name resolution or some IPV6 thing?

 

Absent any knowledge on the software side... what happens if you unplug on of the uplinks?

[Jaan]

Never used an FS switch, and its been a decade since I used a v1910 (the best value switch ever made. IYKYK)

 

I'd be tempted to suggest it might be a) a bug - are the switch's firmware fully up to date? b) just the way LAGG works in this combination of settings c) an artefact of some other services running on the network, perhaps multicast name resolution or some IPV6 thing?

 

Absent any knowledge on the software side... what happens if you unplug on of the uplinks?

 

The HP aren't up to date as we have 3rd party sfp modules that defo brick when we run newer firmware........ That being said the edges are being replaced, so i guess i'll worry about it if it continues after that.

 

FS switches are fully up to date.

 

If i unplug the links i'll to access to that edge so can't do that at the mo as very in production.

 

I guess wireshark might give answers... once i figure it out

[psydii]

Typo in my orginal post... unplug one of the uplinks. TBH I'm just applying basic troubleshooting techniques in the hope something pops up in the logs/behaviour that helps clue you in to the root cause.