- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: MSA2000 LUN and Volume name usage
Disk Enclosures
1753534
Members
5646
Online
108795
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
тАО10-15-2008 11:03 AM
тАО10-15-2008 11:03 AM
MSA2000 LUN and Volume name usage
I'm wondering if there is some tutorial or beginners read me on mapping LUNs and using Volume names on and MSA2000 (msa2212fc). I've read the users guide and read through lots of this forum, but I feel like I'm missing something.
I have 12 dual controller enclosures each with an expansion unit connected to two SAN switches which are connected to HBAs in 6 dl380g5 servers.
Are volume names meaningful at all? It seems that I can use the same volume name on each set of controllers with no conflict.
The same question with LUNS. It seems that I can create more than 1 volume with the same LUN on a single controller without any difficulties.
Any help or pointers to docs will be appreciated.
I have 12 dual controller enclosures each with an expansion unit connected to two SAN switches which are connected to HBAs in 6 dl380g5 servers.
Are volume names meaningful at all? It seems that I can use the same volume name on each set of controllers with no conflict.
The same question with LUNS. It seems that I can create more than 1 volume with the same LUN on a single controller without any difficulties.
Any help or pointers to docs will be appreciated.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-22-2008 08:09 AM
тАО10-22-2008 08:09 AM
Re: MSA2000 LUN and Volume name usage
Hello Jack,
Volume names are to recognize the Luns and can be the same in different arrays with no problem (they are identified in the SAN with WWID's from each other), but it is always good to put unique significant names to differentiate the MSA and the lun, lun numbering follows the same principle, can be repeated in diffent arrays.
If you have the SAN properly configured (zoning and cabling), there should not be any problem.
The user guide is useful for installation and basic config, but the doc I like for configuration issues is the Reference guide:
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01565941/c01565941.pdf
In Page 84 is the volumes section, page 99 for mapping luns on a 2012fc, you migh want to check page 95 for host list information.
Volume names are to recognize the Luns and can be the same in different arrays with no problem (they are identified in the SAN with WWID's from each other), but it is always good to put unique significant names to differentiate the MSA and the lun, lun numbering follows the same principle, can be repeated in diffent arrays.
If you have the SAN properly configured (zoning and cabling), there should not be any problem.
The user guide is useful for installation and basic config, but the doc I like for configuration issues is the Reference guide:
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01565941/c01565941.pdf
In Page 84 is the volumes section, page 99 for mapping luns on a 2012fc, you migh want to check page 95 for host list information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-22-2008 12:31 PM
тАО10-22-2008 12:31 PM
Re: MSA2000 LUN and Volume name usage
Jack,
As a general rule I will use volume names that identify the controllerpair-system-lunnumber. That way I can easily look and identify what device I am working with on what system. The naming convention used for volumes is entirely up to the person configuring the MSA2000. And if you come up with a naming convention down the road that fits your needs better, you can simply go in and change the names of the volumes to fit your needs.
Phil
As a general rule I will use volume names that identify the controllerpair-system-lunnumber. That way I can easily look and identify what device I am working with on what system. The naming convention used for volumes is entirely up to the person configuring the MSA2000. And if you come up with a naming convention down the road that fits your needs better, you can simply go in and change the names of the volumes to fit your needs.
Phil
Once it's in production it's all bugs after that.
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