Solved

Download AP150w firmware 10.0r10b

  • 14 May 2021
  • 5 replies
  • 47 views

We’ve just deployed an older AP150w that’s currently sitting on 10.0r9b.

 

Updating it through ECIQ fails every time without any meaningful logs as to why.

 

Is there a place where I can download the firmware with instructions to patch it manually?

icon

Best answer by Sam Pirok 17 May 2021, 18:27

For your firmware you’ll want to log in at extremeportal.force.com, then go to Products> ExtremeCloud> ExtremeCloud IQ> find the firmware version you want to download it there. 

 

Once you have the firmware file you need, you can try updating via the Web UI or via CLI, this guide covers both: https://extremeportal.force.com/ExtrArticleDetail?an=000078576&q=how%20to%20update%20firmware%20CLI%20IQ

 

If those methods don’t work for you, I’d recommend enabling CAPWAP debugs (https://extremeportal.force.com/ExtrArticleDetail?an=000057308&q=Capwap%20debug), then trying to update the firmware in XIQ as usual, wait for that to fail, then grab tech data (https://extremeportal.force.com/ExtrArticleDetail?an=000081084&q=Tech%20data).

 

If you can open a case, I’d recommend attaching that tech data to your case. If you aren’t able to open a case right now, you can always send the tech data file to me at community@extremenetworks.com, and I’ll take a look for you and let you know what I find out. 

View original

5 replies

Userlevel 7

For your firmware you’ll want to log in at extremeportal.force.com, then go to Products> ExtremeCloud> ExtremeCloud IQ> find the firmware version you want to download it there. 

 

Once you have the firmware file you need, you can try updating via the Web UI or via CLI, this guide covers both: https://extremeportal.force.com/ExtrArticleDetail?an=000078576&q=how%20to%20update%20firmware%20CLI%20IQ

 

If those methods don’t work for you, I’d recommend enabling CAPWAP debugs (https://extremeportal.force.com/ExtrArticleDetail?an=000057308&q=Capwap%20debug), then trying to update the firmware in XIQ as usual, wait for that to fail, then grab tech data (https://extremeportal.force.com/ExtrArticleDetail?an=000081084&q=Tech%20data).

 

If you can open a case, I’d recommend attaching that tech data to your case. If you aren’t able to open a case right now, you can always send the tech data file to me at community@extremenetworks.com, and I’ll take a look for you and let you know what I find out. 

Hi sam

 

After downloading and installing the firmware from extremeportal.force.com under Products> ExtremeCloud> ExtremeCloud IQ>
The AP does not start I try to connect from the cli and it marks the following:

 

U-Boot 2012.10 (Sep 14 2020 - 22:30:17)

DRAM:  256 MiB
WARNING: Caches not enabled
---> caches_on
---> MMU enabled
---> blast_dcache
---> blast_icache
---> caches_on DONE
NAND:   NAND_FLASH_DEVICE_ID_ADDR = 18008194
Done that
(ONFI),  W29N04GV, blocks per lun: 1000 lun count: 1

*WARNING* Invalid strap options for this NAND: page=0 type=3
Overriding invalid strap options: strap_type=2
128 KiB blocks, 2 KiB pages, 16B OOB, 8-bit
NAND:   chipsize
total 0 bad blocks,LIST:
now the up level will see a good flash chip no bad block which size is 20000000
before nvram partition, there are 0 bad blocks
512 MiB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   Registering eth
Broadcom BCM IPROC Ethernet driver 0.1
Using GMAC0 (0x18005000)
et0: ethHw_chipAttach: Chip ID: 0xb95c; phyaddr: 0x1e
bcm_robo_attach: devid: 0x0
bcmiproc_eth-0
MAC address is 7c95:b10c:3d80

NVRAM_MAGIC found at offset 700000
nvram_init: ret 1
Reset CC2650 and TUSB3410
Reset TPM chip...
Reset AUTH chip...
Power Input Detection: POE AT
use back up image 0 for boot
sync boot static info size = 0x1d4
Hit any key to stop autoboot:  0

Loading kernel from device 0: nand0 (offset 0x800000) ... done
Loading rootfs from device 0: nand0 (offset 0x1600000) ... done
## Booting kernel from Legacy Image at 01005000 ...
   Image Name:   Linux-3.16.36
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2456685 Bytes = 2.3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02005000 ...
   Image Name:   uboot initramfs rootfs
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    27078656 Bytes = 25.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
boot_prep_linux commandline: root=/dev/ram console=ttyS0,9600 ramdisk_size=70000                                                       cache-sram-size=0x10000

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Mounting local file systems...
UBI device number 0, total 3240 LEBs (411402240 bytes, 392.3 MiB), available 59 LEBs (7491584 bytes, 7.1 MiB), LEB size 126976 bytes (
Do the DB init,please wait...
ah_net: module license 'unspecified' taints kernel.
Disabling lock debugging due to kernel taint
Updating system config database...
System config upPOE Input Detection -> date complete.
AT
Enable PSE
gmac_var_init: NAPI2_POLL mode
Jumbo disabled
Jumbo disabled
bcm_robo_enable_switch: EEE is disabled
reth1: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 10.10.80.505_e5.1.2.3 (r659762)
register sniffer device on interface eth0.
register sniffer device on interface eth1.
register sniffer device on interface eth2.
register sniffer device on interface eth3.
Jumbo disabled
Jumbo disabled


U-Boot 2012.10 (Sep 14 2020 - 22:30:17)

DRAM:  256 MiB
WARNING: Caches not enabled
---> caches_on
---> MMU enabled
---> blast_dcache
---> blast_icache
---> caches_on DONE
NAND:   NAND_FLASH_DEVICE_ID_ADDR = 18008194
Done that
(ONFI),  W29N04GV, blocks per lun: 1000 lun count: 1

*WARNING* Invalid strap options for this NAND: page=0 type=3
Overriding invalid strap options: strap_type=2
128 KiB blocks, 2 KiB pages, 16B OOB, 8-bit
NAND:   chipsize
total 0 bad blocks,LIST:
now the up level will see a good flash chip no bad block which size is 20000000
before nvram partition, there are 0 bad blocks
512 MiB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   Registering eth
Broadcom BCM IPROC Ethernet driver 0.1
Using GMAC0 (0x18005000)
et0: ethHw_chipAttach: Chip ID: 0xb95c; phyaddr: 0x1e
bcm_robo_attach: devid: 0x0
bcmiproc_eth-0
MAC address is 7c95:b10c:3d80

NVRAM_MAGIC found at offset 700000
nvram_init: ret 1
Reset CC2650 and TUSB3410
Reset TPM chip...
Reset AUTH chip...
Power Input Detection: POE AT
Hit any key to stop autoboot:  0

Loading kernel from device 0: nand0 (offset 0x800000) ... done
Loading rootfs from device 0: nand0 (offset 0x1600000) ... done
## Booting kernel from Legacy Image at 01005000 ...
   Image Name:   Linux-3.16.36
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2456685 Bytes = 2.3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02005000 ...
   Image Name:   uboot initramfs rootfs
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    27078656 Bytes = 25.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
boot_prep_linux commandline: root=/dev/ram console=ttyS0,9600 ramdisk_size=70000 cache-sram-size=0x10000

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Mounting local file systems...
UBI device number 0, total 3240 LEBs (411402240 bytes, 392.3 MiB), available 59 LEBs (7491584 bytes, 7.1 MiB), LEB size 126976 bytes (124.0 KiB)
Do the DB init,please wait...
ah_net: module license 'unspecified' taints kernel.
Disabling lock debugging due to kernel taint
Updating system config database...
System config upPOE Input Detection -> date complete.
AT
Enable PSE
gmac_var_init: NAPI2_POLL mode
Jumbo disabled
Jumbo disabled
bcm_robo_enable_switch: EEE is disabled
reth1: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 10.10.80.505_e5.1.2.3 (r659762)
register sniffer device on interface eth0.
register sniffer device on interface eth1.
register sniffer device on interface eth2.
register sniffer device on interface eth3.
Jumbo disabled
Jumbo disabled
 

 

Userlevel 7

Thanks for that output. Are you able to reset the device using the pinhole reset button on the back of the AP? If not, you’d likely want to open a case so an engineer can help you interrupt the boot process and attempt a TFTP flash on the AP to restore it. 

Hi sam

restart the device using the reset button, without solving the problem.

I have opened a case with extreme and I am waiting for a support response

I would like to ask if there is any extreme community in Spanish that you recommend?

Thanks

Userlevel 7

We do not have a separate community for Spanish speakers, however if you post here in Spanish we’d be happy to help you via a translator so please don’t hesitate to post in Spanish if that is easier for you. Additionally, our knowledge base should translate to the language you have set in your browser. 

Reply