- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- msa question
Disk Enclosures
1752270
Members
4811
Online
108786
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
Go to solution
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
тАО06-30-2004 07:09 PM
тАО06-30-2004 07:09 PM
I have two basic questions for MSA controller & switches,
1. for MSA500, what happen if server use a smart array card. In my compenion for common scsi card array info stores in MSA SA-642 card, not in SCSI disks right? but if I use a server side smart array, where is the arrary information, shall I config it with MSA500 or server side card?
2. for MSA1000, with internal 8 port fc switches, does both controllers have cross connection to both switches? I mean, if one controller fails, all ports connecting to the switch right back to this controller will fail?
thx & regards.
1. for MSA500, what happen if server use a smart array card. In my compenion for common scsi card array info stores in MSA SA-642 card, not in SCSI disks right? but if I use a server side smart array, where is the arrary information, shall I config it with MSA500 or server side card?
2. for MSA1000, with internal 8 port fc switches, does both controllers have cross connection to both switches? I mean, if one controller fails, all ports connecting to the switch right back to this controller will fail?
thx & regards.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 01:11 AM
тАО07-01-2004 01:11 AM
Solution
Hi Tommy,
the MSA controllers (both 1000 & 500) are an extension of the Smart Array line. They all store the RAID info on the disks, thus allowing easy migration from one controller to another, e.g. can take disks that were in a server attached to an SA-5300 and move them to an MSA1000 without data loss (with everything shut down beforehand, and the disks have to be in the correct order).
A server needs a Smart Array controller (either an onboard 5i or a 532) to connect to an MSA500. You configure it via ACU on the attached server.
For the MSA1000, each controller only connects to one switch. The internal switches only have 7 external ports. The other port is internal and connects directly to corresponding MSA controller.
If a controller fails, I/O fails over the the 2nd controller, which is usually in a 2nd fabric. This means that all ports connected to the 1st switch won't see the MSA any more, so unless the hosts have a connection to the 2nd fabric (i.e. a 2nd HBA & securepath) they will lose access to the MSA storage.
Hope this helps.
Regards,
Stephen
the MSA controllers (both 1000 & 500) are an extension of the Smart Array line. They all store the RAID info on the disks, thus allowing easy migration from one controller to another, e.g. can take disks that were in a server attached to an SA-5300 and move them to an MSA1000 without data loss (with everything shut down beforehand, and the disks have to be in the correct order).
A server needs a Smart Array controller (either an onboard 5i or a 532) to connect to an MSA500. You configure it via ACU on the attached server.
For the MSA1000, each controller only connects to one switch. The internal switches only have 7 external ports. The other port is internal and connects directly to corresponding MSA controller.
If a controller fails, I/O fails over the the 2nd controller, which is usually in a 2nd fabric. This means that all ports connected to the 1st switch won't see the MSA any more, so unless the hosts have a connection to the 2nd fabric (i.e. a 2nd HBA & securepath) they will lose access to the MSA storage.
Hope this helps.
Regards,
Stephen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 06:46 PM
тАО07-01-2004 06:46 PM
Re: msa question
thx for your quick help.
Thus raised another concerns:
I've checked MSA30, after raid creation I switched to another RAID card, RAID info still persists. So it turned out RAID info is in disks. My question is, where does these informations in? I've check in Linux OS there's no dedicated partition for store such information.
I used SA5i+ connecting to MSA500 and it works, while SA5302 does not work. MSA500 documents does not indicate which card is supported, this is strange hum?
SA5i+ does not store raid informations, while SA5302 does. When I move out the JBOD that attached to SA5302, it continued trying to locate these disks.
Thus raised another concerns:
I've checked MSA30, after raid creation I switched to another RAID card, RAID info still persists. So it turned out RAID info is in disks. My question is, where does these informations in? I've check in Linux OS there's no dedicated partition for store such information.
I used SA5i+ connecting to MSA500 and it works, while SA5302 does not work. MSA500 documents does not indicate which card is supported, this is strange hum?
SA5i+ does not store raid informations, while SA5302 does. When I move out the JBOD that attached to SA5302, it continued trying to locate these disks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 07:48 PM
тАО07-01-2004 07:48 PM
Re: msa question
Hi,
the MSA500 does not support the SA5302 controller. Only the SA-532 and 5i. In fact, I've just noticed that there is now an MSA500 G2, which is only supported on SA-642 controllers (according to the Quickspecs).
I believe the RAID information is stored in the first few sectors of the physical disk. You will not be able to see this information directly from the OS. As far as individual disks go, only ACU will be able to see those, the OS will not see them. You create an array, then in that array you can create one or more logical drives, and the OS sees these logical drives as physical "disks".
Regards,
Stephen
the MSA500 does not support the SA5302 controller. Only the SA-532 and 5i. In fact, I've just noticed that there is now an MSA500 G2, which is only supported on SA-642 controllers (according to the Quickspecs).
I believe the RAID information is stored in the first few sectors of the physical disk. You will not be able to see this information directly from the OS. As far as individual disks go, only ACU will be able to see those, the OS will not see them. You create an array, then in that array you can create one or more logical drives, and the OS sees these logical drives as physical "disks".
Regards,
Stephen
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