topic Re: AIR-AP1562I-B-K9 unable to connect to Cisco controller 2504 in Wireless

AIR-AP1562I-B-K9 unable to connect to Cisco controller 2504

cldimapilis — Wed, 29 Jun 2022 16:43:09 GMT

FYI.. not very experienced but trying to setup AIR-AP1562I-B-K9 to connect to Cisco Controller 2504

getting the following error:

02/18/2020 05:30:49.0500] wired0: link up
[02/18/2020 05:30:49.1000] wired0: started
[*02/18/2020 05:30:49.1563] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'
[*02/18/2020 05:31:04.2672] Resetting wired0 and[02/18/2020 05:31:04.2900] wired
0: stopped
restart DHCP client
[02/18/2020 05:31:06.3800] wired0 emac 1: link up
[02/18/2020 05:31:06.4300] wired0: link up
[02/18/2020 05:31:06.4800] wired0: started
[*02/18/2020 05:31:06.5350] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'
[*02/18/2020 05:31:21.6454] Resetting wired0 and[02/18/2020 05:31:21.6700] wired
0: stopped
restart DHCP client
[02/18/2020 05:31:23.7600] wired0 emac 1: link up
[02/18/2020 05:31:23.8100] wired0: link up
[02/18/2020 05:31:23.8600] wired0: started
[*02/18/2020 05:31:23.9132] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'
[*02/18/2020 05:31:39.0243] Resetting wired0 and[02/18/2020 05:31:39.0500] wired
0: stopped
restart DHCP client
[02/18/2020 05:31:41.1400] wired0 emac 1: link up
[02/18/2020 05:31:41.1900] wired0: link up
[02/18/2020 05:31:41.2300] wired0: started
[*02/18/2020 05:31:41.2922] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'
[*02/18/2020 05:31:56.4031] Resetting wired0 and[02/18/2020 05:31:56.4300] wired
0: stopped
restart DHCP client
[02/18/2020 05:31:58.5100] wired0 emac 1: link up
[02/18/2020 05:31:58.5700] wired0: link up
[02/18/2020 05:31:58.6100] wired0: started
[*02/18/2020 05:31:58.6709] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'
[*02/18/2020 05:32:13.7813] Resetting wired0 and[02/18/2020 05:32:13.8100] wired
0: stopped
restart DHCP client
[*02/18/2020 05:32:14.5661] CRIT-MeshWiredAdj[0][08:4F:A9:0D:3C:58]: Remove as P
arent
[*02/18/2020 05:32:14.5662] CRIT-MeshLink: Link Down Block Root port Mac: 08:4F:
A9:0D:3C:58 BH Id: 0 Port:0 Device:DEVNO_WIRED0
[*02/18/2020 05:32:14.5663] CRIT-MeshWiredBackhaul[0]: Remove as uplink
[02/18/2020 05:32:15.8900] wired0 emac 1: link up
[02/18/2020 05:32:15.9500] wired0: link up
[02/18/2020 05:32:15.9900] wired0: started
[*02/18/2020 05:32:16.0492] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'

Also unable to enable privileged commands and Im in Exec Mode

Any ideas or tips

Re: AIR-AP1562I-B-K9 unable to connect to Cisco controller 2504

Mark Elsen — Wed, 29 Jun 2022 17:15:26 GMT

- FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi14641

Re: AIR-AP1562I-B-K9 unable to connect to Cisco controller 2504

Rasika Nayanajith — Wed, 29 Jun 2022 20:05:50 GMT

Below messages indicate AP got "mesh image". Unless it is purposely bought with a "mesh" image on it, I would suggest converting it to "Local" mode AP using "capwap ap mode local" CLI command on the AP & then test.

[*02/18/2020 05:32:14.5661] CRIT-MeshWiredAdj[0][08:4F:A9:0D:3C:58]: Remove as P
arent
[*02/18/2020 05:32:14.5662] CRIT-MeshLink: Link Down Block Root port Mac: 08:4F:
A9:0D:3C:58 BH Id: 0 Port:0 Device:DEVNO_WIRED0
[*02/18/2020 05:32:14.5663] CRIT-MeshWiredBackhaul[0]: Remove as uplink

HTH

Rasika

*** Pls rate all useful responses ***

Re: AIR-AP1562I-B-K9 unable to connect to Cisco controller 2504

cldimapilis — Wed, 29 Jun 2022 21:25:31 GMT

Hi Rasika

Thank you for the response, I did do the capwap ap mode local and the unit seems to keep booting up continuously.

Note I have the AP connected directly to the Controller 2504 on the PoE port4 to power it up. Does the Controller provide enough PoE power?

[02/17/2020 13:34:13.6000] wired0 emac 1: link up
[02/17/2020 13:34:13.6500] wired0: link up
[02/17/2020 13:34:13.7000] wired0: started
[*02/17/2020 13:34:13.7514] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'
[*02/17/2020 13:34:17.8571] Waiting for uplink IPv4 configuration
[*02/17/2020 13:34:22.8582] Waiting for uplink IPv4 configuration
[*02/17/2020 13:34:27.8593] Waiting for uplink IPv4 configuration
[*02/17/2020 13:34:28.8594] Rese[02/17/2020 13:34:28.8700] wired0: stopped
tting wired0 and restart DHCP client
[02/17/2020 13:34:30.9800] wired0 emac 1: link up
[02/17/2020 13:34:31.0300] wired0: link up
[02/17/2020 13:34:31.0800] wired0: started
[*02/17/2020 13:34:31.1266] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'
[*02/17/2020 13:34:35.2325] Waiting for uplink IPv4 configuration
[*02/17/2020 13:34:40.2335] Waiting for uplink IPv4 configuration
[*02/17/2020 13:34:45.2345] Waiting for uplink IPv4 configuration
[*02/17/2020 13:34:46.2346] Resetting wired0 and[02/17/2020 13:34:46.2700] wired
0: stopped
restart DHCP client
[02/17/2020 13:34:48.3500] wired0 emac 1: link up
[02/17/2020 13:34:48.4000] wired0: link up
[02/17/2020 13:34:48.4500] wired0: started
[*02/17/2020 13:34:48.4992] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'
[*02/17/2020 13:34:52.6050] Waiting for uplink IPv4 configuration
[*02/17/2020 13:34:57.6061] Waiting for uplink IPv4 configuration
[*02/17/2020 13:35:02.6071] Waiting for uplink IPv4 configuration
[*02/17/2020 13:35:03.6073] Resetting wired0 and[02/17/2020 13:35:03.6400] wired
0: stopped
restart DHCP client
[02/17/2020 13:35:05.7200] wired0 emac 1: link up
[02/17/2020 13:35:05.7700] wired0: link up
[02/17/2020 13:35:05.8200] wired0: started
[*02/17/2020 13:35:05.8717] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'
[*02/17/2020 13:35:09.9783] Waiting for uplink IPv4 configuration
[*02/17/2020 13:35:14.9794] Waiting for uplink IPv4 configuration
[*02/17/2020 13:35:19.9804] Waiting for uplink IPv4 configuration
[*02/17/2020 13:35:20.9806] Rese[02/17/2020 13:35:20.9900] wired0: stopped
tting wired0 and restart DHCP client
[02/17/2020 13:35:23.1000] wired0 emac 1: link up
[02/17/2020 13:35:23.1500] wired0: link up
[02/17/2020 13:35:23.2000] wired0: started
[*02/17/2020 13:35:23.2472] aptrace_register_sysproc_fn: duplicate registeration
for 'wired'
[*02/17/2020 13:35:27.3531] Waiting for uplink IPv4 configuration
[*02/17/2020 13:35:32.3542] Waiting for uplink IPv4 configuration

Re: AIR-AP1562I-B-K9 unable to connect to Cisco controller 2504

Chris Dimapilis — Thu, 30 Jun 2022 23:07:04 GMT

I changed the controller to which the AP is connected to, is set to be 1000Mbps full duplex and it still just reboots

I've also set the controller to be a dhcp server and according to the controller its providing the AP an IP address but the AP does not show any IP

Any ideas ?

Re: AIR-AP1562I-B-K9 unable to connect to Cisco controller 2504

Mark Elsen — Fri, 01 Jul 2022 06:12:54 GMT

>I changed the controller to which the AP is connected to, is set to be 1000Mbps full duplex and it still just reboots

- How is the access point connected to the network ?

Re: AIR-AP1562I-B-K9 unable to connect to Cisco controller 2504

Rasika Nayanajith — Fri, 01 Jul 2022 06:37:06 GMT

If you have a switch (POE+) I would use that.

If same issue I would go with below to reset it one more time via CLI

capwap ap erase all

HTH

Rasika

*** Pls rate all useful responses ***

Re: AIR-AP1562I-B-K9 unable to connect to Cisco controller 2504

Chris Dimapilis — Fri, 01 Jul 2022 14:23:18 GMT

topology is AP-->hardwired-->Cisco Controller 2504 PoE (port 4) and port 1

| |

|------>Serial console -> Serial to USB-->Laptop <-----|

Simple setup, for now, to configure and test. Basically AP connected to Port 4 and Laptop connected to Port 1.