Why is it that TWO different NetApps have the same port assignments? Perhaps
NetApp is keeping them static for sanity sake so that when the box is rebooted
they stay the same:
---------------------------------------------------------------------
[EMAIL PROTECTED] rpcinfo -p idc-na1-svc
program vers proto port service
100011 1 udp 4049 rquotad
100021 4 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 1 udp 4045 nlockmgr
100024 1 tcp 4047 status
100024 1 udp 4047 status
100005 3 tcp 4046 mountd
100005 2 tcp 4046 mountd
100005 1 tcp 4046 mountd
100005 3 udp 4046 mountd
100005 2 udp 4046 mountd
100005 1 udp 4046 mountd
100003 4 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 udp 2049 nfs
100003 2 udp 2049 nfs
100000 2 tcp 111 rpcbind
100000 2 udp 111 rpcbind
[EMAIL PROTECTED]
---------------------------------------------------------------------
[EMAIL PROTECTED] rpcinfo -p idc-na2-svc
program vers proto port service
100011 1 udp 4049 rquotad
100021 4 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 1 udp 4045 nlockmgr
100024 1 tcp 4047 status
100024 1 udp 4047 status
100005 3 tcp 4046 mountd
100005 2 tcp 4046 mountd
100005 1 tcp 4046 mountd
100005 3 udp 4046 mountd
100005 2 udp 4046 mountd
100005 1 udp 4046 mountd
100003 4 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 udp 2049 nfs
100003 2 udp 2049 nfs
100000 2 tcp 111 rpcbind
100000 2 udp 111 rpcbind
[EMAIL PROTECTED]
---------------------------------------------------------------------
-----Original Message-----
From: Hauke Fath [mailto:[EMAIL PROTECTED]
Sent: Monday, March 14, 2005 6:10 AM
To: [EMAIL PROTECTED]
Cc: Hauke Fath; Olmsted, Brian; Darren Reed; Joseph Spenner;
[email protected]
Subject: Re: rules for NFS with NetApp and OOW packets
Am 14.03.2005 um 10:26 Uhr +0100 schrieb [EMAIL PROTECTED]:
> >AFAIK, NetBSD's rpcbind keeps port assignments of the services it
>>manages constant during machine runtime. Reboot the machine, and you
>>are likely to get different assignments - rpcbind does not store any
> >persistent information on that.
>
>rpcbind does not control the port assignments.
Yep, sloppy language. What I intended to say was that on NetBSD rpc
services keep their port after registration with rpcbind till the
next reboot.
A working rpc proxy for nfs3 over tcp would be nice...
hauke
--
/~\ The ASCII Ribbon Campaign Hauke Fath
\ / No HTML/RTF in email Institut f�r Nachrichtentechnik
X No Word docs in email TU Darmstadt
/ \ Respect for open standards Ruf +49-6151-16-3281
