Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

alerts not functioning after upgrading to 10

We have at least one alert set that since upgrading to 10 are no longer activating.

The setups have not changed, I have verified the configs are valid, and I can test fire the alerts just fine and receive the messages. It acts like the part of NPM that monitors the stats isnt seeing the correct data.

The alerts in question detect % utilization on a backup T1 to alert us that the primary fiber line has gone down. when utilization hits 7%, it pages us to let us know data is flowing across the wire. when it drops below 3% it sends another alert to notify us that it has returned to an idle state. It worked fine for months prior to upgrading.

While writing this post, I did a little more research and ran some tests. I setup an alert to email when an interface goes down, and selected one that is currently down. after waiting a few minutes it is still not alerting us to an interface down condition that is present on the network summary page.

Any ideas where to check first?

Find more posts tagged with

Accepted answers

All comments

MarieB

Hi CameraMonkey--

Have you tried this:

Stop all Orion services.
Open the database manager and go to the nodes table.
Query the nodes table and perform a refresh. You will see all nodes you are monitoring listed.
Scroll to the right until you the column that is called Engine ID.
Change the options from Read-Only to Read-Write. Change the values in the Engine ID column to the same value in the nodes table.
After you have done so close the database manager and restart the services.

Let me know if this works for you.

cameramonkey

Im afraid I dont quite follow you in the second half of step 5.

Right now all nodes have a value of 1 in the Engine ID column. You say to change to the same value in the nodes table. Change the value(s) to what? can you be more specific?

KwameB

I'm having a similar problem, but in my case I created the alarms after the upgrade & they were working fine for a while then they just stopped all of a sudden.

Actually only the alarms that were based on bandwidth stopped, all the other alarms were working fine (Interface down, Node down etc.)

I re-created them from scratch & I left the old alarms active & enabled the newly re-created "clones" and only the new ones worked.

KwameB

Hey MarieB, I know your trying to help but i'm lost @ step #5 too

cameramonkey

I re-created them from scratch & I left the old alarms active & enabled the newly re-created "clones" and only the new ones worked.

I just did the same and that fixed the issue for my two critical alerts.

I would still like to fix the canned alerts that are already there. I do use quite a few of them as well, but I dont rely on them for notification. I REALLY REALLY dont want to have to recreate all of those alerts manually.