Satellite 6.2 provisioning on different subnets/vlans

Latest response

Hi folks,

I have a Satellite 6.2 implemented on a specific subnet, with no additional capsule servers besides the integrated one (dns, dhcp and tftp enabled). In my environment, the vm guests are on different subnets, for instance, Dev > 10.8.1.x/24, QA > 10.8.2.x/24, and Prod > 10.8.3.x/24. Satellite is located on subnet 10.8.0.x, and can provision (fully automated) vms on this subnet. Does any one have any idea on how to provision on the other subnets besides the one Satellite belongs to? Or have implemented something on a similar environment?

I have attempted to create a second nic, and moved the services to it, however, it works for a single subnet only. I haven't come to an idea on how to fit multiple networks yet.

Any help or thoughts appreciated. Thanks.

Responses

Hey Alex,

Have you configured the other subnets on Satellite 6? Have you enabled DHCP helpers on the other subnets?

If you can't configure DHCP helpers, you can look at DHCP Relay instead:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/dhcp-relay-agent.html

Cheers,

  • Calvin

Hi Calvin,

Yes, I have all subnets configured on Satellite 6. I was wondering if anyone have experienced configuring Satellite 6 by taking advantage of the integrated capsule, for instance, having multiple NICs to provide dhcp, tftp, and everything in a self-contained install fashion.

Otherwise, I guess I'll have to setup another VM just for dhcp and bootp and configure Satellite with an external service or as you suggested put a DHCP Relay on the other subnets.

Silly question, DHCP helper would be something to be configured at router level? Actually, a firewall is doing the router role among the subnets here.

Thanks, Alex

to do PXE provisioning on multiple subnets, you do NOT need multiple physical interfaces. You need to ensure that

  • The Satellite has the TFTP feature enabled. Install this by running the installer with the --foreman-proxy-tftp true --foreman-proxy-tftp-servername $(hostname) option.
  • Confirm successful installation of the feature by running hammer --output json capsule list
  • Define (or Update) your subnet with Boot Mode: DHCP.
  • Associate the subnet with the TFTP Capsule. (Basically you are telling Satellite: "for this subnet, write out boot files in /var/lib/tftpboot")

On the infrastructure side, in your DHCP configuration you need to tell your DHCP server to boot clients using the boot files that Satellite offers. This is done by setting DHCP's next-server & filename options. Example for ISC DHCP follows:

{
    subnet 192.168.0.0 netmask 255.255.255.0 {
    range 192.168.0.100 192.168.5.150;
    option domain-name-servers 8.8.8.8:
    option bootfile-name "pxelinux.0";
    option domain-name "yourcompany.com";
    default-lease-time 1800;
    max-lease-time 7200;
    next-server "satellite.example.com";

    }

You can run DHCP on the Satellite, but chances are you probably already have it setup in your environment. If you do choose to run DHCP on Satellite, be advised that our installer only sets up one subnet for DHCP. If you want to run multiple subnets using DHCP hosted on Satellite, it is advised to re-run the installer with the foreman-proxy-dhcp-managed option set to FALSE. This tells our puppet-based installer that you are managing the file directly, and to leave it alone. Lastly, configure DHCP as per your needs.

Hi Rich,

We have the same scnario here and I've done the configuratio as you mentioned above. However provisioning on a different subnet still not working. I suppose we still need a DHCP Relay Server sitting in the target subnet?

Edit: P.S. DHCP forward is already enabled on network level.

Thanks, Bryan

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.