Force TCP NFS Mount with TCP/IP 5.6

[Vuffray Joris]

Hi,
I'm trying to force an openvms system to mount an NFS share over TCP instead of udp.
Is there a special mount command to do that?

[Wim Van den Wyngaert]

ucx set servi nfs/port=xxx/prot=tcp ?

Don't have a system to test it.

Wim

[Wim Van den Wyngaert]

Doesn't work.

http://h71000.www7.hp.com/doc/83final/6526/6526pro_051.html#nfs_logical_sec

Check tcp_threads params.

Wim

[Vuffray Joris]

I'll check that.

Thanks for the link...

Rgds, Joris

[Wim Van den Wyngaert]

For the client part it's not that clear. Unix clients can use mount /protocol (or equiv) but VMS seems to have no option.

The info on service level is simply not used. It's simply a db that a service may read to get params but it's not obliged to do so.

Wim

[Vuffray Joris]

I've just tried to skip upd on the NFS Server side (RHEL4), but the VMS Client is then unable to connect & mount the FileSystem.
got:
-SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node

Strange...

I'm wondering if TCP is really supported by the client.

[Wim Van den Wyngaert]

Oeps. Didn't notice that you only need the client. Whatever. I learned already something.

Could it be that portmapper is used to find the protocol ? Ot says something in the log file about MOUNT and protocol.

Wim

[Wim Van den Wyngaert]

Tried it on TCP 5.3. VMS to VMS. Not working either. Can't force the client into TCP.

I did succeed in getting a hang of the NFS server. Stop/id and disable servi didn't work. After a reboot my client still didn't work. Had to reboot the client too. Nice ...

Wim

[Vuffray Joris]

TCP for the NFS Client is a new feature of the 5.6 Version; so it won't work with 5.3

[Wim Van den Wyngaert]

The server is clearly supported in 5.3 eco 2.

How do you specify the client tcp mode ?

Wim