Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

More documents

Recommendations

Info

1 version: 1 2 dn: c=US 3 changetype: add 4 objectClass: top 5 objectClass: country 6 7 dn: l=San Francisco, c=US 8 changetype: add 9 objectClass: top 10 objectClass: locality 11 st: San Francisco 12 14 dn: ou=Artists, l=San Francisco, c=US 15 changetype: add 16 objectClass: top 17 objectClass: organizationalUnit 18 telephoneNumber: +1 415 555 0000 19 20 dn: cn=Peter Michaels, ou=Artists, l=San Francisco, c=US 21 changetype: add 22 sn: Michaels 23 givenname: Peter 24 objectClass: top 25 objectClass: person 26 objectClass: organizationalPerson 27 objectClass: iNetOrgPerson 28 telephonenumber: +1 415 555 0001 29 mail: Peter.Michaels@aaa.com 30 userpassword: Peter123 31 novdocx (en) 6 April 2007 The Delete Change Type Because a delete change record specifies the deletion of an entry, the only fields required for a delete change record are the distinguished name specifier and a delete change type. The following is an example of an LDIF file used to delete the four entries created by the LDIF file shown in “The Add Change Type” on page 27. IMPORTANT: To delete entries you have previously added, reverse the order of the entries. If you don't do this, the delete operation fails because the container entries are not empty. 1 version: 1 2 dn: cn=Peter Michaels, ou=Artists, l=San Francisco, c=US 3 changetype: delete 4 5 dn: ou=Artists, l=San Francisco, c=US 8 changetype: delete 9 10 dn: l=San Francisco, c=US 11 changetype: delete 12 13 dn: c=US 28 Novell eDirectory 8.8 Troubleshooting Guide
14 changetype: delete 15 The Modify Change Type The modify change type lets you to specify the addition, deletion, and replacement of attribute values for an entry that already exists. Modifications take one of the following three forms: novdocx (en) 6 April 2007 Element add: attribute type delete: attribute type Description A keyword indicating that subsequent attribute value specifiers for the attribute type should be added to the entry. A keyword indicating that values of the attribute type are to be deleted. If attribute value specifiers follow the delete field, the values given are deleted. If no attribute value specifiers follow the delete field, then all values are deleted. If the attribute has no values, this operation will fail, but the desired effect will still be achieved because the attribute had no values to be deleted. replace: attribute type A keyword indicating that the values of the attribute type are to be replaced. Any attribute value specifiers that follow the replace field become the new values for the attribute type. If no attribute value specifiers follow the replace field, the current set of values is replaced with an empty set of values (which causes the attribute to be removed). Unlike the delete modification specifier, if the attribute has no values, the replace will still succeed. The net effect in both cases is the same. The following is an example of a modify change type that will add an additional telephone number to the cn=Peter Michaels entry. 1 version: 1 2 dn: cn=Peter Michaels, ou=Artists, l=San Francisco, c=US 3 changetype: modify 4 # add the telephone number to cn=Peter Michaels 4 add: telephonenumber 5 telephonenumber: +1 415 555 0002 6 Just as you can combine a mixture of modifications in a single LDAP modify request, you can specify multiple modifications in a single LDIF record. A line containing only the hyphen (-) character is used to mark the end of the attribute value specifications for each modification specifier. The following example LDIF file contains a mixture of modifications: 1 version: 1 2 3 # An empty line to demonstrate that one or more 4 # line separators between the version identifier 5 # and the first record is legal. 6 7 dn: cn=Peter Michaels, ou=Artists, l=San Francisco, c=US 8 changetype: modify Troubleshooting LDIF Files 29
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: Component Record Delimiters Descrip
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 and 40: 5.3.2 Adding a New Attribute To add
Page 41 and 42: objectclasses: (2.16.840.1.113719.1
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

Create successful ePaper yourself

Delete template?

Save as template?