Script Uploads Non Cisco Devices

andersond

I am having issues with the speed in uploading a script command to HP switches. SolarWinds support is looking into the matter, but haven't been able to provide anything concrete yet.

Anyone else having speed issues with Script Upload to non Cisco devices?

---

Here is what I have found:
--------------------------------------------
CIRRUS SCRIPTING TO CISCO DEVICE:
--------------------------------------------
1. Cirrus issues a single line command to the device in one packet.
2. The Cisco device echos back the original command to Cirrus. This echo is done by sending one character in each packet back to Cirrus.
3. The Cisco then sends back the command line results to Cirrus via one packet.
4. Cirrus then sends the next line of the script you are uploading.

Everything is working hundy dory. The scripts run as fast as you can push the link to your remote device.

--------------------------------------------
CIRRUS SCRIPTING TO HP DEVICE:
--------------------------------------------
1. Cirrus issues a single line command to the device in one packet.
2. The HP device echos back the original command and the command line results in one packet.
3. Cirrus pauses (anywhere from .5 seconds to 4 seconds) then issues the next command.

This process continues until the script is sent. The pauses before sending the commands can make a large script (say 120 lines) take over 5 minutes to run. The fact that scripts run sequentially is a problem here. If you want to push this script to say 70 devices you are looking at over 5 hours to run the scripts.

Mithrilhall

I beta tested v1 & v2 of Cirrus with our Dell switches and Cirrus v1 didn't work. After I gave Solarwinds access to our switches they got Cirrus v2 working flawlessly with our Dell PowerConnect switches.

Have you given a developer from Solarwinds access to any of your switches for testing?