Skip to main content
  1. Home >
  2. Products >
  3. Computing Products >
  4. Servers >
  5. Fujitsu SPARC servers >
  6. Downloads >
  7. User Manuals >
  8. Fujitsu M10-4/Fujitsu M10-4S/SPARC M10-4/SPARC M10-4S Service Manual >
  9. 9.12 Checking the XCP Firmware Version (Building Block Configuration)

9.12 Checking the XCP Firmware Version (Building Block Configuration)


9.12 Checking the XCP Firmware Version (Building Block Configuration)
This section describes the procedure for checking the XCP firmware version after maintenance work on the CPU memory unit lower.
In a SPARC M10-4S building block configuration, the version must match the XCP version on each chassis.
  1. Log in to the XSCF, and confirm that the XCP firmware version is the same as before replacement of the CPU memory unit lower.
  1. If the XCP firmware version is different between the maintenance part and the existing system, the message "XSCF firmware update now in progress. BB#xx, please wait for XSCF firmware update complete." appears at login to the XSCF. Then, the XCP firmware version will be automatically matched.
Password: *****
XSCF firmware update now in progress. BB#00,
please wait for XSCF firmware update complete.
XSCF>
  1. The version matching takes about 50 minutes.
    If the above message appears, execute the showlogs monitor, and check for the "XCP firmware version synchronization completed" message. The message indicates the completion of XCP firmware matching. Then, perform the work below.
XSCF> showlogs monitor
Jul 7 14:51:43 SPARCM10 Event: SCF:XCP firmware version synchronization started
Jul 7 14:51:43 SPARCM10 Event: SCF:XSCF firmware update is started (BB#00)
Jul 7 14:51:43 SPARCM10 Information:/BB#00/CMUL:SCF:SCF Diagnosis initialize RTC (*1)
Jul 7 14:51:43 SPARCM10 Alarm: :SCF:Gaps between BB-ID (*2)
Jul 7 14:51:44 SPARCM10 Event: SCF:XSCF ready
Jul 7 15:28:25 SPARCM10 Event: SCF:Standby XSCF Ready(BB#00)
 :
Jul 7 15:40:17 SPARCM10 Event: SCF:XSCF update has been completed (BBID=0, bank=0)
Jul 7 15:40:18 SPARCM10 Event: SCF:XCP update has been completed (XCP version=2362:last version=2360)
Jul 7 15:40:18 SPARCM10 Event: SCF:XSCF firmware update has been completed (BB#00)
Jul 7 15:40:18 SPARCM10 Event: SCF:XCP firmware version synchronization completed
*1 If the "SCF:SCF Diagnosis initialize RTC" message appears, ignore the message.
*2 If the "SCF:Gaps between BB-ID" message appears, ignore the message.
  1. Execute the version command to check the firmware version on all SPARC M10-4S units.
  1. The versions of all the XCP firmware are displayed.
    In a building block configuration, you can check the Master/Standby versions.
    Confirm that the XCP firmware version on each SPARC M10-4S unit is the same as the master XSCF version.
    If they are the same, steps 3 and later are not necessary. If they are not the same, perform steps 3 and later.
XSCF> version -c xcp
BB#00-XSCF#0 (Master)
XCP0 (Current): xxxx
XCP1 (Reserve): xxxx
BB#01-XSCF#0 (Standby)
XCP0 (Current): xxxx
XCP1 (Reserve): xxxx
BB#02-XSCF#0
XCP0 (Current): xxxx
XCP1 (Reserve): xxxx
BB#03-XSCF#0
XCP0 (Reserve): xxxx
XCP1 (Current): xxxx
  1. If the XCP firmware version is not the same, execute the getflashimage -l command to check  whether the XCP image file of the version before replacement of the CPU memory unit lower is saved on the master XSCF.
  1. If not saved, import the XCP image file.
    The following example imports the XCP image file of the version before XSCFU replacement.
XSCF> getflashimage -l
Existing versions:
        Version                 Size  Date
        BBXCP2360.tar.gz   107690100  Wed Sep 08 11:09:52 JST 2021
XSCF> getflashimage file:///media/usb_msd/xxxx/BBXCP2362.tar.gz
  1. Execute the flashupdate -c sync command to match the XCP firmware version on each SPARC M10-4S unit.
  1. The XCP firmware version will be matched to the master XSCF version.
XSCF> flashupdate -c sync
XCP update is started. [3600sec]
  0..... 30..... 60..... 90.....120.....150.....180.....210.....240.....
270.....300.....330.....360.....390.....420.....450.....480.....510.....
  1. Execute the showlogs monitor command, and check for the "XCP update has been completed" message. The displayed message indicates the completion of the XCP firmware update.
XSCF> showlogs monitor
Sep 8 13:39:31 SPARCM10 Event: SCF:XCP update is started (XCP version=2362:last version=2362)
Sep 8 13:41:55 SPARCM10 Event: SCF:Updating XCP:Preparing to update XSCF (BBID=1, bank=1)
Sep 8 13:42:20 SPARCM10 Event: SCF:Updating XCP:Updating XSCF (BBID=1, XSCF version=02360002)
Sep 8 13:46:35 SPARCM10 Event: SCF:Updating XCP:XSCF updated (BBID=1, bank=1)
Sep 8 13:46:35 SPARCM10 Event: SCF:Updating XCP:XSCF bank has changed (BBID=1, bank=1, XCP version=2362:last version=2360)
Sep 8 13:52:32 SPARCM10 Event: SCF:Standby XSCF Ready(BB#01)
Sep 8 13:53:16 SPARCM10 Event: SCF:Updating XCP:Preparing to update XSCF (BBID=1, bank=0)
Sep 8 13:53:39 SPARCM10 Event: SCF:Updating XCP:Updating XSCF (BBID=1, XSCF version=02360002)
Sep 8 13:57:35 SPARCM10 Event: SCF:Updating XCP:XSCF updated (BBID=1, bank=0)
Sep 8 13:58:22 SPARCM10 Event: SCF:Updating XCP:Preparing to update CMU (BBID=1)
Sep 8 13:58:24 SPARCM10 Event: SCF:Updating XCP:Updating CMU (BBID=1, CMU version=02360002)
Sep 8 14:02:34 SPARCM10 Event: SCF:Updating XCP:CMU updated (BBID=1)
Sep 8 14:03:16 SPARCM10 Event: SCF:XCP update has been completed (XCP version=2362:last version=2362)
  1. Execute the version command, and confirm that the XCP firmware version on each SPARC M10-4S is correct.
XSCF> version -c xcp
BB#00-XSCF#0 (Master)
XCP0 (Current): xxxx
XCP1 (Reserve): xxxx
BB#01-XSCF#0 (Standby)
XCP0 (Current): xxxx
XCP1 (Reserve): xxxx
BB#02-XSCF#0
XCP0 (Current): xxxx
XCP1 (Reserve): xxxx
BB#03-XSCF#0
XCP0 (Reserve): xxxx
XCP1 (Current): xxxx