Fujitsu M10-1/M10-4/M10-4S Servers: XSCF Control Package (XCP) Firmware mismatch message appears

Asset ID:	1-72-2135472.1
Update Date:	2017-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 2135472.1 : Fujitsu M10-1/M10-4/M10-4S Servers: XSCF Control Package (XCP) Firmware mismatch message appears

Applies to:

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 M10-4S - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

When logging in to the XSCF, a "XCP version of XSCF and Back-Panel mismatched!" message appears.

Changes

The XSCF Control Package (XCP) Firmware was updated recently.

Cause

The XCP firmware update from 2280 to 2290 had not completed when rebootxscf was run.

Apr 26 11:47:47 hnunxmte01i Event: SCF:XSCF ready <<<=== "bank apply has completed" message is missing
Apr 26 11:36:37 hnunxmte01i Event: SCF:XSCF writing is performed (BBID=0, XSCF version=02290000)
Apr 26 11:36:06 hnunxmte01i Event: SCF:XSCF update is started (BBID=0, bank=1)
Apr 26 11:33:36 hnunxmte01i Event: SCF:XSCF ready
Apr 26 11:27:33 hnunxmte01i Event: SCF:XSCF bank apply has been completed (BBID=0, bank=0, XCP version=2290:last version=2280)
Apr 26 11:27:32 hnunxmte01i Event: SCF:XSCF update has been completed (BBID=0, bank=0)
Apr 26 11:20:21 hnunxmte01i Event: SCF:XSCF writing is performed (BBID=0, XSCF version=02290000)
Apr 26 11:20:00 hnunxmte01i Event: SCF:XSCF update is started (BBID=0, bank=0)
Apr 26 11:18:25 hnunxmte01i Event: SCF:XCP update is started (XCP version=2290:last version=2280)

From the audit logs we see the update of BBID=0, bank 1 was still running when rebootxscf was executed:

header,37,1,login - console,10.87.110.200,2016-04-26 11:18:24.444 +02:00
subject,21,101,normal,bui 60568 10.87.100.34
header,157,1,command - setldapssl,10.87.110.200,2016-04-26 11:27:33.001 +02:00
subject,21,101,normal,bui 60568 10.87.100.34
command,/sp/cli/usr/bin/flashupdate,-q,-y,-c,update,-m,xcp,-s,2290,-f
platform access,granted
text,The XSCF will be reset. Continue? [y|n] : y
return,0

header,37,1,login - console,10.87.110.200,2016-04-26 11:42:07.697 +02:00
subject,16,101,normal,bui 61661 10.87.100.34
header,64,1,command - setdualpowerfeed,10.87.110.200,2016-04-26 11:42:08.531 +02:00
subject,16,101,normal,bui 61661 10.87.100.34
command,rebootxscf,-y,-s
command,rebootxscf,-y,-s
platform access,granted
return,0

Resulting in mixed versions of firmware:

XSCF>version -c xcp -v :
BB#00-XSCF#0 (Master)
XCP0 (Current): 2290
CMU : 02.28.0000
  POST : 3.10.0
  OpenBoot PROM : 4.36.1+2.15.0
  Hypervisor : 1.4.5
XSCF : 02.29.0000
XCP1 (Reserve): 2290
CMU : 02.27.0001
  POST : 3.9.0
  OpenBoot PROM : 4.36.1+2.14.0
  Hypervisor : 1.4.4
XSCF : 02.29.0000
CMU BACKUP
#0: 02.27.0001
#1: 02.28.0000
XSCF>version_-c cmu -v :
PPAR-ID 0: 02.28.0000
  POST : 3.10.0
  OpenBoot PROM : 4.36.1+2.15.0
  Hypervisor : 1.4.5
PSB#00-0: 02.28.0000(Current)
  POST : 3.10.0
  OpenBoot PROM : 4.36.1+2.15.0
  Hypervisor : 1.4.5
PSB#00-0: 02.27.0001(Reserve)
  POST : 3.9.0
  OpenBoot PROM : 4.36.1+2.14.0
  Hypervisor : 1.4.4
XSCF>

Solution

Run flashupdate -c update -m xcp -f -s 2290 . The -f option is needed to force the update to be run, when flashing with the same XCP version again. From the flashupdate(8) manual page:

-f To update the firmware to the specified ver-
sion, it is overwritten even if the same
version has already been written.

May 5 13:16:31 hnunxmte01i Event: SCF:XCP update has been completed (XCP version=2290:last version=2290)
May 5 13:16:30 hnunxmte01i Event: SCF:CMU update has been completed (BBID=0)
May 5 13:14:33 hnunxmte01i Event: SCF:CMU writing is performed (BBID=0, CMU version=02290000)
May 5 13:14:30 hnunxmte01i Event: SCF:CMU update is started (BBID=0)
May 5 13:13:27 hnunxmte01i Event: SCF:CMU update has been completed (BBID=0)
May 5 13:11:27 hnunxmte01i Event: SCF:CMU writing is performed (BBID=0, CMU version=02290000)
May 5 13:11:26 hnunxmte01i Event: SCF:CMU update is started (BBID=0)
May 5 13:10:19 hnunxmte01i Event: SCF:XSCF update has been completed (BBID=0, bank=0)
------------------------------------------------------------------------------------------------------------------- <<== Lines above were missing from previous attempts. 2nd XSCF update completed message, and the CMU updates.
May 5 13:02:35 hnunxmte01i Event: SCF:XSCF writing is performed (BBID=0, XSCF version=02290000)
May 5 13:02:00 hnunxmte01i Event: SCF:XSCF update is started (BBID=0, bank=0)
May 5 12:59:26 hnunxmte01i Event: SCF:XSCF ready
May 5 12:53:00 hnunxmte01i Event: SCF:XSCF bank apply has been completed (BBID=0, bank=1, XCP version=2290:last version=2290)
May 5 12:53:00 hnunxmte01i Event: SCF:XSCF update has been completed (BBID=0, bank=1)
May 5 12:46:00 hnunxmte01i Event: SCF:XSCF writing is performed (BBID=0, XSCF version=02290000)
May 5 12:45:37 hnunxmte01i Event: SCF:XSCF update is started (BBID=0, bank=1)
May 5 12:43:52 hnunxmte01i Event: SCF:XCP update is started (XCP version=2290:last version=2290)

Running with the force option the XCP firmware is confirmed to be correct:

XSCF>version -c xcp -v :
BB#00-XSCF#0 (Master)
XCP0 (Reserve): 2290
CMU : 02.29.0000
  POST : 3.10.0
  OpenBoot PROM : 4.38.1+2.18.0
  Hypervisor : 1.4.6
XSCF : 02.29.0000
XCP1 (Current): 2290
CMU : 02.29.0000
  POST : 3.10.0
  OpenBoot PROM : 4.38.1+2.18.0
  Hypervisor : 1.4.6
XSCF : 02.29.0000
CMU BACKUP
#0: 02.29.0000
#1: 02.28.0000
XSCF>version_-c cmu -v :
PPAR-ID 0: 02.29.0000
  POST : 3.10.0
  OpenBoot PROM : 4.38.1+2.18.0
  Hypervisor : 1.4.6
PSB#00-0: 02.29.0000(Current)
  POST : 3.10.0
  OpenBoot PROM : 4.38.1+2.18.0
  Hypervisor : 1.4.6
PSB#00-0: 02.29.0000(Reserve)
  POST : 3.10.0
  OpenBoot PROM : 4.38.1+2.18.0
  Hypervisor : 1.4.6
XSCF>

Attachments

This solution has no attachment