Controller AP in the Access Points List in Mobility Express missing?

[donnalbenvillnueva]

I logged into the console of the Controller AP and show version got me this result:

I recently upgraded from 8.3.133 to 8.10.185 but when it finished, the controller AP did not show up as an access point, which was previously shown when I was still in 8.3.133.

Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to
restrictions as set forth in subparagraph (c) of the Commercial
Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

Cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

This product contains some software licensed under the
"GNU General Public License, version 2" provided with
ABSOLUTELY NO WARRANTY under the terms of
"GNU General Public License, version 2", available here:
http://www.gnu.org/licenses/old-licenses/gpl-2.0.html

This product contains some software licensed under the
"GNU Library General Public License, version 2" provided
with ABSOLUTELY NO WARRANTY under the terms of "GNU Library
General Public License, version 2", available here:
http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html

This product contains some software licensed under the
"GNU Lesser General Public License, version 2.1" provided
with ABSOLUTELY NO WARRANTY under the terms of "GNU Lesser
General Public License, version 2.1", available here:
http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html

This product contains some software licensed under the
"GNU General Public License, version 3" provided with
ABSOLUTELY NO WARRANTY under the terms of
"GNU General Public License, Version 3", available here:
http://www.gnu.org/licenses/gpl.html.

This product contains some software licensed under the
"GNU Affero General Public License, version 3" provided
with ABSOLUTELY NO WARRANTY under the terms of
"GNU Affero General Public License, version 3", available here:
http://www.gnu.org/licenses/agpl-3.0.html.

Cisco AP Software, (ap1g4), C1832, RELEASE SOFTWARE
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2024 by Cisco Systems, Inc.
Compiled Fri Mar 24 18:52:59 GMT 2023

ROM: Bootstrap program is U-Boot boot loader
BOOTLDR: U-Boot boot loader Version 41

AP70D3.79DA.3AF8 uptime is 0 days, 0 hours, 14 minutes
Last reload time : Fri Feb 23 06:21:27 UTC 2024
Last reload reason : reload command

cisco AIR-AP1832I-A-K9 ARMv7 Processor rev 0 (v7l) with 996240/383892K bytes of memory.
Processor board ID KWC21120B40
AP Running Image : 8.10.185.0
Primary Boot Image : 8.10.185.0
Backup Boot Image : 8.3.133.0
Primary Boot Image Hash:
Backup Boot Image Hash:
AP Image type : MOBILITY EXPRESS IMAGE
AP Configuration : MOBILITY EXPRESS CAPABLE
2 Gigabit Ethernet interfaces
2 802.11 Radios
Radio FW version : f39e59654a44b14dbeedf2603bab9cd0
NSS FW version : NSS.AK.C.CS-3-fix5

Base ethernet MAC Address : 70:D3:79:DA:3A:F8
Part Number : 0-0000-00
PCA Assembly Number : 074-104313-02
PCA Revision Number : 01
PCB Serial Number : KWC21120B40
Top Assembly Part Number : 000-00000-00
Top Assembly Serial Number : KWC21120B40
Top Revision Number : A0
Product/Model Number : AIR-AP1832I-A-K9

[Rich R]

Are you saying 192.168.0.250 is also the wrong subnet?
If one is correct and one is wrong you only need to change the wrong one (the AP?).
What is the subnet they are connected to on the switch?  They should both be in that subnet.  All the APs and the ME WLC should be in that subnet.

[donnalbenvillnueva]

The correct subnet is the 66. I need to change the ME WLC (which is on 0.250). Based on the log files, the capwap ip of that same hardware is already on 66.171. but I can access the ME GUI on 192.168.0.250. How can I change the ME WLC to be on the 66 subnet?

It was already this way when it was still in 8.3 and I am also confused by this setup which was left by the previous IT person. Haha Thank you for being patient with me @Rich R 

[jagan.chowdam]

>config interface address management <IP address> <netmask> <gateway>
>config interface vlan management XX
>save config

Verify by, 
>show interface detailed management

[donnalbenvillnueva]

Apparently, I dont have "config" privileges due to Lightweight/AireOS limitations. 

[donnalbenvillnueva]

The key information I had to know is that the AP and WLC are two different machines having 2 different IPs. All I had to do was reset the WLC to factory settings, since I cant get anything to work via CLI, and enter the correct IP in the correct subnet settings. Everything works now. Thank you very much!

[Rich R]

Glad you got there eventually <smile>

[jagan.chowdam]

Looks like AP sending discover request to WLC, but it never reached the WLC. Thus, no response recorded for Discovery request. 

What you have is routing/Layer 3 issue. You have to make sure AP and WLC can ping each other. 

IP Address                         : 192.168.66.171
IP netmask                         : 255.255.255.0
Default Gateway                    : 192.168.66.168

 Start by pinging default gateway's for both WLC and AP, then SVI's and trace the path to reach the other device IP. 

Without proper Layer 3 connectivity, WLC and AP can't discover each other.

Jagan Chowdam

[jagan.chowdam]

Did you check if the AP received an IP Address (show capwap ip config)? 

If AP didn't show any IP, go into AP Cisco Shell: (Cisco Controller) > apciscoshell then statically assigning IP with "capwap ap ip xx.xx.xx.xx netmask gateway" command. 

Jagan Chowdam

/**Pls rate useful responses**/

[donnalbenvillnueva]

The AP IP Address was retained from the previous version (8.3.133), I can still ping the AP. Although these information might be useful: The static IP I gave the AP is 192.168.66.171 (from the local network) but the controller IP (to access GUI) is 192.168.0.250. Is this a possible cause for the issue?

[Rich R]

Yes - in a mobility express deployment the ME WLC and AP should normally all be in the same VLAN and same IP subnet.  It is possible to use different VLANs/subnets but that will make your deployment more complicated so keep them all in a single broadcast domain.

If the ME WLC and AP were in different subnets it probably should have never worked, even on 8.3.133, but either way fix it now.  Ideally you should use DHCP for the AP IPs to avoid this type of problem resulting from mistakes in static IP config - you are just creating an extra problem for yourself by using static IP.  It's ok to use a static IP for the ME WLC so that you always know what IP to connect to for management but there is really no need to use static IPs for the APs because they are managed from the WLC.

[jagan.chowdam]

The Management Access Interface is the default interface for in-band management of the controller and is used for communication between the controller and access points (APs). Can you ping the AP from the WLC? 

Move the AP in the same VLAN as the Mobility Express Management IP and it should be able to join. 

Jagan Chowdam

[donnalbenvillnueva]

This might work if I am trying to join other APs, but what I currently have here is only 1 AP which carries an ME image and acts as a controller. This ME Controller doesn't show up as an Access Point in it's own AP Administration Page (accessed via 192.168.0.250). In my understanding, it should show as the Primary Controller and Preferred Master, right?

[marce1000]

 - Note that  this could be a bug ; even after the upgrade ; hence my question if a nearby client can connect to it. Also check the LED state(s) on this controller AP , 

 M.

[donnalbenvillnueva]

@marce1000 

Yes, a nearby client can still connect and it functions but the LEDs are cycling red-amber-green. 

[marce1000]

                    >... but the LEDs are cycling red-amber-green. 
 - Check if the AP is getting sufficient power ; despite previous alerting or not , 

 M.