As a reminder, from the host, you can always issue the following command to view what exports are available:  showmount -ae ip  That is, unless you have set the dm parameter: forceFullShowmount to 0 which hides the exports.  Default is 1 though.   Also, with this new feature, if you are performing this to take advantage of the ability to replicate the VDM along with the NFS exports (as we all know, in the past you had to recreate the exports when bringing the filesystem online on the target), you have to attach the interface to the vdm.  For instance:  1) nas_server -vdm  -attach   2) nas_server -info -vdm   Interfaces to services mapping: Interface: : vdm    <= this will confirm the interface is attached    On the other hand, if you do not attach the interface to the vdm, then for backwards/legacy support, it would behave as we are used to prior to the introduction of this new feature and you would mount using the root_vdm_# path.  IMPORTANT: when bringing the NFS environment online on the target, you have to failover/switchover/reverse the filesystem first then the vdm (not necessarily required with CIFS).  Also, as was the case with CIFS, it will need a same named interface on the target.
Hi all, I'm trying to implement nfs export with DM, and I can successfully export the filesystem. But When I try to mount it I always recieve error from the linux box. I think that I don't use the correct mount command on linux...I've done several tests but I don't understand which command and which parameters I've to use on linux side  VNX export command  server_export vdm-dr -P nfs -name "backup-oracle" -o root=192.168.1.1,access=192.168.1.2 /fs-dr01/backup/backup-oralce1  linux mount command mount -t nfs -o rw 192.168.1.10:/???  thanks  Matteo
VDM NFS export dart 7.0.51-3