- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Disk Event monitoring
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
Forums
Discussions
Discussions
Discussions
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
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-04-2008 11:34 PM
08-04-2008 11:34 PM
Disk Event monitoring
I am getting the following message for a couple of disks on an EMC CX700 bay. I am running HP-UX B.11.11 U 9000/800 on an rp5470. What is the cause and how to resolve the error?
Thanks
From root@idmdsprd.afdb.org Mon Aug 4 20:13:50 MET 2008
Received: (from root@localhost)
by idmdsprd.afdb.org (8.9.3 (PHNE_29774)/8.9.3) id UAA04165;
Mon, 4 Aug 2008 20:13:50 +0200 (METDST)
Date: Mon, 4 Aug 2008 20:13:50 +0200 (METDST)
Message-Id: <200808041813.UAA04165@idmdsprd.afdb.org>
To: root@idmdsprd.afdb.org
From: root@idmdsprd.afdb.org
Subject: idmdsprd: Event Monitor Notification
>------------ Event Monitoring Service Event Notification ------------<
Notification Time: Mon Aug 4 20:13:50 2008
idmdsprd sent Event Monitor notification information:
/storage/events/disks/default/0_10_0_0.4.1.0.0.0.3
is >= 3.
Its current value is SERIOUS(4).
Event data from monitor:
Event Time..........: Mon Aug 4 20:13:50 2008
Severity............: SERIOUS
Monitor.............: disk_em
Event #.............: 100472
System..............: idmdsprd
Summary:
Disk at hardware path 0/10/0/0.4.1.0.0.0.3 : Device connectivity or
hardware failure
Description of Error:
The device is not in a state where it can process requests. Manual
intervention is required.
Probable Cause / Recommended Action:
The device may have been powered off and may be being powered on.
Alternatively, one or both of the terminators on the SCSI bus may be
missing. Install the terminators in their proper locations at the ends of
the SCSI bus.
Alternatively, the SCSI cable may have become detached from the device.
Re-attach the cable.
Alternatively, the SCSI cable may have failed. Replace it.
Alternatively, the device may be in a state where it could not process
this, or any, request. Cycle power to the device.
Alternatively, there could be more than one device having the same address
on the SCSI bus. Make all the addresses on the SCSI bus unique.
Alternatively, the total length of all cable segments on the SCSI bus
exceeds 25 meters. Replace one or more cable segments until the total
length is less than this value.
Alternatively, if all of the above fail to correct the problem, the device
has experienced a hardware failure. Contact your HP support representative
to have the device checked.
Alternatively, if messages corresponding to this condition appear in the
log for more than one device on the SCSI bus, the device adapter may be in
a state from which it cannot extract itself. Perform a system shutdown,
cycle power to the computer and wait for it to reboot.
If, after reboot, messages corresponding to this condition continue to
appear in the log for this SCSI bus, contact your HP support
representative to have the adapter checked.
Additional Event Data:
System IP Address...: 192.168.142.20
Event Id............: 0x489746de00000000
Monitor Version.....: B.01.01
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_disk_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800/L3000-6x
OS Version......................: B.11.11
STM Version.....................: A.35.00
EMS Version.....................: A.03.20
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100472
v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v
Component Data:
Physical Device Path...: 0/10/0/0.4.1.0.0.0.3
Device Class...........: Disk
Inquiry Vendor ID......: DGC
Inquiry Product ID.....: CX700WDR10
Firmware Version.......: HP03
Serial Number..........: 6ASA300620
Product/Device Identification Information:
Logger ID.........: disc30; sdisk
Product Identifier: Disk
Product Qualifier.: DGC CX700WDR10
SCSI Target ID....: 0x00
SCSI LUN..........: 0x03
SCSI Command Data Block:
Command Data Block Contents:
0x0000: 00 00 00 00 00 00
Command Data Block Fields (6-byte fmt):
Command Operation Code...(0x00)..: TEST UNIT READY
Logical Unit Number..............: 0
Hardware Status: (not present in log record).
SCSI Sense Data:
Undecoded Sense Data:
0x0000: 70 00 02 00 00 00 00 0A 00 00 00 00 04 03 00 00
0x0010: 00 00
SCSI Sense Data Fields:
Error Code : 0x70
Segment Number : 0x00
Bit Fields:
Filemark : 0
End-of-Medium : 0
Incorrect Length Indicator : 0
Sense Key : 0x02
Information Field Valid : FALSE
Information Field : 0x00000000
Additional Sense Length : 10
Command Specific : 0x00000000
Additional Sense Code : 0x04
Additional Sense Qualifier : 0x03
Field Replaceable Unit : 0x00
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x00 0x00
Sense Key 0x02, NOT READY, indicates that the logical unit addressed
cannot be accessed. Operator intervention may be required to correct
this condition.
The combination of Additional Sense Code and Sense Qualifier (0x0403)
indicates: Logical unit not ready, manual intervention required.
>---------- End Event Monitoring Service Event Notification ----------<
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2008 11:52 PM
08-04-2008 11:52 PM
Re: Disk Event monitoring
But your diagnostics version is from 2002 (!!!) - consider to update this!
http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2008 12:22 AM
08-05-2008 12:22 AM
Re: Disk Event monitoring
powermt display dev=all
have you lost a path to one of your disks?
Is Navisphere reporting anything funny going on?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2008 12:36 AM
08-05-2008 12:36 AM
Re: Disk Event monitoring
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2008 12:39 AM
08-05-2008 12:39 AM
Re: Disk Event monitoring
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2008 12:49 AM
08-05-2008 12:49 AM
Re: Disk Event monitoring
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2008 12:52 AM
08-05-2008 12:52 AM
Re: Disk Event monitoring
Logical device ID=60060160408A11000B01F97376E3DB11
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP A
you probably want to fail over the LUNS's which do not having matching SP owners!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2008 12:57 AM
08-05-2008 12:57 AM
Re: Disk Event monitoring
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2008 01:08 AM
08-05-2008 01:08 AM
Re: Disk Event monitoring
Login to Navisphere via a web-browser
Look for the server withing the Storage Group tab
Check the default owner of the Lun from thew Storage Group tab
Then its tresspass I believe. But you better check to be 100% sure as I have not done this for ages.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2008 05:00 AM
08-05-2008 05:00 AM
Re: Disk Event monitoring
Thanks for your time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2008 05:54 AM
08-05-2008 05:54 AM