Failure to mount disk on NFS client

[Rajeev Hejib]

I get following error:

SMIV14 » tcpip mount dnfs201: /host=smiv96/path="/nfsdsa201"
%TCPIP$DNFSMOUNT-E-MOUNTFAIL, error mounting _DNFS201:[000000]
-SYSTEM-F-INVLOGIN, login information invalid at remote node

Same works on other node

SMIV15 » tcpip mount dnfs201: /host=smiv96/path="/nfsdsa201"
%TCPIP$DNFSMOUNT-S-MOUNTED, /nfsdsa201 mounted on _DNFS201:[000000]

NFS Server is on Alpha 4100 with
OpenVms 7.3-1
TCP/IP V5.3 - ECO 2

NFS Client with problem is on MicroVAX 3100-95 with
OpenVms 7.1
TCP/IP V5.0

NFS Client where it works is on MicroVAX 3100-95 with
OpenVms 7.1
TCP/IP V5.0A

Only difference I see is with TCP/IP version. I am mounting the disk as user - system

Proxies on NFS server
VMS User_name Type User_ID Group_ID Host_name
DECEDI OND 1 1100 SMIV15, smiv15, SMIV14,smiv14
EDI_GATEWAY OND 0 1100 SMIV15, smiv15, SMIV14,smiv14
EDI_WATCHDOG OND 2 1100 SMIV15
SYSTEM OND 4 1 smiv15, SMIV15, smiv14,SMIV14
TCPIP$NOBODY OND -2 -2 smiv96, SMIV15, smiv15

Can someone please help? Than

[Wim Van den Wyngaert]

Did you restart the NFS server ? In pre-5 this was often needed because the server cached certain info.
Did you check for intrusions ?

Wim

[Daniel Fernandez Illan]

Error indicates that login to mount isn't valid in remote node. Are you check permission of mount for SIMV96 node from SIMV14?

Saludos.
Daniel.

[Daniel Fernandez Illan]

Sorry.
Check export of /nfsdsa201 on NFS server.
Is activated to SIMV14 node?.

Saludos.
Daniel.

[Rajeev Hejib]

Thanks guys for your help. I have tried it and it still fails.

I have stopped and restarted NFS server on SMIV96. There are no intrusions.
export on SMIV96 is
SMIV96:MGR> ucx show export

File System Host name

/nfsdsa200 *
/nfsdsa201 *

and
SMIV96:MGR> ucx show map
Dynamic Filesystem Map
Pathname Logical File System

/nfsdsa200 DSA200:
/nfsdsa201 DSA201:
SMIV96:MGR>

When I did reply/enable on SMIV96 and mounted the disk on SMIV14 I get following on SMIV96

SMIV96:MGR>
%%%%%%%%%%% OPCOM 24-MAY-2005 15:09:48.93 %%%%%%%%%%%
Message from user TCPIP$NFS on SMIV96
%TCPIP-S-NFS_MNTSUC, mounted file system /nfsdsa201
-TCPIP-S-NFS_CLIENT, uid=-2 gid=-2 host_name = SMIV14


SMIV96:MGR>
%%%%%%%%%%% OPCOM 24-MAY-2005 15:09:48.95 %%%%%%%%%%%
Message from user TCPIP$NFS on SMIV96
%TCPIP-S-NFS_UMNSUC, file system /nfsdsa201 is unmounted
-TCPIP-S-NFS_CLIENT, uid=-2 gid=-2 host_name = SMIV14


SMIV96:MGR>

IT DOES mount the disk but dismounts immediately and gives following error on client (SMIV14)


and on SMIV14 following
MIV14 » ucx mount dnfs201:/host=smiv96/path="/nfsdsa201"
TCPIP$DNFSMOUNT-E-MOUNTFAIL, error mounting _DNFS201:[000000]
SYSTEM-F-INVLOGIN, login information invalid at remote no

[Rajeev Hejib]

Thanks very much guys for your help. I have tried it and it still fails.

I have stopped and restarted NFS server on SMIV96. There are no intrusions.
export on SMIV96 is
SMIV96:MGR> ucx show export

File System Host name

/nfsdsa200 *
/nfsdsa201 *

and
SMIV96:MGR> ucx show map
Dynamic Filesystem Map
Pathname Logical File System

/nfsdsa200 DSA200:
/nfsdsa201 DSA201:
SMIV96:MGR>

When I did reply/enable on SMIV96 and mounted the disk on SMIV14 I get following on SMIV96

SMIV96:MGR>
%%%%%%%%%%% OPCOM 24-MAY-2005 15:09:48.93 %%%%%%%%%%%
Message from user TCPIP$NFS on SMIV96
%TCPIP-S-NFS_MNTSUC, mounted file system /nfsdsa201
-TCPIP-S-NFS_CLIENT, uid=-2 gid=-2 host_name = SMIV14


SMIV96:MGR>
%%%%%%%%%%% OPCOM 24-MAY-2005 15:09:48.95 %%%%%%%%%%%
Message from user TCPIP$NFS on SMIV96
%TCPIP-S-NFS_UMNSUC, file system /nfsdsa201 is unmounted
-TCPIP-S-NFS_CLIENT, uid=-2 gid=-2 host_name = SMIV14


SMIV96:MGR>

IT DOES mount the disk but dismounts immediately and gives following error on client (SMIV14)


and on SMIV14 following
MIV14 » ucx mount dnfs201:/host=smiv96/path="/nfsdsa201"
TCPIP$DNFSMOUNT-E-MOUNTFAIL, error mounting _DNFS201:[000000]
SYSTEM-F-INVLOGIN, login information invalid at remote no

[Wim Van den Wyngaert]

Note the -2 in the opcom messages. Indicates "tcpip$nobody" according to your proxy setup. I think you need to define an O(outgoing) proxy on the client side. Compare with the working system. It should map the SYSTEM account.

Wim

[Rajeev Hejib]

Still get the same error. Here is what I have on proxies

Working

SMIV15 » ucx show proxy tcpip*

VMS User_name Type User_ID Group_ID Host_name

TCPIP$NOBODY ON -2 -2 smiv14,
sizzle.service.britgas.co.uk
SMIV15 » ucx show proxy system

VMS User_name Type User_ID Group_ID Host_name

SYSTEM ON 4 1 SMIV96, SMIV15, smiv15




No working

SMIV14 » ucx show proxy tcpip*

VMS User_name Type User_ID Group_ID Host_name

TCPIP$NOBODY ON -2 -2 SMIV96,smiv96


SMIV14 » ucx show proxy system

VMS User_name Type User_ID Group_ID Host_name

SYSTEM ON 4 1 SMIV96,smiv96, SMIV14

[Rajeev Hejib]

Still get the same error. Here is what I have on proxies

Working

SMIV15 » ucx show proxy tcpip*

VMS User_name Type User_ID Group_ID Host_name

TCPIP$NOBODY ON -2 -2 smiv14

SMIV15 » ucx show proxy system

VMS User_name Type User_ID Group_ID Host_name

SYSTEM ON 4 1 SMIV96, SMIV15, smiv15




No working

SMIV14 » ucx show proxy tcpip*

VMS User_name Type User_ID Group_ID Host_name

TCPIP$NOBODY ON -2 -2 SMIV96,smiv96


SMIV14 » ucx show proxy system

VMS User_name Type User_ID Group_ID Host_name

SYSTEM ON 4 1 SMIV96,smiv96, SMIV14

[Wim Van den Wyngaert · Accepted solution]

Note that smiv96 (in lowercase) is not present in the not working part of SYSTEM.


Wim