IBMi.org – Bart's blog

IBM i and PowerVM features and tools

Category Archives: HMC

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

Advertisements

Monitor CPU, POOL utilization from PHYP cycles on POWER8

One of the most popular post on my blog, is the one about monitoring a CPU by CPU cycles dispatched by a POWER Hypervisor link.

With POWER8 we receive new attributes in lslparutil command.

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

Redbook residency – Austin 2014

Few days ago, I came back from IBM in Austin. It was my first time in Austin, homeland of POWER systems, chips, AIX and PowerVM development, but third residency in general. Read more of this post

How to restrict usage of ssh keys for specific hosts only.

In this post I would like to show you how to restrict a ssh connection for a specific host only.

Read more of this post

viosvrcmd – the backdoor to the PHyp?

The title is provocative, but if we agree that Virtual I/O Server is part of the POWER Hypervisor it’s absolutely true. The command viosvrcmd is a HMC command which allows to perform any non-interactive VIO commands by a HMC user which has the taskrole authority – ‘VirtualIOServerCommand’ and visibility to a VIOS LPAR without be prompting for VIOS user and password.

Read more of this post

Monitor CPU, POOL utilization from PHYP cycles

It’s important to know a CPU capacity used by a system. In IBM i world, we have a licpgm – 5761PT1 Performance tools. But what if you run other OS’s than IBM i, on the same POWER box. Or you run LPARs in different shared processor pools ? The most efficient might be tracking CPU cycles dispatched by the POWER Hypervisor. In this post I show you, how to interpret performance data collected by a HMC, and how to allow IBM i collects and display dispatched CPU cycles.

Read more of this post

Managing the Virtual Media Repository

Virtual media repository is very useful PowerVM feature. Some older IBM i administrators probably remember similar function available in iSeries ages ago. In short way, it allows to share CD/DVD images on a frame/server layer.

I use it very often, because it allows load a SLIC without physical access to a server. Practically you can install an IBM i OS, on completely new POWER server, which doesn’t even have a physical CD/DVD drive.

In this post I’d like to show different methods how to manage the Virtual Media Repository. Read more of this post

Changing WWPN of a virtual fiber adapter

You’ve probably noticed WWPNs are automatically generated by a HMC.  But you might get to the point when you need specific World Wide Port Name. Each HBA must have an unique number.  That’s why IBM didn’t give us a choice, and generates these strings automatically. First few characters (C050760….) define a virtual resource. The rest of the string is unique.  A serial number of a console is used to generate distinctive identifier. The problem is when you do some maintenance work, and you lost your ‘old’ WWPN, or you need to migrate to a different VIOS. In most situation you can reconfigure your SAN infrastructure. But if you need to keep a WWPN, you can explicitly set it from a HMC command line. Read more of this post