- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Using non-consecutive LUN numbers for a VVSet
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
Forums
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
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
тАО03-07-2016 05:33 PM
тАО03-07-2016 05:33 PM
Using non-consecutive LUN numbers for a VVSet
IHAC that wants to use only even numbers for their LUN numbers.
If they export 3 volumes (e.g.) without a VVSet, they can specify 2,4,6 as the LUN number and it's fine.
If they export 3 volumes in a VVSet and they try to specify 2,4,6, they get an error that VVSets must have consecutive LUN number.
Is this a GUI limitation? I can't think of any reason this would be a limitation of the 3PAR itself.
Any thoughts?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2016 10:20 PM
тАО03-07-2016 10:20 PM
Re: Using non-consecutive LUN numbers for a VVSet
No, it's the system. From the CLI reference: CREATEVLUN -- ... "Exports from a VV set must be contiguous" ...
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2016 10:22 PM
тАО03-07-2016 10:22 PM
Re: Using non-consecutive LUN numbers for a VVSet
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2016 03:29 PM
тАО03-12-2016 03:29 PM
Re: Using non-consecutive LUN numbers for a VVSet
>"Exports from a VV set must be contiguous"
This is no longer true but you have to go through hoops to make them non-contiguous.
I.e. you have to export a VVset, then delete members. If you then export that VVset to another host, the holes remain.
>they try to specify 2,4,6, they get an error that VVSets must have consecutive LUN number.
The CLI only takes one number, so are you using SSMC?
> Any thoughts as to why that is?
It was designed that way? Just to remember a starting LUN and simply increment by one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2016 06:56 AM
тАО03-14-2016 06:56 AM
Re: Using non-consecutive LUN numbers for a VVSet
This is no longer true but you have to go through hoops to make them non-contiguous.
I.e. you have to export a VVset, then delete members. If you then export that VVset to another host, the holes remain.
Thanks. I don't see this as an option for them. Too much work upfront.
The CLI only takes one number, so are you using SSMC?
Yep, SSMC.
It was designed that way? Just to remember a starting LUN and simply increment by one.
I know it's certainly easier to do it this way, but apparently some customers have other needs. If we allow it on a group of individual LUNs, there's no technical reason it couldn't be allowed on a set of LUNs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2016 11:10 AM
тАО03-14-2016 11:10 AM
Re: Using non-consecutive LUN numbers for a VVSet
>If we allow it on a group of individual LUNs, there's no technical reason it couldn't be allowed on a set of LUNs.
You're confusing SSMC client magic (which can be done one LUN at a time) with the vector method of using VVsets.
The former is built into the client. The latter is built into the HPE 3PAR OS itself.