Создание виртуального DVD на VIOS

E-mail Печать PDF
Рейтинг пользователей: / 2

CDROM - DVDROM (Virtual Optical Device):

Any optical device equipped on the Virtual I/O Server partition (either CD-ROM, DVD-ROM, or DVD-RAM) can be virtualized and assigned at any logical partition, one at a time, using the same virtual SCSI adapter provided to virtual disks. Virtual optical devices can be used to install the operating system and, if DVD-RAM, to make backups.

Creating Virtual Optical Device:

1. On VIO Server create SCSI Server Adapter. This adapter is set to Any client partition can connect.
This dedicated adapter for the virtual optical device helps to make things easier from a system management point of view.

2. On client LPAR: create SCSI client adapter, mapping the id with the server adapter (above)

3. cfgdev (on vio) will bring up a new vhostX
cfgmgr (on client) will bring up a new vscsiX

4. On VIO Server create optical device:

-for using physical CDs and DVDs, create an optical device
$ mkvdev -vdev cd0 -vadapter vhost4 -dev vcd
vcd Available

$ lsdev -virtual
vcd             Available  Virtual Target Device - Optical Media

-for file backed (iso images) optical device
$ mkvdev -fbo -vadapter vhost1
vtopt0 Available

$lsdev -virtual
vtopt0           Available   Virtual Target Device - File-backed Optical

(copy the iso image to /var/vio/VMLibrary, 'lsrep' will show media repository content)
(lssp -> mkrep -sp rootvg -size 4G    <--this will create media repository)
(creating an iso image: mkvopt -name <filename>.iso -dev cd0 -ro)

load the image into the vtopt0 device: loadopt -vtd vtopt0 -disk dvd.1022A4_OBETA_710.iso
(lsmap -all will show it)

or you can check it:
padmin@vios1 : /home/padmin # lsvopt
VTD             Media                                   Size(mb)
vtopt0          AIX_7100-00-01_DVD_1_of_2_102010.iso        3206

if later another disk is needed, you can unload an image with this command: unloadopt -vtd vtopt0
if we don't need the image anymore at all we can remove it from the repository: rmvopt -name AIX_7100-00-01.iso


Как установить ОС через HMC

E-mail Печать PDF
Рейтинг пользователей: / 3

Since HMC firmware version 7.7.7, IBM added very cool feature, which allows installation of the Virtual I/O Server directly from the HMC. This is very convenient when you get your POWER machine to the new location, and you want to install an operating system, for instance, IBM i or AIX, but you prefer to do it remotely.

There was another command installios for quite some time in the HMC. But it wasn’t very user friendly. Especially for IBM i administrators, the command looks like an occult. With new feature ‘Virtual I/O Server Repository’ it’s very easy to get the VIOS installed, even for someone who has never done it before.

If you get a brand new machine to a new location, and you don’t have a NIM server (or you don’t know what is this), it’s enough that you get the HMC operational and accessible from a remote location (you can ask a business partner to configure it). The HMC will host the VIOS installation images and performs almost automatically entire VIOS installation process.

1.Download VIOS installation .iso images from IBM website.

2.Copy installation images to the HMC. Go to HMC Management – Manage Virtual I/O Server Image RepositoryHMC-ManageVIOS Image repository


3.Complete information where the images can be copied from

HMC-ManageVIOS Image repository_details

HMC-ManageVIOS Image repository_result

4. Select your brand new VIOS partition profile, and click Operations – Activate – Profile and select Yes for Install Virtual I/O Server as part of activation process?

HMC-ManageVIOS Image repository_install

5. Type in the IP address, subnet mask and default gateway for VIOS.

HMC-ManageVIOS Image repository_IP


HMC-ManageVIOS Image repository_installation_process

6. The installation process starts. It will do everything what is necessary to install the VIOS.

Remember that your HMC console acts as a NIM server. Therefore, if the console is behind the firewall, you must ensure that all ports required by NIM are opened.

7. When the installation finished, open virtual terminal in the HMC vtmenu , and do the first login to the VIOS with a default password padmin for padmin user.

Once the VIOS is installed, you can use it as virtual media repository. It allows you to create virtual drive where you can load OS installation images (IBM i, AIX, or Linux) and proceed with OS installation completely remotely. This process I described some time ago here.

I think this is great feature in the HMC, and IBM i people should use it. It saves time, its very convenient, and you don’t have to travel to the data room just to insert the SLIC DVD.

Обновлено 21.01.2017 15:08

Как конфигурировать NPIV

E-mail Печать PDF

Step By Step NPIV configuration

For maximum redundancy for the paths create the instance on dual VIOS. We will consider an scenario having Power6/7 Server, with 2 PCI Dual/Single port 8 GB Fibre Card with VIOS level – 2,2 FP24 installed and VIOS is in shutdown state.
First we need to create Virtual fibre channel adapter on each VIOS which we will later on map to physical fibre adapter after logging into VIOS similarly as we do for Ethernet
Please Note: - Create the all lpar clients as per requirements and then configure the Virtual fiber adapter on VIOS. Since we are mapping one single physical fiber adapter to different hosts, hence we need to create that many virtual fiber channel adapter. Dynamically virtual fiber channel adapter can be created but don’t forget to add in profile else you lost the config on power-off.
1. 1. Create Virtual fibre channel adapter on both VIOS server.
HMC--> Managed System-->Manage Profile-->Virtual Adapter
Let say I have define the virtual fiber adapter for AIX client Netwqa  with adapter ids 33 & client adapter id 33
Обновлено 21.01.2017 15:11 Подробнее...

Следите за размером файловой системы на VIOS

E-mail Печать PDF
Рейтинг пользователей: / 1

Make sure you are monitoring file system space on your VIOS.


If you run out of space in the root file system, odd things can happen when you try to map virtual devices to virtual adapters with mkvdev.

For example, a colleague of mine was attempting to map a new hdisk to a vhost adapter on a pair of VIOS. The VIOS was running a recent version of code. He received the following error message (see below). It wasn’t a very helpful message. At first I thought it was due to the fact that he had not set the reserve_policy attribute for the new disk to no_reserve on both VIOS. Changing the value for that attribute did not help.

$ ioslevel

$ mkvdev -vdev hdisk1 -vadapter vhost0 -dev vhdisk1


The command's response was not recognized. This may or may not indicate a problem.


Обновлено 06.09.2014 11:11 Подробнее...