OCPBUGS-55174: Updated the changing-cluster-network-mtu file with NIC info

Author: dfitzmau

modules/nw-cluster-mtu-change.adoc

@@ -23,8 +23,7 @@ ifndef::outposts[= Changing the cluster network MTU]
 ifdef::outposts[= Changing the cluster network MTU to support AWS Outposts]
 
 ifdef::outposts[]
-During installation, the maximum transmission unit (MTU) for the cluster network is detected automatically based on the MTU of the primary network interface of nodes in the cluster.
-You might need to decrease the MTU value for the cluster network to support an AWS Outposts subnet.
+During installation, the maximum transmission unit (MTU) for the cluster network is detected automatically based on the MTU of the primary network interface of nodes in the cluster. You might need to decrease the MTU value for the cluster network to support an AWS Outposts subnet.
 endif::outposts[]
 
 ifndef::outposts[As a cluster administrator, you can increase or decrease the maximum transmission unit (MTU) for your cluster.]
@@ -72,60 +71,59 @@ Status:
 
 ifndef::local-zone,wavelength-zone,post-aws-zones,outposts[]
 . Prepare your configuration for the hardware MTU:
-
-** If your hardware MTU is specified with DHCP, update your DHCP configuration such as with the following dnsmasq configuration:
++
+.. If your hardware MTU is specified with DHCP, update your DHCP configuration such as with the following dnsmasq configuration:
 +
 [source,text]
 ----
-dhcp-option-force=26,<mtu>
+dhcp-option-force=26,<mtu> <1>
 ----
+<1> Where `<mtu>` specifies the hardware MTU for the DHCP server to advertise.
++
+.. If your hardware MTU is specified with a kernel command line with PXE, update that configuration accordingly.
++
+.. If your hardware MTU is specified in a NetworkManager connection configuration, complete the following steps. This approach is the default for {product-title} if you do not explicitly specify your network configuration with DHCP, a kernel command line, or some other method. Your cluster nodes must all use the same underlying network configuration for the following procedure to work unmodified.
 +
---
-where:
-
-`<mtu>`:: Specifies the hardware MTU for the DHCP server to advertise.
---
-
-** If your hardware MTU is specified with a kernel command line with PXE, update that configuration accordingly.
-
-** If your hardware MTU is specified in a NetworkManager connection configuration, complete the following steps. This approach is the default for {product-title} if you do not explicitly specify your network configuration with DHCP, a kernel command line, or some other method. Your cluster nodes must all use the same underlying network configuration for the following procedure to work unmodified.
-
 ... Find the primary network interface by entering the following command:
-
 +
 [source,terminal]
 ----
-$ oc debug node/<node_name> -- chroot /host nmcli -g connection.interface-name c show ovs-if-phys0
+$ oc debug node/<node_name> -- chroot /host nmcli -g connection.interface-name c show ovs-if-phys0 <1>
 ----
+<1> where `<node_name>` specifies the name of a node in your cluster.
 +
---
-where:
-
-`<node_name>`:: Specifies the name of a node in your cluster.
---
-
-... Create the following NetworkManager configuration in the `<interface>-mtu.conf` file:
+... Create the following NetworkManager configuration in the `<interface>-mtu.conf` file.
 +
 .Example NetworkManager connection configuration
 [source,ini]
 ----
 [connection-<interface>-mtu]
-match-device=interface-name:<interface>
-ethernet.mtu=<mtu>
+match-device=interface-name:<interface> <1>
+ethernet.mtu=<mtu> <2>
 ----
+<1> Where `<interface>` specifies the primary network interface name.
+<2> Where `<mtu>` specifies the new hardware MTU value.
 +
---
-where:
-
-`<mtu>`:: Specifies the new hardware MTU value.
-`<interface>`:: Specifies the primary network interface name.
---
+[NOTE]
+====
+For nodes that use 2 network interface controller (NIC) bonds, specify the primary NIC bond and the secondary NIC Bond `<interface>-mtu.conf` file. 
 
-... Create two `MachineConfig` objects, one for the control plane nodes and another for the worker nodes in your cluster:
+.Example NetworkManager connection configuration
+[source,ini]
+----
+[connection-<primary-bond-interface>-mtu]
+match-device=interface-name:<bond-iface-name>
+ethernet.mtu=9000
 
-.... Create the following Butane config in the `control-plane-interface.bu` file:
+[connection-<secondary-bond-interface>-mtu]
+match-device=interface-name:<bond-slave-iface-name>
+ethernet.mtu=9000
+----
+====
 +
-[source,yaml, subs="attributes+"]
+... Create the following Butane config in the `control-plane-interface.bu` file, which is the `MachineConfig` object for the control plane nodes:
++
+[source,yaml,subs="attributes+"]
 ----
 variant: openshift
 version: {product-version}.0
@@ -142,10 +140,10 @@ storage:
 ----
 <1> Specify the NetworkManager connection name for the primary network interface.
 <2> Specify the local filename for the updated NetworkManager configuration file from the previous step.
-
-.... Create the following Butane config in the `worker-interface.bu` file:
 +
-[source,yaml, subs="attributes+"]
+... Create the following Butane config in the `worker-interface.bu` file, which is the `MachineConfig` object for the compute nodes:
++
+[source,yaml,subs="attributes+"]
 ----
 variant: openshift
 version: {product-version}.0
@@ -162,8 +160,8 @@ storage:
 ----
 <1> Specify the NetworkManager connection name for the primary network interface.
 <2> Specify the local filename for the updated NetworkManager configuration file from the previous step.
-
-.... Create `MachineConfig` objects from the Butane configs by running the following command:
++
+... Create `MachineConfig` objects from the Butane configs by running the following command:
 +
 [source,terminal]
 ----
@@ -255,10 +253,9 @@ machineconfiguration.openshift.io/state: Done
 +
 [source,terminal]
 ----
-$ oc get machineconfig <config_name> -o yaml | grep ExecStart
+$ oc get machineconfig <config_name> -o yaml | grep ExecStart <1>
 ----
-+
-where `<config_name>` is the name of the machine config from the `machineconfiguration.openshift.io/currentConfig` field.
+<1> Where `<config_name>` is the name of the machine config from the `machineconfiguration.openshift.io/currentConfig` field.
 +
 The machine config must include the following update to the systemd configuration:
 +
@@ -269,7 +266,7 @@ ExecStart=/usr/local/bin/mtu-migration.sh
 
 ifndef::local-zone,wavelength-zone,post-aws-zones,outposts[]
 . Update the underlying network interface MTU value:
-
++
 ** If you are specifying the new MTU with a NetworkManager connection configuration, enter the following command. The MachineConfig Operator automatically performs a rolling reboot of the nodes in your cluster.
 +
 [source,terminal]
@@ -278,7 +275,7 @@ $ for manifest in control-plane-interface worker-interface; do
     oc create -f $manifest.yaml
   done
 ----
-
++
 ** If you are specifying the new MTU with a DHCP server option or a kernel command line and PXE, make the necessary changes for your infrastructure.
 
 . As the Machine Config Operator updates machines in each machine config pool, it reboots each node one by one. You must wait until all the nodes are updated. Check the machine config pool status by entering the following command:
@@ -325,10 +322,9 @@ Verify that the following statements are true:
 +
 [source,terminal]
 ----
-$ oc get machineconfig <config_name> -o yaml | grep path:
+$ oc get machineconfig <config_name> -o yaml | grep path: <1>
 ----
-+
-where `<config_name>` is the name of the machine config from the `machineconfiguration.openshift.io/currentConfig` field.
+<1> Where `<config_name>` is the name of the machine config from the `machineconfiguration.openshift.io/currentConfig` field.
 +
 If the machine config is successfully deployed, the previous output contains the `/etc/NetworkManager/conf.d/99-<interface>-mtu.conf` file path and the `ExecStart=/usr/local/bin/mtu-migration.sh` line.
 endif::local-zone,wavelength-zone,post-aws-zones,outposts[]
@@ -339,14 +335,9 @@ endif::local-zone,wavelength-zone,post-aws-zones,outposts[]
 +
 ----
 $ oc patch Network.operator.openshift.io cluster --type=merge --patch \
-  '{"spec": { "migration": null, "defaultNetwork":{ "ovnKubernetesConfig": { "mtu": <mtu> }}}}'
+  '{"spec": { "migration": null, "defaultNetwork":{ "ovnKubernetesConfig": { "mtu": <mtu> }}}}' <1>
 ----
-+
---
-where:
-
-`<mtu>`:: Specifies the new cluster network MTU that you specified with `<overlay_to>`.
---
+<1> Where: `<mtu>` specifies the new cluster network MTU that you specified with `<overlay_to>`.
 
 . After finalizing the MTU migration, each machine config pool node is rebooted one by one. You must wait until all the nodes are updated. Check the machine config pool status by entering the following command:
 +

networking/changing-cluster-network-mtu.adoc

@@ -9,7 +9,10 @@ toc::[]
 [role="_abstract"]
 As a cluster administrator, you can change the MTU for the cluster network after cluster installation. This change is disruptive as cluster nodes must be rebooted to finalize the MTU change.
 
+// About the cluster MTU
 include::modules/nw-cluster-mtu-change-about.adoc[leveloffset=+1]
+
+// Changing the cluster network MTU or Changing the cluster network MTU to support AWS Outposts
 include::modules/nw-cluster-mtu-change.adoc[leveloffset=+1]
 
 [role="_additional-resources"]