ALM-12100 AD Service Connection Failed

Updated on 2024-09-23 GMT+08:00

View PDF

Alarm Description

After a third-party active directory (AD) is interconnected, the third-party AD domain user can be synchronized using the synchronization period (60 minutes by default) or manually. During data synchronization, the AD service status will be checked. This alarm is generated when AD service unavailability is detected for three consecutive times. This alarm is cleared when AD service recovers.

NOTE:

This section applies to MRS 3.1.5 and later versions.

Alarm Attributes

Alarm ID	Severity	Auto Clear
12100	Major	Yes

Alarm Parameters

Alarm Parameters	Description
Source	Specifies the cluster or system for which the alarm is generated.
ServiceName	Specifies the name of the service for which the alarm is generated.
RoleName	Specifies the name of the role for which the alarm is generated.
HostName	Specifies the name of the host for which the alarm is generated.

Impact on the System

When the alarm is generated, the AD service is unavailable, and AD domain user synchronization fails. An AD domain user cannot log in to FusionInsight Manager and execute services.

Possible Causes

The configuration item for interconnecting with the third-party AD is incorrect.
The network connection between FusionInsight and the third-party AD service is faulty.
AD server fault
AD service fault

Handling Procedure

Check the third-party AD configuration.

On the FusionInsight Manager page, choose System > Permission > Third-Party AD. The third-party AD configuration page is displayed.
Check whether the AD IP Address, LDAP Port, Bind DN, and Bind DN Password parameters are correctly set.
- If yes, go to 5.
- If no, go to 3.
Modify the incorrect parameters, and then click OK.
Choose System > Permission > User > AD Domain User, click Manual Synchronization, and check whether the message "Manual synchronization successfully." is displayed in the upper right corner of the page.
- If yes, no further action is required.
- If no, go to 5.

Check the third-party AD server and the network.

Log in to the active management node as user root.
On the host you have logged in to, ping the IP address of the third-party AD server to check whether the third-party AD server can be pinged.
- If yes, go to 7.
- If no, go to 8.
Run the following command to check whether the third-party AD service can be connected:

telnet IP port

IP indicates the IP address of the third-party AD server, and port indicates the port used by the third-party AD server.
- If yes, go to 8.
- If no, contact O&M personnel to check the network.
Contact the third-party AD service administrator to check whether the AD service is normal.
- If yes, go to 9.
- If no, contact the third-party AD service administrator to rectify the AD server fault.

Collect the fault information.

On the FusionInsight Manager page, choose O&M > Log > Download.
In the Service area, select Controller under OMS and click OK.
Click in the upper right corner to set Start Date and End Date to 10 minutes before and after the time when the alarm is generated, and click Download.
Contact the O&M personnel and send the collected log information.