Installing IBM i in an IBM i LPAR: Difference between revisions

From Try-AS/400
Jump to navigation Jump to search
(→‎Weblinks: Linkfix)
 
(3 intermediate revisions by the same user not shown)
Line 11: Line 11:
== Preparations in the host-partition ==
== Preparations in the host-partition ==
Follow steps in ''iVirtualization'', starting Page 17 to create (via HMC):
Follow steps in ''iVirtualization'', starting Page 17 to create (via HMC):
* Virtual SCSI Server Adapter (which provides virtual media to the guest LPAR),
* Virtual SCSI Server Adapter (that provides virtual media to the guest LPAR),
* IBM i guest partition and in there,
* IBM i guest partition and in there,
** Virtual SCSI Client Adapter,
** Virtual SCSI Client Adapter,
Line 18: Line 18:
By now you should have reached Page 29.
By now you should have reached Page 29.


In between, we'll prepare the install media images so they can be reached through the virtual SCSI adapter. Therefore, do a <code>WRKIMGCLG</code> and ''load'' the appropriate catalog to a previously created virtual optical drive, hereby called ''OPTVRT01''. Make sure that the I_BASE image is attached (12, work with entries, 6 attach).<b />
In between, we'll prepare the install media images so they can be reached through the virtual SCSI adapter. Therefore, do a <code>WRKIMGCLG</code> and ''load'' the appropriate catalog to a previously created virtual optical drive, hereby called ''OPTVRT01''. Make sure that the I_BASE image is attached (12, work with entries, 6 attach).<br />
Since there is most likely already a physical optical drive in the hardware, the virtual drive appears as ''OPT02'' to the guest LPAR.
Since there is most likely already a physical optical drive in the hardware, the virtual drive appears as ''OPT02'' to the guest LPAR.


Line 34: Line 34:


== Weblinks ==
== Weblinks ==
* [https://www.ibm.com/developerworks/community/files/form/anonymous/api/library/f57fde24-5f30-4295-91fb-e612c6a7a75a/document/0a050aca-3ac9-4e91-87dd-16032645a695/media&usg=AOvVaw32SPVQpq38HRzpSlyBcwv8 iVirtualization], IBM i Host and Client LPARs Easy Install Guide
* [[:File:IVirtualization_-_IBM_iHost_and_Client_LPAR_Easy_Install_Guide_v5.03_TR7.pdf|iVirtualization]], IBM i Host and Client LPARs Easy Install Guide, PDF
* [https://www.ibm.com/support/knowledgecenter/en/POWER5/iphbx_p5/troublesrccodec6004508.htm Startup step C6004508 takes longer than expected in D-mode IPL], IBM Knowledgecenter
* [https://www.ibm.com/support/knowledgecenter/en/POWER5/iphbx_p5/troublesrccodec6004508.htm Startup step C6004508 takes longer than expected in D-mode IPL], IBM Knowledgecenter


[[Category: Software Configuration Guide‏‎]]
[[Category: Software Configuration Guide‏‎]]
[[Category: System Administration‏‎]]
[[Category: System Administration‏‎]]

Latest revision as of 11:41, 21 September 2020

Qsicon Fixme.png This article isn't finished yet or needs to be revised. Please keep in mind that thus it may be incomplete.

Reason: Add remarks for LHEA and VLANs

Here I'll give step by step instructions how to install another instance of IBM i in an IBM i controlled LPAR on POWER hardware. This was tested with V7R2.

Requirements

  • Already installed and running IBM i in the first partition to serve as the Hosting LPAR,
  • IBM HMC (Hardware Management Console) connected with the server's firmware,
  • Install- and PTF-Media as Image Files with accompanying Image Catalog Object in IFS-Directories in the above partition,
  • At least 60 GiB free disk space in the first partition,
  • iVirtualization-PDF as linked in Weblinks.

Preparations in the host-partition

Follow steps in iVirtualization, starting Page 17 to create (via HMC):

  • Virtual SCSI Server Adapter (that provides virtual media to the guest LPAR),
  • IBM i guest partition and in there,
    • Virtual SCSI Client Adapter,
    • LHEA Resources. Detailed explanation how to isolate LPARs by VLANs follows.

By now you should have reached Page 29.

In between, we'll prepare the install media images so they can be reached through the virtual SCSI adapter. Therefore, do a WRKIMGCLG and load the appropriate catalog to a previously created virtual optical drive, hereby called OPTVRT01. Make sure that the I_BASE image is attached (12, work with entries, 6 attach).
Since there is most likely already a physical optical drive in the hardware, the virtual drive appears as OPT02 to the guest LPAR.

Next, we need to create the appropriate objects in the Hosting LPAR. Sign on to a 5150 terminal (emulator). Refer to iVirtualization, Page 38 to 40 for creating the appropriate *NWS description.

Afterwards, continue with Page 43 and create the virtual hard disk image for the new LPAR. A reasonably well installed system will eat about 25 GiB. Add some temporary space for installation/unpacking of the OS and PTFs. Recommended minimum is about 60 GiB. Of course it's easy to add more virtual disks later if the first file will get full over time.
Creation of this storage space will take a few minutes. If you don't want to block your 5250 session for that time, you can submit that as a batch job:

SBMJOB CMD(CRTNWSSTG NWSSTG(LPAR2ASP) NWSSIZE(61440) FORMAT(*OPEN)) JOB(CRTNWSSTG)

After this job is done, you'll get a message waiting indicator, telling you do use DSPMSG to check for messages. If all went well, you'll get a success message for creating the new Storage Space. Proceed with attaching the disk file to the *NWSD and vary on the *NWSD, shown starting Page 40.

Start the LPAR as shown starting Page 47. If you did all steps right, the partition will show some codes and then get stuck with SRC C6004508 for about 10..15 Minutes. This is normal, since the virtual firmware checks OPT01 (the physical drive) very extensive for IPL media. Wait it out. The IPL routine will eventually switch to the virtual drive represented by OPT02 of the guest LPAR. After a while, you'll be asked for the language feature. Continue with Page 49. The next steps may differ from the screens shown but after here, it's just another IBM i installation.

Remember that when asked to give the source media device at any point, you need to submit OPT02, because this device represents the attached OPTVRT01 from within the hosting LPAR.

Weblinks