Max. number of addresses slpd binds to

Question

Running Novell Cluster Services on OES11 multi-homed hosts I'm observing
that the slpd listens on a maximum of 9 IP addresses even is more
addresses are defined. Is this the normal and expected behavior? In the
commented /etc/slp.conf file I do find a variable net.slp.interfaces for
a static configuration but none for the maximum number of
interfaces/addresses.
I our environment it is important that specific NCS ressources offer the
slp service.
Gnther

Answer 1

Hi.
Am 02.12.2014 17:24, schrieb Gnther Schwarz:
>
> Yes, but you can successfully use a cluster ressource as the entry for
> the primary server
Of course. You can use any IP where NCP listens. But it'll refer you to
a real replica holder of your user object as soon as it knows who you
want to be.
> The slpd running on the OES server might or might not be reachable on
> the IP address of a NCS ressource.
Another matter of being slighlty imprecise, sorry. The SLPD in itself
isn't reachable by default, it only talks, but doesn't listen. It only
becomes "reachable", when you explicitly tell it to be a DA (on top of
the default UA and SA which it always "is".
And as I stated in my first reply, you cannot make the DA work on a
virtual cluster IP address, that is correct. But not a matter of count,
it just doesn't work *at all*. You *must* configure the DA on the/a
physical IP of the host. Or in other words, the SLPDA piece of the SLPD
is *not* cluterable. Instead, to achieve fault tolerance, you must use
multiple DAs on the physical hosts.
The UA and SA pieces of SLPD are not connected to clustering, as they're
passive.
> I refer to which addresses the slpd binds. This has nothing to do with
> slp service definitions. See the output of netstat, eg.
> netstat -ap | grep sldp | grep LISTEN
> The maximium of lines I will see in the output is nine.
Actually, you *should* only see one per physical network. But really, it
doesn't matter. One is more than enough, and any attempt to make use of
SLP on more than one is futile. You simply can no,and should not do or
try this.
> Please note that this has nothing to with slp services or service
> definitions. This is all about the networking configuration of the slp
> daemon slpd.
As I said. "The" SLP daemon are three deamons in reality, UA, SA and DA.
All that matters really is the DA, and I've already told you it can only
listen on the first physical IP of the host, and not on a virtual
cluster IP. You can like that or not, but it's a fact. All the rest you
see with netstat is just noise. The presence of a listening port means
nothng for the functionality.
> It seems that it binds to a maximium of nine IP addresses
> at startup. My question was: is this a bug, an option that might be
> configured, or a law or whatever.
The question is, what is your perceived problem with this? The only time
this might actually be a real problem, is if you really have e.g 10 or
more physical network adapters on separate IP networks in a server. If
SLPD in that scenario would really only listen on a max. of nine of
them, then it would certainly be a bug.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de