GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: MSA1000 force Controller failover
HPE EVA Storage
1849025
Members
4523
Online
104041
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
Forums
Discussions
back
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
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
10-13-2006 03:08 AM
10-13-2006 03:08 AM
MSA1000 force Controller failover
Hi,
I have a dual path MSA1000 SAN with the internal 2/8 switches.
The system is currently running a MSCS Exchange cluster with 2 nodes. I am about to add 2 more boxes to the SAN running VMWare ESX3. Before I do this I need to setup SSP so that nothing conflicts. When doing this I have heard that people have had problems with one path not showing up in ACU to add to the SSP group. The fix is apparently to fail over the controller so the other path becomes active and then shows up.
My question is how to initiate this failover manually?
Cheers
Nathan
I have a dual path MSA1000 SAN with the internal 2/8 switches.
The system is currently running a MSCS Exchange cluster with 2 nodes. I am about to add 2 more boxes to the SAN running VMWare ESX3. Before I do this I need to setup SSP so that nothing conflicts. When doing this I have heard that people have had problems with one path not showing up in ACU to add to the SSP group. The fix is apparently to fail over the controller so the other path becomes active and then shows up.
My question is how to initiate this failover manually?
Cheers
Nathan
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2006 03:15 AM
10-13-2006 03:15 AM
Re: MSA1000 force Controller failover
The simplest way would be to just disable the controller's port from the SAN Switch GUI.
This will effectively tell your multipath software that there has been a path failure and will force it to initiate the failover.
Disconnecting one of the active fibre cables should also produce a failover.
If you are using SecurePath, you can initiate a path failover from the SP Manager.
Steven
This will effectively tell your multipath software that there has been a path failure and will force it to initiate the failover.
Disconnecting one of the active fibre cables should also produce a failover.
If you are using SecurePath, you can initiate a path failover from the SP Manager.
Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
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
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP