License:
Free

Download eDir_collisions_v1.0.tar

Program Input:

LDAP source server IP address 
Starting context in target eDirectory tree

Program Actions:

The program will use the IP address and context entered to extract the schema naming attributes and all object RDNs from the context entered and below. The schema naming values are then used with ‘regular expressions’ (regex) to identify all collisioned objects in the extracted data.

The collisioned object data is then ‘context reversed’ and sorted to produce all collisioned objects in container order.

The main results output file is called ‘sorted_collisions.txt’.

Program Requirements:

The program should run on any Linux/Unix OS that supports ldapsearch, grep, egrep, awk, sed and cut. It has been tested on SLED10, SLES10/OES2 SP1 and SLES11.

Installation:

  • Untar the code to a new directory.
  • Use chmod to make sure you can execute the perl program and the shell scripts (e.g. chmod 755 *).
  • Verify connectivity to the intended LDAP source by pinging the LDAP server.
  • Execute the program using: perl getcolls.pl
Notes: To extract all objects from a tree enter the root or organization of the target tree:

e.g.
t=MyTree
o=MyCompany

The code will correctly handle white space in any context entered (e.g. ‘ou=IT Dept.o=MyCo’).

Working files created (these are retained for debug purposes and can be deleted at will):

 collisions.txt
 dnfixed.txt
 dnlist.txt
 getdn.pl
 revcolls.txt
 schema.pl
 schema.txt
 schema2.txt
 schema3.txt
 schema4.txt
 schema5.txt

 
0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...
Tags:
Categories: Cool Tools, eDirectory

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

No Comments
Aug 20, 2009
6:33 pm
Reads:
1,089
Score:
Unrated