|
When you have an understanding of the basics of eDirectory architecture and design, it is important to understand the activities and tools necessary to maintain eDirectory on a day-to-day basis. As with the rest of OES Linux, eDirectory management is performed through web-based utilities. Specifically, comprehensive eDirectory management is available through iManager and iMonitor. For information on installing and configuring both iMonitor and iManager, see Chapter 5, "OES Management Tools." iManager provides comprehensive role-based management capabilities for the entire OES Linux environment. iMonitor consolidates the monitoring and data-gathering aspects of several terminal-based tools, including ndstrace and ndsrepair. It also includes the object viewing and reporting functionality of the NetWare-only utilities, DSBrowse and DSDiag. The iMonitor interface is shown in Figure 7.8. Figure 7.8. The iMonitor user interface.iManager provides a complete set of eDirectory management tools and functions for object, partition, and replica operations. Much of this functionality is also available from the Partition and Replica view in ConsoleOne. As mentioned in Chapter 5, although ConsoleOne is not provided with OES Linux, this utility can still be used in existing infrastructures or specifically downloaded from download.novell.com. You can also use SSH for remote access to a server terminal, from which you can run several eDirectory-specific terminal-based utilities. This section gives you an overview of common eDirectory tasks and the tools used to perform them. eDirectory management tasks can be organized into six main categories:
NOTE Managing specific eDirectory objects is covered in the appropriate chapter on that topic. For example, User and Group object management is covered in Chapter 8, "Users and Network Security," whereas Printer object management is covered in Chapter 13, "OES Printing Services." Partition OperationsYou will be required to make three primary partition operations:
WARNING eDirectory does a great deal of work when performing partition operations. In larger eDirectory environments, each of the operations described in the following sections can take a significant amount of time to process completely. Furthermore, each operation has to complete before the next can begin. Make sure you take this into account when planning these tasks. CREATE A PARTITIONThe first operation we want to look at is creating a partition. As mentioned earlier, partitioning the tree serves to break up the eDirectory database into chunks that can be distributed across multiple servers for fault tolerance and increased performance. If you want to create a new partition, complete the following steps in iManager:
By default, the Master replica of the new partition is created on the server that maintains the Master replica of the parent partition. Read/Write replicas are stored on servers that maintain Read/Write replicas of the parent partition. You can move or change replica placement after the partition has been created, if desired. MERGE A PARTITIONSometimes you want to consolidate partitions, such as when moving from an older NDS environment to a much more scalable eDirectory tree. To merge a partition with its parent, complete the following steps in iManager:
When merged, all replicas of the child partition are removed and the child partition data will be replicated to the existing parent partition replicas. MOVE A PARTITIONThe partition move operation is commonly known as a prune and graft. It involves moving a partition and all its associated containers and objects from one location in the tree to another (pruning a branch from one part of the tree and grafting it in somewhere else). This is the most complex of the partition operations, so note the following qualifications before attempting a partition move:
If you want to prune and graft a partition, complete the following steps in iManager:
The summary screen lists all servers involved in the Move operation so that you can make sure everything is in good shape before attempting the move. Replica OperationsNow that you have eDirectory partitions created and situated within the tree, you might notice that the default placement for the replicas is less than perfect. After all, you probably don't want all Master replicas on one server, and you want to avoid replicating across expensive WAN links, as discussed previously. Replica operations, similar to partition operations, are accomplished from iManager in Partition and Replica Management. There are four primary replica operations:
Selecting Replica View in iManager shows you all servers that hold replicas of the selected partition. These servers form the replica ring. NOTE You will likely see Subordinate reference replicas listed in the iManager Replica View. However, Subordinate references are not manageable in iManager, so their placement is purely informational. ADD A REPLICAIf you want to place a partition replica on a server that does not currently have a copy of that partition, complete the following steps in iManager:
When created, the new partition will participate in all replication processes for that partition. Too many replicas can slow down partition operations significantly, so try to limit the number of replicas to three. CHANGE THE REPLICA TYPESometimes it is useful to be able to change the type of an existing replica. For example, if a Master replica is stored on a server and it is going down for a hardware upgrade, you can change an existing Read/Write replica to be the Master so that eDirectory partition operations can continue normally. NOTE You cannot change the type of a Master replica because a Master replica must exist for every partition. If you want to change a Master replica, change an existing Read/Write replica to be the new Master, and the existing Master will automatically be converted to a Read/Write. If you want to change the type of a replica, complete the following steps in iManager:
The replica will immediately start behaving as the new replica type you have selected. NOTE You cannot create a Master replica from a Filtered replica. DELETE A REPLICASometimes, when partitions have been merged or moved, a given replica is no longer necessary. To delete an existing replica from a server, complete the following steps in iManager:
The replica is removed from the server on which it was stored, and all future partition operations will include only the remaining replicas. CREATE A FILTERED REPLICAIf you are using Filtered replicas in your network, you can configure them with the Replica Wizard option in iManager. To create a Filtered replica, complete the following steps in iManager:
Filtered replicas are often used when eDirectory is sharing data with an external system, such as another directory or database, but only a subset of eDirectory information is shared. Tree OperationsThere are a few operations that you can perform on an entire eDirectory tree, and these are available from iManager as well. Each of these operations is available under eDirectory Maintenance:
NOTE Tree operations are complex operations that are not recommended for those who are not experienced eDirectory administrators. You can easily damage trees with these operations, so be very careful and perform these types of tree operations only when it is absolutely necessary. RENAME A TREEOnce in a while it might become necessary to rename an eDirectory tree. Perhaps an organizational name change has occurred, or you are moving to match your directory-naming scheme to that being used on the Web. Whatever the reason, you can rename your tree by completing the following steps in iManager:
The utility will first perform a check on the tree to be sure that it can be renamed successfully. When the rename is complete, you will be prompted to log out and log back in to the "new" tree. The terminal-based ndsmerge utility can also be used to rename a tree. To perform this operation with this utility, open up a terminal and execute the following command: ndsmerge r <target-tree> <source-admin> MERGE TWO TREESiManager and the terminal-based ndsmerge utility both have the capability to perform a tree merge. During a tree merge, a source tree is inserted into a target tree such that the tree branches at the Organization level, with each branch corresponding to the contents of one of the formerly distinct trees. To perform a tree merge from iManager, complete the following steps:
The utility will first perform a check on both trees to be sure that they can be successfully merged. If you encounter an error during this check process, follow the instructions to resolve the conflict and try the merge again. To perform a tree merge using the ndsmerge terminal utility, the source and destination trees, along with administrative credentials must be specified on the command line as in the following example: ndsmerge m <target-tree> <target-admin> <source-admin> GRAFT ONE TREE INTO ANOTHERA graft is a subset of a merge, in which you can choose the insertion point for the source tree objects. During a tree graft, a source tree is inserted into the specified location of a target tree. The source tree is then converted into a Domain object and it and all of its contents become part of the target tree. To graft one tree into another, complete the following steps:
The utility will first perform a check on both trees to be sure that they can be successfully merged. If you encounter an error during this check process, follow the instructions to resolve the conflict and try the merge again. To perform a tree graft using the ndsmerge terminal utility, the source and destination trees, target container, and administrative credentials, must all be specified on the command line as in the following example: ndsmerge m <target-tree> <target-admin> <source-admin> <target-container> NOTE For more information on ndsmerge, please see ndsmerge help. Monitoring and Maintaining eDirectoryThis section identifies some common administrative tasks that will help you effectively monitor the operation of eDirectory in your network and make little repairs as they are found. After all, the one thing more impressive than resolving a serious network problem is preventing it from occurring in the first place. Although this is not always possible, a program of active monitoring and proactive maintenance will go a long way toward getting you home on time at night. For more information on Novell management tools, see Chapter 5. The following tasks are a starting point for maintaining your eDirectory environment. By monitoring eDirectory process execution, you can see every type of communication activity and determine whether any errors are being reported. The best way to keep track of the activities of eDirectory processes is through iMonitor (see Figure 7.9). iMonitor provides comprehensive trace capabilities for eDirectory. More detailed information on DSTrace capabilities in iMonitor is available in Appendix C, "eDirectory Reference Materials." Figure 7.9. The eDirectory process monitoring configuration in iMonitor.To access the iMonitor Trace page, use a browser to connect to iMonitor and click the Trace Configuration icon in iMonitor's Header frame. iMonitor can be accessed from the Novell eDirectory 8.7 Welcome page found on the OES home page, or can be accessed directly using the iMonitor URL. The iMonitor URL is http://www.quills.com:8028/nds/summary iMonitor Trace gives you web-based access to monitor all eDirectory processes. Tracing eDirectory activity involves the following tasks:
eDirectory traces provide a powerful tool to track eDirectory processes and monitor operations when troubleshooting directory issues. NOTE There is also a terminal-based trace utility called ndstrace. The ndstrace utility can be used directly on an OES Linux terminal to view eDirectory activity. For information on using ndstrace, enter help ndstrace after starting the ndstrace utility. VERIFY THE VERSION OF EDIRECTORYEven if you don't apply updates immediately, it's a good idea to be aware of what updates exist and, more importantly, what issues they are intended to resolve. Keep track of the versions that you have installed on your servers so that as you review Novell support documents, you can keep an eye out for any problems that might relate to your environment. NOTE With the release of eDirectory in NetWare 6, Novell implemented a new versioning scheme in an attempt to eliminate inconsistencies in the previous model. Although still known as eDirectory v8.6 or 8.7 to provide eDirectory customers with a version context they are familiar with, the build version takes a considerably different format. For example, the build version of eDirectory 8.7 that ships with OES Linux is 10551.46. You can check the version of eDirectory that you are currently running on any server in the following ways:
NOTE Review Novell's support website, http://support.novell.com, on at least a quarterly basis for updates to eDirectory files and utilities. VERIFY THAT TIME IS SYNCHRONIZEDCheck the time sync status for each partition in the tree every couple of weeks. Keep an eye out for synthetic time messages that might keep background processes from completing properly. You can check the status of time synchronization between eDirectory servers in the following ways:
NOTE The ntpq utility can be used to check time synchronization status of the local NTP client daemon. Although being synchronized to an NTP time source is important, it is technically more important that servers with eDirectory are in time sync with each other. The ndsrepair and ndsmerge utilities are used to check time synchronization between servers in the same eDirectory tree. If time sync problems are located, they are often resolved by properly configuring the local NTP client. More information on configuring NTP is available in Chapter 2, "Installing OES Linux." If time is not synchronizing properly, you can run into problems with the timestamps that are maintained on eDirectory objects. Timestamps indicate when the object was last synchronized. Probably the best-known eDirectory timestamp issue is synthetic time. Synthetic time occurs when an eDirectory object has a modification timestamp ahead of current network time. If the period between current time and synthetic time is small, this problem will correct itself. However, if the period is large, it is possible to resolve the problem manually by reviewing the eDirectory communications processes to be sure that all replicas are communicating properly. From iMonitor, review the status of the Master replica from Agent Summary. You can drill down on the Master to review current state and a detailed set of statistics. Make sure the Master does not contain any errors, and that it is receiving current updates properly. Timestamps can be repaired in two ways:
WARNING This operation generates a large amount of eDirectory-related traffic as timestamps for all replicas are reset. VERIFY REPLICA SYNCHRONIZATIONYou can view synchronization status from several perspectives. However, making sure that all replicas of a given partition are synchronizing properly is probably one of the best ways to keep track of things. Check this every couple of weeks. You can check the sync status of a replica ring in the following ways:
If you begin to notice inconsistencies in replica rings, you can use the following general steps to diagnose and resolve the problems:
You should regularly use the preceding techniques to monitor synchronization activities and make sure that eDirectory is performing properly. CHECK EXTERNAL REFERENCESExternal references are pointers to eDirectory objects not stored in replicas on the current server. The check examines each external reference and makes sure that it links to a valid eDirectory object. Performing this check on a weekly basis makes sure that queries can traverse the tree properly. You can do one of the following to check external references:
One nice thing about the external reference check is that it will list any obituaries in your tree. Obituaries are references to deleted objects that are maintained until word of the deletion has been propagated to all servers hosting replicas of the affected partition. It is possible for obituaries and other types of external references to become corrupt or get stuck in the tree. One thing that can cause this is problems with network addresses. To resolve network referral problems, do the following:
Checking external references in this way will help ensure the health and smooth operation of your eDirectory environment. CHECK THE EDIRECTORY SCHEMAWhenever you make changes to the eDirectory schema, confirm that all servers hosting eDirectory replicas are properly receiving schema updates. You can check the schema synchronization status in iMonitor by selecting Agent Process Status, and then reviewing the data under the Schema Sync Status heading. It is possible that an eDirectory server, due to communication problems or corruption of synchronization timestamps, will fail to receive schema updates as they are applied to the eDirectory environment. The resulting schema inconsistencies can be resolved by doing the following:
Unless you are making frequent changes to the schema, these types of activities shouldn't be necessary, but you should be aware of how such schema issues can be resolved. REVIEW TREE FOR UNKNOWN OBJECTSOn a monthly basis, search eDirectory for unknown objects. You can do this from iManager by completing the following steps (you can also search for unknown objects from ConsoleOne):
Unknown objects can indicate resources that have not been properly installed or removed from the tree. However, they can also indicate that iManager or ConsoleOne does not have a snap-in capable of recognizing that object type, so don't immediately assume that unknown objects need to be deleted. It is also possible to get eDirectory object and attribute inconsistencies when replicas of the same partition, for whatever reason, have different information stored about the same eDirectory object or object attribute. In order to isolate the server(s) that have the faulty information, it is necessary to unload eDirectory on other servers. This type of troubleshooting can only be done during off hours. In order to troubleshoot this type of problem, do the following:
These tasks will help you ensure the object health within your eDirectory tree and stay on top of the health of your eDirectory environment. |
|