#### Baseboard Management Controller (BMC) configuration
The BMC IP address should be statically assigned using the machine's
-BMC tool or application.
+BMC tool or application. Configuration of the pod11-node3 machine is
+shown in [Appendix A](#bmc-configuration).
To verify IPMI is configured correctly for each cluster machine, use
ipmitool:
#### PXE Boot configuration
Each cluster machine must be configured to PXE boot from the interface
-attached to the `provisioning` network.
+attached to the `provisioning` network. Configuration of the
+pod11-node3 machine is shown in [Appendix A](#pxe-boot-configuration-1).
One method of verifying PXE boot is configured correctly is to access
the remote console of the machine and observe the boot process. If
configured properly to forward PXE boot requests (i.e. VLAN
configuration).
+### Additional BIOS configuration
+
+Each cluster machine should also be configured to enable any desired
+features such as virtualization support. Configuration of the
+pod11-node3 machine is shown in [Appendix
+A](#additional-bios-configuration-1).
## Jump server
root@pod11-node5:# kubectl -n flux-system delete Kustomization icn-master-site-pod11
+## Appendix A: BMC and BIOS configuration of pod11-node3
+
+The BMC and BIOS configuration will vary depending on the vendor. The
+below is intended only to provide some guidance on what to look for in
+the hardware used in the chosen configuration.
+
+### BMC configuration
+
+BMC IP address configured in the BIOS.
+
+
+
+BMC IP address configured in the web console.
+
+
+
+IPMI configuration. Not shown is the cipher suite configuration.
+
+
+
+### PXE boot configuration
+
+The screens below show enabling PXE boot for the specified NIC and
+ensuring it is first in the boot order.
+
+
+
+
+
+### Additional BIOS configuration
+
+The screens below show enabling virtualization options in the BIOS.
+
+
+