11-19-2019 02:49 PM
I have a few AP650's telling me they're connected to the same port on the same switch (They may in fact all come through that uplink, but are definitely connected to another switch first)
I also have an AP30/ATOM unit that thinks it's connected to an HP 5412zl - problem is we've retired that switch quite a while ago.
Just curious what I can do to force this information to refresh, thanks!
02-26-2020 03:15 PM
Ok. I have to clarify something here and admit my mistake. In looking through my column picker I've now included the lldp sys name for Eth0 and Eth1. So it's not that some APs aren't sending the information. All APs are sending lldp info. my bad.
My problem is related to having both Eth ports in use and how the AP handles redundant config. Some APs are "up" on both interfaces while others are only up on one. I'll start a new thread for this topic.
Sorry again for confusing the discussion.
I will add though, @Brian Frappier have you considered disabling the cdp option in the network policy>additional options>network services>LLDP/CDP to see if that at least works as a work around?
02-25-2020 03:22 PM
Looking at two more APs where AP1 is reporting lldp info to ECIQ and AP2 is not, the only difference I can find is that AP1 is reporting 2 lldp neighbors (the same switch on both Eth0 and Eth1) and AP2 is reporting 1 lldp neighbor (switch on Eth1).
These are both configured for Eth0-Eth1 Redundant and patched to the switch with two cat6a cables.
If I run - sh lldp cdp both report "Enabled: no"
Not sure if this is the same root issue you're having or not but figured I'd share since it's at least related.
02-24-2020 10:24 PM
Thanks. Here's a few snippets if it helps.
BURL_BALLROOM#show lldp
LLDP general information
----------------------------
Enabled: yes
Number of LLDP neighbors: 1
Max number of LLDP neighbors: 64
Sending LLDP packets interval (seconds): 30
Sending a holdtime value (seconds): 90
Sending a required power value (watt): 25.5
BURL_BALLROOM#show lldp cdp
CDP general information
----------------------------
Enabled: receive only
Number of CDP neighbors: 14
Max number of CDP neighbors: 64
CDP is currently showing 14 neighbors.
LLDP:
BURL_BALLROOM#show lldp nei
LLDP neighbor table: Total number = 1
--------------------------------
Incoming Port: eth0
Chassis ID(mac address): 18e8:2922:xxxx
Port ID(locally assigned): 0/6
Hold time(seconds): 120
Port description: 0/6
System name: HAI-XXXX
System description: EdgeSwitch 48-Port 500W, 1.9.0-lite, Linux 3.6.5-03329b4a, 0.0.0.0000000
System capabilities: bridge, router
Enables capabilities: bridge
802.1 port VLAN identifier: 1
Management address:
IP address: 10.x.x.x
CDP:
BURL_BALLROOM#show lldp cdp nei
CDP neighbor table: Total number = 14
Incoming interface: eth0
Device-ID: T19P_E2805EC015BF2C
Device addresses:
Device addresses number: 1
IP Address: 10.x.x.x
Holdtime: 164 sec
System Capabilities: Host
Version:53.82.0.20
Platform: T19P_E2
Port-ID (Port on Neighbor's Device): WAN PORT
Incoming interface: eth0
Device-ID: T48S805EC00FF661
Device addresses:
Device addresses number: 1
IP Address: 10.x.x.x
Holdtime: 157 sec
System Capabilities: Host
Version:66.83.0.35
Platform: T48S
Port-ID (Port on Neighbor's Device): WAN PORT
Incoming interface: eth0
Device-ID: T48S805EC0325D32
Device addresses:
Device addresses number: 1
IP Address: 10.x.x.x
Holdtime: 154 sec
System Capabilities: Host
Version:66.83.0.35
Platform: T48S
Port-ID (Port on Neighbor's Device): WAN PORT
Incoming interface: eth0
Device-ID: T48S805EC0333434
Device addresses:
Device addresses number: 1
IP Address: 10.x.x.x
Holdtime: 147 sec
02-24-2020 10:09 PM
Thank you for sharing those details, I'm going to see if I can get someone from our engineering team to weigh in here on why certain entries are picked over others when there are more than one.