Red Hat Satellite 6 Administration

Instructions

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

2. Verify that the Capsule Server is configured to support the Finance organization in the Tokyo location. Synchronize the Build lifecycle environment to prepare for provisioning a new development content host.

   1. In the upper-left corner of the web page, set the organization to Any Organization. Set the location to Any Location.

   2. Click Infrastructure → Capsules. In the capsule.lab.example.com row, click Edit.

   3. Click the Lifecycle Environments tab. In the All items list, click Build (Finance) to move it to the Selected items list.

   4. Click the Locations tab. In the All items list, verify that Tokyo is in the Selected items list. If not, click on Tokyo to move it.

   5. Click the Organizations tab. In the All items list, verify that Finance is in the Selected items list. If not, click on Finance to move it. Click Submit.

   6. On the Capsules page, click capsule.lab.example.com. Click Synchronize → Optimized Sync to start the synchronization process. Wait for the process to complete.

   7. In the upper-left corner of the web page, set the organization to Finance. Set the location to Tokyo.

   Hide Solution

3. Verify that the capsule.lab.example.com system has DNS, DHCP, and TFTP services enabled. Use the following settings:

   Table 9.10. Service Parameters

   Parameter	Value
   DNS network interface	eth0
   DNS forwarder	172.25.250.254
   DNS zone	tokyo.lab.example.com
   DNS reverse	250.25.172.in-addr.arpa
   DHCP network interface	eth0
   DHCP range	172.25.250.50 to 172.25.250.100
   Name server provided by DHCP	172.25.250.220
   Gateway provided by DHCP	172.25.250.254

   
   

   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
      [root@capsule ~]#

   2. Enable the DNS, DHCP, and TFTP services by using the parameters from the table in the Instructions section.

      [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 tokyo.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

   3. Verify that the DNS, DHCP, and TFTP features are active on the Capsule Server. Click Infrastructure → Capsules, and then click the capsule.lab.example.com link.

   4. In the Overview tab, verify that the Active features section lists the DNS, DHCP, and TFTP services.

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

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

   Hide Solution

4. Verify that the tokyo.lab.example.com DNS domain exists in the Finance organization and in the Tokyo location.

   1. Click Infrastructure → Domains, and then click tokyo.lab.example.com link.

   2. In the Domains tab, verify that the capsule.lab.example.com capsule is selected as DNS Capsule.

   3. In the Locations tab, verify that the Tokyo location is in the Selected items list.

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

   Hide Solution

5. Verify the Tokyo Data Center subnet with the following settings.

   Table 9.11. Tokyo Subnet Details

   Field	Value
   Name	Tokyo Data Center
   Network Address	172.25.250.0
   Network Prefix	24
   Gateway Address	172.25.250.254
   Primary DNS Server	172.25.250.220
   IPAM	DHCP
   Start Of Ip Range	172.25.250.50
   End Of Ip Range	172.25.250.100
   Boot Mode	DHCP
   Domains	tokyo.lab.example.com
   Capsules	capsule.lab.example.com

   
   

   1. Click Infrastructure → Subnets and then click Tokyo Data Center link. On the Subnet tab, verify the data from the preceding table. Submit the form only when the remaining tabs are completed.

   2. Click the Domains tab. In the All items list, verify that tokyo.lab.example.com is in the Selected items list.

   3. Click the Capsules tab. Verify that capsule.lab.example.com is selected in every field on this page.

   4. Click the Locations tab. Verify that the Tokyo location is in the Selected items list.

   5. Click the Organizations tab. Verify that the Finance organization is in the Selected items list. Click Submit.

   Hide Solution

6. Create a Finance Provisioning host group with the following settings:

   Table 9.12. Host Group Details

   Parameter	Value
   Name	Finance Provisioning
   Lifecycle environment	Build
   Content view	FinanceServerBase
   Content source	capsule.lab.example.com
   Network domain	tokyo.lab.example.com
   IPv4 subnet	Tokyo Data Center (172.25.250.0/24)
   Operating system architecture	x86_64
   Operating system	RedHat 9.0
   Partition table	Kickstart default
   PXE loader	PXELinux BIOS
   Location	Tokyo
   Organization	Finance
   Activation key	FinanceServers

   
   

   1. Click Configure → Host Groups, and then click Create Host Group.

   2. On the Host Group tab, enter the data from the preceding table. Leave the other fields unchanged. Click Submit.

   Hide Solution

7. Create a servere host resource with the following settings for the system to be provisioned:

   Table 9.13. New Host Details

   Field	Value
   Name	servere
   Organization	Finance
   Location	Tokyo
   Host Group	Finance Provisioning
   Root Password	redhat123
   MAC Address	52:54:00:00:fa:0e

   
   

   1. Click Hosts → Create Host. On the Host tab, enter the initial data from the preceding table. Setting the host group autofills the form with other group parameters. Leave the other fields unchanged. Submit the form only when the remaining tabs are completed.

   2. Click the Operating System tab. Enter the root password from the preceding table. Click Resolve to confirm that the system can retrieve the provisioning templates.

   3. Click the Interface tab. Enter the MAC address from the preceding table. Click Submit.

   Hide Solution

8. Access the servere console and initiate a PXE boot. Provisioning should proceed automatically.

   1. The servere host should reboot automatically. If the host does not reboot, then send a Ctrl+Alt+Del from the servere console.

   2. Select Kickstart default PXELinux from the Booting into OS installer menu. Wait for the provisioning to complete and for the servere system to reboot.

   3. Select the Chainload the first hard drive (hd0) option. On the servere console, log in as the root user with redhat123 as the password. Use the hostname command to verify the system name.

      servere login root
      Password: redhat123
      [root@servere ~]# hostname
      servere.tokyo.lab.example.com

   4. Exit the servere system and close the console.

      [root@servere ~]# exit
      servere login:

   Hide Solution