HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- MSA1500 - Controller failover causing issues with ...
HPE EVA Storage
1827243
Members
2240
Online
109716
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
02-06-2007 12:56 PM
02-06-2007 12:56 PM
MSA1500 - Controller failover causing issues with MSCS
Greetings,
Recently our company has started having problems with our MSA1500 and the 2 / 2 Node Windows 2003 R2 Clusters.
Also attached to the MSA are 1 VMware ESX Server and 1 MS File server. For some reason the MSA fails from the active controller to the passive one and causes our MS systems to loose their storage thus causing our clusters to start thrashing and never recover.
I also noticed with the MSA in where it does not provide a true redundant architecture. I'll try and draw what we have below:
|--A--| |--B--| One Cluster Group
|\ /|
| \ / |
| \ / |
| /\ |
| / \ |
|/ \|
(--1--) (--2--) Fibre Switches
\ /
| |
| |
a| |b
[--MSA--] HP MSA1500
First on the redundancy, if controller (a) is the active controller on the MSA, and I loose switch 1, I loose all storage on my systems.
The MSA controllers don't support dual fiber cards, which is concerning.
In a test of the MSA pulling the cable from node A to switch 1, causes the MSA to fail over after some time, but in that delay, all systems attached to the MSA have lost their storage.
The only system that does not fail is the ESX server.
Additional Information:
The MSA is at the most current firmware.
The QLogic HBA's are at the most current firmware
The Servers (HP Proliant DL380 G4) are at the most current firmware and drivers
The MCDATA fibre switches are at the most current firmware
The ACU software is at the most current version.
We are using StorPort Drivers and MS MPIO Drivers.
Will placing the MSA in an Active / Active configuration help resolve my redundancy issues?
Has anyone else experienced similar issues?
Any advice would greatly be appreciated.
TIA,
Gus
Recently our company has started having problems with our MSA1500 and the 2 / 2 Node Windows 2003 R2 Clusters.
Also attached to the MSA are 1 VMware ESX Server and 1 MS File server. For some reason the MSA fails from the active controller to the passive one and causes our MS systems to loose their storage thus causing our clusters to start thrashing and never recover.
I also noticed with the MSA in where it does not provide a true redundant architecture. I'll try and draw what we have below:
|--A--| |--B--| One Cluster Group
|\ /|
| \ / |
| \ / |
| /\ |
| / \ |
|/ \|
(--1--) (--2--) Fibre Switches
\ /
| |
| |
a| |b
[--MSA--] HP MSA1500
First on the redundancy, if controller (a) is the active controller on the MSA, and I loose switch 1, I loose all storage on my systems.
The MSA controllers don't support dual fiber cards, which is concerning.
In a test of the MSA pulling the cable from node A to switch 1, causes the MSA to fail over after some time, but in that delay, all systems attached to the MSA have lost their storage.
The only system that does not fail is the ESX server.
Additional Information:
The MSA is at the most current firmware.
The QLogic HBA's are at the most current firmware
The Servers (HP Proliant DL380 G4) are at the most current firmware and drivers
The MCDATA fibre switches are at the most current firmware
The ACU software is at the most current version.
We are using StorPort Drivers and MS MPIO Drivers.
Will placing the MSA in an Active / Active configuration help resolve my redundancy issues?
Has anyone else experienced similar issues?
Any advice would greatly be appreciated.
TIA,
Gus
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2007 06:02 PM
02-06-2007 06:02 PM
Re: MSA1500 - Controller failover causing issues with MSCS
That looks like a configuration problem to me.
Have you made sure that each server has a connection-entry on each controller and that its operating system profile is set correctly
Is SSP set up properly? Did you verify in the Qlogic adapters if they can 'see' the MSA disks properly?
Have you made sure that each server has a connection-entry on each controller and that its operating system profile is set correctly
Is SSP set up properly? Did you verify in the Qlogic adapters if they can 'see' the MSA disks properly?
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2007 11:29 PM
02-06-2007 11:29 PM
Re: MSA1500 - Controller failover causing issues with MSCS
Gus,
UWE could be correct.
Based off your diagram, you have MSA C1 as the left side. Actually MSA C1 is the right side.
With VMware, be aware of your SAN configuration. Steps to check.
1)Check your PCI slot assignment. Some slots share a pci bus. With some OS, slots have precedence.
2). If the HBA is dual ported, Port 0 has precedence over Port 1.
3). "Square Up" not a technical term. Make sure you have either the first slot or p0 going to switch 1 -> MSA (right) Controller 1.
I looked up your servers slots(Dl380G4), here is the order. Looking from the back.
3
2
1
Slots 2/3 are shared, so that bus will only run as fast as the slowest PCI card.
UWE could be correct.
Based off your diagram, you have MSA C1 as the left side. Actually MSA C1 is the right side.
With VMware, be aware of your SAN configuration. Steps to check.
1)Check your PCI slot assignment. Some slots share a pci bus. With some OS, slots have precedence.
2). If the HBA is dual ported, Port 0 has precedence over Port 1.
3). "Square Up" not a technical term. Make sure you have either the first slot or p0 going to switch 1 -> MSA (right) Controller 1.
I looked up your servers slots(Dl380G4), here is the order. Looking from the back.
3
2
1
Slots 2/3 are shared, so that bus will only run as fast as the slowest PCI card.
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