How to enable/disable auxiliary class support for DS 6.x and 7.x servers
(Last modified: 04Sep2003)
This document (10083622) is provided subject to the disclaimer at the end of this document.
goal
How to enable/disable auxiliary class support for DS 6.x and 7.x servers
How to enable/disable auxiliary class support on NetWare 4.x
How to enable/disable auxiliary class support for DS 7.x servers
fact
Novell NetWare 4.x
Novell Directory Services 6
Novell Directory Services 7
DS.NLM 6.17 or less
DS.NLM 7.61 or less
NetWare 4.x servers hold replicas of objects with auxiliary classes associated
symptom
Objects are unknown on NetWare 4.x servers
Objects are unknown in ConsoleOne and NWAdmin
Objects have a yellow question mark next to them in ConsoleOne or NWAdmin.
cause
The reason that the objects go unknown in the first place is because DS.NLM version 6.17 or earlier on NetWare 4.x and DS.NLM version 7.61 or earlier on Netware 5.x do not understand auxiliary classes. Although the objects show up as unknown on the DS 6.x or DS 7.x side, the objects are still known on the NDS 8 and greater servers. This is working as designed so that the servers running NDS 8 or higher can synchronize the objects without the NetWare 4.x server complaining. Schema flagged as auxiliary class is not legal in DS 6.17 or earlier and DS 7.61 or earlier, so any object flagged this way will be rejected during synchronization. When an object from an NDS 8 or greater server that has an auxiliary class associated is synchronized to the older DS 6.x and/or DS 7.x servers, the NDS 8 server prepares the object by taking all of the auxiliary class information and storing it in a new attribute called AuxClass Object Class Backup. It then flags the object as Unknown. An Unknown object is legal and will synchronize to the older versions of DS. When an NDS 8 or greater server receives an unknown object in synchronization, it checks to see if their is an auxClasscompatibility attribute. If there is, it replaces the Unknown class with the information in the auxClasscompatibility attribute and the object appears as normal.
fix
By default, the new DS.NLM's (versions 6.19 and/or 7.62 and greater) addresses the issue of objects with auxiliary classes showing up as Unknown objects in NWAdmin or ConsoleOne. This new NLM does NOT let you create auxiliary classes using DS 6.x or 7.x servers. You still need a server in the replica ring that is running NDS 8 or greater in order to create auxiliary classes and associate those classes with objects. All the new DS.NLM does is intercept the client reponses and substitutes the class information located in the Object Class attribute with the information located in the AuxClass Object Class Backup attribute. If you look at the object in DSVIEW or NDS iMonitor, the object will still show up with an Unknown class, but NWAdmin and ConsoleOne will now show up as a known object. You should be able to administer this object with NWAdmin or ConsoleOne as if it were a normal object.
note
NOTE: DS.NLM 6.19 or greater and DS.NLM 7.62 or greater are available for public download at http://support.novell.com/filefinder under files DS621.EXE and DS762B.EXE. They are also available in the NetWare Deployment Manager for NetWare 6.5.
document
Document Title: | How to enable/disable auxiliary class support for DS 6.x and 7.x servers |
Document ID: | 10083622 |
Solution ID: | NOVL89821 |
Creation Date: | 27May2003 |
Modified Date: | 04Sep2003 |
Novell Product Class: | NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.