- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Please help me understand controller/volume redund...
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
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
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-16-2021 08:46 AM - last edited on 08-17-2021 04:18 AM by support_s
08-16-2021 08:46 AM - last edited on 08-17-2021 04:18 AM by support_s
Please help me understand controller/volume redundancy
I am new to this.
I have 2 physical nodes in a Windows 2016 Cluster.
An dual-controller MSA 1060 with a "Data" volume which is presented to both Nodes.
My question is... If I disconnect the iSCSCI cables from 1 of the controller, is the volume supposed to be available to the Active Node?
I tried this and lost access to the volume.
Are both controllers active? or is one of them supposed to be in Standby and kick in when the active one fails?
Thanks for help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2021 11:44 AM
08-16-2021 11:44 AM
Re: Please help me understand controller/volume redundancy
As per your query,
Dual controller means data passed thru these both controller.
If any malfunction in one controller then one controller act as main active controller and its change the state like write mode cache mean data pass thru one controller.
In your case how you setup the controller?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2021 12:24 AM
08-17-2021 12:24 AM
Re: Please help me understand controller/volume redundancy
Hi,
is it cabled in this way?
Then check this: HPE MSA 1060/2060/2062 Storage Arrays Best Practices
Here Section: CONNECTIVITY BEST PRACTICES
And Section: MPIO
Cali

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2021 12:10 PM
08-18-2021 12:10 PM
Re: Please help me understand controller/volume redundancy
I think that the problem you experienced is the number of SESSIONs that your Windows system is creating to the storage target.
By default Windows will only choose a single path: Initiator IP -> Target IP
You should create multiple sessions from the host to the target using the Initiator IPs specifically called out to the specific target IPs.
In other protocols the additional PATHs are automatic but in iSCSI they need to explicitly set.
You should see multiple paths to the LUN in the device manager or the MPIO manager.
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]