- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Force NFS to use TCP
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
Forums
Discussions
Discussions
Discussions
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
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
06-03-2005 03:59 AM
06-03-2005 03:59 AM
We have been asked by auditors to ensure that any NFS connections use TCP rather than UDP. We have 2 machines, one running 11.i and one running 11.0.
We are able to connect from the 11.0 machine to the 11.i machine using TCP as I believe TCP is the default on 11.i. However I am having trouble connecting to the 11.0 machine using TCP. I have added NFS_TCP=1 into the /etc/rc.config.d/nfsconf file and the machine has been rebooted since. I am using the command
# mount -o proto=tcp spms-l20:/disk3/optima /disk3
and this mounts the filesystem. But when I run nfsstat -m the results indicate that the filesystem has been mounted using UDP.
How can I ensure that all NFS connections are using TCP and not UDP?
Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2005 04:20 AM
06-03-2005 04:20 AM
Re: Force NFS to use TCP
Check mountd_options setting. Should look like follows.
MOUNTD_OPTIONS="-o proto=tcp"
Restart nfs.client, nfs.core and nfs.server
This should do it.
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2005 08:20 PM
06-03-2005 08:20 PM
Re: Force NFS to use TCP
To use tcp for NFS you need to have the following....
On NFS Server:
1.check /etc/services to verify TCP is available on server through port 2049. Entry should look like->
nfsd 2049/tcp #NFS remote file system
2.Set the NFS_TCP environment variable
to 1 in the /etc/rc.config.d/nfsconf configuration file in order to
support the TCP transport.
3.To specify protocol type while starting nfsd:
/usr/sbin/nfsd -p
TCP or UDP.
/usr/sbin/nfsd -p TCP
On NFS Client:
You can tell NFS to establish ONLY a TCP connection using the following command: mount -o proto=tcp
Hope this helps
Sudeesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2005 05:06 PM
06-05-2005 05:06 PM
Re: Force NFS to use TCP
$ rpcinfo <11.00_server> | grep nfs
100003 2 udp 0.0.0.0.8.1 nfs superuser
100003 3 udp 0.0.0.0.8.1 nfs superuser
100003 2 tcp 0.0.0.0.8.1 nfs superuser
100003 3 tcp 0.0.0.0.8.1 nfs superuser
The output indicates that NFS is available over UDP and TCP (3rd column) and versions 2 and 3 are available (2nd column).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2005 09:43 PM
06-06-2005 09:43 PM
Re: Force NFS to use TCP
Sudeesh - I have tried all of your suggestions but the filesystem was still being mounted with UDP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2005 09:45 PM
06-06-2005 09:45 PM
Re: Force NFS to use TCP
The output of the rpcinfo command is as follows:
21349 rpcinfo|grep nfs
100003 2 tcp 0.0.0.0.8.1 nfs superuser
100003 3 tcp 0.0.0.0.8.1 nfs superuser
100003 2 udp 0.0.0.0.8.1 nfs superuser
100003 3 udp 0.0.0.0.8.1 nfs superuser
150001 1 udp 0.0.0.0.2.234 pcnfsd superuser
150001 2 udp 0.0.0.0.2.234 pcnfsd superuser
150001 1 tcp 0.0.0.0.2.235 pcnfsd superuser
150001 2 tcp 0.0.0.0.2.235 pcnfsd superuser
Does this mean that NFS over TCP should be available?
Thanks,
Gillian.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2005 09:48 PM
06-06-2005 09:48 PM
Re: Force NFS to use TCP
The MOUNTD_OPTONS was not set so I have now set this.
Can you please tell me what order the restart of NFS.client, core and server should be?
I'm guessing it is in the following order but please correct me if I am wrong:
nfs.client stop
nfs.server stop
nfs.core stop
nfs.core start
nfs.server start
nfs.client start
Thanks,
Gillian.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2005 10:08 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2005 10:15 PM
06-06-2005 10:15 PM
Re: Force NFS to use TCP
nfs.server stop
nfs.client stop
nfs.core stop
nfs.core start
nfs.client start
nfs.server start
Sudeesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2005 10:17 PM
06-06-2005 10:17 PM
Re: Force NFS to use TCP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2005 11:18 PM
07-17-2005 11:18 PM
Re: Force NFS to use TCP
After rebooting the machine for the second time this problem has been resolved. I am unsure why the changes did not take effect before, but thanks for all your responses.
Gillian.