I have an appbeatdc from crescendo networks that I am trying to use Orion NCM to manage. The problem that I am having is that it appears to not be recognizing the command prompt for the device when I execute a command script, and thus every command issued to it by NCM has to time out before it will move on to the next command. The ultimate result is that the command script gets run, but takes way longer than it should do to waiting for the timeouts.
I have tried all manner of settings with VirtualPrompt and VirtualEnablePrompt, tried inserting multiple CRLFs after each command, switching CRLF to CR, none of which appears to have any effect on the issue. Using session tracing, it also looks like there may be an extra control character in every response from the device (seen in SWTelnetDebug.txt) that is fouling up it's ability to detect the prompt. Also, each command appears to be sent (or at least logged) twice. I am attaching session trace output. I've tried many permutations, but the simplest device template I've used and still seen the error is:
<Configuration-Management Device="Generic CLI Devices" SystemOID=" 1.3.6.1.4.1">
<Commands>
<Command Name="RESET" Value="${CR}"/>
<Command Name="MenuBased" Value="false"/>
<Command Name="VirtualPrompt" Value="\>"/>
</Commands>
</Configuration-Management>
Any help on this would be greatly appreciated.
