If i connect that correctly, a command like:

Code:

cmcli get 101

asks itself for a user/password. Your expect-script provides that only once, not for every command. My suggestion is to do it the other way round. Put the following in a script "execasadmin.exp":

Code:

#!/usr/bin/expect
set timeout 20
set mycmd [lindex $argv 0];

spawn $mycmd

expect "Please Enter UserName: " { send "admin\r" }
expect "*Password: " { send "admin123\r" }

interact

This will expect a command line as argument, execute this commandline, then feed it the user and password. Call this in a loop like this:

Code:

#! /bin/bash

mycmdarr[1]="command1"
mycmdarr[2]="command2"
mycmdarr[3]="command3"
mycmdarr[4]="command4"
# [...]
i=1

while [ $i -le ${#mycmdarr[@]} ] ; do
     /path/to/execasadmin.exp "${mycmdarr[$i]}"
     (( i++ ))
done

exit 0

Notice that there might be difficulties once you include redirections, pipelines and other advanced shell features into your commands, but for single/simple commands it should work.

I hope this helps.

bakunin