Highlighted
Absent Member.
Absent Member.
1147 views

OES 2018 OpenSLP DA

Over the last week, I upgraded most of my OES 2015 SP1 servers to OES 2018 without any real problems. This evening, I had a chance to upgrade another server to OES 2018, but after doing so, I found that none of my workstations could find their eDirectory tree. This server that I just tried upgrading was our last SLP DA running on OES 2015 SP1.

After logging into a workstation locally and running slpinfo, I see that the client thinks that it is its own DA. I remember that this was a bug when OES 2018 first came out, and I purposefully held off of upgrading any servers because of it. I wasn't really thinking about it anymore at the point when I started upgrading servers last week, and just assumed that it would have been fixed in one of the updates that have been released in the mean time. It looks like that isn't the case though.

Luckily, I have a fairly small network, without many users on the weekend, so I was able to briefly shutdown all of my eDirectory replica servers and take a VMware snapshot of each before upgrading this server, so "downgrading" the server back to OES 2015 SP1 wasn't too difficult or time consuming, but it seems that I'm going to have to hold off on upgrading for the time being.

The link that I had originally saved to a TID regarding the issue doesn't appear to be valid any more:
https://www.novell.com/support/kb/doc.php?id=7022694

I see that the issue appears to be fixed in SLES 12 SP3, but not in SLES 12 SP2 LTSS, which feeds into the OES 2018 update channel.
https://download.suse.com/Download?buildid=K6Gpqp5oYY8~

Does anyone here have any inside knowledge as to when new OpenSLP packages might find their way into the update channel, or is this something that is unlikely to be fixed until OES 2018 SP1 is released, which would presumably be based on SLES 12 SP3, and receive the fix that way? I think that I might be stuck leaving this server on OES 2015 SP1 and running SLP without redundancy in the mean time.
Labels (2)
0 Likes
4 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: OES 2018 OpenSLP DA

Hi.


On 23.07.2018 01:24, ccalvert wrote:
>
> The link that I had originally saved to a TID regarding the issue
> doesn't appear to be valid any more:
> https://www.novell.com/support/kb/doc.php?id=7022694
>


It still exists in the Google cache:

https://webcache.googleusercontent.com/search?q=cache:hVwYhtmEn5IJ:https://www.novell.com/support/kb/doc.php%3Fid%3D7022694+&cd=1&hl=en&ct=clnk&gl=de

I sugegst you open a SR as the TID says. I'll also ask around why the
TID is gone.

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

Re: OES 2018 OpenSLP DA

Just for the sake of anyone who is running into the same issue and comes across this forum thread, the information in the original TID was migrated to a different TID: https://www.novell.com/support/kb/doc.php?id=7023087
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: OES 2018 OpenSLP DA

On 01.08.2018 17:04, ccalvert wrote:
>
> Just for the sake of anyone who is running into the same issue and comes
> across this forum thread, the information in the original TID was
> migrated to a different TID:
> https://www.novell.com/support/kb/doc.php?id=7023087
>
>

Yes. Did you open a SR? If yes, what was the outcome?

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

Re: OES 2018 OpenSLP DA

I didn't open an SR. We license our Micro Focus products through the SLA contract and would have to purchase an SR separately in order to be able to open one, even if it would likely later be refunded. I could go through our reseller and see if they could open an SR on our behalf to get the patch, or try to get a copy from someone else who already has it, but with the start of school approaching and other projects that need to be completed, I'm going to leave this server on OES 2015 SP1 for now and hold off on any further OES 2018 upgrades until SP1 is out.

I just figured that I should post the link to the new TID in the thread so that anyone looking through the forums for a solution to their sudden SLP problems after upgrading to OES 2018 would find it.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.