Andy's Technotes Home
If a server fails (especially within a multi-server tree) see TIDs 3338221 & 10011467 & 10013083 & 10012033. All basically cover the same material but reading them all while waiting for the some of the early steps will help you understand what it is your are doing so that you can do the right things without killing anything. The concepts are the same on all eDir platforms.
Some of the key commands for different plateforms.
To remove a failed server from a replica ring on Linux, in Partition, Advanced:
/opt/novell/eDirectory/bin/ndsrepair -P -AdThen:
If you are changing a server such that you need to take it out of the tree and restore such as when replacing the harddrives or the whole server, then follow TID 10010933 (formerly TID 2934033)
if you are having issues running eDirectory 8.7.3 or later, check TID 3393940, formerly 10093821
for general NDS things to have checked before calling Novell tech support see TID 2938838 (also was refered to as TID 10014284)
For proper NDS/eDirectory health check proceedures, TID 3564075 (formerly TID 10012858 and 10060600)Checkout "10 Tips for TroubleShooting NDS"
A great reference is Novell's Guide to Troubleshooting eDirectory, by Peter Kuo & Jim Henderson, and my dead-tree edition is 'defaced' by both of their autographs. Heartedly recommended for anyone who has to take care of eDirectory.
Additional NDS health information is available on the following App Notes (available on the Support Connection CDs or at http://developer.novell.com/research/index.htm as viewed through the WayBack Machine)
May 1998 Using DSREPAIR to Maintain the Novell Directory Services Database
August/October 1997 Maintaining a Healthy NDS Tree: Parts 1 & 2
details for maintaining NDS
January 1999 Troubleshooting NDS in NetWare 5 with DSREPAIR and DSTRACE
and an old but still useful for understanding the basics even if some of the details have changed
October 1996 Backing Up and Restoring Novell Directory Services in NetWare 4.11
|Last updated 2013-04-09||Copyright © 1996-2013 Andy Konecny||andyweb @ konecnyconsulting.ca|