Highlighted
billhilger Absent Member.
Absent Member.
1258 views

Replace old server (NW5.1) instead of upgrading-migrating ?

I have a small, mixed environment. Currently, one tree, 3 servers: 1: NW6.5SP8/OES, 2 & 3 : NW5.1 SP8

In the near (-immediate) future, I'm upgrading the NW5x servers (definitely), and possibly later the NW6.5/OES server to OES11.

One of the NW5.1 servers is being replaced - I'm trying to use OES 11 ( from the SLES+OES overlay disk) .
I need -nothing- other than the server name/id and IP address of the old machine. No data, no users.

I've cleaned up the old server ( say #2) - removing all file partitions except SYS, and all users except Admins. Old stuff like print queues, etc as well, using C1.
New migration server is set up per Novell docs, as a migration target, on same subnet, in same tree. --also on brand new hardware.

The migration tool ( set to migrate server ID) hangs on checking eDir; (not exact) ' source server is using eDir 8, which is not supported. Migration project will now terminate.'
Can I ( easily) remove the old server from my tree, and just install the OES11 server with the same name & IP address?
What can I do to avoid confusing/corrupting the eDir replica ring while I do this?

Or - as I suspect I will need to do for the other old NW5.1 ( #3)... do I need to make incremental upgrades - say to NW6.5SP8 first ?
On that server, I will need to preserve users, groups, and file systems when I move it to the new hardware 'home'.

Thankfully, the only uses on these two old boxen are file access and user authentication.

for detail;
Server #1, NW6.5 SP8 / OES (master replica): server version: 5.70.08, eDir 8.7.3.10 SMP, NDS 10554.34, DS.nlm 10554.34, DSRepair 10551.81
Server #2, NW5.1 SP8, (moving name/id only to new hardware): currently server 5.00.11, eDir ( * 8.7.3.4), NDS 8.85c, DS.nlm 8.85c, DSRepair 10550.86
Server #3, NW5.1 SP8 (planning move of all users & file systems): server 5.00.11, eDir ( * 8.6.2.6), NDS 8.85c, DS.nlm 8.85c, DSRepair 10250.42

* eDir versions not directly given in DSRepair tool, instead I used TID Support | Table of eDirectory versions , and the stated version of DSRepair.

Both servers #2 and #3 are old and ornery; I treat #3 like an old, nasty cat - and only give it _careful_ attention when needed.

For now, please let me know what shortcuts / - pro/con about just killing the old server #2 and replacing it with a brand new hardware-software clean slate?
I'll ask for more help ( or pay a consultant if needed) when that time comes for the others.

Thanks for reading, and for any advice.
Labels (2)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Replace old server (NW5.1) instead of upgrading-migrating ?

On Fri, 22 Nov 2013 20:06:02 +0000, billhilger wrote:

> The migration tool ( set to migrate server ID) hangs on checking eDir;
> (not exact) ' source server is using eDir 8, which is not supported.


Worse, it's NW5, so you can't talk to it with IP, and your destination
server can't do IPX.


> Migration project will now terminate.' Can I ( easily) remove the old
> server from my tree, and just install the OES11 server with the same
> name & IP address?


I think that's really all you *can* do at this point.


> What can I do to avoid confusing/corrupting the eDir
> replica ring while I do this?


Remove the old server. Install the new one.


> Or - as I suspect I will need to do for the other old NW5.1 ( #3)... do
> I need to make incremental upgrades - say to NW6.5SP8 first ? On that
> server, I will need to preserve users, groups, and file systems when I
> move it to the new hardware 'home'.


Users and Groups are in eDirectory, so they'll be "preserved" by the fact
that you're not replacing the tree.

File systems - oy. You're probably also going from TFS to NSS here.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
billhilger Absent Member.
Absent Member.

Re: Replace old server (NW5.1) instead of upgrading-migratin

Thanks, David.

Gonna try that one out.
Little to lose, I guess - since I don't need data or users this time.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Replace old server (NW5.1) instead of upgrading-migrating ?

Billhilger,
> Can I ( easily) remove the old server from my tree, and just install
> the OES11 server with the same name & IP address?
> What can I do to avoid confusing/corrupting the eDir replica ring while
> I do this?


Yes. Just follow the procedures for removing a server from the tree, ie
remove DS from it, clean up tree, removing all objects referencing this
server, then add the new.

http://www.novell.com/support/kb/doc.php?id=10056593

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

Knowledge Partner
Knowledge Partner

Re: Replace old server (NW5.1) instead of upgrading-migrating ?

David Gersic,
> Worse, it's NW5, so you can't talk to it with IP, and your destination
> server can't do IPX.


NW 5.1 can talk NCP over IP, unless I am mistaken, but the best solution
is to remove the server cleanly and install a new one.

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

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.