11-18-2013 11:51 PM
Is there a trick to getting the enable password working on a Cisco IOS device?
I set up my first workflow to connect to a Cisco IOS device recently and initially could not get the enable mode working.
Using the "Send Interface Commands" activity, I issue the "enable" command.
From there, the activity times out.
The target is using the Cisco IOS expect template, which I notice has the "Elevating privilege command" option.
How is this used? Should the expect template automatically detect the elevating command and then use the expects below?
If so, this does not seem to be working.
The only way I could get it to work was to add my own manual expect to the "Send Interface Commands" activity. I used the Targets "Elevating Privilege Command" variable reference as the expect, and sent the admin users password in response.
Solved! Go to Solution.
11-27-2013 04:38 PM
It is to open up the expect template to allow you to use an elevate command. If you don't enable those expect templates and you executed an "enable" command and you command prompt turned to the "#" sign, then it would not match any expect templates and the further commands would time out and not work.
--shaun
11-19-2013 03:29 AM
I'm not sure about a "send interface commands" activity, as I do not believe that exists. (Was it something you had custom done by AS?)
However, whenever I need to elevate to enable mode I just use the "Execute Terminal Commands" activity and put "enable" in there and then add an expect to it that would catch the request for password and send back the proper enable level password. The same should hold true for any IOS device.
If you continue to have issues, open a case and let's get some more pairs of eyes on it.
--shaun
11-27-2013 02:54 PM
Sorry, "send interface commands" was my display name for thhe "Execute Terminal Commands" activity.
What I did sounds like what you do too, but I guess that raises a question for me.
In the expect Template properties for the Cisco IOS Device, there is a check box for "Elevating privilege command".
What is this section for if it's not to set up an "expect" for the enable command? I thought with this in place, we wouldn't have to manually specify an expect for "enable" in the activity itself.
11-27-2013 04:38 PM
It is to open up the expect template to allow you to use an elevate command. If you don't enable those expect templates and you executed an "enable" command and you command prompt turned to the "#" sign, then it would not match any expect templates and the further commands would time out and not work.
--shaun
11-27-2013 06:12 PM
So the "Admin Prompt Pattern" above is irrelevent, or it needs both?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide