-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for iLO interfaces that don't report IP but dns name. #140
Comments
should be
for some hosts that have "-" in the name, etc. |
This needs a few more addons to pass the testsuite. I'll post them in a few hours. |
fixed for names that are impossible to resolve (configured but not in dns records). |
It may be a stupid remark, but I don't understand how a device without an IP address would be able to autoconfigure itself, even with a DNS hostname: in order to resolve it, it should be able to send a query to a DNS server... through a unicast UDP or TCP communication, both of them requiring a valid IP source address. |
I think the problem is that if hponcfg only returns dns name + domainname in some cases, and no ip address. I have plenty of machines like that. If that is just a case of missing dns entries, i can go fix it. But i had a few cases where the name resolved, which is puzzling. |
This is either specific to ilo 1.x or ilo that gets its address off dhcp. It may be a stupid policy, but i have no say in the matter. |
updated the script to return ilo ip if it is stated directly (missed that one before)
|
No need to past so much code, as long as I'm not convinced about the exact use case. If I understand correctly, those device could either be configured statically, or dynamically through DHCP. In this last case, there won't be any IP address in the configuration, for obvious reasons, and we should rely on another mechanism to retrieve the actual device state. Am I correct ? Now I have two questions:
Providing samples of 'hponcfg -aw -' output, demonstrating those different cases, would help understanding the issue (and build related tests, also). |
Yes. I think hponcfg output should say something about network configuration Sample hponcfg from an iLOv3 with dhcp enabled; i've redacted the hostname and domain. DHCP_ENABLE VALUE is apparently the information that indicates the dhcp client setup. From looking around in ilo, enabling dhcp disables customization of any ipv4/ipv6 settings, you can only set the hostname, and domain is configured to be obtained via dhcp (it's optional).
|
I know I'm about a year late, but how does your ilo respond (assuming linux) if you use "ipmitool lan print" on the machine in question? This would allow the system to crosscheck that the mac address is correct, etc. Here's what I've got - as you can see it not only indicates dhcp/static configuration, it also shows the assigned DHCP address ipmitool lan printSet in Progress : Set Complete (Yes, I know it shows the snmp community. That's not enabled) |
I'll check this out in a few hours. So far i get missing /dev/ipmi0 device, i'll have to look into that. |
I got it working, i just need to load extra kernel modules. On one server that reports only fqdn but no ip via hponcfg :
the output of hponcfg -aw - :
The blank lines ought to have ip configuration, afaik. |
Hi @yoshi314 |
I haven't noticed this update yet, but i'll give it a shot. The network scan should also resolve a lot of headaches, but i am not sure how will it bind ilo ip to a server in glpi. |
I've noticed that if ilo interface has dns name instead of IP, it doesn't get reported.
This small patch makes FA look for dns name and translates it into IP address, and the iLO interface appears on the list of interfaces of a given machine.
This diff is against 2.2.3-8 from debian wheezy. It should apply easily, though.
The text was updated successfully, but these errors were encountered: