topic Re: AIR-AP3802I-Z-K9 - Not able to login after factory reset in Wireless

AIR-AP3802I-Z-K9 - Not able to login after factory reset

Claudinei Rodrigues — Fri, 21 Jun 2024 17:20:10 GMT

Hey guys, I have this AP and I can't login on it after performing a full factory reset.

I'm not able to write anything when it finishes the boot and I receive the "user access verification" message.

After that these messages start in loop (wired0 emac 0: link up; wired0: link up)

Console Log messages:

User Access Verification
Username: [12/11/2022 12:25:16.5400] wired0 emac 0: link up
[12/11/2022 12:25:16.6000] wired0: link up
[*12/11/2022 12:25:17.3176] ip6_port srcr2, ip6local XXXX, plen 0, gw6 ::, gw6_mac 00:00:00:00:00:00, mtu 1500, vid 0, mode6 2(slaac)
[*12/11/2022 12:25:17.6993] pid 7991's current affinity mask: 3
[*12/11/2022 12:25:17.6993] pid 7991's new affinity mask: 1
[*12/11/2022 12:25:18.2668] device aptrace0 entered promiscuous mode
[*12/11/2022 12:25:18.3170] device to_container entered promiscuous mode
[*12/11/2022 12:25:18.9580] chpasswd: password for user changed
[*12/11/2022 12:25:19.3801] USB Device Disconnected from the AP
[*12/11/2022 12:25:19.8602] DOT11_TXP[0]:Domain configured: 48 class:Z
[*12/11/2022 12:25:20.3259] DOT11_TXP[0]:Domain configured: 0 class:A
[*12/11/2022 12:25:20.4089] DOT11_TXP[0]:Domain configured: 48 class:Z
[*12/11/2022 12:25:20.8888] DOT11_TXP[0]:Domain configured: 0 class:A
[*12/11/2022 12:25:20.9728] DOT11_TXP[2]:Domain configured: 48 class:Z
[*12/11/2022 12:25:22.2359] DOT11_DRV[0]: Stopped Radio 0
[*12/11/2022 12:25:22.2604] DOT11_DRV[0]: DOT11_DRV[0]: set_channel Channel set to 6
[*12/11/2022 12:25:23.1474] DOT11_DRV[1]: Stopped Radio 1
[*12/11/2022 12:25:23.1708] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*12/11/2022 12:25:23.9301] DOT11_DRV[0]: DOT11_DRV[0]: set_channel Channel set to 1
[*12/11/2022 12:25:24.6533] DOT11_DRV[0]: DOT11_DRV[0]: set_channel Channel set to 1
[*12/11/2022 12:25:24.6708] DOT11_DRV[0]: DOT11_DRV[0]: set_channel Channel set to 1
[*12/11/2022 12:25:25.5215] bftype is 6
[*12/11/2022 12:25:25.5448] DOT11_DRV[0]: DOT11_DRV[0]: set_channel Channel set to 1
[*12/11/2022 12:25:26.1810] DOT11_DRV[0]: DOT11_DRV[0]: set_channel Channel set to 1
[*12/11/2022 12:25:26.3150] failed wlconfig_commit netdev = wifi1
[*12/11/2022 12:25:26.3150] Error for wireless request "Commit changes" (8B00) :
[*12/11/2022 12:25:26.3151] SET failed on device wifi1 ; Operation not permitted.
[*12/11/2022 12:25:26.6014] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*12/11/2022 12:25:27.1513] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*12/11/2022 12:25:27.8937] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*12/11/2022 12:25:27.9113] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*12/11/2022 12:25:28.8640] bftype is 6
[*12/11/2022 12:25:28.8868] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*12/11/2022 12:25:29.6280] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*12/11/2022 12:25:30.3619] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[12/11/2022 12:26:02.3000] wired0 emac 0: link up
[12/11/2022 12:26:02.3600] wired0: link up
[12/11/2022 12:26:19.5000] wired0 emac 0: link up
[12/11/2022 12:26:19.5600] wired0: link up
[12/11/2022 12:26:36.7200] wired0 emac 0: link up
[12/11/2022 12:26:36.7800] wired0: link up
[12/11/2022 12:26:53.9300] wired0 emac 0: link up
[12/11/2022 12:26:53.9800] wired0: link up
[12/11/2022 12:27:11.1300] wired0 emac 0: link up
[12/11/2022 12:27:11.1800] wired0: link up
[12/11/2022 12:27:28.3400] wired0 emac 0: link up
[12/11/2022 12:27:28.3900] wired0: link up
[12/11/2022 12:27:45.5500] wired0 emac 0: link up
[12/11/2022 12:27:45.6000] wired0: link up
[12/11/2022 12:28:02.7400] wired0 emac 0: link up
[12/11/2022 12:28:02.8000] wired0: link up
[12/11/2022 12:28:19.9500] wired0 emac 0: link up
[12/11/2022 12:28:20.0000] wired0: link up

These messages never end.

Re: AIR-AP3802I-Z-K9 - Not able to login after factory reset

jagan.chowdam — Thu, 20 Jun 2024 19:29:55 GMT

Is AP getting IP Address? Connect your laptop to the AP port and see if it gets an IP assigned.

Jagan Chowdam

/**Pls rate useful responses**/

Re: AIR-AP3802I-Z-K9 - Not able to login after factory reset

Claudinei Rodrigues — Fri, 21 Jun 2024 12:31:00 GMT

The AP won't get IP. I'm using a switch that isn't in my network just to use the PoE and configure a static ip address of my access point management range.
This AP was in my network working fine, and after the factory reset these messages starts.

Re: AIR-AP3802I-Z-K9 - Not able to login after factory reset

Mark Elsen — Fri, 21 Jun 2024 13:11:01 GMT

- Check port-connectivity for this AP on the switch ; look if established speed and duplex is normal
- Also have a look at the interface counters on the switch , check for errors if any.
- On the switch issue the command : show cdp neighbors detail -> is the AP visible somewhere ?

Re: AIR-AP3802I-Z-K9 - Not able to login after factory reset

Claudinei Rodrigues — Fri, 21 Jun 2024 17:17:44 GMT

Hi,

It established speed an duplex normally, I don't see any errors and the AP is visible with CDP

Switch#sh interfaces g1/0/9
GigabitEthernet1/0/9 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 8c94.xxxx.xxxx (bia 8c94.xxxx.xxxx)
Description: ## access point ##
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is on, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:32, output 00:00:08, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
6471 packets input, 1177915 bytes, 0 no buffer
Received 6468 broadcasts (5876 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 5876 multicast, 0 pause input
0 input packets with dribble condition detected
3372 packets output, 489068 bytes, 0 underruns
Output 0 broadcasts (1338 multicasts)
0 output errors, 0 collisions, 2 interface resets
493 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

Switch#sh cdp nei
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID Local Intrfce Holdtme Capability Platform Port ID
AP70B3.xxxx.xxxx Gig 1/0/9 170 R T AIR-AP380 Gig 0

Switch#sh cdp nei detail
-------------------------
Device ID: AP70B3.xxxx.xxxx
Entry address(es):
IPv6 address: FE80::xxxx:xxxx:xxxx:xxxx (link-local)
Platform: cisco AIR-AP3802I-Z-K9, Capabilities: Router Trans-Bridge
Interface: GigabitEthernet1/0/9, Port ID (outgoing port): GigabitEthernet0
Holdtime : 121 sec

Version :
Cisco AP Software, ap3g3-k9w8 Version: 8.10.183.0
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2014-2015 by Cisco Systems, Inc.

advertisement version: 2
Power drawn: 25.800 Watts
Power request id: 27429, Power management id: 2
Power request levels are:25800 15400 0 0 0
Management address(es):

I'm starting to think that the problem could be my console cable, not the access point. I tryed in others APs and I'm also not able to write anything. It's working only in switches.
I will try with another one tomorrow and let you know.

Re: AIR-AP3802I-Z-K9 - Not able to login after factory reset

Mark Elsen — Sat, 22 Jun 2024 06:15:39 GMT

>...I will try with another one tomorrow and let you know.
Ok , Cisco APs can be picky about the type of console cable used , not all brands will work ,

Re: AIR-AP3802I-Z-K9 - Not able to login after factory reset

Claudinei Rodrigues — Mon, 24 Jun 2024 11:30:25 GMT

The problem was really my console cable, I can access the access point normally after I bought a new one.

Thanks guys!