It seems my last post was marked as spam; apologies if this is a duplicate.
We have been using Prime to upgrade code on our ~3,000 switches. We do distributions during the day building by building and stagger activations every minute in the early morning.
We've found (with both Prime 3.1 and 3.4) that, when doing more than 20 or so switches at a time, the lead switch in a TR will reboot before Prime can tell the downstream switches to reboot, so they never do.
What I want to start doing is distributing in mass, then use a CLI template to utilize the "reload at" command for switches building by building so the switches know to reboot themselves at the right time, eliminating the connectivity issue when the lead switch reboots.
I believe the problem is, when asking to confirm the reload, the terminal width is changing to zero, which I assume enables the behavior of simply hitting the enter or y key immediately confirming the reload with no chance to type out more than one character. Maybe Prime's adding a space which cancels the reload request. No reload is scheduled after this completes.
Is there a way to tell the template to accommodate the terminal width changing to zero?
Here's what I have for a template, and how it fails. I have to do a "clear line vty x" in the switch to force Prime to determine the job as failed, otherwise it remains "Running" indefinitely.
#MODE_ENABLE
wr
#INTERACTIVE
reload at $reloadTime <IQ>Proceed with reload? [confirm]<R>y
#ENDS_INTERACTIVE
#END_MODE_ENABLE
Error: Connection closed while executing the command #MODE_ENABLE
wr
#INTERACTIVE
reload at 05:30 Proceed with reload? [confirm] y
#ENDS_INTERACTIVE
#END_MODE_ENABLE
Response:terminal width 0
TAB_104_Eric#config t
Enter configuration commands, one per line. End with CNTL/Z.
TAB_104_Eric(config)#exit
TAB_104_Eric#wr
wr
Building configuration...
[OK]
TAB_104_Eric#reload at 05:30
