HPSIM 5.1 is randomly disabling monitoring of servers!!!

[EricP]

I notice after auto discovery runs (4:00 AM every day), some servers will be in a monitoring suspended status.

Even more weird, it will show a specific date and time that monitoring is suspended for (in one case this morning a server shows as "suspended until Sat, 4/21/2007, 5:00 AM).

Anyone know why this is happening and how to stop it?

[David Claypool]

Unless someone quickly comes along with information saying that, "Oh, yeah, I noticed the same thing happening, and after I sacrificed a small animal to the CMS then it went away..." my first inclination is that you may have found a new anomaly. It may be that there is something unique in your environment that's making it show up in yours but not in others, but bottom line, get this called in as a case so it can be duplicated and escalated to the developers...

[Matteo Creolini]

Sorry David, but unfortunately I'm not going to say what you expected...

I noticed the same behaviour with SIM 4.2 SP1 even if in my configuration automatic discovery task is disabled.
I have no idea of what is generating the problem but I found two times some servers in suspended state till a date in the future (and if I remember well is the same of EricP: Sat 4/21/2007...) and the hw status icons did not show the maintenace status but a wanderful "ok"; so, no way to know that the server is suspended until you expect an alert that does not come!

If you discover something let us know! Thanks

[David Claypool]

Matteo and Eric: I know I have never heard of this problem and don't believe it has been posted about here before. Therefore, it's not something anyone knows about or is working to fix. Get it called in so someone can get to work.

[EricP]

Well we've just been going through the list of "disabled systems" (which by the way is a bad name -- should be "suspended systems") each morning, and removing any that shouldn't be there.

When we get time, we'll call it in. I can imagine how long that call will be though.

[David Claypool]

When you make the call and it goes through the prompts, say out loud the words "Insight Manager" and it will relay you to the correct team without delay.

[freebird (-.-)]

Ha!!!!!!!!!
Thats all I have to say about that.

[Jimmy Rueedi]

First, I thougt " they are catching the same issue we had.." but after reading all, I've seen, that it probably has nothing to do with the hardware status piolling task.

That was the point at our site:
we created two hardware status polling tasks for servers; one for working hours and one for out of office hours.
Each morning, the office hours interval "forgot" to start...

Where do you "re- enable" the systems, which are disabled?

Regards
Jimmy

[EricP]

Jimmy:

Options/System Properties/ suspend or resume monitoring

[Jimmy Rueedi]

Well, it was just for clarifying for me to understan, what you mean, when you say, "re- enabling" monitoring.

Sorry, actually I'm stumped about this... :-S

we have disabled auto discovery because we only monitor servers and network equipment and they send a SNMP trap when they are booting, so new devices are added to our SIM by automatically identifiying when a trap is received.

Regards
Jimmy

[HP Systems Insight]

Thought I'd chime in with my experience on the subject and I'll try and keep it short. (Running SIM 5.0 back then)

We were having a very similar issue although before I realized that systems were randomly disabling what I had figured out was that some servers (we have over 500 we monitor) were NOT sending alert e-mails - this we knew because WE DO USE CIMNOTIFY as well as SIM and WE LIKE IT THIS WAY (so don't give me the "you don't need both" junk!).

Anyway, I was pulling my hair out trying to figure out what was going on when I starting narrowing in on the problem and for the first time I did see this random disabling problem.

OK, so I wrote a custom script that would alert us whenever a system was disabled (very useful now because there is a group of us that monitor our SIM shared e-mail box).

But, at the same time I started remembering that on the previous PM that we had disabled a huge number of servers and after the PM we re-enabled them.

Long story short I figured out that something had not quite worked right when we tried to re-enable them (although from the SIM view they were NOT showing as disabled) I figured something in the database got messed up and I went and manually re-enabled all devices (not all at once but small numbers at a time) and we've been fine since!

MJ

[john mills_3]

any idea then on how to "re-enable" systems
that are currently disabled when the option
to re-enable is either not there or greyed
out !!

[dhaskins]

Has this issue been resolved?

We are also seeing this issue on our SIM 5.1 installation.

SIM is randomly suspending anywhere from two to five servers a week from monitoring.

Does SIM 5.1 SP1 address this issue?

Any help in this matter would be appreciated.



Donald

[Mikael Rönnbäck]

I'm still seeing this every now and then for a few hundred of our servers, even in SIM 5.1 SP1

[mark q]

I still see this with my insight manager installation, this morning I had over 1700 servers and now I'm down to 1550.. at random..

any word on this being fixed? I'm at the latest version of insight manager.

[Gene Nordahl]

I'm seeing this now too. I found by investigating why so many systems were being skipped during the Daily ID task.

It's been over a year (according to this string) anybody have a fix yet? Or a way to do a collection of disabled systems when HW status isn't disabled?

[J Ruffolo]

I am on v5.2.0.1 and I am still getting this random disabling of servers. My additional problem since moving over to the SQL personal edition is, I can no longer discover new systems. This is currently being pursued by HP.

[Michael Mercogliano]

Does anyone know if there is a solution to monitoring being randomly disabled. The ones I fixed today look as if they were set to be disabled for about a month. I'm on HP SIM build: C.05.03.00.00.

-Mike

[Scott_341]

I've started seeing this same problem on a couple of my servers after I upgraded to 5.3 last week. It seems to have something to do with the Daily System Identification task running as anytime I run that task against either of those servers, they disable. I've disabled that task for now and the servers are staying enabled.

[Michael Mercogliano]

Is there a solution to this issue? I'm still having the problem of random servers being suspended. I'm running:

Central management server:
Hostname: ENTSIMP1.chop.edu
Operating system: Windows 2003
Version: Systems Insight Manager 5.3 with SP1 - Windows
Build version: C.05.03.01.00
Build date: 2009-03-28 21:04
Patches: HOTFIX53_003.jar Wed, 8/19/2009, 2:20 PM EDT
HOTFIX53_004.jar Wed,8/19/2009, 2:20 PM EDT
HOTFIX53_005.jar Wed,8/19/2009, 2:20 PM EDT
HOTFIX53_006.jar Wed,8/19/2009, 2:20 PM EDT
HOTFIX53_007.jar Wed,8/19/2009, 2:20 PM EDT
HOTFIX53_008.jar Fri,10/16/2009, 5:18 PM EDT