Hello...
We have been using an Command Script in Orion NCM (version 6.0 DLX) to back up the configuration of Avocent ACS48 devices. It looks like this:
saveconf ssh cyclades/${SysName}_${YYYY}${MM}${DD}.tgz <destinationserver> <username>
<password>
The first line of the script describes where the configuration is to be copied to and the username to use to log on to the device. The second line of the script is the password for the username. This works quite well.
We have recently installed some Avocent ACS6000 series devices. These are basically the upgraded model of the ACS48. The ssh command changed slightly so the script now looks like this:
saveconf --ssh cyclades/${SysName}_${YYYY}${MM}${DD}.tgz <destinationserver> <username>
When Orion NCM issues a Command Script, it does appears to send all of the commands at once. This is causing an issue with the ACS6000 as it does not allow 'pre typing' of the password. The 'saveconf' command on the first line of the script takes about a second before it prompts the user to enter the password. As Orion NCM appears to send both lines of the script to the device as soon as it has logged on to it, the device does not recognise that the password has been typed in.
Programs like CatTools handle free-form multi-line scripts differently. It waits for a valid response from one command before it goes and issues the next command. This closely mimics a user who often needs to wait for a prompt before they can send the next line of text or data to a device.
Is there a way for Orion NCM to either pause for a few seconds between sending each line of a command script, or can NCM wait for some output from the device before it sends the next line of the script to the device?
Has anyone else had issues like this with Orion NCM Command Scripts? If so, were the issues able to be overcome?
Regards,
... Simon
<password>
