Highlighted
Knowledge Partner
Knowledge Partner
662 views

Upgrade Single Server Tree to OES2018SP1?

Hi.

I notice that during the upgrade of an OES2015 root master server to OES2018SP1, after the first boot, the server requires an eDirectory connection to a *different* server in the tree with a writable replica, which is something new. In previous, even major upgrades, the eDir upgrade always worked fine against the local copy.

What happens when such a thing simply does not exist, e.g in a single server tree, or when (for whatever reason) only one writable replica eixts? Has anybody done this?

Curious,

Massimo

 

 

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
Labels (1)
0 Likes
7 Replies
Knowledge Partner
Knowledge Partner

Re: Upgrade Single Server Tree to OES2018SP1?

Just roughly remembering...

I could proceed with a secondary ip address added to the box in question. Suggested this address as replica holder, got an error but was allowed to proceed anyway.

 

0 Likes
Knowledge Partner
Knowledge Partner

Re: Upgrade Single Server Tree to OES2018SP1?


@mathiasbraun wrote:

Just roughly remembering...

I could proceed with a secondary ip address added to the box in question. Suggested this address as replica holder, got an error but was allowed to proceed anyway.

 


Oh wow. Still wondering what's the reasoning behind this. Or if this isn't just worth a bug report.

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

Re: Upgrade Single Server Tree to OES2018SP1?

I'd grab the logs and report, I don't remember seeing this during beta.  They'll likely want the y2logs and nds logs

0 Likes
Knowledge Partner
Knowledge Partner

Re: Upgrade Single Server Tree to OES2018SP1?

I have no logs as I've never done nor tried this (yet), because obviously, single server tress are somewhat rare. It's just that I couldn't help myself notice that updating a OES2015 server to OES2018SP1, in the post-upgrade 1stboot stage does *not* accept it's own IP (which is filled in by default) and very outspoken and explicit asks for a different server than itself. So it's really unlikely that nobody has seen it (rather, *everybody* must have seen it), but it is likely that nobody has thought about what this means in a single server tree.

 

CU,

Massimo

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

Re: Upgrade Single Server Tree to OES2018SP1?

funny, I've always just ASSumed that I needed a second eDir server in order to do an upgrade, so the couple single-server upgrade I did I first installed another server in a VM... news to me that it wasn't actually necessary until now.

0 Likes
Knowledge Partner
Knowledge Partner

Re: Upgrade Single Server Tree to OES2018SP1?

No previous OES version upgrade ever asked for a connection to a remote server (unless in the LUM stage a remote server has been configured previously). That makes no sense, and it's entirely unnecessary. eDir *is* fully up and running on the local server at his point. It has to be, otherwise the update would fail miserably in case the server you update is the e.g the CA. This is obviously a restriction someone artificially coded into the product.

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

Re: Upgrade Single Server Tree to OES2018SP1?

This started happening somewhen in the OES2015 era. I had posted regarding this here

https://community.microfocus.com/t5/OES-User-Discussions/Deadlock-on-OES2015-upgrade/td-p/2413890

I have no clue what this behaviour is good for as it's merely a "ndsconfig upgrade" and stuff simply works if you workaround the issue as mentioned. I'm also pretty sure that it doesn't need a secondary IP bound on the box which is getting upgraded, i'd guess you just need a listener on (likely) 524 to get to the point where you can opt over.

 

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.