Problem description: Unable to add or discover iLO SP to UMG using an External iLO AD/LDAP user with Admin privileges. Error " Not Communicating " Resolution: Use a Local Admin iLO user to the add or discover the SP in the UMG. Additional Explanation and tests: The iLO behavior is Works As Designed. Here is the release note from v2.5.0.8 when we last made a change to this part of the functionality. I should have added this as a permanent entry in the release notes then also. Will add the equivalent of this statement in future release notes: HP iLO3 and iLO4 Service Processors may now be added or discovered using credentials with an IPMI/DCMI privilege of Administrator, Operator or User. The management capability of the HP iLO3 and iLO4 Service Processor through the appliance will be limited by the privilege of the credential used to add the Service Processor. All other Service Processors supported by the appliance can be added or discovered using credentials with an IPMI/DCMI Administrator privilege as provided in previous appliance releases. As shown in the screenshot below, the Issue is as design because of the way the iLO LDAP user permissions are assigned which is different from the iLO local user permissions. And since the UMG requires IPMI/DCMI Administrator privilege which the LDAP user does not have, hence the error message while trying to add or discover the service processors in this case the iLo4. iLO4 and AD integration… Steps… SP addition to UMG using the AD account steps...
↧