- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- How to change the LUN ID of the VV online(preferab...
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
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
11-12-2018 11:09 PM
11-12-2018 11:09 PM
- Different LUN ID showing for Replicated LUNs
Please find the screenshot of identifier and associated LUN ID from both DC.
Our ESXi team is encountering with below issue and they want the LUN ID on the both arrays to be same to rectify it as per the solution mentioned there.
https://kb.vmware.com/s/article/2054897
Troubleshooting :
- We logged into IMC and 3PAR CLI and found this is not a PP Metro Cluster Issue.
- PP Metro Cluster perspective from 3PAR side it is working fine as manually created VVset is exported and ESX hosts are able to see those LUNs.
- While exporting that VVset from ESX to individual VM as RDM, VMs are unable to see the LUN and not visible and got error : Incompatible device backing specified for device ‘0’
- While checking further, we found that LUN ID 59 on target has already been occupied by other VV due to which other LUN ID 81 has been assigned as ID 59 was not available.
I work for HPE
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2018 02:06 AM - edited 11-13-2018 02:07 AM
11-13-2018 02:06 AM - edited 11-13-2018 02:07 AM
SolutionThey are right, the LUN ID should be the same for the Primary and Secondary (Mirror) Volumes and all ESX Hosts and only between the Volumes make it unique.
But it is the choice of the 3PAR Admin to choose the right LUN ID.
Somtimes I have customers they choose "Auto" by LUN ID assigment and this results in mixed LUN IDs.
So, what can you do now:
Create a Table with all Exported Volumes and the used LUN ID for both Storage.
Unpresent the secondary Volume (Mirror Side of the Volume) and represent it with the same ID as the primary.
Do it in the way, that you have no double assingment, avoid: Volume 1 = LUN ID 10 and Volume 2 = LUN ID 10
Because all Secondary Volumes are Standby in ESX you can do it online.
Rescan the hole Cluster at the end.
