- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- EMS Event Notification "CRITICAL (5)"
Operating System - HP-UX
1752806
Members
5883
Online
108789
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
Discussions
Discussions
Forums
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
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
тАО12-03-2009 10:00 PM
тАО12-03-2009 10:00 PM
EMS Event Notification "CRITICAL (5)"
I am getting the EMS notification in the syslog.log as a crital .. pls find the attached txt of the logs and errors.
I checked the hardware path and device status as per the EMS notification the status of the device is
ext_bus 117 0/12/0/0.102.122.255.1 fcpdev CLAIMED INTERFACE FCP Device Interface
target 67 0/12/0/0.102.122.255.1.3 tgt CLAIMED DEVICE
ctl 15 0/12/0/0.102.122.255.1.3.0 sctl CLAIMED DEVICE IBM 2145
/dev/rscsi/c117t3d0
fcp 4 0/12/0/0.108 fcp NO_HW INTERFACE FCP Domain
fcp 8 0/12/0/0.125 fcp CLAIMED INTERFACE FCP Domain
Pls help me out to fix this..
I checked the hardware path and device status as per the EMS notification the status of the device is
ext_bus 117 0/12/0/0.102.122.255.1 fcpdev CLAIMED INTERFACE FCP Device Interface
target 67 0/12/0/0.102.122.255.1.3 tgt CLAIMED DEVICE
ctl 15 0/12/0/0.102.122.255.1.3.0 sctl CLAIMED DEVICE IBM 2145
/dev/rscsi/c117t3d0
fcp 4 0/12/0/0.108 fcp NO_HW INTERFACE FCP Domain
fcp 8 0/12/0/0.125 fcp CLAIMED INTERFACE FCP Domain
Pls help me out to fix this..
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 10:13 PM
тАО12-03-2009 10:13 PM
Re: EMS Event Notification "CRITICAL (5)"
Hi..
lbolt error signify hardware error.
lbolt error signify hardware error.
Don't fix what ain't broke
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2009 10:14 PM
тАО12-03-2009 10:14 PM
Re: EMS Event Notification "CRITICAL (5)"
Is there any disk with name c102t4d1 ??
If yes, whats is the status ?
If yes, whats is the status ?
Don't fix what ain't broke
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2009 12:01 AM
тАО12-04-2009 12:01 AM
Re: EMS Event Notification "CRITICAL (5)"
Hi
Summary:
Adapter at hardware path 0/12/0/0 : Unable to open previously opened
target
Description of Error:
lbolt value: 2066411522
Unable to access previously accessed target
nport ID = 0x660b13
Probable Cause / Recommended Action:
An attempt to re-open a device which had been opened earlier
has failed.
There should be additional logging messages which will
allow diagnosis of the problem.
This is an HBA (* host bus adaptor *) at hardware address 0/12/0/0 and nport 0x660b13.
Run
ioscan -H 0/12/0/0 to get the device, ie, /dev/fc##.
Run
fcmsutil /dev/fc## to get the state.
Run
cstm<<-EOF
runutil logtool
rs
EOF
To see how many errors are being recorded and paste in the report including the start end end times.
LBOLTS can usually be ignored unless the number of errors is really high. The logtool report will tell you this.
See what is attached to this device, ie, tape drive or disk array. IF tape drive then this is typical.
Summary:
Adapter at hardware path 0/12/0/0 : Unable to open previously opened
target
Description of Error:
lbolt value: 2066411522
Unable to access previously accessed target
nport ID = 0x660b13
Probable Cause / Recommended Action:
An attempt to re-open a device which had been opened earlier
has failed.
There should be additional logging messages which will
allow diagnosis of the problem.
This is an HBA (* host bus adaptor *) at hardware address 0/12/0/0 and nport 0x660b13.
Run
ioscan -H 0/12/0/0 to get the device, ie, /dev/fc##.
Run
fcmsutil /dev/fc## to get the state.
Run
cstm<<-EOF
runutil logtool
rs
EOF
To see how many errors are being recorded and paste in the report including the start end end times.
LBOLTS can usually be ignored unless the number of errors is really high. The logtool report will tell you this.
See what is attached to this device, ie, tape drive or disk array. IF tape drive then this is typical.
Support Fatherhood - Stop Family Law
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP