isr-ap1100ac password reset (embedded Wireless AP)

[radiomean1]

Hello, I have an ISR-1100-4PWE with the embedded AP - isr-ap1100ac.

I need to reset the AP's password (I can access the router itself fine). I have tried the command - 

hw-module subslot 0/2 error-recovery password_reset

but this doesn't seem to do anything. Or maybe I am using the wrong 'default user/pw' (Cisco/Cisco?)

Please can someone assist! Thanks...

[balaji.bandi]

After reset have you tried :

hw-module subslot x/x reload force

https://www.cisco.com/c/en/us/td/docs/routers/access/1100/software/configuration/xe-16-7/cisco_1100_series_swcfg_xe_16_7_x/cisco_1100_series_swcfg_chapter_01010.html

[radiomean1]

Yes, doesn't seem to help.

But I am not sure of the 'default credentials'. Can you confirm what they are please?

[balaji.bandi]

 doesn't seem to help.

The document does not help or the process not worked ? when you reset it go in maintenance mode, so you need to reload force to be operational. When you reloaded - check the console Logs and post here.

when you intiate the command router produce enough logs on the console - have a look and some direction or anything obnormal or failing ?

as per the above document :

default login credentials are Username:Cisco and Password:Cisco

Note  : if the router not a major part of the network i will reload whole router, also provide what version of code running on the Router ?

[radiomean1]

Hello, thanks for info. The process didn't seem to work.

I will study the document at length and get back to you later. Thanks for confirming I am using the default credentials. Much appreciated. Router is running c1100-universalk9.17.10.01a.SPA but I don't know what the AP is running...

[radiomean1]

a) Maybe the problem is that I haven't set an IP address on the AP interface?

b) I thought if you reloaded the router software, it didn't affect the embedded AP?

[balaji.bandi]

Connect console and check

Reloading Router it will reboot whole router, so AP module will also reboot.

[Rich R]

1. Open a console connection to the AP.
2. While keeping the console connection open (with logging) issue the password reset then reload commands for the AP on the router

hw-module subslot 0/2 error-recovery password_reset
hw-module subslot 0/2 reload force

 3. Once the AP has finished reloading try to login on the console.  Save the complete log to a text file and attach here for us to view.

Note that IOS 17.10.1 is a limited support release - meaning it will never get any bug fixes.  You should upgrade to an extended support release like https://software.cisco.com/download/home/286315006/type/282046477/release/Dublin-17.12.3a

[radiomean1]

Many thanks for all the info. I'll give that a go.

[radiomean1]

OK, thanks everyone. I can access the AP via the console with the default Cisco/Cisco credentials.

However, access via the WebGUI doesn't properly work

Also, the AP is a real pig to configure, but I expect I'll get there in the end...

[Rich R]

> However, access via the WebGUI doesn't properly work
Can you be more specific?

[radiomean1]

I'll need to post a screen-shot. Later.

[radiomean1]

Hi, I think access via the WebGUI is premature.

Here is part of the boot-up messages - the module keeps on saying 'waiting for preferred uplink IP connection'. Can you advise please?

e: [*07/29/2024 23:01:52.9399] click-config/io-real.click:141: While initializing 'tohost_wired0 :: ToHost':
[*07/29/2024 23:01:52.9399]   warning: device 'wired0' is down
[*07/29/2024 23:01:53.3999] wmi_dbg_cfg_send: mod[0]00000000 dbgcfg40000000 cfgvalid[0] 00000000 cfgvalid[1] 00000000
[*07/29/2024 23:01:53.3999] wmi_dbg_cfg_send: mod[0]00000000 dbgcfg40000000 cfgvalid[0] 00000000 cfgvalid[1] 00000000
[*07/29/2024 23:01:53.5299] pid 5082's current affinity mask: f
[*07/29/2024 23:01:53.5299] pid 5082's new affinity mask: e
[*07/29/2024 23:01:53.5799] time="2024-07-29T23:01:53Z" level=info msg="[IAPP] SendGrpcDataToWLC called"
[*07/29/2024 23:01:53.6699] device aptrace0 entered promiscuous mode
[*07/29/2024 23:01:53.7499] device to_container entered promiscuous mode
[*07/29/2024 23:01:54.2099] Password for 'Cisco' changed
[*07/29/2024 23:01:54.2699] chatter: tohost_srcr6 :: ToHost: device 'srcr6' went down
[*07/29/2024 23:01:54.3399] chatter: tohost_srcr6 :: ToHost: device 'srcr6' came up
[*07/29/2024 23:01:54.3399] ip6_port srcr6, ip6local fe80::a293:51ff:fed6:9d68, ip6 ::, plen 0, gw6 ::, gw6_mac 00:00:00:00:00:00, mtu 1500, vid 0, mode6 2(slaac)
[*07/29/2024 23:01:55.0299] DOT11_TXP[1]:Domain configured: 12 class:E
[*07/29/2024 23:01:55.6699] DOT11_TXP[0]:Domain configured: 1 class:E
[*07/29/2024 23:01:56.0399] DOT11_DRV[1]: Init Radio1
[*07/29/2024 23:01:56.0799] DOT11_DRV[1]: Stop Radio1
[*07/29/2024 23:01:56.0899] DOT11_DRV[1]: set_channel Channel set to 36
[*07/29/2024 23:01:56.1099] DOT11_DRV[0]: Init Radio0
[*07/29/2024 23:01:56.1499] DOT11_DRV[0]: Stop Radio0
[*07/29/2024 23:01:56.1599] DOT11_DRV[0]: set_channel Channel set to 6
[*07/29/2024 23:01:56.1599] CRIT-MeshControl:
[*07/29/2024 23:01:56.1599] Mesh Control: skipped adding wired1 backhaul
[*07/29/2024 23:01:56.3199] DOT11_CFG[0] Radio Mode is changed from Local to FlexConnect
[*07/29/2024 23:01:56.3199] DOT11_CFG[0]: Starting radio 0
[*07/29/2024 23:01:56.3199] DOT11_DRV[0]: Start Radio0
[*07/29/2024 23:01:56.3199] DOT11_CFG[1] Radio Mode is changed from Local to FlexConnect
[*07/29/2024 23:01:56.3299] DOT11_CFG[1]: Starting radio 1
[*07/29/2024 23:01:56.3299] DOT11_DRV[1]: Start Radio1
[*07/29/2024 23:01:56.3399] DOT11_DRV[0]: Stop Radio0
[*07/29/2024 23:01:56.5399] DOT11_DRV[0]: set_channel Channel set to 1
[*07/29/2024 23:01:56.5599] DOT11_DRV[0]: Start Radio0
[*07/29/2024 23:01:56.5599] DOT11_DRV[0]: Channel set to 1, width 20
[*07/29/2024 23:01:56.5599] DOT11_DRV[0]: Stop Radio0
[*07/29/2024 23:01:56.7799] DOT11_DRV[0]: Channel set to 1, width 20
[*07/29/2024 23:01:56.7799] DOT11_DRV[1]: Stop Radio1
[*07/29/2024 23:01:56.7999] DOT11_DRV[1]: set_channel Channel set to 36
[*07/29/2024 23:01:56.7999] DOT11_DRV[1]: Start Radio1
[*07/29/2024 23:01:56.7999] DOT11_DRV[1]: Stop Radio1
[*07/29/2024 23:01:57.0399] DOT11_DRV[1]: Start Radio1
[*07/29/2024 23:01:57.0399] DOT11_DRV[1]: Channel set to 36, width 20
[*07/29/2024 23:01:57.0499] DOT11_DRV[1]: Stop Radio1
[*07/29/2024 23:01:57.0599] DOT11_DRV[1]: Channel set to 36, width 20
[*07/29/2024 23:01:57.0599] Failed to load flex AP config from file. Default config will be used.
[*07/29/2024 23:01:57.1099] Socket Valid Element wcp/wcp_db Handler set_vlan_name_map Data  Length 10
[*07/29/2024 23:02:01.1599] Waiting for preferred uplink IP configuration
[*07/29/2024 23:02:06.1799] Waiting for preferred uplink IP configuration
[*07/29/2024 23:02:11.1999] Waiting for preferred uplink IP configuration
[*07/29/2024 23:02:16.2199] Waiting for preferred uplink IP configuration
[*07/29/2024 23:02:21.2399] Waiting for preferred uplink IP configuration
[*07/29/2024 23:02:26.2599] Waiting for preferred uplink IP configuration

Username: [*07/29/2024 23:02:31.2799] Waiting for preferred uplink IP configuration
[*07/29/2024 23:02:36.2899] Waiting for preferred uplink IP configuration
[*07/29/2024 23:02:41.3099] Waiting for preferred uplink IP configuration
[*07/29/2024 23:02:46.3299] Waiting for preferred uplink IP configuration
[*07/29/2024 23:02:47.3499] Resetting wired0 and restart DHCP client
[*07/29/2024 23:02:53.3799] Waiting for preferred uplink IP configuration

Both  radios start, but are then stopped?

[Rich R]

The AP and Mobility Express (if enabled) both require an IP address to be able to work (they operate like 2 separate virtual machines on the AP).  That means you either need to have a DHCP server configured to provide the IP addresses or you need to statically configure them manually yourself via console.

[radiomean1]

Hello, I discovered that for myself, thanks... Using the 'day 0' configuration I initially incorrectly setup a static IP and the AP would not route to the internet, so I reset the AP and configured DHCP correctly, and I am now posting this whilst connected to the AP and internet via the router. I've set the AP to a static DHCP IP as well, so I know the IP and can login to the AP web configuration without having to guess the IP. 

I think it is now setup correctly. Thanks for your assistance...