My Favorites

Close

Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

How to fix NFS to a port without changing the standard start and stop script?

This document (7000090) is provided subject to the disclaimer at the end of this document.

Environment


Novell SUSE Linux Enterprise Server 9

Situation

Symptoms:
Since NFS normally uses the portmapper, it will beavailable on different ports after each restart of the server orthe NFS service. This makes it difficult to set up a securefirewall for this server.

Resolution

Workaround Steps: SLES9SP3 must have the post SP3 patch  nfs-utils-1.0.6-103.28 or later installed.Then add this to the kernel startup line in your loader config (tested with grub /boot/grub/menu.lst)
lockd.nlm_tcpport= lockd.nlm_udpport=
it could look like this:

kernel (hd0,1)/boot/vmlinuz root=/dev/sda2 selinux=0 splash=silent resume=/dev/sda1 elevator=cfq showopts clock=pit lockd.nlm_udpport=10005 lockd.nlm_tcpport=10006

and create a file /etc/sysconfig/nfs if it does not already exist, and add the parameter MOUNTD_PORT=<your port> like this:
MOUNTD_PORT=10004

to the end of the file.
Then restart the server.

Additional Information

To verify the ports, execute:

rpcinfo -p

and using the example above, it should output something like:

program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100227 3 udp 2049 nfs_acl
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100227 3 tcp 2049 nfs_acl
100024 1 udp 10005 status
100021 1 udp 10005 nlockmgr
100021 3 udp 10005 nlockmgr
100021 4 udp 10005 nlockmgr
100024 1 tcp 10006 status
100021 1 tcp 10006 nlockmgr
100021 3 tcp 10006 nlockmgr
100021 4 tcp 10006 nlockmgr
100005 1 udp 10004 mountd
100005 1 tcp 10004 mountd
100005 2 udp 10004 mountd
100005 2 tcp 10004 mountd
100005 3 udp 10004 mountd
100005 3 tcp 10004 mountd

Also notice, that the nfs service on port 2049 has not been touched, since the usage of port 2049 is fixed in the startup script.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7000090
  • Creation Date:15-APR-08
  • Modified Date:30-APR-12
    • SUSESUSE Linux Enterprise Server

Did this document solve your problem? Provide Feedback

< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center