HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Critical [5] EMS Event Notification
Operating System - HP-UX
1826081
Members
3198
Online
109690
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
11-26-2004 02:20 PM
11-26-2004 02:20 PM
Critical [5] EMS Event Notification
Hi,
How to tackle this problem,
Nov 27 05:13:14 jhrsap1 EMS [2745]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_5_0_0.8.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 179896346 -r /storage/events/disks/default/0_5_0_0.8.0 -n 179896331 -a
It always occured at syslog.
Server info N4K , HPUX ver.11.0
Please help .....thanks in advance.
How to tackle this problem,
Nov 27 05:13:14 jhrsap1 EMS [2745]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_5_0_0.8.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 179896346 -r /storage/events/disks/default/0_5_0_0.8.0 -n 179896331 -a
It always occured at syslog.
Server info N4K , HPUX ver.11.0
Please help .....thanks in advance.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2004 04:04 PM
11-26-2004 04:04 PM
Re: Critical [5] EMS Event Notification
Hi,
Just run the command
/opt/resmon/bin/resdata -R 179896346 -r /storage/events/disks/default/0_5_0_0.8.0 -n 179896331 -a
and see what you get. The output you get will have a detailed description and a recommendation/solution.
-Sri
Just run the command
/opt/resmon/bin/resdata -R 179896346 -r /storage/events/disks/default/0_5_0_0.8.0 -n 179896331 -a
and see what you get. The output you get will have a detailed description and a recommendation/solution.
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2004 12:56 PM
11-27-2004 12:56 PM
Re: Critical [5] EMS Event Notification
If there is a real lun on lun 0 then you have a real problem.
I do suspect however that ioscan -fnC disk will show there is no actual lun0 presetnted to this system by your fiber card/disk array setup.
What happens when no lun is assigned and presented as lun0 is that your HP system picks up the disk array itself. It thinks its a disk but it really isn't.
Maybe you san admin can think of a way to keep that from happening. We stopped it merely by making sure one of the luns presented to each fiber card is lun0.
SEP
I do suspect however that ioscan -fnC disk will show there is no actual lun0 presetnted to this system by your fiber card/disk array setup.
What happens when no lun is assigned and presented as lun0 is that your HP system picks up the disk array itself. It thinks its a disk but it really isn't.
Maybe you san admin can think of a way to keep that from happening. We stopped it merely by making sure one of the luns presented to each fiber card is lun0.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2004 02:05 PM
11-27-2004 02:05 PM
Re: Critical [5] EMS Event Notification
That's not a fibre disk, that is a local SCSI attached disk and looks like an internal disk on the N4000.
Do an 'ioscan -fnC disk' and see if the disk at hardware path 0/5/0/0.8.0 shows NO_HW. If it does, then that is your problem.
If this disk was bad at one time in the past and has been replaced, then try the following:
# /etc/opt/resmon/lbin/set_fixed -n /storage/events/disks/default/0_5_0_0.8.0
That should reset the disk in EMS so that it is no longer shown as down. Then monitor your syslog and see if the even occurrs again. If it does, then you probably have a disk problem. If it doesn't then it was an old message that was just ocurring repeatedly because it was never reset within EMS.
Do an 'ioscan -fnC disk' and see if the disk at hardware path 0/5/0/0.8.0 shows NO_HW. If it does, then that is your problem.
If this disk was bad at one time in the past and has been replaced, then try the following:
# /etc/opt/resmon/lbin/set_fixed -n /storage/events/disks/default/0_5_0_0.8.0
That should reset the disk in EMS so that it is no longer shown as down. Then monitor your syslog and see if the even occurrs again. If it does, then you probably have a disk problem. If it doesn't then it was an old message that was just ocurring repeatedly because it was never reset within EMS.
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP