HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- EMS Error message in syslog with EMC SAN
HPE EVA Storage
1831225
Members
2778
Online
110021
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
01-23-2003 08:20 AM
01-23-2003 08:20 AM
EMS Error message in syslog with EMC SAN
I'm receiving the following errors in my syslog, and I'd like to disable EMS from even monitoring the Clariion disks.
Jan 22 18:40:35 hpsan01 EMS [2153]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_4_0_0.97.4.19.0.0.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 141099084 -r /storage/events/disks/default/0_4_0_0.97.4.19.0.0.0 -n 141099063 -a
Jan 22 18:40:35 hpsan01 EMS [2153]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_7_0_0.97.4.19.0.0.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 141099087 -r /storage/events/disks/default/0_7_0_0.97.4.19.0.0.0 -n 141099064 -a
Any ideas?
Jan 22 18:40:35 hpsan01 EMS [2153]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_4_0_0.97.4.19.0.0.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 141099084 -r /storage/events/disks/default/0_4_0_0.97.4.19.0.0.0 -n 141099063 -a
Jan 22 18:40:35 hpsan01 EMS [2153]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_7_0_0.97.4.19.0.0.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 141099087 -r /storage/events/disks/default/0_7_0_0.97.4.19.0.0.0 -n 141099064 -a
Any ideas?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2003 08:51 AM
01-23-2003 08:51 AM
Re: EMS Error message in syslog with EMC SAN
Use 'monconfig' for setup/modify event monitoring system.
Please execute these commands listed in the event to get more details on what happened
Eugeny
Please execute these commands listed in the event to get more details on what happened
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2003 04:25 AM
01-24-2003 04:25 AM
Re: EMS Error message in syslog with EMC SAN
Hi,
This is a problem with CommandView.
You have to upgrade to CommandView 1.06 which solved this problem.
Brgds
Olivier
This is a problem with CommandView.
You have to upgrade to CommandView 1.06 which solved this problem.
Brgds
Olivier
Olivier JAVAUX
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP