Some alerts get caught by eventaction and some don't ...
Trying to find out why certain type of alerts get cought by eventaction and some don't.
Got all kinds of voltage errors, warnings and such and those get all the way to our Tivoli gateway.
I've disable a CPU on one of our box and i see it in the console but it never gets shipped to our Tivoli network.
Now i've enable ALL the errors in the Action i've setup so i would get everything sent out. I'm starting to run out of places to look.
If somebody has a clue or something (even documentation wise) i'm all for it.
Thanks for you time.
Eric
# 1
Hi Eberthiaume,
Have you tried looking at the EventAction log on your SunMC Server?
/var/opt/SUNWsymon/log/EventActionHistory.log
(i.e. watch it with "ctail -f" to see it scroll by as you trigger test alarms)
It shows all alarms detected, and what was done about each one. If it says something like "Actions taken: None" for a test alarm, then something in your filtering is forcing EventAciton to ignore it.
Halcyon has pre-sales support for this type of thing, and would be happy to help you out (info@HalcyonInc.com).
Regards,
Mike.Kirk@HalcyonInc.com
http://www.HalcyonInc.com
# 3
Hi eberthiaume,
> Already checked the log file ... its no where to be
> found and that what is bothering me .. pretty strange
> actually cause i can't see any filters on and i've
> setup the Action so it takes all event from all the
> servers every time and repeat each 10 minutes ....
Do you mean the log doesn't exist at all, or that you never see your alarms in it?
I'm guessing the log is there, but when you trigger alarms for some hosts they appear as an entry in the log (and go to Tivoli)... but alarms from other systems never make it to the log (and never get sent to Tivoli).
Here's a simple test:
1) Trigger an alarm on an Agent that you know alarms don't appear for in EventActionHistory.log
2) After you trigger the alarm and see it light up in the Console, switch to the "Alarms" tab for that Agent.
3) Look for your alarm in that tab (press the refresh button a couple times if it doesn't show up in a few seconds)
If you see your alarm in the Alarms tab... but you don't see it in EventActionHistory.log within about 2 minutes.. then something is wrong (or misconfigured) with EventAction. If you _don't_ see your alarm in the Alarms tab... then it's never making it into your SunMC Server's database... and there's something wrong with your Agent or Server. Go repeat steps 1-3 for an Agent that you've seen alarms from recently and confirm that if the alarm makes it to the Alarms tab it shows up in EventActionHistory.log soon after.
EventAction feeds off of the SunMC Oracle database.... if alarms don't make it to the database they will never make it to Tivoli either.
Based on what you find in the test steps you can decide if you should contact Sun support or Halcyon support.
Regards,
Mike.Kirk@HalcyonInc.com
http://www.HalcyonInc.com
# 4
I think Aronek assumed you are using PrimeAlert EventAction (a 3rd party product) - when it's possible that you just accidentally concatenated the two words "event action". All his suggestions pertain to that specific product. (If you are having evaluation problems with that product - feel free to send an e-mail to experts _at_ halcyoninc dot com.)
Are you working with the Sun MC Java Console's attribute editor on each alarmable field, setting up individual actions that call a script that send the alarm to Tivoli? That'd be a different problem. Can you tell us specifically what field you are right clicking on to get the attribute editor? Also run the following command: "/opt/SUNWsymon/util/bin/ctail -f /var/opt/SUNWsymon/log/agentStatus.log" ... when you re-create the problem. A line will appear that contains the problem details including the alarm state. Post that here. (Sorry, I don't have a system on which I can disable a cpu at the moment..)
