Boot Loop on resurrected X450e 24P

[Simon_Bell]

Hi all,

I'm trying to resurrect a long forgotten X450e. I powered it up with the intention of wiping the config as the credentials & IP are unknown.

I can see the boot sequence through the console and it throws up errors about "linkscan" and then reboots:

Starting ExtremeXOS 12.3.4b12Copyright (C) 1996-2010 Extreme Networks. All rights reserved.
Protected by US Patent Nos: 6,678,248; 6,104,700; 6,766,482; 6,618,388; 6,034,957; 6,859,438; 6,912,592; 6,954,436; 6,977,891; 6,980,550; 6,981,174; 7,003,705; 7,017,082; 7,046,665; 7,126,923; 7,142,509; 7,149,217; 7,152,124; 7,154,861; 7,245,619; 7,245,629; 7,269,135.

KICM: bcm_linkscan_register failed for unit 0, error -3!
KICM: bcm_linkscan_unregister failed for unit 0, error -3!
KICM: bcm_linkscan_unregister failed for unit 0, error -3!
insmod: init_module: kicm: Operation not permitted
Failed to open /dev/exosVlan (No such device)
****************************************************
EPM: can not install module exvlan going for reboot

****************************************************

I'm guessing this is telling me the switch is looking for a Master in a stack that it was once part of?

This error is stopping me from resetting the config as the switch never fully initialises.

I can get into the bootloader and have tried setting the image to null, but the above error keeps resetting the switch before I get a recovery logon prompt.

I've seen other articles that say updating the firmware through TFTP will fix this, but when I enter the serial number on the support page, I'm told no downloads are available for the switch.

I guess this is because it's out of maint, which is fair enough and I wouldn't expect to have access to the latest version of the firmware, but I would hope I can download the same version the switch is already running.

Any suggestions?

Cheers,

S.

[Simon_Bell]

Hi Henrique,

yes, I tried both pri and sec configs. Same result I'm afraid.

Kind Regards,

Simon

[Henrique]

Hi Simon, did you try to boot using the other partition?

In the BootROM menu you can do:

BootROM> boot 1

Then, if the issue persists, try to boot using the other partition:

BootROM> boot 2