superfly · Senior Network Engineer · ✭✭✭✭✭

Does the 2901 that's not polling correctly pass the SNMP test? If yes, then check if IOS is the same on both 2901's. If not, update the one that is not polling correctly.

^^ this is what I do for my slow link devices.

That's what it sounds like to me. If you go to "Alerts & Activity" and select Syslog and you see nothing - that will mean that nothing is sending syslogs to solarwinds.

There are 2 reports available. "Devices Sending Syslog or SNMP-Traps to Log Analyzer" and "Devices Sending Syslog or SNMP-Traps to Orion"

I have mine set to CISCO-ENTITY-SENSOR-MIB. But just the other day I had to switch some of my 9300 switches to CISCO-ENVMON-MIB so NPM could pick up power issue.

I don't have Log Analyzer so in my version the rules are already in place by default.

What version Solarwinds are running? Trapviewer no longer works on the new version. You can see the traps by going to Alerts & Activity and click on Traps. But for full functionality you will need Log Analyzer.

Does the chromebox support SNMP? if yes, then look through the available OID's to see if you can find ones that suit your requirements.

Unmanaged devices do not send alerts. Are you sure it's the unmanaged device sending you the alert in question?

You just need to put in details for a SMTP server that you can use to send the email. Check with your mail administrator for the details of the server and whether it needs authentication or not. Here are some instructions documentation.solarwinds.com/.../core-adding-an-smtp-server-sw860.htm

Use Orion Maps. Here are page to help you get started www.solarwinds.com/.../orion-maps

Solarwinds stopped developing NTM some years ago. Network Atlas has been superceded by Orion Maps. So use Orion Maps

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.