Red Hat Satellite 6 Administration

Instructions

The Operations team wants to provision systems on the 172.25.250.0/24 subnet in the Boston location. The content hosts in Boston are members of the boston.lab.example.com DNS domain, and are supported by the external Capsule Server.

You are requested to configure the Capsule Server to provide the DNS, DHCP, and TFTP services. You must configure the boston.lab.example.com DNS zone as authoritative. The DHCP service must provide the 172.25.250.50 - 172.25.250.100 IP address range for provisioning.

1. Log in to the capsule system as the student user and switch to the root user.

   [student@workstation ~]$ ssh student@capsule
   [student@capsule ~]$ sudo -i
   [sudo] password for student: student
   [root@capsule ~]#

2. Enable and configure the DNS, DHCP, and TFTP services on the capsule.lab.example.com system.

   1. Enable the DNS, DHCP, and TFTP services with the specified network configuration parameters. The DNS server for the boston.lab.example.com zone is the capsule.lab.example.com system at the 172.25.250.220 IP address.

      For your convenience, you can copy and paste the following satellite-installer command from the /root/satellite-installer-example.txt file. Wait for the process to complete.

      [root@capsule ~]# satellite-installer --scenario capsule \
      --foreman-proxy-dns true \
      --foreman-proxy-dns-interface eth0 \
      --foreman-proxy-dns-forwarders 172.25.250.254 \
      --foreman-proxy-dns-zone boston.lab.example.com \
      --foreman-proxy-dns-reverse 250.25.172.in-addr.arpa \
      --foreman-proxy-dhcp true \
      --foreman-proxy-dhcp-interface eth0 \
      --foreman-proxy-dhcp-range "172.25.250.50 172.25.250.100" \
      --foreman-proxy-dhcp-nameservers 172.25.250.220 \
      --foreman-proxy-dhcp-gateway 172.25.250.254 \
      --foreman-proxy-tftp true
      ...output omitted...
        Success!
        * Capsule is running at https://capsule.lab.example.com:9090
      
        The full log is at /var/log/foreman-installer/capsule.log

   2. Enable Ansible on the capsule.lab.example.com system. This will enable the Ansible services on the capsule for provisioning.

      [root@capsule ~]# satellite-installer --scenario capsule --enable-foreman-proxy-plugin-ansible
      2023-06-13 16:11:33 [NOTICE] [root] Loading installer configuration. This will take some time.
      2023-06-13 16:11:38 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
      
      ...output omitted...
      
        Success!
        * Capsule is running at https://capsule.lab.example.com:9090
      
        The full log is at /var/log/foreman-installer/capsule.log

   3. Return to the workstation system as the student user.

      [root@capsule ~]# exit
      logout
      [student@capsule ~]$ exit
      logout
      [student@workstation ~]$

3. Log in to the Satellite Server web UI, https://satellite.lab.example.com, as the admin user with redhat as the password.

4. In the upper-left corner of the web page, set the organization to Operations. Set the location to Boston.

5. Verify that the DNS, DHCP, and TFTP features are active on the Capsule Server.

   1. Click Infrastructure → Capsules, and then click the capsule.lab.example.com link.

   2. In the Overview tab, verify that the Active features section lists the DNS, DHCP, and TFTP services. If the services are not yet listed, then click Refresh features.

      Figure 8.2: Capsule active features

6. Create the boston.lab.example.com DNS domain for the Operations organization and the Boston location.

   1. Click Infrastructure → Domains, and then click Create Domain. Enter boston.lab.example.com in the DNS Domain field. Select capsule.lab.example.com in the DNS Capsule field.

   2. In the Locations tab, verify that the Boston location is in the Selected items list.

   3. In the Organizations tab, verify that the Operations organization is in the Selected items list. Click Submit.

7. Create the Boston Data Center subnet, 172.25.250.0/24, and configure its DHCP address range and DNS server as specified in the previous satellite-installer command.

   1. Click Infrastructure → Capsules.

   2. In the capsule.lab.example.com row, select Import IPv4 subnets from the Edit list in the Actions column.

   3. In the 172.25.250.0/24 page, enter the following details. Leave the other fields unchanged. Click Submit.

      Table 8.3. Boston Subnet Details

      Field	Value
      Name	Boston Data Center
      Primary DNS Server	172.25.250.220
      IPAM	DHCP

      
      

8. Define the IP range for the Boston Data Center subnet, and associate the subnet with the boston.lab.example.com domain. Verify that the domain and support services are assigned to the required resources and location.

   1. Click Infrastructure → Subnets, and then click the Boston Data Center link.

   2. Enter 172.25.250.50 in the Start Of Ip Range field, and enter 172.25.250.100 in the End Of Ip Range field.

   3. Click the Domains tab, and then click the boston.lab.example.com domain to move it to the Selected items list.

   4. Click the Capsules tab. Select capsule.lab.example.com in each of the DHCP Capsule, TFTP Capsule, Reverse DNS Capsule, and Template Capsule fields.

   5. Click the Locations tab, and verify that the Boston location is in the Selected items list.

   6. Click the Organizations tab, and verify that the Operations organization is in the Selected items list. Click Submit.

      The Capsule Server is now configured with the required network and domain for provisioning content hosts in Boston.