Skip to main content
  1. Home >
  2. Products >
  3. Computing Products >
  4. Servers >
  5. Fujitsu SPARC servers >
  6. Downloads >
  7. User Manuals >
  8. Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide >
  9. 16.5.2 Updating XCP on a Building Block Configuration System With Multiple XSCFs

16.5.2 Updating XCP on a Building Block Configuration System With Multiple XSCFs


16.5.2 Updating XCP on a Building Block Configuration System With Multiple XSCFs
  1. Log in to the master XSCF.
  2. Execute the showhardconf command, and confirm that Status is Normal for both the master XSCF and standby XSCF.
  1. The following shows examples of the SPARC M10-4S.
XSCF> showhardconf
SPARC M10-4S;
+ Serial:2081230011; Operator_Panel_Switch:Locked;
+ System_Power:Off; System_Phase:Cabinet Power Off;
Partition#0 PPAR_Status:Powered Off;
Partition#1 PPAR_Status:Powered Off;
BB#00 Status:Normal; Role:Master; Ver:2003h; Serial:2081231002;
+ FRU-Part-Number:CA07361-D202 A1
:
BB#01 Status:Normal; Role:Standby Ver:0101h; Serial:7867000297;
+ FRU-Part-Number:CA20393-B50X A2 ;
  1. Execute the version command to check the version of the firmware in operation.
XSCF> version -c xcp -v
BB#00-XSCF#0 (Master)
XCP0 (Current): 2041
CMU           : 02.04.0001
    POST          : 1.42.0
    OpenBoot PROM : 4.34.0+1.16.0
    Hypervisor    : 0.26.9
XSCF          : 02.04.0001
XCP1 (Reserve): 2041
CMU           : 02.04.0001
    POST          : 1.42.0
    OpenBoot PROM : 4.34.0+1.16.0
    Hypervisor    : 0.26.9
XSCF          : 02.04.0001
BB#01-XSCF#0 (Standby)
XCP0 (Reserve): 2041
CMU           : 02.04.0001
    POST          : 1.42.0
    OpenBoot PROM : 4.34.0+1.16.0
    Hypervisor    : 0.26.9
XSCF          : 02.04.0001
XCP1 (Current): 2041
CMU           : 02.04.0001
    POST          : 1.42.0
    OpenBoot PROM : 4.34.0+1.16.0
    Hypervisor    : 0.26.9
XSCF          : 02.04.0001
CMU BACKUP
#0: 02.04.0001
#1: ..
  1. For the SPARC M12-2S, there is no reserve bank of the CMU firmware. The following shows a display example.
XSCF# version -c xcp -v
BB#00-XSCF#0 (Standby)
XCP0 (Reserve): 3010
XSCF          : 03.01.0000
XCP1 (Current): 3010
XSCF          : 03.01.0000
CMU           : 03.01.0000
    POST          :
    OpenBoot PROM :
    Hypervisor    :
BB#01-XSCF#0 (Master)
XCP0 (Reserve): 3010
XSCF          : 03.01.0000
XCP1 (Current): 3010
XSCF          : 03.01.0000
CMU           : 03.01.0000
    POST          :
    OpenBoot PROM :
    Hypervisor    :
CMU BACKUP
#0: 03.01.0000
#1: ..
XSCF#
  1. Execute the getflashimage command to import the XCP image file.
    The following example imports the XSCF image file from a USB device connected to a USB port (where "MAINTENANCE ONLY" is printed) on the XSCF unit panel (rear panel) of the master XSCF. 
XSCF> getflashimage file:///media/usb_msd/xxxx/BBXCP2044.tar.gz
Existing versions:
        Version                 Size  Date
        BBXCP2041.tar.gz    90004045  Tue Apr 09 04:40:12 JST 2013
Mounted USB device
0MB received
1MB received
...

44MB received
45MB received
Download successful: 46827 Kbytes in 109 secs (430.094 Kbytes/sec)
Checking file...
MD5: e619e6dd367c888507427e58cdb8e0a4
XSCF>
  1. XCP image file importing is completed when the normal end messages "Download successful: ..." and "MD5: ..." appear.
Note - If the following error occurs during XCP import, there may be a problem with the XCP file: "Error: File is invalid or corrupt." Check the XCP file.
The possible cause, for example, is that an unauthorized XCP image file was obtained or that the XCP image file downloaded by the customer was subsequently changed through unauthorized access. In such cases, obtain the correct XCP image file and import XCP again.
Note - If a message such as "An internal error has occurred" or "Error: insufficient free space" appears during XCP import, an XSCF firmware error or parts failure may have occurred. In this case, see "16.8  Trouble During Firmware Update" and solve the problem.
  1. Use the getflashimage -l command to check the version of the imported XCP image file.
XSCF> getflashimage -l
Existing versions:
        Version                 Size  Date
        BBXCP2044.tar.gz    90005045  Wed May 29 09:11:40 JST 2013
  1. Execute the flashupdate -c check command to check whether the imported XCP image file can be used for the update.
    Immediately after executing the flashupdate command, execute the showresult command. If the returned end value is 0, you can use the file for the update. 
XSCF> flashupdate -c check -m xcp -s 2044
XSCF> showresult
0
XSCF>
  1. Execute the flashupdate command to update the firmware.
Note - The update takes about 60 minutes.
Note - To safely update the firmware, do not perform power operations for physical partitions and do not reboot the XSCF during the work (steps 7 to 11). For details, see "16.2.1  Notes on Update."
Note - If a message such as "An internal error has occurred" or "Internal error" appears during firmware update, an XSCF firmware error or parts failure may have occurred. In this case, see "16.8  Trouble During Firmware Update" and solve the problem.
XSCF> flashupdate -c update -m xcp -s 2044
The XSCF will be reset. Continue? [y|n] :y
XCP update is started. [3600sec]
  0..... 30..... 60..... 90.....120.....150.....180.....210.....240.....-
270.....300.....330.....360.....390.....420.....450.....480.....510.....|

540.....570.....600.....630.....660.....690.....720.....750.....780.....-

810.....840.....870.....900.....930

:
  1. Here, the XSCF is rebooted, the XSCF session is disconnected.
    At this point in time, the XCP firmware update is not yet complete.
  2. Connect to the master XSCF again.
    Immediately after the XSCF reboot, the states of the master and standby XSCFs are reversed from their original states. For example, when the firmware update is executed with BB-ID number 0 on master XSCF, reconnecting to XSCF will change the status of BB-ID number 1 to master and BB-ID number 0 to standby. In this example, the master XSCF (BB-ID 1) is connected.
Note - For customers who have set the takeover IP address, the machines are automatically connected to the master XSCF when connected using the takeover IP address.
  1. Execute the showbbstatus command, and confirm that you are logged in to the master XSCF. If you are logged in to the standby XSCF, reconnect to the master XSCF.
Note - If the firmware is updated to version XCP 2050 or later, when the XCP firmware update is completed, the switched master/standby XSCF will return to the original state. In such cases, connect to the master XSCF again because the XSCF is rebooted and the XSCF session is disconnected.
XSCF> showbbstatus
BB#01 (Master)
  1. Execute the showlogs monitor command to check the completion of the XCP firmware update.
XSCF> showlogs monitor
May 29 09:38:05 M10-4S-0 Event: SCF:XCP update is started (XCP version=2044:last version=2041)
May 29 09:40:31 M10-4S-0 Event: SCF:XSCF update is started (BBID=0, bank=0)
May 29 09:40:46 M10-4S-0 Event: SCF:XSCF update is started (BBID=1, bank=0)
May 29 09:41:03 M10-4S-0 Event: SCF:XSCF writing is performed (BBID=0, XSCF version=02040004)
May 29 09:41:12 M10-4S-0 Event: SCF:XSCF writing is performed (BBID=1, XSCF version=02040004)
May 29 09:48:18 M10-4S-0 Event: SCF:XSCF update has been completed (BBID=0, bank=0)
May 29 09:50:39 M10-4S-0 Event: SCF:XSCF update has been completed (BBID=1, bank=0)
May 29 09:50:41 M10-4S-0 Event: SCF:XSCF bank apply has been completed (BBID=1, bank=0, XCP version=2044:last version=2041)
May 29 10:01:50 M10-4S-0 Event: SCF:XSCF bank apply has been completed (BBID=0, bank=0, XCP version=2044:last version=2041)
May 29 10:01:51 M10-4S-0 Event: SCF:Change Master Start(BB#01)
May 29 10:03:26 M10-4S-1 Event: SCF:Change Master Complete(BB#01)
May 29 10:05:00 M10-4S-1 Event: SCF:Standby XSCF Ready (BBID#00)
May 29 10:12:56 M10-4S-1 Event: SCF:XSCF update is started (BBID=1, bank=1)
May 29 10:13:23 M10-4S-1 Event: SCF:XSCF update is started (BBID=0, bank=1)
May 29 10:13:24 M10-4S-1 Event: SCF:XSCF writing is performed (BBID=0, XSCF version=02040004)
May 29 10:13:42 M10-4S-1 Event: SCF:XSCF writing is performed (BBID=1, XSCF version=02040004)
May 29 10:20:22 M10-4S-1 Event: SCF:XSCF update has been completed (BBID=0, bank=1)
May 29 10:23:34 M10-4S-1 Event: SCF:XSCF update has been completed (BBID=1, bank=1)
May 29 10:24:42 M10-4S-1 Event: SCF:CMU update is started (BBID=0)
May 29 10:24:58 M10-4S-1 Event: SCF:CMU writing is performed (BBID=0, CMU version=02040004)
May 29 10:25:44 M10-4S-1 Event: SCF:CMU update is started (BBID=1)
May 29 10:25:46 M10-4S-1 Event: SCF:CMU writing is performed (BBID=1, CMU version=02040004)
May 29 10:26:44 M10-4S-1 Event: SCF:CMU update has been completed (BBID=0)
May 29 10:27:51 M10-4S-1 Event: SCF:CMU update has been completed (BBID=1)
May 29 10:29:30 M10-4S-1 Event: SCF:CMU update is started (BBID=0)
May 29 10:29:36 M10-4S-1 Event: SCF:CMU writing is performed (BBID=0, CMU version=02040004)
May 29 10:29:45 M10-4S-1 Event: SCF:CMU update is started (BBID=1)
May 29 10:30:04 M10-4S-1 Event: SCF:CMU writing is performed (BBID=1, CMU version=02040004)
May 29 10:31:18 M10-4S-1 Event: SCF:CMU update has been completed (BBID=0)
May 29 10:31:51 M10-4S-1 Event: SCF:CMU update has been completed (BBID=1)
May 29 10:32:38 M10-4S-1 Event: SCF:XCP update has been completed (XCP version=2044:last version=2041)
May 29 10:32:39 M10-4S-1 Event: SCF:This XSCF will be switched back to standby mode after completion of firmware update
May 29 10:32:39 M10-4S-1 Event: SCF:Change Master Start(BB#00)
May 29 10:33:29 M10-4S-1 Event: SCF:Change Master Complete(BB#00)
May 29 10:42:29 M10-4S-1 Event: SCF:Standby XSCF Ready (BBID#01) 
  1. The following example displays messages on the SPARC M12-2S.
XSCF> showlogs monitor
Apr  5 06:51:06 M12-2S-1 Event: SCF:XCP update is started (XCP version=3010:last version=3009)
Apr  5 07:01:41 M12-2S-1 Event: SCF:Updating XCP:Preparing to update XSCF (BBID=1, bank=1)
Apr  5 07:03:46 M12-2S-1 Event: SCF:Updating XCP:Updating XSCF (BBID=1, XSCF version=03010000)
Apr  5 07:03:54 M12-2S-1 Event: SCF:Updating XCP:XSCF updated (BBID=1, bank=1)
Apr  5 07:06:58 M12-2S-1 Event: SCF:Updating XCP:Preparing to update XSCF (BBID=0, bank=0)
Apr  5 07:09:22 M12-2S-1 Event: SCF:Updating XCP:Updating XSCF (BBID=0, XSCF version=03010000)  
Apr  5 07:10:39 M12-2S-1 Event: SCF:Updating XCP:XSCF updated (BBID=0, bank=0)
Apr  5 07:12:50 M12-2S-1 Event: SCF:Updating XCP:XSCF bank has changed (BBID=1, bank=1, XCP version=3010:last version=3009)
Apr  5 07:20:06 M12-2S-1 Event: SCF:Updating XCP:XSCF bank has changed (BBID=0, bank=0, XCP version=3010:last version=3009)
Apr  5 07:21:27 M12-2S-1 Event: SCF:Change Master Start(BB#01)
Apr  5 07:22:28 M12-2S-2 Event: SCF:Standby XSCF Ready(BB#01)      
Apr  5 07:24:05 M12-2S-2 Event: SCF:Change Master Complete(BB#01)
Apr  5 07:30:08 M12-2S-2 Event: SCF:Updating XCP:Preparing to update XSCF (BBID=1, bank=0)
Apr  5 07:30:35 M12-2S-2 Event: SCF:Updating XCP:Preparing to update XSCF (BBID=0, bank=0)
Apr  5 07:34:41 M12-2S-2 Event: SCF:Standby XSCF Ready(BB#00)
Apr  5 07:35:21 M12-2S-2 Event: SCF:Updating XCP:Updating XSCF (BBID=0, XSCF version=03010000) 
Apr  5 07:40:32 M12-2S-2 Event: SCF:Updating XCP:XSCF updated (BBID=0, bank=1)
Apr  5 07:40:39 M12-2S-2 Event: SCF:Updating XCP:Updating XSCF (BBID=1, XSCF version=03010000)  
Apr  5 07:45:49 M12-2S-2 Event: SCF:Updating XCP:XSCF updated (BBID=1, bank=0)
Apr  5 07:46:18 M12-2S-2 Event: SCF:Updating XCP:Preparing to update CMU (BBID=0)   
Apr  5 07:46:41 M12-2S-2 Event: SCF:Updating XCP:Updating CMU (BBID=0, CMU version=03010000)  
Apr  5 07:48:21 M12-2S-2 Event: SCF:Updating XCP:CMU updated (BBID=0) 
Apr  5 07:49:00 M12-2S-2 Event: SCF:Updating XCP:Preparing to update CMU (BBID=1)
Apr  5 07:49:30 M12-2S-2 Event: SCF:Updating XCP:Updating CMU (BBID=1, CMU version=03010000)
Apr  5 07:51:24 M12-2S-2 Event: SCF:Updating XCP:CMU updated (BBID=1)
Apr  5 07:51:25 M12-2S-2 Event: SCF:XCP update has been completed (XCP version=3010:last version=3009)
Apr  5 07:51:26 M12-2S-2 Event: SCF:This XSCF will be switched back to standby mode after completion of firmware update
Apr  5 07:51:57 M12-2S-1 Event: SCF:Change Master Complete(BB#00) 
If the message "XCP update has been completed" appears, the XCP firmware update has completed.
Note - A message similar to "XSCF update has been completed" or "CMU update has been completed" will appear on the SPARC M10. However, the update of all the XCP firmware will not have completed by the time the message appears.
Note - To safely update the firmware, do not perform power operations for physical partitions, reboot the XSCF, etc. until you have confirmed the "XCP update has been completed" message on the completion of the XCP firmware update. For details, see "16.2.1  Notes on Update."
  1. If the message "XCP update has been completed" does not appear, the update is not yet complete. Execute the showlogs monitor command again to check the completion of the update.
    Usually, the update is completed about 40 minutes after an XSCF reboot.


    - If the power of the physical partition is on

    The update of the target CMU firmware has not yet begun at the point in time where the flashupdate command is executed and update completion is checked. Therefore, the message does not appear for the CMU firmware. The update of the target CMU firmware begins when the physical partition is powered off and on in step 13.


    - If the firmware is updated to version XCP 2050 or later

    After the firmware update is completed, the master and standby XSCFs are automatically switched. The automatic switching takes about 10 minutes.
  1. If the messages "This XSCF will be switched back to standby mode after completion of firmware update," "Change Master Complete," and "Standby XSCF Ready" appear, the switching has been completed.

    To check the completion of the switching, execute the showhardconf command, and confirm that Status is Normal for both the master XSCF and standby XSCF.
XSCF> showhardconf
SPARC M10-4S;
+ Serial:2081230011; Operator_Panel_Switch:Locked;
+ System_Power:Off; System_Phase:Cabinet Power Off;
Partition#0 PPAR_Status:Powered Off;
Partition#1 PPAR_Status:Powered Off;
BB#00 Status:Normal; Role:Master; Ver:2003h; Serial:2081231002;
+ FRU-Part-Number:CA07361-D202 A1
:
BB#01 Status:Normal; Role:Standby Ver:0101h; Serial:7867000297;
+ FRU-Part-Number:CA20393-B50X A2 ;
  1. After confirming that the switching has completed, go to step 12. 
Note - If execution of the showhardconf command displays "Cannot communicate with the other XSCF. Check the other XSCF's state.", the switching of the master and standby XSCFs has not been completed. Execute the showhardconf command again to check the completion of the switching.
Note - Firmware update processing switches the master and standby XSCFs twice. As a result, the XSCF where you executed the flashupdate command returns to being the master XSCF. Switching the master and standby XSCFs may disconnect the XSCF session. If the XSCF session is disconnected, reconnect.
Note - Do not perform power operations for physical partitions, reboot the XSCF, etc. until the switching of the master and standby XSCFs has completed. For details, see "16.2.1  Notes on Update."
  1. - If the firmware is updated to version XCP 2044 or earlier
Firmware update processing switches the master and standby XSCFs. As a result, the other XSCF paired with the XSCF where you executed the flashupdate command becomes the master XSCF.
  1. Execute the switchscf command to return the master and standby XSCFs to their pre-update states.
Note - When updating the firmware to version XCP 2050 or later, you do not have to perform this work because the XSCFs have already been switched.
XSCF> switchscf -t Standby
The XSCF unit switch between the Active and Standby states.
Continue? [y|n] :y
  1. Since an XSCF reboot disconnects the XSCF session, the master XSCF is connected again.

    To check the completion of the switching, execute the showhardconf command, and confirm that Status is Normal for both the master XSCF and standby XSCF.
XSCF> showhardconf
SPARC M10-4S;
+ Serial:2081230011; Operator_Panel_Switch:Locked;
+ System_Power:Off; System_Phase:Cabinet Power Off;
Partition#0 PPAR_Status:Powered Off;
Partition#1 PPAR_Status:Powered Off;
BB#00 Status:Normal; Role:Master; Ver:2003h; Serial:2081231002;
+ FRU-Part-Number:CA07361-D202 A1
:
BB#01 Status:Normal; Role:Standby Ver:0101h; Serial:7867000297;
+ FRU-Part-Number:CA20393-B50X A2 ;
Note - If execution of the showhardconf command displays "Cannot communicate with the other XSCF. Check the other XSCF's state.", the switching of the master and standby XSCFs has not been completed. Execute the showhardconf command again to check the completion of the switching.
  1. Set the XSCF time.
    If the XSCF time has shifted, the logical domain time may shift when the physical partition is powered on.
    For details on how to set the XSCF time, see "6.1.2  Setting the XSCF Time Before System Startup."
  1. To complete the CMU firmware update when the power of the physical partition is on, power off and on the physical partition.
    If the power of the physical partition is off, go to step 14.
Note - In the case of a logical domain configuration, execute the ldm add-spconfig command of Oracle VM Server for SPARC in the control domain to save the latest configuration information in the XSCF before powering off the physical partition.
For details, see "6.2.2  Saving the Logical Domain Configuration Information before System Stop" and "10.11.1  Saving/Displaying Logical Domain Configuration Information."
  1. If the power of the physical partition is on, execute the poweroff command to power off the physical partition.
XSCF> poweroff -p xx
  1. Execute the showpparstatus power command, and confirm that the power of the physical partition is off.
XSCF> showpparstatus -p xx
PPAR-ID        PPAR Status
xx             Powered Off
  1. Execute the poweron command to power on the physical partition.
XSCF> poweron -p xx
  1. Execute the showpparstatus command, and confirm that PPAR Status is "Running."
XSCF> showpparstatus -p xx
PPAR-ID        PPAR Status
xx             Running
  1. Execute the version command, and confirm that the firmware version is up to date.
XSCF> version -c xcp -v
BB#00-XSCF#0 (Master)
XCP0 (Reserve): 2044
CMU           : 02.04.0004
    POST          : 1.43.0
    OpenBoot PROM : 4.34.0+1.19.0
    Hypervisor    : 0.27.3
XSCF          : 02.04.0004
XCP1 (Current): 2044
CMU           : 02.04.0004
    POST          : 1.43.0
    OpenBoot PROM : 4.34.0+1.19.0
    Hypervisor    : 0.27.3
XSCF          : 02.04.0004
BB#01-XSCF#0 (Standby)
XCP0 (Current): 2044
CMU           : 02.04.0004
    POST          : 1.43.0
    OpenBoot PROM : 4.34.0+1.19.0
    Hypervisor    : 0.27.3
XSCF          : 02.04.0004
XCP1 (Reserve): 2044
CMU           : 02.04.0004
    POST          : 1.43.0
    OpenBoot PROM : 4.34.0+1.19.0
    Hypervisor    : 0.27.3
XSCF          : 02.04.0004
CMU BACKUP
#0: 02.04.0004
#1: ..
Note - On the SPARC M10, if firmware is updated by powering on the physical partition, only the current bank of the CMU firmware is updated.
With the CMU firmware, where control is handled only by the current bank, there is no problem with an outdated version of the reserve bank.
If the firmware is updated by stopping the power of a physical partition, then both the reserve bank and current bank of the CMU firmware are updated.
For the CMU firmware version that corresponds to the XCP version, see "Existing XCP Firmware Versions and Support Information" in the latest Product Notes for your server.