Chapter 5. Adding network interfaces

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click Edit next to the host you want to edit.
3. On the Interfaces tab, click Add Interface.
4. Keep the Interface option selected in the Type list.
5. Specify a MAC address. This setting is required.
6. Specify the Device Identifier, for example eth0. The identifier is used to specify this physical interface when creating bonded interfaces, VLANs, and aliases.
7. Specify the DNS name associated with the host’s IP address. Satellite saves this name in Capsule Server associated with the selected domain (the "DNS A" field) and Capsule Server associated with the selected subnet (the "DNS PTR" field). A single host can therefore have several DNS entries.
8. Select a domain from the Domain list. To create and manage domains, navigate to Infrastructure > Domains.
9. Select a subnet from the Subnet list. To create and manage subnets, navigate to Infrastructure > Subnets.
10. Specify the IP address. Managed interfaces with an assigned DHCP Capsule Server require this setting for creating a DHCP lease. DHCP-enabled managed interfaces are automatically provided with a suggested IP address.
11. Select whether the interface is Managed. If the interface is managed, configuration is pulled from the associated Capsule Server during provisioning, and DNS and DHCP entries are created. If using Kickstart provisioning, a configuration file is automatically created for the interface.
12. Select whether this is the Primary interface for the host. The DNS name from the primary interface is used as the host portion of the FQDN.
13. Select whether this is the Provision interface for the host. TFTP boot takes place using the provisioning interface. For image-based provisioning, the script to complete the provisioning is executed through the provisioning interface.
14. Select whether to use the interface for Remote execution.
15. Leave the Virtual NIC checkbox clear.
16. Click OK to save the interface configuration.
17. Click Submit to apply the changes to the host.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click Edit next to the host you want to edit.
3. On the Interfaces tab, click Add Interface.
4. Keep the Interface option selected in the Type list.

5. Specify the general interface settings. The applicable configuration options are the same as for the physical interfaces described in Section 5.1, “Adding a physical interface”.

   Specify a MAC address for managed virtual interfaces so that the configuration files for provisioning are generated correctly. However, a MAC address is not required for virtual interfaces that are not managed.

   If creating a VLAN, specify ID in the form of eth1.10 in the Device Identifier field. If creating an alias, use ID in the form of eth1:10.

6. Select the Virtual NIC checkbox. Additional configuration options specific to virtual interfaces are appended to the form:

   • Tag: Optionally set a VLAN tag to trunk a network segment from the physical network through to the virtual interface. If you do not specify a tag, managed interfaces inherit the VLAN tag of the associated subnet. User-specified entries from this field are not applied to alias interfaces.
   • Attached to: Specify the identifier of the physical interface to which the virtual interface belongs, for example eth1. This setting is required.
7. Click OK to save the interface configuration.
8. Click Submit to apply the changes to the host.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts.
2. Click Edit next to the host you want to edit.
3. On the Interfaces tab, click Add Interface.
4. Select Bond from the Type list. Additional type-specific configuration options are appended to the form.

5. Specify the general interface settings. The applicable configuration options are the same as for the physical interfaces described in Section 5.1, “Adding a physical interface”.

   Bonded interfaces use IDs in the form of bond0 in the Device Identifier field.

   A single MAC address is sufficient.

   If you are adding a secondary interface, select Managed. Otherwise, Satellite does not apply the configuration.

6. Specify the configuration options specific to bonded interfaces:

   • Mode: Select the bonding mode that defines a policy for fault tolerance and load balancing. See Section 5.4, “Bonding modes available in Satellite” for a brief description of each bonding mode.
   • Attached devices: Specify a comma-separated list of identifiers of attached devices. These can be physical interfaces or VLANs.
   • Bond options: Specify a space-separated list of configuration options, for example miimon=100. For more information on configuration options for bonded interfaces, see Configuring network bonding in Red Hat Enterprise Linux 8 Configuring and Managing Networking.
7. Click OK to save the interface configuration.
8. Click Submit to apply the changes to the host.

Procedure

1. Enable BMC power management on your Capsule:

   # satellite-installer \
   --foreman-proxy-bmc-default-provider=ipmitool \
   --foreman-proxy-bmc=true

2. In the Satellite web UI, navigate to Infrastructure > Subnets.
3. Select the subnet of your host.
4. On the Capsules tab, select your Capsule as BMC Capsule.
5. Click Submit.
6. Navigate to Hosts > All Hosts.
7. Click Edit next to the host you want to edit.
8. On the Interfaces tab, click Add Interface.
9. Select BMC from the Type list. Type-specific configuration options are appended to the form.
10. Specify the general interface settings. The applicable configuration options are the same as for the physical interfaces described in Section 5.1, “Adding a physical interface”.

11. Specify the configuration options specific to BMC interfaces:

    • Username and Password: Specify any authentication credentials required by BMC.
    • Provider: Specify the BMC provider.
12. Click OK to save the interface configuration.
13. Click Submit to apply the changes to the host.