...when I'm relitively certain that the NodeIDs WILL conflict / possibly be duplicated ?
Any thoughts / help on this appreciated!
The node has to exist in the nodes table (Orion.Nodes) on the NCM server before you can use AddNodeToNCM to enable NCM management of that node. The script Diner referred to above (CopyNodes.ps1) can be used to copy the node from the NPM server where it is configured now to the NCM server.
You can't specify the NodeID when adding a node, so there is no danger of conflict/duplication of NodeID values.
What versions are you moving from/to?
Hello, for this purpose there exists sample script, which is bundled with your SDK installation. It's by default located in c:\Program Files (x86)\SolarWinds\Orion SDK\Samples\PowerShell\CopyNodes.ps1 . This will copy the nodes from one orion to another. Copies Nodes, Volumes(when enabled in script), Intefaces(when enabled in script) aand the pollers. There's one limitation, that it can't copy WMI nodes. Please go through the script. I believe this can possibly suit your needs
Our current NPM version is apparently 11.0.1, and NCM 7.3.2 is running on those NPM servers (because some version of it has to from what I'm told).
However, we're testing NPM 11.5, so I guess it would be NPM 11.5 (or 11.0.1) to NCM server 7.3.2. Our production servers are running 11.0.1, and as I said above, we're testing NPM 11.5 on a 'nonprod' server.
Your statement confuses me though. Looking at my AddNodeToNCM() method, (which of course calls the */Solarwinds/InformationService/v3/json/Invoke/Cirrus.Nodes/AddNodeToNCM verb) it appears that the payload / body data is simply "[<NodeID>]" (a json array containing the integer node id).
This runs as part of a console app I've written to programmatically add Node(s)/Interface(s) to the appropriate NPM server, then to 'let the NCM server know about it' so to speak. As far as I know, it's been working fine in tests, thus my confusion over your statement that I don't/can't add NodeIDs to NCM.
In fact, here's a snippet from my debug log:18-Mar-2015 22:03:22.9480 DEBUG AddNodeToNCM(): Calling18-Mar-2015 22:03:22.9520 DEBUG AddNodeToNCM(): Uri: |https://lsdorionnonprod:17778/Solarwinds/InformationService/v3/json/Invoke/Cirrus.Nodes/AddNodeToNCM|18-Mar-2015 22:03:22.9550 DEBUG AddNodeToNCM(): Payload: /[471]/18-Mar-2015 22:03:23.6429 DEBUG AddNodeToNCM(): response: 0fe0012a-e831-49e8-a20f-e240fddcd8b518-Mar-2015 22:03:23.6449 DEBUG AddNodeToNCM(): Done
In case that has any bearing on the facts (/what you're trying to tell me.)
I don't think this is what I'm looking for as I'm just trying to 'let NCM know, so that it can track/handle/deal with the specified Node' that's been added to either of our two NPM servers.
(Perhaps 'Add Nodes' was a bad way to put it.)
Thanks,
Scott
The function of "AddNodeToNCM" is to take a node that is already in Orion (in the Nodes table) and enable it for config/NCM monitoring. From the way you describe your setup, it sounds like you have three Orion databases - two with just NPM and one with just NCM. Is that accurate?
Essentially, yes. As I mentioned, I've heard that there are 'mini-versions' (or whatever the official term is) of NCM running on both of the NPM servers because it has to, but our "main" NCM server is now one, rather than two, which they did for several reasons. I can get you those reasons later today if need be, although I'm pretty sure the main reason was so that they could do configuration tasks against BOTH of the NPM servers (or the Nodes being tracked by same) in one place.
