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
Store

How to suppress alert for a routine server reboot

Hi, whenever someone in the team does a routine server reboot and the inevitable alert is sent out there is often a little confusion (or panic!) about what happened.

How do you correctly suppress an alert for a routine, expected, manual server reboot. Its a bit tricky because the main priority is that the alert works for unexpected instances and its too awkward to disable the alert before an expected reboot.

Any help?

Thanks

Find more posts tagged with

Accepted answers

Questionario

For our part we have set the alert to only trigger after the node has been down for more than 3minutes. During that time any system that reboots will be pingable again unless a time-consuming update is being performed right after rebooting which allows no network connections...

seems to work well for us so far though

All comments

njoylif

try [procedural] having the member performing maintenance unmanage the object prior to work, then re-managing after.

petertee

Thanks for the suggestion but Im looking for something alot more automated than that

gbutler

Using advanced alert there are two options that I'm aware of. You can schedule the alert to block out a time period or you can schedule the action to not go off during a block of time.

If you have several actions in your trigger and want some to go off but not others the second option would be the ticket.

In either case you will need to have a specific alert for those systems with reboot schedules.

Questionario

seems to work well for us so far though

jnielson

Perhaps you could write a VB Script for rebooting the server...

The script would update the Nodes table directly - and set the "unmanaged start" and "stop" times, and then reboot the server.

You'd set the script up on each server, and customize it for the node name or node id (depending on your SQL chops), and instruct your staff to reboot using that script.

Once the vbscript is written, you could even use it as a scheduled task for automated weekly/monthly reboots.

anachronism

We only raise alerts if the DeviceStatus (a custom field) is set to Monitored.Our process is that during planned maintenance the person performing the work sets the DeviceStatus to their initials and the ticket number for the work. We can also put in values like "Commissioning" which raises email alerts to a different team.

You could do something similar whereby a scheduled task sets the field to switch it in and out of maintenance (you could go a step further and use the ical format to allow maintenance periods to be scheduled using a calendar app ).

mcbridea

If the reboot is always at the same time you can exclude that period from the alert.

petertee

Thanks, thats a great solution. Simple and effective!

Thanks to all.

ecklerwr1

Apparently version 10 is going to have a standalone utility that may allow this soon:

Per Brandon:

All,

As a standalone component with 10.0 we will also put out a stand alone tool to schedule unmanaging nodes or interfaces.

What you can do with the Schedule Unmanage Utility:

Create a task to unmanage Orion nodes and interfaces for a custom period of time. An unmanage task can be scheduled to run on a schedule.
Edit existing tasks to add or delete Orion objects or adjust the time period.
Why use this utility? If you have routine scheduled maintenance that happens once a week, you can have an unmanage task that runs at the same time. Selected Orion objects will be unmanaged and you won't receive alerts from them during this period of maintenance.

cwitthoft

I to am looking for a good way to supress these alerts. I have followed a few posts and tried the Unamanged Utility from Solar Winds. It works well for certain admin tasks but not the reboot alerts I recieve when I reboot my Orion server itself. I ended up Creating an IP Security Policy that blocks traffic from my Orion server to our internal mail server. When i'm rebooting the orion server for maintenance I open my desktop shortcut to the IP security policy and click assign, after the server reboots I right click and say unassign. Works good for me. But if a new fix comes along keep me posted

cfizz34

New way to do it....

https://www.solarwinds.com/documentation/en/flarehelp/orionplatform/content/core-setting-device-management-states-sw2036.htm