Ping failure after heartbeat failure, no alert??
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Ping failure after heartbeat failure, no alert??

 
Post new topic   Reply to topic    Windows Server Forum Index -> MOM
Author Message
Martijn C
Guest
Posted: Wed Oct 26, 2005 4:51 pm    Post subject: Ping failure after heartbeat failure, no alert?? Reply with quote
Dear ng,

I am testing the scenario that on a machine the agent fails first and
later the machine crashes. When the agent is stopped, it checks for
heartbeats and after that pings a few times (as set in the server)
after which it generates a "MOM Agent heartbeat failure" alert. When I
then disconnect the test machine I do not seem to get a ping failure
message or an event added to the alert.

Question: Is it true that after the heartbeat failure message no 21209
message is sent when the server crashes later??

If this is the case I should update my SLA (change "ping response" to
"mom agent response" as definition of a running server) or write a
script to ping agents with a heartbeat failure to see if they are still
responding to ping.

Any explanations / suggestions are welcome.

Regards,
Martijn.
Back to top
Martijn C
Guest
Posted: Wed Oct 26, 2005 4:51 pm    Post subject: Re: Ping failure after heartbeat failure, no alert?? Reply with quote
Hi Daniel,

I've checked that of course, and no (as stated in my first post).

I have seen a ping failure event grouped on a heartbeat faulure alert
but that was in a situation where the connection was established after
the first heartbeat alert but it wasn't resolved before the ping
failure.

Could you please make sure that the 21209 event will be sent in my
scenario? In that case I can report a bug...

Regards,
Martijn.
Back to top
Daniel Lai [MVP-Managemen
Guest
Posted: Wed Oct 26, 2005 4:51 pm    Post subject: Re: Ping failure after heartbeat failure, no alert?? Reply with quote
Hello,

Thank you for your posting!

It may casue the alerts are grouped to one. Please check the alert in
Operator Console.

If you have any questions, please feel to let me know. I am glad to be of
assistance.


--
Daniel Lai
Microsoft MVP Program Top Contributor
Windows Server-Management Infrastructure
Microsoft Management Solution Consultant
http://msmvps.com/daniel

"Martijn C" <crabbendam@hotmail.com> wrote in message
news:1130339684.353078.247250@g43g2000cwa.googlegroups.com...
Quote:
Dear ng,

I am testing the scenario that on a machine the agent fails first and
later the machine crashes. When the agent is stopped, it checks for
heartbeats and after that pings a few times (as set in the server)
after which it generates a "MOM Agent heartbeat failure" alert. When I
then disconnect the test machine I do not seem to get a ping failure
message or an event added to the alert.

Question: Is it true that after the heartbeat failure message no 21209
message is sent when the server crashes later??

If this is the case I should update my SLA (change "ping response" to
"mom agent response" as definition of a running server) or write a
script to ping agents with a heartbeat failure to see if they are still
responding to ping.

Any explanations / suggestions are welcome.

Regards,
Martijn.
Back to top
davidtyra@hotmail.com
Guest
Posted: Wed Oct 26, 2005 8:51 pm    Post subject: Re: Ping failure after heartbeat failure, no alert?? Reply with quote
Martijn,

We have seen the exact same behavior. The heartbeat failure rule
"Microsoft Operations Manager\Operations Manager 2005\Server\MOM Agent
heartbeat failure" lumps the following four events together: 21210,
21209, 21284, 21285. So, if you get a 21284 (Agent service did not send
heartbeat, but computer responded to ping) and subsequently get a 21209
(Computer did not respond to ping), you will get alerted on the 21284
but not on the 21209 due to alert suppression. We decided to live with
that behavior but I would think you could redo the rules so that the
events are not lumped together.

Regards,

David Tyra
Back to top
Mark Luxton
Guest
Posted: Tue Nov 08, 2005 5:51 pm    Post subject: RE: Ping failure after heartbeat failure, no alert?? Reply with quote
Martijn,

I was getting a similar problem and Microsoft suggested going to SP1 which
wasn't an option at that time. I found that removing the 'Parameter 6 = 1'
string from the properties of the rule 'MOM Agent Heartbeat Failure' fixed
our problem. Leave any other Parmeters in there.

Microsoft said this was not an endorsed solution however. Let me know how
you get on....

Mark

"Martijn C" wrote:

Quote:
Dear ng,

I am testing the scenario that on a machine the agent fails first and
later the machine crashes. When the agent is stopped, it checks for
heartbeats and after that pings a few times (as set in the server)
after which it generates a "MOM Agent heartbeat failure" alert. When I
then disconnect the test machine I do not seem to get a ping failure
message or an event added to the alert.

Question: Is it true that after the heartbeat failure message no 21209
message is sent when the server crashes later??

If this is the case I should update my SLA (change "ping response" to
"mom agent response" as definition of a running server) or write a
script to ping agents with a heartbeat failure to see if they are still
responding to ping.

Any explanations / suggestions are welcome.

Regards,
Martijn.

Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> MOM All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB