SG-5100 lost all ix ports after power outage
-
@stephenw10 Yes, several power cycles.
When we get the 6100 next week I will be able to do more experiments on it.
-
Was your extended power outage due to weather perhaps? If so, I would suspect damaged hardware via a transient surge. Ethernet cabling can make a dandy antenna for picking up EMF surges caused from nearby lightning strikes. I've had switch ports destroyed that way in the past.
-
@bmeeks said in SG-5100 lost all ix ports after power outage:
tro
It was a scheduled outage due to building maintenance.
-
When you are able there is something we might try to rewrite the NIC eeprom contents in case it has somehow been corrupted. That's about the only thing I could imagine changing the PCI device IDs like that. The driver is not complaining about the eeprom checksum which it usually would but it could be it doesn't get that far.
-
@stephenw10 I just received 6100 today and restored to it. Therefore now I have SG5100 to do whatever you want to try regarding eeprom.
-
You can try to reset the NIC EEPROM on the 5100 as follows:
- Connect to the serial console
- Power on the device
- Hit
EscorF12to get the boot menu and chooseEnter Setup - Go into the BIOS settings under Advanced > CSM Configuration
- Change Network to a different value such as UEFI
- Save/exit and reboot
That will nudge it to rewrite the NIC EEPROM and then it should boot (but perhaps slower).
If the NICs work again after that, then go back into the BIOS and change that same setting back to Legacy or whatever it was on yours to start with.
If that does not help, then it probably is a hardware failure.
-
@jimp I tried and did not fix. Thanks for your assistance.
I can continue to use as a test/backup router since it has two working ports still.
-
@brians said in SG-5100 lost all ix ports after power outage:
@jimp I tried and did not fix. Thanks for your assistance.
I can continue to use as a test/backup router since it has two working ports still.
Oh well, it was worth a shot.
Out of curiosity, was the error in the system log still the same as before?
-
@jimp Yes the error was same.
-
Incase somebody finds this thread in the future, there does appear to be issues with some netgate hardware and hard power downs.
Part of our final testing for a new datacenter deployment we perform a hard failover of all equipment by removing the power on each of the redundant pairs of equipment. After removing the power on our 1537 the unit booted back up and ix0 and ix1 were no longer registered. The two onboard copper ports and the expansion slot ports all worked.
pciconf -lv showed the PCI device, but like the OP, it was registered to none@pci. We tried the EEPROM rewrite and that didn't help. Netgate support collected a full status dump of the device, then issued us an RMA for replacement.
Hopefully this saves somebody some time, this hardware appears to be sensitive to unclean shutdowns.
-
Hmm, that's weird. I've seen SFP ports behave oddly across a power cycle, especially with connecting module before vs after boot. But the ix driver was patched to still allow it to attach.
