Sorry for the delay..this time on my side.. I've did some resarch and maybe got the solution for you.
Basically what I see is the what you did is all correct, as long I ask you just to check a couple of things before go what I wrote below, the real issue you got is the way the VM present its newly WWN to the Storage. So here's what you have to check and note.
First of all the check:
inside the ESX type:
#ls /proc/scsi/qla2300
This will help you to find the right hba to search through. Once you got the right number (i.e. 6) type:
# cat /proc/scsi/qla2300/6
This will help you to see if there is traffic through the HBA, you should have an output similar to this:
Virtual Port 1 SCSI LUN Information:
( 0:10): Total reqs 10, Pending reqs 0, flags 0x0, 2:0:1000,
Retry the command once the VM is powerd on:
# cat /proc/scsi/qla2300/6
This time you should see something like this:
FC Port Information for Virtual Ports:
Virtual Port index = 1
Virtual Port 1:VP State = <ACTIVE>, Vp Flags = 0x0
scsi-qla2-port-3=500601609020fd54:500601601020fd54:a00000:1000: 1;
scsi-qla2-port-4=500601609020fd54:500601681020fd54:a10000:1000: 1;
Virtual Port 1 SCSI LUN Information:
( 0:10): Total reqs 10, Pending reqs 0, flags 0x0, 2:0:1000,
now if everything seems ok let's try this:
Download the vmx file from the VM and check the entry similar to these:
wwn.node = “25bb000c29000ba5″
wwn.port = “25bb000c29000da5,25bb000c29000ca5,25bb000c29000ea5,25bb000c29000fa5″
wwn.type = “vc”
these are you what you need to zone..
When the VM is powered on, before the virtual hardware POSTs, it scans the physical HBAs of the ESX host for the RDM mapping to SAN storage. If an HBA doesn’t support NPIV, it is skipped in the detection process. If ESX cannot see the zoned RDM LUN through an NPIV aware HBA, again the HBA is skipped in the detection process.
So first suggestion is to ask your storage admin to manually zone the wwn you just found on the fabric, IMHO I would create 2 different zone one for the host and one for the VM in order to avoid unusual traffic from and to the VM/Host.
ESX will assign a maximum of four NPIV Port WWNs during the detection process. What this means is that if you have four NPIV HBAs connected to four NPIV aware SAN switch ports which are in turn zoned to four SAN LUNs, all four will be NPIV activated. If you have only one NPIV HBA, you’ll only use one of the virtual Port WWNs. If you have six NPIV HBAs, only the first four will be activated with NPIV Port WWNs in the discovery process.
So in my lab test to get things work I tried to disable the zoning and check if everything worked..once I've got the correct WWN I re-zoned all.
I am aware that probably in your enviroment you cant do that easily so the only way is to catch through the storage switch screen if the wwn comes online or not (it require a great eyes since a VM comes online for HBA scan for less than 1 sec) or try with a manual zoning of the WWN created.
Last bu not least remeber that if you regenerated the WWN is better to unregister the VM from the inventory and re-add since Vic use to mantain information on a created WWN VM.
Hope this could solve your problem.
Alex
