VIOS
VIOS
- Details
- Parent Category: главный раздел
- Category: VIOS
- Hits: 4099
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
- Details
- Parent Category: главный раздел
- Category: VIOS
- Hits: 5091
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 Repository
- Details
- Parent Category: главный раздел
- Category: VIOS
- Hits: 3921
Step By Step NPIV configuration
ual Adapter
- Details
- Parent Category: главный раздел
- Category: VIOS
- Hits: 3494
Make sure you are monitoring file system space on your VIOS.
Why?
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
2.2.1.3
$ mkvdev -vdev hdisk1 -vadapter vhost0 -dev vhdisk1
*******************************************************************************
The command's response was not recognized. This may or may not indicate a problem.
*******************************************************************************