28 Hardware Management Console (HMC) Case Configuration Study for LPAR Management
Cpu2 0 0 756 740 700 8 100 19 100 0 0 0 0.42 2683
Cpu3 0 0 702 703 699 8 100 2 100 0 0 0 0.41 2652
In Example 13 and Example 14 the physc parameter has different values for the
two nodes.
Example 14 Output of topas -L on node julia
Interval: 7 Logical Partition: julia Tue Mar 31 17:49:57 1970
Psize: 3 Shared SMT OFF Online Memory: 512.0
Ent: 1.00 Mode: UnCapped Online Logical CPUs: 4
Partition CPU Utilization Online Virtual CPUs: 4
%usr %sys %wait %idle physc %entc %lbusy app vcsw phint %hypv hcalls
100 0 0 0 1.3 132.73100.00 0.00 6701 6 0.0 0
===============================================================================
LCPU minpf majpf intr csw icsw runq lpa scalls usr sys _wt idl pc lcsw
Cpu0 0 0 731 813 726 7 100 31 100 0 0 0 0.33 1683
Cpu1 0 0 1490 791 729 8 100 29 100 0 0 0 0.33 1634
Cpu2 0 0 765 765 704 8 100 18 100 0 0 0 0.33 1697
Cpu3 0 0 713 711 696 9 100 307 100 0 0 0 0.33 1687
Node oli and node julia have 1.0 processor units entitled and 100% CPU usage.
The shared processor pool has 3.0 units, so the idle capacity is 1.0 unit shared
by partitions julia and oli, proportionally to their weight. In our case, partition oli
adds 255/(255+128) from 1.0 processing units, while partition julia adds
128/(255+128) processing units.
Automating HMC tasks
In this section, we describe an example of using the HMC scheduler to perform a
dynamic LPAR operation. The example uses 2 partitions in shared mode on a
system with 4 CPUs and 8 GB of RAM. Our partitions’ configuration is described
in Table 8.
Table 8 CPU and memory allocation table
Partition
name
Memory
(GB)
CPU
(Min/Des/Max)
Virtual
processors
(Min/Des/Max)
Dedicate/
Shared
Capped/
Uncapped
oli 1/5/8 0.1/3.0/4.0 1/4/4 Shared Uncapped
julia 1/2/8 0.1/1.0/4.0 1/4/4 Shared Uncapped