Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    20
  • Subscribers subscribers
    19
  • Views views
    1582
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

slp DA not showing itself (?) in OES

kjhurni
OES 11 SP2 (yeah I know)

3 servers in the tree.

Server1 = 10.10.1.10
Server2 = 10.10.1.11
Server3 = 10.10.1.13

Server1 and Server3 are both openslpDA servers (Server1 is a DS Master, Server2 and Server3 have RW replicas of everything)

Server1 slp.conf (well end part anyway):

net.slp.useScopes = ACME_SLP_GLOBAL
net.slp.isDA = true
net.slp.isBroadcastOnly = false
net.slp.DAAddresses = 10.10.1.10,10.10.1.13
net.slp.MTU = 1450

net.slp.DASyncReg = true
net.slp.isDABackup = true
;net.slp.DABackupLocalReg = true
net.slp.DABackupInterval = 900



Server3 slp.conf (end part as well):

net.slp.useScopes = ACME_SLP_GLOBAL
net.slp.isDA = true
net.slp.isBroadcastOnly = false
net.slp.DAAddresses = 10.10.1.13,10.10.1.10
net.slp.MTU = 1450
net.slp.interfaces = 10.10.1.13

net.slp.DASyncReg = true
net.slp.isDABackup = true
net.slp.DABackupInterval = 900


Server3 was rebooted 2 weeks ago.

All three servers show the same output from:
slptool findsrvs service:bindery.novell:

service:bindery.novell:///Server2,2835
service:bindery.novell:///Server1,810


Server3 is missing.

OES Client on pc's also only show two "bindery" servers:
Server1
and
Server2

Server3 is missing

I tried using TID https://support.microfocus.com/kb/doc.php?id=7001449

But nothing seems to jive/work.

Any ideas as to why this one server refuses to show up as a bindery server?
We're randomly getting "tree or server not found" which I think may be this one server (would have to find a hub to try to do a packet capture to see what's going on from the workstation perspective).

Restarting slpda has no effect.
Parents Reply
  • 0 in reply to MigrationDeletedUser
    Massimo Rosen;2500630 wrote:
    On 06.06.2019 16:34, kjhurni wrote:

    Kevin...

    > net.slp.interfaces = 134.179.251.28

    ???

    CU,
    --
    Massimo Rosen
    Micro Focus Knowledge Partner
    No emails please!
    http://www.cfc-it.de


    Yeah, was trying to change IP's and missed one.

    Sigh
    This is why I should've posted in the private forums but then everyone wants it posted publicly.

    Fixed the original post. Basically that = Server3
Children
  • 0 in reply to kjhurni
    On 06.06.2019 17:06, kjhurni wrote:
    >
    > Massimo Rosen;2500630 Wrote:
    >> On 06.06.2019 16:34, kjhurni wrote:
    >>
    >> Kevin...
    >>
    >>> net.slp.interfaces = 134.179.251.28
    >>
    >> ???
    >>
    >> CU,
    >> --
    >> Massimo Rosen
    >> Micro Focus Knowledge Partner
    >> No emails please!
    >> http://www.cfc-it.de
    >
    > Yeah, was trying to change IP's and missed one.
    >
    > Sigh
    > This is why I should've posted in the private forums but then everyone
    > wants it posted publicly.
    >
    > Fixed the original post. Basically that = Server3
    >
    >
    Ic.

    I would remove it nonetheless, aka the whole line. Why is it there? Same
    goes for the MTU line.

    Also note, that the fact that Server3 is da (or not) is totally
    irrelevant for it's registration of eDirectory with SLP. That you don't
    see it in bindery.novell is either a problem of the local eDir instance
    failing to (re)registering itself with any of the configured DAs, or a
    completely malfucntioning local SLP stack.

    Do you see any other service of server3 in all the SLP services? Say
    smdr.novell or something?

    CU,
    --
    Massimo Rosen
    Micro Focus Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • 0 in reply to kjhurni
    On 06.06.2019 17:06, kjhurni wrote:
    >
    > Massimo Rosen;2500630 Wrote:
    >> On 06.06.2019 16:34, kjhurni wrote:
    >>
    >> Kevin...
    >>
    >>> net.slp.interfaces = 134.179.251.28
    >>
    >> ???
    >>
    >> CU,
    >> --
    >> Massimo Rosen
    >> Micro Focus Knowledge Partner
    >> No emails please!
    >> http://www.cfc-it.de
    >
    > Yeah, was trying to change IP's and missed one.
    >
    > Sigh
    > This is why I should've posted in the private forums but then everyone
    > wants it posted publicly.
    >
    > Fixed the original post. Basically that = Server3
    >
    >
    Ic.

    I would remove it nonetheless, aka the whole line. Why is it there? Same
    goes for the MTU line.

    Also note, that the fact that Server3 is da (or not) is totally
    irrelevant for it's registration of eDirectory with SLP. That you don't
    see it in bindery.novell is either a problem of the local eDir instance
    failing to (re)registering itself with any of the configured DAs, or a
    completely malfucntioning local SLP stack.

    Do you see any other service of server3 in all the SLP services? Say
    smdr.novell or something?

    CU,
    --
    Massimo Rosen
    Micro Focus Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • 0 in reply to MigrationDeletedUser
    Massimo Rosen;2500632 wrote:
    On 06.06.2019 17:06, kjhurni wrote:
    >
    > Massimo Rosen;2500630 Wrote:
    >> On 06.06.2019 16:34, kjhurni wrote:
    >>
    >> Kevin...
    >>
    >>> net.slp.interfaces = 134.179.251.28
    >>
    >> ???
    >>
    >> CU,
    >> --
    >> Massimo Rosen
    >> Micro Focus Knowledge Partner
    >> No emails please!
    >> http://www.cfc-it.de
    >
    > Yeah, was trying to change IP's and missed one.
    >
    > Sigh
    > This is why I should've posted in the private forums but then everyone
    > wants it posted publicly.
    >
    > Fixed the original post. Basically that = Server3
    >
    >
    Ic.

    I would remove it nonetheless, aka the whole line. Why is it there? Same
    goes for the MTU line.

    Also note, that the fact that Server3 is da (or not) is totally
    irrelevant for it's registration of eDirectory with SLP. That you don't
    see it in bindery.novell is either a problem of the local eDir instance
    failing to (re)registering itself with any of the configured DAs, or a
    completely malfucntioning local SLP stack.

    Do you see any other service of server3 in all the SLP services? Say
    smdr.novell or something?

    CU,
    --
    Massimo Rosen
    Micro Focus Knowledge Partner
    No emails please!
    http://www.cfc-it.de


    Ah, so you jogged my memory.

    The Server1 and Server3 have two NIC
    But multiple IP's (two actually) one for each NIC.

    One IP is used STRICTLY for LDAP behind a hardware load balancer, so that's why we restricted the SLP/NCP traffic to the one IP, because we found that the server would reply from the "LDAP" NIC but the load balancer would toss the traffic, thus resulting in errors from the client-side.

    Now that I've remembered that, ironically Server1 doesn't have the restriction line, so possibly that's where the tree or server not found it coming from?

    Server3 is supposed to be a DA (ha)

    I'm not seeing smdr.novell for Server3
    But I see like:
    service:ntp
    service:ldap

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.