I am trying to use the cli event detector. EEM version 3.2
I have a tcl script with the following trigger:
::cisco::eem::event_register_cli pattern "^profile" enter
I then have:
set full_command $arr_einfo(msg)
puts "full command is: $full_command"
I would have expected the last line to print out the full command i enter on the command line.
E.G. if i type "profile a FastEthernet1/0/30"
I would expect the script to output "full command is: profile a FastEthernet1/0/30"
However all it outputs is "full command is profile a" it drops the second argument.
Is this the expected behaviour? I thought maybe there is an issue with providing 2 arguments
so i tried joining the second 2 like this:
"profile aFastEthernet1/0/30"
but when i do this the script only outputs:
"full command is: profile"
Drops all the arguments. Anyone come across this or know what might be going on?
Cheers,
Anthony.