- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- VVset cannot grow because of the duplicated LUN ID
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
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
10-24-2017 11:35 PM
10-24-2017 11:35 PM
Hi,
I have a question about the vvset growth in 3par. The vvset members must have the sequential LUN IDs. So when I add a new vv to an exported vvset. I might be failed, because of the duplicated LUN ID..
I check the OS 3.2.2MU3 release notes. Seems that it is fixed in 3.2.2 MU3. But I tried in the 3.2.2 MU3 and MU4 3par, still met the duplicated LUN ID problem... So is it an issue(may be fixed in the future) or it's the mandatory condition that the LUN ID in the vvset must be continuous?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2017 12:30 PM - edited 10-25-2017 12:31 PM
10-25-2017 12:30 PM - edited 10-25-2017 12:31 PM
SolutionWhen created, VLUNs must be sequential and continuous.
Let's say we have a volume set called MySet with the following volumes and VLUNs:
MyVolA -- 1
MyVolB -- 2
MyVolC -- 3
MyVolD -- 4
MyVolE -- 5
Before 3.2.2 MU3, the VLUNs of MySet had to always be contiguous. If we wanted to remove MyVolC from the set, we first had to remove MyVolE and MyVolD. As of 3.2.2 MU3, we could remove just MyVolC leaving a gap in the assigned VLUN numbers. After removing MyVolC we would still have:
MyVolA -- 1
MyVolB -- 2
MyVolD -- 4
MyVolE -- 5
But: When exporting a volume set, the VLUNs must be sequential and contiguous. If we unexport MySet and later re-export MySet starting with LUN 1, we would have
MyVolA -- 1
MyVolB -- 2
MyVolD -- 3
MyVolE -- 4
"D" and "E" are now LUNs 3 and 4, whereas before they were 4 and 5.
Anytime you are using Volume Sets, you must keep track of the VLUN starting points. If you assign other volumes or volume sets, you must plan for any growth of the existing volume set(s). So with MySet starting at VLUN 1, we would want to export any subsequent volumes to our host starting with, for example, LUN 11. or 21. This would allow us to add some volumes to MySet expanding its list of VLUNs before colliding with the higher VLUN number.
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
10-30-2017 07:24 PM
10-30-2017 07:24 PM
Re: VVset cannot grow because of the duplicated LUN ID
Thanks. enlightening answer!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2017 03:39 PM
11-04-2017 03:39 PM
Re: VVset cannot grow because of the duplicated LUN ID
>If we wanted to remove MyVolC from the set, we first had to remove MyVolE and MyVolD. As of 3.2.2 MU3, we could remove just MyVolC leaving a gap
Hmm, I thought this was a day one feature of having gaps due to removevvset.