Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

NFS client Fails

 
Daniel Fernandez Illan
Trusted Contributor

NFS client Fails

Hi guys.

I have a connection between a Alpha Unix system and some Alpha with VMS 7.3.1

When I intend connect from Unix to one VMS using NFS client (mount -t nfs), system shows this message:

Bad MNT RPC: n3:/dkd1: RPC: Timed out

tcptrace in VMS is:

TCPtrace full display RCV packet 41 at 21-JUL-2004 08:53:42.42

IP Version = 4, IHL = 5, TOS = 00, Total Length = 84 = ^x0054
IP Identifier = ^x58DF, Flags (0=0,DF=0,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 30 = ^x1E, Protocol = 17 = ^x11, Header Checksum = ^x1C53
IP Source Address = 192.168.83.10
IP Destination Address = 192.168.83.12

UDP Source Port = 3255, UDP Destination Port = 111
UDP Header and Datagram Length = 64 = ^x0040, Checksum = ^xEBE1

0A53A8C0 531C111E 0000DF58 54000045 0000 E..TX......S..S.
7C1721BA | E1EB4000 6F00B70C | 0C53A8C0 0010 ..S....o.@...!.|
02000000 A0860100 02000000 00000000 0020 ................
00000000 00000000 00000000 03000000 0030 ................
11000000 03000000 A3860100 00000000 0040 ................
00000000 0050 ....




--------------------------------------------------------------------------------

TCPtrace full display XMT packet 43 at 21-JUL-2004 08:53:42.42

IP Version = 4, IHL = 5, TOS = 00, Total Length = 56 = ^x0038
IP Identifier = ^x790B, Flags (0=0,DF=0,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 30 = ^x1E, Protocol = 17 = ^x11, Header Checksum = ^xFC42
IP Source Address = 192.168.83.12
IP Destination Address = 192.168.83.10

UDP Source Port = 111, UDP Destination Port = 3255
UDP Header and Datagram Length = 36 = ^x0024, Checksum = ^xF178

0C53A8C0 42FC111E 00000B79 38000045 0000 E..8y......B..S.
7C1721BA | 78F12400 B70C6F00 | 0A53A8C0 0010 ..S..o...$.x.!.|
00000000 00000000 00000000 01000000 0020 ................
01080000 00000000 0030 ........




--------------------------------------------------------------------------------

TCPtrace full display RCV packet 44 at 21-JUL-2004 08:53:42.42

IP Version = 4, IHL = 5, TOS = 00, Total Length = 84 = ^x0054
IP Identifier = ^x58E0, Flags (0=0,DF=0,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 30 = ^x1E, Protocol = 17 = ^x11, Header Checksum = ^x1C52
IP Source Address = 192.168.83.10
IP Destination Address = 192.168.83.12

UDP Source Port = 3256, UDP Destination Port = 111
UDP Header and Datagram Length = 64 = ^x0040, Checksum = ^xEADE

0A53A8C0 521C111E 0000E058 54000045 0000 E..TX......R..S.
7C1721BB | DEEA4000 6F00B80C | 0C53A8C0 0010 ..S....o.@...!.|
02000000 A0860100 02000000 00000000 0020 ................
00000000 00000000 00000000 03000000 0030 ................
11000000 03000000 A5860100 00000000 0040 ................
00000000 0050 ....




--------------------------------------------------------------------------------

TCPtrace full display XMT packet 45 at 21-JUL-2004 08:53:42.42

IP Version = 4, IHL = 5, TOS = 00, Total Length = 56 = ^x0038
IP Identifier = ^x790C, Flags (0=0,DF=0,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 30 = ^x1E, Protocol = 17 = ^x11, Header Checksum = ^xFC41
IP Source Address = 192.168.83.12
IP Destination Address = 192.168.83.10

UDP Source Port = 111, UDP Destination Port = 3256
UDP Header and Datagram Length = 36 = ^x0024, Checksum = ^xF86E

0C53A8C0 41FC111E 00000C79 38000045 0000 E..8y......A..S.
7C1721BB | 6EF82400 B80C6F00 | 0A53A8C0 0010 ..S..o...$.n.!.|
00000000 00000000 00000000 01000000 0020 ................
0A000000 00000000 0030 ........




--------------------------------------------------------------------------------

TCPtrace full display RCV packet 46 at 21-JUL-2004 08:53:42.42

IP Version = 4, IHL = 5, TOS = 00, Total Length = 108 = ^x006C
IP Identifier = ^x58E1, Flags (0=0,DF=0,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 30 = ^x1E, Protocol = 17 = ^x11, Header Checksum = ^x1C39
IP Source Address = 192.168.83.10
IP Destination Address = 192.168.83.12

UDP Source Port = 3257, UDP Destination Port = 10
UDP Header and Datagram Length = 88 = ^x0058, Checksum = ^xE3A3

0A53A8C0 391C111E 0000E158 6C000045 0000 E..lX......9..S.
7C1721BC | A3E35800 0A00B90C | 0C53A8C0 0010 ..S......X...!.|
03000000 A5860100 02000000 00000000 0020 ................
1611FE40 1C000000 01000000 01000000 0030 ............@...
78000000 02000000 0000316E 02000000 0040 ....n1.........x
00000000 00000000 78000000 01000000 0050 .......x........
00000031 646B642F 05000000 0060 ..../dkd1...




--------------------------------------------------------------------------------

TCPtrace full display XMT packet 47 at 21-JUL-2004 08:53:42.42

IP Version = 4, IHL = 5, TOS = 00, Total Length = 136 = ^x0088
IP Identifier = ^x790D, Flags (0=0,DF=0,MF=0),
Fragment Offset = 0 = ^x0000, Calculated Offset = 0 = ^x0000
IP TTL = 64 = ^x40, Protocol = 1 = ^x01, Header Checksum = ^xDA00
IP Source Address = 192.168.83.12
IP Destination Address = 192.168.83.10

ICMP Type = 3 UNREACH, Code = 3 PORT, Checksum = ^x24CE
ICMP Unused = 00000000

0C53A8C0 00DA0140 00000D79 88000045 0000 E...y...@.....S.
6C000045 | 00000000 CE240303 | 0A53A8C0 0010 ..S...$.....E..l
0C53A8C0 0A53A8C0 391C111E 0000E158 0020 X......9..S...S.
00000000 7C1721BC A3E35800 0A00B90C 0030 .....X...!.|....
01000000 03000000 A5860100 02000000 0040 ................
02000000 1611FE40 1C000000 01000000 0050 ........@.......
01000000 78000000 02000000 0000316E 0060 n1.........x....
05000000 00000000 00000000 78000000 0070 ...x............
00000031 646B642F 0080 /dkd1...

Fails occurs only in one VMS node.
The rest of nodes works well using NFS client and are similar to problematic node.



17 REPLIES
Martin Vorlaender
Honored Contributor

Re: NFS client Fails

I've never learnt to read TCP dumps, so I can't comment on those.

VMS' NFS server prints a lot of OPCOM messages, though. Perhaps those would be helpful to diagnose the problem?

Also the NFS and proxy configuration on the VMS side would be of interest.

cu,
Martin
Daniel Fernandez Illan
Trusted Contributor

Re: NFS client Fails

Problem was caused on VMS node.

I was using TCPIP for VMS 5.0a and NFS server worked fine, but when I upgraded to TCPIP for VMS 5.4 then NFS server doesn't offers mount services (checked this option with showmount Unix command).

I think that the problem takes place by the incompatibility between both versions for this service.

When I was returned to older version, NFS server works well.

Best Regards.
Wim Van den Wyngaert
Honored Contributor

Re: NFS client Fails

Wild guess,

Your Unix is talking with the portmapper on port 111. This sends the Unix node to port 10 on which there is no listener. So, VMS answers UNREACH.

Wim
Wim
Wim Van den Wyngaert
Honored Contributor

Re: NFS client Fails

BTW : port 10 is mount. Check if it is enabled.

Wim
Wim
Daniel Fernandez Illan
Trusted Contributor

Re: NFS client Fails

In this moment I cann't check NFSv configuration because I was returned to older version.

When I update again, I will verify all those points.

Best regards.
Wim Van den Wyngaert
Honored Contributor

Re: NFS client Fails

Make sure to dump the output of all show commands BEFORE the upgrade.

Wim
Wim
Daniel Fernandez Illan
Trusted Contributor

Re: NFS client Fails

Thanks
Daniel Fernandez Illan
Trusted Contributor

Re: NFS client Fails

Problem occurs with tcp/ip version 5.4 migrated from version 5.0 in OVMS system .

If it uses some proxies with same OVMS user,
in older version all proxies are loaded in dynamic memory but the new version only load
the first proxy defined.

To execute a complete load of proxies, It is neccesary to change some parameters to NFS server in new version. This parameters are:

noproxy_enabled = 1
noproxy_uid = -2
noproxy_gid = -2

(Thanks to HP support)
Wim Van den Wyngaert
Honored Contributor

Re: NFS client Fails

Daniel,

What does this solution has to do with the mount service that wasn't offered ?
It seems a solution for a 2nd problem ...

Wim
Wim
Daniel Fernandez Illan
Trusted Contributor

Re: NFS client Fails

I found that the MOUNT service hung and I cound not enable it when use TCP/IP 5.4.
Command

tcpip sho service mount

display "status disable"

when I intend start this service with:

tcpip enable service mount

displays this message:

%TCPIP-I-SERVSTARTED, MOUNT service already started

This version will be loaded in OVMS 7.3.2, but in OVMS 7.3.1 you can use TCP/IP older (in my case).

I have decide to upgrade OS to 7.3.1 version and maintain older version of TCP/IP.

HP support is working to resove this problem.

Thanks to all.
Daniel Fernandez Illan
Trusted Contributor

Re: NFS client Fails

The problem is solved.

In tcp/ip v5.0a, it doesn't need define Domain name, but witn newest version, if domain name isn't defined, mount deamon fails to start.

Thanks to all.

(¿Can someone close this question?).
Daniel Fernandez Illan
Trusted Contributor

Re: NFS client Fails

The problem is solved.

In tcp/ip v5.0a, it doesn't need define Domain name, but witn newest version, if domain name isn't defined, mount deamon fails to start.

Thanks to all.

(¿Can someone close this question?).
Wim Van den Wyngaert
Honored Contributor

Re: NFS client Fails

Daniel,

You have a close button as you created the thread.

Wim
Wim
Jan van den Ende
Honored Contributor

Re: NFS client Fails

Daniel,

do not forget to give points to those who helped you!
Then you can close the thread.

Jan
Don't rust yours pelled jacker to fine doll missed aches.
Daniel Fernandez Illan
Trusted Contributor

Re: NFS client Fails


I lost my older identification, but i assigned points to replies, before my confusion.

At this momment i'm using a new identification code.

Sorry at all, and a lot of thanks for you aid.
Daniel Fernandez Illan
Trusted Contributor

Re: NFS client Fails

I have located my old identifier.
Close this thread
Thanks to all and sorry for my error.
Daniel
Daniel Fernandez Illan
Trusted Contributor

Re: NFS client Fails

Close this thread.
Saludos, Daniel.