OSDOCS-14356: Added bond best practices to the networking docs

Author: dfitzmau

modules/installation-network-user-infra.adoc

@@ -87,6 +87,15 @@ endif::ibm-z[]
 ifndef::ibm-z[]
 During the initial boot, the machines require an IP address configuration that is set either through a DHCP server or statically by providing the required boot options. After a network connection is established, the machines download their Ignition config files from an HTTP or HTTPS server. The Ignition config files are then used to set the exact state of each machine. The Machine Config Operator completes more changes to the machines, such as the application of new certificates or keys, after installation.
 
+Use a DHCP server for the long-term management of the machines for your cluster. Ensure that the DHCP server is configured to provide persistent IP addresses, DNS server information, and hostnames to the cluster machines. As a cluster administrator, ensure that you reserve the following IP addresses components that interact with the DHCP server:
+
+* Two unique virtual IP (VIP) addresses. One VIP address for the API endpoint and one VIP address for the wildcard ingress endpoint.
+* One IP address for the provisioner node. 
+* An IP address for each control plane node.
+* An IP address for each compute node.
+
+If you have multiple network interfaces that interact with a bonded interface, reserve the same IP addresses for these multiple network interfaces so to ensure better load balancing, fault tolerance, and bandwidth capabilites for your cluster network infrastructure. 
+
 [NOTE]
 ====
 * It is recommended to use a DHCP server for long-term management of the cluster machines. Ensure that the DHCP server is configured to provide persistent IP addresses, DNS server information, and hostnames to the cluster machines.

modules/installation-user-infra-machines-static-network.adoc

@@ -287,9 +287,14 @@ ifndef::ibm-z[]
 [discrete]
 === Bonding multiple SR-IOV network interfaces to a dual port NIC interface
 
-Optional: You can bond multiple SR-IOV network interfaces to a dual port NIC interface by using the `bond=` option.
+As an optional configuration, you can bond multiple SR-IOV network interfaces to a dual port NIC interface by using the `bond=` option. To apply this configuration to your cluster, complete the procedure steps for each node that runs on your cluster.
 
-On each node, you must perform the following tasks:
+[IMPORTANT]
+====
+If your network configuration includes an Open vSwitch (OVS) interface and you enabled `active-backup` bond mode, you must specify a Media Access Control (MAC) address failover. This configuration prevents node communication issues with the bonded interfaces, such as `eno1f0` and `eno2f0`.
+====
+
+.Procedure
 
 ifndef::installing-ibm-power[]
 . Create the SR-IOV virtual functions (VFs) following the guidance in link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_virtualization/managing-virtual-devices_configuring-and-managing-virtualization#managing-sr-iov-devices_managing-virtual-devices[Managing SR-IOV devices]. Follow the procedure in the "Attaching SR-IOV networking devices to virtual machines" section.
@@ -393,12 +398,6 @@ a|Override the Ignition platform ID for the installed system.
 a|`--console <spec>`
 a|Set the kernel and bootloader console for the installed system. For more information about the format of `<spec>`, see the link:https://www.kernel.org/doc/html/latest/admin-guide/serial-console.html[Linux kernel serial console] documentation.
 
-a|`--append-karg <arg>...`
-a|Append a default kernel argument to the installed system.
-
-a|`--delete-karg <arg>...`
-a|Delete a default kernel argument from the installed system.
-
 a|`-n`, `--copy-network`
 a|Copy the network configuration from the install environment.
 
@@ -464,12 +463,6 @@ a|Specify the kernel and bootloader console for the destination system.
 a|`--dest-device <path>`
 a|Install and overwrite the specified destination device.
 
-a|`--dest-karg-append <arg>`
-a|Add a kernel argument to each boot of the destination system.
-
-a|`--dest-karg-delete <arg>`
-a|Delete a kernel argument from each boot of the destination system.
-
 a|`--network-keyfile <path>`
 a|Configure networking by using the specified NetworkManager keyfile for live and destination systems.
 
@@ -488,15 +481,6 @@ a|Apply the specified installer configuration file.
 a|`--live-ignition <path>`
 a|Merge the specified Ignition config file into a new configuration fragment for the live environment.
 
-a|`--live-karg-append <arg>`
-a|Add a kernel argument to each boot of the live environment.
-
-a|`--live-karg-delete <arg>`
-a|Delete a kernel argument from each boot of the live environment.
-
-a|`--live-karg-replace <k=o=n>`
-a|Replace a kernel argument in each boot of the live environment, in the form `key=old=new`.
-
 a|`-f`, `--force`
 a|Overwrite an existing Ignition config.