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

Alerts when Orion server is rebooted

Is this something new with V7? Whenever I rebooted the server before (or restarted the engine) in V6.4 no alerts would be generated but now after upgrading to v7 I'll get alerts on close to 100 devices.

Find more posts tagged with

Accepted answers

All comments

Debbi

I have always had this happen, so much so that before I reboot I disable alerts. I am not on version 7 yet.

dominickv

I noticed the same issue and Im on 6.4, does anyone have an anwser or solution.

Dominick Vanacore
Senior Network Engineer

S|A|C Capital Advisors, LLC

Network_Guru

I've always had this issue. It is related to the number of devices/elements you are
polling, the max polling stats setting & if you have set the initial polling to create
a baseline, or wait for the baseline to be built ~15 min.

You could try increasing the max polls/sec. of turning on the instant baseline, but I
don't recommend this if you are monitoring more than a thousand elements(see admin dox).

I just make it a habit to disable all alerting before rebooting, and waiting 10 minutes
for polls to stabilize before re-enabling. Just click on the events tab, and watch/wait
for the down nodes to come back up & then re-enable alerting.

-=Cheers=-
NG

jonchill

I wondered why I got paged almost 60 times I had just rebooted the serverm, I did not have this problem under 6.4 but since moving to v7 I get this problem.

snowjay

Disabling the alerts is all fine and dandy if it's a manual reboot but if push patches to the server and it then gets automatically rebooted we get the alerts. Or as in the most recent case someone was doing maintenance on the server and clicked reboot by accident, well we had a whole group of people in the data center wondering what was going on. I have tuned my max polls/sec according to the documentation and the numbers have decreased but now I get between 40-50 instead of 90-100.

It's too bad it won't assume devices are up until it polls and discovers otherwise.

Network_Guru

I feel your pain snowjay. I have had the server re-booted at 1AM Saturday morning by the Windows
support team installing patches without my knowledge. Thankfully I only get 4 or 5 alerts
after a reboot, but it was a rude awakening to be sure!

-=Cheers=-
NG

BakerD

Just happen to come this topic searching for something else, but the way I fixed our alerts was to setup an Alert Supression. This is found if you go to edit an alert --> Alert Supression tab. I added my server that NPM is running on and said to suppress alerts if unknown or down or warning. I now only get 5 - 10 at most during a reboot, better than the 50 or more I use to get.

stoned26

I also had this problem in 7.1 and earlier. In 7.2 I have not had the problem. The devices instead of going to a down state and triggering the alerts go in to an unknown state until the poller catches up.

David S.

pancamo

This re-alerting problem is starting to be a big problem!

We have an issue(known msft bug) where the LSASS process takes over the CPU on the SW box... It's caused by TS'n into the SW box and logging out with the SW manager still open...

We'll when this happens (4-5 times a week), we have to restart the solarwinds service. This is causing all the alerts for down system to be resent.

Our network/system guys are about to have a cow over this because they don't know if the alert is real or just a re-alert.

Workarounds anyone?

quote:Originally posted by stoned26

I also had this problem in 7.1 and earlier. In 7.2 I have not had the problem. The devices instead of going to a down state and triggering the alerts go in to an unknown state until the poller catches up.

David S.

Network_Guru

The LSASS process runaway issue is a BIG problem for me as well.
I've found that using the System Manager "gui" style buttons in the right pane to configure the alerts, causes the System Manager app to hang for about 10 seconds and then just close. Checking the taskmanager after this shows the LSASS.exe process hogging the CPU.
I've told everyone to only use the buttons on the top toolbar to configure System Manager, not the gui buttons, but.....

Using V7.5, I no longer get any false alerts when restarting the NetPerfMon service(I do have alert suppression on server startup setup as well), but this also messes up the polling stats for 15-30 minutes.

Lets hope the LSASS issue is fixed in upcoming V8, restarting the poller 2 or 3 times a week is not fun!

-=Cheers=-
NG

pancamo

Do you TS into the SW box to make changes? I'm starting to think that the problem is caused by 2 people TS'n into the box a the same time and sgtarting up System Mgr.

SW support has confirmed that this is a MSFT problem...

quote:Originally posted by Network_Guru

The LSASS process runaway issue is a BIG problem for me as well.
I've found that using the System Manager "gui" style buttons in the right pane to configure the alerts, causes the System Manager app to hang for about 10 seconds and then just close. Checking the taskmanager after this shows the LSASS.exe process hogging the CPU.
I've told everyone to only use the buttons on the top toolbar to configure System Manager, not the gui buttons, but.....

Using V7.5, I no longer get any false alerts when restarting the NetPerfMon service(I do have alert suppression on server startup setup as well), but this also messes up the polling stats for 15-30 minutes.

Lets hope the LSASS issue is fixed in upcoming V8, restarting the poller 2 or 3 times a week is not fun!

-=Cheers=-
NG

Network_Guru

I haven't noticed the LSASS problem since we upgraded the Orion server to Win2k3.
It seems like the RDP sessions are handled better in this rendition of Windows, although it may be that my team is no longer leaving the System Manager app open, after repeated threats from me.<grin>.

www.microsoft.com/.../1e839788-9a2b-4ba6-9929-82435a634cca.mspx

This latest version of RDP also allows one to access the console directly, which also resolves the LSASS issue:

Connect to the console session of a server using Remote Desktop for Administration:
www.microsoft.com/.../1e839788-9a2b-4ba6-9929-82435a634cca.mspx

Using the command line
1.
Open Command Prompt.

2.
Type:

mstsc /console.

-=Cheers=-
NG