- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: MSA1000: adding a controller
HPE EVA Storage
1752806
Members
6133
Online
108789
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-28-2009 12:31 PM
тАО09-28-2009 12:31 PM
MSA1000: adding a controller
Hi there,
We would like to add a second controller to an MSA1000 in an active/active configuration. HereтАЩs what I think the process should be; anyone see any concerns or errors?
The install:
We have an MSA1000 with a single controller running the 7.0 firmware. We have an MSA20 shelf connected with 2 SCSI connections. There is an internal 2/8 SAN switch installed with a single Fiber Channel connection to each server (6 on SAN) and 1 connection to an MSL6000 tape array.
The goal:
The tech we spoke to on what we thought was a routine drive failure thought that the 7.0 firmware would only work properly if 2 controllers were present. We need to have the 7.0 firmware installed for VMWareтАЩs supported hardware list. If I understand right, the 2 controllers will be fault-tolerant as well as load-balancing in an active/active setup.
The process:
тАв Shut down the 6 servers and 1 tape array connected to the SAN.
тАв Reboot SAN for clean firmware.
тАв Install new 2nd controller.
тАв Reboot SAN again.
тАв At prompt on controller LCD, allow firmware to be cloned (assuming itтАЩs not on 7.0 already).
тАв Bring servers back up and confirm that each sees the LUNs it should.
This article seems to be very close to what I want to do, minus the cache upgrade:
http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1254158796471+28353475&threadId=1350084
Any thoughts?
CC
We would like to add a second controller to an MSA1000 in an active/active configuration. HereтАЩs what I think the process should be; anyone see any concerns or errors?
The install:
We have an MSA1000 with a single controller running the 7.0 firmware. We have an MSA20 shelf connected with 2 SCSI connections. There is an internal 2/8 SAN switch installed with a single Fiber Channel connection to each server (6 on SAN) and 1 connection to an MSL6000 tape array.
The goal:
The tech we spoke to on what we thought was a routine drive failure thought that the 7.0 firmware would only work properly if 2 controllers were present. We need to have the 7.0 firmware installed for VMWareтАЩs supported hardware list. If I understand right, the 2 controllers will be fault-tolerant as well as load-balancing in an active/active setup.
The process:
тАв Shut down the 6 servers and 1 tape array connected to the SAN.
тАв Reboot SAN for clean firmware.
тАв Install new 2nd controller.
тАв Reboot SAN again.
тАв At prompt on controller LCD, allow firmware to be cloned (assuming itтАЩs not on 7.0 already).
тАв Bring servers back up and confirm that each sees the LUNs it should.
This article seems to be very close to what I want to do, minus the cache upgrade:
http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1254158796471+28353475&threadId=1350084
Any thoughts?
CC
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2009 07:50 AM
тАО10-03-2009 07:50 AM
Re: MSA1000: adding a controller
Hi CC,
If you're adding a second controller to an MSA1000, I'm fairly certain that you also need to add in a second internal 2/8 SAN switch.
Cheers,
Rob
If you're adding a second controller to an MSA1000, I'm fairly certain that you also need to add in a second internal 2/8 SAN switch.
Cheers,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2009 09:42 AM
тАО10-05-2009 09:42 AM
Re: MSA1000: adding a controller
Thanks for that tip. It does appear from the manual for the 2/8 SAN switch that there is one port directly to the controller. I originally thought that the port went to some sort of backplane and then to the controllers.
So if I understand right, this would be our single-path plan:
* Install new controller.
* Install new 2/8 SAN switch.
* Move one our FC server connections over to the new switch so as to free a port to...
* Connect the new SAN switch to the old one.
Though it seems like adding a switch without making the fabric redundant is unnecessarily complex. And I suspect a new switch purchase will mean that we try to hold on for another year and then upgrade/replace.
Thanks,
CC
So if I understand right, this would be our single-path plan:
* Install new controller.
* Install new 2/8 SAN switch.
* Move one our FC server connections over to the new switch so as to free a port to...
* Connect the new SAN switch to the old one.
Though it seems like adding a switch without making the fabric redundant is unnecessarily complex. And I suspect a new switch purchase will mean that we try to hold on for another year and then upgrade/replace.
Thanks,
CC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2009 11:43 AM
тАО10-05-2009 11:43 AM
Re: MSA1000: adding a controller
Hi CC,
If you are planning to get a redundant environment with an additional controller then a additional in built switch is mandatory.
one port of the 2/8 san switch is connected internaly to the controller and also you need to have 2 fc cards on each server each going to either switches so that the server will have access to the MSA via both the controllers.
both controllers talk to each other via an internal link so once the one controller goes down the other takes ownership of all the Luns and servers gets access via that controller.
after this HW changes you can do the Firmware upgrade and insert the new controller this will copy the fw from the other controller and will reboot automatically.
hopefully this might help !!! all the best
If you are planning to get a redundant environment with an additional controller then a additional in built switch is mandatory.
one port of the 2/8 san switch is connected internaly to the controller and also you need to have 2 fc cards on each server each going to either switches so that the server will have access to the MSA via both the controllers.
both controllers talk to each other via an internal link so once the one controller goes down the other takes ownership of all the Luns and servers gets access via that controller.
after this HW changes you can do the Firmware upgrade and insert the new controller this will copy the fw from the other controller and will reboot automatically.
hopefully this might help !!! all the best
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