Looks like the NetApp uses /etc/services to define what the port should be on?

ftp-data        20/tcp
ftp             21/tcp
telnet          23/tcp
smtp            25/tcp
time            37/tcp           # Time Service
time            37/udp           # Time Service
domain          53/udp           # DNS
domain          53/tcp           # DNS
portmap         111/udp
portmap         111/tcp
dhcps           67/udp           # DHCP server
dhcpc           68/udp           # DHCP client
tftp            69/udp
http            80/tcp
kerberos        88/udp           # Kerberos 5
kerberos        88/tcp           # Kerberos 5
nntp            119/tcp
ntp             123/tcp          # Network Time Protocol
ntp             123/udp          # Network Time Protocol
netbios-name    137/udp          # NetBIOS nameserver
netbios-dg      138/udp          # NetBIOS datagram service
netbios-ssn     139/tcp          # NetBIOS service session
cifs-tcp        445/tcp          # CIFS over TCP with NetBIOS framing
snmp            161/udp
shell           514/tcp
syslog          514/udp
route           520/udp
kerberos-sec    750/udp          # For compatibility with older "750" clients
kerberos-sec    750/tcp          # For compatibility with older "750" clients
nfsd            2049/udp
nfsd            2049/tcp
iscsi-target    3260/tcp

nlockmgr        4045/tcp         # NLM
nlockmgr        4045/udp
mountd          4046/tcp         # NFS mountd protocol
mountd          4046/udp
status          4047/tcp
status          4047/udp
pcnfsd          4048/tcp         # PCNFS protocol
pcnfsd          4048/udp
rquotad         4049/udp

ndmp           10000/tcp
snapmirror     10566/tcp
ndmp-local     32243/tcp         # Internal connection inside NetApp box



-----Original Message-----
From: Olmsted, Brian 
Sent: Monday, March 14, 2005 12:33 PM
To: Olmsted, Brian; 'Hauke Fath'
Cc: '[EMAIL PROTECTED]'; 'Darren Reed'; 'Joseph Spenner';
'[email protected]'
Subject: RE: rules for NFS with NetApp and OOW packets



Maybe inconclusive but this might be an older software release, etc.   Here's 
another NetApp  Filer that is different ports but they are all together, etc   
Perhaps it is configurable


bash-2.02$ rpcinfo -p noc-na1-nfs
   program vers proto   port  service
    100011    1   udp    608  rquotad
    100021    4   tcp    607  nlockmgr
    100021    3   tcp    607  nlockmgr
    100021    1   tcp    607  nlockmgr
    100021    4   udp    606  nlockmgr
    100021    3   udp    606  nlockmgr
    100021    1   udp    606  nlockmgr
    100024    1   tcp    605  status
    100024    1   udp    604  status
    100005    3   tcp    603  mountd
    100005    2   tcp    603  mountd
    100005    1   tcp    603  mountd
    100005    3   udp    602  mountd
    100005    2   udp    602  mountd
    100005    1   udp    602  mountd
    100003    3   udp   2049  nfs
    100003    2   udp   2049  nfs
    100000    2   tcp    111  rpcbind
    100000    2   udp    111  rpcbind
bash-2.02$ 



-----Original Message-----
From: Olmsted, Brian 
Sent: Monday, March 14, 2005 12:30 PM
To: 'Hauke Fath'
Cc: [EMAIL PROTECTED]; Darren Reed; Joseph Spenner;
[email protected]
Subject: RE: rules for NFS with NetApp and OOW packets




Looks like the NetApp Filer using same ports as two other systems in another 
data centre that our group doesn't currently manage seem to have the same port 
assignments as the two that we manage.  These two NetApp filers have most 
likely been rebooted over the past couple of years.   This is good :) 

[EMAIL PROTECTED]: /export/home/olm8980} $ rpcinfo -p corp-na1
   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]: /export/home/olm8980} $
[EMAIL PROTECTED]: /export/home/olm8980} $ rpcinfo -p corp-na2
   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    3   udp   2049  nfs
    100003    2   udp   2049  nfs
    100000    2   tcp    111  rpcbind
    100000    2   udp    111  rpcbind
[EMAIL PROTECTED]: /export/home/olm8980} $ 



-----Original Message-----
From: Hauke Fath [mailto:[EMAIL PROTECTED]
Sent: Monday, March 14, 2005 11:59 AM
To: Olmsted, Brian
Cc: Hauke Fath; [EMAIL PROTECTED]; Darren Reed; Joseph Spenner;
[email protected]
Subject: RE: rules for NFS with NetApp and OOW packets


Am 14.03.2005 um 11:27 Uhr -0500 schrieb Olmsted, Brian:
>Why is it that TWO different NetApps have the same port assignments?

I know for sure that NetBSD port assignments for rpc services can 
change between boots, esp, if you add/remove services.

Sounds like NetApps are NetBSD + something...

        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

Reply via email to