Cisco AP AIR-AP2802I-A-K9SN is not showing in CDP but visible in LLDP

[yogesh rajguru]

HI Team,

I have installed a new access point in our network connected to switch port via media convertor and fiber due to distance , but AP is not registering with WLC.

Also i can see port is up and mac address is learning , but AP is not showing in CDP neighbor but it showing in LLDP neighbor.

What could be reason and solution for this.

CDF-200-4-79#sh cdp nei Gi3/0/1
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID Local Intrfce Holdtme Capability Platform Port ID

Total cdp entries displayed : 0
CDF-200-4-79#sh lldp nei Gi3/0/1
Capability codes:
(R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
(W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other

Device ID Local Intf Hold-time Capability Port ID
AP4C77.6DE1.D650 Gi3/0/1 120 B 0

Total entries displayed: 1

CDF-200-4-79#

[Scott Fella]

I thin that the media convertor is the issue.  Now this is a dumb convertor, so I would not say blocking but probably corrupting something in the process.  If you replaced the media convertor (testing) with a switch as an example, I bet that would work.  Have you tried to replace the media convertor with a different model?  Maybe reach out to the manufacture and see what they have to say.

[rakesh nair]

We removed the setup and connected to another switch in test room using same media convertors, fibers, power injectors and copper cable, it worked 

[rakesh nair]

Hi Anyone,

We did the connection back on fibre and its now showing on CDP neighbor, but not registering to WLC.Getting below error on AP

Dec 14 18:47:12 kernel: [*12/14/2022 18:47:12.0173] CAPWAP State: DTLS Teardown
Dec 14 18:47:16 kernel: [*12/14/2022 18:47:16.7677] No more AP manager addresses remain..
Dec 14 18:47:16 kernel: [*12/14/2022 18:47:16.7677] No valid AP manager found for controller 'T3-F004-WLC-27' (ip: 10.23.101.27)
Dec 14 18:47:16 kernel: [*12/14/2022 18:47:16.7678] Failed to join controller T3-F004-WLC-27.
Dec 14 18:47:16 kernel: [*12/14/2022 18:47:16.7678] Failed to join controller.

[Scott Fella]

Okay, so you tested it in a different location with the same type of media convertor and switch and it works and the ap joins the controller.  Then you moved the ap back to the existing location and now you see CDP, but the ap doesn't join?  Have you tried to replace the media convertor?  Seems like initially you did not see CDP and now you do, what will happen in the future when that media convertor stops passing cdp again?  If you connect a laptop to the media convertor on the far end where your ap connects to, do you notices any issues, slowness, timeouts?

You can install this tool and test cdp/lldp on your laptop:

GitHub - chall32/LDWin: Link Discovery for Windows

[rakesh nair]

Do we have any particular media convertor which will support this AP AIR-AP2802I-A-K9 having connected via ethernet--> media covertor --> SM fibre --> media convertor --> POE injector --> WAP

[Scott Fella]

I have had customers whom did this in warehouses in the past but ran into issues long term with the media convertors failing.  What they ended up doing was mounting a switch to bridge the gap between the AP and the IDF.  They used like an 8 port managed switch that accepted SFP's and that way the can monitor the ports the AP is connected to.  That might be a better option for you.  Hard to say what vendor or media convertor is recommended.

[Leo Laohoo]

After reading this thread, I am leaning towards a faulty media converter. 

Get a media converter from reputable manufacturers, like FS[.]com.

[Rich R]

What do the full logs before that show?
What do the join stats on the WLC show?
Do you have the right country code configured for the AP?
Do you have enough licenses for the AP?
What model of WLC is it and what version of software is it running?

[rakesh nair]

CDF-Blender-Room#sh led CDF-Blender-Room#sh led
state Show LED state info
CDF-Blender-Room#sh led state
Dis_Join_Progress 1
Normal_No_Client 0
Normal_Client 0
Software_Upgrade 0
LedState_Enable_Disable 1
Insuff_Inline_power 0
AP_Location_Enable 0
LedFlash_Infinite_Sec 0
AP_Priming 0
AP_Connect_App 0
AP_Prime_Wait_By_User 0
AP_Primed_To_Wrong_Domain 0
Ethernet_Failure 0
CDF-Blender-Room#

Dec 14 18:12:02 kernel: [*12/14/2022 18:12:02.9773] CAPWAP State: Discovery
--More-- Dec 14 18:12:02 kernel: [*12/14/2022 18:12:02.9780] Got WLC address 10.23.101.27 from DHCP.
Dec 14 18:12:02 kernel: [*12/14/2022 18:12:02.9780] Got WLC address 10.25.101.27 from DHCP.
Dec 14 18:12:02 kernel: [*12/14/2022 18:12:02.9780] IP DNS query for CISCO-CAPWAP-CONTROLLER.wifi.lob.corp.gtaa.com
Dec 14 18:12:02 kernel: [*12/14/2022 18:12:02.9833] Discovery Request sent to 10.25.101.27, discovery type STATIC_CONFIG(1)
Dec 14 18:12:02 kernel: [*12/14/2022 18:12:02.9850] Discovery Request sent to 10.25.101.23, discovery type STATIC_CONFIG(1)
Dec 14 18:12:02 kernel: [*12/14/2022 18:12:02.9861] Discovery Request sent to 10.25.101.24, discovery type STATIC_CONFIG(1)
Dec 14 18:12:02 kernel: [*12/14/2022 18:12:02.9872] Discovery Request sent to 10.23.101.27, discovery type DHCP(2)
Dec 14 18:12:02 kernel: [*12/14/2022 18:12:02.9921] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
Dec 14 18:12:02 kernel: [*12/14/2022 18:12:02.9922] Discovery Response from 10.25.101.27
Dec 14 18:12:03 kernel: [*12/14/2022 18:12:03.0001] Discovery Response from 10.23.101.27
Dec 14 18:13:15 kernel: [*12/14/2022 18:13:15.0000]
Dec 14 18:13:15 kernel: [*12/14/2022 18:13:15.0000] CAPWAP State: DTLS Setup
Dec 14 18:14:12 kernel: [*12/14/2022 18:14:12.0163] dtls_disconnect: ERROR shutting down dtls connection ...
Dec 14 18:14:12 kernel: [*12/14/2022 18:14:12.0163]
Dec 14 18:14:12 kernel: [*12/14/2022 18:14:12.0176]
Dec 14 18:14:12 kernel: [*12/14/2022 18:14:12.0176] CAPWAP State: DTLS Teardown
Dec 14 18:13:15 kernel: [*12/14/2022 18:14:16.7681] No more AP manager addresses remain..
Dec 14 18:13:15 kernel: [*12/14/2022 18:14:16.7681] No valid AP manager found for controller 'T1-MCR1-WLC-27' (ip: 10.25.101.27)
Dec 14 18:13:15 kernel: [*12/14/2022 18:14:16.7682] Failed to join controller T1-MCR1-WLC-27.
Dec 14 18:13:15 kernel: [*12/14/2022 18:14:16.7682] Failed to join controller.
Dec 14 18:13:15 kernel: [*12/14/2022 18:13:15.0000]
Dec 14 18:13:15 kernel: [*12/14/2022 18:13:15.0000] CAPWAP State: DTLS Setup
Dec 14 18:14:12 kernel: [*12/14/2022 18:14:12.0159] dtls_disconnect: ERROR shutting down dtls connection ...
Dec 14 18:14:12 kernel: [*12/14/2022 18:14:12.0160]
Dec 14 18:14:12 kernel: [*12/14/2022 18:14:12.0163]
Dec 14 18:14:12 kernel: [*12/14/2022 18:14:12.0163] CAPWAP State: DTLS Teardown
Dec 14 18:14:16 kernel: [*12/14/2022 18:14:16.7677] No more AP manager addresses remain..
Dec 14 18:14:16 kernel: [*12/14/2022 18:14:16.7678] No valid AP manager found for controller 'T3-F004-WLC-27' (ip: 10.23.101.27)
Dec 14 18:14:16 kernel: [*12/14/2022 18:14:16.7678] Failed to join controller T3-F004-WLC-27.
Dec 14 18:14:16 kernel: [*12/14/2022 18:14:16.7678] Failed to join controller.
Dec 14 18:14:16 kernel: [*12/14/2022 18:14:16.9774]

[rakesh nair]

[rakesh nair]

What do the full logs before that show? Pasted above
What do the join stats on the WLC show? Pasted above
Do you have the right country code configured for the AP? In WLC CA is the country code selected for all APs
Do you have enough licenses for the AP? Yes we do have
What model of WLC is it and what version of software is it running? AIR-CT8510-K9 with 8.5.137.98

[Rich R]

- DTLS connection to both your WLCs are failing from that AP
- your 8510 is running a very old special escalation image which is very likely not supported at all - they're usually only supported until the next full release with your fix in it.  So you should be running 8.5.182.0 as per TAC recommended link below with numerous bug fixes.
- have you done a factory default reset on your AP? (mode button)
- have you checked your WLC's certificates (refer to field notice below) and made sure you have the workaround config applied to ignore expired certs?

[rakesh nair]

Hi Everyone,

We got the issue fixed now after replacing the power injector . 

Earlier we used the black one and now replaced with white one .

Thanks everyone for your wonderful advise and support.