Based on the error messages, this does not look like a simple AD username/password issue. The iLO appears to be failing before or during the LDAP/LDAPS connection phase.Since AD authentication works on the next server, the issue is likely specific to this iLO configuration or connectivity. I would recommend comparing the failing iLO with the working iLO, especially the Directory Server Address, LDAP port, secure LDAP mode, DNS servers, gateway, NTP/time settings, Directory User Context, directory group mappings, and imported CA certificate.If LDAPS is used, please also verify TCP/636 connectivity from the iLO management network to the configured Domain Controller and confirm that the iLO trusts the issuing CA of the Domain Controller certificate. If a domain alias is used as the Directory Server Address, please test with the exact same reachable DC FQDN that is configured on the working server.Additionally, please compare the iLO firmware versions. There are known iLO 5 LDAP-related intermittent behaviors in some firmware levels and also a documented limitation around users with large nested group memberships.https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00105236en_us&page=GUID-D7147C7F-2016-0901-06D0-000000000D84.htmlhttps://support.hpe.com/hpesc/public/docDisplay?docId=a00048142en_us&docLocale=en_US&page=GUID-D7147C7F-2016-0901-06D0-000000002D72.html
Классификация: Пресс-релизы
Тональность 0
Информативность 0
community.hpe.com