Feature #3644

Explicitly link BMC proxies to hosts somehow

Added by Dominic Cleal about 8 years ago. Updated over 4 years ago.

Target version:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:


Currently when trying to determine the BMC proxy to use for management of a given host, there are two search steps:

  1. search for a BMC proxy that also is also the DHCP or rDNS proxy for the BMC NIC's subnet
  2. search for the "first" BMC proxy

We're missing some sort of explicit association between hosts and BMC proxies, unless the DHCP/rDNS feature happens to be in use. It's not entirely clear which object we should use to associate them, perhaps subnet?

Related issues

Has duplicate Foreman - Feature #17008: Explicit Subnet BMC associationDuplicate2016-10-19


#1 Updated by Andrew Cooper almost 8 years ago

We have ran into issues where the first option in your list does not appear to be in effect. I have only seen the first BMC proxy (by name) be picked. We have had to cut down to a single bmc-serving proxy and workaround the issue by allowing additional routing between management subnets. We would love to have more control over which proxy is chosen so the networks can remain discrete for security reasons.

I would recommend the subnet as the object to associate to. This could be set on the subnet page similar to the other smart proxy associations (dhcp,tftp, dns). A bmc interface of a host has to be associated to a subnet so it seems like all the associations are in place.

Another alternative would be to set BMC proxy by BMC interface, but this might be too overkill.

#2 Updated by Dominic Cleal over 5 years ago

Also available in: Atom PDF