cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2277
Views
2
Helpful
4
Replies

C9120 After IOS upgrade, endless loop

Maurizio Caloro
Level 1
Level 1

Dear members, please i need your help

i have installed today the 17.12.1 Image on me 9120AX EWC (i dont have any
possibilities to create for this any tac, this AP was a private ebay investigation)

after the installation the AP did not come up anymore, loop, reset befor the
Logon-Screen appair. after try meny resets like: erase, erase_nvram (selection build 0-18)
the AP appear to have a problem to start right.

So frendly asking, for possible help
meny thanks

--

u-boot> ?
? - alias for 'help'
base - print or set address offset
bdinfo - print Board Info structure
boardinit- Download MFG boardinit bundle and burn images to its repective location
boot - boot default, i.e., run 'bootcmd'
bubt - Burn image to NOR flash boot device
chpart - change active partition
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
dm - Driver model low level access
echo - echo args to console
editenv - edit environment variable
env - environment handling commands
erase - erase FLASH memory
erase_nvram- Erase NVRAM
erase_persistent_data- Erase Persistent Data
exit - exit script
false - do nothing, unsuccessfully
fdt - flattened device tree utility commands
fipsalgval- run algorithm validation on test vector bibnar in memory, default:2000000 (0x02000000)
flinfo - print FLASH memory information
forceboot- force boot from u-boot image
fuse - Fuse sub-system
gpio - Read/Write Gpio Pins
help - print command description/usage
i2c - I2C sub-system
iminfo - print header information for application image
imxtract- extract a part of a multi-image
itest - return true/false on integer compare
ledstate- Set Led State
lzmadec - lzma uncompress a memory region
meminfo - display memory information
mtdparts- define flash/nand partitions
nand - NAND sub-system
nandboot- boot Linux from NAND partition
netboot - boot Linux from network using TFTP/bootp
pci - list and access PCI Configuration Space
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setboardparms- Set Board Params
setbootline- Set Boot Params
setenv - set environment variables
setexpr - set environment variable as the result of eval expression
sf - SPI flash sub-system
showvar - print local hushshell variables
sleep - delay execution for some time
source - run script from memory
sspi - SPI utility command
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
true - do nothing, successfully
ubi - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
usb - USB sub-system
version - print monitor, compiler and linker version

u-boot> setenv BOOT part1
u-boot> saveenv

Saving Environment to SPI Flash...
Erasing SPI flash...Writing to SPI flash...done

u-boot> re
resetting ...
Resetting board...HELO
5.0205HNDRC1a-1.0.38-163.162
CPU0
L1CD
MMUI
MMUA
CODE
ZBBS
MAIN
Boot Strap Register: 0x6fc7b
NVRAM memcfg 0x41627
DDR3-1600 CL11 total 2048MB 2 16bits part[s] %1 SSC

DDR test done successfully
CFE Version: 5
Verifying MASTER U-Boot...
Launching MASTER U-Boot version 0x005e ...


____ _
/ ___|(_) ___ ___ ___
| | | |/ __| / __|/ _ \
| |___ | |\__ \| (__| (_) |
\____||_||___/ \___|\___/
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|

U-Boot 2017.09 (Jun 21 2023 - 10:35:58 -0700) Broadcom BCM49408

Board: VANC-i
I2C: ready
DRAM: 2 GiB
enable MMU ... OK
NAND: Status wait timeout: nandsts=0x0 mask=0x40000000, count=0
NAND ECC BCH-8, page size 4096 bytes, spare size used 216 bytes
1024 MiB
MMC:
SF: Detected mx25l6405d with page size 256 Bytes, erase size 4 KiB, total 8 MiB
In: serial
Out: serial
Err: serial
Platform: 4908
SF: Detected mx25l6405d with page size 256 Bytes, erase size 4 KiB, total 8 MiB
pmc_init:PMC using DQM mode
pmc_patch_4908:7 0 170046e 33c0340
Board IP address : 192.168.1.1:ffffff00
Host IP address : 192.168.1.100
Gateway IP address :
Run from flash/host/tftp (f/h/c) : f
Default host run file name : vmlinux
Default host flash file name : bcm963xx_fs_kernel
Boot delay (0-9 seconds) : 1
Default host ramdisk file name :
Default ramdisk store address :
Board Id (0-18) : 949408EAP_54991
Number of MAC Addresses (1-32) : 10
Base MAC Address : 00:10:18:00:00:00
PSI Size (1-128) KBytes : 128
Enable Backup PSI [0|1] : 1
System Log Size (0-256) KBytes : 100
Auxillary File System Size Percent: 0
flow memory allocation (MB) : 43
buffer memory allocation (MB) : 16
DHD 0 memory allocation (MB) : 10
DHD 1 memory allocation (MB) : 10
DHD 2 memory allocation (MB) : 10
Partition 1 Size (MB) : 8M
Partition 2 Size (MB) : 4M
Partition 3 Size (MB) : 4M
Partition 4 Size (MB) (Data) : 4M

BootImage: MASTER
Found external PHY firmware image
MTDPART Str = (mtdparts=nand:1m(nvram),5888k(bootfs),-(fs))
Net: Registering Ethernet Driver.....
Broadcom BCM 4908 Ethernet driver 0.1
pmc_switch_power_up: Rgmii Tx clock zone1 enable 0 zone2 enable 0.
Setting SGMII Calibration value to 0x9
swap_pair = 0

Detecting PHYs...
84880 A0 ae02:5158 --> N/A
84881 A0 ae02:5150 --> N/A
84884 A0 ae02:5148 --> N/A
84884E A0 ae02:5168 --> N/A
84885 A0 ae02:5178 --> N/A
84886 A0 ae02:5170 --> N/A
84887 A0 ae02:5144 --> N/A
84888 A0 ae02:5140 --> N/A
84888E A0 ae02:5160 --> N/A
84888S A0 ae02:5174 --> N/A
84880 B0 ae02:5159 --> N/A
84881 B0 ae02:5151 --> N/A
84884 B0 ae02:5149 --> N/A
84884E B0 ae02:5169 --> N/A
84885 B0 ae02:5179 --> N/A
84886 B0 ae02:5171 --> N/A
84887 B0 ae02:5145 --> N/A
84888 B0 ae02:5141 --> N/A
84888E B0 ae02:5161 --> N/A
84888S B0 ae02:5175 --> N/A
84891 A0 3590:5090 --> N/A
54991 A0 3590:5094 --> N/A
54991E A0 3590:5098 --> N/A
84891L A0 3590:5080 --> N/A
54991L A0 3590:5084 --> N/A
54991EL A0 3590:5088 --> N/A
84892 A0 3590:50a0 --> N/A
54992 A0 3590:50a4 --> N/A
54992E A0 3590:50a8 --> N/A
84894 A0 3590:50b0 --> N/A
54994 A0 3590:50b4 --> N/A
54994E A0 3590:50b8 --> N/A
54991H A0 3590:50d0 --> N/A
54994H A0 3590:50f0 --> N/A
84891 B0 3590:5091 --> N/A
54991 B0 3590:5095 --> N/A
54991E B0 3590:5099 --> N/A
84891L B0 3590:5081 --> N/A
54991L B0 3590:5085 --> N/A
54991EL B0 3590:5089 --> 0x1f
84892 B0 3590:50a1 --> N/A
54992 B0 3590:50a5 --> N/A
54992E B0 3590:50a9 --> N/A
84894 B0 3590:50b1 --> N/A
54994 B0 3590:50b5 --> N/A
54994E B0 3590:50b9 --> N/A
54991H B0 3590:50d1 --> N/A
54994H B0 3590:50f1 --> N/A

Loading firmware into detected phys...
Firmware version: Blackfin B0 v02-02-03-2020-03-16
Loading firmware into phys: map=0x80000000
Halt the phys processors operation
Upload the firmware into the on-chip memory 100%
Reset the processors to start execution of the code in the on-chip memory
Verify that the processors are running: OK
Verify that the firmware has been loaded with good CRC: OK
Firmware loading completed successfully

Unsupported MII type: 0
bcm4908_eth-0
MAC: 00:10:18:00:00:00

Hit ESC key to stop autoboot: 1 MG link 1G 0
Mounting UBI device fs
ubi0: attaching mtd3
ubi0: scanning is finished
ubi0: attached mtd3 (name "mtd=2", size 1017 MiB)
ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 253952 bytes
ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 4096
ubi0: VID header offset: 4096 (aligned 4096), data offset: 8192
ubi0: good PEBs: 4065, bad PEBs: 4, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 79/20, WL threshold: 4096, image sequence number: 839138221
ubi0: available PEBs: 33, total reserved PEBs: 4032, PEBs reserved for bad PEB handling: 76
Load Addr 0x10000000
Mount UBIFS PARTITION part1 ...
Loading file 'part1/part.bin' to addr 0x10000000...
Done

Checking image signing.
Image signing verification success for part part1 continue to run...
Multi Image Header Found
Count = 0 Offset = 0x10000050 Len = 11201184
Count = 1 Offset = 0x10aaeaf0 Len = 3771844
Count = 2 Offset = 0x10e478b4 Len = 7246
Booting from Partition: part1
arg 0: 0x10000050
arg 1: 0x3000000
arg 2: 0x1800000
## Loading init Ramdisk from Legacy Image at 03000000 ...
Image Name: Simple Ramdisk Image
Created: 2023-07-22 22:28:01 UTC
Image Type: AArch64 Linux RAMDisk Image (lzma compressed)
Data Size: 3771780 Bytes = 3.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01800000
Booting using the fdt blob at 0x1800000
load dtb from fixed memory location directly...
/memory = 0x80000000 bytes @ 0x0
Set Memory to 2147483648l
WARNING: Node's property /reserved-memory/dt_reserved_buffer is not defined
WARNING: Node's property /reserved-memory/dt_reserved_flow is not defined
Appending NVRAM to dtb, ret:0
Loaded DTB from 0x01800000 with size 7246l
Curr Boot Args: console=ttyS0,9600 activepart=part1 activeboot=0 bootver=0x5e boardid=0x2 forceboot=0 coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe rootwait crashkernel=128M@0M ttyS0 mtdparts=nand:1m(nvram),5888k(bootfs),-(fs) ubi.mtd=fs apmode=me BOOT_DEBUG=0
DTB Boot Args (coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe rootwait crashkernel=128M@0M)
Bootargs set to setenv bootargs console=$consoledev,$baudrate activepart=part1 activeboot=0 bootver=0x5e boardid=0x2 forceboot=0 coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe rootwait crashkernel=128M@0M $console $nandEcc $mtdparts ubi.mtd=fs apmode=me BOOT_DEBUG=0
Preferred boot heartbeat count: 4
Erasing SPI flash...Writing to SPI flash...done
Cleanup Complete.... ARMv8_secure_init_done!!!
Loading Ramdisk to 4fb0d000, end 4fea5d84 ... OK
reserving fdt memory region: addr=0 size=20000
Using Device Tree in place at 0000000001800000, end 0000000001804c4d

Starting kernel ...

[01/01/1970 00:00:04.5750] hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
[01/01/1970 00:00:04.6670] brcmboard registered
[*01/01/1970 00:00:15.4700] buginf() enabled.
[*01/01/1970 00:00:15.4780] Made it into bootsh: Jul 22 2023 22:05:30 T-6ad045b278cdd875a6d1b2636aa7993c640d5dd9M-gd8650252-aut
[01/01/1970 00:00:23.4210] UBIFS error (ubi0:0 pid 665): ubifs_read_node: bad node type (255 but expected 1)
[01/01/1970 00:00:23.5280] UBIFS error (ubi0:0 pid 665): ubifs_read_node: bad node at LEB 209:0, LEB mapping status 0
[01/01/1970 00:00:23.6530] Not a node, first 24 bytes:
[01/01/1970 00:00:23.7090] 00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ........................
[01/01/1970 00:00:23.8780] UBIFS error (ubi0:0 pid 665): do_readpage: cannot read page 11892 of inode 68, error -22
[01/01/1970 00:00:24.0000] UBIFS error (ubi0:0 pid 665): ubifs_read_node: bad node type (255 but expected 1)
[01/01/1970 00:00:24.1150] UBIFS error (ubi0:0 pid 665): ubifs_read_node: bad node at LEB 209:0, LEB mapping status 0
[01/01/1970 00:00:24.2390] Not a node, first 24 bytes:
[01/01/1970 00:00:24.2950] 00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ........................
[01/01/1970 00:00:24.4640] UBIFS error (ubi0:0 pid 665): do_readpage: cannot read page 11892 of inode 68, error -22
[*01/01/1970 00:00:24.5890] verify signature failed for /bootpart/part1/ramfs_data_cisco.cpio.lzma
[*01/01/1970 00:00:24.6150] Rebooting in 5 seconds ...

Looping again, and again

1 Accepted Solution

Accepted Solutions

marce1000
VIP
VIP

 

                              >...ubifs_read_node: bad node type (255 but expected 1)
  - To me these look like hardware errors , you may try link below steps ; presumably you may get stuck on legal terms and no access to the needed software from Cisco (with service contract....)
             https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

View solution in original post

4 Replies 4

marce1000
VIP
VIP

 

                              >...ubifs_read_node: bad node type (255 but expected 1)
  - To me these look like hardware errors , you may try link below steps ; presumably you may get stuck on legal terms and no access to the needed software from Cisco (with service contract....)
             https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Leo Laohoo
Hall of Fame
Hall of Fame

This is a known bug feature (CSCvx32806). 

Please read How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points.

meny thanks Marce1000, and Leo Laohoo for your Help, yes the AP booting correctly now

did the Booting-patch update my BIOS/firmware right away?

and I'm just wondering how to proceed, about selecting the correct IOS, I use the 9120 as an EWC,
which one do you use? 17.12.1, or always just the one with the yellow star?

meny thanks for your help, have a nice day!

 

 Ref : https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/214855-ios-xe-wireless-feature-list-per-release.html#toc-hId-18123547
                     >... 17.12.1, or always just the one with the yellow star?
  - If you don't need specific features from the latest release , use the one with the yellow star , 

 M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '
Review Cisco Networking for a $25 gift card