IBMi.org – Bart's blog

IBM i and PowerVM features and tools

Category Archives: VIOS

VIOS 3.1 upgrade for everyone

I assume there are many installations which need to go to VIOS 3.1 by October 2020 due to end of support for VIOS 2.x. Because, I did not find any upgrade procedure for “dummies”, I decided to write one which I hope people find useful. I do not cover only the upgrade process itself, but also share some advises how to do it safely and recover in case of troubles. Upgrade Virtual I/O Server to 3.1 is completely different process than before. For instance, you are going to need an extra disk to perform the operation. Interested?

Read more of this post

New VIOS releases affect the Shared Ethernet Adapter (SEA) functionality

Long story short – how regular VIOS update ended with few weeks investigations completed with the serious VIOS bug and the APAR (IJ25390). The latest VIO releases contain a serious bug which may affect all VIOS/SEA client LPARs on IBM Power Servers.

Read more of this post

LPARKit – tool for managing VIOS from 5250 and cloning IBM i OS

I don’t think many people noticed this information yet, but recently a project which I was involved for last two years get live. My feeling is that many people do not understand the idea, thus I created a post explaining the functionality and possible usage. Read more about LPARKit below – tool which allows to create LPARs from 5250 and cloning IBM i OS. Read more of this post

How to prevent situation when server IPL may affect SAS controller

Last weekend I had a very unpleasant situation. A server reboot made an entire machine unusable. It was very difficult issue, costing an unplanned outage. Actually, we had all series of unfortunate events that day. I got aged by few years, but also learn there is always a solution, event in a hopeless situation. Read the entire story to avoid a similar problem. Read more of this post

Create an LPAR with specific WWPNs

By the command below an LPAR can be created with specific WWPNs, of course if you use NPIV adapters. It can be useful for LPARS migration between servers. It is extremely dangerous command, therefore it should be used only by people who knows what is for. Read more of this post

How to create SEA without touching VIOS

In this post I will describe how to create a Shared Ethernet Adapter (SEA) from the new HMC Enhanced GUI interface where no single command in VIOS command line is required. Read more of this post

My few words about HMC Enhanced + interface

Those of you who run recent hardware, probably noticed the new HMC interface called Enhanced+ GUI available since the HMC Firmware 8.8.1 SP1. In this post I would like to share my point of view and give some advice for people who would like to use it. Read more of this post

Building multiple LPARs with dedicated I/O from the CLI

Hi,

Nowadays, I’m preparing for huge hardware delivery. I’m about to get dozen of MMD’s. The challenge is to configure them (LPAR profiles, VIOS, etc) as soon as possible. I found the way how to automate creation of multiple VIO/LPAR profiles including I/O configuration for multiple servers without knowing SN of the expansions drawers.

Read more of this post

SR-IOV technology on POWER – my few words

Finally the announcement day arrived. POWER8 and SR-IOV have been introduced to the world, and I can share my experience from my last residency.

Single Root I/O Virtualization are not new adapters, but this is a new technology, standard, specification. In fact, it uses adapters which are on the market for some time already. Specification allows to get a slice of a physical adapter and assign it an LPAR. This feature requires a proper hardware, firmware, and all elements around it.

Read more of this post

IBM i with VLAN tagged network

Have you ever think to run your IBM i machine with in IEEE 802.1Q standard, and use the capabilities which offers VLAN tagging? You might heard that your AIX, LINUX colleagues already use it for ages, but for IBM i, this technology is still not available. Well, it is possible!  You can trunk multiple VLANs to one physical port, if you configure the POWER Hypervisor to handle this traffic. Read more of this post