Unable to configure Historical Reporting with LDAP

Last Updated : Sep 22, 2020 |
Prolog information
Metadata
Keywords:

Condition

Unable to configure Historical Reporting with Lightweight Directory Access Protocol (LDAP).

Cause

The LDAP server might be inaccessible from the environment where Historical Reporting is hosted.

Solution

  1. To test the LDAP server accessibility from Avaya Analytics™, log in to the Cluster Control Manager (CCM) console.
  2. Switch to being the root user by entering the command su.
  3. To run the Analytics Administration script, use the following command:
    ADDITIONAL INFORMATION:
    ccm release orca analytics
  4. Select Troubleshooting by pressing the corresponding number.
  5. Select the Historical Reporting option by entering the corresponding number.
  6. Select the Test LDAP server accessibility option by entering the corresponding number.
  7. In the Proceed with LDAP validation field, type y.
    ADDITIONAL INFORMATION:
    Typing n cancels the operation.
  8. In the Enter the FQDN of the LDAP server field, type the FQDN of the LDAP server and press Enter.
  9. In the Enter the port of the LDAP server field, type the port number of the LDAP server and press Enter.
    STEP RESULT:
    If the LDAP server accessibility test is successful, the CCM console displays the following message: Successfully connected to LDAP server. Server is reachable.
    If the LDAP server accessibility test fails, the CCM console displays the following message: Unable to reach LDAP server using telnet.
  10. If the LDAP server accessibility test is successful and you are still not able to configure LDAP, verify that the LDAP password is correct.
  11. If the LDAP server accessibility test fails, check the DNS server and the firewall settings.