NIM operations don’t work after a Live Partition Mobility? Update your NIM client’s CPU_ID !

Using Live partition mobilty is a real pain reliever when you need to get some downtime, in order to upgrade your pseries’ firmware , for example . (if you’re not familiar with LPM migration , here is a visual example,

Share Button

LPM migration failed with reference code 2005 (lpar hung up)

Context I had a problem once which caused the crash of a migrating LPAR, because of a SCSI reserve on my rootvg (rootvg’s hdisk should be ALWAYS set with the no_reserve attribute for LPM, wether they are  managed by MPIO,

Share Button

vasistat command and LPM

The Gui on HMC/SDMC is not the best and most accurate way to check the progress of an LPAR live migration (sometimes you just jump from 0% to 76% with no explaination) The best way is to eavesdrop the vasi0

Share Button

Can’t achieve concurrent live partition migrations ? Check your max_virtual_slots value !

Context Here are my latest discoveries about concurrent LPM : We had at work a situation where we could not perform concurrent live partition migration between our two p795, however or whatever we tried (multiple HMC/SDMC, multiple MSPs, cross-site migrations…),

Share Button

HDLM : change the default reserve policy on all disks

In order to get LPM to work properly, we need to put the no_reserve attribute to all disks (here we have the hitachi disk example) : We can check the new default parameter :

Share Button

Live partition mobility CLI commands

perform a validation : perform a migration :  virtual_fc_mappings: Comma-separated list of virtual fibre channel adapters. Each item in this list has the format slot_num/vios_lpar_name/vios_lpar_id. For example, 4/vios2/3 specifies a virtual fibre channel adapter on a client logical partition with

Share Button

How to ease up HMC’s lsysscfg output when you have many virtual adapters and you want to know if you’re LPM compatible

It can be a nightmare when you need to create a script listing easily and quickly some of the informations given by lssyscfg commande. Unfortunately, IBM didn’t really think about us, because what you get is this : OK, that’s

Share Button