There are a total of 25 Cisco 3502 APs installed. 24 APs were discovered except for 1 AP. I run SH CDP NE on the switch and the AP was discovered by the switch but it does not have an IP address. On the output of the SH CDP NE DE, I noticed that on the AP that is not joining, the Platform is "cisco AIR-SAP3502E-E-K9" while the APs that joined the WLC, the Platform is "cisco AIR-CAP3502E-E-K9". The software versions are also different but this could be because the WLC already upgraded the IOS when the APs joined.
Why is the Platform "SAP3502E" for the AP that did not join.
Attached is the output of the SH CDP NE DE.
Solved! Go to Solution.
Is it possible that AIR-SAP3502E means that the AP is Autonomous? If it is, can I use the "archive download command to upgrade to CAPWAP?
AIR-CAP3502E is a lightweight image
AIR-AP3502E is an autonomous image
An autonomous image, you can use the archive download command.
You need to console into the AP and look at the output. IIRC, there were some of the 3500's that were imaged with the mesh image and required you to add the mac address to the mac fiter in order for it to join, then you can change the mode.
How would I know if the image installed in the AP is mesh?
See below is part of the SH CDP NE output of the AP not joining.
Device ID: ap
IP address: 10.0.0.1
Platform: cisco AIR-SAP3502E-E-K9 , Capabilities: Trans-Bridge IGMP
Interface: GigabitEthernet0/36, Port ID (outgoing port): GigabitEthernet0
Holdtime : 167 sec
Cisco IOS Software, C3500 Software (AP3G1-K9W7-M), Version 12.4(25d)JA, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Thu 09-Dec-10 14:38 by prod_rel_team
advertisement version: 2
Power drawn: 15.400 Watts
Power request id: 59946, Power management id: 2
Power request levels are:15400 14500 0 0 0
Here is a doc that will explain the filename naming convention.
The other thing is that the autonomous and lightweight look different when you console into the ap while its booting up. This is something you should really look at, because it expalins a lot when your ap doesn't join a wlc or if there is something wrong withthe ap.
I'll be going to the site tomorrow and remove this AP so I could console to it. I will be able to see if it is autonomous on the messages.
If when the ap finally boots up and you can issue a config t, then its autonomous.