- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Fiber failover msa2000
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
тАО08-13-2008 11:57 AM
тАО08-13-2008 11:57 AM
Fiber failover msa2000
We are implementing in a test case a msa2000fc dual controller with 2 hp 4/8 san switches on 1 windows 2003 server with 2 fc cards.
The solution shout be fully redundant but we have the following problem.
When we pull out the 2 fiber cables from the controller who is the preferred path of the lun than we lost connection.
All other redundancy functions are working.
We donтАЩt now what to do on this moment.
Thanks,
Henk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2008 12:23 PM
тАО08-13-2008 12:23 PM
Re: Fiber failover msa2000
http://h20000.www2.hp.com/bizsupport/TechSupport/SupportTaskIndex.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=3687128&taskId=110
and
other documentation
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManualтМй=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=12169&prodSeriesId=3687128
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2008 12:41 PM
тАО08-13-2008 12:41 PM
Re: Fiber failover msa2000
I know the over standing links en tried different things.
we put the newest software in the switches and the san.
But it has no result.
Thanks,
Henk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2008 01:40 PM
тАО08-13-2008 01:40 PM
Re: Fiber failover msa2000
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01388355/c01388355.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2008 10:22 PM
тАО08-13-2008 10:22 PM
Re: Fiber failover msa2000
We use windows 2003 server. We installed the MIPO multipath software. The strange thing is when we pull out one fiber the san shows that the connection is down. When we do this with the other cable it also shows it so the san is knowing that the connection is lost. But the san isn't set the controller in fail status and set the other controller primary.
Thanks,
Henk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2008 10:24 PM
тАО08-13-2008 10:24 PM
Re: Fiber failover msa2000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2008 03:28 AM
тАО08-14-2008 03:28 AM
Re: Fiber failover msa2000
It seems we can not get the failover working, we can assign the LUN0 partition to one controller, we can not assign another controller in case of failover.
We can diable the controller and then everything is working fine, however when we pull out the Fivber cables of the preferred controller we can not access the LUN anymore.
Any helpfull hints?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2008 07:08 AM
тАО08-20-2008 07:08 AM
Re: Fiber failover msa2000
Windows 2003 what ??
Windows 2003 x32
Windows 2003 x64
Windows 2003 ia64
we are having same on ia64 and got information "ia64 and MSA2000 NOT supported see specs"
maaybee a driver in September
we are going to replace the MSA via HP
kind regards
Frank
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2008 05:40 AM
тАО09-10-2008 05:40 AM
Re: Fiber failover msa2000
It doesn't matter to what hosts the msa2012fc is connected to.
The problem is that there seems to be no controller failover triggered by disconnected fo links as happens with the MSA1000/1500.
We have been up and down the manual and the controllers configurations but we have not found a way to enable this.
Can someone please tell us what else can we do?
Thanks a lot,
TC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2008 09:10 AM
тАО09-10-2008 09:10 AM
Re: Fiber failover msa2000
> controller failover triggered by disconnected
> fo links as happens with the MSA1000/1500.
Right :-(
The MSA2000 is just 2 controller modules glued together with an adhesive strip.
A controller does NOT present any SCSI LUNs for volumes in a non-owned vdisk - unlike most other storage arrays on this planet.
A 'virtual disk' and its embedded volumes will only move if the controller module fails completely.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2008 03:22 PM
тАО09-17-2008 03:22 PM
Re: Fiber failover msa2000
The big selling point is the "High availability for business continuity: Reduce risk of IT failure with active/active controllers, dual-ported drives, and redundant hardware components.
". That's a direct quote from the website. Are you telling me that's not true? If it's not true then somebody owes me a refund/return because Active/Active means LUN presentations simultaneously from both controllers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2008 09:15 PM
тАО09-17-2008 09:15 PM
Re: Fiber failover msa2000
Sorry for the long post, but I have read many items on this forum and although I understand that the MSA2212fc is not a true dual shared controller (a vdisk is owned by 1 controller) I still do not understand why my configuration does not work, since I have cabled all servers to see both controllers. Any advice?
I have a similar problem with my msa2212fc. We have fully redundant fc cabling with 2 StorageWorks 4/8 switches and 4 DL 360 servers. Each server has dual port Qlogic card with port 0 to switch A, port 1 to switch B.
The MSA is cabled as documented, Ctrl A port 0 and Ctrl B port 1 to switch A, Ctrl A port 1 and Ctrl B port 0 to switch B. This provides a fully redundant path to every DL 360 host running ESX server 3.5.
I created 3 test volumes with global LUNS 0, 1 and 2 on the MSA. Some servers see all the volumes on 1 of the 2 hbas, some see selected volumes on both hbas, but none of the 4 servers sees all 3 volumes on both hbas. It seems almost random, except that it doesn't change with reboots or rescans in Vmware.
The MSA storage manager even indicates the problem in the host volume mapping display screen by showing only 7 of the 8 WWPN numbers and various combinations of "Controller A port 0" or "Controller B port 0" or "Both controller A port 1 and Controller B port 0" for each host WWPN in the table. The way it is cabled, I would expect all hosts to see both controllers.
In addition, some servers see multiple paths under Vmware "manage paths" for some LUNS, but no server sees all volumes and paths. I have tried loop and point to point topologies with no difference. I always leave the MSA host port interconnect disabled as documented for my config.
The cabling has been double checked and all the WWPN numbers for all the devices and ports show up properly when getting port and device status from each of the 4/8 switches, so it seems to be the MSA itself which does not work right. The switches are running the latest v6.1.0d fabric, the vmware is the latest 3.5 update 2.
Thanks,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2008 10:26 PM
тАО09-17-2008 10:26 PM
Re: Fiber failover msa2000
D-O-N-'-T S-H-O-O-T T-H-E M-E-S-S-E-N-G-E-R !-!-!-!
I don't really want to write down _my_ feelings on this, erm, 'product'...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2008 11:58 AM
тАО09-26-2008 11:58 AM
Re: Fiber failover msa2000
HP Support document c01440945
HP StorageWorks MSA2000 host port redundancy
"In testing fault-tolerant configurations, removing a single path, or cable, will result in a successful test. Removing both paths, or cables, from a controller is considered a double fault, and access to Vdisks owned by the controller will no longer be available until the issue is resolved."
It can be read here completely:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=120&prodSeriesId=3687115&prodTypeId=12169&objectID=c01440945
Robert Spiess