NFS Share was set up some time ago by SAN technician and didn't really remember any settings but did a double check and of course there was a list of allowed IP for read/write access. That shouldn't have been a problem cause all servers were there but with the wrong IP address for my old ESXi servers. A vmkernel was setup afterwards with IP address in the same scope as NFS. That must be the best way right? Seems like a bad idea to have NFS attached on a routed link?? Feels like I will need to add a vmk on the new servers as well in the NFS scope. As for now traffic is routed through firewall and we got some serious issues with that traffic. I edited settings as mentioned above and I got the read/write access. Tried to vmotion from old hosts, worked fine, but when I started on new host with routed NFS access I got horrendous latency, it works but this is no good way to migrate servers. Thanks for your input, one problem solved, peetz
Trying to give you some creds here but it's not working... try again later.