Skip to main content

16.5.1 Updating XCP on a System With One XSCF


16.5.1 Updating XCP on a System With One XSCF
  1. Log in to the XSCF.
  2. Execute the showhardconf command, and confirm that the XSCF status (MBU Status) is Normal.
  1. The following shows examples of the SPARC M10-1.
XSCF> showhardconf
SPARC M10-1;
    + Serial:2101151019A; Operator_Panel_Switch:Service;
    + System_Power:Off; System_Phase:Cabinet Power Off;
    Partition#0 PPAR_Status:Powered Off;
    MBU Status:Normal; Ver:2046h; Serial:USDA-P00008 ;
        + FRU-Part-Number:CA20366-B10X 002AB/LGA-MBU -01 ;
        + Power_Supply_System: ;
        + Memory_Size:32 GB;
  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
    CMU BACKUP
    #0: 02.04.0001
    #1: ..
  1. For the SPARC M12-1/M12-2, there is no reserve bank of the CMU firmware. The following shows a display example.
XSCF> version -c xcp -v
BB#00-XSCF#0 (Master)
XCP0 (Reserve): 3010
XSCF          : 03.01.0000
XCP1 (Current): 3010
XSCF          : 03.01.0000
CMU           : 03.01.0000
    POST          : X.X.X
    OpenBoot PROM : X.XX.X+X.XX.X
    Hypervisor    : X.X.X
CMU BACKUP
#0: 03.01.0000
#1: ..
  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).
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 13:56:50 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 30 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 9). 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.....

:
  1. Here, the XSCF is rebooted, and the XSCF session is disconnected.
    At this point in time, the XCP firmware update is not yet complete.
  2. Connect to the XSCF again.
  3. Execute the showlogs monitor command to check the completion of the XCP firmware update.
XSCF> showlogs monitor
May 29 14:30:09 M10-1-0 Event: SCF:XCP update is started (XCP version=2044:last version=2041)
May 29 14:31:59 M10-1-0 Event: SCF:XSCF update is started (BBID=0, bank=1)
May 29 14:32:18 M10-1-0 Event: SCF:XSCF writing is performed (BBID=0, XSCF version=02040004)
May 29 14:39:27 M10-1-0 Event: SCF:XSCF update has been completed (BBID=0, bank=1)
May 29 14:39:28 M10-1-0 Event: SCF:XSCF bank apply has been completed (BBID=0, bank=1, XCP version=2044:last version=2041)
May 29 14:47:12 M10-1-0 Event: SCF:XSCF ready
May 29 14:48:32 M10-1-0 Event: SCF:XSCF update is started (BBID=0, bank=0)
May 29 14:48:52 M10-1-0 Event: SCF:XSCF writing is performed (BBID=0, XSCF version=02040004)
May 29 14:55:51 M10-1-0 Event: SCF:XSCF update has been completed (BBID=0, bank=0)
May 29 14:57:04 M10-1-0 Event: SCF:CMU update is started (BBID=0)
May 29 14:57:07 M10-1-0 Event: SCF:CMU writing is performed (BBID=0, CMU version=02040004)
May 29 14:59:07 M10-1-0 Event: SCF:CMU update has been completed (BBID=0)
May 29 15:00:19 M10-1-0 Event: SCF:CMU update is started (BBID=0)
May 29 15:00:20 M10-1-0 Event: SCF:CMU writing is performed (BBID=0, CMU version=02040004)
May 29 15:02:18 M10-1-0 Event: SCF:CMU update has been completed (BBID=0)
May 29 15:02:20 M10-1-0 Event: SCF:XCP update has been completed (XCP version=2044:last version=2041)
  1. The following example displays messages on the SPARC M12-2.
XSCF> showlogs monitor
Mar 15 15:29:34 M12-2-0 Event: SCF:XCP update is started (XCP version=3010:last version=3009)
Mar 15 15:39:20 M12-2-0 Event: SCF:Updating XCP:Preparing to update XSCF (BBID=0, bank=0)
Mar 15 15:42:59 M12-2-0 Event: SCF:Updating XCP:Updating XSCF (BBID=0, XSCF version=03010000)
Mar 15 15:43:13 M12-2-0 Event: SCF:Updating XCP:XSCF updated (BBID=0, bank=0)
Mar 15 15:43:20 M12-2-0 Event: SCF:Updating XCP:XSCF bank has changed (BBID=0, bank=0, XCP version=3010:last version=3009)
Mar 15 16:02:49 M12-2-0 Event: SCF:Updating XCP:Preparing to update XSCF (BBID=0, bank=1)
Mar 15 16:04:18 M12-2-0 Event: SCF:Updating XCP:Updating XSCF (BBID=0, XSCF version=03010000)
Mar 15 16:04:22 M12-2-0 Event: SCF:Updating XCP:XSCF updated (BBID=0, bank=1)
Mar 15 16:04:47 M12-2-0 Event: SCF:XSCF ready
Mar 15 16:07:47 M12-2-0 Event: SCF:Updating XCP:Preparing to update CMU (BBID=0)
Mar 15 16:08:17 M12-2-0 Event: SCF:Updating XCP:Updating CMU (BBID=0, CMU version=03010000)
Mar 15 16:08:28 M12-2-0 Event: SCF:Updating XCP:CMU updated (BBID=0)
Mar 15 16:08:31 M12-2-0 Event: SCF:XCP update has been completed (XCP version=3010:last version=3009)
  1. 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 20 minutes after the "XSCF ready" message appears.
  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."
  2. To complete the CMU firmware update, power off and on the physical partition.
    If the power of the physical partition is on, the target CMU firmware has not been updated at this point in time. Therefore, the message does not appear for the CMU firmware.
    If the power of the physical partition is off, go to step 12.
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. Execute the poweroff command to power off the physical partition. 
XSCF> poweroff -p 0
  1. Execute the showpparstatus power command, and confirm that the power of the physical partition is off.
XSCF> showpparstatus -p 0
PPAR-ID        PPAR Status
00             Powered Off
  1. Execute the poweron command to power on the physical partition.
XSCF> poweron -p 0
  1. Execute the showpparstatus command, and confirm that PPAR Status is "Running."
XSCF> showpparstatus -p 0
PPAR-ID        PPAR Status
00             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
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.