2010-10-11 12:58 PM
I am attempting to configure the VSC Provisioning and Cloning functionallity in a vCenter 4.1 (backend ESX 4.0) environment. Everytime I try and add the storage controller, it just sits there for a long time, then finally comes back with a timeout error. This storage system has multiple IP addresses associated with it (1 for management, 1 for CIFS, 1 for iSCSI and 1 for NFS). I have tried using both the managment and CIFS ip connections with the same results. The iSCSI and NFS networks are not routeable, so I am unable to talk with them directly from the vCenter server (a common configuration, I would imagine).
I have looked at the filer options that seemed relevant to this, but am still not having any luck. I am open to any and all suggestions at this point.
2010-10-11 11:42 PM
I’m wondering if you hit this error because of the temp NFS license not being there. Take a look at this thread
2010-10-12 07:28 AM
Unfortunately, that is not the case. This system is fully licensed for NFS (along with just about everything else). NFS actually is the primary data store type for the VMware environment.
At first I thought it was because of thier legacy firewalled network, but we just re-located the filer to a new datacenter, and the networks are no longer heavily firewalled from one another.
2010-10-28 06:04 AM
Correct, now the link actually works, it didn't a couple of hours ago.
The changelog doesn't mention the "nfs license not installed" bug.
Guess I'll install it in my lab and see what happens.