cancel
Showing results for 
Search instead for 
Did you mean: 
dpatzold1979
Level 10

NPM 10.2.2 Defaults to select all active interfaces when adding a node. Can the default be changed?

Jump to solution

After upgrade to NPM 10.2.2 all active interfaces are selected when adding a node. Prevoiusly in  10.1.3 only had cpu & memory were on by default.

For example adding access layer switches is very common for us and we only want to monitor CPU/Memory by default. I could not find anywwhere to change the default behavior.

Any advice or would this be a feature request to go back to NPM 10.1.3 way.

For now instruct to select none then go back and select CPU & Memory

2012-04-17_095138.png

0 Kudos
6 Replies
casey.schmit
Level 13

Re: NPM 10.2.2 Defaults to select all active interfaces when adding a node. Can the default be changed?

Jump to solution

Unfortunately, there is not a way to change this behavior.  If I remember correctly(and it's been a while), we changed the behavior to make it easier for folks, since in most cases, users want to add more than just CPU and memory.  Your workaround(select none, then only CPU) is currently your best option.

Thanks,

Casey

0 Kudos
savell
Level 13

Re: NPM 10.2.2 Defaults to select all active interfaces when adding a node. Can the default be changed?

Jump to solution

This change in behaviour managed to just bite us.

Operations staff weren't used to checking what was selected by default - adding a number of voice gateways with the (now) default behaviour added >500 interfaces per voice gateway.

It will be just as bad for switches.

I understand why some sites would like the new default, but I would like the option to go back to just CPU and Memory as the default...

How do I quickly detect devices that may have a large number of interfaces monitored?

I can educate, but it's going to happen again - I need some way to see when  it occurs and on which devices.

Dave.

Edit:

So I can do a quick SQL Query that tells me which nodes have a large number of interfaces monitored.

SELECT Nodes.Caption, Interfaces.NodeID, Count(*)

FROM [Interfaces]

LEFT OUTER JOIN Nodes ON Interfaces.NodeID = Nodes.NodeID

GROUP BY Interfaces.NodeID, Nodes.Caption

ORDER BY Count(*) desc

I really don't want to create another process/report however to keep an eye on this type of thing.

0 Kudos
dpatzold1979
Level 10

Re: NPM 10.2.2 Defaults to select all active interfaces when adding a node. Can the default be changed?

Jump to solution

So i trained my users as i caught this after the upgrade. and it already hit me 2 times. It increases elemenets/load on the poller. It adds Vlan interfaces or loopbacks that we just dont need to monitor.

0 Kudos
netlogix
Level 15

Re: NPM 10.2.2 Defaults to select all active interfaces when adding a node. Can the default be changed?

Jump to solution

I don't like it either, Server 2008 R2 always shows 6+ interfaces and I know that it really only has one, so I have to click to change to none, then check off the ones I want.  It's not that hard, but it a little bit of a pain now.

0 Kudos
savell
Level 13

Re: NPM 10.2.2 Defaults to select all active interfaces when adding a node. Can the default be changed?

Jump to solution

Can we request that this be logged as an enhancement request please (make the default behaviour selectable).

As a general rule, I would have thought that any change to previous default behaviour should be made selectable - to avoid situations just such as this.

Dave.

0 Kudos
Highlighted
dpatzold1979
Level 10

Re: NPM 10.2.2 Defaults to select all active interfaces when adding a node. Can the default be changed?

Jump to solution

Guys i added this to the feature request section.

Please go "Like it" to increase traction on this request.

http://thwack.solarwinds.com/thread/48577

0 Kudos