Adding Node Outside of the Web Interface

Hey everyone!

We're running Platform version 2017.3 in a network with no internet access. I'm working on getting our environment upgraded but until all of those documents get signed and stamped in triplicate, I have to work with what we've got.

Our Cortex and Administration services have stopped working which seems to prevent any web interaction with pages that include credential management. I'm not going to invest a lot of my time, or support time into a version so old that is already in process of getting replaced.

Since we can't interact with pages that handle credential management, I can't edit discoveries or access the add node page.

Does anyone have any suggestions on how to add nodes outside of the web interface, like directly to the DB?

Find more posts tagged with

add_node

Accepted answers

All comments

jm_sysadmin

I don't have an easy answer for you, my recollection of what I did on version 2017 is a little rusty. You may be able to use the code in the SDK, but I believe that fixing the cortex and administration services is a priority both for adding nodes and for the upgrades. Direct SQL writes might bridge the gap, but its not a path I have tried. Personally, I would make a back up and re-run the configuration wizard. Just making guesses about what you are running is tough, and I don't know your constraints. Do you expect to get on the new version soon? The license doesn't need to be assigned right away. Do you have the ability to copy the database and reinstall to new servers? You can still download the old code from the customer portal, and a fresh install might be quicker than trying to reverse engineer things that should work.

sinesalis

I am trying to get on the new version as soon as possible and I have been working with the support team on that process. The only thing holding the new version up is internal company procedures.

When we do get the green light for the new version, my plan is to actually build it all over again rather than try to port over the existing DB. There doesn't seem to be much worth retaining and I believe it would be far more trouble than it's worth.

[quote userid="242049" url="~/product-forums/network-performance-monitor-npm/f/forum/91063/adding-node-outside-of-the-web-interface/290207#290207"]Personally, I would make a back up and re-run the configuration wizard.[/quote]

This is something support graciously worked with me on even though 2017.3 is past EOL. Unfortunately that did not resolve it, nor did reinstalling/repairing the components or rebuilding some of the applicable tables.

I was considering the direct SQL writes, but I was worried that attempting it could leave our already finnicky environment even worse.

I appreciate the response!

I'll keep checking on this thread, but I won't count on a work around. New version seems to be the way to go.