cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
902
Views
3
Helpful
9
Replies

9200 CDP for Meraki APs not seen

econstas
Level 1
Level 1

Hello Everyone, I have a situation with a new install where we have a stacked 48 port 9200 having issues seeing the Access Points in the cdp table. Cdp is turned on both the global and on the interfaces. I did notice that the uplink switches from time to time drops out of the cdp table without having a port bounce. I turned on cdp debugging and logs are seen below. I ran cable tdr test and they are normal. I am wondering if it could be a bad set of switches, IOS needs to be upgraded, or cabling to all the aps are needing to be reset. I did ask them to take an ap down and run a new patch cable right at the switch, but that won't happen till next week.  One thing to note is that the APs are getting IPs in the correct network, but they also can't reach the Meraki dashboard even though other aps in the environment can with no issues. It seems to all be local to this one set of switches.  Any suggestions on what can be done?

Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 52   C9200L-48P-4X   17.09.03    CAT9K_LITE_IOSXE INSTALL
2 52      C9200L-48P-4X   17.09.03    CAT9K_LITE_IOSXE INSTALL

 

I did turn on CDP debugging - 

Packet Infra debugs:

Ip Address Port
------------------------------------------------------|----------

CDP:
CDP packet info debugging is on
CDP events debugging is on
CDP neighbor info debugging is on
CDP IP info debugging is on
CDP LOC Server info debugging is on
CDP inline power info debugging is on

 


084853: Jan 11 17:35:54.637 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet1/0/48
084854: Jan 11 17:35:55.170 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet1/0/47
084855: Jan 11 17:35:55.543 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet2/0/48
084856: Jan 11 17:35:56.814 GMT: CDP_EV: Device-ID TLV is invalid
084857: Jan 11 17:36:00.178 GMT: CDP_EV: Device-ID TLV is invalid
084858: Jan 11 17:36:00.775 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet2/0/46
084859: Jan 11 17:36:02.199 GMT: CDP-PA: version 2 packet sent out on TenGigabitEthernet2/1/1
084860: Jan 11 17:36:03.269 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet1/0/46
084861: Jan 11 17:36:04.755 GMT: CDP-PA: version 2 packet sent out on TenGigabitEthernet1/1/1
084862: Jan 11 17:36:07.707 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet2/0/47
084863: Jan 11 17:36:11.135 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet2/0/45
084864: Jan 11 17:36:12.828 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet2/0/48
084865: Jan 11 17:36:13.723 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet1/0/48
084866: Jan 11 17:36:13.978 GMT: CDP_EV: Device-ID TLV is invalid
084867: Jan 11 17:36:14.199 GMT: CDP_EV: Device-ID TLV is invalid
084868: Jan 11 17:36:14.731 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet1/0/47

084870: Jan 11 17:36:19.506 GMT: CDP-PA: version 2 packet sent out on TenGigabitEthernet2/1/1
084871: Jan 11 17:36:20.663 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet2/0/46
084872: Jan 11 17:36:21.367 GMT: CDP-PA: version 2 packet sent out on TenGigabitEthernet1/1/1
084873: Jan 11 17:36:22.083 GMT: CDP-PA: version 2 packet sent out on GigabitEthernet1/0/46
084874: Jan 11 17:36:23.364 GMT: CDP-PA: Packet received from SWITCH6S c on interface TenGigabitEthernet2/1/1
084875: Jan 11 17:36:23.364 GMT: **Entry NOT found in cache**
084876: Jan 11 17:36:23.364 GMT: CDP-EV: Packet Received from SWITCH6S with capability = 29 and Platform string = cisco WS-C3750X-48P on interface TenGigabitEthernet2/1/1
084877: Jan 11 17:36:23.366 GMT: CDP-EV: New Neighbor discovered, notified registered clients on interface TenGigabitEthernet2/1/1
084878: Jan 11 17:36:23.607 GMT: CDP-PA: Packet received from SWITCH6S on interface TenGigabitEthernet1/1/1
084879: Jan 11 17:36:23.607 GMT: **Entry NOT found in cache**
084880: Jan 11 17:36:23.608 GMT: CDP-EV: Packet Received from SWITCH6S with capability = 29 and Platform string = cisco WS-C3750X-48P on interface TenGigabitEthernet1/1/1
084881: Jan 11 17:36:23.609 GMT: CDP-EV: New Neighbor discovered, notified registered clients on interface TenGigabitEthernet1/1/1
084882: Jan 11 17:36:24.127 GMT: CDP_EV: Device-ID TLV is invalid
SWITCH9S#

 

port configuration:


SWITCH9S#sh run int g1/0/47
Building configuration...

Current configuration : 222 bytes
!
interface GigabitEthernet1/0/47
description DO NOT NAC - MERAKI WAP
switchport trunk native vlan 802
switchport trunk allowed vlan 255,802,803,855
switchport mode trunk
switchport nonegotiate
load-interval 30
end

SWITCH9S#sh run int g1/0/46
Building configuration...

Current configuration : 391 bytes
!
interface GigabitEthernet1/0/46
description DO NOT NAC - MERAKI WAP
switchport trunk native vlan 802
switchport trunk allowed vlan 255,802,803,855
switchport mode trunk
switchport nonegotiate
load-interval 30
power inline static
speed 1000
duplex full
auto qos trust
service-policy input AutoQos-4.0-Trust-Cos-Input-Policy
service-policy output AutoQos-4.0-Output-Policy
end

 

 

SWITCH9S#show post
Stored system POST messages:

Switch 1
---------

POST: CRYPTO Tests : Begin
POST: CRYPTO Tests : End, Status Passed

POST: PORT Loopback: loopback Test : Begin
POST: PORT Loopback: loopback Test : End, Status Passed

POST: SIF Tests : Begin
POST: SIF Tests : End, Status Passed

POST: Thermal, Temperature Tests : Begin
POST: Thermal, Temperature Tests : End, Status Passed

POST: Inline Power Controller Tests : Begin
POST: Inline Power Controller Tests : End, Status Passed
Switch 2
---------

POST: CRYPTO Tests : Begin
POST: CRYPTO Tests : End, Status Passed

POST: PORT Loopback: loopback Test : Begin
POST: PORT Loopback: loopback Test : End, Status Passed

POST: SIF Tests : Begin
POST: SIF Tests : End, Status Passed

POST: Thermal, Temperature Tests : Begin
POST: Thermal, Temperature Tests : End, Status Passed

POST: Inline Power Controller Tests : Begin
POST: Inline Power Controller Tests : End, Status Passed

1 Accepted Solution

Accepted Solutions

econstas
Level 1
Level 1

thanks everyone. We are opening up a TAC case on it. I am not sure if its hardware on the switch side or something else I am missing. 

View solution in original post

9 Replies 9

First' debug cdp.must not run for entire SW' but use debug condition and specify interface.

Second it can the AP use lldp not cdp.

MHM

Thanks. MHM - LLDP is turned on too but still no connection to Meraki Dashboard.  The only things connected to the switch are the APs and the two switch uplinks. We have 6 or 7 aps connected to the switch.

I will send you PM

Thanks 

MHM

@econstas 

CDP seems face issue "CDP_EV: Device-ID TLV is invalid"

But, If your problem is the AP not showing on the Meraki dashboard, this can be something else. Does the AP have connectivity with Meraki cloud? CDP would not cause this. 

Hello
do the aps have internet access?
do they need to be allowed through any fw?
are they statically ip addressed or dhcp?
If they are connected via trunk make sure native vlan is correct mgt access is allowed
lastly have you enrolled them into the dashboard-if so try removing them and adding them


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Thanks Everyone,

@paul driver Yes the APs should have access to the Dashboard. These are 6 additional to another 20 we installed at the site. This switch is an access switch that uses the same distro and router that allows the other 20 access to the dashboard. The APs are initially using dhcp in a specific management network. We reserve in the IPs into infoblox after they are connected to the dashboard. The aps have already been claimed, but just hadn't communicated with the dashboard. 

@Flavio Miranda I am thinking of having someone unhook one of the aps and run a new patch cable to see if the cabling is bad. Potential reset the ap just incase that doesn't work. We had someone run the cabling to the new switch and the aps. It seems to be aok, but just in case could be a layer1 issue.

 

@MHM Cisco World Ok. Will check out the PM. 

Thanks again for the assistance.

 

 

Hello
okay so you’ve claimed them successfully-
so next -
does you hardware licence cover these additional aps?
as a test you could in hook a existing ap from it switchport and plumb in one of those new aps and see it reachs the dashboard -vice versa…

or copy a switchport from the same switch that has existing aps successfully attached and test that way


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

econstas
Level 1
Level 1

thanks everyone. We are opening up a TAC case on it. I am not sure if its hardware on the switch side or something else I am missing. 

Hello,

May I know whether this issue has been fixed, and what is the solution? I have the same issue, that I have about 20 MR76 APs connect to cisco 9300L switch, it's strange that on the same switch, some MR46 APs are ok, but some MR76 APs cannot be detected by cdp but lldp is working, the problem is for the MR76 APs that can only detected by lldp, they cannot onboard to Meraki cloud manager although they can get the IP address through DHCP without any problem, and I think they are also able to access to Internet, as all APs are in same subnet within same dhcp pool granted same firewall rule. Much appreciate if you can share the solution if it's already be fixed, thank you!!