- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- MSA1510i and Windows 2003 R2 MSCS Cluster
Disk Enclosures
1753774
Members
6909
Online
108799
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
тАО09-19-2007 04:08 AM
тАО09-19-2007 04:08 AM
MSA1510i and Windows 2003 R2 MSCS Cluster
1. Does anyone have an ETA when MSCS clusters will be supported with the MSA1510i (w/ iSCSI)?
2. As many of us know, MSCS clustering will work in this environment but what are the best practices to prevent any issues? Are there known pitfalls, risks? How to avoid these?
For instance I have in place:
- 2x DL380G5 servers
- W2K3 R2 SP2 64-bit
- MSA1510i 2 controllers, dual GigE ethernet modules, w/ single storage enclosure
- 2x Procurve 2900 GigE switches (for separate iSCSI paths). Separate isolated physical iscsi LANs not on production LAN)
- each server has dual port NC380T NIC, one port per iSCSI path
- MS iSCSI initiator, HP MPIO
MSA Configuration:
- Created one portal group per LAN (each switch in a separate subnet)
- Both nodes share the same single target, via same 2 IP portal groups for shared storage
- iSCSI initiator target is "logged on" twice on each node, one for each controller path/NIC combo
Since this is an active/passive configuration, how do we prevent each node from "pulling" its disks over to one controller versus the other. I witnessed this ping/pong effect once whereby the disks were failing back and forth between MSA controllers, about once per second disrupting all the servers in the iSCSI SAN.
Any assistance with this is greatly appreciated to get us by (with the eventual goal of having active/active firmware on the MSA with cluster support).
[config details are provided attached]
TIA
2. As many of us know, MSCS clustering will work in this environment but what are the best practices to prevent any issues? Are there known pitfalls, risks? How to avoid these?
For instance I have in place:
- 2x DL380G5 servers
- W2K3 R2 SP2 64-bit
- MSA1510i 2 controllers, dual GigE ethernet modules, w/ single storage enclosure
- 2x Procurve 2900 GigE switches (for separate iSCSI paths). Separate isolated physical iscsi LANs not on production LAN)
- each server has dual port NC380T NIC, one port per iSCSI path
- MS iSCSI initiator, HP MPIO
MSA Configuration:
- Created one portal group per LAN (each switch in a separate subnet)
- Both nodes share the same single target, via same 2 IP portal groups for shared storage
- iSCSI initiator target is "logged on" twice on each node, one for each controller path/NIC combo
Since this is an active/passive configuration, how do we prevent each node from "pulling" its disks over to one controller versus the other. I witnessed this ping/pong effect once whereby the disks were failing back and forth between MSA controllers, about once per second disrupting all the servers in the iSCSI SAN.
Any assistance with this is greatly appreciated to get us by (with the eventual goal of having active/active firmware on the MSA with cluster support).
[config details are provided attached]
TIA
"tried and true instead of new and improved"
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2007 03:17 AM
тАО10-01-2007 03:17 AM
Re: MSA1510i and Windows 2003 R2 MSCS Cluster
October update:
1) Acknowleded the fact that HP (still) does not support MSCS clusters on the MSA 1510i yet, no ETA at this time, and no replies to my post.
2) SAP R3 patch: It was discovered that an SAP patch named "NTCLUST" resolve the cluster group ping/pong effect having cluster groups failover and back between cluster nodes which resulted in disks unmounting and re-mounting between hosts while services were running. This resulted in disks pulled out from underneath the application services running. This was exacerbated by the fact that each node was attempting to failover the disks between MSA controllers as well during the cluster group movement between nodes.
After the SAP patch was installed, cluster failover and failback tests are much cleaner now and the environment is less problematic.
If one can share insight into the MSA 1510i supporting MSCS clusters at some point that would be appreciated.
thanks.
1) Acknowleded the fact that HP (still) does not support MSCS clusters on the MSA 1510i yet, no ETA at this time, and no replies to my post.
2) SAP R3 patch: It was discovered that an SAP patch named "NTCLUST" resolve the cluster group ping/pong effect having cluster groups failover and back between cluster nodes which resulted in disks unmounting and re-mounting between hosts while services were running. This resulted in disks pulled out from underneath the application services running. This was exacerbated by the fact that each node was attempting to failover the disks between MSA controllers as well during the cluster group movement between nodes.
After the SAP patch was installed, cluster failover and failback tests are much cleaner now and the environment is less problematic.
If one can share insight into the MSA 1510i supporting MSCS clusters at some point that would be appreciated.
thanks.
"tried and true instead of new and improved"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2007 03:56 AM
тАО10-12-2007 03:56 AM
Re: MSA1510i and Windows 2003 R2 MSCS Cluster
I agree that it will work. We've been running Exchange 2007 and one SQL05 cluster for some time now w/o incident. The Management interface is poorly designed, such that it when the 1510i fails over to the standby controller, you probably will lose connectivity to it. HP's aware of this and working on it. We leave a serial cable connected to a machine all the time so we can console into it.
If there are any misconfigured services in SQL, such as Reporting Services, it will cause issues as well with the cluster.
If there are any misconfigured services in SQL, such as Reporting Services, it will cause issues as well with the cluster.
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