jasadelll

When can we expect this to be capable? We shouldn't have to do any workarounds like adding loopback intefaces to every one of our nodes or do any complicated discovery filtering (which, by the way, is STILL not possible) in order to make this work. We should simply be able to assign multiple IP addresses nodes. With…

So here is my workaround. It's hokey, admittedly, but it's the best I can figure out. I have nightly discovery running on all of my subnets. When discovery finds an existing host under a separate unique IP address, I do the following * Select the newly discovered node and click 'Import Nodes.' * Deselect all volumes and…

Has there been any promise of this feature becoming available in future revisions? Periodic discoveries are completely manual to sift through, particularly where the node with multiple IP addresses is a router or a server with several volumes. It nearly renders regular discoveries useless. I've been adding an exceeding…

I'll take the lack of replies to be a "no." Well if there is truly not a feature to keep IPAM synchronized with NPM, that would be a good feature to consider for future revisions.

Support helped me figure it out. Even though there were no other active jobs in NCM's scheduler, the Windows task scheduler had three "orphan" jobs out there named "OrionImport-####". I didn't know that NCM-scheduled jobs show up in the Windows task scheduler. Anyway I'm good to go.

Found the answer myself. I needed to run Baseline for Entire Network