Yeah, safe if you do it first. Maybe a good habit to get in. My "F5" safe mode comment was to disable scripts and such on boot.ctrl-x when doing something like this
----This I have yet to try, but I understand that if you do a Netinstall using the 'configure script' option, this will install the OS with your configuration settings as 'default' - so a 'system reset' will merely reset the RB to your original config...
Can anyone confirm this?
I like the way Juniper does it on JunOS even better. In Cisco IOS every command that you type immediately takes effect, even if it is not yet commited to flash and would not be restored after a reboot. For example, if you're logging in to a Cisco IOS box via telnet and issue a "shutdown" command for the interface via which your telnet session is running you've killed yourself off.Which would be perfectly possible by adopting a system like on Ciscos:
All changes are in memory only. Reboot, and they are gone away. Only a dedicated command writes the current running config to the flash and makes it permanent...
I've intentionally done many system reset's remotly before... we build the config of our AP's out of a database and it dumps a config text file for us, it's occosionaly easier to dump a "fresh" config rather then go in and change settings... so I do a system reset, then mac-telnet in from another device on the tower, and paste the config in, do a reboot just to make sure (actually part of the config script) and the AP boots back up 100% configured and fuly functional.perhaps if feasible that both
/ system shutdown
/ system reset
should be available through serial and console port only?
how often do you do a reset or shutdown unless you're actually on site and about to pull the plug or reconfigure it from scratch?