NDS Tree problems
jkm...@cox.com
I've got a nw 5.0, sp6e, server that was the 1st server to be installed on
the network of 26 other servers. It held the master partition of the root.
I've got to replace it with another server (NW5.1) and have the
replacement all setup and ready to go when the time is right. I've added a
read/write master root partition to another server and changed it to
master. I removed all other partitions from the 5.0 server.
This morning the NW5.0 server was offline due to a switch failure and the
NDS tree wasn't available for users to logon even though the server that
holds the root partition was online.
What's happening here? Am I missing something? Will I be able to remove
the 5.0 server without losing the tree information? The only thing that
shows up on the 5.0 server in NDS manager is the OU partition which is
indicating its in a 'dead' state.
I hope that it's a simple fix because I need to get the 5.0 server out of
the tree, the sooner the better.
Thanks,
Bob
Jeff Mig DSE
If you look in DSREPAIR, Report Sync Status on all the servers that
hold a replica of root, are they all in Sync ?
Was the first 5.0 server not the CA for the tree ? In NW6 or above,
you can move the CA, I am sure you cannot with 5.
Are your clients hard set to point to the old 5.0 server? What would
happen if you put the IP ADDRESS of the new Master of root as the tree
name ?
How are things configured as far as prtocols ? If IPX, do you do any
SAP filtering on the Network ? OR are you using IP ? SLP/DNS setup
correctly.
From the cool solutions site download SAPSNOOP. That will show you if
SAP is getting to the workstations in question.
All you really need to do is install another server, add a replica of
root, then remove the replica off the old server. Then you can remove
DS.
Lastly, do you see any obituaries that may not have purged?
-Jeff
Marcel Cox
Your message was not posted to the official Novell news
server. While your news server might show the Novell support
newsgroups, Novell has no official connection with other news
servers, and the message you posted will probably never
propagate to the official Novell server. The SysOps only see
messages on the Novell server and for that reason,
you will probably never get a reply to your
message posted here.
I suggest you post your message directly to the official
novell news server named support-forums.novell.com. The
Novell news server is freely accessible both through HTTP
and NNTP. See http://support.novell.com/forums for details.
This message was posted automatically. Please do not reply
to it.
Marcel Cox
Novell Support Forums SysOp
bru...@myrealboxnospamme.com
the dead state you will not be able to remove it cleanly. I would do a
health check on DS(lots of TIDs on this) and focus on obituaries. One of
the servers in the ring, with the partition you have a dead replica for,
must not be processing obits completely. There are also a number of TIDs
for that. Search on obituaries in the knowledgebase. Hope this helps.
Bruce
CNE6, CNI
Andrew C Taubman
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)
Opinions expressed above are not
necessarily those of Novell Inc.
Raff2
move everything (data) to the replacement server and cautiously take the
problem server off line to see what affect it will have with the network, if
any. The network is replicating and time syncing without errors. I'm in the
process of upgrading/patching the other 17 servers on the network that this
server held the master to the root. Of course, this is time consuming in
itself. If there are problems at first when I remove the server, I'll have a
better idea of what to expect and you'll probably hear from me again.
Thanks,
Bob Raffety, CNE5
"Andrew C Taubman" <ataubman.Remov...@novell.AndThis.com> wrote
in message news:n_fRb.244$Wh....@prv-forum2.provo.novell.com...