================================================================================
Release Notes for
NEC Express5800/R320e, R310e
BMC Firmware Revision 04.81
================================================================================
NEC Corporation.
October. 2021

[Contents]
1.  About the software
2.  Server models for update
3.  Update procedures
    <Windows(R) OS>
    <Red Hat Enterprise Linux(R) OS>
    <VMware ESXi(R) 6.0 Update x>
    <VMware ESXi(R) 6.5 / VMware ESXi(R) 6.5 Update x>
4.  Revision history
5.  Legal notices (trademarks and copyrights)

--------------------------------------------------------------------------------
1.  About the software

This BMC Firmware update module supports the following functional enhancement
in the NEC Express5800/R320e-M4, R320e-E4 and R310e-E4 models:

BMC 04.81
  - Supported OpenJDK12 or later in Java.
    If you use OpenJDK, you also need IcedTea-Web.
    However, IcedTea-Web has issue that using OpenJDK13 or later causes java apps
    to fail to launch, so we recommend that you use the latest version of Amazon
    Corretto 11 instead of OpenJDK.

    IcedTea-Web
    <https://github.com/AdoptOpenJDK/IcedTea-Web/releases>

    Amazon Corretto 11
    <https://github.com/corretto/corretto-11/releases>

  - Remove the button to start the SEL/SDR/FRU/MC/Backup screen on the IPMI 
    information screen of EXPRESSSCOPE Engine 3, and add the "Launch Viewer" button.
  - When you press "Launch Viewer" button, the screen of "IPMI Information", 
    which is a Java application, is displayed, and a button to display 
    the SEL/SDR/FRU/MC/Backup screen is displayed on that screen.
  - The minimum value that can be specified for the Delay Time of AC-LINK 
    in BIOS SETUP is changed to 70 seconds. (Currently 50 seconds)
    [BIOS SETUP] -> [Server]->[Power Control Configuration]
  - BMC-LAN IPv6 addresses can now be addressed starting with "fe8".
  - Fixed an issue where remote media would become unavailable after a vulnerability
    scan on BMC-LAN port(Management LAN port).
  - The expiration date of the self-signed server certificate set by default 
    in EXPRESSSCOPE Engine 3 was extended to 2025/03/14 until 2039/10/24.
  - In rare cases, server boot failed due to cpu individual difference, but BMC 
    improvements solved this problem.
  - Improved the problem that didn't sometimes have response when the remote media
    of EXPRESSSCOPE Engine 3 connected.

  *Notes after updating to BMC 4.81 (Windows only)

   (1) The following warning log may be registered once in the system event log
       after Windows startup, but in the case of one time, there is no problem,
       so you may ignore it.

        ------------------------
        Event ID    : 3101
        Source      : ESMCommonService
        Description : Failed saving BMC config.
        ------------------------

   (2) When the same warning log as (1) is registered continuingly every 1 minute
       with the following case.

       <The case that occurs>
        - After BMC firmware update
        - After module replacement
        - After Windows start

      In this case, you can solve it by restarting the Windows service.
      Follow these steps to restart the "ftSys Maintenanceand Diagnostics(MAD)" 
      service.

      (2)-1 Rename the below folder for backup.
            before: C:\Program files\ftsys\Vtm\config
            after:  C:\Program files\ftsys\Vtm\config_bak

      (2)-2 Open [Control Panel](view by : Large icons or Small icons) -> 
            [Administrative Tools] -> [Services]

      (2)-3 The management window of [Services] is started.
            It chooses "ftSys Maintenance and Diagnostics (MAD)" from a screen 
            on the right side and displays a right-click menu.

      (2)-4 Select [Restart] from the right-click menu.

      (2)-5 The [Service Control] window is displayed, and the progress bar of 
            [stop] and [start] the service is displayed, and when this window 
            disappears automatically, it is completed.

      (2)-6 It is OK if you check the event log of the system and the relevant 
            warning log is no longer registered.

            Note) If you continue to have a warning log registered after this
                  operation, please contact us.

Note:
  - To prevent a system failure, please read this document carefully and 
    follow the procedure for successful update.  Should your system 
    malfunction or be powered off due to an unplanned event during update (for
    example, power blackout or cutoff, lightening, and noise), the system may 
    be damaged and fail to operate normally.  In this case, any remedial 
    measures shall be taken at your expense.

  - Please don't do this update from management PCs using remote KVM of 
    EXPRESSSCOPEEngine3. Update may sometimes fail.

  - To update with ExpressUpdate of ESMPRO/Manager is not supported 
    in this module. 

-------------------------------------------------------------------------------
2.  Server models for update

Users who use the following server models and BMC firmware versions need update:
 - Models to update: 
    NEC Express5800/R320e-M4
    NEC Express5800/R320e-E4
    NEC Express5800/R310e-E4

 - BMC Firmware versions to update:
    BMC Firmware Revision 04.34
    BMC Firmware Revision 04.64
    BMC Firmware Revision 04.71


NOTE:
If current BMC firmware version is later than the above an update is not required.

NOTE:
If current BMC firmware version is 04.34, confirm the following.

  In case of
   - You have performed an ssh connection to the BMC after the system has been
     powered on.
     ('Powered on' means both AC plugs are connected.)

  If your system hits this case, it requires BMC FW update after following procedure.
    1. OS shutdown.
    2. AC Power off by unplugging both AC cables.
    3. Wait more than 30 seconds.
    4. AC Power on by plugging both AC cables.
    5. DC Power on.
    6. Wait until system Duplex.
       Then you can start to update the BMC Firmware.

 - How to confirm the BMC Firmware version (Windows(R) OS):

    (1) Run ft server Utility.

        <Windows Server(R) 2008 R2>
        (Start->All programs->NEC ESMPRO Agent->ft server utility)

        <Windows Server(R) 2012 R2>
        (Start->(down-arrow button)->NEC ESMPRO Agent->ft server utility)

    (2) Select [Firmware] in [BMC] tree and confirm BMC Firmware version.
         ID 10/120 : Runtime means BMC Firmware version of CPU/IO Module0
         ID 11/120 : Runtime means BMC Firmware version of CPU/IO Module1


 - How to confirm the BMC Firmware version (Red Hat Enterprise Linux(R) OS):

    (1) Run ft server Utility.

        # /opt/nec/esmpro_sa/bin/ESMftcutil

    (2) Select [Firmware(ID:[nn/120])] under the target [BMC(ID:[nn/120])]
        in [BMC] tree and confirm [Runtime] in [Firmware Revision].
         * nn: 10 or 11

         (ID:[10/120]) : Runtime means BMC Firmware version of CPU/IO Module0
         (ID:[11/120]) : Runtime means BMC Firmware version of CPU/IO Module1


 - How to confirm the BMC Firmware version (VMware ESXi(R)):

    (1) Login to the ftSys Management Appliance as a root user.

    (2) Run the following command and confirm [Firmware Rev].

        # /opt/ft/bin/ftsmaint ls 10/120 or
        # /opt/ft/bin/ftsmaint ls 11/120

         10/120 : BMC Firmware version of CPU/IO Module0
         11/120 : BMC Firmware version of CPU/IO Module1

--------------------------------------------------------------------------------
3.  Update procedures

 - <Windows(R) OS>:

   Follows the below procedure.

   3-1. Preparation of Update

     (1) Confirm that the System FT LED in front of ft server lights in green.
         - System FT LED can also be confirmed in ESMPRO/Manager.
          
     (2) Log-in the system as a user with administrator privilege for 
         the ft server in local or remote access.

     (3) Terminate all running applications in ft server.

     (4) If the backup software related services in ft server are operating, 
         the PCI module may be not duplexed properly.
         Please be sure to stop the services before update procedure.

     (5) Download the zipped file into any hard disk directory in ft server and 
         unzip the file into any directory.

     (6) If there is a disc in the DVD drive in ft server, please eject it.

     (7) Change the delaytime of AC-LINK of BMC setting and save the current
         BMC setting.

         By implementing the following procedure, the delay time of AC-LINK of 
         the current BMC setting is changed.
         And, the BMC settings are then saved in files in the ft control software.

         Notes) In this change procedure, when you change the delaytime of AC-LINK
                of BMC setting and save the current BMC setting, please do not 
                change these by using ESMPRO/Manager of management PC.
                Please use BMC Configuration in ft server.

          1. Run BMC Configuration in ft server.

             <Windows Server(R) 2008 R2>
              (Start menu -> All Programs -> BMC_Configuration -> BMC Configuration])

             <Windows Server(R) 2012 R2>
              (Start menu -> (down-arrow button) -> 
                                             BMC_Configuration -> BMC Configuration)

             Note) If current user is not a built-in Administrator, right click 
                   the menu and select gRun as administratorh.

          2. Click "Set BMC Configuration" button.

          3. Select the "Miscellaneous" tab.

          4. Check the following about AC-LINK settings in the Power Restore Delay.

            4-1. "Last State" or "Power On" are selected.
                 If the "Delay Time" is 69 seconds or less, proceed to step 5.

            4-2. When "Stay Off" is selected and the "Delay Time" is less than 69 seconds
                 select "Last State" and proceed to step 5.

                 Note) In this case, you need to return to "Stay Off" after the BMC 
                       firmware update.

            4-3. If it dose not fall under the above, taking notes of the "Delay Time" 
                 and proceed to step 6.
                 This note is used in "3-3. Procedure after the update".

          5. Change the "Delay Time" to at least 70 seconds.
             Make a note of the value you set here.
             This note is used in "3-3. Procedure after the update".

          6. Click "Apply" button.

          7. Click "OK" button.

             After that, when the "Other software is changeing the Configuration,
             Please wait a minutes" messages are displayed , follows the procedure below.
              -Click "OK" button.
              -Please wait for about 1 minute.
              -Please return to step 2.

          8. Click "Close" button.

          9. Please wait about 3 minutes before proceeding.

   3-2. Update procedure

     (1) Double-click BMCUP.BAT in the directory, then the BMC Firmware Update 
         Program will start. 

         Note) While updating, the screen may disappear temporarily.
               This is not an error if the screen reappears.

     (2) Confirm the progress using the ft server utility.
     
          1. Run ft server Utility.

             <Windows Server(R) 2008 R2>
             (Start menu->All programs->NEC ESMPRO Agent->ft server utility)

             <Windows Server(R) 2012 R2>
             (Start menu->(down-arrow button)->NEC ESMPRO Agent->ft server utility)

          2. Select [Firmware] of [BMC] tree and confirm Status.
             Refresh the current status by pressing the [F5] key.

          3. When the update process is completed, status will show 'Duplex, Duplex'.
             The update process will takes approximately 30 minutes.
            
     (3) Confirm whether the update process has succeeded using the ft server 
         utility.

         Select [Firmware] in [BMC] tree and confirm BMC Firmware version.

         Confirm firmware as follows.
           ID 10/120 : Runtime=04.81 Boot=01.03 Sdr=04.08
           ID 11/120 : Runtime=04.81 Boot=01.03 Sdr=04.08

         Otherwise, update process is failed.
         Update again by following 3-2. Update Procedure.

     (4) Confirm the System FT LED lights in green in front of ft server or
         in ESMPRO/Manager.

     (5) After Firmware update completes, delete the unzip file if necessary.

   3-3. Procedure after the update.

     (1) Follow these steps to set up AC-LINK.

          1. Run BMC Configuration.

             <Windows Server(R) 2008 R2>
              (Start menu -> All Programs -> BMC_Configuration -> BMC Configuration])

             <Windows Server(R) 2012 R2>
              (Start menu -> (down-arrow button) -> 
                                             BMC_Configuration -> BMC Configuration)

             Note) If current user is not a built-in Administrator, right click 
                   the menu and select gRun as administratorh.

          2. Click "Set BMC Configuration" button.

          3. Select the "Miscellaneous" tab.

          4. If the "Delay time" in the AC-LINK in the Power Restore Delay settings is 
             different from the "Delay time" the value that you were taking notes of, 
             return the "Delay time".

          5. If you have performed "3-1 Preparation of Update" -> (7) -> 4-2 and need to 
             return AC-LINK to "Stay Off", select "Stay Off" in AC-LINK.

          6. Click "Apply" button.

          7. Click "OK" button.

             After that, when the "Other software is changeing the Configuration,
             Please wait a minutes" messages are displayed , follows the procedure below.
              -Click "OK" button.
              -Please wait for about 1 minute.
              -Please return to step (2).

          8. Click "Close" button.


 - <Red Hat Enterprise Linux(R) OS>:

   Follows the below procedure.

   3-1. Preparation of Update

     (1) Confirm the System FT LED lights in green.

     (2) Log-in to the system as a root user.

     (3) Terminate all running applications in ft server.

     (4) Download the zipped file into any hard disk directory in ft server and 
         unzip the file into any directory. 
         Write down the path to the directory containing the unzipped files.

         <Command Example>
         # mkdir /tmp/fw
         # cd /tmp/fw
         # unzip <zip filename>

         Note)
           /tmp/fw is a reference example.

         The firmware update uses next 4 files:
           '062-03711bmc_b01.03r04.81s04.08.bin'
           'change.sh'
           'saveBmc.sh'
           'restoreBmc.sh'

     (5) Save the current BMC setting.

         It uses 'saveBmc.sh'.
         Run the following command.
         When the "OK" messages are displayed the save has completed.

         # cd /tmp/fw              <- Replace it with the directory you have noted in (4).
         # sh saveBmc.sh

         <Example>
         ----------------------------------------------
         # sh saveBmcs.sh

         OK.
         ----------------------------------------------

     (6) If the "Delay Time" of AC-LINK in the BMC setting saved in (5) is 
         69 seconds or less, change the value of the saved file to 70 seconds.
         (From BMC 4.81, the lowest "Delay Time" was changed to 70 seconds).

         It uses 'change.sh'.
         Run the following command.
         When the "OK" messages are displayed the changes has completed.

         # cd /tmp/fw              <- Replace it with the directory you have noted in (4).
         # sh change.sh

         <Example>
         ----------------------------------------------
         # sh change.sh
         xxxxxxxxxxxx
         OK.
         ----------------------------------------------

     (7) Restore the BMC settings to reflect the values changed in (6).

         It uses 'restoreBmc.sh'.
         Run the following command.
         When the "OK" messages are displayed the restore has completed.

         # cd /tmp/fw              <- Replace it with the directory you have noted in (4).
         # sh restoreBmc.sh

         <Example>
         ----------------------------------------------
         # sh restoreBmc.sh

         OK.
         ----------------------------------------------

   3-2. Update procedure

     (1) Check which is the secondary CPU/IO module.

         The PCI module with the PRIMARY LED illuminated is the primary module.
         The PRIMARY LED is off on the secondary module.

     (2) Run ft server Utility.
         # /opt/nec/esmpro_sa/bin/ESMftcutil

     (3) Select [Firmware(ID:[nn/120])] under the target [BMC(ID:[nn/120])]
         of secondary PCI module in [BMC] tree.
         * nn: 10 or 11
           (ID:[10/120]) : Upper module(CPU/IO Module0)
           (ID:[11/120]) : Lower module(CPU/IO Module1)

     (4) Check [Current state] of the target component is 'DUPLEX' by 
         selecting [Refresh]. And then select [Update] of Firmware Update.

         Enter the file path you have written down in section 3-1 step (4)
         in [Enter the file location of the new firmware] text box, and 
         select [Activate].

         <Input example>  '/tmp/fw/062-03711bmc_b01.03r04.81s04.08.bin'

     (5) After the Confirmation message is displayed, select [ok].
         BMC firmware update starts.

         When the update starts, the following message is output to syslog.
          Note) syslog is /var/log/messages

         'kernel: EVLOG: INFORMATION - BMC nn/120, firmware burn starting.'
         * nn: 10 or 11

         After the Information message is displayed, select [ok].

     (6) After the Firmware screen is displayed, select [Close].

     (7) The update process will take approximately 15 minutes.

         When the update is completed, the following message is output on syslog.
         'kernel: EVLOG: INFORMATION - BMC nn/120, firmware burn succeeded.'
         * nn: 10 or 11

     (8) Confirm whether update process has succeeded using the ft server utility.

         Select [Firmware(ID:[nn/120])] under the target [BMC(ID:[nn/120])]
         of the secondary PCI module in [BMC] tree.
         * nn: 10 or 11

         Confirm firmware as follows. 
           Firmware Revision: Runtime=04.81 Boot=01.03 Sdr=04.08

         And when [Current state] is 'DUPLEX', the firmware update has succeeded.

         Otherwise, update process has failed.
         Update again by following 3-2. Update Procedure.

     (9) If the firmware update of the secondary PCI module is completed, 
         Start the firmware update of the  primary PCI module.

         Select [PCI module(ID:[nn])] of primary PCI module in [ft server] tree.
         * nn: 10 or 11

    (10) Confirm that [Current state] is 'DUPLEX'.
         And Select [Stop] of [Start/Stop].

    (11) After the Confirmation message is displayed, select [ok].

         When you stop the operation of the primary PCI module, 
         a failover occurs and the secondary PCI module becomes the primary 
         module.

         Note) When the primary PCI module is stopped, the screen temporarily 
               blacks out and then displayed again.
         Note) DISK ACCESS LED of hard disk is blinking amber or green.

    (12) Select [Start] of [Start/Stop].
         After the Confirmation message is displayed, select [ok].

         Firmware update starts automatically.

         The update process will takes approximately 15 minutes.

    (13) Confirm whether update process has succeeded by using the ft server utility.

         Select [Firmware(ID:[nn/120])] under the target [BMC(ID:[nn/120])]
         of secondary PCI module in [BMC] tree.
         * nn: 10 or 11

         Confirm firmware as follows. 
           Firmware Revision: Runtime=04.81 Boot=01.03 Sdr=04.08

    (14) Confirm the System FT LED lights in green.


  3-3.Procedure after the update.

     (1) Restore the BMC settings saved in "3-1 Preparation of Update".

         It uses 'restoreBmc.sh'.
         Run the following command.
         When the "OK" messages are displayed the restore has completed.

         # cd /tmp/fw              <- Replace it with the directory you have noted.
         # sh restoreBmc.sh

         <Example>
         ----------------------------------------------
         # sh restoreBmc.sh

         OK.
         ----------------------------------------------

    (2) After Firmware update completes, delete the unzip file if necessary.


 - <VMware ESXi(R) 6.0 Update x>:

   Follows the procedure below.

   3-1. Preparation of Update

     (1) Confirm the System FT LED lights in green.

     (2) Login to the ftSys Management Appliance as a root user.

     (3) Shutdown all guest OS except for the ftSys Management Appliance.

     (4) Terminate all running applications on the ftSys Management Appliance.

     (5) Download the zipped file into any hard disk directory on the Management
         PC and unzip the files into any directory.

         The firmware update uses next 2 files:
           '062-03711bmc_b01.03r04.81s04.08.bin'
           'change.sh'

     (6) Copy the 2 files described above to any directory of the ftSys Management
         Appliance by following the steps below.

          1. Write the image file onto CD/DVD media, and set in CD/DVD drive
             of management PC in which VMware vSphere(R) Client is installed.

          2. Select the ftSys Management Appliance from the left pane of
             VMware vSphere(R) Client. 
             Click the CD/DVD button on toolbar, and connect CD/DVD drive
             to the ftSysManagement Appliance.

          3. Login to the ftSys Management Appliance as a root user,
             and mount the CD/DVD.

             <Command example>
              # mkdir /mnt/cdrom
              # mount /dev/cdrom /mnt/cdrom

             Note)
               When the /mnt/cdrom directory exists, the mkdir command is unnecessary.

          4. Copy the image file from CD/DVD drive to a desired directory of 
             ftSys Management Appliance.

             <Command example>
              # mkdir /tmp/fw
              # cp /mnt/cdrom/062-03711bmc_b01.03r04.81s04.08.bin /tmp/fw
              # cp /mnt/cdrom/change.sh /tmp/fw

             Note)
               Write down the path to the directory which copied the file.
               /tmp/fw is a reference example.

             Note)
               When file system of the CD/DVD is ISO9660, the file name is changed
                as follows. Please use the changed file name in this case.

                 before: 062-03711bmc_b01.03r04.81s04.08.bin
                 after : 062_03711bmc_b01_03r04_81s04_08.bin
                         '-'(hyphen) and '.'(period except the file extension),
                         change to '_'(underscore).

          5. After the image file is copied, unmount CD/DVD.

             <Command example>
              # cd /
              # umount /mnt/cdrom

             Disconnect the CD/DVD drive from the ftSys Management Appliance 
             by clicking the CD/DVD button on toolbar in VMware vSphere(R) Client. 

     (7) Save the current BMC setting.
         Run the following command on the ftSys Management Appliance.
         When the "OK" messages are displayed the save has completed.

         # /opt/ft/bin/ftsmaint saveBmcs

         <Example>
         ----------------------------------------------
         # /opt/ft/bin/ftsmaint saveBmcs

         OK.
         ----------------------------------------------

     (8) If the "Delay Time" of AC-LINK in the BMC setting saved in (7) is 
         69 seconds or less, change the value of the saved file to 70 seconds.
         (From BMC 4.81, the lowest "Delay Time" was changed to 70 seconds).

         It uses 'change.sh'.
         Run the following command.
         When the "OK" messages are displayed the changes has completed.

         # cd /tmp/fw            <-- Replace it with the directory you have noted in (6).
         # sh change.sh

         <Example>
         ----------------------------------------------
         # sh change.sh
         xxxxxxxxxxxx
         OK.
         ----------------------------------------------

     (9) Restore the BMC settings to reflect the values changed in (8).
         Run the following command.
         When the "OK" messages are displayed the restore has completed.

         # /opt/ft/bin/ftsmaint restoreBmcs

         <Example>
         ----------------------------------------------
         # /opt/ft/bin/ftsmaint restoreBmcs

         OK.
         ----------------------------------------------

   3-2. Update procedure

     (1) Run the following command on the ftSys Management Appliance.
         # /opt/ft/bin/ftsmaint burnBmcs <<bmc_file>>

         For <<bmc_file>>, specify the file path where the image file was
         copied in Step 3-1,(6).
         <bmc_file example>
           /tmp/fw/062-03711bmc_b01.03r04.81s04.08.bin

     (2) The update process will take approximately 30 minutes.
         When the following messages are displayed the update has completed.
         
         <Example, when an update succeeded>
          ----------------------------------------------
          Updated firmware on the device at path 11/120.
          Updated firmware on the device at path 10/120.
          ----------------------------------------------

         <Example, when an update succeeded at only one side>
         ----------------------------------------------
         Updated firmware on the device at path 11/120.
         Tried to update firmware on the device at path 10/120.  <-- The update failed.
         ----------------------------------------------

     (3) Confirm whether the update process has succeeded by using the following
         If the update fails on one or both sides, try again from (1).

         # /opt/ft/bin/ftsmaint ls 10/120

         <Example>
          ----------------------------------------------
          Op State : DUPLEX
          :
          Firmware Rev : 04.81/01.03/04.08
          ----------------------------------------------

         If [Op State] is 'DUPLEX' and [Firmware Rev] is '04.81/01.03/04.08' then
         the Firmware update has completed successfully.

         Confirm whether the other module update process has succeeded 
         using the following command.

         # /opt/ft/bin/ftsmaint ls 11/120

         <Example>
          ----------------------------------------------
          Op State : DUPLEX
          :
          Firmware Rev : 04.81/01.03/04.08
          ----------------------------------------------

         If [Op State] is 'DUPLEX' and [Firmware Rev] is '04.81/01.03/04.08' then
         the Firmware update has completed successfully.

     (4) Confirm the System FT LED lights in green.

     (5) After Firmware update completes, delete the unzip file and directory
         if necessary.

  3-3.Procedure after the update.

     (1) Restore the BMC settings you saved in preparation for the update.
         Run the following command.
         When the "OK" messages are displayed the restore has completed.

         # /opt/ft/bin/ftsmaint restoreBmcs

         <Example>
         ----------------------------------------------
         # /opt/ft/bin/ftsmaint restoreBmcs

         OK.
         ----------------------------------------------

 - <VMware ESXi(R) 6.5 / VMware ESXi(R) 6.5 Update x>:

   Follows the procedure below.

   3-1. Preparation of Update

     (1) Confirm the System FT LED lights in green.

     (2) Login to the ftSys Management Appliance as a root user.

     (3) Shutdown all guest OS except for the ftSys Management Appliance.

     (4) Terminate all running applications on the ftSys Management Appliance.

     (5) Download the zipped file into any hard disk directory on the Management
         PC and unzip the files into any directory.

         The firmware update uses next 2 files:
           '062-03711bmc_b01.03r04.81s04.08.bin'
           'change.sh'

     (6) Store above files in any directory of the ftSys Management Appliance as follows.

          1. Write files onto CD/DVD media, and set in CD/DVD drive of management PC.

          2. Select the ftSys Management Appliance [Virtual Machines] of
             Navigator on VMware Host Client.
             Select [Launch remote console] of [Console] tab,
             the remote console (VMRC) is started.

          3. Select [VMRC] menu of the remote console screen,
             select [Removable Devices] - [CD/DVDdrive x] - [x.Connect to x],
             and connect DVD to the set DVD drive.

          4. Login to the ftSys Management Appliance as a root user,
             and mount the CD/DVD.

             <Command example>
              # mkdir /mnt/cdrom
              # mount /dev/cdrom /mnt/cdrom

             Note)
               When the /mnt/cdrom directory exists, the mkdir command is unnecessary.

          5. Copy the image file from CD/DVD drive to a desired directory of 
             ftSys Management Appliance.

             <Command example>
              # mkdir /tmp/fw
              # cp /mnt/cdrom/062-03711bmc_b01.03r04.81s04.08.bin /tmp/fw
              # cp /mnt/cdrom/change.sh /tmp/fw

             Note)
               Write down the path to the directory which copied the file.
               /tmp/fw is a reference example.

             Note)
               When file system of the CD/DVD is ISO9660, the file name is changed
                as follows. Please use the changed file name in this case.

                 before: 062-03711bmc_b01.03r04.81s04.08.bin
                 after : 062_03711bmc_b01_03r04_81s04_08.bin
                         '-'(hyphen) and '.'(period except the file extension),
                         change to '_'(underscore).

          6. After the image file is copied, unmount CD/DVD.

             <Command example>
              # cd /
              # umount /mnt/cdrom

          7. Press the <Ctrl>+<Alt> keys to release the mouse,
             select [VMRC] menu of the remote console screen,
             select [Removable Devices] - [CD/DVDdrive x] - [Disconnect x:],
             and then take out the DVD from the DVD drive.

     (7) Save the current BMC setting.
         Run the following command on the ftSys Management Appliance.
         When the "OK" messages are displayed the save has completed.

         # /opt/ft/bin/ftsmaint saveBmcs

         <Example>
         ----------------------------------------------
         # /opt/ft/bin/ftsmaint saveBmcs

         OK.
         ----------------------------------------------

     (8) If the "Delay Time" of AC-LINK in the BMC setting saved in (7) is 
         69 seconds or less, change the value of the saved file to 70 seconds.
         (From BMC 4.81, the lowest "Delay Time" was changed to 70 seconds).

         It uses 'change.sh'.
         Run the following command.
         When the "OK" messages are displayed the changes has completed.

         # cd /tmp/fw            <-- Replace it with the directory you have noted in (6).
         # sh change.sh

         <Example>
         ----------------------------------------------
         # sh change.sh
         xxxxxxxxxxxx
         OK.
         ----------------------------------------------

     (9) Restore the BMC settings to reflect the values changed in (8).
         Run the following command.
         When the "OK" messages are displayed the restore has completed.

         # /opt/ft/bin/ftsmaint restoreBmcs

         <Example>
         ----------------------------------------------
         # /opt/ft/bin/ftsmaint restoreBmcs

         OK.
         ----------------------------------------------

   3-2. Update procedure

     (1) Run the following command on the ftSys Management Appliance.

         # /opt/ft/bin/ftsmaint burnBmcs <<bmc_file>>

         For <<bmc_file>>, specify the file path where the image file was
         copied in Step 3-1,(6).
         <bmc_file example>
           /tmp/fw/062-03711bmc_b01.03r04.81s04.08.bin

     (2) The update process will take approximately 30 minutes.
         When the following messages are displayed the update has completed.
         
         <Example, when an update succeeded>
          ----------------------------------------------
          Updated firmware on the device at path 11/120.
          Updated firmware on the device at path 10/120.
          ----------------------------------------------

         <Example, when an update succeeded at only one side>
         ----------------------------------------------
         Updated firmware on the device at path 11/120.
         Tried to update firmware on the device at path 10/120.  <-- The update failed.
         ----------------------------------------------

     (3) Confirm whether the update process has succeeded by using the following
         If the update fails on one or both sides, try again from (1).

         # /opt/ft/bin/ftsmaint ls 10/120

         <Example>
          ----------------------------------------------
          Op State : DUPLEX
          :
          Firmware Rev : 04.81/01.03/04.08
          ----------------------------------------------

         If [Op State] is 'DUPLEX' and [Firmware Rev] is '04.81/01.03/04.08' then
         the Firmware update has completed successfully.

         Confirm whether the other module update process has succeeded 
         using the following command.

         # /opt/ft/bin/ftsmaint ls 11/120

         <Example>
          ----------------------------------------------
          Op State : DUPLEX
          :
          Firmware Rev : 04.81/01.03/04.08
          ----------------------------------------------

         If [Op State] is 'DUPLEX' and [Firmware Rev] is '04.81/01.03/04.08' then
         the Firmware update has completed successfully.

     (4) Confirm the System FT LED lights in green.

     (5) After Firmware update completes, delete the unzip file and directory
         if necessary.

  3-3.Procedure after the update.

     (1) Restore the BMC settings you saved in preparation for the update.
         Run the following command.
         When the "OK" messages are displayed the restore has completed.

         # /opt/ft/bin/ftsmaint restoreBmcs

         <Example>
         ----------------------------------------------
         # /opt/ft/bin/ftsmaint restoreBmcs

         OK.
         ----------------------------------------------

--------------------------------------------------------------------------------
4.  Revision history

October. 2015 BMC Firmware Revision: 04.34
  -first edition

August. 2016 BMC Firmware Revision: 04.64
  - For security measure, OpenSSL is renewed in 1.0.1m base.
  - EXPRESSSCOPEEngine3 is TLS1.1/1.2 supported.
  - When repeating ssh login to BMC, memory leak of BMC occurred, and the problem
     that BMC resets after that was improved.
    When repeating ssh login and ssh logout for 24 hours by one minute interval,
     BMC reset occurs in about 15 days.
    When it's at the timing of repeat above-mentioned, the phenomenon which can't
     do ssh login to BMC occurs several hours before BMC reset.
    Further, when BMC was reset, IO modules becomes Simplex state temporarily,
     and after that, it's restored to Duplex state automatically.
    But ft-server sometimes doesn't restore to Duplex state and does reboot.

October. 2017 BMC Firmware Revision: 04.71
  - For security measure, OpenSSL is renewed in 1.0.1t base.
  - When connecting to EXPRESSSCOPEEngine3 the message "If Javascript is Enabled
     on your web browser, automatically change to loginpage." is displayed to 
    the browser and the login screen was not displayed, this problem is corrected.
    When this problem occurred, the phenomenon you can't access to BMC from 
    NEC ESMPRO Manager also occurs.
  - The problem that the setting of user for EXPRESSSCOPEEngine3 can be changed 
    from outside was corrected.
  - When ManagementLAN (BMC-LAN) received a JumboFrame packet, the problem that 
    network of EXPRESSSCOPEEngine3 stopped working any more was corrected.
  - When BMC firmware changed the path of IPMB access, SEL which was outputting 
    is easy to mistake for an error. Therefore this SEL was deleted.
  - The problem that vertical stripes sometimes display to RemoteKVM was 
    corrected.
  - Interface between the driver on OS and BMC was improved.
  - Enhanced the automatic recovery feature of BMC.
  - The problem that the SNMP alert from EXPRESSSCOPEEngine3 isn't rarely issued
    in the VMware environment was corrected.

October. 2021 BMC Firmware Revision: 04.81
  - Supported OpenJDK12 or later in Java.
    If you use OpenJDK, you also need IcedTea-Web.
    However, IcedTea-Web has issue that using OpenJDK13 or later causes java apps
    to fail to launch, so we recommend that you use the latest version of Amazon
    Corretto 11 instead of OpenJDK.

    IcedTea-Web
    <https://github.com/AdoptOpenJDK/IcedTea-Web/releases>

    Amazon Corretto 11
    <https://github.com/corretto/corretto-11/releases>

  - Remove the button to start the SEL/SDR/FRU/MC/Backup screen on the IPMI 
    information screen of EXPRESSSCOPE Engine 3, and add the "Launch Viewer" button.
  - When you press "Launch Viewer" button, the screen of "IPMI Information", 
    which is a Java application, is displayed, and a button to display 
    the SEL/SDR/FRU/MC/Backup screen is displayed on that screen.
  - The minimum value that can be specified for the Delay Time of AC-LINK 
    in BIOS SETUP is changed to 70 seconds. (Currently 50 seconds)
    [BIOS SETUP] -> [Server]->[Power Control Configuration]
  - BMC-LAN IPv6 addresses can now be addressed starting with "fe8".
  - Fixed an issue where remote media would become unavailable after a vulnerability
    scan on BMC-LAN port(Management LAN port).
  - The expiration date of the self-signed server certificate set by default 
    in EXPRESSSCOPE Engine 3 was extended to 2025/03/14 until 2039/10/24.
  - In rare cases, server boot failed due to cpu individual difference, but BMC 
    improvements solved this problem.
  - Improved the problem that didn't sometimes have response when the remote media
    of EXPRESSSCOPE Engine 3 connected.

  *Notes after updating to BMC 4.81 (Windows only)

   (1) The following warning log may be registered once in the system event log
       after Windows startup, but in the case of one time, there is no problem,
       so you may ignore it.

        ------------------------
        Event ID    : 3101
        Source      : ESMCommonService
        Description : Failed saving BMC config.
        ------------------------

   (2) When the same warning log as (1) is registered continuingly every 1 minute
       with the following case.

       <The case that occurs>
        - After BMC firmware update
        - After module replacement
        - After Windows start

      In this case, you can solve it by restarting the Windows service.
      Follow these steps to restart the "ftSys Maintenanceand Diagnostics(MAD)" 
      service.

      (2)-1 Rename the below folder for backup.
            before: C:\Program files\ftsys\Vtm\config
            after:  C:\Program files\ftsys\Vtm\config_bak

      (2)-2 Open [Control Panel](view by : Large icons or Small icons) -> 
            [Administrative Tools] -> [Services]

      (2)-3 The management window of [Services] is started.
            It chooses "ftSys Maintenance and Diagnostics (MAD)" from a screen 
            on the right side and displays a right-click menu.

      (2)-4 Select [Restart] from the right-click menu.

      (2)-5 The [Service Control] window is displayed, and the progress bar of 
            [stop] and [start] the service is displayed, and when this window 
            disappears automatically, it is completed.

      (2)-6 It is OK if you check the event log of the system and the relevant 
            warning log is no longer registered.

            Note) If you continue to have a warning log registered after this
                  operation, please contact us.

--------------------------------------------------------------------------------
5.  Legal notices (trademarks and copyrights)

All contents on this software are the copyright of NEC Corporation or the 
third-party software developer.

EXPRESSSCOPE is a registered trademark of NEC Corporation.

Microsoft, Windows, Windows Server and Internet Explorer are either registered
trademarks or trademarks of Microsoft Corporation in the United States and/or 
other countries.

Linux is a trademark or registered trademark of Linus Torvalds in Japan and
other countries. Red Hat and Red Hat Enterprise Linux are trademarks or 
registered trademarks of Red Hat, Inc. in the United States and other countries.

VMware, VMware ESXi and VMware vSphere are registered trademark or trademark
of VMware, Inc in the United States and/or other jurisdictions. All other marks
and names mentioned herein may be trademarks of their respective companies.

Java are registered trademark or trademark of Oracle Corporation 
in the United States and/or other jurisdictions. All other marks and names 
mentioned herein may be trademarks of their respective companies.

Amazon Corretto are either registered trademarks or trademarks of Amazon Web
Services, Inc. in the United States and/or other countries.

IcedTea-Web is open source software of the GNU Lesser General Public License.

All other company names and product names mentioned herein are registered 
trademarks or trademarks of their respective owners.
