If you have a Juniper SRX router thingie, you might have noticed the orange light glowing on it:
It is the alarm light, and could have been triggered by many reasons, like the one mentioned in http://unixwars.blogspot.com/2015/08/juniper-srx-router-booted-from-backup.html>later post. On its defense, it is nice to know the silly router is upset about something. And, it sure beats a blinking 200W light or a blaring air raid siren. Still, it is staring at me with its deep unmoving orange eyes demanding attention. So, let's do some probulating, shall we?
When I asked it what's up, this is what it told me:
root@uranus> show system alarms 2 alarms currently active Alarm time Class Description 2014-03-23 10:42:35 EDT Minor Autorecovery information needs to be saved 2014-03-23 10:42:33 EDT Minor Rescue configuration is not set root@uranus>
After I saw that, it hit me like a, er, something heavy (please come up with something more original than the usual ton of bricks. I have never been hit by one and plan on staying that way) and unyielding: about that time I did a full wipe and reinstall! So, since it is being so nice to tell us what it wants, let's see about pleasing it. If we look at this thread in the juniper forums, we see the command to save the rescue configuration is:
root@uranus> request system configuration rescue save root@uranus> show system alarms 1 alarms currently active Alarm time Class Description 2014-03-23 10:42:35 EDT Minor Autorecovery information needs to be saved root@uranus>
One down, one to go. Now, how to save the autorecovery info? I am going to punt and assume the command should be very similar to the one we used to save the rescue info. Like Cisco's IOS, you can use ? to see which arguments a give command take. So, we try
root@uranus> request system configuration ? Possible completions: rescue Request operation on system rescue configuration root@uranus> request system ? Possible completions: autorecovery Manage autorecovery information certificate Manage X509 certificates configuration Request operation on system configuration download Manage downloads firmware Upgrade or downgrade firmware halt Halt the system license Manage feature licenses logout Forcibly end user's CLI login session power-off Power off the system reboot Reboot the system scripts Manage scripts (commit, op, event) services Request service applications information set-encryption-key Set EEPROM stored encryption key snapshot Archive data and executable areas software Perform system software extension or upgrade storage Request operation on system storage zeroize Erase all data, including configuration and log files root@uranus> request system ?
Aha, we found autorecovery. Which arguments does request system autorecovery take?
root@uranus> request system autorecovery ? Possible completions: state Manage autorecovery state information root@uranus> request system autorecovery state ? Possible completions: clear Delete previously saved autorecovery state recover Check for problems and recover state if needed save Save autorecovery state root@uranus> request system autorecovery state ?
So it seems that request system autorecovery state save will do the trick. Let's try it then:
root@uranus> request system autorecovery state save Saving config recovery information Saving license recovery information Saving BSD label recovery information root@uranus>
and the orange light's gone! Another mystery solved...