SG-4860-1U won't power on automatic after power failure
-
I have an old SG-4860-1U, I think it must be 9-10 years old.
It is powered from a UPS, same UPS power 4 Supermicro servers. When we have a power failure the UPS shutdown all servers including the SG-4680 after 10 minutes so it is a controlled shutdown.
When we get power back everything starts as it should except the SG-4680. So, we have everything up and running again but no internet. To get the SG-4680 to power on again I must push the switch on the back.
Is there anything in the bios I can change to make it power on automatic? I looked around in the bios but it has very limited functionality.
-
@seanr22a Which UPS package are you using? There's a checkbox in APCupsd for "Kill on Power Fail" which powers off the UPS. I know the ARM models can't actually power off on their own...don't recall about the 4860s.
Ours both eventually died BTW, just one day lights were on but no one was home. (IIRC)
-
@SteveITS OP is asking if there's any way for the SG-4680 to power itself back on following restoration of mains power (which may or may not have included UPS battery depletion).
-
@tinfoilmatt I know, maybe I wasn't clear, but there are some models that don't fully shut off unless they actually lose power, thus don't boot up again in that situation. So a "shut yourself down" followed by the UPS regaining power before its battery dies (or the outlet is shut off) doesn't trigger a boot. It may not apply to the 4860...want to say that was just ARM units. But that's the checkbox in apcupsd. (which, IMO, is not clear what it does, and it's unchecked by default)
If the router is actually losing power and doesn't boot at power on I'd be worried it's near its EOL. (does console show anything?) I don't recall our exact dates offhand but I think ours lasted around 5 and 7 or maybe 6 and 8 years.
-
@SteveITS Interesting. So if OP is making use of the
apcupsdpackage on pfSense (and obviously ensures that pfSense is configured to 'shut itself down' last/only after the other four Supermicro servers are fully powered down),apcupsdcan also instruct the UPS to kill itself? Then once mains power is restored to the UPS, that would cause all devices, including the SG-4860, to power back up automatically?Being that the
nutpackage purports to 'support APCUPSD protocol', presumably it may also be able to do the same. -
@tinfoilmatt said in SG-4860-1U won't power on automatic after power failure:
apcupsd can also instruct the UPS to kill itself? Then once mains power is restored to the UPS, that would cause all devices, including the SG-4860, to power back up automatically?
Yes that's the trick. If the battery runs out the UPS turns off. If the battery doesn't run out and the outlets aren't turned off (that's a setting in APC PowerChute Windows IIRC) then the devices plugged in to the UPS technically never lose power. It's basically the same as Diagnostics>Halt and waiting forever for it to turn itself on again.
I've never used NUT so can't help there.
-
The 4860-1U was a bit special in that respect. I'm not sure there is a way to force it on from that situation.
-
I'm not using the APC package on the SG-4860. I have the APC software running at one of the Supermicro servers.
In the script that runs when the UPS is going turn itself off completely it ssh in to the SG-4860 and the other Supermicro servers and initiate a shutdown and finaly shutdown itself - very simple setup. I never get into the situation mentioned there the power is restored after the shutdown has been made, if I would get there none of the servers would come back online.The question is why the SG-4860 doesn't power on automatic when the power is restored. It's a bit strange because in my world the pfsense box is the one that always should start automatic after a power failure.
-
It's been a while! But as I understand it the power supply used in those early 1U units was capable of retaining sufficient power that it might remain in standby after a power outage. In that situation the button on the back can be used to power it up.
If you're just using a script you might try telling the device to shutdown and halt rather than power off (go to standby).
