Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

More documents

Recommendations

Info

• Far less desirable method: If all servers in the replica ring that have a copy of the orphaned obituary are older than eDirectory 8.6, load DSBrowse with the -a option, browse to the object, then time-stamp the entry. This will make the object as it exists on this server the authoritative copy. We do not recommend making objects authoritative as a matter of practice. Resolving Orphaned Obituaries on Extrefs novdocx (en) 22 June 2009 • Less desirable method: Run DSRepair with the time stamp option selected. • Less desirable method: Move a real replica to the server, wait for it to turn on, then wait for the obituary to be processed. If the obituary is not processed, use the information in Section 9.4, “Troubleshooting Tips,” on page 56 to resolve the issue now that the object is on a real replica. After the obituary has processed, the replica can be removed if desired. 9.4.2 Previous Practices In the past, several different strategies have been employed to resolve stuck obituaries. Some of these strategies involve expensive partitioning operations, or the use of undocumented features that might cause problems in the future. The first strategy was to switch which replica held the master. This would work in some cases because the master is the agent responsible for moving the Back Link obituaries through their various states. In the case where the replica was inconsistent and the master didn't hold the deleted object, switching masters to an agent that held the deleted entry with its obituaries would give the new agent the license to push the obituaries through their states and eventually purge it out. Send Single Entry is a much cleaner and less dangerous way to resolve obituaries that are stuck because the replica is inconsistent. The second strategy used was to run DSRepair with certain switches to delete all obituaries. (There is a third-party application which resolves stuck obituaries by launching DSRepair.) We do not recommend this strategy. Using those switches will delete all obituaries on this agent, which means that obituaries that are not stuck might also be removed, creating further replica inconsistencies and more stuck obituaries. Because this is not a distributed operation, you must run DSRepair on all of the servers with stuck obituaries, which increases the odds that one of those servers has obituaries for another partition which will be prematurely deleted. The premature deletion of obituaries can cause additional orphaned obituaries and, in turn, cause problems which can be found years later when you change replicas types, add new replicas, or perform other partitioning operations. The third strategy used was to make objects authoritative, either using DSBrowse with the advanced mode operation and time stamping the entry, or running DSRepair with the -0T switch. This forces the entry to become authoritative and synchronize out to all other replicas. This should be done with great care because you might lose data changed on other servers. We recommend that this be a rarely employed method of obituary cleanup. 58 Novell eDirectory 8.8 Troubleshooting Guide
10Migrating to Novell eDirectory This chapter explains the process to migrate to Novell ® eDirectory TM from: • Section 10.1, “Migrating the Sun ONE Schema to Novell eDirectory,” on page 59 • Section 10.2, “Migrating the Active Directory Schema to Novell eDirectory Using ICE,” on page 62 10.1 Migrating the Sun ONE Schema to Novell eDirectory To migrate the Sun ONE* schema to Novell eDirectory, complete the following steps: “Step 1: Perform the Schema Cache Update Operation” on page 59 “Step 2: Rectify the Error LDIF File to Eliminate the Errors” on page 60 “Step 3: Import the LDIF File” on page 62 10.1.1 Step 1: Perform the Schema Cache Update Operation You can write the errors encountered while comparing the schema to an error file using the following command: ice -e LDIF error file name -C -a -SLDAP -s Sun ONE server -p Sun ONE port - DLDAP -s eDirectory server -p eDirectory port For example: ice -e err.ldf -C -a -SLDAP -s sun_srv1 -p sun_port1 -DLDAP -s edir_srv2 -p edir_port2 Any errors encountered while comparing the schema is written to the error file (err.ldf in the example). You do not need to login to perform this operation unless one of the servers require authentication in order to read the Root DSE. Microsoft Active Directory requires authentication to read the Root DSE. 10 novdocx (en) 22 June 2009 Migrating to Novell eDirectory 59
Page 1 and 2:
Troubleshooting Guide AUTHORIZED DO
Page 3 and 4:
Novell Trademarks Client32 is a tra
Page 5 and 6:
Contents About This Book 11 novdocx
Page 7 and 8: 10.2.1 Step 1: Perform the Schema C
Page 9 and 10: 23.7.3 On Windows . . . . . . . . .
Page 11 and 12: About This Book This Troubleshootin
Page 13 and 14: 1Resolving Error Codes For a comple
Page 15 and 16: 2Installation and Configuration •
Page 17 and 18: 4c Edit the /etc/slpuasa.conf to ad
Page 19 and 20: pkgadd -d NOVLniu0.pkg 4 Start eDir
Page 21 and 22: 3Determining the eDirectory Version
Page 23 and 24: • Run iMonitor. On the Agent Summ
Page 25 and 26: 4Log Files This section contains in
Page 27 and 28: 5Troubleshooting LDIF Files The Nov
Page 29 and 30: Component Record Delimiters Descrip
Page 31 and 32: The Modify Change Type The modify c
Page 33 and 34: Field newsuperior (optional) Descri
Page 35 and 36: 5.2 Debugging LDIF Files • “Ena
Page 37 and 38: Option Base DN Scope Description Ba
Page 39 and 40: Using the Novell Import Conversion
Page 41 and 42: 5.3.2 Adding a New Attribute To add
Page 43 and 44: objectclasses: (2.16.840.1.113719.1
Page 45 and 46: 6Troubleshooting SNMP This section
Page 47 and 48: SERVER test-server test-server is t
Page 49 and 50: 7iMonitor • Section 7.1, “Brows
Page 51 and 52: 8iManager • Section 8.1, “LDAP
Page 53 and 54: 9Obituaries There has been a great
Page 55 and 56: If the obituary is a Primary obitua
Page 57: • Obituaries can change states on
Page 61 and 62: Option 3: Add cn to the definition
Page 63 and 64: changetype: modify delete: objectcl
Page 65 and 66: Any records that contain references
Page 67 and 68: 1Schema This section includes infor
Page 69 and 70: 12ndsrepair • Section 12.1, “Ru
Page 71 and 72: 13Replication • Section 13.1, “
Page 73 and 74: 14Clone DIB Issues • Section 14.1
Page 75 and 76: 15Novell Public Key Infrastructure
Page 77 and 78: 16Troubleshooting Utilities on Linu
Page 79 and 80: Option Description -P Replica and P
Page 81 and 82: Option Optional Schema Enhancements
Page 83 and 84: Determines the complete synchroniza
Page 85 and 86: 16.5.2 Troubleshooting ndsrepair Er
Page 87 and 88: Trace Flag DNS DRLK DVRS Descriptio
Page 89 and 90: Trace Flag Parameters Description *
Page 91 and 92: Trace Flag Parameters Description !
Page 93 and 94: 17NMAS on Linux and UNIX • Sectio
Page 95 and 96: 18Troubleshooting on Windows • Se
Page 97 and 98: 19Accessing HTTPSTK When DS Is Not
Page 99 and 100: 20Encrypting Data in eDirectory In
Page 101 and 102: Action 1. Upgrade the server to a c
Page 103 and 104: 21The eDirectory Management Toolbox
Page 105 and 106: 2SASL-GSSAPI This section discusses
Page 107 and 108: Action: Do the following: 1 Update
Page 109 and 110:
23Miscellaneous • Section 23.1,
Page 111 and 112:
These parameters are available in /
Page 113 and 114:
23.7.3 On Windows 1 Go to the novel
Page 115 and 116:
23.19 ndsd Not Listening at the Loo
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?