- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - VMware
- >
- ESX and continuous access
Operating System - VMware
1748181
Members
3712
Online
108759
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
тАО08-04-2010 12:47 PM
тАО08-04-2010 12:47 PM
Hi
When using continuous access between 2 EVA's + vsphere (no srm) and when ESX server is shut down and luns are failed over to the secondary EVA, the same server is booted up with access to luns on secondary EVA, is it then necessary to do a add storage on the ESX server to see the luns again?
-inex
When using continuous access between 2 EVA's + vsphere (no srm) and when ESX server is shut down and luns are failed over to the secondary EVA, the same server is booted up with access to luns on secondary EVA, is it then necessary to do a add storage on the ESX server to see the luns again?
-inex
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2010 11:59 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2010 01:29 PM
тАО08-05-2010 01:29 PM
Re: ESX and continuous access
yes, we will test this, but I do know what kind of factors you are thinking of here
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2010 11:21 PM
тАО08-05-2010 11:21 PM
Re: ESX and continuous access
I have not seen a detailled description of all the factors ESX uses to try telling the difference between the original volume and a snapshot/clone/replication in once single place and when a specific item is applied - maybe it does not even exist.
A commonly known item is the LUN address (sometimes called the "LUN ID" or "LUN Number"/"LUN #").
Another one is the "SCSI inquire string". I don't know if it is still used in current ESX 4.x, but in previous versions it was used, too. This was noticed when one did replicate between different EVA controller models, e.g. EVA8000 (HSV210) and EVA4000/6000 (HSV200).
And then there is the "LUN WWN" (a 128-bit value starting with "6" and provided in a SCSI page), which in most cases is identical to the virtual disk's internal UUID. It is sometimes called the "LUN ID" or "LUN serial number".
If the old one gets lost due to a snapclone, mirror clone or maybe after a CA failover, you can modify the virtual disks's "LUN WWN" back as long as the vdisk is not presented. But make sure no other vdisk uses the same value.
I've put together some VMware Knowledge Base articles you might find interesting to read.
1005751 - Resignaturing VMFS3 volumes from the command line
http://kb.vmware.com/kb/1005751
1011387 - ESX/ESXi 4.x handling of LUNs detected as snapshot
http://kb.vmware.com/kb/1011387
1015986 - Force mounting a VMFS datastore residing on a snapshot LUN results in the error: Cannot change the host configuration
http://kb.vmware.com/kb/1015986
1017469 - Missing LUNS after upgrading to ESX/ESXi 3.5 Update 5 or ESX/ESXi 4.x
http://kb.vmware.com/kb/1017469
A commonly known item is the LUN address (sometimes called the "LUN ID" or "LUN Number"/"LUN #").
Another one is the "SCSI inquire string". I don't know if it is still used in current ESX 4.x, but in previous versions it was used, too. This was noticed when one did replicate between different EVA controller models, e.g. EVA8000 (HSV210) and EVA4000/6000 (HSV200).
And then there is the "LUN WWN" (a 128-bit value starting with "6" and provided in a SCSI page), which in most cases is identical to the virtual disk's internal UUID. It is sometimes called the "LUN ID" or "LUN serial number".
If the old one gets lost due to a snapclone, mirror clone or maybe after a CA failover, you can modify the virtual disks's "LUN WWN" back as long as the vdisk is not presented. But make sure no other vdisk uses the same value.
I've put together some VMware Knowledge Base articles you might find interesting to read.
1005751 - Resignaturing VMFS3 volumes from the command line
http://kb.vmware.com/kb/1005751
1011387 - ESX/ESXi 4.x handling of LUNs detected as snapshot
http://kb.vmware.com/kb/1011387
1015986 - Force mounting a VMFS datastore residing on a snapshot LUN results in the error: Cannot change the host configuration
http://kb.vmware.com/kb/1015986
1017469 - Missing LUNS after upgrading to ESX/ESXi 3.5 Update 5 or ESX/ESXi 4.x
http://kb.vmware.com/kb/1017469
.
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