08-26-2022 02:32 AM
Hi chaps,
I'm trying to recover a C9130 which failed to upgrade the code and now is in a loop boot, but it seems to me that the recovery process from U-Boot couldn't be the same as C9120 from this guide as C9130 is unable to ping gateway, any ideas?
Regards
08-26-2022 02:51 AM
- If the tftp server is on the same subnet then you don't need the gateway , else configure it anyway and see what happens when the tftp server is needed in the subsequent commands.
M.
08-26-2022 03:04 AM
Hi Marce, that is the problem, the TFTP server is remote, so I need the GW.
BUT the main problem is that the AP is not pinging the gateway which is in the same switch it is connected. Proper VLAN set, proper netmask, AP is powering on so port is good... I wonder if this is something to be with C9130 been mGig and switch port been mGig as well.
08-26-2022 03:11 AM
- Check if the switchport is in connected mode for the ap-connection ,make sure that error counters on the port are idle , also verify that you can ping the particular gateway from another host in the same subnet as the access point.
M.
08-26-2022 05:48 AM
The weird thing is that the switchport keeps showing disconnected, even when AP is in U-Boot mode.
I have tested the AP on a 1Gbps switch and it doesn't make any difference.
Openning TAC to investigate if this is a faulty unit.
08-26-2022 07:20 PM
IF the AP is in u-boot, post the complete output to the command "pri"
08-29-2022 12:29 AM
Swapping partition does not make any change, and both images keep crashing at some time during boot up.
TAC case open to check if it needs a RMA.
Here it goes the output from both printenv and printshenv:
(BTLDR) # printenv
BOOT=part1
FACTORY_RESET=2
bootcmd=bootipq
bootdelay=3
ethact=eth0
ethaddr=00:00:00:00:00:xx
fdtcontroladdr=4a989ec0
gatewayip=10.13.50.1
ipaddr=10.13.50.24
machid=8010001
netmask=255.255.255.0
serverip=10.8.8.2
soc_version_major=2
soc_version_minor=0
stderr=serial@78B3000
stdin=serial@78B3000
stdout=serial@78B3000
Environment size: 354/65532 bytes
(BTLDR) # printshenv
BAUDRATE=9600
BOOT=part1
ENABLE_BREAK=1
FACTORY_RESET=0
INIT_CAPWAP_DEBUG=0
KDUMP=0
LED_BRIGHTNESS=8
MANUAL_BOOT=0
MEMORY_DEBUG=0
Shared environment size: 149/16384 bytes, write counter: 43, active 1:0
12-15-2022 04:44 PM
Did TAC end up RMA'ing this AP? We have the same issue. Part 1 and Part 2 both do not boot up properly and it keeps rebooting. We were going to try and do recovery from uboot to our tftp server, but the port won't come up for a network connection. Did TAC fix yours if so how?
12-15-2022 11:59 PM
At the end TAC RMA'ed the part as it was faulty.
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