Script execution is sssllllloooooooowwwwww......?`

Hey there,

I'm executing a script from Cirrus 3.5.1 and it's really really slow - on the order of 15 minutes to run 15 lines of code. Any ideas on why the scripting engine is taking so long to execute? At this rate, it's a whole lot faster for me to this manually.

Thanks,

Will

Find more posts tagged with

Accepted answers

All comments

willhepptemp

As a follow-up, below is what's in the session trace. Clearly, Cirrus is just sitting there wasting time for no reason. Any ideas where "TimerTick" is located and how I can change its frequency and duration?

Will

Process Line = <* dbnnetaccsw11a-34n.14 # >
Pushing back: <* dbnnetaccsw11a-34n.14 # >
mPrompt is : <dbnnetaccsw11a-34n.2 # >
TimerTick: mstrData=<* dbnnetaccsw11a-34n.14 # > State=3 - Connected to server - idle
Pending Disconnect = False
TimerTick: Just tick-tockin away. ..
TimerTick: mstrData=<* dbnnetaccsw11a-34n.14 # > State=3 - Connected to server - idle
Pending Disconnect = False
TimerTick: Just tick-tockin away. ..
TimerTick: mstrData=<* dbnnetaccsw11a-34n.14 # > State=3 - Connected to server - idle
Pending Disconnect = False
TimerTick: Just tick-tockin away. ..
TimerTick: mstrData=<* dbnnetaccsw11a-34n.14 # > State=3 - Connected to server - idle
Pending Disconnect = False
TimerTick: Just tick-tockin away. ..
TimerTick: mstrData=<* dbnnetaccsw11a-34n.14 # > State=3 - Connected to server - idle
Pending Disconnect = False
TimerTick: Just tick-tockin away. ..
TimerTick: mstrData=<* dbnnetaccsw11a-34n.14 # > State=3 - Connected to server - idle
Pending Disconnect = False
TimerTick: Just tick-tockin away. ..
TimerTick: mstrData=<* dbnnetaccsw11a-34n.14 # > State=3 - Connected to server - idle
Pending Disconnect = False
TimerTick: Just tick-tockin away. ..
TimerTick: mstrData=<* dbnnetaccsw11a-34n.14 # > State=3 - Connected to server - idle
Pending Disconnect = False
TimerTick: Timeout

Haley

The Session Trace is showing that Cirrus is expecting a response back from the device but no response is being returned by the device. Therefore, the device is waiting the entire time before sending the next command. You can modify this time setting under File > Settings > Network > Telnet Settings > Telnet Prompt Timeout.

willhepptemp

Hey Haley,

Thanks but why would this be happening for only Extreme Networks gear? I think that the return is coming back but it's not what Cirrus is expecting. So, for example, the Extreme XOS has a sequence number that increments for every line of code entered. As a result, the prompt is different after every entry. Also, it's not consistent. Sometimes it seems to go faster but mostly it does not.

Thanks again,

Will

Haley

That sounds like the culprit. Cirrus is expecting the same prompt to be returned and since the returned prompt keeps changing, then Cirrus waits for the timeout to expire before sending the next line.

Haley, I have found the same slow behavior with Cirrus & Cisco elements in two scenarios;

Banner messages (No prompt on next line), and for some odd reason
Blank lines in a configuration script snippet.

Do you have blank lines in your script? Might help..

-JP

willhepptemp

Oddly enough, I did have blank lines in the script but removed them once things were slow to see what would happen. Unfortunately, it didn't make a difference...