[040] IBM POWER Pt. 4: Installing IBM i

preview_player
Показать описание
...a.k.a. "I just bought this POWER7 server on eBay...now what?"

In part four of this series, we'll install an IBM i partition.

Рекомендации по теме
Комментарии
Автор

WOW! Great education. I cant wait to get my home lab P7 or P8. I want to follow along each step and learn! Thank you

gort
Автор

As someone who has worked with os/400 at IBM back in the day I fully agree with your opinion about the os name change 😂

tiagosolano
Автор

Strange seeing the S36 option. Back in the day I worked on S34 which was a neat system. Thanks again Mathew. Really good playlist. Off to set up your mainframe one now

spikeukspikeuk
Автор

IBM REALLY needs to have something like a hobbyist licence & an emulator to go along with IBM i.

Also, are you planning on doing a full IBM i tour sometime?

mspeter
Автор

This is a great tutorial! When my drives arrive this is first on my list before I install Linux. Funny enough I have an HMC which I get with the server which should make the initial console connection even easier. Now all IBM needs to do is allow hobbyist licenses like OpenVMS has so don't have to wipe everything every 71 days. They are really strangling the platform by not having a program like this imo.

MrCommodorebob
Автор

Hi Matthew,

I've followed every step of this tutorial series beat for beat on my IBM Power 8 S814 and I'm getting to the screen at 47:49. The progress bar never begins to load and my console window abruptly ends the connection to my server. The only difference is I'm trying to install the Licensed Internal Code for IBM i 7.4. Do you know why this is happening?

Here are the status codes that display in my os400 partition. 3 that stand out to me are:
B6000415 (11:48:50 PM UTC) - Create user profile failed
CA0000A0 (11:02:23 PM UTC) - Open firmware package corrupted (phase 2)
CA000090 (11:02:23 PM UTC) - Open firmware package corrupted (phase 1)

However if you look at the timestamps for the package corrupted messages they seem to appear when I initially create the os400 partition in IVM.
Initializing the disk takes 34 minutes on my machine and the package corrupted messages appear 45 minutes before the partition blows up which is leading me to believe this.

B6000415 (11:48:50 PM UTC) - Create user profile failed
D200C301 (11:48:50 PM UTC)
D200C300 (11:48:50 PM UTC)
C2008119 (11:48:50 PM UTC)
C2008118 (11:48:50 PM UTC)
B2D03002 (11:48:50 PM UTC)
D200C2FF (11:48:50 PM UTC) - Hypervisor I/O reset complete successfully
D200C200 (11:48:50 PM UTC) - Deallocating events
D200C1FF (11:48:50 PM UTC) - Hypervisor I/O reset sent successfully
D200C100 (11:48:50 PM UTC) - Sending Hypervisor I/O reset
D200E03F (11:48:50 PM UTC)
D200E038 (11:48:50 PM UTC)
D200E036 (11:48:50 PM UTC)
D200E034 (11:48:50 PM UTC)
D200E032 (11:48:50 PM UTC)
D200E030 (11:48:50 PM UTC)
D200B04F (11:48:50 PM UTC)
D200B040 (11:48:50 PM UTC)
D200B08F (11:48:50 PM UTC) - End reset VIO slots
D200B080 (11:48:50 PM UTC) - Begin reset VIO slots
D200E06F (11:48:50 PM UTC) - End power off VIO slots
D200E060 (11:48:49 PM UTC) - Begin power off VIO slots
D200E06F (11:48:49 PM UTC) - End power off VIO slots
D200E060 (11:48:49 PM UTC) - Begin power off VIO slots
D200B06F (11:48:49 PM UTC) - End transfer VIO slot locks to VSP
D200B060 (11:48:49 PM UTC) - Begin transfer VIO slot locks to VSP
D200B07F (11:48:49 PM UTC) - End reset slots
D200B070 (11:48:49 PM UTC) - Begin reset slots
D200B05F (11:48:49 PM UTC) - End transfer slot locks to VSP
D200B050 (11:48:49 PM UTC) - Begin transfer slot locks to VSP
D200B3FF (11:48:49 PM UTC) - Hypervisor reset complete successfully
D200B310 (11:48:49 PM UTC) - Deactivating panel functions
D200B300 (11:48:49 PM UTC) - Closing Hypervisor events paths
D200B1FF (11:48:49 PM UTC) - Hypervisor reset successfully sent
D200B100 (11:48:49 PM UTC) - Sending Hypervisor reset
D200A200 (11:48:49 PM UTC) - Begin partition power down. SRC word 3 contrains the reason for the power off.
B6000415 (11:48:49 PM UTC) - Create user profile failed
D200A100 (11:48:49 PM UTC) - Received MSD SP attention
B6000415 (11:48:49 PM UTC) - Create user profile failed
C60041EE (11:48:49 PM UTC)
C60041ED (11:48:49 PM UTC)
C60041EB (11:48:49 PM UTC)
C60041F6 (11:14:43 PM UTC)
(11:12:25 PM UTC)
C60041F6 (11:09:17 PM UTC)
C6004036 (11:09:02 PM UTC)
C6004035 (11:09:02 PM UTC)
C6004034 (11:09:02 PM UTC)
C6004031 (11:09:02 PM UTC) - Destroy IPL task, DST has been started
C6004030 (11:09:02 PM UTC) - Free static storage
C6004029 (11:09:02 PM UTC) - Make IPL task not critical
C6004026 (11:08:56 PM UTC) - Hardware card checkout
C6004025 (11:08:56 PM UTC) - Initializes battery test
C6004024 (11:08:56 PM UTC) - Disable CPM
C6004021 (11:08:56 PM UTC) - Initialize performance data collector
C6003959 (11:08:56 PM UTC) - The typical sequence for an A/B/C mode IPL is 3900, 3910, 3911 (warm IPL only), 3912 (warm IPL only), 3913, 3915, 3917, and then other System Licensed Internal Code IPL progress codes. The others are seen when an IOP flash update occurs, usually on a D mode and possibly on a side (source) switch between A and B or C.
C6004017 (11:08:56 PM UTC) - Initialize RM (component) process management
C600401A (11:08:56 PM UTC)
C6004016 (11:07:17 PM UTC) - Set time of day
C6004033 (11:07:17 PM UTC) - Guest Partition Virtual I/O Initialization Complete
(11:07:16 PM UTC)
C6004508 (11:03:35 PM UTC) - Verifying system password (if DASD check OK)
C6004015 (11:03:35 PM UTC) - Initialize MISR
C6004014 (11:03:35 PM UTC) - Initialize RM (component) seize lock
C6004013 (11:03:35 PM UTC) - Initialize context management
C600401C (11:03:35 PM UTC)
C6004305 (11:03:34 PM UTC)
C60041F6 (11:03:28 PM UTC)
C60041F0 (11:03:22 PM UTC)
C600401B (11:02:51 PM UTC)
C6004012 (11:02:51 PM UTC) - Initialize RMAC component data values
C6004011 (11:02:51 PM UTC) - Initialize remote services
C500E200 (11:02:51 PM UTC) - Licensed Internal Code system hardware initialization
C6004009 (11:02:51 PM UTC) - Initialize I/O machine
C6004007 (11:02:51 PM UTC) - Start SLID
C6003962 (11:02:51 PM UTC) - The typical sequence for an A/B/C mode IPL is 3900, 3910, 3911 (warm IPL only), 3912 (warm IPL only), 3913, 3915, 3917, and then other System Licensed Internal Code IPL progress codes. The others are seen when an IOP flash update occurs, usually on a D mode and possibly on a side (source) switch between A and B or C.
C20082FF (11:02:51 PM UTC) - VSP IPL complete successfully
C2008200 (11:02:51 PM UTC) - Continue acknowledgement received from System Licensed Internal Code
C20081FF (11:02:50 PM UTC) - Processors started successfully, now waiting to receive the continue acknowledgement from System Licesned Internal Code
C2008120 (11:02:50 PM UTC) - Starting processors
C200811C (11:02:50 PM UTC)
C2008119 (11:02:50 PM UTC)
C2008118 (11:02:50 PM UTC)
C2008110 (11:02:50 PM UTC) - Initializing event paths
C2008109 (11:02:50 PM UTC)
C2008109 (11:02:50 PM UTC)
C2008109 (11:02:50 PM UTC)
C2008109 (11:02:50 PM UTC)
C200810A (11:02:50 PM UTC)
C20080CF (11:02:50 PM UTC)
C20080C0 (11:02:50 PM UTC)
C20080A0 (11:02:50 PM UTC) - End transfer VIO slot locks to partition
C2008080 (11:02:50 PM UTC) - Begin transfer VIO slot locks to partition
C2008060 (11:02:50 PM UTC) - End transfer slot locks to partition
C2008040 (11:02:50 PM UTC) - Begin transfer slot locks to partition
C20029FF (11:02:50 PM UTC)
C2002970 (11:02:50 PM UTC)
C2002960 (11:02:50 PM UTC)
C2002950 (11:02:50 PM UTC)
C2002900 (11:02:50 PM UTC)
C20028FF (11:02:50 PM UTC)
C2002800 (11:02:50 PM UTC)
C20025FF (11:02:50 PM UTC) - End powering on VIO slots
C2002500 (11:02:50 PM UTC) - Begin power on VIO slots
C20023FF (11:02:50 PM UTC) - End acquiring VIO slot locks
C2002300 (11:02:50 PM UTC) - Begin acquiring VIO slot locks
C200810F (11:02:50 PM UTC)
C2008104 (11:02:50 PM UTC) - Loading data structures into main store
C2008100 (11:02:50 PM UTC) - Initializing SP Communication Area #2
C20080FF (11:02:50 PM UTC) - Hypervisor low level session manager object is ready
D200C301 (11:02:50 PM UTC)
D200C300 (11:02:50 PM UTC)
C200802F (11:02:50 PM UTC)
C2008020 (11:02:50 PM UTC)
C20024FF (11:02:50 PM UTC) - End powering on slots
C2002400 (11:02:50 PM UTC) - Begin powering on slots
C20022FF (11:02:50 PM UTC) - End acquiring slot locks
C2002200 (11:02:50 PM UTC) - Begin acquiring slot locks
D200C2FF (11:02:50 PM UTC) - Hypervisor I/O reset complete successfully
D200C200 (11:02:50 PM UTC) - Deallocating events
D200C1FF (11:02:50 PM UTC) - Hypervisor I/O reset sent successfully
D200C100 (11:02:50 PM UTC) - Sending Hypervisor I/O reset
D200E03F (11:02:50 PM UTC)
D200E038 (11:02:50 PM UTC)
D200E036 (11:02:50 PM UTC)
D200E034 (11:02:50 PM UTC)
D200E032 (11:02:50 PM UTC)
D200E030 (11:02:50 PM UTC)
D200B04F (11:02:50 PM UTC)
D200B040 (11:02:50 PM UTC)
D200B08F (11:02:50 PM UTC) - End reset VIO slots
D200B080 (11:02:50 PM UTC) - Begin reset VIO slots
D200E06F (11:02:50 PM UTC) - End power off VIO slots
D200E060 (11:02:50 PM UTC) - Begin power off VIO slots
D200E06F (11:02:50 PM UTC) - End power off VIO slots
D200E060 (11:02:50 PM UTC) - Begin power off VIO slots
D200B06F (11:02:50 PM UTC) - End transfer VIO slot locks to VSP
D200B060 (11:02:50 PM UTC) - Begin transfer VIO slot locks to VSP
D200B07F (11:02:50 PM UTC) - End reset slots
D200B070 (11:02:50 PM UTC) - Begin reset slots
D200B05F (11:02:50 PM UTC) - End transfer slot locks to VSP
D200B050 (11:02:50 PM UTC) - Begin transfer slot locks to VSP
D200B3FF (11:02:50 PM UTC) - Hypervisor reset complete successfully
D200B310 (11:02:50 PM UTC) - Deactivating panel functions
D200B300 (11:02:50 PM UTC) - Closing Hypervisor events paths
D200B1FF (11:02:50 PM UTC) - Hypervisor reset successfully sent
D200B100 (11:02:50 PM UTC) - Sending Hypervisor reset
C2007150 (11:02:49 PM UTC)
[...]

nicholasricher
Автор

Those udf file uploads were all exactly 11.6MB/sec. I wonder if the virtual NIC was connected at 100Mbps instead of gigabit.

wesley
Автор

Hi, there is no possibility to use image catalog when install licpgm ?
Btw very good video !!
Thanks

christianchan
Автор

Hi I got one power 6 8203 I’m trying to set up the LAN console but when I try to do 25+26 in the panel control for get 65 and then 21 I don’t get the 65 just 64!

Do you know why 64 and not 65? I need 65
Thanks to all

netdem