alli87
asked on
Iscsi Storage in VMware
Good Morning,
I recently added some Iscsi storage to an esxi host a nd did all the bindings for it to come. When I check the storage adapters its is showing the paths to the storage . However, I dont see it added as a datastore.
I recently added some Iscsi storage to an esxi host a nd did all the bindings for it to come. When I check the storage adapters its is showing the paths to the storage . However, I dont see it added as a datastore.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I can see there is LUN0 presented.
How large have you made this LUN?
is this a new LUN or re-used LUN?
How large have you made this LUN?
is this a new LUN or re-used LUN?
ASKER
The size of the Lun is 3.41 TB . I have migrated two virtual machines to this Lun from another Host . However I want to get this host to see the same Lun now.
What version of ESX? 4.x?
Max size of LUN is 2TB-512bytes
Max size of LUN is 2TB-512bytes
Configuration Maximums for VMware vSphere 4.1
http://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdf
http://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdf
ASKER
My Apologies , The size of the volume is 1.3 TB. See the attached file showing the volume on the host .
Volume-Size.PNG
Volume-Size.PNG
this lun is used on another hosts?
ASKER
Yes it is
it's not VMFS 5?
ASKER
No its a VMFS 4 volume
so this single 1.3TB LUN VMFS3 is presented two other hosts and is working?
ASKER
It is Presented to one other host and is working
try the following esxcfg-volume -l
example output
~ # esxcfg-volume -l
VMFS3 UUID/label: 4cc89503-f054d0d4-2865-002 21958e471/ nas3-vmfs
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.600140588e9bab7d2b7ed4 b53dadc1de :1 range: 0 - 1048319 (MB)
and then
esxcfg-volume -m 4cc89503-f054d0d4-2865-002 21958e471 (UUID from above)
or
esxcfg-volume -m nas3-vmfs (or friendly datastore name)
example output
~ # esxcfg-volume -l
VMFS3 UUID/label: 4cc89503-f054d0d4-2865-002
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.600140588e9bab7d2b7ed4
and then
esxcfg-volume -m 4cc89503-f054d0d4-2865-002
or
esxcfg-volume -m nas3-vmfs (or friendly datastore name)
ASKER
When I run this command (esxcfg-volume -l) it goes back to the root prompt with no error. I am not sure if this means it is successful but I do not get the output you get above .
if means it cannot find any volumes.
ASKER
Ok , I also just restarted the hosts and still no luck.
Create a new lun and present to this host as a test
ASKER
I created a new lun and presented it to the second host and the same thing happens , it comes up under storage adapters but not under datastore.
Lun-test.PNG
Lun-test.PNG
did you try presenting to the first host?
or is the second host, the host you are having issue with?
when you click add storage the LUN does not appear?
when you click add storage the LUN does not appear?
there must be something wrong on this host, or configured differently to the other.
ASKER
The new Lun has now come up for all hosts
ASKER
Correction it appears for all the hosts in the add storage section . However when I try to add it to hosts two and three I get an error . When i try to add it to the first host i get through . I know there is a problem with Hosts two and three but do you have any idea what it could be ?
error message is?
ASKER
Call "HostDatastoreSystem.Creat eVmfsDatas tore" for object "datastoreSystem-224" on vCenter Server "friedrice.MEDIANET.local" failed.
Operation failed, diagnostics report: Unable to create Filesystem, please see VMkernel log for more details.
Operation failed, diagnostics report: Unable to create Filesystem, please see VMkernel log for more details.
okay, is this a new LUN, or a reused LUN, often errors occur like this is because the lun, is reused and may have existing partitions or data that cannot be deleted or erased.
check the vmkernel.log for further details, from the console
check the vmkernel.log for further details, from the console
ASKER
Is there anything specific to look for in them ? I have been looking at them for the past half hour and I'm not seeing anything popping out at me.
is this a newly created lun or old lun?
ASKER
Its a new one i created after having the problem with the initial 1.3 Tb LUN
whats the size?
ASKER
5 GB
5 GB? that' small?
ASKER
Yeh I just created one just big enough to come up under vmware . Do you think the size is an issue ?
try a larger LUN 20GB
ASKER
I just tried with a 600 GB LUN while giving access to only one host and still got the same error
ASKER
I Have tried another combination buy configuring a new server with ESXi and adding the same 1.3TB LUN through Iscsi and it comes up with no problems . This means the issue is with the Dell R610. I tried reinstalling ESXi on the R610 and redoing the entire configuration and still it does not come up , however when I connect to it I do not get the error anymore . I have also checked the BIOS and all virtualization features are enabled there . Any ideas what could be the difference with the R610 ?
it would be time to check the logs on the ESXi server
see here
http://xtravirt.com/vmware-esxi-4-log-files
see here
http://xtravirt.com/vmware-esxi-4-log-files
ASKER
Iscsi-Paths.PNG
Iscsi-Paths-2.PNG