Good morning,
In my use of NCM on my nortel switches I have learned that the scripts that were shipped wit the product do not totally suffice.
We use 8610's, 470's and 5520's switches. I wanted to use NCM to login and pull down configs. Because of the assumed low risk I ran the log in script on a 470 during business hours. Now those who use these devices know that these are menu driven. The script will automate a human interface to get to cli so it can run the applicable commands to get the config. Now what happened is the config executes 14 down arrow commands. When I did this on my 470 stack, 14 down arrows selected "Reset default settings" and when it entered that menu, the script ran "Terminal lenght 0". With discussion with the dev guys at solarwinds we determined that the space in the term length command changed the "No" to a "yes" and then it hit enter and enter again, which reset the switch to it's default settings causing a major outage.
After some digging around I have found a fix for this issue.
When a 470 or a 5520 are running in a stack of anything more than 1 device the amount of down arrows that it takes to get to cli is 16. When these devices are running in single mode the down arrows required is 14.
I simply just made a copy of the shipped script, changed it's name to Multi and added 2 ${DownArrown} commands.
The other night, during an maintenice window, after running them in my lab, I deployed the tool to my network. Because the 8610 switches are all cli I didn't experience any issues with them.
I hope this helps anyone running NCM with Nortel devices.
