Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Nodes not showing under NPM but are in fact there

Anyone have suggestion as to why one AD / Orion account can see all the nodes under a group in NPM Summary and another account can only see SOME of the nodes under the same group? (We have AD groups, assign those AD groups access to site groups in Orion.) But in the case of the account not seeing all the nodes, if we go to manage the nodes under the site group, we can actually see the device when we search for it!

Find more posts tagged with

node_missing_from_npm_summary

Accepted answers

All comments

d09h

If the node management page is the second web page where everything appears, perhaps there is a limitation on the first web page? Which limitations do you have on that page, on accounts, and on the resource in question on the page?

Do you use domain authentication? If so, do both the affected and unaffected account see the same domain in upper right of web pages

(ex. ACME CORP\singlebuoy and ACME CORP\coworker)?

cahunt

First thought would be limitations, but if you can find it in a search you may check your views per account and see if they are different. Possibly 2 views that look the same, but one module has a filter on it (check the edit button on the module).

You can post a screen shot of each page with the different nodes listed... also the manage nodes page (and how it is sorted...could it be sorted differently?)

singlebuoy

Im looking under Settings > User Accounts > Manage Accounts > Groups > Check off the group, Edit and under Account Limitations there is only one rule and its set to allow access to the site group. We use domain authentication. The two accounts are under different AD groups and it is reflected in the upper right hand corner.

cahunt

not sure what Group this is, but your Limitations of North and South America - are they on the other account?

If so, can you post a shot of each display or manage nodes page where the list of nodes shows (so 2 shots of same page with the diff account logins...) - this is really better coming off a summary page...if it is the manage nodes page include the current sort option on each shot.

singlebuoy

On the other account there are no site limitations other than it being read only world wide. Its not restricted to any site. I actually have multiple accounts and the only one that I can see all the nodes is my read only account which is the bottom pic.

d09h

Perhaps temporarily change the grouping (maybe even remove?). If that is unacceptable, make a copy of each page, and assuming the behavior follows the copies, see if ungrouping or even grouping by different criteria actually shows the missing devices, or if it always omits devices.

Maybe write an SWQL query to achieve the same grouping. This is more of a workaround mentality than identifying the actual root cause. Which is more important to you?

cahunt

if the view ID is the same, then it would be related to the account. If you are familiar with the DB Manager you may be able to find the details in one of the views tables and make sure they match.