Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Morong, Gerry" <Gerry.Morong@hp.com>
Cc: <nfs@lists.sourceforge.net>
Subject: Re: NFS and UDP port 1434
Date: 01 Feb 2003 10:04:02 +0100	[thread overview]
Message-ID: <shsr8aspe2l.fsf@charged.uio.no> (raw)
In-Reply-To: <E67F8F12671DF54FB828481785943030037EB836@cceexc22.americas.cpqcorp.net>

>>>>> " " =3D=3D Gerry Morong <Morong> writes:

     > Have a hundred plus Red Hat 7.3 NFS clients connecting to
     > several NetApps and Red Hat 7.3 fileservers.=A0 They are
     > configured to run NFS V3 over UDP.=A0 When the SQL slammer bug
     > hit our routers were reconfigured to block UPD port 1434.=A0 This
     > caused sporadic NFS lockups for mounts outside the local subnet
     > subject to the port blocking.=A0 Once the port blocking was
     > cleared from the routers, NFS connections freed up and started
     > working again. What part of NFS should be using UDP port 1434?=A0

'/usr/sbin/rpcinfo -p' will tell you.

It is probably either rpc.statd or rpc.lockd

Cheers,
  Trond





-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2003-02-01  9:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31 17:21 NFS and UDP port 1434 Morong, Gerry
2003-02-01  9:04 ` Trond Myklebust [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=shsr8aspe2l.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=Gerry.Morong@hp.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox