- Community Home
- >
- Servers and Operating Systems
- >
- Integrity Servers
- >
- Re: EMS When is a MAJOR_WARNING not a MAJOR_WARNIN...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2007 10:21 PM
тАО08-20-2007 10:21 PM
We have EMS 4.20 installed on all our servers together with ISEE A.03.95.057.
Last Sunday we had an incident where ISEE phoned home with a CPU cache error on one of our rx7640's. The problem was that EMS didn't notify us of this. The incident is logged as MAJOR_WARNING in the EMS log file and I have checked the EMS configuration where MAJOR_WARNINGS should be written to the syslog and emails sent. This is configured correctly. However neither of these things happenned.
Does anyone know of any additional criteria that can affect the decision on the severity of the call or is this an EMS error (bug) of some sort?
Additional info:
EMS text logging is set the INFORMATION level.
EMS configured using etc/opt/resmon/lbin/monconfig
Regards
Andrew Y
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 03:01 AM
тАО08-21-2007 03:01 AM
Re: EMS When is a MAJOR_WARNING not a MAJOR_WARNING
check your config in ems if there is notification if event => 4 (major warning). see http://docs.hp.com/en/5991-6760/ch03s03.html#bajdfcaj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 03:09 AM
тАО08-21-2007 03:09 AM
Re: EMS When is a MAJOR_WARNING not a MAJOR_WARNING
The current monitor configuration is:
1) Send events generated by all monitors
with severity >= MAJOR WARNING to SYSLOG
2) Send events generated by all monitors
with severity >= INFORMATION to TEXTLOG /var/opt/resmon/log/event.log
3) Send events generated by all monitors
with severity >= MAJOR WARNING to EMAIL root
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 03:26 AM
тАО08-21-2007 03:26 AM
Re: EMS When is a MAJOR_WARNING not a MAJOR_WARNING
i mean check the criteria for individual event. it could have overwritten the criteria for all events. what event did you get for this? you can see the event inside the file /var/opt/resmon/log/event.log
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 03:37 AM
тАО08-21-2007 03:37 AM
Re: EMS When is a MAJOR_WARNING not a MAJOR_WARNING
I assume your are referring to this:
>/system/events/cpu/cmc ... OK.
For /system/events/cpu/cmc/cache_errors:
Events >= 1 (INFORMATION) Goto TEXTLOG; file=/var/opt/resmon/log/event.log
Events >= 3 (MAJOR WARNING) Goto SYSLOG
Events >= 3 (MAJOR WARNING) Goto EMAIL; addr=root
Events >= 1 (INFORMATION) Goto TEXTLOG; file=/var/opt/resmon/log/rst.log
Client Configuration File: /var/stm/config/tools/monitor/rst_cmc_em.clcfg
Events >= 1 (INFORMATION) Goto TCP; host=localhost port=1402
Comment: RST Request
Client Configuration File: /var/stm/config/tools/monitor/rst_cmc_em.clcfg
Events >= ?? Goto TCP; host=localhost port=49176
Client Configuration File: /var/stm/config/tools/monitor/wbem_cmc_em.clcfg
There is no entry in :
/var/opt/resmon/log/event.log
But there is in:
Event data from monitor: /var/opt/resmon/log/rst.log
Event Time..........: Sun Aug 19 23:09:15 2007
Severity............: MAJORWARNING
Monitor.............: cmc_em
Event #.............: 100642
System..............: sovprod1.sovint.co.za
Regards
Andrew Y
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 03:50 AM
тАО08-21-2007 03:50 AM
Re: EMS When is a MAJOR_WARNING not a MAJOR_WARNING
Events >= 3 (MAJORWARNING) Goto TEXTLOG; file=/var/opt/resmon/log/event.log
So I believe, that's why it's not captured in the event.log file. As for the syslog, it should be captured. What is the oldest date in the syslog.log file? Have you also checked the OLDsyslog.log file? As for the mail notification,
Events >= 3 (MAJOR WARNING) Goto EMAIL; addr=root
Did you check the mail for root account?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 04:37 AM
тАО08-21-2007 04:37 AM
Re: EMS When is a MAJOR_WARNING not a MAJOR_WARNING
But there is the following:
Events >= 1 (INFORMATION) Goto TEXTLOG; file=/var/opt/resmon/log/event.log
which should cover it.
But since this wasn't working either perhaps there is an error in the config.
There was no mail sent to root either. The only entry is in the rst.log file.
Regards
Andrew Y
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 12:20 PM
тАО08-21-2007 12:20 PM
Re: EMS When is a MAJOR_WARNING not a MAJOR_WARNING
"JAGaf78710 cmc_em event 100642 generates 'major warning' for sin"
You might want to update ISEE to latest version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 06:15 PM
тАО08-21-2007 06:15 PM
Re: EMS When is a MAJOR_WARNING not a MAJOR_WARNING
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 10:22 PM