- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: NFS client Fails
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2004 08:10 PM
тАО07-20-2004 08:10 PM
NFS client Fails
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2004 06:43 PM
тАО07-21-2004 06:43 PM
Re: NFS client Fails
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2004 09:44 PM
тАО07-21-2004 09:44 PM
Re: NFS client Fails
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2004 09:59 PM
тАО07-21-2004 09:59 PM
Re: NFS client Fails
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2004 10:09 PM
тАО07-21-2004 10:09 PM
Re: NFS client Fails
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2004 10:26 PM
тАО07-21-2004 10:26 PM
Re: NFS client Fails
When I update again, I will verify all those points.
Best regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2004 10:28 PM
тАО07-21-2004 10:28 PM
Re: NFS client Fails
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2004 10:29 PM
тАО07-21-2004 10:29 PM
Re: NFS client Fails
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 08:08 PM
тАО07-26-2004 08:08 PM
Re: NFS client Fails
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)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2004 06:43 PM
тАО07-27-2004 06:43 PM
Re: NFS client Fails
What does this solution has to do with the mount service that wasn't offered ?
It seems a solution for a 2nd problem ...
Wim