05-04-2018 09:17 AM - edited 07-05-2021 08:35 AM
Hi Guys,
I’m having an issues with cisco AP 3802E.
When I try to assign static IP Address getting below error. Please help me on this.
Capwap process not ready yet. Try after few moments.
I was done some troubleshoot please find below
#capwap ap restart
Capwap process not ready yet. Try after few moments.
#ap-type capwap
Capwap process not ready yet. Try after few moments.
#capwap ap ip 192.xx.x.101 255.255.0.0 192.xx.xx.1
Capwap process not ready yet. Try after few moments.
CAPWAP socket is not ready, save static IP addr to config file.
#capwap ap primary-base XX 192.xx.xx.109
Capwap process not ready yet. Try after few moments.
AP Running Image : 8.2.151.0
Primary Boot Image : 8.2.151.0
Backup Boot Image : 0.0.0.0
Solved! Go to Solution.
05-04-2018 04:31 PM
05-04-2018 04:31 PM
05-04-2018 04:33 PM
05-12-2018 09:32 AM
05-12-2018 04:15 PM
05-12-2018 07:29 PM
Hi Leo,
We don't have TAC support.
I was tried upload new firmware to break ap boot order but it's going u-boot>>
can you help me here how to upload firmware through u-boot>>
05-12-2018 07:34 PM
10-25-2018 09:09 AM
I have the same problem too.
conversion to capwap to mobility ...
it does not take the dhcp from the "router" and I can not send the new firmware to TFPT.
waiting for POE negotiation to complete
.....
always in loop
wired0: stopped config down up
wired0: started
aptrace_register_sysproc_fn: duplicate registeration for 'wired'
Waiting for uplink IPv4 / IPv6 configuration
Waiting for uplink IPv4 / IPv6 configuration
example:
capwap ap ip 192.168.88.10 255.255.255.0 192.168.88.1
> show ip interface brief
Interface IP-Address Method Status Protocol Speed
wired0 unassigned unset down up n / a
wired1 unassigned unset down down n / a
wifi0 unassigned unset administatively down down n / a
wifi1 unassigned unset administatively down down n / a
srcr6 unassigned unset up up n / a
My serial is not on the defective list.
Cisco AIR-AP3802I-E-K9 ARMv7
AP Running Image: 8.3.140.6
Primary Boot Image: 8.3.140.6
Backup Boot Image: 8.3.134.79
# Booting kernel from Legacy Image at 02000000 ...
Image Name: Barbados Firmware Image
Created: 2018-03-19 22:34:28 UTC
Image Type: ARM Linux Multi-File Image (uncompressed)
this is my env:
u-boot >> pri
BOOT = part2 (modify to part1)
DRAWER = max
ENABLE_BREAK = 1
FACTORY_RESET = 1
MALLOC_len = 5
MANUAL_BOOT = 0
MEMORY_DEBUG = 0
MPmode SMP =
autoload = yes
baud rate = 9600
boorcmd = nandboot
bootcmd = nandboot
BootDelay = 3
bootfile = board_init_barbados2k.img
cacheShare = no
disaMvPnp = no
eeeEnable = no
enaClockGating = no
enaCpuStream = no
enaFPU = yes
enaMonExt = no
enaWrAllo = no
eth1addr = 00: 50: 43: 00: 02: 01
eth1mtu = 1500
eth2addr = 00: 50: 43: 00: 00: 01
eth2mtu = 1500
ethact = egiga2
ethaddr = 00: 50: 43: 00: 02: 01
ethmtu = 1500
ethprime = egiga2
factory-reset = yes
fdt_high = 0x2000000
image_name = part.bin
initrd_high = 0xffffffff
limit_dram_size = yes
LoadAddr = 0x02000000
loads_echo = 0
mtddevname = fs
mtddevnum = 2
mtdids = nand0 = armada-nand
mtdparts mtdparts = = armada-nand: 1m (oops), 1m (reserved), - (fs)
nandEcc nfcConfig = = 4bitecc
netretry = no
partition = nand0,2
pcieTune = no
pexMode = RC
stderr = serial
stdin = serial
stdout = serial
yuk_ethaddr = 00: 00: 00: EE: 51: 81
Environment size: 966/65532 bytes
u-boot >>
how can I update the firmware ????
10-25-2018 02:18 PM
10-26-2018 01:20 AM
u-boot>> dhcp
SF: Detected N25Q32A with page size 64 KiB, total 4 MiB
Uncompressing AQ phy firmware...
mvEgigaInit: egiga2 mvNetaPortEnable failed (error)
mvEgigaInit: egiga2 failed
mvEgigaInit: egiga1 mvNetaPortEnable failed (error)
mvEgigaInit: egiga1 failed
10-26-2018 01:56 AM
10-26-2018 02:15 AM
10-26-2018 02:56 AM
Leo: obviously the 2 devices are on the same lan with dhcp from router
My serial number is not in the list of defects
If you explain how to load a new firmware from u-boot can I do it without opening a TAC ???
10-26-2018 03:22 AM
fmproit@yahoo.it wrote:
Leo: obviously the 2 devices are on the same lan with dhcp from router
When the AP was in u-boot, you entered the command "dhcp". This would've enabled the AP to obtain a valid IP address. But it didn't. So I suspect something is wrong with the DHCP config.
10-30-2018 03:45 AM
with the dhcp command I always have the usual error.
The Ap is connected directly to the router, like all other devices.
u-boot >> dhcp
SF: Detected N25Q32A with page size 64 KiB, total 4 MiB
Uncompressing AQ phy firmware ...
mvEgigaInit: egiga2 mvNetaPortEnable failed (error)
mvEgigaInit: egiga2 failed
mvEgigaInit: egiga1 mvNetaPortEnable failed (error)
mvEgigaInit: egiga1 failed
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide