RANT! Fix Device Selection in NCM Manager.

I think I get it, I think I know why the selection tool allows you traverse multiple groups and select and modify devices from different groups at once.

I think I can see some usefulness but, I HAVE NEVER NEEDED IT.

It has only ever caused frustration as I accidentally modify 10 devices from another group I was done working on an hour ago......

Does anyone else have this problem?

Solarwinds, can you remove this "functionality", please?

Find more posts tagged with

manage_ncm_nodes

device selection

device select

selection

ncm

Accepted answers

All comments

jpetkevich

ansenlabardee Are you open to having a session to talk about this? I also recommend creating a Feature Request so that others can upvote your idea.

ansenlabardee

Sure when would you like to talk? I would have opened a feature request but this feels more like a bug?

rschroeder

Having the ability to affect multiple machine types is helpful for me. I can select all my Cisco 9300's and 4510's and 2960XRs and make the same change to their community strings or AAA settings and more. I use this functionality.

On the other hand, I've not yet had the misfortune of selecting two or more different platforms and applying a config change erroneously to one or more of them. I've had several occasions where I almost made config changes to unwanted devices--but only when I have not double-checked the nodes selected. It's easy to use NCM's Configuration Management page to inadvertently select the machine types you want AND machine types already checked by an earlier script.

In this hypothetical example I initially selected one switch for an upload that worked successfully. The tool kept the the original single switch in the "selected" nodes area when I later came back and selected a router to configure.

It's easy to see TWO nodes are selected instead of one, and it's up to me to:

Use the "Clear Selection" link to remove all nodes BEFORE I start selecting new nodes, or
Use the "Show selected only" link to show what's going to be updated

Yes, this is a spot that can cause problems if you don't use care. I'd be up for making it more idiot proof by automatically engaging a "Clear selection" option before a new script could be executed, but that has an inconvenient result, too. If I want to perform multiple tasks against the original nodes, automatically clearing the selection means I must reselect them.

The trick is to use the "Show selected only" EVERY time I use this window, and then I must review the nodes to ensure I'm only affecting what I expect to affect. Or I must use the "Clear selection" option before doing anything.

Double-check, triple-check, before applying changes. Like a good carpenter, measure twice, cut once.

ansenlabardee

Look I get what you are saying but I have to disagree, its broken.

Like I said I understand the use case; "I think I can see some usefulness".

In its current configuration it has to be causing more headaches and wasting more time than its saving across the board.

Objects should not remain selected if I go to an entirely different section of Orion.

There is no reason they even need to be selected if you change tabs inside of configuration management.

It's far too easy to select objects inside of a group, make a change and comeback later forgetting that you have selected items.

This whole attitude of "fix the Enduser" and not fixing the product is getting old and seems to be very prevalent at Solarwinds.

I might be a bit more forgiving if the documentation wasn't garbage too.

jpetkevich

I will email some times to you directly.

sja

If the configuration manager is not working for you..try using the compliance with remediation.

I find it very useful ...

That video that explain how..

https://m.youtube.com/watch?v=NOSPupDFsbg