superfly · Senior Network Engineer · ✭✭✭✭✭

Do you have NCM? If so, try running an "Update Inventory" job on these UPS's.

Just go into Manage Nodes. Tick the nodes you want to change and then click on Edit Properties. Once in scroll down to Polling Method and tick the box. Now just fill in the details as required and all the nodes you selected will be updated with the new info.

Yes you do but without it you can still receive the syslogs and display them. See details it the link I posted.

This should be fine. Just boot the server (if necessary) after the database server has been rebooted.

I assume the device will log a syslog for this. You could just for now alert on the syslog message if the out-of-the-box alert doesn't work.

You have to write a custom widget. I've posted details in this thread. thwack.solarwinds.com/.../

For me the syslog widget disappeared already on 2019.4 but see this thread on how you can display it again. https://thwack.solarwinds.com/product-forums/network-performance-monitor-npm/f/forum/84621/dashboard-query-for-syslog/

Are you actually talking about the real time change detection emails? If so, you have to fill the details out in this section.

Have you tried to create a new NCM config job and see if it works?

I have the same issue. I'm not sure how to fix it and can not find a report to show the H/W version. You could log a support ticket to get the widget fixed.

Go to Alerts & Activity and select Events. Then filter on Node Added.

Hi Ben. I had one of mine go faulty. The battery started expanding and trying to break out of the case. So I threw it out. Just thought you should know.

I thought I'd test a domain account and it too fails for me. Maybe the latest upgrade broke it? I only ever use a local account as atlas works a lot faster. Maybe this will need a ticket logged with support to get sorted.

That sounds like you don't have the correct credentials. Try creating a new credential on the vsphere and use that to connect with.

Create a brand new user and see how you go.

Try running config wizard again. If still no luck, contact support.

So you have deleted the node out of Solarwinds. Then when you add it back in, what does it fail on? Does it pass this test?

I just created a new local Solarwinds admin account making sure it had rights for Network Atlas. I then jumped onto the Solarwinds server and logged onto Network Atlas with this new account. All worked sweet. Maybe try that. If that doesn't work, try a reboot.

Does this help? https://support.solarwinds.com/SuccessCenter/s/article/Send-Orion-alert-emails-using-Office-365-and-Outlook?language=en_US

Ah I see. Yeah they don't show as they are not applied to the node but rather are applied the object like drive, physical memory etc or to the application. You can see in the alert which objects it will apply to by clicking the 'show list' but that's all I can see. I don't know how to make these show on the node details…

Great to hear you've got it sorted! Nicely done

If you click on "show list" do you see the 3 objects ok? If so, are the other 2 muted maybe?

You are correct that it is only the probe that needs to be able to communicate the remote network. It then sends this data back to Solarwinds. https://documentation.solarwinds.com/en/success_center/npm/content/npm-create-a-probe.htm Is there a firewall between Solarwinds and the probe? And are you 100% sure the probe can…

As part of your download config job, you just tick the following boxes which will send an email to show you all the configs that are not the same. I do the same thing. I first download the startup configs. Then I run a second job that downloads the running configs and compares it to the most recent config that was download…

I don't know of a report but you can add the widget "All Alerts this Object can trigger" to your node details page. It will list out all the alerts that can trigger for the node you have selected.

I use this in my alerts to show days hours minutes <b>Downtime:</b> ${SQL:Select '${N=Alerting;M=Downtime}'/1440} Days ${SQL: Select '${N=Alerting;M=Downtime}'%1440/60} Hours ${SQL: Select '${N=Alerting;M=Downtime}'%1440%60;} Minutes' Hope that helps.

Yes there will be a small outage as the services need to be restarted. Here's the info documentation.solarwinds.com/.../core-downloading-the-solarwinds-mib-database-sw3581.htm

I wouldn't bother monitoring unrouted VLAN's. In fact, I wouldn't even monitor VLAN's. I would monitor only uplink interfaces and interfaces to important devices like servers.

If you go to Manage Nodes, select the Node and click on Edit Properties, is this box ticked and details filled out and tested?

Yeah I've done the same thing. I just show serial number in a separate widget.