Understanding HP Instant Capacity (iCAP) version 6.x and 7.x Codewords Whitepaper

System contact e-mail: Not set
From e-mail: Set to the default ('adm')
Asset reporting: on
Exception status: No exception
Local Hard Partition Information
--------------------------------
Total processors: 8
Intended Active processors: 6
Active processors: 6
Licensed processors that can be activated: 0
Processors that can be activated if licensed: 2
Processors that cannot immediately be activated: 0
Global iCOD Information
-----------------------
iCOD cells: 0
Actual inactive cells: 0
iCOD processors: 2
Actual inactive processors: 2
iCOD Memory: 0.0 GB
Actual inactive Memory: 0.0 GB
Processors using temporary capacity: 0
Temporary capacity available: 29 days, 22 hours, 30
minutes
Projected temporary capacity expiration: N/A
Allocation of iCOD Resources Among Partitions
-------------------------------------------------------------
nPar Inactive Inactive Inactive
ID Cells Memory CPUs nPar Name
==== ======== =========== ======== ======================
0 0 0.0 GB 2 Partition 0 (local)
N/A 0 0.0 GB 0 Unassigned Cells
iCOD Partition Configuration Information
-----------------------------------------------------------------
Intended Actual Compatible
nPar Active Active Total Software
ID CPUs CPUs CPUs Installed nPar Name
==== ======== ====== ===== ========== ======================
0 6 6 8 Yes Partition 0 (local)
Applying an RTU codeword
This example shows the permanent activation of a core. An RTU codeword is applied to the system.
As mentioned in the note from icod_modify (below), no core is automatically activated when the
codeword is applied. The icod_modify command must be used to activate a core. (You may
activate any previously inactive core in any partition and it will use the newly available usage rights.)
Apply the RTU codeword
# icod_modify –C xX603sM.jFCUNVY.WWMkzyg.qWHn7rv-
qb2nz12.dHJR0gU.hnkzLrj.wfF5PX7
The following valid codeword has been applied to the complex:
Right-to-Use Codeword
1 CPUs
17