Please add support for the following:
Cisco 92/93/94/95/9600 switches
Cisco 9800 wireless LAN controllers
Cisco 9100 access points
In the case where SW doesn't already have a canned process to use for upgrades, first I check the online shared templates within Thwack to see what others may have figured out and shared. You should be able to see that within one of the pages/tabs inside NCM. If you dont' find what you want, try various searches to guess what others might have called their shared upgrade template.
If nothing useful has been shared by others, that's when I document literally every step of the upgrade, and then take any of the other templates and customize it to use the steps I've documented.
And then test, test, and test again.
If you go this route, be aware that small changes in future IOS or hardware versions may require you to modify your new template--or even scrap it and start from scratch.
Are you starting with a particular SW upgrade template? I've tried modifying a few we already had and it failed. Haven't seen any other templates that accommodate the upgrade commands negatively. If there is I haven't seen it. I'm sure I could build it as a script, but would love to use it as a template in the NCM firmware upgrade tool.
Any suggestions would be appreciated.
I always start with whatever SW provides, the modify it as necessary to get the job done. For me, the trick is completely understanding the way to upgrade manually, one box at a time. I carefully document every single step and then compare it to what's available within NCM's Upgrade Manager.
If NCM doesn't have a solution pre-built, I'll take an existing upgrade process job, built for a different hardware line, and customize it to include all of the steps I documented (see previous paragraph). Then I only run the new job in a test environment so I can check to see it succeeded, didn't hang anywhere, and leaves the equipment in good working order. While I'm doing the test upgrade I carefully time it so I can predict to the SysAdmins how long the upgrade will take. Although, in a 7x24 Five-9's medical environment like I've worked in, everything has resilience, and should remain up even during an upgrade. Every server has at least two NIC's that go to two different switches, therefore any Nexus switch can be down/rebooting for an upgrade while the other switch serving a different NIC on the same server remains up & running.
Let us know what challenges you run into--and how you overcame them.
Please let us know what you feel is not supported already. I have Catalyst 9300's, 9400's, and 9500's being monitoring by NPM and backed up by NCM and tracked with UDT.
In response to the this request -
NOTE - I DO NOT HAVE SAM I ONLY HAVE NPM/NCM/UDT/VNQM
The device Cisco Nexus 93180YC-FX is not reporting vPCs
I would like to see a device type added for the Cisco 9800 Wireless LAN Controller similar to the existing device type for the 5500 series WLC.
The 5508 WLC shows device type of: "Cisco 5500 Series Wireless Controller" and is given the "Wireless Controller - Summary" view by defualt.
The C9800-L-C-K9 is only being recognized as device type: "Cisco" so I can't see the "Wireless Controller - Summary" view on this device unless I changed the "Web View" for all "Cisco" devices to be "Wireless Controller - Summary" which would then mess up all the standard Cisco device views.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.