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

[Contents]
1.  About the software
2.  Server models for update
3.  Update procedures
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.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.

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.

-------------------------------------------------------------------------------
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


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>:

   Without ExpressUpdate, follow the procedure below.

   3-1. Preparation of Update

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

     (2) Log-in the system as a user with administrator privilege for 
         the local machine.

     (3) Terminate all running applications.

     (4) Download the zipped file into any hard disk directory and 
         unzip the file into any directory.

     (5) Save the current BMC setting.
         The current BMC setting is saved in files in the ft control software
         by putting the following procedure into effect.
         1. Run software of BMC Configuration.

            <Windows Server(R) 2008 R2>
            (Start->All programs->BMC_Configuration->BMC Configuration)

            <Windows Server(R) 2012 R2>
            (Start->(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. Click "Apply" button.(The other operation is unnecessary)
         4. 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.
         5. Click "Close" button.
         6. Please wait for about 1 minute. And to the next.

   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->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] 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.71 Boot=01.03 Sdr=04.08
           ID 11/120 : Runtime=04.71 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.

     (5) After the Firmware update completes delete the unzipped files if necessary.


 - <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 the running applications.

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

         Only the following file is used by Firmware update.
         '062-03711bmc_b01.03r04.71s04.08.bin'

     (5) Save the current BMC setting.
         Run the following command.
         When the "OK" messages are displayed the save has completed.

         # /opt/ft/bin/ftsmaint saveBmcs

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

         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/062-03711bmc_b01.03r04.71s04.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.71 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].
         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.71 Boot=01.03 Sdr=04.08

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

    (15) After Firmware update completes, delete the unzipped files if necessary.


 - <VMware ESXi(R)>:

   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.

         note) Only the following file is used by Firmware update.
               '062-03711bmc_b01.03r04.71s04.08.bin'

     (6) Use the VMware vSphere(R) Client to store the BMC firmware file in the
         desired directory of the ftSys Management Appliance.

         1. After the unzip file is written on CD/DVD, the CD/DVD is installed
             in the Management PC which is contains the VMware vSphere(R) Client.

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

         3. After login to the ftSys Management Appliance as a root user,
            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. BMC firmware file is copied to the desired directory of 
            the ftSys Management Appliance from the CD/DVD.

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

            Write down the path to the directory which contains the file.

            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.71s04.08.bin
                after : 062_03711bmc_b01_03r04_71s04_08.bin
                        '-'(hyphen) and '.'(period except the file extension),
                        change to '_'(underscore).

         5. After the BMC firmware file is copied unmount the 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 the toolbar in the 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.
         ----------------------------------------------

   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 you have copied in Section 3-1 (6) Step 4."

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

     (3) Confirm whether the update process has succeeded by using the following

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

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

         If [Op State] is 'DUPLEX' and [Firmware Rev] is '04.71/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.71/01.03/04.08
          ----------------------------------------------

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

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

     (5) After the Firmware update completes delete the unzipped files and 
         directory if necessary.


--------------------------------------------------------------------------------
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.


--------------------------------------------------------------------------------
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.

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