- Community Home
- >
- Software
- >
- HPE OneView
- >
- OV communication to iLOs defaults to IP rather the...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-05-2019 09:11 AM
11-05-2019 09:11 AM
Hello,
We're running OV 4.20.01.01-0385523 with our iLO4 at fw 2.70 and iLO5 at 1.46.
When clicking on the links for our iLOs within OV on the server hardware page the redirect ends up going to the IP rather then the FQDN. As we don't currently put our IPs in as SANs in our certs this behaviour results in an unsecure connection.
As a test, i redid a couple of certs for iLO4 and 5 with IPs included as SAN and got the secure connection.
Is this expected behaviour in OV? Any way to change the priority?
Thanks.
G.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-05-2019 11:19 AM
11-05-2019 11:19 AM
SolutionThis is expected behavior for HPE OneView 4.20 and older. Starting wtih 5.00, if you add server hardware using the FQDN, OneView will also use it in the iLO links in the server hardware view. Your only other option is to redo your iLO certs with the appropriate SAN values.
I am an HPE employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-21-2019 05:03 AM
11-21-2019 05:03 AM
Re: OV communication to iLOs defaults to IP rather then FQDN
Hello Chris,
In my case I observe different behaviour. Oneview v. 4.20 was using correct links to FQDN hostnames (hostname.ilo.loc which we have in internal DNS), but the 5.0 version offers links to ILO hostname without domain suffix. So I am forced to use the link with IP address anyway.
My configuration: in Onboard admin /Enclosure bay addressing section every blade has Domain set to ilo.loc. The ILO interface Dedicated network port / General shows ilo.loc in the field Domain as expected, with Note: Domain Name is currently set through DHCP.
I tried restarting ILO, refreshing Enclosure etc. but oneview still uses only ILO hostname without domain... What can I do to force FQDN links?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-21-2019 09:22 AM
11-21-2019 09:22 AM
Re: OV communication to iLOs defaults to IP rather then FQDN
Verify that the iLO has a configured DNS domain value set in iLO Hostname Settings when you configure the iLO Network settings. You can verify that it is set correctly by both looking at the iLO login page, or in the upper right corner below the username for the iLO Subsystem name.
I am an HPE employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-21-2019 01:04 PM
11-21-2019 01:04 PM
Re: OV communication to iLOs defaults to IP rather then FQDN
iLO hostname settings show the correct domain name set through DHCP (from enclosure Onboard admin) and the FQDN is displayed correctly both on login screen and in the upper right corner after logging in. I even tried disabling "Use DHCPv4 Supplied Domain Name" option and entered the domain name manually (I used a different suffix just to be sure), which was correctly reflected in ILO web GUI after reset, but OV is still using only ILO hostname, not FQDN.
It is a general behaviour across all servers in both of our OV 5.00.00.02 instances. And I am pretty sure it used to work in OV 4 before the upgrade, it seems to be the new version's "feature".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-21-2019 01:06 PM
11-21-2019 01:06 PM
Re: OV communication to iLOs defaults to IP rather then FQDN
I would ask that you open a support case at this point. That isn't the expected beahvior with 5.00.
I am an HPE employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-21-2019 01:11 PM
11-21-2019 01:11 PM
Re: OV communication to iLOs defaults to IP rather then FQDN
OK, will do. Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-27-2020 12:45 AM
01-27-2020 12:45 AM
Re: OV communication to iLOs defaults to IP rather then FQDN
Hi,
Did you solve it? I have the same problem.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-18-2020 02:13 AM
02-18-2020 02:13 AM
Re: OV communication to iLOs defaults to IP rather then FQDN
Finaly, I found it: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00095146en_us
- Tags:
- I found it:
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP