Hi
I just spent a few hours Troubleshooting a Config Change Template which took almost 2 minutes time to configure two simple access interfaces on a Switch. (it's not a Cisco Switch)
in the device template I had previously entered the following lines, since the "enable mode changes the prompt to something like [hostname]
<Command Name="MenuBased" Value="false"/>
<Command Name="VirtualPrompt" Value="]"/>
<Command Name="EnableIdentifier" Value="]"/>
Thus the Config Change Template still took almost 2 minutes to complete.
After some time I discovered in the Session-Trace the followin lines:
[29.07.2015 18:06:38] UseExactPromptMatch=False
[29.07.2015 18:06:38] Menu-Based mode=False
[29.07.2015 18:06:38] FreezeLoginForPreCommands mode= False
[29.07.2015 18:06:38] FISP mode= False
[29.07.2015 18:06:38] WODSSH Version: 3.0.0.184
[29.07.2015 18:06:38] UseVirtualPromptForCommands False
Searching around I found no reference for this either in the current NCM Administration Guide (V7.4) nor in the Forum.
This made me curious and I added the following line in my Config Change Template
<Command Name="UseVirtualPromptForCommands" Value="true"/>
This sped up execution time a great deal. Now it needed only 8 seconds (compared to almost 2 minutes before). Now it's about the same as when I use a similar template on a Cisco Switch.
To me this is quite important, because I have other Config Change Templates which are far more time consuming (one took 10 minutes to execute, which I found way too much - I'm curious how this will accelerate).
Is this an undocumented command? Why is it not mentioned anywhere?
Addition, 31.07.2015:
It seems to have some side-effects. Last night my nightly config save did not get the whole config from every device that uses this template.
There is a line
snmp-agent usm-user v3 someUser authentication-mode md5 cipher @%@%]y_v>L^lSqV(o)Rn1Yt/,.Qv@%@%
which seems to make NCM believe that it has encountered the prompt, even if you have the UseExactPromptMatch command in the device template.
The relevant part of my device template looked like this:
<Commands>
<Command Name="MenuBased" Value="false"/>
<Command Name="VirtualPrompt" Value="]"/>
<Command Name="UseVirtualPromptForCommands" Value="true"/>
<Command Name="UseExactPromptMatch" Value="true"/>
<Command Name="EnableIdentifier" Value="]"/>
.......
Now I've removed the UseVirtualPromptForCommands line and everything seems back to normal, including the extremely long execution time for a simple Config Change Template.
I still wish someone could tell me more about this UseVirtualPromptForCommands command