Open for Voting

Please modify NPM to "completely" rediscover a node when it is replaced, instead of forcing us to delete the old node and then add the new node. The rediscovery must include removing ports that are not present on replacement nodes.

I'm going through a forklift upgrade this year, replacing about 500 Cisco 2960S switches with 3850's. The replacement switches are given the same names and IP addresses as the outgoing 2960's.

The problem lies in NPM's inability to clean up / remove old ports that aren't present on the new switches.  They remain present in the list of resources for the node, grayed out, until the node is deleted.

I'd rather not have to delete a node and then re-add it just to compensate for NPM's inability to delete absent hardware or interfaces that are not present on the replacement gear.  

Since NPM has a "Rediscover" button for every node, and since that action discovers all NEW interfaces and hardware on a node, why shouldn't NPM be able to learn when some previously-discovered ports are no longer present, and either delete them automatically during Rediscovery or during scheduled Inventory Jobs, or call these ports out for attention after Rediscovery so we can evaluate the output and choose to delete them.

That would be a full-featured tool, and a better one for everyone's environment.

Please add this feature, and save us all the trouble of having to delete and re-add/rediscover nodes.

I'll send VPP's (virtual plus points) to everyone who votes this up!

Swift packets to you!

Rick Schroeder

Parents Comment Children
No Data