Merge pull request #85904 from SNiemann15/abi_lpar_note

[OCPBUGS-44822] Add note about persistent mac addresses

Author: xenolinux

modules/configuring-network-overrides-ibm-z.adoc

@@ -3,10 +3,15 @@
 // * installing/installing_with_agent_based_installer/prepare-pxe-assets-agent.adoc
 :_mod-docs-content-type: PROCEDURE
 [id="configuring-network-overrides-ibm_{context}"]
-= Configuring network overrides in {ibm-z-title}
+= Configuring network overrides in an {ibm-z-title} environment
 
 You can specify a static IP address on {ibm-z-title} machines that use Logical Partition (LPAR) and z/VM. This is useful when the network devices do not have a static MAC address assigned to them.
 
+[NOTE]
+====
+If you are using an OSA network device in Processor Resource/Systems Manager (PR/SM) mode, the lack of persistent MAC addresses can lead to a dynamic assignment of roles for nodes. This means that the roles of individual nodes are not fixed and can change, as the system is unable to reliably associate specific MAC addresses with designated node roles. If MAC addresses are not persistent for any of the interfaces, roles for the nodes are assigned randomly during Agent-based installation.
+====
+
 .Procedure
 
 * If you have an existing `.parm` file, edit it to include the following entry:
@@ -16,7 +21,7 @@ You can specify a static IP address on {ibm-z-title} machines that use Logical P
 ai.ip_cfg_override=1
 ----
 +
-This parameter allows the file to add the network settings to the CoreOS installer.
+This parameter allows the file to add the network settings to the {op-system-first} installer.
 +
 
 .Example `.parm` file
@@ -35,7 +40,7 @@ ignition.firstboot ignition.platform.id=metal
 random.trust_cpu=on
 ----
 <1> For the `coreos.live.rootfs_url` artifact, specify the matching `rootfs` artifact for the `kernel` and `initramfs` that you are booting. Only HTTP and HTTPS protocols are supported.
-<2> For installations on direct access storage devices (DASD) type disks, use `rd.` to specify the DASD where {op-system-first} is to be installed. For installations on Fibre Channel Protocol (FCP) disks, use `rd.zfcp=<adapter>,<wwpn>,<lun>` to specify the FCP disk where {rhel} is to be installed.
+<2> For installations on direct access storage devices (DASD) type disks, use `rd.` to specify the DASD where {op-system-first} is to be installed. For installations on Fibre Channel Protocol (FCP) disks, use `rd.zfcp=<adapter>,<wwpn>,<lun>` to specify the FCP disk where {op-system} is to be installed.
 <3> Specify values for `adapter`, `wwpn`, and `lun` as in the following example: `rd.zfcp=0.0.8002,0x500507630400d1e3,0x4000404600000000`.
 
 [NOTE]

modules/installing-ocp-agent-ibm-z.adoc

@@ -25,9 +25,9 @@ Currently, ISO boot support on {ibm-z-name} (`s390x`) is available only for {op-
 
 In {ibm-z-title} environments, advanced networking technologies such as Open Systems Adapter (OSA), HiperSockets, and Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) require specific configurations that deviate from the standard network settings and those needs to be persisted for multiple boot scenarios that occur in the Agent-based Installation.
 
-To persist these parameters during boot, the `ai.ip_cfg_override=1` parameter is required in the `paramline`. This parameter is used with the configured network cards to ensure a successful and efficient deployment on {ibm-z-title}.
+To persist these parameters during boot, the `ai.ip_cfg_override=1` parameter is required in the `.parm` file. This parameter is used with the configured network cards to ensure a successful and efficient deployment on {ibm-z-title}.
 
-The following table lists the network devices that are supported on each hypervisor for the network configuration override functionality :
+The following table lists the network devices that are supported on each hypervisor for the network configuration override functionality:
 
 [cols="3,2,2,2,2", options="header"]
 |====
@@ -45,7 +45,7 @@ The following table lists the network devices that are supported on each hypervi
 
 | Direct attached Open Systems Adapter (OSA)
 | Supported
-|  Not required ^[3]^
+| Not required ^[3]^
 | Supported
 | Not required