Fujitsu M10-1/M10-4/M10-4S/M12-1/M12-2/M12-2S Servers: CoD in general and issue 'poweron': Not powering on : Poweron canceled due to missing component.

Asset ID:	1-72-1591393.1
Update Date:	2018-05-09
Keywords:

Solution Type Problem Resolution Sure

Solution 1591393.1 : Fujitsu M10-1/M10-4/M10-4S/M12-1/M12-2/M12-2S Servers: CoD in general and issue 'poweron': Not powering on : Poweron canceled due to missing component.

Applies to:

Fujitsu SPARC M12-2S - Version All Versions to All Versions [Release All Releases]
Fujitsu M10-1 - Version All Versions to All Versions [Release All Releases]
Fujitsu M10-4 - Version All Versions to All Versions [Release All Releases]
Fujitsu SPARC M12-2 - Version All Versions to All Versions [Release All Releases]
Fujitsu M10-4S - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Powering on a physical partiton (PPAR) on a SPARC M10 or M12 system might fail with the following information.

   XSCF> poweron -a
   PPAR-IDs to power on :00
   Continue? [y|n] :y
   00 : Not powering on : Poweron canceled due to missing component.

   XSCF> showlogs monitor ==>
   Oct 11 10:20:47 <hostname> Information: /PPAR#0:SCF:PPAR shortage(No Cod License)

   XSCF> showlogs error ==>
   Date: Oct 11 10:20:47 PDT 2013
      Code: 10000000-00faff0000ff0000ff-018a00400000000000000000
      Status: Information            Occurred: Oct 11 10:20:47.642 PDT 2013
      FRU: /PPAR#0
      Msg: PPAR shortage(No Cod License)

Changes

Cause

There are no CPU cores activated. CPU cores must be activated in order to use CPU resources in SPARC M10 and M12 Systems.

The Capacity on Demand (CoD) function is to allow purchases of server-dedicated CPU resources. For SPARC M10 and M12 Systems
CPU resources need to be purchased for one or more CPUs before the server is put into operation. A purchase gives the
right to activate CPU cores. This right is called a "permit", and it provides a permanent right to use a CPU core.
One set of permits is used to activate two CPU cores.

Solution

Before 'poweron' a PPAR one need to allocate CoD resource(s) to the designated PPAR. The following is a short example
to activate CoD resources for all CPU cores on a SPARC M10-4 System and to allocate them to PPAR 0. In this case it is
a 2-socket configuration, i.e. CMUL is the only assembled CMU. There is no CMUU.

   XSCF> addcodactivation <copy'n'paste first key-signature>
   XSCF> <repeat previous step for any other single key-signature>
   XSCF> setcod -p 0 -s cpu 32

Finally you are able to do a 'poweron -p 0'
Use 'showcodactivation' and 'showcodusage' to get an overview about the CoD configuration.

   XSCF> showcodactivation
   Index   Description Count
   ------- ----------- ------
         0 PROC            2
         1 PROC            2
           [...]
        15 PROC            2

   XSCF> showcodusage
   Resource In Use Installed CoD Permitted Status
   -------- ------ --------- ------------- ------
   PROC         32        32            32 OK: 0 cores available
   PPAR-ID/Resource In Use Installed Assigned
   ---------------- ------ --------- --------------
   0 - PROC            32        32       32 cores
   1 - PROC             0         0        0 cores
        [...]
   15 - PROC             0         0        0 cores
   Unused - PROC         0         0        0 cores

Btw: Apply 'showcodactivation -v' to see the used CPU Activation key-signature stored in the XSCF. This verbose output
is not collected by the snapshot command.

   <XCP2221 snapshot root dir> $ ls -1 */*cod*
   xscf_command/@sp@cli@usr@bin@showcod_-v.out
   xscf_command/@sp@cli@usr@bin@showcodactivation.out
   xscf_command/@sp@cli@usr@bin@showcodactivationhistory.out
   xscf_command/@sp@cli@usr@bin@showcodusage_-v_-p_all.out

For backup and restore purposes you might use 'dumpcodactivation' and 'restorecodactivation'. The latter one requires
the PPARs to be powered off. The target/source directory as shown next will be the user's HOME. In this example it is
/export/home/jack/

   XSCF> showcodactivation -v
   Index   Description Count
   ------- ----------- ------
         0 PROC            2
   Product: SPARC M10-4
   SequenceNumber: 2469
   Cpu: noExpiration 2
   Text-Signature-SHA256-RSA2048:
   LASjJGsXegSXDKvQZNHrV7+9lI4XTWNS1kSPxHApufGgi4LEIES04JNIycoyRVC0
   moM51QeG5dxfS1xXzcjnQbdLbcegs8geJYzV7JRXNKDVOR1X0UIN36za0HzQ93Ds
   NuiVWj/grR5+LtO64ZOs7+7dCk5KX8vYnOaEb+DTu7THkVw4se0LqsGV7s6+ZwK5
   f5DPWA52KttNSY32gQOJcmiWRVDecIjEJLuROh4LF4weY6euYjkomLLc2j/wAjms
   ShW3MkCNCNQZW8i0JXfEgY9e/Z6bxJqzii1lRuTbMxKWq+izu3GXOHXp/IGrvIbU
   6Lh5yLI3Cck1OCbSZoyj2A==
   ------- ----------- ------
         1 PROC            2
   Product: SPARC M10-4
   [...]

   XSCF> dumpcodactivation -u jack ftp://192.168.100.5/codkey.m10-4.2111203001.dump
   Password:
   operation completed
   XSCF>

   XSCF> restorecodactivation -u jack ftp://192.168.100.5/codkey.m10-4.2111203001.dump
   Password:
   *** The CPU core Activation keys are overwritten in the backup data.
   *** Do you want to restore this keys to your system? [y/n]:y
   operation completed
   XSCF>

To obtain replacement CPU Activation Keys please see the Fujitsu M10 Systems Getting Started Guide or the Fujitsu M12 Systems Getting Started Guide.

For more details about CoD resource purchases, see...

   Fujitsu <M10-1|M10-4|M10-4S> User Manuals @ Fujitsu M10 Series Server Documentation
   or Fujitsu <M12-1|M12-2|M12-2S> User Manuals @ Fujitsu M12 Series Server Documentation
   both covering...
   Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide
   Chapter 5 - CPU Activation

For CoD recovery purposes see also document 1640230.1 (Fujitsu M10-1/M10-4/M10-4S: Obtaining Replacement COD Licenses).

Attachments

This solution has no attachment