Merge pull request #92681 from SNiemann15/ibmz_lpar_install_improve

[OCPBUGS-43563] Improvements to LPAR installation

Author: jeana-redhat

modules/installation-ibm-z-user-infra-machines-iso.adoc

@@ -76,7 +76,7 @@ The rootfs image is the same for FCP and DASD.
 ** Optional: To enable secure boot, add `coreos.inst.secure_ipl`
 
 ** For installations on DASD-type disks, complete the following tasks:
-... For `coreos.inst.install_dev=`, specify `/dev/dasda`.
+... For `coreos.inst.install_dev=`, specify `/dev/disk/by-path/ccw-<device_id>`. For <device_id> specify, for example, `0.0.1000`.
 ... Use `rd.dasd=` to specify the DASD where {op-system} is to be installed.
 ... Leave all other parameters unchanged.
 +
@@ -86,20 +86,19 @@ Example parameter file, `bootstrap-0.parm`, for the bootstrap machine:
 ----
 cio_ignore=all,!condev rd.neednet=1 \
 console=ttysclp0 \
-coreos.inst.install_dev=/dev/<block_device> \// <1>
+coreos.inst.install_dev=/dev/disk/by-id/scsi-<serial_number> \// <1>
 coreos.inst.ignition_url=http://<http_server>/bootstrap.ign \// <2>
 coreos.live.rootfs_url=http://<http_server>/rhcos-<version>-live-rootfs.<architecture>.img \// <3>
 coreos.inst.secure_ipl \// <4>
 ip=<ip>::<gateway>:<netmask>:<hostname>::none nameserver=<dns> \
 rd.znet=qeth,0.0.bdf0,0.0.bdf1,0.0.bdf2,layer2=1,portno=0 \
-rd.dasd=0.0.3490 \
-zfcp.allow_lun_scan=0
+rd.dasd=0.0.3490
 ----
 ifdef::ibm-z[]
-<1> Specify the block device type. For installations on DASD-type disks, specify `/dev/dasda`. For installations on FCP-type disks, specify `/dev/sda`.
+<1> Specify a unique fully qualified path depending on disk type. This can be either DASD-type or FCP-type disks.
 endif::ibm-z[]
 ifdef::ibm-z-lpar[]
-<1> Specify the block device type. For installations on DASD-type disks, specify `/dev/dasda`. For installations on FCP-type disks, specify `/dev/sda`. For installations on NVMe-type disks, specify `/dev/nvme0n1`.
+<1> Specify a unique fully qualified path depending on disk type. This can be either DASD-type, FCP-type, or NVMe-type disks.
 endif::ibm-z-lpar[]
 <2> Specify the location of the Ignition config file. Use `bootstrap.ign`, `master.ign`, or `worker.ign`. Only HTTP and HTTPS protocols are supported.
 <3> Specify the location of the `rootfs` artifact for the `kernel` and `initramfs` you are booting. Only HTTP and HTTPS protocols are supported.
@@ -115,16 +114,25 @@ Write all options in the parameter file as a single line and make sure you have
 When you install with multiple paths, you must enable multipathing directly after the installation, not at a later point in time, as this can cause problems.
 ====
 ... Set the install device as: `coreos.inst.install_dev=/dev/disk/by-id/scsi-<serial_number>`.
+
+. Optional: Create a `generic.ins` file:
 +
-[NOTE]
-====
-If additional LUNs are configured with NPIV, FCP requires `zfcp.allow_lun_scan=0`. If you must enable `zfcp.allow_lun_scan=1` because you use a CSI driver, for example, you must configure your NPIV so that each node cannot access the boot partition of another node.
-====
-... Leave all other parameters unchanged.
+Some installation methods also require a `generic.ins` file with a mapping of the location of the installation data in the file system of the Hardware Management Console (HMC), the DVD, or the FTP server and the memory locations where the data is to be copied. A sample `generic.ins` file is provided with the {op-system-base} installation media. The file contains file names for the initial RAM disk (`initrd.img`), the kernel image (`kernel.img`), and the parameter (`generic.prm`) files and a memory location for each file.
++
+.Example `generic.ins` file
+[source,terminal]
+----
+images/kernel.img 0x00000000
+images/initrd.img 0x02000000
+images/genericdvd.prm 0x00010480
+images/initrd.addrsize 0x00010408
+----
+
+. Leave all other parameters unchanged.
 +
 [IMPORTANT]
 ====
-Additional postinstallation steps are required to fully enable multipathing. For more information, see “Enabling multipathing with kernel arguments on {op-system}" in _Postinstallation machine configuration tasks_.
+Additional postinstallation steps are required to fully enable multipathing. For more information, see “Enabling multipathing with kernel arguments on {op-system}" in _Machine configuration_.
 ====
 // Add xref once it's allowed.
 +
@@ -142,8 +150,7 @@ rd.znet=qeth,0.0.bdf0,0.0.bdf1,0.0.bdf2,layer2=1,portno=0 \
 rd.zfcp=0.0.1987,0x50050763070bc5e3,0x4008400B00000000 \
 rd.zfcp=0.0.19C7,0x50050763070bc5e3,0x4008400B00000000 \
 rd.zfcp=0.0.1987,0x50050763071bc5e3,0x4008400B00000000 \
-rd.zfcp=0.0.19C7,0x50050763071bc5e3,0x4008400B00000000 \
-zfcp.allow_lun_scan=0
+rd.zfcp=0.0.19C7,0x50050763071bc5e3,0x4008400B00000000
 ----
 +
 Write all options in the parameter file as a single line and make sure you have no newline characters.
@@ -152,7 +159,7 @@ ifdef::ibm-z[]
 . Transfer the initramfs, kernel, parameter files, and {op-system} images to z/VM, for example with FTP. For details about how to transfer the files with FTP and boot from the virtual reader, see link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html-single/interactively_installing_rhel_over_the_network/index#installing-under-z-vm_booting-the-installation-media[Booting the installation on {ibm-z-name} to install {op-system-base} in z/VM].
 . Punch the files to the virtual reader of the z/VM guest virtual machine that is to become your bootstrap node.
 +
-See link:https://www.ibm.com/docs/en/zvm/latest?topic=commands-punch[PUNCH] in IBM Documentation.
+See link:https://www.ibm.com/docs/en/zvm/latest?topic=commands-punch[PUNCH] ({ibm-name} Documentation).
 +
 [TIP]
 ====
@@ -166,7 +173,7 @@ You can use the CP PUNCH command or, if you use Linux, the **vmur** command to t
 $ ipl c
 ----
 +
-See link:https://www.ibm.com/docs/en/zvm/latest?topic=commands-ipl[IPL] in IBM Documentation.
+See link:https://www.ibm.com/docs/en/zvm/latest?topic=commands-ipl[IPL] ({ibm-name} Documentation).
 +
 endif::ibm-z[]
 ifdef::ibm-z-lpar[]