Wireless Access

Dear Members, AP 305 is rebooting continously and giving below massages.


Net: eth0
Radio: qca9990#0, ipq4029#1
Reset: warm
FIPS: passed

Hit <Enter> to stop autoboot: 0
apboot>
apboot>
apboot>
apboot>
apboot>
apboot>
apboot>
apboot> osinfo
Partition 0Volume aos0 not found!
does not contain a valid OS image

Partition 1Volume aos1 not found!
data abort
pc : [<87313df4>] lr : [<87310c70>]
sp : 870efde8 ip : 35986a7c fp : 00000000
r10: 00000000 r9 : 870eff34 r8 : 00000001
r7 : 00000001 r6 : 01800000 r5 : 02000000 r4 : 84000000
r3 : 00000000 r2 : 0a000021 r1 : 0000000a r0 : 02000000
Flags: nzCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...

resetting ...


APBoot 2.4.0.8 (build 64221)
Built: 2018-03-28 at 20:26:16

Model: AP-30x
DRAM: 512 MiB
Flash: Detected MX25R3235F: total 4 MiB
NAND: 128 MiB
PCIE0 link up
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 168c 0040 00002 00 00000004 00000000 00000000 00000000
Power: 802.3af POE
Nand Flash error. Status = 0x30,bitflip number is 32
NAND page read failed. page: 0 status ffffffb6
Nand Flash error. Status = 0x30,bitflip number is 32
NAND page read failed. page: 1 status ffffffb6
Nand Flash error. Status = 0x30,bitflip number is 32
NAND page read failed. page: 40 status ffffffb6
Nand Flash error. Status = 0x30,bitflip number is 32
NAND page read failed. page: 41 status ffffffb6

Have you opened a TAC Case?

The other thing you can try, is when your at apboot>
type

purgeenv

saveenv

boot

 

and see if it comes online after that

TAC Case not opened yet.

I have tried purgeenv several times but response remains same as i shared.

What firmware release do you running? The AP-305 had some issues that are fixed in release 8.3.0.8.

 

See release notes:

https://support.hpe.com/hpsc/doc/public/display?docId=a00078633en_us

Please open a TAC case if you ordered this AP through the regular channels.

 

It could be that the AP has been 'zeroized' by a previous owner if you purchased it second hand, which basically wipes everything possible including possible keys. That is a process that irrevertably takes an AP out of operations and should be done only before definititive decomissioning. If that happend to the AP, you probably can't use it anymore. In that case, you should probably go back to the seller.

Hello,

 

Huh!! It happens in very rare cases.

 

From the Logs I can see that the AP has lost the OS on both 0 and 1 flash.

This sometime happens even to the controllers, in which we configure the TFTP server/USB to boot the Controller over network.

 

You could try the below steps, it may not be successful but it worth a try.

Hit <Enter> to stop autoboot: 0 --> Interrupt the Boot process

>setenv ipaddr <IP Address>

>setenv netmask <Netwmask>

>setenv gatewayip <Gateway IP of the VLAN> --> If AP & Controllers are in same VLAN try to ping the "Master IP"

>setenv masterip <Controller's IP>

>setenv servername <Controller's IP> --> Let the AP download the OS image from the controller, the controller will act as a TFTP server

>saveenv

>printenv --> verify the settings

>boot

 

Collect the APs console output.

 

While AP boots up, check on the controller's Datapath,

#show datapath session table <APs IP address> --> Collect the output and share it along with the APs console logs

 

Try this steps and share the result with us.

 

If you have valid support you can open a TAC ticket, you can get the AP RMAed by submitting the collected console logs and controller outputs if any or reach back to the reseller.

 

Good luck!!

 

 

You could try factory reset command from the AP console they will take it back to the orginal shipping code. After the factory reset just power cycle it. 

I tried factory_reset but nothing happened.... TAC case opened for this AP.