Checking the NDS Revision Level

Other NetWare 4 Patches and Updates

NDS Synchronisation Issues

Directory Tools

• Using DSREPAIR.NLM
  
• Using DSTRACE
  
• Using DSVIEW.NLM

Installation and Migration Issues

• Proper Use of the INSTALL Utility
  
• Installing NetWare 4 Servers into New and Existing Directory Tree
  
• Removing Directory Services with INSTALL

Changing a Server’s Name or Internal IPX Address

Removing the Server from the Directory Tree

Don’t Let Volume SYS Run Out of Space

Determining the Size of the NDS Partition on the Fileserver

Miscellaneous Tips

(15th April 1994)

Checking the NDS Revision Level

NetWare 4.01 was shipped with DS.NLM at revision level 290. However, all NetWare 4 servers must be patched to use the 296 level of NDS. This is the most important service change to enhance NDS reliability. The patch to upgrade from 290 to 296 level of DS.NLM is called DSPAT2.EXE, and it is applied to the SERVER.EXE. (DSPAT2.EXE is available on Apricot Insight BBS AREA37 as part of 401PT1.EXE, a self-extracting file containing a number of NetWare 4.01 patches and up dates.

The revision level of Directory Services on any server can be determined by using the MODULES command at the server prompt. The change level is in parentheses following the module name, as shown below:

DS.NLM
NetWare Directory Services (296)
Version 4.01 25 February 1994

Other NetWare 4 Patches and Updates

It is beneficial to keep up to date on the latest patches and updates for NetWare 4. An up-to-date list of all NetWare patches can be found in the following file:

NWUPDATE.TXT Available from Apricot Insight BBS AREA37

Since the release of NetWare 4.01, several fixes to Directory Services have been made. These and a number of other patches have recently been consolidated into the following file:

401PT1.EXE Available from Apricot Insight BBS AREA37

We strongly suggest you apply this group of patches for NetWare 4.01.

NDS Synchronisation Issues

Allow time for the Directory to synchronise. Often not enough time is allowed for the Directory to synchronise after changes are made. Any significant operation, such as placing a new replica on a server, removing a replica, or rebuilding a replica from the master, can require some time to complete because of the large amounts of data that are exchanged between replicas.

The time required to complete the operation is largely a function of the available bandwidth in the network, the size of the replicas, the number of replicas, and the state of servers and links. Novell have experienced times ranging from a few seconds to an hour or more for partition and replica operations. Be patient, when the data is all transferred, the operation will complete.

Note: In operations where large amounts of information are processed over very fast network links, the server processor speed can become a limiting factor. Take this into consideration when performing partition and replica operations.

The NetWare 4 partition management utilities (PARTMGR or the Partition Manager tool in NWAdmin) are used to request partition and replica operations. However, it is important to understand how these utilities function. When you request one of these operations, the utility returns control to your workstation immediately so you can continue working. Meanwhile, the actual operation is occurring in the background.

You can use the partition management utilities to see if the partition has been placed on or removed from the requested server. Just remember that some operations can take an hour or more to complete, depending on the size of the partition and the other factors mentioned above.

Directory Tools

Using DSREPAIR.NLM
The DSREPAIR.NLM utility is provided with NetWare 4 to repair problems with the Directory Services Database on a single server. It does not correct problems on other servers. It must be run on each server on which you wish to correct Directory database errors.

DSREPAIR checks the following information in the Directory:

• The local Directory tree structure
• The records that make up the Directory on the server
• The schema of the Directory
• Objects in replicas
  - Local references
  - Mandatory and optional properties
• Initial states
• File system trustees on mounted volumes
• Mail directories
• Stream syntax files

DSREPAIR will also allow the designation of a new master replica for a partition. This option is usually used to create a new master for a partition which has lost its master through physical server failure.

DSREPAIR will not do the following:

• Check or perform replica synchronisation
• Check or perform schema synchronisation
• Repair all initial states
• Guarantee local database recovery
• Remove lost Server objects
• Configure time synchronisation
• Synchronise repairs with other replicas (you need to synchronise damaged replicas manually using partition manager)

DSREPAIR changes inconsistent objects to Unknown objects when they do not have mandatory properties or are invalid in other respects (their properties don’t meet minimum requirements for an object type). Unknown objects can be deleted but cannot be changed back to their original object type. (In NetWare 4.01, Unknown objects are represented by question mark icons in the NWAdmin utility.)

Using DSTRACE
NetWare Directory Services contains a simple tool that was originally used by the development engineers to monitor how NDS is functioning. While it was not designed as an end-user tool, DSTRACE can often be used to help to identify problems which may be related to NDS.

To start DSTRACE, type the following from the server console:

SET DSTRACE = ON

DSTRACE creates another server screen which will display information about the NDS synchronisation process. Access this screen by pressing <Alt><Esc> to cycle through the available server screens.

You may use the following optional DSTRACE commands

SET TTF = ON	Redirects trace information to a file (SYS:SYSTEM\DSTRACE.DBG)
SET DSTRACE = *r	Resets the trace file
SET TTF = OFF	Ends the trace to file

Note: If you turn on the TTF option, make sure you turn it off when you are done. Doing so will eliminate the overhead of writing trace information to the file. By default, the trace file will take no more than 1 MB of disk space. If the file reaches 1 MB, it will cycle around and start to write over the oldest information.

To edit the trace file from the server console, type the following command:

LOAD EDIT SYS:SYSTEM\DSTRACE.DBG

You can use DSTRACE to determine the “health” of a replica ring. To do so, watch the DSTRACE screen as the server contacts each member of its replica ring. When each contact ends with the “All Processed = YES” message, you can be reasonably sure that the partition is intact. You can then use the partition management utilities to perform your desired task.

Using DSVIEW.NLM

DSVIEW.NLM is available in the self extracting DSVIEW.EXE file on Apricot Insight BBS AREA 37. This utility can be used to view information about Directory partitions residing on a single server. It will not display information about partitions stored on other NetWare 4 servers.

To run DSVIEW.NLM, use RCONSOLE.EXE or go the console of the server where the NLM will be run and type LOAD DSVIEW.

The following information categories may be selected from the main menu:

1. Entry Information. Use this option to view information about the entries themselves (entries such as local ID, base class, creation time, subordinates, attributes, and attribute values). You can also navigate through the entries by “walking” the tree-for example, going from parent to child or from sibling to sibling.
   
   
2. Partition Information. The option displays the partitions located on the server.
   
   
3. Tree (Start at [Root]). This option displays the entries, beginning at [Root]. This is a quick way to return to the top of the tree.
   
   
4. Attribute Definitions. This option displays the attributes (properties) defined by the schema.
   
   
5. Class Definitions. This option displays the classes defined by the schema.
   
   
6. Server Information. This option displays information specific to the local server (such as name, address, file size of NDS database, and so on).

Installation and Migration Issues

Proper Use of the INSTALL Utility
The way customers occasionally misuse the install utility is another source of challenges in NetWare 4. The following review of how Install works will help you understand how best to use this utility.

Note: This discussion applies only to the version of Install that originally shipped with NetWare 4.01. The Install utility is currently being revised so that it does not create partitions in the way described below. The new version will be put on Apricot Insight when it is available.

Installing NetWare 4 Servers into New and Existing Directory Tree
When a server is being installed into a new OU that does not yet exist in the Directory, Install will create a new partition and store the Master replica of that partition on the newly installed server.

If the server is being installed into an OU that has already been created in the tree, Install will ask if the replica of the partition the server is being installed into should be created on this server. Many installers answer affirmatively to this prompt.

Note: Install will not prompt the user about whether a replica should be created if the server being installed is an upgrade from NetWare 3.1x to NetWare 4. By default, Install will create a replica on the server and upgrade the 3.1x bindery to the server’s context.

With large Directories, our experience has shown that it is better to answer “no” to this prompt. Install will wait for only a few minutes for the requested replica to be installed on the new server. If the replica has not been placed on the server during the short time allowed, the Install process fails.

When installing a new server in an existing NetWare 4 Directory tree, we recommend that you create the new target OU, if needed, with the NetWare 4 administration utilities (NETADMIN or NWAdmin). Do not use Install to create the OU unless this is the first server in the tree. After the server has been successfully installed into the Directory, you can create a replica on the server with the partition management utilities.

By using this alternate strategy, you can install the server in less time and eliminate troublesome errors. You can also grant rights to a subtree administrator to install the server if the partitioning is done first.

To install a server into the tree, use the following procedure:

1. Use DSTRACE to make sure the replica ring containing the OU (or the parent OU) where the server is to be installed is healthy.(See the section on DSTRACE for more information)
   
   
2. Ensure that the container into which the server will be installed exists before the installation begins. Don’t use Install to create the new partion. When Install asks if you would like a copy of this partion on your server, we recommend that you decline the option.
   
   
3. After installation, again use DSTRACE to make sure the replica ring is synchronised and healthy.
   
   
4. If you need a replica on the newly installed server, use the partion management tools to create it. Refer to Utilities Reference manual for instructions.

It is also a good idea to make sure the bindery context on the newly installed server is set to the correct OU. You can use either the SERVMAN NLM or the SET command. To use the SET command, type the following at the console prompt:

SET BINDERY CONTEXT <Enter>

Do not include an “=“ sign (as in SET BINDERY CONTEXT =) or else the bindery context will be set to nothing.

Removing Directory Services with INSTALL

Currently, improper use of the Install utility’s option to remove Directory Services from a server is a source of Directory problems. When users experience problems with most software packages, a typical reaction is to try unloading the software and reloading it. This is not an appropriate tactic when working with NDS. In fact, if done often enough in a short time, this procedure can result in an improperly synchronised Directory.

It is rarely necessary to remove Directory Services. We recommend that you remove NDS only if you are sure that this step will assist in your recovery process. You should have previously tried removing and reinstalling replicas with the partition management utilities. Remember to allow plenty of time for synchronisation to occur when objects in the Directory are changed.

Changing a Server’s Name or Internal IPX Address

NDS system information is stored on each NetWare 4 server. Server-related information is also used in various Directory Services operations. For example, the server name and internal IPX address is associated with the location of each replica. The proper procedure for changing a NetWare 4 server’s name or internal IPX address is as follows:

1. Change the appropriate lines in the AUTOEXEC.NCF file.
2. Down the server. The new server name and/or address will take effect when the server is brought back up again.

Allow sufficient time for these changes to be synchronised across the Directory. You can force the process that updates the server names and IPX addresses within the tree by using the DSTRACE command. At the server console, first type SET DSTRACE=ON and then SET DSTRACE=*L.

Note: In the next release of NetWare 4, the procedure for changing server names and addresses will be significantly enhanced.

Removing the Server from the Directory Tree

Servers may need to be removed from the tree for various reasons, but this procedure should not usually be necessary. Whenever possible, it is best to remove the server while it is still operational and the Directory can be properly updated. Proper removal of servers can significantly reduce the occurrence of problems with the Directory. Do not just turn off a NetWare 4 server and detach it from the network! Follow the correct procedures as outlined below.

If the server is operational and the Directory is synchronised, use the following procedure to remove the server from the tree:

1. Before removing the server, check the “health” of its replica ring using the procedure above in the DSTRACE section.
   
   
2. Using the partition manager tool in NWAdmin or the PARTMGR utility, designate a new Master replica for any Master which exists on the server to be removed. Allow sufficient time for the Directory to synchronise the new Master replica’s location information in all other replicas of the partition. (Look for the message “All Processed=Yes” on the DSTRACE screen.)
   
   
3. Again using NWAdmin or PARTMGR, delete all replicas from the server to be removed. Allow sufficient time for the Directory to synchronise the other replicas of each partition (“All Processed=Yes” on the DSTRACE screen).
   
   
4. Load the Install utility on the server to be removed. Select the “remove Directory Services” option to delete NDS from the server. Again, allow sufficient time for the Directory to synchronise each of the replicas of the partition which held the server object.
   
   
5. Turn off the server and remove it from the network.

To remove a server from the tree if the server has failed or is not available for some reason:

1. If the failed server had any Master replicas on it, you must designate a new location for the Master replica of that partition. To do this, follow the procedure below for each Master replica to be designated.
   
   
   1. Select another server that contains a replica of the partition, to be designated as the new Master.
      
      
   2. Using DSREPAIR, use option number 1 which allows you to change the repair options. Then select option 4 to designate the partition to be a Master. Return to the first DSREPAIR menu and repair the Directory, selecting the correct replicas to be designated as Masters.
      
      
   3. If the server contained any other Master replicas, repeat the above procedure for each one.
      
      
2. Using the administrative utilities (NWAdmin or NETADMIN), delete the Server object and its Volume objects from the Directory. Allow the Directory sufficient time to synchronise before performing other major Directory operations.
   
   

Don’t Let Volume SYS Run Out of Space

A NetWare 4 server’s SYS volume contains the NDS database in a hidden directory. This directory cannot be seen even with the NetWare NDIR command. The only way to view the size of the NDS is to use RCONSOLE and do a directory scan of SYS:_NETWARE. It is imperative that SYS not run out of disk space. If volume SYS becomes full, it causes NetWare’s Transaction Tracking System (TTS) to shut down. NDS tracks all writes to its database with TTS. If TTS is disabled, writing information to the Directory is also disabled. Writes to the Directory will not be allowed until TTS is enabled.

Note: Even if TTS is disabled, users can still log in to delete unneeded files and thus free up more disk space in SYS.

To prevent a server running out of space in SYS, we recommend the following:

• Set minimum disk space alerts so that you get a warning if the remaining space on SYS drops below the minimum. By default, NetWare sends a broadcast alert when the remaining space on a volume reaches 256 blocks. You can adjust the Volume Low Warning Threshold with the SET command at the server.
  
  
• Store users files and application files on a volume other than SYS.
  
  
• Store print queues on a volume other than SYS.
  
  

We also recommend that you put the following statement in the server’s STARTUP.NCF file:

SET AUTO TTS BACKOUT FLAG = ON

This flag causes the TTS systems to automatically back out all transactions which were not complete when the server failed. This eliminates the need for the administrator or server operator to respond to the TTS-related prompts when the server comes up after a failure.

Determining the Size of the NDS Partition on the Fileserver

You can only determine the size of the NDS partition on the fileserver by using RCONSOLE this is because the directory were the NDS information is stored is not visible by any other means.

The NDS information is stored in a directory called SYS:_NETWARE. You can access this directory by doing the following:

1. Run RCONSOLE.
   
   
2. Choose the target file server.
   
   
3. Press <Alt>+<F1>.
   
   
4. Select Directory Scan.
   
   
5. Type the following path and press <Enter>:
   SYS:_NETWARE

You are now at the desired directory and you can view NDS file information.

Miscellaneous Tips

Don’t panic and start deleting and reinstalling Directory Services.

Make sure the Directory is stable before you make changes in the Directory structure. Don’t split or join a partition that you suspect is experiencing a problem.

Ascertain whether the problem is related to the server or to the client software. Check to see that the NET.CFG file specifies the correct context and the correct preferred tree. If the problem is isolated to a single client, it probably isn’t an NDS or server problem. Working with the server to resolve a client problem will only cause frustration at best. At worst, it could lead to other NDS-related problems.

Keep a record of your diagnosis and the actions taken to correct Directory problems.