HPE OneView
1834088 Members
3049 Online
110063 Solutions
New Discussion

Re: OneView v8.2 server profiles fail: iLO Settings Invalid

 
Robert Eckdale
Occasional Contributor

OneView v8.2 server profiles fail: iLO Settings Invalid

After upgrading from v8.0 to v8.2 all of my server profiles fail to apply with the following message:

Unable to reapply server profile: my-server-profile
Issue: The iLO settings are invalid:
The hostname value "dc1.mydomain.com,dc2.mydomain.com,dc3.mydomain.com" contains characters that are not supported in a hostname for iLO setting "Manage directory configuration".

Resolution: Correct the specified iLO settings arguments.

Issue: The hostname value "dc1.mydomain.com,dc2.mydomain.com,dc3.mydomain.com" contains characters that are not supported in a hostname for iLO setting "Manage directory configuration".
Resolution Update the hostname to only contain the characters A-Z, a-z, 0-9, and - without a leading or trailing -.

As I indicated, this wasn't an issue in OneView v8.0 and iLO clearly supports this configuration.

 

3 REPLIES 3
support_s
System Recommended

Query: OneView v8.2 server profiles fail: iLO Settings Invalid

System recommended content:

1. HPE Integrated Lights Out (iLO 4) - Troubleshooting Directory Issues

2. HPE Integrated Lights Out (iLO 5) for Gen10 Servers - Secure Recovery

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

 

Thank you for being a HPE valuable community member.


Accept or Kudo

ChrisLynch
HPE Pro

Re: OneView v8.2 server profiles fail: iLO Settings Invalid

Are you working this issue through support? Can you PM me the support case if so?
I work at HPE
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Robert Eckdale
Occasional Contributor

Re: OneView v8.2 server profiles fail: iLO Settings Invalid

I have not opened a case with HPE support. As a work around I entered just the domain name versus the comma seperated domain controllers FQDNs, however this is less than ideal because now queries are crossing sites.

I'll open a case and get back to you.