DLPAR issues with cloned AIX LPAR
meyawi 270002D6NU Comments (7) Visits (15441)
Recently, I was installing a POWER7 P770 for one of my customers. But instead of installing VIO servers from scratch, we made clones on the storage subsystem (HP 3PAR) from VIOS previously installed on another P770. In one hand, it had the benefit of being a fast method avoiding us to install and configure the Operating Systems, 3PAR multipathing drivers, customer tools; but in the other hand, we have to correct some settings and do some clean-up operations (hostname, devices…).
My customer often uses this method to clone LPAR (AIX/VIO) and as expected DLPAR operations won’t work. Even if my customer usually knows how to correct that, this time had been more tricky because of CAA (Cluster Aware AIX, from AIX 6.1 TL6 & 7.1).
I reproduced this issue with 2 LPARs (AIX 7.1 SP3), but this time the second LPAR was cloned from first one’s rootvg using alt_disk_copy command by moving SAN LUN from one LPAR to the other.
On both partitions, we couldn’t do DLPAR operations :
Only one LPAR is visible from HMC and if we look attentively, IP address is not corresponding to LPAR n°5 and Dcaps value indicates that there is a problem :
hscroot@HMC:~> lspartition -dlpar | grep -A 1 "<" <#6> Part
0 - DR CPU capable (can move CPUs)
1 - DR MEM capable (can move memory)
2 - DR I/O capable (can move I/O resources)
3 - DR PCI Bridge (can move PCI bridges)
4 - DR Entitlement (POWER 5 can change shared entitlement)
5 - Multiple DR CPU (AIX 5.3 can move 2+ CPUs at once)
0x3f = max, and 0xf is common for AIX 5.2
Even after executing this commands on meyawi-clone, it is not possible to do DLPAR.
We will execute this operations on cloned LPAR : meyawi-clone
Then it is necessary to clear node ID :
Generate a new node ID :
Then after a few minutes, we should be able to do DLPAR operations, it is possible to verify DLPAR status threw HMC :
hscroot@HMC:~> lspartition -dlpar | grep -A 1 "<" <#0> Part