Under Construction
Interactive Installation
The interactive installation via the HMC is a very convenient way to install a virtual I/O server. The installation is started using the command “hmc installios” and specifying an HMC. Everything else is queried interactively and then the installation is started.
Before starting the installation, in the case of a dual-HMC configuration, you should first determine on which HMC the installation image or full backup to be installed is stored. The HMC to be used for the installation must be specified as the only argument for “hmc installios”.
If you want to install an installation image, it is best to use the command “vios lsviosimg” to find out which installation images are available via which HMC for the relevant Virtual I/O server:
LPAR-Tool
$ vios lsviosimg ms05-vio1
NAME HMC SIZE IMAGE_FILES
VIOS_4.1.0.0 hmc01 3487.55 dvdimage.v1.iso
VIOS_3.1.4.20 hmc01 5985.77 dvdimage.v2.iso,dvdimage.v1.iso
VIOS_4.1.0.0 hmc02 3487.68 dvdimage.v1.iso
VIOS_3.1.4.30 hmc02 6063.53 dvdimage.v2.iso,dvdimage.v1.iso
$
HMC-CLI
hscroot@hmc01:~> lsviosimg
name=VIOS_4.1.0.0,image_files=dvdimage.v1.iso,size=3487.55
name=VIOS_3.1.4.20,"image_files=dvdimage.v2.iso,dvdimage.v1.iso",size=5985.77
hscroot@hmc01:~>
hscroot@hmc02:~> lsviosimg
name=VIOS_4.1.0.0,image_files=dvdimage.v1.iso,size=3487.68
name=VIOS_3.1.4.30,"image_files=dvdimage.v2.iso,dvdimage.v1.iso",size=6063.53
hscroot@hmc02:~>
If version 4.1.0.00 is to be installed, both HMCs (hmc01 and hmc02) can be used. If version 3.1.4.20 is to be installed, the HMC hmc01 must be used. For version 3.1.4.30, the HMC hmc02 must be used.
Note: The installation images can be found on the HMCs in the directory /extra/viosimages. For each available image there is a subdirectory with the name of the image.
If a fullback of a virtual I/O server stored on one of the HMCs is to be installed, the corresponding HMC can be determined using the command “vios lsviosbk”:
LPAR-Tool
$ vios lsviosbk ms05-vio1
NAME TYPE SIZE HMC LAST_MODIFIED
nim_resources.tar vios 3742.695 hmc01 04/08/2024 18:27:18
fullbackup_1712646419.tar vios 3743.613 hmc01 04/09/2024 07:14:33
backup2.tar vios 3745.957 hmc02 04/09/2024 11:59:07
$
HMC-CLI
hscroot@hmc01:~> lsviosbk
...
name=nim_resources.tar,type=vios,sys_name=ms05,mtms=9009-22G*89EA9C1,vios_name=ms05-vio1,vios_id=1,vios_uuid=42CE2685-A52B-4164-9157-DF008561E07A,last_modified=04/08/2024 18:27:18,size=3742.695
name=fullbackup_1712646419.tar,type=vios,sys_name=ms05,mtms=9009-22G*89EA9C1,vios_name=ms05-vio1,vios_id=1,vios_uuid=42CE2685-A52B-4164-9157-DF008561E07A,last_modified=04/09/2024 07:14:33,size=3743.613
...
hscroot@hmc01:~>
hscroot@hmc02:~> lsviosbk
...
name=backup2.tar,type=vios,sys_name=ms05,mtms=9009-22G*89EA9C1,vios_name=ms05-vio1,vios_id=1,vios_uuid=42CE2685-A52B-4164-9157-DF008561E07A,last_modified=04/09/2024 11:59:07,size=3745.957
...
hscroot@hmc02:~>
The most recent backup is backup2.tar and is stored on the HMC hmc02.
Note: Backups are stored on the HMCs in the /data/viosbackup directory. There is a subdirectory for each managed system, and within this there is a subdirectory for the associated virtual I/O servers, in which the backups are located.
The easiest way to find the correct path is this:
LPAR-Tool
$ hmc cmd hmc02 ls "/data/viosbackup/*/*/backup2.tar"
'/data/viosbackup/9009-22G*89EA9C1/42CE2685-A52B-4164-9157-DF008561E07A/backup2.tar'
Shared connection to hmc02 closed.
$
HMC-CLI
hscroot@hmc02:~> ls "/data/viosbackup/*/*/backup2.tar"
'/data/viosbackup/9009-22G*89EA9C1/42CE2685-A52B-4164-9157-DF008561E07A/backup2.tar'
hscroot@hmc02:~>
If a full backup is to be used on an NFS server, in principle any HMC connected to the Virtual I/O server can be used.
Once you have determined the correct HMC, you can start the command “hmc installios” with this HMC as an argument:
LPAR-Tool
$ hmc installios hmc02
Logging session output to /tmp/installios.720769.log.
...
HMC-CLI
hscroot@hmc02:~> installios
Logging session output to /tmp/installios.720769.log.
...
First, the managed system of the Virtual I/O server must be selected:
The following objects of type "managed system" were found. Please select one:
1. ms01
2. ms02
3. ms03
4. ms04
5. ms05
6. ms06
Enter a number (1-6): 5
Next, you need to select the Virtual I/O Server to be installed:
The following objects of type "virtual I/O server partition" were found. Please select one:
1. ms05-vio1
2. ms05-vio2
Enter a number (1-2): 1
You will then be asked which profile to use:
The following objects of type "profile" were found. Please select one:
1. standard
2. vlan100
Enter a number (1-2): 2
The installation image or fullback to be installed must then be specified with the full path. In the case of an installation image, the first ISO image must be specified. Alternatively, a fullback on an NFS server can also be specified. We show the example input for all 3 cases below.
Using the installation image VIOS_3.1.4.30, the full path to use is the following:
Enter the source of the installation images [/dev/cdrom]: /extra/viosimages/VIOS_3.1.4.30/dvdimage.v1.iso
In case of the fullback backup2.tar from above the path would be:
Enter the source of the installation images [/dev/cdrom]: /data/viosbackup/9009-22G*89EA9C1/42CE2685-A52B-4164-9157-DF008561E07A/backup2.tar
If a fullback with path /export/VIOS/ms05-vio1/nim_resources.tar is used on the NFS server 10.255.255.57
Enter the source of the installation images [/dev/cdrom]: 10.255.255.57:/export/VIOS/ms05-vio1/nim_resources.tar
Then you must specify the IP address of the virtual I/O server, netmask and gateway:
Enter the client's intended IP address: 10.255.255.59
Enter the client's intended subnet mask: 255.255.255.0
Enter the client's gateway: 10.255.255.57
When querying the speed to use, “default” is the best value in most cases:
(Note: To use the adapter's default setting, enter 'default' for speed)
Enter the client's speed [100]: default
Then you have to specify the network interface of the HMC through which the virtual I/O server can be reached. In most cases there is only one interface with a public IP and this must then be used:
Please select an adapter you would like to use for this installation.
(WARNING: The client IP address must be reachable through this adapter!
1. eth0 10.255.255.56
2. eth1 10.0.0.1
3. eth2
4. eth3
5. eth4
6. eth5
7. usb0 169.254.95.121
Enter a number (1-7): 1
If there are multiple interfaces and the wrong interface is selected, the installation will stall later and will not be successful. One of the other interfaces should then be selected.
The command then determines possible Ethernet adapters of the Virtual I/O Server for the installation. One of the adapters must then be selected:
Retrieving information for available network adapters
This will take several minutes...
The following objects of type "ethernet adapters" were found. Please select one:
1. ent U9009.22G.81EA9C1-V1-C5-T1 828d5ff9b705 /vdevice/l-lan@30000005 n/a virtual
Enter a number: 1
Finally, a summary of the data entered so far is displayed. This can be confirmed by pressing Enter and the actual installation can be started. Or the installation can be canceled at this point by pressing Ctrl-C:
Here are the values you entered:
managed system = ms05
virtual I/O server partition = ms05-vio1
profile = vlan100
source = /extra/viosimages/VIOS_3.1.4.30/dvdimage.v1.iso
IP address = 10.255.255.59
subnet mask = 255.255.255.0
gateway = 10.255.255.57
speed = default
duplex = default
install interface = eth0
ethernet adapters = 82:8d:5f:f9:b7:05
Press enter to proceed or type Ctrl-C to cancel...
If the data is correct, you should continue with the installation. The rest of the installation runs automatically without any user input:
nimol_config MESSAGE: Added "REMOTE_ACCESS_METHOD /usr/bin/rsh" to the file "/etc/nimol.conf"
nimol_config MESSAGE: Removed "disable = yes" from the file "/etc/xinetd.d/tftp"
nimol_config MESSAGE: Added "disable = no" to the file "/etc/xinetd.d/tftp"
nimol_config MESSAGE: Removed "local2,local3.* -/var/log/localmessages;RSYSLOG_TraditionalFileFormat" from the file "/etc/rsyslog.conf"
nimol_config MESSAGE: Added "local3.* -/var/log/localmessages;RSYSLOG_TraditionalFileFormat" to the file "/etc/rsyslog.conf"
nimol_config MESSAGE: Added "local2.* /var/log/nimol.log" to the file "/etc/rsyslog.conf"
...
During the installation, messages about the status of the installation are continuously displayed, e.g.:
Tue May 7 09:01:46 2024
-----------/var/log/nimol.log :---------------
Tue May 7 09:05:57 2024 nimol: installios: led code=0c54 : ,info=Installing either BOS or additional packages.
If desired, the installation can also be monitored by opening a console:
LPAR-Tool
$ lpar console ms05-vio1
Open in progress
Open Completed.
89 9 Network Install Manager customization.
HMC-CLI
hscroot@hmc02:~> mkvterm -m ms05 -p ms05-vio1
Open in progress
Open Completed.
89 9 Network Install Manager customization.
Note: A console should only be opened once the installation has started, since the HMC itself opens the console to the Virtual I/O Server before beginning the installation.
When the installation is complete, output similar to the following is shown:
Tue May 7 09:01:46 2024
-----------/var/log/nimol.log :---------------
May 7 09:12:58 10_255_255_59 nimol: ,info=BOS install 100% complete
Finally, there are some reports of cleanup work by the HMC after the installation.
The Virtual I/O Server will reboot automatically after installation.
If the Virtual I/O Server was newly installed using an installation image, you must first accept IBM’s license terms before you can use it. Since no password is set for the user padmin, it is best to open a console:
LPAR-Tool
$ lpar console ms05-vio1
Open in progress
Open Completed.
IBM Virtual I/O Server
login: padmin
[compat]: 3004-610 You are required to change your password.
Please choose a new one.
padmin's New password: XXXXXXXX
Enter the new password again: XXXXXXXX
Indicate by selecting the appropriate response below whether you
accept or decline the software maintenance terms and conditions.
Accept (a) | Decline (d) | View Terms (v) > a
$
HMC-CLI
hscroot@hmc02:~> mkvterm -m ms05 -p ms05-vio1
Open in progress
Open Completed.
IBM Virtual I/O Server
login: padmin
[compat]: 3004-610 You are required to change your password.
Please choose a new one.
padmin's New password: XXXXXXXX
Enter the new password again: XXXXXXXX
Indicate by selecting the appropriate response below whether you
accept or decline the software maintenance terms and conditions.
Accept (a) | Decline (d) | View Terms (v) > a
$
When logging in as the user padmin, a password must be set. The IBM license terms can then be confirmed. Only then can the Virtual I/O Server be used!
Note: There is no default password for the user padmin!
If a fullback has been installed, no license terms need to be accepted and the user padmin naturally has the password that was valid at the time the backup was created.