Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

More documents

Recommendations

Info

3 changetype: add 4 attributeTypes: ( 2.5.4.12 NAME ’title’ DESC ’Standa 5 rd Attribute’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{ 6 64} SINGLE-VALUE X-NDS_NAME ’Title’ X-NDS_NOT_SCHED 7 _SYNC_IMMEDIATE ’1’ X-NDS_LOWER_BOUND ’1’) 8 novdocx (en) 6 April 2007 Adding an Optional Attribute to an Existing Object Class Although adding new schema elements is an acceptable practice, modifying or extending existing schema elements is usually dangerous. Because every schema element is uniquely identified by an OID, when you extend a standard schema element, you effectively create a second definition for the element even though it still uses the original OID. This can cause incompatibility problems. There are times when it is appropriate to change schema elements. For example, you might need to extend or modify new schema elements as you refine them during development. Instead of adding new attributes directly to a class, you should generally use auxiliary classes only to • Add new attributes to an existing object class. • Subclass an existing object class. 5.3.3 Adding or Removing Auxiliary Classes The following sample LDIF file creates two new attributes, creates an auxiliary class with these new attributes, then adds an inetOrgPerson entry with the auxiliary class as an object class of the entry and with values for the auxiliary class attributes. version: 1 # Add an attribute to track a bear’s hair. The attribute is # multi-valued, uses a case ignore string syntax, # and has public read rights # Values may include: long hair, short, curly, straight, # none, black, and brown # X-NDS_PUBLIC_READ ’1’ The 1 allows public read, # 0 denies public read dn: cn=schema changetype: modify add: attributeTypes attributeTypes: ( 2.16.840.1.113719.1.186.4.10 NAME ’bearHair’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-NDS_PUBLIC_READ ’1’ ) # add an attribute to store a bear’s picture dn: cn=schema changetype: modify add: attributeTypes attributeTypes: ( 2.16.840.1.113719.1.186.4.11 NAME ’bearPicture’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 SINGLE-VALUE ) # create an Auxiliary class for the bearfeatures dn: cn=schema changetype: modify add: objectclasses 40 Novell eDirectory 8.8 Troubleshooting Guide
objectclasses: (2.16.840.1.113719.1.186.6.101 NAME ’bearFeatures’ MAY (bearHair $ bearPicture) AUXILIARY) # now create a user named bobby dn: cn=bobby,o=bearcave changetype: add cn: bobby sn: bear givenName: bobby bearHair: Short bearHair: Brown bearHair: Curly bearPicture:< file:///c:/tmp/alien.jpg objectClass: top objectClass: person objectClass: inetOrgPerson objectClass: bearFeatures novdocx (en) 6 April 2007 # now create a person named john that will later be changed # into a bear when bearFeatures is added to its objectClass # list dn: cn=john,o=bearcave changetype: add cn: John sn: bear givenName: john objectClass: top objectClass: person objectClass: inetOrgPerson # now morph john into a bear by adding bearFeatures dn: cn=john,o=bearcave changetype: modify add: objectClass objectClass: bearFeatures - add: bearHair bearHair: long bearHair: black #bearPicture:< file:///c:/tmp/john.jpg> - # to morph john back to a person, simply delete the # objectClass bearFeatures dn: cn=john,o=bearcave changetype: modify delete: objectClass objectClass: bearFeatures When removing auxiliary classes, you don't have to delete all of the values associated with the auxiliary class when you remove the auxiliary class from the objectClass list. eDirectory does this automatically. Troubleshooting LDIF Files 41
Page 1 and 2: Novell eDirectory 8.8 Troubleshooti
Page 3 and 4: Novell Trademarks Client32 is a tra
Page 5 and 6: Contents About This Book 9 novdocx
Page 7 and 8: multiserver tree after having moved
Page 9 and 10: About This Book This Troubleshootin
Page 11 and 12: 1Resolving Error Codes For a comple
Page 13 and 14: 2Installation and Configuration •
Page 15 and 16: DA_ADDR = IP_address_of_the_NetWare
Page 17 and 18: 3Determining the eDirectory Version
Page 19 and 20: • Run iMonitor. On the Agent Summ
Page 21 and 22: server. For example, an Agent Revis
Page 23 and 24: 4Log Files This section contains in
Page 25 and 26: 5Troubleshooting LDIF Files The Nov
Page 27 and 28: Component Record Delimiters Descrip
Page 29 and 30: 14 changetype: delete 15 The Modify
Page 31 and 32: Field newsuperior (optional) Descri
Page 33 and 34: 5.2 Debugging LDIF Files • “Ena
Page 35 and 36: Option Base DN Description Base dis
Page 37 and 38: Using the Novell Import Conversion
Page 39: 5.3.2 Adding a New Attribute To add
Page 43 and 44: 6Troubleshooting SNMP This section
Page 45 and 46: For any problem configuring the eDi
Page 47 and 48: 7Obituaries There has been a great
Page 49 and 50: If the obituary is a Primary obitua
Page 51 and 52: • Obituaries can change states on
Page 53 and 54: 8Migrating to Novell eDirectory Thi
Page 55 and 56: add:objectclasses objectclasses : (
Page 57 and 58: operatingSystemHotfix $ volumeCount
Page 59 and 60: 8.3.3 Migrating the Open LDAP Data
Page 61 and 62: 9Replication • Section 9.1, “Re
Page 63 and 64: 10Novell Public Key Infrastructure
Page 65 and 66: 1Troubleshooting Utilities on Linux
Page 67 and 68: Option Description -P Replica and P
Page 69 and 70: Option Optional Schema Enhancements
Page 71 and 72: a replica on the partition is synch
Page 73 and 74: 11.6 Using ndstrace The ndstrace ut
Page 75 and 76: Trace Flag FRAG IN Description Mess
Page 77 and 78: Trace Flag Parameters Description !
Page 79 and 80: Trace Flag Parameters Description *
Page 81 and 82: 12NMAS on Linux and UNIX • Sectio
Page 83 and 84: 13Troubleshooting on Windows • Se
Page 85 and 86: 14Accessing HTTPSTK When DS Is Not
Page 87 and 88: 15Encrypting Data in eDirectory In
Page 89 and 90: OR 2. Disable ER at the parent or c
Page 91 and 92:
16The eDirectory Management Toolbox
Page 93 and 94:
17SASL-GSSAPI This section discusse
Page 95 and 96:
18Miscellaneous • Section 18.1,
Page 97:
18.5 Disabling SecretStore An eDire
show all

Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?