Fujitsu SPARC M12-1/M12-2/M12-2S, Fujitsu M10-1/M10-4/M10-4S COD CPU Activation Key fails

Asset ID:	1-72-1599957.1
Update Date:	2017-12-07
Keywords:

Solution Type Problem Resolution Sure

Solution 1599957.1 : Fujitsu SPARC M12-1/M12-2/M12-2S, Fujitsu M10-1/M10-4/M10-4S COD CPU Activation Key fails

Applies to:

Fujitsu M10-4 - Version All Versions and later
Fujitsu M10-1 - Version All Versions and later
Fujitsu M10-4S - Version All Versions and later
Fujitsu SPARC M12-1 - Version All Versions and later
Fujitsu SPARC M12-2 - Version All Versions and later
Information in this document applies to any platform.

Symptoms

When adding a COD activation key the system responds with message:

successfully added Activation Key count : 0.
failed Activation Key count : 16.

addcodactivation: CoD Permit is not valid

Cause

This issue has been seen after the replacement of both the psubp and mbu ( M10-1 ) or psubp and cmul ( M10-4S ).

Note: Replacing both of these parts at the same time will cause the complete loss of all configuration and setup information on the xscfu.

Solution

This issue will require a support engineer to fix the issue.

Please contact your Authorized Service Provider for assistance in recovering from this problem.

Internal TSC Process

Gather the following information:

System serial # from showhardconf
XCP version from "version -c xcp"
The date on the XSCFU from "showdate -u"

Once the above information is collected engage a Senior Level2 engineer to create an escalation mode password.

Check that the brandid is incorrectly set to "0".

escalation# brandid
REMCS : off
SvcTag : off
brandid : 0
display : 0

Set the correct value to "1".

escalation# brandid -s brandid=1

Powercycle the platform.

Double check that brandid was set.

escalation# brandid
REMCS : off
SvcTag : off
brandid : 1
display : 1

You should now be able to update the COD Activation Keys.

The above can also occur when brandid is incorrectly set to "0" for any other reason:

XSCF> addcodactivation "Product: SPARC M10-4
> SequenceNumber: 22781
piration 2
Text-Signature-SHA256-RSA2048:
AoXglLF65HUwDTrycO8PoUvY+/LJTb1PG> Cpu: noExpiration 2
uBkII1JuL/l5YBxDORR7GLlPuHnfa/yEMd5C7EmYyS45Gun+xaJlnXMz4vODL
RuaMBn8ZgXCptJ1f> Text-Signature-SHA256-RSA2048:
zwcc0a9
WzkrFrpClhTL+bgisfeIIUHPuXlIchw7KgVL6CU0jjAlDEybnJiVmtnQHhbPLUMd
jfr> AoXglLF65HUwDTrycO8PoUvY+/LJTb1PGb9PqKiAiHojUPzDeNKk+orOr28yHhwp
> qf+uBkII1JuL/l5YBxDORR7GLlPuHnfa/yEMd5C7EmYyS45Gun+xaJlnXMz4vODL
> RuaMBn8ZgXCptJ1fbXDkiCsvZS1aEb42tuK9NrIbfVQM8mOR5o7pdXjnxzwcc0a9
> WzkrFrpClhTL+bgisfeIIUHPuXlIchw7KgVL6CU0jjAlDEybnJiVmtnQHhbPLUMd
> jfraHBifR0kM13dfnLYlvJ1StT7UQQX6ykrVRBp2mIw5NsGQHgEDi3lS70WoSKAF
> nHGkURQxSpN92qrr8KlrBw=="
Above Key will be added, Continue?[y|n]:y
addcodactivation: CoD Permit is not valid

XSCF> showcodusage
Resource In Use Installed CoD Permitted Status
-------- ------ --------- ------------- ------
PROC 0 32 0 OK: 0 cores available

XSCF> version -c xcp
BB#00-XSCF#0 (Master)
XCP0 (Current): 2231
XCP1 (Reserve): 2231

REMCS : off
SvcTag : off
brandid : 0 <<<<<<<<<<<<<<
display : 0

The same license code installation works after having set brandid to 1

Attachments

This solution has no attachment