Hi,

I have recently had the pleasure to install two pairs of VIO servers on two E1080 machines. For various reasons the only option available to me was to install them from the HMC using NIMOL. Once I got the network up, the installation was a breeze. I didn't really have to do much other than kick off the install.

However, I was a little taken aback by the time the installation took. The VIOs had 4 VPs and a 2 CPU entitlement with 8GB RAM. The VIOs were installed on NVMe disks. The actual installation time was about 15 minutes, but then after the VIOs first booted from their disks and the text "IBM Virtual IO Server" was displayed, another 30-40 minutes elapsed until the installation finished and I could accept the license. During this interval, there didn't seem to be much activity. I had the same experience on all 4 VIOs I built.

Can someone please explain what takes so long? Is this a configuration error? Any pointers would be greatly appreciated.

Thanks,
Z

------------------------------
-------------------------
Zoltan Soos
Senior Consultant
Covenco365, UK
------------------------------

#PowerVM

I suspect you already know this, but typically the longest part of an initial VIOS install is the enumeration of Fibre Channel devices.  If you have multiple FC cards mapped to the VIOS lpar, it will take some time to find the install candidates.  The SRC codes displayed on the HMC will give you a clue if this is happening, as they will be related to finding devices.

That doesn't really sound like what you are seeing.  NIMOL installs are essentially network boots using a combination of BOOTP and TFTP to boot, and TFTP to install network images.  Your limiting factor is probably the detection of the network device and the speed of the HMC.  I've found that if you have to do NIMOL or NIM based installs of VIOS, specifying the MAC address of the desired adapter speeds up the install significantly.  You probably have to use the command line to do that, so for a few installs its really not worth the effort.

------------------------------
Vincent Greene
------------------------------

Original Message:
Sent: Mon March 14, 2022 09:21 AM
From: Zoltan Soos
Subject: VIOS install from HMC via NIMOL takes long time

Hi,

I have recently had the pleasure to install two pairs of VIO servers on two E1080 machines. For various reasons the only option available to me was to install them from the HMC using NIMOL. Once I got the network up, the installation was a breeze. I didn't really have to do much other than kick off the install.

However, I was a little taken aback by the time the installation took. The VIOs had 4 VPs and a 2 CPU entitlement with 8GB RAM. The VIOs were installed on NVMe disks. The actual installation time was about 15 minutes, but then after the VIOs first booted from their disks and the text "IBM Virtual IO Server" was displayed, another 30-40 minutes elapsed until the installation finished and I could accept the license. During this interval, there didn't seem to be much activity. I had the same experience on all 4 VIOs I built.

Can someone please explain what takes so long? Is this a configuration error? Any pointers would be greatly appreciated.

Thanks,
Z

------------------------------
-------------------------
Zoltan Soos
Senior Consultant
Covenco365, UK
------------------------------

#PowerVM

Hi Vincent,

Thanks, but it's not the fibre channel devices. When the spinning happens we're way past the adapter configuration phase, and there are no codes on the LED either at that point. The HMC the latest and greatest Power based edition. I doubt it's the performance of the HMC hardware.

------------------------------
Zoltan Soos
Senior Consultant
Covenco365, United Kingdom
------------------------------

Original Message:
Sent: Thu March 17, 2022 11:49 AM
From: Vincent Greene
Subject: VIOS install from HMC via NIMOL takes long time

I suspect you already know this, but typically the longest part of an initial VIOS install is the enumeration of Fibre Channel devices.  If you have multiple FC cards mapped to the VIOS lpar, it will take some time to find the install candidates.  The SRC codes displayed on the HMC will give you a clue if this is happening, as they will be related to finding devices.

That doesn't really sound like what you are seeing.  NIMOL installs are essentially network boots using a combination of BOOTP and TFTP to boot, and TFTP to install network images.  Your limiting factor is probably the detection of the network device and the speed of the HMC.  I've found that if you have to do NIMOL or NIM based installs of VIOS, specifying the MAC address of the desired adapter speeds up the install significantly.  You probably have to use the command line to do that, so for a few installs its really not worth the effort.

------------------------------
Vincent Greene

Original Message:
Sent: Mon March 14, 2022 09:21 AM
From: Zoltan Soos
Subject: VIOS install from HMC via NIMOL takes long time

Hi,

I have recently had the pleasure to install two pairs of VIO servers on two E1080 machines. For various reasons the only option available to me was to install them from the HMC using NIMOL. Once I got the network up, the installation was a breeze. I didn't really have to do much other than kick off the install.

However, I was a little taken aback by the time the installation took. The VIOs had 4 VPs and a 2 CPU entitlement with 8GB RAM. The VIOs were installed on NVMe disks. The actual installation time was about 15 minutes, but then after the VIOs first booted from their disks and the text "IBM Virtual IO Server" was displayed, another 30-40 minutes elapsed until the installation finished and I could accept the license. During this interval, there didn't seem to be much activity. I had the same experience on all 4 VIOs I built.

Can someone please explain what takes so long? Is this a configuration error? Any pointers would be greatly appreciated.

Thanks,
Z

------------------------------
-------------------------
Zoltan Soos
Senior Consultant
Covenco365, UK
------------------------------

#PowerVM

On Mon, Mar 14, 2022 at 02:48:42PM +0000, Zoltan Soos via IBM Community wrote:
> I have recently had the pleasure to install two pairs of VIO servers
> on two E1080 machines. For various reasons the only option available
> to me was to install them from the HMC using NIMOL. Once I got the
> network up, the installation was a breeze. I didn't really have to
> do much other than kick off the install.
>
> However, I was a little taken aback by the time the installation
> took. The VIOs had 4 VPs and a 2 CPU entitlement with 8GB RAM. The
> VIOs were installed on NVMe disks. The actual installation time was
> about 15 minutes, but then after the VIOs first booted from their
> disks and the text "IBM Virtual IO Server" was displayed, another
> 30-40 minutes elapsed until the installation finished and I could
> accept the license. During this interval, there didn't seem to be
> much activity. I had the same experience on all 4 VIOs I built.
>
> Can someone please explain what takes so long? Is this a
> configuration error? Any pointers would be greatly appreciated.

I've having the exact same issue. PowerVM 3.1.0.10 Flash ISO installed
from HMC v9.2 952 using NIMOL built into the HMC.

The install is complete, and from the scrollback on the console it is
past multiuser initialization. The HBAs have already said no child
device so HBA detection isn't the holdup, it should now be prompting
for login on the console. However the Web UI is just sitting there
spinning. I wonder if there is a static timeout set in the UI code?

I'm likely to revert to NIM for the rest of my installs so I have the
opportunity to confirm my install device and skip this pause.


Successfully updated the Kernel Authorization Table.
Successfully updated the Kernel Role Table.
Successfully updated the Kernel Command Table.
Successfully updated the Kernel Device Table.
Successfully updated the Kernel Object Domain Table.
Successfully updated the Kernel Domains Table.
Successfully updated the Kernel RBAC log level.
Successfully updated the Kernel RBAC log level.
OPERATIONAL MODE Security Flags
ROOT : ENABLED
TRACEAUTH : DISABLED
System runtime mode is now OPERATIONAL MODE.
Setting tunable parameters...complete
Starting Multi-user Initialization
Performing auto-varyon of Volume Groups
Activating all paging spaces
0517-075 swapon: Paging device /dev/paging00 is already active.
swapon: Paging device /dev/hd6 activated.

The current volume is: /dev/hd1
Primary superblock is valid.

The current volume is: /dev/hd10opt
Primary superblock is valid.
Performing all automatic mounts
Multi-user initialization completed
Checking for srcmstr active...complete
Starting tcpip daemons:
0513-059 The syslogd Subsystem has been started. Subsystem PID is 6029616.
0513-059 The portmap Subsystem has been started. Subsystem PID is 3998150.
0513-059 The inetd Subsystem has been started. Subsystem PID is 6095252.
Finished starting tcpip daemons.
Starting NFS services:
0513-059 The biod Subsystem has been started. Subsystem PID is 5767624.
[STOP] Virtual I/O server detected, ASO will exit.0513-059 The rpc.statd Subsystem has been started. Subsystem PID is 5833162.
0513-059 The rpc.lockd Subsystem has been started. Subsystem PID is 5702078.
Completed NFS services.
default 1xx.xx.x.x done
EpicBuild loopback done
System reconfiguration in progress. Please wait.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi1 ):
0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi2 ):
0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi3 ):
0514-061 Cannot find a child device.
/ filesystem not converted.
Small inode extents are already enabled.
en2
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.org
inet0 changed
en2 changed
inet0 changed
Method error (/usr/lib/methods/cfgemfscsi -l fscsi1 ):
0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi2 ):
0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi3 ):
0514-061 Cannot find a child device.

Rebuild of Scriptinfo file is complete

Setting vpm_fold_policy to 4 in nextboot file
Setting vpm_fold_policy to 4
0513-059 The lldpd Subsystem has been started. Subsystem PID is 6422988.
0513-059 The ecpvdpd Subsystem has been started. Subsystem PID is 6947300.
IBM Virtual I/O Server


It just sits there. 15 minutes now.

------------------------------------------------------------------
Russell Adams Russell.Adams@AdamsSystems.nl
Principal Consultant Adams Systems Consultancy
http://adamssystems.nl/


Original Message:
Sent: 3/14/2022 9:22:00 AM
From: Zoltan Soos
Subject: VIOS install from HMC via NIMOL takes long time

Hi,

I have recently had the pleasure to install two pairs of VIO servers on two E1080 machines. For various reasons the only option available to me was to install them from the HMC using NIMOL. Once I got the network up, the installation was a breeze. I didn't really have to do much other than kick off the install.

However, I was a little taken aback by the time the installation took. The VIOs had 4 VPs and a 2 CPU entitlement with 8GB RAM. The VIOs were installed on NVMe disks. The actual installation time was about 15 minutes, but then after the VIOs first booted from their disks and the text "IBM Virtual IO Server" was displayed, another 30-40 minutes elapsed until the installation finished and I could accept the license. During this interval, there didn't seem to be much activity. I had the same experience on all 4 VIOs I built.

Can someone please explain what takes so long? Is this a configuration error? Any pointers would be greatly appreciated.

Thanks,
Z

------------------------------
-------------------------
Zoltan Soos
Senior Consultant
Covenco365, UK
------------------------------
#PowerVM

After observing further, I believe the HMC is waiting for RMC to connect back to it from VIO so that you can accept the license agreement using the checkbox.

------------------------------
========================
Russell Adams
https://adamssystems.nl/
========================
------------------------------

Original Message:
Sent: Mon March 21, 2022 12:26 PM
From: Russell Adams
Subject: VIOS install from HMC via NIMOL takes long time

On Mon, Mar 14, 2022 at 02:48:42PM +0000, Zoltan Soos via IBM Community wrote:
> I have recently had the pleasure to install two pairs of VIO servers
> on two E1080 machines. For various reasons the only option available
> to me was to install them from the HMC using NIMOL. Once I got the
> network up, the installation was a breeze. I didn't really have to
> do much other than kick off the install.
>
> However, I was a little taken aback by the time the installation
> took. The VIOs had 4 VPs and a 2 CPU entitlement with 8GB RAM. The
> VIOs were installed on NVMe disks. The actual installation time was
> about 15 minutes, but then after the VIOs first booted from their
> disks and the text "IBM Virtual IO Server" was displayed, another
> 30-40 minutes elapsed until the installation finished and I could
> accept the license. During this interval, there didn't seem to be
> much activity. I had the same experience on all 4 VIOs I built.
>
> Can someone please explain what takes so long? Is this a
> configuration error? Any pointers would be greatly appreciated.

I've having the exact same issue. PowerVM 3.1.0.10 Flash ISO installed
from HMC v9.2 952 using NIMOL built into the HMC.

The install is complete, and from the scrollback on the console it is
past multiuser initialization. The HBAs have already said no child
device so HBA detection isn't the holdup, it should now be prompting
for login on the console. However the Web UI is just sitting there
spinning. I wonder if there is a static timeout set in the UI code?

I'm likely to revert to NIM for the rest of my installs so I have the
opportunity to confirm my install device and skip this pause.


Successfully updated the Kernel Authorization Table.
Successfully updated the Kernel Role Table.
Successfully updated the Kernel Command Table.
Successfully updated the Kernel Device Table.
Successfully updated the Kernel Object Domain Table.
Successfully updated the Kernel Domains Table.
Successfully updated the Kernel RBAC log level.
Successfully updated the Kernel RBAC log level.
OPERATIONAL MODE Security Flags
ROOT : ENABLED
TRACEAUTH : DISABLED
System runtime mode is now OPERATIONAL MODE.
Setting tunable parameters...complete
Starting Multi-user Initialization
Performing auto-varyon of Volume Groups
Activating all paging spaces
0517-075 swapon: Paging device /dev/paging00 is already active.
swapon: Paging device /dev/hd6 activated.

The current volume is: /dev/hd1
Primary superblock is valid.

The current volume is: /dev/hd10opt
Primary superblock is valid.
Performing all automatic mounts
Multi-user initialization completed
Checking for srcmstr active...complete
Starting tcpip daemons:
0513-059 The syslogd Subsystem has been started. Subsystem PID is 6029616.
0513-059 The portmap Subsystem has been started. Subsystem PID is 3998150.
0513-059 The inetd Subsystem has been started. Subsystem PID is 6095252.
Finished starting tcpip daemons.
Starting NFS services:
0513-059 The biod Subsystem has been started. Subsystem PID is 5767624.
[STOP] Virtual I/O server detected, ASO will exit.0513-059 The rpc.statd Subsystem has been started. Subsystem PID is 5833162.
0513-059 The rpc.lockd Subsystem has been started. Subsystem PID is 5702078.
Completed NFS services.
default 1xx.xx.x.x done
EpicBuild loopback done
System reconfiguration in progress. Please wait.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi1 ):
0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi2 ):
0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi3 ):
0514-061 Cannot find a child device.
/ filesystem not converted.
Small inode extents are already enabled.
en2
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.org
inet0 changed
en2 changed
inet0 changed
Method error (/usr/lib/methods/cfgemfscsi -l fscsi1 ):
0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi2 ):
0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi3 ):
0514-061 Cannot find a child device.

Rebuild of Scriptinfo file is complete

Setting vpm_fold_policy to 4 in nextboot file
Setting vpm_fold_policy to 4
0513-059 The lldpd Subsystem has been started. Subsystem PID is 6422988.
0513-059 The ecpvdpd Subsystem has been started. Subsystem PID is 6947300.
IBM Virtual I/O Server


It just sits there. 15 minutes now.

------------------------------------------------------------------
Russell Adams Russell.Adams@AdamsSystems.nl
Principal Consultant Adams Systems Consultancy
http://adamssystems.nl/


Original Message:
Sent: 3/14/2022 9:22:00 AM
From: Zoltan Soos
Subject: VIOS install from HMC via NIMOL takes long time

Hi,

I have recently had the pleasure to install two pairs of VIO servers on two E1080 machines. For various reasons the only option available to me was to install them from the HMC using NIMOL. Once I got the network up, the installation was a breeze. I didn't really have to do much other than kick off the install.

However, I was a little taken aback by the time the installation took. The VIOs had 4 VPs and a 2 CPU entitlement with 8GB RAM. The VIOs were installed on NVMe disks. The actual installation time was about 15 minutes, but then after the VIOs first booted from their disks and the text "IBM Virtual IO Server" was displayed, another 30-40 minutes elapsed until the installation finished and I could accept the license. During this interval, there didn't seem to be much activity. I had the same experience on all 4 VIOs I built.

Can someone please explain what takes so long? Is this a configuration error? Any pointers would be greatly appreciated.

Thanks,
Z

------------------------------
-------------------------
Zoltan Soos
Senior Consultant
Covenco365, UK
------------------------------
#PowerVM

Hi, waiting 30 minutes, you are really patient. My way is to kick the wizard, takeover the console session by putty and continue the installation. I have seen the "accept license" working in GUI only one time, I think because of having a long coffee break...

Have fun!

Regards, Harald

------------------------------
Harald Stürner
------------------------------

Original Message:
Sent: Mon March 14, 2022 09:21 AM
From: Zoltan Soos
Subject: VIOS install from HMC via NIMOL takes long time

Hi,

I have recently had the pleasure to install two pairs of VIO servers on two E1080 machines. For various reasons the only option available to me was to install them from the HMC using NIMOL. Once I got the network up, the installation was a breeze. I didn't really have to do much other than kick off the install.

However, I was a little taken aback by the time the installation took. The VIOs had 4 VPs and a 2 CPU entitlement with 8GB RAM. The VIOs were installed on NVMe disks. The actual installation time was about 15 minutes, but then after the VIOs first booted from their disks and the text "IBM Virtual IO Server" was displayed, another 30-40 minutes elapsed until the installation finished and I could accept the license. During this interval, there didn't seem to be much activity. I had the same experience on all 4 VIOs I built.

Can someone please explain what takes so long? Is this a configuration error? Any pointers would be greatly appreciated.

Thanks,
Z

------------------------------
-------------------------
Zoltan Soos
Senior Consultant
Covenco365, UK
------------------------------

#PowerVM