| Author |
Message |
christopher
Guest
|
 Posted:
Wed Jan 12, 2005 5:11 pm Post subject:
„MOM agent heartbeat failure“ – rule isn’t working |
|
|
I created two different Custom Computer Groups with two appropriate Custom
Rule Groups (CG1 is associated to RG1, CG2 is associated to RG2).
I copied the “MOM agent heartbeat failure“–Rule from the Operations Manager
2005-MP into each of these Rule groups. For ensuring the created rules are
working properly, I disabled the original “MOM agent heartbeat failure“–Rule
in the MOM2005 Management Pack.
Afterwards, I shut down a server located in CG1. I got a correct “Service
unavailable” message in the operator console and the response (mail to
several operators) worked correctly too, raised by the Rule in RG1.
Then I shut down a server located in CG2. The alert and the response came
too, but caused by the SAME rule, the one in RG1! If I disable this Rule,
nothing happens if I repeat the procedure. No failure in the OpConsole, no
message, nothing!
Everything is configured properly. I assume there is no configuration
mistake in the CG or RG, all other rules in the RG2 (service monitoring,
etc.) are working. By the way, the “original” MOM agent heartbeat
failure–Rule in the MOM2005-MP works fine…
Any suggestions for determining this issue? Thanks for your help! |
|
| Back to top |
|
 |
Trevor
Guest
|
| Posted:
Wed Jan 12, 2005 5:15 pm Post subject:
RE: „MOM agent heartbeat failure “ – rule isn’t work |
|
|
Hi there,
The MOM heartbeat failure rule needs to be sent to the all the management
servers in your MOM group, and not to the agent. Have you checked this is
the case?
Trevor
"christopher" wrote:
| Quote: | I created two different Custom Computer Groups with two appropriate Custom
Rule Groups (CG1 is associated to RG1, CG2 is associated to RG2).
I copied the “MOM agent heartbeat failure“–Rule from the Operations Manager
2005-MP into each of these Rule groups. For ensuring the created rules are
working properly, I disabled the original “MOM agent heartbeat failure“–Rule
in the MOM2005 Management Pack.
Afterwards, I shut down a server located in CG1. I got a correct “Service
unavailable” message in the operator console and the response (mail to
several operators) worked correctly too, raised by the Rule in RG1.
Then I shut down a server located in CG2. The alert and the response came
too, but caused by the SAME rule, the one in RG1! If I disable this Rule,
nothing happens if I repeat the procedure. No failure in the OpConsole, no
message, nothing!
Everything is configured properly. I assume there is no configuration
mistake in the CG or RG, all other rules in the RG2 (service monitoring,
etc.) are working. By the way, the “original” MOM agent heartbeat
failure–Rule in the MOM2005-MP works fine…
Any suggestions for determining this issue? Thanks for your help! |
|
|
| Back to top |
|
|
christopher
Guest
|
| Posted:
Wed Jan 12, 2005 8:41 pm Post subject:
RE: „MOM agent heartbeat failure “ – rule isn’t work |
|
|
Thanks for your answer...
For my better understanding: you mean I have to join the management server
in both groups? But this would signify that I get the message twice, one for
each CG/RG. Right? This wouldn't be a solution.
The problem is that those groups are system priority groups . Group1 for all
critical systems, Group2 for all "non-critical". The group membership defines
the type of response. With this configuration, if there's an error on an
non-critical system, messages are caused anyway, without relation to their
priority. Right?
"Trevor" wrote:
| Quote: | Hi there,
The MOM heartbeat failure rule needs to be sent to the all the management
servers in your MOM group, and not to the agent. Have you checked this is
the case?
Trevor
"christopher" wrote:
I created two different Custom Computer Groups with two appropriate Custom
Rule Groups (CG1 is associated to RG1, CG2 is associated to RG2).
I copied the “MOM agent heartbeat failure“–Rule from the Operations Manager
2005-MP into each of these Rule groups. For ensuring the created rules are
working properly, I disabled the original “MOM agent heartbeat failure“–Rule
in the MOM2005 Management Pack.
Afterwards, I shut down a server located in CG1. I got a correct “Service
unavailable” message in the operator console and the response (mail to
several operators) worked correctly too, raised by the Rule in RG1.
Then I shut down a server located in CG2. The alert and the response came
too, but caused by the SAME rule, the one in RG1! If I disable this Rule,
nothing happens if I repeat the procedure. No failure in the OpConsole, no
message, nothing!
Everything is configured properly. I assume there is no configuration
mistake in the CG or RG, all other rules in the RG2 (service monitoring,
etc.) are working. By the way, the “original” MOM agent heartbeat
failure–Rule in the MOM2005-MP works fine…
Any suggestions for determining this issue? Thanks for your help! |
|
|
| Back to top |
|
|
Colin (615498)
Guest
|
| Posted:
Thu Jan 13, 2005 5:59 am Post subject:
Re: "MOM agent heartbeat failure" - rule isn't working prope |
|
|
Or you could use the original rule and create new alert rules for each rule
group.
"christopher" <christopher@discussions.microsoft.com> wrote in message
news:BED8AA72-5748-48D8-8F3F-4CF40D7C25D5@microsoft.com...
Thanks for your answer...
For my better understanding: you mean I have to join the management server
in both groups? But this would signify that I get the message twice, one
for
each CG/RG. Right? This wouldn't be a solution.
The problem is that those groups are system priority groups . Group1 for all
critical systems, Group2 for all "non-critical". The group membership
defines
the type of response. With this configuration, if there's an error on an
non-critical system, messages are caused anyway, without relation to their
priority. Right?
"Trevor" wrote:
| Quote: | Hi there,
The MOM heartbeat failure rule needs to be sent to the all the management
servers in your MOM group, and not to the agent. Have you checked this is
the case?
Trevor
"christopher" wrote:
I created two different Custom Computer Groups with two appropriate
Custom
Rule Groups (CG1 is associated to RG1, CG2 is associated to RG2).
I copied the "MOM agent heartbeat failure"-Rule from the Operations
Manager
2005-MP into each of these Rule groups. For ensuring the created rules
are
working properly, I disabled the original "MOM agent heartbeat failure"-Rule
in the MOM2005 Management Pack.
Afterwards, I shut down a server located in CG1. I got a correct
"Service
unavailable" message in the operator console and the response (mail to
several operators) worked correctly too, raised by the Rule in RG1.
Then I shut down a server located in CG2. The alert and the response
came
too, but caused by the SAME rule, the one in RG1! If I disable this
Rule,
nothing happens if I repeat the procedure. No failure in the OpConsole,
no
message, nothing!
Everything is configured properly. I assume there is no configuration
mistake in the CG or RG, all other rules in the RG2 (service monitoring,
etc.) are working. By the way, the "original" MOM agent heartbeat
failure-Rule in the MOM2005-MP works fine.
Any suggestions for determining this issue? Thanks for your help! |
|
|
| Back to top |
|
|
christopher
Guest
|
| Posted:
Thu Jan 13, 2005 3:37 pm Post subject:
Re: "MOM agent heartbeat failure" - rule isn't working prope |
|
|
hmm, this would be an option too... haven't minded that yet.. i'll have to
check that. thanks for your help...
"Colin (615498)" wrote:
| Quote: | Or you could use the original rule and create new alert rules for each rule
group.
"christopher" <christopher@discussions.microsoft.com> wrote in message
news:BED8AA72-5748-48D8-8F3F-4CF40D7C25D5@microsoft.com...
Thanks for your answer...
For my better understanding: you mean I have to join the management server
in both groups? But this would signify that I get the message twice, one
for
each CG/RG. Right? This wouldn't be a solution.
The problem is that those groups are system priority groups . Group1 for all
critical systems, Group2 for all "non-critical". The group membership
defines
the type of response. With this configuration, if there's an error on an
non-critical system, messages are caused anyway, without relation to their
priority. Right?
"Trevor" wrote:
Hi there,
The MOM heartbeat failure rule needs to be sent to the all the management
servers in your MOM group, and not to the agent. Have you checked this is
the case?
Trevor
"christopher" wrote:
I created two different Custom Computer Groups with two appropriate
Custom
Rule Groups (CG1 is associated to RG1, CG2 is associated to RG2).
I copied the "MOM agent heartbeat failure"-Rule from the Operations
Manager
2005-MP into each of these Rule groups. For ensuring the created rules
are
working properly, I disabled the original "MOM agent heartbeat failure"-Rule
in the MOM2005 Management Pack.
Afterwards, I shut down a server located in CG1. I got a correct
"Service
unavailable" message in the operator console and the response (mail to
several operators) worked correctly too, raised by the Rule in RG1.
Then I shut down a server located in CG2. The alert and the response
came
too, but caused by the SAME rule, the one in RG1! If I disable this
Rule,
nothing happens if I repeat the procedure. No failure in the OpConsole,
no
message, nothing!
Everything is configured properly. I assume there is no configuration
mistake in the CG or RG, all other rules in the RG2 (service monitoring,
etc.) are working. By the way, the "original" MOM agent heartbeat
failure-Rule in the MOM2005-MP works fine.
Any suggestions for determining this issue? Thanks for your help!
|
|
|
| Back to top |
|
|
christopher
Guest
|
| Posted:
Thu Jan 13, 2005 7:17 pm Post subject:
Re: "MOM agent heartbeat failure" - rule isn't working prope |
|
|
hmm, this isn't working too...
i reactivated the original heartbeat rule and created two alert rules, one
in each rule group. the criterias are the eventID (21209) and the option
"generated by rule in its group only" (or something like that)...
I get the alerts in the OpsConsole, but i don't receive any email
notification - what am i doing wrong?
"christopher" wrote:
| Quote: | hmm, this would be an option too... haven't minded that yet.. i'll have to
check that. thanks for your help...
"Colin (615498)" wrote:
Or you could use the original rule and create new alert rules for each rule
group.
"christopher" <christopher@discussions.microsoft.com> wrote in message
news:BED8AA72-5748-48D8-8F3F-4CF40D7C25D5@microsoft.com...
Thanks for your answer...
For my better understanding: you mean I have to join the management server
in both groups? But this would signify that I get the message twice, one
for
each CG/RG. Right? This wouldn't be a solution.
The problem is that those groups are system priority groups . Group1 for all
critical systems, Group2 for all "non-critical". The group membership
defines
the type of response. With this configuration, if there's an error on an
non-critical system, messages are caused anyway, without relation to their
priority. Right?
"Trevor" wrote:
Hi there,
The MOM heartbeat failure rule needs to be sent to the all the management
servers in your MOM group, and not to the agent. Have you checked this is
the case?
Trevor
"christopher" wrote:
I created two different Custom Computer Groups with two appropriate
Custom
Rule Groups (CG1 is associated to RG1, CG2 is associated to RG2).
I copied the "MOM agent heartbeat failure"-Rule from the Operations
Manager
2005-MP into each of these Rule groups. For ensuring the created rules
are
working properly, I disabled the original "MOM agent heartbeat failure"-Rule
in the MOM2005 Management Pack.
Afterwards, I shut down a server located in CG1. I got a correct
"Service
unavailable" message in the operator console and the response (mail to
several operators) worked correctly too, raised by the Rule in RG1.
Then I shut down a server located in CG2. The alert and the response
came
too, but caused by the SAME rule, the one in RG1! If I disable this
Rule,
nothing happens if I repeat the procedure. No failure in the OpConsole,
no
message, nothing!
Everything is configured properly. I assume there is no configuration
mistake in the CG or RG, all other rules in the RG2 (service monitoring,
etc.) are working. By the way, the "original" MOM agent heartbeat
failure-Rule in the MOM2005-MP works fine.
Any suggestions for determining this issue? Thanks for your help!
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in