- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Proliant DL 385 and scsi SNMP
Operating System - Linux
1752720
Members
5649
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
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
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
09-12-2006 08:38 AM
09-12-2006 08:38 AM
Proliant DL 385 and scsi SNMP
I'm trying to get my box to spit out SNMP traps when I have HDD failure, but I'm having difficulties. Anyone have experience with SuSE 9 and the HP hpasm package?
I've installed net-snmp from HP, and install the hpasm package (7.5.1-8 sles9 x86_64). I get power supply traps ok and fan notifications if I pull one out. But the storage agents are dead on arrival.
Running a /etc/init.d/hpasm status, I get the following:
[root@mp-03 /]>> /etc/init.d/hpasm status
hpasmd is running...
Status of Foundation Agents (cmafdtn): cmathreshd cmahostd cmapeerd
cmathreshd is running...
cmahostd is running...
cmapeerd is running...
Status of Server Agents (cmasvr): cmastdeqd cmahealthd cmaperfd
cmastdeqd is running...
cmahealthd is running...
cmaperfd is running...
Status of Storage Agents (cmastor): cmaeventd cmaidad cmafcad cmaided cmascsid c
masasd
cmaeventd is stopped...
cmaidad is stopped...
cmafcad is stopped...
cmaided is running...
cmascsid is stopped...
cmasasd is stopped...
Ok. So looking at this, my storage agents are stopped. When I reboot, I get segment faults from the console:
cmaidad[5605]: segfault at 0000000000000000 rip 0000000000000000 rsp 00000000fff
fdb9c error 14
cmaeventd[5630]: segfault at 0000000000000000 rip 0000000000000000 rsp 00000000f
fffd54c error 14
cmafcad[5632]: segfault at 0000000000000000 rip 0000000000000000 rsp 00000000fff
fdb0c error 14
When I plug in a monitor to the box, I get different (???) segment fault errors:
cmaeventd[5628] segfault at 0000000000000000 rip 0000000000000000 rsp 000000ffffd54c error 14
cmaidad[5635]: segfault at 0000000000000000 rip 0000000000000000 rsp 000000ffffdb9c error 14
cmafcad[5643]: segfault at 0000000000000000 rip 0000000000000000 rsp 000000ffffdb0c error 14
These ones are specifically related to storage agents.
Any ideas?
I noticed that it's not the first time segment faults have been found on this driver:
http://h50146.www5.hp.com/products/software/oe/linux/mainstream/bin/support/doc/general/mgmt/ima/v730c/hpasm-7.3.0c-67.sles9.x86_64.rpm.txt
I've installed net-snmp from HP, and install the hpasm package (7.5.1-8 sles9 x86_64). I get power supply traps ok and fan notifications if I pull one out. But the storage agents are dead on arrival.
Running a /etc/init.d/hpasm status, I get the following:
[root@mp-03 /]>> /etc/init.d/hpasm status
hpasmd is running...
Status of Foundation Agents (cmafdtn): cmathreshd cmahostd cmapeerd
cmathreshd is running...
cmahostd is running...
cmapeerd is running...
Status of Server Agents (cmasvr): cmastdeqd cmahealthd cmaperfd
cmastdeqd is running...
cmahealthd is running...
cmaperfd is running...
Status of Storage Agents (cmastor): cmaeventd cmaidad cmafcad cmaided cmascsid c
masasd
cmaeventd is stopped...
cmaidad is stopped...
cmafcad is stopped...
cmaided is running...
cmascsid is stopped...
cmasasd is stopped...
Ok. So looking at this, my storage agents are stopped. When I reboot, I get segment faults from the console:
cmaidad[5605]: segfault at 0000000000000000 rip 0000000000000000 rsp 00000000fff
fdb9c error 14
cmaeventd[5630]: segfault at 0000000000000000 rip 0000000000000000 rsp 00000000f
fffd54c error 14
cmafcad[5632]: segfault at 0000000000000000 rip 0000000000000000 rsp 00000000fff
fdb0c error 14
When I plug in a monitor to the box, I get different (???) segment fault errors:
cmaeventd[5628] segfault at 0000000000000000 rip 0000000000000000 rsp 000000ffffd54c error 14
cmaidad[5635]: segfault at 0000000000000000 rip 0000000000000000 rsp 000000ffffdb9c error 14
cmafcad[5643]: segfault at 0000000000000000 rip 0000000000000000 rsp 000000ffffdb0c error 14
These ones are specifically related to storage agents.
Any ideas?
I noticed that it's not the first time segment faults have been found on this driver:
http://h50146.www5.hp.com/products/software/oe/linux/mainstream/bin/support/doc/general/mgmt/ima/v730c/hpasm-7.3.0c-67.sles9.x86_64.rpm.txt
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2006 03:06 PM
09-12-2006 03:06 PM
Re: Proliant DL 385 and scsi SNMP
Shalom,
These issues are usually caused by mismatches between the OS and the actual verion of the OS with patches required by the hpasm tool.
There may be more evidence in the /var/log/messages file that will let you know the actual cause of the fault.
You checked the support matrix?
SEP
These issues are usually caused by mismatches between the OS and the actual verion of the OS with patches required by the hpasm tool.
There may be more evidence in the /var/log/messages file that will let you know the actual cause of the fault.
You checked the support matrix?
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
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