- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- "Twin" Qlogic QMH4062 total failure!
BladeSystem - General
1757014
Members
2384
Online
108858
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
04-29-2010 09:14 AM
04-29-2010 09:14 AM
"Twin" Qlogic QMH4062 total failure!
We have 4 BL490c G6 servers running with sphere with 4 Qlogic 4062 adapters booting off a MSA2012i (now P2000). Two servers, one after the other with a delta time of a couple of hours max failed together; the Qlogic adapter stopped communicating and logged firmware error repeatedly on the console. Luckily our infrastructure could keep the restarted VMs running on the remaining 2 blades and we weren't faced with any particular heavy downtime thanks to VMware HA.
However, it is incredible that the sole single point of failure (the Qlogic iSCSI HBA) failed, not once but TWICE on 2 seperate servers. One of the two adapters will not even enter their BIOS simply reporting corrupted firmware while the other is unable to save any settings in nvram.
Just wanted to document this pretty heavy misshap and to keep an eye out on Qlogic HBAs. Needless to say that our c3000 is under an XR5500 and networked with twin procurve 2810 switches for redundancy so no, it wasn't due to an external "current transient" or ground loop. Nothing was being done around the rack or network. They just died, one after the other. Makes me wonder about the other 2 now.
Just a bad day or is something else lurking under the mat?
However, it is incredible that the sole single point of failure (the Qlogic iSCSI HBA) failed, not once but TWICE on 2 seperate servers. One of the two adapters will not even enter their BIOS simply reporting corrupted firmware while the other is unable to save any settings in nvram.
Just wanted to document this pretty heavy misshap and to keep an eye out on Qlogic HBAs. Needless to say that our c3000 is under an XR5500 and networked with twin procurve 2810 switches for redundancy so no, it wasn't due to an external "current transient" or ground loop. Nothing was being done around the rack or network. They just died, one after the other. Makes me wonder about the other 2 now.
Just a bad day or is something else lurking under the mat?
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