Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SLP services register on wrong interface

1 view
Skip to first unread message

oack...@lanworks.de

unread,
Jan 14, 2004, 1:00:48 PM1/14/04
to
On a NW 6.0 SP3 server with 2 NICs (routing disabled) all SLP services
register on the wrong interface. The server ist running an SLPv2DA with
named scope. I've excluded the wrong IF with 'SLP Exclude IP Addresses',
included the correct one with 'SLP Include IP Addresses', set 'SLP Agent IP
Address' to the correct NIC, then manually deleted all services and
rebooted the server - no effect. Services still register with the wrong NIC.
Any ideas?

Olaf Ackermann

Donald Albury

unread,
Jan 14, 2004, 1:49:07 PM1/14/04
to
Olaf,

Does the last paragraph of TID 10056966
(http://support.novell.com/cgi-bin/search/searchtid.cgi?/10056966.htm)
help?

Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses

Massimo Rosen

unread,
Jan 14, 2004, 3:10:35 PM1/14/04
to
Hi,

You're confusing the settings. The "SLP Include IP Adresses" setting is
used to determine on which IP Adresses SLP is active, in no way which IP
addresses are registered. In fact, to find what (if anything) we can do
for you, we first need to know about which service we're talking here.
Most every SLP service registers itself, and it totally depends on that
service and on which IP it's running. E,g rconag6 registers the
rconsole.novell service, and rconag6 by default listens on the first
bound IP, so it also registers that one.


CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de

oack...@lanworks.de

unread,
Jan 15, 2004, 3:09:09 AM1/15/04
to

Hi Donald,
unfortunately not, because if I disable NCP on that interface (which is a
separate LAN for backup purposes) I wont be able to backup the server.

Olaf

oack...@lanworks.de

unread,
Jan 15, 2004, 4:03:26 AM1/15/04
to
Hi Massimo,
you are probably right; we're talking about all of the services of that
server (ProLiant ML530), that are smdr, securerconsole, rconsole, nlsmeter,
and timesync.
They should bind on interface 1 (production LAN) but instead register to
interface 3 (backup LAN). IF 1 is a built-in Compaq N100 and loads as two
logical IFs for frame types E_II (for IP) and E_802.2 (for IPX). IF 3 is an
additional Q57 Gbit Adapter.
Disabling NCP on IF 3 is not an option. IF 1 is the first to be loaded in
Inetcfg (netinfo.cfg), and tcpip.cfg. The backup LAN IF shows up as IF 3
but nevertheless all services register to it. Logger Screen shows the N100
is loaded first as it should be.
Is there a way to add a preferred IP address to Rconag6.nlm or smdr.nlm as
it is possible with broker.nlm and ndpsm.nlm?
The only workaround I can figure out is removing the Inetcfg.cfg
configuration and loading the boards/protocols separately through
Autoexec.ncf, but I haven't tested it yet.

Olaf

oack...@lanworks.de

unread,
Jan 15, 2004, 6:02:05 AM1/15/04
to
Hi Massimo,

correction: only rconsole, securerconsole, nlsmeter, smdr, and timesync
register on the wrong interface. nwserver, srs, and portal register on the
correct interface.

Olaf

oack...@lanworks.de

unread,
Jan 15, 2004, 10:47:40 AM1/15/04
to
The main problem seemed to be the wrong order of network addresses in the
Network Address attribute of the server object.
Solution: Removed second LAN adapter from inetcfg.nlm, repaired local
database, added the second LAN adapter again, and rebooted the server.
Services now register with both LAN adapters.

Thanks for your input.
Olaf

0 new messages