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

Cannot see NCM Properties on the Node Edit Properties page

The documentation for NCM v7 indicates that the login and communication settings for an NCM node can be changed from the Orion Core node Edit Properties screen.

However, when I go to this page for an NCM node that is already Licensed to NCM, there is no section named "NCM Properties". I do see a check box named "Add Node to NCM" and it is unchecked. Does it have to be checked to be able to magically see the NCM Properties? Why wouldnt it already be checked if the node is already licensed in the NCM database?

This is very confusing.

Find more posts tagged with

Accepted answers

All comments

mdiotte

Hi freemen, You are correct in your understanding that you should see the NCM properties in the node edit when they are already licensed by NCM via the Manage NCM nodes page. Something does seem odd in this situation as you should not see the "Add Node to NCM" checkbox when editing a node, only when adding a new one. The way to add a node to NCM is to use the "Manage NCM Nodes" button in the NCM node list and make sure it equals "Yes" in the "Licensed by NCM" column.

Sounds like there may be a bug here and I would suggest opening a support case so we can investigate further.

danielleh

Upon opening a support case, would you please post back with your ticket #? Also, please keep us updated with your progress.

Thank you!
DH

freemen

Update: I suspect that there is something corrupted in the database, because I temporarily attached to a new NCM database, then added a single node from the Core database and everything worked perfectly.

The original NCM database was pre-existing and must have some issues. In any event, starting with a new NCM database and using nodes from an existing Core DB seems to work correctly.