Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

More documents

Recommendations

Info

1 version: 1 2 dn: c=US 3 objectClass: top 4 objectClass: country 5 6 dn: l=San Francisco, c=US 7 objectClass: top 8 objectClass: locality 9 st: San Francisco 10 11 dn: ou=Artists, l=San Francisco, c=US 12 objectClass: top 13 objectClass: organizationalUnit 14 telephoneNumber: +1 415 555 0000 15 16 dn: cn=Peter Michaels, ou=Artists, l=San Francisco, c=US 17 sn: Michaels 18 givenname: Peter 19 objectClass: top 20 objectClass: person 21 objectClass: organizationalPerson 22 objectClass: iNetOrgPerson 23 telephonenumber: +1 415 555 0001 24 mail: Peter.Michaels@aaa.com 25 userpassword: Peter123 26 novdocx (en) 6 April 2007 This LDIF file is composed of the following parts: Component Version Specifier Description The first line of an LDIF file contains the version. Zero or more spaces are allowed between the colon and the version number, which is currently defined to be 1. If the version line is missing, any application processing the LDIF file is allowed to assume that the file is version 0. It’s also possible that the LDIF file could be rejected as syntactically incorrect. Novell utilities that process LDIF assume a file version of 0 when the version line is missing. Distinguished Name Specifier The first line of every content record (lines 2, 6, 11, and 16 in the example above) specifies the DN of the entry that it represents. The DN specifier must take one of the following two forms: • dn: safe_UTF-8_distinguished_name • dn:: Base64_encoded_distinguished_name Line Delimiters The line separator can be either a line feed or a carriage return/line feed pair. This resolves a common incompatibility between Linux and Solaris text files, which use a line feed as the line separator, and MS-DOS* and Windows text files, which use a carriage return/ line feed pair as the line separator. 26 Novell eDirectory 8.8 Troubleshooting Guide
Component Record Delimiters Description Blank lines (lines 5, 10, 15, and 26 in the example above) are used as record delimiters. Every record in an LDIF file including the last record must be terminated with a record delimiter (one or more blank lines). Although some implementations will silently accept an LDIF file without a terminating record delimiter, the LDIF specification requires it. novdocx (en) 6 April 2007 Attribute Value Specifier All other lines in a content records are value specifiers. Value specifiers must take on one of the following three forms: • Attribute description: value • Attribute description:: Base64_encoded_value • Attribute description: < URL 5.1.3 LDIF Change Records LDIF change records contain modifications to be made to a directory. Any of the LDAP update operations (add, delete, modify, and modify DN) can be represented in an LDIF change record. LDIF change records use the same format for the distinguished name specifier, attribute value specifier, and record delimiter as LDIF content records. (See “LDIF Content Records” on page 25 for more information.) The presence of a changetype field is what distinguishes an LDIF change record from an LDIF content record. A changetype field identifies the operation specified by the change record. A changetype field can take one of the following five forms: Form changetype: add changetype: delete changetype: moddn changetype: modrdn changetype: modify Description A keyword indicating that the change record specifies an LDAP add operation. A keyword indicating that the change record specifies an LDAP delete operation. A keyword indicating that the change record specifies an LDAP modify DN operation if the LDIF processor is bound to the LDAP server as a version 3 client or a modify RDN operation if the LDIF processor is bound to the LDAP server as a version 2 client. A synonym for the moddn change type. A keyword indicating that the change record specifies an LDAP modify operation. The Add Change Type An add change record looks just like a content change record (see “LDIF Content Records” on page 25) with the addition of the changetype: add field immediately before any attribute value fields. All records must be the same type. You can’t mix content records and change records. Troubleshooting LDIF Files 27
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: 5Troubleshooting LDIF Files The Nov
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 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?