mount nfs share on NETAPP FAS3040A failed with "remote node is unknown"

[tongrenyuan]

I am on 8.4 update1000 IA64 openVMS. when i try to mount NFS share on the NETAPP fas3040a  it fails with following error:
$ tcpip mount dnfs100: /host="129.115.6.11" /path="/vol/cifstest1"
%TCPIP$DNFSMOUNT-E-MOUNTFAIL, error mounting _DNFS100:[000000]
-SYSTEM-F-NOSUCHNODE, remote node is unknown
$ ping 129.115.6.11
PING 129.115.6.11 (129.115.6.11): 56 data bytes
64 bytes from 129.115.6.11: icmp_seq=0 ttl=255 time=1 ms
64 bytes from 129.115.6.11: icmp_seq=1 ttl=255 time=1 ms
64 bytes from 129.115.6.11: icmp_seq=2 ttl=255 time=0 ms
*CANCEL*

----129.115.6.11 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/1/1 ms
$

$ tcpip show version

HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 2
on an HP Integrity BL860c i2 (1.60GHz/5.0MB) running OpenVMS V8.4

$

The share is ok for other linux client, for suse client:

linux:~ # cat /etc/SuSE-release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 1
linux:~ # mount 129.115.6.11:/vol/cifstest1 /mnt/
linux:~ # mount
/dev/sda2 on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
devtmpfs on /dev type devtmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,mode=1777)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev)
/dev/sr0 on /media/SLES-11-SP1-DVD-x86_64.0432..001_ type iso9660 (ro,nosuid,nodev,uid=0)
129.115.6.11:/vol/cifstest1 on /mnt type nfs (rw,addr=129.115.6.11)
linux:~ #

[tongrenyuan]

so I  think it maybe the nfs client problem in my openvms. the information:

 $ tcpip show service/full

Service: MOUNT
State: Disabled
Port: 10 Protocol: TCP,UDP Address: 0.0.0.0
User_name: not defined Process: TCPIP$MOUNTD

Service: NFS
State: Enabled
Port: 2049 Protocol: UDP Address: 0.0.0.0
Inactivity: 0 User_name: TCPIP$NFS Process: TCPIP$NFS
Limit: 1 Active: 0 Peak: 0

File: TCPIP$SYSTEM:TCPIP$NFS_RUN.COM
Flags: None

Socket Opts: Rcheck Scheck
Receive: 64000 Send: 64000

Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
File: SYS$SYSDEVICE:[TCPIP$NFS]TCPIP$NFS_RUN.LOG

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

Service: PORTMAPPER
State: Enabled
Port: 111 Protocol: TCP,UDP Address: 0.0.0.0
Inactivity: 0 User_name: TCPIP$PORTM Process: TCPIP$PORTM
Limit: 10 Active: 0 Peak: 0

File: TCPIP$SYSTEM:TCPIP$PORTM_RUN.COM
Flags: None

Socket Opts: Rcheck Scheck
Receive: 0 Send: 0

Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
File: SYS$SYSDEVICE:[TCPIP$PORTM]TCPIP$PORTM_RUN.LOG

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

Service: REXEC
State: Enabled
Port: 512 Protocol: TCP Address: 0.0.0.0
Inactivity: 5 User_name: not defined Process: TCPIP$REXEC
Limit: 300 Active: 0 Peak: 0

File: TCPIP$SYSTEM:TCPIP$REXEC_RUN.COM
Flags: Listen Rexe IPv6

Socket Opts: Rcheck Scheck
Receive: 0 Send: 0

Log Opts: Acpt Actv Dactv Error Exit Mdfy Rjct TimO Addr
File: not defined

Separators:
Port: 0 User_name: 0 Password: 0 Command: 0

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

Service: RLOGIN
State: Enabled
Port: 513 Protocol: TCP Address: 0.0.0.0
Inactivity: 1 User_name: not defined Process: not defined
Limit: 5000 Active: 0 Peak: 0

File: not defined
Flags: Case Listen Proxy Rlog Rtty IPv6

Socket Opts: Keepalive Rcheck Scheck
Receive: 3000 Send: 3000

Log Opts: Acpt Actv Dactv Conn Error Logi Logo Mdfy Rjct TimO
File: not defined

Security
Reject msg: TCPIP RLOGIN Connection refused
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

Service: RSH
State: Enabled
Port: 514 Protocol: TCP Address: 0.0.0.0
Inactivity: 5 User_name: not defined Process: TCPIP$RSH
Limit: 300 Active: 0 Peak: 0

File: TCPIP$SYSTEM:TCPIP$RSH_RUN.COM
Flags: Case Listen Proxy Rexe IPv6

Socket Opts: Rcheck Scheck
Receive: 0 Send: 0

Log Opts: Acpt Actv Dactv Conn Error Exit Mdfy Rjct TimO Addr
File: not defined

Separators:
Port: 0 User_name: 0 Password: 0 Command: 0

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0

Service: SMTP
State: Disabled
Port: 25 Protocol: TCP Address: 0.0.0.0
User_name: not defined Process: TCPIP$SMTP

Service: TELNET
State: Enabled
Port: 23 Protocol: TCP Address: 0.0.0.0
Inactivity: 1 User_name: not defined Process: not defined
Limit: 10000 Active: 1 Peak: 1

File: not defined
Flags: Listen Rtty IPv6

Socket Opts: Keepalive Rcheck Scheck
Receive: 3000 Send: 3000

Log Opts: Actv Dactv Conn Error Logi Logo Mdfy Rjct
File: not defined

Security
Reject msg: not defined
Accept host: 0.0.0.0
Accept netw: 0.0.0.0
$
$ 

[Volker Halle · Accepted solution]

The error message issued from the TCPIP NFS client is: SYSTEM-F-NOSUCHNODE, remote node is unknown

Does your DNS name resolver work ?

Try $ TCPIP SHOW HOST FAS3040A or $ TCPIP PING FAS3040A - if both fail, start with $ TCPIP SET HOST fas3040a/addr=129.115.6.11 then try again.

Once you've overcome this problem, you need to familiarize yourself with TCPIP PROXIES, as NFS access is based on UID and GID, which needs to be mapped via the OpenVMS TCPIP PROXY database from the OpenVMS username to UID/GID pairs to the remote NFS server.

Volker.

[Steven Schweda]

   I'm not a big user of NFS on VMS, so I know nothing, but...

> [...] when i try to mount NFS share [...]

   Did this work before, or is this the first time you've tried it?  Can
you mount anything else on this system?

> -SYSTEM-F-NOSUCHNODE, remote node is unknown
> $ ping 129.115.6.11
> PING 129.115.6.11 (129.115.6.11): 56 data bytes

   Does the NFS client expect a reverse (address-to-name) DNS look-up to
work?  (Can you mount anything where the DNS data are available?)

> Service: REXEC
> [...]
> Service: RLOGIN
> [...]
> Service: RSH
> [...]
> Service: SMTP
> [...]
> Service: TELNET
> [...]

   Nothing to do with NFS.

> Service: MOUNT
> State: Disabled

   I believe that MOUNT (and LOCKD and STATD) are parts of the NFS
server, so they may not matter for the client.

   Have you been through SYS$MANAGER:TCPIP$CONFIG.COM to enable and
start the "Client components > NFS Client" component?

[tongrenyuan]

Thanks for you reply. After add "tcpip set host fas3040a/addr=129.115.6.11",the mount is ok.

But i do not understand that  "needs to be mapped via the OpenVMS TCPIP PROXY database from the OpenVMS username to UID/GID pairs to the remote NFS server." ,,it is must to be ? My nfs server is netapp storage, not VMS server.

$tcpip mount dnfs100: /host="fas3040a" /path="/vol/cifstest1"

and it can be used now.

[tongrenyuan]

Thanks for your reply!

[Volker Halle]

But i do not understand that  "needs to be mapped via the OpenVMS TCPIP PROXY database from the OpenVMS username to UID/GID pairs to the remote NFS server." ,,it is must to be ? My nfs server is netapp storage, not VMS server.

If it works and you don't care about security, so be it...

Otherwise you'll need to work with UID/GID to make sure, only specific users can read/write/delete your files on your NetApp NFS server.

Volker.