I have two hp DL360G3 servers with two hp NICs each teamed for 2Gbit. This
is a 2-node cluster serving volumes on Netware 6.5 SP1.1b. The NFS part does
not seem to have mountd listening on the correct IP for the virtual NIC.

From a Solaris box if I run 'rpcinfo -p <nodename>' on either node it looks
correct:

program vers proto port service
100000 2 udp 111 portmapper
100000 2 tcp 111 portmapper
100007 2 udp 902 ypbind
100009 1 udp 903 yppasswdd
100009 1 tcp 846 yppasswdd
100004 2 udp 904 ypserv
100004 2 tcp 847 ypserv
100004 1 udp 961 ypserv
100004 1 tcp 731 ypserv
100021 1 udp 32779 nlockmgr
100021 2 udp 32779 nlockmgr
100021 3 udp 32779 nlockmgr
100021 4 udp 32779 nlockmgr
100021 1 tcp 32779 nlockmgr
100021 2 tcp 32779 nlockmgr
100021 3 tcp 32779 nlockmgr
100021 4 tcp 32779 nlockmgr
100005 1 udp 1234 mountd
100005 2 udp 1234 mountd
100005 3 udp 1234 mountd
100005 1 tcp 1234 mountd
100005 2 tcp 1234 mountd
100005 3 tcp 1234 mountd
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 udp 2049 nfs
100003 3 tcp 2049 nfs
100024 1 udp 32778 status
100024 1 tcp 32778 status

However, mounts fail. Looking at a trace of the mount it is continually
getting stuck trying to send data to port 1234 [mountd]. I get loops that
are trying to do this:

sendto(5, "A&tl\0\0\0\0\0\0\0\2\0\1\206\245\0\0\0\3\0\0\0\1\ 0\0\0"..., 88,
0, {sa_family=AF_INET, sin_port=htons(1234),
sin_addr=inet_addr("xxx.xxx.xxx.xxx")}, 16) = 88
poll([{fd=5, events=POLLIN}], 1, 3000) = 0
ioctl(5, 0x8912, 0xbfffcc08) = 0
ioctl(5, 0x8913, 0xbfffcc10) = 0

After about 6 attempts it gives up with:

mount: RPC: Timed out

Back on the Netware server if I run 'tcpcon' I see only one reference to
port 1234 [or 'search-agent 1234/tcp #Infoseek Search Agent' in the SERVICES
table]:

IP 0.0.0.0 1234 0.0.0.0 0 listen

And nothing on the teamed IP number for this port. This is surely not
correct? Port 2049 [nfs] is bound to the teamed NIC as I would expect.

So my questions are:

[1] Should port 1234 be bound to 0.0.0.0 or the teamed NIC IP?
[2] Is there an easy way of reverting back to a standalone NIC configuration
temporarily so I can test it with a normal network connection?

Thanks,

--
Matt Ross

-=I haven't lost my mind; it's backed up on tape.=-