New ESX 4.1 Host Cannot Find Existing Extend VMFS

[Pound]

Hi,

I have provisioned new ESX server using ESX 4.1.0, 381591. Everything works fine including join the cluster, apply host profile, and distributed network configuration except the host itself cannot find the existing VMFS datastore when using "Add Storage" wizard. This datastore is extend from 4 LUNs. Each LUN is 1.5 TB. and the total is 6TB.

• When clicking "Device" button in Configuration > Storage tab, it can show all LUNs including RDM LUNs.
• When direct connect to the host, I can see all LUNs in Add Storage wizard but it said it is blank LUNs.
• I cannot see this extend LUN neither log in to vCenter nor direct log in to the host.

I am not sure that there are special instructions for adding existing extend VMFS volume to new hosts. Can anyone suggest?

Best Regards,

Teeravee Sirinapasawasdee (Pound)

[smiler1]

Hi Teeravee

did you get anywhere with this? I am having exactly the same problem.

Regards

Steve

[AndreTheGiant]

Do you have iSCSI storage?

There can be some issue if MTU does not match... See last post in: http://communities.vmware.com/message/1739389

Andre

[smiler1]

no all fibre channel.

A bit more information about our environment. 

We have 5 ESXi4.1 Servers in the cluster all seeing the storage without any problem. We have just added 3 new ones, exactly the same hardware and software and they can all see the LUNs at the hardware level, so when I click on Storage>Devices I can see the LUNS.

When I try and add the datastores through the Add Storage option the LUNs do not come up. If I connect with Vsphere directly to the esx host rather than through the Vcenter server and go to Add storage the LUNs appear but the only option is for me to format the LUNs, which I obviously do not want to do.

All very strange

Steve

[Pound]

No I didn't get any solution. :'(

Sent from my iPhone via Hosted Exchange by GTIS

[Pound]

No, my storage is FC (IBM DS3400).

Sent from my iPhone via Hosted Exchange by GTIS

[AndreTheGiant]

I suggest to open a call to VMware support.

Another problem could be related to VAAI, but your storage does not support VAAI...

Andre