LDAP Directory Collisions Test

If duplicate LDAP entries are created on two or more View Connection Server instances, this can cause problems with the integrity of LDAP data in View. This test checks the ADAM database at pre-configured intervals for the existence of collision references and colliding entries, and reports the count of such entries (if any are found), so that they can be removed with immediate effect to ensure data integrity.

Target of the test : A VMware Horizon Connection server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the VMware Horizon Connection Server being monitored

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed
Host	The host for which the test is to be configured
Port	Refers to the port used by VMware Horizon Connection Server. The default port number is NULL.
View Install DIR	Indicate the full path to the install directory of the target VMware Horizon Connection Server. By default, this is none.
Connection Server name	Specify the name of the target VMware Horizon Connection Server that is to be monitored.
User name	By default, eG Enterprise uses a dual approach i.e., uses VMware PowerCLI and LDAP queries to collect metrics from the target VMware Horizon Connection Server 7 (or above). This dual approach ensures that the metrics are collected more faster than the LDAP query-only approach used for the prior versions of the VMware Horizon Connection Server. Administrators need to install the VMware PowerCLI on the target VMware Horizon Connection server and configure the eG agent to communicate with that CLI to pull the metrics. PowerCLI is a command-line and scripting tool built on Windows PowerShell, which enables easy management, configuration, and automation of vSphere and vCloud environments. With the help of this CLI, the eG agent collects metrics from the target server more quickly than the LDAP approach that was used to collect metrics from VMware Horizon Connection Server version 6 and below. In order to collect metrics using VMware PowerCLI, administrators need to specify the name of the user possessing read-only administrator role in the VMware Horizon Management Console.
Password	Specify the password corresponding to the user here.
Confirm Password	Confirm the password by retyping it here.
Domain Name	Specify the name of the domain to which the VMware Horizon Connection Server belongs to. If the target VMware Horizon Connection Server does not belong to any domain, specify none here.

Measurements made by the test

Measurement

Description

Measurement Unit

Interpretation

Collision entry references found

Indicates the number of collision references currently found in the ADAM database.

Number

Typically, the value 0 is desired for both these measures. A non-zero value indicates the existence of colliding entries. For example, this condition can happen during an upgrade while LDAP replication is inoperative.

When colliding entries exist in the LDAP directory (ADAM database), identify what those entries are and resolve the collision.

Collision entries found

Indicates the number of collision entries currently found in the ADAM database.

Number

Deleted entry references found

Indicates the number of collision references currently deleted from the ADAM database.

Number

Local View LDAP Directory

Indicates whether any collision references were currently found in ADAM database or not.

If this measure reports the value clean, it indicates that no collision references were found in LDAP (ADAM database) directory.

The value Not Clean means there are collision references in LDAP (ADAM database) directory.

The numeric values that correspond to the measure values discussed above are as follows:

State	Numeric Value
Clean	1
Not Clean	0

Note:

By default, this measure reports the above-mentioned Measure Values while indicating whether/not collision references were found in the LDAP directory. However, in the graph of this measure, the same will be indicates using the corresponding numeric equivalents of the states as mentioned in the table above.