Chapter 3. Configuring networking

Procedure

1. In the Satellite web UI, navigate to Administer > Settings and select the Facts tab.
2. To filter out all interfaces starting with specific names, for example, blu, add blu* to the Ignore interfaces with matching identifier option.

3. To prevent databases from storing facts related to interfaces starting with specific names, for example, blu, add blu* to the Exclude pattern for facts stored in Satellite option.

   By default, it contains the same list as the Ignore interfaces with matching identifier option. You can override it based on the your requirements. This filters out facts completely without storing them.

4. To remove facts from the database, enter the following command:

   # foreman-rake facts:clean

   This command removes all facts matching with the filter added in Administer > Settings > Facts > the Exclude pattern for facts stored in Satellite option.

5. To remove interfaces from the database, enter the following command:

   # foreman-rake interfaces:clean

   This command removes all interfaces matching with the filter added in Administer > Settings > Facts > the Ignore interfaces with matching identifier option.

Procedure

1. To preview the DHCP records that are going to be added to the DHCP server, enter the following command:

   # foreman-rake orchestration:dhcp:add_missing subnet_name=NAME

2. If you are satisfied by the preview changes in the previous step, apply them by entering the above command with the perform=1 argument:

   # foreman-rake orchestration:dhcp:add_missing subnet_name=NAME perform=1

3. To keep DHCP records in Satellite and in the DHCP server synchronized, you can remove unwanted DHCP records from the DHCP server. Note that Satellite assumes that all managed DHCP servers do not contain third-party records, therefore, this step might delete those unexpected records. To preview what records are going to be removed from the DHCP server, enter the following command:

   # foreman-rake orchestration:dhcp:remove_offending subnet_name=NAME

4. If you are satisfied by the preview changes in the previous step, apply them by entering the above command with the perform=1 argument:

   # foreman-rake orchestration:dhcp:remove_offending subnet_name=NAME perform=1

Procedure

1. Enter the satellite-installer command to configure the required network services:

   # satellite-installer --foreman-proxy-dhcp true \
   --foreman-proxy-dhcp-gateway "192.168.140.1" \
   --foreman-proxy-dhcp-managed true \
   --foreman-proxy-dhcp-nameservers "192.168.140.2" \
   --foreman-proxy-dhcp-range "192.168.140.10 192.168.140.110" \
   --foreman-proxy-dhcp-server "192.168.140.2" \
   --foreman-proxy-dns true \
   --foreman-proxy-dns-forwarders "8.8.8.8" \
   --foreman-proxy-dns-forwarders "8.8.4.4" \
   --foreman-proxy-dns-managed true \
   --foreman-proxy-dns-reverse "140.168.192.in-addr.arpa" \
   --foreman-proxy-dns-server "127.0.0.1" \
   --foreman-proxy-dns-zone "example.com" \
   --foreman-proxy-tftp true \
   --foreman-proxy-tftp-managed true

2. Find Capsule Server that you configure:

   # hammer capsule list

3. Refresh features of Capsule Server to view the changes:

   # hammer capsule refresh-features --name "satellite.example.com"

4. Verify the services configured on Capsule Server:

   # hammer capsule info --name "satellite.example.com"

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Domains and click Create Domain.
2. In the DNS Domain field, enter the full DNS domain name.
3. In the Fullname field, enter the plain text name of the domain.
4. Click the Parameters tab and configure any domain level parameters to apply to hosts attached to this domain. For example, user defined Boolean or string parameters to use in templates.
5. Click Add Parameter and fill in the Name and Value fields.
6. Click the Locations tab, and add the location where the domain resides.
7. Click the Organizations tab, and add the organization that the domain belongs to.
8. Click Submit to save the changes.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Subnets, and in the Subnets window, click Create Subnet.
2. In the Name field, enter a name for the subnet.
3. In the Description field, enter a description for the subnet.
4. In the Network address field, enter the network address for the subnet.
5. In the Network prefix field, enter the network prefix for the subnet.
6. In the Network mask field, enter the network mask for the subnet.
7. In the Gateway address field, enter the external gateway for the subnet.
8. In the Primary DNS server field, enter a primary DNS for the subnet.
9. In the Secondary DNS server, enter a secondary DNS for the subnet.
10. From the IPAM list, select the method that you want to use for IP address management (IPAM). For more information about IPAM, see Chapter 3, Configuring networking.
11. Enter the information for the IPAM method that you select. Click the Remote Execution tab and select the Capsule that controls the remote execution.
12. Click the Domains tab and select the domains that apply to this subnet.
13. Click the Capsules tab and select the Capsule that applies to each service in the subnet, including DHCP, TFTP, and reverse DNS services.
14. Click the Parameters tab and configure any subnet level parameters to apply to hosts attached to this subnet. For example, user defined Boolean or string parameters to use in templates.
15. Click the Locations tab and select the locations that use this Capsule.
16. Click the Organizations tab and select the organizations that use this Capsule.
17. Click Submit to save the subnet information.