I'm automating some interaction with Cisco ASA devices. I need to do the following:
- login over ssh
- send 'enable', provide enable password
- send 'configure terminal'
- send some other commands, never going to deeper level of config.
- send exit (gets me back to enable mode prompt)
- disable (should get me back to the basic prompt)
Then a bit later, another scripted bit tries to send 'enable' again. This time, the device asks for a username and password. Not just the enable password. This happens consistently on some devices I have tried and never on others. I'm guessing it is something to do with 'disable'. I don't have to use that command, I just need to drop from enable mode back to a regular prompt so that future bits can always expect to start from the base '>' prompt.
Apologies in advance if this is too basic of a question. Any ideas?
Ahh, the answer appears to be this configuration setting:
With that,
disable
thenenable
will require a password.