Cisco AP 3802 init>> Issue

[Hathif Azaam]

Hi,

When the access point reboots, it suddenly goes into the init>> state. I tried finding a solution to resolve this issue, but I couldn't sort it out. Are there any other ways to address these kinds of problems?

Please choose one of the following boards:
1. 3K
2. 2K (new)
3. 2K (proto)
4. Milos
5. 2KH
6. 3KVE (v-sku)
7. 3KH/3KA/4K
8. Duplo
init>>

Warm Regards,

Hathif Azaam

[Mark Elsen]

       - Try pressing 2 and see what happens,

 M.

[Hathif Azaam]

After pressing "2," the access point booted up and allowed me to log in with the credentials. However, it did not join the Wireless LAN Controller (WLC) and failed to receive IP addresses from the DHCP server. The following log message frequently appeared:

[04/11/2025 11:43:39.4000] wired0: started
[*04/11/2025 11:43:41.5573] Waiting for preferred uplink IP configuration
[*04/11/2025 11:43:46.5649] Waiting for preferred uplink IP configuration
[*04/11/2025 11:43:51.5715] Waiting for preferred uplink IP configuration
[*04/11/2025 11:43:54.5776] Resetting wired0 and[04/11/2025 11:43:54.6100] wired0: stopped
restart DHCP client
[04/11/2025 11:43:56.6900] wired0: started
[*04/11/2025 11:43:58.8507] Waiting for preferred uplink IP configuration
[*04/11/2025 11:44:03.8573] Waiting for preferred uplink IP configuration
[*04/11/2025 11:44:08.8638] Waiting for preferred uplink IP configuration
[*04/11/2025 11:44:11.8699] Resetting wired0 and[04/11/2025 11:44:11.9000] wired0: stopped
restart DHCP client
[04/11/2025 11:44:13.9800] wired0: started
[*04/11/2025 11:44:16.1410] Waiting for preferred uplink IP configuration
[*04/11/2025 11:44:21.1477] Waiting for preferred uplink IP configuration
[*04/11/2025 11:44:26.1552] Waiting for preferred uplink IP configuration
[*04/11/2025 11:44:29.1613] Resetting wired0 and[04/11/2025 11:44:29.1900] wired0: stopped
restart DHCP client
[04/11/2025 11:44:31.2800] wired0: started
[*04/11/2025 11:44:33.4341] Waiting for preferred uplink IP configuration
[*04/11/2025 11:44:38.4408] Waiting for preferred uplink IP configuration
[*04/11/2025 11:44:43.4474] Waiting for preferred uplink IP configuration
[*04/11/2025 11:44:46.4536] Resetting wired0 and[04/11/2025 11:44:46.4800] wired0: stopped
restart DHCP client
[04/11/2025 11:44:48.5600] wired0: started
[*04/11/2025 11:44:50.7268] Waiting for preferred uplink IP configuration
[*04/11/2025 11:44:55.7335] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:00.7402] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:03.7465] Resetting wired0 and[04/11/2025 11:45:03.7700] wired0: stopped
restart DHCP client
[04/11/2025 11:45:05.8600] wired0: started
[*04/11/2025 11:45:08.0197] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:13.0264] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:18.0330] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:21.0393] Resetting wired0 and[04/11/2025 11:45:21.0700] wired0: stopped
restart DHCP client
[04/11/2025 11:45:23.1500] wired0: started
[*04/11/2025 11:45:25.3105] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:30.3174] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:35.3241] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:38.3302] Resetting wired0 and[04/11/2025 11:45:38.3600] wired0: stopped
restart DHCP client
[04/11/2025 11:45:40.4400] wired0: started
[*04/11/2025 11:45:42.6032] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:47.6098] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:52.6165] Waiting for preferred uplink IP configuration
[*04/11/2025 11:45:55.6233] Rese[04/11/2025 11:45:55.6300] wired0: stopped
tting wired0 and restart DHCP client
[04/11/2025 11:45:57.7400] wired0: started
[*04/11/2025 11:45:59.8957] Waiting for preferred uplink IP configuration
[*04/11/2025 11:46:04.9023] Waiting for preferred uplink IP configuration

[Leo Laohoo]

DHCP Option 43

[Mark Elsen]

- @Hathif Azaam   - Check if there is DHCP request coming from the AP in the logs of the DHCP server; if not  try a manual IP configuration on the AP and check if that can work ; for testing purposes. If not the AP may have a fatal hardware problem and then needs to be replaced (RMA),

  M.

[Hathif Azaam]

@Mark Elsen I checked everything you mentioned, but the issue persists. As you suggested, I assume there might be a hardware issue or something else causing the problem. Nevertheless, thank you for your support!

[Mark Elsen]

  -  @Hathif Azaam    >... I assume there might be a hardware issue or something else causing the problem
                                 Yeah probably;  a test which you can execute is connecting the AP to a switch and issue the command
                                              show cdp neighbors detail
                                 if you can't see any info from the AP on the port it is connected to then the AP is dead,

  M.