Skip to main content

16.2.1 Notes on Update


16.2.1 Notes on Update
  1. Along with an XCP release, product notes for that version are also made publicly available. The product notes describe the following: added functions, software patch information, the correspondence between new hardware and firmware, bug information, document corrections, etc. Also, the latest product notes contain corrections of past product notes. Be sure to read the product notes for both the firmware version applied and the latest version.
  2. A problem described in "Problems With XCP and Workarounds" in the Product Notes for your server may occur when the firmware is updated. In such cases, take the actions described as workarounds, and then update the firmware again.
  3. Do not apply a version older than the XCP firmware on the system currently in operation. If an older version is applied, system operation is not guaranteed. However, there is no problem with returning to the pre-update version of the firmware, unless any of the settings for the XSCF and Oracle VM Server for SPARC has changed after the firmware update.
    The procedure for returning to the earlier version is similar to the update procedure.
  4. No firmware update is possible where there is failed hardware. Before update, be sure to confirm that there is no failed hardware. If there is failed hardware, recover it from a failure and then update firmware. Check the hardware status with the showhardconf command. Confirm that no hardware is marked with an asterisk (*).
  5. XSCF communication is disconnected once during an update of the entire XCP firmware and the XSCF firmware because the XSCF is rebooted. In this case, connect and log in to the XSCF again.
    Also, the following warning message may be output to the control domain console during the XSCF reboot.
    PICL snmpplugin: cannot fetch object value (err=5, OID=<1.3.6.1.2.1.47.1.4.1>,row=0)

    If cluster software is in use, the following warning message may be output to the logical domain console during the XSCF reboot.
    SA SA_xscf***.so to test host *** failed
    7240 Connection to the XSCF is refused. (node:*** ipadress:*** detail:***)
  6. To safely update firmware, do not perform the operations described below until you have confirmed the "XCP update has been completed" message on the completion of the XCP firmware update. The same also applies to the XSCF Web operations corresponding to XSCF commands.
    - Turning off the input power

    - Executing the poweron, testsb, diagxbu, or reset command, or operating the POWER switch on the operation panel

    - Executing the setdate, switchscf, rebootxscf, initbb, restoreconfig, or restoredefaults command, or operating the RESET switch on the rear panel

    - Executing the getflashimage -d command

    - Executing the flashupdate -c update command

    Also, in a building block configuration system with XCP 2050 or later, after the XCP firmware update is completed, the master and standby XSCFs are automatically switched. Do not perform the above operations until you have confirmed that the master/standby switching has completed.
  7. To check whether the CMU firmware has been revised, see "Latest Information" and "Existing XCP Firmware Versions and Support Information" in the latest Product Notes. For the method of checking the CMU firmware version, see "16.2.3  Method of Checking the Firmware Version."
  8. To complete an update of revised CMU firmware when the power of the target physical partition is on, power off and on the physical partition.
    Also, in a building block configuration, if CMU firmware update has not been applied after the previous firmware update, then the message "flashupdate canceled cause PPAR is running" may appear at the next firmware update time. If this message appears, power off and on the relevant physical partition, and then update the firmware again.
  9. The CMU firmware in the SPARC M10 has a current bank and a reserve bank. If the firmware is updated by powering on a physical partition, only the current bank is updated by the completion of CMU firmware application.
    With the CMU firmware, where control is handled only by the current bank, there is no problem with an outdated firmware 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.
  10. After updating the firmware, save the XSCF setting information again. For details, see "10.10  Saving/Restoring XSCF Settings Information."
  11. In the SPARC M12-1/M10-1, if the XSCF startup mode function is set to "fast" mode, set it to "normal" (default) mode again to update the firmware.
    For details on how to change the startup mode of the XSCF startup mode function, see the xscfstartupmode command in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF Reference Manual.