Support of Cisco 'install mode' switch upgrades. This method uses 'install...' commands to automatically copy .bin files to all members in a stack, unpack the .pkg, files, update the packages.conf, and number of other automatic checks. This is the preferred method for newer switches, and replaced the traditional 'boot system' aka 'bundle' mode upgrades for switches.
perhaps some confusion here. i believe the original FR was addressing some shared config change template being imported into ncm as out of the box. However, this i believe has turned into more device support ouf of the box. Potentially my fault, if i am correct in my assumptions .
I see that this is one of the top feature requests for NCM. I'm curious, is the request that we build more config change templates or build more device templates? The original request was certainly to add more config change templates, but the comments are all around device templates. I suppose one way to distinguish between the two is that adding more device templates will increase the number of vendors and devices that NCM supports, whereas adding more config change templates will improve the depth of support for the existing devices. So, if we had to prioritize one of the two higher, which would you pick (and why?)
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 190,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.