swf5002

EDIT - I may be misunderstanding what you're looking for but here's my original message: Looks like as you enter nodes into NCM it runs a job nightly to update the information. "Refresh Suggested Dates" is a way to force it. If that's not working for you perhaps you have a bug - try opening a support case?

I got what I needed; during the creation of the table where you select what data to pull in I was choosing node rather than custom node poller.

I hadn't seen this thread before but I am also running Exchange 2016 and I have these counters reporting the same. It definitely seems like a bug to me with Exchange somehow. The number it's reporting if you look in perfmon is 2,147,483,655, which to me is suspiciously close to the maximum value of a 32-bit integer. I…

Did you try sharing a folder on the same server that NCM is installed on? That does not work. You also cannot use a local path unlike NCM config backups. This must be a separate server entirely. Also, how did you setup the share? Did you share the folder with authenticated users as modify and then secure the share using…

I have an open ticket with vmware regarding the CPU and memory problem that you're seeing. It's been open since FEBRUARY. We are still doing stupid basic troubleshooting and this guy is sending every response out for "consultation." It's despicable service. Rant over. Anyway, I have vcenter status as Up in my scenario, but…

Hey just FYI, don't do _OLD.sdf as the new name, you have to change the extension to .old. I guess solarwinds is just looking for an .sdf file type rather than the name itself. Learned that from calling support on a different issue.

So after having run inventory jobs, it's clear that solarwinds isn't pulling in (perhaps Dell and Juniper aren't providing on the correct OID) the VLAN information needed. I think I'm going to open a ticket with support to help verify what is needed to get this working correctly for vendors other than Cisco.

Figured this out here:

FWIW I had a similar problem with a Hitachi HDS system. I opened a ticket and after sending them some logs they were able to provide a patch.

So I marked this as answered but even after assigning the alert trigger to specifically down and the alert reset to specifically UP, I am still getting alerts that a node is in warning. I'm going to open a ticket.