Commit, then shutdown

[Tim Boswell]

I'm looking at making an IP/routing change to a remote ESA, and then powering it down for a remote tech to unrack. Obviously, as soon as I commit the changes to the routing tables, I'm going to lose connectivity to the appliance. Is there a way to either schedule a shutdown, or to "commit then shutdown"? My goal is for the appliance to be already configured and powered down when the remote tech gets to it. 

The only way I can see to achieve this right now is the steps below: 

1. Make all the changes I need to make, but don't commit anything
2. Open an SMTP connection to one of the listeners
3. Shut down the appliance with a 60 seconds wait for existing connections to close
4. Commit the IP changes while the appliance is waiting for the connection to close
5. Committing the change will sever the connection (because we changed IP), and the appliance will then shutdown. 

The snag is that I have no idea if I can commit changes after I initiate a shutdown. Can anyone advise? 

[Robert Sherwin]

Once you initiate the shutdown command, any uncommitted changes are lost.  As per making changes, but not committing and running the command... you see the following on CLI output:

Configuration changes entered but not committed.  Shutdown will lose changes.

Any chance of getting console connection, remote KVM hooked up?

[Bob Fayne]

The ESA will stack/buffer commands issued to the CLI to a certain extent. Try this.

Open a notepad or some other text editor. Enter your commands

commit somereason
shutdown 60

Make sure there is a carriage return after the shutdown command (hit Enter after 60). Copy this to the clipboard and paste it to the CLI. I tested it with reboot and it seemed to work but YMMV.